[Bug 368238] Re: Hotkeys stopped working
Thank you for taking the time to report this bug and help to improve Ubuntu. You say that the keys are recognized when you try to bind them in gnome- keybinding-properties - are they shown with exactly these names - XF86Mail, XF86Homepage, and XF86Launch2? If you can see these key names, then this must not be a bug with hotkey input, but instead a problem with GNOME's handling of these keys. ** Package changed: hotkey-setup (Ubuntu) = gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Incomplete -- Hotkeys stopped working https://bugs.launchpad.net/bugs/368238 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 379537] Re: Closing lid does not lock screen
Thanks for the output. One difference to my system is this: blank_screen = false On my system this is set to blank_screen = true. Does changing this setting have any effect on the behavior? Also, I don't know if you missed my earlier question: when you close the lid, does the screensaver activate at all? -- Closing lid does not lock screen https://bugs.launchpad.net/bugs/379537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383256] Re: seahorse no longer running after upgrade to karmic, no gpg agent available
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27462946/Dependencies.txt -- seahorse no longer running after upgrade to karmic, no gpg agent available https://bugs.launchpad.net/bugs/383256 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383256] [NEW] seahorse no longer running after upgrade to karmic, no gpg agent available
Public bug reported: Binary package hint: seahorse With the merge of seahorse 2.24.1-1 from Debian, seahorse no longer ships an Xsession file, so seahorse is not started by default on the desktop. The net result of this is that there's no gpg agent running anymore; since this is the only thing I have ever used seahorse for, I think this is the wrong outcome. It's been pointed out to me on IRC that seahorse is also used for managing the keys stored in gnome-keyring, via Applications - Accessories - Passwords and Encryption Keys, and that this is the common use case, with gpg agent handling being an edge case. I dispute this, on the basis that keyring management doesn't belong under accessories at all (it should be either System-Preferences or System-Administration), and I've never even noticed it there before - I don't think people are actually making much use of this GUI where it currently lives in the menu. At a minimum, I think seahorse needs to be moved under the System menu. But beyond that, I think seahorse ought to restore the Recommends: on seahorse-plugins, and that if we don't want this by default on the desktop, that maybe we shouldn't have seahorse by default either. ProblemType: Bug Architecture: amd64 Date: Wed Jun 3 09:46:43 2009 DistroRelease: Ubuntu 9.10 Package: seahorse 2.27.1-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-6.7-generic SourcePackage: seahorse Uname: Linux 2.6.30-6-generic x86_64 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- seahorse no longer running after upgrade to karmic, no gpg agent available https://bugs.launchpad.net/bugs/383256 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383274] [NEW] wrong icon theme applied to g-p-m in karmic
Public bug reported: Binary package hint: gnome-power-manager After upgrade to karmic, gnome-power-manager is showing all the icons using the default GNOME theme instead of the Ubuntu theme. It's ugly and jarring and I can't make sense of any of the icons. Please fix. :-) ProblemType: Bug Architecture: amd64 Date: Wed Jun 3 10:40:35 2009 DistroRelease: Ubuntu 9.10 Package: gnome-power-manager 2.26.1-0ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-6.7-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.30-6-generic x86_64 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-potential -- wrong icon theme applied to g-p-m in karmic https://bugs.launchpad.net/bugs/383274 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 383274] Re: wrong icon theme applied to g-p-m in karmic
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27463818/Dependencies.txt ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/27463819/DevkitPower.txt ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/27463820/GConfNonDefault.txt ** Tags added: regression-potential -- wrong icon theme applied to g-p-m in karmic https://bugs.launchpad.net/bugs/383274 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 383358] [NEW] g-p-m: battery resolution is terrible with devkit-power in karmic
Public bug reported: Binary package hint: gnome-power-manager In karmic, mouseovers on gnome-power-manager show only one of three values for me: 79%, 49%, or 19%. Before upgrading, a mouseover would show an accurate value for battery charge, as well as an estimate of remaining time. I have no clue if this is caused by the switch to devkit-power, or if it's a regression in g-p-m itself. ProblemType: Bug Architecture: amd64 Date: Wed Jun 3 13:51:39 2009 DistroRelease: Ubuntu 9.10 Package: gnome-power-manager 2.26.1-0ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-6.7-generic SourcePackage: gnome-power-manager Uname: Linux 2.6.30-6-generic x86_64 ** Affects: gnome-power-manager (Ubuntu) Importance: Medium Status: New ** Affects: gnome-power-manager (Ubuntu Karmic) Importance: Medium Status: New ** Tags: amd64 apport-bug regression-potential -- g-p-m: battery resolution is terrible with devkit-power in karmic https://bugs.launchpad.net/bugs/383358 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 383358] Re: g-p-m: battery resolution is terrible with devkit-power in karmic
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27470240/Dependencies.txt ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/27470241/DevkitPower.txt ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/27470242/GConfNonDefault.txt ** Changed in: gnome-power-manager (Ubuntu) Importance: Undecided = Medium ** Also affects: gnome-power-manager (Ubuntu Karmic) Importance: Medium Status: New ** Tags added: regression-potentia ** Tags added: regression-potential ** Tags removed: regression-potentia -- g-p-m: battery resolution is terrible with devkit-power in karmic https://bugs.launchpad.net/bugs/383358 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 104957] Re: users with no password can't log in with gdm
that's not an appropriate use of the 'incomplete' status. ** Changed in: shadow (Ubuntu) Status: Incomplete = New ** Changed in: pam (Ubuntu) Status: Incomplete = New -- users with no password can't log in with gdm https://bugs.launchpad.net/bugs/104957 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 104957] Re: users with no password can't log in with gdm
The 'incomplete' status is meant to indicate that more information is needed from the bug submitter. You appear to be asking for information from the developers... It's already been acknowledged by one of the shadow developers as a bug in that package. I'm still considering whether we should also treat this as a bug in pam for not having a sensible wildcard format for /etc/securetty. -- users with no password can't log in with gdm https://bugs.launchpad.net/bugs/104957 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 104957] Re: users with no password can't log in with gdm
** Changed in: shadow (Ubuntu) Importance: Undecided = Low ** Changed in: shadow (Ubuntu) Status: New = Confirmed ** Changed in: shadow (Ubuntu) Status: Confirmed = Triaged -- users with no password can't log in with gdm https://bugs.launchpad.net/bugs/104957 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 382873] [NEW] gnome-display-properties doesn't show output names with KMS
Public bug reported: Binary package hint: gnome-control-center In karmic using KMS, gnome-display-properties shows both my laptop LCD and my external monitor as 'Unknown'. I know it gave useful descriptors to these in the past, so I think this is a regression connected to KMS itself. In any event, it is a regression vs. jaunty. /var/log/Xorg.0.log shows both a monitor name: (II) intel(0): Monitor name: L2210NW and an EDID vendor for the internal display: (II) intel(0): EDID vendor LEN, prod id 16464 ProblemType: Bug Architecture: amd64 Date: Tue Jun 2 12:06:57 2009 DistroRelease: Ubuntu 9.10 Package: gnome-control-center 1:2.26.0-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.30-6.7-generic SourcePackage: gnome-control-center Uname: Linux 2.6.30-6-generic x86_64 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-potential -- gnome-display-properties doesn't show output names with KMS https://bugs.launchpad.net/bugs/382873 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 382873] Re: gnome-display-properties doesn't show output names with KMS
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27424589/Dependencies.txt ** Tags added: regression-potential -- gnome-display-properties doesn't show output names with KMS https://bugs.launchpad.net/bugs/382873 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 379537] Re: Closing lid does not lock screen
Thank you for taking the time to report this bug and help to improve Ubuntu. The acpi-support package is not involved with the screen locking policy; this would seem to be a screensaver issue. You don't mention whether you're using Ubuntu or another variant, so assuming gnome-screensaver. However, I'm not able to reproduce this problem here; closing the lid on my laptop correctly locks the screen. In your case, does the screensaver activate without locking the screen, or does the screensaver not activate at all? Please post the output of the following commands: $ gconftool-2 -R /apps/gnome-power-manager/lock $ gconftool-2 -R /apps/gnome-screensaver ** Package changed: acpi-support (Ubuntu) = gnome-screensaver (Ubuntu) ** Changed in: gnome-screensaver (Ubuntu) Status: New = Incomplete ** Changed in: gnome-screensaver (Ubuntu) Importance: Undecided = Medium -- Closing lid does not lock screen https://bugs.launchpad.net/bugs/379537 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 272587] Re: Resuming from Suspend cause power button action to be called
PhilT,
If you stop acpid ('sudo service acpid stop'), does this problem
persist?
I suspect that this is a linux kernel bug, not a bug in acpi-support.
--
Resuming from Suspend cause power button action to be called
https://bugs.launchpad.net/bugs/272587
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 272587] Re: Resuming from Suspend cause power button action to be called
This is not a bug in 'acpi', which is an unrelated Ubuntu package. Marking invalid. ** Changed in: acpi (Ubuntu) Status: Confirmed = Invalid -- Resuming from Suspend cause power button action to be called https://bugs.launchpad.net/bugs/272587 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 360795] Re: Strange LCD brightness up function implementation on the Acer Aspire 5720
heni, Can you post the output of lshal again, with this fdi file installed? I'd like to double-check that my instructions to you had the intended effect. -- Strange LCD brightness up function implementation on the Acer Aspire 5720 https://bugs.launchpad.net/bugs/360795 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 372592] Re: Update to Totem 2.26.2
(please don't reopen the main Ubuntu task for an SRU; this needs to go on the per-distroseries task once it's approved.) ** Changed in: totem (Ubuntu) Status: In Progress = Fix Released ** Also affects: totem (Ubuntu Jaunty) Importance: Undecided Status: New -- Update to Totem 2.26.2 https://bugs.launchpad.net/bugs/372592 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360795] Re: Strange LCD brightness up function implementation on the Acer Aspire 5720
heni, Please try installing the attached fdi file to /etc/hal/fdi/policy/, restart hal with 'sudo service hal restart', and tell me whether this fixes the problem for you. ** Attachment added: 10-acer-backlight.fdi http://launchpadlibrarian.net/26233080/10-acer-backlight.fdi -- Strange LCD brightness up function implementation on the Acer Aspire 5720 https://bugs.launchpad.net/bugs/360795 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 360795] Re: Strange LCD brightness up function implementation on the Acer Aspire 5720
The only program I see in your process list that I can imagine /could/ do something with this event would be gkrellm. Could you check whether the brightness still changes if you stop both gnome-power-manager and gkrellm? If so, can you check whether the brightness changes when you stop both gnome-power-manager and hal? -- Strange LCD brightness up function implementation on the Acer Aspire 5720 https://bugs.launchpad.net/bugs/360795 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 31063] Re: Asus A6U, two hotkeys not working
As written in https://bugs.launchpad.net/ubuntu/+source/acpi- support/+bug/31063/comments/16, yes, there is a GNOME element to this bug. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid = Confirmed -- Asus A6U, two hotkeys not working https://bugs.launchpad.net/bugs/31063 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360795] Re: Strange LCD brightness up function implementation
Here is the relevant hal output for the macbooks:
udi = '/org/freedesktop/Hal/devices/macbook_backlight'
info.addons = {'hald-addon-macbook-backlight'} (string list)
info.capabilities = {'laptop_panel'} (string list)
info.category = 'laptop_panel' (string)
info.interfaces = {'org.freedesktop.Hal.Device.LaptopPanel'} (string list)
info.parent = '/org/freedesktop/Hal/devices/computer' (string)
info.product = 'MacBook Backlight Control' (string)
info.subsystem = 'unknown' (string)
info.udi = '/org/freedesktop/Hal/devices/macbook_backlight' (string)
laptop_panel.access_method = 'custom' (string)
laptop_panel.num_levels = 118 (0x76) (int)
So this is probably a bug in hald-addon-macbook-backlight. But the
original bug reporter is not using a macbook. If you're having this
issue with a macbook, please open a new bug report with 'ubuntu-bug hal'
and describe what you're seeing.
** Summary changed:
- Strange LCD brightness up function implementation
+ Strange LCD brightness up function implementation on the Acer Aspire 5720
--
Strange LCD brightness up function implementation on the Acer Aspire 5720
https://bugs.launchpad.net/bugs/360795
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 360795] Re: Strange LCD brightness up function implementation
heni, when you say alll is good if I kill gnome-power-manager, do you mean that the brightness level is changed when pressing the button, even without gnome-power-manager running? If so, that's quite unusual as well. -- Strange LCD brightness up function implementation on the Acer Aspire 5720 https://bugs.launchpad.net/bugs/360795 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 335307] Re: Crimean Tatar (Crimean Turkish) locale (crh) is not shown in gdm languages list, even if language support for crh is added
Sorry, no, this is not a candidate for a freeze exception. Such a change would require remastering and retesting the Ubuntu ISOs. Unsubscribing ubuntu-release. It could be considered for an SRU according to the process at https://wiki.ubuntu.com/StableReleaseUpdates. However, my opinion is that it doesn't meet the criteria for SRU, and that the focus should be on addressing this for karmic forward. -- Crimean Tatar (Crimean Turkish) locale (crh) is not shown in gdm languages list, even if language support for crh is added https://bugs.launchpad.net/bugs/335307 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360989] Re: notification-daemon started instead of notify-osd in Netbook Remix
AIUI, this bug is fixed in notify-osd and no further changes are needed to gdm. ** Changed in: gdm (Ubuntu Jaunty) Status: New = Invalid -- notification-daemon started instead of notify-osd in Netbook Remix https://bugs.launchpad.net/bugs/360989 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 272083] Re: Zenity windows appear underneath others
This patch seems to be rather large for the change in question, I wonder if each of the changes is necessary or if this change is overreaching? The upstream bug linked here points out that having the pop-ups steal the focus, which I believe is the result of this change, will /also/ make people unhappy; I think what you ideally want here is for the window to open on top, but to not steal the focus? But neither the existing behavior, nor this change, give you that. I'm concerned about changing the behavior of this program so blatantly, so shortly before release. Mario, would it still meet your needs for mythbuntu if this change landed as an SRU instead, to give it more time to bake? -- Zenity windows appear underneath others https://bugs.launchpad.net/bugs/272083 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 202089] Re: Pulseaudio is blocking normal sound after resume
Sorry, yes, rejecting this for jaunty. I think it's unlikely to warrant an SRU, but we can discuss that if you think it's needed. ** Changed in: pulseaudio (Ubuntu) Status: Fix Committed = Triaged -- Pulseaudio is blocking normal sound after resume https://bugs.launchpad.net/bugs/202089 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 328167] Re: [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
** Changed in: gnome-keyring (Ubuntu Jaunty) Status: Triaged = Won't Fix -- [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty https://bugs.launchpad.net/bugs/328167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360795] Re: Strange LCD brightness up function implementation
This assumes that the brightness is actually being handled the standard way, with hal and gnome-power-manager. I'm not sure this is the case; I can't reproduce such a wrap-around behavior on my hardware, so I suspect this is happening outside of hal's control. Can you please step through the guide at https://wiki.ubuntu.com/Hotkeys/Troubleshooting, to determine where these keypresses are or are not being sent? -- Strange LCD brightness up function implementation https://bugs.launchpad.net/bugs/360795 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
Re: [Bug 328167] Re: [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
On Tue, Apr 14, 2009 at 02:56:58PM +0100, Matt Zimmerman wrote: On Tue, Apr 14, 2009 at 12:59:28PM -, Steve Langasek wrote: ** Changed in: gnome-keyring (Ubuntu Jaunty) Status: Triaged = Won't Fix Wasn't this fixed by gnome-keyring (2.26.0-0ubuntu7) jaunty; urgency=low * Built with -O1 on armel to workaround a deadlock which is triggerred easily on armel; LP #328167. -- Loic Minier l...@dooz.org Thu, 09 Apr 2009 09:58:08 +0200 ? This had been regarded as a workaround, with the bug left open for future work to fix whatever underlying problem led to the -O1 requirement; I was just putting the bug state back to where it was earlier, before the latest upload that was thought to fix it. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty https://bugs.launchpad.net/bugs/328167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360795] Re: Strange LCD brightness up function implementation
Stefano, Please post the output of 'lshal' on this system. -- Strange LCD brightness up function implementation https://bugs.launchpad.net/bugs/360795 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 330684] Re: Merge libdvdread 4.x from Debian unstable
** Changed in: ogmrip (Ubuntu) Importance: Undecided = High ** Changed in: ogmrip (Ubuntu) Status: New = Confirmed -- Merge libdvdread 4.x from Debian unstable https://bugs.launchpad.net/bugs/330684 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 280518] Re: Brightness Applet/Brightness Keys Do Not Work In Gateway M-7315u Laptop
please provide the output of the following commands: lspci -vvnn lshal ** Package changed: gnome-power-manager (Ubuntu) = hal (Ubuntu) ** Changed in: hal (Ubuntu) Status: New = Incomplete -- Brightness Applet/Brightness Keys Do Not Work In Gateway M-7315u Laptop https://bugs.launchpad.net/bugs/280518 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 131227] Re: notification-daemon crashed with SIGSEGV in strcmp()
** Changed in: notification-daemon (Ubuntu Jaunty) Milestone: None = jaunty-updates -- notification-daemon crashed with SIGSEGV in strcmp() https://bugs.launchpad.net/bugs/131227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to notification-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 199496] Re: Tomboy.exe crashed with SIGSEGV in exit()
** Changed in: gtk-sharp2 (Ubuntu) Milestone: ubuntu-8.04 = None -- Tomboy.exe crashed with SIGSEGV in exit() https://bugs.launchpad.net/bugs/199496 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 147045] Re: gnome-appearance-properties hogs processor even after close
Kelen, your issue is unrelated to this bug report. -- gnome-appearance-properties hogs processor even after close https://bugs.launchpad.net/bugs/147045 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 349461] Re: Please provide a VFP-optimised build for pango1.0
** Changed in: pango1.0 (Ubuntu Jaunty) Importance: Wishlist = Medium -- Please provide a VFP-optimised build for pango1.0 https://bugs.launchpad.net/bugs/349461 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 349460] Re: Please provide a VFP-optimised build for gtk+2.0
** Changed in: gtk+2.0 (Ubuntu Jaunty) Importance: Undecided = Medium -- Please provide a VFP-optimised build for gtk+2.0 https://bugs.launchpad.net/bugs/349460 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332342] Re: gnome-keyring-daemon crashed with SIGSEGV
Let's mark this closed as well, then; it hasn't recurred for me, I can always reopen later if I find the problem recurs. ** Changed in: gnome-keyring (Ubuntu) Status: Triaged = Fix Released -- gnome-keyring-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/332342 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 328167] Re: gnome-keyring-daemon eating 100% CPU at login in Jaunty
** Changed in: gnome-keyring (Ubuntu Jaunty) Target: ubuntu-9.04-beta = ubuntu-9.04 -- gnome-keyring-daemon eating 100% CPU at login in Jaunty https://bugs.launchpad.net/bugs/328167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 131227] Re: notification-daemon crashed with SIGSEGV in strcmp()
** Changed in: notification-daemon (Ubuntu Jaunty) Target: ubuntu-9.04-beta = None -- notification-daemon crashed with SIGSEGV in strcmp() https://bugs.launchpad.net/bugs/131227 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to notification-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 328167] Re: gnome-keyring-daemon eating 100% CPU at login in Jaunty
does that mean this bug should be dropped as a release target, since it only manifests with a broken kernel? ** Changed in: gnome-keyring (Ubuntu Jaunty) Target: jaunty-alpha-6 = ubuntu-9.04-beta -- gnome-keyring-daemon eating 100% CPU at login in Jaunty https://bugs.launchpad.net/bugs/328167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 345531] Re: fn keys for backlight (brighness) not working : geforce 8 card on sony vaio
** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- fn keys for backlight (brighness) not working : geforce 8 card on sony vaio https://bugs.launchpad.net/bugs/345531 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 345531] Re: fn keys for backlight (brighness) not working : geforce 8 card on sony vaio
The showkeys output shows that the kernel driver is synthesizing the correct keypress events for these hotkeys, but that the desktop stack is not subsequently able to handle them. We can easily restore the sony scripts to the acpi-support package, but the right way to fix this is if gnome-power-manager (or other desktop package as appropriate) will know what to do with these events on your hardware. So I'm opening a task on gnome-power-manager for this. If that doesn't manage to work itself out in time for release, I'll restore the acpi-support script. ** Changed in: acpi-support (Ubuntu) Assignee: (unassigned) = Steve Langasek (vorlon) ** Changed in: acpi-support (Ubuntu Jaunty) Importance: Undecided = Medium Status: New = Confirmed Target: None = ubuntu-9.04 -- fn keys for backlight (brighness) not working : geforce 8 card on sony vaio https://bugs.launchpad.net/bugs/345531 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 345531] Re: fn keys for backlight (brighness) not working : geforce 8 card on sony vaio
Here's what the old script did, for reference in implementing the gnome- power-manager fix. BRIGHTNESS=$(cat /sys/class/backlight/sony/brightness) if [ $BRIGHTNESS -gt 7 ]; then BRIGHTNESS=0 fi if [ x$1 = xdown ]; then if [ x$BRIGHTNESS != x0 ]; then BRIGHTNESS=$(( $BRIGHTNESS - 1 )) echo $BRIGHTNESS /sys/class/backlight/sony/brightness else [ -x /usr/bin/spicctrl ] /usr/bin/spicctrl -b 0 fi # Recent nvidia Sonys have ACPI methods that do nothing. Thanks, Sony. [ -x /usr/bin/smartdimmer ] smartdimmer -d 2/dev/null elif [ x$1 = xup ]; then if [ x$BRIGHTNESS != x7 ]; then BRIGHTNESS=$(( $BRIGHTNESS + 1 )) echo $BRIGHTNESS /sys/class/backlight/sony/brightness fi [ -x /usr/bin/smartdimmer ] smartdimmer -i 2/dev/null else echo 2 Unknown argument $1 fi -- fn keys for backlight (brighness) not working : geforce 8 card on sony vaio https://bugs.launchpad.net/bugs/345531 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 344989] Re: Suspend fails in Jaunty on Macbook 4,1
** Changed in: gnome-power-manager (Ubuntu) Sourcepackagename: acpi-support = gnome-power-manager -- Suspend fails in Jaunty on Macbook 4,1 https://bugs.launchpad.net/bugs/344989 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 332342] Re: gnome-keyring-daemon crashed with SIGSEGV
I haven't seen this crash again. I have no idea whether that means we should consider it fixed, since the crash only happened the one time. -- gnome-keyring-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/332342 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 343210] Sync gst-plugins-ugly0.10 0.10.10.2-1 (universe) from Debian unstable (main).
[Updating] gst-plugins-ugly0.10 (0.10.10-2 [Ubuntu] 0.10.10.2-1 [Debian]) * Trying to add gst-plugins-ugly0.10... - gst-plugins-ugly0.10_0.10.10.2.orig.tar.gz: downloading from http://ftp.debian.org/debian/ - gst-plugins-ugly0.10_0.10.10.2-1.dsc: downloading from http://ftp.debian.org/debian/ - gst-plugins-ugly0.10_0.10.10.2-1.diff.gz: downloading from http://ftp.debian.org/debian/ I: gst-plugins-ugly0.10 [universe] - gstreamer0.10-plugins-ugly-doc_0.10.10-2 [universe]. I: gst-plugins-ugly0.10 [universe] - gstreamer0.10-plugins-ugly_0.10.10-2 [universe]. I: gst-plugins-ugly0.10 [universe] - gstreamer0.10-plugins-ugly-dbg_0.10.10-2 [universe]. ** Changed in: gst-plugins-ugly0.10 (Ubuntu) Status: Confirmed = Fix Released -- Sync gst-plugins-ugly0.10 0.10.10.2-1 (universe) from Debian unstable (main). https://bugs.launchpad.net/bugs/343210 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 335712] Re: strange escape handling in Exec line of .desktop files
On Thu, Mar 12, 2009 at 10:58:29PM -, Chris Coulson wrote: I've recreated this now. Steve, did you manually edit the Exec line of the desktop file? No, it was auto-generated by wine. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- strange escape handling in Exec line of .desktop files https://bugs.launchpad.net/bugs/335712 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 216104] Re: Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons
Thank you for reporting this bug and helping to improve Ubuntu. I have tested with the current version of GNOME in jaunty and can no longer reproduce this bug, which was reproducible for me with the 8.04 release. If you experienced this bug in hardy, please test to confirm that this bug is fixed for you in jaunty (you can do this using the latest alpha build of jaunty, available from http://cdimage.ubuntu.com/releases/jaunty/alpha-5/). If you are still experiencing the bug described by the test case, we will need more information about your server configuration in order to debug further. If you are experiencing a bug that does *not* match the test case in the bug description, you are experiencing a different bug and should file a separate bug report (possibly leaving a comment here linking that bug, for reference). It is important to verify whether your bug is addressed in the latest development version of Ubuntu, as that is a precondition for backporting the bugfix to the LTS release. ** Changed in: nautilus (Ubuntu) Status: Triaged = Fix Released -- Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons https://bugs.launchpad.net/bugs/216104 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 216104] Re: Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons
The fix is thought to be http://svn.gnome.org/viewvc/gvfs?view=revisionrevision=1774; reassigning to the gvfs package ** Changed in: gvfs (Ubuntu Hardy) Sourcepackagename: nautilus = gvfs -- Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons https://bugs.launchpad.net/bugs/216104 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 321252] Re: Computer do not wake up
** Changed in: gnome-screensaver (Ubuntu) Sourcepackagename: acpi-support = gnome-screensaver -- Computer do not wake up https://bugs.launchpad.net/bugs/321252 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 309215] Re: fortran-using components need to be split out
marking this as 'wontfix' overall for python-numpy, it appears we have a correct solution for pygtk now. ** Changed in: python-numpy (Ubuntu) Status: Triaged = Won't Fix -- fortran-using components need to be split out https://bugs.launchpad.net/bugs/309215 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 104957] Re: users with no password can't log in with gdm
I don't know if the display names always belong to local X servers; answering that question would go a long way to help resolve this bug. It's definitely only insecure if you turn on XDMCP, though, so for your local use that should be fine. -- users with no password can't log in with gdm https://bugs.launchpad.net/bugs/104957 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
Re: [Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
On Mon, Mar 02, 2009 at 03:40:39PM -, Matthijs ten Kate wrote: I can imagine that our problem is not fully related to the original bug since the i5/OS NetServer software wasn't compiled by our friend from Redmond, so if I need to file a new bug for our situation, please let me know. Unless your NetServer is part of an AD realm and you've also configured your Ubuntu workstation for AD, yes, your bug is unrelated and you should file a new bug. But this may be bug #209520. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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 335712] [NEW] strange escape handling in Exec line of .desktop files
Public bug reported: Given a .desktop file with the following line: Exec=env WINEPREFIX=/home/vorlon/.wine wine C:\\comlogo\\Comlogo.exe c:\\comlogo\\demo\\kidspac.lgp clicking on it causes the following command to be executed: wine C:\comlogo\Comlogo.exe c:comlogodemokidspac.lgp I.e., the backslashes in the quoted string are reduced once, but the backslashes in the unquoted string are reduced twice, resulting in an error when running the command. I can't see any reason why the backslashes should be collapsed twice when not quoted; this is definitely not consistent with how this command is interpreted by a shell. ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- strange escape handling in Exec line of .desktop files https://bugs.launchpad.net/bugs/335712 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 259385] Re: Intrepid Compiz hangs on login for i830MG, i845, (and i945GM?) video cards
** Changed in: yelp (Ubuntu Intrepid) Assignee: wangker (272788089-qq) = (unassigned) -- Intrepid Compiz hangs on login for i830MG, i845, (and i945GM?) video cards https://bugs.launchpad.net/bugs/259385 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 23435] Re: Can't select Esperanto language in gnome
reassigning to glibc, because I was just about to file for removal of belocs-locales-bin from jaunty since it's now uninstallable following the last glibc change. ** Changed in: glibc (Ubuntu) Sourcepackagename: belocs-locales-bin = glibc -- Can't select Esperanto language in gnome https://bugs.launchpad.net/bugs/23435 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 331201] Re: Please sync gtk-doc 1.11-3 (main) from debian unstable (main)
acked for sponsorship and FFe. ** Changed in: gtk-doc (Ubuntu) Status: New = Confirmed -- Please sync gtk-doc 1.11-3 (main) from debian unstable (main) https://bugs.launchpad.net/bugs/331201 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk-doc in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 331201] Please sync gtk-doc 1.11-3 (main) from debian unstable (main)
[Updating] gtk-doc (1.10-1ubuntu1 [Ubuntu] 1.11-3 [Debian]) * Trying to add gtk-doc... - gtk-doc_1.11.orig.tar.gz: downloading from http://ftp.debian.org/debian/ - gtk-doc_1.11-3.dsc: downloading from http://ftp.debian.org/debian/ - gtk-doc_1.11-3.diff.gz: downloading from http://ftp.debian.org/debian/ I: gtk-doc [main] - gtk-doc-tools_1.10-1ubuntu1 [main]. ** Changed in: gtk-doc (Ubuntu) Status: Confirmed = Fix Released -- Please sync gtk-doc 1.11-3 (main) from debian unstable (main) https://bugs.launchpad.net/bugs/331201 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk-doc in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 70293] Re: shutdown after plugging in AC with critical battery
marking invalid for acpi-support; this is a gnome-power-manager issue only, acpi-support is not triggering this shutdown. ** Changed in: acpi-support (Ubuntu) Status: Confirmed = Invalid -- shutdown after plugging in AC with critical battery https://bugs.launchpad.net/bugs/70293 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 280242] Re: [Intrepid] suspend to ram, gnome ssh askpass
** Changed in: gnome-keyring (Ubuntu) Sourcepackagename: acpi-support = gnome-keyring -- [Intrepid] suspend to ram, gnome ssh askpass https://bugs.launchpad.net/bugs/280242 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 301242] Re: When I press the shutdown button, the bar disappears and I cannot run command line
** Changed in: linux (Ubuntu) Sourcepackagename: acpi-support = linux ** Changed in: gnome-panel (Ubuntu) Sourcepackagename: linux = gnome-panel -- When I press the shutdown button, the bar disappears and I cannot run command line https://bugs.launchpad.net/bugs/301242 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 305730] Re: on user change after resume, system hibernate again
** Changed in: gnome-screensaver (Ubuntu) Sourcepackagename: acpi-support = gnome-screensaver -- on user change after resume, system hibernate again https://bugs.launchpad.net/bugs/305730 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 298836] Re: [intrepid] Laptop suspends randomly (Medion MD 95400)
** Changed in: gnome-power-manager (Ubuntu) Sourcepackagename: acpi-support = gnome-power-manager -- [intrepid] Laptop suspends randomly (Medion MD 95400) https://bugs.launchpad.net/bugs/298836 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 332342] Re: gnome-keyring-daemon crashed with SIGSEGV
the apport-retrace command appears to be broken in jaunty, but here's a
backtrace from manually unpacking the apport report and running gdb with
the dbgsym packages installed.
(gdb) thread apply all bt full
Thread 2 (process 1322):
#0 0x7f84d11b8496 in poll () from /lib/libc.so.6
No symbol table info available.
#1 0x0046ea90 in async_poll_func (ufds=0x2208e90, nfsd=11, timeout=-1)
at gkr-async.c:113
ret = -516
__PRETTY_FUNCTION__ = async_poll_func
#2 0x7f84d16a770f in g_main_context_iterate (context=0x21df560, block=1,
dispatch=1, self=value optimized out)
at /build/buildd/glib2.0-2.19.8/glib/gmain.c:2761
max_priority = 2147483647
timeout = -1
some_ready = value optimized out
nfds = 11
allocated_nfds = value optimized out
fds = (GPollFD *) 0x2208e90
__PRETTY_FUNCTION__ = g_main_context_iterate
#3 0x7f84d16a7d3d in IA__g_main_loop_run (loop=0x21df6d0)
at /build/buildd/glib2.0-2.19.8/glib/gmain.c:2656
self = (GThread *) 0x21cf690
__PRETTY_FUNCTION__ = IA__g_main_loop_run
#4 0x0040e497 in main (argc=1, argv=0x7fffdacb9a58)
at gkr-daemon.c:752
ctx = (GMainContext *) 0x21df560
Thread 1 (process 7742):
#0 egg_secure_realloc_full (memory=0x7f84d2b6cc68,
length=value optimized out, flags=1) at egg-secure-memory.c:277
block = (Block *) 0x7f84d2ca59c8
donew = value optimized out
alloc = value optimized out
__PRETTY_FUNCTION__ = egg_secure_realloc_full
#1 0x00466d20 in egg_buffer_reserve (buffer=0x7f84cf52ffc0,
len=value optimized out) at egg-buffer.c:175
newlen = 921
#2 0x00466d69 in egg_buffer_resize (buffer=0x7f84d2ca59c8, len=100)
at egg-buffer.c:190
No locals.
#3 0x004340bf in run_client_thread (data=0x2206798)
at gck-ssh-agent.c:118
call = {sock = 9, module = 0x2205830, req = 0x7f84cf52ffc0,
resp = 0x7f84cf52ff90}
req = {buf = 0x7f84d2b6cc68 , len = 4, allocated_len = 128,
failures = 0, allocator = 0x46ae00 egg_secure_realloc}
resp = {buf = 0x221b000 , len = 785, allocated_len = 1092,
failures = 0, allocator = 0x40d0f8 g_real...@plt}
op = value optimized out
__PRETTY_FUNCTION__ = run_client_thread
#4 0x7f84d16cdc74 in g_thread_create_proxy (data=0x21f0630)
at /build/buildd/glib2.0-2.19.8/glib/gthread.c:635
__PRETTY_FUNCTION__ = g_thread_create_proxy
#5 0x7f84d14553ba in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#6 0x7f84d11c1fcd in clone () from /lib/libc.so.6
No symbol table info available.
#7 0x in ?? ()
No symbol table info available.
(gdb)
--
gnome-keyring-daemon crashed with SIGSEGV
https://bugs.launchpad.net/bugs/332342
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 209520] Re: SMB error: Unable to mount location when server configured with security=share
oh - sorry, you mentioned upgrading from 7.10 so I assumed you were running 8.04. Yes, for 8.10 and above the default samba client behavior matches upstream's, and doesn't allow insecure security=share connections by default. You can change the behavior on the client side by setting 'client lanman auth = yes' on the client's /etc/samba/smb.conf, as mentioned earlier in the bug report. The only reason this bug is open is for gvfs to provide a better error message when trying to connect to such a server - the client will still refuse to connect to such servers by default, for security reasons. -- SMB error: Unable to mount location when server configured with security=share https://bugs.launchpad.net/bugs/209520 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 332342] [NEW] gnome-keyring-daemon crashed with SIGSEGV
Public bug reported: Binary package hint: gnome-keyring I want to make sure this bug gets reported because it seems like a pretty serious regression in gnome-keyring, but I'm not sending a coredump to launchpad because gnome-keyring-daemon actually had ahold of my ssh private key at the time it segfaulted. So here instead is a stack trace, cut'n'pasted from apport: Thread 2 (process 1322): #0 0x7f84d11b8496 in poll () from /lib/libc.so.6 #1 0x0046ea90 in ?? () #2 0x7f84d16a770f in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f84d16a7d3d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #4 0x0040e497 in ?? () #5 0x7f84d10fa5a6 in __libc_start_main () from /lib/libc.so.6 #6 0x0040dc39 in ?? () #7 0x7fffdacb9a48 in ?? () #8 0x001c in ?? () #9 0x0003 in ?? () #10 0x7fffdacbaf1b in ?? () #11 0x in ?? () . Thread 1 (process 7742): #0 0x0046aa0c in ?? () #1 0x00466d20 in ?? () #2 0x00466d69 in ?? () #3 0x004340bf in ?? () #4 0x7f84d16cdc74 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7f84d14553ba in start_thread () from /lib/libpthread.so.0 #6 0x7f84d11c1fcd in clone () from /lib/libc.so.6 #7 0x in ?? () I'll keep the crash dump around in case there's more information I can provide. The trigger appears to have been an ordinary ssh connection; I have ssh connection multiplexing enabled by default in .ssh/config, which explains the verbose output, but this output is normal for this particular host and is not normally a problem. $ ssh -C cocoplum.canonical.comControl socket connect(/home/vorlon/.ssh/master-vor...@cocoplum.canonical.com:22): Connection refused Control socket connect(/home/vorlon/.ssh/master-vor...@chinstrap.ubuntu.com:22): Connection refused ControlSocket /home/vorlon/.ssh/master-vor...@chinstrap.ubuntu.com:22 already exists, disabling multiplexing Error reading response length from authentication socket. Permission denied (publickey). $ ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- gnome-keyring-daemon crashed with SIGSEGV https://bugs.launchpad.net/bugs/332342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 209520] Re: SMB error: Unable to mount location when server configured with security=share
This bug is marked as resolved in Ubuntu 8.04; are you sure this is the bug you're seeing? You don't give any details about the problem you're having. -- SMB error: Unable to mount location when server configured with security=share https://bugs.launchpad.net/bugs/209520 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 330652] Re: Laptop LCD brightness settings remain in BIOS
Thank you for taking the time to report this issue and help to improve Ubuntu. This hotkey is not handled by acpi-support; it must be handled by either gnome-power-manager or the kernel. Reassigning to g-p-m. ** Changed in: gnome-power-manager (Ubuntu) Sourcepackagename: acpi-support = gnome-power-manager -- Laptop LCD brightness settings remain in BIOS https://bugs.launchpad.net/bugs/330652 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 329671] Re: ibm-lockbtn script needed to blank screen on R50e
Thank you for taking the time to report this bug and help to improve Ubuntu. The acpi-support package is deprecated, and the key handling provided there is being phased out in favor of direct handling by hal and the GNOME desktop. I believe gnome-settings-daemon is the component that handles the screen-lock keypress, so I'm reassigning this bug there. ** Changed in: gnome-settings-daemon (Ubuntu) Sourcepackagename: acpi-support = gnome-settings-daemon -- ibm-lockbtn script needed to blank screen on R50e https://bugs.launchpad.net/bugs/329671 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83432] Re: [apport] evolution crashed with SIGSEGV in ORBit_small_get_servant()
bug #327550 has been marked as a duplicate of this one, but this bug is two years old whereas the crash has only started happening for me this week. Something must have changed - do you have any idea what? -- [apport] evolution crashed with SIGSEGV in ORBit_small_get_servant() https://bugs.launchpad.net/bugs/83432 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 326083] [NEW] can't set the timezone from the clock applet: Launch helper exited with unknown return code 1
Public bug reported: Binary package hint: gnome-panel From at least Feb 1 on, I'm unable to change my current timezone in jaunty. Clicking the 'set' button results in a dialog popup: Failed to set the system timezone Launch helper exited with unknown return code 1 ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: gnome-panel 1:2.25.90-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel Uname: Linux 2.6.28-6-generic x86_64 ** Affects: gnome-panel (Ubuntu) Importance: Medium Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Confirmed ** Affects: gnome-panel (Ubuntu Jaunty) Importance: Medium Assignee: Ubuntu Desktop Bugs (desktop-bugs) Status: Confirmed ** Tags: apport-bug regression-potential -- can't set the timezone from the clock applet: Launch helper exited with unknown return code 1 https://bugs.launchpad.net/bugs/326083 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326083] Re: can't set the timezone from the clock applet: Launch helper exited with unknown return code 1
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/22035830/Dependencies.txt ** Changed in: gnome-panel (Ubuntu Jaunty) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Confirmed ** Tags added: regression-potential -- can't set the timezone from the clock applet: Launch helper exited with unknown return code 1 https://bugs.launchpad.net/bugs/326083 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 326088] [NEW] g-s-d spews warnings when switching VTs
Public bug reported: Binary package hint: gnome-settings-daemon While debugging keymap issues, I've manually stopped and restarted gnome-settings-daemon, which leaves stderr attached to the tty. I notice that every time I switch VTs (e.g., when suspending/resuming), g-s-d spits out a lot of warnings: Warning: Type PC_RALT_LEVEL2 has 2 levels, but LALT has 3 symbols Ignoring extra symbols Warning: Key OUTP not found in evdev+aliases(qwerty) keycodes Symbols ignored Warning: Key KITG not found in evdev+aliases(qwerty) keycodes Symbols ignored Warning: Key KIDN not found in evdev+aliases(qwerty) keycodes Symbols ignored Warning: Key KIUP not found in evdev+aliases(qwerty) keycodes Symbols ignored Warning: Key RO not found in evdev+aliases(qwerty) keycodes Symbols ignored Warning: No symbols defined for AB11 (keycode 97) Warning: No symbols defined for JPCM (keycode 103) Warning: No symbols defined for I120 (keycode 120) Warning: No symbols defined for AE13 (keycode 132) Warning: No symbols defined for I149 (keycode 149) Warning: No symbols defined for I154 (keycode 154) Warning: No symbols defined for I161 (keycode 161) Warning: No symbols defined for I168 (keycode 168) Warning: No symbols defined for I178 (keycode 178) Warning: No symbols defined for I183 (keycode 183) Warning: No symbols defined for I184 (keycode 184) Warning: No symbols defined for FK13 (keycode 191) Warning: No symbols defined for FK14 (keycode 192) Warning: No symbols defined for FK15 (keycode 193) Warning: No symbols defined for FK16 (keycode 194) Warning: No symbols defined for FK17 (keycode 195) Warning: No symbols defined for FK18 (keycode 196) Warning: No symbols defined for FK19 (keycode 197) Warning: No symbols defined for FK20 (keycode 198) Warning: No symbols defined for FK21 (keycode 199) Warning: No symbols defined for FK22 (keycode 200) Warning: No symbols defined for FK23 (keycode 201) Warning: No symbols defined for FK24 (keycode 202) Warning: No symbols defined for I217 (keycode 217) Warning: No symbols defined for I219 (keycode 219) Warning: No symbols defined for I221 (keycode 221) Warning: No symbols defined for I222 (keycode 222) Warning: No symbols defined for I224 (keycode 224) Warning: No symbols defined for I226 (keycode 226) Warning: No symbols defined for I228 (keycode 228) Warning: No symbols defined for I230 (keycode 230) Warning: No symbols defined for I247 (keycode 247) Warning: No symbols defined for I248 (keycode 248) Warning: No symbols defined for I249 (keycode 249) Warning: No symbols defined for I250 (keycode 250) Warning: No symbols defined for I251 (keycode 251) Warning: No symbols defined for I252 (keycode 252) Warning: No symbols defined for I253 (keycode 253) xmodmap: unable to open file '/home/vorlon/.Xmodmap' for reading xmodmap: 1 error encountered, aborting. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: gnome-settings-daemon 2.25.3-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon Uname: Linux 2.6.28-6-generic x86_64 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Low Status: New ** Tags: apport-bug -- g-s-d spews warnings when switching VTs https://bugs.launchpad.net/bugs/326088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326088] Re: g-s-d spews warnings when switching VTs
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/22035974/Dependencies.txt ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Low -- g-s-d spews warnings when switching VTs https://bugs.launchpad.net/bugs/326088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326083] Re: can't set the timezone from the clock applet: Launch helper exited with unknown return code 1
Ah, I distinctly did not restart gnome-panel after upgrade. Done so now and it's fixed, thanks. :) ** Changed in: gnome-panel (Ubuntu Jaunty) Status: Confirmed = Fix Released -- can't set the timezone from the clock applet: Launch helper exited with unknown return code 1 https://bugs.launchpad.net/bugs/326083 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 242713] Re: Suspends that are longer than 6 hours will inexplicably claim to fail, but not really fail
** Tags added: verification-done ** Tags removed: verification-needed -- Suspends that are longer than 6 hours will inexplicably claim to fail, but not really fail https://bugs.launchpad.net/bugs/242713 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 31063] Re: Asus A6U, two hotkeys not working
The 'disable touchpad' key currently doesn't work with acpi-support because it relies on the obsolete synclient command. The right command to toggle touchpads in 8.10 and above is xinput: $ xinput set-int-prop devnum 'Device Enabled' 8 [0|1] hal needs to be fixed to relay this event, and gnome-settings-daemon needs to be updated to handle it. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided = Low Status: New = Confirmed -- Asus A6U, two hotkeys not working https://bugs.launchpad.net/bugs/31063 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 306310] Re: Resume (from memory) goes back to sleep automatically
On Mon, Feb 02, 2009 at 01:33:32PM -, Chris Bainbridge wrote: With it stopped I get: keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0 keycode 150 = (keysym 0x1008ff2f, XF86Sleep), state = 0x0 This is the expected behavior; one of these is the KeyPress event, the other is the KeyRelease event. I wonder if it is possible that these two events (press and release) both get mapped onto XF86Sleep keycode events, generating two suspend calls? AIUI, the remaining issue is that gnome-power-manager is responding both to the X keypress and the hal event. (I.e., look at the output of 'lshal -m'.) It's not clear to me why this affects some systems and not other. For me, lshal -m shows: 17:05:11.878: computer_logicaldev_input_4 condition ButtonPressed = sleep and no other events when hitting Fn+F4. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- Resume (from memory) goes back to sleep automatically https://bugs.launchpad.net/bugs/306310 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 306310] Re: Resume (from memory) goes back to sleep automatically
Based on discussion with apw, reopening this task since it appears that gnome-power-manager is responding to both an X key event and a hal event when it shouldn't do so. ** Changed in: gnome-power-manager (Ubuntu) Status: Invalid = Confirmed -- Resume (from memory) goes back to sleep automatically https://bugs.launchpad.net/bugs/306310 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 322126] Re: gvfsd-gphoto2 crashed with SIGSEGV in malloc()
I can confirm that this bug is fixed in the latest jaunty upload. ** Changed in: gvfs (Ubuntu) Status: Incomplete = Fix Released -- gvfsd-gphoto2 crashed with SIGSEGV in malloc() https://bugs.launchpad.net/bugs/322126 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 51537] Re: Wrong handling of volume buttons on IBM Thinkpad notebooks
To the extent that this is an acpi-support problem, the fix is committed now and will be uploaded soon. However, with or without acpi-support, the kernel now synthesizes a keypress event for these buttons due to the mask set in /sys/devices/platform/thinkpad_acpi/hotkey_mask. The setting of this mask is currently done in the hotkey-setup package; I'm not sure whether we should consider this current mask setting wrong, but that's the next package in the chain, so opening a task there. ** Changed in: acpi-support (Ubuntu) Status: Confirmed = Fix Committed ** Also affects: hotkey-setup (Ubuntu) Importance: Undecided Status: New -- Wrong handling of volume buttons on IBM Thinkpad notebooks https://bugs.launchpad.net/bugs/51537 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
Re: [Bug 321311] Re: gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set
On Sun, Feb 01, 2009 at 03:24:34PM -, Arne Goetje wrote: Can you please test with GTK_IM_MODULE=scim-bridge, since that is the default setting in Intrepid and Jaunty? Confirmed, the problem is also present when specifying GTK_IM_MODULE=scim-bridge. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set https://bugs.launchpad.net/bugs/321311 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 324200] Re: gvfsd-gphoto2 crashed with SIGSEGV in malloc_consolidate()
*** This bug is a duplicate of bug 322126 *** https://bugs.launchpad.net/bugs/322126 ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/21892439/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/21892440/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/21892441/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/21892442/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/21892443/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/21892444/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/21892445/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/21892446/ThreadStacktrace.txt ** Visibility changed to: Public ** Changed in: gvfs (Ubuntu) Importance: Undecided = Medium Status: New = Confirmed -- gvfsd-gphoto2 crashed with SIGSEGV in malloc_consolidate() https://bugs.launchpad.net/bugs/324200 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 322126] Re: gvfsd-gphoto2 crashed with SIGSEGV in malloc()
Looks like my apport bug got automarked as a duplicate of this one. I'm happy to do a valgrind test - can you provide more guidance wrt the best way to launch a gvfsd backend under valgrind, given that these are normally auto-spawned by gvfsd itself? -- gvfsd-gphoto2 crashed with SIGSEGV in malloc() https://bugs.launchpad.net/bugs/322126 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 320666] Re: gnome-screensaver fails to unlock after gtk 2.15.0 upgrade
*** This bug is a duplicate of bug 321311 *** https://bugs.launchpad.net/bugs/321311 ** This bug has been marked a duplicate of bug 321311 gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set -- gnome-screensaver fails to unlock after gtk 2.15.0 upgrade https://bugs.launchpad.net/bugs/320666 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 306310] Re: Resume (from memory) goes back to sleep automatically
15:12:41.659: computer_logicaldev_input_3 condition ButtonPressed = sleep 15:12:41.690: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = sleep I think this is an acpi-support bug (i.e., this bug is caused by acpi- support being here at all) - acpi-support is set up to synthesize a 'sleep' key event when pressing Fn+F4, but the kernel already handles synthesizing this event, so we end up with *two* hal sleep events showing up on two different input devices. Whether the hal events are what g-p-m or kpowersave should be listening for is a separate question - but we definitely shouldn't be emitting two sleep events for one key press. Conveniently, it happens that I've already committed a fix for this to the acpi-support bzr branch, and will upload soon. In the meantime, users can verify that this fixes the problem by running 'sudo /etc/init.d/acpid stop' and then suspending with Fn+F4. ** Changed in: hal (Ubuntu) Status: New = Invalid ** Changed in: acpi-support (Ubuntu) Sourcepackagename: linux = acpi-support Assignee: Andy Whitcroft (apw) = Steve Langasek (vorlon) Status: In Progress = Fix Committed ** Changed in: gnome-power Status: New = Invalid ** Changed in: gnome-power-manager (Ubuntu) Status: New = Invalid ** Changed in: pm-utils (Ubuntu) Status: New = Invalid -- Resume (from memory) goes back to sleep automatically https://bugs.launchpad.net/bugs/306310 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 321311] Re: gnome-screensaver dialog helper spins indefinitely, never unlocks the session
Tested without GTK_IM_MODULE set per Seb - gnome-screensaver works fine when not using GTK_IM_MODULE=xim. ** Changed in: gtk+2.0 (Ubuntu Jaunty) Sourcepackagename: gnome-screensaver = gtk+2.0 -- gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set https://bugs.launchpad.net/bugs/321311 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 321311] Re: gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set
** Summary changed: - gnome-screensaver dialog helper spins indefinitely, never unlocks the session + gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set -- gnome-screensaver dialog helper spins indefinitely, never unlocks the session, when GTK_IM_MODULE is set https://bugs.launchpad.net/bugs/321311 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 321311] Re: gnome-screensaver dialog helper spins indefinitely, never unlocks the session
I've just tested with downgrading to the intrepid version of gnome- screensaver; same results. I've also done a bit of stracing, and the helper does get as far as reading /etc/pam.d and loading the modules; then it falls down somewhere around where it spawns a separate thread for PAM in order to be able to continue handling UI events. -- gnome-screensaver dialog helper spins indefinitely, never unlocks the session https://bugs.launchpad.net/bugs/321311 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 321311] Re: gnome-screensaver dialog helper spins indefinitely, never unlocks the session
Output from gnome-screensaver --no-daemon --debug while trying to get the screen to unlock: [find_window_at_pointer] gs-manager.c:1175 (01:53:03): Requesting unlock for screen 0 [gs_window_request_unlock] gs-window-x11.c:1586 (01:53:03): Requesting unlock [window_dialog_up_cb] gs-manager.c:1084 (01:53:03): Handling dialog up [gs_grab_get_keyboard] gs-grab-x11.c:166 (01:53:03): Grabbing keyboard widget=3C00021 [gs_grab_get_mouse] gs-grab-x11.c:193 (01:53:03):Grabbing mouse widget=3C00021 [gs_grab_release_mouse] gs-grab-x11.c:237 (01:53:03):Ungrabbing pointer [window_dialog_up_cb] gs-manager.c:1107 (01:53:03): Suspending jobs [gs_job_suspend] gs-job.c:508 (01:53:03):suspending job [gs_job_suspend] gs-job.c:508 (01:53:03):suspending job [popup_dialog_idle] gs-window-x11.c:1531 (01:53:03): Popping up dialog [gs_window_clear_to_background_pixmap] gs-window-x11.c:301 (01:53:03): Clearing window to background pixmap [gs_window_move_resize_window] gs-window-x11.c:455 (01:53:03): Move and/or resize window on monitor 0: x=0 y=0 w=1680 h=1050 [error_watch] gs-window-x11.c:959 (01:53:03):command error output: [gs_debug_init] gs-debug.c:106 (01:53:03):Debugging enabled [listener_service_deleted] gs-listener-dbus.c:1043 (01:53:03): DBUS service deleted: [error_watch] gs-window-x11.c:959 (01:53:04):command error output: [auth_message_handler] gnome-screensaver-dialog.c:221 (01:53:04): Got message style 1: 'Password: ' [listener_service_deleted] gs-listener-dbus.c:1043 (01:53:04): DBUS service deleted: [gs_window_raise] gs-window-x11.c:728 (01:53:04):Raising screensaver window [gs_window_raise] gs-window-x11.c:728 (01:53:04):Raising screensaver window [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [window_obscured_cb] gs-manager.c:1360 (01:53:04): Handling window obscured: obscured [gs_job_stop] gs-job.c:479 (01:53:04): stopping job [gs_job_stop] gs-job.c:482 (01:53:04): Could not stop job: pid not defined [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [window_obscured_cb] gs-manager.c:1360 (01:53:04): Handling window obscured: unobscured [manager_maybe_start_job_for_window] gs-manager.c:227 (01:53:04):Not starting job because dialog is up [gs_manager_request_unlock] gs-manager.c:1791 (01:53:04):Request unlock but dialog is already up [lock_command_watch] gs-window-x11.c:1431 (01:53:04):command output: WINDOW ID=69206045 [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [gs_window_move_resize_window] gs-window-x11.c:455 (01:53:04): Move and/or resize window on monitor 0: x=0 y=0 w=1680 h=1050 [gs_window_raise] gs-window-x11.c:728 (01:53:04):Raising screensaver window [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [error_watch] gs-window-x11.c:959 (01:53:04):command error output: [gs_lock_plug_enable_prompt] gs-lock-plug.c:1189 (01:53:04): Setting prompt to: Password: [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:780 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [gs_window_xevent] gs-window-x11.c:799 (01:53:04): not raising our windows [window_obscured_cb] gs-manager.c:1360 (01:53:04): Handling window obscured: obscured [gs_job_stop] gs-job.c:479 (01:53:04): stopping job [gs_job_stop] gs-job.c:482 (01:53:04): Could not stop job: pid not defined [error_watch] gs-window-x11.c:959 (01:53:07):command error output: [request_response] gnome-screensaver-dialog.c:149 (01:53:07): got response: -2 -- gnome-screensaver dialog helper spins indefinitely, never unlocks the session https://bugs.launchpad.net/bugs/321311 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing
[Bug 315941] Re: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_config_match()
I would like to hear back from the original submitter before concluding this was a duplicate, especially since the bug in question was *not* fixed yet on Jan 21 when you commented that it had stopped for you. -- gnome-settings-daemon crashed with SIGSEGV in gnome_rr_config_match() https://bugs.launchpad.net/bugs/315941 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 281956] Re: evolution uses wrong date to switch to daylight saving timezone in timezone Europe/Brussels
With two successful reports and no reports of regressions after 90 days, I'm marking this as verified - let's not wait until the next DST change for users to run into the problem again before publishing this fix! ** Tags added: verification-done ** Tags removed: verification-needed -- evolution uses wrong date to switch to daylight saving timezone in timezone Europe/Brussels https://bugs.launchpad.net/bugs/281956 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 309674] Re: python-gobject in hardy-updates on sparc misbuilt only for python2.5
** Description changed: The version of pygobject in hardy-updates on sparc is misbuilt to supply only a python2.5 version. This causes ubiquity to fail to build since python-gtk2 is uninstallable (http://launchpadlibrarian.net/20576122 /buildlog_ubuntu-hardy-sparc.ubiquity_1.8.13_FAILEDTOBUILD.txt.gz). The cause of this is timestamp skew in the build; although it currently happens to apply only to sparc, it could affect any other architecture in a future build, and therefore should be fixed before it bites us in a more painful place. Looking at the pygobject source package in hardy-updates, it includes the following two patches: cjwat...@sarantium ~/src/ubuntu/pygobject/pygobject-2.14.2$ diffstat debian/patches/60_use-python-config-for-includes.patch aclocal.m4 | 843 ++- configure| 217 --- configure.ac |4 3 files changed, 449 insertions(+), 615 deletions(-) cjwat...@sarantium ~/src/ubuntu/pygobject/pygobject-2.14.2$ diffstat debian/patches/61_dont_use_setwakeupfd.patch configure| 62 --- configure.ac | 20 --- 2 files changed, 82 deletions(-) If the second patch happens to be applied sufficiently later (in the next second) than the first, the standard Automake rules to rebuild autotools files when they change will note that aclocal.m4 is older than configure.ac, and will therefore rerun aclocal and autoconf, and subsequently run ./config.status --recheck. These are run as subprocesses of make and therefore without the PYTHON environment variable that debian/rules passes to configure; as a result, ./config.status picks up the default system python (2.5) rather than the one forced by the PYTHON environment variable (which is 2.4 in the first build pass). You can see the problem in action by comparing these two build logs: http://launchpadlibrarian.net/15910647/buildlog_ubuntu-hardy-i386.pygobject_2.14.2-0ubuntu1_FULLYBUILT.txt.gz http://launchpadlibrarian.net/15911262/buildlog_ubuntu-hardy-sparc.pygobject_2.14.2-0ubuntu1_FULLYBUILT.txt.gz Possible fixes include: (a) regenerate aclocal.m4 in a later patch rather than in 60_use-python-config-for-includes.patch; (b) touch aclocal.m4 and configure after applying patches; (c) set PYTHON when calling make so that even if ./config.status --recheck is run it will produce correct results. The versions of pygobject in intrepid and jaunty do (a) (they contain debian/patches/90_autofoo.patch) and therefore do not suffer from this problem, although in principle they might later if the autotools patch were removed. I am inclined to recommend approach (c) in both hardy-updates and jaunty, on the basis that it is a more permanent fix. + + TEST CASE: + 1. with hardy-updates enabled and installed, test two or more applications that use pygtk: e.g., alacarte, update-manager, system-config-printer-gnome, quodlibet + 2. enable hardy-proposed and install the python-gobject package there + 3. retest that the above applications continue to work. + + This does not test that the python2.4 bindings that have been + reintroduced on sparc work correctly - nothing in Ubuntu 8.04 should be + using python2.4, really - so we assume that the fact that the python2.4 + bindings are again present in the package is sufficient evidence that + this is fixed. -- python-gobject in hardy-updates on sparc misbuilt only for python2.5 https://bugs.launchpad.net/bugs/309674 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 267018] Re: regression: g-s-d no longer handles Fn+F7 as xrandr --auto
As near as I can tell, this is still present in jaunty. /usr/share/gconf/schemas/apps_gnome_settings_daemon_keybindings.schemas contains: schema key/schemas/apps/gnome_settings_daemon/keybindings/xrandr/key applyto/apps/gnome_settings_daemon/keybindings/xrandr/applyto typestring/type default0xd6/default locale name=C shortActivate connected display/short longActivate a connected display using xrandr/long /locale /schema If I disable my keybinding override (which had pointed this at XF86Display), then Fn+F7 has no effect. (If I re-enable my keybinding override, it has lots of broken effects, but that's for another bug report. :-) I'm pretty sure that this is an event that belongs in the keyboard event layer (per https://wiki.ubuntu.com/Hotkeys/Architecture) rather than as a hal event; so this looks unfixed to me. -- regression: g-s-d no longer handles Fn+F7 as xrandr --auto https://bugs.launchpad.net/bugs/267018 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 322111] [NEW] gnome-settings-daemon xrandr plugin gets wrong resolution on external monitor
Public bug reported: Binary package hint: gnome-settings-daemon Using gnome-settings-daemon to activate my external monitor (using the XF86Display (Fn+F7) key on my thinkpad, which I've configured as the binding in /apps/gnome_settings_daemon/keybindings/xrandr), in jaunty the resolution of the external display is set to match that of my LCD. In previous releases, this correctly used the xrandr-preferred resolution. Output of xrandr after connecting the monitor and hitting Fn+F7: $ xrandr Screen 0: minimum 320 x 200, current 1280 x 800, maximum 2640 x 1700 VGA connected 1280x800+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 60.0 + 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.8* 1152x864 75.0 1024x768 75.0 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48075.0 72.8 66.7 59.9 720x40070.1 LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1280x800 60.0*+ 50.0 1024x768 85.0 75.0 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 72.8 75.0 59.9 720x40085.0 640x40085.1 640x35085.1 TMDS-1 disconnected (normal left inverted right x axis y axis) Output of xrandr after connecting the monitor and running xrandr --auto manually: $ xrandr Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 2640 x 1700 VGA connected 1680x1050+0+0 (normal left inverted right x axis y axis) 473mm x 296mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.0 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48075.0 72.8 66.7 59.9 720x40070.1 LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1280x800 60.0*+ 50.0 1024x768 85.0 75.0 70.1 60.0 832x62474.6 800x60085.1 72.2 75.0 60.3 56.2 640x48085.0 72.8 75.0 59.9 720x40085.0 640x40085.1 640x35085.1 TMDS-1 disconnected (normal left inverted right x axis y axis) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: regression-potential ** Tags added: regression-potential -- gnome-settings-daemon xrandr plugin gets wrong resolution on external monitor https://bugs.launchpad.net/bugs/322111 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 315974] Re: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch()
AFAIK, Ubuntu tasks aren't meant to be marked 'fix committed' unless the fix is in an Ubuntu repo somewhere pending upload, which was not the case here. But I've grabbed the change from upstream revision 672, and this will be uploaded soon anyway. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Committed = In Progress -- gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/315974 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 322111] Re: gnome-settings-daemon xrandr plugin gets wrong resolution on external monitor
This seems to have been fallout from the crasher bug in the xrandr plugin; with that fixed, the resolution comes up correctly. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Invalid -- gnome-settings-daemon xrandr plugin gets wrong resolution on external monitor https://bugs.launchpad.net/bugs/322111 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 315941] Re: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_config_match()
sorry, I mean 2.25.3-0ubuntu2... -- gnome-settings-daemon crashed with SIGSEGV in gnome_rr_config_match() https://bugs.launchpad.net/bugs/315941 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
