Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 603140 - media-video/kaffeine-2.0.5 segfaults
Summary: media-video/kaffeine-2.0.5 segfaults
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Media-video project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-19 20:06 UTC by Jan-Erik Skata
Modified: 2017-01-03 09:43 UTC (History)
1 user (show)

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

Attachments
Strace of starting Kaffeine as normal user (strace.tar.gz,146.77 KB, application/x-gzip)
2016-12-26 16:43 UTC, Jan-Erik Skata 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Erik Skata 2016-12-19 20:06:39 UTC 
18.12 updated ~amd64 system, previous update 11.12.
Updates included Qt and Plasma framework.

Now Kaffeine segfaults when attempting to start as normal user. Starting with sudo works.

$ kaffeine
18-12-16 19:12:41.787 [Info    ] Using built-in dvb device manager
18-12-16 19:12:42.110 [Info    ] Found dvb device P1131714613c21010: ST STV0297 DVB-C
Segmentation fault 


This is all dmesg says:
[   21.490740] dvb_ca adapter 0: DVB CAM detected and initialised successfully
[   38.117709] kaffeine[5606]: segfault at 0 ip           (null) sp 00007ffdc8ddd8b8 error 14 in kaffeine[400000+122000]

Tried re-emerging Kaffeine, rebooted, still does the same.
Comment 1 Michael Palimaka (kensington) gentoo-dev 2016-12-22 14:26:27 UTC 
Could you try to get a backtrace please?
Comment 2 Jan-Erik Skata 2016-12-26 16:43:56 UTC 
Created attachment 457444 [details]
Strace of starting Kaffeine as normal user
Comment 3 Jan-Erik Skata 2017-01-02 22:04:29 UTC 
Problem seems to be resolved after last weeks updates.
Comment 4 Johannes Huber (RETIRED) gentoo-dev 2017-01-03 09:43:36 UTC 
(In reply to Jan-Erik Skata from comment #3)
> Problem seems to be resolved after last weeks updates.

Thanks. Looks like a missing rebuild.