Bug#971783: marked as pending in mate-media

[Maxime G.]

Crash again today, here the full backtrace:

(mate-volume-control-status-icon:59859): Gdk-CRITICAL **: 17:44:19.067: 
gdk_window_thaw_toplevel_updates: assertion 
'window->update_and_descendants_freeze_count > 0' failed

(mate-volume-control-status-icon:59859): Gtk-WARNING **: 19:58:21.546: Calling 
gtk_widget_realize() on a widget that isn't inside a toplevel window is not 
going to work very well. Widgets must be inside a toplevel container before 
realizing them.

(mate-volume-control-status-icon:59859): GLib-GObject-CRITICAL **: 
19:58:21.546: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-volume-control-status-icon:59859): Gdk-CRITICAL **: 19:58:21.546: 
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: assertion 
failed: (window != NULL)
Bail out! Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)

Thread 1 "mate-volume-con" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce type.
(gdb) bt full
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {140737340208256}}
ret = 
#1  0x7702ad2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x76fdbef2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
ret = 
#3  0x76fc6472 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, 
sa_mask = {__val = {93824994969568, 140737488343016, 140737339441927, 
93823560581168, 140733193388032, 93824994584288, 0, 93824997363264, 
5024613291978080768, 140737339702443, 18446744073709551488, 11, 
140737340210816, 140737348604049, 140737488343120, 140737340300128}}, sa_flags 
= -150762193, sa_restorer = 0x77a3f133}
#4  0x7719eec8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x771fee1a in g_assertion_message_expr () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x77969d56 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x77978a6f in gtk_widget_realize () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x77978c68 in gtk_widget_map () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x776ccf80 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7771ee5f in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x772cf4e0 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x772e8bbf in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x772e8dbf in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x77978c12 in gtk_widget_map () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#15 0x77991d10 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#16 0x772cf5a9 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x772e8bbf in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x772e8dbf in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x77978c12 in gtk_widget_map () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x7798786b in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x772cf3b0 in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x772e1d2d in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x772e8bf5 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x772e8dbf in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#25 0x77972986 in gtk_widget_show () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x77924615 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#27 0x77924811 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#28 0x775277e7 in  () at /lib/x86_64-linux-gnu/libgdk-3.so.0
#29 0x771d619a in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x771d567f in g_main_context_dispatch () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x771d5a38 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x771d5cef in g_main_loop_run () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x778073e5 in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#34 0x9f33 in main ()
(gdb) c
Continuing.
Couldn't get registers: Aucun processus de ce type.
(gdb) [Thread 0x7fffe6c0 (LWP 67173) exited]
[Thread 0x7517e6c0 (LWP 59863) exited]
[Thread 0x7597f6c0 (LWP 59862) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.

The program is not being run.


19 mars 2023 20:24 "Maxime G."  

Bug#971783: marked as pending in mate-media

[Maxime G.]

Hi.

Issue reproduced today on Debian Bookworm testing, the 
mate-volume-control-status-icon crash randomly.
mate-volume-control-status-icon --version
mate-volume-control-status-icon 1.26.0

Backtrace with gdb:

$ gdb mate-volume-control-status-icon 
GNU gdb (Debian 13.1-2) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from mate-volume-control-status-icon...
(No debugging symbols found in mate-volume-control-status-icon)
(gdb) r
Starting program: /usr/bin/mate-volume-control-status-icon 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7597f6c0 (LWP 26963)]
[New Thread 0x7517e6c0 (LWP 26964)]
[New Thread 0x7fffe6c0 (LWP 26965)]
[Thread 0x7fffe6c0 (LWP 26965) exited]
[New Thread 0x7fffe6c0 (LWP 26966)]
[New Thread 0x7fffef7fe6c0 (LWP 26967)]
[Thread 0x7fffe6c0 (LWP 26966) exited]
[Thread 0x7fffef7fe6c0 (LWP 26967) exited]
[New Thread 0x7fffef7fe6c0 (LWP 26968)]
[New Thread 0x7fffe6c0 (LWP 26969)]
[Thread 0x7fffef7fe6c0 (LWP 26968) exited]
[Thread 0x7fffe6c0 (LWP 26969) exited]
[Detaching after fork from child process 26970]
[New Thread 0x7fffe6c0 (LWP 26972)]
[New Thread 0x7fffef7fe6c0 (LWP 26973)]
[Thread 0x7fffef7fe6c0 (LWP 26973) exited]
[Thread 0x7fffe6c0 (LWP 26972) exited]
[New Thread 0x7fffe6c0 (LWP 29620)]
[New Thread 0x7fffef7fe6c0 (LWP 29621)]
[Thread 0x7fffe6c0 (LWP 29620) exited]
[Thread 0x7fffef7fe6c0 (LWP 29621) exited]
[New Thread 0x7fffef7fe6c0 (LWP 29622)]
[New Thread 0x7fffe6c0 (LWP 29623)]
[Thread 0x7fffef7fe6c0 (LWP 29622) exited]
[Thread 0x7fffe6c0 (LWP 29623) exited]
[New Thread 0x7fffe6c0 (LWP 29624)]
[New Thread 0x7fffef7fe6c0 (LWP 29625)]
[Thread 0x7fffe6c0 (LWP 29624) exited]
[Thread 0x7fffef7fe6c0 (LWP 29625) exited]
[New Thread 0x7fffef7fe6c0 (LWP 29626)]
[New Thread 0x7fffe6c0 (LWP 29627)]
[Thread 0x7fffef7fe6c0 (LWP 29626) exited]
[Thread 0x7fffe6c0 (LWP 29627) exited]
[New Thread 0x7fffe6c0 (LWP 34349)]

