Bug 13703 - draksnapshot-config crashed
Summary: draksnapshot-config crashed
Status: RESOLVED DUPLICATE of bug 11395
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: NEEDINFO
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-08 09:27 CEST by Andrea Beducci
Modified: 2014-07-09 16:54 CEST (History)
1 user (show)

See Also:
Source RPM: draksnapshot-0.20.3-7.mga4
CVE:
Status comment:

Attachments
lspci output (4.38 KB, text/plain)
2014-07-08 09:27 CEST, Andrea Beducci 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Andrea Beducci 2014-07-08 09:27:23 CEST 
Created attachment 5270 [details]
lspci output

The "draksnapshot-config" program crashed. Drakbug-16.26.11 caught it.

The notebook instead of hibernate has shut down.

Theme name: oxygen-gtk
Kernel version = 3.12.21-desktop-2.mga4
Distribution=Mageia release 4 (Official) for x86_64
CPU=Intel(R) Core(TM)2 Duo CPU     L9600  @ 2.13GHz
Comment 1 Marja Van Waes 2014-07-09 16:49:13 CEST 
Didn't you see anything like:

"you must be root to run this program at /usr/lib/libDrakX/common.pm line 387.
Perl's trace:
standalone::bug_handler() called from /usr/lib/libDrakX/common.pm:387
common::require_root_capability() called from /usr/sbin/draksnapshot-config:39"

If that is what you saw in the drakbug screen, then this is a duplicate of 
bug 11395

If you saw another trace or remark + trace, please paste them in a comment in this report.

CC: (none) => marja11
Whiteboard: (none) => NEEDINFO

Comment 2 Marja Van Waes 2014-07-09 16:53:59 CEST 
Ah, you did, you reported bug 113711, too :-)

So also closing this one as duplicate, feel free to reopen if I misinterpret and you had a different trace on this occasion.

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 3 Marja Van Waes 2014-07-09 16:54:40 CEST 
(In reply to Marja van Waes from comment #2)
> Ah, you did, you reported bug 113711, too :-)
s/113711/13711/
Note You need to log in before you can comment on or make changes to this bug.