[Bug 296127] [NEW] gdmgreeter exits on RandR v1.1
Public bug reported: Binary package hint: gdm 1) $ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 2) $ apt-cache policy gdm gdm: Installed: 2.20.7-0ubuntu1.1 Candidate: 2.20.7-0ubuntu1.1 Version table: *** 2.20.7-0ubuntu1.1 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 2.20.5-0ubuntu3 0 500 http://fi.archive.ubuntu.com hardy/main Packages 3) What you expected to happen - enabled remote logins using gdmsetup, no other changes. (seems to default to gdmgreeter) (NB: This might make your remote session vulnerable to attacks, don't do it if you don't understand the consequences) - expected to be able login from a remote Xserver running XDMCP 4) What happened instead Login screen was not displayed on remote Xserver My debugging gave the following explanation When talking to an X server supporting RandR v1.1 (instead of the current v1.2) gdmgreeter exits before displaying anything. There is no error message to the user. With gdm [debug] Enable=True only 2 lines are found in syslog, which might be related to the problem gdm[6110]: DEBUG: close_if_needed: Got G_IO_HUP on 9 gdm[6110]: DEBUG: close_if_needed: Got error on 9 However, these lines didn't tell me anything. Using strace I found that gdmgreeter seems to be culprit: write(2, The program \'gdmgreeter\' receive..., 583) = 583 However fd 2 seems to be /dev/null and I didn't find any information how to turn on logging. open(/dev/null, O_RDWR) = 2 Using tcpdump/wireshark I found that the last request sent to the X server is RandR opcode 8. My X server replies with BadRequest. The Xserver is correct, because it supports only RandR v1.1 and opcode 8 was added for protocol version 1.2 (see http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;f=randrproto.txt;a=blob) Actually gdmgreeter queries the RandR version just before the bad request, but obviously it does not use the version information appropriately. I'm not sure how common RandR v1.1 is these days. If the full support for the old protocol doesn't seem to be worth the effort, some better logging should be added. Alternatively, could gdmgreeter fall back to gdmlogin if the server supports only the old RandR protocol version? Workaround: switch to gdmlogin. (Called plain with facebrowser in gdmsetup) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: gdm 1) $ lsb_release -rd Description: Ubuntu 8.04.1 Release: 8.04 2) $ apt-cache policy gdm gdm: Installed: 2.20.7-0ubuntu1.1 Candidate: 2.20.7-0ubuntu1.1 Version table: *** 2.20.7-0ubuntu1.1 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 2.20.5-0ubuntu3 0 500 http://fi.archive.ubuntu.com hardy/main Packages 3) What you expected to happen - enabled remote logins using gdmsetup, no other changes. (seems to default to gdmgreeter) (NB: This might make your remote session vulnerable to attacks, don't do it if you don't understand the consequences) - expected to be able login from a remote Xserver running XDMCP 4) What happened instead Login screen was not displayed on remote Xserver My debugging gave the following explanation When talking to an X server supporting RandR v1.1 (instead of the current v1.2) gdmgreeter exits before displaying anything. There is no error message to the user. With gdm [debug] Enable=True only 2 lines are found in syslog, which might be related to the problem gdm[6110]: DEBUG: close_if_needed: Got G_IO_HUP on 9 gdm[6110]: DEBUG: close_if_needed: Got error on 9 However, these lines didn't tell me anything. - Using strace if found that gdmgreeter seems to be culprit: + Using strace I found that gdmgreeter seems to be culprit: write(2, The program \'gdmgreeter\' receive..., 583) = 583 However fd 2 seems to be /dev/null and I didn't find any information how to turn on logging. open(/dev/null, O_RDWR) = 2 Using tcpdump/wireshark I found that the last request sent to X server is RandR opcode 8. My X server replies with BadRequest. The Xserver is correct, because it supports only RandR v1.1 and opcode 8 was added for protocol version 1.2 (see http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;f=randrproto.txt;a=blob) - Actually gdmgreet queries the RandR version just before the bad request, - but obviously it does not use the version information appropriately. + Actually gdmgreeter queries the RandR version just before the bad + request, but obviously it does not use the version information + appropriately. I'm not sure how common RandR v1.1 is these days. If the full support for the old protocol doesn't seem to be worth the effort, some better logging should be added. Alternatively,
[Bug 296127] Re: gdmgreeter exits if Xserver supports only RandR v1.1
** Summary changed: - gdmgreeter exits on RandR v1.1 + gdmgreeter exits if Xserver supports only RandR v1.1 ** Description changed: Binary package hint: gdm 1) $ lsb_release -rd Description: Ubuntu 8.04.1 Release: 8.04 2) $ apt-cache policy gdm gdm: Installed: 2.20.7-0ubuntu1.1 Candidate: 2.20.7-0ubuntu1.1 Version table: *** 2.20.7-0ubuntu1.1 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 2.20.5-0ubuntu3 0 500 http://fi.archive.ubuntu.com hardy/main Packages 3) What you expected to happen - enabled remote logins using gdmsetup, no other changes. (seems to default to gdmgreeter) (NB: This might make your remote session vulnerable to attacks, don't do it if you don't understand the consequences) - expected to be able login from a remote Xserver running XDMCP 4) What happened instead Login screen was not displayed on remote Xserver My debugging gave the following explanation When talking to an X server supporting RandR v1.1 (instead of the current v1.2) gdmgreeter exits before displaying anything. There is no error message to the user. With gdm [debug] Enable=True only 2 lines are found in syslog, which might be related to the problem gdm[6110]: DEBUG: close_if_needed: Got G_IO_HUP on 9 gdm[6110]: DEBUG: close_if_needed: Got error on 9 However, these lines didn't tell me anything. - Using strace I found that gdmgreeter seems to be culprit: + Using strace I found that gdmgreeter seems to be the culprit: (only lines looking important to me copied here) + open(/usr/share/X11/XErrorDB, O_RDONLY) = 6 + read(6, ! $Xorg: XErrorDB,v 1.3 2000/08/..., 37949) = 37949 + close(6)= 0 write(2, The program \'gdmgreeter\' receive..., 583) = 583 + exit_group(1) However fd 2 seems to be /dev/null and I didn't find any information how to turn on logging. + (earlier) open(/dev/null, O_RDWR) = 2 Using tcpdump/wireshark I found that the last request sent to the X server is RandR opcode 8. My X server replies with BadRequest. The Xserver is correct, because it supports only RandR v1.1 and opcode 8 was added for protocol version 1.2 (see http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;f=randrproto.txt;a=blob) Actually gdmgreeter queries the RandR version just before the bad request, but obviously it does not use the version information appropriately. I'm not sure how common RandR v1.1 is these days. If the full support for the old protocol doesn't seem to be worth the effort, some better logging should be added. Alternatively, could gdmgreeter fall back to gdmlogin if the server supports only the old RandR protocol version? Workaround: switch to gdmlogin. (Called plain with facebrowser in gdmsetup) ** Description changed: Binary package hint: gdm 1) $ lsb_release -rd Description: Ubuntu 8.04.1 Release: 8.04 2) $ apt-cache policy gdm gdm: Installed: 2.20.7-0ubuntu1.1 Candidate: 2.20.7-0ubuntu1.1 Version table: *** 2.20.7-0ubuntu1.1 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 2.20.5-0ubuntu3 0 500 http://fi.archive.ubuntu.com hardy/main Packages 3) What you expected to happen - enabled remote logins using gdmsetup, no other changes. (seems to default to gdmgreeter) (NB: This might make your remote session vulnerable to attacks, don't do it if you don't understand the consequences) - expected to be able login from a remote Xserver running XDMCP 4) What happened instead Login screen was not displayed on remote Xserver My debugging gave the following explanation When talking to an X server supporting RandR v1.1 (instead of the current v1.2) gdmgreeter exits before displaying anything. There is no error message to the user. With gdm [debug] Enable=True only 2 lines are found in syslog, which might be related to the problem gdm[6110]: DEBUG: close_if_needed: Got G_IO_HUP on 9 gdm[6110]: DEBUG: close_if_needed: Got error on 9 However, these lines didn't tell me anything. Using strace I found that gdmgreeter seems to be the culprit: (only lines looking important to me copied here) open(/usr/share/X11/XErrorDB, O_RDONLY) = 6 read(6, ! $Xorg: XErrorDB,v 1.3 2000/08/..., 37949) = 37949 close(6)= 0 write(2, The program \'gdmgreeter\' receive..., 583) = 583 exit_group(1) However fd 2 seems to be /dev/null and I didn't find any information how to turn on logging. (earlier) open(/dev/null, O_RDWR) = 2 - Using tcpdump/wireshark I found that the last request sent to the X server is RandR opcode 8. My X server replies with BadRequest. The Xserver is correct,
[Bug 326891] Re: 2.6.27.11 kernel breaks r8169 support for rtl8102e
I use Xubuntu 8.10 on an Acer Aspirce One with the following Ethernet card sudo lspci -v ... 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Subsystem: Acer Incorporated [ALI] Device 015b Flags: bus master, fast devsel, latency 0, IRQ 219 I/O ports at 3000 [size=256] Memory at 5101 (64-bit, prefetchable) [size=4K] Memory at 5100 (64-bit, prefetchable) [size=64K] Expansion ROM at 5102 [disabled] [size=128K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [ac] MSI-X: Enable- Mask- TabSize=2 Capabilities: [cc] Vital Product Data ? Capabilities: [100] Advanced Error Reporting ? Capabilities: [140] Virtual Channel ? Capabilities: [160] Device Serial Number 00-00-ff-ff-00-00-00-04 Kernel driver in use: r8169 Kernel modules: r8169 ... The card worked with kernel 2.6.27-7, but stopped working with 2.6.27-11. I've now upgraded to kernel 2.6.27-13 from intrepid-proposed and the card works again. Thanks Stefan, Martin and/or who else was involved in creating this fix P.S. I did not see an instruction what packages need to be updated, I guessed linux-headers-2.6.27-13-generic linux-image-2.6.27-13-generic linux-restricted-modules-2.6.27-13-generic -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 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 212013] Re: Cannot send any key with AltGr
One update: The problem can also be reproduced with Xubuntu 8.04 instead of Windows XP. Emilio wrote: both with the client that works and the one that doesn't. Hmm, when you say client do you refer to the vnc client (vinagre) on my machine 1 or the X clients on my machine 2? There are too many clients here and maybe my configuration can be understood the easiest way be looking at the attached diagram. I have the old vnc client (well actually it's the old library libgtk- vnc-1.0-0 version 0.3.7-0ubuntu2) and it does not work with any X client. (That's what this bug is all about.) It does not produce any debugging information about keycodes when starting it using the command vinagre --gtk-vnc-debug. (maybe the library needs to be built with an certain flag turned on???) Next I have the new vnc client (well actually it's the new library libgtk-vnc-1.0-0 version 0.3.7-0ubuntu2.1) and it works with most X clients on the remote machine, but not with all. However, the debugging info from vinagre --gtk-vnc-debug, is always the same, regardless which X client on the remote machine has focus. debugging info looks like this: press keycode: 108 state: 0 group 0, keyval: 65027 press keycode: 20 state: 128 group 0, keyval: 92 release keycode: 20 state: 128 group 0, keyval: 92 release keycode: 108 state: 128 group 0, keyval: 65027 (Pressing AltGr, pressing the plus sign, which has the backslash in the AltGr position and releasing them in the opposite order) I guess the vnc client side there is no knowledge about who has focus on the vnc server side. Key presses are just blindly transmitted from the vnc client to the vnc server. But coming back to your question: Try investigating the output for vinagre --gtk-vnc-debug both with the client that works and the one that doesn't. I could not do this, because - only the new vnc client produced debugging output and - the debugging output is the same for both X clients where AltGr works and X clients where AltGr doesn't work. So I'm actually inclined to believe that your fix is valid for the vnc client side problem. (But there must be another bug somewhere in vino, the X server, or vmware running on my machine 2.) Just to exclude any doubts: As mentioned erlier AltGr *does* work correctly for all clients on machine 2 when typing on the physical keyboard of machine 2. ** Attachment added: my configuration http://launchpadlibrarian.net/21916217/vinagre-conf2.png -- Cannot send any key with AltGr https://bugs.launchpad.net/bugs/212013 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 328178] Re: hardy-updates needs a new linux-image
Thanks Brad for submitting this report. Note to the readers: Please pay attention to the related questions link. The issue has been discussed there before. Here are the answers to C, Cooke's questions: C. Cooke The output of 'apt-cache policy gcc' $ apt-cache policy gcc gcc: Installed: 4:4.2.3-1ubuntu6 Candidate: 4:4.2.3-1ubuntu6 Version table: *** 4:4.2.3-1ubuntu6 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 4:4.2.3-1ubuntu3 0 500 http://fi.archive.ubuntu.com hardy/main Packages I don't think this information reveals anything, because gcc is only a dependency package. $ dpkg-query -s gcc Package: gcc Status: install ok installed Priority: optional Section: devel Installed-Size: 64 Maintainer: Ubuntu Core developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: i386 Source: gcc-defaults (1.62ubuntu6) Version: 4:4.2.3-1ubuntu6 Provides: c-compiler Depends: cpp (= 4:4.2.3-1ubuntu6), gcc-4.2 (= 4.2.3-1) Recommends: libc6-dev | libc-dev Suggests: autoconf, automake1.9, bison, flex, gcc-doc, gcc-multilib, gdb, libtool, make, manpages-dev Conflicts: gcc-doc ( 1:2.95.3) Description: The GNU C compiler This is the GNU C compiler, a fairly portable optimizing compiler for C. . This is a dependency package providing the default GNU C compiler. Original-Maintainer: Debian GCC Maintainers debian-...@lists.debian.org So the real beef is in gcc-4.2 $ apt-cache policy gcc-4.2 gcc-4.2: Installed: 4.2.4-1ubuntu3 Candidate: 4.2.4-1ubuntu3 Version table: *** 4.2.4-1ubuntu3 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 4.2.3-2ubuntu7 0 500 http://fi.archive.ubuntu.com hardy/main Packages So you get a different gcc version depending on whether you follow hardy-updates or not. C. Cooke The output of 'dpkg -l linux-image*' $ dpkg-query -l linux-image* | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-=- un linux-imagenone (no description available) un linux-image-2.6none (no description available) ii linux-image-2.6.24-19-generic 2.6.24-19.41 Linux kernel image for version 2.6.24 on x86 ii linux-image-2.6.24-22-generic 2.6.24-22.45 Linux kernel image for version 2.6.24 on x86 ii linux-image-2.6.24-23-generic 2.6.24-23.48 Linux kernel image for version 2.6.24 on x86 ii linux-image-generic2.6.24.23.25 Generic Linux kernel image (I piped through cat in order to avoid truncation) C. Cooke The output of 'uname -a' $ uname -a Linux uwe-desktop 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 GNU/Linux I use the newest of my installed kernels, 2.6.24-23. $ apt-cache policy linux-image-2.6.24-23-generic linux-image-2.6.24-23-generic: Installed: 2.6.24-23.48 Candidate: 2.6.24-23.48 Version table: *** 2.6.24-23.48 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 500 http://security.ubuntu.com hardy-security/main Packages 100 /var/lib/dpkg/status You get the same one from hardy-security and hardy-updates. $ cat /proc/version Linux version 2.6.24-23-generic (bui...@vernadsky) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Jan 26 00:13:11 UTC 2009 It's build using gcc 4.2.3 But: $ gcc --version gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu3) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Summary: Those who follow hardy-updates (and security, of course), have a version mismatch whenever the the newest kernel comes from security. Solution: If a.) the compiler in hardy-updates is different in hardy-main hardy-security than the one in hardy-updates and b.) the newest kernel comes from hardy-security then hardy-updates must provide a kernel compiled with the compiler in hardy- updates. ** Changed in: linux (Ubuntu) Status: Incomplete = New -- hardy-updates needs a new linux-image https://bugs.launchpad.net/bugs/328178 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Hmm, your kernels are for Jaunty. I have only Hardy and Intrepid systems. I have reproduced the problem in Jaunty by using the live CD. But I guess I cannot update the kernel when using the live CD, can I? I can probably install a Jaunty to some disk corner, but I might take a couple of days or week until I find the time. Thanks for working on the patch! -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 324921] Re: [Intrepid] Update kernel to Linux 2.6.27.14
Today I saw that the 2.6.7-14 has been updated from version 14.30 to 14.33. After applying the update, my madwifi driver stopped working. I'm quite new to Ubuntu, but I understood as long as the ABI version does not change, i.e. 14 in this case, there is no need to rebuild kernel modules. After recompiling and reinstalling madwifi it worked again. Is this a problem or did I understand the meaning of ABI wrong? Or is the stability not guaranteed as long as it is still in the proposed repository? -- [Intrepid] Update kernel to Linux 2.6.27.14 https://bugs.launchpad.net/bugs/324921 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 324921] Re: [Intrepid] Update kernel to Linux 2.6.27.14
@Martin I have not investigated the issue any deeper, but my WLAN card of my Aspire One netbook did not work with a vanilla Intrepid installation. (Don't have the card make/model handy right now, but I can look it up later if desired.) So I followed the instructions at https://help.ubuntu.com/community/AspireOne --- clip--- Wireless module There has been some confusion as to which wireless driver provides the best performance and reliability. I have found the following: o madwifi from kernel (ath_pci) - does not attach to hardware. o ath5k from intrepid backports (ath5k) - connects to hardware, but experiences disconnects on medium to heavy wireless activity, and can not communicate with some AP's using WPA2 PSK. o madwifi-hal from http://snapshots.madwifi-project.org/ (ath_pci) - Everything works. --- clip --- The newest madwifi did indeed work for me. @Stefan I did not check the logs whether there was anything interesting. The first thing I noticed after upgrading was that ath_pci had be commented in /etc/modules. So I uncommented it again and rebooted. When WLAN still didn't work, I just recompiled and reinstalled. After that WLAN worked again. If this is important (or you are just interested to understand what is going on) and 14.30 is still available I could try to reproduce the issue and check the logs. I don't think gcc version has changed since I installed 14.30 and compiled madwifi the first time. -- [Intrepid] Update kernel to Linux 2.6.27.14 https://bugs.launchpad.net/bugs/324921 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Thanks for the intrepid versions. I've just tested the i386 version in the same machine as this report was created (see attached files above). No character corruption occurs anymore in my sampletable.txt in tty1 ... tty6. Correct characters seem to be displayed all the time. (Well I have not double checked every single character with a Unicode table. But those characters I happen to know by heart are correct and all other look correct to me) However, the characters previously corrupted appear in a different color now. While all characters, which worked before are displayed in some kind of grey, the new characters are displayed in white. Any explanation for this? The problem is already mentioned in https://bugs.launchpad.net/ubuntu/bugs/303561 The setfont(8) man page mentions that only 8 instead of 16 can be displayed if a font has more than 256 glyphs. But I understand this affects the whole console and not only the last 256 glyphs. If this understanding is correct, the reason should not be that the default grey is no longer available, because it is still used for all have always worked characters. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Oops, broken link in previous comment. New attempt: https://bugs.launchpad.net/bugs/303561 -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 324921] Re: [Intrepid] Update kernel to Linux 2.6.27.14
I haven't tried the rmmod suggestion yet. Will do that later. After installing the new -14 kernel built by Stefan for https://bugs.launchpad.net/bugs/355057 my madwifi stopped working again. The log entries look exactly the same as the last time. I guess rebuilding and reinstalling it will help again, but I haven't done it so far, just in case somebody is interested in further details (and it's too late for me anyway). I guess after the upgrade it starts to use the default Ubuntu driver, but I don't see any explanation why. This time ath_pci is not commented out in /etc/modules. Here are some kernel log lines: madwifi works before installing a new -14 kernel (only lines, which seem related to wifi) Apr 20 22:19:36 pikkukone kernel: [ 16.976739] ath_hal: module license 'Proprietary' taints kernel. Apr 20 22:19:36 pikkukone kernel: [ 17.076383] AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) Apr 20 22:19:36 pikkukone kernel: [ 17.977143] ath_pci :03:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 Apr 20 22:19:36 pikkukone kernel: [ 17.977189] ath_pci :03:00.0: setting latency timer to 64 Apr 20 22:19:36 pikkukone kernel: [ 18.479068] MadWifi: ath_attach: Switching rfkill capability off. Apr 20 22:19:36 pikkukone kernel: [ 20.822474] wifi0: Atheros AR2425 chip found (MAC 14.2, PHY SChip 7.0, Radio 10.2) Apr 20 22:19:36 pikkukone kernel: [ 20.864718] acer-wmi: Acer Laptop ACPI-WMI Extras madwifi does not work after installing a new -14 kernel (only lines, which seem related to wifi up to the error) Apr 20 23:19:43 pikkukone kernel: [ 17.144157] ath_hal: module license 'Proprietary' taints kernel. Apr 20 23:19:43 pikkukone kernel: [ 17.192511] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Apr 20 23:19:43 pikkukone kernel: [ 17.840840] wlan: 0.9.4 Apr 20 23:19:43 pikkukone kernel: [ 18.132467] ath_pci: 0.9.4 Apr 20 23:19:43 pikkukone kernel: [ 18.132592] ath_pci :03:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 Apr 20 23:19:43 pikkukone kernel: [ 18.132635] ath_pci :03:00.0: setting latency timer to 64 Apr 20 23:19:43 pikkukone kernel: [ 18.180993] wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13) -- [Intrepid] Update kernel to Linux 2.6.27.14 https://bugs.launchpad.net/bugs/324921 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
The man page is correct and it _will_ only affect the last 256 glyphs. You are right, I didn't read it carefully enough and understood it wrong. The trick is to mirror the colours indexed by 0-7 to the ones indexed by 8-15. If this were possible it would be another bug, because it does clearly not happen at least for my console. Or is there some limitation that the same color can only be used once and you have to use similar colors? Then people with poor monitors would have an advantage :) As said before I don't think this is high priority for me personally, because I prefer to use computers in English (as long as I can decide myself) and work in X11 (as long as I don't have to do trouble shooting). But if Ubuntu intends to be a localized system, it might of course be nice to eventually get the console working flawlessly also for languages using non-ASCII letters after so many years. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Forgot to answer... would it be ok to add you with your email as a Tested-by I'm not familiar with LKML policies and I couldn't find anything in the FAQ at least quickly. If looking at some characters on the console can be considered testing in that context, it's OK to add my email. However, if this somehow includes the promise that this does not cause any regression, I would not feel comfortable to make such promise after such little usage and with my non-existing backgound knowledge about the involved code. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
OK, so please feel free to add my email as tested-by. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 351207] Re: random pixels displayed for a certain character on tty
This bug is no regression occurring around kernel 2.6.27-13. It exists (at least) in Hardy, Intrepid and also in Jaunty. I'll provide more details, log and photos of the problem soon. But there is no reason to mark the verification of proposed Intrepid kernels 2.6.27-13 and -14 as failed because of this. -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 326891] Re: 2.6.27.11 kernel breaks r8169 support for rtl8102e
I've suspected that 2.6.27-13 causes regression in the framebuffer console. See my comment of 2009-03-29 above and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/351207. However, that problem has existed long before. So it's no regression and it is not any reason not to go forward with 2.6.27-13 (or -14). -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 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 324921] Re: [Intrepid] Update kernel to Linux 2.6.27.14
The framebuffer console problem reported as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/351207 is not regression. I have reproduced it in Hardy and also with the latest released Intrepid kernel 2.6.27-11. As far as this report is concerned you can remove the verification- failed tag. Sorry about the noise. -- [Intrepid] Update kernel to Linux 2.6.27.14 https://bugs.launchpad.net/bugs/324921 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 330200] Re: [Intrepid] Update kernel to Linux 2.6.27.16/17
Hmm, I don't seem to be able to find the package. Is it really in the intrepid-proposed repository? $ sudo apt-get update ... $ apt-cache policy linux-image-2.6.27-14-generic linux-image-2.6.27-14-generic: Asennettu: 2.6.27-14.30 Ehdokas: 2.6.27-14.30 Versiotaulukko: *** 2.6.27-14.30 0 400 http://fi.archive.ubuntu.com intrepid-proposed/main Packages 100 /var/lib/dpkg/status $ apt-cache policy linux-image-2.6.27-17-generic W: Pakettia linux-image-2.6.27-17-generic ei löydy $ apt-cache policy linux-image-2.6.27-16-generic W: Pakettia linux-image-2.6.27-16-generic ei löydy -- [Intrepid] Update kernel to Linux 2.6.27.16/17 https://bugs.launchpad.net/bugs/330200 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 355057] [NEW] Non-ASCII characters get corrupted in framebuffer console
Public bug reported: This issue has been reported several times before in various forms. Typically about one national character missing. I try to summarize all information I have collected in this new general report and mark the earlier reports about special cases as duplicates. Several non-ASCII characters get corrupted in the framebuffer console. (see attached photos) This happens when returning from X back to the console using Ctrl-Alt-F1 ... Ctrl-Alt-F6. The characters are are displayed correctly when booting into single user mode and not starting X. (see attached intrepid-single-user-OK.jpg) So the problem is not incomplete font implementation or some locale issue. This is why I report the bug to the kernel instead of to console-setup, if feels that console-setup should not cause random pixel characters (But of course the bug could really be somewhere else. I'm far from understanding completely how this all works.) I also attach my /etc/defaults/console-setup Actually the problem is described in /usr/share/doc/console-setup/FAQ.gz However, it says that this happens only in text mode, not in framebuffer mode. So how can I find out in which mode my console is actually running? I believe that my console should be in framebuffer mode, because: $ lsmod | grep fb fbcon 47648 0 tileblit 10880 1 fbcon font 16512 1 fbcon bitblit13824 1 fbcon However there is a file /etc/modprobe.d/blacklist-framebuffer and it says # Framebuffer drivers are generally buggy and poorly-supported, and cause # suspend failures, kernel panics and general mayhem. For this reason we # never load them automatically. So do we use fbcon, but not the underlaying framebuffer??? Some documentation is here http://www.mjmwired.net/kernel/Documentation/fb/fbcon.txt, but I'm still confused. The problem is not specifc to the reported kernel version. I see it also with the current Hardy kernel and the Jaunty Beta LiveCD (see jaunty-liveCD.jpg). The problem is not specific to the reported grahics card. I see it also on Nvidia, on Radeon, and also on the virtualized card created by VMware. The previously reported bugs (now linked as duplicates) cover also various hardware and software configurations. I have tested the range Unicode U+00A0 ... U+00FF, my console coding is UTF-8. http://www.utf8-chartable.de/ can be used for referece. (From the previousily reported national character issues I conclude that also characters outside this range are affected) You can easily test yourself using the attached file $ cat sampletable.txt The character corruption comes in 2 different forms: - Random pixel character range: All characters between and including U+00E9 and U+00FF are corrupted. Often the pixels are completely random (See attached intrepid-random-pixel-range.jpg) and they are different on each console tty1, tty2, ... Sometimes they are just all white or black. The somehow weird thing is that the U+00E8 (e grave) is always the last character displayed correctly, whereas U+00E9 (e acute) is always the first corrupted character. - missing accents. There is no random corruption in this case, but accents are missing from capital letters. It looks more like an intentional low-grade variant of the font. Accents are present on lowercase letters. A couple of very rare characters (e.g. thorn) are displayed as white blocks. (see attached intrepid-no-accents.jpg) I guess this variant of the problem may lead to the belief that a certain configuration is not affected, if you just test a couple of lowercase characters. The same kernel on the same machine can sometimes show random pixel character range and sometimes missing accents. E.g. when boot first into single user mode and start your X later in contrast of starting everything the standard way. (intrepid-random-pixel-range.jpg and intrepid-no-accents.jpg are from the same machine using the same kernel) P.S. Not sure how important this problem really is. I started to dig when investigating some serious display corruption (affecting also X on framebuffer 7) So originally I thought if even the console gets corrupted things are really bad. But in the meantime I have come to the conclusion that this character corruption is most likely a completely different issue from my original problem. For me personally non-ASCII characters on the console are of minor importance. On the other side according to Ubunutu philosophy software should be available in the user's local language. This of course requires that national characters work, if somebody works on the console. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 Package: linux-image-2.6.27-14-generic 2.6.27-14.30 ProcCmdLine: root=UUID=f6bf9b65-0cad-45bd-b3a0-a7353a3900af ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fi_FI.UTF-8 SHELL=/bin/bash
[Bug 355057] Re: Non-ASCII characters get corrupted in framebuffer console
** Attachment added: picture 1/4 http://launchpadlibrarian.net/24802446/intrepid-no-accents.jpg -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
** Attachment added: sampletable.txt for easy reproduction http://launchpadlibrarian.net/24802397/sampletable.txt -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
** Attachment added: picture 2/4 http://launchpadlibrarian.net/24802480/intrepid-random-pixel-range.jpg -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
** Attachment added: my /etc/defaults/console-setup http://launchpadlibrarian.net/24802358/console-setup ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/24802359/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/24802360/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24802361/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24802362/HalComputerInfo.txt ** Attachment added: LsUsb.txt http://launchpadlibrarian.net/24802363/LsUsb.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24802364/Lspci.txt ** Attachment added: ProcCpuInfo.txt http://launchpadlibrarian.net/24802365/ProcCpuInfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24802367/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24802368/ProcModules.txt -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Oops launchpad does not really display the file name. Picture 1/4 was intrepid-no-accents.jpg Picture 2/4 was intrepid-random-pixel-range.jpg ** Attachment added: intrepid-single-user-OK.jpg http://launchpadlibrarian.net/24802539/intrepid-single-user-OK.jpg -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
** Attachment added: jaunty-liveCD.jpg http://launchpadlibrarian.net/24802562/jaunty-liveCD.jpg -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 351207] Re: random pixels displayed for a certain character on tty
*** This bug is a duplicate of bug 355057 *** https://bugs.launchpad.net/bugs/355057 ** This bug has been marked a duplicate of bug 355057 Non-ASCII characters get corrupted in framebuffer console -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 202539] Re: The letter ö shows as random bitmap on console
*** This bug is a duplicate of bug 355057 *** https://bugs.launchpad.net/bugs/355057 The problem affects not only the letter ö, but many others too. I have created a more general report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057 and will mark this report as a duplicate. Taleman, please don't take this as a personal offense, the honor of reporting the letter ö problem first, remains of course yours. ** This bug has been marked a duplicate of bug 355057 Non-ASCII characters get corrupted in framebuffer console -- The letter ö shows as random bitmap on console https://bugs.launchpad.net/bugs/202539 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 351207] Re: random pixels displayed for a certain character on tty
*** This bug is a duplicate of bug 355057 *** https://bugs.launchpad.net/bugs/355057 I have create a new bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057. It describes the problem better (I hope) , has pictures attached and the misleading suspicion about regression is no longer mentioned. Marking this old report as a duplicate. -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 273189] Re: non-ascii layout/encoding problems at login line
getty and locales might be one problem. I have not looked into that. But another problem are non-ASCII characters being corrupted on the console. I believe you might see a combination of both problems. The character corruption problem has been reported as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057 -- non-ascii layout/encoding problems at login line https://bugs.launchpad.net/bugs/273189 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 303561] Re: Polish diacritics not working in Alt-Ctrl-Fx console
I understand you report a different problem here, that the characters are missing in the first place. But could you possibly also be affected by this problem that non-ASCII characters get corrupted? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057 -- Polish diacritics not working in Alt-Ctrl-Fx console https://bugs.launchpad.net/bugs/303561 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
There are 2 more reports, which I originally thought they report the same issue. However, after reading them again, I decided not to mark them as duplicates, because they contain also other aspects, which might be unique to them. For cross reference, the links are https://launchpad.net/bugs/190746 and https://launchpad.net/bugs/273189 -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Oops, couldn't read my own handwritten notes and the previous comment got wrong... These 2 reports might contain duplicate aspects (but also some other things) https://launchpad.net/bugs/273189 https://launchpad.net/bugs/303561 This one sounds somehow loosely related to the topic (but not a duplicate) https://launchpad.net/bugs/190746 Sorry about the noise. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 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 343208] Re: After updating Kernel, Wired connection does not work
*** This bug is a duplicate of bug 326891 *** https://bugs.launchpad.net/bugs/326891 Are you 100% sure this is also broken in 2.6.27-13? Please comment in https://bugs.launchpad.net/bugs/326891 2.6.27-13 fixed it for me. ** This bug has been marked a duplicate of bug 326891 2.6.27.11 kernel breaks r8169 support for rtl8102e -- After updating Kernel, Wired connection does not work https://bugs.launchpad.net/bugs/343208 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 326891] Re: 2.6.27.11 kernel breaks r8169 support for rtl8102e
Yes, I can confirm the previous comment. 2.6.27-14 works, too (-7 working, -11 broken, -13 working, -14 working) -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 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 326891] Re: 2.6.27.11 kernel breaks r8169 support for rtl8102e
my last comment was about Intrepid, sorry about the extra noise -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 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 351207] Re: random pixels displayed for a certain character on tty
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/24492079/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/24492080/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24492081/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24492082/HalComputerInfo.txt ** Attachment added: LsUsb.txt http://launchpadlibrarian.net/24492083/LsUsb.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24492084/Lspci.txt ** Attachment added: ProcCpuInfo.txt http://launchpadlibrarian.net/24492085/ProcCpuInfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24492086/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24492087/ProcModules.txt -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 351207] Re: random pixels displayed for a certain character on tty
** Attachment added: /etc/defaults/console-setup http://launchpadlibrarian.net/24492117/console-setup -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 351207] Re: random pixels displayed for a certain character on tty
** Attachment added: smaple.txt to reproduce without Finnish keyboard http://launchpadlibrarian.net/24492131/sample.txt -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 351207] [NEW] random pixels displayed for a certain character on tty
Public bug reported: This seems to be regression in kernel 2.6.27-13. The issue also exists in 2.6.27-14. (both from intrepid-proposed) The issue does not exist in kernels 2.6.27-7 and 2.6.27-11 (from intrepid-updates or security), when booting these old kernels in my otherwise unchanged system. (I have not yet had time to test other kernels. I guess -12 might be interesting to find out where the problem has been really introduced and -18 might be interesting whether the issue has been solved in the meantime. Please advise, which kernel should be tested, if any) When using a tty (Ctrl-Alt-F1 ... Ctrl-Alt-F6) the character Latin small letter o with diaresis unicode U+00F6 or UTF-8 0xc3b6 is displayed as random pixels. The pixel pattern seems to be different after each boot and it's always different on each tty (tty1 ... tty6). However it does not seem to change on the same tty as long as the machine is not rebooted. I use a Finnish keyboard (see attached console-setup file) and it also supports the non-ASCII characters - Latin small letter a with diaresis Unicode U+00E4 equals UTF-8 0xc3a4 and - Latin small letter a with ring above Unicode U+00E5 equals UTF-8 0xc3a5 The latter 2 characters (as well as the ASCII characters) do appear always correctly. Without a Finnish keyboard the problem can be repeated by cat sample.txt (attached) (if your terminal is in utf8 mode) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: ath_hal Package: linux-image-2.6.27-14-generic 2.6.27-14.30 ProcCmdLine: root=UUID=f6bf9b65-0cad-45bd-b3a0-a7353a3900af ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-14.30-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 326891] Re: 2.6.27.11 kernel breaks r8169 support for rtl8102e
Intrepid. Although 2.6.27-13 fixes the network adapter problem, I believe it causes regression elsewhere. Please see my report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/351207 -- 2.6.27.11 kernel breaks r8169 support for rtl8102e https://bugs.launchpad.net/bugs/326891 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 324921] Re: [Intrepid] Update kernel to Linux 2.6.27.14
I believe there is regression with the framebuffer. Please see my report in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/351207 -- [Intrepid] Update kernel to Linux 2.6.27.14 https://bugs.launchpad.net/bugs/324921 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 351207] Re: random pixels displayed for a certain character on tty
Yes, I think that should be no problem. I'll have a business trip first, so please be patient for a couple of days. -- random pixels displayed for a certain character on tty https://bugs.launchpad.net/bugs/351207 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 296127] Re: gdmgreeter exits if remote Xserver supports only RandR v1.1
Alternative work-around: Disable RandR altogether on your remote Xserver supporting only v1.1. gdmgreeter works fine now. -- gdmgreeter exits if remote Xserver supports only RandR v1.1 https://bugs.launchpad.net/bugs/296127 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 296127] Re: gdmgreeter exits if remote Xserver supports only RandR v1.1
The question is of course whether the bug is in gdmgreeter code proper or in some library it uses. If anybody has some hints how to debug this? (maybe something easier than building gdmgreeter myself with debug indo and single-stepping through it) -- gdmgreeter exits if remote Xserver supports only RandR v1.1 https://bugs.launchpad.net/bugs/296127 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 310329] [NEW] apt-get install option --[no]-install-recommends should be documented
Public bug reported: Binary package hint: apt 1.) lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 2.) apt-cache policy apt apt: Installed: 0.7.9ubuntu17.1 Candidate: 0.7.9ubuntu17.1 Version table: *** 0.7.9ubuntu17.1 0 500 http://fi.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status 0.7.9ubuntu17 0 500 http://fi.archive.ubuntu.com hardy/main Packages 3.) What you expected to happen calling man apt-get should list all command line options 4.) What happened instead options --install-recommends --no-install-recommends are not mentioned on the man page I think these options are pretty important, because I don't think there exists a generally useful default to put to apt.conf. It depends very much on the package, whether I want to the have the recommended packages or whether they just clutter up my system. So the command line options are very handy to use. But a bit difficult to find as long as they are undocumented. Well, a fix should be very easy (just add a 2 sentences to the man page). Unfortunately I'm a Ubuntu newcomer and not at all familiar how I could contribute such a fix. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- apt-get install option --[no]-install-recommends should be documented https://bugs.launchpad.net/bugs/310329 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 305586] Re: continuous [driAllocateTexture:636] even when idle
since it is has been some time with no response from the original reporter. I'm the original reporter. However, if the issue still exists Yes, it does, (intrepid system with all updates, tested 2 minutes ago) apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 7.2-1ubuntu2 Candidate: 7.2-1ubuntu2 Version table: *** 7.2-1ubuntu2 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status feel free to reopen with the requested information. Sorry, I'm not aware that any additional information has been requested from me. Could you please rephrase what you need. ** Changed in: mesa (Ubuntu) Status: Invalid = New -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 305586] Re: continuous [driAllocateTexture:636] even when idle
Please find attached both the Xorg and the gdm/\:0 logs. They are copied more or less immediately after booting with normal visual effects. Only one xterm was started during that time. ** Attachment added: Xorg.0.log and gdm/\:0.log http://launchpadlibrarian.net/20285892/xlogs.tbz ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 305586] Re: continuous [driAllocateTexture:636] even when idle
Oops, sorry, I completely forgot about this log file. I hope I'll remember to do it soon. (Right now I'm not close to the machine in question and it's not online) -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 212013] Re: Cannot send any key with AltGr
Thanks Emilio!
libgtk-vnc-1.0-0 version 0.3.7-0ubuntu2.1 from the PPA tested with the
following setup
local machine (vinagre): Intrepid, Finnish keyboard
remote machine (vino): Hardy, Finnish keyboard
when using Emacs on the remote machine: All AltGr combinations work: @ £
$ { [ ] } \ € ~ |
However, when using Windows XP in Vmware Workstation in the remote machine,
AltGr combinations don't work. AltGr
doesn't seem to be received, the unaltered characters are produced.
Of course there now 2 closed source products involved and it would be
easy to blame them. However, what I don't understand is: Vmware is
externally nothing else but an X Windows client, isn't it? This X
Windows client can handle the input from the physical Finnish keyboard
correctly. Shouldn't the input from vino be exactly the same? So the
inner layers of closed source software shouldn't be able to tell the
difference and should have no chance to screw anything up.
Any advice how to debug this is welcome.
--
Cannot send any key with AltGr
https://bugs.launchpad.net/bugs/212013
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 305586] [NEW] continuous [driAllocateTexture:636] even when idle
Public bug reported: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description:Ubuntu 8.10 Release:8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings 4) The message [driAllocateTexture:636] unable to allocate texture is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application is running. Without being an expert in this area, I understand this means that the resources of graphics card have been exhausted. I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefully). Anyway I think writing an error to a log file about once a second in a clean system is not acceptable. Further details Hardware: Laptop IBM T40 Graphics card: (--) PCI:*([EMAIL PROTECTED]:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe000/0, 0xc010/0, I/O @ 0x3000/0, BIOS @ 0x/131072 Software: a plain intrepid installation with all recommended updates and only 3 minor additional packages installed Work around: Go to System -- Preferences -- Appearance // Visual Effects and change the default setting Normal to None Without understanding much of that topic I made the following guesses: - The Normal visual effects of 2008 are just too heavy for an approximately 5 year old laptop. (I understand business laptops like this one are not optimized for graphics performance anyway) - Because the graphic card runs out of resources the error occurs continuously If my guesses are correct the only solution is that Ubuntu must recognize during installation (or a each boot), whether the graphics card is powerful enough to handle Normal visual effects. If not, they should be disabled by default, because the average user - will not read the log files, - will not understand what the error message [driAllocateTexture:636] means (nor do I) - and will not be able to draw the conclusion that visual effect should be disabled I further guessed that gnome-control-center might possibly be responsible for the default settings, because it allows the user to change the visual effects. If this guess was wrong, the bug needs to be redirected to another package, whoever is responsible for choosing the default value) (Of course if my guesses above that the visual effects will just not reasonably work on such an old laptop graphics card were wrong, it might be possible to correct the implementation of the visual effects. Then again, the bug should be redirected to whoever causes the error message) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings 4) The message [driAllocateTexture:636] unable to allocate texture - is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application - is running. + is written to /var/log/gdm/\:0.log about once a second even when the + system is idle and no graphics intensive application is running. Without being an expert in this area, I understand this menas the the resources of graphics card have been exhausted. I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefually) Further details Hardware: Laptop IBM T40 Graphics card: (--) PCI:*([EMAIL PROTECTED]:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe000/0, 0xc010/0, I/O @ 0x3000/0, BIOS @ 0x/131072 Software: a plain intrepid installation with all recommended updates and only 3 minor additional packages installed Work around: Go to System --
[Bug 305586] Re: continuous [driAllocateTexture:636] even when idle
** Description changed: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings 4) The message [driAllocateTexture:636] unable to allocate texture is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application is running. - Without being an expert in this area, I understand this menas the the + Without being an expert in this area, I understand this means that the resources of graphics card have been exhausted. - I believe this can be seen by the end user e.g. by drastically reduced - scrolling performance e.g. in a normal gnome terminal (but I have not - investigated this claim very carefually) + I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefully). Anyway I think writing an error to a log file about once a + second in a clean system is not acceptable. Further details Hardware: Laptop IBM T40 Graphics card: (--) PCI:*([EMAIL PROTECTED]:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe000/0, 0xc010/0, I/O @ 0x3000/0, BIOS @ 0x/131072 Software: a plain intrepid installation with all recommended updates and only 3 minor additional packages installed Work around: Go to System -- Preferences -- Appearance // Visual Effects and change the default setting Normal to None - Without understand much of that topic I made the following guesses: + Without understanding much of that topic I made the following guesses: - - The Normal visual effects of 2008 are just too heavy for ~ 5 year old laptop. (I understand business laptops like this - are not optimized for graphics performance anyway) + - The Normal visual effects of 2008 are just too heavy for ~ 5 year + old laptop. (I understand business laptops like this one are not + optimized for graphics performance anyway) - Because the graphic card runs out of resources the error occurs - continously + continuously - If my guesses are correct the only solution is that Ubuntu should - recognize, whether the graphics card is powerful enough to handle - Normal visual effects. If not they should be diabled by default, - because the average user + If my guesses are correct the only solution is that Ubuntu must + recognize during installation (or a each boot), whether the graphics + card is powerful enough to handle Normal visual effects. If not, they + should be disabled by default, because the average user - will not read the log files, - will not understand what the error message [driAllocateTexture:636] means (nor do I) - and will not be able to draw the conclusion that visual effect should be disabled I further guessed that gnome-control-center might possibly be responsible for the default settings, because it allows the user to change the visual effects. If this guess was wrong, the bug needs to be redirected to another package, whoever is - responsibel for choosing the default value) + responsible for choosing the default value) (Of course if my guesses above that the visual effects will just not - reasonably work on such an old laptop graphics card were wrong, it might - be possible to correct the implementation of the visual effects. Then - again, the bug should be redirected to whoever causes the error message) + reasonably work on such an old laptop graphics card were wrong, it + might be possible to correct the implementation of the visual effects. + Then again, the bug should be redirected to whoever causes the error + message) ** Description changed: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings 4) The message
[Bug 305586] Re: continuous [driAllocateTexture:636] even when idle
** Description changed: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings - 4) The message + 4) What happend: The message [driAllocateTexture:636] unable to allocate texture is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application is running. Without being an expert in this area, I understand this means that the resources of graphics card have been exhausted. I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefully). Anyway I think writing an error to a log file about once a second in a clean system is not acceptable. Further details Hardware: Laptop IBM T40 Graphics card: (--) PCI:*([EMAIL PROTECTED]:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe000/0, 0xc010/0, I/O @ 0x3000/0, BIOS @ 0x/131072 Software: a plain intrepid installation with all recommended updates and only 3 minor additional packages installed Work around: Go to System -- Preferences -- Appearance // Visual Effects and change the default setting Normal to None Without understanding much of that topic I made the following guesses: - The Normal visual effects of 2008 are just too heavy for an approximately 5 year old laptop. (I understand business laptops like this one are not optimized for graphics performance anyway) - Because the graphic card runs out of resources the error occurs continuously If my guesses are correct the only solution is that Ubuntu must recognize during installation (or a each boot), whether the graphics card is powerful enough to handle Normal visual effects. If not, they should be disabled by default, because the average user - will not read the log files, - will not understand what the error message [driAllocateTexture:636] means (nor do I) - and will not be able to draw the conclusion that visual effect should be disabled I further guessed that gnome-control-center might possibly be responsible for the default settings, because it allows the user to change the visual effects. If this guess was wrong, the bug needs to be redirected to another package, whoever is responsible for choosing the default value) (Of course if my guesses above that the visual effects will just not reasonably work on such an old laptop graphics card were wrong, it might be possible to correct the implementation of the visual effects. Then again, the bug should be redirected to whoever causes the error message) ** Description changed: Binary package hint: gnome-control-center 1) $ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 2) $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://fi.archive.ubuntu.com intrepid/main Packages 3) What I expected to happen: No resource problems and/or continuous error messages to log on an idle system with default settings 4) What happend: The message [driAllocateTexture:636] unable to allocate texture is written to /var/log/gdm/\:0.log about once a second even when the system is idle and no graphics intensive application is running. Without being an expert in this area, I understand this means that the resources of graphics card have been exhausted. I believe this can be seen by the end user e.g. by drastically reduced scrolling performance e.g. in a normal gnome terminal (but I have not investigated this claim very carefully). Anyway I think writing an error to a log file about once a second in a clean system is not acceptable. Further details Hardware: Laptop IBM T40 Graphics card: (--) PCI:*([EMAIL PROTECTED]:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] rev 2, Mem @ 0xe000/0, 0xc010/0, I/O @ 0x3000/0, BIOS @ 0x/131072 Software: a plain intrepid installation with all recommended updates and only 3
[Bug 738964] Re: update-manager crashed with NotAuthorizedError in _run(): org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name': ':1.57'}): org.debian.apt.upgrade-packages
*** This bug is a duplicate of bug 704667 ***
https://bugs.launchpad.net/bugs/704667
** Visibility changed to: Public
** This bug has been marked a duplicate of bug 704667
Update-manager crashes on fresh natty installs-- NotAuthorizedError:
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name':
':1.107'}): org.debian.apt.upgrade-packages
* You can subscribe to bug 704667 by following this link:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/704667/+subscribe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738964
Title:
update-manager crashed with NotAuthorizedError in _run():
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name',
{'name': ':1.57'}): org.debian.apt.upgrade-packages
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 656100] Re: [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed.
Excellent!!! After git checkout 6936fb and building and starting applications as in comment #42 the problem is gone. Tested with running stellarium and resizing glxgears. -- [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed. https://bugs.launchpad.net/bugs/656100 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 656100] Re: [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed.
To clarify: I have only built and tested r200_dri.so on 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02) The comment says that the fix is for r200. No idea whether it helps also for the different card driver mentioned in #45 -- [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed. https://bugs.launchpad.net/bugs/656100 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 656100] Re: [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed.
Now I've built both radeon_dri.so and r200_dri.so for the benfit of those who are not so familiar with git and building. (or those who just want to save the time to do it) 1. Extract the attached file. tar xf mesafix-6936fb.tbz 2, go to the newly created directory cd mesafix-6936fb 3. run OpenGL applications like this LIBGL_DRIVERS_PATH=. glxgears LIBGL_DRIVERS_PATH=. stellarium If it does not work make sure that the applications really use the fixed libraries and not the previously installed ones 1. Find the process id of the application ps -e 2. display the libraries used grep xp /proc/1234/maps (replace 1234 by the process id you got in step 1) 3. Make sure the dri library comes from your newly created directory instead of /usr/lib/dri Elias: could you please test on your laptop to see whether the r200 fix also helps for the radeon driver used for your graphics adapter. ** Attachment added: radeon_dri and r200_dri from git commit 6936fb https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/656100/+attachment/1696916/+files/mesafix-6936fb.tbz -- [radeon][r200] ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi-space_accounted' failed. https://bugs.launchpad.net/bugs/656100 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 549801] Re: USB WiFi adapter with rt2870 chipset won't connect
Please ignore comment #33. It turned out that my device (D-Link DWA-140 B2) contains an RT3070, not an RT2870. Getting the driver source from Ralink and building makes it work on Lucid; Maverick not yet tested Sorry about the noise. -- USB WiFi adapter with rt2870 chipset won't connect https://bugs.launchpad.net/bugs/549801 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 573905] Re: Lucid/Maverick: Wireless USB DLink DWA-140 does not connect
I just learned that there is an important difference between a DWA-140 and a DWA-140 ver. B2. The DWA-140 contains an RT2870, the DWA-140 B2 contains an RT3070. The device I have borrowed is a B2, so the apport logs above apply to RT3070 only. In Lucid downloading and building the RT3070 driver from Ralink solves the problem. (I have also the rt2800usb driver blacklisted, not yet double-checked whether that is required) Maverick not yet tested. -- Lucid/Maverick: Wireless USB DLink DWA-140 does not connect https://bugs.launchpad.net/bugs/573905 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 528679] Re: Kpackedkit update details inform that there are no update descriptions
Yes, this happens from time to time lin Lucid. It looks like a network error (I guess it fetches the description from a Canonical server). But it happens at least 10 times more frequently than network errors in other programs, e.g. Browser. So I'm sure this could be somehow improved in kpackagekit. Maybe just retrying if the first attempt fails? (I understand browsers do this) -- Kpackedkit update details inform that there are no update descriptions https://bugs.launchpad.net/bugs/528679 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 649284] [NEW] kpackagekit shows incorrect security classification
Public bug reported: Binary package hint: kpackagekit In Lucid kpackagekit shows a fix in the wrong group from time to time. This is difficult to reproduce, because it depends on the package versions installed and on the package versions available from the repos. So in normal usage (i.e. if you don't downgrade packages) the same problem will never appear twice. Today I happen to have the issue for linux-generic: $ apt-cache policy linux-generic linux-generic: Installed: 2.6.32.24.25 Candidate: 2.6.32.25.27 Version table: 2.6.32.25.27 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages *** 2.6.32.24.25 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2.6.32.21.22 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages $ The candidate version comes from lucid-updates, not from lucid security. Still kpackagekit shows it as a security fix. See attached screen shot. Note that the version numbers in kpackagekit are equal to those shown by apt-cache. I will apport-collect this report ASAP in order to provide necessary version info. --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Kubuntu 10.04 Lucid Lynx - Beta i386 (20100406.1) Package: kpackagekit 0.5.4-0ubuntu4.3 PackageArchitecture: i386 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 Tags: lucid Uname: Linux 2.6.32-24-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: kpackagekit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected kubuntu -- kpackagekit shows incorrect security classification https://bugs.launchpad.net/bugs/649284 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 649284] Re: kpackagekit shows incorrect security classifiaction
** Attachment added: screenshot https://bugs.launchpad.net/bugs/649284/+attachment/1645815/+files/kpackagekit.png ** Tags added: apport-collected ** Description changed: Binary package hint: kpackagekit In Lucid kpackagekit shows a fix in the wrong group from time to time. This is difficult to reproduce, because it depends on the package versions installed and on the package versions available from the repos. So in normal usage (i.e. if you don't downgrade packages) the same problem will never appear twice. Today I happen to have the issue for linux-generic: $ apt-cache policy linux-generic linux-generic: Installed: 2.6.32.24.25 Candidate: 2.6.32.25.27 Version table: 2.6.32.25.27 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages *** 2.6.32.24.25 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 2.6.32.21.22 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages $ The candidate version comes from lucid-updates, not from lucid security. Still kpackagekit shows it as a security fix. See attached screen shot. Note that the version numbers in kpackagekit are equal to those shown by apt-cache. - I will apport-collect this report ASAP in order to provide necessary - version info. + I will apport-collect this report ASAP in order to provide necessary version info. + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + InstallationMedia: Kubuntu 10.04 Lucid Lynx - Beta i386 (20100406.1) + Package: kpackagekit 0.5.4-0ubuntu4.3 + PackageArchitecture: i386 + ProcEnviron: + LANGUAGE= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 + Tags: lucid + Uname: Linux 2.6.32-24-generic i686 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- kpackagekit shows incorrect security classification https://bugs.launchpad.net/bugs/649284 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 649284] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.edge.launchpad.net/bugs/649284/+attachment/1645860/+files/Dependencies.txt ** Summary changed: - kpackagekit shows incorrect security classifiaction + kpackagekit shows incorrect security classification -- kpackagekit shows incorrect security classification https://bugs.launchpad.net/bugs/649284 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 649284] Re: kpackagekit shows incorrect security classification
Because the linux-generic fix in question was an ABI change, a new package not previously installed was pulled. However, it was not from security either: $ apt-cache policy linux-image-generic linux-image-generic: Installed: 2.6.32.25.27 Candidate: 2.6.32.25.27 Version table: *** 2.6.32.25.27 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.6.32.24.25 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 2.6.32.21.22 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages $ apt-cache policy linux-image-2.6.32-25-generic linux-image-2.6.32-25-generic: Installed: 2.6.32-25.44 Candidate: 2.6.32-25.44 Version table: *** 2.6.32-25.44 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status $ (These commands executed after applying the update. Nothing vsible in kpackagekit at this point of time anymore of course) -- kpackagekit shows incorrect security classification https://bugs.launchpad.net/bugs/649284 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kpackagekit in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 721771] [NEW] natty: systemtap incompatible with kernel
Public bug reported: Binary package hint: systemtap Systemtap module compilation fails with error: ‘param_ops_int64_t’ undeclared here (not in a function) This has been reported and also fixed upstream: http://sourceware.org/bugzilla/show_bug.cgi?id=11940 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: systemtap 1.3-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5 Uname: Linux 2.6.38-4-generic i686 Architecture: i386 Date: Sat Feb 19 15:21:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110218) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: systemtap ** Affects: systemtap (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721771 Title: natty: systemtap incompatible with kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721771] Re: natty: systemtap incompatible with kernel
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721771 Title: natty: systemtap incompatible with kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721771] Re: natty: systemtap incompatible with kernel
Because systemtap package does not declare the dependecy on the kernel debug info correctly, obviously apport-bug has not included the relevant info either. But yes I have correct kernel debug info installed: ii linux-image-2.6.38-4-generic-dbgsym 2.6.38-4.31 Linux kernel debug image for version 2.6.38 on x86/x86_64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721771 Title: natty: systemtap incompatible with kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721771] Re: natty: systemtap incompatible with kernel
Commit 75a48ca3 mentioned in the upstream bug report applies cleanly to the systemtap source in natty and solves the problem with error: ‘param_ops_int64_t’ undeclared here (not in a function) I tried 2 simple system tap scripts: 1 succeeded and 1 failed. The new error is: error: 'CLONE_STOPPED’ undeclared here (not in a function) Upstream there is a changelog entry Wed Jan 19 2011 Frank Ch. Eigler f...@redhat.com - 1.4-3 - adapt to kernel CLONE_STOPPED deprecation Haven't had time to look into that yet. But from the changelog text I guess it's the same problem again. The systemtap version in natty is just too old to work with the natty kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721771 Title: natty: systemtap incompatible with kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721771] Re: natty: systemtap incompatible with kernel
The second problem error: 'CLONE_STOPPED’ undeclared here (not in a function) is fixed by upstream commit b30b7ed1. All my tests are successful for the moment (that doesn't tell much, I have used only very simple scripts) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721771 Title: natty: systemtap incompatible with kernel -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
Hi Bryce, [This is an automatic notification.] This bug was reported against an earlier version of Ubuntu, can you test if it still occurs on Lucid? Did your script fail here? The bug has been report against a very recent version of Lucid and I have run apport-collect as you can see from all the attachments. Since reporting the bug and running apport-collect only one possibly relevant update has come (linux-kernel) Current Operating System: Linux geuder-t40 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=8567e5f2-2176-4d29-826d-7f6316bd60b2 ro quiet splash --- Current Operating System: Linux geuder-t40 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=8567e5f2-2176-4d29-826d-7f6316bd60b2 ro quiet splash The crash still appears and the stack is still exactly the same (modulo address randomization) I change the status back to New and remove the needs-retested-on-lucid- by-june tag ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = New ** Tags removed: needs-retested-on-lucid-by-june -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 305586] Re: continuous [driAllocateTexture:636] even when idle
Hi Bryce, With Lucid I have switched to Kubuntu on that machine. I'm not sure whether it is possible to retest the original problem in Kubuntu, because the visual effects are probably quite differently implemtned. I cannot promise that I have time to install Ubuntu until June, but I'll try to keep it in mind. As mentioned in comment #12 I'm not sure whether log writings would appear in LiveCD environment (after all there is no disk to write the log to) So I guess installing Ubuntu Lucid is the only way to be sure. -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
FYI: the same problem has also been observed in Arch Linux with a slightly different model of Radeon graphics adapter. http://bbs.archlinux.org/viewtopic.php?id=95549 -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
I was somehow guessing that EXA could be the culprit and tried to verify my guess by disabling EXA. How could I do that? Simply renaming /usr/lib/xorg/modules/libexa.so did not work, the server gets a fatal error when it cannot locate the file. I googled around and understood that XAA is a predecessor of EXA. So I created the following conf file: Section Device Identifier Configured Video Device Driver ati Option AccelMethod XAA EndSection According the log the file was read without warnings and AccelMethod XAA was selected. But the Radeon driver still decided to load libexa.so. And no surprise the crash did occur again. Is EXA hardcoded in the drivers for this card or can I disable it somehow? -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 562418] Re: empty ddebs when dh_strip is called twice
$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04 LTS Release:10.04 Codename: lucid I believe I'm affected by the bug. When trying to debug Xorg I get the CRC mismatch warnings mentioned in the original bug description. So I thought I could help verify the correction. I understood that the problem was in pkg-create-dbgsym and the correction to this package should now be verified. The first thing I did was building xorg-server source package. That went fine after installing all the required tools and -dev packages. $ dpkg-buildpackage -rfakeroot -uc -us ... was the command I used. I still don't have pkg-create-dbgsym installed at all in this phase... $ apt-cache policy pkg-create-dbgsym pkg-create-dbgsym: Installed: (none) Candidate: 0.42 Version table: 0.42 0 500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages ..., but to my surprise the debug package... ../xserver-xorg-core-dbg_1.7.6-2ubuntu7_i386.deb ... has been generated by the normal build command I had guessed the the debug package would be created by using (tools inside) pkg-create-dbgsym. I do understand that launchpad is not a forum for questions, but if somebody could provide short instructions how to verify the correction I would be grateful. -- empty ddebs when dh_strip is called twice https://bugs.launchpad.net/bugs/562418 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 562418] Re: empty ddebs when dh_strip is called twice
Oops sorry, I guess the answer is in the bug description: Produces empty ddebs and broken debug links ... , when being built on Soyuz (not locally). Not sure what Soyuz stands for here, but I guess the problem affects only Ubuntu build infrastructure. If I build locally on my own machine I don't have the problem in the first place, so there is no way to verify the correction either? -- empty ddebs when dh_strip is called twice https://bugs.launchpad.net/bugs/562418 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 532845] Re: [Lucid] Option NoTrapSignals ignored when debugging xserver
In the current version xserver-xorg-core 2:1.7.6-2ubuntu7 Option NoTrapSignals works correctly. I use Kubuntu and I have created a file /usr/lib/X11/xorg.conf.d/01-server.conf to give the option (but there are of course many other possible places) In /var/log/Xorg.0.log you can see the difference when the server crashes. By default there is a backtrace, with the NoTrapSignals there is none. Also in gdb you can see the difference. After a SEGV you can continue without the option (the handlers will be run and then Xorg will exit). With NoTrapSignal you cannot continue after a SEGV, the process has already been terminated. -- [Lucid] Option NoTrapSignals ignored when debugging xserver https://bugs.launchpad.net/bugs/532845 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 575140] [NEW] [RV250] Kubuntu Lucid: Xorg gets SEGV
Public bug reported: Binary package hint: xserver-xorg-video-radeon In Lucid Kubuntu Xorg crashes from time to time. Before Lucid this machine had Intrepid Ubuntu and as far as I remember Xorg has not crashed for more than a year. According to /var/log/Xorg.0.log the call stack looks like this Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a116b] 1: /usr/bin/X (0x8048000+0x6789d) [0x80af89d] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x8d0410] 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x766000+0xb2039) [0x818039] 4: /usr/lib/xorg/modules/libexa.so (0x14c000+0x9490) [0x155490] 5: /usr/lib/xorg/modules/libexa.so (0x14c000+0x9558) [0x18] 6: /usr/bin/X (miCopyRegion+0x21b) [0x817598b] 7: /usr/bin/X (miDoCopy+0x44d) [0x8175ead] 8: /usr/lib/xorg/modules/libexa.so (0x14c000+0x7a4a) [0x153a4a] 9: /usr/bin/X (0x8048000+0xd9fa3) [0x8121fa3] 10: /usr/bin/X (0x8048000+0x2b1f5) [0x80731f5] 11: /usr/bin/X (0x8048000+0x2c877) [0x8074877] 12: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a] 13: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x17fbd6] 14: /usr/bin/X (0x8048000+0x1e961) [0x8066961] Segmentation fault at address (nil) Caught signal 11 (Segmentation fault). Server aborting I enabled apport, but if did never catch the Xorg SEGV (It caught other SEGVs so I don't know what I did wrong) I built matching debug packages (the ones from the repositories cannot be used because of https://bugs.launchpad.net/bugs/562418) but still the call stackin gdb is always useless: (gdb) bt full #0 __memcpy_ia32 () at ../sysdeps/i386/i686/multiarch/../memcpy.S:75 No locals. #1 0x in ?? () No symbol table info available. I will run apport-collect and attach a few log files. ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
apport information ** Tags added: apport-collected ** Description changed: Binary package hint: xserver-xorg-video-radeon In Lucid Kubuntu Xorg crashes from time to time. Before Lucid this machine had Intrepid Ubuntu and as far as I remember Xorg has not crashed for more than a year. According to /var/log/Xorg.0.log the call stack looks like this Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a116b] 1: /usr/bin/X (0x8048000+0x6789d) [0x80af89d] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x8d0410] 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x766000+0xb2039) [0x818039] 4: /usr/lib/xorg/modules/libexa.so (0x14c000+0x9490) [0x155490] 5: /usr/lib/xorg/modules/libexa.so (0x14c000+0x9558) [0x18] 6: /usr/bin/X (miCopyRegion+0x21b) [0x817598b] 7: /usr/bin/X (miDoCopy+0x44d) [0x8175ead] 8: /usr/lib/xorg/modules/libexa.so (0x14c000+0x7a4a) [0x153a4a] 9: /usr/bin/X (0x8048000+0xd9fa3) [0x8121fa3] 10: /usr/bin/X (0x8048000+0x2b1f5) [0x80731f5] 11: /usr/bin/X (0x8048000+0x2c877) [0x8074877] 12: /usr/bin/X (0x8048000+0x1ed7a) [0x8066d7a] 13: /lib/tls/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0x17fbd6] 14: /usr/bin/X (0x8048000+0x1e961) [0x8066961] Segmentation fault at address (nil) Caught signal 11 (Segmentation fault). Server aborting I enabled apport, but if did never catch the Xorg SEGV (It caught other SEGVs so I don't know what I did wrong) I built matching debug packages (the ones from the repositories cannot be used because of https://bugs.launchpad.net/bugs/562418) but still the call stackin gdb is always useless: (gdb) bt full #0 __memcpy_ia32 () at ../sysdeps/i386/i686/multiarch/../memcpy.S:75 No locals. #1 0x in ?? () No symbol table info available. I will run apport-collect and attach a few log files. + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + DkmsStatus: Error: [Errno 2] No such file or directory + GdmLog: + Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed with exit code 1: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory + QFileSystemWatcher: failed to add paths: /home/geuder/.config/ibus/bus + Bus::open: Can not get ibus-daemon's address. + IBusInputContext::createInputContext: no connection to ibus-daemon + cat: /var/log/gdm/:0.log: No such file or directory + GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory + GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory + InstallationMedia: Kubuntu 10.04 Lucid Lynx - Beta i386 (20100406.1) + Lsusb: + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: IBM 23734G2 + Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5 + PackageArchitecture: i386 + PccardctlIdent: + Socket 0: +no product info available + Socket 1: +no product info available + PccardctlStatus: + Socket 0: +no card + Socket 1: +no card + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=8567e5f2-2176-4d29-826d-7f6316bd60b2 ro quiet splash + ProcEnviron: + LANGUAGE= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 + Tags: lucid lucid + Uname: Linux 2.6.32-21-generic i686 + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + dmi.bios.date: 06/18/2007 + dmi.bios.vendor: IBM + dmi.bios.version: 1RETDRWW (3.23 ) + dmi.board.name: 23734G2 + dmi.board.vendor: IBM + dmi.board.version: Not Available + dmi.chassis.asset.tag: 995gz93 + dmi.chassis.type: 10 + dmi.chassis.vendor: IBM + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn23734G2:pvrThinkPadT40:rvnIBM:rn23734G2:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: + dmi.product.name: 23734G2 + dmi.product.version: ThinkPad T40 + dmi.sys.vendor: IBM + glxinfo: Error: [Errno 2] No such file or directory + system: + distro: Ubuntu + codename: lucid + architecture: i686 + kernel: 2.6.32-21-generic ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47793121/BootDmesg.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --
[Bug 575140] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47793125/CurrentDmesg.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Dependencies.txt
apport information ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47793132/Dependencies.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47793133/Lspci.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] PciDisplay.txt
apport information ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/47793134/PciDisplay.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47793135/ProcCpuinfo.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47793137/ProcInterrupts.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47793139/ProcModules.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/47793140/RelatedPackageVersions.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] UdevDb.txt
apport information ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47793141/UdevDb.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47793142/UdevLog.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] XorgLog.txt
apport information ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/47793143/XorgLog.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/47793144/XorgLogOld.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Xrandr.txt
apport information ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/47793145/Xrandr.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] setxkbmap.txt
apport information ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/47793146/setxkbmap.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/47793149/xdpyinfo.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] xkbcomp.txt
apport information ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/47793150/xkbcomp.txt -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
Forgot to mention: I did all investigations twice. First with the default Xorg trap handlers. After that with disabled Xorg trap handlers. The stack did no look different in gdb. (attachment 1/4, Xorg.log with trap handlers) ** Attachment added: Xorg.0.log.crash4trapped http://launchpadlibrarian.net/47793302/Xorg.0.log.crash4trapped -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
attachment 2/4, gdb session with trap handlers ** Attachment added: crash4trapped http://launchpadlibrarian.net/47793325/crash4trapped -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
attachment 3/4 Xorg.log without trap handlers ** Attachment added: Xorg.0.log.crash5noTrap http://launchpadlibrarian.net/47793361/Xorg.0.log.crash5noTrap -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 575140] Re: [RV250] Kubuntu Lucid: Xorg gets SEGV
attachment 4/4 gdb session log without trap handlers ** Attachment added: Xorg.0.log.crash5noTrap http://launchpadlibrarian.net/47793397/Xorg.0.log.crash5noTrap -- [RV250] Kubuntu Lucid: Xorg gets SEGV https://bugs.launchpad.net/bugs/575140 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 305586] Re: continuous [driAllocateTexture:636] even when idle
Hi Bryce, Tanks for your message. I'm about to leave to holidays and unfortunately I won't be able to investigate the issue right now. I should be be able to look into again in mid-August at the latest. -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 305586] Re: continuous [driAllocateTexture:636] even when idle
Sorry about the delay, too many things ongoing... Tried with Karmic Alpha 5 LiveCD. There are no continuous log writings with normal desktop effects. (Is logging active in LiveCD enviroment???) Double checked with my current Intrepid installation: continuous log writings do still occur as originally reported. -- continuous [driAllocateTexture:636] even when idle https://bugs.launchpad.net/bugs/305586 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 566317] Re: Lucid openjdk/icedtea cannot verify applet signature
As far as I understand Firefox and Java use different certificates. Is that correct? I know how to list certificates in Firefox, but I don't know how to do so in openjdk, I found the openjdk policy tool. Is that the right tool to use? Unfortunately I don't seem to be able to use it. It displays only empty lists. Please advice how to check, whether the certificate is in the certificate store. -- Lucid openjdk/icedtea cannot verify applet signature https://bugs.launchpad.net/bugs/566317 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
