Bug#1050502: gnome-shell crash when restarting with ALT+F2, "r" on nvidia-graphics-drivers

2023-09-17 Thread Markus Steinko

Hi smvc,

here's another re-trace with "set pagination off" and "bt" as option 
when in (gdb):



system@station:~$ sudo env 
DEBUGINFOD_URLS="https://debuginfod.debian.net; coredumpctl debug

[sudo] Passwort für system:
   PID: 2552 (gnome-shell)
   UID: 1001 (system)
   GID: 1001 (system)
    Signal: 11 (SEGV)
 Timestamp: Sun 2023-09-17 12:16:05 CEST (4min 5s ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: 
/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@x11.service

  Unit: user@1001.service
 User Unit: org.gnome.Shell@x11.service
 Slice: user-1001.slice
 Owner UID: 1001 (system)
   Boot ID: 4484d6c6520845a2b96a9c02b4600322
    Machine ID: b1d0c5df0e5141788707bd1b93bec3f9
  Hostname: station
   Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1001.4484d6c6520845a2b96a9c02b4600322.2552.169494576500.zst 
(present)

  Size on Disk: 44.7M
   Message: Process 2552 (gnome-shell) of user 1001 dumped core.

    Module libudev.so.1 from deb systemd-254.1-3.amd64
    Module libsystemd.so.0 from deb systemd-254.1-3.amd64
    Stack trace of thread 2552:
    #0  0x7fe2b1681f63 _XSend (libX11.so.6 + 0x43f63)
    #1  0x7fe2b1678331 XQueryExtension (libX11.so.6 + 
0x3a331)

    #2  0x7fe2aee82d66 n/a (libXext.so.6 + 0x9d66)
    #3  0x7fe2aee834b4 XSyncTriggerFence (libXext.so.6 
+ 0xa4b4)
    #4  0x7fe2b1b0de68 meta_sync_free 
(libmutter-12.so.0 + 0x10de68)
    #5  0x7fe2b1b0c85d meta_compositor_x11_dispose 
(libmutter-12.so.0 + 0x10c85d)
    #6  0x7fe2b278c39e g_object_run_dispose 
(libgobject-2.0.so.0 + 0x1d39e)
    #7  0x7fe2b1aaeb1d meta_compositor_destroy 
(libmutter-12.so.0 + 0xaeb1d)
    #8  0x7fe2b1acec1d meta_display_close 
(libmutter-12.so.0 + 0xcec1d)
    #9  0x7fe2b24277de shell_global_reexec_self 
(libshell-12.so + 0x277de)

    #10 0x7fe2b11f8f7a n/a (libffi.so.8 + 0x6f7a)
    #11 0x7fe2b11f840e n/a (libffi.so.8 + 0x640e)
    #12 0x7fe2b11f8b0d ffi_call (libffi.so.8 + 0x6b0d)
    #13 0x7fe2b1fc3fa7 n/a (libgjs.so.0 + 0x58fa7)
    #14 0x7fe2b1fc4698 n/a (libgjs.so.0 + 0x59698)
    #15 0x7fe2af196650 n/a (libmozjs-102.so.0 + 0x196650)
    #16 0x7fe2af189d97 n/a (libmozjs-102.so.0 + 0x189d97)
    #17 0x7fe2af195e13 n/a (libmozjs-102.so.0 + 0x195e13)
    #18 0x7fe2af196297 n/a (libmozjs-102.so.0 + 0x196297)
    #19 0x7fe2af19685c n/a (libmozjs-102.so.0 + 0x19685c)
    #20 0x7fe2af23fb5d 
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE 
(libmozjs-102.so.0 + 0x23fb5d)

    #21 0x7fe2b1fa0ed1 n/a (libgjs.so.0 + 0x35ed1)
    #22 0x7fe2b1ff4884 n/a (libgjs.so.0 + 0x89884)
    #23 0x7fe2b2785540 g_closure_invoke 
(libgobject-2.0.so.0 + 0x16540)

    #24 0x7fe2b2798afc n/a (libgobject-2.0.so.0 + 0x29afc)
    #25 0x7fe2b2799d51 n/a (libgobject-2.0.so.0 + 0x2ad51)
    #26 0x7fe2b27a0186 g_signal_emit_valist 
(libgobject-2.0.so.0 + 0x31186)
    #27 0x7fe2b27a0243 g_signal_emit 
(libgobject-2.0.so.0 + 0x31243)
    #28 0x7fe2b1aceea2 meta_display_request_restart 
(libmutter-12.so.0 + 0xceea2)
    #29 0x7fe2b1ae46a3 restart_check_ready 
(libmutter-12.so.0 + 0xe46a3)

    #30 0x7fe2b22c8ec3 n/a (libgio-2.0.so.0 + 0xb5ec3)
    #31 0x7fe2b22c9b63 n/a (libgio-2.0.so.0 + 0xb6b63)
    #32 0x7fe2b226abe7 n/a (libgio-2.0.so.0 + 0x57be7)
    #33 0x7fe2b2263506 n/a (libgio-2.0.so.0 + 0x50506)
    #34 0x7fe2b22c8ec3 n/a (libgio-2.0.so.0 + 0xb5ec3)
    #35 0x7fe2b22c9b63 n/a (libgio-2.0.so.0 + 0xb6b63)
    #36 0x7fe2b2262efa n/a (libgio-2.0.so.0 + 0x4fefa)
    #37 0x7fe2b229458e n/a (libgio-2.0.so.0 + 0x8158e)
    #38 0x7fe2b22c8ec3 n/a (libgio-2.0.so.0 + 0xb5ec3)
    #39 0x7fe2b22c9b63 n/a (libgio-2.0.so.0 + 0xb6b63)
    #40 0x7fe2b2292980 n/a (libgio-2.0.so.0 + 0x7f980)
    #41 0x7fe2b22929fd n/a (libgio-2.0.so.0 + 0x7f9fd)
    #42 0x7fe2b2124099 n/a (libglib-2.0.so.0 + 0x57099)
    #43 0x7fe2b21272d7 n/a (libglib-2.0.so.0 + 0x5a2d7)
    #44 0x7fe2b2127bdf g_main_loop_run 
