[Desktop-packages] [Bug 1050612] Re: gdm doesn't respect $PATH, hardcodes X location
** Bug watch added: GNOME Bug Tracker #684138 https://bugzilla.gnome.org/show_bug.cgi?id=684138 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=684138 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in GDM: The Gnome Display Manager: Unknown Status in “gdm” package in Ubuntu: New Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1050612/+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 1050612] Re: gdm doesn't respect $PATH, hardcodes X location
apport information ** Tags added: apport-collected quantal third-party-packages ** Description changed: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. - I am using ubuntu quantal, my packages are up-to-date and I compiled X - from upstream git master on fd.org. + I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. + --- + ApportVersion: 2.5.1-0ubuntu7 + Architecture: amd64 + DistroRelease: Ubuntu 12.10 + Package: gdm 3.5.91-0ubuntu1 + PackageArchitecture: amd64 + Tags: third-party-packages quantal + Uname: Linux 3.6.0-rc5 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo vboxusers ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1050612/+attachment/3313346/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in “gdm” package in Ubuntu: Incomplete Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+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 1050612] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1050612/+attachment/3313356/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in “gdm” package in Ubuntu: Incomplete Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+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 1050612] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1050612/+attachment/3313357/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in “gdm” package in Ubuntu: Incomplete Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+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 1050612] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1050612/+attachment/3313347/+files/ProcEnviron.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+attachment/3313347/+files/ProcEnviron.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+attachment/3313346/+files/Dependencies.txt ** Description changed: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers + --- + ApportVersion: 2.5.1-0ubuntu7 + Architecture: amd64 + DistroRelease: Ubuntu 12.10 + Package: gdm 3.5.91-0ubuntu1 + PackageArchitecture: amd64 + Tags: third-party-packages quantal + Uname: Linux 3.6.0-rc5 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: sudo vboxusers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in “gdm” package in Ubuntu: Incomplete Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers --- ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.10 Package: gdm 3.5.91-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages quantal Uname: Linux 3.6.0-rc5 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+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 1050612] [NEW] gdm doesn't respect $PATH, hardcodes X location
Public bug reported: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. ** Affects: gdm (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1050612 Title: gdm doesn't respect $PATH, hardcodes X location Status in “gdm” package in Ubuntu: Incomplete Bug description: Description of the problem: - LightDM as display manager: X from /usr/local/bin/X is used, just as it should, according to the $PATH env variable defined in /etc/environment. Everything works fine with LightDM. - GDM as display manager: X is always used from /usr/bin/X, and $PATH is ignored. It seems that the location of X is hardcoded somewhere. If I move /usr/bin/X to /usr/bin/X.bak and restart GDM, it fails to start and doesn't find X in /usr/local/bin. I am using ubuntu quantal, my packages are up-to-date and I compiled X from upstream git master on fd.org. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1050612/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "x-1.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+attachment/3221568/+files/x-1.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "x-0-greeter.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+attachment/3221567/+files/x-0-greeter.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "weston.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+attachment/3221565/+files/weston.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "x-0.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+attachment/3221566/+files/x-0.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] [NEW] [system compositor] monitor detection incorrect
Public bug reported: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "x-1-greeter.log" https://bugs.launchpad.net/bugs/1024111/+attachment/3221563/+files/x-1-greeter.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 1024111] Re: [system compositor] monitor detection incorrect
** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+attachment/3221564/+files/lightdm.log -- 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/1024111 Title: [system compositor] monitor detection incorrect Status in “lightdm” package in Ubuntu: New Bug description: If LightDM loads, it does in this way: the interface is jumbled up in the upper left corner, and some flickering purple-ish colour is shown on the rest of the screen. I think something about the monitor (resolution) detection goes wrong, as it says in the lightdm logs (file x-1-greeter.log): ... [+2,06s] DEBUG: main-window.vala:98: Screen is 640x480 pixels [+2,06s] DEBUG: main-window.vala:104: Monitor 0 is 0x0 pixels at 0,0 ... (I will attach all content of /var/log/lightdm for further information) My graphics hardware is an ATI Mobility Radeon 3400 (RV620). In case you are wondering, Unity and Unity-2D are not installed, but GNOME-Shell and GNOME fallback session are installed instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1024111/+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 974573] Re: gnome-control-center layout problems w/o overlay-scrollbars
This is exactly the reason why I really start to dislike ubuntu ... it seems like "we want you to use overlay-scrollbars, and the Ambiance theme, otherwise you may get a broken desktop". I want to have the choice, I want to choose which theme and which software I am using. But with each ubuntu release, the number of choices that _just work_ becomes smaller and smaller, as it seems to me. I became very fond of ubuntu over the last few years. It provided the best user experience IMHO. Installation, package management and system administration was straightforward and I always had the choice to use the software and DE I wanted (GNOME Classic up to 2.32, GNOME-Shell from 3.0 on). But as soon as Unity, overlay-scrollbars and other "optimisations" came, more and more software was patched to work with these changes. Freedom of choice was left behind. I understand why some of these choices were made. It was the aspiration to create a coherent DE and user experience. But this is what happened: Using non-standard software became more and more difficult. But I have to say I really appreciate the work that the GNOME packagers of ubuntu do, they do a great job; 3.4 was in the repositories hours after it was released. It's not their decision to stick with Totem 3.0, Evolution 3.2, ... They can't do anything about ubuntu-specific patches to GNOME packages. But they really affect my overall GNOME experience (which happened to be first-class when I came to ubuntu, -and I loved it- but things have changed. GNOME is now a second-class-citizen, no matter what people say about "Unity being based on GNOME"). So now I really am about to move to debian testing / Linux Mint Debian Edition, because they deliver a GNOME experience that is closer to as it was meant to be by the GNOME developers, not "crippled" by unity- specific patches. And I am sorry if this comment seems unfriendly or emotional ... but I love GNOME, and I came to love ubuntu; there are things about it that really upset me, though. Should I write to the ubuntu-desktop mailing list about this, maybe as a starting point for an open discussion about this issue? -- 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/974573 Title: gnome-control-center layout problems w/o overlay-scrollbars Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: I am using precise and up-to-date software packages plus the gnome3-team PPA packages. As far as I know, in the appearance section of GNOME Control Center, 4 wallpapers should be displayed in a row. But if you don't use overlay-scrollbars, the layout doesn't fit the width of four wallpaper icons anymore, and so a "line break" after three thumbnails is generated (which looks ugly gecause of the unused space between the third thumbnail and the scrollbar). (I am using Adwaita from gnome-themes-standard 3.4.) I added a screenshot to better explain what I mean :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu4 Uname: Linux 3.3.1-ck1-bfs x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 21:31:13 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120209) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/974573/+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 974573] Re: gnome-control-center layout problems w/o overlay-scrollbars
** Summary changed: - gnome-control-centerlayout problems w/o overlay-scrollbars + gnome-control-center layout problems w/o overlay-scrollbars -- 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/974573 Title: gnome-control-center layout problems w/o overlay-scrollbars Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: I am using precise and up-to-date software packages plus the gnome3-team PPA packages. As far as I know, in the appearance section of GNOME Control Center, 4 wallpapers should be displayed in a row. But if you don't use overlay-scrollbars, the layout doesn't fit the width of four wallpaper icons anymore, and so a "line break" after three thumbnails is generated (which looks ugly gecause of the unused space between the third thumbnail and the scrollbar). (I am using Adwaita from gnome-themes-standard 3.4.) I added a screenshot to better explain what I mean :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu4 Uname: Linux 3.3.1-ck1-bfs x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 21:31:13 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120209) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/974573/+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 974573] [NEW] gnome-control-centerlayout problems w/o overlay-scrollbars
Public bug reported: I am using precise and up-to-date software packages plus the gnome3-team PPA packages. As far as I know, in the appearance section of GNOME Control Center, 4 wallpapers should be displayed in a row. But if you don't use overlay-scrollbars, the layout doesn't fit the width of four wallpaper icons anymore, and so a "line break" after three thumbnails is generated (which looks ugly gecause of the unused space between the third thumbnail and the scrollbar). (I am using Adwaita from gnome-themes-standard 3.4.) I added a screenshot to better explain what I mean :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu4 Uname: Linux 3.3.1-ck1-bfs x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 21:31:13 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120209) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages -- 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/974573 Title: gnome-control-centerlayout problems w/o overlay-scrollbars Status in “gnome-control-center” package in Ubuntu: New Bug description: I am using precise and up-to-date software packages plus the gnome3-team PPA packages. As far as I know, in the appearance section of GNOME Control Center, 4 wallpapers should be displayed in a row. But if you don't use overlay-scrollbars, the layout doesn't fit the width of four wallpaper icons anymore, and so a "line break" after three thumbnails is generated (which looks ugly gecause of the unused space between the third thumbnail and the scrollbar). (I am using Adwaita from gnome-themes-standard 3.4.) I added a screenshot to better explain what I mean :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu4 Uname: Linux 3.3.1-ck1-bfs x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 21:31:13 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120209) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/974573/+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 974573] Re: gnome-control-centerlayout problems w/o overlay-scrollbars
** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/974573/+attachment/3011782/+files/gnome-control-center-bug.png -- 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/974573 Title: gnome-control-centerlayout problems w/o overlay-scrollbars Status in “gnome-control-center” package in Ubuntu: New Bug description: I am using precise and up-to-date software packages plus the gnome3-team PPA packages. As far as I know, in the appearance section of GNOME Control Center, 4 wallpapers should be displayed in a row. But if you don't use overlay-scrollbars, the layout doesn't fit the width of four wallpaper icons anymore, and so a "line break" after three thumbnails is generated (which looks ugly gecause of the unused space between the third thumbnail and the scrollbar). (I am using Adwaita from gnome-themes-standard 3.4.) I added a screenshot to better explain what I mean :) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu4 Uname: Linux 3.3.1-ck1-bfs x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Thu Apr 5 21:31:13 2012 InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120209) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/974573/+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 918725] [NEW] LightDM defaults the keyboard layout to English every startup
Public bug reported: Since the version which introduced the keyboard indicator today (Jan 19, 2012), I always have to choose my German keyboard before every single login (which is annoying). This way, my password is spelled incorrectly if I don't switch to the German layout. If I type my password "imagining" an English layout on my keyboard, GNOME session inherits the English keyboard layout. Setting the locale system-wide doesn't help. Editing /etc/environment or ~/.profile doesn't help. It seems LightDM ignores those settings. my system: ubuntu 12.04 with up-to-date packages LightDM 1.1.1 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/918725 Title: LightDM defaults the keyboard layout to English every startup Status in “lightdm” package in Ubuntu: New Bug description: Since the version which introduced the keyboard indicator today (Jan 19, 2012), I always have to choose my German keyboard before every single login (which is annoying). This way, my password is spelled incorrectly if I don't switch to the German layout. If I type my password "imagining" an English layout on my keyboard, GNOME session inherits the English keyboard layout. Setting the locale system-wide doesn't help. Editing /etc/environment or ~/.profile doesn't help. It seems LightDM ignores those settings. my system: ubuntu 12.04 with up-to-date packages LightDM 1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/918725/+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 883824] Re: eye of gnome doesn't start
The gnome3-team/gnome3 - PPA was active on my system, I just wanted my GNOME (e.g. Totem, tracker) to be up to date... I always read through PPA descriptions and disclaimers before I use one - a small message like "At the moment glib 2.31 breaks EOG, so don't activate this PPA if you rely on it" would have prevented the problem. I reverted to glib 2.30 and eog works again! Thank you for your (fast) help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/883824 Title: eye of gnome doesn't start Status in “eog” package in Ubuntu: Incomplete Bug description: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+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 883824] Re: eye of gnome doesn't start
Permissions on the file are "srwxrwxrwx. 1 root root 0 2011-10-31 14:46 X0"and "drwxrwxrwt. 2 root root 4096 2011-10-31 14:46 .X11-unix" on the directory (as you wrote they should be). The problem only occurs with eog, I think it was introduced through an update a few days ago. Before that, it worked fine. No proprietary drivers are installed on my system. I suspected that it could have something to do with selinux being enabled on my system, but eog also didn't work after I deactivated selinux. Thank you for your help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/883824 Title: eye of gnome doesn't start Status in “eog” package in Ubuntu: Incomplete Bug description: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+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 883824] Re: eye of gnome doesn't start
Thank you for your answer! I ran "strace -o eogrun.log eog" and nothing happened for a few minutes, then I terminated the eog process. ** Attachment added: "eogrun.log" https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+attachment/2579348/+files/eogrun.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/883824 Title: eye of gnome doesn't start Status in “eog” package in Ubuntu: New Bug description: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+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 883824] [NEW] eye of gnome doesn't start
Public bug reported: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/883824 Title: eye of gnome doesn't start Status in “eog” package in Ubuntu: New Bug description: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+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 883824] Re: eye of gnome doesn't start
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/883824 Title: eye of gnome doesn't start Status in “eog” package in Ubuntu: New Bug description: eog doesn't start at all. Multiple attempts to start it result in multiple processes that terminate about 10 seconds later. Terminal output: user@ubuntu:~$ eog GLib-GIO-CRITICAL **: Timeout was reached // about 10 seconds after program start user@ubuntu:~$ ubuntu version: 11.10 (clean install) eog package version: 3.2.1-0ubuntu1 active repositories: oneiric + updates, security, backports, proposed main and universe ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: eog 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 13:27:24 2011 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/883824/+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
