[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #5 from Robert --- Created attachment 150474 --> https://bugs.kde.org/attachment.cgi?id=150474&action=edit journalctl log, filtered for plasmashell The following line was added to /etc/environment: QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #4 from Robert --- Comment on attachment 150473 --> https://bugs.kde.org/attachment.cgi?id=150473 journalctl log, filtered for kwin_wayland The following line was added to /etc/environment: QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 --- Comment #3 from Robert --- Created attachment 150473 --> https://bugs.kde.org/attachment.cgi?id=150473&action=edit journalctl log, filtered for kwin_wayland following line was added to /etc/environment QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454086] External USB-C display stop working after upgrading to 5.24.90
https://bugs.kde.org/show_bug.cgi?id=454086 --- Comment #42 from Robert --- Are we sure https://bugs.kde.org/show_bug.cgi?id=456369 is a duplicate of this one? I can't find any entries in the uploaded logs that match the ones I attached to the other bug report. Also, the issue here seems to be entirely non functional usb-c monitors. In my experience, the monitor works fine (connected before boot). Both external monitor and built in fail after disconnecting it, until reboot. The log entry that caught my eye was: plasmashell[1693]: requesting unexisting screen 0 There are a lot of those, everytime I reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456369] New: Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery
https://bugs.kde.org/show_bug.cgi?id=456369 Bug ID: 456369 Summary: Plasma Shell 5.25: Black screen when disconnecting external monitor with no hope of recovery Product: plasmashell Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: robertdeja...@tutanota.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 150427 --> https://bugs.kde.org/attachment.cgi?id=150427&action=edit Some journalctl entries from the previous boot (that got stuck because of this issue) After upgrading to Plasma Desktop 5.25, disconnecting a monitor attached through USB-C (HDMI Alt Mode) results in a black screen. Reconnecting it does not restore video. The only thing that helps is to force a reboot. I cannot try a direct HDMI connection, because my laptop doesn't have one. It happens consistently since upgrading the Plasma Desktop. Version 5.24 worked fine. I have tried a Gnome session to make sure nothing else is causing this issue. In Gnome it works fine. STEPS TO REPRODUCE 1. Start a Plasma Shell session with an external monitor connected using an USB-C dock 2. Disconnect either the monitor, or the whole dock 3. Laptop screen does not turn on 4. Reconnect the external monitor / dock 5. No image on either monitor 6. Try to switch to a virtual terminal (ctrl-alt-f3) 7. Still no picture Black screen, no matter what I do Laptop screen turns on when disconnecting the monitor, external screen shows desktop when plugging it back in. SOFTWARE/OS VERSIONS Linux version: 5.18.9 KDE Plasma Version: 5.25.0 / 5.25.1 / 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5+kde+r167 Mesa Version: 22.1.3 Hardware: Dell XPS 13 9310 2 in 1 Intel Core i7 1165G7 Iris XE Graphics -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455466] Google Chrome crashes Latte Dock
https://bugs.kde.org/show_bug.cgi?id=455466 Robert D changed: What|Removed |Added CC||rob...@robertdonat.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455466] Google Chrome crashes Latte Dock
https://bugs.kde.org/show_bug.cgi?id=455466 --- Comment #4 from Robert D --- Created attachment 150310 --> https://bugs.kde.org/attachment.cgi?id=150310&action=edit New crash information added by DrKonqi latte-dock (0.10.77) using Qt 5.15.5 Opened the add a widget selector to Latte Dock -- Backtrace (Reduced): #4 0x7f6eb4d8a1d4 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f6eb4db9ef0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f6eb4da2ffe in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f6eb4da67fe in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f6eb4dab211 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #20 from Robert Günzler --- I found that running kdenlive with firejail and supplying the following kendlive.local config removes the issue: blacklist /usr/share/fonts/noto-emoji Without this setting I see a similar font glitch to what Shawn describes, where the 'clip properties' panel is rendering text with emoji characters in places where there shouldn't be any... Maybe this is somehow related to https://bugreports.qt.io/browse/QTBUG-82311 ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Robert Strube changed: What|Removed |Added CC||rstr...@gmail.com --- Comment #87 from Robert Strube --- I'm also running into this issue. Every time my system wakes up from sleep the wallpaper settings completely reset to defaults. This also happens after a system restart. I don't do anything special with panels so I can't confirm if these would also reset. I run a multi-monitor configuration - this appears to be the common denominator. This is one of the most frustrating bugs I've encountered with Plasma so far. Problem existed on 5.24.5. I haven't tested with 5.25 yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455540] Unable to download from Settings with error "invalid number of concurrent streams"
https://bugs.kde.org/show_bug.cgi?id=455540 --- Comment #11 from Robert Gorajski --- You may have heard it, but Arch is a rolling relase distribution with very fast updates. What about openSUSE LEAP, Debian, etc. ?(In reply to Felix Fischer from comment #10) > Can confirm that just today on arch extra/qt5-base got an update to > 5.15.5+kde+r163-1 that fixed it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #5 from Robert Kratky --- Still present on: Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland The setting in ~/.config/kaccessrc is correct (and reflects the state of the respective checkbox in SystemSettings): [Keyboard] StickyKeys=true (This is the only thing that's stopping me from switching to Wayland. If there's a manual workaround, I'd love to know about it.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455542] System settings - cannot download anything from the Internet. Error: Download "...." failed, error: SETTINGS invalid number of concurrent streams
https://bugs.kde.org/show_bug.cgi?id=455542 Robert Gorajski changed: What|Removed |Added CC||robert.goraj...@gmail.com --- Comment #1 from Robert Gorajski --- Created attachment 149887 --> https://bugs.kde.org/attachment.cgi?id=149887&action=edit Error -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455542] New: System settings - cannot download anything from the Internet. Error: Download "...." failed, error: SETTINGS invalid number of concurrent streams
https://bugs.kde.org/show_bug.cgi?id=455542 Bug ID: 455542 Summary: System settings - cannot download anything from the Internet. Error: Download "" failed, error: SETTINGS invalid number of concurrent streams Product: systemsettings Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: robert.goraj...@gmail.com Target Milestone: --- SUMMARY *** When you start System Settings, you can't download anything from the Internet, like for example: Icons (applies to all the new things I want to download from the Internet in System settings: Fonts, Global Appearance and all the rest). *** STEPS TO REPRODUCE 1. Open System Settings 2. Click Icons (for example) 3. Click Download new icons 4. Select any new icons, open them and then click upload in the upper right corner of the window. 5. The "An error has occurred" window opens. Error message: "Downloading "..." failed, error: SETTINGS invalid number of concurrent streams" OBSERVED RESULT "Downloading "..." failed, error: SETTINGS invalid number of concurrent streams" EXPECTED RESULT New icons are downloaded. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.4 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION 1. As I wrote above, it applies to all things to download from the Internet in System Settings 2. The messages I described may be a little different in English. I use the openSUSE version with Polish - I translated the messages into English myself. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438991] Setting a task switcher shortcut involving shift+tab (backtab) isn't working continuously
https://bugs.kde.org/show_bug.cgi?id=438991 Robert Czechowski changed: What|Removed |Added CC||roczech+kdeb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455236] New: Recording shortcut involving Shift-Tab records an invalid shortcut
https://bugs.kde.org/show_bug.cgi?id=455236 Bug ID: 455236 Summary: Recording shortcut involving Shift-Tab records an invalid shortcut Product: systemsettings Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: roczech+kdeb...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Recording a shortcut involving Shift-Tab (e.g. Ctrl+Shift+Tab for "Walk Through Windows (Reverse)") records this shortcut as "Ctrl+Shift+Tab" and this shortcut then does not work. However, when I edit `~/.config/kglobalshortcutsrc` so the shortcut reads "Ctrl+Shift+Backtab" (_Back_tab instead of Tab), the shortcut will work. I guess Systemsetting is expected to record this shortcut as "Ctrl+Shift+Backtab" instead of "Ctrl+Shift+Tab", here. STEPS TO REPRODUCE 1. Open Systemsettings -> Shortcuts -> Shortcuts -> KWin 2. Change "Walk Through Windows" to Ctrl+Tab, deactivate the Default shortcut Alt+Tab 3. Change "Walk Through Windows (Reverse)" to Ctrl+Shift+Tab, deactivate the Default shortcut Alt+Shift+Backtab 4. Log out and log in again (Changing "Walk Through Windows" does not fully work without new login) 5. Press Ctrl+Shift+Tab OBSERVED RESULT Nothing happens EXPECTED RESULT (Reverse) Window switching should occur. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 Robert Barat (volt4ire) changed: What|Removed |Added CC||rwba...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453799] New: KDE Connect setting custom commands
https://bugs.kde.org/show_bug.cgi?id=453799 Bug ID: 453799 Summary: KDE Connect setting custom commands Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: --- Application: kdeconnect-settings (22.04.0) Qt Version: 5.15.2 Frameworks Version: 5.93.0 Operating System: Linux 5.17.5-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was trying to add a custom command, and when I open the settings for that it crashes everytime. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDE Connect Settings (kdeconnect-settings), signal: Segmentation fault [KCrash Handler] #4 0x7fc47911dd58 in std::__uniq_ptr_impl >::_M_ptr (this=) at /usr/include/c++/12/bits/unique_ptr.h:191 #5 std::unique_ptr >::get (this=) at /usr/include/c++/12/bits/unique_ptr.h:462 #6 std::unique_ptr >::operator-> (this=) at /usr/include/c++/12/bits/unique_ptr.h:455 #7 qGetPtrHelper > const> (ptr=...) at /usr/include/qt5/QtCore/qglobal.h:1143 #8 KSycocaEntry::d_func (this=) at /usr/src/debug/kservice-5.93.0-1.2.x86_64/src/sycoca/ksycocaentry.h:139 #9 KSycocaEntry::property (this=0x0, name=...) at /usr/src/debug/kservice-5.93.0-1.2.x86_64/src/sycoca/ksycocaentry.cpp:104 #10 0x7fc468b1f425 in KdeConnectPluginKcm::KdeConnectPluginKcm (this=, parent=, args=..., componentName=..., this=, parent=, args=..., componentName=...) at /usr/src/debug/kdeconnect-kde-22.04.0-1.2.x86_64/kcmplugin/kdeconnectpluginkcm.cpp:26 #11 0x7fc468b29339 in RunCommandConfig::RunCommandConfig (args=..., parent=0x5645ddc7b3c0, this=0x7fc464011bb0) at /usr/src/debug/kdeconnect-kde-22.04.0-1.2.x86_64/plugins/runcommand/runcommand_config.cpp:29 #12 KPluginFactory::createInstance (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:875 #13 0x7fc47aafe5c3 in KPluginFactory::create (this=0x5645ddd4ceb0, iface=0x7fc4790be9a0 "KCModule", parentWidget=0x5645ddc7b3c0, parent=0x5645ddc7b3c0, args=..., keyword=...) at /usr/src/debug/kcoreaddons-5.93.0-1.2.x86_64/src/lib/plugin/kpluginfactory.cpp:232 #14 0x7fc47abdd015 in KPluginFactory::create (args=..., parent=0x5645ddc7b3c0, keyword=..., this=0x5645ddd4ceb0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:936 #15 KCModuleLoader::loadModule (metaData=..., parent=0x5645ddc7b3c0, args=...) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleloader.cpp:98 #16 0x7fc47abdfd0d in KCModuleProxyPrivate::loadModule (this=0x5645ddd90e50) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleproxy.cpp:119 #17 0x7fc47abe0338 in KCModuleProxy::realModule (this=) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kcmoduleproxy.cpp:59 #18 0x7fc47abf2f7c in PluginDelegate::configure (this=this@entry=0x5645ddc40da0, index=...) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kpluginwidget.cpp:486 #19 0x7fc47abf372a in PluginDelegate::slotConfigureClicked (this=0x5645ddc40da0) at /usr/src/debug/kcmutils-5.93.0-1.2.x86_64/src/kpluginwidget.cpp:471 #20 0x7fc4799e0def in QtPrivate::QSlotObjectBase::call (a=0x7ffcb5d38880, r=0x5645ddc40da0, this=0x5645ddc81640) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x5645ddc8c900, signal_index=9, argv=0x7ffcb5d38880) at kernel/qobject.cpp:3886 #22 0x7fc4799da0cf in QMetaObject::activate (sender=sender@entry=0x5645ddc8c900, m=m@entry=0x7fc47aa6e180 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffcb5d38880) at kernel/qobject.cpp:3946 #23 0x7fc47a646152 in QAbstractButton::clicked (this=this@entry=0x5645ddc8c900, _t1=) at .moc/moc_qabstractbutton.cpp:308 #24 0x7fc47a6463ba in QAbstractButtonPrivate::emitClicked (this=0x5645ddd38060) at widgets/qabstractbutton.cpp:415 #25 0x7fc47a647f48 in QAbstractButtonPrivate::click (this=0x5645ddd38060) at widgets/qabstractbutton.cpp:408 #26 0x7fc47a648167 in QAbstractButton::mouseReleaseEvent (this=0x5645ddc8c900, e=0x7ffcb5d38e00) at widgets/qabstractbutton.cpp:1044 #27 0x7fc47a595f48 in QWidget::event (this=0x5645ddc8c900, event=0x7ffcb5d38e00) at kernel/qwidget.cpp:9020 #28 0x7fc47a55437e in QApplicationPrivate::notify_helper (this=this@entry=0x5645dd8cf270, receiver=receiver@entry=0x5645ddc8c900, e=e@entry=0x7ffcb5d38e00) at kernel/qapplication.cpp:3632 #29 0x7fc47a55c8c2 in QApplication::notify (this=, receiver=0x5645ddc8c900, e=) at kernel/qapplication.cpp:3076 #30 0x7fc4799a9988 in QCoreApplication::notifyInternal2 (receiver=0x5645ddc8c900, event=0x7ffcb5d38e00) at kernel/qcoreapplication.cpp:1064
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 Robert Günzler changed: What|Removed |Added CC||r+...@gnzler.io --- Comment #19 from Robert Günzler --- I experience the same problem using the latest AppImage bundle: kdenlive-master-212-linux-64-gcc.AppImage This is made even worse when kdenlive uses wayland, since it crashes the compositor -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453430] New: Dolphin crashed after closing tab
https://bugs.kde.org/show_bug.cgi?id=453430 Bug ID: 453430 Summary: Dolphin crashed after closing tab Product: dolphin Version: 22.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rob...@axium.co.nz CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.4.0-107-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Dolphin had 4 different tabs open and closing the fourth tab was the trigger. Not sure what made it special, but it was largely full of executable binary files. Closing any other tab first would allow that one to close without issue and closing ther others seemed to work reliably. Sometimes closing the tab in question would work without crashing, in which case opening another tab and navigating to the folder allowed it to again be reproduced once closed. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 57051] [New LWP 57052] [New LWP 57053] [New LWP 57054] [New LWP 57055] [New LWP 57056] [New LWP 57057] [New LWP 57659] [New LWP 57678] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc86d2f2508 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 __preamble__ [Current thread is 1 (Thread 0x7fc86a6bf9c0 (LWP 57049))] Thread 10 (Thread 0x7fc8437fe700 (LWP 57678)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fc86f581975 in QBasicMutex::lockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc8719e176e in QMutexLocker::QMutexLocker (m=, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:238 #3 UpdateItemStatesThread::run (this=0x55bea85778c0) at ./src/views/versioncontrol/updateitemstatesthread.cpp:33 #4 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fc843fff700 (LWP 57659)): [KCrash Handler] #4 0x in ?? () #5 0x7fc8719e186f in UpdateItemStatesThread::run (this=0x55bea8605ca0) at ./src/views/versioncontrol/updateitemstatesthread.cpp:41 #6 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fc859ffb700 (LWP 57057)): #0 __GI___libc_read (nbytes=16, buf=0x7fc859ffa9d0, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=22, buf=0x7fc859ffa9d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fc86d2edb2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc86d2a4ebe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc86d2a5312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc86d2a54a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc86f7c265b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc86f76687b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc86f580442 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fc85a7fc700 (LWP 57056)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fc85a7fbb50, clockid=, expected=0, futex_word=0x55bea7e186f0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc85a7fbb50, clockid=, mutex=0x55bea7e186a0, cond=0x55bea7e186c8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55bea7e186c8, mutex=0x55bea7e186a0, abstime=0x7fc85a7fbb50) at pthread_cond_wait.c:656 #3 0x7fc86f587618 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc86f584b21 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc86f581623 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc86dd19609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fc86f1fe163 in clone () at ../sysdeps/unix/sysv/li
[gwenview] [Bug 439519] Jpeg format converted to ".jpe"
https://bugs.kde.org/show_bug.cgi?id=439519 Robert Grasböck changed: What|Removed |Added CC||robert.grasbo...@gmail.com --- Comment #20 from Robert Grasböck --- (In reply to Ian Goddard from comment #17) > Workaroud: > System setting>Applications>File associations > Look up the enter jpeg in the filename search box. > The Filename Patterns list to the right has *.jpe as the first pattern in > the list. Select this, click Remove, click Apply. > It seems to solve the problem, or at least, so far, so good Thank you, that worked also for me! I was searching a while to come to this fix. Never, ever thought, that this problem has todo with file associations !?!? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453070] [Wayland] Night Color not working on Wayland session
https://bugs.kde.org/show_bug.cgi?id=453070 Robert Britton changed: What|Removed |Added CC||britto...@protonmail.com --- Comment #3 from Robert Britton --- I can third this issue. Like Behzad -- Night Color works just fine on X11, but it's completely broken on Wayland. I'm on Arch with a fully up-to-date system as of today 5/1. I can't say whether or not this happened before the current version of Plasma I'm on was released into Arch repositories; I've only started trying to use Wayland in the past week. Night Color doesn't work whatsoever for me on Wayland. It doesn't matter what activation time you set it to or what temperature you set it to adjust to, it just doesn't work. It's as if it doesn't exist. The Night Color widget can be toggled on or off, and it displays changes as such, but nothing happens. I AM NOT A DEVELOPER but from my troubleshooting I think this might have to do with the way monitor names are detected and tracked in Wayland versus X11. The other major issue with Wayland I've been having is that on my current user account, existing since January and whatever version of Plasma was available on Arch then, any changes I make to display settings don't get saved, either resolution or refresh rate. This means I have to re-set my monitor to output at 144 Hz every single time I start a Wayland session. I've tested pretty extensively with a test user I made this weekend, and that user doesn't have the settings-not-being-saved issue, but it does also have a broken Night Color. I use a single monitor with DVI. I think these two issues may possibly be related somehow. System info: Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz Memory: 15.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 running proprietary driver version 510.60.02 I'd be happy to provide more info if needed -- config files, etc. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 452964] New: Kate syntax coloring .xml containing space
https://bugs.kde.org/show_bug.cgi?id=452964 Bug ID: 452964 Summary: Kate syntax coloring .xml containing space Product: frameworks-syntax-highlighting Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: robertwish...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Created attachment 148347 --> https://bugs.kde.org/attachment.cgi?id=148347&action=edit Syntax color example In a user defined Kate .xml syntax file, an item containing a space does not process correctly, for example for binary append When the weakDeliminator attribute is used in the .xml file to instruct the parser to ignore space as a delimiter in the , as here, the above text in a document, for example, open file for binary append as f1 is not properly colored if preceded or succeeded by a space. All syntax coloring in the document for items is lost if the is delimited by space. STEPS TO REPRODUCE 1. Add for binary append to a Kate user-defined syntax file list. 2. Open Kate, add open file for binary append as f1 to an appropriate document. 3. OBSERVED RESULT for binary append is not colored EXPECTED RESULT for binary append should be colored SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: Fedora 36 beta (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.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 Robert David changed: What|Removed |Added CC||robert.david.public@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451022] New: Kwin crashed on mulitiple desktops
https://bugs.kde.org/show_bug.cgi?id=451022 Bug ID: 451022 Summary: Kwin crashed on mulitiple desktops Product: kwin Version: 5.24.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: robertdevasi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.24.2) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: when a window minimized from one Desktop and move to another - Unusual behavior I noticed: - Custom settings of the application: I'm using the maximize-to-new-virtual desktop kwin script The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 15012] [New LWP 15013] [New LWP 15014] [New LWP 15031] [New LWP 15039] [New LWP 15040] [New LWP 16128] [New LWP 16130] [New LWP 16131] [New LWP 16133] [New LWP 16134] [New LWP 16135] [New LWP 16136] [New LWP 16296] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7efd20a9cf in __GI___poll (fds=0x7ffc54b7da38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f7ef888b9c0 (LWP 14998))] Thread 15 (Thread 0x7f7eaacae700 (LWP 16296)): #0 0x7f7efe2f2fab in QArrayData::data() (this=) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #1 QTypedArrayData::data() (this=) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 #2 QTypedArrayData::begin(pollfd*) (this=) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #3 QVector::data() (this=) at ../../include/QtCore/../../src/corelib/tools/qvector.h:134 #4 QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:502 #5 0x7f7efe299c9b in QEventLoop::exec(QFlags) (this=this@entry=0x7f7eaacadbc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f7efe0b3362 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f7eff190569 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f7efe0b4543 in QThreadPrivate::start(void*) (arg=0x5593846dff40) at thread/qthread_unix.cpp:331 #9 0x7f7efde98609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f7efd217163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f7ebafbf700 (LWP 16136)): #0 0x7f7efd20aac6 in __ppoll (fds=fds@entry=0x7f7ead98, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f7efe2f1909 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f7ead98) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f7ead98) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f7ead98, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7f7efe2f2fb3 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7f7efe299c9b in QEventLoop::exec(QFlags) (this=this@entry=0x7f7ebafbebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f7efe0b3362 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f7efe0b4543 in QThreadPrivate::start(void*) (arg=0x559384045200) at thread/qthread_unix.cpp:331 #9 0x7f7efde98609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f7efd217163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f7ed39ff700 (LWP 16135)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559383b32910) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559383b328c0, cond=0x559383b328e8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559383b328e8, mutex=0x559383b328c0) at pthread_cond_wait.c:638 #3 0x7f7ef580f5eb in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f7ef580f1eb in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f7efde98609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f7efd217163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f7eba3e4700 (LWP 16134)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55
[kdeconnect] [Bug 438126] KDE Connect enabled via Android’s accessibility service overrides external keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=438126 Robert G. Siebeck changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 450400] New: always launches with Unknown error code 2,076,331,712 Please send a full bug report at https://bugs.kde.org.
https://bugs.kde.org/show_bug.cgi?id=450400 Bug ID: 450400 Summary: always launches with Unknown error code 2,076,331,712 Please send a full bug report at https://bugs.kde.org. Product: konqueror Version: 21.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: rjki...@yahoo.com 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. click on Konqueror 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450300] New: System Settings crash (notification sent)
https://bugs.kde.org/show_bug.cgi?id=450300 Bug ID: 450300 Summary: System Settings crash (notification sent) Product: systemsettings Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: bobkar...@gmail.com Target Milestone: --- Created attachment 146769 --> https://bugs.kde.org/attachment.cgi?id=146769&action=edit System Crash Report ## See attachment. 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 --- Comment #9 from Robert Mader --- (In reply to Nate Graham from comment #8) > There isn't going to be a 5.23.6 (non-LTS Plasma versions only get five > bugfix releases). So unless your distro's packagers backport it, we'll have > to wit until Plasma 5.24 in a week or so. Thanks for pointing that out! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 --- Comment #7 from Robert Mader --- Just tested on 5.23.5 and unfortunately the fix is not yet backported. Would be very glad if it made it into 5.23.6 :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448470] New: Gstreamer waylandsink does not update video content
https://bugs.kde.org/show_bug.cgi?id=448470 Bug ID: 448470 Summary: Gstreamer waylandsink does not update video content Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: robert.ma...@posteo.de Target Milestone: --- SUMMARY When running the Gstreamer waylandsink example demo, the content/pattern/"test video" never gets updated and is stuck on the first frame. STEPS TO REPRODUCE ``` git clone g...@gitlab.freedesktop.org:gstreamer/gstreamer.git cd gstreamer meson build cd build ninja cd .. ./gst-env.py cd subprojects/gst-plugins-bad/tests/examples/waylandsink/ ../../../../../build/subprojects/gst-plugins-bad/tests/examples/waylandsink/waylandsink ``` OBSERVED RESULT The test video/pattern is never updated after the first frame EXPECTED RESULT See test test video/pattern animating SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.4 ADDITIONAL INFORMATION This works as intended on Weston and Mutter. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Sticky keys does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 Robert Kratky changed: What|Removed |Added CC||kra...@rob.cz --- Comment #2 from Robert Kratky --- Can confirm on: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 447866] [class diagram] Multiple association ends are drawn on the same edge point
https://bugs.kde.org/show_bug.cgi?id=447866 --- Comment #6 from Robert Hairgrove --- (In reply to Oliver Kellogg from comment #5) > I am changing the automatic line update algorithm so that it does not snap > to midpoints/corners but instead uses the widget center as a reference point. > The association end point is mapped onto the widget edge using the > connecting line to the center. Sounds good to me. Thank you for all of your hard work improving Umbrello's stability and usability, Oliver! (BTW, wishing you a very Happy New Year!) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955
--- Comment #3 from Robert Webb ---
Tried it a third time, slightly differently.
Opened Gwenview.
This time, instead of clicking in the Places sidebar, I clicked
'recentlyused:/locations/' under the Recent Folders tab.
Gwenview crashed immediately.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 0x7f3ab0fc9a2e in QVector >::count
(this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:241
#7 QVariantAnimationPrivate::recalculateCurrentInterval (this=0x7ffe0004,
force=false) at animation/qvariantanimation.cpp:228
#8 0x7f3ab2291f15 in QModelIndex::parent (this=0x5610f643c300) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443
#9 QListView::scrollTo (this=0x5610f650a4c0, index=...,
hint=QAbstractItemView::EnsureVisible) at itemviews/qlistview.cpp:571
#10 0x7f3ab2253300 in QAbstractItemView::currentChanged
(this=0x5610f650a4c0, current=..., previous=...) at
itemviews/qabstractitemview.cpp:3677
#11 0x7f3ab11fb3c8 in doActivate (sender=0x5610f6424680,
signal_index=4, argv=0x7ffe11319c30) at kernel/qobject.cpp:3898
#12 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f6424680, m=m@entry=0x7f3ab14990a0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffe11319c30)
at kernel/qobject.cpp:3946
#13 0x7f3ab116f6d3 in QItemSelectionModel::currentChanged
(this=this@entry=0x5610f6424680, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#14 0x7f3ab11730b9 in QItemSelectionModel::setCurrentIndex
(this=0x5610f6424680, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#15 0x7f3ab224cedf in QAbstractItemView::setCurrentIndex (this=, index=...) at itemviews/qabstractitemview.cpp:1080
#16 0x5610f42e6d0f in Gwenview::MainWindow::slotDirListerCompleted
(this=0x5610f64418c0) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/app/mainwindow.cpp:1399
#17 Gwenview::MainWindow::qt_static_metacall (_o=0x5610f64418c0, _c=, _id=, _a=) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_mainwindow.cpp:245
#18 0x7f3ab11fb3c8 in doActivate (sender=0x5610f643c070,
signal_index=4, argv=0x7ffe11319e90) at kernel/qobject.cpp:3898
#19 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f643c070, m=m@entry=0x7f3ab2a2ff60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#20 0x7f3ab29b9cb3 in KCoreDirLister::completed
(this=this@entry=0x5610f643c070) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:479
#21 0x7f3ab29c203b in KCoreDirListerCache::slotResult (this=0x7f3ab2a333c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
j=) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/kcoredirlister.cpp:1327
#22 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a080,
r=0x7f3ab2a333c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
this=0x5610f6da72d0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x5610f6da59a0, signal_index=6,
argv=0x7ffe1131a080) at kernel/qobject.cpp:3886
#24 0x7f3ab11f485f in QMetaObject::activate
(sender=sender@entry=0x5610f6da59a0, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe1131a080)
at kernel/qobject.cpp:3946
#25 0x7f3ab15e8ffc in KJob::result (this=this@entry=0x5610f6da59a0,
_t1=, _t1@entry=0x5610f6da59a0, _t2=...) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#26 0x7f3ab15ed39b in KJob::finishJob (this=0x5610f6da59a0,
emitResult=) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/src/lib/jobs/kjob.cpp:98
#27 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a150,
r=0x5610f6da59a0, this=0x5610f6c65ec0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#28 doActivate (sender=0x5610f6c6db90, signal_index=7,
argv=0x7ffe1131a150) at kernel/qobject.cpp:3886
#29 0x7f3ab296b39d in KIO::SlaveInterface::dispatch (this=0x5610f6c6db90,
_cmd=104, rawdata=...) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slaveinterface.cpp:149
#30 0x7f3ab2963989 in KIO::SlaveInterface::dispatch (this=0x5610f6c6db90)
at /usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slaveinterface.cpp:78
#31 0x7f3ab296d14a in KIO::Slave::gotInput (this=0x5610f6c6db90) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/slave.cpp:336
#32 0x7f3ab11fb393 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1131a390,
r=0x5610f6c6db90, this=0x5610f6dbbf70) at
../../include/QtCore/../../src/corelib/kernel/qobjectd
[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955 --- Comment #2 from Robert Webb --- Tried it again. Same result. Gwenview opened, by DrKonqi after the last crash. Showing the Recent Folders tab. I clicked on Recent Locations in the Places sidebar. Crash. (DrKonqi did not open this time.) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955 Robert Webb changed: What|Removed |Added CC||ro.web...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955 --- Comment #1 from Robert Webb --- Correction: I clicked on Recent Locations in the Places sidebar. Additional info: The main "sub-window" was showing the Recent Folders tab upon opening Gwenview. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447955] Gwenview crashed after clicking Places sidebar/Recent Locations
https://bugs.kde.org/show_bug.cgi?id=447955 Robert Webb changed: What|Removed |Added Summary|Gwenview crashed after |Gwenview crashed after |clicking Recently Used |clicking Places |Locations |sidebar/Recent Locations -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447955] New: Gwenview crashed after clicking Recently Used Locations
https://bugs.kde.org/show_bug.cgi?id=447955
Bug ID: 447955
Summary: Gwenview crashed after clicking Recently Used
Locations
Product: gwenview
Version: 21.12.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: ro.web...@gmail.com
Target Milestone: ---
Application: gwenview (21.12.0)
Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.12-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Opened Gwenview.
Clicked 'Recently Used Locations'.
A moment later, after showing [an empty list?], Gwenview crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = { >> = { >> = {, true>> = {_M_head_impl = {}}, },
> = {_M_head_impl = }, }, }}, }}
[KCrash Handler]
#6 0x7fafc15d3a2e in QVector >::count
(this=) at
../../include/QtCore/../../src/corelib/tools/qvector.h:241
#7 QVariantAnimationPrivate::recalculateCurrentInterval (this=0x7ffc0004,
force=false) at animation/qvariantanimation.cpp:228
#8 0x7fafc289bf15 in QModelIndex::parent (this=0x55e667c8f9b0) at
../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443
#9 QListView::scrollTo (this=0x55e6674336c0, index=...,
hint=QAbstractItemView::EnsureVisible) at itemviews/qlistview.cpp:571
#10 0x7fafc285d300 in QAbstractItemView::currentChanged
(this=0x55e6674336c0, current=..., previous=...) at
itemviews/qabstractitemview.cpp:3677
#11 0x7fafc18053c8 in doActivate (sender=0x55e66734c890,
signal_index=4, argv=0x7ffc86154530) at kernel/qobject.cpp:3898
#12 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e66734c890, m=m@entry=0x7fafc1aa30a0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc86154530)
at kernel/qobject.cpp:3946
#13 0x7fafc17796d3 in QItemSelectionModel::currentChanged
(this=this@entry=0x55e66734c890, _t1=..., _t2=...) at
.moc/moc_qitemselectionmodel.cpp:482
#14 0x7fafc177d0b9 in QItemSelectionModel::setCurrentIndex
(this=0x55e66734c890, index=..., command=...) at
itemmodels/qitemselectionmodel.cpp:1416
#15 0x7fafc2856edf in QAbstractItemView::setCurrentIndex (this=, index=...) at itemviews/qabstractitemview.cpp:1080
#16 0x55e666fb4d0f in Gwenview::MainWindow::slotDirListerCompleted
(this=0x55e667360540) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/app/mainwindow.cpp:1399
#17 Gwenview::MainWindow::qt_static_metacall (_o=0x55e667360540, _c=, _id=, _a=) at
/usr/src/debug/gwenview5-21.12.0-1.1.x86_64/build/app/gwenview_autogen/EWIEGA46WW/moc_mainwindow.cpp:245
#18 0x7fafc18053c8 in doActivate (sender=0x55e667371b20,
signal_index=4, argv=0x7ffc86154790) at kernel/qobject.cpp:3898
#19 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e667371b20, m=m@entry=0x7fafc3039f60
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3946
#20 0x7fafc2fc3cb3 in KCoreDirLister::completed
(this=this@entry=0x55e667371b20) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/build/src/core/KF5KIOCore_autogen/include/moc_kcoredirlister.cpp:479
#21 0x7fafc2fcc03b in KCoreDirListerCache::slotResult (this=0x7fafc303d3c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
j=) at
/usr/src/debug/kio-5.89.0-1.2.x86_64/src/core/kcoredirlister.cpp:1327
#22 0x7fafc1805393 in QtPrivate::QSlotObjectBase::call (a=0x7ffc86154980,
r=0x7fafc303d3c0
<_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>,
this=0x55e667c1fb30) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x55e667c20690, signal_index=6,
argv=0x7ffc86154980) at kernel/qobject.cpp:3886
#24 0x7fafc17fe85f in QMetaObject::activate
(sender=sender@entry=0x55e667c20690, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc86154980)
at kernel/qobject.cpp:3946
#25 0x7fafc1bf2ffc in KJob::result (this=this@entry=0x55e667c20690,
_t1=, _t1@entry=0x55e667c20690, _t2=...) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#26 0x7fafc1bf739b in KJob::finishJob (this=0x55e667c20690,
emitResult=) at
/usr/src/debug/kcoreaddons-5.89.0-1.2.x86_64/src/lib/jobs/kjob.cpp:98
#27 0x7fafc1805393 in QtPrivate::QSlotObjectBase::call (a=0x7ffc86154a50,
r=0x55e667c20690, this=0x55e667b49490) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#28 doActivate (sender=0x55e667b44a60, signal_index=7,
argv=0x7ffc86154a50) at kernel/
[umbrello] [Bug 447866] [class diagram] Multiple association ends are drawn on the same edge point
https://bugs.kde.org/show_bug.cgi?id=447866 Robert Hairgrove changed: What|Removed |Added CC||c...@roberthairgrove.com --- Comment #2 from Robert Hairgrove --- Thank you, Oliver! I tried this, and now I can create two aggregations between the same two class without a problem. Over all, the drawing behavior is much more natural ... the bird view still has problems, though. Sometimes it will not update after adding objects to the diagram until the window is resized. But at least I can move one widget around without moving the other widgets in the opposite direction. After saving the file, closing the app and opening the file again, the text labels for role and multiplicity are placed in strange places. Another thing I noticed is that if I save a file, it does not add the ".xmi" extension if I do not type it explicitly. Also, default permissions are set to 600 instead of the expected 644 or 664 on Linux. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 447824] New: Cannot create two aggregations between the same two classes
https://bugs.kde.org/show_bug.cgi?id=447824 Bug ID: 447824 Summary: Cannot create two aggregations between the same two classes Product: umbrello Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- Created attachment 145048 --> https://bugs.kde.org/attachment.cgi?id=145048&action=edit Model of a simple graph structure SUMMARY Cannot create two aggregations between the same two classes. This is necessary if modeling a graph structure, for example (see attached picture of what I am trying to achieve). STEPS TO REPRODUCE 1. Open a new class diagram, or use the default diagram; 2. Add two classes : Node and Edge; 3. Draw an aggregation from Edge to Node. Give it the role "source", multiplicity 1..1 4. Try to draw another aggregation similar to the above with role "target" OBSERVED RESULT The second aggregation is not created. EXPECTED RESULT Multiple aggregations should be possible. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04.x (available in About System) Qt Version: 5 ADDITIONAL INFORMATION There is an interesting comment in the method body of "AssociationWidget::create()" which probably applies here. ;) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 446020] Bird's eye view shows nothing at first open
https://bugs.kde.org/show_bug.cgi?id=446020 --- Comment #5 from Robert Hairgrove --- (In reply to Oliver Kellogg from comment #4) > (...) - In function resizeSceneToItems, as an experimental change comment out > call to setSceneRect(itemsBoundingRect()). > It appears that the function resizeSceneToItems may be removed > altogether (subject to further tests). Thanks for looking into this, Oliver. In the meantime, I saw that QGraphicsScene will use itemsBoundingRect() anyway if no scene rect was previously set (in Qt docs). However, the strange drawing behavior of the diagrams when only a few objects/widgets are shown, and by extension of the bird's view, seems to stem from the fact that the scene has no minimum rect with sensible defaults for width and height. If I add two dummy widgets, one in the upper left corner and the other in the lower right corner, and keep moving them farther apart by scaling the view size down, then I can draw and resize other objects normally which lie inside of the bounding rect determined by the two dummy widgets. Also, the bird's eye view then works as one would expect. Dragging one object in one direction and having others move in the opposite direction is an optical illusion created by the fact that QGraphicssScene will try to keep all objects contained by it centered. Looking at the Qt example code in the "diagramscene" example, the scene's area is set in the constructor of MainWindow to (0,0,5000,5000) and it never changes. I don't know if this would work for Umbrello (when calling saveTo/loadFromXMI(), for example), but we could try starting out with a default size of 800 x 1100 pixels (which would correspond roughly to a single A4 page in portrait orientation with 96 DPI) and call resizeSceneToItems() only if the scene needs to grow its size or if the user selects "Fit" from the scale control. Perhaps this could be user-configurable? I recall reading somewhere that it is considered best practice only to include as much detail in a single UML diagram as will fit on a single A4 or US Letter size page... but cannot remember where I saw this. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 447598] New: Packages containing other objects are not displayed in a useful manner in a class diagram
https://bugs.kde.org/show_bug.cgi?id=447598 Bug ID: 447598 Summary: Packages containing other objects are not displayed in a useful manner in a class diagram Product: umbrello Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- Created attachment 144906 --> https://bugs.kde.org/attachment.cgi?id=144906&action=edit Contains packages_umbrello.png and packages_correct.png SUMMARY Packages containing other objects are not displayed in a useful manner. First of all, the package name should be displayed in the tab if it contains other packages, classes, or other objects. Second, the contained objects do not move with their parent package, but are shown exclusively with the older "⊕---" notation. STEPS TO REPRODUCE 1. In a class diagram, add a new package, e.g. "Qt" (see attached images); 2. Add a few classes and/or other packages to the diagram. They can be arranged so as to "look like" they are enclosed by the Qt package, but they are not shown in the model tree view as children until they are moved. Move them so that they appear as subobjects of the "Qt" package. 3. Move the "Qt" package away, and the subpackages do not move, but have an ownership association line drawn to them. OBSERVED RESULT See attached screenshot "packages_umbrello.png" EXPECTED RESULT See attached screenshot "packages_correct.png" (drawn with Modelio) SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04.06 KDE Plasma Version: ??? KDE Frameworks Version: 5 Qt Version: 5.12.9 ADDITIONAL INFORMATION Umbrello compiled from Git, latest version as of yesterday (27 December 2021) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 446020] Bird's eye view shows nothing at first open
https://bugs.kde.org/show_bug.cgi?id=446020
--- Comment #3 from Robert Hairgrove ---
(In reply to Robert Hairgrove from comment #1)
>(...) However, there is much more "bugginess" about the bird's eye view (and
>the
> drawing behavior in general) which needs to be looked at. For example, if I
> have added two new classes to an empty class diagram and move one of them,
> the other moves as well but in the opposite direction! There seems to be
> code somewhere causing the scene to always be centered ... is this by
> design? I would probably have to put widgets at the four corners of the
> virtual page to keep things in the middle area from wandering about on the
> screen when one of them is moved or resized. Takes a bit of getting used to.
In the class UMLScene, there is this slot:
void UMLScene::slotObjectCreated(UMLObject* o)
At the end of the slot's method body, there is a call to the member function
resizeSceneToItems();
which is implemented thus:
/**
* Sets the size of the scene to just fit on all the items
*/
void UMLScene::resizeSceneToItems()
{
// let QGraphicsScene handle scene size by itself
setSceneRect(itemsBoundingRect());
}
Why is this necessary? It seems to be the cause of the behavior I described in
the above post in this thread. One would think that the scene should begin with
a default size (user-configurable, of course) which can expand if moving an
object would cross one of the boundaries, but certainly not shrink if it is
larger.
What happens is that on creation of the first widget in the scene, the bird's
eye view will fill up its available display area with a huge rendition of the
widget (much larger than 100%).
Try this:
Open a new class diagram, if one isn't already there;
Create a new class and give it a very short name (such as "A").
The bird's eye will remain blank until the main window is resized or the
splitter handle is dragged. Do that.
Observe the resulting display in the bird's eye view.
Is this intentional?
--
You are receiving this mail because:
You are watching all bug changes.
[amarok] [Bug 446543] Crash on attempting to filter collection using date
https://bugs.kde.org/show_bug.cgi?id=446543 --- Comment #4 from robert marshall --- I'll try to do a build with debug and get a good traceback - not this week though! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 446543] Crash on attempting to filter collection using date
https://bugs.kde.org/show_bug.cgi?id=446543 --- Comment #2 from robert marshall --- Sorry about delay ... events... and this isn't full trying to work out how to install symbols from that ppa [KCrash Handler] #4 0x7f21fc7992e0 in QWidget::setFocus(Qt::FocusReason) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f21fd3ee686 in () at /lib/x86_64-linux-gnu/libamaroklib.so.1 #6 0x7f21fc79f5de in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f21fc75c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f21fc763e5b in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f21fbc607ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x565472189980, event=0x7ffeee36d300) at kernel/qcoreapplication.cpp:1063 #10 0x7f21fc762e77 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f21fc7b9370 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f21fc7bc615 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f21fc75c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f21fbc607ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x565471abed20, event=0x7ffeee36d5c0) at kernel/qcoreapplication.cpp:1063 #15 0x7f21fc04ab13 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f21fc01fe2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f21e5503a6e in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18 0x7f21f0a1d8eb in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f21f0a70d28 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f21f0a1b023 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f21fbcba204 in QEventDispatcherGlib::processEvents(QFlags) (this=0x56546f3768c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f21fbc5f11b in QEventLoop::exec(QFlags) (this=this@entry=0x7ffeee36d8f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f21fbc67604 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x56546ecc165c in () #25 0x7f21fb5c0565 in __libc_start_main (main=0x56546ecbc940, argc=1, argv=0x7ffeee36dbc8, init=, fini=, rtld_fini=, stack_end=0x7ffeee36dbb8) at ../csu/libc-start.c:332 #26 0x56546ecc1e9e in () [Inferior 1 (process 9369) detached] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444673] Esperanto does not show up as a select able language.
https://bugs.kde.org/show_bug.cgi?id=444673 --- Comment #2 from Robert Seere --- (In reply to Nate Graham from comment #1) > The list only shows languages that currently have any translations for KDE > software, and that are are installed. So one of those conditions must not be > true. I manually changed the file ~/.config/plasma-localerc and put LANG=eo.utf8. Now Kate from KDE is now in Esperanto after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446644] Most used quick settings are pointless when set by frequency, they should be 'last used' to facilitate repeat access
https://bugs.kde.org/show_bug.cgi?id=446644 Robert Griffiths changed: What|Removed |Added Summary|Most used quick settings|Most used quick settings |are mostly pointless when |are pointless when set by |set by frequency only, it |frequency, they should be |should contain all kcms the |'last used' to facilitate |user has accessed. |repeat access -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446644] Most used quick settings are mostly pointless when set by frequency only, it should contain all kcms the user has accessed.
https://bugs.kde.org/show_bug.cgi?id=446644 --- Comment #2 from Robert Griffiths --- Sure, if it were me, I would simply change the 5 most used to the 5 last used. Not perfect but much better. But maybe a few more than 5? So it could be most useful when setting up for the 1st time. I use about 9 I think. I'm not sure when most used is at all useful? Users don't return to 'difficult to find' options as much as themes so the harder to find options will fall from the bottom of the list: eg if I go to printers a few times coz I forgot my password or 'something' it will move up the list, I will never need it again, and something useful will disappear! Ideally it would be user choice, with buttons to choose a few settings so as to display a 'MY settings panel'. But that is a lot of work so I propose: 'Last used' in place of 'most used', and maybe a few more than 5. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446644] New: Most used quick settings are mostly pointless when set by frequency only, it should contain all kcms the user has accessed.
https://bugs.kde.org/show_bug.cgi?id=446644 Bug ID: 446644 Summary: Most used quick settings are mostly pointless when set by frequency only, it should contain all kcms the user has accessed. Product: systemsettings Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Settings Assignee: plasma-b...@kde.org Reporter: r.griff...@gmail.com Target Milestone: --- SUMMARY *** 'Most used' quick settings have been useless to me. On many systems I have set up, I have looked for something I just used and came back to and it's never been there for me. e.g. I set battery prefs, switch away to another app, then return to syse to set battery prefs again and all I see in most used are colors, themes etc (which may have a higher access stat but kcms I will use again are not well defined by this stat). *** STEPS TO REPRODUCE 1. Set something up in syse. 2. Close syse. 3. Open syse and check quick-settings 'most used' so as to return to the same setup page. OBSERVED RESULT Nothing I have wanted to return to has ever appeared in 'most used'. It has always been populated with colors, themes etc. EXPECTED RESULT Most used should be 'all used' and all kcms that have been accessed should be in the list, sorted by frequency or time (user option button I think). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 446543] New: Crash on attempting to filter collection using date
https://bugs.kde.org/show_bug.cgi?id=446543 Bug ID: 446543 Summary: Crash on attempting to filter collection using date Product: amarok Version: kf5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Collection Browser Assignee: amarok-bugs-d...@kde.org Reporter: rob...@capuchin.co.uk Target Milestone: kf5 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. Select edit filter for collection 2. Drag down 'last played 3 . Select before (or after) bringing up a date 1/1/1970 4. Click on date attempting to change it OBSERVED RESULT Amarok crashes EXPECTED RESULT Date selection panel should appear SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm using the build of Jun 26 2021 from Pedro Gomez's ppa not sure if that's the most recent build -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 446020] Bird's eye view shows nothing at first open
https://bugs.kde.org/show_bug.cgi?id=446020 --- Comment #2 from Robert Hairgrove --- When running Umbrello as a debug build started from a terminal, after examining the debug output, it seems that the problem here arises from the fact that the default configuration gives us an empty class diagram which can immediately be populated with classes, packages, etc. However, the debug output "view was NULL" on opening the application with no other command-line options seems to indicate that this initial diagram was not yet added to the diagram/view stack ... even though there is a "class_diagram" object present in the tree view? This would certainly explain the fact that there cannot already be a bird's eye view of a view that (officially) does not yet exist. Is this a configurable option? Why doesn't the inital screen show an emty diagram area (dock widget) instead? I would think that with a new project, where there is no code as yet in existence (and perhaps the programming language is not yet determined), it might make more sense to have either no diagram, or else perhaps a use case diagram, presented to the user. At any rate, if there is a valid diagram, there should also be a valid bird's eye view. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 446020] Bird's eye view shows nothing at first open
https://bugs.kde.org/show_bug.cgi?id=446020
--- Comment #1 from Robert Hairgrove ---
In the meantime, I was able to get the bird's eye view to show when a new
widget is added to the diagram. I noticed that selecting something in the tree
view would also trigger the view, so I looked at
UMLScene::slotObjectCreated(UMLObject* o). At the end of the method body, right
after the last line which calls "resizeSceneToItems()", I added these lines:
UMLView* cv = activeView();
if (cv) {
// this should activate the bird view:
UMLApp::app()->setCurrentView(cv, false);
}
The last parameter to setCurrentView() has a default value of "true", which
causes the tree view focus to change e.g. from "class_A" (or whatever the new
widget was named) to the class diagram. Passing "false" keeps the focus on the
widget in the tree view, which seems much more intuitive to me since many
properties would normally need to be edited after creating and naming the
widget. In UMLApp::setCurrentView(), there is a call to "createBirdView()"
which deletes any existing BirdView object and creates a new one. Seems rather
heavy-handed to me, but I couldn't figure out which signals to catch that would
actually do anything useful.
However, there is much more "bugginess" about the bird's eye view (and the
drawing behavior in general) which needs to be looked at. For example, if I
have added two new classes to an empty class diagram and move one of them, the
other moves as well but in the opposite direction! There seems to be code
somewhere causing the scene to always be centered ... is this by design? I
would probably have to put widgets at the four corners of the virtual page to
keep things in the middle area from wandering about on the screen when one of
them is moved or resized. Takes a bit of getting used to.
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 446020] New: Bitd's eye view shows nothing at first open
https://bugs.kde.org/show_bug.cgi?id=446020 Bug ID: 446020 Summary: Bitd's eye view shows nothing at first open Product: umbrello Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- SUMMARY Bitd's eye view shows nothing until the splitter control is dragged or the main window is resized. STEPS TO REPRODUCE 1. Open Umbrello and add something to the empty diagram (e.g. two or three new classes, perhaps draw some association lines); 2. Move things around with the mouse. OBSERVED RESULT The bird's eye view remains empty until the splitter control is moved or the main window is resized. EXPECTED RESULT The bird's eye view should refresh the display immediately when items are added to the diagram or moved. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04.6 LTS KDE Plasma Version: ??? KDE Frameworks Version: 5 Qt Version: 5.12.9 ADDITIONAL INFORMATION Umbrello compiled from Git master -- Version 2.31.70-d8c161b2a (experimental) shown in "About Umbrello" -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445119] Issues with code ignoring and possibly dereferencing nullptr
https://bugs.kde.org/show_bug.cgi?id=445119
--- Comment #6 from Robert Hairgrove ---
(In reply to Oliver Kellogg from comment #5)
> (In reply to Robert Hairgrove from comment #0)
> > Using Umbrello from Git/master:
> >
> > In file "component.cpp" at line 58 in the method
> > "UMLComponent::saveToXMI1()":
> >
> > for (UMLObjectListIt objectsIt(m_objects); objectsIt.hasNext();) {
> > UMLObject* obj = objectsIt.next();
> > uIgnoreZeroPointer(obj);
> > obj->saveToXMI1 (writer);
> > }
> >
> > What happens if "obj" == nullptr? A warning is emitted by
> > "uIgnoreZeroPointer", but "obj" is dereferenced after that anyway, which
> > causes undefined behavior according to the C++ standard.
>
> Looking at the definition of uIgnoreZeroPointer, in
> umbrello/debug/debug_utils.h :
> #define uIgnoreZeroPointer(a) if (!a) { uDebug() << "zero pointer detected"
> << __FILE__ << __LINE__; continue; }
>
> The `continue` statement means that the null pointer will not be accessed.
>
> Just a minor point... not to detract from the question of why lists contain
> null pointers at all.
Thanks, Oliver -- I didn't see the "continue" statement.
--
You are receiving this mail because:
You are watching all bug changes.
[kalendar] [Bug 445853] New: App Closes Unexpectedly
https://bugs.kde.org/show_bug.cgi?id=445853 Bug ID: 445853 Summary: App Closes Unexpectedly Product: kalendar Version: 0.2.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: robertdevasi...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (0.2.1) Qt Version: 5.15.3 Frameworks Version: 5.89.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.23.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: Changing the due time in edit mode, The task will be say overdue even if it is assigned for tomorrow The crash can be reproduced sometimes. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [New LWP 1972] [New LWP 1974] [New LWP 1983] [New LWP 1987] [New LWP 1988] [New LWP 1989] [New LWP 37513] [New LWP 1977] [New LWP 1994] [New LWP 37515] [New LWP 1986] [New LWP 1976] [New LWP 1975] [New LWP 37516] [New LWP 37514] [New LWP 17727] [New LWP 1982] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/kalendar'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f57072d3400 (LWP 1972))] __preamble__ [Current thread is 1 (Thread 0x7f57072d3400 (LWP 1972))] Thread 17 (Thread 0x7f56feffd700 (LWP 1982)): #0 0x7f570c505aff in __GI___poll (fds=0x7f56f0004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f570a25f36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f570a25f4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f570caee602 in QEventDispatcherGlib::processEvents (this=0x7f56fb60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f570ca928ab in QEventLoop::exec (this=this@entry=0x7f56feffcbc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f570c8ac2c2 in QThread::exec (this=this@entry=0x563d0d66b2d0) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f570d096549 in QQmlThreadPrivate::run (this=0x563d0d66b2d0) at qml/ftw/qqmlthread.cpp:155 #7 0x7f570c8ad45c in QThreadPrivate::start (arg=0x563d0d66b2d0) at thread/qthread_unix.cpp:329 #8 0x7f570ac14609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f570c512293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f56c6f88700 (LWP 17727)): #0 0x7f570c505aff in __GI___poll (fds=0x7f56b4004630, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f570a25f36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f570a25f4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f570caee602 in QEventDispatcherGlib::processEvents (this=0x7f56b4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f570ca928ab in QEventLoop::exec (this=this@entry=0x7f56c6f87be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f570c8ac2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f570c8ad45c in QThreadPrivate::start (arg=0x563d0fd12890) at thread/qthread_unix.cpp:329 #7 0x7f570ac14609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f570c512293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f56de048700 (LWP 37514)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f56de047b50, clockid=, expected=0, futex_word=0x563d0e34cd10) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f56de047b50, clockid=, mutex=0x563d0e34ccc0, cond=0x563d0e34cce8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x563d0e34cce8, mutex=0x563d0e34ccc0, abstime=0x7f56de047b50) at pthread_cond_wait.c:656 #3 0x7f570c8b3558 in QWaitConditionPrivate::wait_relative (this=0x563d0e34ccc0, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x563d0e34ccc0) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x563d0e346870, mutex=mutex@entry=0x563d0e165b68, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f570c8b0a61 in QThreadPoolThread::run (this=0x563d0e346860) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f570c8ad45c in QThreadPrivate::start (arg=0x563d0e346860) at thread/qthread_unix.cpp:329 #8 0x7f570ac14609 in start_thread (arg=) at pthread_
[umbrello] [Bug 445119] Issues with code ignoring and possibly dereferencing nullptr
https://bugs.kde.org/show_bug.cgi?id=445119 --- Comment #3 from Robert Hairgrove --- I realize now, after looking through the source code and docs for QList and QPointer, that this would not work with signals and slots unless a completely different copying mechanism and/or redesign of UMLObjectList were implemented. Neither QList nor QPointer are descendents of QObject, so they emit no signals. UMLObjectList would most likely have to contain a QList> member instead of inheriting it directly. Read and write operations could be forwarded directly to the QList member, but adding and removing objects (pointers) should be controlled by UMLObjectList. What I can envision now, without knowing all of the details about how this class is used, is the following: 1. Class UMLObjectList should inherit from QObject, or possibly just implement signals and slots using the Q_OBJECT macro; 2. UMLObjectList should connect itself via slot to the "destroyed()" signal of each element added to its list which should only be permitted through its own "append()" function (and removal through a correlated "remove()" function); 3. Whenever a contained element is destroyed, the slot would have to find the pointer in its list and then remove it. Of course, the actual object deletion would be left to QPointer. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445119] Issues with code ignoring and possibly dereferencing nullptr
https://bugs.kde.org/show_bug.cgi?id=445119 --- Comment #2 from Robert Hairgrove --- (In reply to Ralf Habacker from comment #1) > When I started working on Umbrello, there were many crashes because various > lists contained undefined pointers. This has been massively mitigated by > using QPointer, so that there are zero pointers left, which are checked and > ignored when accessing the lists. Why these null pointers are contained > there has already been investigated and fixed in some cases in the past, > when the cause was identifiable. One reason for this is probably the lack > of referential integrity of the objects involved. Objects are destroyed > although they are still registered in any lists. I wonder if it would help to have each object containing a UMLObjectList member to connect the "destroyed()" signal, emitted whenever a QObject is about to be destroyed, to some cleanup function which would remove the QPointer from its list? This could also be a slot added to the UMLObjectList class (which otherwise doesn't seem to be doing much of anything on its own) instead of having the object containing the list as a member be responsible for its own cleanup? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445275] CodeGenerator* UMLApp::m_codegen is never destroyed
https://bugs.kde.org/show_bug.cgi?id=445275 Robert Hairgrove changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Robert Hairgrove --- OK, this member is deleted when the UMLApp::queryClose() event is called by calling the UMLDoc::closeDocument() method which calls UMLApp::setGenerator() with the argument "Uml::ProgrammingLanguage::Reserved". Marking this as RESOLVED -- NOT A BUG.. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445275] CodeGenerator* UMLApp::m_codegen is never destroyed
https://bugs.kde.org/show_bug.cgi?id=445275 --- Comment #2 from Robert Hairgrove --- (In reply to Robert Hairgrove from comment #1) > (snip...) > a pointer "diagramsWindow" which it creates in its member initialization > list on line 80 and passes "this" as the parent. > (snip) This refers to line 80 of the file "umlappprivate.h". -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445275] CodeGenerator* UMLApp::m_codegen is never destroyed
https://bugs.kde.org/show_bug.cgi?id=445275 --- Comment #1 from Robert Hairgrove --- Following up on this, it seems that there are very many instances where the parent-child relationship between QObject/QWidget and derived classes is not respected: 1. Either the derived class does not initialize its base class QObject or QWidget with a "parent" object, in which case it must be manually deleted (and is sometimes forgotten as in the case of CodeGenerator classes); 2. The derived class DOES initialize its base class with a parent, but it is deleted nonetheless manually somewhere else (as in the class "DiagramsWindow" -- the class UMLAppPrivate, derived from QObject, contains a pointer "diagramsWindow" which it creates in its member initialization list on line 80 and passes "this" as the parent. However, the destructor of UMLAppPrivate ALSO deletes the same pointer, although QObject will delete all of its children on application shutdown. This is certainly cause for a lot of strange crashes and/or memory leaks. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445275] New: CodeGenerator* UMLApp::m_codegen is never destroyed
https://bugs.kde.org/show_bug.cgi?id=445275 Bug ID: 445275 Summary: CodeGenerator* UMLApp::m_codegen is never destroyed Product: umbrello Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- The UMLApp member variable "CodeGenerator* UMLApp::m_codegen" is apparently never destroyed once it is created. The base class CodeGenerator is derived from QObject, but it is always created without a parent and does not initialize the base QObject in its constructor. The containing class UMLApp does not delete this pointer in its destructor. Have I overlooked something here? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 445119] New: Issues with code ignoring and possibly dereferencing nullptr
https://bugs.kde.org/show_bug.cgi?id=445119
Bug ID: 445119
Summary: Issues with code ignoring and possibly dereferencing
nullptr
Product: umbrello
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: umbrello-de...@kde.org
Reporter: c...@roberthairgrove.com
Target Milestone: ---
Using Umbrello from Git/master:
In file "component.cpp" at line 58 in the method "UMLComponent::saveToXMI1()":
for (UMLObjectListIt objectsIt(m_objects); objectsIt.hasNext();) {
UMLObject* obj = objectsIt.next();
uIgnoreZeroPointer(obj);
obj->saveToXMI1 (writer);
}
What happens if "obj" == nullptr? A warning is emitted by "uIgnoreZeroPointer",
but "obj" is dereferenced after that anyway, which causes undefined behavior
according to the C++ standard.
I found instances of similar behavior in about 60 other files.
Which gives rise to the next question: Why are null pointers being stored in
the "m_objects" collection? Instead of an error or warning, this should be
handled by an assert() or something similar, causing the program to exit,
preferably in code which appends the pointers to the collection.
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 444906] New: Configuration change in native POP3 dialog is not valued
https://bugs.kde.org/show_bug.cgi?id=444906 Bug ID: 444906 Summary: Configuration change in native POP3 dialog is not valued Product: Akonadi Version: 5.17.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: POP3 Resource Assignee: kdepim-b...@kde.org Reporter: robert.spill...@gmx.de CC: aa...@kde.org Target Milestone: --- SUMMARY Changing a configuration for a POP3 Resource (either via kmail -> settings --> accounts, or akonadiconsole --> Agents --> (select any POP3 resource) --> Configure Natively) is not valued immediately. STEPS TO REPRODUCE In akonadiconsole choose a POP3 Resource: 1. Use the "Configure Remotely" to check the id of the associated TargetCollection (i. e. inbox folder) 2. Use the "Configure Natively" dialog of a pop3 resource to change the inbox folder. 3. Again, under "Configure Remotely" the TargetCollection is not updated (Restart Agent is required for this update). 4. Testmails sent to the POP3 Resources are still being put in the outdated (old) target collection. 5. The same holds for configuration changes from kmail (uses the native configuration dialog). (This also holds for other configuration items.) OBSERVED RESULT Configuration updates are not valued when used. The agent (or akonadi as a whole) has to be restarted manually. EXPECTED RESULT Configuration updates are valued immediately after being set in the dialog. SOFTWARE/OS VERSIONS Linux (available in About System) KDE Plasma Version: 5.85.0-r3 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Changing an imap resource via the native dialog triggers an automatic agent restart. Maybe that's the way to go for pop3. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 444820] CMake build of master branch fails on Ubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=444820 Robert Hairgrove changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Robert Hairgrove --- I needed to install libclang-10-dev, now it is compiling. For some reason, this was not required a few months ago, since I had libclang-cpp10-dev (et al.) installed, and was able to build Umbrello with no problem... is this documented anywhere? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 442134] "const" correctness in Umbrello sources
https://bugs.kde.org/show_bug.cgi?id=442134
--- Comment #7 from Robert Hairgrove ---
(In reply to Oliver Kellogg from comment #6)
> Git commit 7a8d1cfb0b562fab051c7ec3b46e6eededee5195 by Oliver Kellogg.
> Committed on 11/09/2021 at 08:57.
> Pushed by okellogg into branch 'master'.
>
> Address remaining trivial const correctness fixes from attachment 141364
> [details].
> Suggestions that require code change beyond function signature are postponed
> to a further batch.
>
> M +3-3umbrello/dialogs/multipagedialogbase.cpp
(...big snip...)
If you could now add const overloads to the following functions starting at
line 225 in "umlobject.h", this would undoubtibly help further progress in
making other things const correct, i.e.:
UMLActor * asUMLActor();
UMLArtifact * asUMLArtifact();
UMLAssociation * asUMLAssociation();
UMLAttribute * asUMLAttribute();
(etc. ... then add these declarations after the group:)
const UMLActor * asUMLActor() const;
const UMLArtifact * asUMLArtifact() const;
const UMLAssociation * asUMLAssociation() const;
const UMLAttribute * asUMLAttribute() const;
and in umlobject.cpp starting at line 1382:
UMLActor* UMLObject::asUMLActor(){ return
dynamic_cast(this); }
UMLArtifact * UMLObject::asUMLArtifact() { return
dynamic_cast(this); }
UMLAssociation * UMLObject::asUMLAssociation() { return
dynamic_cast(this); }
(...)
adding the corresponding methods after this group, i.e.:
const UMLActor* UMLObject::asUMLActor() const {
return dynamic_cast(this); }
const UMLArtifact * UMLObject::asUMLArtifact() const{
return dynamic_cast(this); }
const UMLAssociation * UMLObject::asUMLAssociation() const {
return dynamic_cast(this); }
I don't think this would break any existing code?
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 444820] New: CMake build of master branch fails on Ubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=444820 Bug ID: 444820 Summary: CMake build of master branch fails on Ubuntu 18.04 Product: umbrello Version: Git Platform: unspecified OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: installer/packages Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- Created attachment 143129 --> https://bugs.kde.org/attachment.cgi?id=143129&action=edit CMakeOutput.log SUMMARY CMake build of master branch fails on Ubuntu 18.04. Umbrello ChangeLog version is version 2.14.0 (4.14.0). STEPS TO REPRODUCE 1. Downloaded code as .zip package from https://invent.kde.org/sdk/umbrello 2. Followed the instructions in the file INSTALL 3. Run "cmake -DCMAKE_INSTALL_PREFIX=$HOME/umbrello -DCMAKE_BUILD_TYPE=Debug ../" OBSERVED RESULT ``` CMake Error at /usr/lib/llvm-10/lib/cmake/clang/ClangTargets.cmake:636 (message): The imported target "clangBasic" references the file "/usr/lib/llvm-10/lib/libclangBasic.a" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib/llvm-10/lib/cmake/clang/ClangTargets.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib/cmake/clang-10/ClangConfig.cmake:19 (include) unittests/CMakeLists.txt:161 (find_package) -- Configuring incomplete, errors occurred! See also "/home/bob/umbrello-master/build/CMakeFiles/CMakeOutput.log". ``` CMakeOutput.log is attached. EXPECTED RESULT Successful build SOFTWARE/OS VERSIONS Ubuntu 18.04.5 LTS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444673] New: Esperanto does not show up as a select able language.
https://bugs.kde.org/show_bug.cgi?id=444673 Bug ID: 444673 Summary: Esperanto does not show up as a select able language. Product: systemsettings Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_language Assignee: h...@kde.org Reporter: random.gj...@slmail.me CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143035 --> https://bugs.kde.org/attachment.cgi?id=143035&action=edit Screenshot of Esperanto missing SUMMARY STEPS TO REPRODUCE 1. Open System Settings 2. Click Regional Settings 3. Click Add languages.. 4. Look for Esperanto OBSERVED RESULT Esperanto is not in the list of Add Languages at all. EXPECTED RESULT Esperanto needs to show in the Add Languages list as a select able item. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernal: 5.14.14 Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 Robert David changed: What|Removed |Added CC||robert.david.public@gmail.c ||om --- Comment #5 from Robert David --- Hit the same issue on plasma 5.22 and apps 21.04. Any update on this? Is this solved in newer version? Actually having Yakuake little bit Activity aware would be fine (eg option for different session on different activity). But this is off-topic here. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 --- Comment #6 from Robert Strom --- Created attachment 142100 --> https://bugs.kde.org/attachment.cgi?id=142100&action=edit Example of the Salamander copy window minimized I would like the ability to minimize the copy window and get it out of the way while I continue working. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 --- Comment #5 from Robert Strom --- Created attachment 142098 --> https://bugs.kde.org/attachment.cgi?id=142098&action=edit Altap Salamander copying file - copy windows has minimize button Note that the copy window has a minimize button. I have the ability to minimize the copy window and get it out of the way during a long copy (of which I have many of - multi-GB copies). I know that Krusader has the ability to minimize the copy window if I am using KUbuntu, but ther is no ability to minimize if I run Linux Mint Cinnamon, or Pop!_OS, and probably others. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 Robert Strom changed: What|Removed |Added CC||robert.st...@gmail.com --- Comment #4 from Robert Strom --- Created attachment 142095 --> https://bugs.kde.org/attachment.cgi?id=142095&action=edit Altap Salamander Starting Copy Example Picture of another dual pane file manager (this one running on Windows). I have used this file manager since the 1990's. Very, very similar to Krusader, also based on the "Norton Commander" style Dual Pane. This picture is just starting the copy (F5), just like you would in Krusader. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #4 from Robert Strom --- Created attachment 142094 --> https://bugs.kde.org/attachment.cgi?id=142094&action=edit Pop!_OS System Notification are for Krusader -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #3 from Robert Strom --- Created attachment 142093 --> https://bugs.kde.org/attachment.cgi?id=142093&action=edit Krusader Main Window and Copy Window no Minimize button -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #2 from Robert Strom --- No, I don't believe that it helps. I tried looking back at the attachment picture that I posted but it is not showing when I click on it. I am posting two more pictures. One picture of the Krusader window with the Copy Window over it. This should clearly show that the Copy Window has no Minimize button. I can move the window out of the way and still access Krusader and move around in the program while the copy or move is happening but I cannot minimize the window. The second screenshot shows the System / Notifications area for Krusader. I am not seeing what I believe you are referring to. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 Robert Strom changed: What|Removed |Added CC||robert.st...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] New: Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 Bug ID: 443048 Summary: Copy / Move progress bar always on top and unable to minimize Product: krusader Version: 2.7.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: robert.st...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 141972 --> https://bugs.kde.org/attachment.cgi?id=141972&action=edit Progress bar with no ability to minimize SUMMARY I have been using Krusader on a few different Linux distributions and have seen different behavior depending on the distro. I had been using Linux Mint Cinnamon for about a year and a half and then switched due to an issue with VMware Workstation performance. On Linux Mint Cinnamon and on my current distribution, Pop!_OS (System 76) Distributor ID: Pop Description:Pop!_OS 21.04 Release:21.04 Codename: hirsute Whenever I copy or move a file the progress bar is always on top and I am unable to minimize it. In between the Linux Mint Cinnamon and the Pop!_OS installations I ran Kubuntu. While using Kubuntu I experienced the behavior that I would expect from the copy / move progress bar. I was able to minimize the progress bar so that it was unobtrusive / out of the way. So, why is it that the progress bar can be minimized on Kubuntu, but not on other Linux distros? STEPS TO REPRODUCE 1. Copy or move any file 2. 3. OBSERVED RESULT Unable to minimize the progress bar EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #60 from Robert Haslinger --- just tried with iCloud and latest 5.18.1 KOrganizer. its not working. just connecting to the server, all resources are found, but no calendar entries are shown. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 442319] Closing Amarok with playback volume set at 100% and then reopening has volume set at 0%
https://bugs.kde.org/show_bug.cgi?id=442319 robert marshall changed: What|Removed |Added CC||rob...@capuchin.co.uk --- Comment #2 from robert marshall --- I'm seeing this sometimes too - but I'm not sure what is provoking it - or how to reliably show the bug. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 442134] "const" correctness in Umbrello sources
https://bugs.kde.org/show_bug.cgi?id=442134
--- Comment #3 from Robert Hairgrove ---
(In reply to Oliver Kellogg from comment #1)
> Thanks for making the attachment, it is helpful.
>
> Minor point:
> > File: codedocument.h
> > virtual QString getUniqueTag(const QString& prefix = QString()); // const
>
> This one can't be made const due to a side effect this the function body,
>
> QString CodeDocument::getUniqueTag (const QString& prefix) const
> {
> [...]
> m_lastTagIndex = number;
>
> The compiler reports
> "assignment of member ‘CodeDocument::m_lastTagIndex’ in read-only object".
Thank you, Oliver!
As I replied in the umbrello-devel user group (but under another email address,
sorry about that), one could declare "CodeDocument::m_lastTagIndex"
mutable...this would be the easiest way to fix the compilation error.
However, from looking at the implementation code, it appears that this member
merely implements some kind of sequence number used to generate the new tag.
Shouldn't this rather be made a static member, or have a static
"generateSequence()" function? Unless there is only one singleton instance of
CodeDocument objects, the danger of having duplicate values seems very real
here, because each derived instance will have its own copy of the member.
Also, the function is declared virtual ... what if a derived class overrides it
and thus cannot update the private member of the base class?
I suppose this could be avoided if each class were required to have its own
unique prefix which is prepended to the number, but I'm not sure where this is
enforced.
--
You are receiving this mail because:
You are watching all bug changes.
[umbrello] [Bug 442134] New: "const" correctness in Umbrello sources
https://bugs.kde.org/show_bug.cgi?id=442134 Bug ID: 442134 Summary: "const" correctness in Umbrello sources Product: umbrello Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: c...@roberthairgrove.com Target Milestone: --- Created attachment 141364 --> https://bugs.kde.org/attachment.cgi?id=141364&action=edit Umbrello C++ const bugs >From the Umbrello CODING-STYLE document at item 43 (line 245 in the one I have, may not be up-to-date): " 43.) "const correctness" should be preserved as much as possible. Make all getters const." Question: Has anyone actually tried to do this with the existing Umbrello sources? I did, and I had to change about 400 lines of code in just about every file in the source tree before it was again usable. The problem with const (in-)correctness is that it is somewhat like cancer: Once it has started in some code somewhere, it propagates until the entire code base is unusable if one insists on subsequent code being const-correct. But I get the impression that for some of the Umbrello code, which has obviously been around since the very beginning of the app, this was never an issue. At some point, a well-meaning maintainer decided "Oh yes ... we should require const-correctness in our coding standards". I am a great believer in const correctness. So I have another question: How can we do this? I am posting the document I created with descriptions of all the function signatures in all the files so that people can try to follow up on it. But since I am not a regular contributor to the Umbrello project, and still have issues with Git, etc., I will leave it up to those who can actually navigate "invent.kde.org" and do something useful here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441453] New: PIM Calendar Missing
https://bugs.kde.org/show_bug.cgi?id=441453 Bug ID: 441453 Summary: PIM Calendar Missing Product: plasmashell Version: 5.22.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: 1.0 Created attachment 140991 --> https://bugs.kde.org/attachment.cgi?id=140991&action=edit screenshot of missing PIM calendar event section SUMMARY STEPS TO REPRODUCE 1. Removed digital clock widget and re-added 2. Done above and restarted OBSERVED RESULT The same with the above steps EXPECTED RESULT PIM Calendar events to appear SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User Edition (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #9 from Robert --- Nothing in particular I have pinned a wide variety of applications. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #7 from Robert --- I followed your instructions and it crashed again and this time when I started latte i ran it through konsole and it ended up segfaulting and crashed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #6 from Robert --- I will definitely give it a try when I get home from work. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #4 from Robert --- I pinned them to latte by right clicking them and selecting pin to dock on all activities. I’m not sure of the exact wording but it was something in that range. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440753] Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 --- Comment #2 from Robert --- I had reproduced this by doing the same exact thing I was doing when it happened the first time. I opened four different applications and started pinning them to latte-dock one by one after I pinned them the desktop became unresponsive then latte-dock crashed then restarted itself. Not sure what more steps you might need. If you need more info be specific please. I will definitely help where I can in order to provide more info. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440753] New: Latte Crashes when pinning applications
https://bugs.kde.org/show_bug.cgi?id=440753 Bug ID: 440753 Summary: Latte Crashes when pinning applications Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rstreete...@gmail.com Target Milestone: --- Application: latte-dock (0.10.0) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.11.0-25-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I was opening applications so I could pin them to Latte-Dock. I have had this happen a couple of times and so it is definitely reproduceible The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 31415] [New LWP 31416] [New LWP 31417] [New LWP 31418] [New LWP 31419] [New LWP 31420] [New LWP 31423] [New LWP 31435] [New LWP 31443] [New LWP 31444] [New LWP 31445] [New LWP 31446] [New LWP 31447] [New LWP 31448] [New LWP 31449] [New LWP 31450] [New LWP 31451] [New LWP 31452] [New LWP 31453] [New LWP 31454] [New LWP 31459] [New LWP 31467] [New LWP 31468] [New LWP 31469] [New LWP 31470] [New LWP 31471] [New LWP 31477] [New LWP 32068] [New LWP 32069] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x555996a807d0) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fe623cc09c0 (LWP 31414))] Thread 30 (Thread 0x7fe55a619700 (LWP 32069)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x555995fe1a04) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555995fe19b0, cond=0x555995fe19d8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555995fe19d8, mutex=0x555995fe19b0) at pthread_cond_wait.c:647 #3 0x7fe627d2ff2b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x555995fe19b0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x5559a6a96458, mutex=mutex@entry=0x5559a6a96450, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fe629f09b44 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x5559a6a96448) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x5559a6a963b0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7fe629f09fb9 in QSGRenderThread::run() (this=0x5559a6a963b0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7fe627d29dbc in QThreadPrivate::start(void*) (arg=0x5559a6a963b0) at thread/qthread_unix.cpp:329 #9 0x7fe627719609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe62785b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fe55bcf9700 (LWP 32068)): #0 0x7fe6261a14dd in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fe626153dac in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe626154312 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe6261544a3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe627f6afcb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe58c0f99b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fe627f0f25b in QEventLoop::exec(QFlags) (this=this@entry=0x7fe55bcf8bc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7fe627d28c22 in QThread::exec() (this=this@entry=0x7fe61c0218d0) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7fe629b8f559 in QQmlThreadPrivate::run() (this=0x7fe61c0218d0) at qml/ftw/qqmlthread.cpp:155 #8 0x7fe627d29dbc in QThreadPrivate::start(void*) (arg=0x7fe61c0218d0) at thread/qthread_unix.cpp:329 #9 0x7fe627719609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fe62785b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fe5a2417700 (LWP 31477)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5559a2eca000) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5559a2ec9fb0, cond=0x5559a2ec9fd8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5559a2ec9fd8, mutex=0x5559a2ec9fb0) at pthread_cond_wait.c:647 #3 0x7fe627d2ff2b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5559a2ec9fb0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (
[kdialog] [Bug 440720] KDialog mangles filenames containing "#"
https://bugs.kde.org/show_bug.cgi?id=440720 Robert Earl changed: What|Removed |Added CC||eleison23+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 440720] New: KDialog mangles filenames containing "#"
https://bugs.kde.org/show_bug.cgi?id=440720 Bug ID: 440720 Summary: KDialog mangles filenames containing "#" Product: kdialog Version: 20.08 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: eleison23+...@gmail.com Target Milestone: --- SUMMARY When entering a filename in KDialog, if the string contains a "#", KDialog deletes the "#" and everything following it up through the extension. STEPS TO REPRODUCE 1. Launch Google Chrome (for example) 2. Select a file to download 3. Select directory and enter a filename such as "Bug #1.mp4" 4. Press save OBSERVED RESULT Unwanted filename "Bug .mp4" EXPECTED RESULT "Bug #1.mp4" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: Plasma 5.18.5 KDE Frameworks Version: 5.75.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 428765] Konsole custom profile not staying default
https://bugs.kde.org/show_bug.cgi?id=428765 Robert Earl changed: What|Removed |Added CC||eleison23+...@gmail.com --- Comment #1 from Robert Earl --- Created attachment 140555 --> https://bugs.kde.org/attachment.cgi?id=140555&action=edit screenshots of before-and-after konsole profile So I have this same basic issue, in the root account. I first sudo -i and run konsole Set profile up as I like it (black on yellow, 12pt font, 80x24) Profile registers ok, shows up in ~/.local/share Launch konsole & from the command line and it shows up as default: black background, tiny font. If I use Shift+Ctrl+N it works as expected. If I "Manage Profiles" and "Set as Default" and then switch to "Default Profile" it reappears. So it is stored but ignored on launch. Bug confirmed on both of the following host systems: Environment: Kubuntu 18.04.5 LTS (X client); Plasma 5.12.9 Fedora 32 Plasma 5.18.5 (X11 client) Fedora 32 Plasma 5.18.5 (X11 server) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400074] Accessibility Sticky-Keys Becoming Disabled At Random At Times
https://bugs.kde.org/show_bug.cgi?id=400074 Robert Kratky changed: What|Removed |Added CC||kra...@rob.cz --- Comment #3 from Robert Kratky --- For me, this happens every time I restart KDE-Plasma. The setting stays on reliably, unless I launch the desktop newly. No problem with unplugging a replugging the keyboard. The ~/.config/kaccessrc file shows the correct setting (StickyKeys=true) even when the function doesn't work. Setting it to 'false' and then back to 'true' has no effect. Only remedy is to re-apply the setting through the System Settings UI. Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.5-200.fc34.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440187] New: Plasma mobile Discover (on pinephone) offline update fails with error since pacman 6?
https://bugs.kde.org/show_bug.cgi?id=440187 Bug ID: 440187 Summary: Plasma mobile Discover (on pinephone) offline update fails with error since pacman 6? Product: Discover Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (offline) Assignee: lei...@leinir.dk Reporter: r.griff...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Flash Manjaro dev pinephone image, I used yesterdays: 202107220245 from https://github.com/manjaro-pinephone/plasma-mobile-dev/releases 2. Update following the discover notification. 3. Reboot. OBSERVED RESULT Discover (offline updates) complains: "Failed to update 1 package, failed to update database: unexpected system error." Clicking repair doesn't resolve the issue. EXPECTED RESULT Offline updates completes without error, or repair option resolves the error. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Comment by Strit from Manjaro: "yeah. It's a known issue, I believe since the update to pacman 6 / libalpm 13" -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated
https://bugs.kde.org/show_bug.cgi?id=417787 Robert G. Siebeck changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439756] New: Wallpaper goes black when trying to apply high-res wallpaper.
https://bugs.kde.org/show_bug.cgi?id=439756 Bug ID: 439756 Summary: Wallpaper goes black when trying to apply high-res wallpaper. Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: robert.stokr...@planet.nl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Grab a high-res wallpaper (mine is from https://github.com/kitsunebishi/Wallpapers/blob/main/images/00040.png if needed, I also tested other wallpapers from that same repo with the same results). 2. Click on configure desktop, then add and select your wallpaper. 3. Apply said wallpaper. OBSERVED RESULT Had to wait for a few seconds, then wallpaper turned a solid black. EXPECTED RESULT It should just apply the wallpaper. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Pop_OS! 20.04 with kubuntu-desktop (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION For anyone wanting a screen recording, https://imgur.com/JxZi6GY -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438972] The zwp_pointer_gestures_v1 protocol is broken with GTK
https://bugs.kde.org/show_bug.cgi?id=438972 Robert Mader changed: What|Removed |Added Summary|Support the |The zwp_pointer_gestures_v1 |zwp_pointer_gestures_v1 |protocol is broken with GTK |protocol| --- Comment #3 from Robert Mader --- Urgh, sorry, it's already supported - just something with GTK is broken, on either side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438972] Support the zwp_pointer_gestures_v1 protocol
https://bugs.kde.org/show_bug.cgi?id=438972 --- Comment #2 from Robert Mader --- P.S. as little extra motivation: one of the main Firefox Webrender devs runs KDE and would love to debug pinch zoom on his main device :) So implementing would make some people very happy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438972] Support the zwp_pointer_gestures_v1 protocol
https://bugs.kde.org/show_bug.cgi?id=438972 --- Comment #1 from Robert Mader --- Firefox tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1717391 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438972] New: Support the zwp_pointer_gestures_v1 protocol
https://bugs.kde.org/show_bug.cgi?id=438972 Bug ID: 438972 Summary: Support the zwp_pointer_gestures_v1 protocol Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: robert.ma...@posteo.de Target Milestone: --- SUMMARY GTK3/4 as well as Mutter and wlroots (oddly not Weston) implement the zwp_pointer_gestures_v1 protocol to allow pinch and zoom gestures on touchpads. It is used in apps such as Firefox, Gnome Web and evince and allows to make the touchpad experience match closer that of other OSes. It would be great to have it supported in Kwin as well. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/unstable/pointer-gestures/pointer-gestures-unstable-v1.xml -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438315] New: Kwin Closed Unexpectedly
https://bugs.kde.org/show_bug.cgi?id=438315 Bug ID: 438315 Summary: Kwin Closed Unexpectedly Product: kwin Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: robertdevasi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.22.0) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.4.0-74-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: Switching between programs. Updated to new version (5.22) still no change. - Unusual behavior I noticed: Window decorations restarts - Custom settings of the application: Used MACsimize( maximize to new desktop ) kwin script The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 19729] [New LWP 19730] [New LWP 19731] [New LWP 19732] [New LWP 19733] [New LWP 19853] [New LWP 19919] [New LWP 19920] [New LWP 19921] [New LWP 19922] [New LWP 21479] [New LWP 22586] [New LWP 22587] [New LWP 22588] [New LWP 22589] [New LWP 22590] [New LWP 22591] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f073049daff in __GI___poll (fds=0x7ffe7a2928a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f072ab3d280 (LWP 19727))] Thread 18 (Thread 0x7f06df2fe700 (LWP 22591)): #0 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7f06cb60, m=m@entry=0x7f0730d501c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3941 #1 0x7f0730ab2e44 in QAbstractEventDispatcher::aboutToBlock() (this=this@entry=0x7f06cb60) at .moc/moc_qabstracteventdispatcher.cpp:143 #2 0x7f0730b0e1e7 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7f06cb60, flags=...) at kernel/qeventdispatcher_unix.cpp:479 #3 0x7f0730ab4dcb in QEventLoop::exec(QFlags) (this=this@entry=0x7f06df2fdce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #4 0x7f07308cebb2 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7f07308cfd4c in QThreadPrivate::start(void*) (arg=0x55f026ae8f10) at thread/qthread_unix.cpp:329 #6 0x7f072efd0609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f07304aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f06dfaff700 (LWP 22590)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f027cffb88) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f027cffb38, cond=0x55f027cffb60) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f027cffb60, mutex=0x55f027cffb38) at pthread_cond_wait.c:647 #3 0x7f0722d5eb5b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f0722d5e75b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f072efd0609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f07304aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f06cbbd3700 (LWP 22589)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f027cffb88) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f027cffb38, cond=0x55f027cffb60) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f027cffb60, mutex=0x55f027cffb38) at pthread_cond_wait.c:647 #3 0x7f0722d5eb5b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f0722d5e75b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f072efd0609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f07304aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f06d03d4700 (LWP 22588)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f027cffb88) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f027cffb38, cond=0x55f027cffb60) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f027cffb60, mutex=0x55f027cffb38) at pthread_cond_wait.c:647 #3 0x7f0722d5eb5b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f0722d5e75b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f072efd0609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f07304aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f070dffb700 (LWP 22587)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f027cffb88
[kdeconnect] [Bug 438066] New: KDE Connect Crashes
https://bugs.kde.org/show_bug.cgi?id=438066 Bug ID: 438066 Summary: KDE Connect Crashes Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: robertdevasi...@gmail.com Target Milestone: --- Application: kdeconnectd (21.04.1) Qt Version: 5.15.3 Frameworks Version: 5.82.0 Operating System: Linux 5.4.0-74-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: I recently got a new updates from neon packages after updationand restart it happend every time. - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [New LWP 1439] [New LWP 1457] [New LWP 1537] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f189c323aff in __GI___poll (fds=0x7ffe0e8145e8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f18987f6d40 (LWP 1427))] Thread 4 (Thread 0x7f1894c79700 (LWP 1537)): #0 0x7f189ae65508 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f189ae178e1 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f189ae1829b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f189ae184a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f189c8f1b3b in QEventDispatcherGlib::processEvents (this=0x7f188c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f189c895dcb in QEventLoop::exec (this=this@entry=0x7f1894c78ce0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f189c6afbb2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f189c6b0d4c in QThreadPrivate::start (arg=0x557be294ee10) at thread/qthread_unix.cpp:329 #8 0x7f189b839609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f189c330293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f1895e8a700 (LWP 1457)): #0 0x7f189c323aff in __GI___poll (fds=0x7f1888013290, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f189ae1836e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f189ae184a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f189c8f1b3b in QEventDispatcherGlib::processEvents (this=0x7f1888000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f189c895dcb in QEventLoop::exec (this=this@entry=0x7f1895e89cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f189c6afbb2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f189d21af4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f189c6b0d4c in QThreadPrivate::start (arg=0x7f189d29ed80) at thread/qthread_unix.cpp:329 #8 0x7f189b839609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f189c330293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1897a01700 (LWP 1439)): #0 0x7f189c323aff in __GI___poll (fds=0x7f1897a00be8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f189a984c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f189a98690a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1898145e88 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f189c6b0d4c in QThreadPrivate::start (arg=0x557be281e7b0) at thread/qthread_unix.cpp:329 #5 0x7f189b839609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f189c330293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f18987f6d40 (LWP 1427)): [KCrash Handler] #4 Device::reloadPlugins (this=this@entry=0x557be29cdad0) at ./core/device.cpp:192 #5 0x7f189de84562 in Device::addLink (this=this@entry=0x557be29cdad0, identityPacket=..., link=, link@entry=0x557be2a609f0) at ./core/device.cpp:302 #6 0x7f189de77b73 in Daemon::onNewDeviceLink (this=0x7ffe0e816e10, identityPacket=..., dl=0x557be2a609f0) at ./core/daemon.cpp:206 #7 0x7f189c8ce2ee in QtPrivate::QSlotObjectBase::call (a=0x7ffe0e8152e0, r=0x7ffe0e816e10, this=0x557be29cd840) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x557be2928190, signal_index=3, argv=0x7ffe0e8152e0) at kernel/qobject.cpp:3886 #9 0x7f189c8c76b7 in QMetaObject::activate (sender=sender@entry=0x557be2928190,
