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.

Sign up for GitHub

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

Jump to bottom

cinnamon crashes on second user login #6590

Closed
mabod opened this issue Jun 8, 2017 · 25 comments
Closed

cinnamon crashes on second user login #6590

mabod opened this issue Jun 8, 2017 · 25 comments

Comments

@mabod
Copy link

mabod commented Jun 8, 2017

Hi,
when I have one user logged into cinnamon, the second user trying to do that in parallel has cinnamon crashing.

I tested with two fresh installs of Manajaro. It works fine on my laptop with new home directories. But the crash is reproducible on my PC with "legacy" home directories from several month ago and older cinnamon versions.

.xsession-errors says:

(cinnamon:1549): Clutter-CRITICAL **: Unable to initialize Clutter: Initialisierung des Clutter-Backends nicht möglich: Keine Treiber verfügbar.
Window manager error: Unable to initialize Clutter.
Traceback (most recent call last):
File "/usr/bin/cinnamon-launcher", line 53, in
os.execvp(FALLBACK_COMMAND, (FALLBACK_COMMAND,) + FALLBACK_ARGS)
File "/usr/lib/python3.6/os.py", line 559, in execvp
_execvpe(file, args)
File "/usr/lib/python3.6/os.py", line 604, in _execvpe
raise last_exc.with_traceback(tb)
File "/usr/lib/python3.6/os.py", line 594, in _execvpe
exec_func(fullname, *argrest)
FileNotFoundError: [Errno 2] Datei oder Verzeichnis nicht gefunden
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Looking in '/etc/xdg/parcellite/parcelliterc'
Looking in '/etc/xdg/parcellite/parcelliterc'
Looking in '/etc/xdg/parcellite/parcelliterc'
Flag 0x0001, status 0, EXIT 1 STAT 0

inxi -F:

