[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Kristopher Ives changed: What|Removed |Added CC|kristopher.i...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Kristopher Ives changed: What|Removed |Added Summary|Blur effect applied for |Blur effect applied to |aurorae decoration shadows |decoration shadows -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418276] Support for round corners
https://bugs.kde.org/show_bug.cgi?id=418276 Kristopher Ives changed: What|Removed |Added CC||kristopher.i...@gmail.com --- Comment #7 from Kristopher Ives --- We've had this bug and discussions on how to resolve it or workaround it for a few years now: https://bugs.kde.org/show_bug.cgi?id=395725 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 --- Comment #35 from Kristopher Ives --- Where would be the right place to make this kind of change? My proposal would require modifying KDecoration2::Decoration, is that something that can happen? Vlad, do you have any suggestions? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416170] Optional feature to Minimize Elisa to the system tray
https://bugs.kde.org/show_bug.cgi?id=416170 --- Comment #2 from Kristopher Ives --- I agree people have different window manager preferences. I also agree it should be an entirely optional feature disabled by default. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416170] New: Minimize Elisa to system tray / notification tray
https://bugs.kde.org/show_bug.cgi?id=416170 Bug ID: 416170 Summary: Minimize Elisa to system tray / notification tray Product: elisa Version: 19.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: kristopher.i...@gmail.com Target Milestone: --- SUMMARY It would be nice to be able to minimize Elisa to the system tray / notification tray area. STEPS TO REPRODUCE 1. Open Elisa 2. Play a track 3. Close the Elisa window OBSERVED RESULT Playback stops and Elisa is gone. EXPECTED RESULT Playback could continue and Elisa could be in the system tray / notification tray area. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Kernel Version: 4.15.0-74-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 --- Comment #2 from Kristopher Ives --- Thanks. Is there a way to get the latest Krita as a PPA? I would really like to keep using the package manager version instead of AppImage. The PPA I found was: https://launchpad.net/~kritalime/+archive/ubuntu/ppa But it seems to only be 4.2.8? Thank you again for the help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] New: Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 Bug ID: 415996 Summary: Krita crashes when exiting Product: krita Version: 4.2.8 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- Created attachment 124967 --> https://bugs.kde.org/attachment.cgi?id=124967&action=edit Backtrace of crash SUMMARY STEPS TO REPRODUCE 1. Open Krita 2. Resize a Photo 3. Save 4. Close Photo 5. Close Krita OBSERVED RESULT File is saved correctly but as closing Krita crashes and the system crash handler appears. EXPECTED RESULT Krita should just close without crashing. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 4.15.0-74-generic OS Type: 64-bit ADDITIONAL INFORMATION Global menu is being used, kde-hello theme is being used, applet-window-buttons is being used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413141] New: Plasma crashes when booting 5.17
https://bugs.kde.org/show_bug.cgi?id=413141 Bug ID: 413141 Summary: Plasma crashes when booting 5.17 Product: plasmashell Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kristopher.i...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Booting with nothing running yet and Plasma crashes. After booting the KDE Crash Handler appears but Plasma appears to function normally. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f799ab06800 (LWP 1238))] Thread 5 (Thread 0x7f796fa92700 (LWP 1356)): #0 0x7f79918759f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557a5a2652f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x557a5a2652a8, cond=0x557a5a2652d0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x557a5a2652d0, mutex=0x557a5a2652a8) at pthread_cond_wait.c:655 #3 0x7f7974fa02cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f7974f9fff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f799186f6db in start_thread (arg=0x7f796fa92700) at pthread_create.c:463 #6 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f797d6ac700 (LWP 1310)): #0 0x7f79942290b4 in __GI___libc_read (fd=18, buf=0x7f797d6abb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f798e1ab2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f798e1660b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f798e166570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f798e1666dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7994b809db in QEventDispatcherGlib::processEvents (this=0x7f797b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f7994b20eaa in QEventLoop::exec (this=this@entry=0x7f797d6abd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f799493c3ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f799840acb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f799493db72 in QThreadPrivate::start (arg=0x557a5a297170) at thread/qthread_unix.cpp:360 #10 0x7f799186f6db in start_thread (arg=0x7f797d6ac700) at pthread_create.c:463 #11 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f797f734700 (LWP 1250)): #0 0x7f799422dbf9 in __GI___poll (fds=0x7f7978004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f798e1665c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f798e1666dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7994b809db in QEventDispatcherGlib::processEvents (this=0x7f7978000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f7994b20eaa in QEventLoop::exec (this=this@entry=0x7f797f733d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f799493c3ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f7995c340e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f799493db72 in QThreadPrivate::start (arg=0x7f7995eabd80) at thread/qthread_unix.cpp:360 #8 0x7f799186f6db in start_thread (arg=0x7f797f734700) at pthread_create.c:463 #9 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f7985972700 (LWP 1241)): #0 0x7f799422dbf9 in __GI___poll (fds=0x7f7985971ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f799953a747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f799953c36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7988343f00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f799493db72 in QThreadPrivate::start (arg=0x557a5a049060) at thread/qthread_unix.cpp:360 #5 0x7f799186f6db in start_thread (arg=0x7f7985972700) at pthread_create.c:463 #6 0x7f799423a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f799ab06800 (LWP 1238)): [KCrash Handler] #6 0x7f7994ae9dc0 in QSortFilterProxyModelPrivate::build_source_to_proxy_mapping (proxy_to_source=..., source_to_proxy=..., this=0x557a5a6
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725
--- Comment #23 from Kristopher Ives ---
After some debugging it seems the easiest way to move forward past these
problems would be to add support in KDecoration2::Decoration so that it can
calculate the shape of a window. Then these lines could be modified in the blur
plugin to have an additional mask afterwards:
https://github.com/KDE/kwin/blob/e8fe3f2fb7195fe562a073d1a78eb05d74670cfd/effects/blur/blur.cpp#L389-L413
Basically, it would end up having something like this near the end of it:
if (AbstractClient *c = dynamic_cast< AbstractClient * > (toplevel)) {
if (KDecoration2::Decoration *d = c->decoration()) {
if (d->hasWindowShape()) {
region &= d->windowShape(w);
}
}
}
"hasWindowShape" and "windowShape" are just example names, but would be the new
methods added to KDecoration2::Decoration. The default implementation would be
for hasWindowShape() to return false and the default implementation for
windowshape() would be to return the rectangle of the window. However, a
decoration could opt to return a QRegion from windowShape() that better
describes the shape of the window with it's decorations - such as a rectangle
with rounded corners.
If this can already be done with the existing KWin frameworks I am interested
to know how.
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 412875] Kwin crashes when using Zoom effect
https://bugs.kde.org/show_bug.cgi?id=412875 --- Comment #2 from Kristopher Ives --- Thank you David. Sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412875] New: Kwin crashes when using Zoom effect
https://bugs.kde.org/show_bug.cgi?id=412875 Bug ID: 412875 Summary: Kwin crashes when using Zoom effect Product: kwin Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.15.0-65-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Using the Zoom plugin. KWin crashed after I zoomed out and alt tabbed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff473293d00 (LWP 1227))] Thread 7 (Thread 0x7ff43ac4e700 (LWP 2956)): #0 0x7ff46bb499f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55908e0dbf10) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff46bb499f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55908e0dbec0, cond=0x55908e0dbee8) at pthread_cond_wait.c:502 #2 0x7ff46bb499f3 in __pthread_cond_wait (cond=0x55908e0dbee8, mutex=0x55908e0dbec0) at pthread_cond_wait.c:655 #3 0x7ff46fefcb0b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff46fefce19 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff46acd3ec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff46acd42fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff46fef5b72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff46bb436db in start_thread (arg=0x7ff43ac4e700) at pthread_create.c:463 #9 0x7ff472bf988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7ff43a44d700 (LWP 1362)): #0 0x7ff46bb499f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ff46f101fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff46bb499f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7ff46f101f68, cond=0x7ff46f101f90) at pthread_cond_wait.c:502 #2 0x7ff46bb499f3 in __pthread_cond_wait (cond=0x7ff46f101f90, mutex=0x7ff46f101f68) at pthread_cond_wait.c:655 #3 0x7ff46ee0c874 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7ff46ee0c8b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7ff46bb436db in start_thread (arg=0x7ff43a44d700) at pthread_create.c:463 #6 0x7ff472bf988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7ff4408e4700 (LWP 1355)): #0 0x7ff46bb499f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55908da56d6c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff46bb499f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55908da56d18, cond=0x55908da56d40) at pthread_cond_wait.c:502 #2 0x7ff46bb499f3 in __pthread_cond_wait (cond=0x55908da56d40, mutex=0x55908da56d18) at pthread_cond_wait.c:655 #3 0x7ff4414b62cb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7ff4414b5ff7 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7ff46bb436db in start_thread (arg=0x7ff4408e4700) at pthread_create.c:463 #6 0x7ff472bf988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff4510f1700 (LWP 1340)): #0 0x7ff472beccf6 in __GI_ppoll (fds=0x7ff448000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7ff4701346e1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff470135e78 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff4700d8eaa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff46fef43ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff46a54ecb5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7ff46fef5b72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff46bb436db in start_thread (arg=0x7ff4510f1700) at pthread_create.c:463 #8 0x7ff472bf988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff453bf0700 (LWP 1274)): #0 0x7ff472beccf6 in __GI_ppoll (fds=0x7ff44c00b8d8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7ff4701346e1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff470135e78 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff4700d8e
[neon] [Bug 410779] Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink
https://bugs.kde.org/show_bug.cgi?id=410779 --- Comment #3 from Kristopher Ives --- Thanks for reminding me. I have released it under the MIT license. Please let me know if there is anything else I can do to help. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 410779] New: Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink
https://bugs.kde.org/show_bug.cgi?id=410779 Bug ID: 410779 Summary: Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink Product: neon Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: kristopher.i...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Sometimes downloading the latest KDE Neon release image (ISO) can be slow as well as unreliable. Download speeds can range in 200KB/s range and sometimes after waiting for 30 minutes the download simply fails, even when the client-side has a network connection that can easily handle 15MB/s. STEPS TO REPRODUCE 1. Go to neon.kde.org 2. Download an ISO image OBSERVED RESULT Download is slow and sometimes fails. Since most users download via web browsers the failed downloads often cannot be resumed without additional workarounds. EXPECTED RESULT A 1.4GB download shouldn't take that long and shouldn't be a bottleneck to setting up KDE Neon for the first time. ADDITIONAL INFORMATION The current proposed solution on neon.kde.org is to use Metalink files as one is generated for every file that is mirrored. However, Metalink isn't well adopted so most users don't know how to use the files and the software availability for some platforms may be scarce. The metalink files themselves do contain enough information in them to generate .torrent files that don't require any additional infrastructure. This means users can use their BitTorrent clients to download KDE Neon and the files will get pulled from the mirror servers via HTTP while also allowing any peers to seed to each other potentially reducing the bandwidth footprint on the mirrors. I created a Python tool that converts .meta4 files into .torrent files with web seeds that shows how this can be done. An example of this is also hosted at https://metalink.xyz to show it works. Please let me know what roadblocks exist in getting this functionality on neon.kde.org for downloads. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 410779] Slow or unreliable downloads of KDE Neon release images and lack of adoption of Metalink
https://bugs.kde.org/show_bug.cgi?id=410779 --- Comment #1 from Kristopher Ives --- metalink-to-torrent source code https://github.com/krisives/metalink-to-torrent/blob/master/generate-torrent.py -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied for aurorae decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Kristopher Ives changed: What|Removed |Added CC||kristopher.i...@gmail.com --- Comment #19 from Kristopher Ives --- Does anyone know a way to work around this bug or how it may be resolved? It affects SierraBreezeEnhanced among many other window decorations, https://github.com/kupiqu/SierraBreezeEnhanced/issues/24 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #48 from Kristopher Ives --- Running the sqlite3 delete command does "work" but it also removes ALL existing resource links for event he stuff I do want to keep. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #43 from Kristopher Ives --- Created attachment 118876 --> https://bugs.kde.org/attachment.cgi?id=118876&action=edit another ~/.config/kactivitymanagerdrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 --- Comment #44 from Kristopher Ives --- Created attachment 118877 --> https://bugs.kde.org/attachment.cgi?id=118877&action=edit another ~/.config/kactivitymanagerd-statsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Kristopher Ives changed: What|Removed |Added CC||kristopher.i...@gmail.com --- Comment #36 from Kristopher Ives --- Does anyone know how I can work around this until the bug is fixed? Like, which config file to edit so that Kate isn't shown in the list (I know this bug isn't specific to Kate) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402164] Ejecting a CD/DVD ROM immediately closes tray
https://bugs.kde.org/show_bug.cgi?id=402164 --- Comment #3 from Kristopher Ives --- Thanks Nate. The sysctl workaround solved the Redditor's problem. Any reason why this happens with KDE but not other distros? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402164] Ejecting a CD/DVD ROM immediately closes tray
https://bugs.kde.org/show_bug.cgi?id=402164 --- Comment #1 from Kristopher Ives --- Sorry I left out some details in the initial comment, here they are from the OP: KDE neon: 5.14 KDE Plasma: 5.14.4 Frameworks: 5.53.0 Qt Ver: 5.11.2 Kernel: 4.15.0-42-generic -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402164] New: Ejecting a CD/DVD ROM immediately closes tray
https://bugs.kde.org/show_bug.cgi?id=402164 Bug ID: 402164 Summary: Ejecting a CD/DVD ROM immediately closes tray Product: frameworks-kio Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: kristopher.i...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Ejecting a CD/DVD drive causes it to open and immediately closes the tray as if something is repeatedly issuing a "close" command to the CD/DVD ROM drive. STEPS TO REPRODUCE 1. Press the Eject option in Dolphin or run the `eject` command OBSERVED RESULT Tray opens and then immediately closes. EXPECTED RESULT Tray should open and stay open long enough to take a disc out, usually automatically closed by the hardware itself or until the user presses the eject button again. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This started on /r/kde on Reddit via this discussion: https://www.reddit.com/r/kde/comments/a69sec/kde_doesnt_leave_my_cdrom_tray_open/ We observed that it does *not* happen if you exit KDE and run the `eject` command manually. It does happen if you run the `eject` command while inside a KDE session. Also does not happen in other non-KDE based distros such as Ubutnu 18.04 Sorry if the location of this bug is invalid it's hard to find the right place for such a bug in KDE. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401947] Empty Trash menu option no longer appears when right clicking a .desktop file
https://bugs.kde.org/show_bug.cgi?id=401947 --- Comment #5 from Kristopher Ives --- Thanks for the quick help guys. I notice this also seemed to fix a bug related to drag/drop uploads for sites like Imgur and GMail since I can't reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401947] Empty Trash menu option no longer appears when right clicking a .desktop file
https://bugs.kde.org/show_bug.cgi?id=401947 --- Comment #1 from Kristopher Ives --- Do you know a way I can compare all the changes that have happened for KDE Neon git-stable to git-unstable? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 401947] New: Empty Trash menu option no longer appears when right clicking a .desktop file
https://bugs.kde.org/show_bug.cgi?id=401947 Bug ID: 401947 Summary: Empty Trash menu option no longer appears when right clicking a .desktop file Product: frameworks-kio Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Trash Assignee: fa...@kde.org Reporter: kristopher.i...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When I open the context menu for a .desktop file that has URL=trash:/ I no longer see the option to "Empty Trash". I do see other options, including the option to "Move to Trash" which does not empty the trash (Image: https://i.imgur.com/nN2bB1u.png) This was working until a recent update to KDE Neon git-unstable. I tested in a VM and it appears that git-stable and earlier don't have this problem currently. STEPS TO REPRODUCE 1. Install KDE Neon git-unstable 2. Change your Desktop to Folder View 3. Drag from Dolphin the Trash to the desktop (creating a .desktop file with "URL=trash:/") 4. Right click the trash on the desktop OBSERVED RESULT No "Empty Trash" option will be visible. EXPECTED RESULT There should be a "Empty Trash" option. SOFTWARE/OS VERSIONS kio: 5.52.0+p18.04+gi KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION This was started as a Reddit thread: https://www.reddit.com/r/kde/comments/a3zgse/is_anyone_else_having_a_problem_where_the_trash/ If this is the wrong place to submit problems with git-unstable I understand and please be kind enough to point me in the right direction. Thank you for all your hard work on KDE. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398412] Discover crashes at startup with memory corruption ("corrupted size vs. prev_size")
https://bugs.kde.org/show_bug.cgi?id=398412 --- Comment #27 from Kristopher Ives --- Nate, May I ask which commit was reverted? I'm sorry if this information is easy to find in Phabricator I am still learning how to navigate it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398648] New: Magic Lamp minimize doesn't apply Blur
https://bugs.kde.org/show_bug.cgi?id=398648 Bug ID: 398648 Summary: Magic Lamp minimize doesn't apply Blur Product: kwin Version: 5.13.90 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- When using Magic Lamp minimize effect the Blur effect disappears during the animation in Konsole. How to reproduce bug: 1. Enable Magic Lamp minimize effect 2. Enable Blur desktop effect 3. Use Breeze with Blur option 4. Open Konsole 5. Minimize Konsole What happens: Blur goes away. What should happen: Blur should stay while the Magic Lamp minimize animation plays. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398602] New: Crash when launching after updating to 5.13.5
https://bugs.kde.org/show_bug.cgi?id=398602 Bug ID: 398602 Summary: Crash when launching after updating to 5.13.5 Product: Discover Version: 5.13.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- Discover was working and some time recently it began crashing when starting. My current version is 5.13.5 on KDE Neon developer version. --- QQmlComponent: Created graphical object was not placed in the graphics scene. qml: Warning: ToolbarApplicationHeader is deprecated, remove and use the automatic internal toolbar instead. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:258: TypeError: Cannot read property 'length' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:293: TypeError: Cannot read property 'length' of undefined file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/GlobalDrawer.qml:292: TypeError: Cannot read property 'length' of undefined corrupted size vs. prev_size KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 1606 KCrash: Arguments: /usr/bin/plasma-discover Alarm clock --- Please let me know if I can be of more help. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 397914] Picture of the Day doesn't change every day
https://bugs.kde.org/show_bug.cgi?id=397914 --- Comment #5 from Kristopher Ives --- Welp! I think I will leave this in the hands of a more capable KDE developer. I tried to do: ./kdesrc-build kdeplasma-addons As well as: ./kdesrc-build --include-dependencies kdeplasma-addons A large amount of pieces built successfully, but ultimately a few pieces failed to compile with errors like: CMake Error at src/CMakeLists.txt:73 (add_library): Target "KF5XmlGui" links to target "Qt5::CorePrivate" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Likewise kwallet failed to compile because it couldn't find libgpgme, and in general this seems like a lot to change a single line of code! I'm sure a more capable KDE developer can figure it all out or use their existing development environment to figure it out, but for me I'm bowing out of this battle early. KDE build system looks pretty cool but also seems very complex! It seems if I'm not able to this basic change there is likely not much hope in me contributing much value to KDE development wise as a whole. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 397914] Picture of the Day doesn't change every day
https://bugs.kde.org/show_bug.cgi?id=397914 --- Comment #4 from Kristopher Ives --- I was able to get kdesrc-build setup and running and currently am waiting for this command to finish: ./kdesrc-build --include-dependencies plasma-desktop That might take a while, obviously. I am interested if anyone knows if there is an easier way to test these changes. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 397914] Picture of the Day doesn't change every day
https://bugs.kde.org/show_bug.cgi?id=397914 --- Comment #3 from Kristopher Ives --- Hi guys! I tried setting up a development environment to test this, but cmake complains about a chain of things and I gave up after grabbing plasma. Here is what I tried so far: sudo apt build-dep kdeplasma-addons apt source kdeplasma-addons cd kdeplasma-addons* cmake . I then get this problem: Make Error at CMakeLists.txt:9 (message): plasma requires an out of source build. Please create a separate build directory and run 'cmake path_to_plasma [options]' there. So I repeat the process for plasma-desktop, which then gives another layer of turtles: -- The following RUNTIME packages have not been found: * org.kde.plasma.core-QMLModule, QML module 'org.kde.plasma.core' is a runtime dependency. Sorry for not being familiar with KDE development practices! Any advice would be awesome. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 397914] New: Picture of the Day doesn't change every day
https://bugs.kde.org/show_bug.cgi?id=397914 Bug ID: 397914 Summary: Picture of the Day doesn't change every day Product: kdeplasma-addons Version: 5.13.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kimpanel-dataengine Assignee: plasma-b...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- When setting desktop background to Picture of the Day (potd) using provider Bing (and likely others) the background picture doesn't change every day. It does appear to change sometimes, but not every day. I am willing to do more debugging if needed to fix this. I have been reading the potd code and it appears to have a 10 minute timer that uses the last modified time of a cached image file, with this line of code: info.lastModified().daysTo( QDateTime::currentDateTime() ) > 1 Does this mean it only changes every 2 days and the fix might be as simple as changing to greater-or-equals to 1? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396690] New: Add torrent by infohash without a magnet link
https://bugs.kde.org/show_bug.cgi?id=396690 Bug ID: 396690 Summary: Add torrent by infohash without a magnet link Product: ktorrent Version: 5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: kristopher.i...@gmail.com Target Milestone: --- While many savvy users can turn a infohash into a magnet link it's nice to be able to message someone a hash and have them add it without having to turn it into a magnet link manually since some message programs either block magnet links or turn some characters into emoticons. I would be interested in doing the work to add this assuming the KDE team is okay with the change. -- You are receiving this mail because: You are watching all bug changes.
