[systemsettings] [Bug 412906] Feature to save current layout as a new Global Theme package
https://bugs.kde.org/show_bug.cgi?id=412906 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 259285] Implement a GUI method of changing the hostname/domain name
https://bugs.kde.org/show_bug.cgi?id=259285 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486794] Add option to set keyboard shortcuts to directly switch power management profiles
https://bugs.kde.org/show_bug.cgi?id=486794 --- Comment #1 from Jure Repinc --- Also reported as Powerdevil issue 39: https://invent.kde.org/plasma/powerdevil/-/issues/39 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486794] Add option to set keyboard shortcuts to directly switch power management profiles
https://bugs.kde.org/show_bug.cgi?id=486794 Jure Repinc changed: What|Removed |Added URL||https://invent.kde.org/plas ||ma/powerdevil/-/issues/39 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451936] Rendering with chapters
https://bugs.kde.org/show_bug.cgi?id=451936 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457426] enabled Use GPU Acceleration (movit library) dragging files in project bin or timeline crash kdenlive
https://bugs.kde.org/show_bug.cgi?id=457426 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469520] Error starting kdenlive in GPU mode
https://bugs.kde.org/show_bug.cgi?id=469520 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476471] My GPU codec is not supported
https://bugs.kde.org/show_bug.cgi?id=476471 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 488461] encoding at 18fps, never uses more than 20% cpu, and vaapi does not work.
https://bugs.kde.org/show_bug.cgi?id=488461 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487991] When rendering in AV1 - Unable to change the bitrate from over 160, 000kbps file sizes are double the size expected from handbrake
https://bugs.kde.org/show_bug.cgi?id=487991 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482943] Missing setting for notification sounds
https://bugs.kde.org/show_bug.cgi?id=482943 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 491515] New: Notes widget should not get enlarged and moved to another position on Plasma restart
https://bugs.kde.org/show_bug.cgi?id=491515 Bug ID: 491515 Summary: Notes widget should not get enlarged and moved to another position on Plasma restart Classification: Plasma Product: kdeplasma-addons Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- SUMMARY I have a lot of text in one of the notes widgets so not all can be displayed and there are scrollbars in the widget and each time I restart Plasma this Notes widget get enlarged so it displays all text in it and since it becomes too big and can not be in between other widgets it also gets moved to another position. STEPS TO REPRODUCE 1. Add a Notes widget with a lot of text and make the size smaller so not all text is shown 2. Surround the widget by other widgets 3. Restart Plasma OBSERVED RESULT Notes widget gets enlarged so all text fits and it gets moved to another place. EXPECTED RESULT Notes widget should just remain of the same size the user sets and should stay at the same place. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240808 KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.3-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 7900 GRE -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 490234] Crash in TM::targetAdapted when selecting translation memory suggestion
https://bugs.kde.org/show_bug.cgi?id=490234 --- Comment #2 from Jure Repinc --- Created attachment 171638 --> https://bugs.kde.org/attachment.cgi?id=171638&action=edit All threads backtrace -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 490234] Crash in TM::targetAdapted when selecting translation memory suggestion
https://bugs.kde.org/show_bug.cgi?id=490234
--- Comment #1 from Jure Repinc ---
Thread 1 (Thread 0x715e7b00 (LWP 455035) "lokalize"):
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x74e94a63 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#2 0x74e41176 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3 0x74e28917 in __GI_abort () at abort.c:79
#4 0x756e073d in qAbort () at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qglobal.cpp:161
#5 0x75730bfe in qt_message_fatal (message=...,
context=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:2025
#6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg,
context=, msg=, ap=ap@entry=0x7fffae80) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:374
#7 0x756e1df3 in QMessageLogger::fatal (this=,
msg=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qlogging.cpp:889
#8 0x756e0e14 in qt_assert_x (where=, what=, file=, line=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qassert.cpp:77
#9 0x00454d91 in QList::at (this=0x7fffb258, i=186) at
/usr/include/qt6/QtCore/qlist.h:434
#10 0x005730b1 in TM::targetAdapted (entry=..., ref=...) at
/home/jlp/Programiranje/lokalize/src/tm/tmview.cpp:931
#11 0x00573a66 in TM::TMView::slotUseSuggestion (this=0x3907c60, i=0)
at /home/jlp/Programiranje/lokalize/src/tm/tmview.cpp:1012
#12 0x0056cf90 in operator() (__closure=0x4d0f730) at
/home/jlp/Programiranje/lokalize/src/tm/tmview.cpp:154
#13 0x00574bcb in QtPrivate::FunctorCall,
QtPrivate::List<>, void, TM::TMView::initLater():: >::call(struct
{...} &, void **) (f=..., arg=0x7fffc0f0) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#14 0x00574b19 in
QtPrivate::FunctorCallable
>::call, void>(struct {...} &, void *, void **) (f=...,
arg=0x7fffc0f0) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#15 0x00574a3b in
QtPrivate::QCallableObject,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=1, this_=0x4d0f720, r=0x3907c60, a=0x7fffc0f0,
ret=0x0) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#16 0x757e7f90 in QtPrivate::QSlotObjectBase::call (a=0x7fffc0f0,
r=0x3907c60, this=0x4d0f720) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobjectdefs_impl.h:469
#17 doActivate (sender=0x39096f0, signal_index=7, argv=0x7fffc0f0)
at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:4086
#18 0x765374f2 in QAction::triggered (this=this@entry=0x39096f0,
_t1=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/build/src/gui/Gui_autogen/include/moc_qaction.cpp:480
#19 0x7653a0e4 in QAction::activate (this=0x39096f0, event=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qaction.cpp:1102
#20 0x7653a4f0 in QAction::event (e=0x7fffc330, this=0x39096f0) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qaction.cpp:1044
#21 QAction::event (this=0x39096f0, e=0x7fffc330) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qaction.cpp:1027
#22 0x76bc2f6e in QApplicationPrivate::notify_helper (this=, receiver=0x39096f0, e=0x7fffc330) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/kernel/qapplication.cpp:3287
#23 0x7578ec30 in QCoreApplication::notifyInternal2
(receiver=0x39096f0, event=0x7fffc330) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:1142
#24 0x7578ec69 in QCoreApplication::sendEvent (receiver=, event=) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:1583
#25 0x765487a4 in QShortcutMap::dispatchEvent (this=,
e=0x7fffc420) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qshortcutmap.cpp:606
#26 0x76548f07 in QShortcutMap::tryShortcut (this=0x754598,
e=0x7fffc420) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qshortcutmap.cpp:310
#27 0x76244bde in QWindowSystemInterface::handleShortcutEvent
(window=, timestamp=, keyCode=49, modifiers=...,
nativeScanCode=10, nativeVirtualKey=49, nativeModifiers=20, text=...,
autorepeat=false, count=1) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qwindowsysteminterface.cpp:449
#28 0x761e9722 in QGuiApplicationPrivate::processKeyEvent (e=0x597c850)
at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:2434
#29 0x7624983c in QWindowSystemInterface::sendWindowSystemEvents
(flags=flags@entry=...) at
/usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qwindowsysteminterface.cpp:11
[lokalize] [Bug 490234] New: Crash in TM::targetAdapted when selecting translation memory suggestion
https://bugs.kde.org/show_bug.cgi?id=490234 Bug ID: 490234 Summary: Crash in TM::targetAdapted when selecting translation memory suggestion Classification: Applications Product: lokalize Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: translation memory Assignee: sdepi...@gmail.com Reporter: j...@holodeck1.com CC: aa...@kde.org, sha...@ukr.net, vkra...@kde.org Target Milestone: --- SUMMARY This is for version from master which has been ported to Qt6. When your are translating you have an option to select and entry from "Translation Memory" suggestions view panel, using Ctrl+1 fir first suggestion, Ctrl+2 for second and so on. This selection from TM is used to fill out a translated string. When you select it Lokalize crashes STEPS TO REPRODUCE 1. Have something in translation memory that can be chosen for new translation 2. When translation a file press Ctrl+1 to fill out translation with the suggestion from TM OBSERVED RESULT Lokalize crashes in TM::targetAdapted with the following backtrace (all threads BT is be attached) EXPECTED RESULT Suggestion from translation memory should be filled out in translated string without crashing. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240711 KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 7900 GRE -- You are receiving this mail because: You are watching all bug changes.
[libplasma] [Bug 466940] Plasmashell crashes in PlasmaQuick::DialogPrivate::syncToMainItemSize()
https://bugs.kde.org/show_bug.cgi?id=466940 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489940] Plasma crashes in PanelView::updateEnabledBorders on startup
https://bugs.kde.org/show_bug.cgi?id=489940 --- Comment #6 from Jure Repinc --- Just updated so the patch is included and can confirm the crash is gone for me. -- You are receiving this mail because: You are watching all bug changes.
[kbounce] [Bug 489990] The cursor do not change between up/down and right/left on right mouse-click
https://bugs.kde.org/show_bug.cgi?id=489990 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com --- Comment #1 from Jure Repinc --- This works fine for me on the latest version 24.05.2 Operating System: openSUSE Tumbleweed 20240708 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489072] Null screen in QtWaylandClient::QWaylandWindow::handleScreensChanged
https://bugs.kde.org/show_bug.cgi?id=489072 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 476187] OpenH264 codec support
https://bugs.kde.org/show_bug.cgi?id=476187 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489940] Plasma crashes in PanelView::updateEnabledBorders on startup
https://bugs.kde.org/show_bug.cgi?id=489940 Jure Repinc changed: What|Removed |Added CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489940] New: Plasma crashes in PanelView::updateEnabledBorders on startup
https://bugs.kde.org/show_bug.cgi?id=489940 Bug ID: 489940 Summary: Plasma crashes in PanelView::updateEnabledBorders on startup Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: 1.0 Application: plasmashell (6.1.80) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.9.7-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 6.1.80 [CoredumpBackend] -- Information about the crash: After the update and on login Plasma crashes immidiately in PanelView::updateEnabledBorders and restarts three times spawning the three crash dialogs. Plasma comit the package is built from is 13b42d356a1f08b742ec88691acb38365393e703 The crash might have something to do with "Refactor floating panels" commit f7ee03d065b4e293746248f749a7965c4321b1cb Operating System: openSUSE Tumbleweed 20240704 KDE Plasma Version: 6.1.80 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics Screen info: kscreen-doctor -o [20::26:47.544] unknown: adding output 60 [20::26:47.544] unknown: adding output 61 [20::26:47.550] unknown: Loading Wayland backend. Output: 1 HDMI-A-1 enabled connected priority 1 HDMI Modes: 0:3840x2160@60*! 1:4096x2160@60 2:4096x2160@60 3:4096x2160@50 4:4096x2160@30 5:4096x2160@30 6:4096x2160@25 7:4096x2160@24 8:4096x2160@24 9:3840x2160@60 10:3840x2160@60 11:3840x2160@50 12:3840x2160@30 13:3840x2160@30 14:3840x2160@25 15:3840x2160@24 16:3840x2160@24 17:1920x1200@60 18:1920x1080@60 19:1920x1080@60 20:1920x1080@60 21:1920x1080@50 22:1920x1080@30 23:1920x1080@30 24:1920x1080@25 25:1920x1080@24 26:1920x1080@24 27:1920x1080@24 28:1600x1200@60 29:1680x1050@60 30:1400x1050@60 31:1280x1024@75 32:1280x1024@60 33:1440x900@60 34:1280x960@60 35:1280x800@60 36:1152x864@75 37:1280x720@60 38:1280x720@60 39:1280x720@50 40:1024x768@75 41:1024x768@70 42:1024x768@60 43:832x624@75 44:800x600@75 45:800x600@72 46:800x600@60 47:800x600@56 48:720x576@50 49:720x576@50 50:720x480@60 51:720x480@60 52:720x480@60 53:720x480@60 54:640x480@75 55:640x480@73 56:640x480@60 57:640x480@60 58:640x480@60 59:720x400@70 60:1600x1200@60 61:1280x1024@60 62:1024x768@60 63:2560x1600@60 64:1920x1200@60 65:1280x800@60 66:3840x2160@60 67:3200x1800@60 68:2880x1620@60 69:2560x1440@60 70:1920x1080@60 71:1600x900@60 72:1368x768@60 73:1280x720@60 Geometry: 1120,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Output: 2 DVI-D-1 enabled connected priority 2 DVI Modes: 0:1680x1050@60*! 1:1280x1024@75 2:1280x1024@60 3:1440x900@60 4:1280x960@60 5:1280x800@60 6:1152x864@75 7:1280x720@60 8:1024x768@75 9:1024x768@70 10:1024x768@60 11:832x624@75 12:800x600@75 13:800x600@72 14:800x600@60 15:800x600@56 16:640x480@75 17:640x480@73 18:640x480@67 19:640x480@60 20:720x400@70 21:1280x1024@60 22:1024x768@60 23:1280x800@60 24:1600x900@60 25:1368x768@60 26:1280x720@60 Geometry: 0,380 1120x700 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x7fbfb39e136a in QScopedPointer >::get (this=) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qscopedpointer.h:112 [...] #8 QObject::property (this=0x0, name=name@entry=0x5583b5728693 "leftShadowMargin") at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:4298 #9 0x5583b56c8ff5 in PanelView::updateEnabledBorders (this=0x5583d56d3620) at /usr/src/debug/plasma-workspace-6.1.80git.20240707T012925~13b42d35/shell/panelview.cpp:1813 #10 0x5583b56ca793 in PanelView::resizeEvent (this=0x5583d56d3620, ev=0x7fffdfae9410) at /usr/src/debug/plasma-workspace-6.1.80git.20240707T012925~13b42d35/shell/panelview.cpp:1003 #11 0x7fbfb423a9f6 in QWindow::event (this=0x5583d56d3620, ev=0x7fffdfae9410) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qwindow.cpp:2542 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489940] Plasma crashes in PanelView::updateEnabledBorders on startup
https://bugs.kde.org/show_bug.cgi?id=489940 --- Comment #1 from Jure Repinc --- Created attachment 171484 --> https://bugs.kde.org/attachment.cgi?id=171484&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489259] Spamming Meta+V causes Plasma to exit with a Wayland protocol error (error 3: no xdg_popup parent surface has been specified)
https://bugs.kde.org/show_bug.cgi?id=489259 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 488896] Huge frame drops when recording with spectacle
https://bugs.kde.org/show_bug.cgi?id=488896 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 489434] Spectacle crashes on finishing recording with pipewire 1.2.0
https://bugs.kde.org/show_bug.cgi?id=489434 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489806] New: Make it possible so that background window does not raise when starting a drag (mouse down), but does on click
https://bugs.kde.org/show_bug.cgi?id=489806 Bug ID: 489806 Summary: Make it possible so that background window does not raise when starting a drag (mouse down), but does on click Classification: Plasma Product: kwin Version: master Platform: Other URL: https://mstdn.io/deck/@scottjen...@social.coop/1127362 15334560587 OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- Expected behaviour 1. Single click on background window: raise it 2. Drag on icon in background window: just highlight icon and start dragging, no raise Actual behaviour: There are settings in System Settings → Window Management → Window Actions. There you can set the left click from "Activate, raise and forward click" to "Activate and forward click" and some others but none of them satisfies both expected cases at the same time, because the entire click (mouse down + mouse up) is considered. With the default "Activate, raise and forward click" when you start dragging the item in the background window the background window raises and if it covers the entire previously foreground window we lose the drag target window from sight since it goes into background. If "Activate and forward click" setting (without raise) is selected then if you only click on the window in the background it does not raise and you have to click the second time to raise it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed in QWindowPrivate::connectToScreen() when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 --- Comment #3 from Jure Repinc --- Yes, dual screen: Output: 1 DVI-D-1 enabled connected priority 2 DVI Modes: 0:1680x1050@60*! 1:1280x1024@75 2:1280x1024@60 3:1440x900@60 4:1280x960@60 5:1280x800@60 6:1152x864@75 7:1280x720@60 8:1024x768@75 9:1024x768@70 10:1024x768@60 11:832x624@75 12:800x600@75 13:800x600@72 14:800x600@60 15:800x600@56 16:640x480@75 17:640x480@73 18:640x480@67 19:640x480@60 20:720x400@70 21:1280x1024@60 22:1024x768@60 23:1280x800@60 24:1600x900@60 25:1368x768@60 26:1280x720@60 Geometry: 0,380 1120x700 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Output: 2 HDMI-A-1 enabled connected priority 1 HDMI Modes: 0:3840x2160@60*! 1:4096x2160@60 2:4096x2160@60 3:4096x2160@50 4:4096x2160@30 5:4096x2160@30 6:4096x2160@25 7:4096x2160@24 8:4096x2160@24 9:3840x2160@60 10:3840x2160@60 11:3840x2160@50 12:3840x2160@30 13:3840x2160@30 14:3840x2160@25 15:3840x2160@24 16:3840x2160@24 17:1920x1200@60 18:1920x1080@60 19:1920x1080@60 20:1920x1080@60 21:1920x1080@50 22:1920x1080@30 23:1920x1080@30 24:1920x1080@25 25:1920x1080@24 26:1920x1080@24 27:1920x1080@24 28:1600x1200@60 29:1680x1050@60 30:1400x1050@60 31:1280x1024@75 32:1280x1024@60 33:1440x900@60 34:1280x960@60 35:1280x800@60 36:1152x864@75 37:1280x720@60 38:1280x720@60 39:1280x720@50 40:1024x768@75 41:1024x768@70 42:1024x768@60 43:832x624@75 44:800x600@75 45:800x600@72 46:800x600@60 47:800x600@56 48:720x576@50 49:720x576@50 50:720x480@60 51:720x480@60 52:720x480@60 53:720x480@60 54:640x480@75 55:640x480@73 56:640x480@60 57:640x480@60 58:640x480@60 59:720x400@70 60:1600x1200@60 61:1280x1024@60 62:1024x768@60 63:2560x1600@60 64:1920x1200@60 65:1280x800@60 66:3840x2160@60 67:3200x1800@60 68:2880x1620@60 69:2560x1440@60 70:1920x1080@60 71:1600x900@60 72:1368x768@60 73:1280x720@60 Geometry: 1120,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 283020] Store Kmail (Akonadi) tags in IMAP flags to enable syncing between mail clients
https://bugs.kde.org/show_bug.cgi?id=283020 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 --- Comment #1 from Jure Repinc --- Created attachment 171309 --> https://bugs.kde.org/attachment.cgi?id=171309&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] New: Plasma crashed when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 Bug ID: 489638 Summary: Plasma crashed when trying to open Klipper paste menu with keyboard shortcut Meta+V Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: 1.0 Application: plasmashell (6.1.80) Qt Version: 6.7.2 Frameworks Version: 6.4.0 Operating System: Linux 6.9.7-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 6.1.80 [CoredumpBackend] -- Information about the crash: I had Yakuake window open and tried to paste some previously copied text into it so I pressed the keyboard combination Meta+V to open the Klipper paste menu, At this point Plasma crashed and restartet itself. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 std::__atomic_base::fetch_add (__m=std::memory_order_acq_rel, __i=1, this=0x153850f) at /usr/include/c++/13/bits/atomic_base.h:633 #6 QAtomicOps::ref (_q_value=, _q_value=) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qatomic_cxx11.h:259 [...] #8 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x5571645f9690) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer.cpp:1456 #9 0x7f1362a33ae0 in QWeakPointer::QWeakPointer (ptr=0x5571645f9690, this=) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:733 #10 QWeakPointer::assign (ptr=0x5571645f9690, this=0x55716640d7e0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:728 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] On Wayland, center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489180] plasma crashed in QtWaylandClient::QWaylandWindow::waylandScreen() when external monitor lost power
https://bugs.kde.org/show_bug.cgi?id=489180 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 488092] New: Clicking on scrollbar track below the handle does not move view by only one page
https://bugs.kde.org/show_bug.cgi?id=488092 Bug ID: 488092 Summary: Clicking on scrollbar track below the handle does not move view by only one page Classification: Applications Product: Discover Version: 6.0.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com CC: aleix...@kde.org Target Milestone: --- SUMMARY I have selected the setting "Clicking in scrollbar track:" → "Scrolls one page up or down" STEPS TO REPRODUCE 1. Set the setting to only scroll by one page as mentioned above 2. Click below the scrollbar handle OBSERVED RESULT Discover moves the view directly to the clicked location (as if "Scrolls to the clicked location" setting was set). EXPECTED RESULT Dicover should scroll only one page as the settings says. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240531 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 477983] "Total" sensor of Disk Usage widget reports incorrect value
https://bugs.kde.org/show_bug.cgi?id=477983 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487138] Windows placement forgotten all placed on the left screen after switching AVR standby on/off
https://bugs.kde.org/show_bug.cgi?id=487138 --- Comment #2 from Jure Repinc --- Created attachment 169561 --> https://bugs.kde.org/attachment.cgi?id=169561&action=edit KWin Info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487138] Windows placement forgotten all placed on the left screen after switching AVR standby on/off
https://bugs.kde.org/show_bug.cgi?id=487138 --- Comment #1 from Jure Repinc --- Created attachment 169560 --> https://bugs.kde.org/attachment.cgi?id=169560&action=edit kscreen log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487138] New: Windows placement forgotten all placed on the left screen after switching AVR standby on/off
https://bugs.kde.org/show_bug.cgi?id=487138 Bug ID: 487138 Summary: Windows placement forgotten all placed on the left screen after switching AVR standby on/off Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- Created attachment 169559 --> https://bugs.kde.org/attachment.cgi?id=169559&action=edit Screen layout used SUMMARY I have two screens connected to the graphics card, smaller Samsung one is connected via DVI and set to be on the left side and not primary and using 150% scale, bigger one is Panasonic TV and connected via HDMI to Marantz AVR and then this is connected via HDMI to the graphics card. This one is set as primary screen and to the right, using 200% scaling. When I turn the AVR into standby mode the connection from PC to AVR to TV is set as pass-through (so audio plays on TV speakers) and when returning back from standby the connection is normal and audio is processed by AVR and played via speakers connected to it. The problem is that when this switching of AVR from/to standby changes screen/outputs configuration and it used to work mostly fine but now the screen positions of windows are forgotten and all windows are moved to the left smaller Samsung screen instead of remaining on the big right Panasonic screen. This used to work almost fine about on april 25 but now (april 17) that I am back and updated the software it is does not work anymore so something changed during this time frame. STEPS TO REPRODUCE 1. Move all windows to the right big Panasonic screen 2. Switch AVR in/out of standby mode OBSERVED RESULT All windows are moved to the left small Samsung screen EXPECTED RESULT All windows should remain on the screen where they are, in my case all should be on the right screen SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240514 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-default (64-bit) Mesa Version: 24.0.5 Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics Manufacturer: ASUS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472625] sys monitor show space bug
https://bugs.kde.org/show_bug.cgi?id=472625 --- Comment #4 from Jure Repinc --- Created attachment 169359 --> https://bugs.kde.org/attachment.cgi?id=169359&action=edit Disk and disk partitions, space screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472625] sys monitor show space bug
https://bugs.kde.org/show_bug.cgi?id=472625 --- Comment #3 from Jure Repinc --- I also have this bug here. I have a 2 TB SSD and System monitor reports total space as 4 TB (3,6 TiB). Total used space appears to be reported correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472625] sys monitor show space bug
https://bugs.kde.org/show_bug.cgi?id=472625 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 485025] System monitor unable to see any sensors
https://bugs.kde.org/show_bug.cgi?id=485025 --- Comment #1 from Jure Repinc --- I have a similar issue here. Only two hardware sensors (iwlwifi_1-virtual-0, nvme-pci-0a00) of all the ones available are shown. This is what "sensors" command shows: nct6799-isa-0290 Adapter: ISA adapter in0: 920.00 mV (min = +0.00 V, max = +1.74 V) in1:1.02 V (min = +0.00 V, max = +0.00 V) ALARM in2:3.39 V (min = +0.00 V, max = +0.00 V) ALARM in3:3.34 V (min = +0.00 V, max = +0.00 V) ALARM in4:1.02 V (min = +0.00 V, max = +0.00 V) ALARM in5:1.03 V (min = +0.00 V, max = +0.00 V) in6: 632.00 mV (min = +0.00 V, max = +0.00 V) ALARM in7:3.39 V (min = +0.00 V, max = +0.00 V) ALARM in8:3.30 V (min = +0.00 V, max = +0.00 V) ALARM in9:3.34 V (min = +0.00 V, max = +0.00 V) ALARM in10: 1.39 V (min = +0.00 V, max = +0.00 V) ALARM in11: 1.12 V (min = +0.00 V, max = +0.00 V) ALARM in12: 1.03 V (min = +0.00 V, max = +0.00 V) ALARM in13: 440.00 mV (min = +0.00 V, max = +0.00 V) ALARM in14: 2.03 V (min = +0.00 V, max = +0.00 V) ALARM in15: 848.00 mV (min = +0.00 V, max = +0.00 V) ALARM in16: 1.82 V (min = +0.00 V, max = +0.00 V) ALARM in17: 1.28 V (min = +0.00 V, max = +0.00 V) fan1:0 RPM (min =0 RPM) fan2: 1656 RPM (min =0 RPM) fan3:0 RPM (min =0 RPM) fan4:0 RPM (min =0 RPM) fan5:0 RPM (min =0 RPM) fan6:0 RPM (min =0 RPM) fan7:0 RPM (min =0 RPM) SYSTIN:+34.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor CPUTIN:+54.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN0: +47.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN1:+5.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN2: +19.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +100.0°C) sensor = thermistor AUXTIN3: -60.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN4: +24.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +100.0°C) PECI/TSI Agent 0 Calibration: +61.0°C (high = +80.0°C, hyst = +75.0°C) AUXTIN5: +12.0°C PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C TSI0_TEMP: +72.5°C intrusion0: ALARM intrusion1: OK beep_enable: disabled k10temp-pci-00c3 Adapter: PCI adapter Tctl: +72.4°C Tccd1:+64.5°C nvme-pci-0a00 Adapter: PCI adapter Composite:+44.9°C (low = -273.1°C, high = +80.8°C) (crit = +80.8°C) Sensor 1: +44.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +49.9°C (low = -273.1°C, high = +65261.8°C) iwlwifi_1-virtual-0 Adapter: Virtual device temp1:+35.0°C amdgpu-pci-0100 Adapter: PCI adapter vddgfx:1.13 V fan1: 860 RPM (min =0 RPM, max = 2900 RPM) edge: +59.0°C (crit = +94.0°C, hyst = -273.1°C) PPT: 52.07 W (cap = 180.00 W) SYSTEM INFO: System Monitor version 5.92.90 Operating System: openSUSE Tumbleweed 20240506 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 485025] System monitor unable to see any sensors
https://bugs.kde.org/show_bug.cgi?id=485025 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486794] New: Add option to set keyboard shortcuts to directly switch power management profiles
https://bugs.kde.org/show_bug.cgi?id=486794 Bug ID: 486794 Summary: Add option to set keyboard shortcuts to directly switch power management profiles Classification: Plasma Product: Powerdevil Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- It would be nice to have the possibility to switch to some power management profile directly with a configurable keyboard shortcut for the three profiles. It would also make it possible to bind the shortcut to the three special/dedicated power profile keyboard buttons on KDE Slimbook V laptop. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483130] Unlocking with fingerprint leads to other PAM session authentication failure
https://bugs.kde.org/show_bug.cgi?id=483130 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 481069] Consider re-adding the feature to execute commands in notifications
https://bugs.kde.org/show_bug.cgi?id=481069 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474385] Plasma crashes when closing notification after removing icon applet
https://bugs.kde.org/show_bug.cgi?id=474385 --- Comment #6 from Jure Repinc --- Created attachment 167119 --> https://bugs.kde.org/attachment.cgi?id=167119&action=edit Full crash backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474385] Plasma crashes when closing notification after removing icon applet
https://bugs.kde.org/show_bug.cgi?id=474385 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com --- Comment #5 from Jure Repinc --- Just happened to me now. Dragged a *.sh from dolphin to desktop, it created an Icon widgets for URL. Delted it and closed the undo notification and it crahed with the following backtrace Thread 1 (Thread 0x7fa73dadfac0 (LWP 3463)): [KCrash Handler] #5 0x7fa740bd1a2f in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) (sender=0x557abc8c5730, signal=signal@entry=0x0, receiver=receiver@entry=0x7fa7280af0b0, method=method@entry=0x0) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:3215 #6 0x7fa74359e783 in Plasma::Applet::~Applet() (this=0x7fa7280af0b0, this=) at /usr/src/debug/libplasma-6.0.80git.20240307T011941~61071f0f/src/plasma/applet.cpp:75 #7 0x7fa734279c79 in IconApplet::~IconApplet() (this=0x7fa7280af0b0, this=) at /usr/src/debug/plasma-workspace-6.0.80git.20240309T123152~911ef51c/applets/icon/iconapplet.cpp:56 #8 0x7fa740bca6b7 in QObject::event(QEvent*) (this=0x7fa7280af0b0, e=0x557abb0c78c0) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1424 #9 0x7fa742dc1aae in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7fa7280af0b0, e=0x557abb0c78c0) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296 #10 0x7fa740b87498 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fa7280af0b0, event=0x557abb0c78c0) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121 #11 0x7fa740b874d9 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539 #12 0x7fa740b877f7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x557ab3ac6680) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1901 #13 0x7fa740da6783 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x557ab3b825e0) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:243 #14 0x7fa73f9aef30 in g_main_dispatch (context=0x7fa738000ef0) at ../glib/gmain.c:3476 #15 g_main_context_dispatch_unlocked (context=context@entry=0x7fa738000ef0) at ../glib/gmain.c:4284 #16 0x7fa73f9b0b58 in g_main_context_iterate_unlocked (context=context@entry=0x7fa738000ef0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4349 #17 0x7fa73f9b120c in g_main_context_iteration (context=0x7fa738000ef0, may_block=1) at ../glib/gmain.c:4414 #18 0x7fa740da330c in QEventDispatcherGlib::processEvents(QFlags) (this=0x557ab3b05ae0, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #19 0x7fa740b91cbb in QEventLoop::exec(QFlags) (this=0x7ffe1a652a60, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:34 #20 0x7fa740b8b8e6 in QCoreApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #21 0x7fa7413e31bc in QGuiApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:1925 #22 0x7fa742dbeee5 in QApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574 #23 0x557ab312615e in main(int, char**) (argc=, argv=) at /usr/src/debug/plasma-workspace-6.0.80git.20240309T123152~911ef51c/shell/main.cpp:211 Operating System: openSUSE Tumbleweed 20240308 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483456] New: Can't properly translate some messages composed from multiple string (e.g. number of users leaving/joining room)
https://bugs.kde.org/show_bug.cgi?id=483456 Bug ID: 483456 Summary: Can't properly translate some messages composed from multiple string (e.g. number of users leaving/joining room) Classification: Applications Product: NeoChat Version: git master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: j...@holodeck1.com CC: c...@carlschwan.eu Target Milestone: --- In Slovenian language the verb form depends on the number of subjects. E.g. in English you can do composition like this "1 user" "joined the room" "2 users" "joined the room" so you reuse the "joined the room" part for all number of users. But in Slovenian the verb from the second part depends on the number of users: "1 uporabnik" "se je pridružil v sobi" "2 uporabnika" "sta se pridružila v sobi" So you can not reuse the exact same second part. One (not recommended) way of solving this is to also mark the second string as plural. But such jigsaw puzzle style of user message composition from multiple strings is not recommended at all for translation. The strings should be offered as only one string marked as plural so it is all translated as one entity. So far I could see the problem with room events, but maybe there is more. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483090] Crash on startup: RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined
https://bugs.kde.org/show_bug.cgi?id=483090 --- Comment #5 from Jure Repinc --- Created attachment 166975 --> https://bugs.kde.org/attachment.cgi?id=166975&action=edit Blank spaces in list of rooms -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483090] Crash on startup: RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined
https://bugs.kde.org/show_bug.cgi?id=483090 --- Comment #4 from Jure Repinc --- Can confirm the crash is gone. Thanks. NeoChat now starts up fine and I can see rooms and all. Although I do get some strange blank spaces in the rooms list in the panel on the left. Not sure if it is related with this bug or something else to report separately. I'll upload a screenshot of the problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483153] New: Dolphin crashed when I restarted plasmashell
https://bugs.kde.org/show_bug.cgi?id=483153
Bug ID: 483153
Summary: Dolphin crashed when I restarted plasmashell
Classification: Applications
Product: dolphin
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: j...@holodeck1.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (24.04.70)
Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.7-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.0.80 [CoredumpBackend]
-- Information about the crash:
I noticed that the panel with task manager got stuck in always visible state (I
have it set to auto-hide) and covering lower parts of windows (status bars). At
the same time I had Dolphin window open, but not focused. So I decided to
restart plasmashell. When it restarted Dolphin crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
This GDB supports auto-downloading debuginfo from the following URLs:
[NeoChat] [Bug 483090] Crash on startup: RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined
https://bugs.kde.org/show_bug.cgi?id=483090 Jure Repinc changed: What|Removed |Added Version|24.02.0 |git master --- Comment #1 from Jure Repinc --- Fixing the version to git, the actuall commit this is from is e029aaad -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483090] New: Crash on startup: RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined
https://bugs.kde.org/show_bug.cgi?id=483090 Bug ID: 483090 Summary: Crash on startup: RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined Classification: Applications Product: NeoChat Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: j...@holodeck1.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166855 --> https://bugs.kde.org/attachment.cgi?id=166855&action=edit Full crash backtrace I have just started and logged into my Matrix account and then when rooms and all should start loading it crashed. When I relaunch it and select the existing account it also just crashes when it should display rooms. STEPS TO REPRODUCE 1. Login with existing account (I have it on matrix.org) 2. proceed to loading rooms and all OBSERVED RESULT NeoChat crashes and this is shown in the konsole: [22::56:48.611] unknown: State cache incomplete, discarding [22::56:48.616] unknown: qrc:/qt/qml/org/kde/neochat/qml/main.qml:266:9: QML RoomListPage: Created graphical object was not placed in the graphics scene. [New Thread 0x7fff92a006c0 (LWP 26437)] [22::57:5.485] unknown: QSortFilterProxyModel: inconsistent changes reported by source model [22::57:5.488] unknown: QSortFilterProxyModel: inconsistent changes reported by source model [22::57:5.498] unknown: qrc:/qt/qml/org/kde/neochat/qml/RoomListPage.qml:143: TypeError: Cannot read property 'id' of undefined EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240303 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION This is the backtrace I got manually by running it via GDB: Thread 1 "neochat" received signal SIGSEGV, Segmentation fault. […] Thread 1 (Thread 0x72097b00 (LWP 26262) "neochat"): #0 RoomTreeModel::data(QModelIndex const&, int) const (this=, index=, role=17) at /usr/src/debug/neochat-24.04.70git.20240304T180525~e029aaa/src/models/roomtreemodel.cpp:259 #1 0x74f8ea39 in QSortFilterProxyModel::data(QModelIndex const&, int) const (this=this@entry=0x565d7060, index=..., role=role@entry=17) at /usr/src/debug/qtbase-everywhere-src-6.6.2/src/corelib/itemmodels/qsortfilterproxymodel.cpp:2211 #2 0x752993ab in QQmlTreeModelToTableModel::data(QModelIndex const&, int) const (this=, index=, role=17) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmltreemodeltotablemodel.cpp:154 #3 0x752bc138 in QModelIndex::data(int) const (arole=, this=) at /usr/include/qt6/QtCore/qabstractitemmodel.h:493 #4 VDMAbstractItemModelDataType::value(QQmlAdaptorModel const&, int, QString const&) const (this=0x564e8e10, model=, index=, role=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmldmabstractitemmodeldata_p.h:249 #5 0x752b8768 in QQmlAdaptorModel::value(int, QString const&) const (role=..., index=, this=0x570d2980) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmladaptormodel_p.h:110 #6 QQmlAbstractDelegateComponent::value(QQmlAdaptorModel*, int, int, QString const&) const (this=, adaptorModel=0x570d2980, row=, column=, role=...) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmlabstractdelegatecomponent.cpp:22 --Type for more, q to quit, c to continue without paging-- #7 0x7fffcc07c585 in QQmlDelegateChooser::delegate(QQmlAdaptorModel*, int, int) const () at /lib64/libQt6LabsQmlModels.so.6 #8 0x75294d8e in QQmlTableInstanceModel::resolveDelegate(int) (index=1460480384, this=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmltableinstancemodel.cpp:81 #9 QQmlTableInstanceModel::resolveDelegate(int) (this=this@entry=0x570d2970, index=index@entry=1) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmltableinstancemodel.cpp:73 #10 0x75295033 in QQmlTableInstanceModel::resolveModelItem(int) (this=this@entry=0x570d2970, index=1) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmltableinstancemodel.cpp:97 #11 0x752953bf in QQmlTableInstanceModel::object(int, QQmlIncubator::IncubationMode) (this=0x570d2970, index=, incubationMode=QQmlIncubator::AsynchronousIfNested) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qmlmodels/qqmltableinstancemodel.cpp:127 #12 0x7788f8e4 in QQuickTableViewPrivate::createFxTableItem(QPoint const&, QQmlIncubator::IncubationMode) (this=this@entry=0x56fd8100, cell=..., incubationMode=QQmlIncubator::AsynchronousIfNested) at /usr/src/debu
[NeoChat] [Bug 475140] make fontsize customisable in neochat
https://bugs.kde.org/show_bug.cgi?id=475140 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477416] Wishlist: Can the last read indicator act more like Konversation?
https://bugs.kde.org/show_bug.cgi?id=477416 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481644] Neochat appears to "lose" the encryption keys, and there doesn't appear to be any kind of way to tell neochat to fetch them again
https://bugs.kde.org/show_bug.cgi?id=481644 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 482867] Lokalize crashed after saving changes and immidiately closing the tab
https://bugs.kde.org/show_bug.cgi?id=482867 --- Comment #1 from Jure Repinc --- Console output at the time of the crash: [13::14:40.201] unknown: db "kde6-trunk140446001006272" opened 0 "sl" [13::16:28.749] unknown: alt trans file doesn't exist: "/home/jlp/Prevajanje/kde5/trunk/sl/messages/kxmlgui/kxmlgui6.po" [13::16:28.791] unknown: indexed "/home/jlp/Prevajanje/kde6/trunk/sl/messages/kxmlgui/kxmlgui6.po" for word completion in 0 msecs [13::16:28.836] unknown: db "kde6-trunk140446001006272" opened 0 "sl" [13::17:7.210] unknown: QFile::remove: Empty or null file name [13::17:23.599] unknown: alt trans file doesn't exist: "/home/jlp/Prevajanje/kde5/trunk/sl/messages/kwin/kwin.po" [13::17:23.626] unknown: indexed "/home/jlp/Prevajanje/kde6/trunk/sl/messages/kwin/kwin.po" for word completion in 1 msecs [13::19:43.669] unknown: QFile::remove: Empty or null file name 22 -- exe=/usr/bin/lokalize 13 -- platform=xcb 11 -- display=:1 17 -- appname=lokalize 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=31492 20 -- appversion=24.04.70 21 -- programname=Lokalize 31 -- bugaddress=sub...@bugs.kde.org KCrash: Application 'lokalize' crashing... KCrash: Attempting to start /usr/libexec/drkonqi [1]+ ZaustavljenoQT_QPA_PLATFORM=xcb lokalize -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 482867] New: Lokalize crashed after saving changes and immidiately closing the tab
https://bugs.kde.org/show_bug.cgi?id=482867
Bug ID: 482867
Summary: Lokalize crashed after saving changes and immidiately
closing the tab
Classification: Applications
Product: lokalize
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: sdepi...@gmail.com
Reporter: j...@holodeck1.com
CC: aa...@kde.org, sha...@ukr.net
Target Milestone: ---
Application: lokalize (24.04.70)
Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.7-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.0.80 [KCrashBackend]
-- Information about the crash:
Lokalize crashed after I saved the changes I made using keyboard shortcut
(Ctrl+S) and immidiately closing the tab via keyboard shortcut (Ctrl+W). The
tab was opened from the search tab searching for a string in all files from
messages folder,
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Lokalize (lokalize), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fbc456bc3d2 in QSortFilterProxyModel::parent(QModelIndex const&)
const (child=, this=0x55a197d779a0) at
itemmodels/qsortfilterproxymodel.cpp:2219
#7 QSortFilterProxyModel::parent(QModelIndex const&) const
(this=0x55a197d779a0, child=) at
itemmodels/qsortfilterproxymodel.cpp:2212
#8 0x55a193f35962 in QModelIndex::parent() const (this=0x55a199ff6560) at
/usr/include/qt5/QtCore/qabstractitemmodel.h:443
#9 TM::DBFilesModel::updateStats(QModelIndex const&, QModelIndex const&)
(this=0x55a197d779a0, topLeft=..., bottomRight=) at
/usr/src/debug/lokalize-24.04.70git.20240224T021027~982419e/src/tm/dbfilesmodel.cpp:145
#10 0x7fbc457196f0 in QObject::event(QEvent*) (this=0x55a197d779a0,
e=0x7fbc1930) at kernel/qobject.cpp:1347
#11 0x7fbc465a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55a197d779a0, e=0x7fbc1930) at
kernel/qapplication.cpp:3640
#12 0x7fbc456ed938 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55a197d779a0, event=0x7fbc1930) at
kernel/qcoreapplication.cpp:1064
#13 0x7fbc456edafe in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=, event=) at
kernel/qcoreapplication.cpp:1462
#14 0x7fbc456f0f31 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55a195e63060) at
kernel/qcoreapplication.cpp:1821
#15 0x7fbc456f1478 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=, event_type=) at
kernel/qcoreapplication.cpp:1680
#16 0x7fbc45747063 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55a196021890) at kernel/qeventdispatcher_glib.cpp:277
#17 0x7fbc43913f30 in g_main_dispatch (context=0x7fbc38000ec0) at
../glib/gmain.c:3476
#18 g_main_context_dispatch_unlocked (context=context@entry=0x7fbc38000ec0) at
../glib/gmain.c:4284
#19 0x7fbc43915b58 in g_main_context_iterate_unlocked
(context=context@entry=0x7fbc38000ec0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4349
#20 0x7fbc4391620c in g_main_context_iteration (context=0x7fbc38000ec0,
may_block=1) at ../glib/gmain.c:4414
#21 0x7fbc45746876 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55a19602b510, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7fbc456ec3cb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffd1dd49c90, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7fbc456f4860 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7fbc45d7061c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1870
#25 0x7fbc465a5125 in QApplication::exec() () at
kernel/qapplication.cpp:2832
#26 0x55a193e95a82 in main(int, char**) (argc=,
argv=) at
/usr/src/debug/lokalize-24.04.70git.20240224T021027~982419e/src/main.cpp:135
[Inferior 1 (process 31492) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 444335] Full sticky keys functionality does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #20 from Jure Repinc --- (In reply to Nicolas Fella from comment #15) > I'm just not sure how relevant things like "Ring system bell when locking > keys are toggled" > actually are I remember this (and audible confirmations for many other state changes) being mentioned as a requirement for software acceptance for use in Slovenian government offices. Sure the presentation was something like 15-20 years ago, but I doubt it has changed. And I suspect a couple of other public institutions in other countries might have the same requirement. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482446] Plasma crashed when clicking on task manager button after disconnecting/reconnecting screen
https://bugs.kde.org/show_bug.cgi?id=482446 --- Comment #1 from Jure Repinc --- Created attachment 166417 --> https://bugs.kde.org/attachment.cgi?id=166417&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482446] New: Plasma crashed when clicking on task manager button after disconnecting/reconnecting screen
https://bugs.kde.org/show_bug.cgi?id=482446 Bug ID: 482446 Summary: Plasma crashed when clicking on task manager button after disconnecting/reconnecting screen Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: 1.0 Application: plasmashell (6.0.80) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.6-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 6.0.80 [CoredumpBackend] -- Information about the crash: I have two screens and one is connected through AVR. When AVR gets turned on/off the screen configuration is updated (probably because of HDMI audio changes where audio gets switched between AVR output and TV screen output). When this happens windows get rearrangen between the screen (sometimes some windows don't end up on the screen they were before). I also have two panels with two task manager widgets one on each screen. They are set to show only buttons for windows from current screen. But after this rearrangement happens it happened that window was only on one screen but the button for it was shown on both task manager widgets (as if the window was on two screens at the same time which is quite impossible I would say). I tried to minimize windows and drag them around so that they would hopefully update the task manager diplay, but it did not help. When I clicked ona button for such a window on the task manager plasma crashed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 wl_proxy_get_version (proxy=0xffa6571dff03) at ../src/wayland-client.c:2248 #6 0x7f7205dbd4f3 in org_kde_plasma_window_set_state (state=1, flags=1, org_kde_plasma_window=0xffa6571dff03) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/wayland-plasma-window-management-client-protocol.h:777 #7 QtWayland::org_kde_plasma_window::set_state(unsigned int, unsigned int) (this=, state=1, flags=1) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/qwayland-plasma-window-management.cpp:236 #8 TaskManager::WaylandTasksModel::requestActivate(QModelIndex const&) (this=, index=) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/waylandtasksmodel.cpp:955 #9 0x7f7205d726b3 in TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (index=, this=) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:24 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477959] Plasma 6 locks up on 6th gen i5 laptop with AMS turned on
https://bugs.kde.org/show_bug.cgi?id=477959 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476860] Plasma 6: Half the FPS with atomic mode setting
https://bugs.kde.org/show_bug.cgi?id=476860 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482107] Open Terminal here fails to open Konsole
https://bugs.kde.org/show_bug.cgi?id=482107 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481948] Ocean sound theme not installed
https://bugs.kde.org/show_bug.cgi?id=481948 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479987] Neon should check and install related language packs
https://bugs.kde.org/show_bug.cgi?id=479987 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481940] krunner not launching due to org.kde.krunner.service file not installed.
https://bugs.kde.org/show_bug.cgi?id=481940 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481918] New: KTeaTime steeping progress indicator is rendered incorrectly (too big)
https://bugs.kde.org/show_bug.cgi?id=481918 Bug ID: 481918 Summary: KTeaTime steeping progress indicator is rendered incorrectly (too big) Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 166150 --> https://bugs.kde.org/attachment.cgi?id=166150&action=edit KTeaTime progress indicator is visible in the right half of the picture, bottom left corner SUMMARY When a tea is steeping in KTeaTime there is a progress indicator (like a small piechart) being shown over the system tray icon. But it has the incorrect size, it is too big and much of it is cut of. STEPS TO REPRODUCE 1. Start KTeaTime 2. Select a tea from the context menu of the tray icon so the steeping begins OBSERVED RESULT Steeping progress indicator is too big and cut of EXPECTED RESULT Steeping progress indicator should be visible fully SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481917] KTeaTime dark symbolic tray icon is almost invisible when the tray background is dark/black
https://bugs.kde.org/show_bug.cgi?id=481917 --- Comment #1 from Jure Repinc --- Created attachment 166149 --> https://bugs.kde.org/attachment.cgi?id=166149&action=edit KTeaTime tray icon screenshots -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481917] New: KTeaTime dark symbolic tray icon is almost invisible when the tray background is dark/black
https://bugs.kde.org/show_bug.cgi?id=481917 Bug ID: 481917 Summary: KTeaTime dark symbolic tray icon is almost invisible when the tray background is dark/black Classification: Plasma Product: Breeze Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: j...@holodeck1.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY There is a symbolic icon now in breeze package for KTeatime (/usr/share/icons/breeze-dark/apps/22/kteatime-symbolic.svg) but it is the same as the normal symbolic icon (/usr/share/icons/breeze/apps/22/kteatime-symbolic.svg). So it is a very dark icon and is almost invisible if the plasma theme for system tray/panels has dark or black background. STEPS TO REPRODUCE 1. Set Plasma theme to use something dark or black for tray/panel background 2. Star KTeaTime OBSERVED RESULT KTeaTime icon is barely visible EXPECTED RESULT KTeaTime icons should be much more light to have good contrast with background SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 481911] New: Content font size setting is not respected for post content
https://bugs.kde.org/show_bug.cgi?id=481911 Bug ID: 481911 Summary: Content font size setting is not respected for post content Classification: Applications Product: Tokodon Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: j...@holodeck1.com CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 166146 --> https://bugs.kde.org/attachment.cgi?id=166146&action=edit Screenshot of Tokodon font size bug This is for Tokodon version 24.04.70. Content font size appears to only apply to display and account name of the poster and not to the post content itself STEPS TO REPRODUCE 1. Open settings 2. Change content font size to something big OBSERVED RESULT Only Display and account names are enlarged, the font size of post content remains the same EXPECTED RESULT Content post font size should also become bigger. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467724] Allow refreshing an open toot
https://bugs.kde.org/show_bug.cgi?id=467724 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 469833] Support for Peertube
https://bugs.kde.org/show_bug.cgi?id=469833 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 477904] support for LaTeX rendering
https://bugs.kde.org/show_bug.cgi?id=477904 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469762] Give us a way to configure if the destination opens or not after creating an archive via "Compress to..." option from the context menus
https://bugs.kde.org/show_bug.cgi?id=469762 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i
https://bugs.kde.org/show_bug.cgi?id=440663 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442477] Dolphin opens new window or tab when compressing or extracting archives
https://bugs.kde.org/show_bug.cgi?id=442477 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 481778] New: Text in lines is cut in half, only lower half of the line text is visible when font size less than 14
https://bugs.kde.org/show_bug.cgi?id=481778 Bug ID: 481778 Summary: Text in lines is cut in half, only lower half of the line text is visible when font size less than 14 Classification: Applications Product: kompare Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: viewpart Assignee: kompare-de...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- Created attachment 166069 --> https://bugs.kde.org/attachment.cgi?id=166069&action=edit Screenshot of the line bug SUMMARY When I open Kompare to show differences between two files the text in each line is only partially shown, only the bottom half is shown. I tried selecting different fonts (e.g. Hack, DejaVU Sans Mono) and it made no difference. Only when the font size was 14 or more it was fine. See the attached screenshot. STEPS TO REPRODUCE 1. Open Kompare 2. Select two files to show diff of 3. Set font size to less than 14 OBSERVED RESULT Text in each line is cut off in half and only the bottom line is shown EXPECTED RESULT Entire text should be shown in the line SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240220 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics ADDITIONAL INFORMATION I have two screen setup, one is set to 150% scale the other to 200% -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 460873] Missing Wayland API to access Kwin's "keep above others" and "show on all desktops"
https://bugs.kde.org/show_bug.cgi?id=460873 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450579] Wayland: Can't drag and drop to panel when set to Auto Hide
https://bugs.kde.org/show_bug.cgi?id=450579 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com --- Comment #6 from Jure Repinc --- *** Bug 481474 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481474] Dragging content from applications to autohidden panel does not un-hide the panel
https://bugs.kde.org/show_bug.cgi?id=481474 Jure Repinc changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Jure Repinc --- *** This bug has been marked as a duplicate of bug 450579 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481474] Dragging content from applications to autohidden panel does not un-hide the panel
https://bugs.kde.org/show_bug.cgi?id=481474 Jure Repinc changed: What|Removed |Added Version|git-master |master Component|General |Panel Assignee|noaha...@gmail.com |plasma-b...@kde.org Target Milestone|--- |1.0 Product|Spectacle |plasmashell CC||niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481474] Dragging content from applications to autohidden panel does not un-hide the panel
https://bugs.kde.org/show_bug.cgi?id=481474 Jure Repinc changed: What|Removed |Added Summary|Dragging screenshot from|Dragging content from |Spectacle to autohidden |applications to autohidden |panel does not un-hide the |panel does not un-hide the |panel |panel -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481474] Dragging screenshot from Spectacle to autohidden panel does not un-hide the panel
https://bugs.kde.org/show_bug.cgi?id=481474 Jure Repinc changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Jure Repinc --- Indeed happens with all the dragging I tried, just noticed with Spectacle first. I guess this should be moved to Plasma then. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 481474] New: Dragging screenshot from Spectacle to autohidden panel does not un-hide the panel
https://bugs.kde.org/show_bug.cgi?id=481474 Bug ID: 481474 Summary: Dragging screenshot from Spectacle to autohidden panel does not un-hide the panel Classification: Applications Product: Spectacle Version: git-master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: j...@holodeck1.com CC: k...@david-redondo.de Target Milestone: --- Often I want to drag the screenshot from Spectacle to some other application window but if I have the Plasma panel set to autohide, then moving the cursor towards the screen edge where the panel is hiding does not show it so I could continue dragging the screenshot to specific window, where I intend to drop it. STEPS TO REPRODUCE 1. Set Plasma panel to autohide 2. Open some target application when you would like to drag screenshot later 3. Press PrintScreen key to open Spectacle and make screenshot 4. Using the left mouse button start dragging the screenshot towards the screen edge where Plasma panel is hiding OBSERVED RESULT Plasma panel does not get show and enable you to drag the screenshot to target application window EXPECTED RESULT Plasma panel should un-hide the panel and does not allow dragging to continue to target application window SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240214 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481464] Context menu for last/lower entries is misplaced on Wayland
https://bugs.kde.org/show_bug.cgi?id=481464 --- Comment #1 from Jure Repinc --- Created attachment 165902 --> https://bugs.kde.org/attachment.cgi?id=165902&action=edit Screenshot of context menu displacement I clicked on the last entry in the file list and the context menu is displaced quite a bit towards the top -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481464] New: Context menu for last/lower entries is misplaced on Wayland
https://bugs.kde.org/show_bug.cgi?id=481464 Bug ID: 481464 Summary: Context menu for last/lower entries is misplaced on Wayland Classification: Applications Product: dolphin Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: j...@holodeck1.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 165898 --> https://bugs.kde.org/attachment.cgi?id=165898&action=edit Display configuration SUMMARY Using Dolphin 24.04.70 on openSUSE Tumbleweed with packages built daily from KDE git. Some more system info: Operating System: openSUSE Tumbleweed 20240214 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 480 Graphics I have two monitors, setup with different resolutions/sizes and different scaling settings. See attached screenshots. STEPS TO REPRODUCE 1. Right click on any of the last entries in sidepanel (e.g. one under Devices subsection) or in the files list right after you open Dolphin. The lower you click the more context menu is displaced, OBSERVED RESULT Context menu opens but is misplaced, does not appear at the point where you clicked with mouse. You have to switch to another window and then back to get the context menu placed properly. EXPECTED RESULT Place the context menu at the point where you rightclick with mouse right away. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #9 from Jure Repinc --- I just did a regular morning update of packages and the problem appears to be fixed. All mentioned KCMs open now. During the update Qt was updated to version 6.6.2 so maybe that version has a fix for this problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 297253] Left panel remains narrow even after window has been resized to a larger size
https://bugs.kde.org/show_bug.cgi?id=297253 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468539] Side panels do not remember size when resizing
https://bugs.kde.org/show_bug.cgi?id=468539 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 --- Comment #5 from Jure Repinc --- Hi this is my backtrace from running "gdb --args systemsettings kcm_pulseaudio" since KDE crash handler does not catch this crash: [New Thread 0x724006c0 (LWP 18127)] [New Thread 0x714006c0 (LWP 18128)] [New Thread 0x70a006c0 (LWP 18129)] [New Thread 0x7fffe9c006c0 (LWP 18130)] [New Thread 0x7fffe92006c0 (LWP 18131)] [New Thread 0x7fffe3e006c0 (LWP 18132)] [New Thread 0x7fffe34006c0 (LWP 18133)] [New Thread 0x7fffe2a006c0 (LWP 18134)] [New Thread 0x7fffe20006c0 (LWP 18135)] [New Thread 0x7fffe16006c0 (LWP 18136)] [New Thread 0x7fffe0c006c0 (LWP 18137)] [New Thread 0x7fffcfe006c0 (LWP 18138)] [New Thread 0x7fffcf4006c0 (LWP 18139)] [New Thread 0x7fffcea006c0 (LWP 18140)] [New Thread 0x7fffce0006c0 (LWP 18141)] [Thread 0x7fffce0006c0 (LWP 18141) exited] [Thread 0x7fffcea006c0 (LWP 18140) exited] [Thread 0x7fffcf4006c0 (LWP 18139) exited] [Thread 0x7fffcfe006c0 (LWP 18138) exited] [Thread 0x7fffe0c006c0 (LWP 18137) exited] [Thread 0x7fffe16006c0 (LWP 18136) exited] [New Thread 0x7fffe16006c0 (LWP 18142)] [New Thread 0x7fffe0c006c0 (LWP 18143)] [New Thread 0x7fffcfe006c0 (LWP 18144)] [New Thread 0x7fffcf4006c0 (LWP 18145)] [New Thread 0x7fffcea006c0 (LWP 18146)] [New Thread 0x7fffce0006c0 (LWP 18147)] [Thread 0x7fffce0006c0 (LWP 18147) exited] [Thread 0x7fffcea006c0 (LWP 18146) exited] [Thread 0x7fffcf4006c0 (LWP 18145) exited] [Thread 0x7fffcfe006c0 (LWP 18144) exited] [Thread 0x7fffe0c006c0 (LWP 18143) exited] [Thread 0x7fffe16006c0 (LWP 18142) exited] [New Thread 0x7fffe16006c0 (LWP 18148)] [13::20:17.198] unknown: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" Thread 23 "QQmlThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe16006c0 (LWP 18148)] QQmlPropertyCacheCreator::propertyCacheForObject (error=0x7fffe15fe978, context=..., obj=0x7fffa05d8358, this=0x7fffe15fed20) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/jsruntime/qv4resolvedtypereference_p.h:90 90 /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/jsruntime/qv4resolvedtypereference_p.h: Datoteka ali imenik s tem imenom ne obstaja. Missing separate debuginfos, use: zypper install libKF6Notifications6-debuginfo-5.249.0git.20240206T012100~0e5077e-65.1.x86_64 libpulse-mainloop-glib0-debuginfo-17.0-1.4.x86_64 (gdb) thread apply all bt Thread 23 (Thread 0x7fffe16006c0 (LWP 18148) "QQmlThread"): #0 QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const (error=0x7fffe15fe978, context=..., obj=0x7fffa05d8358, this=0x7fffe15fed20) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/jsruntime/qv4resolvedtypereference_p.h:90 #1 QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7fffe15fed20, objectIndex=20, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:277 #2 0x7615d297 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=0x7fffe15fed20, objectIndex=0, context=, isVMERequired=) at /usr/include/qt6/QtCore/qendian.h:258 #3 0x761535ef in QQmlPropertyCacheCreator::buildMetaObjectsIncrementally() (this=0x7fffe15fed20) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/build/include/QtQml/6.6.1/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:223 #4 QQmlTypeCompiler::compile() (this=0x7fffe15fef90) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypecompiler.cpp:62 #5 0x761638f0 in QQmlTypeData::compile(QQmlRefPointer const&, QV4::ResolvedTypeReferenceMap*, std::function const&) (dependencyHasher=..., resolvedTypeCache=0x7fffe15feec0, typeNameCache=..., this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:852 #6 QQmlTypeData::done() (this=) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmltypedata.cpp:502 #7 0x760a8f3b in QQmlDataBlob::tryDone() (this=0x7fffa05c34f0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:485 #8 QQmlDataBlob::tryDone() (this=0x7fffa05c34f0) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.1/src/qml/qml/qqmldatablob.cpp:476 #9 0x76171410 in QQmlTypeLoa
[systemsettings] [Bug 481192] Systemsettings crashes when going into various kcm modules
https://bugs.kde.org/show_bug.cgi?id=481192 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 479265] QML Cyclic dependency
https://bugs.kde.org/show_bug.cgi?id=479265 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 478235] New: Disable building testing if chai-PythonModule is not found
https://bugs.kde.org/show_bug.cgi?id=478235 Bug ID: 478235 Summary: Disable building testing if chai-PythonModule is not found Classification: Applications Product: drkonqi Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: j...@holodeck1.com Target Milestone: --- Created attachment 163994 --> https://bugs.kde.org/attachment.cgi?id=163994&action=edit cmake.log SUMMARY I tried to build DrKonqi via kdesrc-build (as part of workspace build) and since I do not have chai-PythonModule module installed it failed with an error. STEPS TO REPRODUCE 1. have a system without chai-PythonModule 2. try to build drkonqi, e.g. with kdesrc-build OBSERVED RESULT The build failed with error: -- The following REQUIRED packages have not been found: * chai-PythonModule, Python module chai is required for testing. EXPECTED RESULT Maybe the testing build could automatically be disabled also if chai is not found, and it could continue building the rest without it. -- You are receiving this mail because: You are watching all bug changes.
