[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
I see that a lot of work has been done to get this change into precise, but it is not clear to me what the status of this change is for raring and saucy. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
I was about to test the new versions of the various packages but then I noticed that x11proto-core isn't currently installed on my Ubuntu Desktop 13.04 system. So clearly I am failing to understand something. Exactly which package versions should I install on Ubuntu Desktop 13.04 in order to test the newly added support for the ThinkPad microphone mute button? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878277] Re: Keyboard Layout Options | Alt/Win behavior incomprehensible
No improvement in Ubuntu 13.04. ** Tags added: quantal raring -- 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/878277 Title: Keyboard Layout Options | Alt/Win behavior incomprehensible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/878277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1148033] Re: GDBus.Error:org.openobex:Error.Failed: Unable to request session
Running 12.10. Got the error message; installed blueman; problem gone. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1148033 Title: GDBus.Error:org.openobex:Error.Failed: Unable to request session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1148033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1034725] Re: System will not create adhoc network.
** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) -- 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/1034725 Title: System will not create adhoc network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1034725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
This may also help: http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
** Bug watch added: GNOME Bug Tracker #665503 https://bugzilla.gnome.org/show_bug.cgi?id=665503 ** Changed in: network-manager Importance: Medium => Unknown ** Changed in: network-manager Status: Invalid => Unknown ** Changed in: network-manager Remote watch: GNOME Bug Tracker #676278 => GNOME Bug Tracker #665503 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (47509). https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
Update. The bug has been fixed, but not in Precise. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (47509). https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
This bug needs to be reopened because there are new reports of the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (47509). https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31286] Re: Displays repeated keyring dialogs on resume from suspend and login
>From bug #1067555: "I found to reproduce this bug by 2 ways: 1. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything), go take a rest, unlock computer and see a lot of nm-applet dialog. 2. When not connected to a secured (without password saved) wifi, try to connect to the secured wifi (do not type password or do anything); repeat from the begining. To fix this, the dataflow should be like this: On connect event: If keyring-dialog is visible, do nothing, else if connection needs password and password is not saved, display keyring-dialog." ** Bug watch added: GNOME Bug Tracker #676278 https://bugzilla.gnome.org/show_bug.cgi?id=676278 ** Changed in: network-manager Importance: Low => Unknown ** Changed in: network-manager Status: Invalid => Unknown ** Changed in: network-manager Remote watch: GNOME Bug Tracker #359532 => GNOME Bug Tracker #676278 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (47509). https://bugs.launchpad.net/bugs/31286 Title: Displays repeated keyring dialogs on resume from suspend and login To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/31286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] Re: gnome-screensaver-dialog: pam_ecryptfs: seteuid error
> Have you filed a bug upstream with Gnome yet? Nope. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449990/+files/XorgLogOld.txt ** Description changed: I get this error message in the syslog when I authenticate succesfully in the screensaver. - Ubuntu 12.10. - --- + --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: - org.gnome.desktop.session idle-delay uint32 600 - org.gnome.desktop.session session-name 'ubuntu' + org.gnome.desktop.session idle-delay uint32 600 + org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449989/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] GsettingsGnomeScreensaver.txt
apport information ** Attachment added: "GsettingsGnomeScreensaver.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449988/+files/GsettingsGnomeScreensaver.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] GsettingsGnomePowerManager.txt
apport information ** Attachment added: "GsettingsGnomePowerManager.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449987/+files/GsettingsGnomePowerManager.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] GsettingsGnomeLockdown.txt
apport information ** Attachment added: "GsettingsGnomeLockdown.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449986/+files/GsettingsGnomeLockdown.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1085706/+attachment/3449985/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] [NEW] gnome-screensaver-dialog: pam_ecryptfs: seteuid error
Public bug reported: I get this error message in the syslog when I authenticate succesfully in the screensaver. --- ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 DistroRelease: Ubuntu 12.10 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2012-06-13 (172 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: gnome-screensaver 3.6.0-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Tags: quantal running-unity Uname: Linux 3.5.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected quantal running-unity ** Package changed: ecryptfs-utils (Ubuntu) => gnome-screensaver (Ubuntu) ** Tags added: apport-collected quantal running-unity ** Description changed: I get this error message in the syslog when I authenticate succesfully in the screensaver. Ubuntu 12.10. + --- + ApportVersion: 2.6.1-0ubuntu6 + Architecture: amd64 + DistroRelease: Ubuntu 12.10 + EcryptfsInUse: Yes + GnomeSessionIdleInhibited: No + GnomeSessionInhibitors: None + GsettingsGnomeSession: + org.gnome.desktop.session idle-delay uint32 600 + org.gnome.desktop.session session-name 'ubuntu' + InstallationDate: Installed on 2012-06-13 (172 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) + MarkForUpload: True + Package: gnome-screensaver 3.6.0-0ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 + Tags: quantal running-unity + Uname: Linux 3.5.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: gnome-screensaver-dialog: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217551] Re: Password prompt "freezes" system during presence of a drop-down menu [hardy]
** Package changed: network-manager (Ubuntu) => network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/217551 Title: Password prompt "freezes" system during presence of a drop-down menu [hardy] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/217551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 227819] Re: New networkmanager null assert in Hardy
** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/227819 Title: New networkmanager null assert in Hardy To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/227819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 363350] Re: Debug messages in .xsession-errors
** Changed in: gnome-panel (Ubuntu) Status: Confirmed => Fix Released ** Changed in: update-notifier (Ubuntu) Status: Confirmed => Fix Released ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/363350 Title: Debug messages in .xsession-errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/363350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 516059] Re: Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone
** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/516059 Title: Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/516059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878277] Re: Keyboard Layout Options | Alt/Win behavior incomprehensible
No improvement in Ubuntu 12.04. ** Tags added: oneiric precise -- 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/878277 Title: Keyboard Layout Options | Alt/Win behavior incomprehensible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/878277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 19034] Re: ntpdate package and g-s-t disagree over where ntpdate symlink should be installed
** Changed in: gnome-system-tools (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/19034 Title: ntpdate package and g-s-t disagree over where ntpdate symlink should be installed To manage notifications about this bug go to: https://bugs.launchpad.net/system-tools-backends/+bug/19034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 854833] Re: NetworkManager forgets wireless password
** Tags added: precise ** Summary changed: - NetworkManager forgets wireless password + NM asks for Wi-Fi password every time I log in, or every minute, if "Available to all users" not checked; forgets password too -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/854833 Title: NM asks for Wi-Fi password every time I log in, or every minute, if "Available to all users" not checked; forgets password too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/854833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296489] Re: Hotkeys for Wi-Fi (Fn+F9) and backlight control (Fn+F5) do not work on Samsung NC10
** Summary changed: - Samsung NC10 FN Key for WIFI (fn+f9) and backlight control (fn+f5) not working + Hotkeys for Wi-Fi (Fn+F9) and backlight control (Fn+F5) do not work on Samsung NC10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/296489 Title: Hotkeys for Wi-Fi (Fn+F9) and backlight control (Fn+F5) do not work on Samsung NC10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/296489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 296489] Re: Samsung NC10 FN Key for WIFI (fn+f9) and backlight control (fn+f5) not working
Is this still a bug in Ubuntu 12.04? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/296489 Title: Samsung NC10 FN Key for WIFI (fn+f9) and backlight control (fn+f5) not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/296489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 516059] Re: Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone
** Changed in: network-manager (Ubuntu) Status: Incomplete => Opinion ** Changed in: network-manager (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/516059 Title: Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/516059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217551] Re: Password prompt "freezes" system during presence of a drop-down menu [hardy]
** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/217551 Title: Password prompt "freezes" system during presence of a drop-down menu [hardy] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/217551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217551] Re: Password prompt "freezes" system during presence of a drop-down menu [hardy]
Is this bug reproducible in Ubuntu 12.04? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/217551 Title: Password prompt "freezes" system during presence of a drop-down menu [hardy] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/217551/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 516059] Re: slow 3g/gprs bluetooth connection
@Mio: Hello and sorry for not responding to this report in a timely fashion. Are you still having this problem with Ubuntu 12.04? ** Summary changed: - slow 3g/gprs bluetooth connection + Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/516059 Title: Slow 3G/GPRS bluetooth connection with Sony Vaio laptop and SonyEricsson Z610i phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/516059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 173256] Re: [suggestion] Proxysettings in Networkmanager
*** This bug is a duplicate of bug 402223 *** https://bugs.launchpad.net/bugs/402223 ** This bug has been marked a duplicate of bug 402223 Use a VPN connection and/or proxy setting automatically when connected to a certain network -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/173256 Title: [suggestion] Proxysettings in Networkmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/173256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 273150] Re: keyrings are not working
*** This bug is a duplicate of bug 854833 *** https://bugs.launchpad.net/bugs/854833 ** This bug is no longer a duplicate of bug 271097 NetworkManager asks for the wireless password every time ** This bug has been marked a duplicate of bug 854833 NetworkManager forgets wireless password -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/273150 Title: keyrings are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/273150/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 854833] Re: NetworkManager forgets wireless password
** Summary changed: - (oneiric) wireless passwords not remembered + NetworkManager forgets wireless password -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/854833 Title: NetworkManager forgets wireless password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/854833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Question: What has to happen before 32-bit keycodes can be used in Ubuntu? If the work will be done, when is it likely to be finished? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
The microphone mute key yields Linux key input event KEY_MICMUTE which has the value 248. Add 8 to get the X KeyCode number, you get 256. This is greater than the maximum KeyCode that X handles, 255. See: http://www.x.org/wiki/XI2 The problem is similar to the problem with the Zoom hotkey combination on the X220, Fn-Space. The key combination yields KEY_ZOOM, value 372. The corresponding X KeyCode, 380, is also above 255. A workaround is to remap the keycodes to ones that X can handle. See: http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings (This page doesn't describe a way to control the LED on the Microphone Mute key.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 878277] [NEW] Keyboard Layout Options | Alt/Win behavior incomprehensible
Public bug reported: Just upgraded to oneiric. The Keyboard Layout Options | Alt/Win key behavior alternatives are: * Default - So what is the "default"? * Add the standard behaviour to Menu key - What is the "standard behaviour"? What is its relation to "the default"? - Which is the "Menu key"? * Alt is mapped to Right Win, Super to Menu - What does "mapped to" mean? The term "map" is symmetrical, but the application here is asymmetrical. Does this option map the Alt function to the Right Win key, or the Right Win function to the Alt keys? Presumably the first, but it isn't clear. Please say something like "Alt functionality...". * Alt and Meta are on Alt keys - Does this mean that Alt functionality is mapped to the left Alt key and Meta to the right Alt key? Or what? Not clear. * Left Alt is swapped with Left Win - This and other options are not inherently mutually exclusive. So why are these options on radio buttons? A Help button on the dialog would be nice. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/878277 Title: Keyboard Layout Options | Alt/Win behavior incomprehensible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/878277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Thinkpad T400s, T410s, T410, & T510 microphone mute button does not work
The microphone mute key is not currently supported in Ubuntu but the fix is fairly straightforward. First, udev needs to map the micmute key's scancode to a keyname which corresponds to an X key event. This has been fixed[0] in udev upstream. It is possible to make the same change locally, as described here[1]. Second, the key event needs to mute the microphone. This can be accomplished with a small script as described here[1]. [0]http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=6e3b1694a4dea049591af1f089adce327bf6a542 [1]http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings -- 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/408903 Title: Thinkpad T400s, T410s, T410, & T510 microphone mute button does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)
"gconf-editor | desktop | gnome | peripherals | keyboard | bell_mode := on" seems to have the same effect as "xset b 50" and is presumably a more general solution. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/769314 Title: System bell broken in Natty/Unity (despite heroic...) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/769314/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 301174] Re: Use proper sound event instead of system beep
I have since discovered that it is necessary to put pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg in ~/.xprofile, and xset b 100 in ~/.bashrc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/301174 Title: Use proper sound event instead of system beep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/301174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)
Yes, there is an "Alert volume" slider with "Mute" button. I didn't
realize that you were referring to this when you said "system bell" ---
I didn't know that they were the same thing. My apologies. It's true
that this slider has no effect on the volume of the sound that gets
played when the workaround ("pactl upload-sample..." and "xset b 100")
is applied.
Regarding the workaround, I have since discovered that "pactl upload-
sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg" has to
go in ~/.xprofile and "xset b 100" has to go in ~/.bashrc.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in Ubuntu.
https://bugs.launchpad.net/bugs/769314
Title:
System bell broken in Natty/Unity (despite heroic...)
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 555315] Re: ondemand CPU Scaling does not work when AC adapter is plugged in
Regarding ThinkPad throttling the CPU when powered by the 65 W AC adapter and no battery, see http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-Laptops/X61-Your-power-adapter-may-be-cheating-you/td-p/17870 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/555315 Title: ondemand CPU Scaling does not work when AC adapter is plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/555315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)
> 5) gnome-volume-control doesn't. > The "Sound Effects" tab of gnome-volume-control > offers to set the volume and sound for system bell > events, but these have no effect. This is because > gnome-volume-control is trying to control system > bells through metacity. Ideally, it should be rewritten > to control module-x11-bell instead, but a temporary > fix could be to simply disable this tab. In natty, on the Sound Effects tab there is no control for system bell events. So this part of the report seems fixed. FYI, on a fresh natty install, as a workaround, to enable beeps (e.g., terminal bells) permanently I created a ~/.xprofile file with: pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg xset b 100 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/769314 Title: System bell broken in Natty/Unity (despite heroic...) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/769314/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 301174] Re: Use proper sound event instead of system beep
In natty, Compiz plays a sound for the beep (e.g., the terminal bell) if you do this first: * pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg * xset b 100 I have added these commands to my ~/.xprofile script. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/301174 Title: Use proper sound event instead of system beep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/301174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Pete, thanks for the information. To summarize what I now know There are several separate issues. One is the traditional square-wave beep function. Many people say that it is necessary to: * Un-blacklist the pcspkr kernel module and load it. However, I have just discovered that this module is not needed on a Lenovo ThinkPad X61 for "echo 3 > /proc/acpi/ibm/beep" to work. The latter requires only the thinkpad-acpi module. Orthogonal to that issue is getting terminal and other bells to play in the new way, via X, the window manager and pulseaudio. For the terminal bell to ring, it is still necessary to: * enable "Terminal|Edit|Profile Preferences|General|Terminal bell" * set gconf setting "desktop|gnome|peripherals|keyboard|bell_mode" to "on". Under natty compiz then the gconf setting "apps | metacity | general | audible_bell" makes no difference. Before receiving the tip from Pete Ashdown I was re-enabling the compiz-managed newfangled audible bell by deselecting and selecting System Settings|CompizConfig Settings Manager|General|Audible Bell. This actually enabled the traditional square-wave bell! But now I see that * pactl upload-sample /usr/share/sounds/gnome/default/alerts/glass.ogg bell.ogg suffices to enable the newfangled bell. After logging out and in the bell was still enabled without my having to run xset, but I can imagine it may be necessary to run * xset b on * xset b 100 under some circumstances. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
We shouldn't depend on upstream fixing this by removing behavior that upstream regards as a feature. It would be nice if upstream made their feature easier to disable. But we shouldn't wait for them to do that, either, before fixing the problem in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188617] Re: no beep on ping
Related to bug #486154? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/188617 Title: no beep on ping -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Addendum. Even after doing what I just described (above, reply #81), I find that after reboot sometimes beeping doesn't work until I switch window managers between metacity and compiz. :/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
To re-enable the terminal bell on my ThinkPad X61 running Ubuntu 10.10 I took the following actions suggested above: * Un-blacklist pcspkr as described above, then either reboot or modprobe pcspkr. * On the terminal window, tick "Edit | Profile Preferences | General | Terminal bell" * Run gconf-editor and at "apps | metacity | general" tick audible_bell. * Run gconf-editor and at "desktop | gnome | peripherals | keyboard" change "bell_mode" from "off" to "on". * Use the alsamixer program to unmute and raise Beep volume to a suitably high level. * Do pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg Many thanks to the contributors to this bug report! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/486154 Title: System beep broken in Karmic despite heroic efforts to fix it -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80780] Re: uses unusual units to report memory and disk sizes
I realize that this bug report is, according to the title, only about memory and disk sizes, but comment #19 above mentions that network throughput uses "KB/s" (in the tooltip) and I would like to point out that this is indeed contrary to Ubuntu policy and the bug still exists in Ubuntu 10.10. According to Ubuntu policy (https://wiki.ubuntu.com/UnitsPolicy), "kilobytes" should be symbolized "kB". I was about to make this comment at #366235, since that began as a report about "incorrect network speed (throughput) units", but the latter has been assigned to gnome-bugs #580471 where the discussion has sidetracked into the question of whether the average user prefers to see throughput measurements in bits or bytes, and into other questions. Perhaps the decision whether to report bits or bytes can be left to upstream; but let Ubuntu make sure that the symbols used always follow Ubuntu standards. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/80780 Title: uses unusual units to report memory and disk sizes -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 646891] Re: memory measurement is to be in bytes
> In gnome-system-manager, memory used by a program is measured in > Kibibytes, Mebibytes, or Gibibytes, etc. According to the JEDEC memory > standard, this is incorrect. According to Ubuntu policy (https://wiki.ubuntu.com/UnitsPolicy) it is correct to use base-2 (i.e., kibibytes et al.) for RAM sizes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. https://bugs.launchpad.net/bugs/646891 Title: memory measurement is to be in bytes -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 277948] Re: Virtual screen size too small when using dual head
I also have this problem. Whatever underlying problem there has various misbehaviors as results. Here is just one example. I just tried to set the desktop image to a 3080x1050 image which exactly fits my dual-monitor screen area (LVDS 1400x1050 and DVI-0 1680x1050). The image would not display correctly using any of the "Style" settings on "Appearance Preferences | Background | Wallpaper". Then I used "System | Screen Resolution" to move the DVI to the left of LVDS; then back to the right, restoring the original situation. Then with "Style" set to "Fill screen" the desktop background displayed correctly. This suggests to me that nautilus's understanding of the screen dimensions is not correctly synced with X's understanding of the screen dimensions. Another example: Sometimes after logging in the desktop comes up on both monitors but I cannot move the mouse outside the LVDS. Grabbing the title bar I can move about 90% of a window onto the DVI-0 monitor. Another bug which may or may not be related: The window list applet in the LVDS doesn't show windows on the DVI-0 unless "Window List Content" is set to "Show windows from all workspaces". $ xrandr Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 3080 x 1050 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1680x1050+1400+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.9*+ 1600x1024 60.2 1400x1050 60.0 [...] LVDS connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1400x1050 50.0*+ S-video disconnected (normal left inverted right x axis y axis) $ cat /etc/X11/xorg.conf # xorg.conf (X.Org X Window System server configuration file) [...] Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" Defaultdepth16 SubSection "Display" Depth 16 Virtual 3080 1050 EndSubSection EndSection Section "Device" Identifier "Configured Video Device" EndSection $ lspci -v -s 01:00.0 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] Subsystem: IBM Device 0517 Flags: bus master, stepping, fast Back2Back, 66MHz, medium devsel, latency 66, IRQ 11 Memory at e800 (32-bit, prefetchable) [size=128M] I/O ports at 3000 [size=256] Memory at d010 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at d012 [disabled] [size=128K] Capabilities: Kernel modules: radeonfb ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/18901168/Xorg.0.log -- Virtual screen size too small when using dual head https://bugs.launchpad.net/bugs/277948 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269244] Re: /usr/lib/libconf2-4/gconf-sanity-check-2 exited with status 256
I had the same problem: after entering username and password the GUI hung with an empty brown desktop. Installing gnome-panel fixed the problem for me. -- /usr/lib/libconf2-4/gconf-sanity-check-2 exited with status 256 https://bugs.launchpad.net/bugs/269244 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36946] Re: Screen Resolution tool (gnome-display-properties) does not change refresh rate, resolution in Dapper
I have the same problem. I have a laptop which I use in several locations where I have several different external monitors that I like to use alongside the laptop's panel. Last year I installed Breezy and added these lines to the Section "Device" for "ATI Technologies, Inc. Radeon Mobility M7 LW [Radeon Mobility 7500]": Option "AGPMode" "4" Option "AGPFastWrite" "True" Option "EnablePageFlip""True" Option "MergedFB" "True" Option "CRT2Position" "RightOf" Option "MetaModes" "1400x1050 1400x1050-1280x1024 1400x1050-800x600 1400x1050-640x480" When I dist-upgraded to Dapper last week , initially X would not start at all. Something had overwritten xorg.conf. I re-added the lines above and as a result I can use any of the external monitors *IF* I start X with that external monitor connected. However, I cannot use System|Preferences|Screen_Resolution_Preferences|Resolution to change the resolution. When I click "Apply", the dialog box closes and, simply, nothing happens. "xrandr -s" does work, though. -- Screen Resolution tool (gnome-display-properties) does not change refresh rate, resolution in Dapper https://launchpad.net/malone/bugs/36946 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
