[dolphin] [Bug 459008] All attached drives are not sorted
https://bugs.kde.org/show_bug.cgi?id=459008 --- Comment #7 from Stefan Gies --- Am 05.04.23 um 11:33 schrieb Méven Car: > https://bugs.kde.org/show_bug.cgi?id=459008 > > --- Comment #6 from Méven Car --- > I am not sure how to fix this. > > Because harddrive can be added at any point. > Users currently can expect devices to be visible in the order the were added. > Maintaining an alphabetical order would break this assumption. > > You already have a simple workaround: reorganize the order by hand. > > So I am guessing the best thing we could do, is to add a context menu option > for devices "sort by name". > Do you think Stefan that would be fixing your issue ? > It's okay -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459008] All attached drives are not sorted
https://bugs.kde.org/show_bug.cgi?id=459008 --- Comment #5 from Stefan Gies --- -Original-Nachricht- Betreff: [dolphin] [Bug 459008] All attached drives are not sorted Datum: 2023-04-04T06:06:59+0200 Von: "Stefan Gies" An: "sgies1...@t-online.de" https://bugs.kde.org/show_bug.cgi?id=459008 --- Comment #4 from Stefan Gies --- see attachment -Original-Nachricht- Betreff: [dolphin] [Bug 459008] All attached drives are not sorted Datum: 2023-04-02T21:06:14+0200 Von: "Méven Car" An: "sgies1...@t-online.de" https://bugs.kde.org/show_bug.cgi?id=459008 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #1 from Méven Car --- Could you share the return of the command `solid-hardware list` or `solid-hardware5 list` depending on your system ? And a few of the entries returned by `solid-hardware details udi` where udi is one of the value for one those hard-drives. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459008] All attached drives are not sorted
https://bugs.kde.org/show_bug.cgi?id=459008 --- Comment #4 from Stefan Gies --- see attachment -Original-Nachricht- Betreff: [dolphin] [Bug 459008] All attached drives are not sorted Datum: 2023-04-02T21:06:14+0200 Von: "Méven Car" An: "sgies1...@t-online.de" https://bugs.kde.org/show_bug.cgi?id=459008 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #1 from Méven Car --- Could you share the return of the command `solid-hardware list` or `solid-hardware5 list` depending on your system ? And a few of the entries returned by `solid-hardware details udi` where udi is one of the value for one those hard-drives. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459008] All attached drives are not sorted
https://bugs.kde.org/show_bug.cgi?id=459008 --- Comment #3 from Stefan Gies --- Am 02.04.23 um 21:06 schrieb Méven Car: > solid-hardware5 list see hardware.txt -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 396348] Opening password protected ods-file causes an error
https://bugs.kde.org/show_bug.cgi?id=396348 --- Comment #3 from Stefan Gies --- Am 11.12.22 um 06:08 schrieb Bug Janitor Service: > https://bugs.kde.org/show_bug.cgi?id=396348 > > --- Comment #2 from Bug Janitor Service --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > Resolved -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459008] New: All attached drives are not sorted
https://bugs.kde.org/show_bug.cgi?id=459008 Bug ID: 459008 Summary: All attached drives are not sorted Product: dolphin Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: sgies1...@t-online.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 151991 --> https://bugs.kde.org/attachment.cgi?id=151991=edit Screenshot of my external drives in Dolphin SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add 17 external Harddisks and mount them 2. Then try to find a special drive type 3. The only way to see them sortet is with krusader OBSERVED RESULT not sorted by name EXPECTED RESULT sorted by name SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446808] New: Crash after Login in account
https://bugs.kde.org/show_bug.cgi?id=446808 Bug ID: 446808 Summary: Crash after Login in account Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sgies1...@t-online.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.4) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I started the system and then I logged in. Then the crash happens. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 2068] [New LWP 2088] [New LWP 2352] [New LWP 2361] [New LWP 2373] [New LWP 2376] [New LWP 2396] [New LWP 2447] [New LWP 2449] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f824096daff in __GI___poll (fds=0x7ffc4c7e7db8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f823cac29c0 (LWP 2060))] Thread 10 (Thread 0x7f81e6052700 (LWP 2449)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f1100b4870) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f1100b4820, cond=0x55f1100b4848) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f1100b4848, mutex=0x55f1100b4820) at pthread_cond_wait.c:638 #3 0x7f8240d025cb in QWaitConditionPrivate::wait (deadline=..., this=0x55f1100b4820) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55f110094e10, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f824296dc24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f824296e099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f8240cfc45c in QThreadPrivate::start (arg=0x55f110094d70) at thread/qthread_unix.cpp:329 #8 0x7f823fc47609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f824097a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f81e7ec1700 (LWP 2447)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f10f4d1164) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f10f4d1110, cond=0x55f10f4d1138) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f10f4d1138, mutex=0x55f10f4d1110) at pthread_cond_wait.c:638 #3 0x7f8240d025cb in QWaitConditionPrivate::wait (deadline=..., this=0x55f10f4d1110) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55f10e52af40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f824296dc24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f824296e099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f8240cfc45c in QThreadPrivate::start (arg=0x55f10e52aea0) at thread/qthread_unix.cpp:329 #8 0x7f823fc47609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f824097a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f81f77fe700 (LWP 2396)): #0 0x7f823f2634dd in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f823f215af5 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f823f2162e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f823f2164a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8240f3d61b in QEventDispatcherGlib::processEvents (this=0x7f81e800be70, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8240ee18ab in QEventLoop::exec (this=this@entry=0x7f81f77fdba0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f8240cfb2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f81f4ca907c in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #8 0x7f8240cfc45c in QThreadPrivate::start (arg=0x55f10ec54780) at thread/qthread_unix.cpp:329 #9 0x7f823fc47609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f824097a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f81f7fff700 (LWP 2376)): #0 0x7f824097012b in __GI___select (nfds=46, readfds=0x7f81f7ffeba0, writefds=0x0, exceptfds=0x0, timeout=0x7f81f7ffeb90) at ../sysdeps/unix/sysv/linux/select.c:41 #1 0x7f8232ba37f1 in ?? () from
[k3b] [Bug 435285] K3b, Xfburn and Brasero do not burn a BD-RE error free
https://bugs.kde.org/show_bug.cgi?id=435285 --- Comment #4 from Stefan Gies --- Problem solved. The used media was bad. Sorry -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 435285] K3b, Xfburn and Brasero do not burn a BD-RE error free
https://bugs.kde.org/show_bug.cgi?id=435285 --- Comment #3 from Stefan Gies --- The error happens in Fedora 33 WS 64bit too -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 435285] K3b, Xfburn and Brasero do not burn a BD-RE error free
https://bugs.kde.org/show_bug.cgi?id=435285 --- Comment #2 from Stefan Gies --- Created attachment 137389 --> https://bugs.kde.org/attachment.cgi?id=137389=edit Second PC environment -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 435285] K3b, Xfburn and Brasero do not burn a BD-RE error free
https://bugs.kde.org/show_bug.cgi?id=435285 --- Comment #1 from Stefan Gies --- Created attachment 137310 --> https://bugs.kde.org/attachment.cgi?id=137310=edit Hardware environment Hardware environment -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 435285] New: K3b, Xfburn and Brasero do not burn a BD-RE error free
https://bugs.kde.org/show_bug.cgi?id=435285 Bug ID: 435285 Summary: K3b, Xfburn and Brasero do not burn a BD-RE error free Product: k3b Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: sgies1...@t-online.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- SUMMARY K3b, Xfburn and Brasero do not burn BD-RE error free STEPS TO REPRODUCE 1. open a cd/dvd iso or make a session to write various files 2. try to burn it to bd-re with 2x speed 3. writing is very slow 0.2x speed 4. after a short time the writing will be terminated with an error OBSERVED RESULT The burning will be terminated with an error The error ocures on different 64bit platforms, eg Debian 10, Mx-Linux 19.3, Ubuntu Mate 20.04.2 and so on Following error in XFBurn: Failed: CDB= WRITE(12) : aa 00 00 03 e4 00 00 00 00 20 80 00 : dxfer_len= 65536 EXPECTED RESULT error free writing the image and / or data SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am using KDE Neon in the newest version -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 343810] Bluray burn fails always write with input output error using K3B or brasero/nautilus
https://bugs.kde.org/show_bug.cgi?id=343810 Stefan Gies changed: What|Removed |Added CC||sgies1...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 342533] Crash while dragging and dropping seleced bookmarks
https://bugs.kde.org/show_bug.cgi?id=342533 Stefan Gies changed: What|Removed |Added CC||sgies1...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 342533] Crash while dragging and dropping seleced bookmarks
https://bugs.kde.org/show_bug.cgi?id=342533 --- Comment #5 from Stefan Gies --- Created attachment 137228 --> https://bugs.kde.org/attachment.cgi?id=137228=edit New crash information added by DrKonqi keditbookmarks (20.12.3) using Qt 5.15.2 - What I was doing when the application crashed: Dragging and dropping imported bookmarks -- Backtrace (Reduced): #4 TreeItem::deleteChildren (this=0x0, first=-1, last=-1) at ./src/kbookmarkmodel/treeitem.cpp:73 #5 0x7fefbd7c4c0c in KBookmarkModel::removeBookmark (this=0x55f9e97627a0, bookmark=...) at ./src/kbookmarkmodel/model.cpp:456 #6 0x7fefbd7be594 in CreateCommand::undo (this=0x55f9e9b59020) at ./src/kbookmarkmodel/commands.cpp:159 #7 0x7fefbd7c122e in DeleteCommand::redo (this=0x55f9ea03a450) at ./src/kbookmarkmodel/commands.cpp:323 #8 0x7fefbcb07cda in QUndoCommand::redo() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwebkitpart] [Bug 317475] Konqueror segfault opening link in new tab
https://bugs.kde.org/show_bug.cgi?id=317475 --- Comment #72 from Stefan Gies --- Am 04.12.20 um 06:13 schrieb Justin Zobel: > https://bugs.kde.org/show_bug.cgi?id=317475 > > Justin Zobel changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||justin.zo...@gmail.com > Resolution|--- |WAITINGFORINFO > > --- Comment #71 from Justin Zobel --- > Thank you for the reports. > > As it has been a while since a duplicate was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as > resolved. > > I have set the bug status to "needsinfo" pending your response, please change > back to "reported" or "resolved/worksforme" when you respond, thank you. > I can not test it, because I use a different Distro ! -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 396348] New: Opening password protected ods-file causes an error
https://bugs.kde.org/show_bug.cgi?id=396348 Bug ID: 396348 Summary: Opening password protected ods-file causes an error Product: calligrasheets Version: 3.0.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: opendocument Assignee: calligra-sheets-bugs-n...@kde.org Reporter: sgies1...@t-online.de Target Milestone: --- Created attachment 113853 --> https://bugs.kde.org/attachment.cgi?id=113853=edit LibreCalc-File "test.ods" with password "test" Opening file test.ods not possible. Error reading file in line 1 column 1 Errormessage: An invalid coding in content found -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 369571] Opening a password protected LibreOffice Writer document causes failure
https://bugs.kde.org/show_bug.cgi?id=369571 --- Comment #2 from Stefan Gies <sgies1...@t-online.de> --- Created attachment 101361 --> https://bugs.kde.org/attachment.cgi?id=101361=edit LibreOffice file with password The password is 123456 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 369571] Opening a password protected LibreOffice Writer document causes failure
https://bugs.kde.org/show_bug.cgi?id=369571 --- Comment #1 from Stefan Gies <sgies1...@t-online.de> --- Created attachment 101360 --> https://bugs.kde.org/attachment.cgi?id=101360=edit My hardware This file contains my hardware-configuration -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 369571] New: Opening a password protected LibreOffice Writer document causes failure
https://bugs.kde.org/show_bug.cgi?id=369571 Bug ID: 369571 Summary: Opening a password protected LibreOffice Writer document causes failure Product: calligrawords Version: 2.9.7 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: opendocument Assignee: calligra-words-bugs-n...@kde.org Reporter: sgies1...@t-online.de If you try opening a password protected LibreOffice Writer document Calligra Words fails. Libre Office Writer has the version : 1:5.1.4-0ubuntu1 Reproducible: Always Steps to Reproduce: 1. Create a LibreOffice Writer document (.odt) 2. Save the file with a password 3. Open it with Calligra Words Actual Results: First error message: This document has a invalid chechsum. Second error message: This document uses an unknown encryption method Third error message: Opening the file impossible Expected Results: asking for password and afterwards opening the file to edit it OS : Kubuntu v16.04.1 64 bit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 303175] KMail and IMAP AOL: Unable to fetch item from backend
https://bugs.kde.org/show_bug.cgi?id=303175 --- Comment #4 from Stefan Gies <sgies1...@t-online.de> --- I installed Kmail in Fedora 24 WS 64 in version 16.08.1-1.fc24. The result was after first start without any problems. But after adding a account from aol, the software crashes. After a restart of the pc, the error was reproducable. After theis knowledge I uninstalled the program. -Original-Nachricht- Betreff: [kmail2] [Bug 303175] KMail and IMAP AOL: Unable to fetch item from backend Datum: 2016-09-24T19:52:23+0200 Von: "Denis Kurz via KDE Bugzilla" <bugzilla_nore...@kde.org> An: "sgies1...@t-online.de" <sgies1...@t-online.de> https://bugs.kde.org/show_bug.cgi?id=303175 Denis Kurz <kde...@posteo.de> changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Denis Kurz <kde...@posteo.de> --- This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. -- You are receiving this mail because: You are watching all bug changes.
