Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A dialog informing about a problem was detected spawns every boot #85

Open
jfernandz opened this issue Sep 12, 2020 · 5 comments
Open

Comments

@jfernandz
Copy link

Expected behavior
No spawning dialog

Actual behavior
A dialog spawns saying "a problem was detected..."

Steps To Reproduce

  1. Boots the system as usual

Screenshots
lightdm

Additional context
I'm using lightdm-webkit2-greeter instead lightdm-webkit-greeter because I didn't want to package webkitgtk if webkit2gtk is available in the official repos. Then I was wondering if this is caused because aether theme is not compatible with webkit2gtk

@NoiSek
Copy link
Owner

NoiSek commented Sep 15, 2020

You'll have to provide logs of some kind, there isn't anything to go off of here and that could be happening for a number of reasons.

Try checking /var/log/lightdm/lightdm.log for further information.

@jfernandz
Copy link
Author

@NoiSek here you have the lightdm.log

[+0.03s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=484
[+0.03s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.03s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.03s] DEBUG: Registered seat module local
[+0.03s] DEBUG: Registered seat module xremote
[+0.03s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.03s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.04s] DEBUG: Monitoring logind for seats
[+0.04s] DEBUG: New seat added from logind: seat0
[+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.04s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.04s] DEBUG: Seat seat0: Starting
[+0.04s] DEBUG: Seat seat0: Creating greeter session
[+0.06s] DEBUG: Seat seat0: Creating display server of type x
[+0.09s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.09s] DEBUG: Using VT 7
[+0.09s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.09s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.09s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.09s] DEBUG: XServer 0: Launching X Server
[+0.09s] DEBUG: Launching process 495: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.09s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.09s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.09s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+8.13s] DEBUG: Loading users from org.freedesktop.Accounts
[+8.13s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+11.82s] DEBUG: Got signal 10 from process 495
[+11.82s] DEBUG: XServer 0: Got signal from X server :0
[+11.82s] DEBUG: XServer 0: Connecting to XServer :0
[+11.83s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+11.83s] DEBUG: Session pid=558: Started with service 'lightdm-greeter', username 'lightdm'
[+12.24s] DEBUG: Session pid=558: Authentication complete with return value 0: Success
[+12.24s] DEBUG: Seat seat0: Session authenticated, running command
[+12.24s] DEBUG: Session pid=558: Running command /usr/bin/lightdm-webkit2-greeter
[+12.24s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+12.24s] DEBUG: Session pid=558: Logging to /var/log/lightdm/seat0-greeter.log
[+14.13s] DEBUG: Activating VT 7
[+14.13s] DEBUG: Activating login1 session c1
[+14.13s] DEBUG: Seat seat0 changes active session to c1
[+14.13s] DEBUG: Session c1 is already active
[+60.49s] DEBUG: Greeter connected version=1.30.0 api=1 resettable=false
[+66.97s] DEBUG: Greeter requests data directory for user wyre
[+66.97s] DEBUG: Creating shared data directory /var/lib/lightdm-data/wyre
[+108.80s] DEBUG: Greeter start authentication for wyre
[+108.80s] DEBUG: Session pid=3503: Started with service 'lightdm', username 'wyre'
[+108.92s] DEBUG: Session pid=3503: Got 1 message(s) from PAM
[+108.92s] DEBUG: Prompt greeter with 1 message(s)
[+112.35s] DEBUG: Continue authentication
[+112.38s] DEBUG: Session pid=3503: Authentication complete with return value 0: Success
[+112.38s] DEBUG: Authenticate result for user wyre: Success
[+112.38s] DEBUG: User wyre authorized
[+113.40s] DEBUG: Greeter requests session i3-gnome
[+113.40s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+113.40s] DEBUG: Terminating login1 session c1
[+113.41s] DEBUG: Session pid=558: Sending SIGTERM
[+113.59s] DEBUG: Greeter closed communication channel
[+113.59s] DEBUG: Session pid=558: Exited with return value 1
[+113.59s] DEBUG: Seat seat0: Session stopped
[+113.59s] DEBUG: Seat seat0: Greeter stopped, running session
[+113.59s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+113.60s] DEBUG: Session pid=3503: Running command /etc/lightdm/Xsession gnome-session-i3
[+113.60s] DEBUG: Creating shared data directory /var/lib/lightdm-data/wyre
[+113.60s] DEBUG: Session pid=3503: Logging to .xsession-errors
[+116.58s] DEBUG: Activating VT 7
[+116.58s] DEBUG: Activating login1 session 2
[+116.58s] DEBUG: Seat seat0 changes active session to 
[+116.58s] DEBUG: Seat seat0 changes active session to 2
[+116.58s] DEBUG: Session 2 is already active

seat0-greeter.log just have a single line:

(lightdm-webkit2-greeter:575): Gtk-CRITICAL **: 08:48:17.148: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

But I don't see noting strange. What I've just noticed is that the error may be independent of the theme, because I've disabled all themes and with plain lightdm-webkit2-greeter the dialog is still spawning. 🤔

@mattdmoore
Copy link

Hiya, I've just had this exact same issue; it was due to not changing the folder name after extracting Aether when installing it manually. I renamed the folder in /usr/share/lightdm-webkit/themes/ from Aether-2.2.2 to lightdm-webkit-theme-aether and it seemed to fix the problem. Hope this helps!

@scottgreenup
Copy link

I think @mattdmoore might be right. I wanted to post my logs before trying this:

Output from /var/log/lightdm/seat0-greeter.log

CONSOLE LOG [ERROR] theme_utils.dirlist(): Error opening directory “/usr/share/lightdm-webkit/themes/lightdm-webkit-theme-aether/src/img/wallpapers/”: No such file or directory
CONSOLE LOG [ERROR] theme_utils.dirlist(): Error opening directory “/usr/share/lightdm-webkit/themes/lightdm-webkit-theme-aether/src/img/logos/”: No such file or directory

@scottgreenup
Copy link

I'll confirm that this fix works. I'd recommend updating the README.md to reflect this at the very least?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants