[Bug 262423] Re: [intrepid] Resume from suspend does not work in 2.6.27-1
A note: I managed to resume/suspend successfully (maybe 6 times till now). This is after disabling bluetooth in BIOS. I am not sure which kernel module is the culprit... -- [intrepid] Resume from suspend does not work in 2.6.27-1 https://bugs.launchpad.net/bugs/262423 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 284509] [NEW] /usr/lib/libGL.so.1.2 diversion is not good for switchable graphics
Public bug reported: I have a Thinkpad T400 with switchable graphics hardware (both integrated Intel, and discrete ATi). Although xorg does not support on-the-fly switching, ideally it would be great that after a few rmmod/modprobes and a xorg.conf swap, I would be able to choose between the two chips for the next X session. With the libGL.so.1.2 diversion that exists in fglrx-driver, it makes it a bit harder to have libgl1-mesa-glx and fglrx-driver to co-exist. Simply swapping chipsets does not work since the fglrx libGL is incompatable. Switchable graphics will become more and more popular, and Thinkpads are already popular Linux machines. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- /usr/lib/libGL.so.1.2 diversion is not good for switchable graphics https://bugs.launchpad.net/bugs/284509 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258038] Re: Look into feasibility of using an alternatives system rather than diversions
Might I add the use-cae of switchable graphics. I have a Thinkpad T400 with both Intel and Radeon chipsets. An alternatives system will allow easy alternating between chipsets. -- Look into feasibility of using an alternatives system rather than diversions https://bugs.launchpad.net/bugs/258038 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262423] Re: [intrepid] Resume from suspend does not work in 2.6.27-1
Hi, I am still experiencing this too. I have a Lenovo Thinkpad T400. Linux sparky 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux I would try to boot into a 2.6.26 kernel, but it seems like those packages disappeared with some dist-upgrade, and now I can't find them online either. -- [intrepid] Resume from suspend does not work in 2.6.27-1 https://bugs.launchpad.net/bugs/262423 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263114] Re: System crash when starting X with Cantiga
I just downgraded to the intrepid (2:2.4.1-1ubuntu2) version and I this issue disappeared. I also did a quick diff, and yeah, upstream 2.4.2 is identical to 2.4.1-1ubuntu2. My two thoughts about this crasher are: 1. Was it something in 2.4.1-1ubuntu1? 2. Is their some other package that is clobbering files in this one? Maybe by installing video-intel I clobbered it back to norm. -- System crash when starting X with Cantiga https://bugs.launchpad.net/bugs/263114 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263114] Re: System crash when starting X with Cantiga
I just rebuilt xserver-xorg-video-intel with upstream version 2.4.2. And it solved this issue, so I guess it is fixed in upstream. I think that once this update lands in intrepid, this issue will resolve itself. -- System crash when starting X with Cantiga https://bugs.launchpad.net/bugs/263114 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263114] [NEW] System crash when starting X with Cantiga
Public bug reported: Binary package hint: xserver-xorg-video-intel I have a Lenovo T400 which has Cantiga. It has switchable graphics, but in the BIOS I disabled the discrete (radeonhd) card. When the X server starts the system locks up after it appears that some mode switching happened on the screen. I couldn't find any useful log information. X and Compiz work fine in Hardy, but Intrepid gives this awful crash. Here are versions of packages I have installed: xorg 1:7.4~1ubuntu1 xserver-xorg 1:7.4~1ubuntu1 xserver-xorg-core 2:1.4.99.906-2ubuntu2 xserver-xorg-video-intel 2:2.4.1-1ubuntu1 Kernel: Linux sparky 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux A ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- System crash when starting X with Cantiga https://bugs.launchpad.net/bugs/263114 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263114] Re: System crash when starting X with Cantiga
** Attachment added: A bunch of random logs http://launchpadlibrarian.net/17180770/logs.tar.gz -- System crash when starting X with Cantiga https://bugs.launchpad.net/bugs/263114 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207312] Re: PulseAudio Sound Server: Failed to connect: Connection refused
It seems like my woes were from speech dispatcher blocking the sound device before pulseaudio could get to it. See bug 213755. By starting pulseaudio system wide it seems that you temporarily circumvented this by starting pulseaudio before speech dispatcher. -- PulseAudio Sound Server: Failed to connect: Connection refused https://bugs.launchpad.net/bugs/207312 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213755] [NEW] speech dispatcher blocks audio device
Public bug reported: Binary package hint: speech-dispatcher It seems like speech dispatcher is using alsa with the default espeak module. Per-session pulseaudio refuses to initialize the main sound device because speech-dispatcher opens a handle to it during bootup. Shouldn't the EspeakAudioOutputMethod be pulse? ** Affects: speech-dispatcher (Ubuntu) Importance: Undecided Status: New -- speech dispatcher blocks audio device https://bugs.launchpad.net/bugs/213755 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207312] Re: PulseAudio Sound Server: Failed to connect: Connection refused
Enabling pulseaudio system-wide is not the right solution. I'm stumped as to what is causing this. But I can't seem to get pulseaudio working with the hal autodetect module. ** Changed in: pulseaudio (Ubuntu) Status: Invalid = New -- PulseAudio Sound Server: Failed to connect: Connection refused https://bugs.launchpad.net/bugs/207312 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199688] [NEW] Crash on start with X11 driver
Public bug reported: Binary package hint: brltty When brltty is started with the XW driver it immediately crashes. This happens only in Compiz. This is on Hardy, with brltty 3.9-5ubuntu2. brltty -b xw -n BRLTTY 3.9 rev UNKNOWN [http://mielke.cc/brltty/] brltty: BrlAPI Server: release 0.5.1 brltty: removing stale local socket lock error 1: Operation not permitted. brltty: Error while initializing socket 0 brltty: Console open error 13: Permission denied. brltty: XWindow Braille Driver: version 0.1, 2004 brltty: Console open error 13: Permission denied. X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 28 (X_GrabButton) Serial number of failed request: 154 Current serial number in output stream: 600 Locking assertion failure. Backtrace: #0 /usr/lib/libxcb-xlib.so.0 [0xb7a20767] #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb7a2081e] #2 /usr/lib/libX11.so.6 [0xb7a8d5f8] #3 /usr/lib/libX11.so.6(XClearArea+0x25) [0xb7a630f5] #4 /usr/lib/libXt.so.6(XtSetValues+0x859) [0xb7b9c159] #5 /usr/lib/libXt.so.6(XtVaSetValues+0xb2) [0xb7bae972] #6 /lib/brltty/libbrlttybxw.so [0xb7c23511] #7 brltty(writeBrailleBuffer+0x22) [0x806f562] #8 brltty(message+0x151) [0x8053061] #9 brltty [0x80588a7] #10 /lib/tls/i686/cmov/libc.so.6(exit+0xd4) [0xb7d9af34] #11 /usr/lib/libX11.so.6 [0xb7a8671e] #12 /usr/lib/libX11.so.6(_XError+0xfe) [0xb7a8681e] #13 /usr/lib/libX11.so.6 [0xb7a8df3c] #14 /usr/lib/libX11.so.6(_XEventsQueued+0x4f) [0xb7a8e7ff] #15 /usr/lib/libX11.so.6(XEventsQueued+0x6f) [0xb7a77b2f] #16 /usr/lib/libXt.so.6(XtAppPending+0x65) [0xb7b90865] #17 /lib/brltty/libbrlttybxw.so [0xb7c244c1] #18 brltty(readBrailleCommand+0x21) [0x806fb71] #19 brltty(readCommand+0x1a) [0x8058dca] brltty: xcb_xlib.c:73: xcb_xlib_lock: Assertion `!c-xlib.lock' failed. Aborted (core dumped) ** Affects: brltty (Ubuntu) Importance: Undecided Status: New -- Crash on start with X11 driver https://bugs.launchpad.net/bugs/199688 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
Wow Jamie, thanks for all that. I don't understand 3/4 of it, but at least i got rid of that artifact :) -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
And Peter. here is the registry dump I made with your patch. Cheers! ** Attachment added: reg_dump.txt http://launchpadlibrarian.net/10218673/reg_dump.txt -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
Here is my X log after a suspend/resume, with the debug option enabled. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/10218671/Xorg.0.log -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
I suspect that the reason the corrupt row is disappearing is because DRI is disabled when the server reverts to software rendering. This is something we already knew: disabling DRI makes the screen artifact go away. -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134464] Re: in dual head config a row of pixels is drawn on the wrong monitor
*** This bug is a duplicate of bug 91966 *** https://bugs.launchpad.net/bugs/91966 I mentioned in a post on bug #91966 that this is the changeset that made all the trouble: a4f1a7872f6f959bb4bc6568face710bee3589de It's from the git repo pulled from: git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel I'd also say that the changeset above deals with a lot of memory stuff, it's hard to understand. -- in dual head config a row of pixels is drawn on the wrong monitor https://bugs.launchpad.net/bugs/134464 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume, part row of pixels in error (945GM)
Unlike Juha, disabling DRI, and then doing suspend/resume actually helps. All of your suggestions Peter, and the package you pointed at don't help. -- screen artifacts after resume, part row of pixels in error (945GM) https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume with i810 driver
I'm updated to final Gutsy, but I also tried the final live CD as you suggested. No luck. Attached is the log, as per your request. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/10150963/Xorg.0.log -- screen artifacts after resume with i810 driver https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume with i810 driver
Oh, I forgot to mention: When I disable DRI I don't get any artifacts. I'll attach a log for that too. ** Attachment added: Xorg.0.log http://launchpadlibrarian.net/10151170/Xorg.0.log -- screen artifacts after resume with i810 driver https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume with i810 driver
I pinpointed the changeset in which this happens on the xorg git repo. This is the fd.o bug I opened: https://bugs.freedesktop.org/show_bug.cgi?id=12667 -- screen artifacts after resume with i810 driver https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91966] Re: screen artifacts after resume with i810 driver
Yes. I forgot all about it in Feisty since I was using my own built xserver-xorg-video-i810 version 1.9.93, since the bundled i810 driver (1.7.*) had this bug. Now in Gutsy I am using the xserver-xorg-video-intel driver, and it gives me exactly the same artifact (see screenshot). ** Attachment added: screenshot of artifacts http://launchpadlibrarian.net/9690143/Screenshot.png -- screen artifacts after resume with i810 driver https://bugs.launchpad.net/bugs/91966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62163] Re: variables from the session are not defined
Just another thought, Since dbus is not started via gnome-session, any process that dbus launches is not accessible. This is because gnome-session looks in gconf to see if accessibility is enabled and sets GTK_MODULES accordingly before it launches dbus. As you guys mentioned, gnome-session will not launch dbus if it has already been started. A good example is notification-daemon, any notification bubble that it pops up is completely inaccessible, so a screen reader user in Edgy will never find out that her battery is about to run out, before it is too late. I am not very familiar with Ubuntu conduct in these cases, but is there a chance a fix could be pushed to Edgy users? Cheers! -- variables from the session are not defined https://bugs.launchpad.net/bugs/62163 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63890] Re: Ubuntu has nearly the same logo as the Microsoft Alumni Network
Maybe we are not approaching this right. Maybe MSA _is_ Ubuntu... -- Ubuntu has nearly the same logo as the Microsoft Alumni Network https://launchpad.net/bugs/63890 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54214] Fatal Python error when using the example pyfs.py
Public bug reported: in /usr/share/doc/python2.4-gnome2/examples/vfs/pygvfsmethod/: cp pyfs.conf ~/.gnome2/vfs/modules/ zcat pyfs.py.gz /tmp/pyfs.py export PYTHONPATH=/tmp:$PYTHONPATH mkdir /tmp/testing export TMPDIR=/tmp/testing nautilus --no-desktop pyfs:/// The error I get is: Fatal Python error: could not import gnomevfs ** Affects: python-gnome2 (Ubuntu) Importance: Untriaged Status: Unconfirmed ** Description changed: in /usr/share/doc/python2.4-gnome2/examples/vfs/pygvfsmethod/: cp pyfs.conf ~/.gnome2/vfs/modules/ - cp pyfs.py.gz /tmp + zcat pyfs.py.gz /tmp/pyfs.py export PYTHONPATH=/tmp:$PYTHONPATH mkdir /tmp/testing export TMPDIR=/tmp/testing nautilus --no-desktop pyfs:/// The error I get is: Fatal Python error: could not import gnomevfs -- Fatal Python error when using the example pyfs.py https://launchpad.net/bugs/54214 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54214] Re: Fatal Python error when using the example pyfs.py
Dapper, sorry. -- Fatal Python error when using the example pyfs.py https://launchpad.net/bugs/54214 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
