trying to diagnose login issues #297
Comments
|
Make sure you have gnome-settings-daemon and gnome-session |
|
gnome-session wasn't installed but gnome-settings-daemon was. So, installed gnome-session, Rebooted - no change - just the wallpaper. |
|
I'd check .xsession-errors or |
|
.xsession-errors - nothing really here dad@dad-VirtualBox:~$ tail -200 .xsession-errors openConnection: connect: No such file or directory cannot connect to brltty at :0 Service 'org.kde.kaccessibleapp' does not exist. journalctl -ae --full Jan 02 23:25:09 dad-VirtualBox org.a11y.atspi.Registry[3731]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jan 02 23:25:09 dad-VirtualBox gnome-session[3715]: gnome-session-is-accelerated: llvmpipe detected. Jan 02 23:25:09 dad-VirtualBox org.gnome.ScreenSaver[3627]: ** (gnome-screensaver:3765): WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files Jan 02 23:25:09 dad-VirtualBox org.ayatana.bamf[3627]: initctl: Job is already running: bamfdaemon Jan 02 23:25:09 dad-VirtualBox gnome-session[3715]: gnome-session-binary[3715]: WARNING: Could not parse desktop file budgie-desktop-polkit-gnome-authentication-agent-1.desktop or it references a not found TryExec binary Jan 02 23:25:09 dad-VirtualBox gnome-session-binary[3715]: WARNING: Could not parse desktop file budgie-desktop-polkit-gnome-authentication-agent-1.desktop or it references a not found TryExec binary Jan 02 23:25:09 dad-VirtualBox gnome-session[3715]: gnome-session-binary[3715]: WARNING: Could not parse desktop file telepathy-indicator.desktop or it references a not found TryExec binary Jan 02 23:25:09 dad-VirtualBox gnome-session-binary[3715]: WARNING: Could not parse desktop file telepathy-indicator.desktop or it references a not found TryExec binary Jan 02 23:25:10 dad-VirtualBox gnome-keyring-daemon[3459]: The PKCS#11 component was already initialized Jan 02 23:25:10 dad-VirtualBox gnome-session[3715]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Jan 02 23:25:10 dad-VirtualBox dbus[512]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Jan 02 23:25:10 dad-VirtualBox gnome-keyring-daemon[3459]: The Secret Service was already initialized Jan 02 23:25:10 dad-VirtualBox gnome-session[3715]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh Jan 02 23:25:10 dad-VirtualBox gnome-keyring-daemon[3459]: The SSH agent was already initialized Jan 02 23:25:10 dad-VirtualBox gnome-session[3715]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh |
|
ok - have got past the polkit issue - the path in /etc/xdg/autostart/budgie-desktop-polkit-gnome-authentication-agent-1.desktop is wrong (or at least I need to correct the shipped .desktop file if there is one in the deb package) - manually corrected this and this error is no longer shown. I don't think the telepathy-indicator is relevant - again - install telepathy-indicator and this message has gone. this just leaves this in journalctl -ae --full Jan 03 00:13:30 dad-VirtualBox gnome-session[7521]: pci id for fd 11: 80ee:beef, driver (null) Jan 03 00:13:30 dad-VirtualBox gnome-session[7521]: libGL error: core dri or dri2 extension not found Jan 03 00:13:30 dad-VirtualBox gnome-session[7521]: libGL error: failed to load driver: vboxvideo Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-wm:7742): GLib-GObject-WARNING **: invalid (NULL) pointer instance Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-wm:7742): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-panel:7750): GLib-GObject-WARNING **: cannot register existing type 'BudgieDesktopManager' Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-panel:7750): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-panel:7750): GLib-GObject-CRITICAL **: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-panel:7750): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed Jan 03 00:13:31 dad-VirtualBox gnome-session[7521]: (budgie-panel:7750): GLib-GObject-CRITICAL **: g_object_new_valist: object class 'BudgieRaven' has no property named 'manager' |
|
The polkit file is going to disappear soon. I'll have to see why Vala/GLib is being a dipshit about the BudgieDesktopManager API. |
|
polkit file gone |
|
looking back at the compilation of budgie via the deb there are quite a few warnings about incompatible pointer type assignments and other stuff - see line 4064/3875 as a couple of examples. Anything here that is a worry that maybe causing budgie-wm/panel to throw those critical errors above? |
|
No it's just a combination of two factors. The horror-show that is the internals of gobject (aka struct casting) and the abomination that is Vala's autogenerated C code. |
|
@ikeydoherty - do you have handy a list of files and their file locations where budgie-desktop is installed? What I want to check is to see if my debian package is building correctly and putting stuff in the correct place when the .deb is actually installed. |
|
File list for budgie-desktop: File list for budgie-desktop-devel: These file lists are from the Solus packaging |
|
(Also that's 10.2.2 not git) |
|
thanks - looks like I'm packaging the same files in the same file locations. Any other way I can get more debug info out of the various components on startup? |
|
Edit the /usr/bin/budgie-desktop file to pass --debug to gnome-session |
|
thanks - any of this make any sense? |
|
|
hmm - thanks. Tried as you have said - now have gnome-shell, unity and budgie installed. Same error as you have found above - whatever that whale is ... its dead. |
|
o_O Alright can you see if you're able to launch budgie-panel from one of the other desktops? Just to ensure it's not broken :D |
|
From Unity dad@dad-VirtualBox:~$ budgie-panel & [1] 10221 dad@dad-VirtualBox:~$ (budgie-panel:10221): GLib-GObject-WARNING **: cannot register existing type 'BudgieDesktopManager' (budgie-panel:10221): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (budgie-panel:10221): GLib-GObject-CRITICAL **: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed (budgie-panel:10221): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed (budgie-panel:10221): GLib-GObject-CRITICAL **: g_object_new_valist: object class 'BudgieRaven' has no property named 'manager' If I launch budgie-desktop I get to the wallpaper only screen and I can use CTRL+ALT+T to launch a terminal. dad@dad-VirtualBox:~$ budgie-panel & [1] 10650 dad@dad-VirtualBox:~$ ** Message: manager.vala:898: Another panel is already running. Use --replace to replace it [1]+ Done budgie-panel dad@dad-VirtualBox:~$ budgie-panel --replace & [1] 10654 dad@dad-VirtualBox:~$ (budgie-panel:10654): GLib-GObject-WARNING **: cannot register existing type 'BudgieDesktopManager' (budgie-panel:10654): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed (budgie-panel:10654): GLib-GObject-CRITICAL **: g_param_spec_object: assertion 'g_type_is_a (object_type, G_TYPE_OBJECT)' failed (budgie-panel:10654): GLib-GObject-CRITICAL **: g_object_class_install_property: assertion 'G_IS_PARAM_SPEC (pspec)' failed (budgie-panel:10654): GLib-GObject-CRITICAL **: g_object_new_valist: object class 'BudgieRaven' has no property named 'manager' Note - I can also right click the wallpaper and see the menu options "change background" and "Settings" - both invoke what they should so - is that gnome-session or some part of budgie window manager running? The terminal has a background shadow - so it looks like the window manager/compositor of somesort is running. |
|
The right click stuff is budgie-wm. Looking at the error there's a deep issue in the type system from your vala/glib combination. I'll have to do some workarounds to get it up and running. |
|
I am right on this - a GPL project like sparky are supposed to supply their source when requested? |
|
I've had a look at the LiveCD, Budgie is unmodified entirely in Sparky Linux. The customisations are (unfortunately) made by use of I'd actually like to talk with the developer on improving this, they should be using gschema overrides to achieve their default L&F As for how they distribute their package, well, I'm not a lawyer, so unless I start getting screwed over, I'd like to stay out of it. |
|
ok - I had a feeling the project was doing that. Will let you know if the package they use becomes available. |
|
ok - think I understand now what sparky have done. They compile and install manually via ./autogen --prefix=/usr Then they create a .deb from the prebuilt binaries and ship that. Its not a method Debian nor Ubuntu etc allows - you must build in a relative folder way (i.e. debuild) and the built package moves the built binaries stored in the debian/tmp/usr/... folders to their correct location i.e. ./debian/tmp/usr/share/budgie-desktop/xyz not /usr/share/budgie-desktop/xyz I guess there is something in budgie-desktop compilation that doesnt like this relative folder building method e.g. /usr/share/gir-1.0/Budgie-1.0.gir is 35.7Kb when manually built but via a debian build - Budgie-1.0.gir is only 6kb in size. EDIT: (24/01) dont think the .gir file size is relevant. When building via debian package debian/tmp/usr/lib/libbudgie-plugin.so.0.0.0 is size 22808 bytes whereas if you compile and install manually /usr/lib/libbudgie-plugin.so.0.0.0 is size 110528 Thus - what is NOT being compiled into libbudgie-plugin.so.0.0.0 ? Any thoughts @ikeydoherty ? |
|
ok - going to close this. I cannot fix this under Ubuntu 16.04. Whatever ubuntu is doing whilst building a .deb package is not happening if I build under debian testing - debian testing works fine. I can even take the built debian testing package and install that under Ubuntu 16.04! everything works ok. It's a shame - I wanted to give budgie-desktop the massive attention it deserves by the huge ubuntu + ubuntu derivative users :( Anyway good luck with future versions of budgie @ikeydoherty |
What's the best way to try and diagnose why I get a blank screen with just the wallpaper - after 30 seconds I then get dumped back to the login screen.
I've looked at /var/log/syslog - the last 200 lines has various budgie type warnings - any of these makes sense?
Should I remake the .deb with DEBUG on and relook at syslog? i.e. ./configure --enable-debug ?
The text was updated successfully, but these errors were encountered: