3.7.3 betatesting experiences

Not in 3.7.x ? I tried to copy my photos from the iphone in the windows computer unsuccessfully, then I tried from the recent Elive and it worked like a charm :slight_smile:

cairo-dock overwrites it (just move it upper then) unless you are running the desktop with the composite option

nope, there's not a lock feature in e16

Just uploaded with the remaining tasks for it :slight_smile: should be a much better (more stable & fixes) version with also fine-tuned things, like cairo-dock default settings and other preconfigured things. @zbd I assume this version fixes all the "low ram" issues with the installation and deals it much better

installer? I assume you mean "live boot" (after first boot menu), you cannot boot the 64bit version in a computer that doesn't supports 64bit (most of netbooks in fact lol)

IMPORTANT: DO NOT USE BTRFS !

it is dangerous and unreliable filesystem even in these new version, your data is in danger (i had a second forced shutdown and lost my partition, being entirely unrecoverable), so bad btrfs...

try with 3.7.4, there should be fixes for these low-ram cases, also don't use btrfs

hum, this is curious and should not happen... but i added a code to make a second attempt on these cases (3.7.4)

mmh that's right, from internet seems like the cpu has 64bit, maybe is a bug in kernel (or grub/loader) autodetecting the cpu :thinking: or maybe a bios option, curious in any case

About Nvidia:

(@Rebel450): I had issues using the 390 version too on one of my computers, not sure where is the problem (maybe kernel version, maybe nvidia drivers...), but if somebody knows with certanity that this version of nvidia drivers works for its card, could be good to know if the issue is really with this version of driver (that should work with this version id). Note: 3.7.4 could have updated drivers if they were updated from debian

@triantares @Rebel450 : im lost about the suggestion to remove the nvidia drivers from install :slight_smile: maybe i didn't understood the point, but as explained in another place, the actual behaviour is:

  • user boots in Live mode (as much as he wants) selecting free or privative drivers (since this is the first boot tests, he will know from this point if the privative or the free drivers works better for him)
  • when the desktop has started successfully (and only after that, which means "drivers correctly working"), the user can install elive on HD
  • the same settings he selected about his nvidia are used for the installed system

and this (the last line) is IMHO the best option because ensures that the drivers correctly works, doesn't needs to ask anything to the user, will make sure that will install the same way, etc... so what if the user don't want to use privative drivers? well, just boot with the free drivers option in live mode before to enter to the desktop and start installing :thinking: other thing than "autodetected / autoselected" would be a complication for the end-users

:boogie:

hum, i wonder if this was due to a recyclated (previous OS) conf in /etc, or by an automatic printer configuration detection (which if im not wrong there's an automatic configurator somewhere in elive) or... maybe something like that :thinking:

mmh yeah, they are created on new user but not when migrating users (that doesn't has it), mmh, noted to improve in the installer

noted, that will be improved too for next builds (wrong "default WM" set)

mmh but that should be a good default case for computers that has touchscreen (only), and i dont see a way to autodetect it

@triantares this is useful info, you could move that post entry to a howto page :slight_smile:

in fact looks like the entire "dbus" connection is lost after suspend (hibernate specially?), not sure if is a e16 specific issue, probably the dbus address changes and the desktop doesn't reach it anymore, this causes multiple issues bettween applications like probably touchpad connection

or.. maybe the touchpad just doesn't correctly restores after suspension (hardware specific cases)

:eyepopping:
maybe a bug from debian-upstream, hopefully fixed for their buster release (which is near) - note: try apug to see if updates fixes that

it requires swap, but IMHO the implementation is wrong and it should create a temporal file in the / root filesystem with the space required to store the ram contents and then hibernate (this won't take more time than just write in swap, in fact), maybe a future feature for elive lol

that's a beautiful wallppaer :slight_smile: makes desktop look powerful :nod:

@Terry_Rosinski : I had data corruption due to using btrfs and I was working on recovering everything... also I was moving to colombia for 2 months :slight_smile:

some suggestions:

  • apug
  • elive-skel upgrade .config/cairo-dock
  • edit .e16/startup-applications.list

the second will update your cairo-dock with improved settings, the third is a own feature for the autolaunched applications :slight_smile:

@triantares found a way to feature a "lock" in e16 ?

btw as an option we could also just improve the e16 code to add the feature :slight_smile:

even better than the e17 experience on elive 3.0 stable ? :slight_smile: it is really well featured! (but may feel a bit slower)

added "alt + f8" for that, if you apug and restart desktop configurations
btw e16 allows you to have windows (bigger than screen) shared between their multiple desktops, so you can go back/from them and reach the other window elements

mmh, but i dont see the relation of these window sizes with e16 / elive, they -should- be already small (autoconfigurations for font sizes)

check the comments in the 3.7.4 betatesting page, but if you want to move, you should do a clean install and then copy the files

1 Like