[plasmashell] [Bug 60894] Periodic auto-saving of session state so state isn't lost if there's a crash or power loss
https://bugs.kde.org/show_bug.cgi?id=60894 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #18 from Eric S --- Woah thus bug is old! Is it really so hard to have a timer task run that does the equivalent of the manual save session button? Is there a command line way to trigger that function that I could add to a cron job? If not, could a command line way to activate it be added as a bit of a stopgap for this issue? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 488077] New: quotes implicitly in "automatically close brackets" feature
https://bugs.kde.org/show_bug.cgi?id=488077
Bug ID: 488077
Summary: quotes implicitly in "automatically close brackets"
feature
Classification: Applications
Product: kate
Version: 24.02.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kwrite
Assignee: kwrite-bugs-n...@kde.org
Reporter: subscri...@blackbrook.org
Target Milestone: ---
SUMMARY
My "Enclosing characters" field in my Settings->Editing Options->General is set
to
<>(){}[]
But checking the box above it for "Automatically close brackets when opening
bracket is typed" causes the editor to automatically close double (") and
single (') quotes. There are 3 problems with this:
1) these characters are not listing in the "Enclosing characters" field
2) the wording for the checkbox. These characters are not "brackets"
3) Autoclosing quotes should not be a default, nevermind a hidden default. It
is counterproductive and annoying whenever you need to add quotes to existing
text, write an appostrophe etc, which for me is OFTEN.
STEPS TO REPRODUCE
1. Do not have " or ' in the "Enclosing characters" field
2. Check the box for "Automatically close brackets when opening bracket is
typed"
3. Type a " and observe how it is automatically closed.
4. Uncheck the box for "Automatically close brackets when opening bracket is
typed"
3. Type a " and observe how it is no longer automatically closed.
OBSERVED RESULT
" and ' are automatically closed or not according to the "Automatically close
brackets when opening bracket is typed" checkbox even if not in the "Enclosing
characters" field
EXPECTED RESULT
" and ' are automatically closed only when the "Automatically close brackets
when opening bracket is typed" checkbox even and included in "Enclosing
characters" field
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 466551] Increased CPU consumption in apps when you rapidly switch windows by scrolling on Task Manager widget
https://bugs.kde.org/show_bug.cgi?id=466551 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 --- Comment #27 from Eric S --- I still see it (using 5.27.8). Possibly less often / it takes longer to start occurring. I do have nvidia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 --- Comment #23 from Eric S --- Could any plasma developer comment as to whether what I said in my previous comment (#15) makes any sense? Tthat is, whether there is any sort of windowing resource which the system can "run out" of? The behavior I see effects not just windows but thing like menus and tool tips. Sometimes I just have to open and close a menu repeatedly to get it to paint, as if some of this resource which the system ran out of eventually got garbage collected (or something like that). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #15 from Eric S --- I think I'm seeing the same thing (openSUSE Tumbleweed), except that I can make the problem go away by closing a lot of things. Typically what I close to fix it, at least temporarily is Firefox. I am someone who tends to have a pathological number of browser tabs and windows open so this closes a lot. Sometimes I can make the problem go away for a shorter amount of time by closing some other large application instead. It feels to me as if there were some system resource like window handles or some such that gets exhausted, something that the system is not cleaning up for reuse quickly enough. I'm not saying it must be that, but that's the feel of the behavior. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447207] New: Touchpad config fails to save "Disable touchpad when typing"
https://bugs.kde.org/show_bug.cgi?id=447207 Bug ID: 447207 Summary: Touchpad config fails to save "Disable touchpad when typing" Product: systemsettings Version: 5.23.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: subscri...@blackbrook.org Target Milestone: --- SUMMARY If I change the state of this checkbox and click apply, then exit and reopen the config menu, the state of the checkbox is reverted to what it was before my change. Other config params in the touchpad config do save, like "Maximum time for double tap." It also fails to write the parameter "DisableOnKeyboardActivity" to ~/.config/touchpadrc, though it seems to read this parameter as the state of the checkbox reflects this being set "=true" or "=false". STEPS TO REPRODUCE 1. Open Input Devices in System Settings 2. Choose touchpad 3. Choose Enable/Disable Touchpad tab 4. Change state of Disable touchpad when typing checkbox 5. Click Apply 6. Close window 7. Reopen, following steps 1 - 3 again. OBSERVED RESULT The state of the checkbox has reverted to before the change made EXPECTED RESULT The checkbox state remains, and is reflected in a change to ~/.config/touchpadrc SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.4 (openSuse Tumbleweed) (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.
https://bugs.kde.org/show_bug.cgi?id=119539 --- Comment #63 from Eric S --- That problem in inherent to using any character for separating values. You just happen to be able to think of an example for "/" but there is no reason an artist, genre, etc could not have a comma in their name. In fact, here's one that occurred to me before finishing this comment. "Peter, Paul and Mary." But whether or not we can think of example for a character is irrelevant, it is always going to be potential for any character, and so the user will need a way to elect whether or not a given character is used that way, and a either way for a user to escape such characters in their metadata or a way to list exclusions, or some such solution. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 141991] custom metadata readout and creation (id3v2)
https://bugs.kde.org/show_bug.cgi?id=141991 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #13 from Eric S --- If this were implemented would the ability to search on such custom fields automatically come with it, or should that be another feature request? I'd love to be able to search by conductor. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.
https://bugs.kde.org/show_bug.cgi?id=119539 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #61 from Eric S --- Use of slash (/) is very common for separating multiple artist names also, e.g. "Alice / Bob" -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 424137] Crash after 2 failed attempts to resize
https://bugs.kde.org/show_bug.cgi?id=424137 --- Comment #4 from Eric S --- I did not have any USB drive inserted when any of this happened. Does it still make any sense as a duplicate of 413418? The drive containing the partitions I was working with was an internal hard disk (there was also an internal SSD drive). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 424137] Crash after 2 failed attempts to resize
https://bugs.kde.org/show_bug.cgi?id=424137 --- Comment #3 from Eric S --- I think now what may have been the trigger: udisksd was remounting the drive in response to seeing the changes (the sfdisk command was succeeding...when the resizefs2 command then failed another sfdisk command was run to revert the change--bravo to partion manager for that, btw!) At first I thought this was the cause of resizefs2 failing but no, I watched it and the remount didn't occur until after the whole sequence. I was actually getting a prompt for the sudo equivalent (which originally I mistook for a partition manager action) for the mount, and if I cancel that prompt to prevent the mount, partition manager doesn't crash. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #16 from Eric S --- Could it be udisks2 automounting the partition? Check journalctl... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 424137] Crash after 2 failed attempts to resize
https://bugs.kde.org/show_bug.cgi?id=424137 --- Comment #1 from Eric S --- I tried the resize again after restarting partition manager and got the crash again. I unmounted the partition, tried to resize it, and again the resize failed. This time I'm pretty sure the crash is initated me performing an select All and then Alt-C on the messages in the details window. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 424137] New: Crash after 2 failed attempts to resize
https://bugs.kde.org/show_bug.cgi?id=424137 Bug ID: 424137 Summary: Crash after 2 failed attempts to resize Product: partitionmanager Version: 4.1.0 Platform: Chakra OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: subscri...@blackbrook.org Target Milestone: --- Application: partitionmanager (4.1.0) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 5.2.11-3-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: - What I was doing when the application crashed: Crashed after attempting to resize (grow) a partition...for the second time. The order of events: I tried to unmount the partion in question (call it partition X). It failed without telling me why. I copied the umount command from the message window and ran it in terminal and from the error message, deduced what was preventuing the umount, corrected it, and ran the umount from the terminal. Back in partition manager I then deleted partion Y to create space to grow X. Then I resized X to increase it (not using all of the free space from Y). When I applied it gave me an error on the resize, though the deletion Y was successful. At this point I saw that X was still showing as mounted in partion manager (did it remount it? or did it just no know it was umounted because I did so from the terminal?) So I tried the resize again, getting an error yet again. This time, it crashed...but not until after I had copied the error message (and perhaps closed the message window). -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd37935d00 (LWP 21625))] Thread 8 (Thread 0x7fcd209fd700 (LWP 21860)): #0 0x7fcd3edb1a64 in read () at /usr/lib/libc.so.6 #1 0x7fcd2dc5dfb1 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #2 0x7fcd2e2ed33e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fcd2e2eddb0 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fcd2e2ede70 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fcd2e2fbcd9 in () at /usr/lib/libpulse.so.0 #6 0x7fcd2dc8d088 in () at /usr/lib/pulseaudio/libpulsecommon-11.1.so #7 0x7fcd3d8f0580 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd3edc0a83 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fcd216dd700 (LWP 21633)): #0 0x7fcd3edb5eb1 in poll () at /usr/lib/libc.so.6 #1 0x7fcd3bca157e in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd3bca2562 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd2239c9a6 in () at /usr/lib/libgio-2.0.so.0 #4 0x7fcd3bc6b745 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fcd3d8f0580 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fcd3edc0a83 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcd21ede700 (LWP 21632)): #0 0x7fcd3edb1a64 in read () at /usr/lib/libc.so.6 #1 0x7fcd3bc51180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd3bca013f in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd3bca1520 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fcd3bca164c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fcd3bca1691 in () at /usr/lib/libglib-2.0.so.0 #6 0x7fcd3bc6b745 in () at /usr/lib/libglib-2.0.so.0 #7 0x7fcd3d8f0580 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd3edc0a83 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcd23398700 (LWP 21631)): #0 0x7fcd3edb5eb1 in poll () at /usr/lib/libc.so.6 #1 0x7fcd3bca157e in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd3bca164c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd3f2fa064 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcd3f2a353c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcd40a36e30 in () at /usr/lib/libkpmcore.so.9 #6 0x7fcd3f0ddfdc in () at /usr/lib/libQt5Core.so.5 #7 0x7fcd3d8f0580 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fcd3edc0a83 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fcd23b99700 (LWP 21630)): #0 0x7fcd3d8f667c in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd24094b2b in () at /usr/lib/dri/i965_dri.so #2 0x7fcd24094757 in () at /usr/lib/dri/i965_dri.so #3 0x7fcd3d8f0580 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcd3edc0a83 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fcd2cc58700 (LWP 21629)): #0 0x7fcd3edb5eb1 in poll () at /usr/lib/libc.so.6 #1 0x7fcd3bca157e in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd3bca164c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420140] Expand Application Launcher menu to fit more entries on screen when there is room
https://bugs.kde.org/show_bug.cgi?id=420140 Eric S changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from Eric S --- No! This is NOT a duplicate of 332512. That issue is about being able to manually resize the menu. This issue is about having it autoresize sensibly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420140] New: Expand Application Launcher menu to fit more entries on screen when there is room
https://bugs.kde.org/show_bug.cgi?id=420140 Bug ID: 420140 Summary: Expand Application Launcher menu to fit more entries on screen when there is room Product: plasmashell Version: 5.18.4 Platform: Chakra OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: subscri...@blackbrook.org CC: plasma-b...@kde.org Target Milestone: 1.0 By default, the popup menu uses maybe half of the screen height. If you have more favorites than fit in this area, you are forced to scroll the menu to find them. This is a little frustrating where there is plenty of room on the screen to display them all. It seems to me there is no advantage to not using the available space. It should expand menu upwards until either the screen edge is reached or there is no longer a scrollbar required. There used to be a workaround in the ability to resize this menu. This ability seems to have been lost, but really it should not need to be customized by the user, the optimal size is what I have described above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357136] Can't configure Application Launcher Menu to work well in positions other than bottom left of screen
https://bugs.kde.org/show_bug.cgi?id=357136 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #10 from Eric S --- Agreed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 274102] Automatically backup new unnamed/unsaved notes/files
https://bugs.kde.org/show_bug.cgi?id=274102 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #9 from Eric S --- (In reply to Mathieu Jobin from comment #8) > I believe kate could handle this better. > > my brain knows about the bug and work around it, but most users will get > bitten by this. > > when opening a new file, a temporary backup needs to be created to prevent > dataloss I agree. And I think "avoid dataloss" should be every programmers #1 value / priority. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356482] crash on closing help window
https://bugs.kde.org/show_bug.cgi?id=356482 Eric S changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Eric S --- I can't recreate this anymore, though I'm no longer sure what I meant by a "help window I'd opened from Konsole" but none of the windows I can open from the Help menu cause a crash for me when I close them. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 380296] New: crash when commiting delete then new partation on removable media after removal and re-attaching
https://bugs.kde.org/show_bug.cgi?id=380296 Bug ID: 380296 Summary: crash when commiting delete then new partation on removable media after removal and re-attaching Product: partitionmanager Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: subscri...@blackbrook.org Target Milestone: --- Application: partitionmanager (3.0.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.8.6-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: - What I was doing when the application crashed: I unmounted a partition on removable media (SD drive) then deleted a partition then added a new partion then I ejected the media (having forgotten to "Apply") I reinserted the media, and hit apply. Clearly this was wrong, but partition manager should not crash. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f32433b9d00 (LWP 18520))] Thread 3 (Thread 0x7f321fc3c700 (LWP 18798)): #0 0x7f323f5b9dbd in read () from /usr/lib/libc.so.6 #1 0x7f322b072191 in pa_read () from /usr/lib/pulseaudio/libpulsecommon-9.0.so #2 0x7f322b702a1e in pa_mainloop_prepare () from /usr/lib/libpulse.so.0 #3 0x7f322b703490 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0 #4 0x7f322b703550 in pa_mainloop_run () from /usr/lib/libpulse.so.0 #5 0x7f322b711799 in ?? () from /usr/lib/libpulse.so.0 #6 0x7f322b0a1a28 in ?? () from /usr/lib/pulseaudio/libpulsecommon-9.0.so #7 0x7f323c625444 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f323f5c71af in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f3228f6b700 (LWP 18522)): #0 0x7f323f5b in poll () from /usr/lib/libc.so.6 #1 0x7f3238f431e5 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f3238f43322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f323fedaf2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f323fe855da in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f323fca99a4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f323e16ca25 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f323fcae568 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f323c625444 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f323f5c71af in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f32433b9d00 (LWP 18520)): [KCrash Handler] #4 0x7f3242f1510b in PartWidget::paintEvent(QPaintEvent*) () from /usr/lib/libkpmcore.so.4 #5 0x7f32407b9d48 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #6 0x7f32407729bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #7 0x7f324077a3e6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7f323fe87188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #9 0x7f32407b2b7a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/libQt5Widgets.so.5 #10 0x7f32407b31c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #11 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7f32407b3d79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7f32407b2d31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f32407b3d79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f32407b2d31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f32407b3d79
[filelight] [Bug 370932] File light scans into "do not scan" folders that end with a /
https://bugs.kde.org/show_bug.cgi?id=370932 Eric S changed: What|Removed |Added Summary|File light scans into "do |File light scans into "do |not scan" folders |not scan" folders that end ||with a / -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 370932] File light scans into "do not scan" folders
https://bugs.kde.org/show_bug.cgi?id=370932 --- Comment #1 from Eric S --- Actually I just discovered the problem. All the folders listed in my Do not scan list ended with a /. E.g. /home/ericjs/stuff/. I tried deleting and re-adding a folder, and it was added without a terminating /, like "/home/ericjs/stuff". Rescanning resulted in this directory properly being ignored. I'm pretty sure these folders had a terminating / because that is how a previous version of Filelight created them (I certainly wouldn't have added such a slash myself). So this would seem to be a backwards compatibility issue. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 370932] New: File light scans into "do not scan" folders
https://bugs.kde.org/show_bug.cgi?id=370932 Bug ID: 370932 Summary: File light scans into "do not scan" folders Product: filelight Version: 1.21 Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: subscri...@blackbrook.org Folders that I have listed in "Do not scan these folders:" in the configuration show up in my scan. Reproducible: Always I'm pretty sure this used to work. I can't tell you what version as I haven't run it in a while. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 335079] Text rendering broken for unicode characters
https://bugs.kde.org/show_bug.cgi?id=335079 --- Comment #24 from Eric S --- Isn't the underlying problem here the painting of text using an opaque background? Wouldn't it be better painting it with a transparent background (mask or such)? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353404] My kate version is not listed in the possible versions.
https://bugs.kde.org/show_bug.cgi?id=353404 --- Comment #3 from Eric S --- Forgive me if I'm reading too much into that replybut is there an implied "...therefore we don't / won't do it?" Isn't updating the bug tracking system with the new version simply a standard part of the release process? Isn't it among the most basic things developers should do to maintain the most basic level of professionalism? Or is this bug system deprecated and some other one meant to be used for Kate? Or is Kate essentially an unmaintained project? I'm really struggling to make sense of this... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353404] My kate version is not listed in the possible versions.
https://bugs.kde.org/show_bug.cgi?id=353404 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #1 from Eric S --- I just noticed the same thing. This seems to be very much a WTF kind of thing and was reported 6 months ago. Is it too much to expect someone to reply to this? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362271] New: Font Horizontal space rendering is incorrect
https://bugs.kde.org/show_bug.cgi?id=362271 Bug ID: 362271 Summary: Font Horizontal space rendering is incorrect Product: kate Version: 3.14.3 Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: subscri...@blackbrook.org If I change the font preference to use a compressed font (like Open Sans Condensed) and compare vs the regular version of the font (like Open Sans), the compressed version appears spaced out WIDER than the normal. The little font preview window does it correctly, but when you actually apply it to the editing window you get this inverse-compression effect. You can see this most dramatically with a set of fonts like Input Mono (http://input.fontbureau.com/) which has several different levels of compression, and Kate renders them all in inverse proportion to how they should be. I know this sounds bizarre, but I get this happening consistently for several fonts, and only Kate does this wrong, other applications do it correctly. BTW the version my Kate reports bear no resemblance to anything I'm offered in the version dropdown here. It reports: Version 15.12.3 Using: KDE Frameworks 5.21.0 Qt 5.6.0 (built against 5.6.0) The xcb windowing system Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #7 from Eric S --- I should note that this is a laptop with a 1600 x 900 screen, and I often use it with an external 1920x1200 monitor. It looks similar on either screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #5 from Eric S --- Created attachment 98379 --> https://bugs.kde.org/attachment.cgi?id=98379&action=edit Here is what my screen looks like; 1920 x 1200 screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #4 from Eric S --- Also I disagree that the "Huh, where did my window go?" use case is one that justifies something that will be in the screen at all times (and certainly not as something you cannot disable and is on by default). If you have icon grouping enabled, having multiple windows grouped (not hidden) under the icon is routine...no one is going to have much more than a fleeting single "Huh, where did my window go?" experience when they are a completely new to it. It adds unnecessary clutter for the majority of cases for a single edge case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #3 from Eric S --- My panel is not that tiny. And believe me, my eyes are not that great, I'm not someone who has his screen with everything set really fine. I suspect there is some additional element of screen geometry or something at play. I'll see if there are any specific numbers I can report about my configuration. If you have any suggestions where to get some useful numbers, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361567] task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 --- Comment #1 from Eric S --- It would be wonderful if there were some way to simply turn off this feature. This is a new feature that, in my opinion, is really not in any way useful, even if it worked properly. One only looks at the Task bar if one is about to use it, and by using it immediately finds out how many windows the icon is grouping. Knowing ahead of that click is not really of any benefit that I can see. I really cannot imagine a case where I would glance at the bar to find out how many windows an application has open. And if there is such a use case it is rare enough that it does not warrant having this icon present all the time. So actually a good fix for this would be to simply remove this feature entirely. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames
https://bugs.kde.org/show_bug.cgi?id=269370 --- Comment #11 from Eric S --- (In reply to Eric S from comment #10) > I'm going to open(In reply to Jan Dosoudil from comment #9) > > (In reply to Eric S from comment #7) > > > I find there are other problems with beyond-ASCII characters in dolphin > > > over > > > fish. I have a file with the registered trademark symbol in the name (®). > > > It > > > appears correctly in dolphin over fish, however I cannot open in Dolphin, > > > nor can I copy it from dolphin. It does not matter if I explicitly Select > > > UTF-8 as the remote charset. > > > > > > Note that this worked fine with the version of Dolphin under plasma 4. > > > > I have exactly same problem -- files with Czech characters (UTF-8 encoding) > > doesn't open in Dolphin 5.x over fish. > > I'm going to open another issue for this. I'm guessing this is not being > seen because it is v4.9.4 issue. Actually, there are no 5.x version offered for kio when reporting a bug here. WTF? Is the system just out of date or kio considered part of some other component now in Plasma 5? Also I'm not sure this issue (at least going by the title) is the right one for my and Jan Dosoudil's problem, that fish: cannot open, copy, rename, etc files with non-latin characters in their name. Searching in the bug system for characters under kio there are a whole host of problems with characters beyond ascii but the bugs all seem to be specific in ways that don't necessarily encompass this problem. So I still suspect we need to file another bug, but it's not entirely clear where. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames
https://bugs.kde.org/show_bug.cgi?id=269370 --- Comment #10 from Eric S --- I'm going to open(In reply to Jan Dosoudil from comment #9) > (In reply to Eric S from comment #7) > > I find there are other problems with beyond-ASCII characters in dolphin over > > fish. I have a file with the registered trademark symbol in the name (®). It > > appears correctly in dolphin over fish, however I cannot open in Dolphin, > > nor can I copy it from dolphin. It does not matter if I explicitly Select > > UTF-8 as the remote charset. > > > > Note that this worked fine with the version of Dolphin under plasma 4. > > I have exactly same problem -- files with Czech characters (UTF-8 encoding) > doesn't open in Dolphin 5.x over fish. I'm going to open another issue for this. I'm guessing this is not being seen because it is v4.9.4 issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361567] New: task bar icon for multiple window grouping obscures application icons
https://bugs.kde.org/show_bug.cgi?id=361567 Bug ID: 361567 Summary: task bar icon for multiple window grouping obscures application icons Product: Breeze Version: 5.6.1 Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: subscri...@blackbrook.org CC: kain...@gmail.com Task bar Icon indicating more than one window is being groups almost entirely obscures the application icon. With the current version I find only a tiny sliver of the app icon is visible, which is a big impediment to useabilty. See also this discussion: https://forum.kde.org/viewtopic.php?f=17&t=130682 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348514] Device Notifier missing KDE 4 actions
https://bugs.kde.org/show_bug.cgi?id=348514 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #1 from Eric S --- Maybe this is distro-specific but all my actions from kde4 are in /usr/share/apps/solid/actions. It seems to me one solution or workaround might be distros handled this. KDE ought to highlight the need for this to the distros in some info prominently provided to them when they get the Plasma 5 sources. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357726] volume indicator and wifi quality are too hard to read
https://bugs.kde.org/show_bug.cgi?id=357726 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #1 from Eric S --- I second this! And it is still the case with 5.5.3. This flaw does falls out of the decision to make such icons monochrome in breeze. I'm not fond of that at all. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead
https://bugs.kde.org/show_bug.cgi?id=310156 --- Comment #10 from Eric S --- Oops, nevermind, there already is a Plasma 5 version of this: 348043 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #14 from Eric S --- This is still the case in Plasma 5.5.3. Shouldn't someone update the version? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead
https://bugs.kde.org/show_bug.cgi?id=310156 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #9 from Eric S --- Still happening in Plasma 5.5.3. Btw this seems to have been fixed in Plasma 4...it worked properly in the last several versions I'd used. Could someone update the product and version fields to reflect that? Or does this need to be refiled for Plamsa 5? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 --- Comment #9 from Eric S --- Also, it's frustrating not to be able to vote for this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #8 from Eric S --- "Erratic" is putting it nicely. How about "fundementally broken." -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 349266] System hang when put to sleep
https://bugs.kde.org/show_bug.cgi?id=349266 --- Comment #7 from Eric S --- Having "Component: general, Version: unspecified" isn't a great way to get anyone's attention. I know you're not using Arch, but have a look at this thread where someone had similar symptoms. It might give you some ideas on how to diagnose the problem. https://bbs.archlinux.org/viewtopic.php?id=185731 This may not even be a KDE issue, you might have better luck starting in your distro's forums. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #41 from Eric S --- I'd like to suggest that as far as the Application Launcher window goes, it seems to me it would make the most sense if this window just expanded vertically until it either did not need a scrollbar or has reached the height of the desktop. This would be better than making it resizeable. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356762] New: crash while selecting files using mouse drag
https://bugs.kde.org/show_bug.cgi?id=356762 Bug ID: 356762 Summary: crash while selecting files using mouse drag Product: dolphin Version: 15.08.3 Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: subscri...@blackbrook.org Application: dolphin (15.08.3) Qt Version: 5.5.1 Operating System: Linux 4.2.6-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: It crashes when I select file with a mouse drag. In this case the file are not in the top level folder of the view (i.e. it shows a tree, and these files a few levels down) and in the course of the drag I cause the window to scroll. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f08a47800 (LWP 18156))] Thread 3 (Thread 0x7f5ef33e5700 (LWP 18157)): #0 0x7f5f0845b18d in poll () from /usr/lib/libc.so.6 #1 0x7f5efd1bbae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f5efd1bd757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f5ef4b04329 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f5f0846412d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5eebf53700 (LWP 18158)): #0 0x7f5f084706af in __libc_enable_asynccancel () from /usr/lib/libc.so.6 #1 0x7f5f0845b182 in poll () from /usr/lib/libc.so.6 #2 0x7f5efd6a9ca4 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f5efd6a9dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f5f034885ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f5f0342f5ba in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f5f0324bbd4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f5f03250b7e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f5f0130a464 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f5f0846412d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5f08a47800 (LWP 18156)): [KCrash Handler] #6 0x7f5efab4c2b9 in mdb_txn_abort () from /usr/lib/liblmdb.so #7 0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #8 0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #9 0x7f5efab4c2c7 in mdb_txn_abort () from /usr/lib/liblmdb.so #10 0x7f5eff5bca37 in Baloo::Database::open(Baloo::Database::OpenMode) () from /usr/lib/libKF5BalooEngine.so.5 #11 0x7f5f05ace576 in Baloo::File::load() () from /usr/lib/libKF5Baloo.so.5 #12 0x7f5f06069e96 in ?? () from /usr/lib/libKF5BalooWidgets.so.5 #13 0x7f5f03461231 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x7f5f03d2298c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f5f03d27e66 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f5f03431beb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x7f5f03433fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #18 0x7f5f03488183 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7f5efd6a9a1d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x7f5efd6a9d08 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x7f5efd6a9dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #22 0x7f5f0348858f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7f5f0342f5ba in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #24 0x7f5f0343757c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #25 0x7f5f0877d0c4 in kdemain () from /usr/lib/libkdeinit5_dolphin.so #26 0x7f5f0839b610 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x00400789 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #32 from Eric S --- I'd just like to comment that while many of Blackpaw's bitter comments are very unconstructive, they do reflect the fact that a certain amount of community good will does gets burned away when a "reboot" like Plasma 5 or KDE 4 happen, and it's probably worth thinking about ways to ameliorate that (much bigger discussion than belongs here). Personally I only have tinges of irritation about the backward steps taken in Plasma 5, but Eike's comments actually make me feel better, as showing that the KDE devs really do care. Thanks, Eike, for your calm and well considered responses here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 334923] Kicker menu not correctly resizing
https://bugs.kde.org/show_bug.cgi?id=334923 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #11 from Eric S --- I'd just like to suggest that talking about this stuff in terms of kickoff, kicker, etc isn't friendly to general users of Plasma. Plasma does not present these names to the user. Plasma presents them as "Application Launcher" etc. I have enough history with KDE to have some idea of what is being talked about but frankly I can never remember the difference between the similarly named kickoff and kicker. A new user would no idea. I'd like to suggest that the names used in the issue system and discussions be harmonized with the terminology used by the user interface. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356482] New: crash on closing help window
https://bugs.kde.org/show_bug.cgi?id=356482 Bug ID: 356482 Summary: crash on closing help window Product: konsole Version: 15.08.0 Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: subscri...@blackbrook.org Application: konsole (15.08.0) Qt Version: 5.5.1 Operating System: Linux 4.2.6-1-CHAKRA x86_64 Distribution: "Chakra" -- Information about the crash: closed help window I'd opened from Konsole and Konsole crashed. Tried to suggest this a possibly tied to 352099 but "Suggest this crash is related" button that Ui apparently doesn't work either. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x7fc032c3846f in QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from /usr/lib/libQt5XcbQpa.so.5 #7 0x7fc032c235fb in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/libQt5XcbQpa.so.5 #8 0x7fc032c23b23 in QXcbConnection::processXcbEvents() () from /usr/lib/libQt5XcbQpa.so.5 #9 0x7fc0425c5231 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7fc042e8698c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #11 0x7fc042e8be66 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7fc042595beb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7fc042597fe6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #14 0x7fc0425ec183 in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7fc03c473a1d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x7fc03c473d08 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x7fc03c473dbc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x7fc0425ec58f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #19 0x7fc0425935ba in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #20 0x7fc04259b57c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #21 0x7fc045cd929b in kdemain () from /usr/lib/libkdeinit5_konsole.so #22 0x7fc045934610 in __libc_start_main () from /usr/lib/libc.so.6 #23 0x00400789 in _start () Possible duplicates by query: bug 356252, bug 355764, bug 355612, bug 355221, bug 353605. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 --- Comment #31 from Eric S --- Could someone please change the Product to plasmashell on this issue since people are confirming this as existing (or even worse) in Plasma 5? Or do we need to open a new issue? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup
https://bugs.kde.org/show_bug.cgi?id=323230 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #30 from Eric S --- > I have the same exact problem with kde5 with manjaro, dual monitor. Never had > something > similar while using kde4... Ditto here, with Chakra. Wasn't a problem with Plasma 4. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 349266] System hang when put to sleep
https://bugs.kde.org/show_bug.cgi?id=349266 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #4 from Eric S --- I see something like this sometimes. It may have something to do with processes running in a console (Konsole). With Plasma4 I could sleep the system with processes running in console windows with no problem. Now, I think it prompts me to kills them. I've believe I've have this happen in conjunction with multi-monitor issues such that I never see the prompt issues. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 269370] ftp network folder in dolphin does not honor codepage for filenames
https://bugs.kde.org/show_bug.cgi?id=269370 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #7 from Eric S --- I find there are other problems with beyond-ASCII characters in dolphin over fish. I have a file with the registered trademark symbol in the name (®). It appears correctly in dolphin over fish, however I cannot open in Dolphin, nor can I copy it from dolphin. It does not matter if I explicitly Select UTF-8 as the remote charset. Note that this worked fine with the version of Dolphin under plasma 4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356353] New: launcher window should be resizable
https://bugs.kde.org/show_bug.cgi?id=356353 Bug ID: 356353 Summary: launcher window should be resizable Product: plasmashell Version: 5.4.3 Platform: Chakra OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: subscri...@blackbrook.org CC: plasma-b...@kde.org Unless I'm missing the obvious again (https://bugs.kde.org/show_bug.cgi?id=336522) there is no way to make the height of the launcher window bigger. Currently for me, it is less than the height of my screen and does not hold all of my favorites, and so requires using the scrollbar and is less handy. It was resizeable in plasma 4 but if there is a way to resize it I cannot for the life of me find it. If there IS a way, it should be made more obvious. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
