l and an unsuccesful run?
https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems
--
Saludos,
Felipe Sateler
Control: found -1 14.2-2
Control: fixed -1 14.99-1
Hi Michał!
On Thu, Jul 29, 2021 at 9:27 AM Michał Mirosław
wrote:
> On Thu, Jul 29, 2021 at 12:57:03PM +, Debian Bug Tracking System wrote:
> > Date: Thu, 29 Jul 2021 08:51:50 -0400
> > From: Felipe Sateler
&
pulseaudio crashes on startup in
> pa_alsa_sink_new() -> find_mixer() due to mapping==NULL.
>
You have this in your config:
load-module module-alsa-sink device=hw:1,0 control=Wave
Does it crash if you remove that line?
--
Saludos,
Felipe Sateler
Control: tag -1 pending
Hello,
Bug #982740 in pulseaudio reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/pulseaudio-team/pulseaudio/-/commit/d11d6825e023e818fde
Control: tag -1 pending
Hello,
Bug #960259 in csound reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/csound/-/commit/af28017c591518f530e6abcf8da
Control: tag -1 pending
Hello,
Bug #960128 in csound reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/csound/-/commit/3b4a687bc70ea27e2f87f9b779e
Thank you. Feel free to upload directly to unstable.
Saludos,
Felipe Sateler
On Fri, May 8, 2020, 04:57 Thomas Goirand wrote:
> Hi,
>
> Since nobody seem to care, I uploaded the fix to delay/2:
>
> --- a/debian/control
> +++ b/debian/control
> @@ -19,7 +19,7 @@
>
&g
Control: tag -1 pending
Hello,
Bug #956672 in rtkit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/rtkit/-/commit/ded7abdfeb6ffce87ffea43111a5e
Control: tag -1 pending
Hello,
Bug #946104 in rtkit reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/rtkit/-/commit/46ece9aa4dc416b7880310d7b0333
Package: php-recode
Version: 2:7.4+74
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The php-recode package is currently not installable because it depends
on php7.4-recode, which doesn't exist.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-
don't think this issue qualifies as release-critical. You really should
not be using phpmyadmin over http, and nstead have your http server
redirect to https. I'm thus downgrading.
William, is the entire PR required, or just a section of it?
--
Saludos,
Felipe Sateler
> parties.
>
The idea was to let systemctl/systemd order the jobs in whatever way it saw
fit, according to the ordering requirements of the units. If there is a bug
somewhere, it is either in systemd, or in rpcbind where an ordering
requirement is missing.
Does the problem persist if you add After=rpcbind.socket to rpcbind.service?
--
Saludos,
Felipe Sateler
I'd like long term to
revert the order: disable autospawn by default, and have non-systemd run
something to enable it.
Honestly, I'm a bit annoyed about all this rushing. This behaviour has been
present since 2017, and all of a sudden this is unacceptable and needs to
be fixed less than a month before release.
--
Saludos,
Felipe Sateler
-util is not liking. What is your sbuild setup? It's not
failing for me with sbuild either.
--
Saludos,
Felipe Sateler
Control: found -1 241-5
Control: tags -1 confirmed upstream
Control: forwarded -1 https://github.com/systemd/systemd/issues/11842
I was able to reproduce the issue, and forwarded this upstream.
--
Saludos,
Felipe Sateler
Control: severity -1 important
Control: retitle -1 udev: can't start when architecture != systemd
On Fri, Feb 15, 2019 at 4:19 AM Vincent Danjean wrote:
> Le 15/02/2019 à 08:01, Vincent Danjean a écrit :
> > Le 14/02/2019 à 22:59, Felipe Sateler a écrit :
> >> Is udev by
ature that was problematic
> as I quickly needed the computer for (long) production. If you need
> more info or tests, I should be able to reboot the system in a few
> days.
>
> Regards,
> Vincent
>
> -- Package-specific info:
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'unstable'), (500,
> 'testing'), (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armel, mipsel
>
Is udev by any chance i386 instead of amd64?
--
Saludos,
Felipe Sateler
Control: tag -1 pending
Hello,
Bug #918764 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/systemd-team/systemd/commit/617ee70c31c45ea5d5c6c7b30766d4
On Mon, Feb 4, 2019 at 11:34 AM Axel Beckert wrote:
> Hi Felipe,
>
> Felipe Sateler wrote:
> > Upstream asks if cgroup is in v2-mode in the affected systems.
>
> How do I recognize this? I have no idea of how to check that.
>
With `findmnt -R /sys/fs/cgroup`. It should
On Sun, Feb 3, 2019 at 6:41 PM Felipe Sateler wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/11645
>
> I have forwarded the bug upstream, and proposed two solutions. If upstream
> likes one, we can apply that in the debian package.
>
>
Upstream asks
Control: forwarded -1 https://github.com/systemd/systemd/issues/11645
I have forwarded the bug upstream, and proposed two solutions. If upstream
likes one, we can apply that in the debian package.
Saludos
On Wed, Jan 30, 2019 at 7:47 PM Axel Beckert wrote:
> Hi Felipe,
>
> a short reply with that information I can gather without much effort:
>
> Felipe Sateler wrote:
> > > But we also had reports where this happend
> > > with systemd, so this doesn't se
s, and only if we are
directly spawned
by PID1. otherwise we are not guaranteed to have a
dedicated cgroup */
--
Saludos,
Felipe Sateler
Hi Martin,
On Sun, Jan 27, 2019, 17:37 Martin Pitt Hello Felipe,
>
> Felipe Sateler [2019-01-26 0:04 +]:
> > Bug #919390 in systemd reported by you has been fixed in the
> > Git repository and is awaiting an upload. You can see the commit
> > message below and you c
Control: tag -1 pending
Hello,
Bug #919390 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/systemd-team/systemd/commit/ca9bf5fdd69e1f6bb137d905f90225
Control: tag -1 pending
Hello,
Bug #919390 in systemd reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/systemd-team/systemd/commit/3eea472b0c1c171f86c0cf5c6f4788
Control: severity 909974 important
On Fri, Jan 11, 2019 at 10:15 AM Felipe Sateler wrote:
>
>
> On Tue, Oct 2, 2018 at 4:22 PM Felipe Sateler wrote:
>
>> Hi Matthias, Ivo,
>>
>> On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker
>> wrote:
>> > cl
On Sun, 13 Jan 2019 18:10:57 +0100 Axel Beckert wrote:
> Package: irqbalance
> Version: 1.5.0-2
> Severity: serious
>
> On one of my systems (not the one I'm writing the report on), a
> Raspberry Pi 2 with Debian Sid armhf and sysvinit, the terminal which I
> ran the upgrade in, looked like this (
uld be to run the test from 0.9
with the binary from 0.8.
That said, I certainly welcome help. I'm completely overloaded right now so
I can't look at this.
[1] Thread at https://lists.debian.org/debian-mips/2016/04/msg4.html
--
Saludos,
Felipe Sateler
On Tue, Oct 2, 2018 at 4:22 PM Felipe Sateler wrote:
> Hi Matthias, Ivo,
>
> On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker wrote:
> > clone 869896 -1
> > retitle -1 remove unneeded dependency on backports.ssl-match-hostname
> > block 869896 by -1
> > clo
On Fri, Dec 28, 2018 at 10:33 AM Patrick Matthäi
wrote:
> Hola,
> Am 24.12.2018 um 12:44 schrieb Felipe Sateler:
>
> > Perhaps znc could Provide: znc-plugin-$somenumber, which could be used by
>
>> > out-of-tree plugins? Adding the znc maintainers to the loop for
Control: clone -1 -2
Control: reopen -2
Control: reassign -2 znc
Control: affects -2 znc-backlog
Control: retitle -2 znc: please provide a znc-plugin-$version that external
plugins can depend on
On Tue, Dec 18, 2018 at 3:39 PM Andreas Beckmann wrote:
> On 2018-12-18 18:13, Felipe Sateler wr
by
out-of-tree plugins? Adding the znc maintainers to the loop for their input
--
Saludos,
Felipe Sateler
e-sed-found-by-configure-use-the-sed-command.patch
>
I meant the fix for #905187, and based on the changelog entry.
Anyway, I see you have already tagged an upload containing that commit.
Let's just wait for it to enter unstable.
Thanks!
--
Saludos,
Felipe Sateler
On Wed, Nov 14, 2018 at 11:01 AM Michael Biebl wrote:
> Hi Felipe
>
> On Wed, 14 Nov 2018 10:42:55 -0300 Felipe Sateler
> wrote:
> > + SED=/bin/sed dh_auto_configure --builddirectory $${target}-build
> $(PARALLEL) -- $$(eval echo \$${$${target}_config}); \
ebuilt the package in a
non-merged environment. Please find attached a patch that sets SED to a
known-good value, thus making the build work for both merged and non-merged
systems.
Saludos,
Felipe Sateler
From 1b4df9e00b2093cd688f2d4d455912c8da48494e Mon Sep 17 00:00:00 2001
From: Felipe Sateler
lso contributed, but it's very difficult to
> pin down where exactly the breakdown is, I don't think it's pulseaudio
> itself, it's what it depends on.
>
Based on this information I'm reassigning to the alsa library.
--
Saludos,
Felipe Sateler
ion 1.1.6-1?
--
Saludos,
Felipe Sateler
ease install
pulseaudio-dbgsym (you might need to add the debug archive to
sources.list), and attach the backtrace of the fault.
--
Saludos,
Felipe Sateler
eview2's removal
> from Buster.
>
>
While I sympathize with the desire to get rid of old libraries, I think
this bug comes too late. This bug should have been filed before stretch was
released if the target was buster.
I object to the serious severity, at least for this release cycle.
--
Saludos,
Felipe Sateler
ase archs.
>
Hmm. I wonder why does mips64el have an old binary. This is #821435, and I
requested removal on #822211. Maybe mips64el was not an offical arch back
then?
Anyway, dear FTP master team, please RM patchelf from mips64el.
--
Saludos,
Felipe Sateler
>
Sorry, copy paste fail. The other directory is /run/systemd/seats/ .
--
Saludos,
Felipe Sateler
log?
$ systemctl --user --runtime edit pulseaudio
Add the following lines to the file
[Service]
ExecStart=/usr/bin/pulseaudio --daemonize=no -
Then restart pulseaudio, and get the log with `journalctl --user-unit
pulseaudio --since "$when_you_restarted_pulseaudio"`
--
Saludos,
Felipe Sateler
Hi Matthias, Ivo,
On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker wrote:
> clone 869896 -1
> retitle -1 remove unneeded dependency on backports.ssl-match-hostname
> block 869896 by -1
> clone -1 -2 -3 -4 -5
> reassign -1 libcloud
> reassign -2 python-docker
> reassign -3 websocket-client
> reass
Control: tag -1 pending
Hello,
Bug #906504 in pulseaudio reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pulseaudio-team/pulseaudio/commit/0b8f91adb022d4baf6d6
Control: tag -1 pending
Hello,
Bug #903612 in csound reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/csound/commit/5ea243bb7accd67700bebeaeb22e
Control: tag -1 pending
Hello,
Bug #906504 in pulseaudio reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pulseaudio-team/pulseaudio/commit/84d1788830cdc246b33c
On Sat, Aug 11, 2018 at 9:54 AM Meinolf Gödde wrote:
> The problem is back again. So i hope it helps.
>
The log file is empty :(.
Anyway, are you using MATE? Another bug with the same symptoms seems to be
caused by the mate volume manager (see bug #906622).
Saludos
--
Saludos,
Control: forcemerge 903295 -1
On Tue, Aug 28, 2018, 14:00 Robbie Harwood wrote:
> Package: libpam-systemd
> Version: 238-5
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> (This bug has been reported also against systemd-shim:
> https://bugs.debian.org/cgi-bin
was disabled in !x86 a long time ago for unclear reasons.
> The lack of atomics causes a test exercising the async features to
> hang
> (Closes: #903612)
>
>
Turns out mips and mipsel do not support the atomic builtins used by csound.
Reopening the bug until a new solution i
Control: tag -1 pending
Hello,
Bug #903612 in csound reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/multimedia-team/csound/commit/0bb1b184933425fc22f87a86c24a
On Fri, Aug 17, 2018 at 10:59 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:45 schrieb Michael Biebl:
> > Am 17.08.2018 um 15:37 schrieb Felipe Sateler:
> >
> >> Well, as long as we support the --skip-systemd-native, we can't drop the
> >> check :/
> &g
On Fri, Aug 17, 2018 at 10:33 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:27 schrieb Felipe Sateler:
> > I'll revert the change to unbreak things soon. For the longer term,
> > maybe we can switch the check to
> >
> > /lib/systemd/systemd-sysv-install is-enable
On Fri, Aug 17, 2018 at 10:24 AM Michael Biebl wrote:
> Am 17.08.2018 um 15:13 schrieb Felipe Sateler:
>
> > Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the
> > culprit of the regression. But I'd like to understand why this happens.
> > Shouldn&#
27;
> + case ${ACTION} in
> + systemctl --quiet is-enabled lldpad.service
> + systemctl --quiet is-active lldpad.service
> + RC=101
>
Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the culprit
of the regression. But I'd like to understand why this happens. Shouldn't
update-rc.d have enabled the service?
This looks like the same as #906051.
Setting severity to serious. I'll revert the change, until I find some time
to fully investigate the issue.
--
Saludos,
Felipe Sateler
t; anymore)
> >>
> >> This is also a problem in buster (which is still using 11.1-5)
> >>
> >
> > Seems like pulseaudio is not starting. Please attach the output of
> > `pulseaudio - --daemonize=no`, without applying your workaround.
--
Saludos,
Felipe Sateler
dio - --daemonize=no`, without applying your workaround.
--
Saludos,
Felipe Sateler
Control: tag -1 pending
Hello,
Bug #885038 in paprefs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pulseaudio-team/paprefs/commit/2e76ca4ea884f1470b15a9f943
Control: tag -1 pending
Hello,
Bug #885076 in paprefs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/pulseaudio-team/paprefs/commit/2e76ca4ea884f1470b15a9f943
-graph.php?packages=pulseaudio-module-gconf%2Cplasma-pa%2Cpaprefs%2Cpulseaudio&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
--
Saludos,
Felipe Sateler
t; (See also pulseaudio's bug https://bugs.debian.org/902181)
>
> This raises the urgency of dealing with the bug in plasma-pa to remove
> gconf
> dependency. Please look into this issue (Debian Bug #886048) again and
> solve
> it ASAP.
>
Indeed.
Note that I do not plan to reintroduce the gconf module, so fixing this in
plasma-pa is important.
--
Saludos,
Felipe Sateler
86_64-linux-gnu/libc.so.6(__libc_start_main+0xee) [0x7f6746ccca8e]
> python(_start+0x2a) [0x55ca4720db1a]
The crash actually happens upon module unload (when the interpreter is
exiting). I'm therefore lowering the severity since it doesn't make
the module unusable.
--
Saludos,
Felipe Sateler
you don't object.
>
I'd be happy if you do. I'm currently suffering from ENOTIME so I'm not
likely to get around to doing that soon.
--
Saludos,
Felipe Sateler
ars the time has come to migrate away...
--
Saludos,
Felipe Sateler
Hi Joachim,
On Tue, Nov 14, 2017 at 4:35 PM, Joachim Breitner wrote:
>
> Hi Felipe,
>
> this just came in. Since you last worked on this package, would you be
> interesting in fixing this bug?
>
Sorry, I'm currently lacking time to do this.
--
Saludos,
Felipe Sateler
hat the problem is the
addition of the max_file_size to the Options class. ABI tracker seems
to agree with me[1].
Dear leveldb maintainers, please bump soname and do a transition.
[1]
https://abi-laboratory.pro/tracker/compat_report/leveldb/1.19/1.20/ecd6d/abi_compat_report.html
--
Saludos,
Felipe Sateler
0e4c6b42b7fafac98baa93ef5efac5d766f1ce75
Author: Felipe Sateler
Date: Thu Oct 12 21:21:08 2017 -0300
Release
diff --git a/debian/changelog b/debian/changelog
index 00df070..951a392 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+supercollider (1:3.8.0~repack-2) unstable; urgency=medium
0e4c6b42b7fafac98baa93ef5efac5d766f1ce75
Author: Felipe Sateler
Date: Thu Oct 12 21:21:08 2017 -0300
Release
diff --git a/debian/changelog b/debian/changelog
index 00df070..951a392 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+supercollider (1:3.8.0~repack-2) unstable; urgency=medium
that in this case, the correct fix is to drop the Also= line.
1. We don't want to stop avahi-daemon socket if dnsconfd is removed
2. It appears the Also line is being treated as some form of
dependency manager (ie, to ensure that the avahi-daemon is started
when dnsconfd is started), but it is not necessary, because
avahi-daemon.socket is already Required.
So, I think we have not yet found a compelling case for dropping the
debhelper error. The Also line is not needed, and can be safely
dropped from the avahi-dnsconfd unit.
--
Saludos,
Felipe Sateler
On Tue, Oct 3, 2017 at 7:04 PM, Jonas Smedegaard wrote:
> Quoting Felipe Sateler (2017-10-03 23:32:24)
>> On Tue, Oct 3, 2017 at 5:49 PM, Jonas Smedegaard wrote:
>> > Package: kodi
>> > Version: 2:17.3+dfsg1-2
>> > Severity: grave
>>
>> This s
kodi-repository-kodi and move the latter to
> contrib.
I don't think moving to contrib makes sense. Either the package fits
the requirements for main or it doesn't.
I don't think this package should go in contrib, as it doesn't *need*
any software not available in main. So it should not be moved there.
--
Saludos,
Felipe Sateler
8438806ab1b811372341efbc86a36704ff6b5d6d
Author: Felipe Sateler
Date: Thu Sep 7 19:52:21 2017 -0300
Release
diff --git a/debian/changelog b/debian/changelog
index ce09536..c1d42f1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+supercollider (1:3.7.0~repack-5) unstable; urgency=medium
550dc39611a3ea1cf33ab8bdd73b103e0f3d5faf
Author: Felipe Sateler
Date: Wed Aug 23 13:12:54 2017 -0300
Release
diff --git a/debian/changelog b/debian/changelog
index 364c9b5..c6dd98f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+csound (1:6.09.1~dfsg-2) unstable; urgency=medium
+
+ * Fix build
Control: forwarded -1 https://github.com/csound/csound/pull/839
On Tue, Aug 22, 2017 at 4:07 PM, Anton Gladky wrote:
> tags 872860 +patch
> thanks
>
> Dear maintainers,
>
> in attachment you will find a patch which fixes FTBFS due to a new
> getfem (gmm) version. It would be good if somebody revi
w (and/or
> deleted) files in the udev and libudev1 binaries are detected by
> maintainers (esp. since udev.install uses wildcards for rules files, while
> udev-udeb.rules uses a static list), so that the update can be propagated
> to the udebs if relevant.
--fail-missing is broken on the udeb builds at the moment, so it is
not enabled. I'll try to fix this and enable it. This should help
catch these sort of issues in the future.
--
Saludos,
Felipe Sateler
Package: src:nodejs
Version: 6.11.2~dfsg-2
Severity: serious
nodejs failed to build with this error:
make[1]: Entering directory '/<>'
# Clean up any leftover processes but don't error if found.
ps awwx | grep Release/node | grep -v grep | cat
/usr/bin/python tools/test.py -p tap \
--mod
42e656abae76c8b1ae881e57c58210b7faf3accf
Author: Felipe Sateler
Date: Fri Aug 11 19:58:27 2017 -0400
Release
diff --git a/debian/changelog b/debian/changelog
index 2efb7ba..8f15c17 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+csound-manual (1:6.09.0~dfsg-2) unstable; urgency=medium
57e0082975b7359a681fe975f94ab36c4e5c3978
Author: Felipe Sateler
Date: Wed Aug 9 21:28:19 2017 -0400
Release
diff --git a/debian/changelog b/debian/changelog
index c8dbf32..364c9b5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,16 @@
-csound (1:6.09.1~dfsg-1) UNRELEASED; urgency=medium
+csound (1:6.09.1
non-root as Lennart suggested. AFAICT, the only reasong for
running as root is to access the softsynth device, but that could be
managed via regular uaccess and group mechanism like /dev/snd/* does. We
shouldn't require running pulseaudio as root, as it would be better if
espeakup would run unprivileged.
I'll leave it to the espeakup maintainers to adjust severity.
--
Saludos,
Felipe Sateler
stream releases. Maybe this issue does not exist in the newer
release?
--
Saludos,
Felipe Sateler
go - thus making it impossible
for the alternative programs to actually play the sound.
Some information that would be useful:
1. Is your user part of the audio group?
2. Does any of the programs that actually play the sound run as root or a
user that is in the audio group?
3. Please attach the output of `lsof /dev/snd/*` for each of the
problematic states (this should answer question 2).
--
Saludos,
Felipe Sateler
Control: tags -1 help gift
On Sun, May 21, 2017 at 7:11 PM, Felipe Sateler wrote:
> On Sun, May 21, 2017 at 10:36 AM, Mattia Rizzolo
> wrote:
> > Source: pulseaudio
> > Version: 10.0-1
> > Severity: serious
> >
> > the copyright file has this paragr
Package: pasystray
Version: 0.6.0-1
Severity: serious
pasystray crashes on startup when running under gnome wayland:
#0 0xedc7 in x11_property_init () at x11-property.c:46
#1 0xb10a in init (settings=0x7fffdf10) at pasystray.c:65
#2 0x8f63 in main (argc=
of those)
`grep usr/share/doc /usr/share/doc/*/copyright` in my system lists
several files making references to copyright in other files. Policy
might need to be updated.
--
Saludos,
Felipe Sateler
7b2ec31c8f7bbdcad893502e21533056ad5a26b9
Author: Felipe Sateler
Date: Wed Mar 29 10:40:12 2017 -0300
Release to unstable
diff --git a/debian/changelog b/debian/changelog
index d293d44..29fcf7d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.5.2+dfsg-5) unstable; urgency=medium
+
+ * Use
7b2ec31c8f7bbdcad893502e21533056ad5a26b9
Author: Felipe Sateler
Date: Wed Mar 29 10:40:12 2017 -0300
Release to unstable
diff --git a/debian/changelog b/debian/changelog
index d293d44..29fcf7d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+stk (4.5.2+dfsg-5) unstable; urgency=medium
+
+ * Use
gt; versions with which libsbc 1.3-1 and 1.3-1+b2 were created? Just
> to double check whether the official uploads were indeed created
> with gcc-4.9 for libsbc 1.3-1 and gcc-5/gcc-6 for 1.3-1+b2?
The build logs are publicly available, for this build[1] the versions used were:
binutils_2.25-8
Control: retitle -1 libsbc1: compiling with gcc > 4.9 causes stack corruption
On Fri, Mar 3, 2017 at 3:24 PM, Linus Lüssing wrote:
> On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote:
>> It has been pointed out to me that this may be unrelated to PIE, but
>> just
On Fri, Mar 3, 2017 at 11:06 AM, Felipe Sateler wrote:
> Control: tags -1 - help
> Control: reassign -1 libsbc1 1.3-1+b2
> Control: retitle -1 libsbc1: build with PIE causes stack corruption
> Control: affects -1 pulseaudio
> Control: severity -1 serious
>
>
> On Fri,
Control: severity -1 important
On Wed, 15 Feb 2017 23:15:33 -0600 Bob Tracy wrote:
> Source: nodejs
> Version: 4.7.2~dfsg-2
> Severity: serious
> Justification: fails to build from source
alpha is not a release architecture. Thus downgrading to important.
Saludos
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-1
Severity: grave
Justification: renders docker unusable
Control: affects -1 docker.io
After upgrading to 1.0.0~rc2+git20161109.131.5137186-1 , docker
containers fail to start:
Cannot start service web: rpc error: code = 2 desc = "oci runt
Control: severity -1 normal
On 5 February 2017 at 12:06, Vít Novotný wrote:
> On Sat, Feb 04, 2017 at 09:59:50AM -0300, Felipe Sateler wrote:
>> On 30 January 2017 at 13:33, Vít Novotný wrote:
>> > ( 631.872| 0.000) I: [pulseaudio] module-stream-restore.c: Restoring
&g
nnel map front-left,front-right
This shows mpv, in the first attempt, still tries to output to the
sound card and not to the jack sound server. You can use pavucontrol
to move the stream from the sound card to the jack server.
--
Saludos,
Felipe Sateler
$ pactl set-default-source jack_in
>
> there is no sound nevertheless.
>
> Note that both pulseaudio and jack work flawlessly separately. The
> issue is in making pulseaudio work as a jack client.
Could you attach a verbose log when reproducing the problem?
https://wiki.ubuntu.com/PulseAudio/Log
--
Saludos,
Felipe Sateler
On 25 January 2017 at 14:36, Jacob Luna Lundberg wrote:
>
> Hi Felipe,
>
> On Wed, Jan 25, 2017 at 11:50:33AM -0300, Felipe Sateler wrote:
>> Apparently, fcow-utils as currently packaged is not usable in
>> debian.
>
> It is plenty usable, just not if you are u
, Yann
Richard, maybe you are interested in helping maintain this package?
--
Saludos,
Felipe Sateler
debian
package? The linked git repository contains the entire debian
directory as a single commit. Moreover, that commit includes build
artifacts (eg, the scripts generated by debhelper), so that makes
review harder.
--
Saludos,
Felipe Sateler
bc80398bb019ca483163ba67685e0d64d0e2d2fd
Author: Felipe Sateler
Date: Tue Jan 3 21:30:25 2017 -0300
Release to unstable
diff --git a/debian/changelog b/debian/changelog
index adcedd4..c45af65 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+libgroove (4.3.0-3) unstable; urgency=medium
+
+ * Use
Hi all,
On 26 December 2016 at 05:08, Petter Reinholdtsen wrote:
>
> [Felipe Sateler]
> > This suggests there is some wrong thread usage. Andrew, any idea what
> > could this be?
>
> There are several bugs that can trigger this. For example trying to unlock an
&
Hi,
On 26 December 2016 at 05:08, Petter Reinholdtsen wrote:
> [Felipe Sateler]
>> This suggests there is some wrong thread usage. Andrew, any idea what
>> could this be?
>
> There are several bugs that can trigger this. For example trying to unlock an
> non-locked lock.
1 - 100 of 318 matches
Mail list logo
