I too still see this bug in 8.04.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
After digging out this laptop and testing the intrepid pre-release on
it, I can confirm that the problem is fixed for me.
--
ThinkPad R40e Keyboard/Mouse/Trackpoint regularly unresponsive on Feisty Release
https://bugs.launchpad.net/bugs/107859
You received this bug notification because you are a
Public bug reported:
I have been getting a few segfaults with bzr when used in conjunction
with svn, but until now didn't have an easy way to reproduce.
I decided to run the self test, and see if it passed, and it segfaulted:
$ bzr selftest svn
testing: /usr/bin/bzr
/usr/lib/python2.5/site-pa
$ bzr selftest -s bp.svn -v
bzr: ERROR: no such option: -s
trying something else that may be helpful(?):
$ bzr selftest svn -v
testing: /usr/bin/bzr
/usr/lib/python2.5/site-packages/bzrlib (1.3.1 python2.5.2.final.0)
running 777 tests...
bzrlib.plugins.svn.tests.test_branch.BranchFormatTests.
Okay, trying a newer version seems to have made the segfault go away for
me. (although I haven't exhaustively tested my real-life workloads yet)
So I guess if my version is not supported any more, then that will have
to do and thanks very much for your help everyone.
However, can any of the ubunt
The package manager is just one part of the problem, and it's not even
clear that the problem as a whole can be reasonably solved.
Imagine for a moment that all distros used .deb as their package format.
That is a small step in the right direction (leaving aside the relative
merits of .deb vs othe
I see this same problem.
The question is, what is looking for /dev/dm-0 and why? That will never
exist, will it?
--
"special device /dev/dm-0 does not exist" when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ub
Public bug reported:
Binary package hint: xorg
compiz runs fine initially but eventually reports:
drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command
stream. See dmesg for more info.
and then exits.
dmesg reveals:
[ 1217.412221] [drm:radeon_cs_ioctl] *ERROR* Failed to parse re
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/42369474/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/42369475/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42369476/Dependencies.txt
** A
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
compiz exits with radeon error
https://bugs.launchpad.net/bugs/550850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
This is still marked as incomplete. Can anyone let me know what else is
needed before it is "complete" again? I don't know what other
information is needed.
--
compiz exits with radeon error
https://bugs.launchpad.net/bugs/550850
You received this bug notification because you are a member of Ub
Reproducing this with drm.debug=1 produced more output. Here is what I
hope is the relevant part from dmesg:
Mar 31 22:38:46 martin-laptop kernel: [ 851.833384] [drm:drm_ioctl], pid=829,
cmd=0xc0086464, nr=0x64, dev 0xe200, auth=1
Mar 31 22:38:46 martin-laptop kernel: [ 851.836186] [drm:drm_io
I decided to run strace on compiz, and perhaps this is a clue. Here is
an excerpt from the strace output just before the error:
8346 ioctl(5, 0xc010640b, 0xbfe94660) = 0
8346 ioctl(5, 0xc00c6469, 0xbfe94684) = 0
8346 ioctl(5, 0xc010640b, 0xbfe94660) = 0
8346 ioctl(5, 0xc00c6469, 0xbfe94684
Running compiz from the terminal is what led to the message:
drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command
stream. See dmesg for more info.
.. that I previously mentioned. I have since tried again with "compiz
--debug" but no extra information is revealed.
I am trying to f
After reading a similar report in Debian ( http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=542550 ) It seems that upgrading to 2.2.x to match
the version in Debian testing would fix this.
Also, maven is reportedly very picky about the versions it depend upon,
so perhaps it should specify exact v
"The upstream mainline kernel bug is a known issue -- still open
upstream."
Do you have a refernece to an upstream bug report for this where is it
being tracked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
16 matches
Mail list logo
