[frameworks-kwallet] [Bug 353960] automatic new wallet wizard stops with "no suitable key" without hint
https://bugs.kde.org/show_bug.cgi?id=353960 --- Comment #30 from Lars Gottlieb --- (In reply to Andrew from comment #29) > After seeing "any patch welcome"... I spent the morning working on this: > https://invent.kde.org/frameworks/kwallet/-/merge_requests/83 > > This merge request is for a change in knewwalletdialog.cpp, to change the > message displayed in KWallet when users have newly installed their OS and > select GPG from > "Seems that your system has no keys suitable for encryption. Please set-up > at " > "least one encryption key, then try again." > to > "No suitable keys for encryption found. To create a GPG key, you can:\n" > "1. Option 1) Open Kleopatra and follow Kleopatra's documentation at: > https://docs.kde.org/stable5/en/kleopatra/kleopatra/functions-newkey.html\n; > "2. Option 2) Open Konsole and enter the command: gpg --full-gen-key, then > follow the instructions." > > > It's 100% nothing fancy. I even updated all of the translations (.po) > files... but it turns out I can't really submit those very easily through > the same process, and I'd really only be qualified to submit the German > translation update anyways. The updated instructions (assuming the 'patch') > actually makes it into KWallet eventually I hope are better than nothing. > Also, I'm willing to put more effort into this to see it get done if this > isn't sufficient. That is absolutely a start, and it will help hundreds if not thousands of users to find a solution to this embarrasing problem. Thank you Andrew! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486457] build of amarok3 crashes on starte
https://bugs.kde.org/show_bug.cgi?id=486457 --- Comment #2 from Lars Schimmer --- did recompile with that options and got this output: ** ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: ** ** amarok --debug** ** QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioDataOutput ( no objectName ). QFSFileEngine::open: No file name specified QFSFileEngine::open: No file name specified ASSERT: "qmlPackage.isValid()" in file /usr/src/amarok/amarok/src/context/ContextView.cpp, line 78 44 -- exe=/usr/src/amarok/amarok/build/bin/amarok 13 -- platform=xcb 11 -- display=:0 15 -- appname=amarok 41 -- apppath=/usr/src/amarok/amarok/build/bin 9 -- signal=6 12 -- pid=1264398 21 -- appversion=3.0.0-git 19 -- programname=Amarok 31 -- bugaddress=sub...@bugs.kde.org KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = amarok path = /usr/src/amarok/amarok/build/bin pid = 1264398 KCrash: Arguments: /usr/src/amarok/amarok/build/bin/amarok KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1] + 1264398 suspended (signal) ./bin/amarok 147 ei2pee@orville ~src/amarok/amarok/build (git)-[master] % ./bin/amarok --debug amarok: BEGIN: void App::continueInit() amarok: BEGIN: virtual int App::newInstance() amarok: BEGIN: void App::handleCliArgs(const QString&) amarok: END__: void App::handleCliArgs(const QString&) [Took: 0s] amarok: END__: virtual int App::newInstance() [Took: 0s] amarok: BEGIN: DebugLogger::DebugLogger(QObject*) amarok: END__: DebugLogger::DebugLogger(QObject*) [Took: 0s] amarok: BEGIN: EngineController::EngineController() amarok: END__: EngineController::EngineController() [Took: 0s] amarok: BEGIN: void EngineController::initializePhonon() QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) amarok: BEGIN: void EqualizerController::initialize(const Phonon::Path&) amarok: [EqualizerController] Established Phonon equalizer effect with 11 parameters. amarok: BEGIN: void EqualizerController::eqUpdate() amarok: END__: void EqualizerController::eqUpdate() [Took: 0s] amarok: END__: void EqualizerController::initialize(const Phonon::Path&) [Took: 0s] WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioDataOutput ( no objectName ). amarok: [EngineController] Tick Interval (actual): 100 amarok: END__: void EngineController::initializePhonon() [Took: 0.011s] amarok: BEGIN: CollectionManager::CollectionManager() amarok: END__: CollectionManager::CollectionManager() [Took: 0s] amarok: BEGIN: MainWindow::MainWindow() amarok: BEGIN: Plugins::PluginManager::PluginManager(QObject*) amarok: BEGIN: void Plugins::PluginManager::checkPluginEnabledStates() amarok: [PluginManager] found plugin: "amarok_collection-audiocdcollection" enabled: true amarok: [PluginManager] found plugin: "amarok_service_gpodder" enabled: false amarok: [PluginManager] found plugin: "amarok_collection-daapcollection" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-itunes" enabled: false amarok: [PluginManager] found plugin: "amarok_collection-mtpcollection" enabled: true amarok: [PluginManager] Plugin "amarok_storage-mysqlserverstorage" is vital amarok: [PluginManager] found plugin: "amarok_storage-mysqlserverstorage" enabled: true amarok: [PluginManager] found plugin: "amarok_collection-umscollection" enabled: true amarok: [PluginManager] found plugin: "amarok_service_lastfm" enabled: false amarok: [PluginManager] found plugin: "amarok_collection-playdarcollection" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-rhythmbox" enabled: false amarok: [PluginManager] found plugin: "amarok_service_magnatunestore" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-fastforward" enabled: false amarok: [PluginManager] found plugin: "amarok_importer-amarok" enabled: false amarok: [PluginManager] found plugin: "amarok_service_ampache" enabled: false amarok: [PluginManager] found plugin: "amarok_service_opmldirector
[amarok] [Bug 486457] New: build of amarok3 crashes on starte
https://bugs.kde.org/show_bug.cgi?id=486457 Bug ID: 486457 Summary: build of amarok3 crashes on starte Classification: Applications Product: amarok Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: ls.kdeb...@cgv.tugraz.at Target Milestone: kf5 Application: amarok (3.0.0-git) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-17-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Built amarok3 from source and did run, crashes everytime on start with ./amarok The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Aborted [KCrash Handler] #4 0x7f3e0e53ee2c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7f3e0e4effb2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f3e0e4da472 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f3e0d090c79 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3e0d090024 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f3e0ea90b6b in Context::ContextView::ContextView (this=0x5604ed1c8680, parent=0x0) at /usr/src/amarok/amarok/src/context/ContextView.cpp:78 #10 0x7f3e0ea9028d in ContextDock::createContextView (this=0x5604ed375c60) at /usr/src/amarok/amarok/src/context/ContextDock.cpp:44 #11 0x7f3e0ea90253 in ContextDock::ContextDock (this=0x5604ed375c60, parent=0x5604ece583b0) at /usr/src/amarok/amarok/src/context/ContextDock.cpp:34 #12 0x7f3e0edff1de in MainWindow::init (this=0x5604ece583b0) at /usr/src/amarok/amarok/src/MainWindow.cpp:232 #13 0x7f3e0edfe688 in MainWindow::MainWindow (this=0x5604ece583b0) at /usr/src/amarok/amarok/src/MainWindow.cpp:158 #14 0x7f3e0eded3cf in App::continueInit (this=0x7ffeae942670) at /usr/src/amarok/amarok/src/App.cpp:463 #15 0x5604ebafe5e7 in main (argc=1, argv=0x7ffeae943e08) at /usr/src/amarok/amarok/src/main.cpp:391 [Inferior 1 (process 993581) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 --- Comment #28 from Lars Veldscholte --- I'll have to double check, but I think I've also had it break without a sleep/resume. Also, I think Bug 482629 might the same bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl --- Comment #26 from Lars Veldscholte --- Same issue here. I didn't have this issue on Plasma 5.27 (I was already using Wayland back then). Straight after booting, it always works fine, but after using Plasma for a while and starting up a game, the mouse doesn't work anymore. I've also noticed that sometimes it spontaneously starts working fine again after trying some things (alt-tabbing, clicking, mashing some buttons) but I've not been able to narrow it down to some specific trigger. The issue still exists on Plasma 6.02 / Qt 6.6.2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482408] Unable to customize relative zoom mode shortcut
https://bugs.kde.org/show_bug.cgi?id=482408 --- Comment #2 from Lars Lundefaret --- Ouff. Im just really stupid. I input only the z key but didntcombine it with any clicks, so of course it didnt work... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482408] Unable to customize relative zoom mode shortcut
https://bugs.kde.org/show_bug.cgi?id=482408 Lars Lundefaret changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482410] Unable to customize relative zoom mode shortcut
https://bugs.kde.org/show_bug.cgi?id=482410 Lars Lundefaret changed: What|Removed |Added CC||lars.lundefa...@try.no -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482410] New: Unable to customize relative zoom mode shortcut
https://bugs.kde.org/show_bug.cgi?id=482410 Bug ID: 482410 Summary: Unable to customize relative zoom mode shortcut Classification: Applications Product: krita Version: 5.2.2 Platform: unspecified OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: lars.lundefa...@try.no Target Milestone: --- SUMMARY *** Unable to customize relative zoom Mode keyboard shortcut. I want to change it so it is similar to Photoshop (out of habit) but im unable to do so. *** STEPS TO REPRODUCE 1. Go to the preferences (on a mac) > Canvas input settings -> Zoom Canvas 2. Find the shortcut for realtive zoom mode and change the input to something than the middle mouse button for the shortcut "Relative Zoom Mode" with the "Ctrl + Middle Mouse Button" as the shorcut. // Changing the modifier on this is the only thing that works, but not the key. OBSERVED RESULT Changing it to any other key doesnt work sadly. EXPECTED RESULT The functionality is gone when changing the key. My hope was to change it to work like in PS. Where you can hold down Z and click to zoom in and out. It does work perfect if I dotn change the keys, but it is something of a habit in my muscle memory. And id like to be able to change it rather than relearn it, SOFTWARE/OS VERSIONS macOS: Ventura 13.1 ADDITIONAL INFORMATION M1 Pro -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482408] New: Unable to customize relative zoom mode shortcut
https://bugs.kde.org/show_bug.cgi?id=482408 Bug ID: 482408 Summary: Unable to customize relative zoom mode shortcut Classification: Applications Product: krita Version: 5.2.2 Platform: unspecified OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: lars.lundefa...@try.no Target Milestone: --- SUMMARY *** Unable to customize relative zoom Mode keyboard shortcut. I want to change it so it is similar to Photoshop (out of habit) but im unable to do so. *** STEPS TO REPRODUCE 1. Go to the preferences (on a mac) > Canvas input settings -> Zoom Canvas 2. Find the shortcut for realtive zoom mode and change the input to something than the middle mouse button for the shortcut "Relative Zoom Mode" with the "Ctrl + Middle Mouse Button" as the shorcut. // Changing the modifier on this is the only thing that works, but not the key. OBSERVED RESULT Changing it to any other key doesnt work sadly. EXPECTED RESULT The functionality is gone when changing the key. My hope was to change it to work like in PS. Where you can hold down Z and click to zoom in and out. It does work perfect if I dotn change the keys, but it is something of a habit in my muscle memory. And id like to be able to change it rather than relearn it, SOFTWARE/OS VERSIONS macOS: Ventura 13.1 ADDITIONAL INFORMATION M1 Pro -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 480543] New: Akonadis sqlite backend does not honor sql limits
https://bugs.kde.org/show_bug.cgi?id=480543 Bug ID: 480543 Summary: Akonadis sqlite backend does not honor sql limits Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: schei...@gonicus.de CC: c...@carlschwan.eu Target Milestone: --- SUMMARY This is not a crash report, but this behavior of akonadi and especially akonadis sqlite backend, renders the usability of kdepim with sqlite to useless and leads to many errors users are not expecting. In fact kdepim "feels" very laggy and slow to use. STEPS TO REPRODUCE 1. Use sqlite backend: akonadiserverrc: [%General] Driver=QSQLITE Try to delete more than one thousand mails or prune your trash folder with several thousand mails. Or open a mailbox with several thousand mails. OBSERVED RESULT Mails do not get deleted. You get an error that "deleting mails failed" (with no further information about what failed). Mailfolder do not open in an acceptable period of time, sometimes you get a timeout or nothing happens. You have to restart akonadi to get back to a usable state in that case. Kontact feels unresponsive and extremely laggy. EXPECTED RESULT Mails do get purged (i.e. trash) and mailfolders should load and show in an acceptable amount of time. Kontact/kmail should feel responsive SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kontact Version: 5.24.4 (23.08.4) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 (kompiliert gegen 5.15.11) ADDITIONAL INFORMATION I use kontact with four mail accounts (2xIMAP, GMail and EWS plus a local mailfolder for trash) and three Calendar Sources. The overall amount of Mails is significant, but only one folder exceeds 10k Mails (the local trash folder), the other folders are quite small. LOGGING INFORMATION Every now and then while opening a mailfolder with many mails (but none of my folders carries 9 Mails!): org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY: org.kde.pim.akonadiserver: Error code: "1" org.kde.pim.akonadiserver: DB error: "too many SQL variables" org.kde.pim.akonadiserver: Error text: "too many SQL variables Der Befehl konnte nicht ausgeführt werden" org.kde.pim.akonadiserver: Query: "SELECT PimItemTable.id, PimItemTable.rev, PimItemTable.remoteId, PimItemTable.remoteRevision, PimItemTable.gid, PimItemTable.collectionId, PimItemTable.mimeTypeId, PimItemTable.datetime, PimItemTable.atime, PimItemTable.dirty, PimItemTable.size FROM PimItemTable WHERE ( PimItemTable.id IN ( :0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13, :14, :15, :16, :17, :18, :19, :20, :21, :22, :23, :24, :25, :26, :27, :28, :29, :30, :31, :32, :33, :34, :35, :36, :37, :38, :39, :40, :41, :42, :43, :44, :45, :46, :47, :48, :49, :50, :51, :52, :53, :54, :55, :56, :57, :58, :59, :60, :61, :62, :63, :64, :65, :66, :67, :68, :69, :70, :71, :72, :73, :74, :75, :76, :77, :78, :79, :80, :81, :82, :83, :84, :85, :86, :87, :88, :89, :90, :91, :92, :93, :94, :95, :96, :97, :98, :99, :100, :101, :102, :103, :104, :105, :106, :107, :108, :109, :110, :111, :112, :113, :114, :115, :116, :117, :118, :119, :120, :121, :122, :123, :124, :125, :126, :127, :128, :129, :130, :131, :132, :133, :134, :135, :136, :137, :138, :139, :140, :141, :142, :143, :144, :145, :146, :147, :148, :149, :150, :151, :152, :153, :154, :155, :156, === (snip) :99938, :99939, :99940, :99941, :99942, :99943, :99944, :99945, :99946, :99947, :99948, :99949, :99950, :99951, :99952, :99953, :99954, :99955, :99956, :99957, :99958, :99959, :99960, :99961, :99962, :99963, :99964, :99965, :99966, :99967, :99968, :99969, :99970, :99971, :99972, :99973, :99974, :99975, :99976, :99977, :99978, :99979, :99980, :99981, :99982, :99983, :99984, :99985, :99986, :99987, :99988, :99989, :0, :1, :2, :3, :4, :5, :6, :7, :8, :9 ) )" This error comes quite often, maybe it's not related to opening a folder? I don't know. Trying to delete more than a thousand mails or expunge trash: org.kde.pim.akonadiserver: DATABASE ERROR while PREPARING QUERY: org.kde.pim.akonadiserver: Error code: "1" org.kde.pim.akonadiserver: DB error: "Expression tree is too large (maximum depth 1000)" org.kde.pim.akonadiserver: Error text: "Expression tree is too large (maximum depth 1000) Der Befehl konnte nicht ausgeführt werden" org.kde.pim.akonadiserver: Query: "SELECT PimItemTable.id, PimItemTable.rev, PimItemTable.remoteId, PimItemTable.remoteRevision, PimItemTable.gid, PimItemTable.collectionId, PimItemTable.mimeTypeId, PimItemTable.datetime, PimItemTable.atime, PimItemTable.dirty, PimItemTable.size FROM PimItemTable WHERE ( ( ( PimItemTable.id >= :0 AND PimItemTable.id <= :1 ) OR
[ksplash] [Bug 478786] New: different animation speeds on different refresh rate monitors
https://bugs.kde.org/show_bug.cgi?id=478786 Bug ID: 478786 Summary: different animation speeds on different refresh rate monitors Classification: Plasma Product: ksplash Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lars.l...@gmail.com Target Milestone: --- SUMMARY Splash screen animations play at different speeds depending on the monitors refresh rate. STEPS TO REPRODUCE 1. set the refresh rate of the first monitor to something slow (60Hz) 2. set the refresh rate of the second monitor to something fast (165Hz) 3. play splash screen OBSERVED RESULT second monitor play the animation much faster than the first EXPECTED RESULT both monitors play the animation at the same speed, in sync SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- 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 Lars Gottlieb changed: What|Removed |Added CC||lars.gottl...@gmail.com --- Comment #23 from Lars Gottlieb --- I've been distrohopping a little over this week, and every single KDE based distro I've tried has had this happen every time the user tries to open a Chromium based browse, or an application based on it. This issue has been open for 8 full years. That this is such a low priority for the KDE design team is frankly not a great look. You can wipe it off on the chromium team if you like, but it appears the message comes from KDE, not Chromium. I humbly suggest some ressources be allocated to fix this; if nothing else make the message link to a user friendly solution. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 --- Comment #11 from Lars --- (In reply to Maik Qualmann from comment #10) > There isn't really a crash, I see that it's at a Qt_ASSERT stop. They run Qt > in debug mode or an environment variable is set so that every Qt_ASSERT > leads to an abort. > According to the Qt Doc, m_childCache.value(row, nullptr); would be valid. I > suspect, but that if row is out of range Qt will do a Qt_ASSERT. I will take > a look. > > Maik please note that I used the -debug.appimage on the 8.2.0, just in case that explains this behavior. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 --- Comment #9 from Lars --- (In reply to Maik Qualmann from comment #6) > At this point we're adding an album, but there's no apparent crash. This > part is also in the first backtrace. In digiKam-8.2.0 there is a change in > removing albums to have full read/write protection of the album child cache. > So it would be interesting if you would test our digiKam-8.2.0 AppImage. > > https://files.kde.org/digikam/digiKam-8.2.0-20230826T081258-x86-64.appimage > > Please provide the video file, send it to my mail address. > > Maik done - thanks again for helping! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 --- Comment #8 from Lars --- (In reply to Lars from comment #7) > Created attachment 161223 [details] > backtrace 8.2.0 > > Here's the backtrace of digiKam-8.2.0-20230826T081258-x86-64-debug.appimage Just noticed: I just reran the binary again and this time it did _not_ crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 --- Comment #7 from Lars --- Created attachment 161223 --> https://bugs.kde.org/attachment.cgi?id=161223=edit backtrace 8.2.0 Here's the backtrace of digiKam-8.2.0-20230826T081258-x86-64-debug.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 Lars changed: What|Removed |Added Attachment #161215|0 |1 is obsolete|| --- Comment #5 from Lars --- Created attachment 161221 --> https://bugs.kde.org/attachment.cgi?id=161221=edit backtrace 2 as requested, the normal backtrace, created via `bt`. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 Lars changed: What|Removed |Added Attachment #161209|0 |1 is obsolete|| --- Comment #2 from Lars --- Created attachment 161215 --> https://bugs.kde.org/attachment.cgi?id=161215=edit backtrace added the log output instead of the backtrace, sorry. Here's the backtrace of the same run. Despite being on an encrypted partition, the filesystem is mounted unencrypted, so that is not the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473801] New: crashes while auto-importing new media files
https://bugs.kde.org/show_bug.cgi?id=473801 Bug ID: 473801 Summary: crashes while auto-importing new media files Classification: Applications Product: digikam Version: 8.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-ExifTool Assignee: digikam-bugs-n...@kde.org Reporter: lars+...@kumbier.it Target Milestone: --- Created attachment 161209 --> https://bugs.kde.org/attachment.cgi?id=161209=edit Backtrace and exiftool log SUMMARY digikam cashes while a background job is looking for new entries. It seems stumbles over a videofile while loading the EXIF metadata. This happens reproducibly. STEPS TO REPRODUCE - I can provide the offending videofile, but not in this bug tracking system (as its more than 4mb in size). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro rolling release (64bit, Gnome 44.3) Qt Version: 5.15.10 ADDITIONAL INFORMATION If if call exiftool in the commandline on the file in question, I do get an output with exitcode 0: `exiftool -TagsFromFile /mnt/cryptdata/Bilder/2023/08/19/p1050671.mp4 -all -o -.exv` -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451315] Recent updates to libwayland-server0 et al break i386 support.
https://bugs.kde.org/show_bug.cgi?id=451315 Lars Ivar Igesund changed: What|Removed |Added CC||larsi...@igesund.net --- Comment #25 from Lars Ivar Igesund --- (In reply to Konrad Materka from comment #24) > Steam is not the only popular thing that can't be easily installed, also > "wine". KDE neon is even mentioned on the official site: > https://wiki.winehq.org/Ubuntu > > libpoppler-glib8 is not the only package but also libjpeg-turbo8 (updated > yesterday) The libpoppler thing with wine is still an issue. This may be me not knowing all the supported ways on Neon to install wine, but in particular I need wine 8, and only method I've found (except building it myself) is via the winehq repos. By downgrading libpoppler (which is the recommended/only method out on the Internets), I was able to eventually install winehq-staging, but I lost it again after the next update of the system. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 178678] Navigating mounted network locations is extremely slow in Dolphin compared to command line
https://bugs.kde.org/show_bug.cgi?id=178678 Lars Winterfeld changed: What|Removed |Added CC||lars.winterfeld@tu-ilmenau. ||de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 471983] New: discover notifier is "offline"
https://bugs.kde.org/show_bug.cgi?id=471983 Bug ID: 471983 Summary: discover notifier is "offline" Classification: Applications Product: Discover Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: lagad...@yahoo.de CC: aleix...@kde.org Target Milestone: --- Since I've upgraded KDE neon installations to Ubuntu based 22.04 version the update notifier often does not show available updates because the notifier is "offline". When I open discover, there are updates available. So it seems it is a notifier problem (in KDE neon?). I have this behavior in all my installations (6). Whether if they are freshly installed or upgrades. On three computers it works partly, but only if the computer is connected with cable to the router, not with a wifi connection. On one wifi connected installation it is nearly 50/50, that it is not "offline" after boot. After a restart of the notifier it is "online". (/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier --replace) Seems notifier starts before an internet connection exists and remains in offline status. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 339971] Detach Tabs / Combine multiple windows in tabs
https://bugs.kde.org/show_bug.cgi?id=339971 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468436] Often when away from laptop, desktop has crashed/restarted when I come back, with kwin crash note in dmsg
https://bugs.kde.org/show_bug.cgi?id=468436 --- Comment #3 from Lars Ivar Igesund --- Not sure it helps for the needsinfo status, but I'm currently waiting on this to happen again while also having the necessary debug symbols. Last week it didn't happen, presumably because the triggering situation was cancelled due to laptop turning off rather than going to sleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468436] New: Often when away from laptop, desktop has crashed/restarted when I come back, with kwin crash note in dmsg
https://bugs.kde.org/show_bug.cgi?id=468436 Bug ID: 468436 Summary: Often when away from laptop, desktop has crashed/restarted when I come back, with kwin crash note in dmsg Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: larsi...@igesund.net Target Milestone: --- Relatively often when going away from the laptop (it is connected to power, so don't go to sleep or similar, just screen goes to black), the desktop has relatively often restarted when I get back. Today is first time I have checked, but dmesg had this kwin_wayland[43369]: segfault at 10 ip 7fa9471d0c14 sp 7ffcb18c4518 error 4 in libkwin.so.5.27.3[7fa946f58000+32d000] [28781.826515] Code: 42 58 48 85 c0 74 0f 8b 40 04 85 c0 74 08 48 8b 42 60 c3 0f 1f 00 31 c0 c3 90 66 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa <48> 8b 57 10 48 8b 42 68 48 85 c0 74 0f 8b 40 04 85 c0 74 08 48 8b I am sorry that I don't immediately know if it is possible to get a stack trace from this, or if it is relevant. A potentially relevant note (at least it was this today, I don't remember if it was like this previous times, but I have a feeling they were): I bring my laptop to the office about once a week (today was such a day). There I connect it to a USB-C dock (Dell make), and attach keyboard, roller mouse and an external 4K Dell monitor. When going home, I disconnect the dock, close the lid and put it in my backpack. Home, I take it out and connect it. This evening I left home for a while, and when I returned, the above had happened. STEPS TO REPRODUCE 1. Go away from laptop, possibly after been through some laptop lid closing and opening and such OBSERVED RESULT Desktop has restarted all by itself EXPECTED RESULT Desktop doesn't restart all by itself SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: SLIMBOOK Product Name: PROX-AMD5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 448340] Contents of mime parts wrapped inside multipart/related are not shown
https://bugs.kde.org/show_bug.cgi?id=448340 Lars Scheiter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Lars Scheiter --- With the most recent kdepim update (kontact 22.12.3 on Fedora Kinoite) the problem seems to be fixed, thank you! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 448340] Contents of mime parts wrapped inside multipart/related are not shown
https://bugs.kde.org/show_bug.cgi?id=448340 Lars Scheiter changed: What|Removed |Added CC||schei...@gonicus.de --- Comment #1 from Lars Scheiter --- This does not only affect Applemail. Thunderbird and even KMail itself can compose Mails KMail can't propperly display! I tried to reproduce this behavior and composed a HTML-Mail (richtext) and embeded a jpg. The send folder contained my composed mail. While clicking that mail and switching between HTML and cleartext view my attachment magically disappeared. In HTML-View only a broken Image Icon is displayed. Changing the Attachment view or Theme does not change this behavior. But now comes the "fun part": During my testst this only happenend when kmail was embedded into kontact. Starting kmail as a standalone app does not show this bug! (well, at least in my tests) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453147] amdgpu: GPU reset crash loop
https://bugs.kde.org/show_bug.cgi?id=453147 Lars Scheiter changed: What|Removed |Added CC||schei...@gonicus.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Lars Scheiter changed: What|Removed |Added CC|schei...@gonicus.de | -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 Lars Scheiter changed: What|Removed |Added CC|schei...@gonicus.de | -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 86202] icons in html select boxes
https://bugs.kde.org/show_bug.cgi?id=86202 Lars Scheiter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 --- Comment #3 from Lars Scheiter --- The print dialogue only show printers which are configured in /etc/cups/printers.conf, but no printers which are discovered by cups-browsed. My printers list: # lpstat -a blutdruck accepting requests since Mo 11 Okt 2021 16:59:27 CEST Drucker_Bueecke_mrbeeg accepting requests since Do 30 Jun 2022 07:26:29 CEST Drucker_Praxis_mrbeeg accepting requests since Do 30 Jun 2022 07:26:30 CEST Farblaser_mrbeeg accepting requests since Do 30 Jun 2022 07:26:29 CEST Kyocera_ECOSYS_M5526cdn accepting requests since Do 30 Jun 2022 07:26:31 CEST Kyocera_Lars_mrbeeg accepting requests since Do 30 Jun 2022 16:03:03 CEST nebendruck accepting requests since Mo 11 Okt 2021 16:59:27 CEST Samsung_CLX_3300_Series_SEC001599AE9E6E_ accepting requests since Do 30 Jun 2022 16:19:38 CEST Samsung_Lars_mrbeeg accepting requests since Do 30 Jun 2022 07:26:29 CEST tiefdruck accepting requests since Mo 11 Okt 2021 16:59:27 CEST turmdruck accepting requests since Mo 11 Okt 2021 16:59:27 CEST uberdruck accepting requests since Di 14 Jun 2022 09:04:13 CEST unterdruck accepting requests since Mo 11 Okt 2021 16:59:27 CEST All the printers discovered by cups have unterlines in their names (eg.: "Kyocera_ECOSYS_M5526cdn"), the others are local configured printers (eg.: unterdruck and uberdruck). The only printers shown are local configured printers (See Screenshot.png). Second screenshot is systemsettings showing all printers. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 --- Comment #2 from Lars Scheiter --- Created attachment 150292 --> https://bugs.kde.org/attachment.cgi?id=150292=edit Systemsettings printers Screenshot showing the systemsettings printers -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 --- Comment #1 from Lars Scheiter --- Created attachment 150291 --> https://bugs.kde.org/attachment.cgi?id=150291=edit Printer dialogue Screenshot showing only a handfull of printers in the print dialogue -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 455798] Network printer missing in the print dialog of KDE apps, while available and working in the system settings and all non-KDE apps
https://bugs.kde.org/show_bug.cgi?id=455798 Lars Scheiter changed: What|Removed |Added CC||schei...@gonicus.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 389052] Desired connections run away just before clicking the "connect" button or entering password
https://bugs.kde.org/show_bug.cgi?id=389052 Lars Scheiter changed: What|Removed |Added CC||schei...@gonicus.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 Lars changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #31 from Lars --- (In reply to Maik Qualmann from comment #30) > Git commit 1589a8ce8d5862f4f48406a66af59b180cd02f87 by Maik Qualmann. > Committed on 10/04/2022 at 10:23. > Pushed by mqualmann into branch 'qt5-maintenance'. > > fix crash in openCV BlurDetector > > M +18 -7core/libs/dimg/filters/imgqsort/detector/blur_detector.cpp > > https://invent.kde.org/graphics/digikam/commit/ > 1589a8ce8d5862f4f48406a66af59b180cd02f87 I can confirm, that you fixed the bug in digiKam-7.7.0-20220410T110708-x86-64-debug.appimage - I've scanned the rest of my library without a problem and did a rescan, which is now at 60% without a crash. Thanks a ton! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #29 from Lars --- (In reply to Maik Qualmann from comment #28) Are your changes in version digiKam-7.7.0-20220407T100631-x86-64-debug.appimage ? Tried it with all cpu cores, crashed again. --- [Thread 0x7ffea97fa640 (LWP 967745) exited] Digikam::BlurDetector::getWeightMap: cv::Exception: OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/matrix.cpp:811: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' Digikam::BlurDetector::getWeightMap: cv::Exception: OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/matrix.cpp:811: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' terminate called after throwing an instance of 'cv::Exception' terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/arithm.cpp:650: error: (-209:Sizes of input arguments do not match) The operation is neither 'array op array' (where arrays have the same size and the same number of channels), nor 'array op scalar', nor 'scalar op array' in function 'arithm_op' what(): OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/arithm.cpp:650: error: (-209:Sizes of input arguments do not match) The operation is neither 'array op array' (where arrays have the same size and the same number of channels), nor 'array op scalar', nor 'scalar op array' in function 'arithm_op' [Thread 0x7ffec77fe640 (LWP 967738) exited] [Thread 0x7ffeabfff640 (LWP 967737) exited] Thread 44047 "Digikam::ImageQ" received signal SIGABRT, Aborted. [Switching to Thread 0x7ffee0dea640 (LWP 967718)] 0x7333534c in __pthread_kill_implementation () from /usr/lib/libc.so.6 (gdb) bt #0 0x7333534c in __pthread_kill_implementation () at /usr/lib/libc.so.6 #1 0x732e84b8 in raise () at /usr/lib/libc.so.6 #2 0x732d2534 in abort () at /usr/lib/libc.so.6 #3 0x736827ee in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #4 0x7368ec4c in __cxxabiv1::__terminate(void (*)()) (handler=) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #5 0x7368ecb9 in std::terminate() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #6 0x738a0deb in qt_assert(char const*, char const*, int) () at /tmp/.mount_digiKaHhiDeV/usr/lib/libQt5Core.so.5 #7 0x738a2630 in () at /tmp/.mount_digiKaHhiDeV/usr/lib/libQt5Core.so.5 #8 0x75c2 in start_thread () at /usr/lib/libc.so.6 #9 0x733b8584 in clone () at /usr/lib/libc.so.6 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #27 from Lars --- unfortunately it's still not fixed. :( I've tested against digiKam-7.7.0-20220402T111749-x86-64-debug.appimage with *all* cores. --- Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines 1.02026 Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines 1.03988 Thread 40607 "Digikam::ImageQ" received signal SIGABRT, Aborted. [Switching to Thread 0x7ffe967fc640 (LWP 493776)] 0x7333534c in __pthread_kill_implementation () from /usr/lib/libc.so.6 (gdb) bt #0 0x7333534c in __pthread_kill_implementation () at /usr/lib/libc.so.6 #1 0x732e84b8 in raise () at /usr/lib/libc.so.6 #2 0x732d2534 in abort () at /usr/lib/libc.so.6 #3 0x736827ee in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #4 0x7368ec4c in __cxxabiv1::__terminate(void (*)()) (handler=) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #5 0x7368ecb9 in std::terminate() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #6 0x738a0deb in qt_assert(char const*, char const*, int) () at /tmp/.mount_digiKakEAKQ5/usr/lib/libQt5Core.so.5 #7 0x738a2630 in () at /tmp/.mount_digiKakEAKQ5/usr/lib/libQt5Core.so.5 #8 0x75c2 in start_thread () at /usr/lib/libc.so.6 #9 0x733b8584 in clone () at /usr/lib/libc.so.6 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #25 from Lars --- (In reply to Maik Qualmann from comment #24) Thank you - I'll try it tomorrow, when the new weekly appimage is out. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #22 from Lars --- I can confirm the problem still existing even with *single* core operation in digiKam-7.7.0-20220401T090402-x86-64-debug.appimage --- Digikam::BlurDetector::getWeightMap: cv::Exception: OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/matrix.cpp:811: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/arithm.cpp:650: error: (-209:Sizes of input arguments do not match) The operation is neither 'array op array' (where arrays have the same size and the same number of channels), nor 'array op scalar', nor 'scalar op array' in function 'arithm_op' Thread 44012 "Digikam::ImageQ" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff34d2a640 (LWP 386197)] 0x7333534c in __pthread_kill_implementation () from /usr/lib/libc.so.6 (gdb) bt #0 0x7333534c in __pthread_kill_implementation () at /usr/lib/libc.so.6 #1 0x732e84b8 in raise () at /usr/lib/libc.so.6 #2 0x732d2534 in abort () at /usr/lib/libc.so.6 #3 0x736827ee in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #4 0x7368ec4c in __cxxabiv1::__terminate(void (*)()) (handler=) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #5 0x7368ecb9 in std::terminate() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #6 0x738a0deb in qt_assert(char const*, char const*, int) () at /tmp/.mount_digiKawlrStK/usr/lib/libQt5Core.so.5 #7 0x738a2630 in () at /tmp/.mount_digiKawlrStK/usr/lib/libQt5Core.so.5 #8 0x75c2 in start_thread () at /usr/lib/libc.so.6 #9 0x733b8584 in clone () at /usr/lib/libc.so.6 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #21 from Lars --- yes, I used version digiKam-7.7.0-20220401T090402-x86-64-debug.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868
--- Comment #19 from Lars ---
There seems to be a different problem - same as I've mentioned in my last
comment. This time, the problem occured when I used *all* cores.
---
Digikam::ExifToolParser::slotMetaEngineSettingsChanged: ExifTool path:
"exiftool"
Digikam::ExifToolProcess::checkExifToolProgram: Path to ExifTool: "exiftool"
Digikam::ExifToolProcess::start: ExifToolProcess::start(): create new ExifTool
instance: "exiftool" ("-stay_open", "true", "-@", "-", "-common_args",
"-charset", "filename=UTF8", "-charset", "iptc=UTF8")
[New Thread 0x7ffeccdfa640 (LWP 307778)]
[Thread 0x7ffece7fc640 (LWP 307721) exited]
Digikam::ImageQualityParser::startAnalyse: Final Quality estimated: 57.5384
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.0969293
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.524234
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.509541
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
[Thread 0x7ffeccdfa640 (LWP 307778) exited]
terminate called after throwing an instance of 'cv::Exception'
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.964288
terminate called recursively
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.0224309
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines 0
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.868536
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.793383
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.896827
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.78846
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines 0
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
1.05185
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.792521
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.0884398
Digikam::BlurDetector::detectMotionBlurMap: Motion blurred part detected
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.882502
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.857979
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.84723
Digikam::BlurDetector::isMotionBlur: Standard Deviation for group of lines
0.848067
Thread 40426 "Digikam::ImageQ" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffe8e7f4640 (LWP 307750)]
0x7333534c in __pthread_kill_implementation () from /usr/lib/libc.so.6
(gdb) bt
#0 0x7333534c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#1 0x732e84b8 in raise () at /usr/lib/libc.so.6
#2 0x732d2534 in abort () at /usr/lib/libc.so.6
#3 0x73690ddd in __gnu_cxx::__verbose_terminate_handler() () at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:50
#4 0x7368ec4c in __cxxabiv1::__terminate(void (*)())
(handler=) at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
#5 0x7368ecb9 in std::terminate() () at
/usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
#6 0x738a0deb in qt_assert(char const*, char const*, int) () at
/tmp/.mount_digiKa7qserd/usr/lib/libQt5Core.so.5
#7 0x738a2630 in () at
/tmp/.mount_digiKa7qserd/usr/lib/libQt5Core.so.5
#8 0x75c2 in start_thread () at /usr/lib/libc.so.6
#9 0x733b8584 in clone () at /usr/lib/libc.so.6
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #17 from Lars --- I've tried running the quality maintenance on just *one* core - the last check was with *all* cores. It also crashed on digiKam-7.7.0-20220327T091422-x86-64-debug.appimage with just one core, but in a different place. Should I open a new bug? --- Digikam::BlurDetector::getWeightMap: cv::Exception: OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/matrix.cpp:811: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.5.5) /b/ext_opencv/ext_opencv-prefix/src/ext_opencv/modules/core/src/arithm.cpp:650: error: (-209:Sizes of input arguments do not match) The operation is neither 'array op array' (where arrays have the same size and the same number of channels), nor 'array op scalar', nor 'scalar op array' in function 'arithm_op' Thread 44102 "Digikam::ImageQ" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff35d2c640 (LWP 219382)] 0x7333634c in __pthread_kill_implementation () from /usr/lib/libc.so.6 (gdb) bt #0 0x7333634c in __pthread_kill_implementation () at /usr/lib/libc.so.6 #1 0x732e94b8 in raise () at /usr/lib/libc.so.6 #2 0x732d3534 in abort () at /usr/lib/libc.so.6 #3 0x736837ee in __gnu_cxx::__verbose_terminate_handler() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #4 0x7368fc4c in __cxxabiv1::__terminate(void (*)()) (handler=) at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #5 0x7368fcb9 in std::terminate() () at /usr/src/debug/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #6 0x738a1deb in qt_assert(char const*, char const*, int) () at /tmp/.mount_digiKa4DFGIc/usr/lib/libQt5Core.so.5 #7 0x738a3630 in () at /tmp/.mount_digiKa4DFGIc/usr/lib/libQt5Core.so.5 #8 0x733345c2 in start_thread () at /usr/lib/libc.so.6 #9 0x733b9584 in clone () at /usr/lib/libc.so.6 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #14 from Lars --- (In reply to Maik Qualmann from comment #13) Of course - here it is: --- Thread 96 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffea9ffb640 (LWP 68951)] QList::node_copy (src=0x7ffe5ce39f80, to=0x7ffea4434f98, from=0x7ffe0922c3b0, this=0x7ffea44a3108) at ././/include/QtCore/qlist.h:492 492 ././/include/QtCore/qlist.h: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 QList::node_copy(QList::Node*, QList::Node*, QList::Node*) (src=0x7ffe5ce39f80, to=0x7ffea4434f98, from=0x7ffe0922c3b0, this=0x7ffea44a3108) at ././/include/QtCore/qlist.h:492 #1 QList::detach_helper(int) (this=0x7ffea44a3108, alloc=) at ././/include/QtCore/qlist.h:835 #2 0x760dee0a in QList::detach_helper() (this=0x7ffea44a3108) at ././/include/QtCore/qlist.h:849 #3 QList::detach() (this=0x7ffea44a3108) at ././/include/QtCore/qlist.h:178 #4 QList::begin() (this=0x7ffea44a3108) at ././/include/QtCore/qlist.h:338 #5 Digikam::ImageQualityCalculator::adjustWeightByQualityLevel() const (this=this@entry=0x7ffea44a30e0) at /b/dktemp/digikam-qt5-maintenance/core/libs/dimg/filters/imgqsort/imagequalitycalculator.cpp:120 #6 0x760df023 in Digikam::ImageQualityCalculator::calculateQuality() const (this=0x7ffea44a30e0) at /b/dktemp/digikam-qt5-maintenance/core/libs/dimg/filters/imgqsort/imagequalitycalculator.cpp:99 #7 0x760de94c in Digikam::ImageQualityParser::startAnalyse() (this=this@entry=0x7ffea4390ea0) at /b/dktemp/digikam-qt5-maintenance/core/libs/dimg/filters/imgqsort/imagequalityparser.cpp:160 #8 0x77638b6f in Digikam::ImageQualityTask::run() (this=0xaf8c200) at /b/dktemp/digikam-qt5-maintenance/core/utilities/maintenance/imagequalitytask.cpp:123 #9 0x738de9e1 in () at /tmp/.mount_digiKa1259c0/usr/lib/libQt5Core.so.5 #10 0x738db8c9 in () at /tmp/.mount_digiKa1259c0/usr/lib/libQt5Core.so.5 #11 0x733345c2 in start_thread () at /usr/lib/libc.so.6 #12 0x733b9584 in clone () at /usr/lib/libc.so.6 (gdb) --- I ran it twice to ensure that both runs break in the same place (they did). Version I ran is digiKam-7.7.0-20220327T091422-x86-64-debug.appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #12 from Lars --- (In reply to caulier.gilles from comment #11) > New pre-release AppImage is online now. > > Gilles Caulier Thank you - I tried it and it's still crashing: > double free or corruption (fasttop) > /tmp/.mount_digiKa7FO5hR/AppRun: Zeile 177: 42459 Abgebrochen > (Speicherabzug geschrieben) digikam $@ the second time I got a malloc error. I tried to pin it down to an image, but when I just run it against the last image (more specifically the album) that failed, it went through smoothly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #10 from Lars --- (In reply to caulier.gilles from comment #9) > No, there is no Docker to build AppImage. We use a real computer with Linux > to compile and build the bundle. > > Gilles Caulier someone actually builds the weekly appimage by hand and uploads it? Without CI/CD? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #8 from Lars --- I can confirm the bug on 7.7.0-20220323T020040-x86-64 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #7 from Lars --- (In reply to Maik Qualmann from comment #6) > Make sure you have disabled hardware acceleration for OpenCV (OpenCL) in the > digiKam settings under Miscellaneous-> System. > > Maik it's deactivated. I'm currently trying a run of the weekly build with all cores to see, if the bug is reproducible there. Is there a pipeline or docker image that I could use to build an appimage of your qt5-maintenance branch? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #4 from Lars --- There actually seem to be multiple issues... Running it on all cores produces different errors: - `double free or corruption (fasttop)` - `malloc_consolidate(): invalid chunk size` I've uploaded all logs here: https://box.kumbier.it/f/8afce38f60ce4cd3a3fb/?dl=1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 --- Comment #3 from Lars --- I've added the export variable, but it did not produce more insight than before: ``` digikam.dimg: Detect if each part is motion blur digikam.dimg: Detect if each part is motion blur digikam.dimg: Detect if each part is motion blur digikam.dimg: Standard Deviation for group of lines 0.452814 digikam.dimg: Detect if each part is motion blur digikam.dimg: Standard Deviation for group of lines 0.838613 digikam.dimg: Detect if each part is motion blur digikam.dimg: Standard Deviation for group of lines 0.473135 digikam.dimg: Detect if each part is motion blur digikam.dimg: Standard Deviation for group of lines 0.878844 terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.5.5) /build/opencv/src/opencv-4.5.5/modules/core/src/matrix.cpp:810: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' ``` What it *seems* like is that the crash is not reliable, because I had to wait for hours this time, before it crashed. Might be a race condition. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451868] New: Crash while creating quality
https://bugs.kde.org/show_bug.cgi?id=451868 Bug ID: 451868 Summary: Crash while creating quality Product: digikam Version: 7.6.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Maintenance-Quality Assignee: digikam-bugs-n...@kde.org Reporter: lars+...@kumbier.it Target Milestone: --- SUMMARY digikam crashes after a few minutes when trying to create quality data. Using all cores to create the quality data will reliably crash digikam within a few seconds - everytime with the same error message: ``` terminate called after throwing an instance of 'cv::Exception' what(): OpenCV(4.5.5) /build/opencv/src/opencv-4.5.5/modules/core/src/matrix.cpp:810: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat' zsh: IOT instruction (core dumped) digikam ``` I do not know which image produces the crash. Any help to find out, which image it is, appreciated. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 (built against 5.15.2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448963] Panel disappears after turning monitors off/on
https://bugs.kde.org/show_bug.cgi?id=448963 --- Comment #3 from Lars Veldscholte --- (In reply to Aleksey Zagorodnikov from comment #2) > In my case not only panel is gone, but background goes black and right click > on it not work anymore. Indeed, this is also the case for me (but I hadn't noticed it yet because the desktop was covered by windows). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448963] New: Panel disappears after turning monitors off/on
https://bugs.kde.org/show_bug.cgi?id=448963 Bug ID: 448963 Summary: Panel disappears after turning monitors off/on Product: plasmashell Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: l...@tuxplace.nl Target Milestone: 1.0 SUMMARY After turning my monitors off and back on again, the panel on one of my monitors (always the same one) is missing. Restarting plasmashell (using `plasmashell --replace`) reliably restores the missing panel. STEPS TO REPRODUCE 1. Turn monitors off. 2. Turn monitors on. OBSERVED RESULT The panel on one of my monitors is gone. EXPECTED RESULT The panels stay where they should. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447305] feature-request: add support of wlr-randr for wayland sessions
https://bugs.kde.org/show_bug.cgi?id=447305 Lars Bischoff changed: What|Removed |Added Version|unspecified |5.23.4 Platform|unspecified |Ubuntu Packages --- Comment #2 from Lars Bischoff --- Ah, thanks! I was searching for a native kde command-line tool to manage screens when I wrote my little screen switching script years ago, but couldn't find any. Now, if it only would work when using wayland... First problem I encountered was that the output names are not the same as when using X11. On X11 I have: "DisplayPort-0" and "HDMI-A-0" On wayland I just have outputs "1" and "2". So it's not possible to use exactly the same commands on both X11 and wayland. And then the first time I used that to switch the output from one output to the other, my whole system froze... had to hard reset... Guess I better let wayland mature for another 5 years before trying again, huh? ;) Anyway: Even if kscreen-doctor would work properly, having a DE (or wayland-compositor) independent command-line tool for managing display outputs (similar to xrandr), is IMHO still preferable. So would be great if something like wlr-randr is considered at some point. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447305] New: feature-request: add support of wlr-randr for wayland sessions
https://bugs.kde.org/show_bug.cgi?id=447305 Bug ID: 447305 Summary: feature-request: add support of wlr-randr for wayland sessions Product: kwin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: lbisch...@gmx.de Target Milestone: --- Please add support for wlr-randr (or any other replacement for xrandr) for wayland sessions that allows for script controlled switching of monitors. My use-case: I'm using a script that makes use of xrandr and pactl to switch monitor and audio output to one out of several pre-defined configurations. This currently does not work when using a wayland session due to the lack of a xrandr replacement (at least I could not find any - sorry if there is one). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447084] New: kwin_wayland crashes when sharing screen using WebRTC
https://bugs.kde.org/show_bug.cgi?id=447084 Bug ID: 447084 Summary: kwin_wayland crashes when sharing screen using WebRTC Product: kwin Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: l...@tuxplace.nl Target Milestone: --- SUMMARY kwin_wayland crashes while casting one of my screens using WebRTC/Pipewire/xdg-desktop-portal in Chromium. I can reproduce the crash by simply interacting with the UI in many ways, e.g. opening a new tab in my browser, browsing around in Dolphin, etc. This only seems to occur with Chromium, and not with Firefox. STEPS TO REPRODUCE 1. Open Chromium 2. Share your screen using WebRTC, e.g. on https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ 3. Use your desktop. OBSERVED RESULT KWin crashes. EXPECTED RESULT No crashes. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION Backtrace: [Current thread is 1 (Thread 0x7fe9457510c0 (LWP 38540))] (gdb) bt #0 0x7fe94ce89580 in () at /usr/lib/libkwinglutils.so.13 #1 0x7fe94ce8a56d in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () at /usr/lib/libkwinglutils.so.13 #2 0x7fe94ce84e18 in KWin::GLTexture::render(QRegion const&, QRect const&, bool) () at /usr/lib/libkwinglutils.so.13 #3 0x55db5d5bd113 in () #4 0x55db5d5bd385 in () #5 0x7fe94b9137cb in () at /usr/lib/libQt5Core.so.5 #6 0x7fe94d0bb6b8 in KWin::Cursors::positionChanged(KWin::Cursor*, QPoint const&) () at /usr/lib/libkwin.so.5 #7 0x7fe94b9137cb in () at /usr/lib/libQt5Core.so.5 #8 0x7fe94d0bb4f3 in KWin::Cursor::posChanged(QPoint const&) () at /usr/lib/libkwin.so.5 #9 0x7fe94d1aa091 in () at /usr/lib/libkwin.so.5 #10 0x7fe94b9137cb in () at /usr/lib/libQt5Core.so.5 #11 0x7fe94d0bbd83 in KWin::InputRedirection::globalPointerChanged(QPointF const&) () at /usr/lib/libkwin.so.5 #12 0x7fe94d1acfb8 in KWin::PointerInputRedirection::updatePosition(QPointF const&) () at /usr/lib/libkwin.so.5 #13 0x7fe94d1ad90d in KWin::PointerInputRedirection::processMotion(QPointF const&, QSizeF const&, QSizeF const&, unsigned int, unsigned long long, KWin::LibInput::Device*) () at /usr/lib/libkwin.so.5 #14 0x7fe94d15dd15 in () at /usr/lib/libkwin.so.5 #15 0x7fe94b9137cb in () at /usr/lib/libQt5Core.so.5 #16 0x7fe94d0bcc0a in KWin::LibInput::Connection::pointerMotion(QSizeF const&, QSizeF const&, unsigned int, unsigned long long, KWin::LibInput::Device*) () at /usr/lib/libkwin.so.5 #17 0x7fe94d18c7ca in KWin::LibInput::Connection::processEvents() () at /usr/lib/libkwin.so.5 #18 0x7fe94b90956f in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fe94c5bcd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fe94b8dc41a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fe94b8df519 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #22 0x7fe94b9324ec in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x55db5d5f2d7e in () #24 0x7fe94b8dad8c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7fe94b8e32f4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x55db5d58f8cb in () #27 0x7fe94b036b25 in __libc_start_main () at /usr/lib/libc.so.6 #28 0x55db5d5902ce in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445881] Destination application sometimes crashes upon paste
https://bugs.kde.org/show_bug.cgi?id=445881 --- Comment #2 from Lars Veldscholte --- Just got one of these crashes again. I tried to copy something from Firefox (running in native Wayland mode) to Kate. There doesn't seem to be a backtrace, though. This is the output from gdb: ``` (gdb) run Starting program: /usr/bin/kate [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffefccf640 (LWP 94845)] [New Thread 0x7fffedd18640 (LWP 94846)] kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open shared object file: No such file or directory)" kf.sonnet.core: Sonnet: Unable to load plugin "/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library /usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open shared object file: No such file or directory)" [New Thread 0x7fffecf6a640 (LWP 94847)] [New Thread 0x7fffe64f7640 (LWP 94848)] [New Thread 0x7fffe5cf6640 (LWP 94849)] [New Thread 0x7fffe54f5640 (LWP 94850)] [New Thread 0x7fffe4cf4640 (LWP 94851)] [New Thread 0x7fffd97d1640 (LWP 94852)] [New Thread 0x7fffd8fd0640 (LWP 94853)] [New Thread 0x7fffbbfff640 (LWP 94854)] [New Thread 0x7fffbb7fe640 (LWP 94855)] [New Thread 0x7fffbaffd640 (LWP 94856)] [New Thread 0x7fffba7fc640 (LWP 94857)] [New Thread 0x7fffb9ffb640 (LWP 94858)] [New Thread 0x7fffb97fa640 (LWP 94859)] [New Thread 0x7fffb8ff9640 (LWP 94860)] [New Thread 0x7fff9bfff640 (LWP 94861)] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [Detaching after fork from child process 94863] [Detaching after fork from child process 94865] [Detaching after fork from child process 94868] [Detaching after fork from child process 94869] [Detaching after fork from child process 94870] QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType text/plain;charset=utf-8 QWaylandDataOffer: timeout reading from pipe QWaylandDataOffer: error reading data for mimeType text/plain The Wayland connection broke. Did the Wayland compositor die? [Thread 0x7fffb8ff9640 (LWP 94860) exited] [Thread 0x7fffb97fa640 (LWP 94859) exited] [Thread 0x7fffb9ffb640 (LWP 94858) exited] [Thread 0x7fffba7fc640 (LWP 94857) exited] [Thread 0x7fffbaffd640 (LWP 94856) exited] [Thread 0x7fffbb7fe640 (LWP 94855) exited] [Thread 0x7fffbbfff640 (LWP 94854) exited] [Thread 0x7fffd8fd0640 (LWP 94853) exited] [Thread 0x7fffd97d1640 (LWP 94852) exited] [Thread 0x7fffe4cf4640 (LWP 94851) exited] [Thread 0x7fffe54f5640 (LWP 94850) exited] [Thread 0x7fffe5cf6640 (LWP 94849) exited] [Thread 0x7fffe64f7640 (LWP 94848) exited] [Thread 0x7fffecf6a640 (LWP 94847) exited] [Thread 0x7fffedd18640 (LWP 94846) exited] [Thread 0x7fffefccf640 (LWP 94845) exited] [Thread 0x71078a80 (LWP 94834) exited] [Inferior 1 (process 94834) exited with code 01] (gdb) bt No stack. ``` -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445883] Okular crashes when trying to save a documents on a CIFS-backed mount
https://bugs.kde.org/show_bug.cgi?id=445883
--- Comment #2 from Lars Veldscholte ---
(In reply to Albert Astals Cid from comment #1)
> The crash backtrace is a bit weird.
That's probably because I'm running Arch and therefore don't have any debug
symbols, sorry about that.
> Some questions:
> * Can you confirm this crash does not happen when saving somewhere else?
Yes, I've only observed this for files saved on that CIFS mount. It does not
happen on my local EXT4 file system, as far as I can tell.
> * Does this happen with any file or one in specific?
Happens with any file.
> * Do you get an error dialog?
After looking carefully, I think a dialog appears but the application crashes
immediately after so I don't have time to read it.
> * Does running from the terminal give any warning or error message written
> to it?
Yes, it does:
```
kf.kio.slaves.file: copy() QUrl("file:///tmp/okular.Lckzee") to
QUrl("file:///mnt/Data3/test.pdf") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
kf.kio.slaves.file: Couldn't rename "/mnt/Data3/test.pdf.part" to
"/mnt/Data3/test.pdf" ( Permission denied )
20 -- exe=/usr/bin/okular
17 -- platform=wayland
15 -- appname=okular
17 -- apppath=/usr/bin
10 -- signal=11
11 -- pid=160135
20 -- appversion=21.11.80
19 -- programname=Okular
31 -- bugaddress=sub...@bugs.kde.org
12 -- startupid=0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 160135
KCrash: Arguments: /usr/bin/okular test.pdf
KCrash: Attempting to start /usr/lib/drkonqi
fish: Job 1, 'okular test.pdf' has stopped
```
> * Can you run "valgrind okular myfile.pdf" and make what you do to make it
> crash and attach the output?
Interesting. With Valgrind, Okular doesn't crash, but the same thing happens:
the file gets renamed with `.part` appended. A error dialog appears with the
message "Could not open file:///mnt/Data3/test.pdf".
The output from Valgrind is:
```
==161848== Memcheck, a memory error detector
==161848== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==161848== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==161848== Command: okular test.pdf
==161848==
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open
shared object file: No such file or directory)"
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x110BD0E7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0xF22C6B7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x109E86A7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0xF22CD67: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x102B6DB7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x102B73B7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x102B79B7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x102B7D27: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10A05F77: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10A06577: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10A23C07: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10A24207: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10A24807: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10E0E3E7: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10E0E977: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==at 0xF9FFB5D: ???
==161848==by 0x10E0EF77: ???
==161848==
==161848== Conditional jump or move depends on uninitialised value(s)
==161848==
[okular] [Bug 445883] New: Okular crashes when trying to save a documents on a CIFS-backed mount
https://bugs.kde.org/show_bug.cgi?id=445883 Bug ID: 445883 Summary: Okular crashes when trying to save a documents on a CIFS-backed mount Product: okular Version: 21.11.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: l...@tuxplace.nl Target Milestone: --- SUMMARY When I edit and try to save a document on a SMB share mounted locally in /mnt/ using the CIFS driver, Okular crashes. The document does end up being saved, but with `.part` added to its filename. The document appears intact when removing the `.part` suffix from its filename and opening it again. STEPS TO REPRODUCE 1. Open a document from a CIFS-backed mount. 2. Edit it. 3. Try to save it. OBSERVED RESULT Okular crashes and the file is saved with `.part` appended to its filename. EXPECTED RESULT The file is saved as normal. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION Backtrace: #0 0x7f20c5497d22 in raise () from /usr/lib/libc.so.6 #1 0x7f20c70563e0 in KCrash::defaultCrashHandler(int) () from /usr/lib/libKF5Crash.so.5 #2 #3 0x7f208cda5a7a in FormWidgetText::getContent() const () from /usr/lib/libpoppler.so.115 #4 0x7f20bc17cb65 in Poppler::FormFieldText::text() const () from /usr/lib/libpoppler-qt5.so.1 #5 0x7f20bd940603 in ?? () from /usr/lib/qt/plugins/okular/generators/okularGenerator_poppler.so #6 0x7f20be4b7322 in ?? () from /usr/lib/qt/plugins/okularpart.so #7 0x7f20c5b2d7ab in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f20c5b2d7e0 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f20c686481b in QWidgetTextControl::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQt5Widgets.so.5 #10 0x7f20c5b2d4f7 in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7f20c6094c9e in QTextDocumentPrivate::finishEdit() () from /usr/lib/libQt5Gui.so.5 #12 0x7f20c6861d06 in ?? () from /usr/lib/libQt5Widgets.so.5 #13 0x7f20c6857d1c in QWidgetTextControl::processEvent(QEvent*, QPointF const&, QWidget*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f20c683718d in QTextEdit::inputMethodEvent(QInputMethodEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f20c66a00be in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f20c674f94f in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7f20c665cd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f20c5af63fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #19 0x7f20c3947f34 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #20 0x7f20c66bcf8f in ?? () from /usr/lib/libQt5Widgets.so.5 #21 0x7f20c665cd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x7f20c5af63fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #23 0x7f20c5f5c4fe in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5 #24 0x7f20c5f357d5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #25 0x7f20c39691e1 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #26 0x7f20c40734dc in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0x7f20c40c7799 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0x7f20c4070bc1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0x7f20c5b4f026 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #30 0x7f20c5af4d6c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #31 0x7f20c68713de in QDialog::exec() () from /usr/lib/libQt5Widgets.so.5 #32 0x7f20c6dbb040 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&, QMessageBox::Icon) () from /usr/lib/libKF5WidgetsAddons.so.5 #33 0x7f20c6dbb631 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&) () from /usr/lib/libKF5WidgetsAddons.so.5 #34 0x7f20c6dbf8c8 in ?? () from /usr/lib/libKF5WidgetsAddons.so.5 #35 0x7f20c6dc0050 in KMessageBox::error(QWidget*, QString const&, QString const&, QFlags) () from /usr/lib/libKF5WidgetsAddons.so.5 #36 0x7f20be469613 in Okular::Part::openUrl(QUrl const&, bool)
[kwin] [Bug 445881] New: Destination application sometimes crashes upon paste
https://bugs.kde.org/show_bug.cgi?id=445881 Bug ID: 445881 Summary: Destination application sometimes crashes upon paste Product: kwin Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: l...@tuxplace.nl Target Milestone: --- SUMMARY Every so often, when pasting something from the clipboard, the destination application crashes. This will happen reliably, until the *source* application is restarted. Only then, (after copying the data again), it can be properly pasted without a crash. STEPS TO REPRODUCE 1. Copy something 2. Paste it OBSERVED RESULT The destination application crashes. EXPECTED RESULT The contents of the clipboard is pasted. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15,5 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 391661] KDialog's Open File dialog hangs if an automount NFS share is unavailable
https://bugs.kde.org/show_bug.cgi?id=391661 --- Comment #5 from Lars Bischoff --- meanwhile I found that my issue was addressed here: https://bugs.kde.org/show_bug.cgi?id=442106 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442106] "UUID" or "LABEL" fstab entries cause file browsing slowdown (kio commit 7de9c2e3)
https://bugs.kde.org/show_bug.cgi?id=442106 Lars Bischoff changed: What|Removed |Added CC||lbisch...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 391661] KDialog's Open File dialog hangs if an automount NFS share is unavailable
https://bugs.kde.org/show_bug.cgi?id=391661 Lars Bischoff changed: What|Removed |Added CC||lbisch...@gmx.de --- Comment #4 from Lars Bischoff --- I have observed the same but it is not limited to NFS shares. For me file dialogs get slow when I have a "noauto" mount entry in /etc/fstab AND that device is not available. In my case that is the entry for an external USB-HD: LABEL=ExtBackup /media/ebackup ext4defaults,lazytime,noauto0 2 If I comment out that line, dolphin (and other file dialogs) are fast and responsive. If the line is active AND the ExtHD is not connected, then browsing dirs is extremely sluggish (upto few seconds delays). If the ExtHD is connected but not mounted, then also everything behaves normally. I'm using Kubuntu 21.10 with Plasma 5.22.5 and Frameworks 5.86.0. Kubuntu 21.04 did not had this problem yet. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441791] I'd love an option to inherit tag icon
https://bugs.kde.org/show_bug.cgi?id=441791 Lars Goldschlager changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Lars Goldschlager --- Please disregard, this is the current behaviour by default. I hadn't added new subtags after changing the icon of a tag before sending the email. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441791] New: I'd love an option to inherit tag icon
https://bugs.kde.org/show_bug.cgi?id=441791 Bug ID: 441791 Summary: I'd love an option to inherit tag icon Product: digikam Version: 7.3.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: lars.g...@gmail.com Target Milestone: --- I'd love if it would be possible to configure a tag (during creation and edit) such as its subtags in the hierarchy inherit the tag's icon. My use case is as follows, I have a tag hierarchy for bands with one subtag for each band, whose name is many times the name of the lead, but I also have the lead's name inside the people hierarchy. I'll sometimes tag a photo with both but sometimes with one of the two, so I want to identify them easily, so I use special icons for the bands hierarchy and all the band names. Right now I have to manually add the special icon to each band and I'd love it to be able to set a tag so that any subtag added automatically get its parent's icon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441005] kwin doesn't read WM_CLASS with a single string (bitwig studio)
https://bugs.kde.org/show_bug.cgi?id=441005 --- Comment #10 from lars --- Thank you very much <3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441005] kwin doesn't read WM_CLASS with a single string (bitwig studio)
https://bugs.kde.org/show_bug.cgi?id=441005 --- Comment #8 from lars --- I've shortly read the conversation you had over at the merge request. While you could argue that it is Bitwigs fault in this case, I would also argue that its possible to read the data correctly, as xprop shows. So why wouldn't we include this fallback? It would definitively be helpful with future applications that fail to meet spec. Just my two cents. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 155903] dolphin works fine but when i close the programe the KDE crash Handler appears
https://bugs.kde.org/show_bug.cgi?id=155903 --- Comment #4 from Lars Sørensen --- Created attachment 141000 --> https://bugs.kde.org/attachment.cgi?id=141000=edit New crash information added by DrKonqi dolphin (21.08.0) using Qt 5.15.2 - What I was doing when the application crashed: Right-clicked the Task Manager on the panel and selected close and then dolphin crashed. -- Backtrace (Reduced): #4 0x7f1d85caec73 in QStackedLayout::widget(int) const () from /lib64/libQt5Widgets.so.5 #5 0x7f1d5ff4fa1d in Konsole::TabbedViewContainer::viewSplitterAt(int) () from /lib64/libkonsoleprivate.so.21 #6 0x7f1d5ff528a6 in Konsole::TabbedViewContainer::currentTabViewCount() () from /lib64/libkonsoleprivate.so.21 #7 0x7f1d5fefa849 in Konsole::ViewManager::sessionFinished() () from /lib64/libkonsoleprivate.so.21 #8 0x7f1d85120c99 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 155903] dolphin works fine but when i close the programe the KDE crash Handler appears
https://bugs.kde.org/show_bug.cgi?id=155903 Lars Sørensen changed: What|Removed |Added CC||d...@lrss.dk -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441468] New: Locale breaks when changing region
https://bugs.kde.org/show_bug.cgi?id=441468
Bug ID: 441468
Summary: Locale breaks when changing region
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: erago...@gmx.net
Target Milestone: ---
SUMMARY
Locale breaks when changing region, which results in a lot of different errors
like crashing applications and error logs when updating/upgrading packages with
apt.
STEPS TO REPRODUCE
1. Install a fresh copy of Kubuntu 21.04 with the default language being
American English
2. Change the country under System Settings -> Regional Settings -> Formats ->
Region to Germany (in my case, this is not just a bug specific to Germany)
3. enter "perl" into a terminal and watch the locale break. You should see
something like this:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US",
LC_ALL = (unset),
LC_ADDRESS = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_PAPER = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_TIME = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LANG = "en_DE.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
OBSERVED RESULT
Simply changing the region to a different language breaks the locale, which can
lead to a plethora of different problems outlined in other reports of this bug
(linked below).
In my case for example, anki crashes in program launch because of a broken
UTF-8 locale
Here is an old report of one user changing his region to Greek:
===
New installation of Kubuntu 14.04 and upgraded via kubuntu-ppa. Initially,
country is set to "United States". The locale settings are the following:
~/.kde/env$ cat setlocale.sh
export LANG=en_US.UTF-8
export LANGUAGE=en:el:en
export LC_NUMERIC=en_US.UTF-8
export LC_TIME=en_US.UTF-8
export LC_MONETARY=en_US.UTF-8
export LC_PAPER=en_US.UTF-8
export LC_IDENTIFICATION=en_US.UTF-8
export LC_NAME=en_US.UTF-8
export LC_ADDRESS=en_US.UTF-8
export LC_TELEPHONE=en_US.UTF-8
export LC_MEASUREMENT=en_US.UTF-8
Then, I change Country to Greece, via System Settings. Locale changes as
follows:
export LANG=en_GR.UTF-8
export LANGUAGE=en:el:en
export LC_NUMERIC=en_GR.UTF-8
export LC_TIME=en_GR.UTF-8
export LC_MONETARY=en_GR.UTF-8
export LC_PAPER=en_GR.UTF-8
export LC_IDENTIFICATION=en_GR.UTF-8
export LC_NAME=en_GR.UTF-8
export LC_ADDRESS=en_GR.UTF-8
export LC_TELEPHONE=en_GR.UTF-8
export LC_MEASUREMENT=en_GR.UTF-8
As far as I know, en_GR.UTF-8 is not a valid entry. A severe loss of
functionality is that accents cannot be set properly to greek vowels.
===
Even there is no setlocale.sh on my system, there is a /etc/default/locale
file, which is essentially the same but without all the export statements.
You can partially fix this issue by editing that file, but I still haven't been
able to fix the errors perl throws at me. I would like to retest this with a
fresh installation but I cannot get VirtualBox running.
EXPECTED RESULT
The locale should be correct after changing the region.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 21.04
(available in About System)
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
https://bugs.kde.org/show_bug.cgi?id=335301 is the initial report of this from
seven years ago, and even though it was "resolved downstream", its still an
issue seven years later. These kind of bugs are what gets a lot of users
(including me, at least once!) to switch back to windows or mac because they
get these basics right. I shouldn't have to edit a config file in order for my
PC to work out of the box. And living in Germany/Greece/Norway or wherever and
simply wanting your PC to be in English is, and should not, be "wrong",
impossible or result in a broken locale, like some others pointed out.
Personally I found the above bug report via
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1322968, which was
closed yesterday. We were asked to open a new bug report with this issue here,
as you can see by the last few comments on that bug report.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 441005] kwin doesn't read WM_CLASS with a single string (bitwig studio)
https://bugs.kde.org/show_bug.cgi?id=441005 --- Comment #7 from lars --- Wow, thanks for following up on this so fast :) I just wrote a mail to Bitwig's support, describing the issue to them and linking the specification. Please hit me up if there's anything else I can do or test. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441005] kwin can't read WM_CLASS while xprop can
https://bugs.kde.org/show_bug.cgi?id=441005 --- Comment #3 from lars --- Should i update the kwin version in the initial bug report or is it fine to leave it for now? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441005] kwin can't read WM_CLASS while xprop can
https://bugs.kde.org/show_bug.cgi?id=441005 --- Comment #2 from lars --- I just upgraded to 5.22 using the backport PPA but the issue still persists. The exact version numbers in the system settings are now: KDE Plasma Version 5.22.4 KDE Frameworks Version 5.85.0 Qt Version 5.15.2 Kernel Version 5.11.0-31-generic (64-bit) Graphics Platform X11 kwin -v also reports 5.22.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441005] New: kwin can't read WM_CLASS while xprop can
https://bugs.kde.org/show_bug.cgi?id=441005 Bug ID: 441005 Summary: kwin can't read WM_CLASS while xprop can Product: kwin Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: erago...@gmx.net Target Milestone: --- SUMMARY kwin can't read WM_CLASS of a specific application (bitwig studio), even though xprop can. Because of this, i have to use the window title to create an application rule, which could potentially break. STEPS TO REPRODUCE 1. install bitwig studio and launch the application in demo or guest mode 2. open system settings and navigate to Window Management -> Window Rules -> New -> Detect Window Properties and click the bitwig studio window. 3. open a terminal, run xprop and click the bitwig studio window OBSERVED RESULT xprop correctly shows "WM_CLASS(STRING) = 'com.bitwig.BitwigStudio'", which is exactly what is specified in the .dekstop file. kwin however returns "()" as window class. EXPECTED RESULT kwin should be able to read the WM_CLASS just like xprop SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04.2 LTS (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION 1. The Bitwig GUI is written in Java as far as i know, and the window also has no title bar. 2. Im new to KDE and Linux in general as well as bug reporting so please excuse me if this has been fixed. I searched for a bit but i couldn't find a similar issue. Im on Kubuntu 20.04.2 LTS, which means that kwin is stuck in version 5.18.5. No idea if this has been fixed since. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438111] Starting Firefox in Wayland mode crashes kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=438111 --- Comment #5 from Lars Veldscholte --- (In reply to Vlad Zahorodnii from comment #4) > Another option is to wait for 5.22 to be released. If kwin doesn't crash in > 5.22, this bug report can be closed. The problem is indeed gone in 5.22 :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438111] Starting Firefox in Wayland mode crashes kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=438111 --- Comment #3 from Lars Veldscholte --- (In reply to Vlad Zahorodnii from comment #2) > Looks like a dup of bug 437115. Can you please get a backtrace of the crash > with debug symbols? That indeed looks to be the same bug. I'm running Arch, so I'd have to look into how to build KWin with debug symbols... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438111] Starting Firefox in Wayland mode crashes kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=438111 --- Comment #1 from Lars Veldscholte --- Backtrace: Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /usr/lib/startplasma-waylandsession'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f1e04c16b8e in ?? () from /usr/lib/libkwin.so.5 [Current thread is 1 (Thread 0x7f1dfdc31840 (LWP 10108))] (gdb) bt #0 0x7f1e04c16b8e in () at /usr/lib/libkwin.so.5 #1 0x7f1e049dc83b in () at /usr/lib/libkwin4_effect_builtins.so.1 #2 0x7f1e049dcfea in () at /usr/lib/libkwin4_effect_builtins.so.1 #3 0x7f1e04c1356d in KWin::EffectsHandlerImpl::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () at /usr/lib/libkwin.so.5 #4 0x7f1e04a180fb in () at /usr/lib/libkwin4_effect_builtins.so.1 #5 0x7f1e04c1356d in KWin::EffectsHandlerImpl::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () at /usr/lib/libkwin.so.5 #6 0x7f1e04a1c88c in () at /usr/lib/libkwin4_effect_builtins.so.1 #7 0x7f1e04c1356d in KWin::EffectsHandlerImpl::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () at /usr/lib/libkwin.so.5 #8 0x7f1e04c8e40a in KWin::Scene::paintGenericScreen(int, KWin::ScreenPaintData const&) () at /usr/lib/libkwin.so.5 #9 0x7f1dfc0b2c8e in () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x7f1e04c8a52a in KWin::Scene::finalPaintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #11 0x7f1e04c133fa in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #12 0x7f1e04c133fa in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #13 0x7f1e04c133fa in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #14 0x7f1e04c133fa in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /usr/lib/libkwin.so.5 #15 0x7f1e04c8f866 in KWin::Scene::paintScreen(int*, QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () at /usr/lib/libkwin.so.5 #16 0x7f1dfc0b8024 in KWin::SceneOpenGL::paint(int, QRegion const&, QList const&, KWin::RenderLoop*) () at /usr/lib/qt/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #17 0x7f1e04be60da in KWin::Compositor::composite(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #18 0x7f1e032963bb in () at /usr/lib/libQt5Core.so.5 #19 0x7f1e04b9e043 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /usr/lib/libkwin.so.5 #20 0x7f1e04c7dce4 in KWin::RenderLoopPrivate::dispatch() () at /usr/lib/libkwin.so.5 #21 0x7f1e032963bb in () at /usr/lib/libQt5Core.so.5 #22 0x7f1e0329a38b in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #23 0x7f1e0328c07f in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f1e040cbd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f1e0325f00a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f1e032b6fad in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #27 0x7f1e032b5489 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x56029ccb8bbe in () #29 0x7f1e0325d97c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #30 0x7f1e03265ee4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #31 0x56029cc62f94 in () #32 0x7f1e029e1b25 in __libc_start_main () at /usr/lib/libc.so.6 #33 0x56029cc63b4e in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438111] New: Starting Firefox in Wayland mode crashes kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=438111 Bug ID: 438111 Summary: Starting Firefox in Wayland mode crashes kwin_wayland Product: kwin Version: 5.21.90 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: l...@tuxplace.nl Target Milestone: --- SUMMARY With the latest version of Firefox Beta (90.0), the compositor crashes when Firefox is started in Wayland mode. This didn't happen with the previous version of Firefox, and it also doesn't happen with Firefox in XWayland mode. STEPS TO REPRODUCE 1. Start Firefox 90.0 OBSERVED RESULT The compositor crashes. EXPECTED RESULT The compositor doesn't crash ;) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.8-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437487] [Wayland] Plasmashell crashes when moving panel between screens
https://bugs.kde.org/show_bug.cgi?id=437487 --- Comment #3 from Lars Veldscholte --- @Nathan I tried getting a backtrace but there doesn't seem to be one; it appears that plasmashell just quits rather than crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437491] New: No x-axis labels on charts
https://bugs.kde.org/show_bug.cgi?id=437491
Bug ID: 437491
Summary: No x-axis labels on charts
Product: plasma-systemmonitor
Version: 5.21.90
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: l...@tuxplace.nl
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
The charts in the System Monitor lack axis labels for the x-axis
(horizontal/time axis). This makes is difficult to gauge what the time range
shown is.
I don't know if this is a deliberate choice, given that KSysGuard suffers from
the exact same issue, but I think it would be good to have them; either as just
two points at the ends ("60 s ago" and "now"), or regular labels at fixed
intervals, maybe configurable.
SOFTWARE/OS VERSIONS
System Monitor 5.21.90
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 437487] [Wayland] Plasmashell crashes when moving panel between screens
https://bugs.kde.org/show_bug.cgi?id=437487 Lars Veldscholte changed: What|Removed |Added Summary|[Wayland] Plasmashell |[Wayland] Plasmashell |crashes when moving between |crashes when moving panel |screens |between screens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437487] New: [Wayland] Plasmashell crashes when moving between screens
https://bugs.kde.org/show_bug.cgi?id=437487 Bug ID: 437487 Summary: [Wayland] Plasmashell crashes when moving between screens Product: plasmashell Version: 5.21.90 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: l...@tuxplace.nl Target Milestone: 1.0 Created attachment 138670 --> https://bugs.kde.org/attachment.cgi?id=138670=edit log output of `WAYLAND_DEBUG=1 plasmashell --replace` SUMMARY In a multi-monitor setup, when moving a panel between screens, plasmashell crashes. STEPS TO REPRODUCE 1. Edit a panel 2. Drag it over to a different screen OBSERVED RESULT Plasmashell crashes. EXPECTED RESULT The panel is moved without a crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600 Six-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: AMD Radeon ™ RX 480 Graphics ADDITIONAL INFORMATION See attached the log output of `WAYLAND_DEBUG=1 plasmashell --replace`. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 436033] New: k3b handbook did f1 did not works
https://bugs.kde.org/show_bug.cgi?id=436033 Bug ID: 436033 Summary: k3b handbook did f1 did not works Product: k3b Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@kde.org Reporter: lars_mart...@hotmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY Fedora 34 beta Gnome 40 wayland STEPS TO REPRODUCE 1. Help 2. k3b Handbook F1 3. OBSERVED RESULT Did not start did not get errror EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 436011] Burning isssue with k3b without error
https://bugs.kde.org/show_bug.cgi?id=436011 --- Comment #1 from Lars Martin Hambro --- Created attachment 137765 --> https://bugs.kde.org/attachment.cgi?id=137765=edit k3b md5 sum shasum256 missing and check for disk error. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 436011] New: Burning isssue with k3b without error
https://bugs.kde.org/show_bug.cgi?id=436011 Bug ID: 436011 Summary: Burning isssue with k3b without error Product: k3b Version: 19.12 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Formats Assignee: k...@kde.org Reporter: lars_mart...@hotmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Download a iso files an check shasum 256 its missing to check the cha256 sum on program and sum match. But software did not have any confirm that its works. STEPS TO REPRODUCE Download: https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64-Current.iso Check sum (terminal sha256sum openSUSE-Tumbleweed-DVD-x86_64-Current.iso Match after: dd if= /media/larsmartin/openSUSE-Tumbleweed-DVD-x86_6426 |sha256sum get e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 OBSERVED RESULT Wrong checksum but get passed on burning. Asus BW-14D1XT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux Mint 20.1 Cinnamon KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Type: DVD-R Media ID: TYG03 Capacity: 509:29:61 min (4,4 GiB) Used Capacity: 509:29:61 min (4,4 GiB) Remaining: 00:00:00 min (0 B) Rewritable: no Appendable: no Empty: no Layers: 1 Sessions: 1 Supported writing speeds: 8.0x (11080 KB/s) 12.0x (16620 KB/s) 16.0x (22160 KB/s) ISO 9660 Filesystem Info System Id: LINUX Volume Id: openSUSE-Tumbleweed-DVD-x86_6426 Volume Set Id: - Publisher Id: SUSE LINUX GmbH Preparer Id:KIWI - http://opensuse.github.com/kiwi Application Id: openSUSE-Tumbleweed-DVD-x86_64-Build2665.1-Media Volume Size:4,4 GiB (2 048 B * 2 292 673 blocks = 4 695 394 304 B) Tracks TypeAttributes First-Last Sector Length 1 (Data) no copy/uninterrupted 0 - 2292735 2292736 (509:29:61) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #21 from Lars Ivar Igesund --- I'm currently at Kubuntu 20.04, and also a newer Precision (5530) than the one I reported from last time. I don't think I've seen this issue come up again, so feel free to close on my part. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433094] No way to disable tearing prevention
https://bugs.kde.org/show_bug.cgi?id=433094 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430111] Plasma Wayland crashes when changing order of pinned application
https://bugs.kde.org/show_bug.cgi?id=430111 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl --- Comment #5 from Lars Veldscholte --- Maybe this is helpful: the crash does not occur if I disable tooltips in the Task Manager. FYI this problem applies to all applications in the Task Manager for me, not just pinned ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416869] [Wayland] Tooltip dismisses context menu of systray icons and they become unresponsive to mouse clicks
https://bugs.kde.org/show_bug.cgi?id=416869 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl --- Comment #4 from Lars Veldscholte --- Can also confirm (on Wayland). I'm not sure if it's the exact same issue, but I have a similar problem with the Task Manager's tooltips: STEPS TO REPRODUCE 1. Hover over an application in the Task Manager so the tooltip (with preview) appears 2. Right-click the application so the context menu appears 3. Move your cursor to the context menu OBSERVED RESULT Both the tooltip and the context menu close immediately. This does not happen if you're quick enough to open the context menu before the tooltip appears. EXPECTED RESULT The context menu stays open. Operating System: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.9-arch1-1 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Lars Wendler (Polynomial-C) changed: What|Removed |Added CC||polynomia...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428987] Reordering task manager tasks on the panel make the wayland session crash
https://bugs.kde.org/show_bug.cgi?id=428987 --- Comment #17 from Lars Veldscholte --- Is there something I can try to get a valid backtrace? I'd glad to help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428987] Reordering task manager tasks on the panel make the wayland session crash
https://bugs.kde.org/show_bug.cgi?id=428987 Lars Veldscholte changed: What|Removed |Added CC||l...@tuxplace.nl --- Comment #12 from Lars Veldscholte --- I have the exact same issue. My system info: Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.9-zen1-1-zen OS Type: 64-bit Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD RENOIR I also tried to retrieve a backtrace but got the same output as Nicola: > Backtrace stopped: Cannot access memory at address 0x7ffea621a6d0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418050] KDE Plasma crash on systray click
https://bugs.kde.org/show_bug.cgi?id=418050 Lars Segelken changed: What|Removed |Added CC||lars...@northernraven.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422624] Akonadi does full rescan on every change in maildir
https://bugs.kde.org/show_bug.cgi?id=422624 --- Comment #3 from Lars Doelle --- Hi All, meanwhile the situation has been improved and kmail appears to work normally again here. I cannot provide much further information, beside that i'm running sid and only some library material has been updated. From my side, the report can be closed. Thanks Lars -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418951] The composer breaks down after you unlock the pc
https://bugs.kde.org/show_bug.cgi?id=418951 --- Comment #27 from Lars Wendler (Polynomial-C) --- I have the same problem on an up-to-date Gentoo system. The issue started after upgrading to plasma-5.18 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418951] The composer breaks down after you unlock the pc
https://bugs.kde.org/show_bug.cgi?id=418951 Lars Wendler (Polynomial-C) changed: What|Removed |Added CC||polynomia...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422624] New: Akonadi does full rescan on every change in maildir
https://bugs.kde.org/show_bug.cgi?id=422624 Bug ID: 422624 Summary: Akonadi does full rescan on every change in maildir Product: Akonadi Version: 5.14.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: lars.doe...@on-line.de Target Milestone: --- Hi All, for some days now, akonadi apparently fully scans the maildir whenever anything is changed, i.e. mail received, sent, deleted, etc. This process takes about 2 minutes for the 10.000 mails i have in the maildir. Beside this problem makes kmail virtually unusable for more but a few actions per day, it also has the potential to age the SSD. Unfortunately, i cannot give much further information, but i usually experience such kind of errors during scanning, when something fails to parse. Thus the issue could be triggered by some mail not formatted as it should be, perhaps. In any case, i believe it is a local issue. I write for any suggestion what i could do to further narrow the bug or work around it. I already tried without success: $ akonadictl fsck Kind regards Lars -- You are receiving this mail because: You are watching all bug changes.
