Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 566338 - media-gfx/gnome-screenshot -w segmentation fault on fluxbox
Summary: media-gfx/gnome-screenshot -w segmentation fault on fluxbox
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-20 15:05 UTC by lolisamurai
Modified: 2021-01-10 01:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
gnome-screenshot-backtrace.log (gnome-screenshot-backtrace.log,847 bytes, text/x-log)
2015-12-26 15:27 UTC, lolisamurai
Details
gnome-screenshot-backtrace.log (gnome-screenshot-backtrace.log,3.09 KB, text/x-log)
2015-12-26 16:28 UTC, lolisamurai
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lolisamurai 2015-11-20 15:05:40 UTC
Steps to reproduce:
- Set up Xorg and fluxbox
- emerge media-gfx/gnome-screenshot

$ gnome-screenshot -w
** Message: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11.
Segmentation fault

-a and other modes work fine, it's just -w that crashes
Comment 1 Pacho Ramos gentoo-dev 2015-12-12 14:40:58 UTC
3.18.0 version looks to work ok for me
Comment 2 lolisamurai 2015-12-12 16:04:50 UTC
my bad, I didn't even specify what version I was using. I was on gnome-screenshot 3.16.2.
anyhow, I just emerged 3.18.0 and it still has the same issue. I don't know if this is related to the issue, but I'm running dual monitors with xinerama.
Comment 3 Gilles Dartiguelongue (RETIRED) gentoo-dev 2015-12-13 12:18:57 UTC
Running dual monitor with xinerama here too, on intel chipset, and it just work.
Could you add your emerge --info ? Also, collecting a backtrace would be useful for moving the issue upstream if needs be. You can find instructions on how to do it on the wiki: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
Comment 4 lolisamurai 2015-12-14 19:19:19 UTC
emerge --info: http://pastebin.com/N3z3Uya1

backtrace:
$ gdb -q gnome-screenshot
Reading symbols from gnome-screenshot...Reading symbols from /usr/lib64/debug//usr/bin/gnome-screenshot.debug...done.
done.
(gdb) set args -w
(gdb) run
Starting program: /usr/bin/gnome-screenshot -w
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
** Message: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11.
[New Thread 0x7fffed44a700 (LWP 29861)]

Program received signal SIGSEGV, Segmentation fault.
screenshot_fallback_get_pixbuf (rectangle=<optimized out>)
    at screenshot-utils.c:508
508	screenshot-utils.c: No such file or directory.
Comment 5 Pacho Ramos gentoo-dev 2015-12-26 15:17:48 UTC
(bleh, wrong tab)
Comment 6 Pacho Ramos gentoo-dev 2015-12-26 15:19:56 UTC
(In reply to lolisamurai from comment #4)
> emerge --info: http://pastebin.com/N3z3Uya1
> 
> backtrace:
> $ gdb -q gnome-screenshot
> Reading symbols from gnome-screenshot...Reading symbols from
> /usr/lib64/debug//usr/bin/gnome-screenshot.debug...done.
> done.
> (gdb) set args -w
> (gdb) run
> Starting program: /usr/bin/gnome-screenshot -w
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> ** Message: Unable to use GNOME Shell's builtin screenshot interface,
> resorting to fallback X11.
> [New Thread 0x7fffed44a700 (LWP 29861)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> screenshot_fallback_get_pixbuf (rectangle=<optimized out>)
>     at screenshot-utils.c:508
> 508	screenshot-utils.c: No such file or directory.

Please follow the instructions from "Using logging feature to save the backtrace to file" when following https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces

There are more detailed instructions in:
https://wiki.gentoo.org/wiki/Project:GNOME/GNOME3-Troubleshooting#Getting_backtraces
Comment 7 Pacho Ramos gentoo-dev 2015-12-26 15:21:06 UTC
(In reply to lolisamurai from comment #4)
> emerge --info: http://pastebin.com/N3z3Uya1
> 
> backtrace:
> $ gdb -q gnome-screenshot
> Reading symbols from gnome-screenshot...Reading symbols from
> /usr/lib64/debug//usr/bin/gnome-screenshot.debug...done.
> done.
> (gdb) set args -w
> (gdb) run
> Starting program: /usr/bin/gnome-screenshot -w
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> ** Message: Unable to use GNOME Shell's builtin screenshot interface,
> resorting to fallback X11.
> [New Thread 0x7fffed44a700 (LWP 29861)]
> 
> Program received signal SIGSEGV, Segmentation fault.
> screenshot_fallback_get_pixbuf (rectangle=<optimized out>)
>     at screenshot-utils.c:508
> 508	screenshot-utils.c: No such file or directory.

Please follow the instructions from "Using logging feature to save the backtrace to file" when following https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces

There are more detailed instructions in:
https://wiki.gentoo.org/wiki/Project:GNOME/GNOME3-Troubleshooting#Getting_backtraces
Comment 8 lolisamurai 2015-12-26 15:27:49 UTC
Created attachment 420884 [details]
gnome-screenshot-backtrace.log

erm, is this okay?
Comment 9 Pacho Ramos gentoo-dev 2015-12-26 15:31:36 UTC
The line with "??" shows that you need to rebuild the package providing that lib with debugging symbols too, in this case, glib ;)
Comment 10 lolisamurai 2015-12-26 16:28:17 UTC
Created attachment 420888 [details]
gnome-screenshot-backtrace.log

there we go
Comment 11 Pacho Ramos gentoo-dev 2016-07-02 15:21:00 UTC
please retry with 3.20