(libglib-2.0.so.0 + 0x5abdf)
    #45 0x7fe2b1ada039 meta_context_run_main_loop 
(libmutter-12.so.0 + 0xda039)

    #46 0x5619990919a3 main (gnome-shell + 

Bug#1050502: gnome-shell crashes when restarting it with ALT+F2 and "r"

2023-08-29 Thread Markus Steinko
I tried obtaining a stack and JS trace using GDB for an already running 
gnome-shell like discribed here:


https://wiki.gnome.org/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell

But inbetween gnome-shell crashed and I had to logout- and in again to 
get the journalctl logs.


The gdb.txt:

[Thread 0x7f81d54096c0 (LWP 18756) exited]
[New Thread 0x7f81d54096c0 (LWP 18825)]
[New Thread 0x7f81d4c086c0 (LWP 18826)]
[Thread 0x7f81d4c086c0 (LWP 18826) exited]
[New Thread 0x7f81d4c086c0 (LWP 18932)]
[New Thread 0x7f81b3fff6c0 (LWP 18933)]
[Thread 0x7f81d4c086c0 (LWP 18932) exited]
[New Thread 0x7f81d4c086c0 (LWP 18934)]
[New Thread 0x7f81b2ffd6c0 (LWP 18935)]
[Thread 0x7f81b3fff6c0 (LWP 18933) exited]
[Thread 0x7f81d4c086c0 (LWP 18934) exited]
[Thread 0x7f81b2ffd6c0 (LWP 18935) exited]
[Detaching after fork from child process 18936]
[New Thread 0x7f81b2ffd6c0 (LWP 18938)]
[New Thread 0x7f81d4c086c0 (LWP 18939)]
[Thread 0x7f81b2ffd6c0 (LWP 18938) exited]
[Thread 0x7f81d4c086c0 (LWP 18939) exited]

Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f82013fbf63 in _XSend () from /lib/x86_64-linux-gnu/libX11.so.6
#0  0x7f82013fbf63 in _XSend () at /lib/x86_64-linux-gnu/libX11.so.6
#1  0x7f82013f2331 in XQueryExtension () at 
/lib/x86_64-linux-gnu/libX11.so.6

#2  0x7f81fe957d66 in  () at /lib/x86_64-linux-gnu/libXext.so.6
#3  0x7f81fe9584b4 in XSyncTriggerFence () at 
/lib/x86_64-linux-gnu/libXext.so.6
#4  0x7f820190a340 in meta_sync_free (self=0x55df71f4b2c0) at 
../src/compositor/meta-sync-ring.c:392

    i = 0
    ring = 0x7f8201a50800 
    __func__ = "meta_sync_ring_destroy"
#5  meta_sync_ring_destroy () at ../src/compositor/meta-sync-ring.c:470
    i = 0
    ring = 0x7f8201a50800 
    __func__ = "meta_sync_ring_destroy"
#6  0x7f8201908da5 in meta_compositor_x11_dispose 
(object=0x55df71f1fa00) at ../src/compositor/meta-compositor-x11.c:520

    compositor_x11 = 0x55df71f1fa00
    compositor = 0x55df71f1fa00
    stage = 0x55df71b88220
#7  0x7f8202514d0a in g_object_run_dispose () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x7f82018aca19 in meta_compositor_destroy 
(compositor=0x55df71f1fa00) at ../src/compositor/compositor.c:198
#9  0x7f82018cc08d in meta_display_close (display=0x55df71b8c430, 
timestamp=) at ../src/core/display.c:1178

    _pp = 0x55df71b8c570
    _ptr = 
    compositor = 
    laters = 0x55df71f0f110
#10 0x7f82022274ae in shell_global_reexec_self 
(global=0x55df71bb9810) at ../src/shell-global.c:1339

    arr = 0x7f81e4262c40
    len = 21
    meta_context = 
    buf = 0x55df73d6ef90 "/usr/bin/gnome-shell"
    buf_p = 
    buf_end = 
    error = 0x0
#11 0x7f8200fb2f7a in  () at /lib/x86_64-linux-gnu/libffi.so.8
#12 0x7f8200fb240e in  () at /lib/x86_64-linux-gnu/libffi.so.8
#13 0x7f8200fb2b0d in ffi_call () at /lib/x86_64-linux-gnu/libffi.so.8
#14 0x7f8201dcbfa7 in  () at /lib/x86_64-linux-gnu/libgjs.so.0
#15 0x7f8201dcc698 in  () at /lib/x86_64-linux-gnu/libgjs.so.0
#16 0x7f81fef96620 in  () at /lib/x86_64-linux-gnu/libmozjs-102.so.0
#17 0x7f81fef89d67 in  () at /lib/x86_64-linux-gnu/libmozjs-102.so.0
#18 0x7f81fef95de3 in  () at /lib/x86_64-linux-gnu/libmozjs-102.so.0
#19 0x7f81fef96267 in  () at /lib/x86_64-linux-gnu/libmozjs-102.so.0
#20 0x7f81fef9682c in  () at /lib/x86_64-linux-gnu/libmozjs-102.so.0
#21 0x7f81ff03fb1d in JS_CallFunctionValue(JSContext*, 
JS::Handle, JS::Handle, JS::HandleValueArray 
const&, JS::MutableHandle) () at 
/lib/x86_64-linux-gnu/libmozjs-102.so.0

#22 0x7f8201da8ed1 in  () at /lib/x86_64-linux-gnu/libgjs.so.0
#23 0x7f8201dfc884 in  () at /lib/x86_64-linux-gnu/libgjs.so.0
#24 0x7f820250e3f8 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0

