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

Opening application menu crashes Cinnamon on musl-based distributions #7882

Closed
demize opened this issue Sep 23, 2018 · 14 comments
Closed

Opening application menu crashes Cinnamon on musl-based distributions #7882

demize opened this issue Sep 23, 2018 · 14 comments

Comments

@demize
Copy link

demize commented Sep 23, 2018

 * Cinnamon version: 3.8.8
 * Distribution: Void Linux (musl)
 * Graphics hardware *and* driver used: Intel Corporation 3rd Gen Core processor Graphics Controller (kernel driver in use: i915)
 * 32 or 64 bit: 64-bit
 * No logs available (.xsession-errors is empty, Void Linux doesn't have a syslog by default)

Issue

When the application menu is set to show icons for applications, opening the application menu catastrophically crashes Cinnamon, This issue was originally reported to Void Linux in voidlinux/void-packages#10204.

Steps to reproduce

  1. Install a musl-based distribution such as Void Linux
  2. Install and launch Cinnamon
  3. Try to open the application menu.

Expected behaviour

The application menu will open.

Actual behavior

Cinnamon crashes and restarts in a broken version of safe mode, with no UI elements available.

Other information

Turning off application icons in the application menu config (by right clicking the menu) is a viable workaround, as is installing and using the Papirus theme for application icons. The person who originally reported this issue tested multiple other icon themes to no avail.

@mtwebster
Copy link
Member

Can you restart cinnamon from a terminal so we can get some logging?

cinnamon --restart

@demize
Copy link
Author

demize commented Sep 23, 2018

There's not much from stderr, and there was nothing from stdout. Opening the application menu somehow causes a segfault, which the terminal outputs but doesn't make it to the log file. I wrote out a core dump, and I've uploaded it to MEGA if it'll be any use.

@mtwebster
Copy link
Member

Can you try processing that with gdb? I can't do much with it.

gdb cinnamon core.2028

# from within gdb,
thread apply all bt

Not sure how available debugging symbols are on that distro - that would be best to have (at least for clutter, gtk, cinnamon)

@demize
Copy link
Author

demize commented Sep 23, 2018

Here's the backtrace it gave me: gdb.txt.

Edit: Actually, debug symbols are available, so I'm installing them now and I'll have a much more useful backtrace for you in a minute.

@mtwebster
Copy link
Member

Curious do you have recent files enabled? If so, try disabling: cinnamon-settings->privacy

Check dependencies needed for cinnamon, libclutter-1.0, gtk3, cinnamon-desktop - maybe against other distros to see if anything's missing?

We might be able to determine more if we had debug symbols (which would replace all the ?? with useful function names.

One thing I noticed, papyrus theme only appears to use svg images, no pngs - most themes use a mix of both. This might be a common factor for trying different themes for the time being.

@demize
Copy link
Author

demize commented Sep 23, 2018

I installed all the debug symbols I could figure out based on the backtraces, and here's the new output: gdb-withsymbols.txt

Oddly enough, gdb doesn't seem to properly recognize the symbols for mozjs. Not sure why.

@demize
Copy link
Author

demize commented Sep 23, 2018

Just checked to see, recent files is already disabled.

@mtwebster
Copy link
Member

Is there anything at play limiting process memory? One thing typical of opening the menu (with icons enabled) is a significant memory bump, the first time it's done.

I'm curious if the menu had only a few things in it, would it still crash?

@demize
Copy link
Author

demize commented Sep 23, 2018

There shouldn't be anything limiting process memory; I haven't installed or configured anything to limit memory, and I don't believe Void would have any such limitations configured by default. Cinnamon works fine on the glibc version of Void as well (apparently; I haven't actually tried it myself, since I've only ever used the musl version) so it could be different behavior in memory allocation functions between musl and glibc (musl aims to be standards-conformant while glibc allows a lot that isn't standards-conformant, so it's possible that musl just doesn't like the way something's being done).

@marmistrz
Copy link

This may or may not be related: dino/dino#365
This may be some gtk issue but I've never had the time to narrow it down.

@Vahan86
Copy link

Vahan86 commented Dec 9, 2019

@demize, is this still an issue for you with Cinnamon 4.2?

@Vahan86
Copy link

Vahan86 commented Feb 8, 2020

@icarter09, can we close this issue since there is no response from OP?

@ghost
Copy link

ghost commented Oct 10, 2020

This issue is still present with cinnamon 4.6.7 on musl

@icarter09
Copy link
Member

@kukku14 could you open a new ticket about this issue? Thanks.

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

5 participants