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

Segmentation fault when trying to open display settings with lower resolutions (LMDE6) #392

Open
tanev opened this issue May 7, 2024 · 0 comments

Comments

@tanev
Copy link

tanev commented May 7, 2024

  • csd version: 6.0.0+faye
  • Distribution: LMDE 6 Faye Cinnamon
  • Graphics hardware and driver used:
$ inxi -G
Graphics:
 Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Mobile Series]
   driver: amdgpu v: kernel
 Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Camera type: USB
   driver: uvcvideo
 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X:
   loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
   resolution: 1920x1080~60Hz
 API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Vega 10 Graphics
   (raven LLVM 15.0.6 DRM 3.54 6.5.0-0.deb12.4-amd64)
$ uname -r
6.5.0-0.deb12.4-amd64

Issue

The display settings do not load due to segmentation fault when the resolution is set to 640x480 or lower.

Steps to reproduce

  • (optional) install frozen bubble, load and set to fullscreen (wink-wink)
  • set the screen to 640x480
$ xrandr -s 640x480
$ cinnamon-settings display
/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:444: DeprecationWarning: Gtk.Window.set_wmclass is deprecated
  self.window.set_wmclass(wm_class, wm_class)
Loading Display module
Segmentation fault (core dumped)
  • (optional to resolve):
$ xrandr -s 0 # this is the preferred resolution

Expected behaviour

Either load the application with the settings a bit off the screen or show an error message with some hints how to resolve from this situation (e.g. "unsupported resolution, use xrandr -s <default_resolution>" or something like that).

Other information

Not sure what are the exact steps, but I think there is a separate (set of) bug(s) when frozen bubble is exited and have to return to the default resolution.

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

1 participant