[plasmashell] [Bug 482886] no spacing in Kicker menu entries and strange sub menu rendering
https://bugs.kde.org/show_bug.cgi?id=482886 Karsten changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Karsten --- The same thing happens on 545.29.06. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482886] no spacing in Kicker menu entries and strange sub menu rendering
https://bugs.kde.org/show_bug.cgi?id=482886 Karsten changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Karsten --- I think something went wrong while updating. After reinstalling libplasma the menu works as expected. Sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995 Karsten Elfenbein changed: What|Removed |Added CC||karsten.elfenb...@gmail.com --- Comment #1 from Karsten Elfenbein --- I also get this issue on Arch Linux with Gwenview 23.08.4 KDE Framework 5.113.0 Qt 5.15.11 Window system xcb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482651] Cursor not locked to window in proton/wine games when using Wayland
https://bugs.kde.org/show_bug.cgi?id=482651 Karsten Elfenbein changed: What|Removed |Added CC||karsten.elfenb...@gmail.com --- Comment #1 from Karsten Elfenbein --- There is a similar issue when using GeforceNOW or Amazon Luna. The keyboard inputs can get stuck so you keep walking for example. The mouse can also be moved to the second screen while it should be captured on the first screen (when not in a game menu) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482651] Cursor not locked to window in proton/wine games when using Wayland
https://bugs.kde.org/show_bug.cgi?id=482651 --- Comment #2 from Karsten Elfenbein --- The issue also happens with only one active display. With x11 as graphic platform the issue disappears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482886] New: no spacing in Kicker menu entries and strange sub menu rendering
https://bugs.kde.org/show_bug.cgi?id=482886 Bug ID: 482886 Summary: no spacing in Kicker menu entries and strange sub menu rendering Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: karsten.elfenb...@gmail.com Target Milestone: 1.0 Created attachment 166721 --> https://bugs.kde.org/attachment.cgi?id=166721&action=edit cramped menu entries and random spacing for sub menus STEPS TO REPRODUCE 1. switch the a program/start menu to kicker 2. open kicker OBSERVED RESULT all entries are cramped together with minimal spacing sub menus open with random spacing EXPECTED RESULT entries with more spacing as in screenshots like https://userbase.kde.org/File:Kicker.png sub menus somewhat visually attached to the rest of the menu SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - current Arch Linux running kde 6.0.1, Nvidia 550.54.14 on a 3060ti - Wayland or X11 backend does not matter (x11 backend adds additional black background but that is not limited to Kicker) - happens on an upgraded or even a fresh/empty user profile -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480456] New: Document tree doesn't remember all open/close states
https://bugs.kde.org/show_bug.cgi?id=480456 Bug ID: 480456 Summary: Document tree doesn't remember all open/close states Classification: Applications Product: kate Version: 23.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mnyro...@tprac.de Target Milestone: --- Working with the document tree (left hand sidebar) on a large code base, I keep some tree branches currently worked on as opened while others currenty unimportant closed. Closing kate and restarting it (eg tomorrow), only the last file edited and its tree branch is open. But I'd expect all branches' open state to persist. STEPS TO REPRODUCE 1. activate document sidebar and open several files in distinctive directories 2. open several of files by using the tree view, thus having all their path branches shown 3. close kate (^Q) 4. start kate OBSERVED RESULT 5. all document branches are closed except for the last shown file EXPECTED RESULT 6. all branches' open state should persist SOFTWARE/OS VERSIONS Lubuntu 23.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453454] New: Kate crashes after pressing button "filesystem" in left task bar
https://bugs.kde.org/show_bug.cgi?id=453454
Bug ID: 453454
Summary: Kate crashes after pressing button "filesystem" in
left task bar
Product: kate
Version: 22.04.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: karsten.pfeif...@gmail.com
Target Milestone: ---
Application: kate (22.04.0)
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed: I am starting Kate the first
time after Tumbleweed new installation directly from favorites. The first
action i did was to press the button filesystem from the left task bar. The
problem is reproducible. When i create a first new text file (create, write,
close) the problem is done. Regards Karsten
The crash can be reproduced every time.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QFlags::operator|= (other=,
this=) at
/usr/src/debug/kconfig-5.93.0-1.1.x86_64/src/core/kconfig.cpp:1058
#7 KConfigPrivate::lookupData (this=0x205, group=..., key=0x7effd5d4cf39 "View
Style", flags=..., expand=0x7ffe31758257) at
/usr/src/debug/kconfig-5.93.0-1.1.x86_64/src/core/kconfig.cpp:1059
#8 0x7effdc943d90 in KConfigGroup::readEntry
(this=this@entry=0x55bc2c455ae0, key=key@entry=0x7effd5d4cf39 "View Style",
aDefault=...) at
/usr/src/debug/kconfig-5.93.0-1.1.x86_64/src/core/kconfiggroup.cpp:674
#9 0x7effdc943fac in KConfigGroup::readEntry
(this=this@entry=0x55bc2c455ae0, key=key@entry=0x7effd5d4cf39 "View Style",
aDefault=aDefault@entry=0x7effd5d4cf2e "DetailTree") at
/usr/src/debug/kconfig-5.93.0-1.1.x86_64/src/core/kconfiggroup.cpp:659
#10 0x7effd5ce8cde in KDirOperator::readConfig (this=0x55bc2c9539c0,
configGroup=...) at
/usr/src/debug/kio-5.93.0-1.1.x86_64/src/filewidgets/kdiroperator.cpp:2442
#11 0x7effd41d42d0 in KateFileBrowser::readSessionConfig
(this=this@entry=0x55bc2c90f490, cg=...) at
/usr/src/debug/kate-22.04.0-1.1.x86_64/addons/filebrowser/katefilebrowser.cpp:160
#12 0x7effd41d7a22 in KateFileBrowserPluginView::createFileBrowser
(this=0x55bc2c1cde90, visible=) at
/usr/include/c++/11/bits/unique_ptr.h:173
#13 0x7effdb3fd488 in doActivate (sender=0x55bc2c452b30,
signal_index=7, argv=0x7ffe317585b0) at kernel/qobject.cpp:3898
#14 0x7effdb3f67af in QMetaObject::activate (sender=,
m=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe317585b0) at kernel/qobject.cpp:3946
#15 0x55bc28e2f1eb in KateMDI::ToolView::toolVisibleChanged (_t1=true,
this=) at
/usr/src/debug/kate-22.04.0-1.1.x86_64/build/kate/kate-lib_autogen/EWIEGA46WW/moc_katemdi.cpp:333
#16 KateMDI::ToolView::setToolVisible (vis=true, this=) at
/usr/src/debug/kate-22.04.0-1.1.x86_64/kate/katemdi.cpp:244
#17 KateMDI::Sidebar::showWidget (this=this@entry=0x55bc2be05e50,
widget=) at
/usr/src/debug/kate-22.04.0-1.1.x86_64/kate/katemdi.cpp:480
#18 0x55bc28e2f71d in KateMDI::Sidebar::tabClicked (this=0x55bc2be05e50,
i=) at
/usr/src/debug/kate-22.04.0-1.1.x86_64/kate/katemdi.cpp:628
#19 0x7effdb3fd488 in doActivate (sender=0x55bc2c4518a0,
signal_index=12, argv=0x7ffe31758730) at kernel/qobject.cpp:3898
#20 0x7effdb3f67af in QMetaObject::activate (sender=,
m=m@entry=0x7effdcb3f180, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe31758730) at kernel/qobject.cpp:3946
#21 0x7effdcabf33e in KMultiTabBarButton::clicked (this=,
_t1=) at
/usr/src/debug/kwidgetsaddons-5.93.0-1.1.x86_64/build/src/KF5WidgetsAddons_autogen/include/moc_kmultitabbar.cpp:289
#22 0x7effdb3fd453 in QtPrivate::QSlotObjectBase::call (a=0x7ffe31758840,
r=0x55bc2c4518a0, this=0x55bc2c452010) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x55bc2c4518a0, signal_index=9,
argv=0x7ffe31758840) at kernel/qobject.cpp:3886
#24 0x7effdb3f67af in QMetaObject::activate
(sender=sender@entry=0x55bc2c4518a0, m=m@entry=0x7effdc4d1180,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffe31758840)
at kernel/qobject.cpp:3946
#25 0x7effdc0a50d2 in QAbstractButton::clicked
(this=this@entry=0x55bc2c4518a0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#26 0x7effdc0a534a in QAbstractButtonPrivate::emitClicked
(this=0x55bc2c451bd0) at widgets/qabstractbutton.cpp:415
#27 0x7effdc0a6f10 in QAbstractButtonPrivate::click (this=0x55bc2c451bd0)
at widgets/qabstractbutton.cpp:408
#28 0x7effdc0a7133 in QAbstractButton::mouseReleaseEvent
(this=0x55bc2c4518a0, e=0x7ff
[kdiff3] [Bug 478449] Kdiff crashes if exit via menu or hotkey
https://bugs.kde.org/show_bug.cgi?id=478449 Karsten Düsterloh changed: What|Removed |Added CC||mnyro...@tprac.de --- Comment #1 from Karsten Düsterloh --- I can confirm this on Lubuntu 23.10 with kdiff3 1.10.5 (64 bit). Crash on ^Q and File→Quit, no crash on frame "X". -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472718] New: Merge conflict resolved to empty is saved as newline
https://bugs.kde.org/show_bug.cgi?id=472718 Bug ID: 472718 Summary: Merge conflict resolved to empty is saved as newline Classification: Applications Product: kdiff3 Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: mnyro...@tprac.de Target Milestone: --- When resolving a merge conflict in line 1, and picking "no src line" as the solution, the result saved to file for this conflict is a newline. This is a very grave problem, especially in automerge mode, since the merge result is not part of the input data. And in UI mode, the UI is even lying to you … STEPS TO REPRODUCE 1. Create two input files "x" and "y" with the four lines of content each: file "x": a b c e file "y": b c d e 2. Do a merge of these two files to a new file "z", eg. via kdiff3 -m -o z x y kdiff will complain about 2 merge conflicts. 3. Resolve each conflict by choosing the empty block. Kdiff3 will mark these in the merge view as 4. Save and quit Kdiff3. OBSERVED RESULT Look into the merge result file "z": - the conflict solution "" of merge line 1 was falsely written as an empty line - the conflict solution "" of merge line 4 was correctly not written EXPECTED RESULT The "" of merge line 1 should not result in any output. SOFTWARE/OS VERSIONS KDiff3 Version 1.9.70 (64 bit) (and several older versions) Lubuntu 23.04, i.e. Ubuntu 23.04 with LXDE desktop environment. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472718] Merge conflict resolved to empty is saved as newline
https://bugs.kde.org/show_bug.cgi?id=472718 Karsten Düsterloh changed: What|Removed |Added CC||mnyro...@tprac.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473621] New: Plasma crashed after closing email notification
https://bugs.kde.org/show_bug.cgi?id=473621 Bug ID: 473621 Summary: Plasma crashed after closing email notification Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: karsten.bruc...@gmx.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.6) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [CoredumpBackend] -- Information about the crash: Notification about an incoming mail (-> Thunderbird) popped up. When closing the notification (by using the crosshair button), Plasma crashed. Automatic restart went OK. Happens occasionally, cannot be systematically reproduced /w every notification. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f978a693dad in QtQml::qmlExecuteDeferred(QObject*) () from /lib64/libQt5Qml.so.5 #6 0x7f978ab78e99 in QQuickTransition::prepare(QList&, QList&, QQuickTransitionManager*, QObject*) () from /lib64/libQt5Quick.so.5 #7 0x7f978ab6e3b7 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () from /lib64/libQt5Quick.so.5 #8 0x7f9788f191bb in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f9789da519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 The reporter indicates this bug may be a duplicate of or related to bug 461072, bug 462715, bug 465706, bug 473055. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473621] Plasma crashed after closing email notification
https://bugs.kde.org/show_bug.cgi?id=473621 --- Comment #1 from Karsten Brucker --- Created attachment 161104 --> https://bugs.kde.org/attachment.cgi?id=161104&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473621] Plasma crashed after closing email notification
https://bugs.kde.org/show_bug.cgi?id=473621 --- Comment #3 from Karsten Brucker --- (In reply to Nate Graham from comment #2) > No KDE code in the backtrace: > > Thread 1 (Thread 0x7f9786cc6980 (LWP 1792)): > ... > #22 0x56526dc07e25 in ?? () Sorry to hear that the backtrace does not contain valid information. After opening the bug report, KDE's error data sending facility window remained open for > 3h; I considered this sufficient and closed the window, but maybe the tool was in fact still sending? Can I provide trace, coredump etc. data manually in case the crash happens again? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Tree View mode crashes in KFileItemModel and shows duplicate items
https://bugs.kde.org/show_bug.cgi?id=422282 Karsten Loh changed: What|Removed |Added CC||karsten@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358751] konsole loses file descriptors and eventually runs out of them and crashes
https://bugs.kde.org/show_bug.cgi?id=358751 --- Comment #3 from Karsten Künne --- I haven't seen it with konsole 18.07.80 in OpenSUSE Leap 15.0. So, you can probably close this bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358751] konsole loses file descriptors and eventually runs out of them and crashes
https://bugs.kde.org/show_bug.cgi?id=358751 Karsten Künne changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Karsten Künne --- Forgot to change the status. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 46528] konqi cookie/password dialog box appears on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=46528 Karsten Künne changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #13 from Karsten Künne --- can't reproduce it anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 345412] Can't access the KWallet in KDE 5, since latest updates in Kubuntu Vivid
https://bugs.kde.org/show_bug.cgi?id=345412 Karsten Diem changed: What|Removed |Added CC||kdeb...@thediems.de --- Comment #47 from Karsten Diem --- After upgrading some packages on KDE Neon 5.19, I also encountered this bug. In addition to Jaume Sabater (https://bugs.kde.org/show_bug.cgi?id=345412#c42), I'd like to point out an -at least temporary- solution by downgrading the corresponding packages to their previous versions: sudo apt install kwalletmanager=4:20.04.1-0xneon+18.04+bionic+build34 libkwalletbackend5-5=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet5=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet-data=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet-bin=5.70.0-0xneon+18.04+bionic+build42 libpam-kwallet5=4:5.18.5-0xneon+18.04+bionic+build50 libpam-kwallet-common=4:5.18.5-0xneon+18.04+bionic+build50 Afterwards just reboot and you should be good to go - without losing any stored secrets. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 Karsten Diem changed: What|Removed |Added CC||kdeb...@thediems.de --- Comment #9 from Karsten Diem --- Hey Chris, you might be interested in this: https://bugs.kde.org/show_bug.cgi?id=345412#c47 I also encountered this bug today, so I downgraded all packages related to kwallet. You might want to check the correct versions you've been on before upgrading by issuing this command: grep " upgrade " /var/log/dpkg.log | grep "wallet" which, on my system, resulted in: 2020-06-10 11:36:54 upgrade libpam-kwallet5:amd64 4:5.18.5-0xneon+18.04+bionic+build50 4:5.19.0-0xneon+18.04+bionic+build51 2020-06-10 11:36:54 upgrade libpam-kwallet-common:all 4:5.18.5-0xneon+18.04+bionic+build50 4:5.19.0-0xneon+18.04+bionic+build51 2020-06-16 09:20:54 upgrade libkf5wallet-bin:amd64 5.70.0-0xneon+18.04+bionic+build42 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 09:20:54 upgrade libkf5wallet-data:all 5.70.0-0xneon+18.04+bionic+build42 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 09:20:54 upgrade libkf5wallet5:amd64 5.70.0-0xneon+18.04+bionic+build42 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 09:20:55 upgrade libkwalletbackend5-5:amd64 5.70.0-0xneon+18.04+bionic+build42 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 09:21:37 upgrade kwalletmanager:amd64 4:20.04.1-0xneon+18.04+bionic+build34 4:20.04.2-0xneon+18.04+bionic+build37 (In reply to Chris Coetzee from comment #3) > I'm experiencing the exact same problem after updating Neon tonight. Looks > like my package versions are the same. > > I tried downgrading libkwalletbackend5-5, but I couldn't without breaking > other packages. > > I didn't dig deep for the official sources, but I saw this commit on kwaller > Github project, and it looks like a byte-order change in the encryption may > have caused this. > > https://github.com/KDE/kwallet/blame/master/src/runtime/kwalletd/backend/ > blowfish.cc > > SOFTWARE/OS VERSIONS > Operating System: KDE neon Testing Edition > KDE Plasma Version: 5.18.90 > KDE Frameworks Version: 5.71.0 > Qt Version: 5.14.2 > Kernel Version: 4.15.0-101-generic > OS Type: 64-bit > Wallet Manager: Version 20.04.1 > Wallet Backend: Version 5.70.0 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 345412] Can't access the KWallet in KDE 5, since latest updates in Kubuntu Vivid
https://bugs.kde.org/show_bug.cgi?id=345412 --- Comment #51 from Karsten Diem --- To (temporarily) prevent upgrading those headache-/heart-attack- triggering packages, you might want to pin their versions until the problem has been solved. create /etc/apt/preferences.d/fix_broken_kwallet.pref with Package: kwalletmanager Pin: version 4:20.04.1-0xneon+18.04+bionic+build34 Pin-Priority: 1000 Package: libkwalletbackend5-5 Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet5 Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet-data Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet-bin Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libpam-kwallet5 Pin: version 4:5.18.5-0xneon+18.04+bionic+build50 Pin-Priority: 1000 Package: libpam-kwallet-common Pin: version 4:5.18.5-0xneon+18.04+bionic+build50 Pin-Priority: 1000 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 345412] Can't access the KWallet in KDE 5, since latest updates in Kubuntu Vivid
https://bugs.kde.org/show_bug.cgi?id=345412 --- Comment #56 from Karsten Diem --- The problem seems to be fixed in neon repository. If you created "fix_broken_kwallet.pref" from (https://bugs.kde.org/show_bug.cgi?id=345412#c51), just remove it and check for / apply updates. I recently received libkf5wallet-bin - 5.71.0-0xneon+18.04+bionic+build49 libkf5wallet-data - 5.71.0-0xneon+18.04+bionic+build49 libkf5wallet5 - 5.71.0-0xneon+18.04+bionic+build49 libkwalletbackend5-5 - 5.71.0-0xneon+18.04+bionic+build49 kwalletmanager- 4:20.04.2-0xneon+18.04+bionic+build37 libpam-kwallet5 - 4:5.19.1-0xneon+18.04+bionic+build52 libpam-kwallet-common - 4:5.19.1-0xneon+18.04+bionic+build52 on my KDE Neon 5.19 machine and wallet can be opened just like before. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 421007] New: Crash on right-click in file tab-header
https://bugs.kde.org/show_bug.cgi?id=421007 Bug ID: 421007 Summary: Crash on right-click in file tab-header Product: kile Version: 2.9.92 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: karsten.k...@gmx.de Target Milestone: --- Application: kile (2.9.92) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-8-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: This crash happens when right-clicking the tab header of a file in an openend Kile project The crash can be reproduced every time. -- Backtrace: Application: Kile (kile), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff8fd7184c0 (LWP 34627))] Thread 9 (Thread 0x7ff8e0a3b700 (LWP 34636)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e91533f38) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558e91533ee8, cond=0x558e91533f10) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558e91533f10, mutex=0x558e91533ee8) at pthread_cond_wait.c:655 #3 0x7ff8e5e4251b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7ff8e5e42397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7ff904b8efa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff907a7a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7ff8e123c700 (LWP 34635)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e91533dd8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558e91533d88, cond=0x558e91533db0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558e91533db0, mutex=0x558e91533d88) at pthread_cond_wait.c:655 #3 0x7ff8e5e4251b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7ff8e5e42397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7ff904b8efa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff907a7a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7ff8e1a3d700 (LWP 34634)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e91533c78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558e91533c28, cond=0x558e91533c50) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558e91533c50, mutex=0x558e91533c28) at pthread_cond_wait.c:655 #3 0x7ff8e5e4251b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7ff8e5e42397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7ff904b8efa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff907a7a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ff8e223e700 (LWP 34633)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e91533b18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558e91533ac8, cond=0x558e91533af0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558e91533af0, mutex=0x558e91533ac8) at pthread_cond_wait.c:655 #3 0x7ff8e5e4251b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7ff8e5e42397 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7ff904b8efa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff907a7a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff8f496e700 (LWP 34632)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e90f5bab0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558e90f5ba60, cond=0x558e90f5ba88) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x558e90f5ba88, mutex=0x558e90f5ba60) at pthread_cond_wait.c:655 #3 0x7ff904e5e21b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558e90f5ba60) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x558e90f5b8a8, mutex=mutex@entry=0x558e90f5b8a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7ff907da4125 in KileParser::ParserThread::run (this=0x558e90f5b870) at ./src/parser/parserthread.cpp:169 #6 0x7ff904e5da67 in QThreadPrivate::start (arg=0x558e90f5b870) at thread/qthread_unix.cpp:367 #7 0x7ff904b8efa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7ff907a7a4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff8f516f700 (LWP 34631)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e90f481a0)
[kmail2] [Bug 383279] Kmail unnecessarily prompts for passwords
https://bugs.kde.org/show_bug.cgi?id=383279 --- Comment #5 from Karsten Künne --- It got better in kmail-17.12.3 (Leap 15.0) but it still occasionally prompts for password despite GSSAPI authentication. I think I got the prompt on startup and sometimes if I click "Check Mail" or so. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397349] New: PgUp/PgDown doesn't work in message preview
https://bugs.kde.org/show_bug.cgi?id=397349 Bug ID: 397349 Summary: PgUp/PgDown doesn't work in message preview Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: kue...@rentec.com Target Milestone: --- In kmail-17.12.3 (Opensuse Leap 15.0) the PgUp/PgDown keys are broken in the message preview. They only scroll the message one page and no more. If I scroll down further with the arrow key or mouse and then hit PgDown it actually goes UP to more or less one page down from the top. This is new in this version, version 17.04.2 (Opensuse 42.3) was working correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402527] New: Plasma crashes (but successfully restarts) after waking from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=402527 Bug ID: 402527 Summary: Plasma crashes (but successfully restarts) after waking from suspend to RAM Product: plasmashell Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: karsten@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.11-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: After waking the system from suspend to RAM and entering the PW at the lockscreen, plasma always crashes and needs to restart itself. While that works it usually takes one or two open programs with it, most often Thunderbird. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd5fe0005c0 (LWP 1619))] Thread 25 (Thread 0x7fd524bec700 (LWP 13546)): #0 0x7fd6033fcc21 in poll () at /usr/lib/libc.so.6 #1 0x7fd601700540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd60170062e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd60392f5c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd6038d858c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd60371c5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd60371d9cc in () at /usr/lib/libQt5Core.so.5 #7 0x7fd602624a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd603407b23 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fd5273ff700 (LWP 13538)): #0 0x7fd6033f87a4 in read () at /usr/lib/libc.so.6 #1 0x7fd6016ae971 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd6016ff0b0 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fd6017004e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fd60170062e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fd60392f5c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fd6038d858c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fd60371c5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fd60371d9cc in () at /usr/lib/libQt5Core.so.5 #9 0x7fd602624a9d in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fd603407b23 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fd526bfe700 (LWP 5114)): #0 0x7fd60262aafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd603723adc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fd603723bca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fd6054664cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd60546673c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fd60371d9cc in () at /usr/lib/libQt5Core.so.5 #6 0x7fd602624a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fd603407b23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fd4f1cff700 (LWP 29046)): #0 0x7fd60262aafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd603723adc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fd603723bca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fd6054664cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd60546673c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fd60371d9cc in () at /usr/lib/libQt5Core.so.5 #6 0x7fd602624a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fd603407b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fd52700 (LWP 28919)): #0 0x7fd60262aafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd603723adc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fd603723bca in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fd6054664cd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd60546673c in () at /usr/lib/libQt5Quick.so.5 #5 0x7fd60371d9cc in () at /usr/lib/libQt5Core.so.5 #6 0x7fd602624a9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fd603407b23 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fd51c9e9700 (LWP 23941)): #0 0x7fd60262aafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd603723adc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/li
[konsole] [Bug 402863] New: copy and paste stops working after a while
https://bugs.kde.org/show_bug.cgi?id=402863 Bug ID: 402863 Summary: copy and paste stops working after a while Product: konsole Version: 18.08.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: kue...@rentec.com Target Milestone: --- SUMMARY If I run konsole for a while, usually several weeks, it suddenly stops copying text to the clipboard or primary selection. I select some text with the left mouse button and paste it with the middle mouse button but instead of the selected text I get something older which was selected previously. I can select whatever I want with the left button but I always get the same old selection with the middle button paste. It also doesn't matter if I use the Copy menu entry, same result. It looks as if the copy to primary selection function stops working. If I change the primary selection via some other means and paste into konsole I get the changed content. If I start a new window from the konsole File menu it inherits the broken copy. If I start a fresh konsole it works normal. STEPS TO REPRODUCE 1. run konsole for some time, probably weeks 2. select some text 3. paste text into konsole OBSERVED RESULT some old selection is pasted EXPECTED RESULT the newly selected text should be pasted SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: openSUSE build service packages (available in About System) KDE Plasma Version: 5.51 KDE Frameworks Version: 5.51 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server
https://bugs.kde.org/show_bug.cgi?id=375445 Karsten Künne changed: What|Removed |Added CC||kue...@rentec.com --- Comment #5 from Karsten Künne --- I have the same problem with kmail 17.04.2 (openSUSE Leap 42.3). I haven't figured out the limit yet, it seems to be around 1.2 MB. Every message larger than that is not displayed in the preview window. I have to use "View Source" in order to see it. This is only one of the annoying bugs of kmail besides the ugly scrollbar and the flickering of the preview window caused by the html sidebar, the non-printing support, and others. I'm very close to the breaking point in giving up on kmail. It seems to getting worse with every release. (Sorry for the rant) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 383279] New: Kmail unnecessarily prompts for passwords
https://bugs.kde.org/show_bug.cgi?id=383279 Bug ID: 383279 Summary: Kmail unnecessarily prompts for passwords Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: kue...@rentec.com Target Milestone: --- Since I upgraded Kmail from 16.08.2 to 17.04.2 (openSUSE Leap 42.2 to 42.3) Kmail prompts me for passwords on my IMAP accounts every 10 minutes or so. All of my IMAP accounts are configured to use GSSAPI authentication and don't use a password at all (they use my Kerberos ticket for authentication). I have to click OK with an empty password field in order to make the password window disappear. This is very annoying and it started with openSUSE 42.3, Kmail 17.04.2. It could also be Akonadi or some other component doing the password prompting, I can't really tell. The end result is the same for me. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385103] New: kstars/ekos capture folder problem
https://bugs.kde.org/show_bug.cgi?id=385103 Bug ID: 385103 Summary: kstars/ekos capture folder problem Product: kstars Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: ke...@gmx.de Target Milestone: --- Created attachment 108042 --> https://bugs.kde.org/attachment.cgi?id=108042&action=edit screenshot of the dialog running under stellarmate Hi, when using the capture an the local machine (device with the camera) and setting the folder "remote" the folder somehow becomes incorrect. "/mnt/nfs-berlin/stellarmate/library" (tailing slash does not improve the situation) Bias should go to "/mnt/nfs-berlin/stellarmate/library/Bias" But instead it somehow repeats the path for each B i a s letter. "/mnt/nfs-berlin/stellarmate/library/mnt/nfs-berlin/stellarmate/libraryB/mnt/nfs-berlin/stellarmate/libraryi/mnt/nfs-berlin/stellarmate/librarya/mnt/nfs-berlin/stellarmate/librarys/mnt/nfs-berlin/stellarmate/library/g0_b10_Bias_005.fits" The path is also broken in the indi control panel. (So posting the bug here) The folder naming is somewhat confusing as well: upload "local" and "remote" vs. upload "client" and "directory" Used StellarMate OS updated to the latest build. "2017-09-24T13:09:54Z" Best regards Karsten -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 385103] kstars/ekos capture folder problem
https://bugs.kde.org/show_bug.cgi?id=385103 --- Comment #1 from Karsten Elfenbein --- The trigger seems to be that the "Directory" field is empty. -- You are receiving this mail because: You are watching all bug changes.
[knetwalk] [Bug 352039] knetwalk: bogus initialization right after launch
https://bugs.kde.org/show_bug.cgi?id=352039 Karsten Berg changed: What|Removed |Added CC||karsten.b...@synergy2k.de --- Comment #6 from Karsten Berg --- Bug is still present in 3.3.23085 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 498159] New: Flatpack Start gives "Qt: Session management error: Could not open network socket"
https://bugs.kde.org/show_bug.cgi?id=498159 Bug ID: 498159 Summary: Flatpack Start gives "Qt: Session management error: Could not open network socket" Classification: Applications Product: kdiff3 Version: 1.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: edk-gnickartgub-20250...@gresch.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install kdiff3 from Flatpack () 2. Run ``` flatpak run org.kde.kdiff3 ``` 3. Select two arbitrary local directories. OBSERVED RESULT I received the following error messages: ``` Qt: Session management error: Could not open network socket kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" ``` Furthermore, instead of displaying the different directory contents, kdiff3 showed in each pane the message "Encoding: Line end style: Unkown" EXPECTED RESULT - No error messages. - Different directory content displayed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.11.0-108013-tuxedo (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 497340] When run from command line, kdiff3 always fails to open the second file
https://bugs.kde.org/show_bug.cgi?id=497340 Karsten Düsterloh changed: What|Removed |Added CC||mnyro...@tprac.de -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482790] Strange graphical issues make usage near impossible
https://bugs.kde.org/show_bug.cgi?id=482790 --- Comment #18 from Karsten Düsterloh --- Just to chime in why I kinda woke the wolves here yesterday: - Basically I'm using Lubuntu 24.10. - I was using LXDE with a 1920x1200 layout until last week. kdiff3 ran without problems. - Last week I switched to XFCE (LXDE being essentially dead by now). I also got a new monitor with 3840x2160 layout, and kdiff3 acted weird. While kdiff3 in LXDE is still running normally even with that resolution, it's broken in XFCE: - image scrollbars are completely black or showing kinda "noise" - toolbar icons are cut off - menu frames are cut off - clicking to select a section doesn't work most of the time But: Using Raphael's DPI settings from comment #17 above, it's working (and looking) well again! :) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482790] Strange graphical issues make usage near impossible
https://bugs.kde.org/show_bug.cgi?id=482790 Karsten Düsterloh changed: What|Removed |Added CC||mnyro...@tprac.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] New: digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
Bug ID: 440590
Summary: digikam 7.3.0 fails to start: cannot process schema
initialization
Product: digikam
Version: 7.3.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: Database-Schema
Assignee: digikam-bugs-n...@kde.org
Reporter: karsten.defre...@posteo.de
Target Milestone: ---
SUMMARY
After installing OpenSUSE tumbleweed snapshot 20210727 (which provides digikam
7.3.0) on top of an earlier installation with digikam 7.2.0, digikam fails to
start during 'scanning collections'with GUI message
"Failed to update the database schema from version 12 to version 13. Please
read the error messages printed on the console and report this error as a bug
at bugs.kde.org."
STEPS TO REPRODUCE
1. a digikam 7.2.0 installation from e.g. tumbleweed snapshot 20210712, with a
local mySQL database, and some 10k pictures on a server in a local network
2. update to a snapshot with digikam 7.3.0 (I used 20210727)
3. try to start digikam
OBSERVED RESULT
GUI message:
"Failed to update the database schema from version 12 to version 13. Please
read the error messages printed on the console and report this error as a bug
at bugs.kde.org."
CLI message:
karsten@osl-i5:~> digikam -v
digikam 7.3.0
karsten@osl-i5:~> export QT_LOGGING_RULES="digikam*=true"
karsten@osl-i5:~> digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: Internal database server started
digikam.databaseserver: Running 0 seconds...
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 12
digikam.coredb: Core database: makeUpdates 12 to 13
digikam.dbengine: Failure executing query:
""
Error messages: "QMYSQL: Unable to execute query" "Column count of mysql.proc
is wrong. Expected 21, found 20. Created with MariaDB 100215, now running
100510. Please use mariadb-upgrade to fix this error" "1558" 2
Bound values: ()
digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ]
Statement [ "\nDROP PROCEDURE IF EXISTS
create_index_if_not_exists;\n" ]
d
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #3 from Karsten de Freese --- Thanks for the ultra-quick reply, which helped me move on, but with no good result yet.. - I tried the manual update first. Directory /home/karsten/.local/share/digikam/db_misc/ was empty, and probably because of this the upgrade fails (as described by Jens in one of his earlier posts). - Then I downloaded the 7.4.0 AppImage. It did actually produce the same GUI error messages as the 7.3.0 installation. - Erroneously, I started the manual update again while the GUI error messages from the 7.4.0 AppImage were still open, and the manual update succeeded then. - After closing the 7.4.0 error messages I started the installed 7.3.0 version, which produced: "An error occurred during the internal server start. Details: Database process exited unexpectedly during initial connection.Executable: /usr/sbin/mysqldArguments: --defaults-file=/home/karsten/.local/share/digikam/mysql.conf, --datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data, --socket=/home/karsten/.local/share/digikam/db_misc/mysql.socketProcess error: Process crashed" but after closing the error message and confirming the database configuration, digikam continued to start up correctly ONCE. A second start of digikam however resulted in the same error messsage. Closing the message window brings up the database configuration window, and confirming the current configuration brings back the error message etc. etc. The path to db files is set to /var/lib/digikam_db/MySQL. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #5 from Karsten de Freese --- A restart did not change the situation unfortunately, and trying to run the manual update command while the installed 7.3.0 was showing its error message still did not work (this is what I understood from https://mail.kde.org/pipermail/digikam-users/2021-July/032479.html): karsten@osl-i5:~> mariadb-upgrade --socket=/home/karsten/.local/share/digikam/db_misc/ Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/home/karsten/.local/share/digikam/db_misc/' (111) FATAL ERROR: Upgrade failed (Actually directory /home/karsten/.local/share/digikam/db_misc/ is empty at this moment.) When I start the 7.4.0 AppImage, I get the same error message, and when closing the message, the 'Database Configuration' window shows mysqld as missing. Does this point to something? Which Mariadb server version should I have installed? Currently this is 10.5.10. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
--- Comment #7 from Karsten de Freese ---
ok, I think that's what I've done, but let's try again..
I start 7.3.0 via CLI:
- on the CLI:
karsten@osl-i5:~/Downloads> digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name: "digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: "Database process exited unexpectedly during initial
connection."
digikam.databaseserver: Executable: "/usr/sbin/mysqld"
digikam.databaseserver: Arguments:
"--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
digikam.databaseserver: Stdout: ""
digikam.databaseserver: Stderr: "2021-08-04 21:31:44 0 [Note] /usr/sbin/mysqld
(mysqld 10.5.10-MariaDB-log) starting as process 16738 ...\n"
digikam.databaseserver: Exit code: 6
digikam.databaseserver: Process error: "Process crashed"
digikam.databaseserver: Cannot start internal database server
- an error popup window occurs with text "... Database process exited
unexpectedly during initial connection.Executable:
/usr/sbin/mysqldArguments:
--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socketProcess
error: Process crashed"
- I keep the error popup as it is and start the upgrade in a 2nd terminal:
karsten@osl-i5:/data/karsten/Downloads> mariadb-upgrade
--socket=/home/karsten/.local/share/digikam/db_misc/
Version check failed. Got the following error when calling the 'mysql' command
line client
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/home/karsten/.local/share/digikam/db_misc/' (111)
FATAL ERROR: Upgrade failed
(-- no new output on the digikam CLI)
- I click ok on the error message, then the 'Database Configuration' dialog
appears:
-- location of database files: /var/lib/digikam_db/MySQL
-- all mysql binaries have checkmarks in the first column
-- on the digikam CLI:
digikam.general: Testing "mysql_install_db" ...
digikam.general: Found "mysql_install_db"
digikam.general: Testing "mysqladmin" ...
digikam.general: Found "mysqladmin"
digikam.general: Testing "mysqld" ...
digikam.general: Testing "mysqld" ...
digikam.general: Testing "/usr/bin/mysqld" ...
digikam.general: All Binaries Found : false
digikam.general: Testing "/usr/s
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #9 from Karsten de Freese --- under /var/lib/digikam_db/MySQL there is (only) .mysql.digikam/db_data/: karsten@osl-i5:~/Downloads> ls -al /var/lib/digikam_db/MySQL/.mysql.digikam/db_data/ total 156M drwxr-xr-x 1 karsten karsten 736 Aug 4 22:36 . drwxr-xr-x 1 karsten karsten 14 Jul 6 2018 .. drwx-- 1 karsten karsten 2,5K Aug 4 18:51 digikam drwx-- 1 karsten karsten 2,7K Aug 4 18:23 mysql drwx-- 1 karsten karsten 12 Aug 4 18:23 performance_schema drwx-- 1 karsten karsten0 Jul 6 2018 test -rw-rw 1 karsten karsten 80K Aug 4 18:39 aria_log.0001 -rw-rw 1 karsten karsten 52 Aug 4 18:39 aria_log_control -rw-rw 1 karsten karsten 9,1K Aug 4 18:39 ib_buffer_pool -rw-rw 1 karsten karsten 76M Aug 4 18:39 ibdata1 -rw-rw 1 karsten karsten 64M Aug 4 22:36 ib_logfile0 -rw-rw 1 karsten karsten 12M Aug 4 22:36 ibtmp1 -rw-rw 1 karsten karsten0 Jul 6 2018 multi-master.info -rw-rw 1 karsten karsten 1,7K Aug 4 16:01 mysql-bin.000141 -rw-rw 1 karsten karsten 1,7K Aug 4 16:01 mysql-bin.000142 -rw-rw 1 karsten karsten 1,7K Aug 4 16:07 mysql-bin.000143 -rw-rw 1 karsten karsten 2,9K Aug 4 16:59 mysql-bin.000144 -rw-rw 1 karsten karsten 365 Aug 4 16:59 mysql-bin.000145 -rw-rw 1 karsten karsten 1,7K Aug 4 16:59 mysql-bin.000146 -rw-rw 1 karsten karsten 1,7K Aug 4 17:16 mysql-bin.000147 -rw-rw 1 karsten karsten 2,9K Aug 4 18:13 mysql-bin.000148 -rw-rw 1 karsten karsten 342 Aug 4 18:13 mysql-bin.000149 -rw-rw 1 karsten karsten 1,6K Aug 4 18:15 mysql-bin.000150 -rw-rw 1 karsten karsten 49K Aug 4 18:39 mysql-bin.000151 -rw-rw 1 karsten karsten 209 Aug 4 18:30 mysql-bin.index -rw-rw 1 karsten karsten 11 Aug 4 18:39 mysql-bin.state -rw-rw 1 karsten karsten 8,7K Aug 4 22:36 mysql.err -rw-r--r-- 1 karsten karsten 3,3M Aug 4 22:36 mysql.err.old -rw-r--r-- 1 karsten karsten 16 Aug 4 18:23 mysql_upgrade_info is this what's expected? Anyway, I'm afraid that my configuration is indeed corrupted by now. So I should see what I can collect from backups now, and restart with a 7.2.0 AppImage just to have a clean start. Could you point me to the files/directories I'd need to recover? - $HOME/.local/share/digikam/ - the Internal Server Path (currently set to "/var/lib/digikam_db/MySQL" in my config) (is this the same path configred in the 'Database Configuration' dialogue?) - probably some more? Thanks very much for your help! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590
--- Comment #11 from Karsten de Freese ---
No success yet - I could restore the original behaviour, and run the manual
upgrade,
but digikam fails to start with the upgraded database.
This is what I did (all using the installed copy of digikam 7.3.0):
- I restored
-- $HOME/.local/share/digikam/
-- $HOME/.config/digikam*
-- the database directory (/var/lib/digikam_db in my case)
to the state before the update.
- I started digikam 7.3.0 (local installation)
The original error messages popped up - so far as expected.
("Failed to update the database schema from version 12 to version 13...")
- while the error messages were still shown, a manual database upgrade ran
successfully
("mariadb-upgrade
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
- I clicked ok the digikam error messages and digikam terminated after a while
=> so far so good
- BUT: Starting digikam again did result in the error seen yesterday:
"An error occurred during the internal server start.
Details:
Database process exited unexpectedly during initial connection.
Executable: /usr/sbin/mysqld
Arguments: --defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket
Process error: Process crashed"
(formatting by myself)
The debug output in the terminal at this point:
digikam.widgets: Use installed icons
digikam.general: Switch to widget style: ""
digikam.general: Switch to application font: QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Database Parameters:
Type: "QMYSQL"
DB Core Name: "digikam"
DB Thumbs Name:"digikam"
DB Face Name: "digikam"
DB Similarity Name:"digikam"
Connect Options:
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
Host Name: ""
Host port: -1
Internal Server: true
Internal Server Path: "/var/lib/digikam_db/MySQL"
Internal Server Admin Cmd: "mysqladmin"
Internal Server Serv Cmd: "/usr/sbin/mysqld"
Internal Server Init Cmd: "mysql_install_db"
Username: "root"
Password: ""
digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: "Database process exited unexpectedly during initial
connection."
digikam.databaseserver: Executable: "/usr/sbin/mysqld"
digikam.databaseserver: Arguments:
"--defaults-file=/home/karsten/.local/share/digikam/mysql.conf,
--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data,
--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
digikam.databaseserver: Stdout: ""
digikam.databaseserver: Stderr: "2021-08-05 12:13:56 0 [Note] /usr/sbin/mysqld
(mysqld 10.5.10-MariaDB-log) starting as process 29222 ...\n"
digikam.databaseserver: Exit code: 6
digikam.databaseserver: Process error: "Process crashed"
digikam.databaseserver: Cannot start internal database server
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 440590] digikam 7.3.0 fails to start: cannot process schema initialization
https://bugs.kde.org/show_bug.cgi?id=440590 --- Comment #12 from Karsten de Freese --- Finally, success :-) Basically following the same process as below, I used a 7.2.0 AppImage to open the database (as opposed to the installed 7.3.0). After the manual upgrade was run, and the 7.2.0 AppImage terminated, I could successfully launch 7.3.0 without obvious issues so far. So the key point appears to be to use a *working* digikam installation to open the database before upgrade. Maybe this has impact on the automatic update to be built into 7.4.0? Thanks again for your support! - Karsten -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476578] New: digikam crashes when opening 'Tools' menu
https://bugs.kde.org/show_bug.cgi?id=476578 Bug ID: 476578 Summary: digikam crashes when opening 'Tools' menu Classification: Applications Product: digikam Version: 8.1.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: karsten.defre...@posteo.de Target Milestone: --- Application: digikam (8.1.0) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: - started digikam - opened 'Tools' menu, no other action yet - digikam crashed => repeated two times with same result, while the check for new items was still running => another attempt when the check for new items was already finished did not lead to a crash Specific system settings: external mariadb, shared with Win10 installation (as per https://mail.kde.org/pipermail/digikam-users/2018-March/026586.html) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 0x7f377ef04e76 in () at /lib64/libQt5Core.so.5 #5 0x7f3781921be4 in Digikam::Album::childAtRow(int) const () at /lib64/libdigikamgui.so.8.1.0 #6 0x7f3781914955 in Digikam::AbstractAlbumModel::index(int, int, QModelIndex const&) const () at /lib64/libdigikamgui.so.8.1.0 #7 0x7f378193b400 in () at /lib64/libdigikamgui.so.8.1.0 #8 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #9 0x7f377f085ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /lib64/libQt5Core.so.5 #10 0x7f377f08ef4a in QAbstractItemModel::endInsertRows() () at /lib64/libQt5Core.so.5 #11 0x7f377f0bc595 in () at /lib64/libQt5Core.so.5 #12 0x7f377f0c0465 in () at /lib64/libQt5Core.so.5 #13 0x7f377f0c36bd in () at /lib64/libQt5Core.so.5 #14 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #15 0x7f377f085ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () at /lib64/libQt5Core.so.5 #16 0x7f377f08ef4a in QAbstractItemModel::endInsertRows() () at /lib64/libQt5Core.so.5 #17 0x7f37819101e5 in Digikam::AbstractAlbumModel::slotAlbumAdded(Digikam::Album*) () at /lib64/libdigikamgui.so.8.1.0 #18 0x7f377f125442 in () at /lib64/libQt5Core.so.5 #19 0x7f3781918052 in Digikam::AlbumManager::signalAlbumAdded(Digikam::Album*) () at /lib64/libdigikamgui.so.8.1.0 #20 0x7f378194ec4a in Digikam::AlbumManager::scanPAlbums() () at /lib64/libdigikamgui.so.8.1.0 #21 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #22 0x7f377f12921a in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #23 0x7f377f118e5b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7f377fda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #25 0x7f377f0ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #26 0x7f377f1454c9 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #27 0x7f377f145d74 in () at /lib64/libQt5Core.so.5 #28 0x7f3771913f30 in () at /lib64/libglib-2.0.so.0 #29 0x7f3771915b58 in () at /lib64/libglib-2.0.so.0 #30 0x7f377191620c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #31 0x7f377f1460d6 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #32 0x7f377f0ebc2b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #33 0x7f377ffadc67 in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #34 0x7f378182f7c1 in Digikam::DigikamApp::slotMaintenance() () at /lib64/libdigikamgui.so.8.1.0 #35 0x7f377f1253e3 in () at /lib64/libQt5Core.so.5 #36 0x7f377fd9e8b2 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #37 0x7f377fda142f in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #38 0x7f377ff25f02 in () at /lib64/libQt5Widgets.so.5 #39 0x7f377ff2dd33 in () at /lib64/libQt5Widgets.so.5 #40 0x7f377fde6d58 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #41 0x7f377fda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #42 0x7f377fdad5cf in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #43 0x7f377f0ed198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #44 0x7f377fdab92e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #45 0x7f377fe002ba in () at /lib64/libQt5Widgets.so.5 #46 0x7f377
[digikam] [Bug 476578] digikam crashes when opening 'Tools' menu
https://bugs.kde.org/show_bug.cgi?id=476578 --- Comment #3 from Karsten de Freese --- the 8.2.0 AppImage seems to work fine so far. I'll wait for the official release to update my installations (Linux and Win10), to avoid database incompatibilities between the versions. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date
https://bugs.kde.org/show_bug.cgi?id=345565 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de --- Comment #4 from Karsten de Freese --- still an issue with Korganizer 5.12.3 (I'm using Tumbleweed) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 --- Comment #4 from Karsten de Freese --- still an issue with Korganizer 5.12.3 (I'm using Tumbleweed) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 --- Comment #5 from Karsten de Freese --- It appears that the problems can be worked around under specific conditions: - have start & due dates on the same day (e.g. via different times) - save the to-do before entering the recurrence -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date
https://bugs.kde.org/show_bug.cgi?id=345565 --- Comment #5 from Karsten de Freese --- It appears that the problems can be worked around under specific conditions: - have start & due dates on the same day (e.g. via different times) - save the to-do before entering the recurrence -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416838] Crash when using nm-widget to connect to wifi network
https://bugs.kde.org/show_bug.cgi?id=416838 Karsten Sperling Opdal changed: What|Removed |Added CC||palette...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 390024] "Compare" button not enabled on the initial dialog even after filling the file names
https://bugs.kde.org/show_bug.cgi?id=390024 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 375291] New: Crash when closing disover
https://bugs.kde.org/show_bug.cgi?id=375291 Bug ID: 375291 Summary: Crash when closing disover Product: Discover Version: 5.8.95 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: palette...@hotmail.com Target Milestone: --- Application: plasma-discover (5.8.95) Qt Version: 5.7.0 Frameworks Version: 5.31.0 Operating System: Linux 4.4.0-59-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: Closeing the app causes crash - happens all the time now. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd60f6e8c0 (LWP 12101))] Thread 8 (Thread 0x7fccb0b8b700 (LWP 12144)): #0 0x7fcd5d61a69d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcd590df740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcd5909be84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcd5909c340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcd5909c722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fccf0555916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fcd590c2bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fcd5af616ba in start_thread (arg=0x7fccb0b8b700) at pthread_create.c:333 #8 0x7fcd5d62a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fccb138c700 (LWP 12143)): #0 0x7fcd5d61eb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcd5909c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcd5909c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcd5909c4e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcd590c2bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcd5af616ba in start_thread (arg=0x7fccb138c700) at pthread_create.c:333 #6 0x7fcd5d62a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fcd15ffb700 (LWP 12121)): #0 0x7fcd5d61a69d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcd590df740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcd5909be84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcd5909c340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcd5909c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcd5e25223b in QEventDispatcherGlib::processEvents (this=0x7fcd08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fcd5e1fccea in QEventLoop::exec (this=this@entry=0x7fcd15ffad00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #7 0x7fcd5e021fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #8 0x7fcd5e026b98 in QThreadPrivate::start (arg=0x2229280) at thread/qthread_unix.cpp:344 #9 0x7fcd5af616ba in start_thread (arg=0x7fcd15ffb700) at pthread_create.c:333 #10 0x7fcd5d62a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fcd303b1700 (LWP 12110)): #0 0x7fcd590994a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcd5909b9a8 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcd5909c2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcd5909c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcd5e25223b in QEventDispatcherGlib::processEvents (this=0x7fcd280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fcd5e1fccea in QEventLoop::exec (this=this@entry=0x7fcd303b0d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #6 0x7fcd5e021fb4 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7fcd5e026b98 in QThreadPrivate::start (arg=0x2220f30) at thread/qthread_unix.cpp:344 #8 0x7fcd5af616ba in start_thread (arg=0x7fcd303b1700) at pthread_create.c:333 #9 0x7fcd5d62a82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fcd4536c700 (LWP 12109)): #0 0x7fcd5d61eb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcd5909c39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcd5909c4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcd5e25223b in QEventDispatcherGlib::processEvents (this=0x7fcd3c002e00, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fcd5e1fccea in QEventLoop::exec (this=this@entry=0x7fcd4536bc90, flags=..., flags@entry=...
[digikam] [Bug 376351] New: create a tool to automatically group jpeg and raw images with same name
https://bugs.kde.org/show_bug.cgi?id=376351 Bug ID: 376351 Summary: create a tool to automatically group jpeg and raw images with same name Product: digikam Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: kars...@maxi-dsl.de Target Milestone: --- hi digikam team, I've just moved my photo collection from shotwell to digikam, for the fantastic number of interesting features, and most importantly, the option to use a central mysql database. There's one thing I’m missing though, and I may very well just not have found out how to do it: I'd like to group jpeg and raw files of the same photo, as I usually have my camera set to produce both formats for each shot. With my existing photo collection, it's not really feasible to do this by hand. I've seen ticket 126149, but I'm not able to find the functionality I understand from this ticket in digikam 5.4 - instead, grouping images by file type (view/group pictures/by format) just separates them into two lists for jpeg and raw. So what am I looking for: - a way to combine files with same filename, but different 'picture type' extensions into a group (in my & similar cases it will be exactly two files with the same date/time, and extensions .JPG and e.g. .ORF) - either put the .JPG on top or make it configurable - this could be done automatically for all jpeg/raw pairs (I understand that this is what is described in 126149?) - or as a BQM tool to be run manually (in this case, ideally this functionality should also be available during image download) There are quite some similar feature requests, most already resolved, so please excuse me if I just don't see the obvious.. thanks for looking into this - Karsten -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376351] create a tool to automatically group jpeg and raw images with same name
https://bugs.kde.org/show_bug.cgi?id=376351 --- Comment #5 from Karsten de Freese --- thanks for the quick help! 'context menu select group -> group selected by type' did exactly what I was looking for. This function did not catch my attention before, probably because I was assuming that it would do the same thing as 'view -> group pictures -> by format', instead of the slightly different wording. With the changed UI string this will certainly be more obvious..! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398227] New: Crash on start
https://bugs.kde.org/show_bug.cgi?id=398227 Bug ID: 398227 Summary: Crash on start Product: Discover Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: palette...@hotmail.com Target Milestone: --- Application: plasma-discover (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.17.8-041708-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Starting the application The applicaton shows the initial windows with no content (bitmap of the desktop). The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5897d9f800 (LWP 25719))] Thread 11 (Thread 0x7f584b7fe700 (LWP 25730)): #0 0x7f589336fbf9 in __GI___poll (fds=0x7f58400018a0, nfds=1, timeout=8884) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f588db62439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f588db6254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5893cbd90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5893c629ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5893a8122a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5893a8616d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f588fc8f6db in start_thread (arg=0x7f584b7fe700) at pthread_create.c:463 #8 0x7f589337c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f5850f91700 (LWP 25728)): #0 0x7f589336fbf9 in __GI___poll (fds=0x55cfa73e9130, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f588db62439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f588db627d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5852dcfe76 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f588db89e05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f588fc8f6db in start_thread (arg=0x7f5850f91700) at pthread_create.c:463 #6 0x7f589337c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f5851792700 (LWP 25727)): #0 0x7f589336fbf9 in __GI___poll (fds=0x55cfa735be30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f588db62439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f588db6254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f588db62591 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f588db89e05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f588fc8f6db in start_thread (arg=0x7f5851792700) at pthread_create.c:463 #6 0x7f589337c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f5860abc700 (LWP 25726)): #0 0x7f588fc95ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f5860abbc40, expected=0, futex_word=0x7f5854006df0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f588fc95ed9 in __pthread_cond_wait_common (abstime=0x7f5860abbd00, mutex=0x7f5854006da0, cond=0x7f5854006dc8) at pthread_cond_wait.c:533 #2 0x7f588fc95ed9 in __pthread_cond_timedwait (cond=0x7f5854006dc8, mutex=0x7f5854006da0, abstime=0x7f5860abbd00) at pthread_cond_wait.c:667 #3 0x7f5893a87458 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5893a8352d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5893a8616d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f588fc8f6db in start_thread (arg=0x7f5860abc700) at pthread_create.c:463 #7 0x7f589337c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f58612bd700 (LWP 25725)): #0 0x7f589336fbf9 in __GI___poll (fds=0x7f58540049b0, nfds=1, timeout=113884) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f588db62439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f588db6254c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5893cbd90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5893c629ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5893a8122a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5893a8616d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f588fc8f6db in star
[korganizer] [Bug 345498] monthly To-do given incorrect start and due dates
https://bugs.kde.org/show_bug.cgi?id=345498 Karsten de Freese changed: What|Removed |Added CC||kars...@maxi-dsl.de --- Comment #2 from Karsten de Freese --- I can confirm this issue with KOrganizer 5.3 KDE Applications 16.08.2 OpenSUSE leap 42.2 also for other frequencies of recurrence. When setting up a non-recurring to-do, everything seems to work as expected - I can set start dates, due dates and reminders without the different settings influencing each other. However if the to-do is set to recurring, response to the settings is erratic. An example: - I set up a to-do, starting the next day (at a specific time), and due one day later. A reminder is set at 15min before due time. - the to-do is shown correctly in the to-do list view, and also more detailed via the 'show' context menu entry - when I add a weekly recurrence, start and due dates are mysteriously moved by two days in the to-do list view, while via the 'show' context menu only the due date is shifted, and only by one day.. In other cases I've also seen the reminder being changed in addition, recurrence setting being greyed out, or also an error messages when trying to save the modified task (something like 'only allocated resources are allowed to make changes', I can't reproduce this right now). The behavior does seem independent of the calendar type I select - local personal calendar vs. CalDAV -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 318357] GROUP : group by file-names [patch]
https://bugs.kde.org/show_bug.cgi?id=318357 Karsten de Freese changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #20 from Karsten de Freese --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 503894] Unable to connect to MySQL database from Digikam on openSUSE Tumbleweed after update
https://bugs.kde.org/show_bug.cgi?id=503894 Karsten de Freese changed: What|Removed |Added CC||karsten.defre...@posteo.de --- Comment #17 from Karsten de Freese --- Tomas, I hope it's ok if I jump into this ticket - I ran into the same problem after last Tumbleweed update. Would mind directing me to some information what needs to be done to set up ssl / TLS correctly? I understand that mariadb does this for a long time already by default (using self-generated certificates), so I guess I'd need to change my digikam database configuration? Thanks - Karsten -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 503894] Unable to connect to MySQL database from Digikam on openSUSE Tumbleweed after update
https://bugs.kde.org/show_bug.cgi?id=503894 --- Comment #19 from Karsten de Freese --- I've been able to resolve my problem in the meantime - 1st of all, I was wrong in assuming that the mariadb version installed on my server already provides TLS connections with self-generated certificates - this is only with a very recent version of mariadb I cannot use for other reasons (not supported with nextcloud) - So I configured mariadb TLS with the certificates I'm using for a web server on the same machine. This did the trick, and digikam connects to its databases again. No changes needed in digikam's database configuration. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 503894] Unable to connect to MySQL database from Digikam on openSUSE Tumbleweed after update
https://bugs.kde.org/show_bug.cgi?id=503894 --- Comment #21 from Karsten de Freese --- hi Chad, have a look at https://mariadb.com/docs/server/security/securing-mariadb/securing-mariadb-encryption/data-in-transit-encryption/secure-connections-overview Assuming you already have TLS certificates (e.g. from letsencrypt) set up on the server that hosts the mariadb server, these are the steps that worked for me: - on the server, locate the / a mariadb configuration file (there may be more than one, which may all be evaluated) => in my case (under debian), I used '/etc/mysql/mariadb.cnf' - look for the section '[mariadb]' (if there is none, create it by putting [mariadb] at the beginning of an empty line) - In this section (so it existed) you should find a few commented-out lines, such as #ssl_cert = /etc/my.cnf.d/certificates/server-cert.pem #ssl_key = /etc/my.cnf.d/certificates/server-key.pem #ssl_ca = /etc/my.cnf.d/certificates/ca.pem - Add the links to your existing TLS certificates - in my case these were ssl_cert = /etc/letsencrypt/live//cert.pem ssl_key = /etc/letsencrypt/live//privkey.pem => note that I have not added the link to the ca.pem - this should not be needed for letsencrypt certificates - now restart mariadb to evaluate the modified configuration using your OS'es mechanism - in my case: sudo systemctl restart mariadb - if you wish, you may check if TLS was actually enabled: - login to mariadb with your admin account: sudo mariadb -u -p => you will be prompted for your admin password - on the mariadb prompt, enter SHOW GLOBAL VARIABLES LIKE 'have_ssl'; (the semicolon needs to be there) - you should see something like +--+---+ | Variable_name | Value| +--+---+ | have_ssl| YES | +--+---+ - exit mariadb: exit; That's it - digikam should now start, assuming that its databases had been created correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 karsten changed: What|Removed |Added CC||i...@dr-burger.com --- Comment #8 from karsten --- I had the same behaviour using CentOS 7.2. When I selected "Classic" bluefish instead of GPG it prompted me for a password and its confirmation, and this worked to create a kde wallet. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358751] konsole loses file descriptors and eventually runs out of them and crashes
https://bugs.kde.org/show_bug.cgi?id=358751 --- Comment #1 from Karsten Künne --- Any news on this issue? It happens every other day and is quite annoying. For instance, today: lsof -p 26307 | grep socket | wc 9638667 75114 (26307 is the pid of konsole) It basically looks like that (lsof -p 26307): ... konsole 26307 user 93u unix 0x88012e1ec400 0t0 100037400 socket konsole 26307 user 94u unix 0x8800471bdc00 0t0 100058007 socket konsole 26307 user 95u unix 0x8800471bd480 0t0 100058008 socket konsole 26307 user 96u unix 0x88016a945480 0t0 100061420 socket konsole 26307 user 97u unix 0x88000f839080 0t0 100061421 socket konsole 26307 user 98u unix 0x880178d6d480 0t0 100062430 socket konsole 26307 user 99u unix 0x880178d6dc00 0t0 100062431 socket konsole 26307 user 100u unix 0x8801201f0800 0t0 100063827 socket konsole 26307 user 101u unix 0x8801318010c0 0t0 100063828 socket konsole 26307 user 102u unix 0x8801f9a0ec00 0t0 100067538 socket (that goes on for many many more lines) konsole 26307 user 1018u unix 0x880121886c00 0t0 142460886 socket konsole 26307 user 1019u unix 0x88026debb080 0t0 142460887 socket konsole 26307 user 1020u unix 0x88004869e440 0t0 142461875 socket konsole 26307 user 1021u unix 0x880120a4cb80 0t0 142461876 socket konsole 26307 user 1022u unix 0x88021f862b80 0t0 142542903 socket konsole 26307 user 1023u unix 0x88021f8627c0 0t0 142542904 socket And it has eaten up all the file descriptors. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358751] konsole loses file descriptors and eventually runs out of them and crashes
https://bugs.kde.org/show_bug.cgi?id=358751 Karsten Künne changed: What|Removed |Added Version|unspecified |15.12.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358751] New: konsole loses file descriptors and eventually runs out of them and crashes
https://bugs.kde.org/show_bug.cgi?id=358751 Bug ID: 358751 Summary: konsole loses file descriptors and eventually runs out of them and crashes Product: konsole Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: kue...@rentec.com If I start a fresh konsole process it has 3 socket connections open. If I work for a while and then check again the number of sockets belonging to konsole increases. This is going on until konsole reaches the file descriptor limit and either won't let me open more sessions or crashes. Most of the socket connections are between itself. Following is the current situation on my desktop for instance (netstat_unix is a simple script which adds the other end of a socket to the output): ./netstat_unix | grep konsole Warning: couldn't map 4 sockets. unix 3 [ ] STREAM CONNECTED 58236419 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58236420 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58244071 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58232305 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58209503 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58196821 1997/dbus-daemon 25237/konsole @/tmp/dbus-ZwOV6P0BFv unix 3 [ ] STREAM CONNECTED 58197623 25237/konsole 2054/ksmserver unix 3 [ ] STREAM CONNECTED 58244072 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58209504 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58212918 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58236369 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58304458 665/dbus-daemon 25237/konsole /var/run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 58196824 1885/Xorg 25237/konsole @/tmp/.X11-unix/X0 unix 3 [ ] STREAM CONNECTED 58236370 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58214076 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58197618 25237/konsole 1997/dbus-daemon unix 3 [ ] STREAM CONNECTED 58215713 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58215714 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58214075 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58209509 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58212919 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58232306 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58208783 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58208784 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58209508 25237/konsole 25237/konsole unix 3 [ ] STREAM CONNECTED 58305787 25237/konsole 665/dbus-daemon unix 3 [ ] STREAM CONNECTED 58199112 2054/ksmserver [kd 25237/konsole e @/tmp/.ICE-unix/2054 unix 3 [ ] STREAM CONNECTED 58197622 25237/konsole 1885/Xorg Over time the number of sockets from konsole process 25237 to itself will continue to rise. This is with Version 15.12.0, Using: KDE Frameworks 5.16.0 Qt 5.5.1 (built against 5.5.0) The xcb windowing system on OpenSUSE Leap 42.1 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 371407] New: Unable to start KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=371407 Bug ID: 371407 Summary: Unable to start KDE Partition Manager Product: partitionmanager Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: palette...@hotmail.com Application: partitionmanager (2.2.1) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.0-45-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: - What I was doing when the application crashed: Starting application and got pass root request. The application had scan my harddrives sda sdb when it reached sdc it crashed.Drive sdc is my memory card reader. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa673bac900 (LWP 11423))] Thread 5 (Thread 0x7fa661121700 (LWP 11504)): #0 0x7fa67c9ad9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa678450740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840ce84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67840d340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa67840d722 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa66202e916 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fa678433bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa679c676fa in start_thread (arg=0x7fa661121700) at pthread_create.c:333 #8 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fa661922700 (LWP 11503)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa67840d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67840d4e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa678433bc5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa679c676fa in start_thread (arg=0x7fa661922700) at pthread_create.c:333 #6 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fa66aaca700 (LWP 11425)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa67840d39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa67840d4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa67d2dc23b in QEventDispatcherGlib::processEvents (this=0x7fa6640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa67d286cea in QEventLoop::exec (this=this@entry=0x7fa66aac9c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #5 0x7fa67d0abfb4 in QThread::exec (this=this@entry=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #6 0x7fa67b54d7a5 in QDBusConnectionManager::run (this=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196 #7 0x7fa67d0b0b98 in QThreadPrivate::start (arg=0x7fa67b5c1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344 #8 0x7fa679c676fa in start_thread (arg=0x7fa66aaca700) at pthread_create.c:333 #9 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fa670c8b700 (LWP 11424)): #0 0x7fa67c9b1e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa677f82c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa677f848d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa67360fa39 in QXcbEventReader::run (this=0x1a959c0) at qxcbconnection.cpp:1337 #4 0x7fa67d0b0b98 in QThreadPrivate::start (arg=0x1a959c0) at thread/qthread_unix.cpp:344 #5 0x7fa679c676fa in start_thread (arg=0x7fa670c8b700) at pthread_create.c:333 #6 0x7fa67c9bdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fa673bac900 (LWP 11423)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/5/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:103 #8 QBasicAtomicInteger::load (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:99 #9 QtPrivate::RefCount::ref (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::operator= (this=0x7fa65c04fc78, other=...) at tools/qstrin
