[kalendar] [Bug 470320] New: Kalendar crashes when clicking on contact
https://bugs.kde.org/show_bug.cgi?id=470320
Bug ID: 470320
Summary: Kalendar crashes when clicking on contact
Classification: Applications
Product: kalendar
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: claudio.cam...@kde.org
Reporter: bachirg...@gmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: kalendar (23.04.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.4-arch1-1 x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
When using the Kalendar application, I switched to selecting the fields of a
contact and the application crashed
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Kalendar (kalendar), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6
QVector::indexOf(QQuickItemPrivate::ChangeListener
const&, int) const [clone .constprop.0] [clone .isra.0] (t=..., from=0,
this=) at /usr/include/qt/QtCore/qvector.h:1009
#7 0x7fc4aa02ce34 in
QVector::removeOne(QQuickItemPrivate::ChangeListener
const&) (t=..., this=) at /usr/include/qt/QtCore/qvector.h:180
#8 QQuickItemPrivate::removeItemChangeListener(QQuickItemChangeListener*,
QFlags) (this=0x55c8f61cd4e0,
listener=, types=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickitem.cpp:3930
#9 0x7fc4a6f5c8ac in
QQuickScrollBarAttachedPrivate::setFlickable(QQuickFlickable*)
(this=this@entry=0x55c8f61c6310, item=item@entry=0x0) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:766
#10 0x7fc4a6f5cb53 in QQuickScrollBarAttached::~QQuickScrollBarAttached()
(this=0x55c8f7c954f0, this=) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:1017
#11 0x7fc4a6f5cb7e in QQuickScrollBarAttached::~QQuickScrollBarAttached()
(this=0x55c8f7c954f0, this=) at
/usr/src/debug/qt5-quickcontrols2/qtquickcontrols2/src/quicktemplates2/qquickscrollbar.cpp:1018
#12 0x7fc4a80c5d8d in QObjectPrivate::deleteChildren()
(this=this@entry=0x55c8f6f57a20) at kernel/qobject.cpp:2137
#13 0x7fc4a80c6509 in QObject::~QObject() (this=,
this=) at kernel/qobject.cpp:1115
#14 0x7fc43dd1b1a3 in QQuickScrollView::~QQuickScrollView()
(this=0x55c8f8696220, this=) at
../../../include/QtQuickTemplates2/5.15.9/QtQuickTemplates2/private/../../../../../../qtquickcontrols2/src/quicktemplates2/qquickscrollview_p.h:58
#15 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55c8f8696220, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#16 QQmlPrivate::QQmlElement::~QQmlElement()
(this=0x55c8f8696220, this=) at
/usr/include/qt/QtQml/qqmlprivate.h:144
#17 0x7fc4a9aa6cc6 in QQmlObjectCreator::clear() (this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1461
#18 QQmlObjectCreator::clear() (this=0x55c8fa642e80) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectcreator.cpp:1452
#19 0x7fc4a9a4b331 in QQmlIncubatorPrivate::clear() (this=0x55c8f774b500)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlincubator.cpp:174
#20 0x7fc4a9a4b030 in QQmlIncubator::clear()
(this=this@entry=0x55c8f62ed8a0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlincubator.cpp:606
#21 0x7fc4a6e382f9 in
QQmlDelegateModelPrivate::releaseIncubator(QQDMIncubationTask*)
(this=0x55c8f8456e20, incubationTask=0x55c8f62ed8a0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1085
#22 0x7fc4a6e59cc9 in
QQmlDelegateModelPrivate::itemsRemoved(QVector
const&, QVarLengthArray, 11>*, QHash >*) [clone .isra.0] (this=0x55c8f8456e20,
translatedRemoves=, movedItems=0x7ffdc6fc19f8,
removes=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1690
#23 0x7fc4a6e397ab in
QQmlDelegateModelPrivate::itemsMoved(QVector
const&, QVector const&)
(this=this@entry=0x55c8f8456e20, removes=, inserts=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1782
#24 0x7fc4a6e3f5c3 in QQmlDelegateModel::_q_modelReset()
(this=0x55c8f83624c0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1933
#25 0x7fc4a6e48333 in QQmlDelegateModel::qt_metacall(QMetaObject::Call,
int, void**) (this=0x55c8f83624c0, _c=QMetaObject::InvokeMetaMethod, _id=8,
_a=0x7ffdc6fc1cd0) at .moc/moc_qqmldelegatemodel_p.cpp:371
#26 0x7fc4a80cfc1f in doActivate(QObject*, int, void**)
(sender=0x55c8f54173e0, signal_index=21, argv=0x7ffdc6fc1cd0) at
kernel/qobject.cpp:3949
#27 0x7fc4a8057562 in
[frameworks-baloo] [Bug 466916] baloo_file_extractor crashes and the coredump take too much space
https://bugs.kde.org/show_bug.cgi?id=466916 --- Comment #5 from bachirg...@gmail.com --- It is (In reply to tagwerk19 from comment #2) > Possible that this is fixed with Frameworks 5.104 (Bug 465801) It is indeed fixed (I mean it's an old report, but it seems like the bug is not there since this version) -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 469917] New: XWaylandVideoBridge launches four instances at start
https://bugs.kde.org/show_bug.cgi?id=469917 Bug ID: 469917 Summary: XWaylandVideoBridge launches four instances at start Classification: Applications Product: XWaylandVideoBridge Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bachirg...@gmail.com CC: aleix...@kde.org, k...@davidedmundson.co.uk Target Milestone: --- SUMMARY 4 instances are launched instead of only one (which leads to problem when sharing) STEPS TO REPRODUCE 1. Boot computer 2. 4 instances are visible in the system tray and in htop 3. Try to share a screen 4. 4 windows pop up OBSERVED RESULT EXPECTED RESULT Only one instances is started automatically SOFTWARE/OS VERSIONS Linux: 6.3.2-arch1-1 (available in About System) KDE Plasma Version: 5.106.0 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Note that the software was installed through the AUR (if you are unfamiliar with it, just know that the following bash script (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=xwaylandvideobridge-bin) was run to build and install the program (it repacks the flatpak into a regular arch package basically)) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466916] New: baloo_file_extractor crashes and the coredump take too much space
https://bugs.kde.org/show_bug.cgi?id=466916 Bug ID: 466916 Summary: baloo_file_extractor crashes and the coredump take too much space Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.103.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: bachirg...@gmail.com Target Milestone: --- Created attachment 157025 --> https://bugs.kde.org/attachment.cgi?id=157025=edit Backtraces generated by gdb and drkonqi-coredump-gui SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** baloo_file_extractor crashes and the coredump take too much space (in /var/lib/systemd/coredump), I attached some backtraces generated by drkonqi and gdb, but feel free to ask for more details STEPS TO REPRODUCE 1. Use Baloo 2. It crashes and ends up producing several Gb of coredumps after some time OBSERVED RESULT The program crashes and generates too much coredumps EXPECTED RESULT The program doesn't crash or at least generates a limited amount of dumps SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460140] The System Tray applet is too big when opened
https://bugs.kde.org/show_bug.cgi?id=460140 bachirg...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from bachirg...@gmail.com --- (In reply to Nate Graham from comment #1) > Can you resize it to be smaller by dragging from an edge, like you would for > a normal app window? Oh ! I actually can, didn't know they were resizeable ! Guess that settles it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460140] New: The System Tray applet is too big when opened
https://bugs.kde.org/show_bug.cgi?id=460140 Bug ID: 460140 Summary: The System Tray applet is too big when opened Classification: Plasma Product: plasmashell Version: 5.25.90 Platform: Archlinux OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bachirg...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 152652 --> https://bugs.kde.org/attachment.cgi?id=152652=edit A screenshot showing the size of the open System Tray applet SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click on the downward arrow on the "System Tray" that leads to the Status and Notifications menu OBSERVED RESULT The applet becomes way too big, covering most of the screen (see attachment) EXPECTED RESULT The applet has a normal size (as it used to be) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION This bug did not seem to manifest itself until I switched to 5.25.90, and it is present in Xorg and Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 460139] New: On Wayland, Spectacle cannot take screenshots of drawings made with the "Mouse Mark" desktop effect
https://bugs.kde.org/show_bug.cgi?id=460139 Bug ID: 460139 Summary: On Wayland, Spectacle cannot take screenshots of drawings made with the "Mouse Mark" desktop effect Classification: Applications Product: Spectacle Version: 22.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: bachirg...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Make sure you are on Wayland 2. Draw anything with the "Mouse Mark" desktop effect 3. Take a screenshot with Spectacle with the drawings in the Area OBSERVED RESULT The mouse marks should appear on the screenshot EXPECTED RESULT The mouse marks do not appear on the screenshot SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (kernel 5.19.13-arch1-1) (available in About System) KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 433875] Xorg-session.log fills itself with errors and grows absurdly large (led to a system crash on my computer)
https://bugs.kde.org/show_bug.cgi?id=433875 --- Comment #2 from bachirg...@gmail.com --- (In reply to Rolf Eike Beer from comment #1) > When I start kgpg from a terminal I see that message about 5 times, and then > it stops. More lines only show up when I try to do anything, like refresh > the key list. Have you tried to start it by setting it to autostart with the Xorg session ? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 433875] New: Xorg-session.log fills itself with errors and grows absurdly large (led to a system crash on my computer)
https://bugs.kde.org/show_bug.cgi?id=433875 Bug ID: 433875 Summary: Xorg-session.log fills itself with errors and grows absurdly large (led to a system crash on my computer) Product: kgpg Version: 20.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: bachirg...@gmail.com Target Milestone: --- SUMMARY When an invalid path to the GnuPG configuration file is specified and KGpg is set to start when the xorg session start, it will fill the xorg-session.log with errors until the system crashes because it has no more disk space left STEPS TO REPRODUCE 1. Set KGpg to start with the session in KGpg settings 2. Provide an invalid path to the GnuPG configuration file in KGpg OBSERVED RESULT The xorg-session.log (located in ~/.local/share/sddm/xorg-session.log) if you are using SDDM) fills itself with errors stating that the provided path is invalid. The file ends up being very large and fills at several Mb per seconds on my computer (it reached 300Gb in a few hours :D ) EXPECTED RESULT The error is logged once (or finite amount really) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
