[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=608402. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-06-27T10:29:54+00:00 ritz wrote: Description of problem: gpm crashes on startup Version-Release number of selected component (if applicable): gnome-power-manager-2.31.3-1.fc14.x86_64 How reproducible: always Additional info: $ gnome-power-bugreport.sh Distro version: Fedora release 14 (Rawhide) Kernel version: 2.6.34-45.fc14.x86_64 g-p-m version:2.31.3 HAL version: 0.5.14 System manufacturer: missing System version: missing System product: missing AC adapter present: yes Battery present: yes Laptop panel present: yes CPU scaling present: no bt - Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory [New Thread 0x70a6f710 (LWP 2477)] (gnome-power-manager:2474): GLib-GObject-WARNING **: gsignal.c:2276: signal `proxy-status' is invalid for instance `0x6b7260' Detaching after fork from child process 2479. The program 'gnome-power-manager' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 171 error_code 5 request_code 148 minor_code 15) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (gdb) bt #0 0x0030646aa420 in _exit () from /lib64/libc.so.6 #1 0x003064636f52 in exit () from /lib64/libc.so.6 #2 0x0037df867fcf in ?? () from /usr/lib64/libgdk-x11-3.0.so.0 #3 0x003067e46da4 in _XError () from /usr/lib64/libX11.so.6 #4 0x003067e4d277 in ?? () from /usr/lib64/libX11.so.6 #5 0x003067e4d983 in _XReply () from /usr/lib64/libX11.so.6 #6 0x00306aa051bc in XRRGetOutputProperty () from /usr/lib64/libXrandr.so.2 #7 0x00419e0a in ?? () #8 0x0041a330 in ?? () #9 0x0041aa4a in ?? () #10 0x00409ba9 in ?? () #11 0x77873915 in g_type_create_instance (type=) at gtype.c:1888 #12 0x7785669c in g_object_constructor (type=, n_construct_properties=0, construct_params=0x0) at gobject.c:1483 #13 0x7785796a in g_object_newv (object_type=7159312, n_parameters=0, parameters=0x0) at gobject.c:1267 #14 0x7785819c in g_object_new (object_type=7159312, first_property_name=0x0) at gobject.c:1179 #15 0x0040d912 in ?? () #16 0x77873915 in g_type_create_instance (type=) at gtype.c:1888 #17 0x7785669c in g_object_constructor (type=, n_construct_properties=0, construct_params=0x0) at gobject.c:1483 #18 0x7785796a in g_object_newv (object_type=7025504, n_parameters=0, parameters=0x0) at gobject.c:1267 #19 0x7785819c in g_object_new (object_type=7025504, first_property_name=0x0) at gobject.c:1179 #20 0x0040d312 in ?? () #21 0x0040ce7c in ?? () #22 0x00306461ed6d in __libc_start_main () from /lib64/libc.so.6 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/614248/comments/0 On 2010-06-27T12:42:19+00:00 Richard wrote: Your backtrace is meanlingless. You need to install the debuginfo packages. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/614248/comments/1 On 2010-07-13T08:28:52+00:00 ritz wrote: Breakpoint 1, 0x003b500aa260 in _exit () from /lib64/libc.so.6 (gdb) bt #0 0x003b500aa260 in _exit () from /lib64/libc.so.6 #1 0x003b50036f12 in exit () from /lib64/libc.so.6 #2 0x003423c65cff in ?? () from /usr/lib64/libgdk-x11-3.0.so.0 #3 0x003b53c46da4 in _XError () from /usr/lib64/libX11.so.6 #4 0x003b53c4d277 in ?? () from /usr/lib64/libX11.so.6 #5 0x003b53c4d983 in _XReply () from /usr/lib64/libX11.so.6 #6 0x003b584051bc in XRRGetOutputProperty () from /usr/lib64/libXrandr.so.2 #7 0x0041c25a in gpm_brightness_output_get_internal (brightness= 0x6d5180, output=81, cur=0x7fffd644) at gpm-brightness.c:178 #8 0x0041c780 in gpm_brightness_output_get_percentage (brightness= 0x6d5180, op=) at gpm-brightness.c:323 #9 gpm_brightness_foreach_resource (brightness=0x6d5180, op=) at gpm-brightness.c:489 #10 gpm_brightness_foreach_screen (brightness=0x6d5180, op=) at
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Can this fix possibly be backported to Lucid? Or should I open a separate bug? (gnome-power-manager:1719): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy- status' is invalid for instance `0x88068f0' $ apt-cache policy gnome-power-manager gnome-power-manager: Installed: 2.30.0-0ubuntu1 Candidate: 2.30.0-0ubuntu1 Version table: *** 2.30.0-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
It doesn't really justify a backport, it's only a warning -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
On 09/21/2010 02:00 PM, Chris Coulson wrote: It doesn't really justify a backport, it's only a warning Got it - thanks. -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Then I think it is time to close this bug and to thank everybody who was involved in fixing it; On my system another update of gnome-power- manager has passed without making the problem return. ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Fix Released -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
On my system the last update to gnome-power-manager seems to have resolved the crash. Can anyone confirm this? -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Yes, I confirm! Am 25.08.2010 22:18, schrieb PeterPall: On my system the last update to gnome-power-manager seems to have resolved the crash. Can anyone confirm this? -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
It seems to be stable now (gnome-power-manager 2.31.90-0ubuntu4, Dell M65). John - Original Message From: PeterPall 614...@bugs.launchpad.net To: johnb...@yahoo.com Sent: Wed, August 25, 2010 9:18:15 PM Subject: [Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' On my system the last update to gnome-power-manager seems to have resolved the crash. Can anyone confirm this? -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a direct subscriber of the bug. Status in “gnome-power-manager” package in Ubuntu: Confirmed Status in “gnome-power-manager” package in Fedora: Unknown Bug description: Binary package hint: gnome-power-manager got this error when maverick start: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-power-manager 2.31.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-14.19-generic-pae 2.6.35 Uname: Linux 2.6.35-14-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Aug 6 09:50:40 2010 ExecutablePath: /usr/bin/gnome-power-manager GConfNonDefault: /apps/gnome-power-manager/lock/blank_screen=false /apps/gnome-power-manager/lock/use_screensaver_settings=false /apps/gnome-power-manager/notify/sleep_failed_uri= /apps/gnome-power-manager/ui/icon_policy=charge GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic-pae root=UUID=00c5de83-479c-4ab0-9b54-9af0a727175e ro vga=791 quiet splash ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: gnome-power-manager XsessionErrors: (polkit-gnome-authentication-agent-1:2678): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed dmi.bios.date: 10/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd10/22/2009:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/614248/+subscribe -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Likewise the current gnome-power-manager 2.31.90-0ubuntu4 appears to be stable on my system (HP ProBook 4310s). -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
** Bug watch added: Red Hat Bugzilla #608402 https://bugzilla.redhat.com/show_bug.cgi?id=608402 ** Also affects: gnome-power-manager (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=608402 Importance: Unknown Status: Unknown -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
More precisely, the Backlight atom is not being set. Also GPM checks the BACKLIGHT atom and not the Backlight atom which is deprecated. -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
This bug is caused by failed hardware recognition somewhere in uPower or the Kernel. This causes gpm to (rather awkwardly) pass a null off to xrandr, resulting in a crash. Fixing the crash will not restore functionality however. -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
This bug might be a duplicate of Bug #615812 and Bug #618967; On my system gnome-power-manager no longer asks for a password. -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
Another duplicate of this bug might be Bug #615071. ** Changed in: gnome-power-manager (Ubuntu) Status: New = Incomplete ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Confirmed -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
I too am seeing crashes in gnome-power-management: (gnome-power-manager:2355): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x1406230' 12 Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 159 error_code 5 request_code 150 minor_code 15) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
I am seeing the same problem: gnome-power-manager crashes immediately on launch with this message: (gnome-power-manager:3662): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.13/gobject/gsignal.c:2275: signal `proxy- status' is invalid for instance `0x9274d30' Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 161 error_code 5 request_code 150 minor_code 15) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... However, when I relaunch gnome-power-manager from the terminal, it asks for a password to run gnome-power-backlight-helper. If I refuse the password, gnome-power-manager does not crash (though it does still emit the proxy-status warning) -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614248] Re: gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8'
** Attachment added: .xsession-errors http://launchpadlibrarian.net/53153418/.xsession-errors ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/53153298/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/53153299/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/53153300/Dependencies.txt ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/53153301/DevkitPower.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/53153302/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/53153303/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/53153304/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/53153305/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/53153306/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/53153307/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/53153308/ProcStatus.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/53153309/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/53153310/UdevLog.txt ** Attachment added: gnome-power-bugreport.txt http://launchpadlibrarian.net/53153311/gnome-power-bugreport.txt -- gnome-power-manager:2651: GLib-GObject-WARNING **: /build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is invalid for instance `0x85b24c8' https://bugs.launchpad.net/bugs/614248 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
