You are not logged in.
Hey guys,
as you know, I'm running BL on my Asus 11" Cloudbook and so far I have been extremely happy with it. Yesterday (for the sake of just trying it) I decided to switch to a terminal. To my surpise, the screen flickered a little and threw me right back to the login screen of my DM. Funnily I was absolutely unable to recover any of the running programs of my existing session. I was as if my X session just got killed and OB started over again. So having a closer look I found out that I had no framebuffer device. So I tried switching over to a plain old terminal without framebuffer, but so far I have not been able.
I already tryed several boot options from Grub2 bort none of them could help me with my problem. The screen has a resolution of 1366x786.
Regards
Merlin
· My Desktop · My Laptop · Install guide · Modified bl-exit ·
Offline
Just found out that light-locker exhibits the same behaviour.
· My Desktop · My Laptop · Install guide · Modified bl-exit ·
Offline
Hi MerlinElMago,
I can not reproduce this.
I suspect this behaviour might be caused by your relatively new hardware.
Try installing the graphical stack from backports, or, if you have time and inclination, try the 'stretch' or 'sid' repos.
BTW.
Thanks again for you contribution to bl-exit.
If all developers agree, I will integrate the changes in the official bl-exit version.
Cheers
Offline
Those things use http://ark.intel.com/products/87257/Int … o-2_16-GHz with a non-HD Intel integrated graphics card. Not that new; perhaps it's a driver issue. Can you look if there is something interesting in the syslog and the Xorg log? Also please post the output of lsmod and lspci.
Two suggestions: Upgrade to a kernel from jessie-backports. There are threads on this already.
Or try uninstalling the xserver-xorg-video-intel user space driver and reboot; this will use Xorg modesetting instead.
Offline
Just found out that light-locker exhibits the same behaviour.
When you say Light-locker exhibits the same behavior, do you mean that running the light-locker-command -l command and try to log back into that very session, it shuts down all of your programs running through openbox?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Those things use http://ark.intel.com/products/87257/Int … o-2_16-GHz with a non-HD Intel integrated graphics card. Not that new; perhaps it's a driver issue. Can you look if there is something interesting in the syslog and the Xorg log? Also please post the output of lsmod and lspci.
Two suggestions: Upgrade to a kernel from jessie-backports. There are threads on this already.
Or try uninstalling the xserver-xorg-video-intel user space driver and reboot; this will use Xorg modesetting instead.
Some additional info on mode setting for those interested..:
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Or try uninstalling the xserver-xorg-video-intel user space driver and reboot; this will use Xorg modesetting instead.
That is only recommended for use with newer Xorg versions than Bunsenlabs has, performance would be poor with the modesetting driver in BL.
@OP: Try editing /etc/default/grub and un-comment this line:
GRUB_TERMINAL_OUTPUT=console
Then save the file and update your GRUB configuration:
sudo grub-mkconfig -o /boot/grub/grub.cfg
This will disable the graphical console; there may be an incompatibility with the resolution set there and your graphics card.
Alternatively, try adding "nomodeset" as a kernel command line parameter:
https://wiki.archlinux.org/index.php/Ke … eters#GRUB
Offline
First of all... thanks for your help.
@xaos52:
Of course you are allowed to use my code for bl-exit. After all, that's what I postied it for
I have tried booting with terminal output to console... and that is the strange thing. I'm absolutely unable to get any console, be it regular text mode or framebuffer.
I will try and upgrade my kernel version. I was reluctant to do this because of the warning titled "don't break bunsenlabs"
When you say Light-locker exhibits the same behavior, do you mean that running the light-locker-command -l command and try to log back into that very session, it shuts down all of your programs running through openbox?
Yep, exactly. Whatever I run, bl-lock or directly light-locker, throws me right back at the login promt. When I log back in, it's like a newly rebooted session, no trace of my open programs or whatsoever.
Regards
Merlin
· My Desktop · My Laptop · Install guide · Modified bl-exit ·
Offline
Anything in your systemd journalctl logs?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
I do not completely understand what's going on. Here's my journactl just when I press CTRL+ALT+F1:
jun 30 13:58:02 BunsenLaptop org.ayatana.bamf[1575]: (bamfdaemon:1679): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
jun 30 13:58:14 BunsenLaptop org.a11y.atspi.Registry[1633]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
jun 30 13:58:14 BunsenLaptop org.a11y.atspi.Registry[1633]: after 218 requests (218 known processed) with 0 events remaining.
jun 30 13:58:14 BunsenLaptop polkitd(authority=local)[490]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.55, object path /o
jun 30 13:58:14 BunsenLaptop org.freedesktop.Notifications[1575]: xfce4-notifyd: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0
jun 30 13:58:15 BunsenLaptop org.ayatana.bamf[1575]: (bamfdaemon:1679): Gdk-WARNING **: bamfdaemon: Fatal IO error 11 (Recurso no disponible temporalme
jun 30 13:58:15 BunsenLaptop org.a11y.atspi.Registry[1524]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
jun 30 13:58:15 BunsenLaptop org.a11y.atspi.Registry[1524]: after 218 requests (218 known processed) with 0 events remaining.
jun 30 13:58:15 BunsenLaptop org.a11y.Bus[1518]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes
jun 30 13:58:15 BunsenLaptop gnome-keyring-daemon[1543]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned
jun 30 13:58:15 BunsenLaptop org.a11y.Bus[1575]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes
jun 30 13:58:15 BunsenLaptop org.gtk.vfs.Daemon[1575]: A connection to the bus can't be made
jun 30 13:58:15 BunsenLaptop org.gtk.vfs.Daemon[1575]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0
jun 30 13:58:15 BunsenLaptop ca.desrt.dconf[1575]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 byte
jun 30 13:58:15 BunsenLaptop lightdm[485]: ** (process:1784): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freede
jun 30 13:58:15 BunsenLaptop lightdm[1784]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
jun 30 13:58:15 BunsenLaptop systemd-logind[446]: New session c3 of user lightdm.
jun 30 13:58:15 BunsenLaptop org.a11y.Bus[1793]: Activating service name='org.a11y.atspi.Registry'
jun 30 13:58:15 BunsenLaptop org.a11y.Bus[1793]: Successfully activated service 'org.a11y.atspi.Registry'
jun 30 13:58:15 BunsenLaptop org.a11y.atspi.Registry[1799]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
jun 30 13:58:17 BunsenLaptop systemd-logind[446]: Removed session c2.
jun 30 13:58:20 BunsenLaptop systemd-logind[446]: Removed session 2.
jun 30 13:58:21 BunsenLaptop lightdm[485]: ** (process:1807): WARNING **: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freede
jun 30 13:58:21 BunsenLaptop lightdm[1784]: pam_unix(lightdm-greeter:session): session closed for user lightdm
jun 30 13:58:21 BunsenLaptop lightdm[1807]: pam_unix(lightdm:session): session opened for user merlin by (uid=0)
jun 30 13:58:21 BunsenLaptop systemd-logind[446]: New session 3 of user merlin.
jun 30 13:58:22 BunsenLaptop org.a11y.Bus[1852]: Activating service name='org.a11y.atspi.Registry'
jun 30 13:58:22 BunsenLaptop polkitd(authority=local)[490]: Registered Authentication Agent for unix-session:3 (system bus name :1.70 [/usr/lib/policyk
jun 30 13:58:22 BunsenLaptop org.a11y.Bus[1852]: Successfully activated service 'org.a11y.atspi.Registry'
jun 30 13:58:22 BunsenLaptop org.a11y.atspi.Registry[1906]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Regards
· My Desktop · My Laptop · Install guide · Modified bl-exit ·
Offline
bamfdaemon
??
Installed from ubuntu?
Try removing it again and see if it solves your problem
Cheers
EDIT:
Sorry. I may have jumped to conclusions. I did not know bamfdaemon, so I presumed it was from Ubuntu.
But I now see it is in Debian too.
Offline
You're getting bounced to lightdm? What if you remove lightdm temporarily, what happens?
sudo apt remove lightdm lightdm-*
I don't care what you do at home. Would you care to explain?
Online