#25 0x7f820252101c in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#26 0x7f82025221b1 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x7f8202528552 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x7f82025285ff in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x7f82018cc2fe in meta_display_request_restart 
(display=display@entry=0x55df71b8c430) at ../src/core/display.c:2601

    result = 0
#30 0x7f82018e15b3 in restart_check_ready (context=0x55df71511c80) 
at ../src/core/restart.c:64

    display = 0x55df71b8c430
    context = 0x55df71511c80
    error = 0x0
    length = 7
    line = 
#31 restart_check_ready (context=0x55df71511c80) at ../src/core/restart.c:58
    context = 0x55df71511c80
    error = 0x0
    length = 7
    line = 
#32 restart_helper_read_line_callback (source_object=, 
res=, user_data=0x55df71511c80) at ../src/core/restart.c:92

    context = 0x55df71511c80
    error = 0x0
    

Bug#1050731: libmutter-12-0: gnome-shell libmutter-12 segfault

2023-08-29 Thread Markus Steinko

Dear Maintainer,


The same bug happens on my machine. I sent a bug report to the gnome-shell 
maintainers:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050502

Best regards, Markus


Bug#1050502: gnome-shell crashes when restarting it with ALT+F2 and "r"

2023-08-25 Thread Markus Steinko
Here's another coredump debug with libmutter debugging symbols 
installed. The ending differs a little.


I also found two more *.zst files containing information depending on 
gnome-shell. Let me know if i should upload them...



user@hostname:~$ sudo coredumpctl debug
   PID: 5471 (gnome-shell)
   UID: 1001 (system)
   GID: 1001 (system)
    Signal: 11 (SEGV)
 Timestamp: Fri 2023-08-25 12:59:02 CEST (1h 39min ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: 
/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@x11.service

  Unit: user@1001.service
 User Unit: org.gnome.Shell@x11.service
 Slice: user-1001.slice
 Owner UID: 1001 (system)
   Boot ID: 3c019ffcbc854654aa0270575308680f
    Machine ID: b1d0c5df0e5141788707bd1b93bec3f9
  Hostname: station
   Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1001.3c019ffcbc854654aa0270575308680f.5471.169296114200.zst 
(present)

  Size on Disk: 18.2M
   Message: Process 5471 (gnome-shell) of user 1001 dumped core.

    Module libudev.so.1 from deb systemd-254.1-2.amd64
    Module libsystemd.so.0 from deb systemd-254.1-2.amd64
    Stack trace of thread 5471:
    #0  0x7ffa9e0f5f14 clutter_stage_get_device_coords 
(libmutter-clutter-12.so.0 + 0x9bf14)
    #1  0x7ffa9e0f6bf6 clutter_stage_repick_device 
(libmutter-clutter-12.so.0 + 0x9cbf6)

    #2  0x7ffa9d48af7a n/a (libffi.so.8 + 0x6f7a)
    #3  0x7ffa9d48a40e n/a (libffi.so.8 + 0x640e)
    #4  0x7ffa9d48ab0d ffi_call (libffi.so.8 + 0x6b0d)
    #5  0x7ffa9e1cbfa7 n/a (libgjs.so.0 + 0x58fa7)
    #6  0x7ffa9e1cc698 n/a (libgjs.so.0 + 0x59698)
    #7  0x7ffa9b596620 n/a (libmozjs-102.so.0 + 0x196620)
    #8  0x7ffa9b589d67 n/a (libmozjs-102.so.0 + 0x189d67)
    #9  0x7ffa9b595d3d n/a (libmozjs-102.so.0 + 0x195d3d)
    #10 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #11 0x7ffa9baf7ac7 n/a (libmozjs-102.so.0 + 0x6f7ac7)
    #12 0x3963f5a5de28 n/a (n/a + 0x0)
    #13 0x55710626f498 n/a (n/a + 0x0)
    #14 0x3963f5a5b56a n/a (n/a + 0x0)
    #15 0x7ffa9bcda384 n/a (libmozjs-102.so.0 + 0x8da384)
    #16 0x7ffa9b592088 n/a (libmozjs-102.so.0 + 0x192088)
    #17 0x7ffa9b595d3d n/a (libmozjs-102.so.0 + 0x195d3d)
    #18 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #19 0x7ffa9b59682c n/a (libmozjs-102.so.0 + 0x19682c)
    #20 0x7ffa9b63fb1d 
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE 
(libmozjs-102.so.0 + 0x23fb1d)

    #21 0x7ffa9e1a8ed1 n/a (libgjs.so.0 + 0x35ed1)
    #22 0x7ffa9e1fc884 n/a (libgjs.so.0 + 0x89884)
    #23 0x7ffa9e9e33f8 g_closure_invoke 
(libgobject-2.0.so.0 + 0x163f8)

    #24 0x7ffa9e9f601c n/a (libgobject-2.0.so.0 + 0x2901c)
    #25 0x7ffa9e9f7951 n/a (libgobject-2.0.so.0 + 0x2a951)
    #26 0x7ffa9e9fd552 g_signal_emit_valist 
(libgobject-2.0.so.0 + 0x30552)
    #27 0x7ffa9e9fd5ff g_signal_emit 
(libgobject-2.0.so.0 + 0x305ff)
    #28 0x7ffa9e097dc5 n/a (libmutter-clutter-12.so.0 + 
0x3ddc5)

    #29 0x7ffa9e3192f2 n/a (libglib-2.0.so.0 + 0x442f2)
    #30 0x7ffa9e0994e3 n/a (libmutter-clutter-12.so.0 + 
0x3f4e3)
    #31 0x7ffa9e09956d n/a (libmutter-clutter-12.so.0 + 
0x3f56d)
    #32 0x7ffa9e097335 n/a (libmutter-clutter-12.so.0 + 
0x3d335)
    #33 0x7ffa9e0a1cba n/a (libmutter-clutter-12.so.0 + 
0x47cba)
    #34 0x7ffa9e0a6901 n/a (libmutter-clutter-12.so.0 + 
