! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Program terminated with signal SIGSEGV on battery empty
Status:
RESOLVED: MOVED
Priority:
Very Low
Severity:
trivial
Product:
Xfce4-power-manager
Component:
General

Comments

Description jentaia 2018-07-17 11:58:07 CEST
Output in System Reports
================
(from German "Systemberichte")

===================================================================
 GDB Log                                                           
===================================================================

warning: core file may not match specified executable file.
[New LWP 2486]
[New LWP 2709]
[New LWP 2708]
Core was generated by `xfce4-power-manager'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fd08c4e9746 in ?? ()
[Current thread is 1 (LWP 2486)]

===================================================================
 GDB Backtrace                                                     
===================================================================

warning: core file may not match specified executable file.
[New LWP 2486]
[New LWP 2709]
[New LWP 2708]
Core was generated by `xfce4-power-manager'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fd08c4e9746 in ?? ()
[Current thread is 1 (LWP 2486)]
#0  0x00007fd08c4e9746 in ?? ()
#1  0x000055615075d028 in ?? ()
#2  0x0000000000000002 in ?? ()
#3  0x000055615075c887 in ?? ()
#4  0x0000000000000000 in ?? ()

===================================================================
 GDB Backtrace (all threads)                                       
===================================================================

warning: core file may not match specified executable file.
[New LWP 2486]
[New LWP 2709]
[New LWP 2708]
Core was generated by `xfce4-power-manager'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fd08c4e9746 in ?? ()
[Current thread is 1 (LWP 2486)]

Thread 3 (LWP 2708):
#0  0x00007fd08c55974d in ?? ()
No symbol table info available.
#1  0x0000000000000000 in ?? ()
No symbol table info available.

Thread 2 (LWP 2709):
#0  0x00007fd08c55974d in ?? ()
No symbol table info available.
#1  0x0000000000000000 in ?? ()
No symbol table info available.

Thread 1 (LWP 2486):
#0  0x00007fd08c4e9746 in ?? ()
No symbol table info available.
#1  0x000055615075d028 in ?? ()
No symbol table info available.
#2  0x0000000000000002 in ?? ()
No symbol table info available.
#3  0x000055615075c887 in ?? ()
No symbol table info available.
#4  0x0000000000000000 in ?? ()
No symbol table info available.
#0  0x00007fd08c4e9746 in ?? ()
#1  0x000055615075d028 in ?? ()
#2  0x0000000000000002 in ?? ()
#3  0x000055615075c887 in ?? ()
#4  0x0000000000000000 in ?? ()


What I noticed
=========

I recently switched from Linux Mint Xenial to Linux Mint Bionic. Since then my Acer Extensa 2509 notebook wouldn't hibernate. Even s2disk didn't function anymore. It would prepare for hibernation and than just "hang", the fan would regularly go high and down again about every 20 or 30 seconds. I just gave up on hibernation.

I was just looking through my system reports - whatever they try to tell me - and found similar issues with other Linux applications but none with the power manager.
I think the time I got this message was when I had to put away the notebook and I don't think I had time to shut it down.

Linux doesn't do anything that I set in the power manager. So I don't think it did shutdown when the battery was empty. So it just "crashed" as everything else did when the battery was empty.
I don't know if there's any sort of gui power manager that really does what I want it to on Linux Mint. For now, it can only show the battery level.

It's nothing I can't live with. So I made it trivial with very low priority. I just thought that my "Systemberichte" wanted me to report it and so I did.
Comment 1 Git Bot editbugs 2020-05-27 01:42:51 CEST
-- GitLab Migration Automatic Message --

This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/xfce4-power-manager/-/issues/38.

Please create an account or use an existing account on one of our supported OAuth providers. 

If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests

Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev

Bug #14541

Reported by:
jentaia
Reported on: 2018-07-17
Last modified on: 2020-05-27

People

Assignee:
Ali Abdallah
CC List:
3 users

Version

Attachments

Additional information