https://bugs.kde.org/show_bug.cgi?id=414200
--- Comment #2 from Matt Fagnani ---
Created attachment 124236
--> https://bugs.kde.org/attachment.cgi?id=124236=edit
New crash information added by DrKonqi
kinfocenter (5.17.3) using Qt 5.12.5
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=413003
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=413003
--- Comment #2 from Matt Fagnani ---
Created attachment 124235
--> https://bugs.kde.org/attachment.cgi?id=124235=edit
New crash information added by DrKonqi
kinfocenter (5.17.3) using Qt 5.12.5
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=414411
--- Comment #1 from Matt Fagnani ---
Created attachment 124069
--> https://bugs.kde.org/attachment.cgi?id=124069=edit
ksplashqml 5.16.5 segmentation fault report
I saw a ksplashqml 5.16.5 segmentation fault in update_buffers at
../src/egl/driv
https://bugs.kde.org/show_bug.cgi?id=414411
Bug ID: 414411
Summary: plasmashell 5.17.3 on Wayland segmentation fault in
update_buffers at
../src/egl/drivers/dri2/platform_wayland.c:633 in
https://bugs.kde.org/show_bug.cgi?id=405609
--- Comment #13 from Matt Fagnani ---
Created attachment 124037
--> https://bugs.kde.org/attachment.cgi?id=124037=edit
valgrind log file for system settings segmentation fault
I ran valgrind --log-file=valgrind-systemsettings5-2.txt systemsettin
https://bugs.kde.org/show_bug.cgi?id=414220
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=414220
--- Comment #1 from Matt Fagnani ---
Created attachment 123979
--> https://bugs.kde.org/attachment.cgi?id=123979=edit
New crash information added by DrKonqi
plasmashell (5.17.3) using Qt 5.12.5
- What I was doing when the application crashed
https://bugs.kde.org/show_bug.cgi?id=405609
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=414220
Bug ID: 414220
Summary: Plasmashell 5.17.3 aborted when its Wayland connection
experienced a fatal error
Product: plasmashell
Version: 5.17.3
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=414118
Bug ID: 414118
Summary: System Settings aborted when its Wayland connection
broke
Product: systemsettings
Version: 5.16.5
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=414116
Bug ID: 414116
Summary: Plasmashell aborted when its Wayland connection broke
Product: plasmashell
Version: 5.16.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=413901
Matt Fagnani changed:
What|Removed |Added
Summary|Konsole aborted when its|Ksysguard aborted when its
https://bugs.kde.org/show_bug.cgi?id=413901
Bug ID: 413901
Summary: Konsole aborted when its Wayland connection broke
Product: ksysguard
Version: 5.16.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=413058
Bug ID: 413058
Summary: Konsole aborted when Wayland connection broke
Product: konsole
Version: 19.08.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=410582
--- Comment #7 from Matt Fagnani ---
Created attachment 123022
--> https://bugs.kde.org/attachment.cgi?id=123022=edit
New crash information added by DrKonqi
konsole (19.08.0) using Qt 5.12.5
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=410582
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=411730
Matt Fagnani changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=411730
Bug ID: 411730
Summary: powerdevil 5.16.4 segmentation faults and aborts when
restarting while logging out of Plasma on Wayland
Product: Powerdevil
Version: 5.16.4
Platform:
https://bugs.kde.org/show_bug.cgi?id=411662
Bug ID: 411662
Summary: plasmashell segmentation fault after configuring the
task manager to set the Show tooltips to off in Plasma
5.16.4 on Wayland
Product: plasmashell
https://bugs.kde.org/show_bug.cgi?id=410332
--- Comment #1 from Matt Fagnani ---
Created attachment 121808
--> https://bugs.kde.org/attachment.cgi?id=121808=edit
gdb full trace of all threads and other output from the plasmashell
segmentation fault core file on logging out of Plasma on Wayl
https://bugs.kde.org/show_bug.cgi?id=410332
Bug ID: 410332
Summary: plasmashell 5.16.2 segmentation faults in
wl_proxy_marshal_constructor at
wayland-client.c:819-820 in libwayland-client when
logging out of Plasma
https://bugs.kde.org/show_bug.cgi?id=410306
Bug ID: 410306
Summary: plasmashell segmentation fault in
QtWaylandClient::QWaylandXdgSurface::setGrabPopup at
qwaylandxdgshell.cpp:371
Product: plasmashell
Version:
https://bugs.kde.org/show_bug.cgi?id=410290
--- Comment #1 from Matt Fagnani ---
Created attachment 121779
--> https://bugs.kde.org/attachment.cgi?id=121779=edit
valgrind log when run on falkon showing invalid reads and writes
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=410290
Bug ID: 410290
Summary: Segmentation faults in qGetPtrHelper in at
qobject.h:121 in qt5-qtbase-5.12.4 when closing falkon
involving not saving history and showing the menu bar
https://bugs.kde.org/show_bug.cgi?id=410211
Matt Fagnani changed:
What|Removed |Added
Summary|plasmashell segmentation|plasmashell segmentation
https://bugs.kde.org/show_bug.cgi?id=409652
Matt Fagnani changed:
What|Removed |Added
Version|5.15.5 |5.16.2
--- Comment #1 from Matt Fagnani ---
Qt
https://bugs.kde.org/show_bug.cgi?id=410211
Bug ID: 410211
Summary: plasmashell segmentation fault when running
startplasmacompositor from VT in Fedora Rawhide
Product: plasmashell
Version: 5.16.2
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=409735
Bug ID: 409735
Summary: plasmashell segmentation fault in PlotSGNode::bind()
at plotter.cpp:695 of kf5-kdeclarative-5.59.0-2.fc30
on Wayland
Product: plasmashell
https://bugs.kde.org/show_bug.cgi?id=409688
Bug ID: 409688
Summary: kwin_wayland aborted when shutting down involving
invalid reads and writes, use of uninitialized
variables etc.
Product: kwin
Version: 5.15.5
https://bugs.kde.org/show_bug.cgi?id=409652
Bug ID: 409652
Summary: xembedsniproxy segmentation faults in
FdoSelectionManager::init when logging into Plasma on
X after running scap-workbench remediation script
Product:
https://bugs.kde.org/show_bug.cgi?id=408553
Matt Fagnani changed:
What|Removed |Added
Component|wayland-generic |general
Assignee|kwin-bugs-n
https://bugs.kde.org/show_bug.cgi?id=408553
Matt Fagnani changed:
What|Removed |Added
URL|https://bugzilla.redhat.com |https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=408553
--- Comment #3 from Matt Fagnani ---
Created attachment 121409
--> https://bugs.kde.org/attachment.cgi?id=121409=edit
coredumpctl gdb output of segmentation fault in powerdevil when logging of
Plasma on Wayland
Thanks Christoph. I th
https://bugs.kde.org/show_bug.cgi?id=408847
--- Comment #11 from Matt Fagnani ---
I requested that David's patch in comment 5 be backported to Qt 5.12.4 in
Fedora 30 at https://bugzilla.redhat.com/show_bug.cgi?id=1723017
Jan Grulich added four patches to qt5-qtwayland-5.12.4-2 which didn't
https://bugs.kde.org/show_bug.cgi?id=409021
--- Comment #2 from Matt Fagnani ---
Created attachment 121087
--> https://bugs.kde.org/attachment.cgi?id=121087=edit
ksplashqml segmentation fault trace from drkonqi when running plasmashell under
valgrind on Plasma on Wayland with qt 5.1
https://bugs.kde.org/show_bug.cgi?id=409021
--- Comment #1 from Matt Fagnani ---
Created attachment 121086
--> https://bugs.kde.org/attachment.cgi?id=121086=edit
valgrind run on plasmashell in Plasma 5.15.5 on Wayland with qt 5.12.4 showing
invalid read and write and uninitialized value
https://bugs.kde.org/show_bug.cgi?id=409021
Matt Fagnani changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=409021
Bug ID: 409021
Summary: Segmentation faults of plasmashell in
wl_proxy_set_queue at wayland-client.c:2094 in
libwayland-client in Plasma 5.15.5 on Wayland with Qt
5.12.4
https://bugs.kde.org/show_bug.cgi?id=408847
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=408971
Matt Fagnani changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=408971
Bug ID: 408971
Summary: Closing konsole with two tabs open in Plasma on
Wayland led to segmentation faults and invalid
reads/writes
Product: konsole
Version: 19.04.2
https://bugs.kde.org/show_bug.cgi?id=408553
Matt Fagnani changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=408553
--- Comment #1 from Matt Fagnani ---
Created attachment 120766
--> https://bugs.kde.org/attachment.cgi?id=120766=edit
gdb output with full trace of all threads from segmentation fault of
org_kde_powerdevil when logging out of Plasma on Wayl
https://bugs.kde.org/show_bug.cgi?id=408553
Bug ID: 408553
Summary: Segmentation faults and invalid reads/writes in
powerdevil when logging out of Plasma 5.15.5 on
Wayland in Fedora 30
Product: Powerdevil
https://bugs.kde.org/show_bug.cgi?id=407025
Bug ID: 407025
Summary: xdg-desktop-portal-kde 5.15.4 segmentation faults in
gbm_device_destroy at gbm.c:109 in mesa-libgbm when
logging out of Plasma
Product:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #17 from Matt Fagnani ---
Created attachment 117348
--> https://bugs.kde.org/attachment.cgi?id=117348=edit
New crash information added by DrKonqi
ksysguard (5.14.4) using Qt 5.11.3
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=402848
Matt Fagnani changed:
What|Removed |Added
CC||jgrul...@redhat.com
Component|discover
https://bugs.kde.org/show_bug.cgi?id=402848
--- Comment #4 from Matt Fagnani ---
Created attachment 117280
--> https://bugs.kde.org/attachment.cgi?id=117280=edit
error messages in konsole when valgrind was run on discover
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=402848
--- Comment #3 from Matt Fagnani ---
Created attachment 117279
--> https://bugs.kde.org/attachment.cgi?id=117279=edit
valgrind output when run on discover
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402848
--- Comment #2 from Matt Fagnani ---
I ran valgrind --leak-check=no --log-file=valgrind-discover-5.14.5-1.txt
plasma-discover & The valgrind output following the crash showed an invalid
read of size 4 in QHttpNetworkConnectionChannel::sendReq
https://bugs.kde.org/show_bug.cgi?id=402848
Matt Fagnani changed:
What|Removed |Added
Platform|Other |Fedora RPMs
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402848
--- Comment #1 from Matt Fagnani ---
Created attachment 117277
--> https://bugs.kde.org/attachment.cgi?id=117277=edit
full trace of all threads for discover crash
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402848
Bug ID: 402848
Summary: Discover 5.14.4 crashed when clicking on Checking for
updates and about 50 notifications appeared
Product: Discover
Version: 5.14.4
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #16 from Matt Fagnani ---
Created attachment 116888
--> https://bugs.kde.org/attachment.cgi?id=116888=edit
New crash information added by DrKonqi
ksysguard (5.14.4) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=401965
--- Comment #2 from Matt Fagnani ---
(In reply to Michael Pyne from comment #1)
> This is indeed at least partially intentional. I won't promise that there's
> not been oversights from developers adding scripts to forget to also
https://bugs.kde.org/show_bug.cgi?id=401965
Bug ID: 401965
Summary: Missing subdirectories of
kde-dev-scripts-18.04.3-1.fc29
Product: kdesdk-scripts
Version: unspecified
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #15 from Matt Fagnani ---
AddressSanitizer caught a use-after-free error in TopLevel::answerReceived at
ksysguard.cpp:450 while ksysguard was closing on the 24th time I ran it. The
second function from the top was KSGRD::SensorAgent
https://bugs.kde.org/show_bug.cgi?id=401088
--- Comment #3 from Matt Fagnani ---
(In reply to Kai Uwe Broulik from comment #2)
> Imho that notification is pointless and should be removed, it's mostly meant
> for when a NFS mount becomes stale.
I don't have an NFS or other network m
https://bugs.kde.org/show_bug.cgi?id=401088
Matt Fagnani changed:
What|Removed |Added
Version|master |5.14.3
--- Comment #1 from Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=400499
Matt Fagnani changed:
What|Removed |Added
Version|5.13.5 |5.14.3
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #14 from Matt Fagnani ---
Created attachment 116434
--> https://bugs.kde.org/attachment.cgi?id=116434=edit
AddressSanitizer output from running and closing ksysguard
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #13 from Matt Fagnani ---
Created attachment 116433
--> https://bugs.kde.org/attachment.cgi?id=116433=edit
valgrind --leak-check=yes --show-leak-kinds=definite
--log-file=valgrind-ksysguard-5.txt ksysguard output
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #12 from Matt Fagnani ---
All of the valgrind runs' first invalid reads were in
KSGRD::SensorAgent::processAnswer at SensorAgent.cpp:186 as in the following.
All of the other invalid reads or writes have
KSGRD::SensorAgent::processAnswer
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #11 from Matt Fagnani ---
Memory leaks were detected with 8-9 definitely lost blocks, 48 indirectly lost
blocks, and 19 possibly lost blocks per run. I'm unsure if the segmentation
faults are related to those memory leaks. One line I wrote
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #10 from Matt Fagnani ---
Created attachment 116396
--> https://bugs.kde.org/attachment.cgi?id=116396=edit
valgrind --read-var-info=yes --log-file=valgrind-ksysguard-3.txt ksysguard
output
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #9 from Matt Fagnani ---
Created attachment 116395
--> https://bugs.kde.org/attachment.cgi?id=116395=edit
valgrind --log-file=valgrind-ksysguard-2.txt ksysguard output
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #8 from Matt Fagnani ---
Created attachment 116394
--> https://bugs.kde.org/attachment.cgi?id=116394=edit
valgrind --log-file=valgrind-ksysguard-1.txt ksysguard output
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #7 from Matt Fagnani ---
I ran valgrind on ksysguard three times. valgrind showed invalid reads and
writes each time after I closed ksysguard. 97 invalid reads and 23 invalid
writes were listed on both of the first and third runs. 89
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #6 from Matt Fagnani ---
Crashes involving segmentation faults in operator== (s1=..., s2=...) at
tools/qstring.cpp:3153 were reported for:
kpat at https://bugs.kde.org/show_bug.cgi?id=363726#c5
kdeconnectd at https://bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #5 from Matt Fagnani ---
Those ksysguard crashes with segmentation faults at operator==(QString const&,
QString const&) (s1=..., s2=...) at tools/qstring.cpp:3153 seem to involve the
line if (s1.d->size != s2.d->size) i
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #4 from Matt Fagnani ---
Created attachment 116390
--> https://bugs.kde.org/attachment.cgi?id=116390=edit
New crash information added by DrKonqi
ksysguard (5.14.3) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=401088
Bug ID: 401088
Summary: "Filesystem mounted at '/' is not responding"
notification on log in to Plasma 5.14.3
Product: plasmashell
Version: master
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #3 from Matt Fagnani ---
Created attachment 116263
--> https://bugs.kde.org/attachment.cgi?id=116263=edit
New crash information added by DrKonqi
ksysguard (5.14.3) using Qt 5.11.1
- What I was doing when the application crashed
https://bugs.kde.org/show_bug.cgi?id=400778
--- Comment #7 from Matt Fagnani ---
kinfocenter 5.14.3 still shows the blank Energy Consumption Statistics after I
updated to Plasma 5.14.3 and KF5 5.52.0. I saw three error messages in addition
to those I mentioned before relating to kirigami
https://bugs.kde.org/show_bug.cgi?id=400929
Bug ID: 400929
Summary: kwallet-pam errors when logging into Plasma from
lightdm
Product: kwallet-pam
Version: unspecified
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #12 from Matt Fagnani ---
(In reply to Stefan Brüns from comment #11)
> (In reply to Matt Fagnani from comment #10)
> > I read in another post that the failed assertion might indicate a corrupted
> > baloo index whi
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #10 from Matt Fagnani ---
Created attachment 116200
--> https://bugs.kde.org/attachment.cgi?id=116200=edit
New crash information added by DrKonqi
baloo_file (5.52.0) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #8 from Matt Fagnani ---
Created attachment 116198
--> https://bugs.kde.org/attachment.cgi?id=116198=edit
New crash information added by DrKonqi
baloo_file (5.52.0) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400498
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #1 from Matt Fagnani ---
Created attachment 116189
--> https://bugs.kde.org/attachment.cgi?id=116189=edit
New crash information added by DrKonqi
ksysguard (5.13.5) using Qt 5.11.1
- What I was doing when the application crashed
https://bugs.kde.org/show_bug.cgi?id=400499
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You
https://bugs.kde.org/show_bug.cgi?id=400778
--- Comment #6 from Matt Fagnani ---
drkonqi showed that valgrind --leak-check=yes
--log-file=valgrind_kinfocenter_3.txt kinfocenter crashed due to a segmentation
fault with the following trace although the functions shown appear to be mostly
from
https://bugs.kde.org/show_bug.cgi?id=400778
--- Comment #5 from Matt Fagnani ---
Created attachment 116173
--> https://bugs.kde.org/attachment.cgi?id=116173=edit
strace kinfocenter output before making any further changes
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400778
--- Comment #4 from Matt Fagnani ---
Created attachment 116172
--> https://bugs.kde.org/attachment.cgi?id=116172=edit
valgrind log for when kinfocenter closed normally
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400778
--- Comment #3 from Matt Fagnani ---
Created attachment 116171
--> https://bugs.kde.org/attachment.cgi?id=116171=edit
valgrind log for when kinfocenter crashed due to invalid reads
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=400778
Matt Fagnani changed:
What|Removed |Added
Platform|Other |Fedora RPMs
--- Comment #2 from Matt Fagnani
https://bugs.kde.org/show_bug.cgi?id=400778
Bug ID: 400778
Summary: Energy consumption statistics panel in kinfocenter
5.13.5 was blank
Product: kinfocenter
Version: 5.13.5
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #7 from Matt Fagnani ---
Nate, I'm inexperienced at interpreting such traces so I doubt that I'm more
familiar than you are at it.
Stefan, I've reassigned the Fedora report I filed on these crashes from
kf5-baloo to lmdb at https
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #4 from Matt Fagnani ---
While bug 389625 involves baloo and liblmdb.so.0, the crashing thread from the
trace in 389625 doesn't show mdb_assert_fail and the failed assertion rc == 0
in mdb_page_dirty at mdb.c in liblmdb.so. I think
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #2 from Matt Fagnani ---
I ran gdb on baloo_file based on the instructions in the Retrieving a backtrace
when an uncaught exception is causing a crash section at
https://community.kde.org/Guidelines_and_HOWTOs/Debugging
https://bugs.kde.org/show_bug.cgi?id=400498
--- Comment #1 from Matt Fagnani ---
The crash might've been due to a failed assertion rc == 0 in mdb_page_dirty at
mdb.c:2127-2128 in liblmdb.so.0.0.0 in the lmdb-libs package.
A possible fix in the lmdb package was noted at the following report
https://bugs.kde.org/show_bug.cgi?id=400499
Bug ID: 400499
Summary: ksysguard crashed when closing
Product: ksysguard
Version: 5.13.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=400498
Bug ID: 400498
Summary: baloo_file crashed a few minutes after starting Plasma
Product: frameworks-baloo
Version: 5.51.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=350140
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--- Comment #16
https://bugs.kde.org/show_bug.cgi?id=398293
Matt Fagnani changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=398293
Bug ID: 398293
Summary: kalzium interface is missing parts
Product: kalzium
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
301 - 397 of 397 matches
Mail list logo
