[akregator] [Bug 485062] Akregator | Flatpak version 6.0.0 | Font on the Reading pane looks blurry/broken
https://bugs.kde.org/show_bug.cgi?id=485062 Sean Gray changed: What|Removed |Added CC||sean00g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 485062] New: Akregator | Flatpak version 6.0.0 | Font on the Reading pane looks blurry/broken
https://bugs.kde.org/show_bug.cgi?id=485062 Bug ID: 485062 Summary: Akregator | Flatpak version 6.0.0 | Font on the Reading pane looks blurry/broken Classification: Applications Product: akregator Version: 6.0.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sean00g...@gmail.com Target Milestone: --- Created attachment 168167 --> https://bugs.kde.org/attachment.cgi?id=168167=edit Screenshot of the defect SUMMARY Font on the Reading pane looks blurry STEPS TO REPRODUCE 1. Open the App (flatpak version) 2. select a feed 3. click on any entry OBSERVED RESULT font is broken/blurry EXPECTED RESULT font should be smooth SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.6.15-amd64 (64-bit) Graphics Platform: Wayland Processors: 24 × 13th Gen Intel® Core™ i7-13700K Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D29 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482235] New: No longer able to trigger desktop grid effect via screen edge corner action
https://bugs.kde.org/show_bug.cgi?id=482235 Bug ID: 482235 Summary: No longer able to trigger desktop grid effect via screen edge corner action Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: colsen.s...@gmail.com Target Milestone: --- Prior to upgrading to Plasma 6.0, I was able to initiate the desktop grid effect via moving my pointer to a screen corner. After the upgrade, I am able to initiate the desktop grid effect via a keyboard shortcut (and the desktop grid itself works fine). But I'm no longer able to configure my screen edge actions to trigger the desktop grid effect. The options I have available for all eight screen edge/corner locations are as follows: No action Peek at Desktop Lock Screen Show KRunner Activity Manager Present Windows - All Desktops Present Windows - Current Desktop Present Windows - Current Application Overview Toggle window switching Toggle alternative window switching I would expect to see "Desktop Grid" within that list of options, but I don't. I've tried selecting "Overview", thinking that perhaps it would show a grid, but it does not. It seems to function in a nearly identical manner to "Present Windows - Current Desktop". These existing bugs seem like potential duplicates: https://bugs.kde.org/show_bug.cgi?id=442518 https://bugs.kde.org/show_bug.cgi?id=454102 However, they show as already being fixed. I am running on Plasma 6.0.0, KDE Neon 6.0, Qt Version 6.6.2, Kernel 6.5.0-21-generic, Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Sean changed: What|Removed |Added CC|seanpatr...@duck.com| -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 --- Comment #26 from Sean --- (In reply to Rich Johnson from comment #5) > I've created 2 files in /usr/share/dbus-1/services to make my Restart, > Shutdown & Logout work again: > > $ cat org.kde.Shutdown.service > [D-BUS Service] > Name=org.kde.Shutdown > Exec=/usr/bin/plasma-shutdown > > $ cat org.kde.LogoutPrompt.service > [D-BUS Service] > Name=org.kde.LogoutPrompt > Exec=/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout-greeter Thanks Rich Johnson, this works perfectly (for the other noobs out there I created the file in Kate and just saved to the correct directly specified by Rich) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481985] Feature request: bring back "Walk through desktops" shortcut
https://bugs.kde.org/show_bug.cgi?id=481985 Sean Colsen changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #5 from Sean Colsen --- > need a shortcut to cycle between the current and the previous desktop. Yes. Correct I installed the KWin script you linked to. It works great for me!! THANK YOU!!! I'm marking this as resolved now since my problem is solved via the KWin script. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481990] New: Can't shut down or restart
https://bugs.kde.org/show_bug.cgi?id=481990 Bug ID: 481990 Summary: Can't shut down or restart Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: seanpatr...@duck.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** 'Restart' and 'Shutdown' buttons don't work in application launcher STEPS TO REPRODUCE 1. Start KDE Neon Plasma 6 2. Attempt to shutdown or restart through application launcher 3. OBSERVED RESULT Nothing happens, no error messages, no effect EXPECTED RESULT Desktop shuts down or restarts SOFTWARE/OS VERSIONS Linux/KDE Plasma: KKDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION These worked fine before in the unstable version of KDE Neon plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481985] Feature request: bring back "Walk through desktops" shortcut
https://bugs.kde.org/show_bug.cgi?id=481985 --- Comment #2 from Sean Colsen --- I found these similar issues of people that seem to be reporting the same thing as me. https://bugs.kde.org/show_bug.cgi?id=481297 https://bugs.kde.org/show_bug.cgi?id=460502 https://bugs.kde.org/show_bug.cgi?id=479984 These were all closed as "RESOLVED INTENTIONAL". I implore you: please do not close this one too. This issue as a feature request for something to fill this need again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481985] Feature request: bring back "Walk through desktops" shortcut
https://bugs.kde.org/show_bug.cgi?id=481985 --- Comment #1 from Sean Colsen --- Perhaps it's also worth mentioning that I see two other keyboard shortcuts titled "Switch to Next Desktop" and "Switch to Previous Desktop". I've tried enabling them, but they don't appear to do anything. I have a vague recollection that these keyboard shortcuts used to function in a manner where they would switch to the next/previous desktop in the order they are listed. That's not what I want. I want to be able to switch to the desktop I was previously on. I could be remembering incorrectly though. If there is an easy way to enable a one-shot shortcut to simply switch to the desktop I was previously on, I'd love to know how to do that! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481985] New: Feature request: bring back "Walk through desktops" shortcut
https://bugs.kde.org/show_bug.cgi?id=481985 Bug ID: 481985 Summary: Feature request: bring back "Walk through desktops" shortcut Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: colsen.s...@gmail.com Target Milestone: --- I see that in https://invent.kde.org/plasma/kwin/-/merge_requests/3871 the desktop switching keyboard shortcuts were removed. I just upgraded to KDE 6 today and am crestfallen to discover that these keyboard shortcuts no longer work. This ticket is a desperate plea for you to please bring (at least some of) them back. Perhaps I am idiosyncratic, but I have been relying on heavily on the "Walk through desktops" keyboard shortcut for probably well over 10 years. I would venture to guess that I have been using this keyboard shortcut over 100 times every day. Seriously. I actually use it slightly MORE frequently than switching between windows. I'm front end web software engineer, and I organize my work into a grid of 9 desktops, most commonly making use of several desktops at a time. Without getting too into the weeds, I'll just say that "switching to the desktop that I was previously on" gives me a very convenient way to toggle between two groups of similar windows at a time, and that is tremendously helpful for my day-to-day tasks and the way my brain works. Often I have one desktop with Thunderbird, Matrix Element, GitHub, Basecamp (all the comms windows); and another with my code editor, terminal, browser, dev tools (my dev work). I toggle between those two desktops frequently. Then I might utilize a different desktop for a slightly more ephemeral task, say a small bit of research that requires several windows but will only take 2 hours. Then I'm often toggling between that desktop and my comms desktop or my dev desktop. I've tried using activities for this but it really doesn't work as well for me. I like to be able to visually group windows into similar types of tasks without having to give names to them. And I like to zoom out and see all my open windows at once using the desktop grid. Those things are harder with activities. Desktops feel lighter weight and easier for me to reason about. I am still able to use keyboard shortcuts to switch to a specific desktop or to switch to a desktop in a specific direction (e.g. "left"), but that doesn't allow me to toggle between two desktops. That's the important thing I'm missing. I desperately want a keyboard shortcut again that will take me to the desktop I was just on. It doesn't even need to have the "walk though" functionality. That is, I don't need to see a list switcher pop up to switch between any of my 9 desktops (because I can use the grid for that). I just want to go back to the one I was just on. Please please PLEASE!!! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481810] New: Changing any printer setting hangs program, CUPS error message stuck on screen
https://bugs.kde.org/show_bug.cgi?id=481810 Bug ID: 481810 Summary: Changing any printer setting hangs program, CUPS error message stuck on screen Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: seanpatr...@duck.com Target Milestone: --- Created attachment 166089 --> https://bugs.kde.org/attachment.cgi?id=166089=edit Error message SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch Printers from Discover 2. Try to make any change to settings 3. Close program OBSERVED RESULT Error message box pops up on screen "CUPS SERVER ERROR - connection reset by peer' 2nd error message box pops up on screen "There was an error during the CUPS operation - Success' Can not close error boxes (can't click off) Can not close Printer program (Not responding) or force close it EXPECTED RESULT Printer settings changed You can close printer program You can 'X' off error messages SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde NEON Plasma 6.1 Dev / Unstable edition / Wayland (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.00 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480811] Black screen on startup since 2/2 updates
https://bugs.kde.org/show_bug.cgi?id=480811 --- Comment #2 from Sean --- (In reply to Sean from comment #1) > I had the same bug. I was able to refresh/update the packages and get into > desktop normally after getting to the command line (ctrl+alt+f4), logging > in, and running pkcon refresh, then pkcon update. > > That being said - my 'HDR' option in the display is now missing and the > scaling seems a little wonky. Update: there was no HDR as I was reverted to X11 after running above updates. Upon switching back to Wayland, and rebooting - all is well again (scaling and HDR options) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480811] Black screen on startup since 2/2 updates
https://bugs.kde.org/show_bug.cgi?id=480811 Sean changed: What|Removed |Added CC||seanpatr...@duck.com --- Comment #1 from Sean --- I had the same bug. I was able to refresh/update the packages and get into desktop normally after getting to the command line (ctrl+alt+f4), logging in, and running pkcon refresh, then pkcon update. That being said - my 'HDR' option in the display is now missing and the scaling seems a little wonky. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 480121] New: kmail crash when changing layout
https://bugs.kde.org/show_bug.cgi?id=480121 Bug ID: 480121 Summary: kmail crash when changing layout Classification: Applications Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: seanmcne...@gmail.com Target Milestone: --- Application: kmail (5.24.4 (23.08.4)) Qt Version: 5.15.11 Frameworks Version: 5.113.0 Operating System: Linux 6.6.11-200.fc39.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 39.20240121.0 (Kinoite) DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: When changine the layout to/from message panel below message list it crashes. To reproduce: Configure KMail Appearance -> Layout in Message Preview Pane Change the selection and hit OK The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x7f5fc8232ad4 in Akonadi::StandardMailActionManager::action(Akonadi::StandardMailActionManager::Type) const () from /lib64/libKPim5AkonadiMime.so.5 #5 0x7f5fd2614042 in KMMainWidget::updateFolderMenu() () from /lib64/libkmailprivate.so.5 #6 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f5fc907183d in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /lib64/libQt5Core.so.5 #8 0x7f5fc9079f77 in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /lib64/libQt5Core.so.5 #9 0x7f5fc9075194 in QItemSelectionModel::select(QModelIndex const&, QFlags) () from /lib64/libQt5Core.so.5 #10 0x7f5fc6f2f0c2 in KViewStateSerializer::restoreSelection(QStringList const&) () from /lib64/libKF5WidgetsAddons.so.5 #11 0x7f5fc79bcc43 in Akonadi::ETMViewStateSaver::selectCollections(QVector const&) () from /lib64/libKPim5AkonadiWidgets.so.5 #12 0x7f5fc8d1b1a0 in MessageList::Pane::restoreHeaderSettings(int, bool) () from /lib64/libKPim5MessageList.so.5 #13 0x7f5fc8d10451 in MessageList::Pane::Pane(bool, QAbstractItemModel*, QItemSelectionModel*, QWidget*) () from /lib64/libKPim5MessageList.so.5 #14 0x7f5fd25f84d8 in KMMainWidget::createWidgets() () from /lib64/libkmailprivate.so.5 #15 0x7f5fd25f9e20 in KMMainWidget::readConfig() () from /lib64/libkmailprivate.so.5 #16 0x7f5fd2600c73 in KMMainWidget::slotConfigChanged() () from /lib64/libkmailprivate.so.5 #17 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #18 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f5fc90e8871 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x7f5fc9ea9c74 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #21 0x7f5fc9ea9eff in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #22 0x7f5fc9eab860 in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #23 0x7f5fc9eaba68 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #24 0x7f5fc9df3698 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #25 0x7f5fc9daeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7f5fc9db7456 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7f5fc90b4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #28 0x7f5fc9db56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #29 0x7f5fc9e0d1b9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7f5fc9e1073f in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #31 0x7f5fc9daeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #32 0x7f5fc90b4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7f5fc956cc1b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #34 0x7f5fc954acfc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #35 0x7f5fc189ae94 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #36 0x7f5fc28bde5c in g_main_context_dispatch_unlocked.lto_priv () from /lib64/libglib-2.0.so.0 #37 0x7f5fc2918f18 in g_main_context_iterate_unlocked.isra () from /lib64/libglib-2.0.so.0 #38 0x7f5fc28bbad3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #39 0x7f5fc9106ad9 in
[krita] [Bug 367694] Support loading palettes saved as a CSS file
https://bugs.kde.org/show_bug.cgi?id=367694 Sean Castillo changed: What|Removed |Added CC||seanchrn...@gmail.com --- Comment #4 from Sean Castillo --- I got working on this. I have the most basic implementation working (4 RGB swatches and using the file name as the palette name), and I'll make sure it works with anything that could come up before I submit it. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470219] New: krunner sometimes crashes after typing a few numbers/letters
https://bugs.kde.org/show_bug.cgi?id=470219 Bug ID: 470219 Summary: krunner sometimes crashes after typing a few numbers/letters Classification: Plasma Product: krunner Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@attackllama.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Application: krunner (5.27.5) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.3-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: krunner often crashes after a few numbers are typed in. Occasionally it works completely fine. This seems to happen regardless of whether krunner is invoked via Alt+Space or `krunner` in a terminal. The crash can be reproduced sometimes. -- Backtrace: Application: KRunner (krunner), signal: Segmentation fault [KCrash Handler] #4 0x7f1990c5bc54 in MathStructure::clear(bool) () at /usr/lib/libqalculate.so.22 #5 0x7f1990c5c257 in MathStructure::setAborted(bool) () at /usr/lib/libqalculate.so.22 #6 0x7f1990bc3746 in CalculateThread::run() () at /usr/lib/libqalculate.so.22 #7 0x7f1990c76113 in Thread::doRun(void*) () at /usr/lib/libqalculate.so.22 #8 0x7f19ace9d44b in () at /usr/lib/libc.so.6 #9 0x7f19acf20e40 in () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7f1906bfe6c0 (LWP 7351) "Thread (pooled)"): #1 0x7f19ace9cab5 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x7f19ad4fadf4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f19ad4f7f2a in () at /usr/lib/libQt5Core.so.5 #4 0x7f19ad4f30da in () at /usr/lib/libQt5Core.so.5 #5 0x7f19ace9d44b in () at /usr/lib/libc.so.6 #6 0x7f19acf20e40 in () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f19073ff6c0 (LWP 7350) "Thread (pooled)"): #1 0x7f19ace9cab5 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #2 0x7f19ad4fadf4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7f19ad4f7f2a in () at /usr/lib/libQt5Core.so.5 #4 0x7f19ad4f30da in () at /usr/lib/libQt5Core.so.5 #5 0x7f19ace9d44b in () at /usr/lib/libc.so.6 #6 0x7f19acf20e40 in () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f19349ef6c0 (LWP 7349) "gmain"): #1 0x7f19abd6c17f in () at /usr/lib/libglib-2.0.so.0 #2 0x7f19abd0e1a2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f19abd0e1f2 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f19abd3c315 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f19ace9d44b in () at /usr/lib/libc.so.6 #6 0x7f19acf20e40 in () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f1937fff6c0 (LWP 7336) "GlobalQueue[24]"): #1 0x7f19ad4eea76 in QBasicMutex::lockInternal() () at /usr/lib/libQt5Core.so.5 #2 0x7f19ad4eec53 in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #3 0x7f19ad4f7188 in QReadWriteLock::tryLockForRead(int) () at /usr/lib/libQt5Core.so.5 #4 0x7f19aeef5b0d in () at /usr/lib/libQt5DBus.so.5 #5 0x7f19aeeecfe9 in QDBusConnection::asyncCall(QDBusMessage const&, int) const () at /usr/lib/libQt5DBus.so.5 #6 0x7f199d395220 in () at /usr/lib/libKF5Runner.so.5 #7 0x7f199d39ebd0 in () at /usr/lib/libKF5Runner.so.5 #8 0x7f199ff8b7de in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f199ff8c726 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f199ff90442 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f19ad4f30da in () at /usr/lib/libQt5Core.so.5 #12 0x7f19ace9d44b in () at /usr/lib/libc.so.6 #13 0x7f19acf20e40 in () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f193cff96c0 (LWP 7335) "GlobalQueue[23]"): #1 0x7f19ad4ef47c in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #2 0x7f19ad6cfebe in () at /usr/lib/libQt5Core.so.5 #3 0x7f19aeefcdd5 in QDBusAbstractInterface::connectNotify(QMetaMethod const&) () at /usr/lib/libQt5DBus.so.5 #4 0x7f19ad6cddd1 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /usr/lib/libQt5Core.so.5 #5 0x7f19ad6ce15e in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () at /usr/lib/libQt5Core.so.5 #6 0x7f19919dcc17 in KActivities::Stats::ResultWatcher::ResultWatcher(KActivities::Stats::Query, QObject*) () at
[kmail2] [Bug 470002] New: Resource “Mailbox” is broken. Authentication failed
https://bugs.kde.org/show_bug.cgi?id=470002 Bug ID: 470002 Summary: Resource “Mailbox” is broken. Authentication failed Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: seanm0...@gmail.com Target Milestone: --- Created attachment 159108 --> https://bugs.kde.org/attachment.cgi?id=159108=edit Error given by kmail SUMMARY I am using Kmail for my university’s Corporate Outlook Exchange email. At seemingly random intervals I get an error relating to authentication (see attached image) and I will have to manually select Check Mail to update my inbox. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470002] Resource “Mailbox” is broken. Authentication failed
https://bugs.kde.org/show_bug.cgi?id=470002 --- Comment #1 from Sean M --- https://discuss.kde.org/t/kmail-resource-mailbox-is-broken-authentication-failed/1422 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 468669] ksplashqml crashes at login in SplashWindow::setStage() (Fedora 38 beta)
https://bugs.kde.org/show_bug.cgi?id=468669 Sean M changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Sean M --- Fixed by running 'sudo dnf install mesa-*' -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 468669] New: ksplashqml crashes at login (Fedora 38 beta)
https://bugs.kde.org/show_bug.cgi?id=468669 Bug ID: 468669 Summary: ksplashqml crashes at login (Fedora 38 beta) Classification: Plasma Product: ksplash Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: seanm0...@gmail.com Target Milestone: --- ksplashqml crashes at login, resulting in Plasma hanging. To continue login I must switch to tty and startx. Operating System: Fedora Linux 38 (beta) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-300.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 14.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 81YQ System Version: IdeaPad 5 15ARE05 Crash dump: https://pastebin.com/LRS44RVt -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 434820] ksplashqml crashed when login in wayland session
https://bugs.kde.org/show_bug.cgi?id=434820 Sean M changed: What|Removed |Added CC||seanm0...@gmail.com --- Comment #3 from Sean M --- Same issue occurring on Fedora 38 beta. Must switch to tty and startx to login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Sean Mackedie changed: What|Removed |Added CC|colonelpani...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 208215] Valgrind does not support Objective-C garbage collection (Obj-C GC)
https://bugs.kde.org/show_bug.cgi?id=208215 --- Comment #1 from Sean --- In the intervening 14 years, Objective-C garbage collection has been deprecated and then removed from macOS. This ticket should just be closed. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464022] When hotplugging mouse/keyboard with USB switcher, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Sean changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Sean --- After an update and restart yesterday/today, the issue has gone away. I'm not sure what the root cause was, but resolving anyways. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464022] When hotplugging mouse/keyboard with USB switcher, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Sean changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 420653] Make it easier extract a compressed archive to the current location in the Dolphin plugin
https://bugs.kde.org/show_bug.cgi?id=420653 Sean Long changed: What|Removed |Added CC||long-sean-...@proton.me --- Comment #3 from Sean Long --- Is this still something we are looking at implementing? I have no c++ or Qt experience, but am happy to give it a shot. I am thinking the right click menu would end up being: Extract here Extract > Extract archive to... Extract archive here, autodetect subfolder -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464022] When hotplugging mouse/keyboard with USB switcher, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 --- Comment #3 from Sean --- (In reply to Nate Graham from comment #2) > Because you're on X11, input isn't going through KWin but rather the input > drives for the X11 server. Can you try on Wayland to see if it still > happens? Thanks! Confirmed that it still happens when using Wayland. Operating System: EndeavourOS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Kernel Version: 6.1.4-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464022] When hotplugging mouse/keyboard with USB switcher, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Sean changed: What|Removed |Added CC||s...@krail.dev -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 351962] Missing Comment in desktop file
https://bugs.kde.org/show_bug.cgi?id=351962 Sean Long changed: What|Removed |Added CC||long-sean-...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464022] When hotplugging mouse/keyboard with USB switcher, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Sean changed: What|Removed |Added Summary|When hotplugging|When hotplugging |mouse/keyboard, input is|mouse/keyboard with USB |unusable for 45 seconds |switcher, input is unusable ||for 45 seconds -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464022] When hotplugging mouse/keyboard, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 --- Comment #1 from Sean --- After further testing, this appears to be caused due to me using a USB switcher (specifically I'm using https://www.amazon.com/gp/product/B082K87B87). What I've tried: 1. [ ] Hotplugging the mouse to the USB switcher doesn't cause any delay 2. [ ] Hotplugging the mouse directly to the PC doesn't cause any delay 3. [x] Hotplugging the USB switcher to the PC causes 45 second delay 4. [x] Hitting the switch button on USB switcher and then switching back causes 45 second delay Note that the USB switcher itself isn't broken. This same USB switcher works fine with my macOS and Windows computers---no delay. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Sean changed: What|Removed |Added Ever confirmed|0 |1 --- Comment #122 from Sean --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464022] When hotplugging mouse/keyboard, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Sean changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=435113 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Sean changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464022 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464022] New: When hotplugging mouse/keyboard, input is unusable for 45 seconds
https://bugs.kde.org/show_bug.cgi?id=464022 Bug ID: 464022 Summary: When hotplugging mouse/keyboard, input is unusable for 45 seconds Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s...@krail.dev Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Unplug keyboard and mouse 2. Plug in keyboard and mouse; start timer 3. Observe that keyboard and mouse are unusable until 45 seconds pass 4. Keyboard and mouse work OBSERVED RESULT Keyboard and mouse are unusable for 45 seconds after hotplugging (this includes at login if using a USB switcher). After 45 seconds, keyboard and mouse are usable. EXPECTED RESULT Mouse and keyboard are usable immediately/shortly after hotplugging. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Kernel Version: 6.1.3-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I ran into a similar issue like this due to https://bugs.kde.org/show_bug.cgi?id=435113. However, mouse settings are not reset after the hotplugging now; there's just a 45-second delay. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463290] New: Disconnecting USB from Android Crashed Dolphin
https://bugs.kde.org/show_bug.cgi?id=463290 Bug ID: 463290 Summary: Disconnecting USB from Android Crashed Dolphin Classification: Applications Product: dolphin Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sean...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.0) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 5.15.0-56-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: Seems like it happened when I was creating a link to the mtp:/Hachiman-Taro/SD card/Music/ The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f2e537be164 in QWidget::style() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f2e5379a274 in QApplication::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f2e53794763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f2e52c9f09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2e52cf7e2b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2e52cf8774 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2e50825d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f2e5087a6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f2e508233e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f2e52cf8af8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2e52c9d9bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f2e539a7a12 in QDialog::exec() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f2e54bf48a0 in KFilePlaceEditDialog::getInformation(bool, QUrl&, QString&, QString&, bool, bool&, int, QWidget*) () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #17 0x7f2e54be7fef in ?? () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #18 0x7f2e54bef367 in KFilePlacesView::contextMenuEvent(QContextMenuEvent*) () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #19 0x7f2e537d787e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f2e53885bf2 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f2e52c9edfa in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f2e53794752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f2e5379bce4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f2e52c9f09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f2e537f1874 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f2e537f43a5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f2e53794763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f2e52c9f09a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f2e53089a87 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x7f2e5305da6c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7f2e4d634c8e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #32 0x7f2e50825d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f2e5087a6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f2e508233e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f2e52cf8af8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f2e52c9d9bb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f2e52ca5f54 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x55ab4f30fa7d in ?? () #39 0x7f2e525bad90 in __libc_start_call_main (main=main@entry=0x55ab4f309bb0, argc=argc@entry=2, argv=argv@entry=0x7ffcf34106f8) at ../sysdeps/nptl/libc_start_call_main.h:58 #40 0x7f2e525bae40 in __libc_start_main_impl (main=0x55ab4f309b
[dolphin] [Bug 462728] Dolphin crashes when unmounting external hard drive
https://bugs.kde.org/show_bug.cgi?id=462728 Sean Peterson changed: What|Removed |Added CC||sean...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Sean Mackedie changed: What|Removed |Added Version|5.24.5 |5.25.3 CC||colonelpani...@gmail.com --- Comment #16 from Sean Mackedie --- Same problem for me on EndeavourOS, although the pressing issue isn't icons on the desktop (as I don't have a lot on my desktop) but settings for widgets. I have a panel added to the top of my screen with system info (CPU usage, HDD space and activity, memory usage etc.) and each time Plasma is reloaded the settings for those widgets are reset. Like others in this thread, I noticed changes made to plasma-org.kde.plasma.desktop-appletsrc each time, however even making the file read-only doesn't prevent the widgets being reset. I was able to reproduce the issue even by deleting the existing plasma-org.kde.plasma.desktop-appletsrc, restarting Plasma, and then simply adding a single new panel with a single "Toal CPU Usage" widget, changing its settings, and upon restarting Plasma the widget is reset to defaults. KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.15-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 260266] Allow assigning keyboard shortcuts to service menu actions
https://bugs.kde.org/show_bug.cgi?id=260266 Sean Monahan changed: What|Removed |Added CC||k...@seanahan.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Sean changed: What|Removed |Added CC||s...@krail.dev -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414559] Running "sudo udevadm trigger -s input" resets touchpad configuration; can happen after system upgrade
https://bugs.kde.org/show_bug.cgi?id=414559 Sean changed: What|Removed |Added CC||s...@krail.dev -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449737] "Disable vector optimizations" options have no apparent effect
https://bugs.kde.org/show_bug.cgi?id=449737 --- Comment #9 from Sean Mirrsen --- (In reply to Dmitry Kazakov from comment #7) > Hi, Sean! > > Could you please check if this package fixes this issue? > > https://disk.yandex.ru/d/lDNTKUKCayqGzA > > The package also changes the behavior of all existing brushes with Soft and > Gaussian tips for size below 10 px (it enables supersampling for them, which > has always been enabled for Default brush tips). How do you think, is such > behavior change acceptable for the user? Would love to test it, however my only PC with tablet access (as it literally is the tablet) runs Windows. Can't test an .appimage, which I believe is a Linux package. But it does sound like it should help, and it would be an appropriate change - there's no danger of performance loss for brushes that small, and the sub-pixel blending should be improved by supersampling. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449737] "Disable vector optimizations" options have no apparent effect
https://bugs.kde.org/show_bug.cgi?id=449737 --- Comment #5 from Sean Mirrsen --- (In reply to Dmitry Kazakov from comment #3) > Hi, Sean! > > Could you tell what brush preset you used as a base for the test? My go-to brushes for this test (I've tested a range of versions starting from 4.1.1 I was at and down to current) are the 'c) Pencil-2' and 'c) Pencil-1 Hard' brushes from Krita 4 resources, and the 'ink precision 03' brush from Krita 3 resources, set to 1px or 2px width. The exact brush does not matter though - any brush with 'Gaussian' or 'Soft' mask modes will have broken sub-pixel blending at small diameters. (In reply to Halla Rempt from comment #4) > Maybe similar to https://bugs.kde.org/show_bug.cgi?id=433603 It's probably related - by sheer power of deduction it's highly likely that a major performance optimization targeting gaussian and soft brush mask modes added in the same version where issues with said modes began, is probably the cause of those issues - however my issue is not specifically that the optimizations break this. All optimizations end up breaking something somewhere. But there's an option that seems like it should turn these optimizations off, and it does not. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449737] "Disable vector optimizations" options have no apparent effect
https://bugs.kde.org/show_bug.cgi?id=449737 --- Comment #2 from Sean Mirrsen --- (In reply to Halla Rempt from comment #1) > You shouldn't use screenshots to compare, but use an imagemagick diff on > saved png images to see whether it's really the rendering to the image or > the currently chosen way to render the image on the canvas. I'm not sure what that is or how to do it. Or how it would help - I can't perfectly recreate the exact same strokes on different images, for a 'diff', which I assume highlights differences, to be useful. The aliasing/subpixel blending artifacts do end up in the saved image. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449737] New: "Disable vector optimizations" options have no apparent effect
https://bugs.kde.org/show_bug.cgi?id=449737 Bug ID: 449737 Summary: "Disable vector optimizations" options have no apparent effect Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: controllers...@mail.ru Target Milestone: --- Created attachment 146383 --> https://bugs.kde.org/attachment.cgi?id=146383=edit Comparison of several 1px and 2px sized brushstrokes rendering in 5.0.2 and 4.1.7 versions of Krita. SUMMARY The "Disable all vector optimizations" and "Disable AVX vector optimizations" option under Performance settings, seem like they should disable the vectorization optimizations introduced for the Gaussian and Soft brush mask modes in Krita version 4.2.0. Said vectorization optimizations are the source of undesired behavior (breaking sub-pixel blending for small brush sizes, see included screenshot), and thus turning them off is desirable for specific activities (such as sprite art, normally done primarily with small brushes). However, checking the options to disable said optimizations, has no apparent effect. STEPS TO REPRODUCE 1. Observe the Gaussian and Soft mode brush issues at sizes below 2 pixels being present with the options disabled. 2. Enable the "Disable AVX vector optimizations" and "Disable all vector optimizations" options in advanced performance settings, and restart Krita. 3. Attempt drawing. OBSERVED RESULT The brushstroke rendering artifacts at sizes of 2 pixels and below, remain, as seen in all versions of Krita since 4.2.0. EXPECTED RESULT The brushstroke rendering at sizes of 2 pixels and below, returns to that seen in Krita versions 4.1.x. SOFTWARE/OS VERSIONS Windows: 8.0 x64 ADDITIONAL INFORMATION Yes I have tested Krita versions since 4.1.1 that I was using. This behavior begins and remains unchanged since 4.2.0 when optimizations specifically for the affected brush mask modes have been added. Changing "brush flow mode" settings to either 4.2 or 4.1.x has no effect. Changing canvas acceleration to opengl, ANGLE, software, or turning it off entirely has no effect except on performance. - Krita Version: 5.0.2 Languages: en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, en_US, en, ru_RU, ru, en_US, en Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 6.2.9200 Pretty Productname: Windows 8 (6.2) Product Type: windows Product Version: 8 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) HD Graphics 4000 Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_EXT_map_buffer_range" "GL_ANGLE_lossy_etc_decode" "GL_ANGLE_client_arrays" "GL_OES_texture_npot" "GL_ANGLE_depth_texture" "GL_NV_EGL_stream_consumer_external" "GL_ANGLE_framebuffer_blit" "GL_ANGLE_translated_shader_source" "GL_EXT_sRGB" "GL_KHR_debug" "GL_OES_vertex_array_object" "" "GL_EXT_occlusion_query_boolean" "GL_EXT_blend_minmax" "GL_EXT_discard_framebuffer" "GL_EXT_texture_format_BGRA" "GL_OES_standard_derivatives" "GL_OES_element_index_uint" "GL_ANGLE_framebuffer_multisample" "GL_EXT_shader_texture_lod" "GL_CHROMIUM_bind_uniform_location" "GL_ANGLE_program_cache_control" "GL_CHROMIUM_copy_texture" "GL_OES_texture_float" "GL_CHROMIUM_copy_compressed_texture" "GL_EXT_color_buffer_float" "GL_OES_texture_half_float_linear" "GL_OES_surfaceless_context" "GL_ANGLE_multiview" "GL_OES_packed_depth_stencil" "GL_EXT_debug_marker" "GL_OES_EGL_image"
[systemsettings] [Bug 447273] New: Crash in system settings for most all Appearance selections
https://bugs.kde.org/show_bug.cgi?id=447273
Bug ID: 447273
Summary: Crash in system settings for most all Appearance
selections
Product: systemsettings
Version: 5.23.3
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: seanmcne...@gmail.com
Target Milestone: ---
Application: systemsettings5 (5.23.3)
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.8-200.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35.20211219.0 (Kinoite)
DrKonqi: 5.23.3 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Clicked Appearance
Clicked Get New Global Themes
Also crashed when selecting Colors, Windows Decoration, Cursors, Launch
Feedback, Splash Screen.
- Custom settings of the application:
Fully configured Fedora 35 KDE spin with /home mounted as a separate partition.
Moved system to Fedora Kinoite 35 and mounted home as /var/home.
Added some things to ostree:
LayeredPackages: akmod-nvidia crash edk2-ovmf gdb glibc.i686 kate
kde-connect kdeconnectd kontact kwalletcli libvirt-client qemu
spamassassin virt-manager xorg-x11-drv-nvidia
xorg-x11-drv-nvidia-cuda
LocalPackages: rpmfusion-free-release-35-1.noarch
rpmfusion-nonfree-release-35-1.noarch
The crash can be reproduced every time.
-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 QQmlRefPointer::QQmlRefPointer (other=...,
this=0x7ff7fceb8ff0) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152
#7 QQmlType::QQmlType (this=, this=) at
qml/qqmltype.cpp:121
#8 0x7ff8254bb1e4 in
QQmlPropertyCacheCreator::propertyCacheForObject
(error=, context=..., obj=, this=)
at
../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:310
#9 QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=, objectIndex=, context=...,
isVMERequired=) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:264
#10 0x7ff8256bdc51 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=0x7ff7fceb93a0, objectIndex=3, context=..., isVMERequired=) at /usr/include/qt5/QtCore/qendian.h:290
#11 0x7ff8256bdc51 in
QQmlPropertyCacheCreator::buildMetaObjectRecursively
(this=0x7ff7fceb93a0, objectIndex=0, context=..., isVMERequired=) at /usr/include/qt5/QtCore/qendian.h:290
#12 0x7ff8256beaf0 in
QQmlPropertyCacheCreator::buildMetaObjects
(this=0x7ff7fceb93a0) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:215
#13 QQmlTypeCompiler::compile (this=0x7ff7fceb9570) at
qml/qqmltypecompiler.cpp:85
#14 0x7ff82562fe8c in
QQmlTypeData::compile(QQmlRefPointer const&,
QV4::ResolvedTypeReferenceMap*, std::function const&)
(dependencyHasher=..., resolvedTypeCache=0x7ff7fceb94f8, typeNameCache=...,
this=0x555b45b27840) at qml/qqmltypedata.cpp:774
#15 QQmlTypeData::done (this=0x555b45b27840) at qml/qqmltypedata.cpp:451
#16 0x7ff82562392d in QQmlDataBlob::tryDone (this=0x555b45b27840) at
qml/qqmldatablob.cpp:524
#17 QQmlDataBlob::tryDone (this=0x555b45b27840) at qml/qqmldatablob.cpp:515
#18 0x7ff82566fec9 in QQmlTypeLoader::setData
(this=this@entry=0x555b4349e6c8, blob=blob@entry=0x555b45b27840, d=...) at
qml/qqmltypeloader.cpp:457
#19 0x7ff825670966 in QQmlTypeLoader::setData
(this=this@entry=0x555b4349e6c8, blob=blob@entry=0x555b45b27840, fileName=...)
at qml/qqmltypeloader.cpp:437
#20 0x7ff825670c28 in QQmlTypeLoader::loadThread (this=0x555b4349e6c8,
blob=0x555b45b27840) at qml/qqmltypeloader.cpp:299
#21 0x7ff825635191 in QQmlTypeLoaderThread::loadThread (this=, b=0x555b45b27840) at qml/qqmltypeloaderthread.cpp:162
#22 0x7ff8256d263f in QQmlThreadPrivate::threadEvent (this=0x555b448df0d0)
at qml/ftw/qqmlthread.cpp:198
#23 QQmlThreadPrivate::event (this=0x555b448df0d0, e=0x555b46809010) at
qml/ftw/qqmlthread.cpp:142
#24 0x7ff82735e443 in QApplicationPrivate::notify_helper (this=, receiver=0x555b448df0d0, e=0x555b46809010) at
kernel/qapplication.cpp:3632
#25 0x7ff8267847d8 in QCoreApplication::notifyInternal2
(receiver=0x555b448df0d0, event=0x555b46809010) at
kernel/qcoreapplication.cpp:1064
#26 0x7ff826787d46 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x555b44f97320) at
kernel/qcoreapplication.cpp:1821
#27 0x7ff8267d6117 in postEventSourceDispatch (s=0x7ff7d814b8f0) at
kernel/qeventdispatcher_glib.cpp:277
#28 0x7ff82451d130 in g_main_dispatch (context=0x7ff7d81450c0) at
../glib/gmain.c:3381
#29
[kde] [Bug 441885] Latte dock crashing when changing Plasma appearance
https://bugs.kde.org/show_bug.cgi?id=441885 Sean Fried changed: What|Removed |Added Summary|Crashing when changing |Latte dock crashing when |Plasma appearance |changing Plasma appearance -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441885] Crashing when changing Plasma appearance
https://bugs.kde.org/show_bug.cgi?id=441885 Sean Fried changed: What|Removed |Added Summary|Craching when changing |Crashing when changing |Plasma appearance |Plasma appearance -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441885] New: Craching when changing Plasma appearance
https://bugs.kde.org/show_bug.cgi?id=441885 Bug ID: 441885 Summary: Craching when changing Plasma appearance Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sean.fr...@gmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.11.0-31-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: Latte seems to crash whenever I am playing with themes. Changing to a different theme/messing with window decorations/etc. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fc4b4e29544 in QSGTexture::setFiltering(QSGTexture::Filtering) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fc4b4e5777f in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fc4b4e41169 in QSGBatchRenderer::Renderer::renderUnmergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc4b4e44f8d in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fc4b4e457a2 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fc4b4e2dc84 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fc4b4e2e153 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fc4b4e8e8d7 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fc4b4efa139 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fc4b4e9caed in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7fc4b4e9d457 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7fc4b2ddb341 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fc4b213e450 in start_thread (arg=0x7fc470b34640) at pthread_create.c:473 #17 0x7fc4b28d2d53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (LWP 1983 "latte-dock"): #1 0x7fc4aed0ef4a in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #2 0x7fc4aed10348 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #3 0x7fc4b213e450 in start_thread (arg=0x7fc471cf2640) at pthread_create.c:473 #4 0x7fc4b28d2d53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (LWP 1978 "KCupsConnection"): #1 0x7fc4b14a3cc6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4b144e023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4b302021b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc4b2fc511b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc4b2dda182 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc472603e0c in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #7 0x7fc4b2ddb341 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc4b213e450 in start_thread (arg=0x7fc47251c640) at pthread_create.c:473 #9 0x7fc4b28d2d53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (LWP 1959 "QQmlThread"): #1 __GI___libc_read (fd=18, buf=0x7fc48bffe9b0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fc4b1450d1c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4b14a3c6d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc4b144e023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc4b302021b in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc4b2fc511b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc4b2dda182 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc4b4b3e7a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fc4b2ddb341 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc4b213e450 in start_thread (arg=0x7fc48bfff640) at pthread_create.c:473 #11 0x7fc4b28d2d53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (LWP 1812 "latte-d:disk$3"): #1 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x561799a39608,
[digikam] [Bug 440588] New: Metadata is not saved in 7.3.0
https://bugs.kde.org/show_bug.cgi?id=440588 Bug ID: 440588 Summary: Metadata is not saved in 7.3.0 Product: digikam Version: 7.3.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Engine Assignee: digikam-bugs-n...@kde.org Reporter: aobr29...@blueyonder.co.uk Target Milestone: --- SUMMARY Metadata is not being saved in version 7.3.0. No problem in version 7.2.0. STEPS TO REPRODUCE 1. Select image and click Tools/Edit Metadata. 2. Enter metadata in any format in any box. 3. Click OK or Apply OBSERVED RESULT Metadata disappears EXPECTED RESULT Metadata should be saved SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Downloaded and installed 7.3.0 yesterday -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 217686] Strontium is listed with the wrong atomic radius
https://bugs.kde.org/show_bug.cgi?id=217686 Sean Robinson changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #6 from Sean Robinson --- Kalzium appears to have never added the calculated radii of the elements to its database. As stated, Kalzium only displays the van der Waals radius and the covalent radius. Therefore I am marking this bug report as "resolved - intentional." -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 433693] New: minor issue, omitting argument to -application causes incorrect error message
https://bugs.kde.org/show_bug.cgi?id=433693 Bug ID: 433693 Summary: minor issue, omitting argument to -application causes incorrect error message Product: Snoretoast Version: 0.5.99 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vonr...@kde.org Reporter: sean.mcle...@gmail.com Target Milestone: --- Created attachment 136217 --> https://bugs.kde.org/attachment.cgi?id=136217=edit Patch to correct this issue. SUMMARY When you invoke snoretoast with "-application" but without any arguments the error message incorrectly refers to it as "-pipeName" and "-applicatzion" STEPS TO REPRODUCE 1. invoke snoretoast with the -application switch but do not specify an application OBSERVED RESULT Error displayed calls the switch "-pipeName" and "-applicatzion": PS> snoretoast -application Missing argument to -pipeName. Supply argument as -applicatzion "C:\foo.exe" EXPECTED RESULT PS> snoretoast -application Missing argument to -application. Supply argument as -application "C:\foo.exe" SOFTWARE/OS VERSIONS Windows: all macOS: n/a Linux/KDE Plasma: n/a (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: n/a ADDITIONAL INFORMATION The fix is really simple, the problematic lines can be seen at https://invent.kde.org/libraries/snoretoast/-/blob/cbd1fa1b2eab79baf2d69c3285bc3ee019f9c833/src/main.cpp#L200-202 but I've attached a patch to correct it anyway. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423189] New: Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 Bug ID: 423189 Summary: Cannot make default script active Product: kmail2 Version: 5.13.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: sieve Assignee: kdepim-b...@kde.org Reporter: s...@vectemis.co.uk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install 2. Edit script 3. Select as active OBSERVED RESULT Item is not selectable. Box turns blue briefly, line disappears and comes back unselected. New sieve rules are not active. EXPECTED RESULT Script selected as default script and work SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32/5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Last known to work in version: pim-sieve-editor-18.12.2-1.fc29.x86_64.rpm -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422236] New: No horizontal scroll bar
https://bugs.kde.org/show_bug.cgi?id=422236 Bug ID: 422236 Summary: No horizontal scroll bar Product: kdenlive Version: 20.04.1 Platform: MS Windows OS: Other Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jeeps...@siu.edu Target Milestone: --- Created attachment 128914 --> https://bugs.kde.org/attachment.cgi?id=128914=edit kdenlive no scroll bar SUMMARY I just installed 20.4.1 (standalone) and after installing video clips, I cannot scroll horizontally. The only way to find the end of the clips I installed was to zoom out. STEPS TO REPRODUCE It happened after installation and first use. I also restarted to see if it would work and it didn't OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421905] New: After returning from suspend (sleep), windows show no title bar and are unresponsive
https://bugs.kde.org/show_bug.cgi?id=421905 Bug ID: 421905 Summary: After returning from suspend (sleep), windows show no title bar and are unresponsive Product: kwin Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kde.b...@moteprime.org Target Milestone: --- SUMMARY After returning from suspend (sleep), windows show no title bar and are unresponsive. The applications themselves seem to be running, and it is possible to interact with the task bar and K menu. Newly launched applications also show the same problem. This started happening after updating the official Kubuntu KDE packages on 21 May 2020. Restarting the machine cures the problem, but this rather defeats the purpose of suspend mode! STEPS TO REPRODUCE 1. Open some applications (e.g. Firefox, Dolphin) 2. K menu > Leave > Sleep 3. Wake machine up again OBSERVED RESULT Application windows are displayed at original size but moved to top left of screen. No title bar is displayed on the window, so they cannot be moved or closed. Windows appear to be unresponsive. Clicking on a window does not activate it or divert focus from the desktop, so typing brings up the desktop search bar. The K menu and task bar work as expected, but newly launched applications also lack title bars and cannot be moved or interacted with, which is why I think that this is a problem with the window manager. EXPECTED RESULT Applications are restored to state before suspend SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION The full version number reported for kwin-x11 is 5.18.5-0ubuntu0.1 Kernel version: 5.4.0-31-generic OS Type: 64 bit Processors: 4x Intel Core i3-6100 CPU @ 3.70GHz Memory: 15.6 GiB of RAM Graphics: GM206 (GeForce GTX 950) OpenGL version 4.6.0 NVIDIA 440.64 Monitor: 4K HDMI -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384485] Face Regions are deleted when unconfirmed face suggestion is rejected by user
https://bugs.kde.org/show_bug.cgi?id=384485 Sean Millichamp changed: What|Removed |Added CC||s...@bruenor.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405879] Hang when clicking on the canvas with a stylus after changing layer opacity by entering a number
https://bugs.kde.org/show_bug.cgi?id=405879 Sean Sosa changed: What|Removed |Added CC||seansos...@gmail.com --- Comment #34 from Sean Sosa --- The program just now crashed and deleted all my art pieces except 1. Anybody got a fix for that? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406809] digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=406809 --- Comment #11 from Sean O'Neill --- Thank you. Maik. That worked fine. I can open and use Digikam 6.2.0 now. Regards Sean Sent from Mail for Windows 10 From: Maik Qualmann Sent: 30 August 2019 17:26 To: aobr29...@blueyonder.co.uk Subject: [digikam] [Bug 406809]digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes onstartup. https://bugs.kde.org/show_bug.cgi?id=406809 --- Comment #10 from Maik Qualmann --- Somehow you started 2 digiKam instances at the same time, if I interpret it correctly in the log. The reason is that the table column "manualOrder" already exists. I suspect that you have tested beta version of digiKam 5.x.x and now the database is failing to update. It's best to move "C:\Users\Sean\Pictures\digikam4.db" to a safe location and digiKam will create a new database. Later you can use the migration tool in digiKam to copy the old digikam4.db into the new one. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406809] digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=406809 --- Comment #9 from Sean O'Neill --- Created attachment 122421 --> https://bugs.kde.org/attachment.cgi?id=122421=edit Windows crash report - -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406809] digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=406809 --- Comment #8 from Sean O'Neill --- Created attachment 122420 --> https://bugs.kde.org/attachment.cgi?id=122420=edit Debug log -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406809] digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=406809 Sean O'Neill changed: What|Removed |Added OS|Linux |MS Windows CC||aobr29...@blueyonder.co.uk --- Comment #6 from Sean O'Neill --- Cannot upgrade from Digikam 5.8 to version 6.2.0 64-bit. Get error message: "Failed to update the database schema from version 9 to version 10". Then program shuts down. Have tried to uninstall Digikam entirely several times, but same message displays each time and problem persist. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408550] Applet unable to display emoticons in Wi-Fi SSID
https://bugs.kde.org/show_bug.cgi?id=408550 --- Comment #4 from Sean McCully --- (In reply to Jan Grulich from comment #3) > This seem to work for me, when I create a hotspot on my phone with emojis in > the SSID, then they are correctly displayed in both the applet and nmcli. Interesting... Thanks for the reply! Not really sure how to check my own environment's differences against yours. my bash version is '5.0.3(1)-release' and when I attempt to manually do this: printf '\U1F984\n' the output is still a square. Anyone know of the first place I should look? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408550] Applet unable to display emoticons in Wi-Fi SSID
https://bugs.kde.org/show_bug.cgi?id=408550 --- Comment #2 from Sean McCully --- Created attachment 121703 --> https://bugs.kde.org/attachment.cgi?id=121703=edit nmcli output -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 408550] New: Applet unable to display emoticons in Wi-Fi SSID
https://bugs.kde.org/show_bug.cgi?id=408550 Bug ID: 408550 Summary: Applet unable to display emoticons in Wi-Fi SSID Product: plasma-nm Version: 5.15.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: seancmccu...@gmail.com Target Milestone: --- Created attachment 120764 --> https://bugs.kde.org/attachment.cgi?id=120764=edit View from Android on left, view from applet on right SUMMARY If a wifi SSID contains emoticons, then they won't appear properly. STEPS TO REPRODUCE 1. Create a wifi SSID with emoticons in the name. 2. Bring up the applet while in range. OBSERVED RESULT It doesn't show the emoticons EXPECTED RESULT It does shot the emoticons SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] [PATCH] Fix missing kevent_qos syscall (macOS 10.11)
https://bugs.kde.org/show_bug.cgi?id=383723 --- Comment #31 from Sean --- Confirmed fixed in 3.14rc2. Though it still can't launch TextEdit, for which I've created: https://bugs.kde.org/show_bug.cgi?id=399504 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399504] New: valgrind 3.14rc2 is unable to launch TextEdit.app on macOS 10.12.6
https://bugs.kde.org/show_bug.cgi?id=399504 Bug ID: 399504 Summary: valgrind 3.14rc2 is unable to launch TextEdit.app on macOS 10.12.6 Product: valgrind Version: 3.14 SVN Platform: Other OS: OS X Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: cwat...@cam.org Target Milestone: --- Created attachment 115480 --> https://bugs.kde.org/attachment.cgi?id=115480=edit valgrind output running TextEdit SUMMARY valgrind 3.14rc2 is unable to launch TextEdit.app on macOS 10.12.6 STEPS TO REPRODUCE 1. just issue: valgrind /Applications/TextEdit.app OBSERVED RESULT - various text is output (attached), most notably: ==10558== Thread 2: ==10558== Invalid read of size 4 ==10558==at 0x1077A52B1: ??? (in /usr/lib/system/libsystem_pthread.dylib) ==10558==by 0x1077A507C: ??? (in /usr/lib/system/libsystem_pthread.dylib) ==10558== Address 0x18 is not stack'd, malloc'd or (recently) free'd ==10558== ==10558== ==10558== Process terminating with default action of signal 11 (SIGSEGV) ==10558== Access not within mapped region at address 0x18 ==10558==at 0x1077A52B1: ??? (in /usr/lib/system/libsystem_pthread.dylib) ==10558==by 0x1077A507C: ??? (in /usr/lib/system/libsystem_pthread.dylib) then the memcheck-amd64-darwin process crashes, see attached backtrace. EXPECTED RESULT - to be able to launch TextEdit, probably the simplest Cocoa application. SOFTWARE VERSIONS macOS 10.12.6 (16G1510) valgrind 3.14rc2 ADDITIONAL INFORMATION - Maybe related to https://bugs.kde.org/show_bug.cgi?id=372779 ? - I was able to run ls & cat with valgrind, so it's not totally broken - Calculator.app fails in the same way. - I suppose it could be identifying a real bug, but TextEdit is pretty simple... and one supposes these days that Apple uses ASan & TSan... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383723] [PATCH] SIGILL failure with ud2 opcode _dispatch_kq_init (in /usr/lib/system/libdispatch.dylib) (macOS)
https://bugs.kde.org/show_bug.cgi?id=383723 Sean <cwat...@cam.org> changed: What|Removed |Added CC||cwat...@cam.org --- Comment #28 from Sean <cwat...@cam.org> --- I just ran into this _dispatch_kq_init bug too (in valgrind 3.13 on macOS 10.12.6). I don't have much to add except: you don't need anything as complex as a Qt app, you can reproduce trying valgrind against TextEdit.app, which is a pretty basic Cocoa app, i.e.: $ valgrind /Applications/TextEdit.app -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 --- Comment #18 from Sean Bolton <s...@smbolton.com> --- Yes, the krita-4.0.0-x86_64.appimage is working on my Slackware 14.2-current system. Checking carefully with ldd, I see none of the 'in-AppImage, out-of-AppImage, in-AppImage' linkage that resulted in the previous breakage. Slackware does not set QT_PLUGIN_PATH. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391448] New: Toolbar disappeared
https://bugs.kde.org/show_bug.cgi?id=391448 Bug ID: 391448 Summary: Toolbar disappeared Product: krita Version: 3.3.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: fatter.wario5...@gmail.com Target Milestone: --- I was using krita and the toolbar with all the paint tools disappeared, i tried looking through all the menus to find a way to get it back but couldn't find anything, i tried to do a full reinstall and it was still missing -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 379810] qca compilation fails with openssl 1.1
https://bugs.kde.org/show_bug.cgi?id=379810 Sean Harmer <s...@theharmers.co.uk> changed: What|Removed |Added CC||s...@theharmers.co.uk -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 --- Comment #16 from Sean Bolton <s...@smbolton.com> --- I'm sure this is no surprise, but the krita-3.3.2-x86_64.appimage still fails to work on my Slackware 14.2-current system, failing for the exact same reason. If the libpng package is being installed as a dependency of libpng-devel, why does libpng16.so.16 not get included in the AppImage? Is it maybe because libpng12.so.2 is included, and the build script thinks that satisfies the need for libpng16? @cpel, if you do pursue this standard AppImage build tool, you might look at how the pax-utils 'lddtree' [1] tool scans for library dependencies, which could relieve the packager of the necessity of listing the dependencies by hand. [1] https://github.com/gentoo/pax-utils -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385780] Speed Effect is not saved after editing
https://bugs.kde.org/show_bug.cgi?id=385780 Sean Porterfield <bgz...@sf.porterfield.net> changed: What|Removed |Added CC||bgz...@sf.porterfield.net --- Comment #1 from Sean Porterfield <bgz...@sf.porterfield.net> --- I've been having problems like this with Version 17.04.3 from PPA on Ubuntu 16.04 LTS. PPA is not offering me an upgrade, but apparently it wouldn't resolve the issue, based on this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 --- Comment #2 from Sean Bolton <s...@smbolton.com> --- I just confirmed that this same problem occurs with krita-3.2.0-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382944] New: krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"'
https://bugs.kde.org/show_bug.cgi?id=382944 Bug ID: 382944 Summary: krita-3.1.4-x86_64.appimage fails to run with 'could not find or load the Qt platform plugin "xcb"' Product: krita Version: 3.1.4 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: s...@smbolton.com Target Milestone: --- Attempting to run krita-3.1.4-x86_64.appimage on my Slackware 14.2-current x86_64 system fails with: ``` This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: minimal, offscreen, xcb. Reinstalling the application may fix this problem. Aborted ``` Running 'QT_DEBUG_PLUGINS=1 ./krita-3.1.4-x86_64.appimage' reveals the following: ``` QLibraryPrivate::loadPlugin failed on "/tmp/.mount_LTAl95/usr/bin/plugins/platforms/libqxcb.so" : "Cannot load library /tmp/.mount_LTAl95/usr/bin/plugins/platforms/libqxcb.so: (./lib/libz.so.1: version `ZLIB_1.2.9' not found (required by /usr/lib64/libpng16.so.16))" ``` So the problem is that libqxcb.so (which is contained in the AppImage) links to libpng16.so.16 (which is *not* in the AppImage), which links to libz.so.1 (which *is* in the AppImage). I am not familiar with AppImage, but I am surprised it does not contain some sort of automated check in the build process, to prevent just this situation where linked-to libraries outside the AppImage link to libraries that can be found inside the AppImage. The in-out-in linkage situation is an open door to this sort of version mismatch. The fix would be to include libpng16.so.16 in the AppImage. A workaround on my system is to link to an older version of libpng16.so.16: ``` mkdir /home/smbolton/t ln -s /usr/lib64/libpng16.so.16.27.0 /home/smbolton/t/libpng16.so.16 LD_LIBRARY_PATH=/home/smbolton/t ./krita-3.1.4-x86_64.appimage ``` Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #15 from Sean V Kelley <sea...@posteo.de> --- Same issue: OpenSUSE Tumbleweed dolphin 16.12.3 Laptop: 4K display Attached Display: 4K display Using hidpi scaling factor of 2 in KDE Only able to open a single file using Dolphin on the Attached Display. Further attempts to open another file on the Attached Display is blocked. Only work around, use context menu each time I open a file OR close Dolphin, relaunch Dolphin and open file. However, on the laptop display when attached or not attached to the external 4K display I can freely open files, multiple. This is super annoying. Sean -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 Sean V Kelley <sea...@posteo.de> changed: What|Removed |Added CC||sea...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 378100] New: Amarok crashes at launch
https://bugs.kde.org/show_bug.cgi?id=378100 Bug ID: 378100 Summary: Amarok crashes at launch Product: amarok Version: 2.8.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: sean.umph...@gmail.com Target Milestone: 2.9 Application: amarok (2.8.0) Qt Version: 5.8.0 Frameworks Version: 5.32.0 Operating System: Linux 4.10.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I just logged into my KDE Plasma system and ran the Amarok application. Application did not even start and crash reporting assistant appeared. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [KCrash Handler] #6 0x7f14fdd1e306 in __strcmp_sse2 () at /usr/lib/libc.so.6 #7 0x7f14ed60468d in lh_insert () at /usr/lib/libcrypto.so.1.0.0 #8 0x7f14ed533a99 in OBJ_NAME_add () at /usr/lib/libcrypto.so.1.0.0 #9 0x7f14d80c5ea5 in () at /usr/lib/libssl.so.1.1 #10 0x7f14fc906399 in __pthread_once_slow () at /usr/lib/libpthread.so.0 #11 0x7f14d7dc9069 in CRYPTO_THREAD_run_once () at /usr/lib/libcrypto.so.1.1 #12 0x7f14d80c608b in OPENSSL_init_ssl () at /usr/lib/libssl.so.1.1 #13 0x7f14d876676d in () at /usr/lib/libimobiledevice.so.6 #14 0x7f14fc906399 in __pthread_once_slow () at /usr/lib/libpthread.so.0 #15 0x7f150109434a in call_init.part () at /lib64/ld-linux-x86-64.so.2 #16 0x7f150109445b in _dl_init () at /lib64/ld-linux-x86-64.so.2 #17 0x7f1501098908 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #18 0x7f14fddc3c74 in _dl_catch_error () at /usr/lib/libc.so.6 #19 0x7f15010980a9 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #20 0x7f14f7ef6f86 in () at /usr/lib/libdl.so.2 #21 0x7f14fddc3c74 in _dl_catch_error () at /usr/lib/libc.so.6 #22 0x7f14f7ef7669 in () at /usr/lib/libdl.so.2 #23 0x7f14f7ef7022 in dlopen () at /usr/lib/libdl.so.2 #24 0x7f14fe557e10 in () at /usr/lib/libQtCore.so.4 #25 0x7f14fe552025 in () at /usr/lib/libQtCore.so.4 #26 0x7f14fe5526bb in () at /usr/lib/libQtCore.so.4 #27 0x7f14ff8394b0 in KPluginLoader::load() () at /usr/lib/libkdecore.so.5 #28 0x7f14ff839798 in KPluginLoader::factory() () at /usr/lib/libkdecore.so.5 #29 0x7f1500c26338 in Plugins::PluginManager::createFactory(KPluginInfo const&) () at /usr/lib/libamaroklib.so.1 #30 0x7f1500c27de3 in Plugins::PluginManager::createFactories(QString const&) () at /usr/lib/libamaroklib.so.1 #31 0x7f1500c28952 in Plugins::PluginManager::init() () at /usr/lib/libamaroklib.so.1 #32 0x7f1500c290d5 in Plugins::PluginManager::PluginManager(QObject*) () at /usr/lib/libamaroklib.so.1 #33 0x7f1500c291d8 in Plugins::PluginManager::instance() () at /usr/lib/libamaroklib.so.1 #34 0x7f1500c190d9 in MainWindow::MainWindow() () at /usr/lib/libamaroklib.so.1 #35 0x7f1500bfde43 in App::continueInit() () at /usr/lib/libamaroklib.so.1 #36 0x7f1500bff03c in App::App() () at /usr/lib/libamaroklib.so.1 #37 0x004085c8 in () #38 0x7f14fdcbe511 in __libc_start_main () at /usr/lib/libc.so.6 #39 0x0040a20a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 Sean <seanbean...@gmx.de> changed: What|Removed |Added Platform|Other |Kubuntu Packages --- Comment #11 from Sean <seanbean...@gmx.de> --- Ok, now it is working - you have to change the theme for the symbols globally (and not for the whole screens). Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 --- Comment #8 from Sean <seanbean...@gmx.de> --- Created attachment 104462 --> https://bugs.kde.org/attachment.cgi?id=104462=edit Kmymoney Icons -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 --- Comment #9 from Sean <seanbean...@gmx.de> --- I use Kmymoney in german -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 --- Comment #6 from Sean <tammo.l...@mailbox.org> --- I have changed to oxygen theme globally but icons still missing -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 --- Comment #4 from Sean <tammo.l...@mailbox.org> --- Why is this bug "poorly described", what informations do you need? But if I get it right, it will be fixed in version 5. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 377119] New: Icons still missing
https://bugs.kde.org/show_bug.cgi?id=377119 Bug ID: 377119 Summary: Icons still missing Product: kmymoney4 Version: 4.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: tammo.l...@mailbox.org Target Milestone: --- There are still icons in the navigation missing - for example the "Categories"-Icon -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377117] New: No Geolocation functionality anymore
https://bugs.kde.org/show_bug.cgi?id=377117 Bug ID: 377117 Summary: No Geolocation functionality anymore Product: digikam Version: 4.14.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation Assignee: digikam-de...@kde.org Reporter: seanbean...@gmx.de Target Milestone: --- There ist no geolocation functionality anymore. It worked in older versions but now it is missing! No tab, no editor etc. This is a very important feature. -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 373028] Rocs is not responding
https://bugs.kde.org/show_bug.cgi?id=373028 --- Comment #2 from Sean <s...@fluidandsolidearth.net> --- ALSO; PS: no usable output when started from command line - i.e. no error message. -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 373028] Rocs is not responding
https://bugs.kde.org/show_bug.cgi?id=373028 --- Comment #1 from Sean <s...@fluidandsolidearth.net> --- > the top is frozen (green circle). Orange, sorry. -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 373028] Rocs is not responding
https://bugs.kde.org/show_bug.cgi?id=373028 Sean <s...@fluidandsolidearth.net> changed: What|Removed |Added CC||s...@fluidandsolidearth.net -- You are receiving this mail because: You are watching all bug changes.
[Rocs] [Bug 373028] New: Rocs is not responding
https://bugs.kde.org/show_bug.cgi?id=373028 Bug ID: 373028 Summary: Rocs is not responding Product: Rocs Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: visual graph editor Assignee: rocs-bugs-n...@kde.org Reporter: s...@fluidandsolidearth.net Target Milestone: --- Created attachment 102496 --> https://bugs.kde.org/attachment.cgi?id=102496=edit Graphical representation of Bug. ## Output of uname -a Linux glassplanet 4.8.9-1-MANJARO #1 SMP PREEMPT Fri Nov 18 19:17:47 UTC 2016 x86_64 GNU/Linux ## OS : KDE/Manjaro branch of Netrunner ## ROCS version 2.1.50; KDE Framework 5.28.0 QT 5.7.0, xcb Window System ## Problem In the visual graph editor, the application doesn't respond to mouse events. ## Steps to reproduce: 1. Start Rocs 2. Make a graph with 6+ nodes 3. Change the edge style (e.g. a new color) 4. Try to add a new edge. - Click on one node - Drag to another node At this point, some nodes will be "frozen" that the edge will not be added. You can't even move the "frozen" node around. See the attached picture, starting from the root (node 0) the first node at the top is frozen (green circle). I can add edges among the bottom nodes as i wish, but the first top node doesn't respond. Clicking on it also doesn't bring the orange highlighting around it. This is a bit of inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 370242] "Geldinstitute": "Konten ohne zugewiesene Geldinstitute" cannot delete
https://bugs.kde.org/show_bug.cgi?id=370242 --- Comment #7 from Sean <seanbean...@gmx.de> --- This doesn't change anything. If I configure "Geschlossene Konten nicht anzeigen" in the Kmymoney-Configuration than this special account "Konten ohne zugewiesene Geldinstitute" is not shown. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 370242] "Geldinstitute": "Konten ohne zugewiesene Geldinstitute" cannot delete
https://bugs.kde.org/show_bug.cgi?id=370242 --- Comment #5 from Sean <seanbean...@gmx.de> --- consistency check: same result configure KMyMoney: no one is checked If I look under accounts there is the same number of accounts compared the number under institutions. @Thomas: so if everything is ok what can I do, because I cant find the account with no institution. Maybe I understand you wrong... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365014] All windows hide on repeating desktop click
https://bugs.kde.org/show_bug.cgi?id=365014 Sean V Kelley <sea...@posteo.de> changed: What|Removed |Added CC||sea...@posteo.de --- Comment #18 from Sean V Kelley <sea...@posteo.de> --- Same issue for me on Arch: Qt 5.7.0-1 KDE 5.7.2 Plasma 5.7.2 Sean -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 362550] New: Community, Forum, Userbase, and Techbase timeout on IPv6
https://bugs.kde.org/show_bug.cgi?id=362550 Bug ID: 362550 Summary: Community, Forum, Userbase, and Techbase timeout on IPv6 Product: www.kde.org Version: unspecified Platform: Other URL: https://community.kde.org/Main_Page OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: s...@sdoconnell.net When accessing any of the following sites from a computer with dual stack IPv4/IPv6, the connection times out before the page is loaded: https://community.kde.org/ https://forum.kde.org/ https://userbase.kde.org/ https://techbase.kde.org/ If IPv6 is disabled, or if the following entries are added to the local hosts file (forcing connectivity via IPv4) the sites load normally: 192.230.74.89 forum.kde.org 192.230.74.89 community.kde.org 192.230.74.89 cdn.kde.org 192.230.74.99 userbase.kde.org 192.230.74.99 techbase.kde.org Reproducible: Always Steps to Reproduce: 1. Configure computer with dual stack IPv4/IPv6 connectivity, set to prefer IPv6. 2. Access one of the URLs above. Actual Results: Page timeouts before loading. Expected Results: Page loads normally. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 362207] New: Cannot edit mount points - OK / Apply button missing
https://bugs.kde.org/show_bug.cgi?id=362207 Bug ID: 362207 Summary: Cannot edit mount points - OK / Apply button missing Product: partitionmanager Version: 1.2.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: kde.b...@moteprime.org There is no way to apply changes to an edited mount point. Reproducible: Always Steps to Reproduce: 1. Start Partition Manager 2. Select a partition with a mount point. 3. Right click and select "Unmount" to unmount it. 4. Right click and select "Edit Mount Point" to edit the mount point. 5. The edit mount point dialog is displayed. Actual Results: You can edit the mount point but there is no way to accept the changes. The only way to close the dialog is with the close button (red "X" at top right) which cancels the change. Expected Results: There should be an OK or Apply button in this dialog. I note that the version selected for Kubuntu 16.04 LTS is 1.2.1, which is well behind the curve. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362167] Allow user to turn off animated carousel of favored applications.
https://bugs.kde.org/show_bug.cgi?id=362167 Sean Ellis <kde.b...@moteprime.org> changed: What|Removed |Added Summary|Allow some user |Allow user to turn off |configuration |animated carousel of ||favored applications. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362163] Cannot sort application lists
https://bugs.kde.org/show_bug.cgi?id=362163 --- Comment #1 from Sean Ellis <kde.b...@moteprime.org> --- I note that the "apparently random order" is in fact popularity. This wasn't obvious as the first page of applications all have 5 visible stars. It would still be good to sort on different criteria, though. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362167] Allow some user configuration
https://bugs.kde.org/show_bug.cgi?id=362167 Sean Ellis <kde.b...@moteprime.org> changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362166] When configuring connection, populate fields with DHCP information
https://bugs.kde.org/show_bug.cgi?id=362166 --- Comment #1 from Sean Ellis <kde.b...@moteprime.org> --- Ironically, I omitted the word "blank" from "completely blank page of settings" in the original description. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 362166] New: When configuring connection, populate fields with DHCP information
https://bugs.kde.org/show_bug.cgi?id=362166 Bug ID: 362166 Summary: When configuring connection, populate fields with DHCP information Product: plasma-nm Version: 5.5.5 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: editor Assignee: lu...@kde.org Reporter: kde.b...@moteprime.org CC: jgrul...@redhat.com On installation, Network Manager defaults the connection to DHCP. This gathers lots of useful information - gateways, DNS settings, etc. If I then decide to change the network address (I have a reserved static range that I use for machines that act as servers), the connection editor presents me with a completely page of settings. It would be very helpful to fill these in with the parameters already supplied by DHCP. Reproducible: Always Steps to Reproduce: 1. Open Networks from the system tray. 2. Select the "Configure network connections" icon - Connection Editor launches 3. Right click on a connection and select "Edit..." 4. Select the "IPv4" tab 5. Select method "manual" Actual Results: The fields for DNS server and current IP address are left blank for you to fill in. Expected Results: These fields should be auto-filled with the DHCP-supplied information (if available) for editing. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362163] New: Cannot sort application lists
https://bugs.kde.org/show_bug.cgi?id=362163 Bug ID: 362163 Summary: Cannot sort application lists Product: Discover Version: 5.6.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kde.b...@moteprime.org When browsing available software packages, they are presented in an apparently random order. It is possible to sort the list of installed packages by name, but not the available packages. It would be good to allow them to be sorted by name, popularity, etc. Reproducible: Always Steps to Reproduce: 1. Open Discover 2. Select a category 3. View list of available packages Actual Results: Packages are displayed in a predefined by rather strange order Expected Results: Allow sorting by name / popularity / etc. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362140] Discover don't find anything on search
https://bugs.kde.org/show_bug.cgi?id=362140 Sean Ellis <kde.b...@moteprime.org> changed: What|Removed |Added CC||kde.b...@moteprime.org --- Comment #1 from Sean Ellis <kde.b...@moteprime.org> --- I also see this (Kubuntu 16.04, 64 bit). Example: select the "Systems and Settings" category. The icon for "Synaptic Package Manager" is shown in the first row of displayed applications. Despite it clearly being present, it cannot be found by name. In the search box, type "package" - zero results. Type "Synaptic" - zero results. Type "Syn" - zero results. Curiously, if you type "Sy", I get four results, BCache Monitor, plasma5-applets-system-panel, bumblebee-indicator and Lackadaisy. This last one is not even in the selected category. -- You are receiving this mail because: You are watching all bug changes.