0x4c901)

    #35 0x7ffa9d48af7a n/a (libffi.so.8 + 0x6f7a)
    #36 0x7ffa9d48a40e n/a (libffi.so.8 + 0x640e)
    #37 0x7ffa9d48ab0d ffi_call (libffi.so.8 + 0x6b0d)
    #38 0x7ffa9e1cbfa7 n/a (libgjs.so.0 + 0x58fa7)
    #39 0x7ffa9e1cc698 n/a (libgjs.so.0 + 0x59698)
    #40 0x7ffa9b596620 n/a (libmozjs-102.so.0 + 0x196620)
    #41 0x7ffa9b589d67 n/a (libmozjs-102.so.0 + 0x189d67)
    #42 0x7ffa9b595de3 n/a (libmozjs-102.so.0 + 0x195de3)
    #43 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #44 0x7ffa9b59682c n/a (libmozjs-102.so.0 + 0x19682c)
    #45 0x7ffa9b63fb1d 
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE 
(libmozjs-102.so.0 + 0x23fb1d)


Bug#1050502: gnome-shell crashes when restarting it with ALT+F2 and "r"

2023-08-25 Thread Markus Steinko

Here's also an coredumpctl debug output:

user@hostname:/var/lib/systemd/coredump$ sudo coredumpctl debug
[sudo] Passwort für user:
   PID: 5471 (gnome-shell)
   UID: 1001 (system)
   GID: 1001 (system)
    Signal: 11 (SEGV)
 Timestamp: Fri 2023-08-25 12:59:02 CEST (48min ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: 
/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.Shell@x11.service

  Unit: user@1001.service
 User Unit: org.gnome.Shell@x11.service
 Slice: user-1001.slice
 Owner UID: 1001 (system)
   Boot ID: 3c019ffcbc854654aa0270575308680f
    Machine ID: b1d0c5df0e5141788707bd1b93bec3f9
  Hostname: station
   Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1001.3c019ffcbc854654aa0270575308680f.5471.169296114200.zst 
(present)

  Size on Disk: 18.2M
   Message: Process 5471 (gnome-shell) of user 1001 dumped core.

    Module libudev.so.1 from deb systemd-254.1-2.amd64
    Module libsystemd.so.0 from deb systemd-254.1-2.amd64
    Stack trace of thread 5471:
    #0  0x7ffa9e0f5f14 clutter_stage_get_device_coords 
(libmutter-clutter-12.so.0 + 0x9bf14)
    #1  0x7ffa9e0f6bf6 clutter_stage_repick_device 
(libmutter-clutter-12.so.0 + 0x9cbf6)

    #2  0x7ffa9d48af7a n/a (libffi.so.8 + 0x6f7a)
    #3  0x7ffa9d48a40e n/a (libffi.so.8 + 0x640e)
    #4  0x7ffa9d48ab0d ffi_call (libffi.so.8 + 0x6b0d)
    #5  0x7ffa9e1cbfa7 n/a (libgjs.so.0 + 0x58fa7)
    #6  0x7ffa9e1cc698 n/a (libgjs.so.0 + 0x59698)
    #7  0x7ffa9b596620 n/a (libmozjs-102.so.0 + 0x196620)
    #8  0x7ffa9b589d67 n/a (libmozjs-102.so.0 + 0x189d67)
    #9  0x7ffa9b595d3d n/a (libmozjs-102.so.0 + 0x195d3d)
    #10 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #11 0x7ffa9baf7ac7 n/a (libmozjs-102.so.0 + 0x6f7ac7)
    #12 0x3963f5a5de28 n/a (n/a + 0x0)
    #13 0x55710626f498 n/a (n/a + 0x0)
    #14 0x3963f5a5b56a n/a (n/a + 0x0)
    #15 0x7ffa9bcda384 n/a (libmozjs-102.so.0 + 0x8da384)
    #16 0x7ffa9b592088 n/a (libmozjs-102.so.0 + 0x192088)
    #17 0x7ffa9b595d3d n/a (libmozjs-102.so.0 + 0x195d3d)
    #18 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #19 0x7ffa9b59682c n/a (libmozjs-102.so.0 + 0x19682c)
    #20 0x7ffa9b63fb1d 
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE 
(libmozjs-102.so.0 + 0x23fb1d)

    #21 0x7ffa9e1a8ed1 n/a (libgjs.so.0 + 0x35ed1)
    #22 0x7ffa9e1fc884 n/a (libgjs.so.0 + 0x89884)
    #23 0x7ffa9e9e33f8 g_closure_invoke 
(libgobject-2.0.so.0 + 0x163f8)

    #24 0x7ffa9e9f601c n/a (libgobject-2.0.so.0 + 0x2901c)
    #25 0x7ffa9e9f7951 n/a (libgobject-2.0.so.0 + 0x2a951)
    #26 0x7ffa9e9fd552 g_signal_emit_valist 
(libgobject-2.0.so.0 + 0x30552)
    #27 0x7ffa9e9fd5ff g_signal_emit 
(libgobject-2.0.so.0 + 0x305ff)
    #28 0x7ffa9e097dc5 n/a (libmutter-clutter-12.so.0 + 
0x3ddc5)

    #29 0x7ffa9e3192f2 n/a (libglib-2.0.so.0 + 0x442f2)
    #30 0x7ffa9e0994e3 n/a (libmutter-clutter-12.so.0 + 
0x3f4e3)
    #31 0x7ffa9e09956d n/a (libmutter-clutter-12.so.0 + 
0x3f56d)
    #32 0x7ffa9e097335 n/a (libmutter-clutter-12.so.0 + 
0x3d335)
    #33 0x7ffa9e0a1cba n/a (libmutter-clutter-12.so.0 + 
0x47cba)
    #34 0x7ffa9e0a6901 n/a (libmutter-clutter-12.so.0 + 