(mate-volume-control-status-icon:26960): Gtk-WARNING **: 18:58:02.738: Calling 
gtk_widget_realize() on a widget that isn't inside a toplevel window is not 
going to work very well. Widgets must be inside a toplevel container before 
realizing them.

(mate-volume-control-status-icon:26960): GLib-GObject-CRITICAL **: 
18:58:02.738: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-volume-control-status-icon:26960): Gdk-CRITICAL **: 18:58:02.738: 
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: assertion 
failed: (window != NULL)
Bail out! Gtk:ERROR:../../../gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)

Thread 1 "mate-volume-con" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce type.
(gdb) 
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) n
Program not restarted.
(gdb) bt
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#1  0x7702ad2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#2  0x76fdbef2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#3  0x76fc6472 in __GI_abort () at ./stdlib/abort.c:79
#4  0x7719eec8 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x771fee1a in g_assertion_message_expr () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x77969d56 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x77978a6f in gtk_widget_realize () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x77978c68 in gtk_widget_map () at 
/lib/x86_64-linux-gnu/libgtk-3.so.0
#9  0x776ccf80 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x7771ee5f in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x772cf4e0 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x772e8bbf in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x772e8dbf in g_signal_emit () at 

Bug#971783: Any news ?

[Maxime G.]

Hi Mike, there is a workarround to auto restart the 
mate-volume-control-status-icon when it suddenly stops:

$ systemctl --user edit 
app-mate\\x2dvolume\\x2dcontrol\\x2dstatus\\x2dicon-autostart.service

Add between commented lines:

[Service]
Restart=always

$ systemctl --user daemon-reload
$ systemctl --user restart 
app-mate\\x2dvolume\\x2dcontrol\\x2dstatus\\x2dicon-autostart.service

Max.

15 février 2022 22:01 "Mike Gabriel"  a écrit:

> On So 13 Feb 2022 10:37:22 CET, Maxime G. wrote:
> 
>> Hello.
>> 
>> In Debian stable we try to have stable packages. But
>> volume-control-applet is not stable and crashes.
>> Despite the logs I sent earlier, here is a way to reproduce the problem:
>> - Connect a bluetooth speaker.
>> - Switch the main output of pulseaudio to the speaker.
>> - Play a media (web browser or player)
>> - Turn off the bluetooth speaker.
>> -> volume-control-applet crash
>> 
>> Thank you.
> 
> This will surely help finding the issue. I haven't had time for this,
> yet. But with a fool proof way of reproducing this, chances to get
> this fixes are getting bigger.
> 
> Thanks,
> Mike
> 
> --
> 
> DAS-NETZWERKTEAM
> c\o Technik- und Ökologiezentrum Eckernförde
> Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
> mobile: +49 (1520) 1976 148
> landline: +49 (4351) 850 8940
> 
> GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

Bug#971783: Any news ?

[Maxime G.]

Hello.

In Debian stable we try to have stable packages. But volume-control-applet is 
not stable and crashes.
Despite the logs I sent earlier, here is a way to reproduce the problem:
- Connect a bluetooth speaker.
- Switch the main output of pulseaudio to the speaker.
- Play a media (web browser or player)
- Turn off the bluetooth speaker.
-> volume-control-applet crash

Thank you.

Bug#971783: mate-volume-control-status-icon dies here too

[Maxime G.]

Thank you for your actions Mike.

Can you look at these open tickets for the same issue and take actions ?
#966840
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966840
#856072 (this one since 2017)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856072

