you wont believe how often that one has rebooted today.
after reboot:
I found a new (e16?) bug: after suspend the touchpad doesn't work but touchscreen does.
i think that the DBUS session is lost when restoring from suspension, but we need to verify that this does (or does not) happen in E22 too, to know if is a specific bug of e16 or the system itself
yeah i assumed that you should have do that, but just in case...
what if you do "sudo ifconfig" ? asks for sudo password? what you need to accomplish is to run the command from sudo without asking for the password
sudo ifconfig works fine.In the meantime there's more going on:
The machine will not shutdown now.
Going to sleep now. Have to get up in 5 hours. 
Wait @triantares, maybe the issue is with systemd,
sudo service sudo restart
this command is backwards compatible, but is not the correct one for system, it lacks things, like, if the daemon cannot be restarted it should tell you that! instead, it just looks like it is restarted. In systemd you should use this instead:
sudo systemctl restart sudo
but here i have it "masked", this means the daemon is not running? no sudo ? 
i have ifconfig working too, but if im not wrong, when you change a daemon setting (editing files like the sudo ones) you need to:
sudo systemctl daemon-reload
or... i dont know much about systemd, but maybe you are using the old provided sudo configuration and thsi is why not works
btw, you can unmask sudo too !
it shows errors in your HD, again the problematic cable? (well, it dont says HD, it just says error usb)
Maybe you have more luck if you enter in the IRC debian channel (without saying that you are in elive, otherwise they redirect you to elive lol) and ask how to change the configuration of sudo because doesn't looks like to accept your changes
So again, your goal is "sudo brightnessctl" (working without asking password)
What about calling it with the full path? like:
sudo /usr/bin/brightnessctl
same problem?
NOT URGENT
Sound (up / down) keys and Luminosity keys not working on my Dell Laptop.
I Tried to assign my keyboard keys to actual Bindings already created by Elive but it doest't work
Yoda
Note: always say "on which desktop" is the issue, so every one works in a different way 
I assume you mean E16, they should be recognized by default as multimedia keys, but maybe you have a missing package to support this specific hardware, try to google for "linux multimedia keys COMPUTERMODEL"
1 Like
My experience so far on a Dell XPS 13 L322x:
Used upgrade mode so as to not lose current data in Elive partition.
Elive recognised other partion running Bunsenlabs.
Was able to boot into Elive, but no xsession -
This may have been the problem (or coincidence) - the first attempt I selected yes - got no xsession - 2nd time I said no - no problems.
Now reaquainting myself with E16...been a long time!
I like the ocasional messages during the install:
"rearranging atoms in the Universe..."
when you ask for a donation during the install, perhaps something like:
"Please consider supporting our work so we can keep Elive Alive"
Or something -
Anyway - as an Alpha - fantastic. Nothing is on fire! (Yet).
Sound, brightness controls, networking - all good.
1 Like
So your installation was as an "upgrade mode" from an Elive system or from a Busenlabs ? (that's a different mode of the installer called "migration mode", much well tested)
Really? hum.. this is interesting, this message is only for add a mount optimization option, to me sounds like a coincidence but who knows! more exactly it adds the option "data=writeback" for the root partition in /etc/fstab 
maybe i should just remove this "feature"
Changed from:
The installation will take a while to finish, in the meantime, would you like this project to continue to exist?
to:
The installation will take a while to finish, in the meantime, please consider supporting our work so we can keep Elive alive
Did you have seen the donation message appear twice or only one time ? @jfbourdeau reported it before that was twice and I don't know if my recent changes fixed them
Wohooo! 
1 Like
after booting said laptop again I now have " sudo ifconfig" asking for the password again, just like brigtnesssctl and rfkill ....... so somethings definitely wrong there.
It' s not brightnessctl or the keys it' s the way sudo is handled by systemd, methinks.
I feel the same about having to enter admin passward to mount a partition, which creates unescessary rw problems.
Maybe it' s an idea to move on to a separate thread and call it " sudo and systemd problems" .
Seeing the live system works (well on live one is the root user, that would explain it) and the installed doesn' t ...... it would seem to be an ownership problem.
As to the shutting down and USB: That was probably me yanking out the live usb disk too soon. I was just too tired to be patient. 
You are refering to a physical install on which the brightness button work?
If so could you try " sudo ifconfig" in a terminal and report if it asks for a password (it shouldn' t).
Watch out that you haven' t previously used the sudo password in the terminal (it gets saved for a period of time) but do it in a freshly opened terminal.
I'd be very interested in the result.
Thank you.
In my case, a shared ext4 partition (with new elive user added BTW)
will not start X. Not even after several tries ..... will look into that later. First things first. 
dded /usr/bin/sudo to the conf file, after unmasking service.sudo and reloading and even rebooting,
The picture is the howto.
But still: No joy!
That only leaves using " visudo" to alter the main sudoers file, evne if it' s only to test.
Installed on an yoga ideapad and the same issue -even " dmesg " requires sudo.
I am actually surprised others have their brightness working in the install.
ok I reinstalled Elive 3.7.0 E16 to test GRUB / multi boot installation
Drive 2 SATA 1 Sdb Manjaro
Drive 1 SATA 0 sda Elive
ELive installed, and in the log window said it saw manjaro. Didn't ask me where to put grub
Result after installation
- PC boot on Manjaro by default. SATA 0, sda is the default, 1st drive (in the order to boot)
- if I force the boot to Manjaro through BIOS ( F+key to choose disk) and choose Manjaro disk, I see the Manjaro GRUB menu and I can boot
- if I choose through BIOS ( F+F9 ) ELive, I have some GRUB ERROR ( Grub panic, I think was the word ) and I can't boot Elive
Yoda
All this for @triantares:
yep, you need to run sudo with these commands and see that doesn't asks for password, your files are correctly configured but maybe your sudo daemon is not running, systemd probably, try to unmask and to restart? i dont know it is masked on my machine too (but it doesn't asks for passwords for me)
your e16 desktop should have booted with the startup applications needed to manage users passwords, this means, the password for mount partitions in thunar is asked only one time (ideal is never, since you already logged) and then your passwords sessions is remembered. Note that e16 (or all desktops) seems to have problems keeping the dbus session running after hibernation (after suspend too?), which can be related (you can see this by running thunar from terminal iirc, and you'll see dbus warnings)
In short, we need to isolate problems, for example:
- problem with dbus: only in e16 or in all desktops? only after to hibernate? suspend affected too?
- problem with sudo: only the configurations are not used? the daemon is running? other configurations works? its because your user has not initiated the session correctly? (you must have all the startup applications enabled by default, the ones that are already checked when you create a new desktop environment, they are preselected for elive @triantares, try that too
very probably
I added the brightness conf in the installer, so he must have it correctly working in the installed system... you can also try to reinstall @triantares lol, which is a fast step (your sudo system looks messed up but i dont know why, yet)
❯❯❯ cat /etc/sudoers.d/timeout_password
# Timeout to ask again password for next sudo commands: 1 minute
Defaults:ALL timestamp_timeout=1
This is very delicated thing, and not suggested (different versions of apps saves differents configs of apps in the user home, that can be uncompatible sharing it), the biggest problem can be caused by a different user UID
❯❯❯ echo $UID
1783
this is not related to sudo, its because now in new systems (maybe because systemd), the user is not allowed to run dmesg, so you must have privileges for run it (i know, its annoying)
have you enabled the reports during install? i don't see them in the server (sometimes the tool is stuck and doesn't receive them)
your install sounds correct, but i will need to see the logs to know where exactly was the grub installed, and the grub error for elive is pretty strange, like it didn't installed correctly on the disk for elive
I will do it again later today, I thin I didn't enable it... But I did enter my email...
Could you remind me of the extra command I need to type ?
Of entering my email was enough and you'll get your info ?
Yoda
nope, you are talking about the "user configuration", has no relation with the reports
BUT! if you run the installer as "eliveinstaller" it wont report anything
You need to:
sudo -E eliveinstaller-wrapper
(more easy: just run the installer from the menus, not from a terminal)
I am confused
So you want me to launch the installer like this and it report to you what you need ?