0x4c901)

    #35 0x7ffa9d48af7a n/a (libffi.so.8 + 0x6f7a)
    #36 0x7ffa9d48a40e n/a (libffi.so.8 + 0x640e)
    #37 0x7ffa9d48ab0d ffi_call (libffi.so.8 + 0x6b0d)
    #38 0x7ffa9e1cbfa7 n/a (libgjs.so.0 + 0x58fa7)
    #39 0x7ffa9e1cc698 n/a (libgjs.so.0 + 0x59698)
    #40 0x7ffa9b596620 n/a (libmozjs-102.so.0 + 0x196620)
    #41 0x7ffa9b589d67 n/a (libmozjs-102.so.0 + 0x189d67)
    #42 0x7ffa9b595de3 n/a (libmozjs-102.so.0 + 0x195de3)
    #43 0x7ffa9b596267 n/a (libmozjs-102.so.0 + 0x196267)
    #44 0x7ffa9b59682c n/a (libmozjs-102.so.0 + 0x19682c)
    #45 0x7ffa9b63fb1d 
_Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16HandleValueArrayENS1_13MutableHandleIS6_EE 
(libmozjs-102.so.0 + 0x23fb1d)

    #46 0x7ffa9e1a8ed1 n/a (libgjs.so.0 + 0x35ed1)
    #47 0x7ffa9e1fc884 n/a (libgjs.so.0 + 0x89884)
    

Bug#1050502: reportbug: gnome-shell crashes when restarting it with ALT+F2 and "r"

2023-08-25 Thread Markus Steinko

Package: gnome-shell
Version: 44.3-5
Severity: normal

Dear Maintainer,



* What led up to the situation?

After installing some updates this morning and rebooting the system an error
occurred. When starting the system and logging in from gdm3 the cursor 
showed a

black cross and not an arrow. After logging in I was able to use the system.
Restarting the gnome-shell with ALT+F2 and then typing r - made the system
crash. I was told that an error occurred and the user needs to be logged 
out.
Hitting the Super key showed the workspace but choosing a windows made 
gnome-

shell crash again.
Logging out and in again is solving the crash temporarily.

* What exactly did you do (or not do) that was effective (or
ineffective)?

