| Summary: | [abrt] xfce4-power-manager-1.0.10-3.fc17: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christoph Wickert <cwickert> | ||||||||||
| Component: | xfce4-power-manager | Assignee: | Christoph Wickert <cwickert> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | cwickert, martin.nyhus, maxamillion, mrunge, z117 | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:2bb71a58f8e3b63d1253268873dd7077e3b63bed | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-06-04 07:59:03 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Christoph Wickert
2012-03-25 10:07:25 UTC
Created attachment 572503 [details]
File: dso_list
Created attachment 572504 [details]
File: coredump
Created attachment 572505 [details]
File: maps
Created attachment 572506 [details]
File: backtrace
*** Bug 805528 has been marked as a duplicate of this bug. *** *** Bug 751121 has been marked as a duplicate of this bug. *** Haven't seen this for a longer time now. Bug can be closed, right? I think so. I was the one who filed the bug and I haven't seen it ever again. And it seems it was not even caused by xfce4-power-manager because the bug disappeared without an update. Still have it on each suspend/resume cycle and power cord unplug. Looks like it is locale-dependent. Always got it with LANG=ru_RU.utf8, and no crash with LANG=C. I've traced it down to
(gdb)
xfpm_battery_get_message_from_battery_state (battery=0x80c5800)
at xfpm-battery.c:242
242 msg = g_strdup_printf (_("%s (%i%%)\nEstimated time left is %s."), tmp, battery->priv->percentage, est_time_str);
(gdb) print tmp
$3 = (gchar *)
0x8116c00 "Система работает от: батарея "
(gdb) print est_time_string
No symbol "est_time_string" in current context.
(gdb) print est_time_str
$4 = (gchar *) 0x8140ec0 "3 часа 1 минута"
(gdb) n
Program received signal SIGSEGV, Segmentation fault.
0x4b96aa6c in _IO_vfprintf_internal (s=s@entry=0xbfffecc0,
format=<optimized out>, format@entry=
0xb7ca2ad1 "%s\nУстройство (%s) разряжается (%i%%)\nОставшееся время работы около %s.", ap=
0xbfffee0c "\300\016\024\b\370\267\006\b", ap@entry=0xbfffee04 "")
at vfprintf.c:1570
1570 process_string_arg (((struct printf_spec *) NULL));
(gdb) q
|