[dolphin] [Bug 420587] "Limit to home directory" option only available when right-clicking a directory, not empty space
https://bugs.kde.org/show_bug.cgi?id=420587 --- Comment #1 from Abscissa --- This adversely affects discoverability of the feature. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420587] New: "Limit to home directory" option only available when right-clicking a directory, not empty space
https://bugs.kde.org/show_bug.cgi?id=420587 Bug ID: 420587 Summary: "Limit to home directory" option only available when right-clicking a directory, not empty space Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: bus_kdezi...@semitwist.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The "Limit to home directory" option is only included in the right-click menu when right-clicking an actual directory in the Folders panel, not when right-clicking empty space within the Folders panel (for example, after the end of the list). This is strange because the option doesn't actually relate to any specifically chosen directory, and is a rather a property of the entire panel itself. STEPS TO REPRODUCE 1. Run dolphin. 2. Go to the Folders panel. 3. Right-click the empty space within the Folders panel below the last entry in the tree. OBSERVED RESULT "Limit to home directory" option is missing from popup context menu. EXPECTED RESULT "Limit to home directory" option should be shown in popup context menu. SOFTWARE/OS VERSIONS Linux: Manjaro, Kernel 5.6.6-1 KDE Plasma Version: 5.18.4.1-1 KDE Frameworks Version: 5.69.0-2 Qt Version: 4.8.7-29.1 and 5.14.2-1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400272] Dolphin crashes on startup on invalid XML config file
https://bugs.kde.org/show_bug.cgi?id=400272 Abscissa changed: What|Removed |Added Depends on||400271 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400271 [Bug 400271] Need way to allow applications to handle invalid XML without crashing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400271] Need way to allow applications to handle invalid XML without crashing.
https://bugs.kde.org/show_bug.cgi?id=400271 Abscissa changed: What|Removed |Added Blocks||400272 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400272 [Bug 400272] Dolphin crashes on startup on invalid XML config file -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400272] New: Dolphin crashes on startup on invalid XML config file
https://bugs.kde.org/show_bug.cgi?id=400272 Bug ID: 400272 Summary: Dolphin crashes on startup on invalid XML config file Product: dolphin Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bus_kdezi...@semitwist.com CC: elvis.angelac...@kde.org Target Milestone: --- I was unable to fix the status of Bug 400093 so I'm continuing it here. The basic problem is that Dolphin immediately crashes upon startup if ~/.local/share/kxmlgui5/dolphin/dolphinui.rc is malformed. According to Elvis Angelaccio, this is due to a limitation in kxmlgui. I have filed a corresponding issue for kxmlgui: Bug 400271 Replying to Elvis Angelaccio's message from Bug 400093: "There is an abort() in kxmlgui if the xml file has a wrong syntax." If that's true, then that's clearly a major shortcoming of kxmlgui. In this case, the correct course of action is not to mark this a non-bug, but rather to open an issue for kxmlgui to support optionally dealing with bad XML in a way other than crashing the entire application (see below) and to mark that issue as blocking this one. "There is nothing we can do to prevent the crash, as that file is used to build the whole GUI and must be correct." That is clearly not true. For example, kxmlgui can first be fixed to add optional support for handling bad XML in a way other than crashing, after which, Dolphin can be fixed to do any one or more of the following (and these are just off the top of my head): A. Present a dialog informing the user that ~/.local/share/kxmlgui5/dolphin/dolphinui.rc is malformed. Maybe even show some basic information about the error, such as line number. So the user actually knows what went wrong and why, and at least has some hope of doing something about it, rather than being left with what appears to be (and may as well be, from their perspective) a fatally broken piece of software. B. Start Dolphin anyway, using the default configuration Dolphin already uses when no dolphinui.rc is found. So the user can at least still use the application if they need to. C. (Maybe) Rename the corrupted dolphinui.rc to a backup name, so it doesn't continue to cause problems. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400093] Dolphin crashes on startup on invalid XML config file.
https://bugs.kde.org/show_bug.cgi?id=400093 Abscissa changed: What|Removed |Added Depends on||400271 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400271 [Bug 400271] Need way to allow applications to handle invalid XML without crashing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400271] Need way to allow applications to handle invalid XML without crashing.
https://bugs.kde.org/show_bug.cgi?id=400271 Abscissa changed: What|Removed |Added Blocks||400093 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=400093 [Bug 400093] Dolphin crashes on startup on invalid XML config file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400271] New: Need way to allow applications to handle invalid XML without crashing.
https://bugs.kde.org/show_bug.cgi?id=400271 Bug ID: 400271 Summary: Need way to allow applications to handle invalid XML without crashing. Product: frameworks-kxmlgui Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: bus_kdezi...@semitwist.com Target Milestone: --- According to Elvis Angelaccio over at Bug 400093, "There is an abort() in kxmlgui if the xml file has a wrong syntax." As a result, Dolphin crashes upon startup if its config has become messed up, and is unable to perform any actions such as informing the user of what went wrong, loading a default configurations instead, etc. If both my understanding and Elvis's analysis of kxmlgui correct, then this means ANY application using kxmlgui is doomed to the same crash behaviour, with no option for graceful handling. What is needed is a mechanism, possibly opt-in, for an application using kxmlgui to be told of an error in the XML, leaving it up to the application to determine how to proceed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400093] Dolphin crashes on startup on invalid XML config file.
https://bugs.kde.org/show_bug.cgi?id=400093 Abscissa changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #8 from Abscissa --- "There is an abort() in kxmlgui if the xml file has a wrong syntax." If that's true, then that's clearly a major shortcoming of kxmlgui. In this case, the correct course of action is not to mark this a non-bug, but rather to open an issue for kxmlgui to support optionally dealing with bad XML in a way other than crashing the entire application (see below) and to mark that issue as blocking this one. "There is nothing we can do to prevent the crash, as that file is used to build the whole GUI and must be correct." That is clearly not true. For example, kxmlgui can first be fixed to add optional support for handling bad XML in a way other than crashing, after which, Dolphin can be fixed to do any one or more of the following (and these are just off the top of my head): A. Present a dialog informing the user that ~/.local/share/kxmlgui5/dolphin/dolphinui.rc is malformed. Maybe even show some basic information about the error, such as line number. So the user actually knows what went wrong and why, and at least has some hope of doing something about it, rather than being left with what appears to be (and may as well be, from their perspective) a fatally broken piece of software. B. Start Dolphin anyway, using the default configuration Dolphin already uses when no dolphinui.rc is found. So the user can at least still use the application if they need to. C. (Maybe) Rename the corrupted dolphinui.rc to a backup name, so it doesn't continue to cause problems. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400093] Dolphin crashes on startup on invalid XML config file.
https://bugs.kde.org/show_bug.cgi?id=400093 --- Comment #4 from Abscissa --- The matter of "Dolphin suspected of corrupting its config file" is now reported as Bug 400228. Leaving this issue open as Dolphin crashing on bad XML input. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400228] New: Dolphin suspected of corrupting its config file.
https://bugs.kde.org/show_bug.cgi?id=400228
Bug ID: 400228
Summary: Dolphin suspected of corrupting its config file.
Product: dolphin
Version: unspecified
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: bus_kdezi...@semitwist.com
CC: elvis.angelac...@kde.org
Target Milestone: ---
As noted in Issue #400093 ("Dolphin crashes on startup on invalid XML config
file."), my ~/.local/share/kxmlgui5/dolphin/dolphinui.rc has become corrupted
(thus leading to an initially-mysterious inability to start Dolphin without it
immediately crashing) even though I have not made any edits to the file.
I am aware there are other potential and theoretical causes for this. However,
when an application-specific config file is corrupted, it's usually (even if
not always) the application itself that corrupted it, since after all, that's
the software that's most likely to touch the given file the most often.
Therefore, I am reporting it here so the developers are aware and can be on the
lookout for anything suspect in the code.
As in the other issue (#400093), I am pasting the corrupted file contents
below.
I looks to me like something must have done the following:
1. Loaded the file into a buffer.
2. Wrote a shorter version of the data into the same buffer.
3. Failed to correctly set the new shorter length of the buffer.
4. Wrote the newly-garbled buffer back out to disk.
Location Bar
Main Toolbar
zoom_in"/>
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 400093] Dolphin crashes on startup on invalid XML config file.
https://bugs.kde.org/show_bug.cgi?id=400093 --- Comment #3 from Abscissa --- Splitting the corruption itself into a separate issue... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400093] Dolphin crashes on startup on invalid XML config file.
https://bugs.kde.org/show_bug.cgi?id=400093 Abscissa changed: What|Removed |Added Summary|Dolphin always crashes on |Dolphin crashes on startup |startup |on invalid XML config file. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400093] Dolphin always crashes on startup
https://bugs.kde.org/show_bug.cgi?id=400093 --- Comment #2 from Abscissa --- Renaming that file does prevent the crash. I'll update the issue title accordingly. Note also, there's still the question of what messed up the file in the first place. I've never touched it. The contents of the file is included below. I looks to me like something (I would assume most likely Dolphin itself) must've done the following: 1. Loaded the file into a buffer. 2. Wrote a shorter version of the data into the same buffer. 3. Failed to correctly set the new shorter length of the buffer. 4. Wrote the newly-garbled buffer back out to disk. In any case, crashing on bad input is obviously a bug, too. Location Bar Main Toolbar zoom_in"/> -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400093] New: Dolphin always crashes on startup
https://bugs.kde.org/show_bug.cgi?id=400093 Bug ID: 400093 Summary: Dolphin always crashes on startup Product: dolphin Version: 18.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bus_kdezi...@semitwist.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphin automatically crashes every time I try to start it. STEPS TO REPRODUCE 1. Start dolphin. 2. It crashes. (Before a dolphin window is displayed) 3. OBSERVED RESULT It crashes. Before a dolphin window is displayed. EXPECTED RESULT Not crashing. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1-1 KDE Frameworks Version: 5.51.0-1 Qt Version: 5.11.2-1 ADDITIONAL INFORMATION Problem also occurred on Dolphin 18.08.1. The last version I had installed before that did work correctly, however, it had been awhile since I'd updated so I have no idea what version that was. Crash report: -- Application: Dolphin (dolphin), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1505f56800 (LWP 1876))] Thread 3 (Thread 0x7f1503541700 (LWP 1878)): #0 0x7f150fb12c21 in poll () from /usr/lib/libc.so.6 #1 0x7f150af7dee0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f150af7dfce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f150dc73fe4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f150dc1f8cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f150da68eb9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f150dec5ba6 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f150da72f65 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f150be55a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f150fb1db23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f150476a700 (LWP 1877)): #0 0x7f150fb12c21 in poll () from /usr/lib/libc.so.6 #1 0x7f150ab93630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f150ab952db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f1505ae4c5a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f150da72f65 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f150be55a9d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f150fb1db23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1505f56800 (LWP 1876)): [KCrash Handler] #6 0x7f150fa59d7f in raise () from /usr/lib/libc.so.6 #7 0x7f150fa44672 in abort () from /usr/lib/libc.so.6 #8 0x7f150f19679a in KXMLGUIClient::setXML(QString const&, bool) () from /usr/lib/libKF5XmlGui.so.5 #9 0x7f150f197222 in ?? () from /usr/lib/libKF5XmlGui.so.5 #10 0x7f150f1b97ab in KXmlGuiWindow::createGUI(QString const&) () from /usr/lib/libKF5XmlGui.so.5 #11 0x7f150f1ba5bc in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /usr/lib/libKF5XmlGui.so.5 #12 0x7f150f1ba68c in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /usr/lib/libKF5XmlGui.so.5 #13 0x7f150fc31e47 in ?? () from /usr/lib/libkdeinit5_dolphin.so #14 0x7f150fc26484 in kdemain () from /usr/lib/libkdeinit5_dolphin.so #15 0x7f150fa46223 in __libc_start_main () from /usr/lib/libc.so.6 #16 0x55e9adeb805e in _start () [Inferior 1 (process 1876) detached] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380983] New: Transfer User Settings
https://bugs.kde.org/show_bug.cgi?id=380983 Bug ID: 380983 Summary: Transfer User Settings Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: bus_kdezi...@semitwist.com Target Milestone: --- Where are KDevelop's settings stored? Or more to the point, how can I transfer my KDevelop settings (highlighting colors, key bindings, etc) to another machine? https://forum.kde.org/viewtopic.php?f=218=140451=f3614bdf374e88e0188d23632484a7c0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378443] Plasma 5 start-button gets too big when the panel is vertical. (there was no problem in Plasma 4)
https://bugs.kde.org/show_bug.cgi?id=378443
--- Comment #24 from Abscissa <bus_kdezi...@semitwist.com> ---
Just checked this out in the latest Neon unstable live disc. While it's
definitely improved ("Show Desktop" works perfectly and immediately reacts to
changes in the "Panel" Icon Size setting (when applied)), there are still some
issues with still with other widgets:
- "Application Menu" and "Application Dashboard" doesn't react immediately to
Icon Size changes. I have to force it to refresh first. I did that by switching
the widget to something else (like "Application Launcher") and back again.
- "Application Menu" and "Application Dashboard" *sometimes* react to changes
in "Desktop" Icon Size. But then sometimes it seems to go with the "Panel" Icon
Size. Try playig around with changing the icon size setting and then using the
"Alternatives... -> Switch" feature.
- The following widgets (that I've discovered so far) are completely unaffected
by this fix and still exhibit the old, incorrect behavior:
* "Application Launcher"
* "Activities" (a problem for me, since I use this)
* "Activity Bar"
* "Quicklaunch" (This might be a separate issue though, due to the way it seems
to work)
* "Analog Clock"
* "Binary Clock"
* "Calendar"
* "Bluetooth"
There may be others as well, I didn't check all of them.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 378443] Plasma 5 start-button gets too big when the panel is vertical. (there was no problem in Plasma 4)
https://bugs.kde.org/show_bug.cgi?id=378443 --- Comment #22 from Abscissa <bus_kdezi...@semitwist.com> --- Fantastic! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378443] Plasma 5 start-button gets too big when the panel is vertical. (there was no problem in Plasma 4)
https://bugs.kde.org/show_bug.cgi?id=378443 Abscissa <bus_kdezi...@semitwist.com> changed: What|Removed |Added CC||bus_kdezi...@semitwist.com --- Comment #14 from Abscissa <bus_kdezi...@semitwist.com> --- This issue has been keeping me on KDE4 for years, despite having brought it up on the forums as far back as 2014 with no response whatsoever (except for a link to this ticket just this month): https://forum.kde.org/viewtopic.php?f=83=122938=319975#p319975 https://forum.kde.org/viewtopic.php?f=289=131908 TO REPRODUCE THIS ISSUE (trivial): This is trivial to reproduce on any KDE5/Plasma5 installation: 1. Create a new "Default Panel". 2. Move it to the left or right side of the screen. 3. Adjust the width so the text on the task manager button is actually readable and doesn't look like Win7 or OSX. The issue is now reproduced. Note too, that "Kicker" is not the only widget that exhibits this problem. MOST other widgets available also exhibit the same problem, including all the alternate application menus and the "three ball" activities menu. Unlike KDE4, this has nothing to do the images used, and has everything to do with the way Plasma5 calculates sizes for widgets on a panel. -- You are receiving this mail because: You are watching all bug changes.
