[systemsettings] [Bug 484046] Joysticks are not detected in System Settings / Game Controller
https://bugs.kde.org/show_bug.cgi?id=484046 Rose changed: What|Removed |Added CC||thorned.rose@intothegarbage ||chuteflyboy.net --- Comment #1 from Rose --- I have the same issue with my Thrustmaster T-flight. Only it is also crashing the only application I use my HOTAS with. My system (also Arch Linux and KDE Plasma 6.0.4), correctly detects the HOTAS: Bus 003 Device 004: ID 044f:b108 ThrustMaster, Inc. T-Flight Hotas X Flight Stick It worked perfectly with Plasma 5. This has only started since 6. I normally use my HOTAS with Elite Dangerous (the only software I use it with) via Steam Proton. Since Plasma 6, Elite Dangerous (ED) crashes constantly on "Planetary generation system". Deleting ED's Bindings file worked for a while to get around that but any time I brought back any custom bindings, it's straight back to crashing. Since trying swapping USB ports, it crashes regardless and the game is now unplayable. I have tried installed joyutils, jstest-gtk (my HOTAS shows up there fine), swapping USB ports, different Proton versions, verifying game files, reinstalling the Elite Dangerous, switching from Wayland to X11. Other reports of same issue: - https://bbs.archlinux.org/viewtopic.php?pid=2170071 - https://www.reddit.com/r/kde/comments/1bti68v/kde_6_controller_calibrate/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423815] New: Krita crashes when I create or click a frame while animating and also crashes when I make a layer while animating
https://bugs.kde.org/show_bug.cgi?id=423815 Bug ID: 423815 Summary: Krita crashes when I create or click a frame while animating and also crashes when I make a layer while animating Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: johnenica1...@gmail.com Target Milestone: --- SUMMARY Krita crashes when I create or click a frame while animating and also crashes when I make a layer while animating STEPS TO REPRODUCE 1. Fix 2. Or fix 3. Please fix OBSERVED RESULT It keep crashing EXPECTED RESULT Please fix SOFTWARE/OS VERSIONS Windows: crashing macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 4.3.0 KDE Frameworks Version: 4.3.0 Qt Version: 4.3.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416489] New: First time reporting a bug(s)
https://bugs.kde.org/show_bug.cgi?id=416489 Bug ID: 416489 Summary: First time reporting a bug(s) Product: krita Version: 4.2.7.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: sailorlo...@gmail.com Target Milestone: --- Created attachment 125256 --> https://bugs.kde.org/attachment.cgi?id=125256&action=edit Two Bugs SUMMARY I'd say to get two bugs in one recording in under a minute is pretty impressive! First Bug is a replay issue with the animation play button when two different window files are both playing at once. The other is a visual obscurity, where one layer/frame that shouldn't be visible and isn't visible until I play an animation. (details on Bugs here VVV) https://telegra.ph/Krita-Bug-x2-01-20 SOFTWARE/OS VERSIONS Windows: MS Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356113] Pen Pressure Doesn't Work.
https://bugs.kde.org/show_bug.cgi?id=356113 Rose changed: What|Removed |Added CC||alysfeld...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382258] New: Crashing and No Pen Pressure
https://bugs.kde.org/show_bug.cgi?id=382258 Bug ID: 382258 Summary: Crashing and No Pen Pressure Product: krita Version: 3.1.4 Platform: Other OS: unspecified Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: alysfeld...@gmail.com Target Milestone: --- Created attachment 106569 --> https://bugs.kde.org/attachment.cgi?id=106569&action=edit BugView Report Help! Krita has been crashing whenever I open it or attempt to open new canvases. When it does not crash, the pen pressure does not work. I have tried multiple suggested solutions, such as disabling and enabling OpenGL, uninstalling and reinstalling Krita, restarting my laptop, updating Intel Graphics (which I couldnt get to actually update), and manually activating pen pressure. Nothing works! I use a Wacom Intuos, my laptop is a Dell with Windows 8. Attached is the BugView report of me attempting to draw in a canvas, not having pen pressure, trying different things to fix it, and ultimately- Krita crashing. Please help! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 --- Comment #15 from Rose --- (In reply to Zamundaaa from comment #13) > 6.3.1 is out with that change included; please re-test! Just updated to 6.3.1. Turned Night Light to always on. All seemed well - it looked correct. Slept my PC and upon waking, again, all looked fine. However, when I set it back to my usual "Switching Times: Custom times", I'm again getting the weird pink tinge. It's no where near as obvious pink tinge as it was originally but it is still there. If I switch from "Custom times" to "Always on night light", I again get the correct orange. If I switch back to "Custom times", it goes back to the slight pink tinged parts of apps. I've tried taking a photo but it's difficult to show as my camera is not really picking up the pink tinge very well: https://i.postimg.cc/R0hX1B7t/IMG-20250219-115229-426.jpg It's again, still only affecting non-white areas of the screen and white areas of the screen remain completely unfiltered and look normal white. With "Always on night light", white parts of apps have the orange filter applied appropriately. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 --- Comment #16 from Rose --- Ok, I tried something else and I realise it's not anything to do with "Always on..." vs "Custom times" - it's the colour temperature setting. For my usual day time use, I use 5,700-6,000 kelvins and my night time use is around 3,500-4,000 kelvins - if I use the slider, the closer I get to the day time colour temp, the less orange filter I get, the more the non-white areas start appearing pink and the white areas look plain white. This is noticeable to my vision at around 4,800 kelvins (and higher until about 6,300k at which point it just looks like the night light is off). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 --- Comment #14 from Rose --- (In reply to Rose from comment #7) > I updated my system, this morning, to KDE frameworks 6.11 and this issue has > resolved for me. In case this info is still useful, I still encounter this bug if my system goes to sleep - once woken up, I again experience the pink tinged applications instead of the correct night light orange. This only happens waking from sleep though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 --- Comment #7 from Rose --- I updated my system, this morning, to KDE frameworks 6.11 and this issue has resolved for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] New: HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 Bug ID: 500036 Summary: HDR + Night Light combination results in pink tinge to applications and shadows Classification: Plasma Product: kwin Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: colour-management Assignee: kwin-bugs-n...@kde.org Reporter: thorned.r...@intothegarbagechuteflyboy.net Target Milestone: --- Created attachment 178327 --> https://bugs.kde.org/attachment.cgi?id=178327&action=edit HDR and Nightlight both enabled SUMMARY Having both HDR and Night Light enabled at the same time results in parts of applications being pink tinged (others not) and the Night Light colour is not the warm orange expected, nor does it seem to be 'covering' the whole screen correctly. STEPS TO REPRODUCE 1. Have HDR enabled 2. Turn Night Light on (or automatically scheduled on) OBSERVED RESULT Parts of applications and shadows look pink, the night light filter does not 'cover' the entire screen and is an incorrect shade. EXPECTED RESULT Night Light should look (mostly) the same whether HDR is on or off. SOFTWARE/OS VERSIONS Operating System: CachyOS Linux (Arch based) KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-2-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 33.6 GB of RAM Graphics Processor: AMD Radeon RX 6800 XT Manufacturer: ASUS ADDITIONAL INFORMATION This seems to have only started after updating to Plasma 6.3. - See attached image for what it looks like with both HDR and the Night Light enabled (observed result). - HDR on but Night Light off: https://i.postimg.cc/xd3m8798/HDR-on-Nightlight-Off.jpg - HDR off and Night Light on: https://i.postimg.cc/QxgTxChs/HDR-off-Nightlight-on.jpg Supplied photos are using a phone camera since screenshots do not show the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500036] HDR + Night Light combination results in pink tinge to applications and shadows
https://bugs.kde.org/show_bug.cgi?id=500036 --- Comment #6 from Rose --- (In reply to Real Name Here from comment #5) > I experience this in HDR and SDR while using an ICC profile. The warmer, I > set night light the pinker everything becomes. I just tested this out on a monitor that uses an ICC profile but isn't HDR enabled, and can confirm I get the same behaviour. My usual monitor (that I based this report on and took screenshots) uses a built-in ICC profile (moot when using HDR as that the ICC setting gets disabled when enabling HDR) so I had assumed it was an issue with the combination of Night Light + HDR rather than Night Light + ICC. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 467243] New: Certain ui elements prevent touch scrolling
https://bugs.kde.org/show_bug.cgi?id=467243 Bug ID: 467243 Summary: Certain ui elements prevent touch scrolling Classification: Applications Product: Tokodon Version: 23.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: r...@krx.sh CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When using a touchscreen, swiping vertically does not always scroll the view. Instead some other action is sometimes taken, or nothing happens at all. Affected elements include: - profile bios (where the bio text gets selected) - the text content of a post (where nothing happens), but only in Thread view and not in e.g. Home or Local - the gap between the user info and the text content, or between the text content and the media in a post (where nothing happens) - profile links (where link text gets selected), but not their labels STEPS TO REPRODUCE 1. navigate to a scrollable view where any of those elements is visible 2. put your finger on one of the elements 3. move your finger up or down the screen OBSERVED RESULT see above EXPECTED RESULT the view scrolls SOFTWARE/OS VERSIONS postmarketOS edge Plasma Mobile 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456546] Compose key = Right Alt has no effect when using non-primary keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456546 --- Comment #3 from Rose Hudson --- > Sorry for the delay. You're absolutely right, on X11 we don't handle compose > keys directly, the X server takes care of this. Is xkbcommon responsible in the Wayland session too? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456546] Compose key = Right Alt has no effect when using colemak-dh
https://bugs.kde.org/show_bug.cgi?id=456546 --- Comment #1 from Rose Hudson --- Turns out that moving colemak-dh to the top of the layouts list made the compose key work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456546] Compose key = Right Alt has no effect when using non-primary keyboard layout
https://bugs.kde.org/show_bug.cgi?id=456546 Rose Hudson changed: What|Removed |Added Summary|Compose key = Right Alt has |Compose key = Right Alt has |no effect when using|no effect when using |colemak-dh |non-primary keyboard layout -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 478903] New: Crash a moment after launch
https://bugs.kde.org/show_bug.cgi?id=478903
Bug ID: 478903
Summary: Crash a moment after launch
Classification: Applications
Product: NeoChat
Version: 24.01.85
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: r...@krx.sh
CC: c...@carlschwan.eu
Target Milestone: ---
STEPS TO REPRODUCE
1. Open NeoChat
2. (Optional) Select an account and try to select a room
3. (Alternatively) Wait a bit
(sorry, that's the best I can do)
OBSERVED RESULT
NeoChat crashes
SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0beta1-2
libquotient Version: 0.8.1.2-3
ADDITIONAL INFORMATION
Last message in the log is consistently "quotient.events.members: Mismatched
name in the room members list; avoiding the list corruption".
Backtrace:
#0 0x7f3267df9ef5 in
QExplicitlySharedDataPointer::operator!() const
(this=, this=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/tools/qshareddata.h:197
#1 QJsonObject::valueImpl(QLatin1String) const (key=...,
this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/serialization/qjsonobject.cpp:310
#2 QJsonObject::value(QLatin1String) const (this=0x8, key=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/serialization/qjsonobject.cpp:301
#3 0x7f3269d30f3b in QJsonObject::operator[](QLatin1String) const
(key=..., this=, this=, key=...) at
/usr/include/qt6/QtCore/qjsonobject.h:61
#4 Quotient::RoomEvent::senderId() const (this=) at
/usr/src/debug/libquotient/libQuotient-0.8.1.2/Quotient/events/roomevent.cpp:38
#5 0x5653c476a927 in NeoChatRoom::NeoChatRoom(Quotient::Connection*,
QString, Quotient::JoinState)::{lambda()#2}::operator()() const [clone
.lto_priv.0] () at
/usr/src/debug/neochat/neochat-24.01.85/src/neochatroom.cpp:112
#6 0x7f3267dbeaa9 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffcf50a1738, r=0x5653c76c3720, this=0x5653c631b940, this=,
r=, a=)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qobjectdefs_impl.h:469
#7 doActivate(QObject*, int, void**) (sender=0x5653c76c3720,
signal_index=3, argv=0x7ffcf50a1738) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qobject.cpp:4044
#8 0x7f3269cfdf24 in Quotient::Room::baseStateLoaded()
(this=0x5653c76c3720) at
/usr/src/debug/libquotient/build/QuotientQt6_autogen/include/moc_room.cpp:3119
#9 Quotient::Room::updateData(Quotient::SyncRoomData&&, bool) (this=, data=..., fromCache=false) at
/usr/src/debug/libquotient/libQuotient-0.8.1.2/Quotient/room.cpp:1976
#10 0x7f3267dafc74 in QObject::event(QEvent*) (this=0x5653c76c3720,
e=0x5653c76c25c0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qobject.cpp:1446
#11 0x7f3268f7bf4b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5653c76c3720, e=0x5653c76c25c0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/widgets/kernel/qapplication.cpp:3290
#12 0x7f3267d65488 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5653c76c3720, event=event@entry=0x5653c76c25c0)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qcoreapplication.cpp:1134
#13 0x7f3267d65814 in QCoreApplication::sendEvent(QObject*, QEvent*)
(event=0x5653c76c25c0, receiver=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qcoreapplication.cpp:1575
#14 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
(receiver=0x0, event_type=0, data=0x5653c5c0abd0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qcoreapplication.cpp:1946
#15 0x7f3267fad734 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=0x0, event_type=0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qcoreapplication.cpp:1803
#16 postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5653c5d50b00)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/corelib/kernel/qeventdispatcher_glib.cpp:244
#17 0x7f326570df69 in g_main_dispatch (context=0x7f325c000ef0) at
../glib/glib/gmain.c:3476
#18 0x7f326576c367 in g_main_context_dispatch_unlocked
(context=0x7f325c000ef0) at ../glib/glib/gmain.c:4284
#19 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7f325c000ef0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4349
#20 0x7f326570c162 in g_main_context_iteration (context=0x7f325c000ef0,
may_block=1) at ../glib/glib/gmain.c:4414
#21 0x7f3267fab164 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5653c5cbcfc0, flags=...)
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0-beta1/src/coreli
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 Rose Hudson changed: What|Removed |Added CC||r...@krx.sh -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456546] New: Compose key = Right Alt has no effect when using colemak-dh
https://bugs.kde.org/show_bug.cgi?id=456546 Bug ID: 456546 Summary: Compose key = Right Alt has no effect when using colemak-dh Product: kwin Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: r...@krx.sh Target Milestone: --- *This occurs on both Wayland and X11 Plasma sessions, so maybe the problem lies somewhere upstream.* STEPS TO REPRODUCE 1. Set keyboard layout to English (UK, Colemak-DH) 2. Enable Position of Compose Key -> Right Alt in advanced keyboard settings 3. Try to use the compose key OBSERVED RESULT Right Alt functions as normal, as a modifier to access alternate characters EXPECTED RESULT Right Alt functions as compose key SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Compose key = Right Alt works fine on qwerty. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427759] New: yubioath-desktop no longer installable
https://bugs.kde.org/show_bug.cgi?id=427759 Bug ID: 427759 Summary: yubioath-desktop no longer installable Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: markr...@markrose.ca CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- In Neon User Edition 5.20, the Ubuntu package yubioath-desktop from universe is no longer installable due to broken dependencies. $ apt-cache policy yubioath-desktop yubioath-desktop: Installed: (none) Candidate: 5.0.3-1 Version table: 5.0.3-1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages $ sudo apt-get install yubioath-desktop Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) yubioath-desktop:amd64 < none -> 5.0.3-1 @un puN Ib > Broken yubioath-desktop:amd64 Depends on qml-module-io-thp-pyotherside:amd64 < none | 1.5.9-1build1 @un uH > Considering qml-module-io-thp-pyotherside:amd64 1 as a solution to yubioath-desktop:amd64 Reinst Failed early because of qtdeclarative-abi-5-12-8:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help resolve the situation: The following packages have unmet dependencies: yubioath-desktop : Depends: qml-module-io-thp-pyotherside but it is not going to be installed E: Unable to correct problems, you have held broken packages -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427759] yubioath-desktop no longer installable
https://bugs.kde.org/show_bug.cgi?id=427759 Mark Rose changed: What|Removed |Added CC||markr...@markrose.ca -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 475085] New: Meta should always be mod1
https://bugs.kde.org/show_bug.cgi?id=475085 Bug ID: 475085 Summary: Meta should always be mod1 Classification: Frameworks and Libraries Product: frameworks-kconfig Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: kr...@krose.org CC: kdelibs-b...@kde.org Target Milestone: --- When using advanced keyboard options that move meta around (such as "Meta is mapped to Win"), compatibility with applications that don't use xkb virtual modifiers requires that meta always be mod1, as legacy applications (such as emacs) assume mod1 is meta. STEPS TO REPRODUCE 1. Turn on "Meta is mapped to Win" 2. `xmodmap -pm` OBSERVED RESULT mod1 lists Alt keys and mod4 lists Meta keys. EXPECTED RESULT It should be the other way around (or, at the very least, mod1 should not include any keys mapped to virtual modifiers other than `Meta`). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.5 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 475085] Meta should always be mod1
https://bugs.kde.org/show_bug.cgi?id=475085 --- Comment #1 from Kyle Rose --- I will add that there should be an advanced option in keyboard settings that allows the user to bring their own xkbcomp file that Plasma then just loads at the appropriate time. I don't really want to use Plasma's mechanism for configuring key mappings, but I'm forced to because the alternative is jumping through these hoops: 1. Disable the Keyboard Daemon in Settings/Startup and Shutdown/Background Services 2. Set up an Autostart script that runs xkbcomp with my preferred mapping 3. After loading the new mapping, `systemctl --user reload-or-restart plasma-kwin_x11.service` because kwin needs to be restarted to use the new mapping It would be easier to just point Plasma at a fully-formed xkbcomp file and let it load it at the right time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476834] New: Panel popups are xdg-toplevels, positioned wrongly on Sway
https://bugs.kde.org/show_bug.cgi?id=476834 Bug ID: 476834 Summary: Panel popups are xdg-toplevels, positioned wrongly on Sway Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: r...@krx.sh CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Plasma panels seem to get positioned correctly in Sway, but clicking on e.g. the speaker opens an audio popup that gets positioned as if it were a normal window - tiled, not adjacent to the panel. With WAYLAND_DEBUG=1, it seems that such popups are being created as xdg-toplevels while an xdg-popup parented to the panel with zwlr_layer_surface_v1::get_popup might be more appropriate and allow them to be positioned as they are under kwin. STEPS TO REPRODUCE 1. Open Sway 2. Run plasmashell 3. Click on any of the system tray icons OBSERVED RESULT The popup gets tiled as if it were a normal window EXPECTED RESULT The popup appears next to its icon on the panel SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with kde-unstable (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475739] New: Plasma crashes after changing audio profile in pavucontrol
https://bugs.kde.org/show_bug.cgi?id=475739 Bug ID: 475739 Summary: Plasma crashes after changing audio profile in pavucontrol Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kr...@krose.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: This seems to happen once per boot/wake from hibernate or suspend: the first time I change audio profile for my motherboard audio device, Plasma crashes, (presumably) taking Firefox with it. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 271916 (plasmashell) UID: 1000 (krose) GID: 1000 (krose) Signal: 11 (SEGV) Timestamp: Tue 2023-10-17 10:03:43 EDT (24s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (krose) Boot ID: d668527e945240e3a440266866cc88a0 Machine ID: 664a7982d2ac41c29342ce753ce1d617 Hostname: nausicaa Storage: /var/lib/systemd/coredump/core.plasmashell.1000.d668527e945240e3a440266866cc88a0.271916.169755142300.zst (present) Size on Disk: 133.3M Message: Process 271916 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 271916: #0 0x7f1ef38a9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #1 0x7f1ef385af32 __GI_raise (libc.so.6 + 0x3bf32) #2 0x7f1ef6279b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f1ef385afd0 __restore_rt (libc.so.6 + 0x3bfd0) #4 0x7f1ef38a9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #5 0x7f1ef385af32 __GI_raise (libc.so.6 + 0x3bf32) #6 0x7f1ef385afd0 __restore_rt (libc.so.6 + 0x3bfd0) #7 0x7f1ef38a4da4 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da4) #8 0x7f1ef38a7468 __pthread_cond_wait_common (libc.so.6 + 0x88468) #9 0x7f1ef3ed1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #10 0x7f1ef5e0bd58 n/a (libQt5Quick.so.5 + 0x20bd58) #11 0x7f1ef5e0d013 n/a (libQt5Quick.so.5 + 0x20d013) #12 0x7f1ef45493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1493f5) #13 0x7f1ef4f62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #14 0x7f1ef40b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #15 0x7f1ef453e5cd _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e5cd) #16 0x7f1ef4511cac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111cac) #17 0x7f1eeeafbeca n/a (libQt5XcbQpa.so.5 + 0x6deca) #18 0x7f1ef2a571b4 n/a (libglib-2.0.so.0 + 0x571b4) #19 0x7f1ef2a5a2d7 n/a (libglib-2.0.so.0 + 0x5a2d7) #20 0x7f1ef2a5a8f0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a8f0) #21 0x7f1ef4109836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f1ef40b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7f1ef40b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x56107c5bedc3 n/a (plasmashell + 0x26dc3) #25 0x7f1ef38461ca __libc_start_call_main (libc.so.6 + 0x271ca) #26 0x7f1ef3846285 __libc_start_main_impl (libc.so.6 + 0x27285) #27 0x56107c5beee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 271969: #0 0x7f1ef391b05f __GI___poll
[kwin] [Bug 466031] Per-virtual-desktop tiling layouts
https://bugs.kde.org/show_bug.cgi?id=466031 Rose Hudson changed: What|Removed |Added CC|r...@krx.sh | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399440] RTL aligned text and Hebrew text when application language is English
https://bugs.kde.org/show_bug.cgi?id=399440 Shmuel Rose changed: What|Removed |Added CC||shmuel...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422651] New: Bad paragraph spacing
https://bugs.kde.org/show_bug.cgi?id=422651 Bug ID: 422651 Summary: Bad paragraph spacing Product: kmail2 Version: 5.14.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ppnmmw9zj...@absolutesix.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create an email with an HTML signature 2. Type some text 2. Hit the Enter Key twice to create a new paragraph 3. Type more text OBSERVED RESULT When the email is sent or saved the double line breaks are converted to this: SOME TEXT MORE TEXT The added " " creates huge whitespaces between each paragraph. EXPECTED RESULT A normal sized empty line between each paragraph. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void Linux & Manjaro with KDE Plasma (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This behavior is the same in both Void Linux and Manjaro. Kmail 5.13.x does not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422982] New: Segfault in KisNodeProgressProxy::setRange
https://bugs.kde.org/show_bug.cgi?id=422982 Bug ID: 422982 Summary: Segfault in KisNodeProgressProxy::setRange Product: krita Version: 4.2.8 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: norna...@nornagon.net Target Milestone: --- Created attachment 129359 --> https://bugs.kde.org/attachment.cgi?id=129359&action=edit Full crash report SUMMARY Program crashed while painting. STEPS TO REPRODUCE I can't reproduce this, but in case one of these seems relevant: I was messing with filter layers on a clone layer, outline selection and clearing (w/ Delete), while undoing. SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION Here's the stack trace (the full crash report is attached): Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libkritaimage.18.dylib 0x00010ff43a3a KisNodeProgressProxy::setRange(int, int) + 42 1 libkritawidgetutils.18.dylib0x0001109310e8 KoProgressUpdater::updateUi() + 712 2 org.qt-project.QtCore 0x00011213ef55 QMetaObject::activate(QObject*, int, int, void**) + 1765 3 org.qt-project.QtCore 0x000112146bf2 QTimer::timerEvent(QTimerEvent*) + 98 4 org.qt-project.QtCore 0x000112137e78 QObject::event(QEvent*) + 104 5 org.qt-project.QtWidgets0x000110f2c110 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272 6 org.qt-project.QtWidgets0x000110f2d4c5 QApplication::notify(QObject*, QEvent*) + 581 7 libkritaui.18.dylib 0x00010ecc9ada KisApplication::notify(QObject*, QEvent*) + 26 8 org.qt-project.QtCore 0x00011210f384 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 9 org.qt-project.QtCore 0x000112166bf2 QTimerInfoList::activateTimers() + 930 10 libqcocoa.dylib 0x00011496b062 0x114937000 + 213090 11 com.apple.CoreFoundation0x7fff4253bd17 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 12 com.apple.CoreFoundation0x7fff4253bcbd __CFRunLoopDoSource0 + 108 13 com.apple.CoreFoundation0x7fff4251f6d3 __CFRunLoopDoSources0 + 283 14 com.apple.CoreFoundation0x7fff4251ec45 __CFRunLoopRun + 1189 15 com.apple.CoreFoundation0x7fff4251e54e CFRunLoopRunSpecific + 455 16 com.apple.HIToolbox 0x7fff4177d1ab RunCurrentEventLoopInMode + 292 17 com.apple.HIToolbox 0x7fff4177cded ReceiveNextEventCommon + 355 18 com.apple.HIToolbox 0x7fff4177cc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64 19 com.apple.AppKit0x7fff3fb1477d _DPSNextEvent + 1135 20 com.apple.AppKit0x7fff3fb1346b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361 21 com.apple.AppKit0x7fff3fb0d588 -[NSApplication run] + 699 22 libqcocoa.dylib 0x00011496be68 0x114937000 + 216680 23 org.qt-project.QtCore 0x00011210aacf QEventLoop::exec(QFlags) + 431 24 org.qt-project.QtCore 0x00011210f9d2 QCoreApplication::exec() + 130 25 org.krita 0x00010d9924e6 main + 10806 26 libdyld.dylib 0x7fff6e4873d5 start + 1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422982] Segfault in KisNodeProgressProxy::setRange
https://bugs.kde.org/show_bug.cgi?id=422982 --- Comment #2 from Jeremy Rose --- Fantastic, thanks! Sorry for the noise, I searched for the top of the stack trace and didn't find anything. Glad to hear it's fixed :) On Sun, Jun 14, 2020 at 10:33 AM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=422982 > > Boudewijn Rempt changed: > >What|Removed |Added > > > CC||b...@valdyas.org > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > > --- Comment #1 from Boudewijn Rempt --- > Ah, this was fixed for 4.3.0 -- second beta now available, final release > this > week. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423204] New: Crash in KoShape::parent
https://bugs.kde.org/show_bug.cgi?id=423204 Bug ID: 423204 Summary: Crash in KoShape::parent Product: krita Version: 4.2.8 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: norna...@nornagon.net Target Milestone: --- Created attachment 129509 --> https://bugs.kde.org/attachment.cgi?id=129509&action=edit Full crash report SUMMARY Null dereference in KoShape::parent STEPS TO REPRODUCE I don't have reliable repro steps, but this happened when I toggled a layer to be invisible. OBSERVED RESULT Crash with SIGSEGV at address 0x0090 Truncated stack trace (full report attached): Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libkritaflake.18.dylib 0x00011166b598 KoShape::parent() const + 8 1 libkritaui.18.dylib 0x00010fc3dbae KisNodeShape::editabilityChanged() + 478 2 org.qt-project.QtCore 0x000113383112 QObject::event(QEvent*) + 770 3 org.qt-project.QtWidgets0x00011217c110 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272 4 org.qt-project.QtWidgets0x00011217d4c5 QApplication::notify(QObject*, QEvent*) + 581 5 libkritaui.18.dylib 0x00010ff18ada KisApplication::notify(QObject*, QEvent*) + 26 SOFTWARE/OS VERSIONS macOS: 10.14.6 -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 494696] Importing return tickets from Deutsche Bahn only imports ride back
https://bugs.kde.org/show_bug.cgi?id=494696 Rose Reed changed: What|Removed |Added CC||kde-b...@devrose.de -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 494696] New: Importing return tickets from Deutsche Bahn only imports ride back
https://bugs.kde.org/show_bug.cgi?id=494696
Bug ID: 494696
Summary: Importing return tickets from Deutsche Bahn only
imports ride back
Classification: Applications
Product: KDE Itinerary
Version: unspecified
Platform: Arch Linux
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: vkra...@kde.org
Reporter: kde-b...@devrose.de
Target Milestone: ---
When adding a return ticket ("there & back") via the "Import" -> "Deutsche Bahn
Online Ticket" option, only the trip back is being imported into Itinerary,
with no way to import the first trip there. In my case I tried to import a
ticket I had booked a trip on October 18 with a return trip on October 19. Only
the trip back on October 19 was imported into Itinerary.
STEPS TO REPRODUCE
1. Obtain an order number and last name of a return ticket booked with Deutsche
Bahn
2. Import the return ticket via the "Deutsche Bahn Online Ticket" import option
OBSERVED RESULT
Only the trip back gets imported and shown in Itinerary.
EXPECTED RESULT
Both the leaving and return trip are being imported and shown in Itinerary.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Itinerary Version: 24.08.2
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Android 14:
Fairphone 5 5G
KDE Itinerary Version 24.08.2
KDE Frameworks Version: 6.6.0
The android windowing system
Qt Version: 6.7.2
--
You are receiving this mail because:
You are watching all bug changes.
[kio-gdrive] [Bug 486576] Cannot log into Google account with two factor authentication enabled
https://bugs.kde.org/show_bug.cgi?id=486576 Rose Reed changed: What|Removed |Added CC||kde-b...@devrose.de --- Comment #8 from Rose Reed --- I have the same issue when trying to log in. I could imagine it could be having to do with the UserAgent and the limited features in the WebView login window. Is there any way to get the login token to try and complete the process in Firefox or Chrome, or could the login open in the users default browser instead of its own window? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 475085] Meta should always be mod1
https://bugs.kde.org/show_bug.cgi?id=475085 --- Comment #3 from Kyle Rose --- Coincidental that this got updated today, because I learned just a few hours ago that I am 100% wrong about alt and meta. Historically, alt was always mapped to Mod1, and meta was implementation-dependent. So this should be closed wontfix. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 475085] Meta should always be mod1
https://bugs.kde.org/show_bug.cgi?id=475085 Kyle Rose changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364308] Strange behaviour with one rotated monitor on multimonitor configuration
https://bugs.kde.org/show_bug.cgi?id=364308 Vik-Thor Rose changed: What|Removed |Added CC||catt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 124052] 'New Object Layer' function not working
https://bugs.kde.org/show_bug.cgi?id=124052 Carly Rose Streker changed: What|Removed |Added CC||broken_and_str...@aol.com --- Comment #2 from Carly Rose Streker --- It will not let me open a layer or anything? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 124052] 'New Object Layer' function not working
https://bugs.kde.org/show_bug.cgi?id=124052 --- Comment #4 from Carly Rose Streker --- I fixed the bug and I sent that yesterday so your just fine. Sent from my iPhone > On Oct 30, 2017, at 3:21 AM, Boudewijn Rempt wrote: > > https://bugs.kde.org/show_bug.cgi?id=124052 > > --- Comment #3 from Boudewijn Rempt --- > Hi Carly, > > You're replying to a bug report from 2006 -- eleven years ago. If you have a > question or need help, it's better to post on the forum than here, where it's > only by accident that I saw your comment... https://forum.kde.org/krita > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 496665] New: Animation curves: transformation mask keeps adding keyframes
https://bugs.kde.org/show_bug.cgi?id=496665 Bug ID: 496665 Summary: Animation curves: transformation mask keeps adding keyframes Classification: Applications Product: krita Version: 5.2.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: rosetta.j...@gmail.com Target Milestone: --- Created attachment 176101 --> https://bugs.kde.org/attachment.cgi?id=176101&action=edit report for the crash mentioned in my forum post SUMMARY hello! im trying to do some simple tweening using the animation curves docker, and i use very few keyframes for this. however a few different operations (crop, scale image) make it so that a new keyframe has been added in between the ones i made myself, on every single frame. (note: this is my first time making a bug report, so apologies for any mistakes). STEPS TO REPRODUCE: CROP 1. On a new file, create a new layer and draw a dot with any brush. 2. On the animation timeline, add a blank frame on frame 0 and frame 21 for the dot layer. 3. Add a transformation mask to the dot layer. Pin both layers to the timeline for ease. 4. In the animation curves docker, create new keyframes for the transformation mask on frame 0 and frame 20. 5. Change the value of the keyframe on frame 20 to val:150.00. When the animation is played, the dot should move from left to right until frame 20 where it disappears. 6. Save the file. 7. Crop the image. 8. Undo the crop. OBSERVED RESULT As soon as the image is cropped, new keyframes are added on every frame between frame 0 and frame 20 (on the transformation mask). The new keyframes are on every single property, not just Position (X). They match the values each frame had before the crop, that is, if i had manually added keyframes on each frame by clicking "add keyframe", it would have looked like this as well. Undoing the crop does not remove the additional keyframes. EXPECTED RESULT No new keyframes should be added after cropping. STEPS TO REPRODUCE: SCALE IMAGE 1. Use the saved version of the file from the previous example (or repeat steps 1-5). 2. Image -> Scale Image To New Size. 3. Undo the scaling. OBSERVED RESULT Same issue as with cropping, though undoing the scaling also undoes the changes on the keyframes. EXPECTED RESULT No new keyframes should be added after scaling the image. these are the bugs that prompted me filing this report. however, i also tested a few more functions from the image tab, and found even more bugs. ive listed them here: https://krita-artists.org/t/animation-curves-transformation-mask-keeps-adding-keyframes/107860/ -- You are receiving this mail because: You are watching all bug changes.
