Bug#758556: [Pkg-chromium-maint] Bug#758556: killed by SIGABRT
I had same problem. Solved after downgrading all *pango* packages from "1.36.6-1" to "1.36.3-1" gir1.2-pango-1.0:amd64 libpango-1.0-0:amd64 libpango-1.0-0:i386 libpango1.0-0:amd64 libpango1.0-0:i386 libpangocairo-1.0-0:amd64 libpangocairo-1.0-0:i386 libpangoft2-1.0-0:amd64 libpangoft2-1.0-0:i386 Ciao.
Bug#704850: libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable with libpango1.0-0
Hi. I figure out the issue. There was a previous installation of "libpango1.0-0:i386" in rc state that prevent "libpango1.0-0:amd64" to be removed and lock the installation for new version of "libpango1.0-0:all" After "dpkg -P libpango1.0-0:i386" I'm now able to upgrade the package. I think it's dpkg's issue as decribed in #682365 [1] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682365 Regards. Matteo.
Bug#704850: libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable with libpango1.0-0
Package: libpango1.0-0 Version: 1.32.5-3 Severity: grave Justification: renders package unusable Dear Maintainer, libpango1.0-0 1.32.5-3 fails to install. I try to upgrade gnome-shell to 3.8 from experimental. Upgrade of the system hangs during configuration of libpango1.0-0 and renders the system unusable. DpkgTerminalLog: dpkg: error processing /var/cache/apt/archives/libpango1.0-0_1.32.5-3_all.deb (--unpack): libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable with libpango1.0-0 which has multiple installed instances I restored the system using snapshots repository. So I try to upgrade libpango1.0-0 only but I get same error. Maybe the problem is for my machine only? Best regards. Matteo. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (900, 'unstable'), (700, 'testing'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#704834: libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable with libpango1.0-0
Package: libpango1.0-0Version: 1.32.5-3Severity: graveJustification: renders package unusable Dear Maintainer, libpango1.0-0 1.32.5-3 fails to install. I try to upgrade gnome-shell to 3.8 from experimental. Upgrade of the system hangsduring configuration of libpango1.0-0 and renders the system inusable. DpkgTerminalLog:dpkg: error processing /var/cache/apt/archives/libpango1.0-0_1.32.5-3_all.deb (--unpack):libpango1.0-0:all 1.32.5-3 (Multi-Arch: no) is not co-installable with libpango1.0-0 which has multiple installed instances I restored the system using snapshots repository. So I try to upgrade libpango1.0-0 only but I get same error. Maybe it's problem for my machine only? Best regards.Matteo. -- System Information:Debian Release: 7.0 APT prefers unstable APT policy: (900, 'unstable'), (700, 'testing'), (500, 'experimental')Architecture: amd64 (x86_64)Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/8 CPU cores)Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)Shell: /bin/sh linked to /bin/dash
Bug#670927: Aisleriot: Issue with guile
Package: aisleriot Version: 1:3.4.1-1 Severity: important Dear Maintainer, When I start "sol" in terminal I have the follow output and aisleriot doesn't start. *Backtrace:* *In ice-9/boot-9.scm:* * 149: 2 [catch #t # ...]* * 157: 1 [#]* *In unknown file:* * ?: 0 [catch-closure]* * * *ERROR: In procedure catch-closure:* *ERROR: Throw to key `decoding-error' with args `("scm_from_stringn" "input locale conversion error" 22 #vu8(115 111 108))'.* Regards. Matteo. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (700, 'testing'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages aisleriot depends on: ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii gconf-service3.2.5-1 ii gconf2 3.2.5-1 ii guile-2.0-libs 2.0.5+1-3 ii libatk1.0-0 2.4.0-2 ii libc62.13-31 ii libcairo21.12.0-2.1 ii libcanberra-gtk3-0 0.28-4 ii libcanberra0 0.28-4 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.1-1 ii libgtk-3-0 3.4.1-2 ii librsvg2-2 2.36.1-1 aisleriot recommends no packages. Versions of packages aisleriot suggests: pn gnome-cards-data -- no debconf information
Bug#662639: gnome-shell: frequent lockups on hardware accelerated actions
Package: gnome-shellVersion: 3.2.2.1-3Followup-For: Bug #662639 Same issue for me too. The freeze sometime happens when I unplug the AC connector or I reconnect it.Very often it appens when I start "GNOME Onscreen Keyboard". No logs in .xsession-errors about the freeze. The only way is to restart gdm3 service in tty. Regards. -- System Information:Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (700, 'testing'), (500, 'experimental')Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15)Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on:ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3ii gconf-service 3.2.3-4ii gir1.2-accountsservice-1.0 0.6.15-4ii gir1.2-atk-1.0 2.4.0-2ii gir1.2-caribou-1.0 0.4.2-2ii gir1.2-clutter-1.0 1.8.4-1ii gir1.2-cogl-1.0 1.8.2-1ii gir1.2-coglpango-1.0 1.8.2-1ii gir1.2-folks-0.6 0.6.8-2ii gir1.2-freedesktop 1.32.1-1ii gir1.2-gconf-2.0 3.2.3-4ii gir1.2-gdkpixbuf-2.0 2.26.1-1ii gir1.2-gee-1.0 0.6.4-1ii gir1.2-gkbd-3.0 3.4.0.2-1ii gir1.2-glib-2.0 1.32.1-1ii gir1.2-gmenu-3.0 3.2.0.1-2ii gir1.2-gnomebluetooth-1.03.4.0-1ii gir1.2-gtk-3.0 3.4.1-2ii gir1.2-json-1.0 0.14.2-1ii gir1.2-mutter-3.03.2.2-1ii gir1.2-networkmanager-1.00.9.4.0-3ii gir1.2-pango-1.0 1.30.0-1ii gir1.2-polkit-1.0 0.104-2ii gir1.2-soup-2.4 2.38.1-2ii gir1.2-telepathyglib-0.120.18.1-1ii gir1.2-telepathylogger-0.2 0.2.12-1ii gir1.2-upowerglib-1.0 0.9.15-3ii gjs 1.32.0-1ii gnome-bluetooth 3.4.0-1ii gnome-icon-theme-symbolic3.4.0-2ii gnome-settings-daemon 3.2.2-3ii gnome-shell-common 3.2.2.1-3ii gsettings-desktop-schemas3.4.1-2ii libatk1.0-0 2.4.0-2ii libc6 2.13-30ii libcairo-gobject2 1.12.0-2ii libcairo21.12.0-2ii libcamel-1.2-29 3.2.2-3ii libcanberra0 0.28-4ii libclutter-1.0-0 1.8.4-1ii libcogl-pango0 1.8.2-1ii libcogl5 1.8.2-1ii libcroco3 0.6.5-1ii libdbus-1-3 1.5.12-1ii libdbus-glib-1-2 0.98-1ii libdrm2 2.4.33-1ii libebook-1.2-12 3.2.2-3ii libecal-1.2-10 3.2.2-3ii libedataserver-1.2-153.2.2-3ii libedataserverui-3.0-1 3.2.2-3ii libffi5 3.0.10-3ii libfolks25 0.6.8-2ii libfontconfig1 2.9.0-1ii libfreetype6 2.4.9-1ii libgconf-2-4 3.2.3-4ii libgdk-pixbuf2.0-0 2.26.1-1ii libgee2 0.6.4-1ii libgirepository-1.0-1 1.32.1-1ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-1ii libgl1-mesa-glx [libgl1] 8.0-2ii libglib2.0-0 2.32.0-4ii libgnome-desktop-3-2 3.4.1-2ii libgnome-keyring03.4.1-1ii libgnome-menu-3-03.2.0.1-2ii libgstreamer0.10-0 0.10.36-1ii libgtk-3-0 3.4.1-2ii libical0 0.48-1ii libjson-glib-1.0-0 0.14.2-1ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-3ii libmutter0 3.2.2-1ii libnm-glib4 0.9.4.0-3ii libnm-util2 0.9.4.0-3ii libnspr4-0d 4.9-1ii libnss3-1d 3.13.3-1ii libpango1.0-01.30
Bug#665004: xserver-xorg-input-synaptics: scrolling stopped working after upgrade 1.5.0 --> 1.5.99
Same issue for me in Elantech touchpad. Probably the new features "HorizHysteresis" and "VertHysteresis", added with 1.5.99.901-1 version, cause the issue. Setting "VertHysteresis" and "HorizHysteresis" to "0" don't have effects. The scrolling is very unusable. I don't know how investigate more. Best regards.Matteo.
Bug#611100: libgl1-mesa-dri - Xorg segmentation fault on
Very well. Bug resolved with new version of mesa. Thak you for your work. Regards. Matt.
Bug#611100: libgl1-mesa-dri - Xorg segmentation fault on radeon gpu
Hi. Upgrading Xorg (7.6), xserver-xorg (1.9.4) and libgl1-mesa-dri (7.10-2) don't solve the problem. The question is related to "r300_dri.so" file. With 7.10-2 version installed, if I replace file only, by 7.8.2 version one, it's possible start Xserver again. Please ask for more info if you can't reproduce this bug. Regards. Matt.
Bug#552528: alacarte: "segmentation fault" in version 0.12.4-1
Hello! This is the new output: (gdb) run /usr/bin/alacarte Starting program: /usr/bin/python /usr/bin/alacarte [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x764bf7a0 in append_escaped_text (text=0xf1e000 , length=15851520) at /tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c:2040 2040/tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c: No such file or directory. in /tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c (gdb) thread apply all bt full Thread 1 (Thread 0x77fe06f0 (LWP 23993)): #0 0x764bf7a0 in append_escaped_text (text=0xf1e000 , length=15851520) at /tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c:2040 end = 0xd91d5c "" c = #1 IA__g_markup_escape_text (text=0xf1e000 , length=15851520) at /tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c:2117 str = 0xaf73a0 __PRETTY_FUNCTION__ = "IA__g_markup_escape_text" #2 0x74bcc8c1 in gtk_widget_set_property (object=0xd900f0, prop_id=, value=, pspec=0xbb7740) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c:2513 tooltip_markup = tooltip_text = 0xaf73a0 "\020\200\030ìÿ\177" #3 0x76b641c8 in object_set_property (object=0xd900f0, property_name=, value=0xd91c28) at /tmp/buildd/glib2.0-2.22.2/gobject/gobject.c:968 tmp_value = {g_type = 64, data = {{v_int = 14228784, v_uint = 14228784, v_long = 14228784, v_ulong = 14228784, v_int64 = 14228784, v_uint64 = 14228784, v_float = 1.99387732e-38, v_double = 7.0299533564955954e-317, v_pointer = 0xd91d30}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}} param_id = 21 #4 IA__g_object_set_property (object=0xd900f0, property_name=, value=0xd91c28) at /tmp/buildd/glib2.0-2.22.2/gobject/gobject.c:1678 ---Type to continue, or q to quit--- nqueue = pspec = 0xbb7740 __PRETTY_FUNCTION__ = "IA__g_object_set_property" #5 0x74a001f7 in _gtk_builder_construct (builder=0xeecca0, info=0xee0640, error=0x7fffd5d8) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkbuilder.c:481 param = 0xaf73a0 parameters = 0xd8fa40 construct_parameters = 0xd82180 object_type = 10691360 obj = i = 1 iface = 0xe6ab70 custom_set_property = 1 buildable = 0xd900f0 __PRETTY_FUNCTION__ = "_gtk_builder_construct" #6 0x74a01612 in builder_construct (data=0xed8f70, object_info=0xee0640, error=0x7fffd5d8) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkbuilderparser.c:197 object = 0x0 __PRETTY_FUNCTION__ = "builder_construct" #7 0x74a01dc6 in end_element (context=, element_name=0xee1020 "object", user_data=0xed8f70, error=0x7fffd5d8) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkbuilderparser.c:981 object_info = 0xee0640 __PRETTY_FUNCTION__ = "end_element" ---Type to continue, or q to quit--- #8 0x764c2a36 in IA__g_markup_parse_context_parse (context=0xee3df0, text=, text_len=, error=0x7fffd688) at /tmp/buildd/glib2.0-2.22.2/glib/gmarkup.c:1498 tmp_error = 0x0 close_name = 0xaf6b40 __PRETTY_FUNCTION__ = "IA__g_markup_parse_context_parse" #9 0x74a0136f in _gtk_builder_parser_parse_buffer (builder=0xeecca0, filename=0xd0a9e4 "/usr/share/alacarte/alacarte.ui", buffer=0xe4b960 "\n\n\n \n \n \n \n <"..., length=51482, requested_objs=0x0, error=0x7fffd688) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkbuilderparser.c:1162 domain = 0xed9480 "alacarte" l = #10 0x74a00d9f in IA__gtk_builder_add_from_file (builder=0xeecca0, filename=0xd0a9e4 "/usr/share/alacarte/alacarte.ui", error=0x7fffd6d8) at /tmp/buildd/gtk+2.0-2.18.3/gtk/gtkbuilder.c:674 buffer = 0xe4b960 "\n\n\n \n \n \n \n <"... length = 51482 tmp_error = 0x0 __PRETTY_FUNCTION__ = "IA__gtk_builder_add_from_file" #11 0x75047ea9 in ?? () from /usr/lib/pymodules/python2.5/gtk-2.0/gtk/_gtk.so No symbol table info available. #12 0x0048efc5 in PyEval_EvalFrameEx () No symbol table info available. #13 0x0049023c in PyEval_EvalCodeEx () ---Type to continue, or q to quit--- No symbol table info available. #14 0x004d9652 in ?? () No symbol table info available. #15 0x004186a3 in PyObject_Call () No symbol table info available. #16 0x0041f3a4 in ?? () No symbol table info available. #17 0x004186a3 in PyObject_Call () No symbol table info available. #18 0x004893e2 in PyEval_CallObjectWithKeywords () No symbol table info available. #19 0x004220e6 in PyInstance_New () No symbol table info available. #20 0x004186a3 in PyObject_Call () No symbol table info available. #21 0x0048c014 in PyEval_EvalFrameEx () No symbol table info availab
Bug#552528: alacarte: "segmentation fault" in version 0.12.4-1
Hi. This is the output of gdb: (gdb) run /usr/bin/alacarte Starting program: /usr/bin/python /usr/bin/alacarte [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. 0x764bf7a0 in g_markup_escape_text () from /lib/libglib-2.0.so.0 (gdb) thread apply all bt full Thread 1 (Thread 0x77fe06f0 (LWP 15903)): #0 0x764bf7a0 in g_markup_escape_text () from /lib/libglib-2.0.so.0 No symbol table info available. #1 0x74bcc8c1 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #2 0x76b641c8 in g_object_set_property () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #3 0x74a001f7 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #4 0x74a01612 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #5 0x74a01dc6 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #6 0x764c2a36 in g_markup_parse_context_parse () from /lib/libglib-2.0.so.0 No symbol table info available. #7 0x74a0136f in ?? () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #8 0x74a00d9f in gtk_builder_add_from_file () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #9 0x75047ea9 in ?? () from /usr/lib/pymodules/python2.5/gtk-2.0/gtk/_gtk.so No symbol table info available. #10 0x0048efc5 in PyEval_EvalFrameEx () ---Type to continue, or q to quit--- No symbol table info available. #11 0x0049023c in PyEval_EvalCodeEx () No symbol table info available. #12 0x004d9652 in ?? () No symbol table info available. #13 0x004186a3 in PyObject_Call () No symbol table info available. #14 0x0041f3a4 in ?? () No symbol table info available. #15 0x004186a3 in PyObject_Call () No symbol table info available. #16 0x004893e2 in PyEval_CallObjectWithKeywords () No symbol table info available. #17 0x004220e6 in PyInstance_New () No symbol table info available. #18 0x004186a3 in PyObject_Call () No symbol table info available. #19 0x0048c014 in PyEval_EvalFrameEx () No symbol table info available. #20 0x0048fa60 in PyEval_EvalFrameEx () No symbol table info available. #21 0x0049023c in PyEval_EvalCodeEx () No symbol table info available. ---Type to continue, or q to quit--- #22 0x00490432 in PyEval_EvalCode () No symbol table info available. #23 0x004af628 in PyRun_FileExFlags () No symbol table info available. #24 0x004af8cb in PyRun_SimpleFileExFlags () No symbol table info available. #25 0x00414572 in Py_Main () No symbol table info available. #26 0x77207a8d in __libc_start_main () from /lib/libc.so.6 No symbol table info available. #27 0x004139d9 in _start () No symbol table info available. Regards. Matteo Aquilano. > Subject: Re: Bug#552528: alacarte: "segmentation fault" in version 0.12.4-1 > From: j...@debian.org > To: matteo_aquil...@hotmail.com; 552...@bugs.debian.org > Date: Tue, 3 Nov 2009 13:09:55 +0100 > > forcemerge 552528 552536 > thanks > > Sorry but strace is not a general-purpose debugging tool. Please avoid > sending such huge and unusable traces. > > To debug such crashes when they are not reproducible (which is the case > here), we need a GDB backtrace: > * Run "gdb /usr/bin/python" > * At the gdb prompt, type "run /usr/bin/alacarte" > * When it crashes, type "thread apply all bt full" and send us the > output of this command. > > Please see http://wiki.debian.org/HowToGetABacktrace for more details. > > Cheers, > -- > .''`. Josselin Mouette > : :' : > `. `' “I recommend you to learn English in hope that you in > `- future understand things” -- Jörg Schilling _ Messenger su ogni PC, prova la Web Bar! http://www.messenger.it/
Bug#552536: alacarte: "segmentation fault" in version 0.12.4-1
Subject: alacarte: "segmentation fault" in version 0.12.4-1 Package: alacarte Version: 0.12.4-1 Severity: normal Hi. After upgrade to 0.12.4-1 in Unstable alacarte fails to start with "segmentation fault". Same problem in my other PC with debian testing. The bug is not reproducible if downgrade the package to 0.12.1-1 . I attached the strace. Regards. Matteo Aquilano. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/1 CPU core) Locale: lang=it...@euro, lc_ctype=it...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages alacarte depends on: ii gnome-menus 2.28.0-1 an implementation of the freedeskt ii python2.5.4-2An interactive high-level object-o ii python-gmenu 2.28.0-1 an implementation of the freedeskt ii python-gobject2.20.0-1 Python bindings for the GObject li ii python-gtk2 2.16.0-1 Python bindings for the GTK+ widge ii python-support1.0.4 automated rebuilding support for P Versions of packages alacarte recommends: ii gnome-panel 2.28.0-2 launcher and docking facility for alacarte suggests no packages. -- no debconf information _ Nuovo Windows 7: per semplificare le attività di tutti i giorni. Trova il PC più adatto alle tue esigenze. http://windows.microsoft.com/shop
Bug#552506: gnome-power-manager: "xset dpms force off" don't keep display off
Subject: gnome-power-manager: "xset dpms force off" don't keep display off Package: gnome-power-manager Version: 2.28.1-2 Severity: normal Hi. After upgrade to 2.28.1-2 in SID, "xset dpms force off" shut down the display for few seconds then the display is resumed even if PC is idle. If i kill the "gnome-power-manager" process, I don't have problems and the display is off until a key press or move touchpad. If "gnome-power-manager" process is active, the display don't stay off. I kill gnome-power-manager first. Start 'gnome-power-manager --verbose', then 'xset dpms force off'. The output is in the attachment. Regards. Matteo Aquilano. -- Package-specific info: Distro version: squeeze/sid Kernel version: 2.6.31-1-amd64 g-p-m version:2.28.1 HAL version: 0.5.13 System manufacturer: missing System version: missing System product: missing AC adapter present: yes Battery present: yes Laptop panel present: yes CPU scaling present: yes Battery Information: battery.charge_level.current = 71280 (0x11670) (int) battery.charge_level.design = 71280 (0x11670) (int) battery.charge_level.last_full = 71280 (0x11670) (int) battery.charge_level.percentage = 100 (0x64) (int) battery.charge_level.rate = 0 (0x0) (int) battery.is_rechargeable = true (bool) battery.model = 'Primary' (string) battery.present = true (bool) battery.rechargeable.is_charging = false (bool) battery.rechargeable.is_discharging = false (bool) battery.reporting.current = 6600 (0x19c8) (int) battery.reporting.design = 6600 (0x19c8) (int) battery.reporting.last_full = 6600 (0x19c8) (int) battery.reporting.rate = 0 (0x0) (int) battery.reporting.technology = 'Li-ion' (string) battery.reporting.unit = 'mAh' (string) battery.serial = '' (string) battery.technology = 'lithium-ion' (string) battery.type = 'primary' (string) battery.vendor = 'Hewlett-Packard' (string) battery.voltage.current = 10800 (0x2a30) (int) battery.voltage.design = 10800 (0x2a30) (int) battery.voltage.unit = 'mV' (string) DeviceKit data: Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT1 native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0c/PNP0C0A:00/power_supply/BAT1 vendor: Hewlett-Packard model:Primary power supply: yes updated: Mon Oct 26 23:13:24 2009 (1066 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged energy: 71.28 Wh energy-empty:0 Wh energy-full: 71.28 Wh energy-full-design: 71.28 Wh energy-rate: 0 W voltage: 10.8 V percentage: 100% capacity:100% technology: lithium-ion Device: /org/freedesktop/DeviceKit/Power/devices/line_power_ACAD native-path: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:0c/ACPI0003:00/power_supply/ACAD power supply: yes updated: Mon Oct 26 23:13:19 2009 (1071 seconds ago) has history: no has statistics: no line-power online: yes Daemon: daemon-version: 012 can-suspend: yes can-hibernateyes on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes GNOME Power Manager Process Information: matt 4557 0.0 0.3 153908 7812 pts/1S23:23 0:00 \_ gnome-power-manager matt 5000 0.0 0.0 3884 576 pts/0R+ 23:31 0:00 \_ /bin/sh /usr/share/gnome-power-manager/gnome-power- HAL Process Information: 107 1356 0.0 0.2 38448 5044 ?Ss 22:10 0:01 /usr/sbin/hald root 1422 0.0 0.0 19920 1364 ?S22:10 0:00 \_ hald-runner root 1468 0.0 0.0 22032 1344 ?S22:10 0:00 \_ /usr/lib/hal/hald-addon-rfkill-killswitch root 1480 0.0 0.0 22032 1252 ?S22:10 0:00 \_ /usr/lib/hal/hald-addon-generic-backlight root 1493 0.0 0.0 22040 1244 ?S22:10 0:00 \_ hald-addon-input: Listening on /dev/input/event6 /dev/input root 1511 0.0 0.0 22040 1240 ?S22:10 0:01 \_ hald-addon-storage: polling /dev/hdc (every 2 sec) root 1513 0.0 0.0 22048 1208 ?S22:10 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 107 1514 0.0 0.0 25932 1252 ?S22:10 0:00 \_ hald-addon-acpi: listening on acpid socket /var/run/acpid.s root 2565 0.0 0.0 22032 1212 ?S22:27 0:00 \_ /usr/lib/hal/hald-addon-leds -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990,