[Bug 1209106] Re: system tray icon is next to launcher
It's not fixed for me in Qt 5.6 and Ubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209106 Title: system tray icon is next to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1209106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135789] Re: Shift Switcher: Odd re-focus behaviour switching between different windows spanning different desktops
** Changed in: compiz (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135789 Title: Shift Switcher: Odd re-focus behaviour switching between different windows spanning different desktops To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/135789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 560570] Re: fglrx fails to identify attached monitor, displays blank screen
I'm delighted to report that my instance of this bug was fixed by the latest released of the Catalyst drivers (10.7). I've tested this along with kernel 2.6.32-24 and Xserver 2:1.7.6-2ubuntu7.3 (all 32 bit). Compiz and GL in general work fine. Many thanks to the fglrx team for the fix Manuel -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Thanks for the hint Felix, as you suggested I downloaded the latest Catalyst, installed the generated packages (rel 8.741 in my case) and run aticonfig. Unfortunately it failed with the same behaviour as before. Is there any way to put the driver in any sort of 'verbose mode' so I can gather more information? Also, I didn't know that Catalyst could be installed in Ubuntu 10.04 after the removal of HAL place Space Odissey joke here. I will keep track of new releases and try them, rather than waiting for the ubuntu rollout as I was doing until now. Thanks again Manuel -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Indeed, I'm using a socket AM2 motherboard equipping the nForce 430 chipset (aka MCP51); to be more precise it is an Asus model A8MN-BR, marketed as Hematite-GL8E by HP. I presume Chris from post #13 has the same model. I'll check for other reports with this particular gpu/chipset combo to see whether we can amalgamate them in a master thread. Regards Manuel -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
After some digging, I've found ticket filed for this same issue in ATI's bugzilla: http://ati.cchtml.com/show_bug.cgi?id=1794 what I gathered from other thread references in the ticket is that the issues with MCP51 follow a regression in Catalyst 9.9 ** Bug watch added: ATi Linux Platform Bugs #1794 http://ati.cchtml.com/show_bug.cgi?id=1794 -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Just to report that the behaviour experienced after updating flgrx to the latest version (2:8.723.0ubuntu4) is identical (brief flash in Plymouth, then Xorg hangs with 100% CPU load on boot). The outputs for all logs all the same (nothing meaningful, AFAIU). I reiterate my offer to the developers to help retrieving any debugging information that may be relevant. Regards, Manuel -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
whoops; in comment #7 please s/adverts/averts/g -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 569475] [NEW] [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update
Public bug reported: After updating xorg-driver-fglrx to 2:8.723.1-0ubuntu3, the machine previously exhibiting the behaviour described in bug #560570 (running 10.04 beta) now fails to load libfglrxdrm.so and reverts to vesa. I presume this is an update error unrelated to the problem defined in the other bug (driver hang), thus I'm submitting it as a new one. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg-driver-fglrx 2:8.723.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: fglrx Architecture: i386 CheckboxSubmission: 33a6ff8ffd30f8bd1df95c0b208fcb87 CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d Date: Sat Apr 24 17:31:37 2010 DkmsStatus: fglrx, 8.723.1, 2.6.32-21-generic, i686: installed InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) MachineType: HP-Pavilion RR498AA-ABU s7720.uk ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=31fcdf37-c8d7-4b82-be95-905814e9201d ro quiet splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: fglrx-installer dmi.bios.date: 12/18/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.03 dmi.board.name: Hematite dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.03:bd12/18/2006:svnHP-Pavilion:pnRR498AA-ABUs7720.uk:pvr:rvnASUSTekComputerINC.:rnHematite:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: RR498AA-ABU s7720.uk dmi.sys.vendor: HP-Pavilion glxinfo: Error: command ['glxinfo'] failed with exit code -11: system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update https://bugs.launchpad.net/bugs/569475 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 569475] Re: [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/45203332/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/4520/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/45203334/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/45203335/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/45203336/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/45203337/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/45203338/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/45203339/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/45203340/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/45203341/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/45203342/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/45203343/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/45203344/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/45203345/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/45203346/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/45203347/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/45203348/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/45203349/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/45203350/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/45203351/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/45203352/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/45203353/xkbcomp.txt -- [HD5450] Cannot load module fglrxdrm after xorg-driver-fglrx 2:8.723.1-0ubuntu3 update https://bugs.launchpad.net/bugs/569475 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 568716] Re: [i855GM] playing any video causes a hard crash
*** This bug is a duplicate of bug 558633 *** https://bugs.launchpad.net/bugs/558633 I believe this bug matches the description of bug #558633, as xv also fails in my case ** This bug has been marked a duplicate of bug 558633 Xorg hangs up when trying to play video using xv on i855 -- [i855GM] playing any video causes a hard crash https://bugs.launchpad.net/bugs/568716 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
I filed the video playing problem described above as #568716, which I also believe is a duplicate of bug #558633 -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 568716] [NEW] [i855GM] playing any video causes a hard crash
Public bug reported: Binary package hint: xserver-xorg-video-intel Since installing 10.04 beta on a laptop equipped with a intel 855GM graphics card, I've been consistently experiencing the following: when trying to play video media in any format, using either Totem or vlc, X windows crashes and the screen goes into text mode, displaying some of the boot log; it then blinking for a couple of seconds before going entirely black. The machine utterly crashes, being completely irresponsible to any keyboard input or remote access via ssh. Once rebooted, the system logs for the session where the crash occurred are missing. I'm sorry I don't have any useful information regarding this crash beyond this description, but if you can think of any way I could collect some please let me know and I will try it. I doubt it would be related, but this machine requires re-enabling KMS after the last intel driver update (bug #565870); the crash playing video media has also occurred with all the previous intel driver releases in 10.04. It does not happen if I use a vesa driver. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 CurrentDmesg: [ 27.497737] ppdev: user-space parallel port driver [ 27.811042] lib80211_crypt: registered algorithm 'TKIP' [ 37.748033] eth1: no IPv6 routers present Date: Thu Apr 22 23:12:42 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: FUJITSU SIEMENS LIFEBOOK P7010 PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=94bd4efc-5540-4757-b489-0d0e7ed33d73 ro quiet splash i915.modeset=1 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel dmi.bios.date: 01/16/2006 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.28 dmi.board.name: FJNB189 dmi.board.vendor: FUJITSU dmi.board.version: CP248014-01 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: P70__ dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.28:bd01/16/2006:svnFUJITSUSIEMENS:pnLIFEBOOKP7010:pvr:rvnFUJITSU:rnFJNB189:rvrCP248014-01:cvnFUJITSUSIEMENS:ct10:cvrP70__: dmi.product.name: LIFEBOOK P7010 dmi.sys.vendor: FUJITSU SIEMENS system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- [i855GM] playing any video causes a hard crash https://bugs.launchpad.net/bugs/568716 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 568716] Re: [i855GM] playing any video causes a hard crash
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/45050445/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/45050446/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/45050447/Lspci.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/45050448/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/45050449/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/45050450/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/45050451/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/45050452/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/45050453/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/45050454/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/45050455/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/45050456/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/45050457/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/45050458/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/45050459/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/45050460/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/45050461/xkbcomp.txt -- [i855GM] playing any video causes a hard crash https://bugs.launchpad.net/bugs/568716 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
Hi bryce, Sorry for the inconvenience of the tarball; I had to report this bug collecting this information by hand, rather than using the ubuntu tool. The interface only allows 1 file at a time, thus this seemed the most convenient way to file a bug with all the relevant information already attached. ** Attachment added: contents of the original tarball http://launchpadlibrarian.net/44942000/lspci.out -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
** Attachment added: contents of the original tarball (syslog.1) http://launchpadlibrarian.net/44942006/syslog.1 -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
** Attachment added: contents of the original tarball (Xorg.1.conf) http://launchpadlibrarian.net/44942040/Xorg.1.log -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
With regards to enabling KMS, I was under the wrong impression that it was still enabled for the intel driver. Re-enabling it via i915.modeset=1 on the grub cmd line adverts the crash and X boots successfully. However DRI seems to have been deliberately disabled (see attached Xorg.conf), thus AIGLX instantiates the Mesa renderer. Also, playing any video in Totem or VLC player simply kills X. I don't know whether this is related to DRI, or to my update path from 9.10, where it used to work. I will try to find any information relevant on the logs to this last crash and append it later. I've also noticed that there is a master bug discussing the blacklisting of KMS for i855 (bug #511001). I will quote this particular bug in it. ** Attachment added: Xorg log for a KMS enabled boot http://launchpadlibrarian.net/44942636/Xorg.0.log -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 511001] Re: [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?)
Just to let you know that bug #565870 presents a case where disabling KMS actually causes X to crash on boot. -- [i855] Lucid Freeze shortly after X startup (needs KMS blacklist?) https://bugs.launchpad.net/bugs/511001 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 554814] Re: Network mounts timeout almost instantly
Bruno, Brian, I can confirm that after the last batch of updates (nautilus 1:2.30.0-0ubuntu4, and nautilus-share 0.7.2-12build1) I haven't been able to reproduce the problem a single time. Unfortunately that same update also broke my graphics driver, thus the delay. Thanks a lot for your help, Manuel ** Changed in: nautilus (Ubuntu) Status: Incomplete = Fix Released -- Network mounts timeout almost instantly https://bugs.launchpad.net/bugs/554814 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
For further information, I've tried disabling KMS both with nomodeset and i915.modeset = 0 on the grub cmd line, both of which caused no change. -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Thanks Gary, I'm afraid my problem doesn't have to do with multiple monitors as I only have 1 attached. I will try to get hold of a second one to test whether this is due to the monitor not being supported, but from the way it hangs X I doubt so (otherwise it should bail out with no screens found or a similar msg...). -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 565870] [NEW] Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
Public bug reported: Binary package hint: xserver-xorg-video-intel After updating to xserver-xorg-video-intel to version 2:2.9.1-3ubuntu4 on a laptop running Lucid Lynx beta, and rebooting, it crashed after showing the boot splash screen. The machine was not reachable via ssh, so I rebooted it in single user mode and found the following error msg in the Xorg log: Fatal server error: Failed to submit batchbuffer: Input/output error The laptop is using intel's 855GM integrated graphics, which used to work fine with the previous version of the driver. I've tried disabling KMS from the grub cmd line, but the result is the same. I'm enclosing the logs for the failed boot, as well as the lspci output. Please let me know if any other information could be of any help. Thanks Manuel ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Sat Apr 18 11:54:46 2010 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 565870] Re: Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error
** Attachment added: Xorg log, syslog of the failed boot, along with lspci's out http://launchpadlibrarian.net/44679235/logs_and_lspci.tar.gz -- Xorg crashes with 855GM on boot: Failed to submit batchbuffer: Input/output error https://bugs.launchpad.net/bugs/565870 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
As by my previous post, I don't think this is a duplicate of Bug#552644, since the latest update didn't fix it. It may be related, though. ** Description changed: After installing fglrx 2:8.721.0ubuntu10 on Lucid Lynx beta 1 and running 'aticonfig --initial', X (1.7.5) only displays a blank screen (system is running, can be ssh'ed in). This is the same effect experienced on a prior Karmic Koala installation with an older version of the driver. On the other hand, xorg's radeon driver runs properly (albeit without GL acceleration). When running 'aticonfig --query-monitor', I get the following output: Default Adapter - ATI Radeon HD 5400 Series # Connected monitors: none - Enabled monitors: none + Enabled monitors: none If I run xrandr when using xorg's radeon driver, the display is detected: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm -1680x1050 59.9*+ -1280x1024 75.0 60.0 -1152x864 75.0 -1024x768 75.0 60.0 -800x60075.0 60.3 -640x48075.0 59.9 -720x40070.1 + 1680x1050 59.9*+ + 1280x1024 75.0 60.0 + 1152x864 75.0 + 1024x768 75.0 60.0 + 800x60075.0 60.3 + 640x48075.0 59.9 + 720x40070.1 VGA-0 disconnected (normal left inverted right x axis y axis) The card is a Saphire Radeon HD 5450 (512 DDR3 model) with 3 outputs: DVI, HDMI and VGA. The DVI output is connected to a DELL 2005 FPW monitor, with 1680x1050 native resolution. Please advice if any other information is necessary. Regards Manuel ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.721-0ubuntu10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 CheckboxSubmission: 33a6ff8ffd30f8bd1df95c0b208fcb87 CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d Date: Sun Apr 11 10:13:51 2010 DkmsStatus: fglrx, 8.721, 2.6.32-19-generic, i686: installed InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) MachineType: HP-Pavilion RR498AA-ABU s7720.uk ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=31fcdf37-c8d7-4b82-be95-905814e9201d ro quiet splash ProcEnviron: - LANG=en_GB.utf8 - SHELL=/bin/bash + LANG=en_GB.utf8 + SHELL=/bin/bash SourcePackage: fglrx-installer dmi.bios.date: 12/18/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.03 dmi.board.name: Hematite dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.03:bd12/18/2006:svnHP-Pavilion:pnRR498AA-ABUs7720.uk:pvr:rvnASUSTekComputerINC.:rnHematite:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: RR498AA-ABU s7720.uk dmi.sys.vendor: HP-Pavilion glxinfo: Error: command ['glxinfo'] failed with exit code -11: system: - distro: Ubuntu - codename: lucid - architecture: i686 - kernel: 2.6.32-19-generic + distro: Ubuntu + codename: lucid + architecture: i686 + kernel: 2.6.32-19-generic ** This bug is no longer a duplicate of bug 552644 Lucid Lynx 64 bit nightly build hangs on boot -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
*** This bug is a duplicate of bug 552644 *** https://bugs.launchpad.net/bugs/552644 I'm afraid I wasn't as lucky as Nick and 2:8.723-0ubuntu1 didn't fix my problem. The only difference I could notice is that there is a slight flash of the screen when it hangs on the splash screen, while the image displayed remains the same. Out of the two scenarios that Felix described, the 1st is what is happening to me: Xorg is hanging, taking 100% of one core. I tried attaching to it from gdb (su) and get a PC or a stack trace but even the debugger hangs trying to do so. Please let me know if there is any other thing I could try that could be of help to diagnose this problem. I was hoping this problem would just be a matter of the display not being supported (because of the odd --query-monitor result). It now looks much more complicated. Regards Manuel -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 554814] Re: Network mounts timeout almost instantly
Hello Brian, In my case the base installation was Karmic. I had rebooted many times since. This is a problem I'm only experiencing with this particular computer (a slightly old centrino laptop); I've another system with the same 10.04 beta installation, having followed an identical upgrade path, and I never noticed this problem accessing the same network shares. I've attached the lspci output on the laptop in case it can be of any help. I've done some further testing on this machine. Using a wired or wireless connections makes no difference. Booting from the ubuntu live cd actually changes the behavior completely: samba mounts don't work, but rather than timing out inmediatly, they show a message saying that the resource is being mounted, click on the button below to cancel. This never concludes. On the other hand, sftp mounts do work without any problem, which they don't do on the upgraded Karmic (they fail in the same way as Samba). I know this is just blind shooting, but I hope it can give you some better clues that my 1st report. Thanks Manuel ** Attachment added: lspci output on the centrino laptop affected by this problem http://launchpadlibrarian.net/44076137/lspci.txt -- Network mounts timeout almost instantly https://bugs.launchpad.net/bugs/554814 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
Hello Felix, I'm enclosing the correct version of the log files, along with the xorg.conf file generated by aticonfig. There is a slight change of behaviour since updating gdm; now rather than stalling on a blank screen, X now stalls on the ubuntu 10.04 splash (screen white lettering on top of orange dots). I guess this is not rendered through fglrx, but please correct me if I'm wrong. As far as I can interpret the log files, I cannot see anything conspicuous apart from the driver mentioning that there is no device section for the pci dev at 1:00:1. This is the HDMI audio dev embedded in the card, as far as I can gather from the lspci output (also enclosed). The aticonfig --query-monitor output remains the same (not that it should change, I pressume) Hope this helps, and thanks a lot Manuel ** Attachment added: Log files and Xorg.conf when running X with fglrx http://launchpadlibrarian.net/43961837/logs_and_conf_with_fglrx.tar.gz -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] [NEW] fglrx fails to identify attached monitor, displays blank screen
Public bug reported: After installing fglrx 2:8.721.0ubuntu10 on Lucid Lynx beta 1 and running 'aticonfig --initial', X (1.7.5) only displays a blank screen (system is running, can be ssh'ed in). This is the same effect experienced on a prior Karmic Koala installation with an older version of the driver. On the other hand, xorg's radeon driver runs properly (albeit without GL acceleration). When running 'aticonfig --query-monitor', I get the following output: Default Adapter - ATI Radeon HD 5400 Series # Connected monitors: none Enabled monitors: none If I run xrandr when using xorg's radeon driver, the display is detected: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 1680 x 1680 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm 1680x1050 59.9*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.0 60.0 800x60075.0 60.3 640x48075.0 59.9 720x40070.1 VGA-0 disconnected (normal left inverted right x axis y axis) The card is a Saphire Radeon HD 5450 (512 DDR3 model) with 3 outputs: DVI, HDMI and VGA. The DVI output is connected to a DELL 2005 FPW monitor, with 1680x1050 native resolution. Please advice if any other information is necessary. Regards Manuel ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.721-0ubuntu10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: fglrx Architecture: i386 CheckboxSubmission: 33a6ff8ffd30f8bd1df95c0b208fcb87 CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d Date: Sun Apr 11 10:13:51 2010 DkmsStatus: fglrx, 8.721, 2.6.32-19-generic, i686: installed InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) MachineType: HP-Pavilion RR498AA-ABU s7720.uk ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=31fcdf37-c8d7-4b82-be95-905814e9201d ro quiet splash ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: fglrx-installer dmi.bios.date: 12/18/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.03 dmi.board.name: Hematite dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.03:bd12/18/2006:svnHP-Pavilion:pnRR498AA-ABUs7720.uk:pvr:rvnASUSTekComputerINC.:rnHematite:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: RR498AA-ABU s7720.uk dmi.sys.vendor: HP-Pavilion glxinfo: Error: command ['glxinfo'] failed with exit code -11: system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-19-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 560570] Re: fglrx fails to identify attached monitor, displays blank screen
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43764367/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/43764368/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43764370/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/43764371/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/43764372/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/43764373/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/43764374/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/43764375/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/43764376/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/43764377/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/43764378/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/43764379/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/43764380/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/43764381/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/43764382/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/43764383/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/43764384/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/43764385/xkbcomp.txt -- fglrx fails to identify attached monitor, displays blank screen https://bugs.launchpad.net/bugs/560570 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 554814] [NEW] Network mounts timeout almost instantly
Public bug reported: Binary package hint: nautilus Hello, I'm running Ubuntu 10.04 beta 1 upgraded over a 9.10 setup installed from CD. Since upgrading, I've noticed that when I try to access any of the shares on my home network, the connections seem to time out almost instantly, reporting the msg: Could not open location share : DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus). Other Linux boxes on the network can access those shares without a problem (both over samba and sftp). What is more striking, some times the 10.04 machine actually does manage to connect if I keep retrying fast enough (e.g. go to the network browser, that list the share, and press enter in 'Track Field' fashion). It seems that somehow the timeout value used to set up the connection to the share has been reduced to a fraction of its original value. I presume that this may have happened as a result of the update, since I managed to access the shares booting from a 10.04 CD. It may well be something specific to the upgrade of my previous setup, but I though I should let you know just in case it is more generalised. The version of nautilus I'm running is 1:2:30:0-0ubuntu3. Also, If you think this is a matter of that timeout value, it would be greatly appreciated if you let me know where it lives. Thanks a lot, Manuel ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Sat Apr 3 21:29:46 2010 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091020.3) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Network mounts timeout almost instantly https://bugs.launchpad.net/bugs/554814 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 554814] Re: Network mounts timeout almost instantly
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43005547/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/43005548/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/43005549/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/43005550/XsessionErrors.txt ** Attachment added: usr_lib_nautilus.txt http://launchpadlibrarian.net/43005551/usr_lib_nautilus.txt -- Network mounts timeout almost instantly https://bugs.launchpad.net/bugs/554814 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
