[Ubuntu-x-swat] [Bug 1724335] [NEW] Keyboard 'alternative switch to next source' layout option is not honoured by X applications run by XWayland
Public bug reported: I have "Alternative switch to next source" option set to "Right Alt (while pressed)" in "Input source options" within "Region & Language" in settings. I use US kbd layout, but often I need my national characters, so I use the "while pressed" solution since years, it's much faster than always changing KBD layouts. Now, in Ubuntu 17.10 this still works perfectly in applications like gnome-terminal. However I have the suspect it never works now in any X applications (like: firefox, xterm, and few of them what I've tried). So I have the feeling that "legacy" X apps run by Xwayland does not honour the input settings properly, which is a problem for me to using the desktop now in this form. Surely, it is only my guess that it's the problem of Xwayland now, what runs the X apps on "top of" wayland. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 20:12:31 2017 DistUpgraded: 2017-06-20 12:44:34,135 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.28, 4.13.0-15-generic, x86_64: installed virtualbox, 5.1.28, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Richland [Radeon HD 8470D] [1849:9996] InstallationDate: Installed on 2015-07-10 (829 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash scsi_mod.use_blk_mq=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-06-20 (119 days ago) dmi.bios.date: 02/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd02/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 21 14:44:53 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: radeon ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1724335 Title: Keyboard 'alternative switch to next source' layout option is not honoured by X applications run by XWayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724335/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use xrandr to set the correct resolution. This is not an option with wayland though, so I cannot even use my desktop normally, I guess I should downgrade ubuntu, since no way to use the machine in a sane way anymore, and not so much other solution I could find :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Ok, I've found a workaround, to specify this kernel parameter in GRUB: video=VGA-1:1920x1080@60 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use xrandr to set the correct resolution. This is not an option with wayland though, so I cannot even use my desktop normally, I guess I should downgrade ubuntu, since no way to use the machine in a sane way anymore, and not so much other solution I could find :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Please tell me, if you need further information of some kind of co- operation to resolve this issue. Thanks a lot, in advance. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Another interesting finding with grep'ing around in /var/log for VGA-1: root@vega:/var/log# grep VGA-1 syslog May 4 14:27:10 vega unity-settings-[1644]: unable to get EDID for xrandr-VGA-1: unable to get EDID for output And maybe the even more interesing part in /var/log/gpu-manager.log log_file: /var/log/gpu-manager.log last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot can't access /run/u-d-c-nvidia-was-loaded file can't access /run/u-d-c-fglrx-was-loaded file Looking for fglrx modules in /lib/modules/4.10.0-21-generic/updates/dkms Looking for nvidia modules in /lib/modules/4.10.0-21-generic/updates/dkms Is nvidia loaded? no Was nvidia unloaded? no Is nvidia blacklisted? no Is fglrx loaded? no Was fglrx unloaded? no Is fglrx blacklisted? no Is intel loaded? yes Is radeon loaded? no Is radeon blacklisted? no Is amdgpu loaded? no Is amdgpu blacklisted? no Is nouveau loaded? no Is nouveau blacklisted? no Is fglrx kernel module available? no Is nvidia kernel module available? no Vendor/Device Id: 8086:152 BusID "PCI:0@0:2:0" Is boot vga? yes Skipping "/dev/dri/card0", driven by "i915" Skipping "/dev/dri/card0", driven by "i915" Skipping "/dev/dri/card0", driven by "i915" Found "/dev/dri/card0", driven by "i915" output 0: card0-VGA-1 Number of connected outputs for /dev/dri/card0: 1 Does it require offloading? yes last cards number = 1 Has amd? no Has intel? yes Has nvidia? no How many cards? 1 Has the system changed? No main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf Current core alternative: (null) Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf Is nvidia enabled? no Is nvidia egl enabled? no Is fglrx enabled? no Is mesa enabled? yes Is mesa egl enabled? yes Is pxpress enabled? no Is prime enabled? no Is prime egl enabled? no Is nvidia available? no Is nvidia egl available? no Is fglrx available? no Is fglrx-core available? no Is mesa available? yes Is mesa egl available? yes Is pxpress available? no Is prime available? no Is prime egl available? no Single card detected Nothing to do No change - nothing to do -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
I'm really not an xrandr / etc wizard, but what looks strange for me, that it seems something reports "VGA-1" when all the examples on the Net (and in xrandr man page) mentions "VGA". Even in Xorg.log: root@vega:~# fgrep VGA /var/log/Xorg.0.log [25.034] (II) modeset(0): Output VGA-1 has no monitor section [25.037] (II) modeset(0): EDID for output VGA-1 [25.037] (II) modeset(0): Printing probed modes for output VGA-1 [25.037] (II) modeset(0): Output VGA-1 connected [25.037] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1688253 Title: Wrong resolution, and "unknown monitor" since upgraded to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1688253/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1688253] [NEW] Wrong resolution, and "unknown monitor" since upgraded to 17.04
Public bug reported:
I've never had a problem like this before. Now, after upgraded to Ubuntu
17.04 it was already strange to see the boot logo in a kind of low and
fuzzy resolution. And it remained for the LightDM login screen, also for
the desktop after logged on. System setting -> Display reports "Unknown
Display". System settings -> Software & updates -> Additional drivers
shows title "Unknown: Unknown" though after that "Using Processor
microcode firmware for Intel CPUs from intel-microcode" is active. I
could "work the problem around" (see the end of this writing) but it's
really ugly that I need to run a script every time, when it always
worked well on the same machine before this Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis)
0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection (this
monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088 1120
-hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my script
(I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock 67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Ubuntu-x-swat] [Bug 1562398] [NEW] Xorg freeze on SDL2 using full screen with wine with windows program
Public bug reported: My problem seems to be rather specific. I develop an emulator for a 8 bit computer with SDL2, capable of running on Linux and Windows. I use cross-compiling with mingw for Windows, and wine to test it. It seems the problem occurs when I try the windows build, with full screen mode. When I try to switch full screen off, I get back my desktop, and mouse can be moved, however I can't simply do anything with keyboard and neither with mouse anymore. If I press power-off button of my notebook, system seems to shuts down though, but I need to do that, as it's not possible to use my desktop anymore. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 26 22:03:58 2016 DistUpgraded: 2015-10-18 23:18:25,282 INFO cache.commit() DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-30-generic, i686: installed virtualbox, 5.0.14, 4.2.0-34-generic, i686: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 (1484 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to wily on 2015-10-18 (159 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Mar 26 20:31:35 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 freeze i386 ubuntu wily -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1562398 Title: Xorg freeze on SDL2 using full screen with wine with windows program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1562398/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1340964] Re: Xorg crashed with SIGABRT in _XSERVTransClose()
I have this bug only with systemd, choosing upstart everything is OK, again please read my comment at bug 1434396 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1340964 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1340964] Re: Xorg crashed with SIGABRT in _XSERVTransClose()
I have a problem described in bug 1434396 that is: Xserver does not start on boot, and the low graphics mode dialog is presented instead, though if I exit to console and start lightdm service by hand it works. After logging in, bug report dialog on X crash appears and that brings me to this report. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1340964 Title: Xorg crashed with SIGABRT in _XSERVTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
The dialog box saying low graphics mode allows me to exit to console, if I do that, I can see on console 7 (ALT+F7): [FAILED] Failed to start Light Display Manager. See systemctl status lightdm.service for details. [DEPEND] Dependency failed for Graphical Interface. Entering the suggested command: lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled) Active: failed (Result: resources) since Sun 2015-03-22 11:57:36 CET; 4min 44s ago Docs: man:lightdm(1) Process: 982 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Process: 978 ExecStartPre=/bin/sh -c [ $(basename $(cat /etc/X11/default-display-manager 2/dev/null)) = lightdm ] (code=exited, status=0/SUCCESS) Main PID: 982 (code=exited, status=1/FAILURE) Mar 22 11:57:35 antares systemd[1]: Unit lightdm.service entered failed state. Mar 22 11:57:35 antares systemd[1]: lightdm.service failed. Mar 22 11:57:36 antares systemd[1]: lightdm.service holdoff time over, scheduling restart. Mar 22 11:57:36 antares systemd[1]: lightdm.service failed to schedule restart job: Transaction is destructive. Mar 22 11:57:36 antares systemd[1]: Unit lightdm.service entered failed state. Mar 22 11:57:36 antares systemd[1]: lightdm.service failed. issuing command service lightdm start starts lightdm though, and I can login and work. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
** Package changed: xorg (Ubuntu) = lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1434396/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1434396] [NEW] Xserver does not start, on boot (low-graphics mode)
Public bug reported: After upgrading to (32bit) vivid I hadn't got any problem, but since a day (daily upgraded) booting results in a dialog saying low graphics mode and a dialog window about this. Choosing running in default mode causes to boot splash to be shown forever. if I choose exit to console, log in then service stop then start for lightdm, it works then though. Maybe is not Xserver bug, but the new init system (systemd) race condition of starting things, or such? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 20 07:35:37 2015 DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationDate: Installed on 2012-03-03 ( days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Mar 20 07:25:51 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start, on boot (low-graphics mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1434396] Re: Xserver does not start, on boot (low-graphics mode)
By the way I am not sure if it's related: on booting backlight of the LCD (of the notebook) is always set to minimal during the boot at one moment, barely visible (but surely I can use the keyboard Fn + corresponding key to increase to a readable level). It was also the situation with the previous ubuntu version ... Also I am using an external monitor through the VGA connector connected, till logging in, the login is presented on the notbook's own LCD (with that dimmed backlight ...) the external monitor has no signal at all till the login screen appears after that only an ubuntu logo is shown in front of my background picture. After logging in, the configured situation works, ie the internal LCD of the notebook goes off, and I can use the external monitor. In case of shutting the system down, the notebook's internal LCD turns on with that very dimmed backlight till the machine powers off completely. However this behaviour was more or less the same, now my current problem that X doesn't seem to start at all, which was not the case before. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
** Summary changed: - Xserver does not start, on boot (low-graphics mode) + Xserver does not start on boot (low-graphics mode) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1416999] [NEW] After a while X becomes quite slow
Public bug reported: I am not sure if it's bug of xserver-xorg or other package. The problem: after reboot everything seems to be fine, scrolling within windows, moving windows are smooth and fast. After some time however everything becomes quite slow, eg output in gnome-terminal which made the content scrolling can bee seen when refreshing, even an editor (like geany) is slow when you move the cursor, moving windows is also slow and jerky. A reboot (or logging out then in, it seems) cures the problem but after a while problem return. I am not sure if it's related, but /var/log/Xorg.0.log is full of lines like this: [191341.166] (II) intel(0): switch to mode 1920x1080@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none For example now I have 107 lines like this. I am using daily updated Ubuntu 14.10 (32 bit), and it's a problem experienced since some weeks (I can't tell more precisely, sorry), I haven't seen this before, ever. Also, Xorg seems to use quite lot of CPU (according to top), at least more than usual, but it's hard to tell exact numbers. Maybe related: I usually don't switch my computer off. Compiz seems to use more and more memory, according the top it used something like 4% (4Gbyte of RAM) but I also seend something like 22% after some days of uptime. Closing all windows on the desktop seems not to help so it's more like some kind of memory leaking? The only suspect log lines in the kernel log (dmesg): [ 13.493187] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 13.493198] [drm] Driver supports precise vblank timestamp query. [ 13.501309] [drm] Wrong MCH_SSKPD value: 0x20100406 [ 13.501311] [drm] This can cause pipe underruns and display issues. [ 13.501312] [drm] Please upgrade your BIOS to fix this. [ 13.940404] fbcon: inteldrmfb (fb0) is primary device [ 13.940502] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 13.981857] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 14.802073] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 22.099955] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A [ 22.099959] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun However no screen corruption etc can be seen, just slowness after a while. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 2 09:15:43 2015 DistUpgraded: 2014-10-24 21:56:36,231 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-05-08 (270 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lsusb: Bus 002 Device 003: ID 1267:0213 Logic3 / SpectraVideo plc Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-24 (100 days ago) dmi.bios.date: 02/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Ubuntu-x-swat] [Bug 1157585] [NEW] [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x01000000
Public bug reported: This (or these kind ...) of bugs sometimes happens. No exact information how to trigger, but it seems some kind of rapid change between workspaces can help to trigger it. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu1 Architecture: i386 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 19 18:08:19 2013 DistUpgraded: 2013-03-05 12:13:09,827 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-12-generic, i686: installed virtualbox, 4.2.8, 3.8.0-13-generic, i686: installed DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0100 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:d000] InstallationDate: Installed on 2012-03-01 (383 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) InterpreterPath: /usr/bin/python3.3 Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1267:0213 Logic3 / SpectraVideo plc MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=4781446b-537b-4ed1-8e36-707369788c63 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.42-0ubuntu2 xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0100 UpgradeStatus: Upgraded to raring on 2013-03-05 (14 days ago) UserGroups: dmi.bios.date: 03/31/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H61M-D2-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-D2-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Wed Mar 20 06:41:51 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS/2+USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu2b1 xserver.video_driver: intel ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash compiz-0.9 freeze i386 raring ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1157585 Title: [sandybridge-gt1] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157585/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe :
[Ubuntu-x-swat] [Bug 1070845] [NEW] xserver-xephyr became the default X server after upgrading to Ubuntu 12.10 from 12.04
Public bug reported: I've just upgraded my desktop from Ubuntu 12.04 to 12.10 (32 bit). Everything works fine till the lightdm login screen: after I gave my password nothing happened, and login screen was not responsive either. Switching back to text console, I noticed that several things (which usually run in a unity session) runs. But where? Then I had the odd idea that maybe it runs on the headless X server, xserver-xephyr or xvfb or so. Since only xserver-xephyr was installed, I removed that package. Stopping then starting lightdm service, after removing xserver-xephyr cured the problem. Now I am curious if it's worth to report or not, that it seems xserver-xephyr became the default X server somehow during the upgrade. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xephyr (not installed) ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu4 Architecture: i386 CompizPlugins: [core,commands] CompositorRunning: compiz Date: Wed Oct 24 15:31:03 2012 DistUpgraded: 2012-03-01 18:01:42,336 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.2.0-32-generic-pae, i686: installed virtualbox, 4.1.18, 3.5.0-18-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:d000] InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1267:0213 Logic3 / SpectraVideo plc MachineType: Gigabyte Technology Co., Ltd. H61M-D2-B3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=4781446b-537b-4ed1-8e36-707369788c63 ro quiet SourcePackage: xorg-server UpgradeStatus: Upgraded to quantal on 2012-03-01 (236 days ago) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H61M-D2-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-D2-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1070845 Title: xserver-xephyr became the default X server after upgrading to Ubuntu 12.10 from 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1070845/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1052910] [NEW] Rendering problems in X with various applications.
Public bug reported: Since a while I have stange issues with X. As it happens with multiple applications, I guess it's not application related but some xserver related issue. The issue itself is about having odd horizonal stripes sometimes, or sometimed unreadable fonts, etc. Sometimes they disappear after a while or after switching windows/workspaces, but not always. At least gnome-terminal, google-chrome and pidgin are all affected, it seems. I use 32 bit ubuntu precise, and ubuntu-2D (with compositor turned on in metacity though, through gconf) session. I even had a GPU lockup problem once, when only magic-sysreq helped to kill Xserver because it was frozen [452138.919043] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [452138.919055] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state But the problem I've described happed before (and since then) this hung too. I've tried what kernel msg suggested (after guessing to mount debugfs ...), but: root@vega:~# cat /debug/dri/0/i915_error_state cat: /debug/dri/0/i915_error_state: Cannot allocate memory And then systems slowed down a lot ... Also producing: [541762.704278] cat: page allocation failure: order:10, mode:0x40d0 [541762.704283] Pid: 31054, comm: cat Tainted: G C O 3.2.0-31-generic-pae #50-Ubuntu [541762.704285] Call Trace: [541762.704291] [c1590320] ? printk+0x2d/0x2f [541762.704296] [c10fac2f] warn_alloc_failed+0xbf/0x100 [541762.704299] [c10fd90f] __alloc_pages_nodemask+0x56f/0x740 [541762.704302] [c10fdb5c] __get_free_pages+0x1c/0x30 [541762.704305] [c1132fc7] kmalloc_order_trace+0x27/0xa0 [541762.704307] [c10fcbc9] ? free_compound_page+0x19/0x20 [541762.704310] [c1133db1] __kmalloc+0x1c1/0x1e0 [541762.704312] [c11003bc] ? put_page+0x2c/0x40 [541762.704314] [c1132f65] ? kfree+0x105/0x120 [541762.704318] [c1162669] seq_read+0x139/0x380 [541762.704320] [c1144cdc] vfs_read+0x8c/0x160 [541762.704322] [c1162530] ? seq_lseek+0x170/0x170 [541762.704324] [c1144ded] sys_read+0x3d/0x70 [541762.704327] [c15ad51f] sysenter_do_call+0x12/0x28 [541762.704328] Mem-Info: [541762.704329] DMA per-cpu: [541762.704330] CPU0: hi:0, btch: 1 usd: 0 [541762.704332] CPU1: hi:0, btch: 1 usd: 0 [541762.704333] CPU2: hi:0, btch: 1 usd: 0 [541762.704334] CPU3: hi:0, btch: 1 usd: 0 [541762.704335] Normal per-cpu: [541762.704336] CPU0: hi: 186, btch: 31 usd: 0 [541762.704338] CPU1: hi: 186, btch: 31 usd: 172 [541762.704339] CPU2: hi: 186, btch: 31 usd: 0 [541762.704340] CPU3: hi: 186, btch: 31 usd: 0 [541762.704341] HighMem per-cpu: [541762.704342] CPU0: hi: 186, btch: 31 usd: 0 [541762.704343] CPU1: hi: 186, btch: 31 usd: 58 [541762.704344] CPU2: hi: 186, btch: 31 usd: 0 [541762.704346] CPU3: hi: 186, btch: 31 usd: 0 [541762.704348] active_anon:207107 inactive_anon:100998 isolated_anon:12 [541762.704349] active_file:60027 inactive_file:36043 isolated_file:31 [541762.704350] unevictable:39 dirty:47 writeback:46 unstable:0 [541762.704350] free:43063 slab_reclaimable:19864 slab_unreclaimable:6669 [541762.704351] mapped:21417 shmem:59043 pagetables:5655 bounce:0 [541762.704355] DMA free:9192kB min:784kB low:980kB high:1176kB active_anon:184kB inactive_anon:844kB active_file:3344kB inactive_file:2176kB unevictable:0kB isolated(anon):48kB isolated(file):44kB present:15804kB mlocked:0kB dirty:0kB writeback:0kB mapped:88kB shmem:144kB slab_reclaimable:8kB slab_unreclaimable:16kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [541762.704359] lowmem_reserve[]: 0 869 1917 1917 [541762.704364] Normal free:126536kB min:44216kB low:55268kB high:66324kB active_anon:159196kB inactive_anon:179936kB active_file:146256kB inactive_file:88108kB unevictable:20kB isolated(anon):0kB isolated(file):80kB present:890008kB mlocked:20kB dirty:184kB writeback:0kB mapped:21400kB shmem:81240kB slab_reclaimable:79448kB slab_unreclaimable:26660kB kernel_stack:5288kB pagetables:3504kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [541762.704367] lowmem_reserve[]: 0 0 8389 8389 [541762.704372] HighMem free:36524kB min:512kB low:13848kB high:27188kB active_anon:669048kB inactive_anon:223212kB active_file:90508kB inactive_file:53888kB unevictable:136kB isolated(anon):0kB isolated(file):0kB present:1073908kB mlocked:136kB dirty:4kB writeback:184kB mapped:64180kB shmem:154788kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:19116kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:578 all_unreclaimable? no [541762.704375] lowmem_reserve[]: 0 0 0 0 [541762.704377] DMA: 35*4kB 10*8kB 7*16kB 4*32kB 3*64kB 3*128kB 4*256kB 2*512kB 0*1024kB 1*2048kB 1*4096kB = 9228kB [541762.704383] Normal: 4308*4kB 1457*8kB 1867*16kB 1326*32kB 268*64kB 12*128kB 0*256kB 1*512kB
[Ubuntu-x-swat] [Bug 1052910] Re: Rendering problems in X with various applications.
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1052910] Re: Rendering problems in X with various applications.
** Attachment added: Rendering problems with pidgin. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323888/+files/Screenshot%20from%202012-09-19%2011%3A50%3A24.png ** Attachment removed: Rendering problems with pidgin. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323887/+files/Screenshot%20from%202012-09-19%2011%3A50%3A24.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1052910] Re: Rendering problems in X with various applications.
** Attachment added: Rendering problems with pidgin. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323887/+files/Screenshot%20from%202012-09-19%2011%3A50%3A24.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1052910] Re: Rendering problems in X with various applications.
** Attachment added: Rendering problems with google-chrome. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+attachment/3323886/+files/Screenshot%20from%202012-09-19%2014%3A49%3A44.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052910/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1029265] Re: X server sometimes crashes after sleep
Mitten: interesting, you have different notebook (I have a lenovo thinkpad) but it seems the xorg backtracke is quite similar also the message in dmesg which is exactly having the same +1f3000 as in mine. Probably it's a general bug affected the users of the same GPU, or so then? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1029265 Title: X server sometimes crashes after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1029265/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1029265] Re: X server sometimes crashes after sleep
Ok, now it happens too frequently, which renders my notebook unusable as I don't dare to suspend it: with more than 50% chance it will cause Xorg to crash after resuming. Eg my current output of dmesg contains these: [ 2809.064137] Xorg[1137]: segfault at 9 ip b7699b48 sp bfffbc20 error 4 in Xorg[b7579000+1f3000] [20580.509216] Xorg[10643]: segfault at 9 ip b772cb48 sp bfabc590 error 4 in Xorg[b760c000+1f3000] [28250.590881] Xorg[14981]: segfault at 9 ip b7693b48 sp bfa98f70 error 4 in Xorg[b7573000+1f3000] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1029265 Title: X server sometimes crashes after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1029265/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1029265] [NEW] X server sometimes crashes after sleep
Public bug reported: If I close the lid of the notebook without external power, it goes into sleep state. However sometimes (but not always!) after resuming, X crashes, I only see everything disappear and lightdm screen can bee seen again, with sigsegv info in kernel message buffer (dmesg) etc. Note that crash is not instant: after resuming usually I work something like half a minute before crash happens. [ 2793.783728] Xorg[1075]: segfault at 9 ip b7645b28 sp bfa504d0 error 4 in Xorg[b7525000+1f3000] ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jul 26 07:35:38 2012 DistUpgraded: 2012-03-03 11:33:01,134 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.12, 3.2.0-27-generic-pae, i686: installed ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21dd] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 003: ID 04f2:b228 Chicony Electronics Co., Ltd MachineType: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2012-03-03 (144 days ago) dmi.bios.date: 11/04/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET38WW (1.15 ) dmi.board.name: 5016NW6 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5016NW6 dmi.product.version: ThinkPad L520 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1.2 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1029265 Title: X server sometimes crashes after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029265/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1029265] Re: X server sometimes crashes after sleep
** Attachment added: Xorg log file with the crash https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029265/+attachment/3236565/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1029265 Title: X server sometimes crashes after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029265/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 1029265] Re: X server sometimes crashes after sleep
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1029265 Title: X server sometimes crashes after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1029265/+subscriptions ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
Hmm I haven't seen this kind of problem a since a while, let's hope than, it's fixed :) It was hard to tell when and how the problem can be triggered, but for sure it should have happened since some days at least, and nothing since a hmm month or so? I can't tell exactly, but as I've noted above in a comment: it seems setting grub to use only terminal mode fixed this ... I don't know how it's related to the kernel fix you've mentioned. Without setting grub to terminal I have not even usuable console if I switch there with CTRL+ALT+F1 for example -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
Interesting, as far as I can remember, it was also my case, I mean X crashed during typing always (?). Nowdays I can't reproduce this problem anymore though ... (I am not sure if there is connection, but about since then when I applied GRUB_TERMINAL=console in /etc/default/grub since otherwise I have no text console just some odd garbage on the screen if I switch back to text consoles with CTRL-ALT-F1 or so). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 762478] Re: [nouveau] No icons shown in unity launcher
I have similar issue with fglrx, launcher and panel seems to be at the right position but just silhouette of them can be seen, all is black. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/762478 Title: [nouveau] No icons shown in unity launcher ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
I will check the new kernel out. What is odd to me, that in case of the second login after the boot (either with logging out first, or after the crash when gdm displayed again) it does not happen, only at the first time. The only difference I could notice that in case of the first login X seems to use tty7 while it's tty8 later (as I've commented already). I had the idea that maybe it's related to my boot problem that no splash, text consoles etc can be seen only some kind of odd bar code like image. Anyway I would be keen to help with bisecting however it can be hard, since the crash sometimes need a hour or so to happen, so I can't be sure exactly (at least not within a sane time) that the given kernel is OK or not. But I will see ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
So, any idea what can I help to eliminate this bug? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Not exactly a great surprise but I would like to note that indeed, using that PPA fixes my problem and works fine. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
The only difference between first and further logins after boot that in case of first one X uses tty7, furher logins use tty8. I don't now if it's normal or it counts ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
Now I discovered (I haven't noticed it earlier since I rebooted the system more times per day) that it seems after a system boot, X seems to be unstable, however after an X crash (when gdm screen is redisplayed and I must relogin then) it seems to be stable then. I've tried to do the backtrace (with using NoTrapSignals in config file as it was suggested). The interesting thing that one time I got SIGINT and after I got the backtrace and I quited with gdb (it was attached to already running process with ssh'ing from another machine) X continued to work without any crash ... I re-attach gdb to X process and after some minutes I noticed the true problem (SIGQUIT) however the backtrace itself seems to be very similar only the signals are different. Anyway the result is attached (the other backtrace I was talking about is almost the same just it is SIGINT instead of SIGQUIT, I have checked it out with making diff between the traces). ** Attachment added: gdb-Xorg-2.txt https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/765136/+attachment/2071826/+files/gdb-Xorg-2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
I am wondering if my bug report (bug 764272) is the same issue or not ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
Sorry my very last comment here was posted here as a mistake, it was attended to write as response to another browser tab ... (isn't it possible to delete my own comment somehow?). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [MASTER] X uses software rendering with nouveau
@Timo: ahaa, thanks. I am just curious what is the official recommendation for natty (now and when natty is released as stable) users with nvidia card: since nvidia's binary only driver is not installed by default (if I am correct) and also it seems to be unstable (X crashes sometimes with it (bug 765136). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [MASTER] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [MASTER] X uses software rendering with nouveau
Also I have no usable text console neither with nouveau, nor nvidia's binary driver as I've commented that bug report I've mentioned in my previous comment here. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [MASTER] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [natty] X uses software rendering with nouveau
If it counts, I am using DVI cable between the video card and the monitor. And by the way, I have another just upgraded machine also with nvidia card and DVI: that time I tried to use nvidia's binary driver. The result: I have signal, but just very odd bar-code like screen can be seen instead of boot logo and also when I try to use text based console instead of X. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [natty] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 765136] [NEW] [natty] X often crashes since upgrade to natty
Public bug reported: Binary package hint: xorg Since upgrade to natty, X often just crashes at random moments (about at every hour or so, but of course there is no exact period). I'm using nvidia's binary driver. Xorg log files always says Caught signal 3 (Quit). Server aborting and the following lines are common (the others or not): 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a531b] 1: /usr/bin/X (0x8048000+0x60808) [0x80a8808] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x76940c] I can mention to examples now (which I have logs about), one is: Backtrace: [ 908.812] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a531b] [ 908.812] 1: /usr/bin/X (0x8048000+0x60808) [0x80a8808] [ 908.812] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xd8f40c] [ 908.812] 3: /usr/bin/X (0x8048000+0x2807e) [0x807007e] [ 908.812] 4: /usr/bin/X (0x8048000+0x1a81c) [0x806281c] [ 908.812] 5: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x235e37 ] [ 908.812] 6: /usr/bin/X (0x8048000+0x1a411) [0x8062411] [ 908.812] Caught signal 3 (Quit). Server aborting the other is: Backtrace: [ 8197.382] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a531b] [ 8197.383] 1: /usr/bin/X (0x8048000+0x60808) [0x80a8808] [ 8197.383] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x76940c] [ 8197.383] 3: /usr/lib/libpixman-1.so.0 (pixman_edge_init+0x1d8) [0x1657c8] [ 8197.383] 4: /usr/lib/libpixman-1.so.0 (pixman_line_fixed_edge_init+0x6c) [0x 1658cc] [ 8197.383] 5: /usr/lib/libpixman-1.so.0 (pixman_rasterize_trapezoid+0x120) [0x 165ba0] [ 8197.389] 6: /usr/lib/xorg/modules/libfb.so (fbRasterizeTrapezoid+0x5e) [0xb7 b9ce] [ 8197.389] 7: /usr/bin/X (miTrapezoids+0x23f) [0x81c7faf] [ 8197.389] 8: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x69e6000+0x498ed3) [ 0x6e7eed3] [ 8197.392] Caught signal 3 (Quit). Server aborting ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg 1:7.6+4ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 270.41.03 Sat Apr 9 00:04:57 PDT 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu3) Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: None Date: Mon Apr 18 22:10:20 2011 DistUpgraded: Log time: 2010-09-12 13:58:25.192945 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.0.4, 2.6.35-28-generic, i686: installed vboxhost, 4.0.4, 2.6.38-8-generic, i686: installed vboxhost, 4.0.4, 2.6.35-27-generic, i686: installed nvidia-current, 270.41.03, 2.6.35-28-generic, i686: installed nvidia-current, 270.41.03, 2.6.38-8-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: nVidia Corporation NV43 [GeForce 6200] [10de:014f] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:819e] JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) Lsusb: Bus 002 Device 004: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty Bus 002 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 002 Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger 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: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=a5601479-5c0c-426e-931b-fe8ab0d82b50 ro splash quiet vt.handoff=7 Renderer: Unknown SourcePackage: xorg UpgradeStatus: Upgraded to natty on 2010-09-12 (218 days ago) dmi.bios.date: 06/08/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1005 dmi.board.name: A8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1005:bd06/08/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 765136] Re: [natty] X often crashes since upgrade to natty
Also it seems I am not lucky with natty if we speak about vga cards :) With ATI radeon it turned out I hit a drm module bug which was fixed already in upstream but not in ubuntu's kernel, with nvidia, trying nouveau I have no video signal till gdm or when I switch to text console at all (and I need libgl1-mesa-dri-experimental for any decent performance, but still CPU usage goes high sometimes), with nvidia binary driver, random crashes, and also no boot logo+text console (but there is video signal, just some barcode like ugliness on the screen). I am wondering if I should stay with maverick, it seems to be more stable both video nvidia and ATI in my experience. Also I am very open to help Ubuntu like with the ATI radeon bug too, when I did the kernel git bisecting to find the problematic commit (bug 735126) . Just please tell me what I can do to help in debugging or so, and I try to support ubuntu development with the help I can do at least ... Thanks in advance! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/765136 Title: [natty] X often crashes since upgrade to natty ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
And even if it does not block the installation for some reason, the installed system would not boot because of freezing on boot with KMS enabled. Though I only tried this with maverick-natty upgrade, but I guess it does not count at all, if it's an upgraded system, live system, etc, if it's kernel 2.6.38 it will freeze on radeon module, since afaik KMS is enabled by default in all cases and upstream only fixes this problem later, and it's not in natty's kernel yet. So I guess is affects every possible of usage/installation/upgrade method of natty on hardwares where it's issue - according to bug reports (including mine) it's at least Toshiba Satellite notebooks -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
It seems the bug is identified also a short patch (at fdo bugtracker) which cures the problem. Today I will try to apply that patch to the ubuntu's kernel source tree to see that it really fixes the freeze. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 759562] [NEW] [natty] X uses software rendering with nouveau
Public bug reported: Binary package hint: xserver-xorg-video-nouveau In natty, X uses software rendering, as I can tell it by issuing 'glxinfo' command, also Xorg.0.log states this. That log file is about trying to load nouveau_dri.so but I have no such an object in my system, and I have no idea where I can get it from. Another (maybe unrelated!) problem, that during the boot process, my monitor switches off till gdm comes, also if I try to switch to text based console (alt-ctrl-f1, for example). [29.099] (II) AIGLX: Trying DRI driver /usr/lib/dri/nouveau_dri.so [29.133] (II) AIGLX: dlopen of /usr/lib/dri/nouveau_dri.so failed (/usr/lib/ dri/nouveau_dri.so: cannot open shared object file: No such file or directory) [29.133] (II) AIGLX: Trying DRI driver /usr/lib/dri-alternates/nouveau_dri.s o [29.158] (II) AIGLX: dlopen of /usr/lib/dri-alternates/nouveau_dri.so failed (/usr/lib/dri-alternates/nouveau_dri.so: cannot open shared object file: No suc h file or directory) [29.158] (II) AIGLX: Trying DRI driver /usr/lib32/dri/nouveau_dri.so [29.158] (II) AIGLX: dlopen of /usr/lib32/dri/nouveau_dri.so failed (/usr/li b32/dri/nouveau_dri.so: cannot open shared object file: No such file or director y) [29.158] (II) AIGLX: Trying DRI driver /usr/lib32/dri-alternates/nouveau_dri .so [29.158] (II) AIGLX: dlopen of /usr/lib32/dri-alternates/nouveau_dri.so fail ed (/usr/lib32/dri-alternates/nouveau_dri.so: cannot open shared object file: No such file or directory) [29.158] (II) AIGLX: reverting to software rendering [29.158] (II) AIGLX: Screen 0 is not DRI capable [29.158] (II) AIGLX: Trying DRI driver /usr/lib/dri/swrast_dri.so [29.609] (II) AIGLX: Loaded and initialized swrast ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: Off modes: edid-base64: Date: Wed Apr 13 10:21:34 2011 DistUpgraded: Log time: 2010-10-20 23:32:50.594007 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.0.4, 2.6.38-8-generic, i686: installed vboxhost, 4.0.4, 2.6.35-28-generic, i686: installed vboxhost, 4.0.4, 2.6.35-27-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: nVidia Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:826d] Lsusb: Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 1267:0213 Logic3 / SpectraVideo plc 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: Hewlett-Packard HP Compaq dx2200 MT ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.38-8-generic root=UUID=24e2665f-aaa4-440b-8cb4-c37742bd51e8 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to natty on 2010-10-20 (174 days ago) dmi.bios.date: 08/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: MS7254 1.05 dmi.board.name: 0A48 dmi.board.vendor: MSI dmi.chassis.asset.tag: HUB6520N19 dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrMS72541.05:bd08/14/2006:svnHewlett-Packard:pnHPCompaqdx2200MT:pvr:rvnMSI:rn0A48:rvr:cvnMSI:ct3:cvr: dmi.product.name: HP Compaq dx2200 MT dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.4+bzr20110411-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty ubuntu unity-2d -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [natty] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [natty] X uses software rendering with nouveau
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [natty] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [natty] X uses software rendering with nouveau
Sorry, about the text console: no video signal (according to my LCD monitor's opinion) during the boot, and if I switch to text console from X (like with CTRL-ALT-F1) I still see the X session however screen is not updated, till I switch back and of course mouse etc does not work either. Meanwhile I can log in blindly and even start an mp3 with mpg123 by using the console even if I only see the screen of X frozen (till I switch back). But as I've mentioned, maybe it's not related to this bug which is about having software rendering only. I've just checked it out: lgb@vega:$ ls -la /usr/lib/dri/*nou* -rw-r--r-- 1 root root 220068 2011-04-11 08:15 /usr/lib/dri/nouveau_vieux_dri.so Should I try symlink this to nouveau_dri.so? Since it seems X wants that, but I have onlyt this vieux (whatever it is ...) file only which seems to be at least similar (in file name at least) to what X would like to dlopen(). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [natty] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 759562] Re: [natty] X uses software rendering with nouveau
After some google'ing I've installed package libgl1-mesa-dri- experimental now I have hw rendering, but still I am wondering if it's normal since it means that nvidia owners can't use their desktops normally with natty unless installing nvidia's binary driver (I guess), is this the normal behaviour or is it really a bug? Also I still have the no signal monitor feedback on boot and no text concoles problems. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/759562 Title: [natty] X uses software rendering with nouveau ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
According to my tests, the suggested commit really fixes the problem, so I would suggest to include that patch within natty's kernel too: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=patch;h=97ea530f6fac1f9632b0c4792a2a56411454adbe -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Bisect process is - finally - done, so I have the first bad commit from Linus' GIT between 2.6.37 and 2.6.38 which seems to introduce the problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I have started to try different versions of vanilla kernels please take a look at freedesktop.org bugtracker -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I've tried what Alex told on freedesktop's bugtracker (please take a look there) so it really seems it's nothing about X itself, just loading the module without X involved the freeze happens. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Hi, thanks for the information, I've just added myself to the cc list on the freedesktop bug tracker. I will investigate, sorry for the delay, just I had no access to my notebook till now. I will try some things today. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Maybe I've missed something: I've tried to blacklist radeon module, so I've created /etc/modprobe.d/blacklist-radeon.conf with blacklist radeon on it, then I did depmod -a then dpkg-reconfigure linux- image-`uname -r` (I used the freshest natty kernel booted with radeon.modeset=0 before to allow me to use the system). After reboot it still bugs. Does it signal a deeper problem, or should I blacklist radeon module in a different way? Unfortunately I can't check the kernel output now unlike before (with netconsole), I just have black screen and non disk activity after a while on booting. Please tell me how I could do this better, if my solution was not correct at least. Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
MTRR settings: reg00: base=0x0fffe ( 4095MB), size= 128KB, count=1: write-protect reg01: base=0x0 (0MB), size= 2048MB, count=1: write-back reg02: base=0x08000 ( 2048MB), size= 1024MB, count=1: write-back reg03: base=0x0bff0 ( 3071MB), size=1MB, count=1: uncachable reg04: base=0x1 ( 4096MB), size= 1024MB, count=1: write-back kernel: Linux orion 2.6.38-8-generic-pae #41-Ubuntu SMP Tue Apr 5 21:14:26 UTC 2011 i686 i686 i386 GNU/Linux kernel cmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=14c446e2-e9e0-47a2-992e-f04d3f9b7bf3 ro radeon.modeset=0 text quiet splash vt.handoff=7 I also attached the output of dmesg. I only comment this, since upstream suggests the inspection of mtrr settings. ** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/735126/+attachment/1987339/+files/dmesg -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
By the way I've tried radeon.blacklist=yes kernel parameter as it was suggested according to some google'd resources. Then radeon did not load indeed, and system booted (checked with lsmod | grep radeon, no result). modprobe'ing radeon did not work then (illegal parameter about that radeon.blacklist). When I used insmod with the full path of radeon.ko, screen went black immediately, the same result as my intial bug report. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I've forgot to mention: I've removed the remained virtualbox stuffs totally, also dkms, etc. Still, there is no change about the issue. I've also tried to limit the available memory for the kernel with mem=512M kernel parameter. I've also tried nopat I've found in some forum, but still the same problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I've also tried some odd thing: using mem=512M nopat radeon.blacklist=yes text extra kernel parameters, for sure, I got text console well then (even without mem/nopat it works). Then I removed MTRR entries one by one (echo disable=X | /proc/mtrr, X=0 ...). System went slow like hell, never seen before, but I guess it's natural after this action. Then I tried to insert radeon.ko with insmod by giving its full path, but still the result is the very same again :( :( Sorry for writing too much, tell me if I don't need to try and comment every ideas of mine. Anyway I'm waiting for some suggestion now ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Yes, that disables kms. I am still wondering about this kms thing: if kernel mode setting is not in the kernel but done by the X Server or so, what's the deal? Why make it acceleration disappear? I would be happy to say bye-bye to KMS (and boot loge), let leave X to change video mode (instead of kernel) but I want acceleration which should be not related to setting video mode up. Or I miss something :) Surely, the best would be to do by kernel at once etc, but if it does not work for me, I can live without it, but it does not work that way it seems [no acceleration] :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 749749] [NEW] X crashes with signal 11
Public bug reported: Binary package hint: xorg Recently (never happened before) I often have the case when closing (or exiting from shell wihin) a gnome terminal window causes all windows to close. Sometimes even the while X goes away with signal 11 in the Xorg.log file. I am attaching the right Xorg.log file now. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.06 Mon Sep 13 06:35:06 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: i386 Date: Sun Apr 3 23:42:57 2011 EcryptfsInUse: Yes Lsusb: Bus 002 Device 005: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty Bus 002 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 002 Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger 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: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=a5601479-5c0c-426e-931b-fe8ab0d82b50 ro splash quiet ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 06/08/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1005 dmi.board.name: A8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1005:bd06/08/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-28-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick ubuntu-une -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/749749 Title: X crashes with signal 11 ___ 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
[Ubuntu-x-swat] [Bug 749749] Re: X crashes with signal 11
** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/bugs/749749/+attachment/1974846/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/749749 Title: X crashes with signal 11 ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Installing fglrx allows me to use natty's own kernel, but unity is unusable then, only black boxes can be seen instead of the panel, the launcher etc. Classic session works. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I've changed the status from incomplete to new, since I gave some data which was asked. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I've also tried the generic, non-PAE kernel, also there was some update for natty, but the problem remains as it was. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Please tell me, if I can do more to debug the problem, I really would like to test natty on that notebook (and at our firm we have usually this Toshiba notebook for more people, though they are not so keen on doing anything extra for a working system, sadly). Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I am sure I am not the right person to judge, but is it possible that it's not even az Xorg server related bug but some kind of kernel problem when KMS is enabled (the default)? I have no Xorg log at all, and I have the suspect that system haven't even reached the point to start Xorg (but I am not sure) just check the netconkern.log file what I've sent: processes stuck used in the boot process, probably before Xorg has the chance to start ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
No, and even no MAC address can be found in the ARP table, so I guess networking is not on yet before the freeze, or so? Now there was an update for kernel 2.6.38-7 (instead of -6) but the same problem. Btw, it's nice to mention that magic sysreq keys seems to work (at least alt- sysreq-b reboots the system) but I can't see any message (because of the video mode on the console?) so it's not so useful, I've tried to sync, unmount and reboot with the corresponding magic sysreq combos, but still, after I boot with maverick's kernel, still there is no sign of _any_ log message of the natty's kernel, or xorg logs at all what I would be able to send you. So I have no idea how this problem can be reported with more info, maybe network console can be useful, but I've only read about that, I haven't ever tried to use it yet ... Is it worth to try? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Ok, I've booted with the old (maverick's kernel) and I hacked a new script as the first one in /etc/rcS.d which modprobes the network console module and also brings up the network and setting the log level of the console. Then I rebooted with natty's current kernel, the usual effect: half of the screen is filled with garbage, no disk activity, etc. But I got some messages on my other machine with network console: At first it did not seems to contain any problematic message (panic, etc). However, after some time, there were some blocked for more than ... like messages, it seems about commands used during the boot (iptables-restore: I had setup for iptables rules to load with, NetworkManager, etc ...). I've attached the log file to this comment. Hope it helps. ** Attachment added: netconkern.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/735126/+attachment/1924749/+files/netconkern.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Just adding the radeon.modeset=0 to the natty's kernel's parameters causes the system to be able to boot (into a usable state, with X etc, of course not the same 3D performance etc), and not messages like the previous one with KMS not disabled. So for me, it seems only using or not using KMS cause this kernel bug? If it's that ... I'm also attaching the kernel log I got now with radeon.modeset=0 with natty's kernel (Linux orion 2.6.38-7-generic-pae #36-Ubuntu SMP Fri Mar 18 22:23:27 UTC 2011 i686 i686 i386 GNU/Linux). I've also got this one with network console grabbed on another machine, so maybe it's fair enough now to compare with the previous. ** Attachment added: netconkern-modeset-disabled.log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/735126/+attachment/1924760/+files/netconkern-modeset-disabled.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
I also tried the safe mode I can see the boot messages then with natty's kernel, but there is only a black screen some seconds later (imho at starting X itself ). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] [NEW] [natty] system freezes on boot without disabling KMS
Public bug reported: Binary package hint: xserver-xorg-video-ati After upgrading maverick (x86 32 bit system but with PAE kernel) system does not boot, after some disk activity the upper half of the screen is filled with garbage and no more disk activity. Booting an older kernel (from maverick) works. Also it work with natty's kernel if I give radeon.modeset=0 parameter at grub but then there is now hw accel. (glxinfo reports software rendering, booting natty with maverick's kernel seems to have it, glxinfo reports galium as the render string then). This is a Toshiba Satellite A300 notebook with 4G of RAM and video hw: 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series xserver-xorg-video-radeon1:6.14.0-0ubuntu2 Linux orion 2.6.38-6-generic-pae #34-Ubuntu SMP Tue Mar 8 15:47:54 UTC 2011 i686 i686 i386 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xserver-xorg-video-radeon 1:6.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-6.34-generic-pae 2.6.38-rc7 Uname: Linux 2.6.38-6-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,regex,mousepoll,resize,wall,grid,move,animation,place,snap,session,imgpng,workarounds,vpswitch,gnomecompat,expo,ezoom,staticswitcher,fade,scale] CompositorRunning: None Date: Mon Mar 14 22:03:35 2011 DistUpgraded: Log time: 2011-03-13 16:50:20.128908 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.0.0, 2.6.35-24-generic-pae, i686: installed vboxhost, 4.0.0, 2.6.35-28-generic-pae, i686: installed vboxhost, 4.0.0, 2.6.35-25-generic-pae, i686: installed vboxhost, 4.0.0, 2.6.35-27-generic-pae, i686: installed vboxhost, 4.0.0, 2.6.35-26-generic-pae, i686: installed GraphicsCard: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff1e] InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: TOSHIBA Satellite A300 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic-pae root=UUID=14c446e2-e9e0-47a2-992e-f04d3f9b7bf3 ro quiet splash vt.handoff=7 radeon.modeset=0 Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to natty on 2011-03-13 (1 days ago) dmi.bios.date: 03/20/2009 dmi.bios.vendor: INSYDE dmi.bios.version: 1.90 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd03/20/2009:svnTOSHIBA:pnSatelliteA300:pvrPSAGCE-0KC00FHU:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite A300 dmi.product.version: PSAGCE-0KC00FHU dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.4-0ubuntu4 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 735126] Re: [natty] system freezes on boot without disabling KMS
Unfortunately, I can't send bug report related to the exact environment where bug occurs since system does not boot then at all. So this bug report was made when radeon.modeset=0 was used. Also, I couldn't find any usable information in kernel or Xorg log files ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/735126 Title: [natty] system freezes on boot without disabling KMS ___ 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
[Ubuntu-x-swat] [Bug 671292] Re: screen corruption in maverick
Now it becomes more and more annoying. It seems it always happen more or less frequently with all of the applications: menu elements etc are stuck in a corrupted way on all workspaces. For example the chrome/chromium issue I've mentioned: dragged items can be seen floating over all contents, on all workspaces. Also, menu by clicking on the background (nautilus), terminal's menu, VICE's (commodore emulator) menu, etc sometimes remain on the screen: sometimes only some border, sometimes the whole content, sometimes some corrupted version of the original element. And it won't go away before I kill the application it opened the original item. For a demonstration I attach a screenshot. I guess it's the result of using composite support of metacity (I don't use compiz, but composition support of metacity activated via gconf key). ** Attachment added: Screenshot.png https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/671292/+attachment/1819295/+files/Screenshot.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. https://bugs.launchpad.net/bugs/671292 Title: screen corruption in maverick ___ 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
[Ubuntu-x-swat] [Bug 671292] Re: screen corruption in maverick
Also please note that I am not sure it's the fault of the graphics driver (nvidia in my case), it can be something else too, just I haven't noticed it with other card, though I have this bug on two different machines, both of them are equipped with nvidia card, and use nvidia's binary driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. https://bugs.launchpad.net/bugs/671292 Title: screen corruption in maverick ___ 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
[Ubuntu-x-swat] [Bug 671292] Re: screen corruption in maverick
I've just checked, killing metacity fixes the problem at the issue at least what I've post screenshot about ... But it a bit overkill to kill/replace metacity all the time it happens ... :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. https://bugs.launchpad.net/bugs/671292 Title: screen corruption in maverick ___ 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
[Ubuntu-x-swat] [Bug 671292] [NEW] screen corruption in maverick
Public bug reported: Binary package hint: xorg My problem is hard to clearly explain, I am sorry if it does not reach the right package in LP or so. Since upgraded to Maverick (I have two different machines as examples, both of them are 32bit x86). I've noticed it first with chromium browser, please check my bug report out: http://code.google.com/p/chromium/issues/detail?id=60919 In nutshell: if I drag an image (or a selected text for example) with the mouse and I release it, it remains on the screen above every content, even if I switch another workspace/window or play full screen video, as I would have some kind of monitor OSD or so. I have a screenshot attached to the bugreport on chromium I've mentioned above. The reason that I did the bug report here too: in that ticket I was told that the reason can be the maverick and not chromium itself. And it looks true: while the problem 100% reproducable in chromium, I could notice similar bugs with other applications well, though maybe not so often (it can be the usage pattern: it's quite frequent that I click on something while move the mouse and it causes that drag anomaly in chromium, while it can be trickier in other apps to trigger this problem maybe?), for example using geany to code in PHP and Python causes sometimes to have remainment of the wire of a dialog can be seen all the time and only exiting from geany can help, the same way as with chromium. Hopefully my bugreport is useable somehow ... Thanks! ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 260.19.06 Mon Sep 13 06:35:06 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) Architecture: i386 Date: Fri Nov 5 07:59:51 2010 EcryptfsInUse: Yes Lsusb: Bus 002 Device 004: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty Bus 002 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 002 Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger 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: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=a5601479-5c0c-426e-931b-fe8ab0d82b50 ro splash quiet ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 06/08/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1005 dmi.board.name: A8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1005:bd06/08/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-23-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick ubuntu-une -- screen corruption in maverick https://bugs.launchpad.net/bugs/671292 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 671292] Re: screen corruption in maverick
-- screen corruption in maverick https://bugs.launchpad.net/bugs/671292 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 636619] Re: keyboard layout switching goes crazy
@RIch: maybe it is (I've commented that bug too now). It seems the problem is triggered after some rapid change on the layout by the scroll lock key (set to switch layout in my config) and/or print screen button to take a screenshot. However I haven't seen it since a while, I will try to reproduce it anyway (recently I didn't need to use my different kbd layouts quite heavily which was the case when I reported the problem though). -- keyboard layout switching goes crazy https://bugs.launchpad.net/bugs/636619 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev 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
[Ubuntu-x-swat] [Bug 636619] [NEW] keyboard layout switching goes crazy
Public bug reported: Binary package hint: xorg After upgrading to maverick I have an annoying problem. I am using four keyboard layouts, usage of three of them are indicated by the scroll lock led. I am using the scroll lock key to switch between them. After some change between the layouts, something goes crazy and it starts to cycle between the layouts very quickly without my intent, the led flashes all the time, and also I can see that pressing the same key generates different character randomly based on the fact which layout was active in that moment. I cannot find a solution to stop this action. The keyboard indicator on the panel shows the primary layout only, not cycling there. I had the idea to start xev, and I see endless printings like this PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886504, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886505, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886562, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886634, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886635, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886694, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886695, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886756, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886811, state PropertyNewValue PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886812, state PropertyNewValue ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xserver-xorg 1:7.5+6ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 256.53 Fri Aug 27 21:03:42 PDT 2010 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu2) Architecture: i386 Date: Sun Sep 12 22:04:25 2010 EcryptfsInUse: Yes Lsusb: Bus 002 Device 004: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty Bus 002 Device 003: ID 045e:0039 Microsoft Corp. IntelliMouse Optical Bus 002 Device 002: ID 046d:08da Logitech, Inc. QuickCam Messanger 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: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=a5601479-5c0c-426e-931b-fe8ab0d82b50 ro splash quiet ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 06/08/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1005 dmi.board.name: A8N-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 2.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1005:bd06/08/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.35-20-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- keyboard layout switching goes crazy https://bugs.launchpad.net/bugs/636619 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 636619] Re: keyboard layout switching goes crazy
** Attachment added: .proc.driver.nvidia.cards.0.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575458/+files/.proc.driver.nvidia.cards.0.txt ** Attachment added: .proc.driver.nvidia.registry.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575459/+files/.proc.driver.nvidia.registry.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575460/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575461/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575462/+files/Dependencies.txt ** Attachment added: DkmsStatus.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575463/+files/DkmsStatus.txt ** Attachment added: GdmLog.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575464/+files/GdmLog.txt ** Attachment added: GdmLog1.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575465/+files/GdmLog1.txt ** Attachment added: GdmLog2.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575466/+files/GdmLog2.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575467/+files/Lspci.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575468/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575469/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575470/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575471/+files/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575472/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575473/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575474/+files/UdevLog.txt ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575475/+files/XorgConf.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575476/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575477/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575478/+files/Xrandr.txt ** Attachment added: glxinfo.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575479/+files/glxinfo.txt ** Attachment added: nvidia-settings.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575480/+files/nvidia-settings.txt ** Attachment added: peripherals.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575481/+files/peripherals.txt ** Attachment added: setxkbmap.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575482/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575483/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.launchpad.net/bugs/636619/+attachment/1575484/+files/xkbcomp.txt -- keyboard layout switching goes crazy https://bugs.launchpad.net/bugs/636619 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
Ahaa, I see, the only problem that .21 made things even more worse (no idea about .22 yet) so lucid will come out (today?) as not being able to show me even a login screen (so looks like no successfull boot, only black screen) on some (?) intel GPUs. Sure, I can work-around that with using that 2.6.34 rc3 kernel from PPA, true ... Thanks for the comment! -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
For me: .20 mostly works, only crashes on XVideo usage, .21: black screen after boot, nothing works. 2.6.34 rc3 kernel (not official lucid kernel! from ppa): everything works, even XVideo. -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
It seems that the current (and previous) lucid kernel simply cannot work well enough to be usable on my notebook at least. Using http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc3-lucid/ works, but that's not the default kernel for lucid, of course. 2.6.32.21-31 makes xorg crashes on XVideo but also at some other cases according to my experience, switching off KMS does not help. The newer kernel in lucid since then (2.6.32.21-32) is even more worse, since the xorg does not even start, and machine freezes completly. So for me at least this bug makes lucid unusable on my hardware which is a show-stopper. Currently I am using 2.6.34 kernel from that PPA to be able to use lucid. -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
So I have the same (but) with kernel 2.6.32-21.32 (with out without that i915.modeset=0) as braseb commented ... -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
I don't have the notbook with me now, but a co-worker of mine has the same issue with identical hardware. It seems there is no problem with this kernel: http://kernel.ubuntu.com/~kernel- ppa/mainline/v2.6.34-rc3-lucid/ (just checked out on his notebook). It means that for example mplayer can play videos with XVideo output (mplayer -vo xv ...) without a crash. Also kernel package just has been upgraded to 2.6.32-21.32. With that kernel not even login screen got just black screen and no disk I/O after a while ... (even with boot options nosplash - btw even with noplash there is splash -, and quiet option is removed too). According to /var/log/kern.log the kernel log ends at the MTRR stuffs in the middle of a line and logs of the new boot (with that 2.6.34 kernel which works) starts with the date/time not at a new line ... xorg.log files in /var/log/ does not give many informations the only difference some kind of acpi socket opening problems. -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: [855GM] GPU hang when an application tries to use XVideo
In recovery mode system boots but if I try to launch X from root console, system freezes totally. -- [855GM] GPU hang when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel 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
[Ubuntu-x-swat] [Bug 554835] Re: xorg crashes when an application tries to use XVideo
Btw I have had a crash during normal usage of the desktop (no xv apps - as far as I know), the xorg.log and kernel log indicated that it's the same problem (exactly the same messages). I am not sure however that it was not caused by some xv apps, but as far as I know it wasn't that at that time at least ... -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 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
[Ubuntu-x-swat] [Bug 554835] [NEW] xorg crashes when an application tries to use XVideo
Public bug reported: Binary package hint: xorg xorg crashes when an application tries to use xv. Then screen flashes (I guess gdm tries to start again and again) at the end only black screen I can got, and only hard reset can help. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg 1:7.5+3ubuntu1 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 23:25:47 2010 Lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0ace:1215 ZyDAS WLA-54L 802.11bg Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard compaq nx9020 (PG662ES#AKC) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=dcdc2473-3fd8-4e42-8132-6612dc8c9bf9 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 08/18/2004 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.10 dmi.board.name: 3084 dmi.board.vendor: Quanta dmi.board.version: 41.09 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.10:bd08/18/2004:svnHewlett-Packard:pncompaqnx9020(PG662ES#AKC):pvrRev1:rvnQuanta:rn3084:rvr41.09:cvnQuanta:ct10:cvrN/A: dmi.product.name: compaq nx9020 (PG662ES#AKC) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-19-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 554835] Re: xorg crashes when an application tries to use XVideo
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43009046/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/43009047/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/43009048/Dependencies.txt ** Attachment added: DkmsStatus.txt http://launchpadlibrarian.net/43009049/DkmsStatus.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/43009050/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/43009051/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/43009052/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/43009053/Lspci.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/43009054/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/43009055/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/43009056/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/43009057/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/43009058/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/43009059/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/43009060/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/43009061/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/43009062/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/43009063/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/43009064/Xrandr.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/43009066/glxinfo.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/43009067/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/43009068/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/43009069/xkbcomp.txt -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 554835] Re: xorg crashes when an application tries to use XVideo
I've attached the xorg.log to this comment. Linux orion 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux version of xserver-xorg is 1:7.5+3ubuntu1, 2:2.9.1-3ubuntu1 for xserver- xorg-video-intel Video: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Subsystem: Hewlett-Packard Company Device 3084 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 10 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Region 1: Memory at e000 (32-bit, non-prefetchable) [size=512K] Region 2: I/O ports at 1800 [size=8] Capabilities: [d0] Power Management version 1 Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: i915 Kernel modules: i915 ** Attachment added: xorg log when crashed http://launchpadlibrarian.net/43009665/Xorg.0.log.old -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 554835] Re: xorg crashes when an application tries to use XVideo
I've found this in the kernel log: Apr 3 23:00:26 orion kernel: [ 575.444041] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Apr 3 23:00:26 orion kernel: [ 575.444056] render error detected, EIR: 0x Apr 3 23:00:26 orion kernel: [ 575.444070] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 27995 at 27994) -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 554835] Re: xorg crashes when an application tries to use XVideo
Applications tries which caused crash: mplayer (with xv output vo) and miro (using xine backend to play video). I am attaching the output of the xvinfo command. ** Attachment added: xvinfo.txt http://launchpadlibrarian.net/43010589/xvinfo.txt -- xorg crashes when an application tries to use XVideo https://bugs.launchpad.net/bugs/554835 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 441505] Re: Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw
** Attachment added: My xorg.conf file http://launchpadlibrarian.net/33044640/xorg.conf -- Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw https://bugs.launchpad.net/bugs/441505 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 441505] Re: Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw
I also have similar problem, it's a single core system, xorg processes uses all the idle CPU and desktop is quite slow to respond. I've upgraded from jaunty (to karmic beta, to be more accurate: the state of ubuntu repositories at october 4) where I hadn't got this problem. I'm using nvidia's binary driver which is in ubuntu repositories. xserver-xorg: Installed: 1:7.4+3ubuntu5 Candidate: 1:7.4+3ubuntu5 Version table: *** 1:7.4+3ubuntu5 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status nvidia-185-kernel-source: Installed: 185.18.36-0ubuntu3 Candidate: 185.18.36-0ubuntu3 Version table: *** 185.18.36-0ubuntu3 0 500 http://archive.ubuntu.com karmic/restricted Packages 100 /var/lib/dpkg/status -- Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw https://bugs.launchpad.net/bugs/441505 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 441505] Re: Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/33044690/Xorg.0.log -- Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw https://bugs.launchpad.net/bugs/441505 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
[Ubuntu-x-swat] [Bug 441505] Re: Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw
By the way, I am using gnome, and I don't run compiz (just plain metacity), but it's a dual screen setup (see xorg.conf). -- Xorg continuously taking up 15% CPU, system slow, GUI windows take several seconds to draw https://bugs.launchpad.net/bugs/441505 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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
