[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> I'd really suggest to rank it as a stop-ship bug, please! Jaunty already shipped, and, to be honest, there's nothing in this bug that suggests to me that it should have stopped the shipment of either Ubuntu or Kubuntu this past month. (I'm affected by it, and while it's a bit of a nuisance in Kate, it's not mission-critical.) > what can all the affected users do to help isolate the root cause of this bug Wait for two weeks and live with the graphical nuisance until then. As I understand it, this is a very touchy bug that's been resolved in KDE 4.3, which will have its first beta release on May 12. Kubuntu Karmic will then have its first alpha release on May 14th, so presumably there's going to be some rapid packaging going on at the time. > How can a bug with 10 duplicates stay in "undecided" so long? Well, just to recap, this is a bug that doesn't affect most people (and we're not sure why it affects the people it does). It's apparently upstream of KDE, even, much less Kubuntu; but it's also claimed by Intel to be downstream of them; and meanwhile the KDE folks are saying "We said no Qt 4.5 with KDE 4.2 -- Kubuntu didn't listen." We can't narrow down where it goes or where the problem is occurring, because the problem doesn't create crash logs of any sort. And it's already got a fix some time in the near future (KDE 4.3), and it was only discovered shortly before the release date. And it's got a supplemental fix which works if it doesn't introduce further bugs into the system. I think that all of these contribute to this bug report staying in undecided. We don't know where to start looking for the problem, even, and the problem will hopefully be solved soon anyway. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338669] Re: (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset
> How can you say that you cannot narrow down the possible culprits? Because the .tar.gz of the qt4.5 source is 100 MB in size. If we had a crash report saying "there was a segmentation fault right here," we could maybe figure out where in that beast of a source code it was -- but just asking "what line in the KDE 4.2 source is calling the wrong function in the Qt 4.5 source which is also misusing EXA when it repaints the screen" is a question that can't be answered without much more information than the problem itself provides. > So, waiting for an yet unstable alpha release is the solution? I'm not saying that you should jump on the Karmic alpha -- once people have solid Karmic-4.3 integration, there will almost surely be a .deb posted to the jaunty-backports repository. > How about proposing KDE 4.2 compiled against qt4.4 (shipped by default) and package qt4.5 as an alternative with a BIG FAT WARNING? I haven't seen anything preventing such a strategy on a release-update. You can get KDE 4.2 + Qt 4.4 + Kubuntu! However, you will have to use Intrepid to do it. As jaunty-backports will probably eventually contain KDE 4.3, so too the intrepid-backports repository contains, right now, KDE 4.2. And Intrepid has not been retrofitted to use Qt 4.5 -- 4.5 is strictly Jaunty and up. > According to this changelog this bug might have already been solved in qt. I don't see anything in that changelog to suggest a fix for anything EXA-specific, much less rendering artifacts. What line are you referring to, specifically? (I'm not really a Kubuntu dev, so don't take my word as gospel here. The Debian unstable repository (sid) contains a .deb for Qt 4.5.1, and ScottK on IRC says that the current plan is to merge this into Karmic, but keep it out of Jaunty. It might get backported later; I don't know.) > Which KDE bug are you referring to? I was referring to this comment (comment #21) by Aaron J. Seigo: https://bugs.kde.org/show_bug.cgi?id=187356#c21 > Are you referring to the KDE 4.3 fix? What if the bug is really in Qt 4.5? I was referring to using UXA. (More specifically, since it looks like nobody has placed these instructions explicitly here, adding the line [ Option"AccelMethod""UXA"] to the "Device" section in /etc/X11/xorg.conf .) So far UXA has been working for me, but the problem was much less prevalent for me than it apparently is for you. >using a "better" version of Qt within Jaunty (perhaps using an optional repository?) Jaunty has already shipped with Qt 4.5, and my amateurish attempts to simulate a downgrade to Qt 4.4 with aptitude and the Intrepid repositories have not looked promising. I don't think anyone can provide you with a PPA (an optional repository) that would solve the multitude of dependencies. Everything (?) in Kubuntu Jaunty was built with the idea, "okay, we're releasing a Qt 4.5 operating system this April." Much of it breaks when you try to pull the tablecloth out from under it. If you want KDE 4.2 + Kubuntu, and you cannot enable UXA for some reason or another (or if UXA doesn't solve the problem), then it looks like your only option is Intrepid at the moment. Karmic may offer a backport of KDE 4.3 in a couple weeks if you're willing to wait. -- (Needs UXA) painting artifacts after qt4.5 upgrade on intel chipset https://bugs.launchpad.net/bugs/338669 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 313298] [NEW] NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card
Public bug reported: Binary package hint: network-manager The Netgear WG311v2 runs off of the TI ACX chipsets, which have a native Linux driver that comes preinstalled in Ubuntu and Kubuntu. Unfortunately, it doesn't Just Work out-of-the-box, but I can't try to debug it just yet, because it causes NetworkManager to fail rather catastrophically. A call to top -p$(pgrep NetworkManager) reveals that, when the card is plugged in, NetworkManager uses 50-60% of my old-ish Athlon64 4000+ processor, and its memory footprint (both virtual and resident) increases by roughly 100 MB per minute or so. So, I quickly run into a situation where all of the actions of KDE suddenly freeze, and I have to turn the computer off manually, via the front switch. (The crash apparently happens even if I pkill the NetworkManager utility, which I found quite bizarre. The crash doesn't occur if I physically remove the wireless card and then boot into Kubuntu normally.) The system is mostly a default Kubuntu Intrepid x64 install, but I used apt-get to update the network-manager package to the latest version (0.7~~svn20081018t105859-0ubuntu1.8.10.1), as well as to install Wine and its dependencies. Everything else is just as the CD provided it. Since the wireless card isn't working, I've connected an ethernet cable directly to my wireless router to download updates, post this report, etc. My /var/log/syslog contains entries like: Jan 2 12:37:38 tiamat NetworkManager: nm_error_monitoring_device_link_state(): error monitoring wired ethernet link state: error occurred while waiting for data on socket Jan 2 12:37:57 tiamat last message repeated 211513 times But these only occur when the wireless card is installed. NetworkManager has no problem monitoring eth0 (nor does it try to repeat itself indefinitely) when the wireless card is out. If this is a problem with the ACX drivers, then I could maybe try to blacklist them and replace them with the ndiswrapped Windows XP drivers. The WG311v2 has, shall we say, a poor review history on ubuntuforums.org. But I'm reporting this as a bug with NetworkManager because NetworkManager is the one that memleaks and hogs cpu. (NetworkManager does not do this in a fresh install of Debian. However, that might be because Debian refuses to acknowledge that a wlan0 exists in the first place. This happened no matter what I tried to do with ndiswrapper, which seemed rather buggy on Debian. At least Kubuntu recognizes that wlan0 exists, even if it crashes the entire computer with that observation.) What other info can I send to you guys? (Keep in mind that, if you want me to generate output when the wireless card is installed, I have to be able to generate it in under 5-10 minutes, if I want to save myself from the crash. Needless to say, I'm not running with the wireless card installed by default.) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NetworkManager uses 60% cpu and leaks mem like crazy with a WG311v2 wireless card https://bugs.launchpad.net/bugs/313298 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 349020] [NEW] garbage pixels fill up dynamic content areas in KDE 4.2
Public bug reported: Some dynamic content areas -- the ones that come to mind are in Quassel and Kate -- are filled up with garbage pixels that are (as far as I can tell) grabbed from the rest of the screen at erratic times in KDE 4.2. Quassel is the easy place to generate this bug: usually (but not always!), if I click on the Quassel window to bring it to the foreground when it is behind another window, some of the area covered by the original window is filled with garbage apparently taken from various places on the rest of the screen. If a chat room is active, it may also happen when another window is dragged over Quassel, but that does not always happen. Once the garbage pixels exist, they stay constant, presumably cached by something-or-other. Except for this fact: like I said, dragging a window over Quassel doesn't always trigger the bug; but usually, if there are already garbage pixels, window dragging can enlarge the area where they occur and sometimes even change their contents. Clearing the garbage pixels to "try again" (i.e., try to replicate them under a similar scenario) is easy: just resize the window, and the garbage pixels disappear when the window gets redrawn. Kate is much more finicky, but will sometimes fill up with garbage pixels when being scrolled with the cursor keys. (This is very random and hard to reproduce consistently -- sometimes it happens, sometimes it doesn't.) Notably, disabling or enabling K > System Settings > Desktop > Enable desktop effects does not change whether this bug is occurring or not. Also notably, I'm using an integrated graphics card on my laptop to do these, so this is probably not related to any outstanding graphics driver bugs. My overall setup is a widescreen tablet PC with integrated graphics, running the latest Kubuntu Jaunty alpha. All packages were up to date as of this morning, and this bug has been occurring for much much longer than that. A screen capture of Quassel during one of these bugs is attached; I'll also post a reply with a screen capture of the same in Kate. (Yes, apparently GIMP can screen-capture it!) ** Affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
An example of it occurring in Kate, too: ** Attachment added: "kdebug.jpg" http://launchpadlibrarian.net/24365545/kdebug.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 349020] Re: garbage pixels fill up dynamic content areas in KDE 4.2
** Attachment added: "kdebug_q.jpg" http://launchpadlibrarian.net/24365523/kdebug_q.jpg -- garbage pixels fill up dynamic content areas in KDE 4.2 https://bugs.launchpad.net/bugs/349020 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
ujean: have you tried just installing wacom-tools from the repositories? I'm really not sure that it's necessary to recompile. If it is necessary to compile, well, those three messages look like compiler warnings but not errors. Does the compiling process finish despite them? You might be still be able to copy wacom.so over to where it needs to go. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
Timo: There may still be a need to have them (the xorg.conf sections), as far as I can tell. In particular, the [xsetwacom set] command requires a device name, which is configured in xorg.conf. As far as I know, there's no documentation on the default name for the tablet autoconfiguration. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 358643] Re: Xorg crashed with SIGSEGV in DeleteInputDeviceRequest()
After reading the above posts by mu3en and having a little extra time to fiddle with these things, I can confirm that the xserver-xorg-core deb in Timo's PPA (more specifically, the amd64 one for me) fixes the problem on my tablet PC -- I can now go back to the old xorg.conf (see bug # 359133 -- in particular, I also use a /dev/ttyS0 module). I didn't have to recompile linuxwacom -- it just worked with the wacom- tools package in the repos (aptitude shows it as 0.8.2.2-0ubuntu2). Hurray! Timo, you rock! Also, xsetwacom apparently has a "list dev" option that I didn't know about before, but when X autoconfigures the tablet, it doesn't create any entries under there. Maybe I shouldn't worry about that, though -- if you're setting up manual tablet rotation with xsetwacom, you should probably expect to have to manually reconfigure your tablet in X too. -- Xorg crashed with SIGSEGV in DeleteInputDeviceRequest() https://bugs.launchpad.net/bugs/358643 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
Jasper: did you already try the fix from bug # 358643 ? It's important if we find out that this fix isn't universal, and you didn't say anything about it. Just to recap that fix here, Timo Aaltonen has a personal package archive with patched .deb packages of xserver-xorg-core, which are available at this URL: http://ppa.launchpad.net/tjaalton/ppa/ubuntu/pool/main/x/xorg-server/ For at least two of us, telling dpkg to install that .deb over our current version of xserver-xorg-core has fixed this bug. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] [NEW] GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
Public bug reported: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. This suggests that maybe something with the wacom driver is to blame? I don't know, and at this point I'm lost. Probably the only helpful thing I can really tell you is that it was a recent package that broke the setup; firefox used to run just fine. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25213807/Dependencies.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25213809/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25213810/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25213811/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25213812/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25213813/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25213814/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25213815/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25213816/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25213817/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25213818/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25213819/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25213820/xkbcomp.txt -- GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
** Summary changed: - GTK apps cause Xorg to segfault with error 4 under Kubuntu Jaunty + Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty ** Description changed: Binary package hint: xorg In the latest aptitude full-upgrade I did (running Kubuntu Jaunty) there were a couple of packages that said they were "recommended but would not be installed." -- I more or less shrugged these off, but I forgot to write them down. After the computer rebooted, a whole mess of things happened: the biggest one is that now, whenever I start any GTK-based app, (tested with GIMP, Firefox, and CellWriter) X segfaults. Since the bug is trivially reproducable, I've recorded the /var/log/syslog messages on four separate occasions after deliberately triggering this bug. They all have these lines in common: Xorg[*]: segfault at d0 ip 00496786 sp 7fff***0 error 4 in Xorg[40+1c3000] [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 0 kdm[]: X server for display :0 terminated unexpectedly I have also seen these three lines erratically appear; they suggestively implicate Qt 4.5, but it may be that Qt is just noticing the X segfault: python[17124]: segfault at 30 ip 7fc440976bb5 sp 7fff4a0e38f8 error 4 in libQtCore.so.4.5.0[7fc440807000+24] ksmserver[17070]: segfault at 8 ip 7f2045afbe2b sp 7f203b28f648 error 4 in libQtDBus.so.4.5.0[7f2045ab7000+74000] ksmserver[19042]: segfault at 8 ip 7f4c24ecde2b sp 7f4c1a661648 error 4 in libQtDBus.so.4.5.0[7f4c24e89000+74000] There is also a backtrace recorded in /var/logs/Xorg.0.log.old file, which looks like this: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f2d63995040] 3: /usr/lib/xorg/modules/input//wacom_drv.so [0x7f2d61795035] 4: /usr/bin/X(ActivateDevice+0x3e) [0x447a8e] 5: /usr/bin/X(OpenInputDevice+0x10) [0x4968e0] 6: /usr/bin/X(ProcXOpenDevice+0xa3) [0x545823] 7: /usr/bin/X(Dispatch+0x364) [0x44e304] 8: /usr/bin/X(main+0x3bd) [0x433d8d] 9: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f2d639805a6] 10: /usr/bin/X [0x433219] Saw signal 11. Server aborting. - This suggests that maybe something with the wacom driver is to blame? - - I don't know, and at this point I'm lost. Probably the only helpful - thing I can really tell you is that it was a recent package that broke - the setup; firefox used to run just fine. + An upcoming comment will discuss this more in-depth. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: xorg 1:7.4~5ubuntu18 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersion: Linux version 2.6.28-11-generic (bui...@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 SourcePackage: xorg Uname: Linux 2.6.28-11-generic x86_64 -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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 359133] Re: Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty
I don't see a way to refile this post under a different project, but it probably belongs under xserver-xorg and possibly under xserver-xorg- input-wacom. I've resolved my personal issue to my own satisfaction, although I'm not sure that xorg should segfault on this particular issue. The key to the puzzle came with a more extensive problem description in apport, which I tried to submit but didn't succeed. In any case, part of the apport response discussed that it was trying to remove the Wacom device. That convinced me that Qt, which I was previously staring very hard at, was not the problem and that I should check on the Wacom settings in my xorg.conf file. When those were removed, two things happened: (1) GTK programs did indeed start again; (2) my tablet input device still worked, as if by magic. (It didn't before I put those lines there!) So, to place the bug more narrowly: there were some recent patches in xserver-xorg-input-wacom. I believe that one of these patches automatically configures the tablet device for you -- a process that previously had to be done manually in xorg.conf. If the xorg.conf file specifies a manual configuration, apparently everything goes smooth for most applications, but GTK for some reason tries to remove the device and/or create a new one -- the details aren't clear to me. When the device gets removed and then recreated, Xorg apparently gets confused and segfaults. I have the feeling that not all of that is right, but in any case: something weird is happening that probably shouldn't be happening, even though the userbase it affects is probably a fringe case. -- Wacom + GTK + old configuration causes Xorg to segfault with error 4 under Kubuntu Jaunty https://bugs.launchpad.net/bugs/359133 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