Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1022082] SEGV (11) on /usr/bin/file-roller
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 26 Jan 2017 14:43:29 +0000
  • Message-id: <>

--- Comment #1 from Mikhail Kasimov <mikhail.kasimov@xxxxxxxxx> ---
k_mikhail@linux-mk500:~> coredumpctl gdb file-roller PID: 11561
UID: 1000 (k_mikhail)
GID: 100 (users)
Signal: 11 (SEGV)
Timestamp: Чтв 2017-01-26 15:56:43 EET (45min ago)
Command Line: file-roller --force --extract-to=/home/k_mikhail/111
Executable: /usr/bin/file-roller
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (k_mikhail)
Boot ID: 4d44c27febf348c294643906f326d245
Machine ID: 4664bc7cba6aee90fe1efc7f571cbf28
Hostname: linux-mk500
Message: Process 11561 (file-roller) of user 1000 dumped core.

GNU gdb (GDB; openSUSE Leap 42.2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/file-roller...(no debugging symbols
[New LWP 11561]
[New LWP 11563]
[New LWP 11564]
[New LWP 11565]
[New LWP 11566]
[New LWP 11569]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/".
Core was generated by `file-roller --force --extract-to=/home/k_mikhail/111
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000449d55 in ?? ()
[Current thread is 1 (Thread 0x7fc19e40f9c0 (LWP 11561))]
Missing separate debuginfos, use: zypper install

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >