[plasmashell] [Bug 484266] New: Regular Task Manager (not icons-only) frequently becomes uninteractable on multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=484266 Bug ID: 484266 Summary: Regular Task Manager (not icons-only) frequently becomes uninteractable on multi-monitor setup Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY I have a 1920x1080 secondary monitor, and a 2560x1440 primary monitor. The task manager (regular version, not icons-only version) frequently no longer responds to clicks or hover of the mouse on the primary monitor (but not the secondary monitor) until the panel is manually edited and resized. This started happening with Plasma6. Tray icon can still be interacted with as can the clock, but start menu can't. Panel is non-floating. STEPS TO REPRODUCE 1. Have two monitors of different resolutions. Add a panel on the primary monitor, switch it to non-floating, set the task manager to the regular version. 2. Use the system for a while OBSERVED RESULT Entries in the task manager can no longer be clicked or interacted with in other ways. They still update when otherwise focused though. EXPECTED RESULT Task manager doesn't break SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.8.1, Wayland (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This does not happen on my laptop which only has one display. AMDGPU, RX 7900 XT, Mesa 24.0.3, but hopefully a bug in which the panel clearly still renders properly but just doesn't know where the mouse cursor is is not driver dependent. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482785] New: No way to see full process name if it's too long
https://bugs.kde.org/show_bug.cgi?id=482785 Bug ID: 482785 Summary: No way to see full process name if it's too long Classification: Applications Product: plasma-systemmonitor Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: kdeb...@fratti.ch CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY In the Processes view, when a process has a very long name, such as systemd-ask-password-agent in tree view, the "Name" column cannot be expanded, and there is no hover tooltip on the "Name" column to display the full ellipsised name. STEPS TO REPRODUCE 1. Spawn a process with a long name 2. Try to find out what it's name is through plasma-systemmonitor OBSERVED RESULT Process name is cut off with ellipsis, to prevent my very small and smooth brain from receiving too much information. Expanding the name column doesn't work because it has a maximum width for some reason, presumably to stop my very small and smooth brain from making it too wide and then getting confused and crying. There is no hover tooltip showing the full name when hovering over the cut off name. EXPECTED RESULT Either let me make the column wider or add a tooltip. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477178] Plasma crashes after moving the mouse over the task bar
https://bugs.kde.org/show_bug.cgi?id=477178 --- Comment #1 from Nicolas F. --- Created attachment 163260 --> https://bugs.kde.org/attachment.cgi?id=163260=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477178] New: Plasma crashes after moving the mouse over the task bar
https://bugs.kde.org/show_bug.cgi?id=477178 Bug ID: 477178 Summary: Plasma crashes after moving the mouse over the task bar Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.1.60-1-lts x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: I was moving my mouse cursor from a firefox window downwards towards my task bar, and KDE Plasma crashed. Driver: amdgpu/radeonsi, Ryzen 3700U (Laptop SoC) The crash can be reproduced sometimes. -- Backtrace (Reduced): #4 0x7fe3b82ac0a1 in dri2_wl_swap_buffers_with_damage () at ../mesa-23.2.1/src/egl/drivers/dri2/platform_wayland.c:1661 #5 0x7fe3b829c328 in dri2_swap_buffers () at ../mesa-23.2.1/src/egl/drivers/dri2/egl_dri2.c:1881 #6 0x7fe3b829406d in eglSwapBuffers () at ../mesa-23.2.1/src/egl/main/eglapi.c:1433 #7 0x7fe3b937a6f5 in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) (this=0x55ca15fef840, surface=0x55ca13faab40) at /usr/src/debug/qt5-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:502 [...] #10 0x7fe3be0f371a in operator() (__closure=) at thread/qthread_unix.cpp:350 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #11 from Nicolas F. --- This is still an issue in 5.27.6. Is there any additional info I can provide to help narrow this down? Another machine using the same plasma version doesn't have this issue, so I assume it's either some configuration or hardware causing this. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470852] Crash when opening picture in Downloads folder when sorting by date
https://bugs.kde.org/show_bug.cgi?id=470852 Nicolas F. changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #7 from Nicolas F. --- *** Bug 471235 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471235] Uncaught out of range exception in exiv2 when opening image
https://bugs.kde.org/show_bug.cgi?id=471235 Nicolas F. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nicolas F. --- Looks like this is https://github.com/Exiv2/exiv2/issues/2650 and therefore a duplicate of https://bugs.kde.org/show_bug.cgi?id=470852 *** This bug has been marked as a duplicate of bug 470852 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471235] Uncaught out of range exception in exiv2 when opening image
https://bugs.kde.org/show_bug.cgi?id=471235 --- Comment #1 from Nicolas F. --- Found the precise image that triggers it, this (slightly nsfw) Shimarin. https://overviewer.org/~pillow/up/35369a3c92/1482455152606.png Should make it easy to reproduce now -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471235] New: Uncaught out of range exception in exiv2 when opening image
https://bugs.kde.org/show_bug.cgi?id=471235
Bug ID: 471235
Summary: Uncaught out of range exception in exiv2 when opening
image
Classification: Applications
Product: gwenview
Version: 23.04.2
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: kdeb...@fratti.ch
Target Milestone: ---
SUMMARY
Gwenview crashes when opening an image in a specific folder, presumably while
trying to parse other images in this folder, as the opened image is not a PNG
file but it crashes in PNG metadata parsing. It appears to be a problem with an
empty but present authorname field or something.
STEPS TO REPRODUCE
1. Open gwenview
OBSERVED RESULT
It crashes, drkonqi never launches successfully (dunno why)
EXPECTED RESULT
It doesn't crash
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.3.8-arch1-1/ Wayland
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
ADDITIONAL INFORMATION
Crash backtrace (bt full)
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {
__val = {140737308731440}
}
ret =
#1 0x7529f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
No locals.
#2 0x7524fa08 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#3 0x75238538 in __GI_abort () at abort.c:79
save_stage = 1
act = {
__sigaction_handler = {
sa_handler = 0x20,
sa_sigaction = 0x20
},
sa_mask = {
__val = {140737307944515, 2664, 140737306508196, 34, 1, 4, 0, 14,
140737310568216, 140737488336768, 93825020659392, 14, 0, 140737488337440,
140737353991356, 93825020642888}
},
sa_flags = -134353124,
sa_restorer = 0x753f2780
}
#4 0x7549ca6f in __gnu_cxx::__verbose_terminate_handler () at
/usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
terminating = true
t =
#5 0x754b011c in __cxxabiv1::__terminate (handler=) at
/usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
No locals.
#6 0x754b0189 in std::terminate () at
/usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
No locals.
#7 0x754b03ed in __cxxabiv1::__cxa_throw (obj=,
tinfo=0x7566c0e8 , dest=0x754c85c0
) at
/usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/eh_throw.cc:98
globals =
header = 0x57090d80
#8 0x76ef05d0 in Exiv2::DataBuf::c_data (this=,
offset=) at /usr/src/debug/exiv2/exiv2-0.28.0/src/types.cpp:180
No locals.
#9 0x76f8d3f5 in Exiv2::Internal::PngChunk::parseTXTChunk (data=...,
keysize=13, type=type@entry=Exiv2::Internal::PngChunk::tEXt_Chunk) at
/usr/src/debug/exiv2/exiv2-0.28.0/src/pngchunk_int.cpp:113
text =
textsize =
arr = {
pData_ = std::vector of length 0, capacity 0
}
#10 0x76f8e2c3 in Exiv2::Internal::PngChunk::decodeTXTChunk
(pImage=0x57170e90, data=..., type=Exiv2::Internal::PngChunk::tEXt_Chunk)
at /usr/src/debug/exiv2/exiv2-0.28.0/src/pngchunk_int.cpp:54
key = {
pData_ = std::vector of length 13, capacity 13 = {65 'A', 117 'u',
116 't', 104 'h', 111 'o', 114 'r', 39 '\'', 115 's', 32 ' ', 110 'n', 97 'a',
109 'm', 101 'e'}
}
arr = {
pData_ = std::vector of length 0, capacity 0
}
#11 0x77013a9d in Exiv2::PngImage::readMetadata (this=0x57170e90)
at /usr/src/debug/exiv2/exiv2-0.28.0/src/pngimage.cpp:435
chunkData = {
pData_ = std::vector of length 14, capacity 14 = {65 'A', 117 'u',
116 't', 104 'h', 111 'o', 114 'r', 39 '\'', 115 's', 32 ' ', 110 'n', 97 'a',
109 'm', 101 'e', 0 '\000'}
}
chunkLength = 14
chunkType = "tEXt"
closer = {
_vptr.IoCloser = 0x77155a10 ,
bio_ = @0x57043d40
}
imgSize = 151008
cheaderBuf = {
pData_ = std::vector of length 8, capacity 8 = {0 '\000', 0 '\000', 0
'\000', 14 '\016', 116 't', 69 'E', 88 'X', 116 't'}
}
#12 0x77dd805a in Gwenview::Exiv2ImageLoader::load
(this=0x7fffbb98, filePath=...) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/exiv2imageloader.cpp:88
filePathByteArray = {
d = 0x570fabe0
}
#13 0x77e1a683 in Gwenview::TimeUtils::CacheItem::updateFromExif
(this=this@entry=0x5706b9c8, url=...) at
/usr/src/debug/gwenview/gwenview-23.04.2/lib/timeutils.cpp:87
path = {
d = 0x570705a0
}
loader = {
d = 0x5700afb0
}
img =
[dolphin] [Bug 470161] New: Modifier keys during drag and drop operations don't work at all on Wayland
https://bugs.kde.org/show_bug.cgi?id=470161 Bug ID: 470161 Summary: Modifier keys during drag and drop operations don't work at all on Wayland Classification: Applications Product: dolphin Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: kdeb...@fratti.ch CC: kfm-de...@kde.org Target Milestone: --- SUMMARY No matter whether the modifier key is pressed before or during a drag and drop operation, dragging one file from one dolphin window to another dolphin window does not respect the modifier key at all. STEPS TO REPRODUCE 0. Use Wayland 1. Hold Ctrl 2. Drag file from one Dolphin window 3. drop it on another Dolphin window OBSERVED RESULT Dolphin pops up the unhelpful "here's the actions you could've used with a modifier key!" context menu EXPECTED RESULT Dolphin copies the files SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.5 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I'm using Wayland. No, this is not a duplicate of the bug where you have to hold the modifier key before starting the drag. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442232] On Wayland, Dolphin always sends WL_DATA_DEVICE_MANAGER_DND_ACTION_COPY even when holding Shift
https://bugs.kde.org/show_bug.cgi?id=442232 --- Comment #2 from Nicolas F. --- It's actually even more broken now despite the Qt thing being merged. Holding shift before the drag-and-drop operation no longer works either. I give up. Feel free to reopen, or don't, whatever makes you feel better, I no longer care. Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: LENOVO Product Name: 20NK000GMZ System Version: ThinkPad T495 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #9 from Nicolas F. --- Don't think that's the same bug, removing the ScreenMapping section from my appletsrc and restarting plasmashell does not resolve the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #7 from Nicolas F. --- (In reply to Nate Graham from comment #6) > Does KRunner also begin to consume excessive memory when you use KRunner to > search for "k"? No, KRunner continues to work as normal and does not consume excessive amounts of memory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #5 from Nicolas F. --- I did some more testing. plasmashell enters its broken memory-hogging non-application-launching state the moment I search for "k" in the application launcher. This happens with *all* search plugins disabled, i.e. no results being returned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #4 from Nicolas F. --- Here's another heaptrack that was captured from the moment plasmashell started, where it exhibits the same issue pretty much immediately. I don't know how to interpret the output, it doesn't *seem* to be tracking the actual problematic allocations, hinting at something more sinister: https://overviewer.org/~pillow/up/6c583e01f5/heaptrack.plasmashell.65921.zst As an aside node, my current plasmashell process is consuming 2 GiB of memory right now and also doesn't allow me to launch applications through the menu. It seems to get worse over time -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 --- Comment #2 from Nicolas F. --- No external monitors, AMD integrated GPU (Vega 8). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466261] New: plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs
https://bugs.kde.org/show_bug.cgi?id=466261 Bug ID: 466261 Summary: plasmashell suddenly consumes over 1 GiB of memory, no longer allows launching programs Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Created attachment 156615 --> https://bugs.kde.org/attachment.cgi?id=156615=edit heaptrack of plasmashell exhibiting the issue SUMMARY Something, not sure what, causes plasmashell to consume 1.3 GB of memory. Additionally, new programs can no longer be launched from the application launcher, showing the error "Resource error (fork failure): Cannot allocate memory" With the dmesg output: [ 1827.216162] __vm_enough_memory: pid: 3772, comm: plasmashell, no enough memory for the allocation This was not an issue in plasma 5.26, and started happening with 5.27.0 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.12 (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Heaptrack shows huge RSS size, but no specific allocation that caused the heap to grow so large. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 465867] Global Shortcuts: unable to snoop on key and all modifier combinations of key
https://bugs.kde.org/show_bug.cgi?id=465867 --- Comment #2 from Nicolas F. --- I don't think it is a problem in the protocol itself, nothing in it specifies that implementations should treat modifier keys in this way. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 465867] New: Global Shortcuts: unable to snoop on key and all modifier combinations of key
https://bugs.kde.org/show_bug.cgi?id=465867 Bug ID: 465867 Summary: Global Shortcuts: unable to snoop on key and all modifier combinations of key Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY For something like push-to-talk, one might want a dedicated button that works regardless of which other modifiers are being held. Say, the F13 key. To use the F13 key through the GlobalShortcuts portal in Mumble (using https://github.com/mumble-voip/mumble/pull/5976 ) I need to also bind Shift+F13, Alt+F13, Shift+Alt+F13, Ctrl+F13, ... etc. etc. This is extremely awkward, and we'd be better off with the implementation allowing for a flag to say "bind this key and any combinations of this key" STEPS TO REPRODUCE 1. Build Mumble with the GlobalShortcuts PR 2. Add a shortcut for some key 3. Press shift+that key OBSERVED RESULT Shortcut doesn't activate EXPECTED RESULT Shortcut has a flag to say "this key is the be all and end all of shortcuts and if it's pressed whoever listens to it gets told about it", and I get to push-to-talk SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.12 (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465566] New: Password entry field does not do focus stealing prevention
https://bugs.kde.org/show_bug.cgi?id=465566 Bug ID: 465566 Summary: Password entry field does not do focus stealing prevention Classification: Plasma Product: kscreenlocker Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch Target Milestone: --- SUMMARY In a multi-monitor setup, if one monitor takes longer to wake up than the other, kscreenlocker switches the focus from the password entry field to the new monitor during typing. This prevents me from inputting my password immediately after the primary monitor wakes up. STEPS TO REPRODUCE 1. Get two monitors, one of which wakes from sleep slower than the other 2. Wait for them to lock and fall asleep 3. Shake the mouse or whatever else to begin the wakeup, start typing in the password field OBSERVED RESULT Input focus switches to the secondary slower monitor as soon as it wakes up. EXPECTED RESULT Focus remains on the password field on the primary monitor that I'm typing into. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.10 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION An alternative solution would be an option to restrict the password entry for the lock screen to a specific monitor, so that the secondary monitor does not interfere. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464653] New: Dolphin crashed when clicked on in the task bar
https://bugs.kde.org/show_bug.cgi?id=464653
Bug ID: 464653
Summary: Dolphin crashed when clicked on in the task bar
Classification: Applications
Product: dolphin
Version: 22.12.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: kdeb...@fratti.ch
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (22.12.1)
Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.7-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.26.5 [KCrashBackend]
-- Information about the crash:
I clicked on Dolphin and it crashed with the following backtrace. All of plasma
seemed to restart. (Taskbar disappeared and reappeared)
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f0def0baa23 in QObject::property (this=this@entry=0x556f04486890,
name=name@entry=0x7f0df0e8ff96 "desktopFileName") at kernel/qobject.cpp:4123
#7 0x7f0df0e89b85 in KUiServerV2JobTracker::registerJob
(this=0x556f044850e0, job=) at
/usr/src/debug/kjobwidgets/kjobwidgets-5.102.0/src/kuiserverv2jobtracker.cpp:186
#8 0x7f0df0e86ae3 in operator() (__closure=0x556f04427ff0) at
/usr/src/debug/kjobwidgets/kjobwidgets-5.102.0/src/kuiserverv2jobtracker.cpp:227
#9 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KUiServerV2JobTracker::registerJob(KJob*):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor,
0>::call, void> (arg=, f=...) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#11
QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x556f04427fe0, r=, a=, ret=) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#12 0x7f0def0be931 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x7f0df0e97060
<_ZZN12_GLOBAL__N_117Q_QGS_serverProxy13innerFunctionEvE6holder.lto_priv.1>,
signal_index=3, argv=0x7fff7b196290) at kernel/qobject.cpp:3923
#14 0x7f0def0be931 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate (sender=0x556f03ba5040, signal_index=5,
argv=0x7fff7b1963b0) at kernel/qobject.cpp:3923
#16 0x7f0df0441e94 in QDBusServiceWatcher::serviceOwnerChanged
(this=this@entry=0x556f03ba5040, _t1=..., _t2=..., _t3=...) at
.moc/moc_qdbusservicewatcher.cpp:242
#17 0x7f0df0447b33 in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged
(this=, newOwner=..., oldOwner=..., service=...) at
/usr/src/debug/qt5-base/qtbase/src/dbus/qdbusservicewatcher.cpp:76
#18 QDBusServiceWatcher::qt_static_metacall (_o=_o@entry=0x556f03ba5040,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=3,
_a=_a@entry=0x7fff7b196530) at .moc/moc_qdbusservicewatcher.cpp:116
#19 0x7f0df0447e13 in QDBusServiceWatcher::qt_metacall
(this=0x556f03ba5040, _c=QMetaObject::InvokeMetaMethod, _id=3,
_a=0x7fff7b196530) at .moc/moc_qdbusservicewatcher.cpp:197
#20 0x7f0df044b45f in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) [clone .constprop.0]
(this=, object=, msg=..., metaTypes=...,
slotIdx=) at
/usr/src/debug/qt5-base/qtbase/src/dbus/qdbusintegrator.cpp:1001
#21 0x7f0def0b1a70 in QObject::event (this=0x556f03ba5040,
e=0x7f0de4010600) at kernel/qobject.cpp:1347
#22 0x7f0defd78b5c in QApplicationPrivate::notify_helper (this=, receiver=0x556f03ba5040, e=0x7f0de4010600) at
kernel/qapplication.cpp:3640
#23 0x7f0def08de08 in QCoreApplication::notifyInternal2
(receiver=0x556f03ba5040, event=0x7f0de4010600) at
kernel/qcoreapplication.cpp:1064
#24 0x7f0def08e913 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556f039c36a0) at
kernel/qcoreapplication.cpp:1821
#25 0x7f0def0d4d48 in postEventSourceDispatch (s=0x556f039ee170) at
kernel/qeventdispatcher_glib.cpp:277
#26 0x7f0ded26d87b in g_main_dispatch (context=0x7f0de4005010) at
../glib/glib/gmain.c:3454
#27 g_main_context_dispatch (context=0x7f0de4005010) at
../glib/glib/gmain.c:4172
#28 0x7f0ded2c4c89 in g_main_context_iterate.constprop.0
(context=0x7f0de4005010, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4248
#29 0x7f0ded26c132 in g_main_context_iteration (context=0x7f0de4005010,
may_block=1) at ../glib/glib/gmain.c:4313
#30 0x7f0def0d8b2c in QEventDispatcherGlib::processEvents
(this=0x556f039a0020, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#31 0x7f0def0865ac in
[xdg-desktop-portal-kde] [Bug 461697] New: Implement org.freedesktop.portal.Camera
https://bugs.kde.org/show_bug.cgi?id=461697 Bug ID: 461697 Summary: Implement org.freedesktop.portal.Camera Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeb...@fratti.ch CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY Please implement the org.freedesktop.portal.Camera portal. This portal allows PipeWire to choose cameras, which is important for the future when we're going to be doing multitasking (what an exciting new age) with cameras on Linux, which isn't possible with v4l2 but is possible with the PipeWire daemon wrapping it. One particular application that needs this portal is this obs fork: https://github.com/wtay/obs-studio/tree/pipewire-unified-dev -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440583] The editor window becomes unusable in wayland
https://bugs.kde.org/show_bug.cgi?id=440583 Nicolas F. changed: What|Removed |Added CC||kdeb...@fratti.ch -- You are receiving this mail because: You are watching all bug changes.