Thanks.
Max.


19 novembre 2021 08:05 "Mike Gabriel"  a 
écrit:

> Control: severity -1 serious
> 
> Hi Maxime,
> 
> On Fr 19 Nov 2021 06:25:19 CET, Maxime G. wrote:
> 
>> Hi Mike.
>> 
>> Thanks for your reply about 1.26.
>> 
>> But it seems that the project don't want to take on this.
>> 
>> https://github.com/mate-desktop/mate-media/issues/159
>> https://github.com/mate-desktop/mate-media/issues/167
>> https://github.com/mate-desktop/mate-media/issues/109
>> https://github.com/mate-desktop/mate-media/issues/148
>> https://github.com/mate-desktop/mate-media/issues/137
>> https://github.com/mate-desktop/mate-media/issues/104
>> https://github.com/mate-desktop/mate-media/issues/89
>> 
>> This is problematic because we use this little icon a lot.
>> 
>> Thanks.
>> Max.
> 
> I'll raise severity of this bug as segfaulting applications require to
> be fixed. This also prioritizes fixing this bug for myself.
> 
> I'll look into this the coming days...
> 
> Mike
> --
> 
> DAS-NETZWERKTEAM
> c\o Technik- und Ökologiezentrum Eckernförde
> Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
> mobile: +49 (1520) 1976 148
> landline: +49 (4351) 850 8940
> 
> GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
> mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

Bug#971783: mate-volume-control-status-icon dies here too

[Maxime G.]

Hi Mike.

Thanks for your reply about 1.26.

But it seems that the project don't want to take on this.

https://github.com/mate-desktop/mate-media/issues/159
https://github.com/mate-desktop/mate-media/issues/167
https://github.com/mate-desktop/mate-media/issues/109
https://github.com/mate-desktop/mate-media/issues/148
https://github.com/mate-desktop/mate-media/issues/137
https://github.com/mate-desktop/mate-media/issues/104
https://github.com/mate-desktop/mate-media/issues/89

This is problematic because we use this little icon a lot.

Thanks.
Max.

Bug#971783: mate-volume-control-status-icon dies here too

[Maxime G.]

Hi.

What's the status of the ticket? Someone to update or push up to the project?

Tx.


18 juillet 2021 21:18 "Maxime G."  a écrit:

> New crash today for the volume control (mate-volume-control-status-icon), 
> please see the full debug
> level log attached to this e-mail.
> 
> Thanks.
> Max.

Bug#973552: GPU crashed while doing screencast using OBS studio

[Maxime G.]

Hello.

Like part of #987388, I had the same problem just now (gpu reset). The driver 
crashed when I pressed the record button in OBS studio with VAAPI.
I got a black screen and then back to the desktop, with a still image of my 
last action, everything was frozen.
I didn't lose the tty, I was able to restart lightdm without rebooting the 
machine by changing the tty and kept the uptime.

You will find the log attached.

Package: xserver-xorg-video-amdgpu 19.1.0-2
xorg-server 2:1.20.11-1 
Linux 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) x86_64 GNU/Linux

