yeah -- I found it pretty much constant when I had the effects on. Am using gnome for a bit to see if it makes any difference, it maybe seems to happen a bit less often, but it still happens :( so it doesn't seem to be purely down to KDE (kubuntu developers will be pleased to hear (maybe! - sorry if it makes it worse))
will try to remeber to post kde.log when i switch back to kde for long enough for it to happen (or when I get On 15 May 2010 11:54, martin castle <marshc...@googlemail.com> wrote: > this is the output from .xsession-errors & .xsession-errors.1 --- a clean > startup and one that shutdown. Dont know if that will help any. Sorry - am > just a user so am at a bit of an anxious loss until someone can hold my hand > a little :/ > > > > > On 14 May 2010 21:54, James Sams <sams.ja...@gmail.com> wrote: > >> I'm getting a similar error in an upgraded kubuntu (from 9.10 to 10.04) >> on 64 bit hardware. There is nothing in Xorg.log files to indicate a >> whole X crash, but my ~/.xsession-error has similar output: >> >> XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" >> after 394169 requests (394168 known processed) with 3 events >> remaining. >> kxkb: Fatal IO error: client killed >> kded4: Fatal IO error: client killed >> kdeinit4: Fatal IO error: client killed >> kdeinit4: sending SIGHUP to children. >> . . . >> (followed by 150+ lines of application crashes, see attached >> xsession-errors for the full output). >> >> I just posted a thread at ubuntuforums.org (before I saw this) in case >> anyone wants to follow whatever discussion results there: >> http://ubuntuforums.org/showthread.php?p=9300254 (that thread also >> complains about the hundreds of thousands of lines of output from >> kmail/kontact and amarok that are needlessly being thrown into >> xsession-errors, which is probably not relevant to the crashing). >> >> $ lspci >> 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory >> Controller Hub (rev 07) >> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series >> Chipset Integrated Graphics Controller (rev 07) >> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset >> Integrated Graphics Controller (rev 07) >> 00:03.0 Communication controller: Intel Corporation Mobile 4 Series >> Chipset MEI Controller (rev 07) >> 00:03.3 Serial controller: Intel Corporation Mobile 4 Series Chipset AMT >> SOL Redirection (rev 07) >> 00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network >> Connection (rev 03) >> 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #4 (rev 03) >> 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #5 (rev 03) >> 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #6 (rev 03) >> 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >> Controller #2 (rev 03) >> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio >> Controller (rev 03) >> 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >> Port 1 (rev 03) >> 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >> Port 2 (rev 03) >> 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express >> Port 4 (rev 03) >> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #1 (rev 03) >> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #2 (rev 03) >> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI >> Controller #3 (rev 03) >> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI >> Controller #1 (rev 03) >> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) >> 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller >> (rev 03) >> 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller >> (rev 03) >> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller >> (rev 03) >> 03:00.0 Network controller: Intel Corporation Wireless WiFi Link 5300 >> >> >> >> ** Attachment added: ".xsession-errors following the described crash" >> http://launchpadlibrarian.net/48464424/xcrash.3 >> >> -- >> X server crashes randomly >> https://bugs.launchpad.net/bugs/573957 >> You received this bug notification because you are a direct subscriber >> of the bug. >> >> Status in “xorg-server” package in Ubuntu: New >> >> Bug description: >> Binary package hint: xorg >> >> After upgrade to Lucid, the X server started to crash, however I fail to >> detect any pattern. It can occur only after hours of use or quite soon after >> logging in, thus I guess it's pretty random. >> >> After the crash, the screen blinks (with black screen and terminal output) >> for a few times and then GDM restarts and I'm able to log back in. >> >> Please note that I'm not using a standard Ubuntu kernel due to a problem >> I've had since Karmic: in that case, X wouldn't even start. However, even >> with a modified kernel, I experienced no problems while using Karmic. >> >> A sample output of .xsession following the crash : >> >> (gnome-terminal:1799): Gtk-CRITICAL **: gtk_accel_map_unlock_path: >> assertion `entry != NULL && entry->lock_count > 0' failed >> gnome-session[965]: WARNING: Detected that screensaver has left the bus >> gnome-settings-daemon: Fatal IO error 11 (Resource temporarily >> unavailable) on X server :0.0. >> Window manager warning: Fatal IO error 104 (Connection reset by peer) on >> display ':0.0'. >> gnome-session: Fatal IO error 104 (Connection reset by peer) on X server >> :0.0. >> polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource >> temporarily unavailable) on X server :0.0. >> nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server >> :0.0. >> gdu-notification-daemon: Fatal IO error 11 (Resource temporarily >> unavailable) on X server :0.0. >> gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) >> on X server :0.0. >> gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X >> server :0.0. >> The application 'gksu' lost its connection to the display :0.0; >> most likely the X server was shut down or you killed/destroyed >> the application. >> >> Please ask if you need any further information. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 10.04 >> Package: xorg 1:7.5+5ubuntu1 >> Uname: Linux 2.6.34-020634rc6-generic i686 >> Architecture: i386 >> Date: Sun May 2 21:58:42 2010 >> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 >> (20100427.1) >> ProcEnviron: >> LANGUAGE=en >> LANG=en_GB.utf8 >> SHELL=/bin/bash >> SourcePackage: xorg >> system: >> distro: Ubuntu >> codename: lucid >> architecture: i686 >> kernel: 2.6.34-020634rc6-generic >> >> To unsubscribe from this bug, go to: >> >> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/573957/+subscribe >> > > -- X server crashes randomly https://bugs.launchpad.net/bugs/573957 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
