Created attachment 12410 [details]
backtrace of pavucontrol segfault

This is same as bug https://bugzilla.redhat.com/show_bug.cgi?id=1725150, that has been fixed with https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/commit/284082551938b65e71d06bda793fedbd4a4f41ab. Updating to cauldron and mga8/updates_testing in pavucontrol-4.0-3.mga8|9.

Please use "%define subrel 1" next time for a stable release update.

CC: (none) => geiger.david68210

It it's ready for qa, please reassign the bug and provide an advisory

Assigning to you Giuseppe, Thanks reporting this.

Assignee: bugsquad => ghibomgx
CC: (none) => ouaurelien

And this should be assigned to QA.

Advisory:
========================

Updated pavucontrol package fixes a segfault on exiting

The updated pavucontrol package fixes a segfault by applying an upstream
patch.

References:
 - https://bugs.mageia.org/show_bug.cgi?id=28486
 - https://bugzilla.redhat.com/show_bug.cgi?id=1725150
 - https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/commit/284082551938b65e71d06bda793fedbd4a4f41ab
========================

Updated packages in core/updates_testing:
========================
pavucontrol-4.0-3.mga8

from SRPM:
pavucontrol-4.0-3.mga8.src.rpm

Assignee: ghibomgx => qa-bugs

Intel i5 2500, Intel graphics, 64-bit Mga8 Plasma system.

I was unable to reproduce this, but when I run "pavucontrol" from Konsole, I do see this:

$ pavucontrol

(pavucontrol:298229): Gtk-WARNING **: 15:04:09.366: Theme parsing error: gtk.css:2:33: Failed to import: Error opening file /home/tom/.config/gtk-3.0/window_decorations.css: No such file or directory

I've seen this sort of warning before, when running a gtk+ app in a QT environment, and so far it seems to have been harmless. 

Closing pavucontrol just gives me the user prompt.

After the update, I get the same thing. So, it looks OK to me, but, since I couldn't reproduce the error, I can't say that it is fixed. 

Hmmm. Suddenly wondering... If I HAD the "window_decorations.css" file that seems to be missing, would I have then seen the problem in the old pavucontrol?

CC: (none) => andrewsfarm

(In reply to Thomas Andrews from comment #7)
> Intel i5 2500, Intel graphics, 64-bit Mga8 Plasma system.
> 
> I was unable to reproduce this, but when I run "pavucontrol" from Konsole, I
> do see this:
> 
> $ pavucontrol
> 
> (pavucontrol:298229): Gtk-WARNING **: 15:04:09.366: Theme parsing error:
> gtk.css:2:33: Failed to import: Error opening file
> /home/tom/.config/gtk-3.0/window_decorations.css: No such file or directory
> 
> I've seen this sort of warning before, when running a gtk+ app in a QT
> environment, and so far it seems to have been harmless. 
> 
> Closing pavucontrol just gives me the user prompt.
> 
> After the update, I get the same thing. So, it looks OK to me, but, since I
> couldn't reproduce the error, I can't say that it is fixed. 
> 
> Hmmm. Suddenly wondering... If I HAD the "window_decorations.css" file that
> seems to be missing, would I have then seen the problem in the old
> pavucontrol?

This is unrelated.
For the gtk3 bug see: https://bugs.mageia.org/show_bug.cgi?id=28299

I see. Another KDE-induced bug.

Well, any suggestions on what I can do to reproduce this issue on one of my other boxes, so I can confirm that it is fixed?

Unsure if Plasma is best platform to test this, as I think it uses pavucontrol-qt.

Also, I will test under GNOME or Xfce.

There's an idea. 

Tonight I'll see if I can get the steam boiler up to pressure on Foolishness, my old Dell Inspiron 5100. It uses 32-bit Xfce. It's about time I updated it again, anyway.

Still can't reproduce it. Dell Inspiron 5100, 32-bit P4, Radeon RV200 graphics, 32-bit Xfce system.

I get the same results as Comment 7, only without the warning. Nothing at all to indicate the present pavucontrol has anything wrong with it. The update candidate works just the same. So, it looks OK for 32-bits, except that I can't tell if it fixes the issue.

mga8, x64
pavucontrol exits cleanly in Mate on current machine.
$ rpm -q pavucontrol
pavucontrol-4.0-2.mga8

CC: (none) => tarazed25

Just tried this in a 54-bit mga8 Gnome Vbox guest, and once again cannot reproduce the issue before the update or after.

This has gone on long enough. Even though we can't seem to verify that the issue is fixed, the reporter says it's fixed, and at least this update doesn't seem to do any harm. Giving it both OKs, and validating. Advisory in Comment 6.

Keywords: (none) => validated_update
Whiteboard: (none) => MGA8-64-OK MGA8-32-OK
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0125.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED