[plasmashell] [Bug 490346] Plasmashell crashes while the PC is idling
https://bugs.kde.org/show_bug.cgi?id=490346 --- Comment #1 from David Tonhofer --- Created attachment 171704 --> https://bugs.kde.org/attachment.cgi?id=171704&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490346] New: Plasmashell crashes while the PC is idling
https://bugs.kde.org/show_bug.cgi?id=490346 Bug ID: 490346 Summary: Plasmashell crashes while the PC is idling Classification: Plasma Product: plasmashell Version: 6.1.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: bugh...@gluino.name Target Milestone: 1.0 Application: plasmashell (6.1.2) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.8-200.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 40 (KDE Plasma)" DrKonqi: 6.1.2 [CoredumpBackend] -- Information about the crash: Locked screen and left machine. Coming back, the Crash Handler had opened with a crash report. This seems to happen from time to time. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f72b15e02f7 in QV4::ExecutableAllocator::allocate (this=this@entry=0x55dc7470de20, size=1408, size@entry=1395) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/qml/jsruntime/qv4executableallocator.cpp:168 #6 0x7f72b18c588d in JSC::ExecutableMemoryHandle::ExecutableMemoryHandle (this=0x55dc76cd34b0, allocator=0x55dc7470de20, size=1395) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/qml/../3rdparty/masm/stubs/ExecutableAllocator.h:36 #7 JSC::ExecutableAllocator::allocate (this=, size=1395) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/qml/../3rdparty/masm/stubs/ExecutableAllocator.h:73 #8 JSC::AssemblerBuffer::executableCopy (ownerUID=, effort=, this=0x55dc772e23b8, globalData=...) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/qml/../3rdparty/masm/assembler/AssemblerBuffer.h:138 #9 JSC::X86Assembler::X86InstructionFormatter::executableCopy (this=0x55dc772e23b8, globalData=..., ownerUID=0x0, effort=JSC::JITCompilationMustSucceed) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/qml/../3rdparty/masm/assembler/X86Assembler.h:2423 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485258] Dolphin crashed after dragging a file to the path breadcrumb
https://bugs.kde.org/show_bug.cgi?id=485258 --- Comment #33 from David Tonhofer --- I'm on Fedora 40 an according to the "About This System" tool, I have: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland This bug is not currently happening so, looks fine. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485786] Moving a directory/file with the cursor crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=485786 --- Comment #7 from David Tonhofer --- Seems to happen at or a bit beyond deleteLater() See also: #486065 "dolphin crashed while draggin a video file to another app" #486454 "Dolphin crashed when dragging and dropping an .mkv file onto firefox" -- gets a bit further than deleteLater() #486579 "Dolphin crash" -- gets a bit further than deleteLater() #486589 "Dolphin crashes with segfault when space is pressed (maybe)" #486702 "Drag file from Dolphin to elsewhere" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485786] Moving a directory/file with the cursor crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=485786 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #6 from David Tonhofer --- Encountered on Fedora 40. KDE Info Center / About this system reports: Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland #4 0x7f8f441e950e in QObject::deleteLater() () at /lib64/libQt6Core.so.6 #5 0x7f8f46a7055c in KDEPrivate::KUrlNavigatorButton::dragMoveEvent(QDragMoveEvent*) () at /lib64/libKF6KIOFileWidgets.so.6 #6 0x7f8f453ebe00 in QWidget::event(QEvent*) () at /lib64/libQt6Widgets.so.6 #7 0x7f8f4538b368 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #8 0x7f8f453963bb in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #9 0x7f8f44195ab8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #10 0x7f8f4540157e in QWidgetWindow::handleDragMoveEvent(QDragMoveEvent*) () at /lib64/libQt6Widgets.so.6 #11 0x7f8f4540261e in QWidgetWindow::event(QEvent*) () at /lib64/libQt6Widgets.so.6 #12 0x7f8f4538b368 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt6Widgets.so.6 #13 0x7f8f44195ab8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt6Core.so.6 #14 0x7f8f449e6e5a in QGuiApplicationPrivate::processDrag(QWindow*, QMimeData const*, QPoint const&, QFlags, QFlags, QFlags) () at /lib64/libQt6Gui.so.6 #15 0x7f8f44a47fbd in QWindowSystemInterface::handleDrag(QWindow*, QMimeData const*, QPoint const&, QFlags, QFlags, QFlags) () at /lib64/libQt6Gui.so.6 #16 0x7f8f41579761 in QtWaylandClient::QWaylandDataDevice::data_device_motion(unsigned int, int, int) () at /lib64/libQt6WaylandClient.so.6 Easily reproducible, one just need to "grab a file" and slide it over the widgets of the window (not the contents). It's probably a problem with a popup. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486579] New: Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=486579
Bug ID: 486579
Summary: Dolphin crash
Classification: Applications
Product: dolphin
Version: 24.02.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: bugh...@gluino.name
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (24.02.2)
Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.8-300.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.4 [CoredumpBackend]
-- Information about the crash:
Dolphin crashes when I moved a file into a subdirectory
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/dolphin...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/2d85b7f56c5d3f0e70c0251b556750c1c75dd942/debuginfo...
[New LWP 102895]
[New LWP 102898]
[New LWP 102896]
[New LWP 102899]
[New LWP 104236]
[New LWP 102914]
[New LWP 104049]
[New LWP 104321]
[New LWP 104322]
[New LWP 104422]
[New LWP 102897]
[New LWP 104421]
[New LWP 104320]
[New LWP 102900]
Downloading separate debug info for /lib64/libdolphinprivate.so.6...
Downloading separate debug info for /lib64/libKF6NewStuffWidgets.so.6...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/b6af9b48bcf77df2fba399e6d9aee71af0ec9d9f/debuginfo...
Downloading separate debug info for /lib64/libKF6Parts.so.6...
Downloading separate debug info for /lib64/libKF6BalooWidgets.so.6...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/41a4b3f59eaafb61a139d83a0cc0dcb5eee7d139/debuginfo...
Downloading separate debug info for /lib64/libKF6Baloo.so.6...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/5d00577cc00f1cec147bbb297cc7e2fc80d944c8/debuginfo...
Downloading separate debug info for /lib64/libphonon4qt6.so.4...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/043050b76efaaf923172e6af15f67c0cf40532d2/debuginfo...
Downloading separate debug info for /lib64/libKF6UserFeedbackWidgets.so.6...
Downloading separate debug info for /lib64/libdolphinvcs.so.6...
Downloading separate debug info for /lib64/libKF6FileMetaData.so.3...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/ab93065c3cd5c4b270aedd6d1936242f32736981/debuginfo...
Downloading separate debug info for /lib64/libKF6NewStuffCore.so.6...
Downloading separate debug info for /lib64/libKF6BalooEngine.so.6...
Downloading separate debug info for /lib64/libKF6Attica.so.6...
Downloading separate debug info for /lib64/libKF6Syndication.so.6...
Downloading separate debug info for /lib64/liblmdb.so.0.0.0...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/28fe8fe301d3607ab0923f01fb4653c38e87ba96/debuginfo...
Downloading separate debug info for /lib64/libnss_sss.so.2...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/41a35f1e4f0eb50136f0198670c5f7d8b6f0c026/debuginfo...
Downloading separate debug info for /lib64/libnss_systemd.so.2...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/forgetfileitemaction.so...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/678302e94e051ea002eaa7a16e8fbb05cf7bf439/debuginfo...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/kactivitymanagerd_fileitem_linking_plugin.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/tagsfileitemaction.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/compressfileitemaction.so...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/e84b15044cb43217762c0a31cbb8e203ed0ad92d/debuginfo...
Downloading separate debug info for /lib64/libkerfuffle.so.24...
Downloading separate debug info for /lib64/libKF6Pty.so.6...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/slideshowfileitemaction.so...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/0369fecfde07ff584ff8bb769ef327b01a16200a/debuginfo...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/plasmavaultfileitemaction.so...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/gdrivecontextmenuaction.so...
Downloading separate debug info for
/home/rost/.cache/debuginfod_client/5bfd0019c5b900887b1142cb410d7f8612e4464e/debuginfo...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kfileitemaction/kio-admin.so...
Downloading separate debug info for
/home/rost/.cache/debuginfod_clien
[Spectacle] [Bug 456232] Spectacle crashes when I switch to "capture window underneath cursor" (does not usually crash)
https://bugs.kde.org/show_bug.cgi?id=456232 --- Comment #2 from David Tonhofer --- Thank you, A cursory check indicates that the bug does not currently occur. I guess this can be closed ... I'm still running: Fedora 36: 6.2.15-100.fc36.x86_64 with Qt 5.15.8 with spectacle-22.12.0-1.fc36.x86_64 Best regards, -- David -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 450217] (SEGV) Crash in Akonadi::Server::AkonadiServer::connectionDisconnected
https://bugs.kde.org/show_bug.cgi?id=450217 --- Comment #21 from David Tonhofer --- Since postix has marked my report as duplicate, I will repost my way to reproduce reproducibly: 1) Start "Godot" 2) Have a "yellow tooltip" pop up about the window frame (not proper to Godot, but to the window manager) for example, go into the "minimize" button until "minimize" tooltip pops up 3) Move the mouse into the "minimize" tooltip 4) Kwin (not only Akonadi) crashes with segmentation fault. running: kwin-wayland-5.27.3-2.fc36 crash function: QTimer::timeout(QTimer::QPrivateSignal) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #5 from David Tonhofer --- Created attachment 157928 --> https://bugs.kde.org/attachment.cgi?id=157928&action=edit core backtrace collected at kwin crash This may only be remotely related to the reported bug -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #4 from David Tonhofer --- While trying to reproduce via: 1) Start Godot 2) Make a "yellow tooltip" pop up about the window frame (not proper to Godot but to the window manager) for example, go into the "minimize" button until "minimize" pops up 3) Move the mouse into the "minimize" tooltip 4) Kwin (not only Akonadi) crashes with segmentation fault (but I can't report bug because "kernel is tainted", cat /proc/sys/kernel/tainted says "512", i.e. "kernel issued warning"). running: kwin-wayland-5.27.3-2.fc36 crash function: QTimer::timeout(QTimer::QPrivateSignal) Attaching the "core_backtrace", for what it's worth -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash when cursor moves into a tooltip popup window
https://bugs.kde.org/show_bug.cgi?id=467430 David Tonhofer changed: What|Removed |Added Summary|Akonadi crash possibly due |Akonadi crash when cursor |to dolphin |moves into a tooltip popup ||window -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #2 from David Tonhofer --- VERY reproducible. But I'm not sure whether it is KDE/Qt, GTK or Fedora related. For example, if you have the "abrt" tool open (report-gtk) and you activate the tooltip for the "minimize" button in the "abrt" window's decorations and you move the mouse into the tooltip ... kwin_wayland goes down with segmentation fault. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 --- Comment #1 from David Tonhofer --- Created attachment 157520 --> https://bugs.kde.org/attachment.cgi?id=157520&action=edit New crash information added by DrKonqi akonadiserver (5.22.0 (22.12.0)) using Qt 5.15.8 I happened again. The triggering event seems to be a yellow-colored tooltip that pops up near the mouse. If the mouse cursor is moved into the tooltip, akonadi crashes. -- Backtrace (Reduced): #4 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff5f24b0b8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff5f24b0b8) at /usr/include/c++/12/bits/vector.tcc:181 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 467430] New: Akonadi crash possibly due to dolphin
https://bugs.kde.org/show_bug.cgi?id=467430 Bug ID: 467430 Summary: Akonadi crash possibly due to dolphin Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: akonadiserver (5.22.0 (22.12.0)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.18-100.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: I feel this is at least the 3 time I have encountered this crash What happens: - I have a large-ish list of ODT LibreOffice Text docucment, the directory where they reside is open in DOLPHIN - Iteratively do: -- Click on document, opening it. -- Edit the name of the document in DOLPHIN by prepending a date (_MM_DD_) found inside the document. Hit RETURN. -- This rearranges the document list in DOLPHIN of course (as expected, but I know that renaming documents in DOLPHIN used to be fraught with some arbitrariness & danger) -- Do not bother to close thise LibreOffice Writer instance, which accumulates windows, but that's ok as I can close them all in one click once done. The crash seems to occur after hitting RETURN upon having renamed a document. Also, YouTube is playing lofi in the background. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff9bf42a28) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff9bf42a28) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7fff9bf42a28) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7fff9bf429a0) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/akonadi.cpp:234 #11 0x7f0e8aec8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f0e8ae9d4cb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f0e8aea0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #14 0x7f0e8aeeeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7f0e89b18faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7f0e89b6e2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7f0e89b16940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7f0e8aeee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7f0e8ae9bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f0e8aea4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #21 0x55fcbd308058 in AkApplicationBase::exec (this=0x7fff9bf42970) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/shared/akapplication.cpp:107 #22 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.12.0-2.fc36.x86_64/src/server/main.cpp:65 [Inferior 1 (process 2555) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458511] New: If a PDF has a name containing double quotes, its preview is not rendered.
https://bugs.kde.org/show_bug.cgi?id=458511 Bug ID: 458511 Summary: If a PDF has a name containing double quotes, its preview is not rendered. Product: dolphin Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If a PDF has a name with double quotes, its preview is not rendered. For example, the preview is rendered in case the PDF is named a_b.pdf but is not rendered if the file is named a"b".pdf Additionally, the preview actually disappears if named in that way, either through dolphin or through the command line. (This may indicate that the filename string is passed to the shell in a command, but with quotes wrapped around, which may open a can of worms) Reproducible: Always KDE Frameworks: 5.97.0 Qt: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457265] New: Improvement: configuring the digital clock in the panel should be done in the same way as for "spectacle"
https://bugs.kde.org/show_bug.cgi?id=457265 Bug ID: 457265 Summary: Improvement: configuring the digital clock in the panel should be done in the same way as for "spectacle" Product: plasmashell Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: bugh...@gluino.name Target Milestone: 1.0 Created attachment 150969 --> https://bugs.kde.org/attachment.cgi?id=150969&action=edit Panel Digital Clock Settings vs clock settings available in "spectacle" Configuring the format of the digital clock in the panel is less than ideal: You have to choose the "format" implicitly associated with a country. But what is that format? What if you don't want that but prefer another system? By contrast, in spectacle for example, the filename accepts a date-time format string (sadly, and very confusingly, the codes are not the same as the ones used by date(1), which should also be fixed 😞 ) Maybe one could foresee the possibility of having a date-time format string for the clock widget too; maybe it can be pulled out of regional settings at first, but then be freely editable. See the configuration possibilities in the attached image -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457151] New: Filenames that have improper (non-UTF-8) characters are anathema to dolphin
https://bugs.kde.org/show_bug.cgi?id=457151 Bug ID: 457151 Summary: Filenames that have improper (non-UTF-8) characters are anathema to dolphin Product: dolphin Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: kfm-de...@kde.org Target Milestone: --- Created attachment 150916 --> https://bugs.kde.org/attachment.cgi?id=150916&action=edit The improperly named file in Dolphin I used to have a few files apparently from an old archive with characters that were not properly encoded as UTF-8, instead the bytestring for the filename was ISO-8859-1. So for example "ü" would be encoded as 0xFC or octal 374. I found out that it was impossible to rename to from inside Dolphin. For example, if you create a file "FührerCat.txt" with the ü encoded as 0xFC from the shell: - $ mkdir TEST && cd TEST $ touch $'F\xFChrerCat.txt' $ ls 'F'$'\374''hrerCat.txt' - Then the file is shown in dolphin with a placeholder (see attachment) but you cannot rename it. Dolphin says "the file does not exist" and refuses to rename it. I have renamed them from the command line but somehow a few ended up in the Trash, too (which can be done by moving their containing folder into the trash). In .local/share/Trash: - $ cd .local/share/Trash/ $ tree . ├── directorysizes ├── files │  └── TEST │  └── F\374hrerCat.txt └── info └── TEST.trashinfo 3 directories, 3 files - If one now attempts to empty the trash from Dolphin, Dolphin complains "could not remove folder" so one has to do it from the command line -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 456509] New: All applications suddenly ripped away while I do nothing special (since this morning's update: Fedora 36, updating
https://bugs.kde.org/show_bug.cgi?id=456509 Bug ID: 456509 Summary: All applications suddenly ripped away while I do nothing special (since this morning's update: Fedora 36, updating Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: akonadiserver (5.20.1 (22.04.1)) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.18.10-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: So I was editing something in LibreOffice writer, sometimes changing names of files in dolphin while watching Jimmy Dore on Youtube via Firefox. Then all the applications got ripped away. This already happened a bit earlier today when I move the mouse to the top right corner of the screen. Wham! All the applications are gone. This never happened before a "dnf update" I did "this morning" of 2022-07-09, so it has probably something to do with that. Unfortunately I do not know which packages those were. The "dnf.log" in /var/log is not informative enough and my script to track package updates is currently out of commission. Just the right time. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 std::default_delete::operator() (__ptr=0x110, this=) at /usr/include/c++/12/bits/unique_ptr.h:89 #5 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12/bits/unique_ptr.h:396 #6 std::__new_allocator > >::destroy > > (__p=, this=0x7fff2040bbf8) at /usr/include/c++/12/bits/new_allocator.h:181 #7 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12/bits/alloc_traits.h:535 #8 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7fff2040bbf8) at /usr/include/c++/12/bits/vector.tcc:181 #9 std::vector >, std::allocator > > >::erase (__position=..., this=0x7fff2040bbf8) at /usr/include/c++/12/bits/stl_vector.h:1530 #10 Akonadi::Server::AkonadiServer::connectionDisconnected (this=0x7fff2040bb70) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/server/akonadi.cpp:234 #11 0x7f9256087694 in QObject::event (this=0x7fff2040bb70, e=0x7f91f4005a20) at kernel/qobject.cpp:1314 #12 0x7f925605d63b in doNotify (event=0x7f91f4005a20, receiver=0x7fff2040bb70) at kernel/qcoreapplication.cpp:1154 #13 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #14 QCoreApplication::notifyInternal2 (receiver=0x7fff2040bb70, event=0x7f91f4005a20) at kernel/qcoreapplication.cpp:1064 #15 0x7f92560609b4 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x559b07bee000) at kernel/qcoreapplication.cpp:1821 #16 0x7f92560ae807 in postEventSourceDispatch (s=0x559b07c0dee0) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f925437cfaf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f92543d22c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #19 0x7f925437a940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f92560ae2fa in QEventDispatcherGlib::processEvents (this=0x559b07c0b350, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f925605c0ba in QEventLoop::exec (this=this@entry=0x7fff2040b9e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f9256064162 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x559b05ea9fa8 in AkApplicationBase::exec (this=0x7fff2040bb40) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/shared/akapplication.cpp:107 #24 main (argc=, argv=) at /usr/src/debug/kf5-akonadi-server-22.04.1-1.fc36.x86_64/src/server/main.cpp:65 [Inferior 1 (process 5873) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 456232] New: Spectacle crashes when I switch to "capture window underneath cursor" (does not usually crash)
https://bugs.kde.org/show_bug.cgi?id=456232 Bug ID: 456232 Summary: Spectacle crashes when I switch to "capture window underneath cursor" (does not usually crash) Product: Spectacle Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: bugh...@gluino.name CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.18.7-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Switched to "capture window underneath cursor" About to perform capture The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x55f89955dee3 in PlatformXcb::getWindowUnderCursor (this=0x55f89b29d5b0) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:238 #5 0x55f899560298 in PlatformXcb::grabTransientWithParent (theIncludeDecorations=true, theIncludePointer=false, this=0x55f89b29d5b0) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:585 #6 PlatformXcb::doGrabNow (this=0x55f89b29d5b0, theGrabMode=, theIncludePointer=, theIncludeDecorations=true) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:698 #7 0x7f54a6c18066 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1e2e6f70, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 QSingleShotTimer::timerEvent (this=0x55f89b91fef0) at kernel/qtimer.cpp:320 #9 0x7f54a6c0b525 in QObject::event (this=0x55f89b91fef0, e=0x7ffe1e2e70c0) at kernel/qobject.cpp:1336 #10 0x7f54a76afc82 in QApplicationPrivate::notify_helper (this=, receiver=0x55f89b91fef0, e=0x7ffe1e2e70c0) at kernel/qapplication.cpp:3637 #11 0x7f54a6be1658 in QCoreApplication::notifyInternal2 (receiver=0x55f89b91fef0, event=0x7ffe1e2e70c0) at kernel/qcoreapplication.cpp:1064 #12 0x7f54a6c31681 in QTimerInfoList::activateTimers (this=0x55f89b2927b0) at kernel/qtimerinfo_unix.cpp:643 #13 0x7f54a6c31f5c in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #14 0x7f54a479efaf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #15 0x7f54a47f42c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #16 0x7f54a479c940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #17 0x7f54a6c322fa in QEventDispatcherGlib::processEvents (this=0x55f89b288140, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #18 0x7f54a6be00ba in QEventLoop::exec (this=this@entry=0x7ffe1e2e7360, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x7f54a6be8162 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x7f54a7025ee0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1860 #21 0x7f54a76afbf9 in QApplication::exec () at kernel/qapplication.cpp:2829 #22 0x55f89952ce86 in main (argc=, argv=) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Main.cpp:112 [Inferior 1 (process 46086) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 456120] Just an idea: If the right border of window leaves the screen, shift the top-right window buttons into the still visible area
https://bugs.kde.org/show_bug.cgi?id=456120 --- Comment #2 from David Tonhofer --- Created attachment 150254 --> https://bugs.kde.org/attachment.cgi?id=150254&action=edit If the active elements were kept visible, that would be rad -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 456120] Just an idea: If the right border of window leaves the screen, shift the top-right window buttons into the still visible area
https://bugs.kde.org/show_bug.cgi?id=456120 --- Comment #1 from David Tonhofer --- Created attachment 150253 --> https://bugs.kde.org/attachment.cgi?id=150253&action=edit Window shifted right -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 456120] New: Just an idea: If the right border of window leaves the screen, shift the top-right window buttons into the still visible area
https://bugs.kde.org/show_bug.cgi?id=456120 Bug ID: 456120 Summary: Just an idea: If the right border of window leaves the screen, shift the top-right window buttons into the still visible area Product: Breeze Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugh...@gluino.name CC: uhh...@gmail.com Target Milestone: --- Created attachment 150252 --> https://bugs.kde.org/attachment.cgi?id=150252&action=edit The window about to be shifted right I often shift windows out of the "visible viewport" towards the "right" so that the top window decorations become inaccessible. Could the window manager shift them into the visible area if that happens. It would be of some practical advantage. See attached images. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455949] New: Dolphin crash when (as I remember) I click on the "write into" button the the dialog that pops up when moving subdirectories named identically "onto" each other
https://bugs.kde.org/show_bug.cgi?id=455949 Bug ID: 455949 Summary: Dolphin crash when (as I remember) I click on the "write into" button the the dialog that pops up when moving subdirectories named identically "onto" each other Product: dolphin Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.18.6-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: I was moving a set of directory Ax into directoy B. Ax contains directores named the same as directories already in B (let's say X) In that case a popup window is shown that asks whether the move should just add directores fom Ax/X into B/X. (If I remmeber correctly) I clicked on Yes. Then Dolphin crashes. I hope the move was "transactional" in that no files have been lost (but I have seen Dolphin overwrite files due to a problem with the renaming feature in the interface, so who knows :-( The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7ff099c25c3c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7ff099bd59c6 in raise () from /lib64/libc.so.6 #6 0x7ff099bbf7f4 in abort () from /lib64/libc.so.6 #7 0x7ff099bbf71b in __assert_fail_base.cold () from /lib64/libc.so.6 #8 0x7ff099bce576 in __assert_fail () from /lib64/libc.so.6 #9 0x7ff097752bbc in wl_proxy_unref (proxy=) at ../src/wayland-client.c:230 #10 0x7ff097754b62 in proxy_destroy (proxy=0x7ff097758258 <__PRETTY_FUNCTION__.3>) at ../src/wayland-client.c:514 #11 0x7ff097754c6e in wl_proxy_destroy_caller_locks (proxy=0x55d83f2b3980) at ../src/wayland-client.c:523 #12 wl_proxy_destroy (proxy=0x55d83f2b3980) at ../src/wayland-client.c:546 #13 0x7ff0977e18a9 in wl_callback_destroy (wl_callback=) at ../../include/QtWaylandClient/5.15.3/QtWaylandClient/private/../../../../../src/client/wayland-wayland-client-protocol.h:1220 #14 QtWaylandClient::QWaylandWindow::reset (this=0x55d83f0e8ff0) at /usr/src/debug/qt5-qtwayland-5.15.3-2.fc36.x86_64/src/client/qwaylandwindow.cpp:255 #15 0x7ff09a79b337 in QWindowPrivate::setVisible (this=0x55d83e6ce0c0, visible=visible@entry=false) at kernel/qwindow.cpp:408 #16 0x7ff09ae675f1 in QWidgetWindow::setNativeWindowVisibility (this=, visible=visible@entry=false) at kernel/qwidgetwindow.cpp:215 #17 0x7ff09ae438fd in QWidgetPrivate::hide_sys (this=this@entry=0x55d83f0e8ba0) at kernel/qwidget.cpp:8022 #18 0x7ff09ae4a800 in QWidgetPrivate::hide_helper (this=this@entry=0x55d83f0e8ba0) at kernel/qwidget.cpp:7950 #19 0x7ff09ae4f4e8 in QWidgetPrivate::setVisible (this=0x55d83f0e8ba0, visible=) at kernel/qwidget.cpp:8146 #20 0x7ff09ae4f5c6 in QWidget::setVisible (this=this@entry=0x55d83ee3f9c0, visible=visible@entry=false) at kernel/qwidget.cpp:8057 #21 0x7ff09b01cb06 in QDialog::setVisible (this=0x55d83ee3f9c0, visible=) at dialogs/qdialog.cpp:849 #22 0x7ff09b01b131 in QDialogPrivate::hide (this=this@entry=0x55d83f0e8ba0, resultCode=resultCode@entry=4) at dialogs/qdialog.cpp:158 #23 0x7ff09b01b168 in QDialog::done (this=, r=4) at dialogs/qdialog.cpp:637 #24 0x7ff09a2a8c36 in QtPrivate::QSlotObjectBase::call (a=0x70decaf0, r=, this=0x55d83e9f7660) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #25 doActivate (sender=0x55d83f07c010, signal_index=9, argv=0x70decaf0) at kernel/qobject.cpp:3886 #26 0x7ff09a2a3c67 in QMetaObject::activate (sender=sender@entry=0x55d83f07c010, m=m@entry=0x7ff09b3356a0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x70decaf0) at kernel/qobject.cpp:3946 #27 0x7ff09af00ae6 in QAbstractButton::clicked (this=this@entry=0x55d83f07c010, _t1=) at .moc/moc_qabstractbutton.cpp:308 #28 0x7ff09af00d5e in QAbstractButtonPrivate::emitClicked (this=0x55d83f17a190) at widgets/qabstractbutton.cpp:415 #29 0x7ff09af0299c in QAbstractButtonPrivate::click (this=0x55d83f17a190) at widgets/qabstractbutton.cpp:408 #30 0x7ff09af02bbb in QAbstractButton::mouseReleaseEvent (this=0x55d83f07c010, e=0x70ded080) at widgets/qabstractbutton.cpp:1044 #31 0x7ff09afff6ce in QToolButton::mouseReleaseEvent (this=, e=) at widgets/qtoolbutton.cpp:622 #32 0x7ff09ae4f798 in QWidget::event (this=0x55d83f07c010, event=0x70ded080) at kernel/qwidget.cpp:9033 #33 0x7ff09ae0cc82 in QApplicationPrivate::notify_helper
[konsole] [Bug 438239] New: Apparently Konsole crashed just as I was closing it
https://bugs.kde.org/show_bug.cgi?id=438239 Bug ID: 438239 Summary: Apparently Konsole crashed just as I was closing it Product: konsole Version: 21.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: konsole (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: I had just typed CTRL-D to close the konsole. Then the crash handler protested (I wouldn't have noticed anything amiss if the crash handler hadn't said anything). This is a knsole with a "new profile" (set as default but KDE doesn't care about the default; well, that's another bug) with: - Black on light background - Another font than the hard-to-read "noto" The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7f8887fa6a78 in Konsole::PlainTextDecoder::decodeLine(Konsole::Character const*, int, unsigned char) () from /lib64/libkonsoleprivate.so.21 #5 0x7f8887f620ad in Konsole::TerminalDisplay::inputMethodQuery(Qt::InputMethodQuery) const () from /lib64/libkonsoleprivate.so.21 #6 0x7f8887419d3c in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #7 0x7f88873d8e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f461f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f8882fd958a in QtWaylandClient::QWaylandTextInput::updateState(QFlags, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #10 0x7f8886d7958d in QGuiApplicationPrivate::_q_updateFocusObject(QObject*) () from /lib64/libQt5Gui.so.5 #11 0x7f4924fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f8886d87e66 in QWindow::focusObjectChanged(QObject*) () from /lib64/libQt5Gui.so.5 #13 0x7f8887413d7b in QWidget::clearFocus() () from /lib64/libQt5Widgets.so.5 #14 0x7f8887414e48 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #15 0x7f8887ef95c5 in Konsole::TerminalColor::~TerminalColor() () from /lib64/libkonsoleprivate.so.21 #16 0x7f8887f54353 in Konsole::TerminalDisplay::~TerminalDisplay() () from /lib64/libkonsoleprivate.so.21 #17 0x7f8887f5454d in Konsole::TerminalDisplay::~TerminalDisplay() () from /lib64/libkonsoleprivate.so.21 #18 0x7f4890c1 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f88873d8e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f461f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f464c76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7f4aec57 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7f88861374cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f888618b4e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7f8886134c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f4ae6f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f4609b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f468544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x7f7feabd in kdemain () from /lib64/libkdeinit5_konsole.so #30 0x7f03bb75 in __libc_start_main () from /lib64/libc.so.6 #31 0x56145ae3214e in _start () [Inferior 1 (process 41892) detached] Possible duplicates by query: bug 436863, bug 429973, bug 413345, bug 403101, bug 381101. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384974] Dolphin crashes after failing to copy files to Android phone over mtp
https://bugs.kde.org/show_bug.cgi?id=384974 --- Comment #15 from David Tonhofer --- I don't know why there should be two implementation paths (different libraries?), but as a replacement solution, downloading pics from an attached phone via gwenview works A-OK. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363771] deactivate "Aufklappmenue"
https://bugs.kde.org/show_bug.cgi?id=363771 --- Comment #8 from David Tonhofer --- Created attachment 116622 --> https://bugs.kde.org/attachment.cgi?id=116622&action=edit New crash information added by DrKonqi plasmashell (5.13.5) using Qt 5.11.1 - What I was doing when the application crashed: I have disabled Dolphin's "inline rename" feature (because that is a surefire way to make Dolphin disappear files; maybe it has been fixed?). So, renaming a file involved entering the new name into a popup dialog. Once that is done a popup menu shows up with various actions (I don't know where that comes from, Dolphin never did that before). This being annoying, I select "disable this pop-up" in the dialog. A crash then occurs. -- Backtrace (Reduced): #6 0x7fd92caf8d18 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /lib64/libQt5Core.so.5 #7 0x7fd92dc8a72b in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7fd92dc8cf0e in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #9 0x7fd92dc30475 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7fd92dc37b90 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363771] deactivate "Aufklappmenue"
https://bugs.kde.org/show_bug.cgi?id=363771 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 334533] if a file position in a list changes while it is renamed a wrong file is renamed instead
https://bugs.kde.org/show_bug.cgi?id=334533 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #8 from David Tonhofer --- In the original report: "I frequently run into this bug when renaming in a folder with several, continuously updated files and using the sorting by date. While those are bad results this bug is likely not triggered that often for average users." Actually, if this is the same bug, I often trigger it by just sorting files from the main window into the sidebar where target directories are listed (I tried to find a way to reproduce this in #389892). For some reason, rename often becomes active when I do that. I probably nuked a few files doing so. Now I have to be super attentive, this is like a self-driving car. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 378786] inline rename: scrolling causes rename of wrong file
https://bugs.kde.org/show_bug.cgi?id=378786 --- Comment #9 from David Tonhofer --- I have Dolphin 17.12.2 and it happened again. Is it supposed to be fixed in that version? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393897] New: Dolphin crashes when it (unsuccessfully) tries to copy a file to an Android phone attached to the USB & the USB is unplugged
https://bugs.kde.org/show_bug.cgi?id=393897 Bug ID: 393897 Summary: Dolphin crashes when it (unsuccessfully) tries to copy a file to an Android phone attached to the USB & the USB is unplugged Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.2) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.16.5-200.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: Trying to copy a file to Android device This works sometimes and sometimes you cannot access the device, copying takes forever etc. Then you have to be patient, unplug the device, try again, etc. It seems to work better with camera:// URL than the mtp:// URL. In short, not ready for prime time. So we are having this case again where the file transfer is in a funk. 20 KiB takes forever. Time to unplug the USB device. Dolphin crash. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f962f107940 (LWP 28056))] Thread 5 (Thread 0x7f95f44ce700 (LWP 28060)): #0 0x7f9626a4bc6b in poll () from /lib64/libc.so.6 #1 0x7f961e357e99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f961e357fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f96278a1c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f962784f96a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f96276a08ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f96276a4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f9622ce450b in start_thread () from /lib64/libpthread.so.0 #8 0x7f9626a5616f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f9604d30700 (LWP 28059)): #0 0x7f9622cea82d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9606991f4b in util_queue_thread_func () from /usr/lib64/dri/nouveau_dri.so #2 0x7f9606991e67 in impl_thrd_routine () from /usr/lib64/dri/nouveau_dri.so #3 0x7f9622ce450b in start_thread () from /lib64/libpthread.so.0 #4 0x7f9626a5616f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f960dc60700 (LWP 28058)): #0 0x7f9626a47738 in read () from /lib64/libc.so.6 #1 0x7f961e39c0a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f961e3579a8 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f961e357e40 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f961e357fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f96278a1c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f962784f96a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f96276a08ca in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f962986d449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #9 0x7f96276a4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f9622ce450b in start_thread () from /lib64/libpthread.so.0 #11 0x7f9626a5616f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f960ff98700 (LWP 28057)): #0 0x7f9626a4bc6b in poll () from /lib64/libc.so.6 #1 0x7f961d8c7fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f961d8c9dda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f96120fabf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f96276a4de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f9622ce450b in start_thread () from /lib64/libpthread.so.0 #6 0x7f9626a5616f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f962f107940 (LWP 28056)): [KCrash Handler] #6 0x7f962ad5dd74 in KIO::Slave::deref() () from /lib64/libKF5KIOCore.so.5 #7 0x7f962ad5e1dd in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #8 0x7f9627879513 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f962ad02439 in KIO::ConnectionPrivate::dequeue() [clone .part.12] () from /lib64/libKF5KIOCore.so.5 #10 0x7f962787a26a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #11 0x7f9628b7992c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7f9628b81174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x00
[dolphin] [Bug 392706] New: Image preview predictably fails for half-uploaded images but then doesn't address the problem later
https://bugs.kde.org/show_bug.cgi?id=392706 Bug ID: 392706 Summary: Image preview predictably fails for half-uploaded images but then doesn't address the problem later Product: dolphin Version: 17.12.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Created attachment 111812 --> https://bugs.kde.org/attachment.cgi?id=111812&action=edit Example of failed previews If you upload an jpg image and Dolphin grabs it to generate a preview, it may stay "half gray" as the preview fails mid-way. This is not so bad, but Dolphin should be back later for a re-take on the preview - this does not happen (how do into explicitly telling Dolphin to redo the previews?) Fixing this would mean keeping a database about temporarily failed previews somewhere (a portable SQL database or something) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 349287] window title stops updating after closing left side of split view
https://bugs.kde.org/show_bug.cgi?id=349287 David Tonhofer changed: What|Removed |Added Platform|Archlinux Packages |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 349287] window title stops updating after closing left side of split view
https://bugs.kde.org/show_bug.cgi?id=349287 --- Comment #3 from David Tonhofer --- The fun thing is that it restarts updating if you SPLIT and the close the RIGHT side. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 349287] window title stops updating after closing left side of split view
https://bugs.kde.org/show_bug.cgi?id=349287 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name Version|16.12.2 |17.12.2 --- Comment #2 from David Tonhofer --- Still the case in Dolphin 17.12.2 on Fedora 27. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389455] Baloo crashed every time immediately after the start
https://bugs.kde.org/show_bug.cgi?id=389455 --- Comment #3 from David Tonhofer --- Created attachment 111752 --> https://bugs.kde.org/attachment.cgi?id=111752&action=edit New crash information added by DrKonqi baloo_file_extractor (5.44.0) using Qt 5.9.4 KDE had just started. This was directly after reboot. Then segmentation fault in __memmove_sse2_unaligned_erms () called from Baloo::PostingCodec::decode() -- Backtrace (Reduced): #7 0x7efd2338dc93 in Baloo::PostingCodec::decode(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #8 0x7efd2337f704 in Baloo::PostingDB::get(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #9 0x7efd2338b380 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #10 0x7efd23384c62 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #11 0x556107978acc in Baloo::App::processNextFile() () -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389455] Baloo crashed every time immediately after the start
https://bugs.kde.org/show_bug.cgi?id=389455 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 392442] New: Kscreenlocker keyboard layout selection issue.
https://bugs.kde.org/show_bug.cgi?id=392442 Bug ID: 392442 Summary: Kscreenlocker keyboard layout selection issue. Product: kscreenlocker Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugh...@gluino.name CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- This is for kscreenlocker-5.12.2-1.fc27.x86_64 (The Bugzilla "Version" box only shows 5.8.7, 5.10.2, 5.10.3, unspecified. This should probably be fixed) I have configured the keyboard layouts: ch - German (Switzerland), Varian French (Switzerland) be - Belgian gb - English (UK) After startup, kscreenlocker is in the US layout as indicated by the layout indicator btm left. I don't know where the layout comes from... The selector also indicates "ch" as possibility but for some reason I cannot select it immediately (i.e. trying to select it results in no change), I need to faff around, select "Belgium" first, then I can select it. From there on, things work as expected. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392419] New: Line-filling trailing spaces are picked up by "copy" operation after konsole window resize.
https://bugs.kde.org/show_bug.cgi?id=392419 Bug ID: 392419 Summary: Line-filling trailing spaces are picked up by "copy" operation after konsole window resize. Product: konsole Version: 17.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Even with "trim trailing spaces" enabled: 1) Have a small window 2) With some output, e.g. the output of tree --help 3) Resize window, making it larger 4) tree --help again 5) Copy-paste the contents back into the history 6) The lowermost lines have no trailing space, but from some point onwards, trailing spaces have been inject to fill space and are also picked up by the copy operation. This is not necessarily the line that is not visible after command execution, it may be a few lines earlier (may depend on some buffer size) X) This is easily seen when pasting into LibreOffice Word with "Toggle formatting marks" on (the Paragraph sign clicked) and View>FieldShadings on -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392258] New: Baloo segfaults in "Baloo::PostingCodec::decode(QByteArray const&)" (on kf5-baloo-5.44.0-1.fc27)
https://bugs.kde.org/show_bug.cgi?id=392258 Bug ID: 392258 Summary: Baloo segfaults in "Baloo::PostingCodec::decode(QByteArray const&)" (on kf5-baloo-5.44.0-1.fc27) Product: frameworks-baloo Version: 5.44.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: baloo_file_extractor (5.44.0) Qt Version: 5.9.4 Frameworks Version: 5.44.0 Operating System: Linux 4.15.8-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: - What I was doing when the application crashed: I had just copy-pasted from the web into LibreOffice Writer, and had saved. There was no particular desktop activity going on at that time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32f43b3500 (LWP 18131))] Thread 3 (Thread 0x7f32d5f56700 (LWP 18135)): #0 0x7f32ebc543f4 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x7f32ebc0e3ec in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f32ebc0edcb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f32ebc0efac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f32f1794c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f32f174296a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f32f15938ca in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f32f2f63449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7f32f1597de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f32ef84250b in start_thread () from /lib64/libpthread.so.0 #10 0x7f32f094916f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f32df6e0700 (LWP 18133)): #0 0x7f32f093ec6b in poll () from /lib64/libc.so.6 #1 0x7f32eb597fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f32eb599dda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f32e227ebf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f32f1597de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f32ef84250b in start_thread () from /lib64/libpthread.so.0 #6 0x7f32f094916f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f32f43b3500 (LWP 18131)): [KCrash Handler] #6 0x7f32f08f38db in __memmove_sse2_unaligned_erms () from /lib64/libc.so.6 #7 0x7f32f3615c93 in Baloo::PostingCodec::decode(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #8 0x7f32f3607704 in Baloo::PostingDB::get(QByteArray const&) () from /lib64/libKF5BalooEngine.so.5 #9 0x7f32f3613380 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #10 0x7f32f360cc62 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #11 0x55de841a1acc in Baloo::App::processNextFile() () #12 0x7f32f1778934 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f32f176d21b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f32f23b092c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f32f23b8174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f32f1743be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f32f1793f5b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7f32f1794829 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f32ebc0eb77 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f32ebc0ef20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7f32ebc0efac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f32f1794c2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f32f174296a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f32f174b094 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55de841a0a2f in main () The reporter indicates this bug may be a duplicate of or related to bug 388621. Possible duplicates by query: bug 390610, bug 390363, bug 389455, bug 388621, bug 388296. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #23 from David Tonhofer --- Atlassian says: https://jira.atlassian.com/browse/CONFCLOUD-59271 "Thanks for bringing this issue to our attention. We've reviewed it with the team and decided we won't fix at this time. This is an issue that's unique to Zip7 software which uses the MS-DOS time format. We'd recommend using another zip software tool like WinZip, WinRAR, or PeaZip, none of which should have issues." okay.jpg -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #22 from David Tonhofer --- Support request opened at Atlassian https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-373392 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #21 from David Tonhofer --- Igor Pavlov says: "There are incorrect Date/Time values in headers. ZIP uses MS-DOS time format. Maybe your software (that was used to create these archives) writes Unix timestamps or some garbage data instead of MS-DOS timestamps. You can report about that problem to "Atlassian Confluence Cloud" developers. Maybe it was already fixed. So check for new version of their software." -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #19 from David Tonhofer --- Created attachment 111216 --> https://bugs.kde.org/attachment.cgi?id=111216&action=edit Small Confluence export (ok with p7zip) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #20 from David Tonhofer --- Created attachment 111217 --> https://bugs.kde.org/attachment.cgi?id=111217&action=edit Small Confluence export (has subpage) (NOT ok with p7zip) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391404] New: RFE: Dolphin shows an icon corresponding to the file suffix. It show one corresponding to the actual file type.
https://bugs.kde.org/show_bug.cgi?id=391404 Bug ID: 391404 Summary: RFE: Dolphin shows an icon corresponding to the file suffix. It show one corresponding to the actual file type. Product: dolphin Version: 17.12.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- As I have currently a bit of trouble with Dolphin renaming my files willy-nilly, I though that: Currently Dolpin displays an icon depending on the file suffix, e.g. one "image" icon for ".png", and another for ".pdf" - irrespective of the true file type (which is ontained by a call to the functionality of 'file' I suppose), which can be checked in the "properties" dialog. Showing a file icon depending on the actual file type instead of the file suffix would be the Right Thing to do. It would alert the user to a type problem if a ".png" is displayed as a pdf for example. If there is no suffix in the first place, the icon displayed depends on the file type in any case. So one would also be consistent here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] A file can go into a weird superposition state "being moved while being renamed", which causes an unrelated file to be renamed to the file just moved
https://bugs.kde.org/show_bug.cgi?id=389892 David Tonhofer changed: What|Removed |Added Summary|Moving a file causes an |A file can go into a weird |unrelated file in the |superposition state "being |source directory to take on |moved while being renamed", |the name of the moved file |which causes an unrelated ||file to be renamed to the ||file just moved -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] Moving a file causes an unrelated file in the source directory to take on the name of the moved file
https://bugs.kde.org/show_bug.cgi?id=389892 --- Comment #4 from David Tonhofer --- Even more precise: The problem comes from the fact that somehow renaming is triggered on the file. Suppose the file in details view mode is unmarked (it may be semi-marked, there is a thin blue line underneath, not 100% sure what this is about, my reflexes don't tell me). Click on it, it acquires a blue background. Release mouse, move off the file. Now: a) Move mouse back to file, click and don't release button, hold it. b) The file will go into "rename mode" after 500ms or so, after which it cannot be moved. However in some cases: a) Move mouse back to file, click and don't release button, move it to the left-side "Places bar" for example. b) Sometimes the file while go into "rename mode" while you move it. If you now drop it into a "place", the file underneath the just moved file in the "details view" will be given the name of the file just moved. I don't know what exactly triggers the quantum state of "being moved" + "being renamed" at the same time, but the state machine seems to have a bug in any case. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #18 from David Tonhofer --- Report opened at p7zip: https://sourceforge.net/p/p7zip/bugs/206/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391338] New: Dolphin crashes if a filesystem tree's permissions are (massively) updated outside of Dolphin
https://bugs.kde.org/show_bug.cgi?id=391338 Bug ID: 391338 Summary: Dolphin crashes if a filesystem tree's permissions are (massively) updated outside of Dolphin Product: dolphin Version: 17.12.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (17.12.1) Qt Version: 5.9.4 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: Dolphin was (probably) open on a filesystem tree that I was updating by script, changing the ownership, permissions and SELinux attributes. While a whole lot of permissions geot updated, Dolphin crashed (this happened twice). Is it overwhelmed by too many messages? The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc0cca1b940 (LWP 13462))] Thread 5 (Thread 0x7fc091f48700 (LWP 13466)): #0 0x7fc0c51bb45f in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #1 0x7fc0c51bc92c in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7fc0c51bc9ce in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #3 0x7fc0bbc3b3f9 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #4 0x7fc0bbc3bdcb in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #5 0x7fc0bbc3bfac in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #6 0x7fc0c51bcc4b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fc0c516a96a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #8 0x7fc0c4fbb8ca in QThread::exec() () at /lib64/libQt5Core.so.5 #9 0x7fc0c4fbfde2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fc0c05c861b in start_thread () at /lib64/libpthread.so.0 #11 0x7fc0c435c98f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc09b144700 (LWP 13465)): #0 0x7fc0c05cecbb in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc09f3e2f4b in util_queue_thread_func () at /usr/lib64/dri/nouveau_dri.so #2 0x7fc09f3e2e67 in impl_thrd_routine () at /usr/lib64/dri/nouveau_dri.so #3 0x7fc0c05c861b in start_thread () at /lib64/libpthread.so.0 #4 0x7fc0c435c98f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc0a7454700 (LWP 13464)): #0 0x7fc0bbc813d9 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7fc0bbc3ad8e in g_main_context_acquire () at /lib64/libglib-2.0.so.0 #2 0x7fc0bbc3bd55 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7fc0bbc3bfac in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7fc0c51bcc4b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fc0c516a96a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fc0c4fbb8ca in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7fc0c7188449 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #8 0x7fc0c4fbfde2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7fc0c05c861b in start_thread () at /lib64/libpthread.so.0 #10 0x7fc0c435c98f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc0ad874700 (LWP 13463)): #0 0x7fc0c43503db in poll () at /lib64/libc.so.6 #1 0x7fc0bb1aafe7 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fc0bb1acdda in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fc0af9d6bf9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fc0c4fbfde2 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fc0c05c861b in start_thread () at /lib64/libpthread.so.0 #6 0x7fc0c435c98f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc0cca1b940 (LWP 13462)): [KCrash Handler] #6 0x7fc0c6f0c964 in KDirWatchPrivate::inotifyEventReceived() () at /lib64/libKF5CoreAddons.so.5 #7 0x7fc0c5194513 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #8 0x7fc0c51a02b8 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /lib64/libQt5Core.so.5 #9 0x7fc0c51a0682 in QSocketNotifier::event(QEvent*) () at /lib64/libQt5Core.so.5 #10 0x7fc0c649492c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7fc0c649c174 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7fc0c516bbe7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #16 from David Tonhofer --- I agree -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] Moving a file causes an unrelated file in the source directory to take on the name of the moved file
https://bugs.kde.org/show_bug.cgi?id=389892 David Tonhofer changed: What|Removed |Added Severity|normal |major --- Comment #3 from David Tonhofer --- Better reproducible: 1) Have a directory of many files. 2) Create a target directory that is linked to via the Dolphin "left pane" (the left pane where you find like the Wastebasket, Search For, Devices etc). 3) The Mouse Click behaviour is set to "Double click to open files and folders" (Sysetm Settings > Input Devices > Mouse) (because I still haven't found out how one can actually DO anything at all if a file opens on first click) 4) Do this: Click on a file in the Dolphin main pane, release Mouse. The file is selected. Move the file into the target directory in the "left pane" With high probability (1/5?), a file or even a directory in the "from" directory takes on the filename of the file just moved. Moving this to "major" as this will result in file loss. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #14 from David Tonhofer --- 7zip 18.01 on Windows also says there are "header errors" but doesn't say what exactly the problem is. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #13 from David Tonhofer --- Hmmm $ rpm --query --file $(which 7z) p7zip-plugins-16.02-9.fc27.x86_64 $ rpm --query --file $(which 7za) p7zip-16.02-9.fc27.x86_64 Actually, if the version number of p7zip (the latest p7zip at sourceforge is indeed 16.02) corresponds to the version number of 7z, it's a bit out of date. The 7z latest is 18.01/2018-01-28, 16.02 was 2016-05-21. "Bugs have been fixed" in the meantime: http://www.7-zip.org/history.txt Maybe it's one of those bugs. (Incidentally, 15.05 was the one with the exploitable vulnerabilities: http://blog.talosintelligence.com/2016/05/multiple-7-zip-vulnerabilities.html - Completely unfunnily, the 7z history log says nothing about these; this does not inspire confidence in 7z. At all. Langsec: Serious business!) I will test this on a Windows machine nearby. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 David Tonhofer changed: What|Removed |Added Attachment #110518|Atlassian Confluence Export |Atlassian Confluence Export description|Zip file, not ok to 7zip|Zip file, not ok to 7z -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 David Tonhofer changed: What|Removed |Added Attachment #110517|application/octet-stream|application/zip mime type|| Attachment #110517|A zip file that works with |Atlassian Confluence Export description|7z |Zip file, ok to 7z -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #12 from David Tonhofer --- Created attachment 110520 --> https://bugs.kde.org/attachment.cgi?id=110520&action=edit Output of zipinfo -v for the file that does not works with 7z -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #11 from David Tonhofer --- Created attachment 110519 --> https://bugs.kde.org/attachment.cgi?id=110519&action=edit Output of zipinfo -v for the file that works with 7z -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #10 from David Tonhofer --- Created attachment 110518 --> https://bugs.kde.org/attachment.cgi?id=110518&action=edit Atlassian Confluence Export Zip file, not ok to 7zip Create an "export" of a fresh Atlassian Confluence Space with some test content The resulting zip file is NOT ok to 7z. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #9 from David Tonhofer --- Created attachment 110517 --> https://bugs.kde.org/attachment.cgi?id=110517&action=edit A zip file that works with 7z Create an "export" of a totally fresh & empty Atlassian Confluence Space. The resulting zip file is ok to 7z. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389554] RFE: Allow configuration of a default "wallpaper directory"
https://bugs.kde.org/show_bug.cgi?id=389554 --- Comment #5 from David Tonhofer --- Sounds cool. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #8 from David Tonhofer --- It was created by Atlassian Confluence (the "cloud" solution), which is probably done via a Java library. I can create a empty archive to see what happens, but in the end this seems to be the 7z library being fickle. I can open a bug at Fedora about this. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423
--- Comment #5 from David Tonhofer ---
Output of "7z t"
Sadly, informative messages are often treated as if they were made of precious
gems. They are exceedingly sparse. So here:
--
7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_GB.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs
Intel(R) Xeon(R) CPU W3520 @ 2.67GHz (106A5),ASM)
Scanning the drive for archives:
1 file, 952325789 bytes (909 MiB)
Testing archive: Confluence_Aikido_2018_01_01.zip
WARNINGS:
Headers Error
--
Path = Confluence_Aikido_2018_01_01.zip
Type = zip
WARNINGS:
Headers Error
Physical Size = 952325789
Everything is Ok
Archives with Warnings: 1
Warnings: 1
Files: 2569
Size: 1114914438
Compressed: 952325789
--
WTF!
Runinng ark using
QT_LOGGING_RULES=ark.*.debug=true ark
we get
---
ark.main: Entering application loop
ark.part: Attempting to open archive
"/home/calvin/Confluence_Aikido_2018_01_01.zip"
ark.kerfuffle: Going to create archive
"/home/calvin/Confluence_Aikido_2018_01_01.zip"
ark.kerfuffle: Checking plugin "kerfuffle_cli7z"
ark.kerfuffle: Created read-only interface for
"/home/calvin/Confluence_Aikido_2018_01_01.zip"
ark.kerfuffle: Created read-write interface for
"/home/calvin/Confluence_Aikido_2018_01_01.zip"
ark.cli7z: Loaded cli_7z plugin
ark.cli7z: Setting up parameters...
ark.kerfuffle: Successfully loaded plugin "kerfuffle_cli7z"
ark.kerfuffle: Created archive instance
ark.kerfuffle: LoadJob created
ark.kerfuffle: Executing "/usr/bin/7z" ("l", "-slt",
"/home/calvin/Confluence_Aikido_2018_01_01.zip") within directory
"/home/calvin"
ark.cli7z: p7zip version "16.02" detected
ark.cli7z: Archive name: "/home/calvin/Confluence_Aikido_2018_01_01.zip"
ark.cli7z: Archive type: "zip"
ark.kerfuffle: Archive corrupt
ark.part: Showing columns: (0, 1, 2, 7, 8)
ark.kerfuffle: Process finished, exitcode: 0 exitstatus:
QProcess::ExitStatus(NormalExit)
ark.kerfuffle: Executing LoadCorrupt prompt
ark.kerfuffle: Job finished, result: true , time: 5548 ms
---
Attaching the output of "zipinfo -v" too
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 388423] [p7zip] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #6 from David Tonhofer --- Created attachment 110501 --> https://bugs.kde.org/attachment.cgi?id=110501&action=edit Beginning of "zipinfo -v" output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389554] RFE: Allow configuration of a default "wallpaper directory"
https://bugs.kde.org/show_bug.cgi?id=389554 --- Comment #2 from David Tonhofer --- Well, the Pictures folder is actually just a work folder (it contains screenshots among other), not a repository of Wallpapers, which are somewhere in an Archive folder. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] Moving a file causes an unrelated file in the source directory to take on the name of the moved file
https://bugs.kde.org/show_bug.cgi?id=389892 --- Comment #2 from David Tonhofer --- It happened again. I am using Dolphin in "split window" mode when moving files from one directory to the other (from right to left, say) I have the feeling that it has something to do with a file having the "renaming action" active on the right side. You then move that file to the left side, which works but the renaming action on the right side is "sticky" and gloms onto the file that was displayed underneath the one just moved, giving it the name of the file just moved. Something like that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] Moving a file causes an unrelated file in the source directory to take on the name of the moved file
https://bugs.kde.org/show_bug.cgi?id=389892 --- Comment #1 from David Tonhofer --- Special configuration of my mouse: Activating windows Policy = "Focus Follows Mouse" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389893] New: Sorting by "created" basically not doing what it is supposed to do
https://bugs.kde.org/show_bug.cgi?id=389893 Bug ID: 389893 Summary: Sorting by "created" basically not doing what it is supposed to do Product: dolphin Version: 17.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- Move a file into a directory shown in Dolphin in the "Details View Mode" Add the "Created" column. Sort by it ascending. The latest entry added to the directory with these stat(5) info: Access: 2018-02-04 22:28:25.487676109 +0100 Modify: 2018-02-04 22:28:25.624673578 +0100 Change: 2018-02-04 22:28:40.095406154 +0100 is at the very top, followed by stuff that has been in there for ages. In fact, the contents of the directory are NOT sorted by "Created" (whatever that is supposed to be) but by the name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389892] New: Moving a file causes an unrelated file in the source directory to take on the name of the moved file
https://bugs.kde.org/show_bug.cgi?id=389892 Bug ID: 389892 Summary: Moving a file causes an unrelated file in the source directory to take on the name of the moved file Product: dolphin Version: 17.12.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- I have an occasional bug whereby the following happens: A file (foo.pdf, say) in directory A is moved to directory B using Dolphin. This move succeeds but an unrelated file (stuff.txt, say) in directory A then takes on the name "foo.pdf". This happens occasionally and I haven't been able to reproduce this reliably. It's extremely annoying though. Is there a way to switch on some kind of "action trace" of Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389554] RFE: Allow configuration of a default "wallpaper directory"
https://bugs.kde.org/show_bug.cgi?id=389554 David Tonhofer changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389554] New: RFE: Allow configuration of a default "wallpaper directory"
https://bugs.kde.org/show_bug.cgi?id=389554 Bug ID: 389554 Summary: RFE: Allow configuration of a default "wallpaper directory" Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugh...@gluino.name CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 110180 --> https://bugs.kde.org/attachment.cgi?id=110180&action=edit I want a new Wallpaper: By default, go to ~/Pictures Currently when getting new Wallpapers, the Wallpapering dialogue goes to ~/Pictures (at least in a Fedora 27 KDE configuration). Better: Allow configuring the default wallpaper directory, possibly in the "System Configuration" supermenu. (Actually, allow setting an URI including a file:// URI and a time interval so that it is updated automatically at fixed intervals and ... nah, too complex for such a use case) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388214] Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...
https://bugs.kde.org/show_bug.cgi?id=388214 --- Comment #4 from David Tonhofer --- Ok, it happened again. It happens when you copy the contents of large directories (1000's of files) using Dolphin. At which point the world stops (even the clock gets stuck for 10 minutes...) And then you are plagued by 30 by thirty ghost notifications (maybe they are created whenever dolphin asks for overwrite confirmation?) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389437] New: Dolphin does not deal well with a file that is visible on two places via a hardlink and that is moved onto itself
https://bugs.kde.org/show_bug.cgi?id=389437 Bug ID: 389437 Summary: Dolphin does not deal well with a file that is visible on two places via a hardlink and that is moved onto itself Product: dolphin Version: 17.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- Suppose you have A/F1.txt and B/F1.txt Both files are backed by the same inode. If you move A/F1.txt into directory B, Dolphin pops up a dialog saying: "The action will overwrite the destination". Click on "Overwrite". The dialog disappears then reappears immediately, nothing is "moved". This goes on forever until you "Cancel". It is unclear what Dolphin SHOULD do in this case. Maybe unlink A/F1.txt. Or tell the user that A/F1.txt and B/F1.txt are actually the same file and it will skip moving the file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389436] New: RFE: Dolphin's "Overwrite Dialog" should indicate whether hashsum of source and target files match
https://bugs.kde.org/show_bug.cgi?id=389436 Bug ID: 389436 Summary: RFE: Dolphin's "Overwrite Dialog" should indicate whether hashsum of source and target files match Product: dolphin Version: 17.12.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 110122 --> https://bugs.kde.org/attachment.cgi?id=110122&action=edit Example of current Dialog generated by Dolphin When a file named "X" is moved into a folder that already contains a file named "X", dolphin pops up a dialog notifying the user that "this action will overwrite the destination". The dialog indicates the size of the source and target. Unfortunately, the size may not carry enough information for the user to make an informed decision. In particular, the size of the two files may be identical, and the files may still differ. The "Modify Date", although shown, may be confusing or wrong. Improvement: Help the user out by indicating that the MD5 sum of left and right files match (evidently, if the size doens't match, this does not need to be computed) MD5 hash is sufficient here because one is not working in a context in which a weak hash is of relevance. One just want a fast hashing algorithm. For large files computing the MD5 sum may be expensive. Thus, for files above a certain size (which should be configurable), the dialog could offer the option to compute the MD5 sum on demand (by clicking a button) instead of computing it outright. The "Apply to All" option would continue to not care about MD5 hashsums of the files. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #3 from David Tonhofer --- It works if I deselect the "P7zip" plugin. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 --- Comment #2 from David Tonhofer --- Created attachment 109893 --> https://bugs.kde.org/attachment.cgi?id=109893&action=edit Plugins selected -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 388423] New: ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem
https://bugs.kde.org/show_bug.cgi?id=388423 Bug ID: 388423 Summary: ark says zip "archive corrupt" but both "zip -F" and "unzip -t" find no problem Product: ark Version: 17.08.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plugins Assignee: rthoms...@gmail.com Reporter: bugh...@gluino.name CC: elvis.angelac...@kde.org Target Milestone: --- A large archive file (909M, a backup of an Atlassian Confluence installation) opened via "ark" (via the KDE interface or "ark --batch") says the archive is corrupt. On the command line: ark.kerfuffle: Archive corrupt A popuu says "The archive you're trying to open is corrupt. Some files may be missing or damaged [Open as Read-Only] [Don't Open]". Unfortunately no further information. Continuing with "Open as Read-Only" unpacks the archive. It can be opened w/o problems using unzip and both "zip -F" and "unzip -t" find no problem. Indeed, if I compare the MD5SUM of all the files unpacked by ark and unzip, everything matches up. Unfortunately I have no additional information as ark does not seem to have a verbose mode :-( ... the archive contains confidential info, so I can't provide it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388214] Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...
https://bugs.kde.org/show_bug.cgi?id=388214 --- Comment #3 from David Tonhofer --- kuiserver5, right? Is there actually a documentation on that? Nothing at KDE docs. I have found a blogpost: https://pindablog.wordpress.com/2008/07/24/more-on-kuiserver-and-extenders/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388214] Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...
https://bugs.kde.org/show_bug.cgi?id=388214 --- Comment #1 from David Tonhofer --- Created attachment 109510 --> https://bugs.kde.org/attachment.cgi?id=109510&action=edit There seems to be no processes corresponding to the notifications -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388214] New: Zombie notifications in plasmashell. There must be way to inspect/debug what is going on...
https://bugs.kde.org/show_bug.cgi?id=388214 Bug ID: 388214 Summary: Zombie notifications in plasmashell. There must be way to inspect/debug what is going on... Product: plasmashell Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugh...@gluino.name CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 109509 --> https://bugs.kde.org/attachment.cgi?id=109509&action=edit Zombie notifications in action In Fedora 27 KDE, which uses plasma-workspace-5.11.3-2.fc27.x86_64 I encounter the following: I am doing some heavy rearrangement/copying operations in Dolphin, in parallel. This seems to succeed (how do I into "I'm sure it succeeded?", ah, transactions and Unix filesystems, a problem since 1969 ;-) However, the plasmashell notification widget seems to remain in the "not sure" state (see attachment). 9 jobs are marked as "in progress" and display the "Zylon Moving Eye". However these notifications never go away. No processes seem to correspond to thos (see attachment) There is neither a title, nor a log, nor any explanation about what these are (basically, "zombie notifications", innit?) There needs to be a way to debug these. PID number, thread number. What caused the notification to appear, command line, anything. And indications about what happens if I press "pause" or "stop". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387878] Cosmetics: Icon inconsistency when you drag an icon to the "Panel" from the "Application Launcher"
https://bugs.kde.org/show_bug.cgi?id=387878 --- Comment #3 from David Tonhofer --- Hi Nate, The same things happens, see attached screenshot. Concerning the designations: The "Application Launcher" is what would match the "Windows Start Menu". It's the menu that pops up when you go the "start button" (in Fedora, the blue button with the barred integral sign). (Sorry about my Homer Simpson level of explanation, all the KDE widgets have names but they not fully unintuitive. And it's all about finding stuff and sending messages to stuff and getting notifications from stuff - I feel a new approach at GUIs is needed. No, not Metro! Anyway...) The fact is that the two icons in the "horizontal bar across the bottom of the screen" (i.e. the "Panel") are two different things. -> The small one, obtained by dragging the "Spreadsheet" icon from the "Start Menu" can be "unpinned" but that's it. -> The large one, obtained by right-clicking the "Spreadsheet" icon and selecting "Add to Panel" cannot be "unpinned" but has "properties". Implementation details are probably bubbling up here, like if one element is represented by a symlink and the other a configuration file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387878] Cosmetics: Icon inconsistency when you drag an icon to the "Panel" from the "Application Launcher"
https://bugs.kde.org/show_bug.cgi?id=387878 --- Comment #2 from David Tonhofer --- Created attachment 109382 --> https://bugs.kde.org/attachment.cgi?id=109382&action=edit Large and Small icon for the same stuff in the "Panel", Breeze icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387878] New: Cosmetics: Icon inconsistency when you drag an icon to the "Panel" from the "Application Launcher"
https://bugs.kde.org/show_bug.cgi?id=387878 Bug ID: 387878 Summary: Cosmetics: Icon inconsistency when you drag an icon to the "Panel" from the "Application Launcher" Product: plasmashell Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: bugh...@gluino.name CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 109360 --> https://bugs.kde.org/attachment.cgi?id=109360&action=edit Large and Small icon for the same stuff in the "Panel" This happens on Fedora 27 KDE: I have added the icon for LibreOffice Calc to the "Application Launcher" as well as to the "Panel" (as shown in the screenshot). The icon was added by using the option in the drop-down menu One can at that point drag & drop the "Spreadsheet" icon from the "Application Launcher" to the "Panel". At that point, you get an secondary icon for "Spreadsheet" which is smaller than the one added via the drop-down menu and which also has another style of explanatory pop-up note. This should probably be unified if there are no other pressing things to do. (I have only tested this with the "Oxygen" Icon Theme btw. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 153492] New display style in trash bin. Sorted by deletion date.
https://bugs.kde.org/show_bug.cgi?id=153492 --- Comment #18 from David Tonhofer --- Sweet! -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 153492] New display style in trash bin. Sorted by deletion date.
https://bugs.kde.org/show_bug.cgi?id=153492 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #15 from David Tonhofer --- I can't believe this is a nearly 10y old bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379780] New: File rename operation interleaves badly with file copy operation
https://bugs.kde.org/show_bug.cgi?id=379780 Bug ID: 379780 Summary: File rename operation interleaves badly with file copy operation Product: dolphin Version: 16.12.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Scenario: 1) Copy a large file A off the USB stick (which takes a bit) 2) Start renaming a file B that already resides in the copy destination directory 3) The file copy operation for A finishes while renaming of B is going on 4) The file A is before B in lexicographic order 5) The icon of the file B that I want to rename is switched with the icon of the file A, the rename operation stays pending. 5) If I press return now, I would rename A, not B Reproducable. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379720] Kmail crashes when opening a saved e-mail (.eml) saved off Microsoft OWA
https://bugs.kde.org/show_bug.cgi?id=379720 --- Comment #1 from David Tonhofer --- Created attachment 105440 --> https://bugs.kde.org/attachment.cgi?id=105440&action=edit kmail crashes on this -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379720] New: Kmail crashes when opening a saved e-mail (.eml) saved off Microsoft OWA
https://bugs.kde.org/show_bug.cgi?id=379720 Bug ID: 379720 Summary: Kmail crashes when opening a saved e-mail (.eml) saved off Microsoft OWA Product: kmail2 Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name Target Milestone: --- Application: kmail (5.4.3) Qt Version: 5.6.2 Frameworks Version: 5.33.0 Operating System: Linux 4.10.14-100.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: Opened e-mail saved from Microsoft OWA (this was an attachment that Microsoft Exchange sent me for approval). There is nothing special about the e-mail. Standard text file of 10483 bytes, Can attach on request The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd60e420940 (LWP 3718))] Thread 27 (Thread 0x7fd4fb5ff700 (LWP 3776)): #0 0x7fd62f8ecbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd62adfc959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fd62adfd020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fd62adfd1f0 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fd62adf9c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fd62f8e75ca in start_thread () at /lib64/libpthread.so.0 #6 0x7fd6332f30ed in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fd585773700 (LWP 3771)): #0 0x7fd62f8ecbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd617a791a4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fd617a791e9 in () at /lib64/libQt5Script.so.5 #3 0x7fd62f8e75ca in start_thread () at /lib64/libpthread.so.0 #4 0x7fd6332f30ed in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fd586bf6700 (LWP 3759)): #0 0x7fd6332e756d in poll () at /lib64/libc.so.6 #1 0x7fd622f1ea06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fd622f1eb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fd6340ed80b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fd63409c83a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fd633efb343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fd633eff9aa in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fd62f8e75ca in start_thread () at /lib64/libpthread.so.0 #8 0x7fd6332f30ed in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fd5a5ffb700 (LWP 3752)): #0 0x7fd62f8ecbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd62adfc959 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fd62adfd020 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fd62adfd1f0 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fd62adf9c2d in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fd62f8e75ca in start_thread () at /lib64/libpthread.so.0 #6 0x7fd6332f30ed in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fd5a67fc700 (LWP 3751)): #0 0x7fd62f8ecbd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd62ad0c7c0 in mojo::system::Waiter::Wait(unsigned long, unsigned int*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fd62acf839c in mojo::system::Core::WaitManyInternal(unsigned int const*, unsigned int const*, unsigned int, unsigned long, unsigned int*, mojo::system::HandleSignalsState*) () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fd62acf889c in mojo::system::Core::WaitMany(mojo::system::UserPointer, mojo::system::UserPointer, unsigned int, unsigned long, mojo::system::UserPointer, mojo::system::UserPointer) () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fd62acf4cf5 in MojoWaitMany () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fd62c36bc47 in mojo::common::MessagePumpMojo::DoInternalWork(mojo::common::MessagePumpMojo::RunState const&, bool) () at /lib64/libQt5WebEngineCore.so.5 #6 0x7fd62c36be7e in mojo::common::MessagePumpMojo::DoRunLoop(mojo::common::MessagePumpMojo::RunState*, base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #7 0x7fd62c36bfb9 in mojo::common::MessagePumpMojo::Run(base::MessagePump::De
[kmail2] [Bug 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #39 from David Tonhofer --- I am seeing aknoadiserver going to 100% forever once kmail is started. Even with kmail off, akonadi keeps working on the IMAP folders like a madman: /usr/bin/akonadi_control \_ akonadiserver | \_ /usr/libexec/mysqld --defaults-file=/home/hobbes/.local/share/akonadi/mysql.conf --datadir=/home/hobbes/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-hobbes.aB9Ele/mysql.socket \_ /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_0 \_ /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent \_ /usr/bin/akonadi_baloo_indexer --identifier akonadi_baloo_indexer \_ /usr/bin/akonadi_birthdays_resource --identifier akonadi_birthdays_resource \_ /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0 \_ /usr/bin/akonadi_followupreminder_agent --identifier akonadi_followupreminder_agent \_ /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_0 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_10 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_11 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_12 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_13 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_14 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_15 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_16 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_17 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_18 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_19 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_2 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_20 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_21 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_3 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_4 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_5 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_6 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_7 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_8 \_ /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_9 \_ /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_0 \_ /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent \_ /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent \_ /usr/bin/akonadi_migration_agent --identifier akonadi_migration_agent \_ /usr/bin/akonadi_newmailnotifier_agent --identifier akonadi_newmailnotifier_agent \_ /usr/bin/akonadi_notes_agent --identifier akonadi_notes_agent \_ /usr/bin/akonadi_sendlater_agent --identifier akonadi_sendlater_agent This is Fedora 22: - akonadi-1.13.0-16 - kdepim-runtime-libs-4.14.10-5 How do I confirm the problem? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 196314] akonadiserver takes 100% cpu for hours
https://bugs.kde.org/show_bug.cgi?id=196314 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #2 from David Tonhofer --- Well, 100% CPU for 15 hours straight is still a thing 6 years later, with akonadi-1.13.0-16 and qt 4.8.6. Must be another bug. Probably. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357945] New: Deleting a message on an IMAP account moves the message to local "Trash" instead of IMAP "Trash"
https://bugs.kde.org/show_bug.cgi?id=357945 Bug ID: 357945 Summary: Deleting a message on an IMAP account moves the message to local "Trash" instead of IMAP "Trash" Product: kmail2 Version: 4.14.7 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name Heads-up to the maintainer: Selectable version numbering on this bug lists 4.14.7 and 5.1, but I have 4.14.10 (using KDE development platform 4.14.14). Should probably be completed Created an IMAP "receving account" called "bughunt" In the "Advanced Part", the "Trash folder" is set to the remote "Trash", i.e. "bughunt/inbox/Trash" However, when deleting a message using "Move to Trash" in dropdown menu or "delete" key, the deleted message does not appear in the IMAP folder "Trash" but instead appears in the "Local Folders" "trash" (written with lowercase) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 --- Comment #5 from David Tonhofer --- Also bug#340529 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #4 from David Tonhofer --- Same as bug#283345 I guess I have a similar one with kaddressbook bug#357266 - and my guess is that the application uses short numeric ids to reference akonadi database records which, after a rebuild, have completely different ids at random. Just a hunch. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 333655] Baloo indexing I/O introduces serious noticable delays
https://bugs.kde.org/show_bug.cgi?id=333655 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336274] "Connecting…" status causes high plasmashell CPU usage
https://bugs.kde.org/show_bug.cgi?id=336274 David Tonhofer changed: What|Removed |Added CC||bugh...@gluino.name --- Comment #32 from David Tonhofer --- > As soon as I deselect "Application Status" in the "System Tray Settings", > which makes the spinning icon disappear, the CPU usage is much lower. Observed on Fedora 22 with plasma-desktop-5.5.0-4 kf5-plasma-5.17.0-2 Upgrading to Fedora 23 soon anyway... -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357266] New: Dangerous design problem for kaddressbook groups in case ~/.local/share/akonadi/ is blown away
https://bugs.kde.org/show_bug.cgi?id=357266 Bug ID: 357266 Summary: Dangerous design problem for kaddressbook groups in case ~/.local/share/akonadi/ is blown away Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name CC: to...@kde.org Suppose you get a dumbass attack and blow away the Akonadi database in ~/.local/share/akonadi/ On restart, akonadi rebuilds the database. The basic contacts in kaddressbook are all fine. However, the *groups* now contain random contacts (embarrasing if you don't notice and use them without verification) or result in kaddressbook crashing when opened. This might be due to kaddressbook setting up groups using small-int identifiers into the Akonadi database (maybe?) instead of using UUIDs that would make it clear that the original contact entry has just gone away. It should be clear to Akonadi that the group has become dangerously messed up and no longer contain valid references. Safety first etc. P.S. This problem also occurs with the configuration of IMAP accounts (trash/draft/template folders and sending identities) - kmail starts up and does not complain at all but is all messed up underneath instead of insulting the issue with clear error messages. P.S. (The version of "kaddressbook" is "4.14.10.-7" which is not listed in Version (it stops at 4.13.2)??) Reproducible: Always Steps to Reproduce: I will have to reproduce it in actuality, but the steps would be: 1. Destroy ~/.local/share/akonadi/ 2. Restart 3. kaddressbook contacts messed up -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357263] New: Crash when opening addressbook entry (group) from kmail
https://bugs.kde.org/show_bug.cgi?id=357263 Bug ID: 357263 Summary: Crash when opening addressbook entry (group) from kmail Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugh...@gluino.name CC: to...@kde.org Application: kaddressbook (4.14.10) KDE Platform Version: 4.14.14 Qt Version: 4.8.6 Operating System: Linux 4.2.8-200.fc22.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Opened addressbook group. Kmail displays a dialog saying that it is working Then crashes The addressbook seems to be foobared underneath though; addressbook group has wrong contents (that's why I wanted to open it) -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7fc8ee7c39c8 in raise () at /lib64/libc.so.6 #7 0x7fc8ee7c565a in abort () at /lib64/libc.so.6 #8 0x7fc8ef0fdb5d in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6 #9 0x7fc8ef0fb9a6 in () at /lib64/libstdc++.so.6 #10 0x7fc8ef0fb9f1 in () at /lib64/libstdc++.so.6 #11 0x7fc8ef0fbc59 in __cxa_rethrow () at /lib64/libstdc++.so.6 #12 0x7fc8ef794cfe in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #13 0x7fc8ef79a6a9 in QCoreApplication::exec() () at /lib64/libQtCore.so.4 #14 0x00405560 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