System: Host: unten Kernel: 4.9.30-1-MANJARO x86_64 (64 bit)
Desktop: Cinnamon 3.4.1 Distro: Manjaro Linux
Machine: Device: desktop System: ASUS product: All Series
Mobo: ASUSTeK model: Z97-A v: Rev 1.xx serial: 150137258403935
UEFI [Legacy]: American Megatrends v: 2401 date: 04/24/2015
CPU: Quad core Intel Core i5-4460 (-MCP-) cache: 6144 KB
clock speeds: max: 3400 MHz 1: 841 MHz 2: 800 MHz 3: 800 MHz
4: 800 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210]
Display Server: X.org 1.19.3 driver: nvidia
tty size: 80x24 Advanced Data: N/A for root
Audio: Card-1 NVIDIA High Definition Audio Controller
driver: snd_hda_intel
Card-2 MCS driver: USB Audio
Sound: Advanced Linux Sound Architecture v: k4.9.30-1-MANJARO
Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full
mac: 08:62:66:31:50:18
Drives: HDD Total Size: 2080.4GB (51.8% used)
ID-1: /dev/sda model: INTEL_SSDSA2M080 size: 80.0GB
ID-2: /dev/sdb model: WDC_WD20EARX size: 2000.4GB
Partition: ID-1: / size: 24G used: 9.2G (41%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 46G used: 32G (75%) fs: ext4 dev: /dev/sda3
ID-3: /opt size: 1.8T used: 964G (56%) fs: ext4 dev: /dev/sdb1
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C
Fan Speeds (in rpm): cpu: 0
Info: Processes: 215 Uptime: 8 min Memory: 1702.3/7931.7MB
Client: Shell (bash) inxi: 2.3.9
@mabod
Copy link
Author

mabod commented Jun 8, 2017

It probalby has nothing to do with old vs. new home directories. The issue even occurs with newly created suers.

@leigh123linux
Copy link
Contributor

leigh123linux commented Jun 8, 2017 •
edited
Loading

This error indicates a graphics driver issue

(cinnamon:1549): Clutter-CRITICAL **: Unable to initialize Clutter: Initialisierung des Clutter-Backends nicht möglich: Keine Treiber verfügbar.
Window manager error: Unable to initialize Clutter.

and this is because the Manajaro dev is too lazy to add metacity, gnome-panel or tint2 deps to cinnamon package.

File "/usr/bin/cinnamon-launcher", line 53, in
os.execvp(FALLBACK_COMMAND, (FALLBACK_COMMAND,) + FALLBACK_ARGS)
File "/usr/lib/python3.6/os.py", line 559, in execvp
_execvpe(file, args)
File "/usr/lib/python3.6/os.py", line 604, in _execvpe
raise last_exc.with_traceback(tb)
File "/usr/lib/python3.6/os.py", line 594, in _execvpe
exec_func(fullname, *argrest)
FileNotFoundError: [Errno 2] Datei oder Verzeichnis nicht gefunden

@mabod
Copy link
Author

mabod commented Jun 8, 2017

Excuse me, but this does not explain why it works on 2 PCs and not on the third. All three PCs have a fresh Manjaro installation.

What exactly is missing from your point of view? metacity and gnome-panel and tint2 are not installed on any of the 3 PCs.

@mabod
Copy link
Author

mabod commented Jun 8, 2017 via email

@mtwebster
Copy link
Member

Are both users using a DM (lightdm?) which then starts cinnamon-session? Any user logged in and any other user crashes? Or is there a user common to this?

@leigh123linux
Copy link
Contributor

leigh123linux commented Jun 8, 2017 •
edited
Loading

If it works fine on 2 it indicates the third has some graphics driver issue.

Excuse me, but this does not explain why it works on 2 PCs and not on the third. All three PCs have a fresh Manjaro installation.

I was explaining why you had the output warning, they aren't directly related to critical clutter warning.
metacity, gnome-panel and tint2 provide the fallback session when X is broken.

What exactly is missing from your point of view? metacity and gnome-panel and tint2 are not installed on any of the 3 PCs.

@mabod
Copy link
Author

mabod commented Jun 8, 2017 via email

@oberon-manjaro
Copy link
Contributor

because the Manajaro dev is too lazy...

@leigh123linux , Manjaro packager here. It would have been nice to have received this information in a more neutral or even friendly way.
Archlinux btw doesn't list these dependencies either - I guess they are equally lazy packagers?
Why don't you simply list the dependencies in the README instead of making sloppy remarks like this?

@leigh123linux
Copy link
Contributor

leigh123linux commented Jun 9, 2017 •
edited
Loading

@Oberon2007 Don't get me started on Arch :-)

It isn't a recent change either (nearly 4 years old).

383e70c

Don't give me any of your crappy attitude as the deps are clearly listed in the control files!

Why don't you simply list the dependencies in the README instead of making sloppy remarks like this?

https://github.com/linuxmint/Cinnamon/blob/master/debian/control#L46

@JosephMcc
Copy link
Contributor

@mabod What happens if you use the open source nvidia driver on the machine with the issue? I'm fairly certain we've seen other people have issues with the legacy drivers.

@clefebvre
Copy link
Member

because the Manajaro dev is too lazy...

@leigh123linux I agree with @Oberon2007 on this, there's really no need to go at each other for no reason like this. Let's leave distrowars to fanboys and trolls and talk about more interesting things.

@leigh123linux
Copy link
Contributor

leigh123linux commented Jun 9, 2017 •
edited
Loading

@mabod why are you using an old nvidia version? what kernel are you using?

The PC with issue is having a NVIDIA GT218 running legacy driver nvidia 340.101

340.101/340.102 doesn't work with 4.9+ kernel without patching

@oberon-manjaro
Copy link
Contributor

Thank you @clefebvre .
In any case to me it looks in the above output like what actually dumps core first is gnome-panel?
Installing gnome-panel, metacity and tint2 additionally apparently didn't help in this case.

@leigh123linux
Copy link
Contributor

@clefebvre My gripe was about sloppy packaging.
@Oberon2007 sorry if I offended you.
I'm 99.9999% certain that the issue is caused by a broken X (nvidia) driver and not related to cinnamon.

@clefebvre
Copy link
Member

Well you can probably reproduce the issue with another DE, take a minimal one for instance... Blackbox or something like that. Open two sessions, see if the second one has 3D acceleration (inxi -Gx or similar).

@oberon-manjaro
Copy link
Contributor

From what I gather, the single user is able to launch the session fine. The issue seems to occur only when other sessions are already open. That seems weird because it would mean that the driver does actually work with the cinnamon session...

@mabod
Copy link
Author

mabod commented Jun 9, 2017 via email

@leigh123linux
Copy link
Contributor

@mabod why use the old 340.xx driver? 340.102 is current!!!!!!!!!!!!

https://www.archlinux.org/packages/extra/x86_64/nvidia-340xx/

P.S Try reading the responses properly!!!!!

@leigh123linux
Copy link
Contributor

Looking at the 340.101 build file it's only compatible with 4.9 kernel

https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/nvidia-340xx&id=80e466a0a4efcb253460324294a9addadd7fcefe

@oberon-manjaro
Copy link
Contributor

Manjaro uses neither Arch kernel nor extramodules. We build them ourselves for every kernel series: https://github.com/manjaro/packages-extra?files=1
I'm not saying that I would know it is a Cinnamon issue, but in any case if the driver would not be working, how would it be possible to launch the session successfully fire just one user?

@mabod
Copy link
Author

mabod commented Jun 9, 2017 •
edited
Loading

I did another test with nouveau. Deinstalled the nvidia 340xx package and activated nouveau. That makes things worse.

Now even the first session is not starting correctly. Basically the same behaviour as before but even for the first session. Manjaro-Hello App is starting, desktop with icons is showing, right mouse-click opens desktop menu but the cinnamon-panel crashes. /var/log/Xorg.0.log is not showing any error (no EE entries). But .xsessions-errors says:

[cinnamon-settings-daemon-smartcard] Failed to start: Es konnte kein passender Smartcard-Treiber gefunden werden

(cinnamon:1502): Clutter-CRITICAL **: Unable to initialize Clutter: Initialisierung des Clutter-Backends nicht möglich: Keine Treiber verfügbar.
Window manager error: Unable to initialize Clutter.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

** (gnome-panel:1507): WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Looking in '/etc/xdg/parcellite/parcelliterc'
Looking in '/etc/xdg/parcellite/parcelliterc'

** (cinnamon-killer-daemon:1527): WARNING **: Binding '<Control><Alt>Escape' failed!
Looking in '/etc/xdg/parcellite/parcelliterc'
Flag 0x0001, status 0, EXIT 1 STAT 0

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(nemo-desktop:1520): GLib-CRITICAL **: g_hash_table_foreach: assertion 'version == hash_table->version' failed

(gnome-panel:1507): Gtk-WARNING **: Allocating size to top-panel 0x1522420 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(gnome-panel:1507): Gtk-WARNING **: Allocating size to bottom-panel 0x1522800 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(nemo-desktop:1520): Gtk-WARNING **: Allocating size to NemoWindowPane 0x25bc4f0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

By the way, the systemd log is always showing a pulseaudio coredump when switching user. I assume this is a different issue but want to mentio anyways.

Matthias

PS
I have tested this with kernel 4.9 and 4.11. No difference.

@leigh123linux
Copy link
Contributor

leigh123linux commented Jun 9, 2017 •
edited
Loading

@Oberon2007 I have looked at the manjaro nvidia packaging and it doesn't look right to me.

Can you confirm that all the patches listed get applied at build time

https://github.com/manjaro/packages-extra/blob/master/linux411-extramodules/nvidia-340xx/PKGBUILD#L49

If so it's totally broken with any kernel lower than 4.11 due to missing #ifdef's for different kernel versions.
Note the ifdef in these patches

https://pkgs.rpmfusion.org/cgit/nonfree/nvidia-340xx-kmod.git/tree/

User group membership could cause it, some distro's require the user to be a member of video group

but in any case if the driver would not be working, how would it be possible to launch the session successfully fire just one user?

@oberon-manjaro
Copy link
Contributor

We build dedicated extramodule packages for each kernel and each kernel is built to use matching extramodules.
So the PKGBUILD linked applies only for linux411.
For example linux49-nvidia-340xx is patched differently.

@mabod
Copy link
Author

mabod commented Jun 9, 2017

The situation is getting more complex and is eventually not cinnamon related anymore. I installed plasma5 in parallel and I can not switch to a second user with plasma5 either. So switching fron cinnamon-to-plamsa5 does not work but also plasma5-to-plasma5 does not work. I can only have one user at a time.

.xsession-errors for the second suer says:

startkde: Starting up...
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/fonts_akregator.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/fonts_global.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/fonts_kate.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/kde4breeze.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/krdb_libpathwipe.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/krunnerplugins.upd' for new updates
2017-06-09T19:17:29 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates
2017-06-09T19:17:29 kscreenlocker.upd: Found new update '0.1-autolock'
2017-06-09T19:17:29 kscreenlocker.upd: Skipping update '0.1-autolock'
Looking in '/etc/xdg/parcellite/parcelliterc'
Looking in '/etc/xdg/parcellite/parcelliterc'

** (parcellite:4637): WARNING **: Binding 'A' failed!

Flag 0x0001, status 0, EXIT 1 STAT 0
Service started, version: 7.0.0
Service started, version: 7.0.0

(manjaro-hello:4636): Gtk-WARNING **: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(manjaro-hello:4636): Gtk-WARNING **: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(manjaro-hello:4636): Gtk-WARNING **: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

** (parcellite:4637): WARNING **: Invalid borders specified for theme pixmap:
/usr/share/themes/Breath/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
klauncher: Exiting on signal 1
Unexpected response from KInit (response = 0).
startkde: Could not start ksmserver. Check your installation.
ICE default IO error handler doing an exit(), pid = 4617, errno = 32
Application::crashHandler() called with signal 6; recent crashes: 1
Error: Can't open display: :1
startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/1006/kdeinit5__1) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop: unable to open display ':1'
xprop: unable to open display ':1'
startkde: Done.
KCrash: Application 'kwin_x11' crashing...
Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/kwin_x11: FATAL ERROR while trying to open display :1

This seems to be an X11 issue.

Matthias

@mabod
Copy link
Author

mabod commented Jun 10, 2017

The problem is solved. And I have to say that @leigh123linux was right from the beginning. It is a graphics driver issue.

I removed the nvidia card and switched to intel on-board graphics. That did the trick. User switching works like a charm now. So this is actually a bug in the nvidia 340xx driver.

Thanks for everybody who tried to help. Specifically to @leigh123linux. Your comments made me look deeper into this graphics thing. /var/log/Xorg.1.log gave me the last hint to try without nvidia.

Matthias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mtwebster @clefebvre @leigh123linux @JosephMcc @mabod @oberon-manjaro