[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead store this data in extended attributes
https://bugs.kde.org/show_bug.cgi?id=322922 Tomasz Kaźmierczak changed: What|Removed |Added CC||tome...@runbox.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487587] New: Dolphin crashes when I try to open a WebDAV location
https://bugs.kde.org/show_bug.cgi?id=487587 Bug ID: 487587 Summary: Dolphin crashes when I try to open a WebDAV location Classification: Applications Product: dolphin Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tome...@runbox.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-10036-tuxedo x86_64 Windowing System: Wayland Distribution: TUXEDO OS 3 DrKonqi: 6.0.4 [KCrashBackend] -- Information about the crash: Whenever I'm trying to access a WebDAV resource using Dolphin, the application crashes. This happens after trying to open the resource by clicking a "shortcut" file, but also after directly entering the URL (webdavs://:2078) into the Dolphin's address bar. This affects Dolphin 24.02.2 with Plasma 6 (TuxedoOS), but does NOT happen in Dolphin 23.08.1 with Plasma 5 (Kubuntu). The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=132166446316224) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=132166446316224) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=132166446316224, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x78346ae42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x78346ae287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x78346bafdb6e in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x78346baf820a in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2025 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7ffd456804a0) at ./src/corelib/global/qlogging.cpp:374 #12 0x78346bafe511 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:889 #13 0x78346bac2ac2 in qt_assert (assertion=assertion@entry=0x78346db9eaa7 "!path2.startsWith(s_slash)", file=file@entry=0x78346db9ea8f "./src/core/../utils_p.h", line=line@entry=122) at ./src/corelib/global/qassert.cpp:68 #14 0x78346da83ef9 in Utils::concatPaths (path1=..., path2=...) at ./src/core/../utils_p.h:120 #15 Utils::concatPaths (path1=..., path2=...) at ./src/core/../utils_p.h:120 #16 0x78346daaff0f in KFileItemPrivate::readUDSEntry (this=this@entry=0x56696d6e3890, _urlIsDirectory=_urlIsDirectory@entry=true) at ./src/core/kfileitem.cpp:318 #17 0x78346dab26bc in KFileItemPrivate::KFileItemPrivate (permissions=4294967295, mimeTypeDetermination=KFileItem::NormalMimeTypeDetermination, delayedMimeTypes=, urlIsDirectory=true, itemOrDirUrl=..., mode=4294967295, entry=..., this=0x56696d6e3890) at ./src/core/kfileitem.cpp:74 #18 KFileItem::KFileItem (this=, entry=..., itemOrDirUrl=..., delayedMimeTypes=, urlIsDirectory=, this=, entry=..., itemOrDirUrl=..., delayedMimeTypes=, urlIsDirectory=) at ./src/core/kfileitem.cpp:579 #19 0x78346db42c81 in KCoreDirListerCache::slotEntries (this=, job=, entries=...) at ./src/core/kcoredirlister.cpp:1202 #20 0x78346ba6355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #21 doActivate (sender=0x56696d4b77f0, signal_index=19, argv=0x7ffd456809f0) at ./src/corelib/kernel/qobject.cpp:4078 #22 0x78346daf5c08 in KIO::ListJob::entries (this=, _t1=, _t2=...) at ./obj-x86_64-linux-gnu/src/core/KF6KIOCore_autogen/include/moc_listjob.cpp:254 #23 0x78346ba6355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #24 doActivate (sender=0x56696d71aa10, signal_index=9, argv=0x7ffd45680c50) at ./src/corelib/kernel/qobject.cpp:4078 #25 0x78346db62598 in KIO::WorkerInterface::listEntries (_t1=..., this=0x56696d71aa10) at ./obj-x86_64-linux-gnu/src/core/KF6KIOCore_autogen/include/moc_workerinterface_p.cpp:539 #26 KIO::WorkerInterface::dispatch (this=0x56696d71aa10, _cmd=, rawdata=...) at ./src/core/workerinterface.cpp:146 #27 0x78346db5b5e3 in KIO::WorkerInterface::dispatch (this=0x56696d71aa10) at ./src/core/workerinterface.cpp:60 #28 0x78346db5814a in KIO::Worker::gotInput (this=0x56696d71aa10) at ./src/core/worker.cpp:263 #29 0x78346ba6355e in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:469 #30 doActivate (sender=0x56696d152ec0, signal_index=3, argv=0x7ffd45680e18) at ./src/corelib/kernel/qobject.cpp:4078 #31 0x78346b9fa272 in QObject::event (this=0x56696d152ec0, e=0x56696d587850) at
[xdg-desktop-portal-kde] [Bug 481029] Can't share screen with pipewire - kpipewire_logging: Window not available PipeWireSourceItem
https://bugs.kde.org/show_bug.cgi?id=481029 --- Comment #2 from Tomasz Kołosowski --- Just before the "Window not available" message starts spamming, I get these lines: xdg-desktop-portal-kde[5698]: qrc:/ScreenChooserDialog.qml:178: TypeError: Cannot call method 'standardButton' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:81: TypeError: Cannot read property 'minimumWidth' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:80: TypeError: Cannot read property 'minimumHeight' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:76: TypeError: Cannot read property 'flags' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:106: TypeError: Cannot call method 'standardButton' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:104: TypeError: Cannot call method 'standardButton' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:50: TypeError: Cannot read property 'dialogButtonBox' of null xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:84: TypeError: Cannot call method 'present' of null contentDialog.item.present() xdg-desktop-portal-kde[5698]: file:///usr/lib/qt6/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:84: TypeError: Cannot call method 'present' of null xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd694b7d0, id="pipeWireSourceItem", parent=0x5b8cd6879110, geometry=8,8 233x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481029] Can't share screen with pipewire - kpipewire_logging: Window not available PipeWireSourceItem
https://bugs.kde.org/show_bug.cgi?id=481029 --- Comment #1 from Tomasz Kołosowski --- One more thing, it did work flawlessly fro me under plasma 5, it's update to 6 that broke it somehow. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481029] New: Can't share screen with pipewire - kpipewire_logging: Window not available PipeWireSourceItem
https://bugs.kde.org/show_bug.cgi?id=481029 Bug ID: 481029 Summary: Can't share screen with pipewire - kpipewire_logging: Window not available PipeWireSourceItem Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@tkolo.pl CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When trying to share screen from any application (firefox, teams, element) the portal window with screen/application selectio never appears. Instead i get a continuous spam in system journal: xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) xdg-desktop-portal-kde[5698]: kpipewire_logging: Window not available PipeWireSourceItem(0x5b8cd685a800, id="pipeWireSourceItem", parent=0x5b8cd6964d50, geometry=8,8 234x110) STEPS TO REPRODUCE 1. Install plasma 6.0 RC2 2. Try to share screen with pipewire (not old/X11), i.e. from here https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ OBSERVED RESULT xdg-portal screen selection window never apperas, spam in journal logs EXPECTED RESULT xdg-portal window should appear and allow me to select which screen / application I want to share SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Possibly related to #469016 and #466320 though the only similarity I see is the log line - the cause in these bug reports seem to be different, hence a new report. Unlike in #469016 window previews in taskbar work flawlessly so no relation here. Restarting xdg-desktop-portal-kde (systemctl --user restart xdg-desktop-portal.service) causes the journal log spam to stop. -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 479178] xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 Tomasz changed: What|Removed |Added CC||tomy.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 479178] xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 Tomasz changed: What|Removed |Added CC||aleix...@kde.org, ||k...@davidedmundson.co.uk Component|general |general Product|kde |XWaylandVideoBridge Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479178] New: xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 Bug ID: 479178 Summary: xwaylandvideobridge doesn't work, shares white/black screen Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tomy.b...@gmail.com Target Milestone: --- SUMMARY *** The screen shared is just white or black Discord -> flatpak Xwayland bridge -> pacman and flatpak (kdeapps) *** STEPS TO REPRODUCE 1. Install discord 2. Install xwaylandvideobridge 3. Try to share screen through discord 4. Select A screen in the system popup 5. Select video bridge in discord 6. Nothing is shared OBSERVED RESULT White/Black screen is shared, if using the flatpak version, for me the pacman version just crashed. EXPECTED RESULT Screen is being shared SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C88 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 --- Comment #33 from Tomasz Chmielewski --- > Workaround, at least for the taskbar: Disable the middle mouse click function > in the taskbar settings. Where exactly is this setting? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 --- Comment #31 from Tomasz Chmielewski --- Just happened for me today with Konsole. KDE Plasma Version: 5.27.10 KDE Frameworks version: 5.112.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442321] Task manager sometimes opens new instance of an already-running app on left click when using wayland
https://bugs.kde.org/show_bug.cgi?id=442321 Tomasz Chmielewski changed: What|Removed |Added CC||man...@wpkg.org --- Comment #25 from Tomasz Chmielewski --- This happens also for me - randomly - on Kubuntu 23.04. Extremely annoying. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 464895] New: Crashing consistantly when opening league of legends
https://bugs.kde.org/show_bug.cgi?id=464895 Bug ID: 464895 Summary: Crashing consistantly when opening league of legends Classification: Plasma Product: lattedock Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tomy.b...@gmail.com Target Milestone: --- Application: latte-dock (0.10.77) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.7-zen1-1-zen x86_64 Windowing System: X11 Distribution: Garuda Linux DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: league of legends installed using this helper script https://github.com/kyechou/leagueoflegends The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7fa57bf8b444 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7fa57bfbb3b0 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7fa57bfa438e in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7fa57bfa7e1c in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7fa57bfac6b1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7fa57bf940a5 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fa57bf94544 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #11 0x7fa57bfedac5 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #12 0x7fa57c047fd1 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #13 0x7fa57bff8096 in () at /usr/lib/libQt5Quick.so.5 #14 0x7fa57bffcfa4 in () at /usr/lib/libQt5Quick.so.5 #15 0x7fa579ee432a in () at /usr/lib/libQt5Core.so.5 #16 0x7fa57989f8fd in () at /usr/lib/libc.so.6 #17 0x7fa579921d20 in () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fa54504e6c0 (LWP 67844) "KCupsConnection"): #1 0x7fa578716ee3 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7fa57876dae8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7fa578715132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fa57a0d8b4f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa57a0865ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa579ee725f in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fa5440cabee in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7fa579ee432a in () at /usr/lib/libQt5Core.so.5 #9 0x7fa57989f8fd in () at /usr/lib/libc.so.6 #10 0x7fa579921d20 in () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fa54c9486c0 (LWP 67794) "QQmlThread"): #1 0x7ffc5055b9a0 in clock_gettime () #2 0x7fa5798e671d in clock_gettime () at /usr/lib/libc.so.6 #3 0x7fa578716429 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #4 0x7fa57876da56 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fa578715132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #6 0x7fa57a0d8b4f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fa57a0865ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7fa579ee725f in QThread::exec() () at /usr/lib/libQt5Core.so.5 #9 0x7fa57bac00e0 in () at /usr/lib/libQt5Qml.so.5 #10 0x7fa579ee432a in () at /usr/lib/libQt5Core.so.5 #11 0x7fa57989f8fd in () at /usr/lib/libc.so.6 #12 0x7fa579921d20 in () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fa54d2ef6c0 (LWP 67762) "latte-dock"): #1 0x7fa575a8d524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7fa575a8e8a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7fa57989f8fd in () at /usr/lib/libc.so.6 #4 0x7fa579921d20 in () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa5553ff6c0 (LWP 67736) "QQmlThread"): #1 0x7fa579914367 in poll () at /usr/lib/libc.so.6 #2 0x7fa57876dbef in () at /usr/lib/libglib-2.0.so.0 #3 0x7fa578715132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fa57a0d8b4f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa57a0865ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fa579ee725f in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fa57bac00e0 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fa579ee432a in () at /usr/lib/libQt5Core.so.5 #9 0x7fa57989f8fd in () at /usr/lib/libc.so.6 #10 0x7fa579921d20 in
[plasmashell] [Bug 463525] cannot launch kickoff menu item by pressing Enter after selecting with Tab
https://bugs.kde.org/show_bug.cgi?id=463525 Tomasz Osak changed: What|Removed |Added CC||to...@poczta.fm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463525] New: cannot launch kickoff menu item by pressing Enter after selecting with Tab
https://bugs.kde.org/show_bug.cgi?id=463525 Bug ID: 463525 Summary: cannot launch kickoff menu item by pressing Enter after selecting with Tab Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: to...@poczta.fm CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 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. Press WINDOWS aka META => kickoff opens 2. Press Tab a few times to select desired item (here "Uruchom ponownie", that in Polish means "Restart") 3. Having selected "Uruchom ponownie" press Enter => item "Uruchom ponownie" loses focus and nothing else happens. OBSERVED RESULT Enter did not launch selected menu item. EXPECTED RESULT Pressing Enter launches selected menu item. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 36 (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462710] New: Crash when Unchecking Allow all users to use this network
https://bugs.kde.org/show_bug.cgi?id=462710 Bug ID: 462710 Summary: Crash when Unchecking Allow all users to use this network Classification: Applications Product: systemsettings Version: 5.26.4 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: coo...@buntownik.pl Target Milestone: --- Application: systemsettings (5.26.4) Qt Version: 5.15.7 Frameworks Version: 5.100.0 Operating System: Linux 6.0.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: System settings every time when I try to uncheck VPN network option in General saying "allow all users to use this network" The crash can be reproduced every time. -- Backtrace: Application: Ustawienia systemowe (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f14b01b3c28 in WifiSecurity::setStoreSecretsSystemWide(bool) () at /lib64/libplasmanm_editor.so #5 0x7f14cb9132cd in () at /lib64/libQt5Core.so.5 #6 0x7f14cb9132cd in () at /lib64/libQt5Core.so.5 #7 0x7f14cc6a7fde in QCheckBox::stateChanged(int) () at /lib64/libQt5Widgets.so.5 #8 0x7f14cc698c4a in () at /lib64/libQt5Widgets.so.5 #9 0x7f14cc698d97 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7f14cc5e6c38 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7f14cc5a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7f14cc5ad922 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f14cb8dc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f14cc5aba9e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #15 0x7f14cc5ffa58 in () at /lib64/libQt5Widgets.so.5 #16 0x7f14cc602fb0 in () at /lib64/libQt5Widgets.so.5 #17 0x7f14cc5a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #18 0x7f14cb8dc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #19 0x7f14cbd7b9ad in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #20 0x7f14cbd4f37c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #21 0x7f14c80c30fa in () at /lib64/libQt5XcbQpa.so.5 #22 0x7f14ca11ca90 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #23 0x7f14ca11ce48 in () at /lib64/libglib-2.0.so.0 #24 0x7f14ca11cedc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #25 0x7f14cb933b56 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #26 0x7f14cb8dab9b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7f14cb8e2d06 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #28 0x5645e64e3fa8 in () #29 0x7f14cb02c5b0 in __libc_start_call_main () at /lib64/libc.so.6 #30 0x7f14cb02c679 in __libc_start_main_impl () at /lib64/libc.so.6 #31 0x5645e64e48d5 in () [Inferior 1 (process 19667) detached] The reporter indicates this bug may be a duplicate of or related to bug 461924. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 Tomasz Paweł Gajc changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #5 from Tomasz Paweł Gajc --- Ok after a deep dive i found a culprit inside one of downstream patches. Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 --- Comment #4 from Tomasz Paweł Gajc --- Ok, i know what is going on. Will come back with a PR to fix this today. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 Tomasz Paweł Gajc changed: What|Removed |Added Component|wayland-generic |general --- Comment #3 from Tomasz Paweł Gajc --- I tried with startplasma-x11 and i got the same effect o_0 Even dowgrade mesa to 22.2.3 without no luck -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 --- Comment #2 from Tomasz Paweł Gajc --- [tpg@omv-rockpro64 ~]$ kwin_wayland --exit-with-session konsole No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is set kf.globalaccel.kglobalacceld: No desktop file found for service "krunner.desktop" OpenGL vendor string: Panfrost OpenGL renderer string: Mali-T860 (Panfrost) OpenGL version string: 3.1 (Core Profile) Mesa 22.3.0 Driver: Panfrost GPU class: Mali T8xx series OpenGL version: 3.1 Mesa version: 22.3 Linux kernel version: 6.1 Requires strict binding:no GLSL shaders: no Texture NPOT support: yes Virtual Machine:no kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker" kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate" libkwinglutils: Shaders are not supported libkwinglutils: Failed to link shader: "error: no shaders attached to the program\n\x00" libkwinglutils: Shaders are not supported libkwinglutils: Failed to link shader: "error: no shaders attached to the program\n\x00" libkwinglutils: Shaders are not supported libkwinglutils: Failed to link shader: "error: no shaders attached to the program\n\x00" libkwinglutils: Shaders are not supported libkwinglutils: Failed to link shader: "error: no shaders attached to the program\n\x00" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 Tomasz Paweł Gajc changed: What|Removed |Added Platform|Other |OpenMandriva -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 --- Comment #1 from Tomasz Paweł Gajc --- Created attachment 154207 --> https://bugs.kde.org/attachment.cgi?id=154207=edit MESA_GL_VERSION_OVERRIDE=2.0 WAYLAND_DEBUG=1 KWIN_GL_DEBUG=1 kwin_wayland --exit-with-session konsole -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462518] New: Black screen when running kwin_wayland on rk3399
https://bugs.kde.org/show_bug.cgi?id=462518 Bug ID: 462518 Summary: Black screen when running kwin_wayland on rk3399 Classification: Plasma Product: kwin Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tpg...@gmail.com Target Milestone: --- Created attachment 154206 --> https://bugs.kde.org/attachment.cgi?id=154206=edit WAYLAND_DEBUG=1 KWIN_GL_DEBUG=1 kwin_wayland --exit-with-session konsole SUMMARY I noticed that kwin_wayland produces black screen on my rk3399 (rockpro64) when i run Plasma or sddm Weston works wihout any problems. When i run MESA_GL_VERSION_OVERRIDE=2.0 kwin_wayland --exit-with-session konsole i see a black screen with a white rectangle which i seems it is a konsole window This gives a konsole window with decorations with swrast and it works like expected - MESA_GL_VERSION_OVERRIDE=1.0 kwin_wayland --exit-with-session konsole STEPS TO REPRODUCE 1. Run startplasma-wayland on rk3399 i.e Pine64 rockpro64 2. Observe a black screen 4. kill session 5. Run kwin_wayland --exit-with-session konsole - from fresh VT on rk3399 i.e Pine64 rockpro64 6. Observe a black screen OBSERVED RESULT Black empty screen EXPECTED RESULT Working plasma SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenMandriva cooker aarch64 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100 Qt Version: 5.15.7 with all the KDE patches ADDITIONAL INFORMATION [tpg@omv-rockpro64 ~]$ rpm -qf $(command -v kwin_wayland) kwin-wayland-5.26.4-1.aarch64 [tpg@omv-rockpro64 ~]$ rpm -qf /usr/lib64/libQt5Core.so.5 lib64qt5core5-5.15.7-5.aarch64 [tpg@omv-rockpro64 ~]$ rpm -qf /usr/lib64/libKF5WaylandClient.so.5 lib64KF5WaylandClient5-5.100.0-1.aarch64 [tpg@omv-rockpro64 ~]$ rpm -qf /usr/lib64/libOSMesa.so.8 lib64osmesa8-22.3.0-1.aarch64 [tpg@omv-rockpro64 ~]$ uname -a Linux omv-rockpro64 6.1.0-server-0.rc7.2omv2290 #1 SMP PREEMPT_DYNAMIC Mon Nov 2 8 08:47:13 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 454947] Cannot map buttons due to incorrect xsetwacom invocation
https://bugs.kde.org/show_bug.cgi?id=454947 --- Comment #4 from Tomasz Lemiech --- PR tested on Intuos 4. Works OK. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 462074] New: kdevelop site under maintenance for a long time
https://bugs.kde.org/show_bug.cgi?id=462074 Bug ID: 462074 Summary: kdevelop site under maintenance for a long time Classification: Applications Product: kdevelop Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: to...@poczta.fm 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. go to the website: www.kdevelop.org 2. click a link: "News" or "Features" or "Contribute" or "About" or "Support" or "Donate" OBSERVED RESULT "Site under maintenance" appears. EXPECTED RESULT Respective sites should appear. 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.
[korganizer] [Bug 460197] KOrganizer 22.08.1 crashes when trying to create a new event
https://bugs.kde.org/show_bug.cgi?id=460197 Tomasz Kołosowski changed: What|Removed |Added CC||tomek+kdeb...@kolosowscy.pl --- Comment #1 from Tomasz Kołosowski --- Same issue here, identical system environment (Arch Linux, latest KDE). I can add that my calendar is Nextcloud/WebDAV based. I also noticed that events from that calendar did not appear in KOrganizer. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458360] Mistranslation in Polish for Media Controls plugin in KDE Connect
https://bugs.kde.org/show_bug.cgi?id=458360 --- Comment #1 from Tomasz Huczek --- Created attachment 151625 --> https://bugs.kde.org/attachment.cgi?id=151625=edit Video showcasing the problem -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458360] New: Mistranslation in Polish for Media Controls plugin in KDE Connect
https://bugs.kde.org/show_bug.cgi?id=458360 Bug ID: 458360 Summary: Mistranslation in Polish for Media Controls plugin in KDE Connect Product: kdeconnect Version: 22.08.0 Platform: Android OS: Other Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: tomjh9...@gmail.com Target Milestone: --- SUMMARY Plugins for Media Controls (Sterowanie Odtwarzaczem) have wrong descriptions and they do the opposite of what the say they do STEPS TO REPRODUCE 1. Set language to Polish 2. Open KDE Connect app on your device 3. Go into plugin settings OBSERVED RESULT The descriptions for Media Controls (Sterowanie Odtwarzaczem) do not match their actions EXPECTED RESULT The descriptions should be flipped for these plugins SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.19.2-arch1-1 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 KDE Connect app Version: 1.19.1 (from F-Droid) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450473] Transparent windows content on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=450473 --- Comment #3 from Tomasz Paweł Gajc --- Hi, Looks like there were some problems with mesa, because after couple of upgrades things started to work on aarch64. IMHO this can be closed. [tpg@omv-rockpro64 ~/OpenMandriva/rpmlint]$ LC_ALL=C qdbus org.kde.KWin /KWin supportInformation Informacje o wsparciu dla KWin: Pytając na np. https://forum.kde.orgużyj wyświetlanych tu danych. Dostarczają one informacji o obecnie uruchomionym wystąpieniu, o opcjach, które są używane, o używanym sterowniku OpenGL i o włączonych efektach. Proszę wysłać te informacje, pod tekstem wprowadzenia, przy użyciu usługi paste bin takiej jak https://paste.kde.org, aby nie zaśmiecać wątku. == Version === KWin version: 5.25.1 Qt Version: 5.15.5 Qt compile version: 5.15.4 XCB compile version: 1.15 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: OpenMandriva Vendor Release: 12201002 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,5,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Platform == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: Breeze_Snow themeSize: 24 Options === focusPolicy: 0 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 6 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 0 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: Screen Edges desktopSwitching: false desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: HDMI-A-1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 6 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL ES 2.0 OpenGL vendor string: Panfrost OpenGL renderer string: Mali-T860 (Panfrost) OpenGL version string: OpenGL ES 3.1 Mesa 22.1.2 OpenGL platform interface: EGL OpenGL shading language version string: OpenGL ES GLSL ES 3.10 Driver: Panfrost GPU class: Mali T8xx series OpenGL version: 3.1 GLSL version: 3.10 Mesa version: 22.1.2 Linux kernel version: 5.18.7 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- kwin4_effect_windowaperture kwin4_effect_squash kwin4_effect_sessionquit kwin4_effect_scale kwin4_effect_logout kwin4_effect_login kwin4_effect_fadingpopups kwin4_effect_dialogparent colorpicker blendchanges screenshot screenedge zoom slidingpopups slide kwin4_effect_morphingpopups kwin4_effect_maximize kwin4_effect_fullscreen kwin4_effect_frozenapp desktopgrid highlightwindow overview windowview startupfeedback kscreen screentransform Currently Active Effects: - Effect Settings: kwin4_effect_windowaperture: pluginId: kwin4_effect_windowaperture isActiveFullScreenEffect: false kwin4_effect_squash: pluginId
[wacomtablet] [Bug 454947] New: Cannot map buttons due to incorrect xsetwacom invocation
https://bugs.kde.org/show_bug.cgi?id=454947
Bug ID: 454947
Summary: Cannot map buttons due to incorrect xsetwacom
invocation
Product: wacomtablet
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jazzv...@gmail.com
Reporter: szpaj...@gmail.com
Target Milestone: ---
Commit dd97e6ab6a0a91d01d54a02131685e5d1fc78c05 ("Fix Qt 5.15 obsoletions")
introduced the new syntax of QProcess.start() routine in xsetwacomadaptor.cpp
(modified further in 88422002167f941e1457695a0e9fa3b1212c32f3). It requires
command arguments to be passed as a QStringList rather than as a single
QString. Unfortunately this broke the ability to map express buttons because
the resulting xsetwacom command line string is built incorrectly.
The current invocation in XsetwacomAdaptor::setParameter():
setConf.start(QString::fromLatin1("xsetwacom"), QStringList() <<
QString::fromLatin1("set") << device << param);
results in the following execve() call for button mappings:
execve("/usr/bin/xsetwacom", ["/usr/bin/xsetwacom", "set", "Wacom Intuos4 4x6
Pad pad", "Button 1", "key ctrl shift e"], 0x7ffe783a6088 /* 74 vars */
This is incorrect, because xsetwacom expects "Button" and the button number to
be in separate arguments, while the above call passes it as one. Executing the
above command string manually yields the following error:
$ "/usr/bin/xsetwacom" "set" "Wacom Intuos4 4x6 Pad pad" "Button 1" "key ctrl
shift e"
Parameter 'Button 1' is no longer in use. It was replaced with 'Button'.
The old way of doing this was:
cmd = QString::fromLatin1( "xsetwacom set \"%1\" %2 \"%3\"" ).arg( device
).arg( param ).arg( value );
QProcess setConf;
setConf.start( cmd );
which produced this:
execve("/usr/bin/xsetwacom", ["/usr/bin/xsetwacom", "set", "Wacom Intuos4 4x6
Pad pad", "Button", "1", "key ctrl shift e"], 0x7ffcfd4ad278 /* 75 vars */
and this works fine, because %2 is not enclosed in quotes, so "Button 1" gets
split in two arguments.
Further changes to the xsetwacom launching code introduced in commit
88422002167f941e1457695a0e9fa3b1212c32f3 did not fix the problem.
STEPS TO REPRODUCE
1. Install wacomtablet.so from current git master
2. Try to map some buttons in the Express Buttons GUI
3. Apply the changes or replug the tablet
OBSERVED RESULT
Mappings are set according to the settings entered in the GUI
EXPECTED RESULT
Mappings are kept at their defaults.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 450473] Transparent windows content on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=450473 Tomasz Paweł Gajc changed: What|Removed |Added Version|5.24.1 |5.24.2 --- Comment #1 from Tomasz Paweł Gajc --- Nothing changed on 5.24.2 :( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450473] Transparent windows content on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=450473 Tomasz Paweł Gajc changed: What|Removed |Added Keywords||wayland Platform|Other |OpenMandriva Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450473] New: Transparent windows content on Plasma Wayland
https://bugs.kde.org/show_bug.cgi?id=450473 Bug ID: 450473 Summary: Transparent windows content on Plasma Wayland Product: kwin Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tpg...@gmail.com Target Milestone: --- Created attachment 146877 --> https://bugs.kde.org/attachment.cgi?id=146877=edit transparent windows SUMMARY It started to happen somewhere in Nov 2021. When i login to Plasma(Wayland) session and i start some app, like konsole then it starts but its window content are transparent. Almost all KDE applications behaves like that. i found nothing in journalctl, even with mesa or qt in debug mode. What is important if i login into Weston session from sddm, then everything works like expected - no transparent window content. STEPS TO REPRODUCE 1. Login to PlasmaWayland 2. start konsole - see transparent window content 3. start falkon - see transparent window content 4. start systemsettings - see window content behaves like expected OBSERVED RESULT Transparent windows content under Plasma Wayland EXPECTED RESULT See real windows content SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: OpenMandriva Lx 4.50 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 (with all the up to date patches from KDE git) Kernel Version: 5.16.0-server-clang-1omv4050 (64-bit) Processors: 4 × ARM Cortex-A53, 2 × ARM Cortex-A72 Memory: 3.7 GiB of RAM Graphics Processor: Mali-T860 ADDITIONAL INFORMATION I'm running on Pine RockPro64 aarch64 [tpg@omv-rockpro64 ~]$ inxi -sG Graphics: Device-1: display-subsystem driver: rockchip_drm v: N/A Device-2: rk3399-dw-hdmi driver: dwhdmi_rockchip v: N/A Device-3: rk3399-mali driver: panfrost v: kernel Display: x11 server: OpenMandriva X.org 1.21.1.3 driver: loaded: modesetting resolution: 1920x1080~60Hz OpenGL: renderer: Mali-T860 (Panfrost) v: 3.1 Mesa 22.0.0-rc2 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 437923] Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 --- Comment #2 from Tomasz Osak --- Created attachment 144236 --> https://bugs.kde.org/attachment.cgi?id=144236=edit New crash information added by DrKonqi khelpcenter (5.7.6.21083) using Qt 5.15.2 - What I was doing when the application crashed: I was viewing Okular's help. - Custom settings of the application: Okular 21.08.3-1 from Official repositories extra in Manjaro KDE Operating System: Manjaro Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 5700 -- Backtrace (Reduced): #4 0x7f45fc9ee154 in _XGetRequest () from /usr/lib/libX11.so.6 #5 0x7f45fc9c7f17 in XChangeWindowAttributes () from /usr/lib/libX11.so.6 #6 0x7f45ff1429e7 in KHTMLView::mouseMoveEvent(QMouseEvent*) () from /usr/lib/libKF5KHtml.so.5 #7 0x7f45fe040fce in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #8 0x7f45fe0f1a93 in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 437923] Okular help crash when opening
https://bugs.kde.org/show_bug.cgi?id=437923 Tomasz Osak changed: What|Removed |Added CC||to...@poczta.fm -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 --- Comment #27 from Tomasz Lemiech --- (In reply to Eduardo from comment #26) > What happens to this new kdeconnectd when we have this patch applied? Does > it keep running forever or is it killed somehow? It gets killed together with everything else. I don't see it lingering after I log off from KDE. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Tomasz Lemiech changed: What|Removed |Added Attachment #143454|ksmserver fix |ksmserver_reject_new_client description||s_when_in_killing_state.dif ||f -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 --- Comment #22 from Tomasz Lemiech --- Created attachment 143454 --> https://bugs.kde.org/attachment.cgi?id=143454=edit ksmserver fix -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown
https://bugs.kde.org/show_bug.cgi?id=432643 Tomasz Lemiech changed: What|Removed |Added CC||szpaj...@gmail.com --- Comment #21 from Tomasz Lemiech --- Same thing here. Gentoo, no systemd, plasma-workspace-5.22.5, kdeconnect-21.04.3. Here is what happens: - ksmserver sends SmsDie to its clients (including kdeconnectd) - kdeconnectd exits correctly and immediately gets restarted via dbus (requested by plasmashell) - the new kdeconnectd instance connects to ksmserver with a new client ID - ksmserver wants to kill it, but SmsDie times out (here comes the 10-sec delay) - finally everything quits. So it's not the original kdeconnectd process which is causing the problem, but the new one, which came up after the first one exited. Presumably it's a race condition of some sort - the process might not yet be ready to handle messages from ksmserver (or maybe the message callbacks are not yet registered). Never mind - at this stage it does not respond to SmsDie. Given the fact that ksmserver was about to shut down itself and was in the process of killing its clients, I think it shouldn't have accepted the new client in the first place. Otherwise if the new client had responded to SmsDie properly, it could have been restarted once again and in theory this could loop multiple times preventing ksmserver from emptying its client list completely. Attached patch (ksmserver_reject_new_clients_when_in_killing_state.diff) does what the file name says. Works for me, no more hangs on exit. Logs before (note the different client IDs of the initial kdeconnectd instance and the one which fails to respond to SmsDie): org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366413980190510004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366413980190510004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366413980190510004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366413980190510004 ) (...) org.kde.kf5.ksmserver: Starting killing clients (...) org.kde.kf5.ksmserver: startKilling: client "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366413980190510004 ) (...) org.kde.kf5.ksmserver: We killed all clients. We have now clients.count()= 7 (...) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366414160190510008 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366414160190510008 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366414160190510008 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366414160190510008 ) org.kde.kf5.ksmserver: SmsDie timeout, client "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366414160190510008 ) Logs after (the new kdeconnectd instance tries to connect but gets rejected): org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366408890157090004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366408890157090004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366408890157090004 ) org.kde.kf5.ksmserver: New client properties: "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366408890157090004 ) (...) org.kde.kf5.ksmserver: Starting killing clients (...) org.kde.kf5.ksmserver: startKilling: client "/usr/lib64/libexec/kdeconnectd" ( 10e0656c6900016366408890157090004 ) (...) org.kde.kf5.ksmserver: We killed all clients. We have now clients.count()= 11 (...) org.kde.kf5.ksmserver: Connection rejected: ksmserver is shutting down -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Plasma crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #59 from Tomasz Paweł Gajc --- I see now that plasmashell process just does clean exit when screen goes off. [root@omv-rockpro64 .config]# rpm -qf $(command -v plasmashell) plasma-workspace-5.22.90-1.aarch64 Anything related to this issue in my journal log: Sep 24 19:13:08 omv-rockpro64 kded5[283183]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 24 19:13:08 omv-rockpro64 org_kde_powerdevil[283198]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Sep 24 19:13:08 omv-rockpro64 kded5[283183]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. coredumpctl is clean -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Tomasz Paweł Gajc changed: What|Removed |Added Flags||Wayland+ Product|kwin|plasmashell Component|wayland-generic |generic-crash Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #40 from Tomasz Paweł Gajc --- Openmandriva Lx Cooker with Plasma-5.22.3, Frameworks-5.84.0 and up to date patchset for Qt5 i no longer observer any plasmashell crashes with Wayland. coredumpctl is clean when my monitor goes into standby, but yet plasmashell as a process is terminated: Jul 18 00:50:36 omv-rockpro64 org_kde_powerdevil[97696]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 kded5[97674]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: Old primary output: QScreen(0x3a12a290, name="HDMI-A-1") New primary output: QScreen(0x3bd30840, name="") Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: trying to show an empty dialog Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:121: TypeError: Cannot read property 'x' of null Jul 18 00:50:36 omv-rockpro64 plasmashell[97698]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:135: TypeError: Cannot read property 'y' of null Jul 18 00:50:36 omv-rockpro64 systemd[84533]: Started dbus-:1.2-org.kde.KSplash@2.service. Jul 18 00:50:37 omv-rockpro64 kded5[97674]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. Jul 18 00:50:37 omv-rockpro64 plasmashell[97698]: The Wayland connection experienced a fatal error: Błąd protokołu Jul 18 00:50:40 omv-rockpro64 kded5[97674]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:40 omv-rockpro64 org_kde_powerdevil[97696]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Jul 18 00:50:40 omv-rockpro64 kded5[97674]: kscreen.kded: Config does not have at least one screen enabled, WILL NOT save this config, this is not what user wants. Jul 18 00:51:17 omv-rockpro64 klauncher[97917]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Jul 18 00:51:37 omv-rockpro64 plasma_waitforname[97885]: org.kde.knotifications: WaitForName: Service was not registered within timeout Jul 18 00:51:37 omv-rockpro64 systemd[84533]: dbus-:1.2-org.kde.KSplash@2.service: Main process exited, code=exited, status=1/FAILURE Jul 18 00:51:37 omv-rockpro64 systemd[84533]: dbus-:1.2-org.kde.KSplash@2.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Tomasz Paweł Gajc changed: What|Removed |Added CC||tpg...@gmail.com --- Comment #29 from Tomasz Paweł Gajc --- same thing happens on OpenMandriva Lx cooker with up to date Plasma 5.21.5 and framweworks 5.82.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431311] Discount (required version >= 2) can not be found
https://bugs.kde.org/show_bug.cgi?id=431311 --- Comment #3 from Tomasz Paweł Gajc --- Yes libmarkdown-devel is installed in buildroot, you can notice that on logs I did attach. -- Found discount: /usr/lib64/libmarkdown.so Seems like okularGenerator_md.so is linked to libmarkdown.so.2(), so came is somehow broken with its false positive tests. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 431312] New: Add OpenMandriva to Platform dropdown list
https://bugs.kde.org/show_bug.cgi?id=431312 Bug ID: 431312 Summary: Add OpenMandriva to Platform dropdown list Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: tpg...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY Hi, please add OpenMandriva to Platform drop down list STEPS TO REPRODUCE 1. File a bug report 2. Choose OS: Linux 3. Cant find OpenMandriva in Platform list, so choose Other OBSERVED RESULT No OpenMandriva Linux distribution to choose from Platform dropdown list EXPECTED RESULT I can choose OpenMandriva from Platform dropdown list 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.
[okular] [Bug 431311] New: Discount (required version >= 2) can not be found
https://bugs.kde.org/show_bug.cgi?id=431311 Bug ID: 431311 Summary: Discount (required version >= 2) can not be found Product: okular Version: 20.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: tpg...@gmail.com Target Milestone: --- Created attachment 134660 --> https://bugs.kde.org/attachment.cgi?id=134660=edit Build Log SUMMARY I'm building Okular-20.12.1 with enabled Discount support. Unfortunately cmake cannot it find. STEPS TO REPRODUCE 1. install discount-2.2.7 2. run okular build 3. OBSERVED RESULT -- The following OPTIONAL packages have not been found: * Discount (required version >= 2) EXPECTED RESULT Discount is found and Okular is build with libmarkdown support SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenMandriva Cooker 4.2 RC (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Build logs with tracing enabled here https://abf.openmandriva.org/build_lists/932120 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424408] Multiple coredumps with every login/logout
https://bugs.kde.org/show_bug.cgi?id=424408 Tomasz Paweł Gajc changed: What|Removed |Added CC||tpg...@gmail.com --- Comment #37 from Tomasz Paweł Gajc --- Hi, i have a fully updated OpenMandriva cooker with Plasma 5.20.4 and KDE Frameworks 5.77.0 [root@tpg-virtualbox systemd]# rpm -qa | grep plasma-workspace plasma-workspace-wayland-5.20.4-3.x86_64 plasma-workspace-5.20.4-3.x86_64 plasma-workspace-x11-5.20.4-3.x86_64 After hitting logout on Plasma Wayland session i see these in coredumpctl: Fri 2020-12-11 12:30:07 CET1955 1001 1006 6 present /usr/lib64/libexec/drkonqi Fri 2020-12-11 12:30:08 CET 896 1001 1006 6 present /usr/lib64/libexec/kdeconnectd Fri 2020-12-11 12:30:08 CET 921 1001 1006 6 present /usr/lib64/libexec/org_kde_powerdevil Fri 2020-12-11 12:30:18 CET 843 1001 1006 6 present /usr/bin/kded5 Fri 2020-12-11 12:30:18 CET1954 1001 1006 6 present /usr/bin/plasmashell gru 11 12:29:56 tpg-virtualbox su[1089]: pam_unix(su:session): session closed for user root gru 11 12:29:56 tpg-virtualbox systemd[754]: app-org.kde.konsole-919a169276f3431ba46e448492368421.scope: Succeeded. gru 11 12:29:56 tpg-virtualbox plasmashell[1954]: file:///usr/lib64/qt5/qml/org/kde/plasma/components/ModelContextMenu.qml:38:1: QML ModelContextMenu: Ac> gru 11 12:29:57 tpg-virtualbox plasmashell[1954]: file:///usr/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:91:17: Unabl> gru 11 12:29:57 tpg-virtualbox kaccess[870]: The X11 connection broke (error 1). Did the X11 server die? gru 11 12:29:57 tpg-virtualbox kactivitymanagerd[912]: The X11 connection broke (error 1). Did the X11 server die? gru 11 12:29:57 tpg-virtualbox kernel: A fatal guest X Window error occurred. This may just mean that the Window system was shut down while the client w> gru 11 12:29:57 tpg-virtualbox kernel: A fatal guest X Window error occurred. This may just mean that the Window system was shut down while the client w> gru 11 12:29:57 tpg-virtualbox kded5[843]: ktp-kded-module: activity service not running, user account presences won't load or save gru 11 12:29:57 tpg-virtualbox kernel: A fatal guest X Window error occurred. This may just mean that the Window system was shut down while the client w> gru 11 12:29:57 tpg-virtualbox kernel: Terminating ... gru 11 12:29:57 tpg-virtualbox kernel: Terminating HGCM thread ... gru 11 12:29:57 tpg-virtualbox kernel: Terminating X11 thread ... gru 11 12:29:57 tpg-virtualbox systemd[754]: dbus-:1.2-org.kde.ActivityManager@0.service: Succeeded. gru 11 12:29:57 tpg-virtualbox org_kde_powerdevil[921]: The Wayland connection broke. Did the Wayland compositor die? gru 11 12:29:57 tpg-virtualbox kdeconnectd[896]: The Wayland connection broke. Did the Wayland compositor die? gru 11 12:29:57 tpg-virtualbox drkonqi[1955]: The Wayland connection broke. Did the Wayland compositor die? gru 11 12:29:57 tpg-virtualbox plasmashell[1954]: The Wayland connection broke. Did the Wayland compositor die? gru 11 12:29:57 tpg-virtualbox kded5[843]: The Wayland connection broke. Did the Wayland compositor die? gru 11 12:29:58 tpg-virtualbox drkonqi[1989]: Failed to create wl_display (No such file or directory) gru 11 12:29:58 tpg-virtualbox drkonqi[1989]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. gru 11 12:29:58 tpg-virtualbox drkonqi[1989]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the appli> Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, wayland-egl, wayland, wayland-xcomposite-e> gru 11 12:29:58 tpg-virtualbox systemd[1]: Created slice system-systemd\x2dcoredump.slice. gru 11 12:29:58 tpg-virtualbox systemd[1]: Started Process Core Dump (PID 1994/UID 0). gru 11 12:29:58 tpg-virtualbox drkonqi[1993]: Failed to create wl_display (No such file or directory) gru 11 12:29:58 tpg-virtualbox drkonqi[1993]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. gru 11 12:29:58 tpg-virtualbox drkonqi[1993]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the appli> Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, wayland-egl, wayland, wayland-xcomposite-e> gru 11 12:29:58 tpg-virtualbox kernel: Error waiting for X11 thread to terminate: VERR_TIMEOUT gru 11 12:29:58 tpg-virtualbox kernel: Terminating threads done gru 11 12:29:58 tpg-virtualbox sddm-helper[745]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_close_session gru 11 12:29:58 tpg-virtualbox sddm-helper[745]: pam_unix(sddm:session): session
[kscreenlocker] [Bug 430206] New: screen saver unlocks session even if PAM time restrictions apply in /etc/security/time.conf
https://bugs.kde.org/show_bug.cgi?id=430206 Bug ID: 430206 Summary: screen saver unlocks session even if PAM time restrictions apply in /etc/security/time.conf Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: coo...@buntownik.pl CC: bhus...@gmail.com Target Milestone: --- SUMMARY screen saver unlocks session even if PAM time restrictions apply in /etc/security/time.conf - after logout there is no way to log into but locking does not prevent user to unlock STEPS TO REPRODUCE 1. Log into KDE session when time restrictions allows to do so 2. lock session and wait/configure until time restrictions apply 3. enter password - PAM is ineffective/not verified against PAM_time.so and user can unlock his session. OBSERVED RESULT PAM time restrictions innefective EXPECTED RESULT PAM time restrictions apply to every application which authenticate also to screen locking SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma 5.20.3 (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 425822] 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 Tomasz Paweł Gajc changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Tomasz Paweł Gajc --- Sorry for the noise. After proper update to 1.8 version things are compiling without errors. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 425822] 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 Tomasz Paweł Gajc changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Tomasz Paweł Gajc --- Hi, ive added your commit to clazy-1.8 build. Still same error: https://abf.openmandriva.org/build_lists/917634 /usr/include/llvm/Support/type_traits.h:31:28: error: no template named 'remove_reference_t' in namespace 'std'; did you mean 'remove_reference'? using UnderlyingT = std::remove_reference_t; ~^ https://github.com/OpenMandrivaAssociation/clazy/commit/0a749bf7fd51cce3006737bba22a0fa5acd727a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428614] New: Plasma-Wayland Crashes and resets shortly after login
https://bugs.kde.org/show_bug.cgi?id=428614 Bug ID: 428614 Summary: Plasma-Wayland Crashes and resets shortly after login Product: plasmashell Version: 5.19.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: to...@poczta.fm CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.5) Qt Version: 5.15.1 Frameworks Version: 5.73.0 Operating System: Linux 5.8.16-300.fc33.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 33 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: I logged in. The mouse cursor has frozen. I moved the mouse. System crashed and reset. - Unusual behavior I noticed: The mouse cursor has frozen. - Additional info There are addtional errors related to the "xorg-x11-drv-nouveau". My system: Laptop ASUS TUF FX705DT AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx NVIDIA GeForce GTX 1650 4GB -- Backtrace: Application: Plazma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f92bc410bc5 in raise () from /lib64/libc.so.6 #5 0x7f92bc3f98a4 in abort () from /lib64/libc.so.6 #6 0x7f92bc81cb07 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #8 0x7f92ab0925ed in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () from /lib64/libQt5WaylandClient.so.5 #9 0x7f92ab093f90 in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () from /lib64/libQt5WaylandClient.so.5 #10 0x7f92a83c40aa in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #11 0x7f92be32e0fc in QSGRenderThread::syncAndRender(QImage*) () from /lib64/libQt5Quick.so.5 #12 0x7f92be330c2f in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #13 0x7f92bc8514bc in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #14 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #15 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92bc856e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f92be3310c5 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #3 0x7f92bc8514bc in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #4 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #5 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92a2ec2f2b in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f92a2ec29f7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f92bbd033f9 in start_thread () from /lib64/libpthread.so.0 #4 0x7f92bc4d4b03 in clone () from /lib64/libc.so.6 #1 0x7f92baf7b078 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #2 0x7f92baf7cb83 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f92bafcdc4b in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7f92baf7a41f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f92bca2da4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f92bc9e165b in
[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled
https://bugs.kde.org/show_bug.cgi?id=353062 --- Comment #10 from Tomasz Borowik --- (In reply to Tomasz Borowik from comment #9) > Soon we'll need a whole new system service for managing environment variable > workarounds to launch any gui program;p Sorry for being snarky, posted mainly to mention the workaround in my case, not to just complain. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 353062] Freeze/failure to start when "show tray icon" is enabled
https://bugs.kde.org/show_bug.cgi?id=353062 Tomasz Borowik changed: What|Removed |Added CC||timo...@gmail.com --- Comment #9 from Tomasz Borowik --- +10 can't remember how many years I've been suffering this. Using dwm + trayer on nixos, and this completely blocks various minor kde/qt applications from launching at all. For me the QT_QPA_PLATFORMTHEME workaround doesn't work. But this does: unset XDG_CURRENT_DESKTOP Now if I remember correctly adding XDG_CURRENT_DESKTOP=kde somewhere was a workaround for some other failure, unfortunately can't remember what. Soon we'll need a whole new system service for managing environment variable workarounds to launch any gui program;p -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428044] New: tools buttons modification
https://bugs.kde.org/show_bug.cgi?id=428044 Bug ID: 428044 Summary: tools buttons modification Product: Breeze Version: 5.20.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: dudzi...@gmail.com Target Milestone: --- SUMMARY Please do windows header/tools buttons inline with windeco buttons. This would save space and give the window a slick look! 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.
[clazy] [Bug 425822] New: 1.7 version does not compile with LLVM/clang-11.x
https://bugs.kde.org/show_bug.cgi?id=425822 Bug ID: 425822 Summary: 1.7 version does not compile with LLVM/clang-11.x Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tpg...@gmail.com CC: smart...@kde.org Target Milestone: --- SUMMARY 1.7 version does not compile with LLVM/clang-11.x STEPS TO REPRODUCE 1. set LLVM/clang-11.x as default compiler 2. try to compile clazy-1.7 3. observe error OBSERVED RESULT Full logs can be found here https://abf.openmandriva.org/build_lists/817596 [1/107] Building CXX object CMakeFiles/ClazyPlugin.dir/src/checks/manuallevel/tr-non-literal.cpp.o FAILED: CMakeFiles/ClazyPlugin.dir/src/checks/manuallevel/tr-non-literal.cpp.o /usr/bin/clang++ -DCLAZY_DISABLE_AST_MATCHERS -DClazyPlugin_EXPORTS -DHAVE_CLANG_CONFIG_H -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -I. -I../ -I../src -Os -fomit-frame-pointer -g1 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -m64 -mtune=generic -std=c++11 -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -fno-exceptions -fno-rtti -fPIC -Os -fomit-frame-pointer -g1 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -m64 -mtune=generic -MD -MT CMakeFiles/ClazyPlugin.dir/src/checks/manuallevel/tr-non-literal.cpp.o -MF CMakeFiles/ClazyPlugin.dir/src/checks/manuallevel/tr-non-literal.cpp.o.d -o CMakeFiles/ClazyPlugin.dir/src/checks/manuallevel/tr-non-literal.cpp.o -c ../src/checks/manuallevel/tr-non-literal.cpp In file included from ../src/checks/manuallevel/tr-non-literal.cpp:23: In file included from ../src/checks/manuallevel/tr-non-literal.h:26: In file included from ../src/checkbase.h:28: In file included from ../src/clazy_stl.h:26: In file included from /usr/include/clang/AST/Stmt.h:16: In file included from /usr/include/clang/AST/DeclGroup.h:16: In file included from /usr/include/llvm/Support/TrailingObjects.h:50: In file included from /usr/include/llvm/Support/Alignment.h:24: In file included from /usr/include/llvm/ADT/Optional.h:20: /usr/include/llvm/Support/type_traits.h:31:28: error: no template named 'remove_reference_t' in namespace 'std'; did you mean 'remove_reference'? using UnderlyingT = std::remove_reference_t; ~^ /usr/bin/../lib64/gcc/x86_64-openmandriva-linux-gnu/10.2.0/../../../../include/c++/10.2.0/type_traits:1593:12: note: 'remove_reference' declared here struct remove_reference ^ EXPECTED RESULT No errors SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenMandriva Lx Cooker (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425821] New: coretaggedfileiconprovider.h:90:11: error: unknown type name 'QByteArray'
https://bugs.kde.org/show_bug.cgi?id=425821 Bug ID: 425821 Summary: coretaggedfileiconprovider.h:90:11: error: unknown type name 'QByteArray' Product: kid3 Version: 3.8.x Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: tpg...@gmail.com Target Milestone: --- SUMMARY 3.8.3 version does not compile with Qt 5.15.0 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Full logs https://abf.openmandriva.org/build_lists/817595 FAILED: src/core/CMakeFiles/kid3-core.dir/model/coretaggedfileiconprovider.cpp.o /usr/bin/clang++ -DKID3_BUILD_CORE_LIB -DKID3_BUILD_PLUGIN_LIB -DQT_ASCII_CAST_WARNINGS -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_NO_STL -DQT_NO_URL_CAST_FROM_STRING -DQT_STRICT_ITERATORS -DQT_XML_LIB -I../ -I. -I../src/core/utils -I../src/core/config -I../src/core/tags -I../src/core/export -I../src/core/import -I../src/core/model -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/./mkspecs/linux-clang -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtXml -isystem /usr/include/qt5/QtDBus -Os -fomit-frame-pointer -g1 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -m64 -mtune=generic -flto -Wundef -Wcast-align -Wall -W -Wpointer-arith -Woverloaded-virtual -fno-common -Werror=return-type -Wweak-vtables -D_REENTRANT -fvisibility=hidden -fvisibility-inlines-hidden -Os -fomit-frame-pointer -g1 -Wstrict-aliasing=2 -pipe -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all --param=ssp-buffer-size=4 -m64 -mtune=generic -flto -DQT_NO_DEBUG -fPIC -MD -MT src/core/CMakeFiles/kid3-core.dir/model/coretaggedfileiconprovider.cpp.o -MF src/core/CMakeFiles/kid3-core.dir/model/coretaggedfileiconprovider.cpp.o.d -o src/core/CMakeFiles/kid3-core.dir/model/coretaggedfileiconprovider.cpp.o -c ../src/core/model/coretaggedfileiconprovider.cpp In file included from ../src/core/model/coretaggedfileiconprovider.cpp:27: ../src/core/model/coretaggedfileiconprovider.h:90:11: error: unknown type name 'QByteArray' virtual QByteArray iconIdForTaggedFile(const TaggedFile* taggedFile) const; ^ ../src/core/model/coretaggedfileiconprovider.h:98:42: error: unknown type name 'QByteArray' virtual QVariant pixmapForIconId(const QByteArray& id); ^ ../src/core/model/coretaggedfileiconprovider.cpp:109:38: error: out-of-line definition of 'pixmapForIconId' does not match any declaration in 'CoreTaggedFileIconProvider' QVariant CoreTaggedFileIconProvider::pixmapForIconId(const QByteArray& id) ^~~ 3 errors generated. EXPECTED RESULT No errors SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenMandriva Lx Cooker (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.15.0 ADDITIONAL INFORMATION LLVM/clang-11.x is default compiler -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 368847] Assert in KWin::WindowQuad KWin::WindowQuad::makeSubQuad
https://bugs.kde.org/show_bug.cgi?id=368847 Tomasz Meresiński changed: What|Removed |Added CC|other+...@meresinski.eu | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 418793] New: QML Connections: Implicitly defined onFoo properties in Connections are deprecated
https://bugs.kde.org/show_bug.cgi?id=418793
Bug ID: 418793
Summary: QML Connections: Implicitly defined onFoo properties
in Connections are deprecated
Product: frameworks-kirigami
Version: 5.67.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: tpg...@gmail.com
Target Milestone: Not decided
SUMMARY
STEPS TO REPRODUCE
1. run systemsettings5 in konsole
2. pen global apperance
3. see warnings
OBSERVED RESULT
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:506:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:405:13:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:222:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/newstuff/qml/QuestionAsker.qml:106:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/newstuff/qml/QuestionAsker.qml:106:5: QML
Connections: Cannot assign to non-existent property "onClosing"
file:///usr/lib64/qt5/qml/org/kde/newstuff/qml/QuestionAsker.qml:65:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:111:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:111:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ComboBox.qml:111:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:65:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:168:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:106:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:78:5:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:100:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:65:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:168:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:106:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:100:9:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/AbstractApplicationHeader.qml:78:5:
QML Connections: Implicitly defined onFoo properties in Connections are
deprecated. Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:65:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/Menu.qml:65:5:
[frameworks-kirigami] [Bug 418792] New: Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
https://bugs.kde.org/show_bug.cgi?id=418792 Bug ID: 418792 Summary: Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/o rg.kde.desktop.plasma/Units.qml" Product: frameworks-kirigami Version: 5.67.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: tpg...@gmail.com Target Milestone: Not decided SUMMARY STEPS TO REPRODUCE 1. Run for example a systemsettings5 in konsole 2. observer output 3. see error OBSERVED RESULT [tpg@tpg-80xl sddm]$ systemsettings5 Cyclic dependency detected between "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib64/qt5/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" [tpg@tpg-80xl sddm]$ rpm -qf $(command -v systemsettings5) systemsettings-5.18.3-1.x86_64 EXPECTED RESULT No error SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenMandriva Lx Cooker (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.15.0-0.beta1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378436] Instance create job emits result too early
https://bugs.kde.org/show_bug.cgi?id=378436 Tomasz Paweł Gajc changed: What|Removed |Added Blocks||416403 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=416403 [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 Tomasz Paweł Gajc changed: What|Removed |Added Depends on||378436 CC||tpg...@gmail.com --- Comment #14 from Tomasz Paweł Gajc --- I'm also hit by this bug. I've tired couple of times with different email providers, always on fresh user. [tpg@tpg-80xl ~]$ rpm -qf $(command -v accountwizard) kmail-account-wizard-19.12.3-1.x86_64 [tpg@tpg-80xl ~]$ rpm -qf /usr/lib64/libQt5Core.so.5 lib64qt5core5-5.15.0-0.beta1.10.x86_64 [tpg@tpg-80xl ~]$ accountwizard "QFormBuilder was unable to create a custom widget of the class 'KLineEdit'; defaulting to base class 'QLineEdit'." "QFormBuilder was unable to create a custom widget of the class 'KLineEdit'; defaulting to base class 'QLineEdit'." "QFormBuilder was unable to create a custom widget of the class 'KLineEdit'; defaulting to base class 'QLineEdit'." org.kde.pim.accountwizard: Did not find D-Bus method: "setAccountIdentity" available methods are: org.kde.pim.accountwizard: "destroyed(QObject*)" org.kde.pim.accountwizard: "destroyed()" org.kde.pim.accountwizard: "objectNameChanged(QString)" org.kde.pim.accountwizard: "deleteLater()" org.kde.pim.accountwizard: "_q_reregisterTimers(void*)" org.kde.pim.accountwizard: "_q_serviceOwnerChanged(QString,QString,QString)" org.kde.pim.accountwizard: Impossible to convert argument : QVariant(int, 1106148123) org.kde.pim.accountwizard: Did not find D-Bus method: "setAccountIdentity" available methods are: org.kde.pim.accountwizard: "destroyed(QObject*)" org.kde.pim.accountwizard: "destroyed()" org.kde.pim.accountwizard: "objectNameChanged(QString)" org.kde.pim.accountwizard: "deleteLater()" org.kde.pim.accountwizard: "_q_reregisterTimers(void*)" org.kde.pim.accountwizard: "_q_serviceOwnerChanged(QString,QString,QString)" org.kde.pim.accountwizard: Impossible to convert argument : QVariant(int, 1106148123) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=378436 [Bug 378436] Instance create job emits result too early -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 Tomasz Janecki changed: What|Removed |Added CC||t_jane...@o2.pl --- Comment #63 from Tomasz Janecki --- I just found this bug report, I have reported a similar bug in KDE Connect: https://bugs.kde.org/show_bug.cgi?id=415897 My main concern was with "Presentation remote" which was translated in such an old fashioned way, that I had no idea what it was, but I also mentioned the Cancel / Anuluj / Zaniechaj error. Now I see that the problem lies with a translator, who did this on purpose. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 415897] New: Very confusing translation of "presentation" and "cancel" in KDE Connect
https://bugs.kde.org/show_bug.cgi?id=415897
Bug ID: 415897
Summary: Very confusing translation of "presentation" and
"cancel" in KDE Connect
Product: i18n
Version: unspecified
Platform: Android
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: pl
Assignee: kdei18n-pl-uw...@lists.sourceforge.net
Reporter: t_jane...@o2.pl
Target Milestone: ---
SUMMARY
Polish translation of KDE Connect is broken. On the main screen there's an
option called "Slideshow remote", which is also on the list of plugins (under
the same name).
It is translated as "Sterowanie pokazem przeźroczy", which is absurd, because
no one uses the term "przeźrocza" (transparent slides?) anymore, it's a word
out of the 80's. I had to search for the translation file to figure out what
this function actually does.
It seems as if someone tried to find a different, very old-timey, translation
of a slideshow. In Polish software a "slideshow" is always translated as "pokaz
slajdów" (it's the same in Gwenview) and "presentation" as "prezentacja". This
is the first time I've encountered "pokaz przeźroczy" and had no idea what that
was supposed to be.
The correct translation is "Sterowanie prezentacją".
Also "cancel" is translated as "zaniechaj" instead of "anuluj". It looks as if
the translation was done by a very old person, who hasn't used computers and
doesn't know that those phrases have standard Polish translations.
This error is in (it took me a long time to find where to look for it):
/trunk/l10n-kf5/pl/messages/extragear-network/kdeconnect-android.po
STEPS TO REPRODUCE
1. Launch KDE Connect on Android (current version 1.13.5)
2. Click on a paired device.
3. You see an incorrect translation as a second option ("Sterowanie pokazem
przeźroczy").
OBSERVED RESULT
Wrong translation:"Sterowanie pokazem przeźroczy", "Zaniechaj"
EXPECTED RESULT
Correct translation: "Sterowanie prezentacją", "Anuluj"
SOFTWARE/OS VERSIONS
Android
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Tomasz C. changed: What|Removed |Added CC||tli...@cebula.eu.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #98 from Tomasz Kołosowski --- 6 years later, we got it back. You're my hero man, I can't thank you enough. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 363947] kde connect: Could not mount device.
https://bugs.kde.org/show_bug.cgi?id=363947 --- Comment #33 from Tomasz Chmielewski --- Never mind - found it, it's the device running KDE. The wording could be improved there (and it's not called "plugin settings"). Also - I agree that the error message could be better. Thanks for your help, accessing files works for me now! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 363947] kde connect: Could not mount device.
https://bugs.kde.org/show_bug.cgi?id=363947 --- Comment #32 from Tomasz Chmielewski --- In the "Settings" menu in kdeconnect on Android, I can see "More settings", which says Per-device settings can be found under 'Plugin settings' from within a device. But where exactly can I find "Plugin settings"? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 363947] kde connect: Could not mount device.
https://bugs.kde.org/show_bug.cgi?id=363947
--- Comment #30 from Tomasz Chmielewski ---
On Android (Google Pixel 2 XL):
- kdeconnect 1.12.6 ("last updated Mar 23, 2019")
- Android 9, security patch level: March 5, 2019
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 363947] kde connect: Could not mount device.
https://bugs.kde.org/show_bug.cgi?id=363947
Tomasz Chmielewski changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0 |1
CC||man...@wpkg.org
Status|RESOLVED|REOPENED
--- Comment #28 from Tomasz Chmielewski ---
Please reopen.
I'm not able to browse the filesystem on a Google Pixel 2 phone. Other actions
like ringing work fine.
Error reported is: "Failed to mount filesystem: device not responding".
Output from kdeconnect:
$ /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
kdeconnect.core: KdeConnect daemon starting
kdeconnect.core: onStart
kdeconnect.core: KdeConnect daemon started
kdeconnect.core: Broadcasting identity packet
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "google"
kdeconnect.plugin.sftp: add to dolphin
kdeconnect.plugin.sftp: Created device: "google"
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeconnect.core: TCP connection done (i'm the existing device)
kdeconnect.core: Starting server ssl (I'm the client TCP socket)
kdeconnect.core: Socket successfully established an SSL connection
kdeconnect.core: It is a known device "google"
kdeconnect.plugin.sftp: Mount device: "google"
kdeconnect.plugin.sftp: Created mounter
kdeconnect.plugin.sftp: Starting loop to wait for mount
kdeconnect.plugin.sftp: Timeout: device not responding
kdeconnect.plugin.sftp: Destroy mounter
kdeconnect.plugin.sftp: Unmount QObject(0x0)
Running kdeconnect 1.3.3 on Kubuntu 18.10, and the newest kdeconnect version on
Android installed from Google Play (as of 2019-Mar-24).
"ss -tpna" output (192.168.1.3 - Google Pixel 2 phone; 192.168.1.5 - Kubuntu
18.10):
# ss -tpna|grep 192.168.1.3
ESTAB 00 [:::192.168.1.5]:48438
[:::192.168.1.3]:1716
users:(("kdeconnectd",pid=13368,fd=21))
"tcpdump" shows some packets are exchanged on port 1716, but not sure how to
debug this further.
The same kdeconnect on Kubuntu browses the files on an ASUS phone just fine.
--
You are receiving this mail because:
You are watching all bug changes.
[tellico] [Bug 391614] Inconsistent selection state after save
https://bugs.kde.org/show_bug.cgi?id=391614 Tomasz Goliński changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Tomasz Goliński --- The problem is still there with Tellico-3.1.4. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405250] Menus gone missing
https://bugs.kde.org/show_bug.cgi?id=405250 --- Comment #2 from tomasz --- Thank for a very quick reply. CTRL+M did the trick. The other option (right click, "Show Menubar") took a long time to find even with your description. So I guess it's not all too obvious. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405250] New: Menus gone missing
https://bugs.kde.org/show_bug.cgi?id=405250 Bug ID: 405250 Summary: Menus gone missing Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: tjkot...@gmail.com Target Milestone: --- SUMMARY There are no menus on the top title bar - or whatever it's called. STEPS TO REPRODUCE 1. No sure what I did - but as of a couple weeks ago all menus on the title bar are missing (Browse, Album, Tag, Item, View, etc) 2. Every time I run Digikam it does it 3. This never happened to me before OBSERVED RESULT Missing menus EXPECTED RESULT Menus should be present SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Once it started happening (when I was using 6.0 Beta 3) - running a released 6.0 and 6.1 beta makes no difference - menus are not there. I suspect it's some kind of a set up option - but don't know where to look. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403828] New: Discover crashes when showing upgrades
https://bugs.kde.org/show_bug.cgi?id=403828 Bug ID: 403828 Summary: Discover crashes when showing upgrades Product: Discover Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: tomek+kdeb...@kolosowscy.pl CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.5-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: - click tray icon with upgrades - click "show upgrades" - wait ~5s The crash can be reproduced every time. -- Backtrace: Application: Odkrywca (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff94b5f8080 (LWP 29512))] Thread 38 (Thread 0x7ff8bcff9700 (LWP 29684)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x in () Thread 37 (Thread 0x7ff8bdffb700 (LWP 29683)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x in () Thread 36 (Thread 0x7ff8be7fc700 (LWP 29682)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x in () Thread 35 (Thread 0x7ff8b700 (LWP 29681)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x in () Thread 34 (Thread 0x7ff8d8ff9700 (LWP 29680)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x in () Thread 33 (Thread 0x7ff8bf7fe700 (LWP 29679)): #0 0x7ff94ff46c21 in poll () at /usr/lib/libc.so.6 #1 0x7ff94e70c540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff94e70c62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff9390d750f in () at /usr/lib/libostree-1.so.1 #4 0x7ff94e6e767b in () at /usr/lib/libglib-2.0.so.0 #5 0x7ff94f1fda9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff94ff51b23 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7ff8d97fa700 (LWP 29678)): #0 0x7ff94ff46c21 in poll () at /usr/lib/libc.so.6 #1 0x7ff94e70c540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff94e70c62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff9390d750f in () at /usr/lib/libostree-1.so.1 #4 0x7ff94e6e767b in () at /usr/lib/libglib-2.0.so.0 #5 0x7ff94f1fda9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff94ff51b23 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7ff8bd7fa700 (LWP 29677)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x7ff94e6e5837 in g_slist_prepend () at /usr/lib/libglib-2.0.so.0 #3 0x in () Thread 30 (Thread 0x7ff8ff7fe700 (LWP 29676)): #0 0x7ff94ff5f12b in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7ff94ff6f749 in __check_pf () at /usr/lib/libc.so.6 #2 0x24882ba0c62b3c00 in () #3 0x in () Thread 29 (Thread 0x7ff8fdffb700 (LWP 29675)): #0 0x7ff94ff46c21 in poll () at /usr/lib/libc.so.6 #1 0x7ff94e70c540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff94e70c62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff9390d750f in () at /usr/lib/libostree-1.so.1 #4 0x7ff94e6e767b in () at /usr/lib/libglib-2.0.so.0 #5 0x7ff94f1fda9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff94ff51b23 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7ff8fd7fa700 (LWP 29674)): #0 0x7ff94ff46c21 in poll () at /usr/lib/libc.so.6 #1 0x7ff94e70c540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff94e70c62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff9390d750f in () at /usr/lib/libostree-1.so.1 #4 0x7ff94e6e767b in () at /usr/lib/libglib-2.0.so.0 #5 0x7ff94f1fda9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7ff94ff51b23 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7ff8daffd700 (LWP 29673)): #0 0x7ff94ff46c21 in poll () at /usr/lib/libc.so.6 #1 0x7ff94e70c540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff94e70c62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff9390d750f in () at /usr/lib/libostree-1.so.1 #4 0x7ff94e6e767b in
[kwin] [Bug 401549] New: Crash when switching desktop
https://bugs.kde.org/show_bug.cgi?id=401549 Bug ID: 401549 Summary: Crash when switching desktop Product: kwin Version: 5.14.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: other+...@meresinski.eu Target Milestone: --- Application: kwin_x11 (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: This crash happens when I switch desktop during the time of "Fall apart" desktop effect. I wasn't able to reproduce it with standard close window effect but maybe I wasn't fast enough. It reproduces every time. - Custom settings of the application: Fall apart desktop effect is on. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0bd0e68840 (LWP 31650))] Thread 6 (Thread 0x7f0b95deb700 (LWP 31686)): #0 0x7f0bd07c3cf6 in __GI_ppoll (fds=0x7f0b900012f8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0bcddc5d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0bcddc745e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0bcdd6e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0bcdb99bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bc82884f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f0bcdba4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0bc97fc6db in start_thread (arg=0x7f0b95deb700) at pthread_create.c:463 #8 0x7f0bd07d088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f0b955ea700 (LWP 31661)): #0 0x7f0bc98029f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f0bccda9fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0bc98029f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f0bccda9f68, cond=0x7f0bccda9f90) at pthread_cond_wait.c:502 #2 0x7f0bc98029f3 in __pthread_cond_wait (cond=0x7f0bccda9f90, mutex=0x7f0bccda9f68) at pthread_cond_wait.c:655 #3 0x7f0bccab4954 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f0bccab4999 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f0bc97fc6db in start_thread (arg=0x7f0b955ea700) at pthread_create.c:463 #6 0x7f0bd07d088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0bae5e2700 (LWP 31658)): #0 0x7f0bd07c3cf6 in __GI_ppoll (fds=0x7f0b9c000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0bcddc5d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0bcddc745e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0bcdd6e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0bcdb99bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bc82884f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f0bcdba4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0bc97fc6db in start_thread (arg=0x7f0bae5e2700) at pthread_create.c:463 #8 0x7f0bd07d088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0bb5482700 (LWP 31654)): #0 0x7f0bd07c3cf6 in __GI_ppoll (fds=0x7f0ba800efc8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f0bcddc5d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0bcddc745e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0bcdd6e30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0bcdb99bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0bc716fe45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f0bcdba4adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0bc97fc6db in start_thread (arg=0x7f0bb5482700) at pthread_create.c:463 #8 0x7f0bd07d088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0bb7f22700 (LWP 31653)): #0 0x7f0bd07c3bf9 in __GI___poll (fds=0x7f0bb7f21c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0bcd8d8747 in
[ksysguard] [Bug 302667] Cannot use fam15h_power sensor in Ksysguard
https://bugs.kde.org/show_bug.cgi?id=302667 Tomasz Goliński changed: What|Removed |Added Resolution|WAITINGFORINFO |--- CC||toma...@alpha.uwb.edu.pl Status|NEEDSINFO |REPORTED --- Comment #2 from Tomasz Goliński --- I just tested it with ksysguard 5.13.5 and AMD FX-8370E. Sensors show fam15h_power module loaded: fam15h_power-pci-00c4 Adapter: PCI adapter power1: 32.93 W (crit = 94.84 W) However I don't see any way to access it from ksysguard. It is not listed in CPU related sensors nor in hardware sensors section. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400606] Dead space above thumbnails.
https://bugs.kde.org/show_bug.cgi?id=400606 --- Comment #2 from tomasz --- Will test with beta 3 as soon as it's available. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397856] Export to remote storage: transfer not done
https://bugs.kde.org/show_bug.cgi?id=397856 --- Comment #4 from tomasz --- That's correct - I'm using AppImage Is there is workaround or a fix for this KIO problem? Many times in the past I wanted to use the export function - but as far as I remember it never worked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400606] New: Dead space above thumbnails.
https://bugs.kde.org/show_bug.cgi?id=400606 Bug ID: 400606 Summary: Dead space above thumbnails. Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-IconView Assignee: digikam-bugs-n...@kde.org Reporter: tjkot...@gmail.com Target Milestone: --- This is new to beta 2. Just checked it on 27Apr18 beta - and it was OK back then. STEPS TO REPRODUCE 1. Click on "Thumbnails" button. OBSERVED RESULT 1. There is dead space above the panel with thumnails all the way to the top menu bar. 2. Albums view panel on the left goes all the way to the top menu bar as is should EXPECTED RESULT 1. Thumbnails panel should go all the way up to the top menu bar. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: ?? KDE Frameworks Version: 5.49 Qt Version: 5.9.6 xcb windowing system ADDITIONAL INFORMATION Ubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397856] Export to remote storage: transfer not done
https://bugs.kde.org/show_bug.cgi?id=397856 tomasz changed: What|Removed |Added CC||tjkot...@gmail.com --- Comment #1 from tomasz --- I'm seeing the same (and have been for a while). 6.0 beta 2 (and 6.0-git, 27Apr18) on Ubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Tomasz Rychter changed: What|Removed |Added CC||tomasz.rych...@gmail.com --- Comment #65 from Tomasz Rychter --- Kubuntu 18.04.1 - Konsole Version 17.12.3 - bug still exists (gnome-terminal works just fine) -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 400068] New: multi parameter functions don't work when decimal separator is set to comma in current locale
https://bugs.kde.org/show_bug.cgi?id=400068 Bug ID: 400068 Summary: multi parameter functions don't work when decimal separator is set to comma in current locale Product: kmplot Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: tomek+kdeb...@kolosowscy.pl Target Milestone: --- SUMMARY If system is set to a locale that uses comma instead of dot as decimal separator, functions like min() or max() which take multiple parameters won't work, as system thinks that comma is decimal separator rather than parameter separator. STEPS TO REPRODUCE 1. Set decimal separator to comma in system settings -> regional settings -> formats -> numbers (i.e. pl_PL uses comma) 2. Try to plot anything using min or max, i.e. f(x) = max(sin(x),cos(x)) OBSERVED RESULT Plot isn't drawn as kmplot complains about input being invalid EXPECTED RESULT Plot is drawn SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Tested under pl_PL locale, when running LANG=C kmplot everything works as expected -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=381850 --- Comment #5 from Edward Tomasz Napierala --- FWIW, I'm wondering if it could have been fixed in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181741. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 381850] akonadi, kimap, kmail very broken on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=381850 Edward Tomasz Napierala changed: What|Removed |Added CC||tr...@freebsd.org --- Comment #3 from Edward Tomasz Napierala --- Just wondering... is the workaround still neccessary with 12.0-ALPHA or recent 11-STABLE? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 391614] Inconsistent selection state after save
https://bugs.kde.org/show_bug.cgi?id=391614 --- Comment #4 from Tomasz --- I think I can reproduce this problem in the following way: 1. Edit an entry 2. Chose another entry without saving the previous one first 3. Dialog pops up asking you to chose what to do. Chose "Save entry". After that Tellico exhibits the problem - the second entry becomes permanently and transparently selected. If I save modifications to the entry manually, the bug doesn't trigger. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398340] VirtualBOX, VMware Player - hot corners don't work, hot edges work as intended
https://bugs.kde.org/show_bug.cgi?id=398340 --- Comment #2 from Tomasz Feliksiak --- (In reply to Martin Flöser from comment #1) > Please try to grab the mouse in the virtual machine. The seamless mouse > integration might destroy the feature. You're absolutely right. In VirtualBOX turning OFF mouse integration fixes hot corners (it's even possible to add shortcut to this operation). I didn't find that option in VMware Player (free version). In both VirtualBOX and VMware Player after connecting USB mouse to virtual machine (and in the same time disconnecting from host) fixes hot corners too. I didn't spend much time on this but getting back mouse to host for me was possible only after shutting off guest. Maybe there is some other way. Nonetheless is that the right way to go? Shouldn't hot corners work like hot edges do? If someone switch from host to guest as often as me, switching mouse from guest to host is so much problem it's absolutely pointless to use hot corners (of course I can live without them but that's not the way to fix bugs). Of course I'm interested how hot corners differ from hot edges in this situation and I will be gratefull for explanation. For now I still consider this as a bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398340] New: VirtualBOX, VMware Player - hot corners don't work, hot edges work as intended
https://bugs.kde.org/show_bug.cgi?id=398340 Bug ID: 398340 Summary: VirtualBOX, VMware Player - hot corners don't work, hot edges work as intended Product: kwin Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: vo...@webtrunki.pl Target Milestone: --- In work I use Kubuntu 18.04.1 LTS as my main system and there everything works fine. I use top left corner for windows presentation and bottom right for desktop grid. In home I have Windows 10 and VMware Player 14 (14.1.3 build-9474260) with exact the same Kubuntu 18.04.1 LTS. Earlier I used VirtualBOX (5.2.18 r124319 (Qt5.6.2)). No mater on which VM software I run Kubuntu, hot corners doesn't work. Inspired by bugs https://bugs.kde.org/show_bug.cgi?id=290887 and https://bugs.kde.org/show_bug.cgi?id=321259 I started testing this a bit, and noticed that hot edges are working normally. Reproducible: Always Steps to Reproduce: 1. Install Kubuntu 18.04.1 on VMware Player (with open-vm-tools) or VirtualBox (with vboxguestadditions) and go fullscreen (in window it's the same but harder to hit corner/edge of screen) 2. Bind any effect to the corners and edges 3. Throw your mouse in the corners and edges Actual Results: Hot corners doesn't work, hot edges are working Expected Results: Working hot corners and edges -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 311535] Cannot scale Screen.
https://bugs.kde.org/show_bug.cgi?id=311535 Tomasz Kołosowski changed: What|Removed |Added CC|tomek+kdeb...@kolosowscy.pl | -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395387] New: Too big icons on HIDPI displays
https://bugs.kde.org/show_bug.cgi?id=395387 Bug ID: 395387 Summary: Too big icons on HIDPI displays Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: tomek+kdeb...@kolosowscy.pl Target Milestone: --- Created attachment 113324 --> https://bugs.kde.org/attachment.cgi?id=113324=edit Screenshot demonstrating the problem Since Plasma 5.13 networkmanager's icons are way too big. Attached screenshot which demonstrates the problem -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393521] When I open session / project by fish protocol by 'kdevelop -s hash' then kdevelop crash
https://bugs.kde.org/show_bug.cgi?id=393521 Tomasz Narloch <toma...@wp.pl> changed: What|Removed |Added Component|Language Support: PHP |general -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393521] New: When I open session / project by fish protocol by 'kdevelop -s hash' then kdevelop crash
https://bugs.kde.org/show_bug.cgi?id=393521
Bug ID: 393521
Summary: When I open session / project by fish protocol by
'kdevelop -s hash' then kdevelop crash
Product: kdevelop
Version: 5.2.1
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: PHP
Assignee: kdevelop-bugs-n...@kde.org
Reporter: toma...@wp.pl
Target Milestone: ---
In my ubuntu some libs may mismatch. I used ubuntu additional repo
kdevelop 5.2.2
(http://ppa.launchpad.net/blaze/kf5/ubuntu/pool/main/k/kdevelop/)
I'm trying to open project saved on server by fish protocol.
I can do this with success when I open kdevelop, create a new session and then
open project in this session by "Add project to current session".
When I try to open the project in another session "Open session My project"
then kdevelop crash.
Debug:
LANG=C gdb kdevelop -s "{1b7b919e-21d1-4604-bf1d-9674e3c2a2b7}"
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
[tellico] [Bug 391614] Inconsistent selection state after save
https://bugs.kde.org/show_bug.cgi?id=391614 Tomasz <toma...@alpha.uwb.edu.pl> changed: What|Removed |Added CC||toma...@alpha.uwb.edu.pl --- Comment #2 from Tomasz <toma...@alpha.uwb.edu.pl> --- I think something is still broken. I got the same problem with 3.1.2 (even without saving the database). However I cannot reproduce it consistently yet. I also managed to observe a problem where it was impossible to select anything, selection was all the time empty. That happened after saving a database and that time Tellico didn't clear bold from all updated entries. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392759] New: PHP error parser on namespace with a word "String"
https://bugs.kde.org/show_bug.cgi?id=392759 Bug ID: 392759 Summary: PHP error parser on namespace with a word "String" Product: kdevelop Version: 5.2.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: toma...@wp.pl Target Milestone: --- Created attachment 111849 --> https://bugs.kde.org/attachment.cgi?id=111849=edit php parser error on namespace with text String Kdevelop does not properly parse namespace with the text "String", e.g. namespace Joomla\String; use Joomla\String\StringHelper; After finding one of the above lines, Kdevelop stops parsing the rest of the file. Highlight also does not work on the same php file. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387911] New: Close tabs to the right
https://bugs.kde.org/show_bug.cgi?id=387911 Bug ID: 387911 Summary: Close tabs to the right Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: other+...@meresinski.eu Target Milestone: --- There should be an option (known from eg Firefox) to close all tabs (with editor views) to the right. It will make it easier to work with multiple open files. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387762] New: Keyboard shortcut for Create Text file
https://bugs.kde.org/show_bug.cgi?id=387762 Bug ID: 387762 Summary: Keyboard shortcut for Create Text file Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: other+...@meresinski.eu CC: elvis.angelac...@kde.org Target Milestone: --- I cannot add a keyboard shortcut for "Create Text File" action. I use that feature frequently so in my opinion there should be an option to assign a keyboard shortcut for it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386118] New: Unable to select text in notification popup
https://bugs.kde.org/show_bug.cgi?id=386118 Bug ID: 386118 Summary: Unable to select text in notification popup Product: plasmashell Version: 5.11.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: other+...@meresinski.eu CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 108527 --> https://bugs.kde.org/attachment.cgi?id=108527=edit Screenshot I'm unable to select body text of notifications (for example to copy it). To reproduce just send a notification and try to select body of that message. To clarify - text I want to select is "unselectable text" from attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 385044] New: Add weather informations into KCalendar
https://bugs.kde.org/show_bug.cgi?id=385044 Bug ID: 385044 Summary: Add weather informations into KCalendar Product: kontact Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: madshey...@gmail.com Target Milestone: --- This feature would inform user about the evet day weather. Something like this is in outlook and I really like it. Think it's not a hard work to do, so this would be a nice addition to kcalendar ;) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 382025] Dual monitor unable to use, first DP LG UHD, second DVI BenQ FHD, ATI Radeon R9 290
https://bugs.kde.org/show_bug.cgi?id=382025 --- Comment #2 from Tomasz Kowal <t...@onet.eu> --- Yes, with xrandr also occurs when i set 59Hz or 60Hz. With 30Hz is ok. Look for pclk value, is this not too high value for this 3840x2160@60? xandr -q Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384 DisplayPort-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 3840x2160 60.00*+ 30.00 1920x1080 60.0059.94 1600x900 60.00 1280x1024 60.02 1152x864 59.96 1280x720 60.0059.94 1024x768 60.00 800x600 60.32 720x480 60.0059.94 640x480 60.0059.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 1680x1050 59.88 1600x900 60.00 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1280x720 60.00 1152x720 59.97 1024x768 75.0360.00 832x624 74.55 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 gtf 3840 2160 60 # 3840x2160 @ 60.00 Hz (GTF) hsync: 134.10 kHz; pclk: 712.34 MHz Modeline "3840x2160_60.00" 712.34 3840 4152 4576 5312 2160 2161 2164 2235 -HSync +Vsync tk W dniu 17.07.2017 o 11:20, Sebastian Kügler pisze: > https://bugs.kde.org/show_bug.cgi?id=382025 > > --- Comment #1 from Sebastian Kügler <se...@kde.org> --- > Thanks for the report, Tomasz! > > Could you check if this behavior also occurs if you use the xrandr tool to set > up your screens? > -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382025] Dual monitor unable to use, first DP LG UHD, second DVI BenQ FHD, ATI Radeon R9 290
https://bugs.kde.org/show_bug.cgi?id=382025 Tomasz Kowal <t...@onet.eu> changed: What|Removed |Added CC||t...@onet.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382025] New: Dual monitor unable to use, first DP LG UHD, second DVI BenQ FHD, ATI Radeon R9 290
https://bugs.kde.org/show_bug.cgi?id=382025 Bug ID: 382025 Summary: Dual monitor unable to use, first DP LG UHD, second DVI BenQ FHD, ATI Radeon R9 290 Product: systemsettings Version: 5.8.7 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: t...@onet.eu Target Milestone: --- Everu move mouse or window cosing unacceptable shaking whole screen on main UHD monitor. If I turn off second monitor shaking is smaller but still exist. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381012] bug in popup palette color
https://bugs.kde.org/show_bug.cgi?id=381012 --- Comment #11 from Tomasz <ania...@gmail.com> --- Good to know. CMYK is nesessery in offset printing. I don`t need it right now but in the future, who knows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381012] bug in popup palette color
https://bugs.kde.org/show_bug.cgi?id=381012 --- Comment #9 from Tomasz <ania...@gmail.com> --- Yes,you are right. So I should paint in RGB and then switch to CMYK. -- You are receiving this mail because: You are watching all bug changes.
