Bodhi 2.2.0 Pre-Release Discs
#1
Posted 28 December 2012 - 11:05 PM
Please note because these are pre-release images the testing repo is enabled by default on them. Not for stable usage machines, blah blah blah testing warnings here.
The PAE and 64bit feature the 3.7 kernel and the non-PAE features a 3.2 kernel.
Let me know what issues/niggles are found with them. In addition to removing the testing repo - these images will also have updated local docs for the final release.
~Jeff
#2
Posted 29 December 2012 - 08:31 AM
My Deviantart My personal BigBodhi 2.3 disk
#4
Posted 29 December 2012 - 03:58 PM
once, on 29 December 2012 - 01:19 PM, said:
These aren't. I was pressed for time the other day so this slipped my mind. Making this happen is on my check list for the final discs though.
I'll have to look into why the E profiles are resetting people's chosen system language - my guess is the E team setup something in their default profile to cause this, so now our newly updated profiels inherited this issue. Thanks for the heads up.
~Jeff
#5
Posted 29 December 2012 - 06:07 PM
For this version -- are we required to do a full install or will we be able to do an upgrade?
Machine #1: ASUS SABERTOOTH Z77 LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard, Intel Core i5-3550 Ivy Bridge 3.3GHz, G.SKILL Ripjaws X Series 32GB (4 x 8GB) 240-Pin DDR3 SDRAM DDR3 1333, SSD Drive, Bodhi 2.0.1 64-bit
Machine #2 (Car PC): Foxconn AHD1S-K AMD E-350 APU (1.6GHz, Dual-Core) AMD Hudson D1 Mini ITX Motherboard/CPU Combo, 2GB Ram, SSD Drive, Bodhi 2.0.1 32-bit
#6
Posted 29 December 2012 - 06:22 PM
nasa, on 29 December 2012 - 06:07 PM, said:
For this version -- are we required to do a full install or will we be able to do an upgrade?
I will answer this, sudo apt-get dist-upgrade should be enough. I haven't yet taken a close look at it but since I plan on making a service pack bod file for it, I will sooner or latter
"No technology can ever be too arcane or complicated for the black t-shirt crowd."
#7
Posted 29 December 2012 - 07:05 PM
Midori opening first time gives error, page can not be found. The address misses an extra starting /
Will do more testing this weekend, I hope. And give feedback to the doc team too.
Charles.
EEE PC 901, 1GB RAM, 12 GB SSD, WIN-XP SP3, Bodhi 1.4.0
How to mark a thread as [SOLVED]
The Bodhi Guide to Enlightenment
#8
Posted 30 December 2012 - 01:42 AM
Vince
Google Nexus 7 Tablet 16GB model
Gateway LT4010u netbook with 2GB RAM & Intel's Atom N2600 processor
#9
Posted 30 December 2012 - 03:53 PM
Localization parameters/options chosen during the installation aren't applied.
The E file manager can't execute a file and reports some error, after cliking on the file's icon.
#10
Posted 30 December 2012 - 06:27 PM
#11
Posted 30 December 2012 - 08:52 PM
Jeff, on 30 December 2012 - 06:27 PM, said:
~Jeff
that's the VBoxLinuxAdditions.run file. The error with the E File Manager is reported by Enligntenment as "the application failed to start". After that I also installed the PCManFM and LXterminal. When I choose to run the file in the terminal by double clicking on the icon in in PCManFM, nothing happens.
The later is the procedure I generally use, and used, to install the guest additions in 2.0.1.
#12
Posted 30 December 2012 - 08:58 PM
meanpt, on 30 December 2012 - 08:52 PM, said:
The later is the procedure I generally use, and used, to install the guest additions in 2.0.1.
As far as I know that .run file needs to be launched in a terminal.
~Jeff
#14
Posted 31 December 2012 - 01:39 PM
Vince
Google Nexus 7 Tablet 16GB model
Gateway LT4010u netbook with 2GB RAM & Intel's Atom N2600 processor
#16
Posted 31 December 2012 - 04:50 PM
~Jeff
#17
Posted 31 December 2012 - 07:14 PM
Jeff, on 31 December 2012 - 04:50 PM, said:
~Jeff
Thanks Jeff. It's no biggie, just one of those nice to have things and if they don't want to maintain it they should just take it out all together.
Vince
Google Nexus 7 Tablet 16GB model
Gateway LT4010u netbook with 2GB RAM & Intel's Atom N2600 processor
#18
Posted 31 December 2012 - 11:54 PM
Vince, on 31 December 2012 - 07:14 PM, said:
Vince
This is a Debian and thus an Ubuntu Problem, to fix this all you need to do is type in a terminal or tty:
sudo dpkg-reconfigure resolvconf
just follow the prompts and answer the questions then restart Enlightenment..
#19
Posted 31 December 2012 - 11:56 PM
AJSlye, on 31 December 2012 - 11:54 PM, said:
In a terminal or tty type (without the quotes:
"sudo dpkg-reconfigure resolvconf"
just follow the prompts and answer the questions then reboot...
That is already done by default in Bodhi 2.2.0. He is talking about a different (input) issue with forecasts. I'm told it has been fixed in SVN recently - will need to build some updates soon.
~Jeff
#20
Posted 01 January 2013 - 12:13 AM
Jeff, on 31 December 2012 - 11:56 PM, said:
~Jeff
yes, i see this now, but the other fix still applies to not getting data even with the right code..
You can still type in the code, you just can't see it as you type. There is a fix, I just don't remember what it was.

Help
This topic is locked













