Sid's Rhythmbox fails to edit ID3 tags on files that have no tag at all.
This is, in my opinion, release critical for Squeeze.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=628254
Upstream fix:
http://git.gnome.org/browse/rhythmbox/commit/?id=f9cc88274dd008ce153b8fd5448e6d99e602cf6d
The above upstream fix, made against rhythmbox 0.13.x, applies well also
on top of 0.12.8 (attached as a patch, needs -p1 from
Can anybody reproduce that on 0.12.8-2?
I think this one can be closed as invalid.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Does it still happen with 0.12.8-2?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Can you reproduce in 0.12.8-2? I think it's solved, I could easily edit
tags on an .m4a file.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: pulseaudio
Version: 0.9.21-3+b1
Severity: important
This problem was reported several times as an application bug (#558343,
#564864), but it's in fact a Pulseaudio bug, which was already found
fixed in upstream, 0.9.22:
- ticket: http://pulseaudio.org/ticket/752
- patch:
This bug originates in pulseaudio bug #606271
Reported and fixed in upstream (Pulseaudio 0.9.22):
http://pulseaudio.org/ticket/752
This bug originates in pulseaudio bug #606271
Reported and fixed in upstream (Pulseaudio 0.9.22):
http://pulseaudio.org/ticket/752
I cannot reproduce on 0.12.8-2 on my setup.
I've enabled crossfade of 2 seconds, changing songs (both manually and
automatic) works well, time bar seems accurate.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I've checked both the 'Portable Audio Player Source' and 'Library
Source' contents, and both don't have the inaccuracies you mentioned.
They generally look OK to me.
I believe that this bug could be closed now.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Should be merged with #422001 ,
and linked with upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=362876
All relate to the same issue of APE tag eclipsing ID3 tag.
Oren
Hi,
Can you reproduce that on 0.12.8-2 ?
Simply adding a new playlist behaves normally for me..
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
version: 2.30.0-2
I experience the same problem, once in a while, even with the latest sid.
I'm not sure how to reproduce it. usually password prompt shows up well.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Seems related to upstream
https://bugzilla.gnome.org/show_bug.cgi?id=609727
https://bugzilla.gnome.org/show_bug.cgi?id=619954
In any case - the problem exists in upstream 2.30.x, but on the master
branch they simply removed this feature completely (commit
be471c1097980) on May 2010.
I believe
This bug was tagged as FIXED in upstream, iirc because this was fixed in
libgpod, here:
http://gtkpod.git.sourceforge.net/git/gitweb.cgi?p=gtkpod/libgpod;a=commit;h=39ef6f5afebdf80790cce791770fc489fb495ea9
I confirmed that the above libgpod patch is applied in Sid, 0.7.93-0.3
or before.
So
Funny enough, even though the patch was still not applied to rhythmbox
and I'm using the same version as the bug was reported in (0.12.8-2), -
it works for me.
I can click the user/password box.
Can you still reproduce it?
Maybe it was resolved by a fix to another package (e.g. pygtk/gtk)?
Can you still reproduce on 0.12.8-2?
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
Could you try to provide more info:
- Does it still happen on an up-to-date testing/sid? (maybe recent
upgrades to audio driver/pulseaudio fixed that)
- Does rhythmbox print anything interesting when the bad sound happens?
- More info that could help us to reproduce the problem, as it never
Please ignore my latest comment about 'more info needed', unfortunately
it's related to another bug, my bad.
(if maintainers can delete it, even better)
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
Could you try to provide more info:
- Does it still happen on an up-to-date testing/sid? (maybe recent
upgrades to audio driver/pulseaudio fixed that)
- Does rhythmbox print anything interesting when the bad sound happens?
- More info that could help us to reproduce the problem, as it never
Hi,
Could you please make such a FLAC file available on some URL, to ease
the reproducing?
10x
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi,
I've researched it a bit, and posted a potential patch for upstream, I'm
still not confident enough about it, so let's see what upstream say/do.
http://mail.gnome.org/archives/rhythmbox-devel/2011-January/msg00060.html
Oren
--
To UNSUBSCRIBE, email to
Package: network-manager-kde
Version: 1:0.7~~svn941706-2
Severity: grave
Since the recent upgrade of network-manager package and libraries,
knetworkmanager cannot connect to a wireless network anymore - when I click on
a wifi network it simply does nothing.
The gnome applet, on the other hand,
Package: stellarium
Version: 0.10.2-1
Severity: important
That's a weird one: clicking on a drop-down list in the Location dialog (F6 key)
causes a complete freeze of my computer (ctrl+alt+f1 stops working, so does a
short click on the power button). Maybe it happens with other drop-down lists as
Package: insserv
Version: 1.12.0-14
Severity: important
Tags: patch
The rpcbind service is an alternative to the portmap service.
There are many services that depend on $portmap, e.g. nfs-common,
nfs-kernel-server.
Thus, I believe that we should add rpcbind as a portmap alternative.
As far as
open a related bug to rpcbind, to add its own file to insserv.conf.d.
Oren
On Saturday 09 January 2010 22:54:08 Petter Reinholdtsen wrote:
[Oren Held]
As far as I understand this cannot be done in /etc/insserv.d/,
because $portmap is already defined in /etc/insserv.conf.
I thought
WFM
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: rpcbind
Version: 0.2.0-4
Severity: important
As the rpc services started in nfs-common and nfs-kernel-server init scripts do
NOT have a Required-Start setting that relates to rpcbind, insserv decides to
start rpcbind AFTER the scripts that logically require it. Here's my setup:
On Tuesday 02 February 2010 08:48:06 you wrote:
On 29.01.2010 11:22, Oren Held wrote:
Package: network-manager-kde
Version: 1:0.7~~svn941706-2
Severity: grave
Since the recent upgrade of network-manager package and libraries,
knetworkmanager cannot connect to a wireless network
1. Running grub-probe --device /dev/mapper/myvg-myvol fails (that's THE reason
for grub-pc postinstall to fail), while grub-probe --device /dev/myvg/myvol
succeeds (returns ext2). I wouldn't expect different behavior on a symlink
device..
2. The failure shows up in disk/lvm.c grub_lvm_read().
This revision seems to fix the bug, so I guess that simply upgrading the grub
package to latest version would solve this issue; but I even tried to simply
apply this patch, and it worked.
$ bzr diff -r2151..2152
=== modified file 'ChangeLog'
--- ChangeLog
Currently (1.2.1-1), nfs-common depends on portmap | rpcbind; it should be
changed to rpcbind only.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This is looks like a dup of 562757
(although this is the earlier-submitted bug, the discussion has started on
#562757)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
See 544567.
rpcinfo-0.2.0-2 fixes the libc conflict thing.
Yet, THIS bug is caused because the nfs-common package does not require
rpcbind.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sorry, in my previous comment s/rpcinfo/rpcbind/
On Tuesday 29 December 2009 16:44:52 Oren Held wrote:
See 544567.
rpcinfo-0.2.0-2 fixes the libc conflict thing.
Yet, THIS bug is caused because the nfs-common package does not require
rpcbind.
Oren
--
To UNSUBSCRIBE, email
The rpcbind package doesn't even contain an init script, weird.
Steven, Tony: when you run (as root) rpcbind, does it fix it?
Running rpcbindinfo should state if rpcbind is running or not.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Hi,
I have made a simple init script for rpcbind - attached.
Con: it does not use PIDFILEs, because rpcbind doesn't create any.
Oren
rpcbind
Description: application/shellscript
I'll try to sum up the problems and solutions reported so far. I'll stress
that these problems currently render NFS (v2, v3, v4) non-functioning on
latest Debian sid.
1. [nfs-common pkg] needs rpcbind-ONLY dependency: we have to remove portmap
dependency. (#562757)
2. [rpcbind pkg] rpcbind
Hi,
In a private mail, Brian Denheyer raised a dependency problem, which made me
realize that nfs-common, nfs-kernel-server both currently require $portmap.
I guess that this means that:
- /etc/insserv.conf needs to add rpcbind as portmap
- /etc/init.d/rpcbind needs a Provides: portmap line.
Is attached.
1. stop() used to kill all processes named 'rpcbind' - which includes the init
script itself. adding --exec /usr/sbin/rpcbind fixes that.
2. Removes an embarrassing remnant from pulseaudio's init script.
==
--- rpcbind.prev2010-01-04
It seems to me that as long as we have '$portmap portmap' in
/etc/insserv.conf, this trick will not work. Changing this line to '$portmap
+portmap' (plus sign) seems to fix this, cuz 'portmap' is now not the only
required service for the $portmap facility.
Oren
--
To UNSUBSCRIBE, email to
I'm experiencing the same with linux-image-2.6.32-3-amd64 : 2.6.32-9.
Rebooting back to the good linux-image-2.6.32-1-amd64 makes it work.
I think this bug should have higher severity priority.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Maybe it has to do with this issue:
http://bugzilla.kernel.org/show_bug.cgi?id=15424 (contains a link to the
patch inside)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
apt-get source pulseaudio (got v0.9.21_1.2)
./configure; make; make install
and this version that I built seems to work well, as opposed to the same
binary version downloaded from the official Debian repo.
Maybe something in the build process is broken?
Oren
--
To UNSUBSCRIBE, email to
Running a Python profiler (cProfile), it told that all the CPU usage was
done by the gtk.main() function call.
So it doesn't tell much, yet it means that the bug might not be in
Guake's code.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
On 09/03/2010 12:13 AM, Joachim Breitner wrote:
Hi Oren,
I’m looking at this bug report, because it is in the list of release
critical bug. Do you really think the bug is serious (and not just
important). Rephrased: If this bug is not fixed, is Debian better with
the buggy guake, or should
I confirm.
CPU usage has dropped dramatically, probably by an update (but not a
guake update) from the recent days.
Good news, I think this bug should be closed now.
Oren
On 09/17/2010 11:47 AM, Roland Mas wrote:
Hi,
Just wanted to notice that I used to see the behaviour mentioned in
Package: lsb
Version: 3.2-22
Severity: normal
A quick workaround was adding /var/lib/python-support/python2.5/ to the
PYTHONPATH.
Without the workaround, I couldn't import other things from this path as well,
such as 'reportbug' module. So I assume that lsb is just a symptom, and the bug
is
Package: usplash-theme-debian
Version: 4
Severity: normal
I believe that this package should depend on usplash. It doesn't, atm.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-1-amd64
python-support 1.0 which was just uploaded to unstable fixed this, by creating
the /usr/lib/pymodules directory.
http://packages.debian.org/changelogs/pool/main/p/python-support/python-support_1.0.0/changelog
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
I'm using now linux-image-2.6.32-5-amd64 (v2.6.32-15), and I do not
experience this bug anymore
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: guake
Version: 0.4.2-1
Severity: serious
Recently in my Debian unstable, guake became noticably slower. The
typing actually feels slower (keyboard latency), and 'top' reports that
Python uses ~6% of my dual core (constantly), Xorg about 32%. That adds
up to almost one whole core.
Why is
BTW our Ubuntu friends have the same thing:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/427822
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Unstable 64bit. Unlike the prev. comment, I DID upgrade to dependency-based-
boot, so it's irrelevant for this bug.
It seems that the last check time is kept in the local-time timezone, but the
is-last-check-in-the-future time is kept in UTC.
i.e. it tells me something like Time now is 07:30,
Package: cryptsetup
Version: 2:1.3.0-2
Severity: normal
Tags: sid
Since the upgrade to cryptsetup 1.3.0, the cryptdisks init script fails to
start my dm-crypt encrypted device.
Researching it deeper, I've found that the following command (which the init
script uses) doesn't behave as it used
I've tried downgrading to 1.2.0 (both cryptsetup libcryptsetup1 packages),
and the behavior goes back to normal (passphrase works from stdin pipe).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: openssh-client
Version: 1:5.8p1-2
Severity: serious
Since the last update to 5.8p1, I can no more login to any ssh server.
- I think it's tightly related to Ubuntu's
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/708493
- Problem gets solved when downgrading back to 5.5p6
Here's
I believe it's an issue in upstream, as it also reproduces with vanilla
(non-debian) tgz I compiled on the Debian machine, and was also reported on
Ubuntu and Archlinux.
It apparently began with v5.7p1.
See thread on openssh-unix-dev list and ubuntu bug
Hi,
I've reported this bug to upstream, sent a not-so-good-patch, and the
maintainer committed a better fix to git master.
http://mail.gnome.org/archives/seahorse-list/2011-July/msg1.html
http://git.gnome.org/browse/seahorse/commit/?id=66885bc1176288edfd4ff7a93420fedddf846c37
Attaching the
I think this problem is related (or even a dup of) #568877
if /etc/initramfs-tools/conf.d/resume file contains /dev/mapper/vg-lv,
after running dpkg-reconfigure uswsusp, it should get fixed.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Hi,
I confirm the fix. Works like a charm. Thanks.
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Confirming the fix.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I experience a similar behavior, and luckily syslog has a relatively useful
error message:
'gnome-shell[8568]: segfault at 48 ip b6cf7981 sp badacf00 error 4 in
libcogl.so.5.0.0[b6cd4000+77000]'
Now quick googling revealed its related to a libcogl bug as reported herE:
Confirming on 0.9.2.0-1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Daniel,
I too, use GNOME's fallback mode (aka 'gnome classic') with an old video card,
and fail to reproduce it. (I think the 'unreproducible' tag means that we don't
yet know how to reproduce the problem on *other* environments, therefore the
tag is justified)
Can you please kill nm-applet
Daniel,
Can you please kill nm-applet and run it from the console, and paste its
output? (hopefully we'll see a meaningful error)
Thanks
Oren
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
66 matches
Mail list logo
