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
** 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
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
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
** 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
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
** 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
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.
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
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
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
(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
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
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
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
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 =
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
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
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
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
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
** 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
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
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
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.
--
** 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,
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
** 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
** 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
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
** 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.
--
** 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.
--
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
** 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
** 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
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
** 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,
)
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
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 -
** 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
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
[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
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
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
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
** 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.
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
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
.
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
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.,
** 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,
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
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
[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
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
** 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
** 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
** 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
** 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
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
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
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
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
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 =
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
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()
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
** 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:
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
** 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
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
** 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
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
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
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
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
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
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
*** 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:
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
*** 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
' 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
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
** 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
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
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]
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()
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
--
** 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
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
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
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)
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
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.
--
Please test with the just uploaded gnome-settings-daemon
2.25.3-0ubuntu1; this may be the same as bug #315974.
--
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
Please test with the just uploaded gnome-settings-daemon
2.25.3-0ubuntu1; this may be the same as bug #315974.
--
gnome-settings-daemon crashed with SIGSEGV in gnome_rr_output_get_name()
https://bugs.launchpad.net/bugs/321127
You received this bug notification because you are a member of Ubuntu
sorry, I mean 2.25.3-0ubuntu2.
--
gnome-settings-daemon crashed with SIGSEGV in gnome_rr_output_get_name()
https://bugs.launchpad.net/bugs/321127
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
).
--
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
Public bug reported:
Binary package hint: gnome-screensaver
gnome-screensaver in jaunty is failing to unlock my session when I give
it the password. Strace shows the gnome-screensaver-dialog process is
spinning indefinitely watching a socket (the X socket, I guess), and
doesn't appear to be
** Changed in: gnome-control-center (Ubuntu Hardy)
Target: ubuntu-8.04.2 = ubuntu-8.04.3
--
Drag-and-drop theme from web page fails
https://bugs.launchpad.net/bugs/252885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
1201 - 1300 of 1627 matches
Mail list logo
