[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11
Probably not related, but "nvidia-driver-535" was mentioned above in a post. I'm now using ppa:vanvugt/mutter and it seems to be fine, but apt also upgraded nvidia driver from 525 to 535 (maybe not related at all just the new nvidia driver was presented now?). Since then I have hard lock-ups on my system what I've never seen before (no keyboard and mouse works). After forced power-off I see this in the kernel log file: Apr 5 15:42:57 rygel kernel: [ 3282.354685] NVRM: GPU at PCI::01:00: GPU-78091d7e-2007-c450-19a1-f764cae07b00 Apr 5 15:42:57 rygel kernel: [ 3282.354689] NVRM: Xid (PCI::01:00): 79, pid='', name=, GPU has fallen off the bus. Apr 5 15:42:57 rygel kernel: [ 3282.354691] NVRM: GPU :01:00.0: GPU has fallen off the bus. Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: A GPU crash dump has been created. If possible, please run Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: nvidia-bug-report.sh as root to collect this data before Apr 5 15:42:57 rygel kernel: [ 3282.354730] NVRM: the NVIDIA kernel module is unloaded. Apr 5 15:43:02 rygel kernel: [ 3287.474709] NVRM: Error in service of callback Apr 5 15:48:05 rygel kernel: [ 3590.071558] Asynchronous wait on fence NVIDIA:nvidia.prime:11cbb timed out (hint:intel_atomic_commit_ready [i915]) I've never seen anything similar before, though I have this very system/install with nvidia's driver since more than a year or so. Since it's probably a totally different issue (though I am not 100% sure), I've reported here: https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-535/+bug/2060303 It seems now this hard lock up occurs several times per day :( Though the terminal slowness/keyboard input lag/etc is gone, which is good, of course! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Jammy: Triaged Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: In Progress Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Verify that input never froze for any perceptible period of time. 4. Run: journalctl -b0 | grep MetaSyncRing 5. Verify the above command does NOT show messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the code being modified. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I've fetched some older versions (again, I am running 22.04.4) of packages gir1.2-mutter-10 libmutter-10-0 and mutter-common and made them into hold status. After a very ugly and dangerous move, namely editing /var/lib/dpkg/status by hand (to comply the dependencies of gnome-shell which was broken by forcing older versions of packages ... maybe I should have simply installed also older version of gnome-shell, hmm ...), now everything works perfectly again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag in native terminal on Nvidia desktops with X11
I have similar problem. I'm currently using Ubuntu 22.04.4 LTS (x86_64). Since some days (maybe three?) I see very odd behaviour from programs running in gnome-terminal (or xfce4-terminal if it does not matter, I guess the problem is not the terminal itself but VTE probably or similar? - no problem when using KDE's Konsole for example!). I also have nvidia's driver. Some programs "only" have very significant input delay, sometimes like 1 sec or so. However interestingly some programs (most notably neomutt) has "infinite" delay, ie, it lags behind exactly one key. For example if I move upwards in the email list, then pressing down still moves up once. And so on, it seems to be true for all keys. Other applications running in terminal seems to "only" have more significant delay, but it's not always consistent. Especially ssh'ing to a remote machine is a very bad experience now, but even on the local host, without any ssh involved just the shell, it's very notable. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy $ dpkg -l | grep mutter ii gir1.2-mutter-10:amd6442.9-0ubuntu7 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu7 all shared files for the Mutter window manager -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag in native terminal on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
22.04 fresh install, even worse, the window shrunk by 3 lines each time :-O And now even shrinks by 3 rows ... I use toggle full screen back and forth, since this is what I really use a lot, not the maximize. But maximize has the same effect, just checked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
I'm using 20.04.2 LTS (focal), I can also confirm the problem exists there with Xorg and gnome-shell (no idea about 20.10 and/or Wayland though). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881038] [NEW] when trying to lock my screen I always get: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
Public bug reported: When I try to lock the screen, gnome-shell seems to crash, always since two days or so (I update daily basis). crash file is attached. x86_64 Ubuntu 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 01:38:46 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-06 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "crash file" https://bugs.launchpad.net/bugs/1881038/+attachment/5377584/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881038 Title: when trying to lock my screen I always get: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() Status in gnome-shell package in Ubuntu: New Bug description: When I try to lock the screen, gnome-shell seems to crash, always since two days or so (I update daily basis). crash file is attached. x86_64 Ubuntu 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 01:38:46 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-06 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825559] [NEW] Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted
Public bug reported: I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however if I enter gnome shell "overview mode" I cannot leave it anymore, I can't select any window, type to search etc, and all my windows are in the foreground, covering the search bar etc, but not possible to select them. Simply I can't do anything. I can launch applications from the dock but cannot see and access them anymore. So basically I stuck in overview mode which does not work too much. What I can do, is to use the top panel to log out. If I do that, and login again, I only get a black screen and nothing more. I have to press the power button at that point to shut the computer off, so I can turn on again. It seems everything works, just entering into that "overview mode" kills everything then and only reboot helps from that point. Sorry, I am not sure what the official name of the gnome3 shell "overview mode" possibly I used the wrong terminology. Also, my bad English cannot help either to express the problem well enough, I guess. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825559 Title: Upgrading 18.10 to 19.04: cannot leave overview mode, computer needs to be restarted Status in gnome-shell package in Ubuntu: New Bug description: I've upgraded my Ubuntu 18.10 to 19.04. Everything looked okey, however if I enter gnome shell "overview mode" I cannot leave it anymore, I can't select any window, type to search etc, and all my windows are in the foreground, covering the search bar etc, but not possible to select them. Simply I can't do anything. I can launch applications from the dock but cannot see and access them anymore. So basically I stuck in overview mode which does not work too much. What I can do, is to use the top panel to log out. If I do that, and login again, I only get a black screen and nothing more. I have to press the power button at that point to shut the computer off, so I can turn on again. It seems everything works, just entering into that "overview mode" kills everything then and only reboot helps from that point. Sorry, I am not sure what the official name of the gnome3 shell "overview mode" possibly I used the wrong terminology. Also, my bad English cannot help either to express the problem well enough, I guess. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965921] Re: gnome-shell most keyboard shortcuts not working
Still happens time to time, even with fresh 18.10 install. It's a "miracle" that it's such an old bug, but still hits us :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Precise: Confirmed Status in Baltix: New Bug description: Updated Bug Description === For Ubuntu 12.04, System Settings (gnome-control-center and gnome- settings-daemon) was patched to continue to support the gconf keyboard shortcuts used by Unity, Unity 2D, and the GNOME Classic sessions. Unfortunately, GNOME Shell now uses gsettings keyboard shortcuts so GNOME Shell ignores keyboard shortcut changes that get entered into System Settings>Keyboard>Shortcuts. This should be fixed for Ubuntu 12.10 but it's too late and complicated to fix for Ubuntu 12.04. One Workaround == Install dconf-tools Run dconf-editor Look in org.gnome.desktop.wm.keybindings or org.gnome.mutter.keybindings Another Workaround == Set a custom keyboard shortcut. This is useful if you want to set Ctrl+Alt+F to open Firefox for instance. In System Settings, click Keyboard. Switch to the Shortcuts tab and click Custom Shortcuts at the bottom of the list. Click the + button and add a name to remember the shortcut and the specific command you want to execute. Click Apply. Find the name in the list and click the right half of the row. "Disabled" should change to "New accelerator". Enter the keyboard shortcut you want to use. Ctrl+Alt+T to open the terminal and several other usual shortcuts from Unity have been added to GNOME Shell on April 17. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 07:07:44 2012SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: gnome-bluetooth3.2.2-0ubuntu4 indicator-datetime 0.3.92-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 So, as thinking on this, I must say, maybe this is my mis-interpretation of the problem. Maybe not the colour prompt causes this, but if I use a newer (or ssh into a newer) ubuntu box versus ssh into an older version (in both cases ssh in the window only changes the situation of "shrinking" if the window title is modified to reflect this, ie like username@machine1:~ changes into username@machine2:~ because of the ssh). I really feel bad not to be able to express this in a sane way, but it's kind of odd issue for me at least. Just changing PS1 does not change the situation for me either. Ok, now it's even more odd, just trying to test it ... Now window shrinks by TWO lines not only one, and the behaviour I tried to describe above seems not to apply at all :-O I don't know what I can say, maybe this is a more complex issue and my assumption was only true for the given case when I last tested it ...Sorry about that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle Status in gnome-terminal package in Ubuntu: New Bug description: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 I don't know how to tell, but it seems the bug happens when the prompt has effect on the title of the window. What I mean here: opening a gnome-terminal with a colourful PS1 causes this. However if I ssh into another machine which does update the title of the window and the prompt does not use colour, the shrinking stops if I try fullscreen/back cycles again ... If I ssh into a machine which does have this "new" colour prompt then it continues ... If I ssh into a machine which does not effect the title bar, it does not effect the strange behaviour though. So, what I can think about there is some connection about the window bar title updating by the prompt (???) sorry, I have really no idea hot it happens :-O -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle Status in gnome-terminal package in Ubuntu: New Bug description: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in xorg-server package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 965921] Re: gnome-shell most keyboard shortcuts not working
Oh, by the way, it's often happens after locking then unlocking the screen though! It often fixes the problem too (if it was before). But not always ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Precise: Confirmed Status in Baltix: New Bug description: Updated Bug Description === For Ubuntu 12.04, System Settings (gnome-control-center and gnome- settings-daemon) was patched to continue to support the gconf keyboard shortcuts used by Unity, Unity 2D, and the GNOME Classic sessions. Unfortunately, GNOME Shell now uses gsettings keyboard shortcuts so GNOME Shell ignores keyboard shortcut changes that get entered into System Settings>Keyboard>Shortcuts. This should be fixed for Ubuntu 12.10 but it's too late and complicated to fix for Ubuntu 12.04. One Workaround == Install dconf-tools Run dconf-editor Look in org.gnome.desktop.wm.keybindings or org.gnome.mutter.keybindings Another Workaround == Set a custom keyboard shortcut. This is useful if you want to set Ctrl+Alt+F to open Firefox for instance. In System Settings, click Keyboard. Switch to the Shortcuts tab and click Custom Shortcuts at the bottom of the list. Click the + button and add a name to remember the shortcut and the specific command you want to execute. Click Apply. Find the name in the list and click the right half of the row. "Disabled" should change to "New accelerator". Enter the keyboard shortcut you want to use. Ctrl+Alt+T to open the terminal and several other usual shortcuts from Unity have been added to GNOME Shell on April 17. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 07:07:44 2012SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: gnome-bluetooth3.2.2-0ubuntu4 indicator-datetime 0.3.92-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965921] Re: gnome-shell most keyboard shortcuts not working
This bug still affects me now, upgraded to the to-be-released 17.10 (artful). I was a die hard text only user of Linux systems for a while, so I still configure system to "emulate" something like this, ie ALT+F1...F8 to switch between workspaces. However, ALT-F5 does not _always_ works. Sometimes it does sometimes it doesn't and even it changes behaviour from time to time without reboot, logout or anything, which is strange. I can't find how I tell that alt-f5 is _my_ shortcut. It's very annoying that system randomly 'forgets' it, and then somehow remembers it again after some time :-O -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/965921 Title: gnome-shell most keyboard shortcuts not working Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Precise: Confirmed Status in Baltix: New Bug description: Updated Bug Description === For Ubuntu 12.04, System Settings (gnome-control-center and gnome- settings-daemon) was patched to continue to support the gconf keyboard shortcuts used by Unity, Unity 2D, and the GNOME Classic sessions. Unfortunately, GNOME Shell now uses gsettings keyboard shortcuts so GNOME Shell ignores keyboard shortcut changes that get entered into System Settings>Keyboard>Shortcuts. This should be fixed for Ubuntu 12.10 but it's too late and complicated to fix for Ubuntu 12.04. One Workaround == Install dconf-tools Run dconf-editor Look in org.gnome.desktop.wm.keybindings or org.gnome.mutter.keybindings Another Workaround == Set a custom keyboard shortcut. This is useful if you want to set Ctrl+Alt+F to open Firefox for instance. In System Settings, click Keyboard. Switch to the Shortcuts tab and click Custom Shortcuts at the bottom of the list. Click the + button and add a name to remember the shortcut and the specific command you want to execute. Click Apply. Find the name in the list and click the right half of the row. "Disabled" should change to "New accelerator". Enter the keyboard shortcut you want to use. Ctrl+Alt+T to open the terminal and several other usual shortcuts from Unity have been added to GNOME Shell on April 17. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 07:07:44 2012SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: gnome-bluetooth3.2.2-0ubuntu4 indicator-datetime 0.3.92-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1373070] Re: full fix for disconnected path (paths)
Same problem with powerdns, I can't run it with apparmor profile, because it complains: operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/pdns_server" name="run/systemd/journal/dev- log" pid=17236 comm="pdns_server" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 I am not an expert, but I tried to put run/systemd/journal/dev-log into the profile, but it is not accepted as it does not start with / ... But this is what kernel log suggest, so what can I do otherwise? Note: I have: /usr/sbin/pdns_server flags=(complain,attach_disconnected) But still ... (now I have only complain mode). If I exclude pdns from systemd it works btw, and no wonder as it seems the problem somehow connected to systemd's journal, so it's better not to use systemd if possible since it renders apparmor unusable in my experience :( But for sure, I would be more than happy to have a better option, rather than deleting systemd's unit file each time after upgrade pdns ... Or so. this is up-to-date Ubuntu 16.04.3 LTS 64 bit, fresh install, but I have about a dozen of servers with this problem with different daemons as well, not only powerdns. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: Confirmed Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
I've just noticed: it seems it only happens if the shell prompt is colourfull. if it's not, there is no shrinking of the gnome-terminal window height when cycling between fullscreen and windowed mode ... Interesting!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle Status in gnome-terminal package in Ubuntu: New Bug description: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706008] [NEW] gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle
Public bug reported: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wayland-session zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1706008 Title: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle Status in gnome-terminal package in Ubuntu: New Bug description: It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11 configured to toggle between fullscreen and windowed mode. Just noticed, that every time I press F11 to get full screen, then F11 to get back windowed mode, the window becomes one line shorter ... Continuing this I can hit the situation to have only a one line tall window. It's kinda annoying, since during my work I use tons of terminal windows, and I often use full screen / windowed mode switching. Now, I have to resize the window again and again before it becomes too shallow ... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 24 11:14:01 2017 InstallationDate: Installed on 2015-07-10 (744 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1706008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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:
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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:
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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.
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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
[Desktop-packages] [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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
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.
[Desktop-packages] [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
[Desktop-packages] [Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
I've attached some screen shots, if it's more understandable than my not-so-perfect English, sorry about that. Moreover, I had the suspect that it can be a generic window manager issue more, rather than gnome-terminal specific problem, but starting the KDE console (konsole) its fullscreen toggle functionality seems to be OK, just I have problem with the gnome-terminal, it seems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 Status in gnome-terminal package in Ubuntu: New Bug description: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573563] [NEW] Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
Public bug reported: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial ** Attachment added: "Screenshot before pressing F11" https://bugs.launchpad.net/bugs/1573563/+attachment/4642820/+files/Screenshot%20from%202016-04-22%2014-09-39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 Status in gnome-terminal package in Ubuntu: New Bug description: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
** Attachment added: "Screenshot after pressing F11 again, not OK!" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642825/+files/Screenshot%20from%202016-04-22%2014-10-13.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 Status in gnome-terminal package in Ubuntu: New Bug description: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10
** Attachment added: "Screenshot after pressing F11 (fullscreen, OK)" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+attachment/4642824/+files/Screenshot%20from%202016-04-22%2014-09-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1573563 Title: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10 Status in gnome-terminal package in Ubuntu: New Bug description: I use tons of terminal windows (gnome-terminal) all the time for various tasks. Thus, it's important for me to be able to go into full screen mode (F11) - if I need more attention or space and switch back later. I haven't got any problem with this in previous Ubuntu versions, after "switching back" from fullscreen mode, I got the terminal window at its original place and size. However, after upgrading to Ubuntu 16.04 recently, if I press F11 to switch back, the terminal window is enlarged to cover almost the full desktop, it's not "full screen" anymore (that's OK), ie I can see panel, borders, etc, but still it's not the original size and position of the window. So I have to manually resize the window all the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Fri Apr 22 13:48:12 2016 InstallationDate: Installed on 2014-05-08 (715 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1573563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in xorg package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 1434396] Re: Xserver does not start or freezes with systemd + lightdm
Meanwhile, I've upgraded to 15.10. Now the system _mostly_ works, but let's say about every 5th boot the system freezes with black screen if systemd is used. Upstart always work. Interestingly in most cases systemd works as well, but not always. I cannot find any reason about this always changing behaviour if I try to boot multiple times. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start or freezes with systemd + lightdm Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1508219] Re: Possible high CPU usage by firefox while screen is locked
I'm sorry but now it *seems* for me, that it's not firefox, but maybe compiz related (hmmm, or both?), please read the newer bug report of mine: bug 1516308 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1508219 Title: Possible high CPU usage by firefox while screen is locked Status in firefox package in Ubuntu: Confirmed Bug description: It's a bit fuzzy report, I have to admit, and more like a feeling, as I can't check it out too well, but I haven't experienced that in previous Ubuntu versions before upgrading to Wily. I have firefox running with many tabs open. The CPU usage (without too much active pages, ie no videos etc) is about 10-30% at max. If I lock my computer I always hear the fan of the notebook switches onto a higher speed, which disappears if I unlock the screen. It's a bit hard to check it out, if it's really because of firefox, as I can only use "top" if my desktop is unlocked of course, but I can still notice that CPU usage of firefox is still about decreasing after unlocking. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 41.0.2+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lgb2439 F pulseaudio BuildID: 20151016093451 Channel: Unavailable CurrentDesktop: Unity Date: Tue Oct 20 23:48:56 2015 DefaultProfilePlugins: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so (icedtea-7-plugin) Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) DefaultProfilePrefSources: prefs.js ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-03-03 (1326 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MostRecentCrashID: bp-c1602958-abcf-49cb-af9c-c95172151003 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so (icedtea-7-plugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=41.0.2/20151016093451 (In use) Profile1 - LastVersion=39.0a2/20150414004003 (Out of date) RelatedPackageVersions: icedtea-7-plugin 1.5.2-1ubuntu2 google-talkplugin 5.41.0.0-1 rhythmbox-mozilla 3.2.1-1ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: Upgraded to wily on 2015-10-18 (2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1508219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1501250] Re: double clicking on a URL drops the protocol from the URL
Quite ugly "bug" :( I had the habit "since ages" (ehhh) to work in terminal windows, and copy URLs etc. It worked nicely with a quick double click on the URL which does not work anymore after upgrade to Wily :( I understand that it was not meant to select URLs anyway (and not a perfect solution either), but in practice it worked reasonably well. I've just wanted to write a bug report about this, however launchpad was intelligent enough to find me a similar already existing bug report, this one ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1501250 Title: double clicking on a URL drops the protocol from the URL Status in Gnome Virtual Terminal Emulator: Unknown Status in gnome-terminal package in Ubuntu: Confirmed Bug description: After upgrading to 15.10 beta from 15.04, when I double click on a URL, I lose most of the protocol, e.g. if I type 'http://www.ubuntu.com/' into a terminal and double click, what gets selected (and entered into the copy buffer) is '//www.ubuntu.com' To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1501250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1508219] [NEW] Possible high CPU usage by firefox while screen is locked
Public bug reported: It's a bit fuzzy report, I have to admit, and more like a feeling, as I can't check it out too well, but I haven't experienced that in previous Ubuntu versions before upgrading to Wily. I have firefox running with many tabs open. The CPU usage (without too much active pages, ie no videos etc) is about 10-30% at max. If I lock my computer I always hear the fan of the notebook switches onto a higher speed, which disappears if I unlock the screen. It's a bit hard to check it out, if it's really because of firefox, as I can only use "top" if my desktop is unlocked of course, but I can still notice that CPU usage of firefox is still about decreasing after unlocking. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 41.0.2+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lgb2439 F pulseaudio BuildID: 20151016093451 Channel: Unavailable CurrentDesktop: Unity Date: Tue Oct 20 23:48:56 2015 DefaultProfilePlugins: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so (icedtea-7-plugin) Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so (google-talkplugin) iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) DefaultProfilePrefSources: prefs.js ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-03-03 (1326 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MostRecentCrashID: bp-c1602958-abcf-49cb-af9c-c95172151003 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: IcedTea-Web Plugin (using IcedTea-Web 1.5.2 (1.5.2-1ubuntu2)) - /usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/IcedTeaPlugin.so (icedtea-7-plugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=41.0.2/20151016093451 (In use) Profile1 - LastVersion=39.0a2/20150414004003 (Out of date) RelatedPackageVersions: icedtea-7-plugin 1.5.2-1ubuntu2 google-talkplugin 5.41.0.0-1 rhythmbox-mozilla 3.2.1-1ubuntu3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: True SourcePackage: firefox UpgradeStatus: Upgraded to wily on 2015-10-18 (2 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 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1508219 Title: Possible high CPU usage by firefox while screen is locked Status in firefox package in Ubuntu: New Bug description: It's a bit fuzzy report, I have to admit, and more like a feeling, as I can't check it out too well, but I haven't experienced that in previous Ubuntu versions before upgrading to Wily. I have firefox running with many tabs open. The CPU usage (without too much active pages, ie no videos etc) is about 10-30% at max. If I lock my computer I always hear the fan of the notebook switches onto a higher speed, which disappears if I unlock the screen. It's a bit hard to check it out, if it's really because of firefox, as I can only use "top" if my desktop is unlocked of course, but I can still notice that CPU usage of firefox is still about decreasing after unlocking. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 41.0.2+build2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu3
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on freezes with systemd + lightdm
** Summary changed: - Xserver does not start on boot (low-graphics mode) + Xserver does not start on freezes with systemd + lightdm ** Summary changed: - Xserver does not start on freezes with systemd + lightdm + Xserver does not start or freezes with systemd + lightdm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start or freezes with systemd + lightdm Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
This bug seems to be still valid, but its behaviour is somewhat different at least for me. When I first noticed this, X did not start at all, and it dropped to the screen to allow to choose for low graphics mode, exit to console, etc. Now, X starts however it freezes in a way that no keyboard can be used (ie to type my password to be able to log in). I use the system with upstart to work the problem around, but of course it would be better to forget those workarounds ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
It seems though it can be guessed more or less what can cause problems (ie thinkpad + lightdm + systemd) the exact details are not the same, and some other conditions can/do count as well. Also the not always factor sometimes, kinda odd. However, as bug 1340964 if often referenced for me, and it is about some kind of VT activation problem, can it be because some race condition on using VTs or such? Since systemd may do deeper parallelism on the boot process than upstart (I am not sure just guessing) or at least it did it not the very same way, it can explain why it works with upstart but not with systemd. But really, I am just guessing, and trying to give hints, as release data for vivid is coming and this bug still exists rendering ubuntu totally unusable for normal users on some hardware like some thinkpad notebooks which are not so rare, I think. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
For me, it's kinda odd. It seem to work (and worked even some day ago), then trying again (boot again) and it does not work again then ... Recently it seems to be quite unpredictable. But it can be a reason that sometimes I attach external monitor via the VGA D-SUB connector, but sometimes I don't. I'll check both cases out soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Ok, I was too fast ... Tried again: now, X server starts and logic screen is shown (though with the default background not the one based on the last user logged in) but keyboard does not usable and no mouse cursor either. Still, choosing upstart seems to work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Today I tried again and now it seems system boots normally, I can log in, with lightdm+systemd. I guess some of the updates solved the problem, but it would be useful to hear that it's not only me ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
@asala But does using upstart (or systemd, but with gdm instead of lightdm) fixes it for you? Then it can be said, at least lightdm+systemd issue ... However reading duplicates, and comments here, at least it seems, Lenovo Thinkpads are highly affected for some reason, even if not only ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
ThinkPad L520: exactly the same as professordes wrote: systemd + lightdm does not work, dropping to console login freezes (interestingly it worked some days ago when I managed to use service lightdm stop/start to cure the problem at least so systemd could be used with some extra work though, not the system is simply not usable with systemd). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Now it turns out even more bizarre, I can no longer use my notebook with systemd. After having that low-graphics dialog, only exit to console helped (eg stopping/starting lightdm service by hand) but now exit to console cause a freeze that the computer does not react to keyboard anymore (not even num lock led etc). Though sysreq magic key combos seem to work. The only option now is to choose upstart from grub. Then system boots without any problem (not even need to exit console etc) as it should be. Again apport wanted to report Xorg crash after a reboot with upstart, but again, bug 1340964 is referenced. It seems nothing bad happens with upstart, only systemd though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1340964 Title: Xorg crashed with SIGABRT in _XSERVTransClose() Status in xorg-server package in Ubuntu: Confirmed Bug description: received the message at start. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.15.0-6.11-lowlatency 3.15.0 Uname: Linux 3.15.0-6-lowlatency x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Wed Jul 9 17:14:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0136] Subsystem: Acer Incorporated [ALI] Device [1025:0136] InstallationDate: Installed on 2014-06-19 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64+mac (20140619) LightdmGreeterLog: ** (lightdm-gtk-greeter:1640): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:1640): WARNING **: Failed to load user image: Failed to open file '/home/gerardo/.face': No such file or directory LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1609): WARNING **: Failed to load user image: Failed to open file '/home/gerardo/.face': No such file or directory MachineType: Acer Aspire 5315 ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-GfZMXs/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_GB.UTF-8 TERM=linux LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-lowlatency root=/dev/mapper/ubuntu--vg-root ro splash quiet crashkernel=384M-:128M vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () CloseWellKnownConnections () ?? () FatalError () ?? () SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: Xorg crashed with SIGABRT in CloseWellKnownConnections() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Acadia dmi.board.vendor: Acer dmi.board.version: V1.43 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.43 dmi.modalias: dmi:bvnAcer:bvrV1.43:bd06/25/2008:svnAcer:pnAspire5315:pvrV1.43:rvnAcer:rnAcadia:rvrV1.43:cvnAcer:ct1:cvrV1.43: dmi.product.name: Aspire 5315 dmi.product.version: V1.43 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jul 11 21:43:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10100 vendor AUO xserver.version: 2:1.15.1-0ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
And it seems after I can login the crash report dialog brings me to bug 1340964 then. What is interesting for me: why is there a problem Xorg does not start, when it does if I try it then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in lightdm package in Ubuntu: Confirmed Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1340964 Title: Xorg crashed with SIGABRT in _XSERVTransClose() Status in xorg-server package in Ubuntu: Confirmed Bug description: received the message at start. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.15.0-6.11-lowlatency 3.15.0 Uname: Linux 3.15.0-6-lowlatency x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Wed Jul 9 17:14:26 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0136] Subsystem: Acer Incorporated [ALI] Device [1025:0136] InstallationDate: Installed on 2014-06-19 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64+mac (20140619) LightdmGreeterLog: ** (lightdm-gtk-greeter:1640): WARNING **: Failed to load background: Failed to open file '/usr/share/lubuntu/wallpapers/lubuntu-default-wallpaper.png': No such file or directory ** (lightdm-gtk-greeter:1640): WARNING **: Failed to load user image: Failed to open file '/home/gerardo/.face': No such file or directory LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1609): WARNING **: Failed to load user image: Failed to open file '/home/gerardo/.face': No such file or directory MachineType: Acer Aspire 5315 ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-GfZMXs/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_GB.UTF-8 TERM=linux LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.0-6-lowlatency root=/dev/mapper/ubuntu--vg-root ro splash quiet crashkernel=384M-:128M vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () CloseWellKnownConnections () ?? () FatalError () ?? () SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown Title: Xorg crashed with SIGABRT in CloseWellKnownConnections() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/25/2008 dmi.bios.vendor: Acer dmi.bios.version: V1.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Acadia dmi.board.vendor: Acer dmi.board.version: V1.43 dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: V1.43 dmi.modalias: dmi:bvnAcer:bvrV1.43:bd06/25/2008:svnAcer:pnAspire5315:pvrV1.43:rvnAcer:rnAcadia:rvrV1.43:cvnAcer:ct1:cvrV1.43: dmi.product.name: Aspire 5315 dmi.product.version: V1.43 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Jul 11 21:43:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10100 vendor AUO xserver.version: 2:1.15.1-0ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1340964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)
Hmm, reading the duplicates, it seems it's a Lenovo notebook + systemd + lightdm combined problem, and does not occur too much if all of the three conditions do not meet? For me, it's true, all of them, and I have the problem at least ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in lightdm package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start, on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434396 Title: Xserver does not start on boot (low-graphics mode) Status in xorg package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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:
[Desktop-packages] [Bug 1292209] Re: Locking screen does not work in case of fullscreen gnome-terminal
It happened again now (up-to-date 14.04 LTS now): screen started to fade out after pressing CTRL-ALT-L, then it stuck in the middle of process, I can move the mouse, but I can't do anything neither with mouse or keyboard. What helped: switching to text console (CTRL-ALT-F1) login, then killing gnome-terminal. After that, I can switch back to X.org (ALT-F7) and I see the unlock screen now. However of course this is not an ideal solution, and I lost all of my (tons of ...) gnome-terminal windows. Again: it seems it happens sometimes, if I press CTRL-ALT-L when I have a fullscreen (not maximized, but full screen) gnome-terminal on the current workspace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal Status in “gnome-screensaver” package in Ubuntu: New Bug description: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password blindly (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313895] [NEW] Full screen terminal sometimes allows click-through which shouldn't happen
Public bug reported: I work with terminal windows (gnome-terminal) a lot. I have 8 workspaces and multiple terminals on each of them. Sometimes I need to focus on a more complicated issue eg with a server I am logged on via ssh on a terminal, in this case I use full screen mode. Initially it works. However especially when I switch away from that workspace and then back I often have the situation that everything looks totally OK, but if I try to select text on the top of my terminal window (which needs a click first) the panel rises over as somehow it gets the click it seems (even if I see the full screen window which covers all of the screen). It can be seen even before the click as the text cursor changes into pointer where the panel is (at the top of the screen). Sometimes even the side launcher can be seen (it's configured to auto hide in my case) to come up (since window is configured to be somewhat transparent so I can see what's behind) if I move the mouse at the left edge of the screen. Maybe related but I am not sure: if I have a full screen terminal window which has the focus (so covers all the screen) but another (non- fullscreen) terminal window behind, and I switch workspace away then back, sometimes I see the background window raised over the full screen one, and I don't know why as the fullscreen window was on the top before. Sorry, it's not so easy to describe the problem especially not in a language not native for me. Also it's not happens always, but quite frequently. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-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: Mon Apr 28 21:49:58 2014 DistUpgraded: 2013-10-18 20:44:53,416 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-23-generic, i686: installed virtualbox, 4.3.10, 3.13.0-24-generic, i686: installed 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 (786 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) Lsusb: Bus 002 Device 003: ID 04f2:b228 Chicony Electronics Co., Ltd 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: LENOVO 5016NW6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (192 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.11+14.04.20140423-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 28 18:49:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 package-from-proposed trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity
[Desktop-packages] [Bug 1311316] [NEW] After locking screen there is no input field to type password for unlock
Public bug reported: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in “unity” package in Ubuntu: New Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292965] [NEW] Unlocking screensaver needs two redundant steps
Public bug reported: Up-to-date 32 bit 14.04 on Lenovo L520 notebook. After locking the screen eg with CTRL-ALT-L I want to unlock it, so I give my password. It works, but sometimes after some seconds of unlocked state (I already working, ie typing etc) the screen fades out again and I have to give my password again to unlock. It's even more interesting with my wife's account (on the same machine/OS though): she must type her password two times, and the second password prompt follows immediately, not the very same case as mine. It's another issue and I am not sure if it's related at all: after locking the screen never turns off, which was the behaviour before upgraded to 14.04 and I guess the normal behaviour, as it's not so useful to waste power to show the screen for hours, it should goes of after locking till some keypress and/or mouse movement, I think. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 15 20:55:00 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (742 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (148 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292965 Title: Unlocking screensaver needs two redundant steps Status in “gnome-screensaver” package in Ubuntu: New Bug description: Up-to-date 32 bit 14.04 on Lenovo L520 notebook. After locking the screen eg with CTRL-ALT-L I want to unlock it, so I give my password. It works, but sometimes after some seconds of unlocked state (I already working, ie typing etc) the screen fades out again and I have to give my password again to unlock. It's even more interesting with my wife's account (on the same machine/OS though): she must type her password two times, and the second password prompt follows immediately, not the very same case as mine. It's another issue and I am not sure if it's related at all: after locking the screen never turns off, which was the behaviour before upgraded to 14.04 and I guess the normal behaviour, as it's not so useful to waste power to show the screen for hours, it should goes of after locking till some keypress and/or mouse movement, I think. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 15 20:55:00 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (742 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292183] [NEW] Gmail password dialog box does not work and also can render the desktop useless after login
Public bug reported: After each login a dialog box appears to enter the password of my gmail mailbox. However even if I type the correct password, the dialog box reappears. It seems it's totally unimportant if I type the correct or some incorrect password. The only thing which helps is to cancel the dialog box two times. The more important problem however: the dialog box does not appear immediately after the login, sometimes dozens of seconds pass. If I open some application, terminal, etc, it can cause problems especially if the app is in fullscreen mode: then the dialog box made the desktop unusable, I can't change between windows, I can't type, etc (I have to switch to text console, and stop/start lightdm to cure the problem ... the other workaround is to wait after the login the dialog box to appear cancel it two times and then I can work, but that's a bit hmmm odd). I know the problem is with the dialog box, as I can see through the terminal window, since it's set to be somewhat transparent. It's in this way since upgraded to 13.10 (and now in 14.04 too), one of the main motivation to upgrade to 14.04 was to avoid this very annoying feature. However it seems it's still a problem. Unfortunately I have no idea which app/setting/etc made the system to ask this password and why the correct password is not accepted :( Only today I got some hint by swithing into text console and digging in the process list. It seems there is a process which onky can be found during this problem: /usr/lib/gcr/gcr-prompter That's why I send this report against the gcr package as it seems to own that file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcr 3.10.1-1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 20:27:11 2014 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gcr UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) ** Affects: gcr (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1292183 Title: Gmail password dialog box does not work and also can render the desktop useless after login Status in “gcr” package in Ubuntu: New Bug description: After each login a dialog box appears to enter the password of my gmail mailbox. However even if I type the correct password, the dialog box reappears. It seems it's totally unimportant if I type the correct or some incorrect password. The only thing which helps is to cancel the dialog box two times. The more important problem however: the dialog box does not appear immediately after the login, sometimes dozens of seconds pass. If I open some application, terminal, etc, it can cause problems especially if the app is in fullscreen mode: then the dialog box made the desktop unusable, I can't change between windows, I can't type, etc (I have to switch to text console, and stop/start lightdm to cure the problem ... the other workaround is to wait after the login the dialog box to appear cancel it two times and then I can work, but that's a bit hmmm odd). I know the problem is with the dialog box, as I can see through the terminal window, since it's set to be somewhat transparent. It's in this way since upgraded to 13.10 (and now in 14.04 too), one of the main motivation to upgrade to 14.04 was to avoid this very annoying feature. However it seems it's still a problem. Unfortunately I have no idea which app/setting/etc made the system to ask this password and why the correct password is not accepted :( Only today I got some hint by swithing into text console and digging in the process list. It seems there is a process which onky can be found during this problem: /usr/lib/gcr/gcr-prompter That's why I send this report against the gcr package as it seems to own that file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcr 3.10.1-1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 20:27:11 2014 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gcr UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1292183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1292209] [NEW] Locking screen does not work in case of fullscreen gnome-terminal
Public bug reported: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password blindly (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal Status in “gnome-screensaver” package in Ubuntu: New Bug description: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password blindly (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292209] Re: Locking screen does not work in case of fullscreen gnome-terminal
Btw, the other even more odd workaround: switch to text console, kill gnome-terminal and switch back to the VT used by X, and you can unlock then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292209 Title: Locking screen does not work in case of fullscreen gnome-terminal Status in “gnome-screensaver” package in Ubuntu: New Bug description: Somewhat odd situation. If I use CTRL-ALT-L to lock my session, it normally works as expected. However if there is a fullscreen gnome- terminal (F11) was on the screen, CTRL-ALT-L does something interesting: it begins fade the screen but it's left in a middle state, no way to unlock but also it's not locked visually though I can't type anymore. More interestingly: it seems the screen IS locked, since if I type my password blindly (I still see the half faded session ...) I get back my desktop in a usable state! Interesting. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 13 21:25:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'gnome' org.gnome.desktop.session idle-delay uint32 3600 InstallationDate: Installed on 2012-03-03 (740 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2013-10-18 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1255558] Re: Can't type my password after cold boot
Same here, 32 bit up-to-date (daily updated) 14.04 32 bit on a Lenovo L520 notebook. I can't type password at lightdm login screen, and not even able to move up/down (to select user to log in as) with the keyboard. Just click on the AT icon (without actually selecting anything from there eg onboard keyboard etc) it fixes the problem and then I can type password move up/down to select user and of course able to log in then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/128 Title: Can't type my password after cold boot Status in “unity-greeter” package in Ubuntu: Triaged Bug description: Can't type my password after cold boot unless I change my keyboard layout to next (or change and then re-change to same layout) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1 Uname: Linux 3.12.0-4-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 Date: Wed Nov 27 16:27:13 2013 InstallationDate: Installed on 2013-11-19 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131119) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1290904] [NEW] System behaviour does not follow user settings in some cases
Public bug reported: First of all, sorry, I am not sure what kind of package should I specify with this report. Upgraded to trusty, and some of the user settings are not used (or only temporary) anymore: * I use F12 to open a terminal since ages (I depends most on terminals in my work). Setting that works, but after next login, it's forgotten and must be set again. * Whatever I set up for action in case of closing lid of the notebook it always goes into sleep mode, however I _don't_ want that. I'm not sure if there is common problem of these bugs however, just I think it can be common settings problem ... It's daily updated 32bit system on a Lenovo L520 notebook. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 11 16:16:11 2014 InstallationDate: Installed on 2012-03-03 (738 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2013-10-18 (143 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1290904 Title: System behaviour does not follow user settings in some cases Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: First of all, sorry, I am not sure what kind of package should I specify with this report. Upgraded to trusty, and some of the user settings are not used (or only temporary) anymore: * I use F12 to open a terminal since ages (I depends most on terminals in my work). Setting that works, but after next login, it's forgotten and must be set again. * Whatever I set up for action in case of closing lid of the notebook it always goes into sleep mode, however I _don't_ want that. I'm not sure if there is common problem of these bugs however, just I think it can be common settings problem ... It's daily updated 32bit system on a Lenovo L520 notebook. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Mar 11 16:16:11 2014 InstallationDate: Installed on 2012-03-03 (738 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2013-10-18 (143 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1290904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 1086295] [NEW] Cannot log in with more passwd entries with the same UID
Public bug reported: I am not sure if it's a bug, however this works on the text console without problem since years. Yes, that is ugly, I know: sometimes I need to test (while developing) softwares run as a specific unix user. To make this simple I often used the trick to add a line to /etc/passwd with different user name but the same numeric uid/gid as my account used to log in at lightdm's prompt. Usually I remove that line then, but I forgot it, and after reboot I couldn't log in. According to /var/log/lightdm/lightdm.log lightdm treated as I want to use as this phantom user, which is not true. Using simple console login there is no such a problem. AFAIK it's not so nice/legal to use /etc/passed entries refeering for the same unix numerical uid, so I am not sure if it's a bug which should be fixed, or it's something I shouldn't do, but as I've written above, it works (and always worked since 1995 on Debian/Ubuntu/Slackware/RedHat systems - as far as I can recall) on console logins at least. By the way, I haven't added /etc/shadow entry for the user, only /etc/passwd. And of course I tried to log in with my normal user, not the phantom. thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu7 Architecture: i386 Date: Tue Dec 4 09:39:42 2012 InstallationDate: Installed on 2012-03-01 (277 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-03-01 (277 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1086295 Title: Cannot log in with more passwd entries with the same UID Status in “lightdm” package in Ubuntu: New Bug description: I am not sure if it's a bug, however this works on the text console without problem since years. Yes, that is ugly, I know: sometimes I need to test (while developing) softwares run as a specific unix user. To make this simple I often used the trick to add a line to /etc/passwd with different user name but the same numeric uid/gid as my account used to log in at lightdm's prompt. Usually I remove that line then, but I forgot it, and after reboot I couldn't log in. According to /var/log/lightdm/lightdm.log lightdm treated as I want to use as this phantom user, which is not true. Using simple console login there is no such a problem. AFAIK it's not so nice/legal to use /etc/passed entries refeering for the same unix numerical uid, so I am not sure if it's a bug which should be fixed, or it's something I shouldn't do, but as I've written above, it works (and always worked since 1995 on Debian/Ubuntu/Slackware/RedHat systems - as far as I can recall) on console logins at least. By the way, I haven't added /etc/shadow entry for the user, only /etc/passwd. And of course I tried to log in with my normal user, not the phantom. thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu7 Architecture: i386 Date: Tue Dec 4 09:39:42 2012 InstallationDate: Installed on 2012-03-01 (277 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-03-01 (277 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1086295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1064493] Re: Indicator-applet Disappears After Closing a Conversation
I have whitelisted pidgin for systray icon (well not just pidgin but all). The stange thing: I cannot see pidgin's icon, however during switching workspaces, pidgin icon _can_be_ seen but only for that moment while workspace switching sliding effect is played, then it cannot be seen again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1064493 Title: Indicator-applet Disappears After Closing a Conversation Status in “pidgin” package in Ubuntu: Confirmed Bug description: I run pidgin as a start-up application. Since upgrading to Ubuntu 12.10, pidgin doesn't seem to sustain its applet-indicator (by the clock). Pidgin is running, but I have no way to access it until someone messages me. After closing that conversation. I see no way to access my buddy-list other than trying to launching it again from the Unity dash. I like pidgin to have its own indicator-icon by the clock. In 12.04, I could find pidgin's indicator-icon by clicking the envelope-icon- indicator by the clock, but in 12.10, I see no way to access my buddy list. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pidgin 1:2.10.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Tue Oct 9 11:00:02 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: Upgraded to quantal on 2012-10-04 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1064493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in “xorg-server” package in Ubuntu: New Bug description: 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:
[Desktop-packages] [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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. Status in “xorg” package in Ubuntu: New Bug description: 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. Status in “xorg” package in Ubuntu: New Bug description: 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
[Desktop-packages] [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 Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. Status in “xorg” package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 1052910] Re: Rendering problems in X with various applications.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1052910 Title: Rendering problems in X with various applications. Status in “xorg” package in Ubuntu: New Bug description: 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
[Desktop-packages] [Bug 1011594] [NEW] Dragging of tabs does not work with chrome and firefox
Public bug reported: I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a while (I can't tell the exact point, since I've just noticed it) I can't drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in one thing: it works in oneiric at least, since I have a machine running oneiric. If I try to drag a tab in firefox (version 13, not from ubuntu but installed manually). The twist: I use firefox from another machine (running hardy) but via ssh X11 redirection. However, chrome is running on the local machine. In firefox if I drag a tab, nothing happens: I can see the translucent image of the page and I can drag it, I can't dock it between the tabs, if I release the mouse button, the image just jumps back. With chrome, again: I can see the translucent image, and I can drag it, but again, I can't dock it, if I release the mouse button it creates a new window instead of docking among the already existing tabs in the already existing window at the desired position. It seems that locally launched firefox 13 (from ubuntu repo!) works however. Also tab re-arraning eg in geany seems to be OK. Btw, composite effects are enabled via gconf in metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 Date: Mon Jun 11 14:25:45 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (101 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1011594 Title: Dragging of tabs does not work with chrome and firefox Status in “metacity” package in Ubuntu: New Bug description: I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a while (I can't tell the exact point, since I've just noticed it) I can't drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in one thing: it works in oneiric at least, since I have a machine running oneiric. If I try to drag a tab in firefox (version 13, not from ubuntu but installed manually). The twist: I use firefox from another machine (running hardy) but via ssh X11 redirection. However, chrome is running on the local machine. In firefox if I drag a tab, nothing happens: I can see the translucent image of the page and I can drag it, I can't dock it between the tabs, if I release the mouse button, the image just jumps back. With chrome, again: I can see the translucent image, and I can drag it, but again, I can't dock it, if I release the mouse button it creates a new window instead of docking among the already existing tabs in the already existing window at the desired position. It seems that locally launched firefox 13 (from ubuntu repo!) works however. Also tab re- arraning eg in geany seems to be OK. Btw, composite effects are enabled via gconf in metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 Date: Mon Jun 11 14:25:45 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1011594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1011594] Re: Dragging of tabs does not work with chrome and firefox
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1011594 Title: Dragging of tabs does not work with chrome and firefox Status in “metacity” package in Ubuntu: New Bug description: I'm using Unity-2D (so metacity), up-to-date precise, 32 bit. Since a while (I can't tell the exact point, since I've just noticed it) I can't drag tabs in chrome and firefox (to re-order tabs) anymore. I am sure in one thing: it works in oneiric at least, since I have a machine running oneiric. If I try to drag a tab in firefox (version 13, not from ubuntu but installed manually). The twist: I use firefox from another machine (running hardy) but via ssh X11 redirection. However, chrome is running on the local machine. In firefox if I drag a tab, nothing happens: I can see the translucent image of the page and I can drag it, I can't dock it between the tabs, if I release the mouse button, the image just jumps back. With chrome, again: I can see the translucent image, and I can drag it, but again, I can't dock it, if I release the mouse button it creates a new window instead of docking among the already existing tabs in the already existing window at the desired position. It seems that locally launched firefox 13 (from ubuntu repo!) works however. Also tab re- arraning eg in geany seems to be OK. Btw, composite effects are enabled via gconf in metacity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 Date: Mon Jun 11 14:25:45 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1011594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 985449] [NEW] unity-2d launcher behind a full screen window
Public bug reported: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi-transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/985449 Title: unity-2d launcher behind a full screen window Status in “metacity” package in Ubuntu: New Bug description: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi- transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 985449] Re: unity-2d launcher behind a full screen window
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/985449 Title: unity-2d launcher behind a full screen window Status in “metacity” package in Ubuntu: New Bug description: Not exactly a show-stopper bug ... I have a terminal window, not maximazed, but full screen. I'm using Unity-2D+metacity, with composite support is switched on. The terminal window is semi- transparent. Now, if I move the mouse to the left side of the screen, I can see (through the semi transparent window) that Unity-2D's launcher is shown (it's configured for auto-hide). I guess it's a problem, since in case of a full screen window, I wouldn't except that anything other is activated if I move the mouse through the screen, as the screen is filled with a full screen window, so no other thing should be involved. The only problem I have with this: if I switch workspace then, unity-2d's launcher is still shown, so I have to move the mouse pointer on it, and then remove so it can be hidden, which is a bit annoying to do all the time, as I would like auto-hide ... Maybe it's not a metacity but an unity-2d problem? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Thu Apr 19 09:34:33 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/985449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980013] [NEW] moving icons on the desktop leaves some garbage
Public bug reported: I'm using Unity-2D with metacity (composite effects are on). I also switched on icons on the desktop (computer, home, mounted filesystems), but I have custom ones too. If I want to move an icon by dragging it, ugly garbage is left on the screen where I move that icon. The garbage disappears if I click onto some of the unused part of the desktop though. For sure, it's not a show-stopper bug, but looks quite ugly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Thu Apr 12 17:54:13 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (41 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/980013 Title: moving icons on the desktop leaves some garbage Status in “metacity” package in Ubuntu: New Bug description: I'm using Unity-2D with metacity (composite effects are on). I also switched on icons on the desktop (computer, home, mounted filesystems), but I have custom ones too. If I want to move an icon by dragging it, ugly garbage is left on the screen where I move that icon. The garbage disappears if I click onto some of the unused part of the desktop though. For sure, it's not a show-stopper bug, but looks quite ugly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Thu Apr 12 17:54:13 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/980013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 980013] Re: moving icons on the desktop leaves some garbage
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/980013 Title: moving icons on the desktop leaves some garbage Status in “metacity” package in Ubuntu: New Bug description: I'm using Unity-2D with metacity (composite effects are on). I also switched on icons on the desktop (computer, home, mounted filesystems), but I have custom ones too. If I want to move an icon by dragging it, ugly garbage is left on the screen where I move that icon. The garbage disappears if I click onto some of the unused part of the desktop though. For sure, it's not a show-stopper bug, but looks quite ugly. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 Date: Thu Apr 12 17:54:13 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/980013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971322] [NEW] Unity-2D/metacity window placement/move problems in precise
Public bug reported: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed stacked on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of free space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border resistance. In oneiric, if I move a window, there is need for a little push more action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using auto hide for Unity. There is similar problem vertically however the gap is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise Status in “metacity” package in Ubuntu: New Bug description: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed stacked on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of free space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border resistance. In oneiric, if I move a window, there is need for a little push more action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using auto hide for Unity. There is similar problem vertically however the gap is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971322] Re: Unity-2D/metacity window placement/move problems in precise
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise Status in “metacity” package in Ubuntu: New Bug description: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed stacked on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of free space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border resistance. In oneiric, if I move a window, there is need for a little push more action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using auto hide for Unity. There is similar problem vertically however the gap is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971322] Re: Unity-2D/metacity window placement/move problems in precise
Also it seems workspace switcher does not support wrapping: ie if I am at the first workspace, using switch to workspace at the left would cause (in oneiric it works) to the last one and vice versa. This behaviour _is_ enabled, I've just checked gconf settings, but it does not work anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/971322 Title: Unity-2D/metacity window placement/move problems in precise Status in “metacity” package in Ubuntu: New Bug description: I've upgraded oneiric to precise (32 bit). One annoying problem is the window placement/moving policy now. In oneiric this worked (I am using Unity-2D, so metacity, composing manager/effects are enabled) very well. If I open a new window, it will be placed stacked on existing window (eg if I open a new terminal (usually I have to open more of them), even if there is lots of free space on the workspace. So, I think metacity in oneiric tries to use available 'free' screen space, which is not true for oneiric. Another annoying thing is the window border resistance. In oneiric, if I move a window, there is need for a little push more action to be able to move window when border is at another window's border. It's a great help to align windows in a nice way. In precise, this does not work, or at least it behaves oddly: if I move a window towards another horizontally this _is_ this effect, however not at the border but _before_ it! There is a huge space, probably the same size as the Unity launcher bar, is it possible, that positions are miscalculated? I am using auto hide for Unity. There is similar problem vertically however the gap is smaller, and I have no idea if there is some relation of the size of the gap and any other thing. It's about half of the height of the top panel, for example. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: metacity 1:2.34.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic-pae 3.2.13 Uname: Linux 3.2.0-21-generic-pae i686 ApportVersion: 2.0-0ubuntu2 Architecture: i386 Date: Mon Apr 2 09:05:42 2012 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release i386 (20100816.2) SourcePackage: metacity UpgradeStatus: Upgraded to precise on 2012-03-01 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/971322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Is it possible that it's not the bug of gnome-session (I was reported as)? Maybe it should be moved to the right package, at least deletion of /etc/X11/Xsession.d/20desktop-profiles_activateDesktopProfiles helped, and that file is part of pacakge desktop-profiles and rdepends on edubuntu-menueditor according to apt-cache. But that package exited in natty too before I upgraded (and I still has it on other natty systems without problem), so it should be some kind of regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: Confirmed Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Still some minor issues left, like missing icons (firefox etc), maybe that's the problem of bad XDG_DATA_DIRS. I wonder if I made misstake to always install meta packages for kubuntu, edubuntu, xubuntu, etc too, since as far as I can recall, that file you suggested to remove is part of edubuntu package, or something like that ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
I would be surprised, if a specific bug like this is caused by a hardware failure, especially because I am using that notebook since months without a single problem (with previous versions of Ubuntu, too). Also, other DEs, like KDE seems to work nicely, with many resource hungry tasks (which usually triggers bugs like ones with disk I/O, memory or CPU). I've also tried to re-install packages you've mentioned but it did not help. Anyway, just to be sure, I will check it with memcheck at this evening. Also I am thinking to try to reinstall the system (it was an upgrade from natty) to see if it helps, if there is no further ideas to cure the problem; just I thought it can be useful to track this bug if others may have it too ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
I've removed sabayon (dpkg --purge sabayon). I have even done a reboot then. However the problem remains. I've attached the whole .xsession- errors file (I've tested with a totally new and clean user). I've tested memory with memtest for a while at least, as I thought; no problem has been found. However there is one thing, I don't know if related or note, but here it is: I often see during package install/upgrade/etc: Processing triggers for man-db ... Processing triggers for hicolor-icon-theme ... Processing triggers for libglib2.0-0 ... Processing triggers for gconf2 ... Processing triggers for gnome-menus ... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for desktop-file-utils ... Processing triggers for shared-mime-info ... Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' Unknown media type in type 'interface/x-winamp-skin' Note that '/usr/share' is not in the search path set by the XDG_DATA_HOME and XDG_DATA_DIRS environment variables, so applications may not be able to find it until you set them. The directories currently searched are: - /root/.local/share - /usr/share/kde-plasma - - ** Attachment added: .xsession-errors https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+attachment/2535316/+files/.xsession-errors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
By the way, by google'ing a bit, I found something which seems to be a bit similar to my problem at least: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=633851 Also there was an article mentioning that all your gconf schemas have been unregistered for some reason and suggesting this: cd /usr/share/gconf/schemas/ sudo /usr/sbin/gconf-schemas --register *.schemas However this was a quite old post so I doubt it's my case (and btw, it hasn't worked anyway ...) ** Bug watch added: Debian Bug tracker #633851 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633851 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Just one thing (I don't know if it's a problem or not): on a natty system there is file: /usr/share/gconf/schemas/gnome-session.schemas However on my promlematic oneiric notebook is does not exist. However since they are different ubuntugnme releases, maybe it's not even a problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Command gsettings get org.gnome.desktop.session session says: No such schema 'org.gnome.desktop.session'. Setting envvar XDG_DATA_DIRS to /usr/share does not seem to help. The output of grep (with also the -n option) is attached. ** Attachment added: grep.output https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+attachment/2535512/+files/grep.output -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Wow! Yes. With removing (well, moving away to have a backup) I could log in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
@Anakin: hmm, but does it mean that oneiric will be released as stable that I can't even log in to the system? It sounds quite painfull -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
I've reinstall the mentioned packages (apt-get --reinstall install ...) but still no success. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
@Sebastien: thanks for your answer! gnome-session-bin: 3.2.0-0ubuntu2 gconf2: 3.2.0-0ubuntu1 libglib2 is not installed, not even an installable package exists with that name (according to apt-get install) Similar package name seems to be libglib2.0-0 , it's installed, and version is: 2.30.0-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Sorry for the huge amount of comments from me, but I think this bug is simply a show-stopper, since system can't be used at all (well of course, if someone can run another kind of session than gnome ...). I try almost every day to upgrade the system and check the situation with oneiric, but still, the result is the same :( If there is some problem with my bug report (so you can't work with it too much) please note, and I try to help more to identify the problem. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
lgb@orion:~$ gnome-session --version gnome-session 3.2.0 lgb@orion:~$ dpkg -S `which gnome-session` gnome-session-bin: /usr/bin/gnome-session lgb@orion:~$ dpkg -s gnome-session-bin Package: gnome-session-bin Status: install ok installed Priority: optional Section: gnome Installed-Size: 576 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: i386 Source: gnome-session Version: 3.2.0-0ubuntu1 [...] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
If I try to run gnome-session by hand: lgb@orion:~$ gnome-session gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.SessionManager' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.session' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.screensaver' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: Settings schema 'org.gnome.desktop.lockdown' is not installed gnome-session[6343]: GLib-GIO-CRITICAL: g_settings_get_key_info: assertion `settings-priv-schema != NULL' failed gnome-session[6343]: GLib-GIO-CRITICAL: g_settings_get_key_info: assertion `settings-priv-schema != NULL' failed gnome-session[6343]: GLib-CRITICAL: g_variant_get_string: assertion `value != NULL' failed Segmentation fault (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] [NEW] [oneiric] cannot login, failed to load session
Public bug reported: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
** Attachment added: .xsession-erros file https://bugs.launchpad.net/bugs/852485/+attachment/2416290/+files/.xsession-errors -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Btw, I also created a new user, and tested with that, to be sure that no user config files etc can cause problems, but the result was the same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 852485] Re: [oneiric] cannot login, failed to load session
Interesting: running X (with another DE/WM) I got this: lgb@orion:~$ gconftool --dump / gconfentryfile entrylist base=/ Failure listing entries in `/': Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files /entrylist /gconfentryfile The odd thing: if I type this very same command into a shell running on console (so without X) it gives normal result - as far as I see that a big XML structure is good :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/852485 Title: [oneiric] cannot login, failed to load session Status in “gnome-session” package in Ubuntu: New Bug description: I've upgraded to oneiric to test the new not-yet-ready version of ubuntu. However since then I cannot log in at the lightdm (btw I tried to use gdm too, the result is the same) screen. A window (without borders) appear that failed to load session ubuntu. The result is the same, if I try to use alternative options like Ubuntu 2D, Gnome, Gnome classic, Gnome without ubuntu specific, etc etc etc. Just the message is different (the session name in the message). Now I am writing from fluxbox WM, since it was able to load at least. If I try to launch eg gnome-terminal from a terminal in fluxbox, I get: lgb@orion:~$ gnome-terminal Failed to summon the GConf demon; exiting. Failed to activate configuration server: The name org.gnome.GConf was not provided by any .service files .xsession-errors file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session 3.1.91-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic-pae 3.0.4 Uname: Linux 3.0.0-11-generic-pae i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sat Sep 17 12:09:17 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to oneiric on 2011-09-06 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/852485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