Thanks.
Max.
Jul 23 15:03:06 maxime-pc dbus-daemon[12433]: [session uid=1000 pid=12433] 
Activating service name='org.freedesktop.Notifications' requested by ':1.6228' 
(uid=1000 pid=213159 comm="/usr/lib/chromium/chromium --show-component-extens")
Jul 23 15:03:06 maxime-pc dbus-daemon[12433]: [session uid=1000 pid=12433] 
Successfully activated service 'org.freedesktop.Notifications'
Jul 23 15:05:11 maxime-pc kernel: [362445.143522] 
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed 
out!
Jul 23 15:05:16 maxime-pc kernel: [362445.143671] 
[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed 
out!
Jul 23 15:05:16 maxime-pc kernel: [362450.263791] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring vce2 timeout, signaled seq=16431, emitted seq=16432
Jul 23 15:05:16 maxime-pc kernel: [362450.264069] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process  pid 0 thread  pid 0
Jul 23 15:05:16 maxime-pc kernel: [362450.264078] amdgpu :01:00.0: amdgpu: 
GPU reset begin!
Jul 23 15:05:16 maxime-pc kernel: [362450.336599] 
[drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block 
 failed -22
Jul 23 15:05:16 maxime-pc kernel: [362450.544860] amdgpu :01:00.0: amdgpu: 
BACO reset
Jul 23 15:05:17 maxime-pc kernel: [362450.749167] amdgpu :01:00.0: amdgpu: 
GPU reset succeeded, trying to resume
Jul 23 15:05:17 maxime-pc kernel: [362450.750918] [drm] PCIE GART of 1024M 
enabled (table at 0x00F40030).
Jul 23 15:05:17 maxime-pc kernel: [362450.750998] [drm] VRAM is lost due to GPU 
reset!
Jul 23 15:05:17 maxime-pc kernel: [362451.025195] [drm] UVD initialized 
successfully.
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: Traceback (most recent call last):
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]:   File "/usr/local/bin/amdgpu-fan", 
line 8, in 
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: sys.exit(main())
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]:   File 
"/usr/local/lib/python3.9/dist-packages/amdgpu_fan/controller.py", line 78, in 
main
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: FanController(config).main()
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]:   File 
"/usr/local/lib/python3.9/dist-packages/amdgpu_fan/controller.py", line 30, in 
main
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: temp = card.gpu_temp
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]:   File 
"/usr/local/lib/python3.9/dist-packages/amdgpu_fan/lib/amdgpu.py", line 56, in 
gpu_temp
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: return 
float(self.read_endpoint('temp1_input')) / 1000
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]:   File 
"/usr/local/lib/python3.9/dist-packages/amdgpu_fan/lib/amdgpu.py", line 37, in 
read_endpoint
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: return e.read()
Jul 23 15:05:17 maxime-pc amdgpu-fan[566]: PermissionError: [Errno 1] Operation 
not permitted
Jul 23 15:05:17 maxime-pc systemd[1]: amdgpu-fan.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 23 15:05:17 maxime-pc systemd[1]: amdgpu-fan.service: Failed with result 
'exit-code'.
Jul 23 15:05:17 maxime-pc systemd[1]: amdgpu-fan.service: Consumed 4min 42.001s 
CPU time.
Jul 23 15:05:17 maxime-pc kernel: [362451.234397] [drm] VCE initialized 
successfully.
Jul 23 15:05:17 maxime-pc kernel: [362451.237770] amdgpu :01:00.0: amdgpu: 
recover vram bo from shadow start
Jul 23 15:05:17 maxime-pc kernel: [362451.244978] amdgpu :01:00.0: amdgpu: 
recover vram bo from shadow done
Jul 23 15:05:17 maxime-pc kernel: [362451.245004] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245014] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245018] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245021] amdgpu :01:00.0: amdgpu: 
GPU reset(1) succeeded!
Jul 23 15:05:17 maxime-pc kernel: [362451.245023] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245024] SW scheduler is used
Jul 23 15:05:17 maxime-pc kernel: [362451.245026] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245030] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245035] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245036] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245043] [drm] Skip scheduling IBs!
Jul 23 15:05:17 maxime-pc kernel: [362451.245046] [drm] Skip scheduling 

Bug#971783: mate-volume-control-status-icon dies here too

[Maxime G.]

Hello, same issue here.

I have this bug, it happens randomly without manipulation.
Here the log:


(mate-volume-control-status-icon:362306): Gtk-WARNING **: 08:21:55.878: 
gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 
1

(mate-volume-control-status-icon:362306): Gtk-WARNING **: 12:58:14.570: Calling 
gtk_widget_realize() on a widget that isn't inside a toplevel window is not 
going to work very well. Widgets must be inside a toplevel container before 
realizing them.

(mate-volume-control-status-icon:362306): GLib-GObject-CRITICAL **: 
12:58:14.570: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-volume-control-status-icon:362306): Gdk-CRITICAL **: 12:58:14.570: 
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../../../../gtk/gtkwidget.c:5871:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)
Bail out! 
Gtk:ERROR:../../../../gtk/gtkwidget.c:5871:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)
Abandon


Thanks.

Bug#987388: Crash of amdgpu on Debian 11 Bullseye

[Maxime G.]

Hello.

The linux-image-5.10.0-7 update fell in testing (bullseye) and it includes some 
patches for amdgpu. I do many tasks with amdgpu (games, vaapi decoding, vaapi 
encoding, gpu computations), I will report if any problem resurfaces.

Thanks !
Max.

Bug#987388: Crash of amdgpu on Debian 11 Bullseye

[Maxime G.]

According to other sources, it looks like a video memory overrun. I'm looking 
for a way to reproduce it. Do you have any ideas?

Bug#987388: Crash of amdgpu on Debian 11 Bullseye

[Maxime G.]

Package: xserver-xorg-video-amdgpu
Version: 19.1.0-2
Severity: critical

Hi.

Today I reinstalled a machine on Debian 11 Bullseye from testing (it was on 
Debian 10 Buster) and I had a crash of the AMD R9 380.
I could no longer change tty and Xorg was frozen, I could only move the mouse, 
the keyboard shortcut to reboot the kernel was not working.
After manual shutdown (electrical) I found undred lines of this in syslog:

Apr 22 22:36:18 maxime-pc kernel: [18427.590382] amdgpu :01:00.0: amdgpu: 
3fb1172e pin failed
Apr 22 22:36:18 maxime-pc kernel: [18427.590464] 
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer 
with error -12
Apr 22 22:36:18 maxime-pc kernel: [18427.605898] amdgpu :01:00.0: amdgpu: 
03ab56e3 pin failed
Apr 22 22:36:18 maxime-pc kernel: [18427.606010] 
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer 
with error -12
Apr 22 22:36:18 maxime-pc kernel: [18427.609057] amdgpu :01:00.0: amdgpu: 
03ab56e3 pin failed
Apr 22 22:36:18 maxime-pc kernel: [18427.609139] 
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer 
with error -12
Apr 22 22:36:18 maxime-pc kernel: [18427.610566] amdgpu :01:00.0: amdgpu: 
03ab56e3 pin failed
Apr 22 22:36:18 maxime-pc kernel: [18427.610644] 
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer 
with error -12
Apr 22 22:36:18 maxime-pc kernel: [18427.644577] amdgpu :01:00.0: amdgpu: 
3fb1172e pin failed
Apr 22 22:36:18 maxime-pc kernel: [18427.644659] 
[drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer 
with error -12

[...]

Apr 22 22:37:15 maxime-pc kernel: [18484.803085] sysrq: HELP : loglevel(0-9) 
reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usa
ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) 
unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) 
show-blocked-tasks(w) dump-ftrace-buffer(z) 
Apr 22 22:37:15 maxime-pc kernel: [18484.803096] sysrq: HELP : loglevel(0-9) 
reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usa
ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) 
unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) 
show-blocked-tasks(w) dump-ftrace-buffer(z) 
Apr 22 22:37:18 maxime-pc kernel: [18487.595072] sysrq: HELP : loglevel(0-9) 
reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usa
ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) 
unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) 
show-blocked-tasks(w) dump-ftrace-buffer(z) 
Apr 22 22:37:18 maxime-pc kernel: [18487.875072] sysrq: HELP : loglevel(0-9) 
reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) 
kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) 
show-memory-usa
ge(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) 
unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(v) 
show-blocked-tasks(w) dump-ftrace-buffer(z) 

(here I was typing on the emergency kernel reboot shortcut on keyboard)

I don't know what could be the reason for this.
But the problem has never occurred on Debian 10 Buster.


Thanks.
Max.

Bug#922699: Caja crash when copying paste

[Maxime G.]

Hi.

We are waiting for a fix from 2 years and we know how to solve it. As we cannot 
copy/paste a folder containing subfolders, you should list this bug as a 
Important bug.
Can a maintainer make a patch for caja in Buster ?

Thanks.
Max.

7 décembre 2020 02:15 "Maxime G."  a écrit:

> Hi.
> 
> Can you make a patch for Debian 10 stable ?
> We have Caja 1.20.3 and when I copy/paste a folder to make a clone copy 
> (duplication), caja
> crashes.
> I can reproduce this on all my Debian stable computers.
> 
> It's happen only when the folder contains sub-folders or/and files.
> 
> Thank you.
> Maxime.

Bug#916441:

[Maxime G.]

Hi.

Bug still occurs on Debian Buster with libvirt-daemon 5.0.0-4+deb10u1 when 
setting virgl on amdgpu.
Not reproducible on i965.


Erreur lors du démarrage du domaine: internal error: qemu unexpectedly closed 
the monitor: /usr/share/libdrm/amdgpu.ids: Permission denied
Failed to create /var/lib/libvirt/.cache for shader cache (Permission 
denied)---disabling.

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb
callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn
ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1400, in startup
self._backend.create()
  File "/usr/lib/python3/dist-packages/libvirt.py", line 1080, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 
/usr/share/libdrm/amdgpu.ids: Permission denied
Failed to create /var/lib/libvirt/.cache for shader cache (Permission 
denied)---disabling.

("permission denied", but virt-manager runs under sudo)

But, setting the workarround mentionned before in qemu.conf works.

Thanks.
Maxime.

Bug#922699: Caja crash when copying paste

[Maxime G.]

Hi.

Can you make a patch for Debian 10 stable ?
We have Caja 1.20.3 and when I copy/paste a folder to make a clone copy 
(duplication), caja crashes.
I can reproduce this on all my Debian stable computers.


It's happen only when the folder contains sub-folders or/and files.

Thank you.
Maxime.