Bug 2170065

Summary: [abrt] rhythmbox: soup_init(): rhythmbox killed by SIGTRAP
Product: [Fedora] Fedora Reporter: funtomasz <tmkfnk>
Component: rhythmboxAssignee: David King <amigadave>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: amigadave, dwmw2, gnome-sig, ingobeh, mclasen, rhughes, rstrode, sandmann, skyfaller, tombouwman, triad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9b7d8d0c99b9c6c27f141c41378c6e864807a8c8
Whiteboard: abrt_hash:53af14467cf3a888929c537cb39f8d8f68ac2a89;VARIANT_ID=xfce;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-16 06:11:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description funtomasz 2023-02-15 15:00:16 UTC 
Description of problem:
Rhythmbox does not start. The rhythmbox -d command in terminal shows the following problem:
libsoup-ERROR **: 15:57:57.521: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.

Version-Release number of selected component:
rhythmbox-3.4.6-2.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        rhythmbox
crash_function: soup_init
executable:     /usr/bin/rhythmbox
journald_cursor: s=ea46e936166d4819a0013c6a7abfed03;i=5f7c13;b=d728e7ae3dd147b8a26dd819c6d24ced;m=9fe2ac2e;t=5f4bdd498e720;x=bb6cbdea8402ca70
kernel:         6.1.11-200.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 funtomasz 2023-02-15 15:00:21 UTC 
Created attachment 1944322 [details]
File: backtrace
Comment 2 funtomasz 2023-02-15 15:00:22 UTC 
Created attachment 1944323 [details]
File: core_backtrace
Comment 3 funtomasz 2023-02-15 15:00:24 UTC 
Created attachment 1944324 [details]
File: cpuinfo
Comment 4 funtomasz 2023-02-15 15:00:25 UTC 
Created attachment 1944325 [details]
File: dso_list
Comment 5 funtomasz 2023-02-15 15:00:26 UTC 
Created attachment 1944326 [details]
File: environ
Comment 6 funtomasz 2023-02-15 15:00:28 UTC 
Created attachment 1944327 [details]
File: limits
Comment 7 funtomasz 2023-02-15 15:00:29 UTC 
Created attachment 1944328 [details]
File: maps
Comment 8 funtomasz 2023-02-15 15:00:30 UTC 
Created attachment 1944329 [details]
File: mountinfo
Comment 9 funtomasz 2023-02-15 15:00:32 UTC 
Created attachment 1944330 [details]
File: open_fds
Comment 10 funtomasz 2023-02-15 15:00:33 UTC 
Created attachment 1944331 [details]
File: proc_pid_status
Comment 11 rday 2023-02-15 22:34:08 UTC 
Similar problem has been detected:

Launched Rhythmbox immediately after boot as a a startup application in the window manager.
It crashed before displaying any window.

reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-rhythmbox-3276.scope
cmdline:        rhythmbox
crash_function: soup_init
executable:     /usr/bin/rhythmbox
journald_cursor: s=d49046101d874252ae5d3751fc0ac150;i=11f2295;b=80f6e73b0992450fbeaa76454535c96a;m=325ea07;t=5f4c368c928ba;x=2f83ab6e49f8cee0
kernel:         6.1.11-200.fc37.x86_64
package:        rhythmbox-3.4.6-2.fc37
reason:         rhythmbox killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 David King 2023-02-16 06:11:22 UTC 

*** This bug has been marked as a duplicate of bug 2169171 ***
Comment 13 Tom Bouwman 2023-02-16 15:37:47 UTC 
*** Bug 2170514 has been marked as a duplicate of this bug. ***
Comment 14 Nelson Pavlosky 2023-02-16 19:54:21 UTC 
*** Bug 2170623 has been marked as a duplicate of this bug. ***
Comment 15 ingo 2023-02-17 13:22:36 UTC 
*** Bug 2170864 has been marked as a duplicate of this bug. ***