On 03/04/2014 06:32 AM, Antoine Beaupré wrote:
Package: pavucontrol
Followup-For: Bug #735898
Control: tags -1 pending
I'll upload this patch shortly (NMU, 2 days delay), since it seems to
fix the problem and pavucontrol is threatened by autoremoval.
Hi Antoine,
The patch is on pavucontrol
On 2014-03-04 16:08:15, Léo Cavaillé wrote:
The patch is on pavucontrol debian git, and I finished the packaging of
2.0 version today, tomorrow I will upload pavucontrol 2.0-1 to the archive.
That's great, thanks!
Do you want me to remove the upload from DELAYED/2? It should be
overriden by
Hi. how-can-i-help just told me that pavucontrol is scheduled for
removal from jessie 2014-03-10 because of this bug. Is a fix with the
proposed patch planned any time soon?
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Package: pavucontrol
Followup-For: Bug #735898
Control: tags -1 pending
I'll upload this patch shortly (NMU, 2 days delay), since it seems to
fix the problem and pavucontrol is threatened by autoremoval.
Cheers,
A.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT
Hi John,
maybe we can investigate also with gdb compiling pavucontrol with debug
symbols:
$ apt-get source pavucontrol cd pavucontrol-1.0
$ export DEB_BUILD_OPTIONS=nostrip noopt
$ dpkg-buildpackage -rfakeroot -uc -us
$ sudo dpkg -i ../pavucontrol_1.0-1_i386.deb
$ gdb pavucontrol
and attach
Done:
~$ gdb `which pavucontrol`
GNU gdb (GDB) 7.6.2 (Debian 7.6.2-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the
On 2014-02-22 18:58:08 -0500, John M. wrote:
Program received signal SIGSEGV, Segmentation fault.
0x00428d80 in read_callback (s=0xcea800, length=4,
userdata=0x9561b0) at mainwindow.cc:385
385 v = ((const float*) data)[length / sizeof(float) -1];
[...]
Thanks. The
Control: tags -1 patch
On 2014-02-23 04:52:46 +0100, Vincent Lefevre wrote:
data can be NULL and the code is obviously buggy.
gnome-control-center seemed to have similar code, thus was also buggy:
https://bugzilla.gnome.org/show_bug.cgi?id=689079
which has a patch:
The full backtrace shows:
(gdb) backtrace full
#0 0x00428d80 in read_callback (s=0xced1b0, length=4,
userdata=0x92d600) at mainwindow.cc:385
w = 0x92d600
data = 0x0
v = 7.1675486625997992e-317
The patch works!
I can finally use pavucontrol (1.0-1) for more than one second.
Thanks a lot for the help provided.
--
John.
On Sun, 2014-02-23 at 05:01 +0100, Vincent Lefevre wrote:
Control: tags -1 patch
On 2014-02-23 04:52:46 +0100, Vincent Lefevre wrote:
data can be NULL and the
Hi John,
yes, you can you try to execute
$ strace -o pavucontrol.log pavucontrol
and attach here pavucontrol.log
--
Simone Vellei (henomis)
GPG KEYID: A3D37CF4
GPG FINGERPRINT: 5A79 3A3A 143E 9B37 9B38 FB86 8E45 8B62 A3D3 7CF4
On 2014-02-14 02:40:36 -0500, John M. wrote:
By creating a new user account, I'm able to open pavucontrol from that
account, but only until I log out and in again. Then it's back to
segmentation fault.
So it seems like the problem is related to a setting in some other
program (gconf? dconf?
Hi,
I patched the source, rebuilt the package and upgraded, but I still get
segmentation fault.
By creating a new user account, I'm able to open pavucontrol from that
account, but only until I log out and in again. Then it's back to
segmentation fault.
So it seems like the problem is related to
On 2014-01-20 15:36:37 +0400, Vlad Orlov wrote:
Can't reproduce it.
I can't reproduce it either. If this doesn't affect most users,
the bug severity should be lowered to important, if the bug is not
reassigned in case it would be:
Run dmesg after that and check the last lines of the output for
The WorksForMe bug is certainly the worst of all.
At the time of reporting the bug, I had just moved to a new laptop, so
the issue happens on a newly installed Jessie. In the old laptop (in
which Wheezy was originally installed in 2011), with all the Jessie
updates, pavucontrol has always
Can't reproduce it.
Run dmesg after that and check the last lines of the output for the hints about
the cause of segfault. If it says something about libgtk-3.so then you've
probably
been hit by a known bug in gtk3-engines-unico [1] and need to change your
GTK+ theme to something not using
Package: pavucontrol
Version: 1.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
When I run pavucontrol, either from the pulseaudio shortcuts (gnome) extension,
or from the command line, it segfaults (the pavucontrol window opens and closes
quickly):
$ pavucontrol
17 matches
Mail list logo
