[Bug 1247388] Re: Mouse cursor disapear / mouse stops working, when switching user
I did an temporary hack to overcome this problem. You can find it here: http://askubuntu.com/a/527239 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1247388 Title: Mouse cursor disapear / mouse stops working, when switching user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1247388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247388] Re: Mouse cursor disapear / mouse stops working, when switching user
Same problem with an Acer Extensa 5635z. Is any additional information needed to solve this problem? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1247388 Title: Mouse cursor disapear / mouse stops working, when switching user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1247388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247388] Re: Mouse cursor disapear / mouse stops working, when switching user
The workaround (reloading psmouse) apparently solves the problem that the touchpad (/dev/input/eventX) is grabbed by the wrong XServer: This can be observed by running: sudo lsof /dev/input/eventX First XServer: Touchpad works. (as the devide is grabbed by the process of the first XServer. Switching to second XServer Second XServer: Touchpad does not work. The device is still grabbed by the first Server sudo rmmod psmouse sudo modprobe psmouse Second XServer: Touchpad works. The device is now grabbed by the second Server. Can anybody explain how the normal procedure of grabbing/releasing of devices works? If i repeat the above test with an USB mouse, this procedure works... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1247388 Title: Mouse cursor disapear / mouse stops working, when switching user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1247388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 838792] Re: Restart logs out, even when there are no other people logged in
same here on 12.04 64bit. No auto-login. Trying to shutdown from a (one and only) Desktop session just logs out to lightdm. There shutdown leads to nothing. No reaction. There is no other real session running. The output of ck-list-sessions: Session4: unix-user = '123' realname = 'Cloudera Manager' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/???' remote-host-name = '' is-local = TRUE on-since = '2012-07-07T16:21:25.747608Z' login-session-id = '4294967295' Session5: unix-user = '1000' realname = 'foobar' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2012-07-07T16:21:51.036134Z' login-session-id = '4294967295' idle-since-hint = '2012-07-07T16:25:22.841253Z' The latter sessions of course exists only because i need to start a tty login to run the command. So normaly there is only this user 123. The processes of that user are just some server processes. After shutting them down (and closing my tty session) i am able to shutdown the system. In my case (and for those reporting other server processes) the problem seems to be, that ConsoleKit (ck-list-session) threats some user processes as active user. How to fix this? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/838792 Title: Restart logs out, even when there are no other people logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/838792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 838792] Re: Restart logs out, even when there are no other people logged in
The problem seems to come from init scripts that use su. This is wrong. The start-stop-daemon system should be used instead. There is an interesting discussion starting here: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/395281/comments/15 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/838792 Title: Restart logs out, even when there are no other people logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/838792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 602254] Re: Proxy Apply System Wide does not preserve authentication settings
The function apply system-wide should at least also update /etc/apt/apt.conf including authentication credentials. This would fix many issues (also the following). An additional remark for those who will sometimes address/fix this issue. There is also a little problem with sudo as it will clear the environment variable http_proxy in case it have been set before. One solution could be to use env_keep. But this could be a security concern. Maybe sudo has another way to define environment variables in a fixed way. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/602254 Title: Proxy Apply System Wide does not preserve authentication settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/602254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 48329] Re: Network Proxy: ignores proxy user/pass provided
This bug is still open for 10.10. Why are the authenification credentials not exported in http_proxy? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/48329 Title: Network Proxy: ignores proxy user/pass provided -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 602254] Re: Proxy Apply System Wide does not preserve authentication settings
in 10.10 even update-manager does not work anymore... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. https://bugs.launchpad.net/bugs/602254 Title: Proxy Apply System Wide does not preserve authentication settings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 48329] Re: Network Proxy: ignores proxy user/pass provided
** Changed in: gnome-terminal (Ubuntu) Status: Fix Released = Confirmed -- Network Proxy: ignores proxy user/pass provided https://bugs.launchpad.net/bugs/48329 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 602254] Re: Proxy Apply System Wide does not preserve authentication settings
I can confirm this problem (10.04): Though the authentication credentials are entered in gnome-network-properties and set as system wide, they are not present in * $http_proxy in shell environments. Neither in on pure tty, nor within terminals under gnome. * /etc/apt/apt.conf * Synaptics In all these cases, only the normal proxy informations are present. On the other hand: * update-manager works. * firefox works, but is still asking for auth credentials. There is interesting output, if you start gnome-network-properties on a commandline... It should be up to the administrator whether the auth credentials are also set system wide or not. -- Proxy Apply System Wide does not preserve authentication settings https://bugs.launchpad.net/bugs/602254 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 48329] Re: Network Proxy: ignores proxy user/pass provided
The bug description is still/again valid for lucid. Should i reopen this bug? -- Network Proxy: ignores proxy user/pass provided https://bugs.launchpad.net/bugs/48329 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 534225] Re: [lucid] setup_http_proxy_env constructs no_proxy incorrectly
I wonder why gnome-terminal is responsible for setting this environment variable. What if the user is using another terminal programm? Another point is that http_proxy may be defined system wide, but no_proxy not... -- [lucid] setup_http_proxy_env constructs no_proxy incorrectly https://bugs.launchpad.net/bugs/534225 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 577219] Re: named switch user does not allow to return to current user
*** This bug is a duplicate of bug 546578 *** https://bugs.launchpad.net/bugs/546578 Yes, it is a duplicate of bug #546578. Marked as duplicate. ** This bug has been marked a duplicate of bug 546578 black screen after a few user switches -- named switch user does not allow to return to current user https://bugs.launchpad.net/bugs/577219 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu (via bug 546578). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138194] Re: Closing lid during initial shutdown causes notebook to suspend
This is not fixed in Lucid on my system. Maybe we try different things. If i press the power button (hardware) a dialog appears showing some options such as shut down. On the bottom of the dialog there is a 60 second countdown running. Closing the lid while this countdown is running will suspend the system. After wakeup, the countdown is going on... -- Closing lid during initial shutdown causes notebook to suspend https://bugs.launchpad.net/bugs/138194 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 564105] Re: [users-admin] Unintentional editing settings of wrong user
Ok, so i agree that this bug is importance low. -- [users-admin] Unintentional editing settings of wrong user https://bugs.launchpad.net/bugs/564105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 564105] Re: [users-admin] Unintentional editing settings of wrong user
In every edit dialog the name of the selected user is written in bold, so I really think you'd notice. To be honest: It happend to me ;-) Once i checked that the intended user has been selected i didn't care on that detail anymore. I think it is very likely that this happen to other users as well. They will not concentrate on details which they assume to stay constant. Sure, that is a mistake, but it's human ;-) And you don't edit groups everyday. Correct. If you remove the 'admin right' it will be the last time you do so. ;-) -- [users-admin] Unintentional editing settings of wrong user https://bugs.launchpad.net/bugs/564105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 564105] [NEW] [users-admin] Unintentional editing settings of wrong user
Public bug reported: Binary package hint: gnome-system-tools In Lucid: 1. In users-admin: Select a user different from your current user. If you need to create a new one, this one gets selected after creation. 2. If you now - while the different user is still selected - click on 'advanced settings' you will be able to edit the settings of the intended (!) user. Good, so far. 3. Now let's suppose, the user clicks on 'Manage Groups' first, maybe because he thinks that this would also offer user specific settings. Just in the moment when the Groups dialog pops up, the user selection in the main window moves 'silently' to the currently logged in user. 4. After closing the groups dialog, the user may now clickt on 'advanced settings'. It is likely, that he will not notice that he is editing his own settings. If he has bad luck, he removes the admin group... Expected behaviour: The selection should stay constant and should only change on user request. Description:Ubuntu lucid (development branch) Release:10.04 gnome-system-tools: 2.30.0-0ubuntu1 ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New -- [users-admin] Unintentional editing settings of wrong user https://bugs.launchpad.net/bugs/564105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
It seems to work with lucid a3. ** Attachment added: devkit-power_ac_disconnected_after_startup.dump http://launchpadlibrarian.net/40103454/devkit-power_ac_disconnected_after_startup.dump -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
** Attachment added: devkit-power_ac_disconnected_before_startup.dump http://launchpadlibrarian.net/40103487/devkit-power_ac_disconnected_before_startup.dump -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
How do i install upower on karmic? Please find attached the requested information from gconftool-2 ** Attachment added: gpm.gconf.values.txt http://launchpadlibrarian.net/40001586/gpm.gconf.values.txt -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = New -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
Test 2 ** Attachment added: Test 2: AC disconnected before startup http://launchpadlibrarian.net/39818861/gpm_ac_disconnected_before_start.log -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
Ok, here are the results. I did two test runs: 1. I started your suggested command first and then disconnect AC. The only notifications are those of AC connect/disconnect. After charge state reached 0.0 i immediately reconnect AC. I didn't risk running out of power. 2. I disconnect AC before starting the laptop. After login i run your command. This time hibernation worked. But it works not everytime. In my opinion the distribution of the notifications over time is strange: Four notifications between 11.9 and 9.8 percent charge, then no notification down to 2.3 percent. At this point the first critical warning appeard (critical, only 5 minutes left). The last notification at 0.9 percent says critical, system hibernates now. And it worked this time. ** Attachment added: Test 1: AC disconnected after startup http://launchpadlibrarian.net/39818731/gpm_ac_disconnected_after_start.log -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
On the 'On battery power' tab it says: When battery power is critical low = Hibernate -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] [NEW] dbus does not report any PowerManagment messages
Public bug reported: Binary package hint: gnome-power-manager My laptop does not supend on critical low battery power. If i plug or unplug AC, then gpm is notified about this and it shows a notification message. if i unplug AC while running a gnome session the icon appears and the tooltip shows, that the battery is discharging. After a while of inactivity, the screen is not dimmed. The warnings about low or critical battery power are not shown. Finally, the laptop does not suspend but just runs out of power... If i start the laptop while AC is not connected then the situation is different: The screen gets dimmed after a few seconds of inactivity. Notifications of low or critical battery power are shown. Unfortunately, the laptop does not suspend. Manual supend works perfect. Output of dbus-monitor --session type='signal',interface='org.freedesktop.PowerManagement': signal sender=org.freedesktop.DBus - dest=:1.101 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string :1.101 method call sender=:1.57 - dest=:1.101 serial=490 path=/; interface=org.freedesktop.DBus.Introspectable; member=Introspect but nothing more. (For example, i unplug/plug AC while the command was running, but no output). Running Ubuntu Karmic 9.10 Kernel 2.6.31-19-generic gpm 2.28.1 My Laptop is an Acer Extensa 5635Z ProblemType: Bug Architecture: amd64 CheckboxSubmission: 06f8f0bfd32794bbacd433bf1b762a08 CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e Date: Tue Feb 23 20:31:22 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Package: gnome-power-manager 2.28.1-0ubuntu1.3 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.31-19-generic x86_64 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 526641] Re: dbus does not report any PowerManagment messages
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39626086/Dependencies.txt ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/39626087/DevkitPower.txt ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/39626088/GConfNonDefault.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39626089/XsessionErrors.txt ** Attachment added: gnome-power-bugreport.txt http://launchpadlibrarian.net/39626090/gnome-power-bugreport.txt -- dbus does not report any PowerManagment messages https://bugs.launchpad.net/bugs/526641 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 138194] Re: Closing lid during initial shutdown causes notebook to suspend
I can reproduce this with karmic gnome. After selecting shutdown a dialog appears with a 60 seconds countdown. Now i close the lid. Instead of shutting down, the laptop suspends now. After pressing a key i enter my password, the screen is restored and the countdown continues. Ok, i could cancel the countdown to avoid the shutdown. But this should behave differently: Shutdown-Countdown-Closing lid-no suspend, but shutdown after countdown, or maybe shutdown immediately. -- Closing lid during initial shutdown causes notebook to suspend https://bugs.launchpad.net/bugs/138194 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] Re: gdm should not use locale settings from /etc/environment
** Changed in: gdm (Ubuntu) Status: Incomplete = New -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] Re: gdm should not use locale settings from /etc/environment
The problem ist, that at the moment it is neccessary to have the locale definition in two different places: /etc/environment /etc/default/locale This is redundant and confusing. the first is used by gdm (and therefore for the whole gnome-session), for example. the later is used by /etc/pam.d/login (in addition to /etc/environment, but /etc/default/locale wins). If you login in a tty, for example. So the problem is, that LANG has to be adjusted in both places to successfully switch from one locale to another. Now, that debian policy says not to use /etc/environmnt all programms should use /etc/default/locale instead, shouldn't they? -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] Re: gdm should not use locale settings from /etc/environment
Yes, you are right, that is the issue. The code from your last posting should look like this: if [ -r /etc/default/locale ]; then . /etc/default/locale export LANG LANGUAGE fi This is the code used since etch. -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] Re: gdm should not use locale settings from /etc/environment
Ubuntu is a derivative of Debian. Therefore i think Ubuntu is somehow bound to design desicions made in Debian. They say: [...] Debian Policy forbids modifying configuration files of other packages, and /etc/environment is a configuration file for PAM. and Locale variables are now stored in /etc/default/locale and no more /etc/environment. Make sure to remove old definitions from /etc/environment, this file is no more modified for the reason explained above. Now the problem is, that the gdm of gutsy is still looking for LANG in /etc/environment. (Even if LANG is not defined there, gdm does _not_ look in /etc/default/locale.) As i (seem to) understand now, the bug report i quoted above is a different thing. But do i misunderstand the content of file /usr/share/doc/belocs-locales-bin/NEWS.Debian.gz? Programms should no longer store their variables in configuration files of other packages. It is also advised to remove LANG from /etc/environment, which - at least in gutsy - does not work: You end up with a non-localized gnome desktop. So, is this a breach of the debian policy? Is this ok for ubuntu? Is the debian policy just political or also technical? Do i miss something? Hope you see my point ;-) -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] Re: gdm should not use locale settings from /etc/environment
See also Bug #77983 -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 161763] Re: gvm doesn't work for remote sessions
Warning: i don't know the impact of the described workaround. Use at your own risk... -- gvm doesn't work for remote sessions https://bugs.launchpad.net/bugs/161763 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 161763] gvm doesn't work for remote sessions
Public bug reported: Binary package hint: gnome-volume-manager Start a local Xserver, set/export DISPLAY and connect to a remote (gutsy) system via 'ssh -X [EMAIL PROTECTED]'. Start 'gnome-session' on the remote system. Now plug a USB-Drive on the remote system. It won't get automounted. The reason is, that gnome-volume-manager is not running. This is because of some code in manager.c (function gvm_local_user) which does a check whether the user is local or not. Are there reasons for that restriction? A 'sudo touch /var/run/console/username:7' before 'gnome-session' is a workaround for that problem. ** Affects: gnome-volume-manager (Ubuntu) Importance: Undecided Status: New -- gvm doesn't work for remote sessions https://bugs.launchpad.net/bugs/161763 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160984] gdm should not use locale settings from /etc/environment
Public bug reported: Binary package hint: gdm Interesting part from /usr/share/doc/belocs-locales-bin/NEWS.Debian.gz: * Locale variables are now stored in /etc/default/locale and no more /etc/environment. The reason is that Debian Policy forbids modifying configuration files of other packages, and /etc/environment is a configuration file for PAM. locales should not be stored there, but this is still neccessary (e.g. for gdm). Then it says: Make sure to remove old definitions from /etc/environment, this file is no more modified for the reason explained above. if i follow that advise, gnome starts with a C locale setting, but not the one which is defined in /etc/default/locale. But then i dont' understand the comments from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389466 * Parse /etc/default/locale in gdm pam files, for now (closes: #389466) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- gdm should not use locale settings from /etc/environment https://bugs.launchpad.net/bugs/160984 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
