[plasmashell] [Bug 458916] Manage Panels and Workspaces resets changes after the window is closed
https://bugs.kde.org/show_bug.cgi?id=458916 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #14 from Nate Graham --- That's a different issue. Can you please try to keep this bug report on topic to the original issue? Are you able to reproduce the original issue in Plasma 5.27, on the upcoming Debian version? If you have other issues, please submit new bug reports for them. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 466888] Violation of KDE Software Privacy Policy
https://bugs.kde.org/show_bug.cgi?id=466888 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- In this context, the word "collect" is clearly referring to the transmission of data to KDE, not its local storage. For example see this sentence: > We collect personal information in order to provide you with services on our > websites. If "collect" is a synonym for "locally store", then the sentence could be re-worded like so: > "We locally store personal information in order to provide you with services > on our websites. Which is clearly nonsensical in its proper context. That leaves the issue of locally stored data that was locally stored prior to telemetry being turned on sent to KDE when telemetry is turned on. because telemetry is off by default, turning it on is clearly an "explicit user action" so I am failing to see the violation of the policy. Can you clarify? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747 --- Comment #15 from S. Christian Collins --- I just tested and the bug still happens on my laptop and in Virtualbox as described in comments #6 and #9. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448833] Overlapping entries when filtering and deleting and filtering again several times
https://bugs.kde.org/show_bug.cgi?id=448833 Patrick Silva changed: What|Removed |Added CC||rokejulianlockhart@outlook. ||com --- Comment #13 from Patrick Silva --- *** Bug 466921 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466921] Garbled text when searching in history.
https://bugs.kde.org/show_bug.cgi?id=466921 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 448833 *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 465584] Default logout screen option missing
https://bugs.kde.org/show_bug.cgi?id=465584 --- Comment #6 from David --- (In reply to Nate Graham from comment #3) > Indeed, there is no "shut down" menu item available in the desktop context > menu. > > Nonetheless, this was an intentional change as it was considered a super > nerdy esoteric feature that confused users. What confuses me is the process that I need to follow now, since now I need to set up a widget that I don't click, assign the shortcut Ctrl+Alt+Del to that widget, remove the global shortcut in the settings, configure the widget, and place it somewhere where I don't accidentally click it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #34 from Miren Radia --- I should have added that it happens for me sometimes when I move windows between my 2 monitors (1x 2256x1504 laptop screen + 1x 3840x2160 external monitor both at 100% scaling) *after* they have been quick-tiled (e.g. to the right of the screen). However, it definitely isn't consistent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #9 from Eric R --- (In reply to Nate Graham from comment #8) > Can you confirm that the items are still there after you restart the > computer? Yes. Just to make sure, I just rebooted now, and the same three items are there. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 466912] Breeze dark folder icon turns to almost-noise under dark themes
https://bugs.kde.org/show_bug.cgi?id=466912 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 448169 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 448169] Contrast for Breeze Dark's Places icons with light foreground clashes
https://bugs.kde.org/show_bug.cgi?id=448169 Nate Graham changed: What|Removed |Added CC||david.cortes.rivera@gmail.c ||om --- Comment #3 from Nate Graham --- *** Bug 466912 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466679] Discover can't handle UEFI Secure Boot firmware updates
https://bugs.kde.org/show_bug.cgi?id=466679 Nate Graham changed: What|Removed |Added Severity|normal |major Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login
https://bugs.kde.org/show_bug.cgi?id=465747
--- Comment #14 from S. Christian Collins ---
Created attachment 157048
--> https://bugs.kde.org/attachment.cgi?id=157048=edit
plasma configuration file-working now
Over the past few days, the issue of the icons moving to my secondary monitor
on has fixed itself on my desktop PC. I couldn't tell you why. Anyway, attached
is my plasma configuration file for that system in case it provides any clues.
Using Kompare between the first attachment ("plasma configuration file") and
this one shows differences, but TBH I don't understand what is going on. I'll
test on my other affected systems to see if it still happens there.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 465790] Resizing an Aurorae-decorated window leads to malformed decorations
https://bugs.kde.org/show_bug.cgi?id=465790 --- Comment #33 from Nate Graham --- Still cannot reproduce with either single or multi-screen arrangements with any Aurorae theme, or when moving windows between screens or disconnecting one of them. :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460664] When waking up from stanby under Wayland, many graphical elements seem corrupted
https://bugs.kde.org/show_bug.cgi?id=460664 Nate Graham changed: What|Removed |Added Status|VERIFIED|RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #4 from Nate Graham --- Then it's a different issue. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466944] kded5 crashed upon waking up
https://bugs.kde.org/show_bug.cgi?id=466944
Nicolas Fella changed:
What|Removed |Added
CC||nicolas.fe...@gmx.de
--- Comment #2 from Nicolas Fella ---
Thread 23 (Thread 0x7fd0542926c0 (LWP 19564)):
#0 0x7fd06472221f in __GI___poll (fds=0x7fd04c04a860, nfds=4, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = 4
sc_cancel_oldtype = 0
#1 0x7fd063cba08d in g_main_context_poll (priority=,
n_fds=4, fds=0x7fd04c04a860, timeout=, context=0x7fd04c001cf0)
at ../glib/gmain.c:4553
ret =
errsv =
poll_func = 0x7fd063c692c0
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 4
allocated_nfds =
fds = 0x7fd04c04a860
begin_time_nsec = 17234957124149
#2 g_main_context_iterate.constprop.0 (context=0x7fd04c001cf0, block=1,
dispatch=1, self=) at ../glib/gmain.c:4243
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 4
allocated_nfds =
fds = 0x7fd04c04a860
begin_time_nsec = 17234957124149
#3 0x7fd063c60f00 in g_main_context_iteration (context=0x7fd04c001cf0,
may_block=1) at ../glib/gmain.c:4313
retval =
#4 0x7fd064eee5fa in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd04c000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:423
d = 0x7fd04c000b90
canWait = true
savedFlags = {
i = 0
}
result =
#5 0x7fd064e9bf3a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd054291d20, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
d = 0x7fd04c001890
threadData =
locker = {
val = 94028014053096
}
ref = {
d = 0x7fd04c001890,
locker = @0x7fd054291c98,
exceptionCaught = true
}
app = 0x7ffc48019270
#6 0x7fd064ce719a in QThread::exec() (this=this@entry=0x7fd065a5f060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
d = 0x55849a606690
locker = {
val = 94028014053096
}
eventLoop = {
= {
_vptr.QObject = 0x7fd06515db68 ,
static staticMetaObject = {
d = {
superdata = {
direct = 0x0
},
stringdata = 0x7fd0650518c0 ,
data = 0x7fd0650517a0 ,
static_metacall = 0x7fd064ece330
,
relatedMetaObjects = 0x0,
extradata = 0x0
}
},
d_ptr = {
d = 0x7fd04c001890
},
static staticQtMetaObject = {
d = {
superdata = {
direct = 0x0
},
stringdata = 0x7fd065054860 ,
data = 0x7fd0650519e0 ,
static_metacall = 0x0,
relatedMetaObjects = 0x0,
extradata = 0x0
}
}
},
members of QEventLoop:
static staticMetaObject = {
d = {
superdata = {
direct = 0x7fd0651553e0
},
stringdata = 0x7fd06504b660 ,
data = 0x7fd06504b600 ,
static_metacall = 0x7fd064e9bb70
,
relatedMetaObjects = 0x0,
extradata = 0x0
}
}
}
returnCode =
#7 0x7fd0659e5b1b in QDBusConnectionManager::run() (this=0x7fd065a5f060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:179
#8 0x7fd064ce84c7 in QThreadPrivate::start(void*) (arg=0x7fd065a5f060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:330
thr = 0x7fd065a5f060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>
data = 0x55849a5ffcc0
__clframe = {
__cancel_routine = 0x7fd064ce78e0 ,
__cancel_arg = 0x7fd065a5f060 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>,
__do_it = 1,
__cancel_type =
}
#9 0x7fd0646ae12d in start_thread (arg=) at
pthread_create.c:442
ret =
pd =
unwind_buf = {
cancel_jmp_buf = {{
jmp_buf = {140532741908160, 8150372205633887095, -256, 2,
140721516546640, 140532733517824, -8161833122996528265, -8161867764012917897},
mask_was_saved = 0
}},
priv = {
pad = {0x0, 0x0, 0x0, 0x0},
data = {
prev = 0x0,
cleanup = 0x0,
canceltype = 0
}
}
}
not_first_call =
#10
[krita] [Bug 466287] Timers cannot have negative intervals crash on startup
https://bugs.kde.org/show_bug.cgi?id=466287 --- Comment #10 from amyspark --- I know. There's a macro that Qt exposes when the bearer management isn't built and that we can use. PyQt5, for some reason, has never made use of it so that's why it needs extra work, otherwise it'll build everything and fail at SIP binding creation. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 466950] New: Mount Control display
https://bugs.kde.org/show_bug.cgi?id=466950 Bug ID: 466950 Summary: Mount Control display Classification: Applications Product: kstars Version: 3.6.3 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jcjes...@free.fr Target Milestone: --- Created attachment 157047 --> https://bugs.kde.org/attachment.cgi?id=157047=edit Mount control SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Mount Control in the planetarium window 2. You see many description errors 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466947] Incorrect File being copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=466947 arcane...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from arcane...@gmail.com --- Upgrading to 5.27.1 Fixed this. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 466949] New: LaTeX font rendering looks always blurry
https://bugs.kde.org/show_bug.cgi?id=466949 Bug ID: 466949 Summary: LaTeX font rendering looks always blurry Classification: Applications Product: LabPlot2 Version: latest Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: dirk.nieme...@siemens.com Target Milestone: --- Created attachment 157046 --> https://bugs.kde.org/attachment.cgi?id=157046=edit lml used for showing the result of LaTeX rendering SUMMARY *** Please open attached project. The project title and the y axis title are set in \LaTeX. The result looks blurry, no matter what I do. STEPS TO REPRODUCE 1. Open attached lml file. 2. Compare the y axis title and the plot title with the x axis title. OBSERVED RESULT All \LaTeX rendered labels are blurred. EXPECTED RESULT I didn't expect too much but the rendered label are pretty much blurry. Workaround: If possible use standard text + symbols from standard fonts. SOFTWARE/OS VERSIONS Windows: 10 20H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Graphics Card Nvidia RTX 2000, serving 2x 4K monitors -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466610] Kalendar crashes randomly while in background
https://bugs.kde.org/show_bug.cgi?id=466610 satya changed: What|Removed |Added CC||satya123.s...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438511] Dolphin group separator lines don't span entire view
https://bugs.kde.org/show_bug.cgi?id=438511 Alexander changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Alexander --- looks good now -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 465590] Audio Volume Device name text extends outside of widget on hover if it's too long
https://bugs.kde.org/show_bug.cgi?id=465590 --- Comment #6 from Nate Graham --- Yeah scrolling faded text is generally considered horrible and hated by everyone, so I don't think we'll be going down that route. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #26 from Nate Graham --- Allexus J, can you still reproduce this issue in Plasma 5.27.2 or later? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #25 from Nate Graham --- Oh oops, I missed that you weren't the original reporter of the issue. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466948] New: [Request] virtual keyboard on regular laptop
https://bugs.kde.org/show_bug.cgi?id=466948 Bug ID: 466948 Summary: [Request] virtual keyboard on regular laptop Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alexander.reim...@pm.me Target Milestone: --- I have installed Maliit keyboard and enabled it under the virtual keyboard settings. It currently seems only possible to use the virtual keyboard with touch devices. I have searched the web countless times and never found a way to show the virtual keyboard on a regular laptop. A hotkey/widget to show/hide the virtual keyboard while a physical keyboard is present would be a huge plus. This seems like a big oversight in terms of accessibility. Use cases: - typing on a laptop with damaged keyboard (a friend does this on windows) - typing in a language with different script (I need it to type Russian) - probably more that I'm not familiar with Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx Memory: 15.3 GiB of RAM Graphics Processor: AMD Radeon Vega 3 / 10 Graphics Manufacturer: LENOVO Product Name: 20KUCTO1WW System Version: ThinkPad E485 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 465584] Default logout screen option missing
https://bugs.kde.org/show_bug.cgi?id=465584 Paul Worrall changed: What|Removed |Added CC||david.cortes.rivera@gmail.c ||om --- Comment #5 from Paul Worrall --- *** Bug 466911 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466911] Default logout option setting disappeared after update
https://bugs.kde.org/show_bug.cgi?id=466911 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Paul Worrall --- *** This bug has been marked as a duplicate of bug 465584 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 --- Comment #4 from Nate Graham --- Do you have some JetBrains app running that's constantly querying the clipboard or something? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466947] Incorrect File being copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=466947 --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! Please note that Plasma 5.26.4 will not be supported for much longer by KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to the latest version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Product|kwin|KScreen Flags|Wayland-, X11+ | Status|NEEDSINFO |REPORTED Component|multi-screen|common Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org --- Comment #7 from Nate Graham --- Thanks. Output: 68 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown This should say "enabled connected priority 1"; moving to KScreen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation a second time, the secondary screen is set as the primary screen
https://bugs.kde.org/show_bug.cgi?id=466342 Nate Graham changed: What|Removed |Added Product|kwin|KScreen Component|multi-screen|common Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #10 from Nate Graham --- Thanks. Looks like the Priority values of the eDP-1 and HDMI-A-1 screen are getting reversed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466947] New: Incorrect File being copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=466947 Bug ID: 466947 Summary: Incorrect File being copied to clipboard Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: arcane...@gmail.com Target Milestone: 1.0 SUMMARY Clipboard is copying the wrong files. For instance copying a pdf might add a previously copied jpg file to the clipboard. The wrong file appears in the clipboard manager. Text continues to work as expected. STEPS TO REPRODUCE 1. Copy a *file* via UI e.g. pdf jpg etc. 2. Paste it elsewhere e.g. desktop 3. Copy a different Item - Clipboard manager shows previous file 4. Paste it else where - Previous file pasted 5. Clear clipboard manager 6. Copy a new file - Initial File added to Clipboard (same as 3) OBSERVED RESULT Copies an item not selected to the clipboard EXPECTED RESULT copy the selected item to the clipboard SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 36 - X11 Session KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION First copy paste of the session works as expected if 'remember history' is turned off. `cp` works as expected. `xclip` works as expected. Drag-drop works sometimes but I can't pin point the logic behind whether it will work or not. Clearing the clipboard and copying clip - paste moves the wrong file A maximum of two files are added to the clipboard. Restarting does not fix anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #8 from Nate Graham --- Can you confirm that the items are still there after you restart the computer? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465712] After upgrade to 5.27, periodic visual glitches when monitors' refresh rates don't match
https://bugs.kde.org/show_bug.cgi?id=465712 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466238 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=465712 --- Comment #12 from Nate Graham --- (In reply to Rune from comment #7) > I have to add: the HDMI monitor (secondary) has a different refresh rate > (66Hz) than the primary one (60Hz). Hmm, maybe it's Bug 465712? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466589] With large clipboard history, plasmashell memory usage grows rapidly and consumes all available RAM
https://bugs.kde.org/show_bug.cgi?id=466589 --- Comment #13 from Pawel --- I have been running the Wayland session with https://invent.kde.org/qt/qt/qtwayland/-/merge_requests/68 applied and I can no longer reproduce this bug using the original clipboard settings. Plasma memory usage is sitting at ~325 MiB. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 Halla Rempt changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/486d154af ||cd754fd72290e4a7f5262a2ea6a ||4477 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Halla Rempt --- Git commit 486d154afcd754fd72290e4a7f5262a2ea6a4477 by Halla Rempt. Committed on 06/03/2023 at 15:19. Pushed by rempt into branch 'master'. Show two decimal places in the vector object tool docker After discussion in the meeting, it was decided that this is fine. M +6-1 plugins/tools/defaulttool/defaulttool/DefaultToolGeometryWidget.cpp https://invent.kde.org/graphics/krita/commit/486d154afcd754fd72290e4a7f5262a2ea6a4477 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 466929] Fuzzy clock does not have an option to change the day the week starts
https://bugs.kde.org/show_bug.cgi?id=466929 Paul Worrall changed: What|Removed |Added Ever confirmed|0 |1 Target Milestone|1.0 |--- Component|general |fuzzy-clock Product|plasmashell |kdeplasma-addons CC||p.r.worr...@gmail.com Status|REPORTED|CONFIRMED Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466946] New: Wish: Keep the "Update All" button available when viewing More Information...
https://bugs.kde.org/show_bug.cgi?id=466946 Bug ID: 466946 Summary: Wish: Keep the "Update All" button available when viewing More Information... Classification: Applications Product: Discover Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: p.r.worr...@gmail.com CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Select a System upgrade on the Updates page 2. Click "More Information..." OBSERVED RESULT After looking at the additional information, I have to go back to the System upgrade page to apply the updates. DESIRED RESULT If possible it would be nice to be able to select "Update All" from the "More Information" page -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 466945] New: Automatic selection of decimal separator doesn't work for pasted data
https://bugs.kde.org/show_bug.cgi?id=466945 Bug ID: 466945 Summary: Automatic selection of decimal separator doesn't work for pasted data Classification: Applications Product: LabPlot2 Version: latest Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: dirk.nieme...@siemens.com Target Milestone: --- Created attachment 157045 --> https://bugs.kde.org/attachment.cgi?id=157045=edit Text for clipboard SUMMARY *** The automatic detection of the decimal separator doesn't work in my use cases. STEPS TO REPRODUCE With a clean installation (nightly build 126) without any changes to the configuration: 1. Open the attached file in a text editor (the data comes from copy & paste from a 3rd party tool. Mark the entire content, copy to clipboard. 2. Run Labplot, create a spreadsheet in Project. 3. CTRL-V the data into the table. OBSERVED RESULT The columns are detected as "Text". If you try to change the type of a col (or both) to "Float" the content is deleted: Changing back the type to "Text" doesn't bring back the values, they are truely deleted. Workaround: Settings / Configure Labplot - set Decimal separator manually to the one used in the clipboard (or file) content. In this case switch between formats "Text" and "Float" will not delete the rows. EXPECTED RESULT Automatic recognition of "." (dot) as decimal separator. No deletion of values when switching between (invalid?) formats. SOFTWARE/OS VERSIONS Windows: 10 20H2 (yes, 20!) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Dead keys are not recognized [accute and grave accents (ú, ù), circumflex (û), diaeresis (ü)]
https://bugs.kde.org/show_bug.cgi?id=410876 --- Comment #13 from Kévin GASPARD DE RENEFORT --- Sorry but I have more to tell about this: - First this bug seems very specific to KTouch, because this doesn't happen outside it but only in the courses: I can type «î» / «Î» without any problem in Firefox while commenting here, or in Mousepad or Discord as well. - Then, if it help I can record a video of this bug and gives the link here. - Finally if you need someone to test anything regarding this very annoying bug, I'll be very glad to help ! -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466707] About this System: "Show More Information" button in System Settings representation doesn't actually show more information when clicked
https://bugs.kde.org/show_bug.cgi?id=466707 --- Comment #5 from Nate Graham --- You're welcome! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466674] Wayland: various apps crash in DpmsManager::addScreen() when display enters sleep
https://bugs.kde.org/show_bug.cgi?id=466674 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/libkscreen/commit/e1f3cb ||774435d11e8f68192eee17decdc ||6e2b661 --- Comment #10 from Aleix Pol --- Git commit e1f3cb774435d11e8f68192eee17decdc6e2b661 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 06/03/2023 at 13:51. Pushed by apol into branch 'Plasma/5.27'. libdpms/wayland: Do not create dpms interfaces for placeholder QScreens M +7-0src/libdpms/waylanddpmshelper.cpp https://invent.kde.org/plasma/libkscreen/commit/e1f3cb774435d11e8f68192eee17decdc6e2b661 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466599] Window decoration icon for Wayland-native electron app shows generic Wayland icon, not actual app icon; Task manager shows correct icon
https://bugs.kde.org/show_bug.cgi?id=466599 --- Comment #5 from g...@marcais.net --- I get slack from AUR. I will report it to Slack. Nevertheless, it is strange that not just Slack but also Signal misbehave when using wayland (not when using Xorg), and that kwin doesn't show the proper icon but the task manager widget does. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451876] Dolphin slow start takes almost 5-6 seconds
https://bugs.kde.org/show_bug.cgi?id=451876 Henrik Gebauer changed: What|Removed |Added CC||c...@henrik-gebauer.de --- Comment #3 from Henrik Gebauer --- I have the same issue (file open dialog took 9-10 seconds to show up). After finding this bug report, deleting user-places.xbel resolved the problem for me. The original file had over 21,000 lines, the newly generated has only 198 lines. The original file was over and over full with entries from kdeconnect (i have only one paired device but there were hundreds of entries) and hundreds entries about docker layers. This bug seems to be related to: Bug 422306 Dolphin and KDE file dialogs open very slowly Bug 466416 KDE Connect keeps adding devices to Dolphin over and over and over and over and over Bug 398908 Dolphin uses up huge amounts of memory over time -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Dead keys are not recognized [accute and grave accents (ú, ù), circumflex (û), diaeresis (ü)]
https://bugs.kde.org/show_bug.cgi?id=410876 Kévin GASPARD DE RENEFORT changed: What|Removed |Added CC||m...@koshie.fr --- Comment #12 from Kévin GASPARD DE RENEFORT --- Hello, I have the exact same issue as described wonderfully by Benjamin Vallin here: https://bugs.kde.org/show_bug.cgi?id=421794 OS: Debian 11.6 KTouch: 20.12.0 Desktop environment: Xfce 4.16 Architecture: 64 bits Kernel: Linux Desktop 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466942] Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466942 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 422306] Dolphin and KDE file dialogs open very slowly
https://bugs.kde.org/show_bug.cgi?id=422306 Henrik Gebauer changed: What|Removed |Added CC||c...@henrik-gebauer.de --- Comment #16 from Henrik Gebauer --- I have the same issue (file open dialog took 9-10 seconds to show up). After reading this bug report and the comments I finally tried deleting ` ~/.local/share/user-places.xbel` and that resolved the problem for me. The original file had over 21,000 lines, the newly generated has only 198 lines. The original file was over and over full with entries from kdeconnect (i have only one paired device but there were hundreds of entries) and hundreds entries about docker layers. I guess this bug is related to * #466416 KDE Connect keeps adding devices to Dolphin over and over and over and over and over * #451876 Dolphin slow start takes almost 5-6 seconds * #398908 Dolphin uses up huge amounts of memory over time -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466944] kded5 crashed upon waking up
https://bugs.kde.org/show_bug.cgi?id=466944 --- Comment #1 from avemi...@protonmail.com --- Created attachment 157044 --> https://bugs.kde.org/attachment.cgi?id=157044=edit dmesg with ACPI errors -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 433779] DrKonqui refuses to submit a bug report
https://bugs.kde.org/show_bug.cgi?id=433779 Scarlett Moore changed: What|Removed |Added CC||sgmo...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466944] New: kded5 crashed upon waking up
https://bugs.kde.org/show_bug.cgi?id=466944 Bug ID: 466944 Summary: kded5 crashed upon waking up Classification: Frameworks and Libraries Product: frameworks-kded Version: 5.103.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: avemi...@protonmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 157043 --> https://bugs.kde.org/attachment.cgi?id=157043=edit thread apply all bt full STEPS TO REPRODUCE 1. Put the laptop to sleep. 2. Try to wake it up. 3. Observe the ACPI errors. 4. Observe the crashed kded5. OBSERVED RESULT kded5 crashed EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: HP Product Name: HP EliteBook 840 14 inch G9 Notebook PC -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466943] Image Quality Sorter - AI Option Does NOT Exist
https://bugs.kde.org/show_bug.cgi?id=466943 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.10.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466943] Image Quality Sorter - AI Option Does NOT Exist
https://bugs.kde.org/show_bug.cgi?id=466943 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG CC||caulier.gil...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- This option will be available only with 8.0.0 release... You can test with 8.0.0-pre-release installer available here : https://files.kde.org/digikam/unstable/ Warnings: 8.0 database scheme is changed compared to 7.9. If you use 8.0 and you want to go back to 7.9, this will not possible. Backup your database first. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 --- Comment #5 from wolthera --- The size is shown in pixels because the spinbox allows you to edit the suffix. When you set it to 'pt' and then the decimals become visible. It's one of the few places in Krita where we do this, but that's also because a drop down with a unit selector would take up too much space. You can fix it to a unit, but there's still the simple usability problem that people don't realize they can type in a different unit which can be converted, and we'll get requests to type in pixels. Personally I'm very neutral towards UX changes, but I think this is the thought process behind the current situation... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 --- Comment #27 from feat...@engineer.com --- @tagwerk19, I'll look into these links. Meanwhile, I've created a PR here: https://invent.kde.org/frameworks/kconfig/-/merge_requests/188 If anyone is willing to review, I'd appreciate it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466931] Custom Message Aggregation Modes are not shown in Message List preferences until restart
https://bugs.kde.org/show_bug.cgi?id=466931 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Oh ! I will investigate it this night or tomorrow morning. Thanks for bug report -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 --- Comment #4 from Halla Rempt --- I'm still not totally sure about this... Should we really show the size in pixels here? And also, isn't the question perhaps more like, the bounds should snap to the pixel? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466943] New: Image Quality Sorter - AI Option Does NOT Exist
https://bugs.kde.org/show_bug.cgi?id=466943 Bug ID: 466943 Summary: Image Quality Sorter - AI Option Does NOT Exist Classification: Applications Product: digikam Version: 7.9.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Setup-Quality Assignee: digikam-bugs-n...@kde.org Reporter: digi...@myfreedom.com.au Target Milestone: --- Created attachment 157042 --> https://bugs.kde.org/attachment.cgi?id=157042=edit Image Quality Select Options I see no AI Image Quality option as listed in Manual see attached you seem to allow only ONE attachment all this huge (unnecessary) complexity - and a basic critical function like no of attachments you screw up) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466097] `setActiveNode` followed by fill does not work as expected
https://bugs.kde.org/show_bug.cgi?id=466097 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- Weirdly enough when I run the script, I get an error: NoneType object has no attribute "grow" on line 21. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 462736] Connection to external Mysql-Server fails
https://bugs.kde.org/show_bug.cgi?id=462736 --- Comment #62 from caulier.gil...@gmail.com --- Alex, I recompiled all with the Mariadb version 10.5 as we used at start of this thread. As i can see in Macports log, a fix have been applied to mariadb compilation. Perhaps this have fixed the orignal problem. I would to preserve the compatibility with older internal mysql database in production. Can you check again we the PKG published at usual place today ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466942] Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466942 Nicolas Fella changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466942] New: Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466942 Bug ID: 466942 Summary: Plasmashell crashes Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nicolas.fe...@gmx.de CC: k...@davidedmundson.co.uk Target Milestone: 1.0 While scrolling through Twitter. Presumably the videos in the timeline triggered (de)activation of the media player applet #0 0x7477603b in QMetaObject::cast(QObject const*) const (this=this@entry=0x4db040 , obj=obj@entry=0x25d8120) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qmetaobject.cpp:349 #1 0x77bb0079 in QMetaObject::cast(QObject*) const (obj=0x25d8120, this=) at /usr/include/qt6/QtCore/qobjectdefs.h:136 #2 qobject_cast(QObject*) (object=0x25d8120) at /usr/include/qt6/QtCore/qobject.h:442 #3 Plasma::Applet::containment() const (this=0x25d8120) at /home/nico/kde6/src/plasma-framework/src/plasma/applet.cpp:624 #4 0x77bb0189 in Plasma::Applet::location() const (this=) at /home/nico/kde6/src/plasma-framework/src/plasma/applet.cpp:686 #5 0x77f7eebf in AppletInterface::location() const (this=0x2492c20) at /home/nico/kde6/src/plasma-framework/src/plasmaquick/plasmoid/appletinterface.cpp:204 #6 AppletInterface::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x2492c20, _c=, _id=, _a=) at /home/nico/kde6/build/plasma-framework/src/plasmaquick/KF6PlasmaQuick_autogen/include/moc_appletinterface.cpp:1071 #7 0x76c3e8aa in QQmlPropertyData::readPropertyWithArgs(QObject*, void**) const (args=0x7fffac30, target=0x2492c20, this=0x7fff9421cca0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:328 #8 QQmlPropertyData::readProperty(QObject*, void*) const (property=0x7fffac00, target=0x2492c20, this=0x7fff9421cca0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:311 #9 QV4::loadProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const&) (v4=0xc638e0, object=0x2492c20, property=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:114 #10 0x76c3f3e2 in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData const*) (engine=engine@entry=0xc638e0, object=, object@entry=0x2492c20, property=0x7fff9421cca0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:253 #11 0x76c3fd19 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlRefPointer const&, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData const**) (engine=engine@entry=0xc638e0, qmlContext=..., object=0x2492c20, name=0x7fff9f3be598, revisionMode=revisionMode@entry=QV4::QObjectWrapper::IgnoreRevision, hasProperty=hasProperty@entry=0x0, property=0x0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:379 #12 0x76e100b2 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) (m=0x7fff9f3be588, id=..., receiver=0x7fff9f3be588, hasProperty=0x0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmltypewrapper.cpp:235 #13 0x76c0d461 in QV4::Object::get(QV4::StringOrSymbol*, bool*, QV4::Value const*) const (receiver=0x7fff9f3be588, hasProperty=0x0, name=0x7fff9f3be590, this=0x7fff9f3be588) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQml/6.4.2/QtQml/private/../../../../../../src/qml/jsruntime/qv4string_p.h:139 #14 QV4::Lookup::getterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value const&) (l=, engine=0xc638e0, object=) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/jsruntime/qv4lookup.cpp:194 #15 0x7fff7388787f in () #16 0x in () -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466938] Duplicate Detection Reference Image
https://bugs.kde.org/show_bug.cgi?id=466938 --- Comment #1 from Maik Qualmann --- Is it really digiKam-8.0.0, is it correct? It is valid for older versions, but not for 8.0.0. Not only the date is used to determine the original image, but also the file size and image size. I've tested it with many sample images and the "better" image is always set as the reference image. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #3 from wolthera --- The problem is in KisSpinBoxUnitManager::getApparentUnitRecommandedDecimals() const; The stroke config widget seems to set decimals in KoStrokeConfigWidget.cpp ln 137, perhaps decimals need to be set at DefaultToolGeometryWidget::setUnit(const KoUnit )? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466938] Duplicate Detection Reference Image
https://bugs.kde.org/show_bug.cgi?id=466938 caulier.gil...@gmail.com changed: What|Removed |Added OS|Other |Microsoft Windows CC||caulier.gil...@gmail.com Component|general |Searches-Similarity -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466938] Duplicate Detection Reference Image
https://bugs.kde.org/show_bug.cgi?id=466938 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466940] Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466940 Nicolas Fella changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 466941] New: Crashes in several scenarios
https://bugs.kde.org/show_bug.cgi?id=466941 Bug ID: 466941 Summary: Crashes in several scenarios Classification: Applications Product: ktimetracker Version: 5.0.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: k...@zipproth.de Target Milestone: --- Created attachment 157041 --> https://bugs.kde.org/attachment.cgi?id=157041=edit call stack On a fresh kubuntu 22.04 installation, ktimetracker crashes several times a day. I tried 2 versions: commit ids 933a2ae and cffa340 (which is from yesterday). Since February 2022, I was using ktimetracker on other Linux distributions (based on Ubuntu 20.04) without any issues. I was using commit id 933a2ae. Since I am using Kubuntu 22.04 it frequently crashes. I attached a screenshot of the call stack. This specific crash happened when I returned to my system and confirmed ktimetracker's dialog. But on other occasions, it simply crashes without any user interaction. I need to build it myself because the version in the distros are too old, they do not support exporting the event log. STEPS TO REPRODUCE 1. Install Kubuntu 22.04 2. use ktimetracker OBSERVED RESULT kubuntu dialog popping about that ktimetracker crashed EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Since no code from ktimetracker appears in the call stack, it might be helpful to load the debug symbols of libKF5IdleTime.so, which appears in the call stack. I'm happy to provide additional information if someone can help me with how to do this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #11 from Zamundaaa --- That's odd, there's not even a single relevant warning in that log. To narrow down where to go from here, please attach the output of drm_info (https://gitlab.freedesktop.org/emersion/drm_info) - once before you play the video, just on the desktop - once while you play the video in fullscreen - twice after you try exiting fullscreen, with at least a few seconds in between Also, if you drag another window on top of the fullscreen video instead of exiting fullscreen, does that also cause the problem? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466287] Timers cannot have negative intervals crash on startup
https://bugs.kde.org/show_bug.cgi?id=466287 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org --- Comment #9 from Halla Rempt --- We'd still have to have the workaround for distribution packages, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466940] Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466940 --- Comment #1 from Nicolas Fella --- #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f64042afec3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f640425fa76 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f6407b678fd in KCrash::defaultCrashHandler(int) (sig=11) at /home/nico/kde6/src/kcrash/src/kcrash.cpp:612 #4 0x7f640425fb20 in () at /lib64/libc.so.6 #5 dri_drawable (driDrawPriv=0x0) at ../src/gallium/frontends/dri/dri_drawable.h:89 #6 dri2_invalidate_drawable (dPriv=0x0) at ../src/gallium/frontends/dri/dri2.c:82 #7 0x7f63f33dfdf8 in QtWaylandClient::QWaylandEglWindow::updateSurface(bool) (this=0x6477f40, create=) at /usr/include/qt6/QtCore/qpoint.h:124 #8 0x7f640524d384 in QWindow::resize(QSize const&) (this=0x6909a30, newSize=...) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/gui/kernel/qwindow.cpp:1914 #9 0x7f640820fa2d in PlasmaQuick::DialogPrivate::syncToMainItemSize() (this=0x53808a0) at /home/nico/kde6/src/plasma-framework/src/plasmaquick/dialog.cpp:711 #10 0x7f64049c7f8f in doActivate(QObject*, int, void**) (sender=0x6a5e780, signal_index=25, argv=0x7ffc0f6e9388) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:3991 #11 0x7f64049c0cc7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f6407ac89a0, local_signal_index=local_signal_index@entry=22, argv=argv@entry=0x0) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:4039 #12 0x7f6407619377 in QQuickItem::heightChanged() (this=) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/src/quick/Quick_autogen/include/moc_qquickitem.cpp:1614 #13 0x7f640763fdba in QQuickItemPrivate::heightChanged() (this=0x64c2970) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQuick/6.4.2/QtQuick/private/../../../../../../src/quick/items/qquickitem_p.h:579 #14 0x7f640762e81c in QQuickItem::geometryChange(QRectF const&, QRectF const&) (this=0x6a5e780, newGeometry=, oldGeometry=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/items/qquickitem.cpp:3788 #15 0x7f64076255f6 in QQuickItem::setHeight(double) (this=0x6a5e780, h=) at /usr/include/qt6/QtCore/qrect.h:610 #16 0x7f640763f296 in QQuickItemPrivate::setHeight(double) (height=, this=0x64c2970) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/redhat-linux-build/include/QtQuick/6.4.2/QtQuick/private/../../../../../../src/quick/items/qquickitem_p.h:218 #17 QObjectCompatProperty::bindingWrapper(QMetaType, QUntypedPropertyData*, QtPrivate::QPropertyBindingFunction) (type=..., dataPtr=0x64c2ac8, binding=...) at /usr/include/qt6/QtCore/6.4.2/QtCore/private/qproperty_p.h:490 #18 0x7f64049cd3ed in QPropertyBindingPrivate::evaluateRecursive_inline(QVarLengthArray&, QBindingStatus*) (status=0x7f6400b7b558, bindingObservers=..., this=0x6b9b8f0) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qproperty_p.h:810 #19 QPropertyBindingPrivate::evaluateRecursive(QVarLengthArray&, QBindingStatus*) (this=0x6b9b8f0, bindingObservers=..., status=0x7f6400b7b558) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qproperty.cpp:283 #20 0x7f6406f9b5e3 in QQmlPropertyBindingJS::expressionChanged() (this=0x6b9b9b0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlpropertybinding.cpp:156 #21 0x7f6406f717b6 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=0x0) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/qml/qml/qqmlnotifier.cpp:70 #22 0x7f64049c7a90 in doActivate(QObject*, int, void**) (sender=0x3dfd350, signal_index=28, argv=0x0) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:3871 #23 0x7f63c5fe11ce in QQuickLayoutPrivate::applySizeHints() const (this=this@entry=0x3ec0ab0) at /usr/include/qt6/QtCore/qsize.h:317 #24 0x7f63c5fe13b8 in QQuickLayout::ensureLayoutItemsUpdated(QFlags) const (this=this@entry=0x3dfd350, options=..., options@entry=...) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quicklayouts/qquicklayout.cpp:816 #25 0x7f63c5fe1553 in QQuickLayout::updatePolish() (this=0x3dfd350) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quicklayouts/qquicklayout.cpp:718 #26 0x7f64076db268 in QQuickWindowPrivate::polishItems() (this=0x68b2680) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/items/qquickwindow.cpp:344 #27 0x7f64078b0953 in QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) (this=this@entry=0x2256ed0, w=w@entry=0x5ffc1f0, inExpose=inExpose@entry=true) at /usr/src/debug/qt6-qtdeclarative-6.4.2-1.fc37.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1557 #28
[plasmashell] [Bug 466940] New: Plasmashell crashes
https://bugs.kde.org/show_bug.cgi?id=466940
Bug ID: 466940
Summary: Plasmashell crashes
Classification: Plasma
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: nicolas.fe...@gmx.de
Target Milestone: 1.0
I *think* it was after receiving a notification
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 dri_drawable (driDrawPriv=0x0) at
../src/gallium/frontends/dri/dri_drawable.h:89
#6 dri2_invalidate_drawable (dPriv=0x0) at
../src/gallium/frontends/dri/dri2.c:82
#7 0x7f63f33dfdf8 in
QtWaylandClient::QWaylandEglWindow::updateSurface(bool) () at
/lib64/libQt6WaylandEglClientHwIntegration.so.6
#8 0x7f640524d384 in QWindow::resize(QSize const&) () at
/lib64/libQt6Gui.so.6
#9 0x7f640820fa2d in PlasmaQuick::DialogPrivate::syncToMainItemSize()
(this=0x53808a0) at
/home/nico/kde6/src/plasma-framework/src/plasmaquick/dialog.cpp:711
#10 0x7f64049c7f8f in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#11 0x7f640762e81c in QQuickItem::geometryChange(QRectF const&, QRectF
const&) () at /lib64/libQt6Quick.so.6
#12 0x7f64076255f6 in QQuickItem::setHeight(double) () at
/lib64/libQt6Quick.so.6
#13 0x7f640763f296 in QObjectCompatProperty::bindingWrapper(QMetaType, QUntypedPropertyData*,
QtPrivate::QPropertyBindingFunction) () at /lib64/libQt6Quick.so.6
#14 0x7f64049cd3ed in
QPropertyBindingPrivate::evaluateRecursive(QVarLengthArray&, QBindingStatus*) () at /lib64/libQt6Core.so.6
#15 0x7f6406f9b5e3 in QQmlPropertyBindingJS::expressionChanged() () at
/lib64/libQt6Qml.so.6
#16 0x7f6406f717b6 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () at /lib64/libQt6Qml.so.6
#17 0x7f64049c7a90 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#18 0x7f63c5fe11ce in QQuickLayoutPrivate::applySizeHints() const () at
/lib64/libQt6QuickLayouts.so.6
#19 0x7f63c5fe13b8 in
QQuickLayout::ensureLayoutItemsUpdated(QFlags)
const () at /lib64/libQt6QuickLayouts.so.6
#20 0x7f63c5fe1553 in QQuickLayout::updatePolish() () at
/lib64/libQt6QuickLayouts.so.6
#21 0x7f64076db268 in QQuickWindowPrivate::polishItems() () at
/lib64/libQt6Quick.so.6
#22 0x7f64078b0953 in
QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) ()
at /lib64/libQt6Quick.so.6
#23 0x7f64078b1c30 in QSGThreadedRenderLoop::handleExposure(QQuickWindow*)
() at /lib64/libQt6Quick.so.6
#24 0x7f6405252498 in QWindow::event(QEvent*) () at /lib64/libQt6Gui.so.6
#25 0x7f6408211adf in PlasmaQuick::Dialog::event(QEvent*) (this=0x6909a30,
event=0x7ffc0f6ebf90) at
/home/nico/kde6/src/plasma-framework/src/plasmaquick/dialog.cpp:1450
#26 0x7f6405fbaa65 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt6Widgets.so.6
#27 0x7f6404968068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt6Core.so.6
#28 0x7f640520025f in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() at /lib64/libQt6Gui.so.6
#29 0x7f64052551cc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /lib64/libQt6Gui.so.6
#30 0x7f6405708824 in userEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt6Gui.so.6
#31 0x7f6403cbbc7f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#32 0x7f6403d12118 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#33 0x7f6403cb8f00 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#34 0x7f6404c23220 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt6Core.so.6
#35 0x7f640497465b in
QEventLoop::exec(QFlags) () at
/lib64/libQt6Core.so.6
#36 0x7f6404970528 in QCoreApplication::exec() () at /lib64/libQt6Core.so.6
#37 0x00424f79 in main(int, char**) (argc=,
argv=) at
/home/nico/kde6/src/plasma-workspace/shell/main.cpp:235
[Inferior 1 (process 9770) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 466939] plasmashell crashes when dropping widget from widget explorer
https://bugs.kde.org/show_bug.cgi?id=466939 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466707] About this System: "Show More Information" button in System Settings representation doesn't actually show more information when clicked
https://bugs.kde.org/show_bug.cgi?id=466707 --- Comment #4 from Johannes Claesson --- (In reply to Nate Graham from comment #3) > Git commit 20f62bdc56be09f69f5d580af3d6e3c520b3c062 by Nate Graham. > Committed on 05/03/2023 at 23:15. > Pushed by ngraham into branch 'master'. > > Rename "Show More Information" button to "Launch Info Center" > > It actually doesn't show you more information--at least not immediately. > This is because it launches Info Center, which displays the very same > page you came from by default. > > Let's rename the button to set user expectations accordingly. > FIXED-IN: 6.0 > > M +1-1Modules/about-distro/src/package/contents/ui/main.qml > > https://invent.kde.org/plasma/kinfocenter/commit/ > 20f62bdc56be09f69f5d580af3d6e3c520b3c062 This makes much more sense. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466287] Timers cannot have negative intervals crash on startup
https://bugs.kde.org/show_bug.cgi?id=466287 amyspark changed: What|Removed |Added Assignee|ha...@valdyas.org |a...@amyspark.me --- Comment #8 from amyspark --- I'll try and remove the bearer management support from Qt and PyQt5. That'll enable us to drop the workaround. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 Ye Jingchen changed: What|Removed |Added CC||ye.jingc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 --- Comment #26 from tagwer...@innerjoin.org --- (In reply to feature from comment #25) > ... This had become much more pervasive a change than I had anticipated ... It might be worthwhile posting a "heads up" on the Nixos forums. There have been simmering discussions about what's needed to define a KDE setup for Nixos/Nix/Home Manager (as "Declarative KDE" rather than scripting the setup). The problem statement or maybe a "cri de couer": https://discourse.nixos.org/t/how-to-configure-kde-properly-in-nix/21362 and a tracking issue: https://github.com/nix-community/home-manager/issues/607 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466793] Missing audio control icon in System preferences
https://bugs.kde.org/show_bug.cgi?id=466793 --- Comment #5 from feveal --- Hi. In the end I decided to upgrade from Kubuntu 20.04 to 22.04 and now everything works fine. There is a hardware detection or configuration problem on a clean install of 22.04. I guess in the future they will be able to fix it. Thank you very much for support De: feveal - Enviado: lunes, 6 de marzo de 2023 9:46 Para: bug-cont...@kde.org Asunto: RE: [systemsettings] [Bug 466793] Missing audio control icon in System preferences Hola I have done two more things; I have first reinstalled from scratch Kubuntu 22.04. The problem with the sound is the same and the HDMI has not recognized me. Bluetooth doesn't work properly either. Then I have removed version 22.04 and I have installed from zero Kubuntu 20.04. With this version everything has worked correctly. Pulseaudio recognizes the HDMI connection. The Bluetooth works correctly. Now I am in doubt whether to wait a while until updating to version 22.04 or to do it now. Thanks De: feveal - Enviado: sábado, 4 de marzo de 2023 22:25 Para: bug-cont...@kde.org Asunto: RE: [systemsettings] [Bug 466793] Missing audio control icon in System preferences Hi, I also have a problem with Bluetooth. The device (headphones) is detected, it connects for two seconds and disconnects. After that you can't connect again. It may have to do with the audio output as HDMI is not recognized either I have looked in blogs and forums, I see that this problem is common Thanks De: feveal - Enviado: viernes, 3 de marzo de 2023 23:27 Para: bug-cont...@kde.org Asunto: RE: [systemsettings] [Bug 466793] Missing audio control icon in System preferences Yes. But I have already managed to make it appear using these commands sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio systemctl --user restart pipewire-session-manager The whole problem started because yesterday I reinstalled Kubuntu 22.04 with Plasma to do a general cleanup. Before I also had the same version installed, but with successive updates since 20.04. So everything was working fine. now when connecting the TV via HDMI it does not detect the audio output and the TV can be seen but not heard. Trying to fix it I had broken something, but I finally managed to get to the beginning. Now I still have the problem that it does not detect the HDMI audio I have tried connecting and disconnecting the HDMI cable, reinstalling pavucontrol, etc. I'm looking for solutions on the web but I can't find the right solution Thanks De: Nicolas Fella Enviado: viernes, 3 de marzo de 2023 22:31 Para: fev...@hotmail.com Asunto: [systemsettings] [Bug 466793] Missing audio control icon in System preferences https://bugs.kde.org/show_bug.cgi?id=466793 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nicolas Fella --- Is plasma-pa installed? -- You are receiving this mail because: You reported the bug. T -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 466790] Many Plasma 5.27 localization strings missing
https://bugs.kde.org/show_bug.cgi?id=466790 --- Comment #8 from Luigi Toscano --- (In reply to Tommi Nieminen from comment #7) > Live and learn… No, I didn’t specify the language, because the issue was > clearly at source as I said: there was no way to translate something which > wasn’t even there. Just to clarify: the strings to translate were there, in the translation branches. The Finnish team, just like many other teams (including the Italian one) uses an additional layer on top which makes it easier to handle multiple branches, but it requires at the moment some additional work for its handling. Knowing which language was affected was an important detail, and would have helped the triaging. In general, the more details about the scenario are available to the bug triagers, the better. > Now that someone (Luigi? or Lasse?) did something in the SVN repo, the > situation is OK. Still I think these kind of things shouldn’t remain only > oral knowledge but should be told somewhere like the KDE wiki > (https://techbase.kde.org/Localization); some of the people localizing > Plasma, like me, are not developers at all… It's not done, because the messages are in the summit branch but needs to be "scattered" in the appropriate branches. Both this update (merge) and the scatter need to be performed periodically. Again, my suggestion is to discuss the future steps and the knowledge transfer in the context of your team's mailing list, https://mail.kde.org/mailman/listinfo/kde-l10n-fi . -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #7 from Eric R --- I can reproduce "Forget Recent Files" never working for Firefox. Please see new "Comparison of Menus, 2022 & 2023" attachment. Currently on firefox/jammy,now 110.0.1+build2-0ubuntu0.22.04.1~mt1 amd64 [installed,automatic] Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5 CPU M 520 @ 2.40GHz Memory: 7.6 GiB of RAM Graphics Processor: NVA8 Manufacturer: LENOVO Product Name: 43142MU System Version: ThinkPad T510 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #10 from Rune --- Created attachment 157039 --> https://bugs.kde.org/attachment.cgi?id=157039=edit Output of journalctl --user-unit plasma-kwin_wayland --boot 0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #9 from Rune --- (In reply to Zamundaaa from comment #8) > Please attach the output of > > journalctl --user-unit plasma-kwin_wayland --boot 0 > after making the bug happen again Output attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446235] The item "Clear recent files list" doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446235 --- Comment #6 from Eric R --- Created attachment 157038 --> https://bugs.kde.org/attachment.cgi?id=157038=edit Comparison of Menus, 2022 & 2023 Firefox task bar right-click menus from 2022 and 2023 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 327881] False Positive Warning on std::atomic_bool
https://bugs.kde.org/show_bug.cgi?id=327881 Jan Niklas Hasse changed: What|Removed |Added CC||jha...@bixense.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 339330] Feature request: Add support for C++11's std::atomic
https://bugs.kde.org/show_bug.cgi?id=339330 Jan Niklas Hasse changed: What|Removed |Added CC||jha...@bixense.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466800] power management crashed when attempting to unlock screen with monitor sleeping
https://bugs.kde.org/show_bug.cgi?id=466800 arseny.us...@gmail.com changed: What|Removed |Added CC||arseny.us...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465973] Display distorts when switching to 5120x1440 resolution
https://bugs.kde.org/show_bug.cgi?id=465973 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #11 from Zamundaaa --- This looks like a driver bug; I've had similar glitches happen before on Xorg with my Samsung CRG9. Can you try the Wayland session? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #8 from Zamundaaa --- Please attach the output of > journalctl --user-unit plasma-kwin_wayland --boot 0 after making the bug happen again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466939] plasmashell crashes when dropping widget from widget explorer
https://bugs.kde.org/show_bug.cgi?id=466939 --- Comment #1 from Nicolas Fella --- #0 std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::find(Qt::DropAction const&) const (__k=: Qt::MoveAction, this=0xb) at /usr/include/c++/12/bits/stl_tree.h:2544 #1 std::map, std::allocator > >::find(Qt::DropAction const&) const (__x=: Qt::MoveAction, this=0xb) at /usr/include/c++/12/bits/stl_map.h:1243 #2 QMap::find(Qt::DropAction const&) const (key=, this=) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/tools/qmap.h:651 #3 QMap::constFind(Qt::DropAction const&) const (key=, this=) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/tools/qmap.h:656 #4 QDrag::dragCursor(Qt::DropAction) const (this=0x1f178e0, action=action@entry=Qt::MoveAction) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/gui/kernel/qdrag.cpp:282 #5 0x753efdfd in QBasicDrag::updateCursor(Qt::DropAction) (this=0x5294f0, action=Qt::MoveAction) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/gui/kernel/qsimpledrag.cpp:274 #6 0x766a66e3 in operator() (action=Qt::MoveAction, accepted=, __closure=) at /usr/src/debug/qt6-qtwayland-6.4.2-1.fc37.x86_64/src/client/qwaylanddatadevice.cpp:105 #7 QtPrivate::FunctorCall, QtPrivate::List, void, QtWaylandClient::QWaylandDataDevice::startDrag(QMimeData*, Qt::DropActions, QtWaylandClient::QWaylandWindow*):: >::call (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:127 #8 QtPrivate::Functor, 2>::call, void> (arg=, f=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:241 #9 QtPrivate::QFunctorSlotObject, 2, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:408 #10 0x747c7d30 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffbcb0, r=, this=0x254b790) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363 #11 doActivate(QObject*, int, void**) (sender=0x35736f0, signal_index=5, argv=0x7fffbcb0) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:3979 #12 0x747c0cc7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x766da020 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffbcb0) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:4039 #13 0x766a1f4d in QtWaylandClient::QWaylandDataSource::dndResponseUpdated(bool, Qt::DropAction) (this=, _t1=, _t2=) at /usr/src/debug/qt6-qtwayland-6.4.2-1.fc37.x86_64/redhat-linux-build/src/client/WaylandClient_autogen/include/moc_qwaylanddatasource_p.cpp:213 #14 0x766996c2 in QtWayland::wl_data_source::handle_target(void*, wl_data_source*, char const*) (data=0x3573700, object=, mime_type=0x7fffdc006ddc "text/x-plasmoidservicename") at /usr/src/debug/qt6-qtwayland-6.4.2-1.fc37.x86_64/redhat-linux-build/src/client/qwayland-wayland.cpp:733 #15 0x74c5ca06 in ffi_call_unix64 () at ../src/x86/unix64.S:104 #16 0x74c5949d in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:673 #17 0x74c5c083 in ffi_call (cif=cif@entry=0x7fffbf00, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7fffbfd0) at ../src/x86/ffi64.c:710 #18 0x77ce2316 in wl_closure_invoke (closure=0x7fffdc006d00, flags=, target=, opcode=0, data=) at ../src/connection.c:1025 #19 0x77cdea89 in dispatch_event (display=display@entry=0x51a3f0, queue=0x51a4c0) at ../src/wayland-client.c:1595 #20 0x77ce0284 in dispatch_queue (queue=0x51a4c0, display=0x51a3f0) at ../src/wayland-client.c:1741 #21 wl_display_dispatch_queue_pending (display=0x51a3f0, queue=0x51a4c0) at ../src/wayland-client.c:1983 #22 0x76664c6d in QtWaylandClient::QWaylandDisplay::flushRequests() (this=) at /usr/src/debug/qt6-qtwayland-6.4.2-1.fc37.x86_64/src/client/qwaylanddisplay.cpp:232 #23 0x747ba370 in QObject::event(QEvent*) (this=0x51a1e0, e=0x7fffdc00c130) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qobject.cpp:1378 #24 0x75dbaa65 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x51a1e0, e=0x7fffdc00c130) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/widgets/kernel/qapplication.cpp:3315 #25 0x74768068 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x51a1e0, event=0x7fffdc00c130) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qcoreapplication.cpp:1026 #26 0x7476f170 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x50c950) at /usr/src/debug/qt6-qtbase-6.4.2-4.fc37.x86_64/src/corelib/kernel/qcoreapplication.cpp:1804 #27 0x74a23957 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5257e0) at
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #12 from Vladimir Yerilov --- Created attachment 157036 --> https://bugs.kde.org/attachment.cgi?id=157036=edit Kwin rule (In reply to Kai Eckert from comment #11) > I can confirm that the bug still exists, it annoys me to the point that I > had to switch off the "keep open" option. Nothing worse than constantly > accidently writing stuff into the wrong window. > > Yakuake 22.12.3 > Plasma 5.27.2 To work it around, go to Window Management -> Window Rules, and a new rule for yakuake as shown on atached file. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 466803] Haruna doesn't open .TS videos on startup
https://bugs.kde.org/show_bug.cgi?id=466803 george fb changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/haruna/commit/5b0273 ||8eb7dd4a49a07aaedb4c7803537 ||ee54024 --- Comment #1 from george fb --- Git commit 5b02738eb7dd4a49a07aaedb4c7803537ee54024 by George Florea Bănuș. Committed on 05/03/2023 at 19:29. Pushed by georgefb into branch 'master'. playlistmodel: fix file opening M +6-8src/application.cpp M +3-3src/application.h M +10 -14 src/models/playlistmodel.cpp M +1-1src/models/playlistmodel.h M +2-2src/qml/MpvVideo.qml https://invent.kde.org/multimedia/haruna/commit/5b02738eb7dd4a49a07aaedb4c7803537ee54024 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466939] New: plasmashell crashes when dropping widget from widget explorer
https://bugs.kde.org/show_bug.cgi?id=466939
Bug ID: 466939
Summary: plasmashell crashes when dropping widget from widget
explorer
Classification: Plasma
Product: plasmashell
Version: master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: nicolas.fe...@gmx.de
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
Application: plasmashell (5.27.80)
(Compiled from sources)
Qt Version: 6.4.2
Frameworks Version: 5.240.0
Operating System: Linux 6.1.14-200.fc37.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.80 [KCrashBackend]
-- Information about the crash:
Open widgets explorer
Take comic book widget
Drag on desktop
Drop
The crash can be reproduced every time.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 0x7fd8d4bed1ee in QDrag::dragCursor(Qt::DropAction) const () at
/lib64/libQt6Gui.so.6
#6 0x7fd8d4befdfd in QBasicDrag::updateCursor(Qt::DropAction) () at
/lib64/libQt6Gui.so.6
#7 0x7fd8d5fb36e3 in
QtPrivate::QFunctorSlotObject, QtWaylandClient::QWaylandWindow*)::{lambda(bool,
Qt::DropAction)#1}, 2, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () at
/lib64/libQt6WaylandClient.so.6
#8 0x7fd8d3fc7d30 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#9 0x7fd8d5faef4d in
QtWaylandClient::QWaylandDataSource::dndResponseUpdated(bool, Qt::DropAction)
() at /lib64/libQt6WaylandClient.so.6
#10 0x7fd8d5fa66c2 in QtWayland::wl_data_source::handle_target(void*,
wl_data_source*, char const*) () at /lib64/libQt6WaylandClient.so.6
#11 0x7fd8d446ea06 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#12 0x7fd8d446b49d in ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=)
at ../src/x86/ffi64.c:673
#13 0x7fd8d446e083 in ffi_call (cif=cif@entry=0x7ffe771d2f90, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffe771d3060) at
../src/x86/ffi64.c:710
#14 0x7fd8d75d6316 in wl_closure_invoke (closure=0x7fd8b400c930,
flags=, target=, opcode=0, data=)
at ../src/connection.c:1025
#15 0x7fd8d75d2a89 in dispatch_event (display=display@entry=0x54f3c0,
queue=0x54f490) at ../src/wayland-client.c:1595
#16 0x7fd8d75d4284 in dispatch_queue (queue=0x54f490, display=0x54f3c0) at
../src/wayland-client.c:1741
#17 wl_display_dispatch_queue_pending (display=0x54f3c0, queue=0x54f490) at
../src/wayland-client.c:1983
#18 0x7fd8d5f71c6d in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /lib64/libQt6WaylandClient.so.6
#19 0x7fd8d3fba370 in QObject::event(QEvent*) () at /lib64/libQt6Core.so.6
#20 0x7fd8d55baa65 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt6Widgets.so.6
#21 0x7fd8d3f68068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt6Core.so.6
#22 0x7fd8d3f6f170 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt6Core.so.6
#23 0x7fd8d4223957 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt6Core.so.6
#24 0x7fd8d32f3c7f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#25 0x7fd8d334a118 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#26 0x7fd8d32f0f00 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#27 0x7fd8d4223220 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt6Core.so.6
#28 0x7fd8d3f7465b in
QEventLoop::exec(QFlags) () at
/lib64/libQt6Core.so.6
#29 0x7fd8d4beef17 in QBasicDrag::drag(QDrag*) () at /lib64/libQt6Gui.so.6
#30 0x7fd8d4bec800 in QDragManager::drag(QDrag*) () at
/lib64/libQt6Gui.so.6
#31 0x7fd8d4bed11f in QDrag::exec(QFlags, Qt::DropAction)
() at /lib64/libQt6Gui.so.6
#32 0x7fd8d6ec79bb in
QQuickDragAttachedPrivate::startDrag(QFlags) () at
/lib64/libQt6Quick.so.6
#33 0x7fd8d6ec8a2b in QQuickDragAttached::qt_metacall(QMetaObject::Call,
int, void**) () at /lib64/libQt6Quick.so.6
#34 0x7fd8d64e64ae in QQmlPropertyData::writeProperty(QObject*, void*,
QFlags) const () at /lib64/libQt6Qml.so.6
#35 0x7fd8d6596ebc in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData
const&, QVariant const&, QQmlRefPointer const&,
QFlags) () at /lib64/libQt6Qml.so.6
#36 0x7fd8d643ccbe in
QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const*, QV4::Value const&) () at /lib64/libQt6Qml.so.6
#37 0x7fd8d643d47e in
QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*,
QQmlRefPointer const&, QObject*, QV4::String*,
QV4::QObjectWrapper::RevisionMode, QV4::Value const&)
[kdenlive] [Bug 447697] Crackling noise when playing preview
https://bugs.kde.org/show_bug.cgi?id=447697 farid changed: What|Removed |Added CC||snd.no...@gmail.com Status|REOPENED|CONFIRMED --- Comment #5 from farid --- I confirm this in latest master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466329] The main window display doesn't update.
https://bugs.kde.org/show_bug.cgi?id=466329 Halla Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Halla Rempt --- So I understand this happens with one specific file? Could you attach the file to the bug report? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465846] Pan tool shortcut
https://bugs.kde.org/show_bug.cgi?id=465846 Halla Rempt changed: What|Removed |Added CC||artch...@qq.com --- Comment #1 from Halla Rempt --- *** Bug 466249 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466249] Shortcut key malfunction and mouse input malfunction
https://bugs.kde.org/show_bug.cgi?id=466249 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Severity|critical|normal Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Halla Rempt --- *** This bug has been marked as a duplicate of bug 465846 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466817] Window snapping makes window rearrangement impossible using snapping, degradation compared to previous window resizing/snapping algorithm
https://bugs.kde.org/show_bug.cgi?id=466817 Nicolas Fella changed: What|Removed |Added Assignee|zrenf...@gmail.com |kwin-bugs-n...@kde.org Product|Active Window Control |kwin Component|General |general -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 466817] Window snapping makes window rearrangement impossible using snapping, degradation compared to previous window resizing/snapping algorithm
https://bugs.kde.org/show_bug.cgi?id=466817 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Keywords|qt6 | -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 466737] ** Removed for violation of community policy **
https://bugs.kde.org/show_bug.cgi?id=466737 Nicolas Fella changed: What|Removed |Added Keywords|qt6 | CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466582] Vector Shape positions are floats, yet the interface pretends they are integers
https://bugs.kde.org/show_bug.cgi?id=466582 Halla Rempt changed: What|Removed |Added Summary|[Regression] Vector Shape |Vector Shape positions are |positions are floats, yet |floats, yet the interface |the interface pretends they |pretends they are integers |are integers| Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
