Description of problem: i connected my samsung a50 by usbc cable and opened the foto app. then i clicked on "import fotos" and i got 3 errors in ABRT: 1 unreportable (kernel) 1 brakes off at the beginning of this workflow here. Unerwarteter Systemfehler Das System ist auf einen Fehler gestoßen und hat sich selber wieder hergestellt. kernel-core 6.1.18-200.fc37.x86_64 got now 4 of those in the last 4 days, that's one kernel oops per day in average, which seems a lot and i can't report them :'-( Also if i unplug the charging cable, external Bluetooth keybord and USB (wireless) Mouse stopp working, AND I HAVE TO REBOOT i am sitting on this issues even without my 3 different USB-C Docking stations connected (kexternal media writers and HDD's mainly connected over those (from Dell and HP, my Läptop is Lenovo) with docks connected it get'S worse. what can i do to be able to report the kernel stuff ? kindest regards, Markus Version-Release number of selected component: gnome-photos-43.0-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user/app.slice/dbus-:1.2-org.gnome.Photos cmdline: /usr/bin/gnome-photos --gapplication-service crash_function: fast_validate executable: /usr/bin/gnome-photos journald_cursor: s=16d5f75eb6224d7ebf9b16f39d130228;i=5dd70;b=4dfcb9c0d9c24eeabf89c77929816d7e;m=1bc8b6a0;t=5f7036ccaddfb;x=adf35284c90af766 kernel: 6.1.18-200.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 fast_validate at ../glib/gutf8.c:1516 #1 g_utf8_validate at ../glib/gutf8.c:1699 #3 g_variant_new_string at ../glib/gvariant.c:1270 #4 g_variant_new_strv at ../glib/gvariant.c:1577 #5 g_variant_valist_new_nnp at ../glib/gvariant.c:4893 #6 g_variant_valist_new_leaf at ../glib/gvariant.c:5065 #7 g_variant_valist_new at ../glib/gvariant.c:5299 #8 g_variant_new_va at ../glib/gvariant.c:5475 #9 g_variant_new at ../glib/gvariant.c:5410 #10 tracker_miner_files_index_call_index_location at src/photos-tracker-miner-files-index.c:348 Potential duplicate: bug 1995557
Created attachment 1951235 [details] File: backtrace
Created attachment 1951236 [details] File: core_backtrace
Created attachment 1951237 [details] File: cpuinfo
Created attachment 1951238 [details] File: dso_list
Created attachment 1951239 [details] File: environ
Created attachment 1951240 [details] File: exploitable
Created attachment 1951242 [details] File: limits
Created attachment 1951243 [details] File: maps
Created attachment 1951244 [details] File: mountinfo
Created attachment 1951245 [details] File: open_fds
Created attachment 1951246 [details] File: proc_pid_status
*** Bug 2180646 has been marked as a duplicate of this bug. ***
*** Bug 2224562 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.