Fedora Account System
Red Hat Associate
Red Hat Customer
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
Created attachment 1944322 [details] File: backtrace
Created attachment 1944323 [details] File: core_backtrace
Created attachment 1944324 [details] File: cpuinfo
Created attachment 1944325 [details] File: dso_list
Created attachment 1944326 [details] File: environ
Created attachment 1944327 [details] File: limits
Created attachment 1944328 [details] File: maps
Created attachment 1944329 [details] File: mountinfo
Created attachment 1944330 [details] File: open_fds
Created attachment 1944331 [details] File: proc_pid_status
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
*** This bug has been marked as a duplicate of bug 2169171 ***
*** Bug 2170514 has been marked as a duplicate of this bug. ***
*** Bug 2170623 has been marked as a duplicate of this bug. ***
*** Bug 2170864 has been marked as a duplicate of this bug. ***