** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/38765807/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38765808/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/38765809/Disassembly.txt
** Attachm
Looks like the last update fixed it. I just needed to logout!
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Invalid
--
Brightness up/down keys do not change brightness on Samsung NC10
https://bugs.launchpad.net/bugs/517241
You received this bug notification because you are a
Public bug reported:
Binary package hint: gnome-power-manager
Brightness cursor keys do not work (gnome and xfce tried).
When the Fn+Up and Fn+Down keys are pressed the slider notification
appears next to the panel but the slider does not move up or down and
the brightness does not change.
Scre
There is some more info on bug #295251
** This bug is no longer a duplicate of bug 295251
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
--
Samsung NC10 screen brightness up/down function keys do not work
https://bugs.launchpad.net/bugs/448885
You received this
There is some more info on bug #295251
** This bug has been marked a duplicate of bug 295251
Samsung NC10 brightness keys block keyboard and produce all-or-nothing effect
--
Samsung NC10 screen brightness up/down function keys do not work
https://bugs.launchpad.net/bugs/448885
You received th
*** This bug is a duplicate of bug 295251 ***
https://bugs.launchpad.net/bugs/295251
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=14052
Importance: Unknown
Status: Unknown
--
Samsung NC10 screen brightness up/down function keys do not work
https://bugs.l
Hi,
Just to follow up. If I follow these instructions in the kernel bug
#12021 (http://bugzilla.kernel.org/show_bug.cgi?id=12021) and switch off
the acpi (acpi=off) then I can control the up/down brightness. However
obviously my battery is no longer detected.
Changing the BIOS setting between "Au
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
nautilus assert failure:
ERROR:dbus-gproxy.c:1051:dbus_g_proxy_manager_unregister: assertion failed:
(link != NULL)
https://bugs.launchpad.net/bugs/429126
You received this bug notification because you are a member of Ubuntu
De
** Visibility changed to: Public
--
seahorse-agent crashed with SIGABRT in __kernel_vsyscall()
https://bugs.launchpad.net/bugs/425382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse-plugins in ubuntu.
--
desktop-bugs mailing li
*** This bug is a duplicate of bug 425382 ***
https://bugs.launchpad.net/bugs/425382
** This bug has been marked a duplicate of bug 425382
seahorse-agent crashed with SIGABRT in __kernel_vsyscall()
--
seahorse-agent crashed with SIGABRT in __kernel_vsyscall()
https://bugs.launchpad.net/bu
Package: gnome-utils
State: installed
Automatically installed: no
Version: 2.25.90-0ubuntu1
Priority: optional
Section: gnome
--
[Feisty] gnome-screenshot should not take a screenie of itself
https://bugs.launchpad.net/bugs/93234
You received this bug notification because you are a member of Ubun
Hi this happens for me also on Jaunty
** Tags added: 9.04 jaunty
--
[Feisty] gnome-screenshot should not take a screenie of itself
https://bugs.launchpad.net/bugs/93234
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Tags added: 9.04
** Tags removed: 8.10
--
gdmgreeter crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/317171
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing lis
** Tags added: 8.10 jaunty ubuntu
--
gdmgreeter crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/317171
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
OK. When I tested it last week no apport crash report was created.
However, there must have been some update fix because a crash dump has
been created now.
Submitted as new bug report 317171.
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/21215035/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21215036/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/21215037/Disassembly.txt
** Attachm
** Attachment added: "Xorg.1.log"
http://launchpadlibrarian.net/20978419/Xorg.1.log
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
D
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/20978415/Xorg.0.log
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
D
** Attachment added: "GDM log 2"
http://launchpadlibrarian.net/20978382/%253A1.log
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
De
** Attachment added: "%3A0.log"
http://launchpadlibrarian.net/20978372/%253A0.log
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
Des
** Attachment added: "dmesg"
http://launchpadlibrarian.net/20978369/dmesg
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
Desktop Bug
** Attachment added: "messages"
http://launchpadlibrarian.net/20978370/messages
--
segfault at 1cc in libgdk-x11-2.0 and libX11 when logging in via XDCMP with
Hummingbird exceed
https://bugs.launchpad.net/bugs/314699
You received this bug notification because you are a member of Ubuntu
Deskt
Public bug reported:
Binary package hint: gdm
I have setup XDCMP on the ubuntu server and can connect to it and logon
if I use XMing.
If I use Exceed I can successfully connect and get a logon screen (if I
disable RRAND) but when I logon the session disconnects.
In the message log I find segfau
23 matches
Mail list logo