Reconfigured gdm3, configured the gdm3 .conf file to let it use Wayland if
needed (set the # false) , removed "nomodeset" from grub configuration and
reinstalled any installed package with aptitude reinstall ~i.

* What was the outcome of this action?

The error persists.

* What outcome did you expect instead?

The error could be solved.


-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4
ii gir1.2-accountsservice-1.0 22.08.8-6
ii gir1.2-adw-1 1.3.4-1
ii gir1.2-atk-1.0 2.48.3-1
ii gir1.2-atspi-2.0 2.48.3-1
ii gir1.2-freedesktop 1.76.1-5
ii gir1.2-gcr-3 3.41.1-3
ii gir1.2-gdesktopenums-3.0 44.0-2
ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii gir1.2-gdm-1.0 44.1-2
ii gir1.2-geoclue-2.0 2.7.0-3
ii gir1.2-glib-2.0 1.76.1-5
ii gir1.2-gnomebg-4.0 44.0-2
ii gir1.2-gnomebluetooth-3.0 42.6-1
ii gir1.2-gnomedesktop-4.0 44.0-2
ii gir1.2-graphene-1.0 1.10.8-1
ii gir1.2-gstreamer-1.0 1.22.5-1
ii gir1.2-gtk-4.0 4.10.5+ds-3
ii gir1.2-gweather-4.0 4.3.2-1
ii gir1.2-ibus-1.0 1.5.29~beta2-1
ii gir1.2-mutter-12 44.3-7
ii gir1.2-nm-1.0 1.44.0-1
ii gir1.2-nma4-1.0 1.10.6-1
ii gir1.2-pango-1.0 1.51.0+ds-2
ii gir1.2-polkit-1.0 123-1
ii gir1.2-rsvg-2.0 2.54.7+dfsg-2
ii gir1.2-soup-3.0 3.4.2-4
ii gir1.2-upowerglib-1.0 0.99.20-2
ii gir1.2-webkit2-4.1 2.40.5-1
ii gnome-backgrounds 44.0-2
ii gnome-settings-daemon 45~beta-1
ii gnome-shell-common 44.3-5
ii gsettings-desktop-schemas 44.0-2
ii gstreamer1.0-pipewire 0.3.78-1
ii libatk-bridge2.0-0 2.48.3-1
ii libatk1.0-0 2.48.3-1
ii libc6 2.37-7
ii libcairo2 1.16.0-7
ii libecal-2.0-2 3.49.2-4
ii libedataserver-1.2-27 3.49.2-4
ii libgcr-base-3-1 3.41.1-3
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libgirepository-1.0-1 1.76.1-5
ii libgjs0g 1.76.2-4
ii libgles2 1.6.0-1
ii libglib2.0-0 2.77.2-1
ii libglib2.0-bin 2.77.2-1
ii libgnome-autoar-0-0 0.4.4-2
ii libgnome-desktop-4-2 44.0-2
ii libgraphene-1.0-0 1.10.8-1
ii libgtk-3-0 3.24.38-2
ii libgtk-4-1 4.10.5+ds-3
ii libical3 3.0.16-1+b1
ii libjson-glib-1.0-0 1.6.6-1
ii libmutter-12-0 44.3-7
ii libnm0 1.44.0-1
ii libpango-1.0-0 1.51.0+ds-2
ii libpolkit-agent-1-0 123-1
ii libpolkit-gobject-1-0 123-1
ii libpulse-mainloop-glib0 16.1+dfsg1-2+b1
ii libpulse0 16.1+dfsg1-2+b1
ii libsecret-1-0 0.21.0-1
ii libsystemd0 254.1-2
ii libx11-6 2:1.8.6-1
ii libxfixes3 1:6.0.0-2
ii python3 3.11.4-5+b1

Versions of packages gnome-shell recommends:
ii bolt 0.9.5-1
ii chrome-gnome-shell 42.1-4
ii evolution-data-server 3.49.2-4
ii gdm3 44.1-2
ii gkbd-capplet 3.28.1-1
ii gnome-control-center 1:44.3-3
ii gnome-menus 3.36.0-1.1
ii gnome-remote-desktop 44.2-6
ii gnome-user-docs 44.3-2
ii ibus 1.5.29~beta2-1
ii iio-sensor-proxy 3.5-1
ii power-profiles-daemon 0.13-2
ii switcheroo-control 2.6-1+b1
ii unzip 6.0-28

Versions of packages gnome-shell suggests:
ii gir1.2-malcontent-0 0.11.0-4
pn gir1.2-telepathyglib-0.12 
pn gir1.2-telepathylogger-0.2 
ii gnome-shell-extension-prefs 44.3-5

Versions of packages gnome-session depends on:
ii adwaita-icon-theme [adwaita-icon-theme-full] 43-1
ii fonts-cantarell 0.303.1-1
ii gnome-session-bin 44.0-2
ii gnome-session-common 44.0-2
ii gnome-settings-daemon 45~beta-1
ii xdg-desktop-portal-gnome [xdg-desktop-portal-backend] 43.1-2
ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.14.1-1

Versions of packages gnome-session suggests:
ii desktop-base 12.0.6+nmu1
ii gnome-keyring 42.1-1+b2

Versions of packages gnome-settings-daemon depends on:
ii gnome-settings-daemon-common 45~beta-1
ii gsettings-desktop-schemas 44.0-2
ii libasound2 1.2.9-1
ii libc6 2.37-7
ii libcairo2 1.16.0-7
ii libcanberra-gtk3-0 0.30-10
ii libcanberra0 0.30-10
ii libcolord2 1.4.6-2.2
ii libcups2 2.4.2-5
ii libfontconfig1 2.14.2-4
ii libgcr-base-3-1 3.41.1-3
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libgeoclue-2-0 2.7.0-3
ii 

Bug#1012838: Bug closed?

2023-04-27 Thread Markus Steinko

Dear maintainer,

I guess this bug is fixed with the latest upgrade?!

Best regards,



Bug#1024245: network-manager: after upgrade - can't modify or add connections

2022-11-19 Thread Markus Steinko

There's a workaround for this case which worked for me:

You need to edit 
"/usr/share/glib-2.0/schemas/org.gnome.nm-applet.eap.gschema.xml" and 
just change one line like you can see here:


https://gitlab.gnome.org/GNOME/libnma/-/merge_requests/44/diffs

from:

path="/org/gnome/nm-applet/eap/"gettext-domain="nm-applet">


to:



After that you need to run:

sudo glib-compile-schemas /usr/share/glib-2.0/schemas/

and your done.

Good luck.


Bug#1012838: grub-pc: updating grub-pc in offline mode on reboot does not add other OS entries like Windows 10

2022-06-15 Thread Markus Steinko

Dear Maintainer,

updating grub or reconfiguring grub-pc did not do the trick in my case.

I had to add "GRUB_DISABLE_OS_PROBER=false" to /etc/default/grub to let 
the update-grub command add the Windows 10 partition.



Best regards,



Bug#996468: nvidia-kernel-dkms won't install for kernel 5.14.0-1 and 5.14.0-2

2021-10-16 Thread Markus Steinko



The patch provided in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994860 
works for upgrading the system. The changes can be done to the already 
installed files and an update is possible after that.

Regards,



Bug#994860: nvidia-driver: Does not build against new kernel 5.14.0-1-amd64

2021-10-07 Thread Markus Steinko
The patch works for upgrading the system. Thanks a lot. I applied the 
changes to the installed files on my system and was able to upgrade the 
kernel.



Cheers,



Bug#972468: Error! Bad return status for module build on kernel: 5.9.0-1-amd64 (x86_64)

2020-10-24 Thread Markus Steinko

Dear maintainer,

when reinstalling the nvidia-kernel-dkms package the following error 
occours:


DKMS: install completed.
Building initial module for 5.9.0-1-amd64
Error! Bad return status for module build on kernel: 5.9.0-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/450.66/build/make.log for more 
information.

dpkg: Fehler beim Bearbeiten des Paketes nvidia-kernel-dkms (--configure):
 »installiertes nvidia-kernel-dkms-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 10 zurück

Fehler traten auf beim Bearbeiten von:
 nvidia-kernel-dkms


The make file is attached.

DKMS make.log for nvidia-current-450.66 for kernel 5.9.0-1-amd64 (x86_64)
Sa 24. Okt 13:49:27 CEST 2020
make KBUILD_OUTPUT=/lib/modules/5.9.0-1-amd64/build V=1 -C /lib/modules/5.9.0-1-amd64/source M=/var/lib/dkms/nvidia-current/450.66/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/5.9.0-1-amd64/source NV_KERNEL_OUTPUT=/lib/modules/5.9.0-1-amd64/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video NV_SPECTRE_V2=0 modules
make[1]: Verzeichnis „/usr/src/linux-headers-5.9.0-1-common“ wird betreten
make -C /usr/src/linux-headers-5.9.0-1-amd64 -f /usr/src/linux-headers-5.9.0-1-common/Makefile modules
make[2]: Verzeichnis „/usr/src/linux-headers-5.9.0-1-amd64“ wird betreten
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (		\
echo >&2;			\
echo >&2 "  ERROR: Kernel configuration is invalid.";		\
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";	\
echo >&2 ;			\
/bin/false)
make -f /usr/src/linux-headers-5.9.0-1-common/scripts/Makefile.build obj=/var/lib/dkms/nvidia-current/450.66/build \
single-build= \
need-builtin=1 need-modorder=1
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
NV_CONFTEST_CMD=/bin/sh /var/lib/dkms/nvidia-current/450.66/build/conftest.sh " gcc-10" x86_64 /lib/modules/5.9.0-1-amd64/source /lib/modules/5.9.0-1-amd64/build
NV_CONFTEST_CFLAGS=-O2 -D__KERNEL__ -DKBUILD_BASENAME="#conftest26943" -DKBUILD_MODNAME="#conftest26943" -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include -I/lib/modules/5.9.0-1-amd64/source/arch/x86/include/asm/mach-default -I/lib/modules/5.9.0-1-amd64/source/include/asm-x86/mach-default -I/lib/modules/5.9.0-1-amd64/build/include2 -I/lib/modules/5.9.0-1-amd64/build/include -include /lib/modules/5.9.0-1-amd64/build/include/generated/autoconf.h -I/lib/modules/5.9.0-1-amd64/source/arch/x86/include -I/lib/modules/5.9.0-1-amd64/source/arch/x86/include/uapi -I/lib/modules/5.9.0-1-amd64/build/arch/x86/include/generated -I/lib/modules/5.9.0-1-amd64/build/arch/x86/include/generated/uapi -I/lib/modules/5.9.0-1-amd64/source/include -I/lib/modules/5.9.0-1-amd64/source/include/uapi -I/lib/modules/5.9.0-1-amd64/source/include/xen -I/lib/modules/5.9.0-1-amd64/build/include/generated/uapi -I/var/lib/dkms/nvidia-current/450.66/build/common/inc -I/var/lib/dkms/nvidia-current/450.66/build -Wall -MD   -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"450.66\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -fno-pie -Wall -Wundef -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -fmacro-prefix-map=/usr/src/linux-headers-5.9.0-1-common/= -fcf-protection=none -Wno-packed-not-aligned
KBUILD_CFLAGS=-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone 

Bug#972468: nvidia-driver 450.66-1

2020-10-24 Thread Markus Steinko
I am facing the same bug for nvidia-driver (450.66-1) on a a bullseye 
system where the nvidia-persistenced package still remains on version 
(450.57-1).




Bug#972076: tasksel --new-install

2020-10-14 Thread Markus Steinko
When rechecking for the warning I figured out that `tasksel 
--new-install` also gives an error. I'm not sure if this is because of 
already having all needed and available packages that option offers 
installed, or if it maybe is another bug.



sudo tasksel --new-install
Invalid entry length (16). Fixed up to 11.
Invalid entry length (16). Fixed up to 11.
Invalid entry length (16). Fixed up to 11.
WARNING: tempfile is deprecated; consider using mktemp instead.
tasksel: Aptitude fehlgeschlagen (100)


Regards,



Bug#972076: tasksel suggests the use of mktemp instead of tempfile

2020-10-12 Thread Markus Steinko

Package: tasksel
Version: 3.59
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?

    Using tasksel to install some task, or with the --new-install 
option

        ends successfully, but with a warning:
    WARNING: tempfile is deprecated; consider using mktemp instead.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

    Just read through the postinst script to see how paths get handled.

   * What was the outcome of this action?

    I could not find what I was looking for, as tasksel maybe 
depends on

        another package which is responsible for the warning.

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tasksel depends on:
ii  apt 2.1.10
ii  debconf [debconf-2.0]   1.5.74
ii  liblocale-gettext-perl  1.07-4
ii  perl-base   5.30.3-4
ii  tasksel-data    3.59

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information:
  tasksel/tasks: desktop, gnome-desktop, cinnamon-desktop, 
mate-desktop, ssh-server

  tasksel/desktop:
  tasksel/first: desktop, gnome-desktop, ssh-server, standard
  tasksel/title:



Bug#960787: libc6 stays unconfigured

2020-05-16 Thread Markus Steinko

Subject: libc6 stays unconfigured
Package: libc6
Version: 2.30-8
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?
I reinstalled all packages with sudo aptitude reinstall ~i
In the end libc6 and libgcc-s1 stayed unconfigured and needrestart just 
found

some processes that needed to be restarted.

Trigger für libc-bin (2.30-8) werden verarbeitet ...
Prüfe Prozesse...
Prüfe Kandidaten...
Scanning processor microcode...
Prüfe Linux-Kernel...

Der laufende Kernel ist aktuell.

Der Prozessor Mikrocode ist aktuell.

Dienste werden neu gestartet...
 systemctl restart systemd-timesyncd.service
Dienste deren Neustart verschoben wurde:
 /etc/needrestart/restart.d/dbus.service
 systemctl restart gdm.service
 systemctl restart gdm3.service
 systemctl restart systemd-logind.service
 systemctl restart unattended-upgrades.service

Es müssen keine Container neu gestartet werden.

Nutzer-Sitzungen mit veralteten Prozessen:
 Debian-gdm @ user manager service: at-spi-bus-laun[1245], 
gnome-shell[1305],

ibus-daemon[1326], pulseaudio[876],
  systemd[784]
 station @ session #3: gdm-session-wor[1546], gdm-x-session[1656], gnome-
keyring-d[1601], gnome-session-b[1672],
  ibus-daemon[1781], ibus-x11[1804]
 station @ user manager service: aptitude[5223], at-spi-bus-laun[1790],
bwrap[5236,5246], gnome-session-b[1828],
  gnome-terminal-[3288], gvfsd[1603], pulseaudio[1578], 
p11-kit-server[5243],

systemd[1553]
E: »libc6:amd64« konnte nicht konfiguriert werden.
E: »libgcc-s1:amd64« konnte nicht unmittelbar konfiguriert werden. Lesen Sie
»man 5 apt.conf« unter APT::Immediate-Configure bezüglich weiterer 
Details. (2)


Aktueller Status: 6587 (+3) new.
Es gibt 3 zusätzliche veraltete Pakete: libdvdcss-dev, libdvdcss2,
libdvdcss2-dbgsym
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

sudo apt-get install --reinstall libc6 libgcc-s1 reconfigured those two
packages after reinstallation.
   * What was the outcome of this action?
sudo apt-get install --reinstall libc6 libgcc-s1
[sudo] Passwort für station:
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
0 aktualisiert, 0 neu installiert, 2 erneut installiert, 0 zu entfernen 
und 0

nicht aktualisiert.
Es müssen noch 0 B von 2.860 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Vorkonfiguration der Pakete ...
(Lese Datenbank ... 262171 Dateien und Verzeichnisse sind derzeit 
installiert.)

Vorbereitung zum Entpacken von .../libc6_2.30-8_amd64.deb ...
Entpacken von libc6:amd64 (2.30-8) über (2.30-8) ...
Vorbereitung zum Entpacken von .../libgcc-s1_10.1.0-1_amd64.deb ...
Entpacken von libgcc-s1:amd64 (10.1.0-1) über (10.1.0-1) ...
libgcc-s1:amd64 (10.1.0-1) wird eingerichtet ...
libc6:amd64 (2.30-8) wird eingerichtet ...
Trigger für libc-bin (2.30-8) werden verarbeitet ...
Prüfe Prozesse...
Prüfe Kandidaten...
Scanning processor microcode...
Prüfe Linux-Kernel...

Der laufende Kernel ist aktuell.

Der Prozessor Mikrocode ist aktuell.

Dienste werden neu gestartet...
 systemctl restart accounts-daemon.service atd.service avahi-daemon.service
clamav-freshclam.service colord.service cron.service cups-browsed.service
cups.service exim4.service firewalld.service nmbd.service nvidia-
persistenced.service packagekit.service polkit.service rsyslog.service 
rtkit-
daemon.service smbd.service switcheroo-control.service 
systemd-journald.service

systemd-resolved.service systemd-timesyncd.service systemd-udevd.service
udisks2.service upower.service
Dienste deren Neustart verschoben wurde:
 systemctl restart ModemManager.service
 systemctl restart NetworkManager.service
 /etc/needrestart/restart.d/dbus.service
 systemctl restart gdm.service
 systemctl restart gdm3.service
 systemctl restart systemd-logind.service
 systemctl restart unattended-upgrades.service
 systemctl restart wpa_supplicant.service

Es müssen keine Container neu gestartet werden.

Nutzer-Sitzungen mit veralteten Prozessen:
 Debian-gdm @ user manager service: at-spi-bus-laun[1245], 
gnome-shell[1305],

ibus-daemon[1326], pulseaudio[876],
  systemd[784]
 station @ session #3: gdm-session-wor[1546], gdm-x-session[1656], gnome-
keyring-d[1601], gnome-session-b[1672],
  ibus-daemon[1781], ibus-x11[1804]
 station @ user manager service: at-spi-bus-laun[1790], bwrap[5236,5246],
gnome-session-b[1828],
  gnome-terminal-[3288], gvfsd[1603], pulseaudio[1578], 
p11-kit-server[5243],

systemd[1553]

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 

Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless

2020-03-17 Thread Markus Steinko

On Tue, 17 Mar 2020 10:26:17 +0100 Markus Steinko  wrote:
> Dear maintainer,
>
> downgrading a system from bullseye to buster (via apt-pinning) was kind
> of impossible (due to removal of libcrypt.so.1 and unresolved
> dependencies of libc-bin and libc6, I think)  when I was facing the bug
> for the first time and I was not being logged in as root within an 
active

> terminal. Copying the content of the extracted
> libcrypt1_4.4.15-1_amd64.deb file to its destination helped to get it
> fixed.
>
> `cp /libcrypt1_4.4.15-1_amd64/data/usr/lib/x86_64-linux-gnu/.
> /usr/lib/x86_64-linux-gnu/`
>
> Regards,
>
> Markus
>
>
>

Oops,

I made a mistake when posting this, due to reading through two open 
browser tabs:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953562

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953958

That's why the subject is not set correct. Sorry.



Bug#953958: Bug#953562: libcrypt1 should ship file in /usr, breaks is useless

2020-03-17 Thread Markus Steinko

Dear maintainer,

downgrading a system from bullseye to buster (via apt-pinning) was kind 
of impossible (due to removal of libcrypt1.so and unresolved 
dependencies of libc-bin and libc6, I think)  when I was facing the bug 
for the first time and I not being logged in as root within an active 
terminal. Copying the content of the extracted 
libcrypt1_4.4.15-1_amd64.deb file to its destination helped to get it 
fixed.


`cp /libcrypt1_4.4.15-1_amd64/data/usr/lib/x86_64-linux-gnu/. 
/usr/lib/x86_64-linux-gnu/`


Regards,

Markus



Bug#901931: timidity-daemon: upgrading to 2.14.0-3 breaks whole sound-system

2018-07-13 Thread Markus Steinko

Thanks a lot Gabriele, that did the trick! :-)

Cheers, Markus



Bug#902819: system freeze (hang task) when launching Xorg(1) after a new version of linux-image installed

2018-07-01 Thread Markus Steinko

Same here,

I could get the screen running with using lightdm instead of gdm3 and I 
changed to mesa-diverted using sudo update-glx --config glx. But I am 
missing some performance.


I needed to change the grub kernel line to 'nomodeset text single' to be 
able to do same terminal workaround.




Bug#901931: the soundsystem still breaks after todays timidity and timidity-daemon upgrade to 2.14.0-8

2018-06-30 Thread Markus Steinko

Dear Maintainer,

sadly the bug still appears after todays system upgrade, which also 
upgraded timidity and timidity-daemon to version 2.14.0-8.


What kind of system information do you need to reproduce the situation?

Kind regards,



Bug#901931: timidity-daemon: upgrading to 2.14.0-3 breaks whole sound-system

2018-06-21 Thread Markus Steinko

Same here, running debian sid/testing with gnome and using gnome-shell.

I was able to keep the timidity and timidity-daemon packages installed 
by reconfiguring them with dpkg and reinstalling them again. I spend 
hours to find the reason for the muted soundsystem, telling me the 
output would be a dummy and that no other devices are available. Thanks 
a lot for your report!