After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477927 - crash in Battery Charge Monitor: Attempting to connect vi...
crash in Battery Charge Monitor: Attempting to connect vi...
Status: RESOLVED DUPLICATE of bug 446097
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-18 01:45 UTC by morgan.weetman
Modified: 2007-10-06 09:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description morgan.weetman 2007-09-18 01:45:12 UTC 
What were you doing when the application crashed?
Attempting to connect via ssh to this host


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 25235456 vsize: 25235456 resident: 10162176 share: 8212480 rss: 10162176 rss_rlim: 4294967295
CPU usage: start_time: 1190079245 rtime: 6 utime: 5 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/battstat-applet-2'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208604048 (LWP 32708)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163664

Thread 1 (Thread -1208604048 (LWP 32708))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 ??
    from /lib/libdbus-1.so.3
  • #8 ??
    from /lib/libdbus-1.so.3
  • #9 dbus_move_error
    from /lib/libdbus-1.so.3
  • #10 libhal_device_property_exists
    from /usr/lib/libhal.so.1
  • #11 ??
  • #12 ??
    from /usr/lib/libhal.so.1
  • #13 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #14 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #21 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #22 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #23 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (688238 sec old) ---------------------
localuser:mweetman being added to access control list
SESSION_MANAGER=local/rogue.corp1.local:/tmp/.ICE-unix/2896
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
Loading "installonlyn" plugin
(gnome-terminal:3368): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Comment 1 morgan.weetman 2007-09-18 14:06:58 UTC 
This bug seems to have some relationship with the ThinkFinger package and modifications to pam configuration, I had the following config in /etc/pam.d/system.auth -

auth        required      pam_env.so
auth        sufficient    pam_thinkfinger.so
auth        sufficient    pam_unix.so nullok_secure try_first_pass
auth        requisite     pam_succeed_if.so uid >= 500 quiet
auth        required      pam_deny.so

which prevented login via ssh ( not sure if it is correct ). The login attempt directly correlates with the battery monitor app crash, I have commented out the thinkfinger line at present to work around this.
Comment 2 Susana 2007-10-06 09:44:43 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 446097 ***