Bug 362822

Summary: KStars receives segfault in libqcxb when I close my laptop lid
Product: [Applications] kstars Reporter: Rob <kstars>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Rob 2016-05-08 17:07:10 UTC
I'm using KStars bleeding (help says Version 2.6.0), updated today, and I've found that KStars now crashes when I close the lid of my laptop, see journal output below.  I've been doing various installations/removals so it's possible I've messed something up, but KStars wasn't doing this yesterday:

May 08 17:55:21 rob-Latitude-D830 systemd-logind[610]: Lid closed.
May 08 17:55:21 rob-Latitude-D830 cpufreqd[676]: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/energy_full (No such file or directory)
May 08 17:55:21 rob-Latitude-D830 cpufreqd[676]: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/energy_now (No such file or directory)
May 08 17:55:21 rob-Latitude-D830 cpufreqd[676]: get_class_device_attribute: couldn't open /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/power_now (No such file or directory)
May 08 17:55:22 rob-Latitude-D830 kernel: show_signal_msg: 30 callbacks suppressed
May 08 17:55:22 rob-Latitude-D830 kernel: kstars[1731]: segfault at 20 ip 00007f8a517e0e3b sp 00007ffdb0796908 error 4 in libqxcb.so[7f8a517b2000+b5000]
May 08 17:55:26 rob-Latitude-D830 systemd-logind[610]: Lid opened.

Any idea what I might have done to cause this?

Rob

Reproducible: Always

Steps to Reproduce:
1. Start KStars
2. Close laptop lid


Expected Results:  
KStars to remain unaffected.
Comment 1 Jasem Mutlaq 2016-05-08 19:18:32 UTC

*** This bug has been marked as a duplicate of bug 343674 ***
Comment 2 Rob 2016-05-08 19:38:24 UTC
Thanks Jasem. For now I've set IgnoreLid=true in /etc/UPower/Upower.conf and that's a sufficient workaround for me.