Thanks for the heads up - I will definitely avoid 15.10 until this is
fixed :).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/173350
Title:
Caps lock LED changes
Since this bug has come to my attention again, I should note that the
behavior that Jean-Paul described in comment 15 is still behaving that
way on oneiric. trial -u
twisted.internet.test.test_tcp.TCPClientTestsBuilder_Glib2Reactor.test_addresses
still bombs out on the 1021st run. I guess we
I am seeing this again in Lucid, with the virtual key LED on the
Logitech DiNovo.
The workaround of using xmodmap still works, though.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a
Correction: the workaround described above *does not* work any more. I
can't figure out a way to prevent my keyboard from beeping constantly.
This is really annoying :(.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this
So, after trying every combination of options I could think of to no
effect, as well as several reboots, I gave up. However, after rebooting
the *keyboard itself*, the beeps are gone! So it's possible that this
is a firmware bug in the keyboard and not in ubuntu. I will update if I
discover
I have the same symptoms as Brandon Bell.
--
[lucid] battery status not detected/shown until /proc entry viewed
https://bugs.launchpad.net/bugs/513716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
Nicola, you seem to be right. From what I can tell, the offending code
is very nearly copy/pasted into pygobject in
pygmainloop.c:pyg_signal_watch_prepare. As far as I can see, pygtk
should be invoking this code, not duplicating it.
** Also affects: pygobject
Importance: Undecided
Martin,
Thanks very much for your explanation. That's a slightly convoluted
path to follow; it would be very helpful if Launchpad had a more direct
feature that allowed us to see the relationship.
However, until it does, your explanation is very useful and it will help
me understand future
Is there any way to get from the comment above to a changeset or
revision number or release which fixed the bug? Or even what the
problem was actually determined to be? The discussion above is all very
vague. I am especially confused because this went from new to fix
released without an
Public bug reported:
Binary package hint: deskbar-applet
I love the fact that I can use deskbar as a library, because there's
some very useful functionality in there. However:
$ python
Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help,
** Also affects: deskbar-applet
Importance: Undecided
Status: New
--
import deskbar causes a chdir to ~
https://bugs.launchpad.net/bugs/386612
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for deskbar-applet.
--
Public bug reported:
Here is a Python script, using pygtk, which demonstrates the problem.
from gtk import main, main_quit
from gobject import threads_init, timeout_add, source_remove
import sys
def test(iterations, use_threads):
if use_threads:
threads_init()
tick = 0
while
** Also affects: pygtk (Ubuntu)
Importance: Undecided
Status: New
--
gtk_main leaks a file descriptor every time the main loop is run if threads
have been initialized
https://bugs.launchpad.net/bugs/363245
You received this bug notification because you are a member of Ubuntu
Desktop
Usually Python programs are pretty good approximations of their C
counterparts, but in this case the bug is in PyGTK. It's on line 1098
of gtk.override from the pygtk package.
Actually the bug has been in PyGTK for a long time. It was in the
version distributed in hardy. The reason it's
Filed the bug upstream as
http://bugzilla.gnome.org/show_bug.cgi?id=579406
** Bug watch added: GNOME Bug Tracker #579406
http://bugzilla.gnome.org/show_bug.cgi?id=579406
** Also affects: pygtk via
http://bugzilla.gnome.org/show_bug.cgi?id=579406
Importance: Unknown
Status:
Robin: the bug is not in pulseaudio. It's in the kernel. Given that
pulse doesn't ship any kernel drivers, there's nothing that it should
conceivably be able to do to block kill -9.
dreamsare4living seems to indicate that the bug is still present in
intrepid.
--
Totem is 'uninterruptible'
Is there any planned fix for hardy?
--
Totem-gstreamer produces artifacts during playback
https://bugs.launchpad.net/bugs/217196
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Can someone from the kernel team please indicate what information would
be useful in investigating this problem? It still occurs for me
periodically, and I would be more than happy to spend some effort
gathering diagnostics when it does.
--
Totem is 'uninterruptible'
[EMAIL PROTECTED]:~$ uname -a
Linux suijin 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686
GNU/Linux
As far as I'm aware, this is the latest Hardy kernel, not an updated
Intrepid kernel.
Good luck reproducing the bug, I have not been able to find a reliable
way to do so.
--
Totem
*** This bug is a duplicate of bug 173350 ***
https://bugs.launchpad.net/bugs/173350
** This bug has been marked a duplicate of bug 173350
Caps lock LED changes state even when caps lock is mapped to ctrl
--
CapsLock LED still lights after change to CTRL key
Still happening, updated to the latest everything in Hardy.
This time I made a tarball of /proc/pid of the affected process; I can
upload bits of that if it would be helpful to anyone.
I checked in /var/log/kern.log and discovered that a totem segfault
immediately preceded the unkillable
As Thomas Paris reports, this probably isn't caused by fuse, since he
had it occur in a situation where fuse was not being used.
** Changed in: fuse (Ubuntu)
Status: New = Invalid
--
Totem is 'uninterruptible'
https://bugs.launchpad.net/bugs/213053
You received this bug notification
Thanks for the pointer, Kjell. Filed against 'linux' now.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Totem is 'uninterruptible'
https://bugs.launchpad.net/bugs/213053
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Kjell, can you suggest a better package for it to be filed against?
Since this bug manifests in so many different applications, it seems to
clearly be in the kernel.
--
Totem is 'uninterruptible'
https://bugs.launchpad.net/bugs/213053
You received this bug notification because you are a member
FMaz, Christian -
Are you running the latest Hardy kernel, i.e. 2.6.24-18? I have not
managed to reproduce this issue since I upgraded. It's intermittent
though, so I'm not sure it's actually fixed...
--
Totem is 'uninterruptible'
https://bugs.launchpad.net/bugs/213053
You received this bug
Sadly I can't remove my mistaken report against Fuse or the probably-
wrong report against Totem, but the additional report of apt-get
becoming unkillable suggests that this is clearly a kernel bug (as my
original duplicate bug said).
Can anyone kernel-savvy give us some help with diagnosing or
*** This bug is a duplicate of bug 213053 ***
https://bugs.launchpad.net/bugs/213053
** This bug has been marked a duplicate of bug 213053
Totem is 'uninterruptible'
--
completely unkillable process eating 100% CPU
https://bugs.launchpad.net/bugs/230993
You received this bug notification
Interesting. I also experienced this issue, using sshfs - another fuse
filesystem.
Anyone here experiencing this *not* using a fuse filesystem?
** Also affects: fuse (Ubuntu)
Importance: Undecided
Status: New
--
Totem is 'uninterruptible'
https://bugs.launchpad.net/bugs/213053
You
The program doesn't crash, and the behavior is not reproducible when
running under strace - or gdb, for that matter. Is there any other
debugging information that I can provide?
--
[gutsy] deskbar applet locks up during first search after startup
https://bugs.launchpad.net/bugs/150559
You
Public bug reported:
When I first invoke the deskbar applet after I've logged in, I type a
few characters and the window becomes unresponsive.
However, it's an odd kind of unresponsive because the window manager
(both compiz and metacity) don't notice that it's dead, and don't offer
me the
*** This bug is a duplicate of bug 90258 ***
https://bugs.launchpad.net/bugs/90258
Sorry for the delay. After reading the information on bug #90258, I
discovered that the symptoms were exactly the same; I've marked this as
a duplicate. Thank you for the feedback!
** This bug has been
Public bug reported:
Binary package hint: gnome-applets
I have replicated this on 3 machines with different fstab and disk
configurations, all running Ubuntu Edgy 7.04.
The disk mounter applet shows my partitions as expected when I first log
in.
If I log out, then log back in, as any user, a
Public bug reported:
This python program:
import sys
sys.stdout.write(\x1b[4h )
will reliably crash any VTE-based terminal.
This bug is new in Feisty. Neither edgy nor dapper have the problem.
** Affects: vte (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
crash on IRM
more information - this was introduced as of
1:0.16.0svn20070403-0ubuntu1 - downgrading to 0.16.0-0ubuntu4 fixes the
issue.
--
crash on IRM escape code
https://bugs.launchpad.net/bugs/103095
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
*** This bug is a duplicate of bug 70535 ***
My crash was also in the middle of copying to a NAS.
--
[apport] nautilus crashed with signal 25 in __kernel_vsyscall()
https://launchpad.net/bugs/90034
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
35 matches
Mail list logo
