eopkg history gives you a number. Choose the number before the last update. I did this once years ago so check again in eopkg help.( -t [--takeback] arg : Takeback to the state after the given operation
finished)
something like sudo eopkg -t yournumberhere. I hope.
oh yeah. one person yesterday tried to rollback to fix an app and it sure got fixed but two more broke because of a deprecated package in last update. so it may be best to wait out the r-box thing
Added this to the GNOME 43 issues task. Rhythmbox uses libsoup 2, but likely one of the packages it depends on now uses libsoup 3, causing the conflict. Hopefully something simple... Thanks for the report!
samteezy Rhythmbox works for me
system:
Host: solus Kernel: 5.15.68-218.current arch: x86_64 bits: 64
Desktop: Budgie v: 10.6.4 Distro: Solus 4.3 fortitude
Libraries libsoup:
eopkg li | grep libsoup
libsoup - GNOME HTTP client/server library
libsoup3 - GNOME HTTP client/server library
Show yours libsoup.
no problem here also.
pomon I'd forgotten about this thread. Still having the issue. Output of mine:
eopkg li | grep libsoup
libsoup - GNOME HTTP client/server library
libsoup-32bit - 32-bit libraries for libsoup
libsoup3 - GNOME HTTP client/server library
libsoup3-32bit - 32-bit libraries for libsoup3
Wonder what would happen if I remove those 32 bit libs?
Same for me with just 2 libsoup
eopkg li | grep libsoup
libsoup - GNOME HTTP client/server library
libsoup3 - GNOME HTTP client/server libraryRhythmbox works again for you ?
2 months ago I said it launched in Budgie. Now it launches in Mate. Beach ball spins a few seconds, but it launched.
Lucky man, mine is always out of service. 
** (rhythmbox:119333): WARNING **: 19:23:21.547: Could not open device /dev/radio0
(rhythmbox:119333): libsoup-ERROR **: 19:23:21.749: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
Trappe pour point d'arrêt et de trace (core dumped)$ rhythmbox
(rhythmbox:5004): GdkPixbuf-CRITICAL **: 11:41:08.767: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(rhythmbox:5004): GdkPixbuf-CRITICAL **: 11:41:08.785: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(rhythmbox:5004): GdkPixbuf-CRITICAL **: 11:41:08.797: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.015: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type b, target type NULL)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.015: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type b, target type NULL)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.089: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.090: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.090: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.145: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.145: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)
(rhythmbox:5004): Gtk-WARNING **: 11:41:09.145: Negative content width -9 (allocation 4, extents 6x7) while allocating gadget (node button, owner GtkButton)terminal launched fine and output looks normal.
As for yours: "Could not open device /dev/radio0" I don't get that at all. RB is being seen as a volume?
"libsoup-ERROR **: 19:23:21.749: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported." ---that could be just what it says. Maybe you brought in one of the libsoups with some build you did or some outside app? smells like a conflict but I'm not a pro.
eopkg info libsoup will tell you what its dependencies are
You're surely right, a conflict is very possible. eopkg info libsoup indicates a lot of Reverse Dependencies :
Reverse Dependencies: appstream-glib font-manager rhythmbox libchamplain
inkscape gradio libgeocode-glib librest-07 dleyna-server
libwebkit-gtk geoclue libgdata python-nbxmpp homebank
shotwell ostree seahorse gfbgraph gthumb cawbird
budgie-screenshot-applet budgie-weathershow-applet
Reverse Dependencies: flatpak-builder astroid shotwell libgeocode-glib geoclue
darktable seahorse gamehub budgie-screenshot-applet
font-manager ostree librest-07 appstream-glib gjitenkai
gthumb cawbird playmyvideos rhythmbox libtimezonemap
budgie-weathershow-applet libchamplain snapd-glib liferea
vocal gnome-recipes rygel uhttpmock gst-plugins-good
libsoup-32bit libmateweather libgda libsoup-dbginfo
gradio gfbgraph ibus-libpinyin inkscape
budgie-haste-applet geany-plugins libsoup-devel
dleyna-server libwebkit-gtk libgdata bookworm remmina
homebank python-nbxmpp coffee osinfo-db-tools osm-gps-map^^ deleted everything I had to say. you have 2 lists of reverse deps. I thought you were showing the standard output: dependencies then reverse dep. Negated my point, so hence the axe edit.
This issue is listed on the dev tracker here. As yet, no-one has done anything about it. :/
EbonJaeger that explains the libsoup version conflict in his initial output:
"rhythmbox: libsoup version mismatch causes it to segfault on open. Rhythmbox uses libsoup 2, but grilo (a dependency of Rhythmbox) uses libsoup 3."
OK, found, for me it's rhythmbox-alternative-toolbar the responsible. Without it, rhythmbox runs.
Oh yes, it works with a reinstall of rhythmbox-alternative-toolbar ! 
