[knotes] [Bug 475098] KNotes crashes on start
https://bugs.kde.org/show_bug.cgi?id=475098 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||knotes/-/commit/77b3810d64d ||ecd5da6a37b242867be3967208a ||8a Status|REPORTED|RESOLVED --- Comment #1 from Laurent Montel --- Git commit 77b3810d64decd5da6a37b242867be3967208a8a by Laurent Montel. Committed on 02/10/2023 at 07:23. Pushed by mlaurent into branch 'master'. Fix 475098:KNotes crashes on start M +1-1src/apps/knotesapp.cpp https://invent.kde.org/pim/knotes/-/commit/77b3810d64decd5da6a37b242867be3967208a8a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475013] Global menu prevents the panel to disappear when set to "windows can cover"
https://bugs.kde.org/show_bug.cgi?id=475013 Matthias changed: What|Removed |Added Component|Panel |Global Menu Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471248] plasmashell on Wayland crashed occasionally when playing Instagram story videos in Firefox
https://bugs.kde.org/show_bug.cgi?id=471248 --- Comment #6 from Matt Fagnani --- I saw this type of crash in Plasma 5.27.8 on Wayland in a Fedora 39 KDE Plasma installation with the same errors in the journal. An Instagram story video was stopping and the next one was starting in Firefox 120.0a1 on Wayland at the time of the crash. This crash is the first I've seen of this problem in the last 2-3 months, so the problem has been much less frequent than it was with 5.27.5. The problem might involve a race condition in which the media player applet was infrequently null then used or not as it was disappearing and reappearing when transitioning between videos. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474868] Plasma crashes when recovering from sleep state
https://bugs.kde.org/show_bug.cgi?id=474868 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Nate Graham --- Thanks for that gdb backtrace, it was much more helpful. There's good news and bad news. The good news is that the backtrace shown there is a known crash that's already been fixed! See 468430. The bad news is that it was supposed to be fixed in 5.27.5, and you're using 5.27.7. That leaves a few options for why you might still be seeing it: 1. I've mis-identified the crash and it's not actually Bug 468430 2. Debian made a packaging boo-boo and either isn't including the commits that fixed the crash (https://invent.kde.org/plasma/plasma-workspace/-/commit/acbc7234937027a6cf98b173517136d4bdbdfe94 and https://invent.kde.org/plasma/plasma-workspace/-/commit/9bea46b09e5d407697dc2cb660e72e0d538d482f) or is somehow re-introducing it with local patching of some kind 3. Bug 468430 isn't fully fixed, and you've found a new way to trigger it. For now I think #1 and #2 are the most likely scenario, but I judge #2 to be likelier at this point in time. At least, it's something we should rule out. Can you contact the Debian folks about it? Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474868] Plasma crashes when recovering from sleep state
https://bugs.kde.org/show_bug.cgi?id=474868 --- Comment #3 from sophi --- I got another crash (I get them about 10 a day :) ) Opened it myself with gdb and it got MUCH more information (gdb) bt #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at ./nptl/pthread_sigmask.c:43 #1 0x7f830585a6f9 in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7f83082bfe9b in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at ./src/kcrash.cpp:414 #3 0x7f83082c0b3e in KCrash::defaultCrashHandler(int) (sig=11) at ./src/kcrash.cpp:625 #4 0x7f830585a510 in () at /lib/x86_64-linux-gnu/libc.so.6 #5 QWeakPointer::internalData() const (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:702 #6 QPointer::data() const (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:77 #7 QPointer::operator QScreen*() const (this=0x60) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:83 #8 DesktopView::screenToFollow() const (this=0x0) at ./shell/desktopview.cpp:123 #9 0x561f18fb26d3 in ShellCorona::screenInvariants() const (this=0x7f82f0004bd0) at ./shell/shellcorona.cpp:828 #10 0x7f83060fba32 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff4317a890, r=0x7f82f0004bd0, this=0x561f1b26ac40) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x7f82f0004cf8, signal_index=3, argv=0x7fff4317a890) at kernel/qobject.cpp:3925 #12 0x7f83060f454f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f83063632e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4317a890) at kernel/qobject.cpp:3985 #13 0x7f83060ff85a in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #14 0x7f83060ef30b in QObject::event(QEvent*) (this=0x7f82f0004cf8, e=0x7fff4317a9e0) at kernel/qobject.cpp:1369 #15 0x7f8306f62d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7f82f0004cf8, e=0x7fff4317a9e0) at kernel/qapplication.cpp:3640 #16 0x7f83060c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7f82f0004cf8, event=0x7fff4317a9e0) at kernel/qcoreapplication.cpp:1064 #17 0x7f83060c329e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #18 0x7f830611bcc9 in QTimerInfoList::activateTimers() (this=0x561f1af03d40) at kernel/qtimerinfo_unix.cpp:643 #19 0x7f830611c574 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=) at kernel/qeventdispatcher_glib.cpp:183 #20 0x7f8304a6d1b4 in g_main_dispatch (context=context@entry=0x561f1af04ad0) at ../../../glib/gmain.c:3476 #21 0x7f8304a702d7 in g_main_context_dispatch_unlocked (context=0x561f1af04ad0) at ../../../glib/gmain.c:4284 #22 g_main_context_iterate_unlocked (context=context@entry=0x561f1af04ad0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4349 #23 0x7f8304a708f0 in g_main_context_iteration (context=0x561f1af04ad0, may_block=1) at ../../../glib/gmain.c:4414 #24 0x7f830611c8d6 in QEventDispatcherGlib::processEvents(QFlags) (this=0x561f1af03e80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #25 0x7f83060c1b7b in QEventLoop::exec(QFlags) (this=this@entry=0x7fff4317ac20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #26 0x7f83060ca020 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #27 0x7f830653258c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1863 #28 0x7f8306f62ca5 in QApplication::exec() () at kernel/qapplication.cpp:2832 #29 0x561f18f82db4 in main(int, char**) (argc=, argv=) at ./shell/main.cpp:235 (gdb) print *(class ShellCorona*)0x7f82f0004bd0 $1 = { = { = {_vptr.QObject = 0x561f190154c0 , static staticMetaObject = {d = {superdata = {direct = 0x0}, stringdata = 0x7f83062969c0 , data = 0x7f83062968a0 , static_metacall = 0x7f83060f9910 , relatedMetaObjects = 0x0, extradata = 0x0}}, d_ptr = {d = 0x561f1b26b7f0}, static staticQtMetaObject = { d = {superdata = {direct = 0x0}, stringdata = 0x7f8306299960 , data = 0x7f8306296ae0 , static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static staticMetaObject = {d = {superdata = {direct = 0x7f830635a180 }, stringdata = 0x7f83084def80 , data = 0x7f83084dec20 , static_metacall = 0x7f83084894a0 , relatedMetaObjects = 0x0, extradata = 0x0}}, d = 0x561f1b269370}, = {d_ptr = 0x0}, static staticMetaObject = {d = {superdata = {direct = 0x7f83084fec80 }, stringdata = 0x561f18ff9960 , data = 0x561f18ff9360 , static_metacall = 0x561f18fbde10 , relatedMetaObjects = 0x0, extradata = 0x0}}, m_config = {d = 0x561f1b2ae890}, m_configPath = {d = 0x561f1b406d10}, m_accentColorConfigWatcher = {value = 0x561f1b352830, d =
[Spectacle] [Bug 473793] High contrast when taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=473793 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472980] Plasmashell crashes sometimes when clearing the clipboard
https://bugs.kde.org/show_bug.cgi?id=472980 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474420] systemsettings drops a shortcut
https://bugs.kde.org/show_bug.cgi?id=474420 --- Comment #3 from b...@whitleymott.net --- how might i reset to default shortcut settings? and how might i save and restore either all shortcut settings or all kwin shortcut settings? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474868] Plasma crashes when recovering from sleep state
https://bugs.kde.org/show_bug.cgi?id=474868 --- Comment #2 from sophi --- Is there something I can do to help to solve the issue? I feel it might be related to multi-monitor setup, particularly display port 4K monitor that has another monitor connected to it (display port carries two signals). So when system wakes up from suspend (either monitor off or from S3 I think), plasma often crashes. I don't know why in the stack trace the same .so library method sometimes is resolved and sometimes is not. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 475123] Specific flatpak applications cannot be launched through krunner if DBusActivatable=true
https://bugs.kde.org/show_bug.cgi?id=475123 g311571...@gmail.com changed: What|Removed |Added CC||g311571...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 475123] New: Specific flatpak applications cannot be launched through krunner if DBusActivatable=true
https://bugs.kde.org/show_bug.cgi?id=475123 Bug ID: 475123 Summary: Specific flatpak applications cannot be launched through krunner if DBusActivatable=true Classification: Plasma Product: krunner Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: g311571...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY dconf flatpak version can't launch through krunner and complains "Invalid object path: /ca/desrt/dconf-editor ". But it can be start normally through commndline or Kickoff STEPS TO REPRODUCE 1. Keep DBusActivatable=true in dconf desktop entry which is by default 2. Open krunner and search donf 3. launch it OBSERVED RESULT "Invalid object path: /ca/desrt/dconf-editor ", and launch fail EXPECTED RESULT launch normally SOFTWARE/OS VERSIONS (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Arch linux X11 When I set `DBusActivatable=false` everything will be fine. And this bug only happen on krunner. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475122] need file info even collection is offline
https://bugs.kde.org/show_bug.cgi?id=475122 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Media CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Alex Lieflander changed: What|Removed |Added CC||pub...@atlief.com --- Comment #26 from Alex Lieflander --- (In reply to Dm from comment #23) > (kubuntu 22.04, plasma 5.24.7, KDE Frameworks 5.92.0, QT 5.15.3, X11) > There is a little hack: even when screen is locked, keyboard shortcuts are > still available. So you can go to settings -> shortcuts -> power -> suspend > (or hibernate) -> assign a new shortcut -> push power button (agree reassign) > Now suspend (or hibernate) works in every case (logged in or lockscreen) Another workaround is to use the "tiny-power-button" Linux kernel module. This module waits for power button presses (like the "button" module that most desktop environments use), but instead of sending the event to user-space it directly sends a shutdown signal to your init manager. This completely bypasses KDE-Plasma and thus allows the power button to work while the screen is locked. Note: 1. Your kernel must have been compiled with the tiny-power-button module 2. Your init manager must support shutdown signals 3. This module only waits for power button presses 4. If compiled as a module, tiny-power-button must be loaded on every boot 5. The button module must not be loaded before or after the tiny-power-button module is loaded 6. If the button module was compiled directly into the kernel you may need to do other modifications The relevant Kconfig option for note 1 is CONFIG_ACPI_TINY_POWER_BUTTON=m or CONFIG_ACPI_TINY_POWER_BUTTON=y. By default, the signal used in note 2 is different than SIGTERM and friends, and causes a graceful shutdown. Most init managers (like SystemD) support it, but you could theoretically use another signal at the risk of data loss. Due to note 3, events like closing the lid wouldn't work and thus this workaround may not be suitable for laptops. Note 4 can be achieved on most systems by adding "tiny-power-button" to /etc/modules. Note 5 can be achieved on most systems by adding "blacklist button" to /etc/modprobe.d/blacklist.conf. The problematic Kconfig option in note 6 would be CONFIG_ACPI_BUTTON=y, however you might still be able to use this workaround by adding additional boot arguments. -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 475121] Importing a playlist causes an immediate application crash
https://bugs.kde.org/show_bug.cgi?id=475121 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475122] New: need file info even collection is offline
https://bugs.kde.org/show_bug.cgi?id=475122 Bug ID: 475122 Summary: need file info even collection is offline Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: shikai...@hotmail.com Target Milestone: --- Created attachment 162017 --> https://bugs.kde.org/attachment.cgi?id=162017=edit screenshot SUMMARY *** I have multiple collections from removable/smb location, and they are not always connected/online. When I manage photos, I don't even view them (preview the photo/video). At Thumbnails view, I can just select photos and assign tags/ratings etc. This can be done when collections is offline, which is a great feature. But amone the vast amount of photos, There's no way to know info. where the file location is or which collection it belongs to, when the collection of the photo is offline(see attachment). Wish-feature is, to display infomation where the file path is, or from which collection it belongs to, when its collection is offline. *** Thanks! -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 475121] New: Importing a playlist causes an immediate application crash
https://bugs.kde.org/show_bug.cgi?id=475121 Bug ID: 475121 Summary: Importing a playlist causes an immediate application crash Classification: Applications Product: audiotube Version: 23.08.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: smste...@proton.me Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When attempting to import a playlist from YouTube/YouTube Music, Audiotube crashes and closes immediately. A split second before the crash, an empty playlist called "Unknown" is created, and then the entire application crashes. Looking at the output of `flatpak run org.kde.audiotube` shows this at the moment of the crash: futuresql: Running "select video_id from playlist_entries where playlist_id = ? order by random() limit 4" Exception: Server returned HTTP 400: Bad Request. Request contains an invalid argument. At: /app/lib/python3.10/site-packages/ytmusicapi/ytmusic.py(142): _send_request /app/lib/python3.10/site-packages/ytmusicapi/mixins/playlists.py(109): get_playlist STEPS TO REPRODUCE 1. Open Audiotube, either via `flatpak run org.kde.audiotube` or via rofi 2. Attempt to import a playlist with the URL generated by YouTube/YouTube Music 3. App crashes immediately after creating empty "Unknown" playlist OBSERVED RESULT Audiotube creates an empty playlist called "Unknown" and then immediately force closes EXPECTED RESULT The playlist will be created inside Audiotube from the shareable link generated from YouTube/YouTube Music SOFTWARE/OS VERSIONS Arch Linux Hyprland Audiotube 23.08.1 flatpak from Flathub KDE Application Platform branch 5.15-22.08 from Flathub ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474508] Almost completely black screen after waking up from screen energy saving
https://bugs.kde.org/show_bug.cgi?id=474508 --- Comment #6 from nkwkel...@gmail.com --- (In reply to nkwkelvin from comment #4) > (In reply to Nate Graham from comment #3) > > If you right-click on the black background, what happens? > > > > If you hit Alt+F2 to bring up KRunner, type "plasmashell" and hit enter, > > what happens? > > > > If that doesn't do anything, does anything happen if instead you enter > > "plasmashell --replace"? > > I forgot to try right-click last time this issue happens. I will try next > time. > > I tried Alt+F2 but I can't see KRunner. But I still type plasmashell and > plasmashell --replace and hit enter, but nothing happens. > > I also tried going to a Konsole (by using the working upper left corner > thing) and run plasmashell and plasmashell --replace, but still nothing > happens. I tried right-click but nothing shows up. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 475120] Pages blanking or losing content (nytimes.com)
https://bugs.kde.org/show_bug.cgi?id=475120 --- Comment #1 from yellowherr...@tutanota.com --- Qt version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 475120] New: Pages blanking or losing content (nytimes.com)
https://bugs.kde.org/show_bug.cgi?id=475120 Bug ID: 475120 Summary: Pages blanking or losing content (nytimes.com) Classification: Applications Product: Falkon Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: yellowherr...@tutanota.com Target Milestone: --- Pages on the New York Times' website render normally for a second or two after loading, but then either completley blank to white or cut out a portion of the page. Examples: https://www.nytimes.com (top portion cut off) https://www.nytimes.com/section/world (entire page blanks) https://www.nytimes.com/spotlight/pop-culture (entire body cut off) https://www.nytimes.com/2023/10/01/us/politics/mccarthy-speaker-gaetz.html (top portion cut off) https://www.nytimes.com/activate-access/digitalpass (entire page blanks) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466124] kmail preview pane empty on wayland nvidia
https://bugs.kde.org/show_bug.cgi?id=466124 younker...@gmail.com changed: What|Removed |Added CC||younky.y...@yahoo.com --- Comment #3 from younker...@gmail.com --- I have this same issue on Gentoo with the latest plasma, kde-frameworks and kmail. Although I can go to settings to close the preview then open it, but when I restart kmail. the preview panel is empty again. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 475119] Google Login does not work, loads endlessly
https://bugs.kde.org/show_bug.cgi?id=475119 --- Comment #1 from Steve Cossette --- Not sure if it helps, but when I try to add an account, I see this message in the system logs: Oct 01 19:31:13 fedora-laptop signon-ui[96043]: QIODevice::read (QFile, "/home/farchord/.cache/signon-ui/cookies/6.jar"): device not open Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Email]" Oct 01 19:31:14 fedora-laptop signon-ui[96043]: browser-request.cpp 738 initializeField Couldn't find element: "input[name=Passwd]" -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 475119] New: Google Login does not work, loads endlessly
https://bugs.kde.org/show_bug.cgi?id=475119 Bug ID: 475119 Summary: Google Login does not work, loads endlessly Classification: Frameworks and Libraries Product: KAccounts Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: farch...@gmail.com CC: ad...@leinir.dk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When I add a Google account under Settings -> Personalization -> Online accounts, after adding the e-mail address, the page just loads endlessly without going to the password entry page. STEPS TO REPRODUCE 1. Open the KDE settings 2. Go to Personalization -> Online accounts 3. Add a Google account, and enter a google email. Click next. OBSERVED RESULT Page just loads endlessly without going to password EXPECTED RESULT The password entry field should then show SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics Memory: 30.3 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475117] Built against qt6 version: various errors, menu and dialog glitches
https://bugs.kde.org/show_bug.cgi?id=475117 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475115] baloo_file crashes every start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475115 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475118] New: The PIM plugin of the Digital Clock widget causes plasmasheel to crash when enabled
https://bugs.kde.org/show_bug.cgi?id=475118 Bug ID: 475118 Summary: The PIM plugin of the Digital Clock widget causes plasmasheel to crash when enabled Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: paul.br...@kde.org Target Milestone: 1.0 SUMMARY Enabling the PIM plugin in the Digital Clock configutarion cause plasmashell to crash. b) bt #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at pthread_sigmask.c:43 #1 0x7f4fa585c90d in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7f4fa808927b in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash5/kcrash-5.110.0/src/kcrash.cpp:419 #3 0x7f4fa808b886 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash5/kcrash-5.110.0/src/kcrash.cpp:630 #4 0x7f4fa585c710 in () at /usr/lib/libc.so.6 #5 0x7f4fa60d065f in doActivate(QObject*, int, void**) (sender=0x559896673fe0, signal_index=4, argv=0x7ffc606d5be0) at kernel/qobject.cpp:3957 #6 0x7f4fa4eed6a4 in QQmlDelegateModelItem::rowChanged() (this=0x559896673fe0) at .moc/moc_qqmldelegatemodel_p_p.cpp:221 #7 QQmlDelegateModelItem::setModelIndex(int, int, int, bool) (this=0x559896673fe0, idx=, newRow=, newColumn=, alwaysEmit=false) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:2433 #8 0x7f4fa4eeae19 in QQmlDelegateModel::_q_itemsInserted(int, int) (this=, index=0, count=27) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1609 #9 0x7f4fa4ef35c3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x559895831180, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7ffc606d5e00) at .moc/moc_qqmldelegatemodel_p.cpp:371 #10 0x7f4fa60d076f in doActivate(QObject*, int, void**) (sender=0x559895831930, signal_index=13, argv=0x7ffc606d5e00) at kernel/qobject.cpp:3951 #11 0x7f4fa6057403 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x559895831930, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592 #12 0x7f4fa6057567 in QAbstractItemModel::endInsertRows() (this=0x559895831930) at itemmodels/qabstractitemmodel.cpp:2780 #13 0x7f4fa607574e in QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) (this=this@entry=0x559895831a30, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=) at itemmodels/qsortfilterproxymodel.cpp:950 #14 0x7f4fa6075ce1 in QSortFilterProxyModelPrivate::handle_filter_changed(QVector&, QVector&, QModelIndex const&, Qt::Orientation) (this=this@entry=0x559895831a30, source_to_proxy=..., proxy_to_source=..., source_parent=..., orient=orient@entry=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1376 #15 0x7f4fa6076120 in QSortFilterProxyModelPrivate::filter_changed(QModelIndex const&) (this=0x559895831a30, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:1305 #16 0x7f4fa6083a92 in QSortFilterProxyModel::setFilterFixedString(QString const&) (this=, pattern=) at itemmodels/qsortfilterproxymodel.cpp:2882 #17 0x7f4fa60851f3 in QSortFilterProxyModel::qt_metacall(QMetaObject::Call, int, void**) (this=this@entry=0x559895831930, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=12, _a=_a@entry=0x7ffc606d63c0) at .moc/moc_qsortfilterproxymodel.cpp:429 #18 0x7f4ec001944a in KSortFilterProxyModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x559895831930, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7ffc606d63c0) at /usr/src/debug/kitemmodels5/build/src/qml/itemmodelsplugin_autogen/include/moc_ksortfilterproxymodel.cpp:349 #19 0x7f4fa76784b4 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=0x7ffc606d6660, type=QMetaObject::InvokeMetaMethod, index=, argv=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectorgadget.cpp:51 #20 0x7f4fa7578ac1 in CallMethod (callType=, callArgs=, engine=, argTypes=, argCount=, returnType=, index=, object=) at /usr/include/qt/QtCore/qvarlengtharray.h:189 #21 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=, data=, engine=, callArgs=, callType=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:1553 #22 0x7f4fa757def6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const (this=, thisObject=0x7f4f803bb538, argv=, argc=1) at
[frameworks-baloo] [Bug 475115] baloo_file crashes every start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475115 Piotr Mierzwinski changed: What|Removed |Added Keywords||qt6 CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475117] Built against qt6 version: various errors, menu and dialog glitches
https://bugs.kde.org/show_bug.cgi?id=475117 --- Comment #2 from accou...@kuchenmampfer.de --- Created attachment 162016 --> https://bugs.kde.org/attachment.cgi?id=162016=edit Info dialog text overflow with konsole output -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475117] Built against qt6 version: various errors, menu and dialog glitches
https://bugs.kde.org/show_bug.cgi?id=475117 --- Comment #1 from accou...@kuchenmampfer.de --- Created attachment 162015 --> https://bugs.kde.org/attachment.cgi?id=162015=edit Broken PlaybackRateCustomizerDialog with console output -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 475116] Opening new tab fails, if current tab is root shell
https://bugs.kde.org/show_bug.cgi?id=475116 FirstAirBender changed: What|Removed |Added Summary|Opening new tab if current |Opening new tab fails, if |tab is root, fails |current tab is root shell -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475117] New: Built against qt6 version: various errors, menu and dialog glitches
https://bugs.kde.org/show_bug.cgi?id=475117 Bug ID: 475117 Summary: Built against qt6 version: various errors, menu and dialog glitches Classification: Applications Product: kasts Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: accou...@kuchenmampfer.de Target Milestone: --- SUMMARY *** Today, I built Kasts from source against qt6 in order to explore it and find bugs. I found a few things: 1. The "show episode info" dialog has text flowing outside of the dialog (below it) when opened for the first time after app launch 2. The "chapters" dialog is incredibly slow to open and induces heavy load on the cpu 3. The "more actions" menu popup on the "subscriptions" page changes its width when the mouse enters its area 4. The `customizeRatesDialog` is too small, the grid of current playback rate options is cut off 5. That same dialog can also neither be moved nor resized, but that is already an issue in the current release 6. When using touchpad scroll to increase the volume to 100%, lifting the fingers from the touchpad resets the volume to 90%. This might have been introduced by myself, I will see if I can figure out what causes it. 7. On the console, I get these following errors many times and in different variations: ``` qrc:/PlaybackRateMenu.qml:43: TypeError: Passing incompatible arguments to C++ functions from JavaScript is not allowed. "Could not convert argument 0 at" "@qrc:/PlaybackRateMenu.qml:43" "resetModel@qrc:/PlaybackRateMenu.qml:63" "expression for onAccepted@qrc:/PlaybackRateMenu.qml:82" "expression for onAccepted@file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:501" qrc:/PlaybackRateMenu.qml:43: TypeError: Passing incompatible arguments to C++ functions from JavaScript is not allowed. file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:386:37: QML Binding: Binding loop detected for property "value" qrc:/PlaybackRateMenu.qml:77:9: QML PlaybackRateCustomizerDialog: Binding loop detected for property "implicitHeight" qrc:/qt/qml/org/kde/desktop/Menu.qml:37:18: QML ListView: Binding loop detected for property "implicitWidth" qt.qml.context: qrc:/FeedListDelegate.qml:104:9 Parameter "mouse" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead. QSGPlainTexture: Mipmap settings changed without having image data available. Call setImage() again or enable m_retain_image. Falling back to previous mipmap filtering mode. ``` *** STEPS TO REPRODUCE 1. build Kasts from source against qt6 using kdesrc-build 2. run it from the terminal and explore the UI SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon distrobox running on top of Crystal Linux KDE Plasma Version: master KDE Frameworks Version: master - 5.111.0 I *think* Qt Version: 6.6 ADDITIONAL INFORMATION Not pressing, just things to have on the radar to fix before the plasma 6 release. When I looked at some of the related the Kasts QML code, it seemed fine, so I guess at least some of these issues lie in underlying technologies/frameworks. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 475116] New: Opening new tab if current tab is root, fails
https://bugs.kde.org/show_bug.cgi?id=475116 Bug ID: 475116 Summary: Opening new tab if current tab is root, fails Classification: Applications Product: yakuake Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: noblech...@web.de Target Milestone: --- Created attachment 162014 --> https://bugs.kde.org/attachment.cgi?id=162014=edit This is what I see when I open a new tab from a tab which is root 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 a tab, and type `sudo -i` 2. From that tab, open a new tab 3. OBSERVED RESULT New tab fails with permission errors. Furthermore, when I exit the root shell in that tab, any further attempts to open a new tab still fails with the same error. EXPECTED RESULT A new tab should open as usual to the user's home directory SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475115] New: baloo_file crashes every start of Plasma
https://bugs.kde.org/show_bug.cgi?id=475115 Bug ID: 475115 Summary: baloo_file crashes every start of Plasma Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY Since some time I experience crash of baloo_file everytime when I login to Plasma. I have installed dbg symbols package: "kf6-baloo-dbgsym/jammy,now 0.0+p22.04+vunstable+git20230926.0255-0 amd64 [installed]" Below please find backtrace: Application: baloo_file (baloo_file), signal: Aborted PID: 1196 (baloo_file) UID: 1000 (piotr) GID: 1001 (piotr) Signal: 6 (ABRT) Timestamp: Mon 2023-10-02 00:49:02 CEST (1min 51s ago) Command Line: /usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file Executable: /usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service Unit: user@1000.service User Unit: kde-baloo.service Slice: user-1000.slice Owner UID: 1000 (piotr) Boot ID: 3a51bae2aabe4254af6ad76748f6bef7 Machine ID: 29636ac4c94e4738937d6efc05c8378c Hostname: Dell Storage: /var/lib/systemd/coredump/core.baloo_file.1000.3a51bae2aabe4254af6ad76748f6bef7.1196.169620054200.zst (present) Disk Size: 663.6K Message: Process 1196 (baloo_file) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: ad925365535dffe43427fe70542f12e0575bceec Found module libmd.so.0 with build-id: cd2d2f71b3967ebde30e2aa43b8eb63339020c06 Found module libgpg-error.so.0 with build-id: 3fbec71c67bee60d8aef00697ee187079b0fb307 Found module libbsd.so.0 with build-id: 9a6c72469251e2feb63e175ef5cb944ce6e00df3 Found module libbrotlicommon.so.1 with build-id: 43a72967cf84155914c8b3e915926733d1e57c11 Found module libgcrypt.so.20 with build-id: 60a5e524de0ed8323edf33e9eb9127a9eee02359 Found module libcap.so.2 with build-id: b4bf900abf14aabe12d90988ceb30888acb2bcb0 Found module liblz4.so.1 with build-id: a85971851cd059f1af80d553c8e7170d42ec59a1 Found module liblzma.so.5 with build-id: b85da6c48eb60a646615392559483b93617ef265 Found module libXdmcp.so.6 with build-id: 6b60f99504aa1d3999ea02a14366d1a39d6c5dcf Found module libXau.so.6 with build-id: 7089b383cacbfc1760634a3be19a923e51fe3315 Found module libbrotlidec.so.1 with build-id: 4b1f390dd6e24d49684db8b2443d082379e8e977 Found module libgraphite2.so.3 with build-id: 5ffbc76fc948f6b88d766a7210c2e6a329a6c278 Found module libuuid.so.1 with build-id: 64c0d0cb22fa2bdeca075a0c0418ba5ff314b220 Found module libexpat.so.1 with build-id: d212d1f61d04a1e60fccad1a8c118428cfd9be42 Found module libGLdispatch.so.0 with build-id: 19c339ecd74c020f1db1342213a07114f4baf5e0 Found module libgomp.so.1 with build-id: 9c1fa6c4f40f1192c0551f60641f00130510f24d Found module libpcre.so.3 with build-id: 3982f316c887e3ad9598015fa5bae8557320476a Found module libicudata.so.70 with build-id: b1c2496dd0543023c7a19c961bb7f3abc818f465 Found module libsystemd.so.0 with build-id: 75127719050b94774f76b6d153ad298b35f7a5f7 Found module libxcb.so.1 with build-id: 1bef862a339557aa16c34c7a4b27f8f3aea90517 Found module libfam.so.0 with build-id: e4f407bf295eff27ead40bad4bf9467ff9a571bf Found module libfreetype.so.6 with build-id: bc6c65a19e6f75fea5e74a7fd6c0b91182e1a8b0 Found module libmd4c.so.0 with build-id: 2d23f4702a68dc317e32ce7a3e41e0fa7ba93215 Found module libharfbuzz.so.0 with build-id: 57a633dece9f1faaeff35ece444829cd744a931e Found module libpng16.so.16 with build-id: d58bf7c11ac793d528926238d831792b5ef792cf Found module libOpenGL.so.0 with build-id: 19bb1d13712da197419d0359c3796da1f040e7dd Found module libGLX.so.0 with build-id: ac8b68a74f1ead77477f89bc98998ecb064e3ae5 Found module libxkbcommon.so.0 with build-id: a4b17d939092101dc8f6b2a1d70eaf1fddb2dd51 Found module libfontconfig.so.1 with build-id: 0bb435fdd5ec37178e14ea03bb36f779a4b72a94 Found module libEGL.so.1 with build-id: 236d96c92ee2914a0e90e06e01b79dfcba0f7b41 Found module ld-linux-x86-64.so.2 with build-id: 3146e5a5e66e1fd6ab59a39e486a9d246bc675c0 Found module libgcc_s.so.1 with build-id:
[valgrind] [Bug 461074] DWARF2 CFI reader: unhandled DW_OP_ opcode 0x11 (consts) and DW_OP_ opcode 0x92 (bregx)
https://bugs.kde.org/show_bug.cgi?id=461074 Mark Wielaard changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Summary|valgrind: |DWARF2 CFI reader: |m_debuginfo/readdwarf.c:239 |unhandled DW_OP_ opcode |6 |0x11 (consts) and DW_OP_ |(copy_convert_CfiExpr_tree) |opcode 0x92 (bregx) |: Assertion 'srcix >= 0 && | |srcix < VG_(sizeXA)(srcxa)' | |failed. | --- Comment #10 from Mark Wielaard --- Thanks, that implementation of DW_OP_bregx is almost literally the same as what I came up with. I also implemented DW_OP_consts, which was reported in comment #1. And DW_OP_const8s, DW_OP_const8u and DW_OP_constu since they are fairly similar and were also missing. commit 9dd5db3cb1c46c50d29bf11a495a77e2669b847a Author: Mark Wielaard Date: Mon Oct 2 00:37:24 2023 +0200 Implement DW_OP_{bregx,consts,const8s,const8u,constu} in dwarfexpr_to_dag readdwarf.c (dwarfexpr_to_dag) didn't hanle various DW_OP expressions causing Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode and errors m_debuginfo/readdwarf.c:2822 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. Implement DW_OP_bregx and DW_OP_consts as reported in bug #461074. Also add implementations for DW_OP_const8s, DW_OP_const8u and DW_OP constu. https://bugs.kde.org/show_bug.cgi?id=461074 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475114] New: Make fully KDE to run on dedicated card
https://bugs.kde.org/show_bug.cgi?id=475114 Bug ID: 475114 Summary: Make fully KDE to run on dedicated card Classification: Plasma Product: kwin Version: 5.27.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: pentelja...@o2.pl Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Instead of asking on forum i would like to ask directly developers, how to enable fully on SDDM AND KDE itself dedicated card. https://discuss.kde.org/t/how-to-make-nvidia-the-default-card-on-wayland/5233 *** STEPS TO REPRODUCE None, since theres no guide or none working. OBSERVED RESULT ubuntu tool to swap between driver versions fucks up as always, manually installed direct from nvidia site doesnt work, nvidia-smi dont see anything, or uselessly running xorg. without any other programs which should EXPECTED RESULT Run full power on dedicated card let it be used and use its computing power SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 23.04 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION ``` lsd@lsd-Crawler-E25:~$ cat /etc/environment PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" #KWIN_DRM_DEVICES="/dev/dri/card1:/dev/dri/card0" #GBM_BACKEND=nvidia-drm #[D__GLX_VENDOR_LIBRARY_NAME=nvidia #ENABLE_VKBASALT=1 #LIBVA_DRIVER_NAME=nvidial``` without hashes crashes all -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 475113] Switch from Pastebin to similar service
https://bugs.kde.org/show_bug.cgi?id=475113 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 475113] New: Switch from Pastebin to similar service
https://bugs.kde.org/show_bug.cgi?id=475113 Bug ID: 475113 Summary: Switch from Pastebin to similar service Classification: Frameworks and Libraries Product: frameworks-purpose Version: 5.110.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: popov...@ukr.net Target Milestone: --- SUMMARY Currently, Pastebin has a limitation: guests can create up to 10 new pastes per 24 hours.. Therefore, Plasma also has a limitation of 10 inserts per 24 hours for all users combined. IMHO it makes sense to switch from Pastebin to another similar service. I can recommend dpaste.com (https://dpaste.com/api/v2/), as it has a simple API, has no restrictions on the number of pastes and doesn't require any API keys. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230828 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 --- Comment #42 from Lukáš Turek <8...@8an.cz> --- Unfortunately you're right, it didn't help, it really seems the RFC8308 extension is needed, which requires MINA SSHD version 2.3.0 or later. Do we really need to use RSA for client authentication? Or could the KDE Connect client (Linux app) also switch to an ECDSA key? The error "no mutual signature algorithm" does not appear when I try to send my ECDSA public key: debug1: Next authentication method: publickey debug1: Offering public key: id_rsa RSA SHA256:En18wk81oylB2/tXALRVR665pvuP3XHZOVUdTWnZ06w agent debug1: send_pubkey_test: no mutual signature algorithm debug1: Offering public key: id_ecdsa ECDSA SHA256:JL1U9qfHt51GmmiT41JB9WDRDP4cWWA8H/boCR08qCU explicit debug2: we sent a publickey packet, wait for reply -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes in QWidgetLineControl::internalSetText() after saving and reediting the item
https://bugs.kde.org/show_bug.cgi?id=466164 --- Comment #9 from Lennart Rosam --- (In reply to Lennart Rosam from comment #8) > Created attachment 162013 [details] > New crash information added by DrKonqi > > kmenuedit (5.27.8) using Qt 5.15.10 > > I tried editing the Menu entry for 1Password. Here's the 1password.desktop > file that caused the crash for me: > > [Desktop Entry] > Name=1Password > Exec=/opt/1Password/1password --ozone-platform-hint=auto %U > Terminal=false > Type=Application > Icon=1password > StartupWMClass=1Password > Comment=Password manager and secure wallet > MimeType=x-scheme-handler/onepassword; > Categories=Office; > > -- Backtrace (Reduced): > #4 0x7f98add0d9d4 in QWidgetLineControl::internalSetText(QString > const&, int, bool) () from /lib64/libQt5Widgets.so.5 > #5 0x55636d72563c in BasicTab::setEntryInfo (this=0x55636ee996b0, > entryInfo=0x55636f0d7ea0) at > /usr/src/debug/kmenuedit-5.27.8-1.fc38.x86_64/basictab.cpp:382 > #6 0x7f98acee8608 in doActivate (sender=0x55636ee634d0, > signal_index=27, argv=0x7ffec390ff80) at kernel/qobject.cpp:3937 > [...] > #8 0x55636d72c378 in TreeView::entrySelected (_t1=, > this=0x55636ee634d0) at > /usr/src/debug/kmenuedit-5.27.8-1.fc38.x86_64/redhat-linux-build/ > kmenuedit_autogen/EWIEGA46WW/moc_treeview.cpp:250 > #9 TreeView::itemSelected (this=0x55636ee634d0, item=0x55636f115d50) at > /usr/src/debug/kmenuedit-5.27.8-1.fc38.x86_64/treeview.cpp:642 Update: Turns out, the desktop file I originally posted (from /usr/share/applications) was not the culprit. I edited the shortcut before and a file was created under ~/.local/share/applications. Removing the file fixes the crash. Here's the content of the file: [Desktop Entry] Categories=Office; Comment=Password manager and secure wallet Exec='/opt/1Password/1password --ozone-platform-hint=auto' Icon=1password MimeType=x-scheme-handler/onepassword; Name=1Password NoDisplay=false Path= StartupNotify=true StartupWMClass=1Password Terminal=false TerminalOptions= Type=Application X-KDE-SubstituteUID=false X-KDE-Username= So to reproduce, put the file contents from comment #8 into /usr/share/applications/1password.desktop and the contents of the file above into ~/.local/share/applications/1password.desktop. Then try to edit the 1Password application under "Office". -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] kmenueditor crashes in QWidgetLineControl::internalSetText() after saving and reediting the item
https://bugs.kde.org/show_bug.cgi?id=466164 Lennart Rosam changed: What|Removed |Added CC||register+kdeb...@signup.tak ||uto.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475112] New: Brush outline not rendering if brush tip 100% white
https://bugs.kde.org/show_bug.cgi?id=475112 Bug ID: 475112 Summary: Brush outline not rendering if brush tip 100% white Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: aiena.makehu...@gmail.com Target Milestone: --- SUMMARY *** Brush outline does not render if brush pixels are white. *** STEPS TO REPRODUCE 1. Make sure that brush outlines (Configure Krita -> General-> Brush Outline Shape) is enabled. Can be either circle/preview outline. (behavior reproducible in either) 2. Create a 1024x1024 image 3. delete the background so it is transparent 4. draw and fill a white colored circle 5. export image as a .png 6. Now in the brush editor import the above image as a predefined brush tip 7. with it active hover over the canvas area to see if outline is shown. OBSERVED RESULT No outline shown if the texture color is white. EXPECTED RESULT I expected the transparency to create the brush tip outline. Additional info: If you use any other color instead of white with transparency the brush outline seems to show up fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 bndksz...@gmail.com changed: What|Removed |Added CC||bndksz...@gmail.com --- Comment #68 from bndksz...@gmail.com --- I have the same problem Distro: Arch Kernel: 6.5.5-arch1-1 Desktop: Plasma 5.27.8 Wayland GPU: Nvidia RTX 2060 with 535.113.01-2 driver -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 463322] The Dashboard and accounts screen are showing the £ at the end instead of the beginning of the amount ie:- 100£ instead of £100 for every column.
https://bugs.kde.org/show_bug.cgi?id=463322 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #9 from Stephane MANKOWSKI --- This seems to be due to flatpak. You can find some information here: https://github.com/flatpak/flatpak/issues/3712 I close this ticket because this is not a bug in skrooge code. Regards. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475111] New: Pen stroke lacks pressure and has significant delay on first stroke if under filter layer.
https://bugs.kde.org/show_bug.cgi?id=475111 Bug ID: 475111 Summary: Pen stroke lacks pressure and has significant delay on first stroke if under filter layer. Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- Created attachment 162012 --> https://bugs.kde.org/attachment.cgi?id=162012=edit Filter layer bug example file SUMMARY After moving the canvas in any way, (panning, zooming, rotating), the first and only the first brush stroke is severely delayed and, if it's a tablet pen, occasionally lacks pen pressure. A less severe version of the bug occurs if the layer is not in a group.I've divided them into bug 1 and 2. Bug 1. If the layer is in a group and under a filter layer, this bug happens every time the canvas is moved. Bug 2. If the layer is outside of a group but under a filter later, the bug only happens the first time the layer is moved under the filter layer in the stack. STEPS TO REPRODUCE BUG 1 1. Open the attached file, select the 'Layer' Layer. 2. Move the canvas in any way 3. Draw a brush stroke. Observe that the pen lacks pressure sensitivity, and the stroke itself is heavily delayed in rendering. BUG 2 1. Open the attached file, move both 'Filter' and "Layer' layers outside of the group. 2. Move the 'Layer' layer above the filter layer 3. Move the 'Layer' layer below the filter layer. 4. Draw a brush stroke Observe that the same bug as bug #1 occurs, but that it only happens once and never again until the layer is moved again. System information Krita Version: 5.3.0-prealpha (git 27302a3) Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-lp64 Kernel Version: 6.2.0-33-generic Pretty Productname: Ubuntu 23.04 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "NVIDIA GeForce RTX 4090/PCIe/SSE2" Driver version: "4.6.0 NVIDIA 535.104.05" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.3, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 4.6, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) GL version: 4.6 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Detected renderers: (Supported) NVIDIA GeForce RTX 4090/PCIe/SSE2 (OpenGL ES 3.2 NVIDIA 535.104.05) (Supported) NVIDIA GeForce RTX 4090/PCIe/SSE2 (4.6.0 NVIDIA 535.104.05) Hardware Information Memory: 61 Gb Cores: 32 Swap: /tmp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475110] New: Crashes when starting up Chromium
https://bugs.kde.org/show_bug.cgi?id=475110 Bug ID: 475110 Summary: Crashes when starting up Chromium Classification: Plasma Product: kwin Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: colin.mc...@gmail.com Target Milestone: --- Application: kwin_x11 (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-12-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Crashes when starting up Chromium. This issue first appeared just after a set of upgrades which included upgrading the nVidea drivers. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault PID: 425138 (kwin_x11) UID: 1000 (colin) GID: 1000 (colin) Signal: 11 (SEGV) Timestamp: Sun 2023-10-01 16:28:56 EDT (51s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (colin) Boot ID: 56ebca667ee84364a6a87e6c73414484 Machine ID: e9d7b45a282f41229648bce3884ed40d Hostname: onyx Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.56ebca667ee84364a6a87e6c73414484.425138.169619213600.zst (present) Size on Disk: 4.5M Message: Process 425138 (kwin_x11) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64 Stack trace of thread 425138: #0 0x7fadd18aec24 pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7fadd185b1b9 sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7fadd4c13e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7fadd4c14b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7fadd185afd0 n/a (libc.so.6 + 0x3bfd0) #5 0x56349a54ecc0 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 [New LWP 425138] [New LWP 425146] [New LWP 425140] [New LWP 425143] [New LWP 425145] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/kwin_x11 --replace'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fadd18aec24 in pthread_sigmask () from /lib/x86_64-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x7fadcd5639c0 (LWP 425138))] [Current thread is 1 (Thread 0x7fadcd5639c0 (LWP 425138))] Thread 5 (Thread 0x7fada6c0 (LWP 425145)): #0 0x7fadd191b03f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fadd05d49ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fadd05d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fadd2909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fadd28b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fadd26cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fadd26cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fadd18a8044 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7fadd19285fc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7fadb63df6c0 (LWP 425143)): #0 0x7fadd191b03f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fadd05d49ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fadd05d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fadd2909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fadd28b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fadd26cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fadd3b28555 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fadd26cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fadd18a8044 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7fadd19285fc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fadc79ff6c0 (LWP 425140)): #0 0x7fadd191b03f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fadd05d49ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2
[skrooge] [Bug 418686] no sounds from Skrooge flatpak app
https://bugs.kde.org/show_bug.cgi?id=418686 Stephane MANKOWSKI changed: What|Removed |Added Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 474391] in Merge imported operations, prefer fields with values over blank fields
https://bugs.kde.org/show_bug.cgi?id=474391 Stephane MANKOWSKI changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/offi ||ce/skrooge/-/commit/255d090 ||9cea56670725a7c54dbe96abae9 ||d36139 Resolution|--- |FIXED --- Comment #1 from Stephane MANKOWSKI --- Git commit 255d0909cea56670725a7c54dbe96abae9d36139 by Stephane MANKOWSKI. Committed on 01/10/2023 at 22:34. Pushed by smankowski into branch 'master'. in Merge imported operations, prefer fields with values over blank fields M +4-0CHANGELOG M +4-1skgbankmodeler/skgoperationobject.cpp M +1-1tests/skgbankmodelertest/skgtestimportqif2.cpp https://invent.kde.org/office/skrooge/-/commit/255d0909cea56670725a7c54dbe96abae9d36139 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 474391] in Merge imported operations, prefer fields with values over blank fields
https://bugs.kde.org/show_bug.cgi?id=474391 Stephane MANKOWSKI changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 474759] The tool to align the category of operations with their payees' always fills in the category of the first payee it found
https://bugs.kde.org/show_bug.cgi?id=474759 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/skrooge/-/commit/a5edb01 ||08d77768cf771689ecb34ba4c2f ||ac309a Status|ASSIGNED|RESOLVED --- Comment #1 from Stephane MANKOWSKI --- Git commit a5edb0108d77768cf771689ecb34ba4c2fac309a by Stephane MANKOWSKI. Committed on 01/10/2023 at 22:12. Pushed by smankowski into branch 'master'. The tool to align the category of operations with their payees' always fills in the category of the first payee it found M +3-3plugins/skrooge/skrooge_operation/skgoperationplugin.cpp M +1-1plugins/skrooge/skrooge_operation/skgoperationplugin.h https://invent.kde.org/office/skrooge/-/commit/a5edb0108d77768cf771689ecb34ba4c2fac309a -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 474759] The tool to align the category of operations with their payees' always fills in the category of the first payee it found
https://bugs.kde.org/show_bug.cgi?id=474759 Stephane MANKOWSKI changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475108] New Transaction Crashes App
https://bugs.kde.org/show_bug.cgi?id=475108 Jack changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jack --- What changed since you last successfully created a new transaction? Can you run the program from command line? That might show a useful error message output to the console. You will have to find the full path to the executable, as it is not likely to be on your PATH. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475109] New: The color picker plugin doesn't work properly.
https://bugs.kde.org/show_bug.cgi?id=475109 Bug ID: 475109 Summary: The color picker plugin doesn't work properly. Classification: Applications Product: kate Version: 23.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: plugin-preview Assignee: kwrite-bugs-n...@kde.org Reporter: thep.m.r.ghazip...@gmail.com Target Milestone: --- Created attachment 162011 --> https://bugs.kde.org/attachment.cgi?id=162011=edit That shows the problem. 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. Enable color picker plugin in settings. 2. Type a color code in your editor that kate can detect it's a color code.(there must be a preview of the color you've typed) 3. Place your cursor everywhere before the color code. 4.Click enter button. 5.It always make a black box that works but must not be there. OBSERVED RESULT It always make a black box that works but must not be there. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux 6.1.53-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456329] System Settings crashed when I switched to the Sidebar View
https://bugs.kde.org/show_bug.cgi?id=456329 `{third: "Beedell", first: "Roke"}`{.JSON5} changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456329] System Settings crashed when I switched to the Sidebar View
https://bugs.kde.org/show_bug.cgi?id=456329 --- Comment #5 from `{third: "Beedell", first: "Roke"}`{.JSON5} --- (In reply to Nate Graham from comment #3) > Can you still reproduce it in Plasma 5.27? Per > The crash does not seem to be reproducible. I doubt I ever knew exactly how to reproduce it initally, much less now. However, doing what I have recorded doesn't appear to yield a crash, not that (per the aforementioned) it ever did reliably. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 462200] plasma-systemmonitor french translation could be improved
https://bugs.kde.org/show_bug.cgi?id=462200 --- Comment #3 from y...@masson-informatique.fr --- Thanks both of you for digging into this! And in this situation I really think that "rate" should be translated "vitesse", not "taux". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 475100] SSH entries in KRunner
https://bugs.kde.org/show_bug.cgi?id=475100 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 474549] Can't configure proxy before signing in
https://bugs.kde.org/show_bug.cgi?id=474549 Carl Schwan changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 470774] Allow multiple categories for budgets
https://bugs.kde.org/show_bug.cgi?id=470774 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr Status|REPORTED|NEEDSINFO --- Comment #1 from Stephane MANKOWSKI --- Hi, I don't know MoneyDashboard and I don't understand the need. In Skrooge a budget item can be attached to a category (example: Car > Services). If you want, you can create a budget item for a parent category (example: Car). So, I don't really understand what you need more. Could you give me a detailed example ? -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 472061] AppData missing in 2.30.0 tarball
https://bugs.kde.org/show_bug.cgi?id=472061 Stephane MANKOWSKI changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/skrooge/-/commit/d6cc5e3 ||ec5b45cb8f7c8d298c66a706009 ||491cbf Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Stephane MANKOWSKI --- Git commit d6cc5e3ec5b45cb8f7c8d298c66a706009491cbf by Stephane MANKOWSKI. Committed on 01/10/2023 at 21:30. Pushed by smankowski into branch 'master'. AppData missing in 2.30.0 tarball M +1-0skrooge/org.kde.skrooge.appdata.xml https://invent.kde.org/office/skrooge/-/commit/d6cc5e3ec5b45cb8f7c8d298c66a706009491cbf -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475108] New: New Transaction Crashes App
https://bugs.kde.org/show_bug.cgi?id=475108 Bug ID: 475108 Summary: New Transaction Crashes App Classification: Applications Product: kmymoney Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: b.krywin...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open account ledger 2. create new transaction 3. begin typing date OBSERVED RESULT crash EXPECTED RESULT add new transaction to ledger SOFTWARE/OS VERSIONS Windows: macOS: 13.5.2 (22G91) on 2018 Mac Mini AND on 2020 M1 Macbook Air; App version 5.1.80-a0f67e0d2 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.
[dolphin] [Bug 474951] Allow the search bar to always remain visible.
https://bugs.kde.org/show_bug.cgi?id=474951 --- Comment #6 from `{third: "Beedell", first: "Roke"}`{.JSON5} --- > It also saves people the trouble of manually hiding the search after they > have already found what they were searching for. But it doesn't for me. It's the opposite. *That*'s the sole reason that I have provided, because it's the sole reason I want it. What you stated is the sole reason I've provided isn't really a reason, and I'm thus not certain why you've interpreted it as such, especially since I've so clearly stated why this is more fundamentally desirable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475107] New: Crash when exiting Canvas Only mode while toolbar is expanded
https://bugs.kde.org/show_bug.cgi?id=475107 Bug ID: 475107 Summary: Crash when exiting Canvas Only mode while toolbar is expanded Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Android 13.x Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: xeses16...@tastrg.com Target Milestone: --- SUMMARY *** The title is basically the summary. *** STEPS TO REPRODUCE 1. Go to Settings, Configure Toolbar, and add enough actions to mainToolbar so that they can't all fit into the toolbar 2. Go to Settings, Configure Krita, Canvas-only settings, have everything checked except toolbars and dockers 3. Start a new drawing 4. Activate canvas-only mode (in my case, I used the finger-tap touch shortcut) 5. Click the expand button on the right edge of the toolbar to show all of your hidden actions 6. Disable canvas-only mode with the finger-tap shortcut OBSERVED RESULT Krita will immediately crash. EXPECTED RESULT To disable canvas-only mode and not crash. SOFTWARE/OS VERSIONS Android 13, Motorola near-stock UI Krita 5.1.5, arm64 apk ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475106] Raise the address bar to better indicate that it's clickable
https://bugs.kde.org/show_bug.cgi?id=475106 postix changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475106] New: Raise the address bar to better indicate that it's clickable
https://bugs.kde.org/show_bug.cgi?id=475106 Bug ID: 475106 Summary: Raise the address bar to better indicate that it's clickable Classification: Applications Product: dolphin Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pos...@posteo.eu CC: kfm-de...@kde.org Target Milestone: --- Created attachment 162010 --> https://bugs.kde.org/attachment.cgi?id=162010=edit Mockups SUMMARY Ever since I have installed Plasma on my parents computers, I have noticed that they had issues to figure out that the address bar in Dolphin is actually clickable. For them it just looked like informative text, which was visually not very distinct from the rest in the toolbar. Thus we believe that it'd be easier to understand and in passing look better, if the address bar were raised as shown in the attached mockup taken from [1]. [1] https://phabricator.kde.org/T12308 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475103] "Horizontal" and "vertical" - wrong usage of these terms in Tiling Layout creator
https://bugs.kde.org/show_bug.cgi?id=475103 --- Comment #2 from holyzo...@trash-mail.com --- Sorry pls delete <"Left-Right" vs "Top-Bottom"> from summary above. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475105] New: Ctrl + Any direction of mouse wheel zooms always in until Ctrl is pressed a 2nd time
https://bugs.kde.org/show_bug.cgi?id=475105 Bug ID: 475105 Summary: Ctrl + Any direction of mouse wheel zooms always in until Ctrl is pressed a 2nd time Classification: Applications Product: dolphin Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pos...@posteo.eu CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When I initially open Dolphin and change the icon sizes in any view using Ctrl + Mouse Wheel, Dolphin always first zooms in independent of the scroll wheel direction. Then after releasing Ctrl and pressing Ctrl again, zooming starts to depend on the mouse wheel direction as expected. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230926 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.4-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432243] kf.xmlgui: cannot find .rc file "kinfocenterui.rc" for component "kinfocenter"
https://bugs.kde.org/show_bug.cgi?id=432243 TraceyC changed: What|Removed |Added CC||kdeb...@tlcnet.info -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 475037] Dashboard: the font in "Income & Expenditure" is too small and has a bad contrast
https://bugs.kde.org/show_bug.cgi?id=475037 Stephane MANKOWSKI changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/skrooge/-/commit/67023c2 ||41a661b7e4199c46c2854055f72 ||ec244f Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Stephane MANKOWSKI --- Git commit 67023c241a661b7e4199c46c2854055f72ec244f by Stephane MANKOWSKI. Committed on 01/10/2023 at 20:40. Pushed by smankowski into branch 'master'. Dashboard: the font in "Income & Expenditure" is too small and has a bad contrast M +1-1plugins/skrooge/default/account_table.qml M +1-1plugins/skrooge/default/account_table_light.qml M +1-1plugins/skrooge/default/alarm.qml M +1-1plugins/skrooge/default/bank_table.qml M +1-1plugins/skrooge/default/bank_table_light.qml M +1-1plugins/skrooge/default/budget_table.qml M +1-1plugins/skrooge/default/categories_period_table.qml M +1-1plugins/skrooge/default/categories_variations.qml M +1-1plugins/skrooge/default/categories_variations_issues.qml M +1-1plugins/skrooge/default/income_vs_expenditure.qml M +1-1plugins/skrooge/default/interests.qml M +1-1plugins/skrooge/default/personal_finance_score.qml M +1-1plugins/skrooge/default/portfolio.qml M +1-1plugins/skrooge/default/scheduled_operations.qml https://invent.kde.org/office/skrooge/-/commit/67023c241a661b7e4199c46c2854055f72ec244f -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 475104] New: Kirigami Gallery - List View - Drag doesn't work
https://bugs.kde.org/show_bug.cgi?id=475104 Bug ID: 475104 Summary: Kirigami Gallery - List View - Drag doesn't work Classification: Applications Product: kirigami gallery Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: openmail+...@siezi.com Target Milestone: --- Created attachment 162009 --> https://bugs.kde.org/attachment.cgi?id=162009=edit Drag and Drop not working SUMMARY Trying to drag list item breaks the layout. STEPS TO REPRODUCE 1. Open the Kirigami Gallery and navigate to the List View example 2. Drag & Drop list items OBSERVED RESULT See attachment video for example. The drag & drop isn't properly working. EXPECTED RESULT Provide a working drag & drop example. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-2-cachyos (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION It was my first try implementing the drag feature and was looking at the Gallery app to get started, but that code isn't properly working? Since the feature is working in other places in the plasma desktop I finally used this as an starting point [1]. I assume the Gallery example code isn't up to date? Or is it an issue elsewhere? [1] https://invent.kde.org/plasma/kwin/-/blob/master/src/kcms/rules/ui/main.qml -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 475086] Skrooge fails to import files
https://bugs.kde.org/show_bug.cgi?id=475086 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Stephane MANKOWSKI --- Hi, You are using a "snap" version of Skrooge. This version seems to be not well packaged. You should contact the packager. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389727] Ability to drag widgets between panels
https://bugs.kde.org/show_bug.cgi?id=389727 Nate Graham changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469471] Impossible to drag widget's FullRepresentation off the panel (dragging CompactRepresentation works)
https://bugs.kde.org/show_bug.cgi?id=469471 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1750 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475103] "Horizontal" and "vertical" - wrong usage of these terms in Tiling Layout creator
https://bugs.kde.org/show_bug.cgi?id=475103 --- Comment #1 from holyzo...@trash-mail.com --- Ok, sorry the Konsole option does make sence. Split view, which is adjective split; noun: view. It wouldn't make sense if you interpret split as verb. Maybe things get/got lost in translation :) into other languages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389727] Ability to drag widgets between panels
https://bugs.kde.org/show_bug.cgi?id=389727 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1750 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450579] Wayland: Can't drag and drop to panel when set to Auto Hide
https://bugs.kde.org/show_bug.cgi?id=450579 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1750 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430391] Audo-hidden panel unexpectedly accepts drags of widgets even when hidden
https://bugs.kde.org/show_bug.cgi?id=430391 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1750 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446813] Applets dragged from a panel to the desktop land at panel edge instead of the cursor position
https://bugs.kde.org/show_bug.cgi?id=446813 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1750 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475103] New: "Horizontal" and "vertical" - wrong usage of these terms in Tiling Layout creator
https://bugs.kde.org/show_bug.cgi?id=475103 Bug ID: 475103 Summary: "Horizontal" and "vertical" - wrong usage of these terms in Tiling Layout creator Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: unspecified OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: holyzo...@trash-mail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Sorry, can't find a good category. SUMMARY *** The terms "Horizontal" vs "vertical" "Left-Right" vs "Top-Bottom" are confused in the options of the Tiling Layout creator (to be accessed by SUPER + T). *** STEPS TO REPRODUCE 1. log into Plasma and hit SUPER + T 2. Take one of the fields and select: Split Vertically (why is it a capital V btw?) and it splits the field horizontally, i. e. the "split" is then a horizontal line. 3. Take one of the fields and select: Split Horizonatlly (why is it a capital H btw?) and it splits the field vertically, i. e. the "split" is then a vertical line. OBSERVED RESULT Vertical split is horizontal. Horizontal split is vertical. EXPECTED RESULT Vertical split is vertical. Horizontal split is horizontal. SOFTWARE/OS VERSIONS Manjaro Linux (Stable). KDE Plasam KDE Plasma Version: 5 27 8 KDE Frameworks Version: 5 110 0 Qt Version: 5 15 10 ADDITIONAL INFORMATION It's the same in Konsole with "Left-Right" vs "Top-Bottom". There might be other apps as well? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475000] Automatic switching starts and finishes an hour late
https://bugs.kde.org/show_bug.cgi?id=475000 --- Comment #4 from holyzo...@trash-mail.com --- It doesn't seem to fix it, also after some reboots. The background service is activated. It's not such a bad-bad bug and winter time switch will fix it until spring, I guess. Plus, everyboday affected can work around it by setting the exact location in Switching times: Sunset and sunrise at MANUAL location. Maybe one has to delete some cookie or so? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 Dashon changed: What|Removed |Added CC||sparky123558w...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475090] ExposeClass method selects the next window class when the window with the current focus is closed and the next window in line is from a different class
https://bugs.kde.org/show_bug.cgi?id=475090 --- Comment #1 from Jim Jones --- i found a more reproducible way: 1. open 3 terminal windows and one dolphin window 2. focus aka click on the dolphin window 3. click on one of the terminal windows 4. call ExposeClass 5. close the terminal window that got clicked/focused in "3." 6. now the dolphin windows only is shown instead of the 2 still open terminal instances -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #6 from Dashon --- (In reply to Niccolò Venerandi from comment #4) > I can confirm this is intentional; the desktop bar will only be shown: > - If you have one desktop row > - If you have multiple desktop rows, and a number of desktop that's equal or > less to the desktop rows (a.k.a. a single column of desktops) If moving the desktop bar to the left side of the screen is intentional also, I found that you can no longer click and grab to scroll the desktop bar. This means if you have a number of virtual desktops bigger than your screen size. Then you can not access those from the overview. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475102] Interface and wallpaper randomly "crashes?". How to fix it?
https://bugs.kde.org/show_bug.cgi?id=475102 tymek changed: What|Removed |Added Summary|It randomly "crashes?". How |Interface and wallpaper |to fix it? |randomly "crashes?". How to ||fix it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #5 from Dashon --- (In reply to Niccolò Venerandi from comment #4) > I can confirm this is intentional; the desktop bar will only be shown: > - If you have one desktop row > - If you have multiple desktop rows, and a number of desktop that's equal or > less to the desktop rows (a.k.a. a single column of desktops) Ok, but I believe this should be mentioned somewhere, so that people know to change there setup when it comes time to upgrade. As I mention this currently works, but will stop working when it comes time to upgrade to plasma 6. Another thing I noticed is that if you create a number of virtual desktops equal to the number of rows. The desktop bar moves from the top to the left side which is something else that does not currently happen in 5.27. Is this also intentional or should there be a different issue for this? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475102] It randomly "crashes?". How to fix it?
https://bugs.kde.org/show_bug.cgi?id=475102 --- Comment #2 from tymek --- So it frequently happens when just using my desktop, but I had noticed it happens every time when I try to add or change something on the top interface panel. My linux is on an external drive because I use different desktops. It happens on every one, but more frequently on my Lenovo G50-30 or especially on my Toshiba satellite c850d-119, it's more random on my asus notebook e406m or my sister's huawei notebook. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475102] It randomly "crashes?". How to fix it?
https://bugs.kde.org/show_bug.cgi?id=475102 --- Comment #1 from tymek --- Created attachment 162008 --> https://bugs.kde.org/attachment.cgi?id=162008=edit video of a crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440191] Audio wont render
https://bugs.kde.org/show_bug.cgi?id=440191 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO --- Comment #1 from emohr --- Please check with actual 23.08.1 version from the download page to see if it still happen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475097] Clipboard shortcut changes still applied after cancelling configuration
https://bugs.kde.org/show_bug.cgi?id=475097 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463590] Crash when loading a HD 1080p clip
https://bugs.kde.org/show_bug.cgi?id=463590 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||MOVIT+ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457426] enabled Use GPU Acceleration (movit library) dragging files in project bin or timeline crash kdenlive
https://bugs.kde.org/show_bug.cgi?id=457426 emohr changed: What|Removed |Added Flags||MOVIT+ CC||fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 466391] Program crashes when adding Bezier Curve effect to clip
https://bugs.kde.org/show_bug.cgi?id=466391 emohr changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from emohr --- This is solved with version 23.08.1. I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475039] Crashes by opening a project file created by version 23.08.0
https://bugs.kde.org/show_bug.cgi?id=475039 emohr changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from emohr --- Thank you for the feedback. I close the issue. If it still appears in the latest version, please feel free to re-open it and update the affected version number. For your wishes: Some of this function (insert) is already possible with key shortcuts. See here https://docs.kdenlive.org/en/cutting_and_assembling/editing.html#insert-mode and key “V” with the 3-point-editing: https://docs.kdenlive.org/en/cutting_and_assembling/editing.html#point-editing -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475102] It randomly "crashes?". How to fix it?
https://bugs.kde.org/show_bug.cgi?id=475102 tymek changed: What|Removed |Added URL||https://www.youtube.com/wat ||ch?v=oDz3Sb8eDqY -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 Niccolò Venerandi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL CC||nicc...@venerandi.com --- Comment #4 from Niccolò Venerandi --- I can confirm this is intentional; the desktop bar will only be shown: - If you have one desktop row - If you have multiple desktop rows, and a number of desktop that's equal or less to the desktop rows (a.k.a. a single column of desktops) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 452833] [libvpx @0000000002bcb340] Transparency encoding with auto_alt_ref does not work Rotoscope render
https://bugs.kde.org/show_bug.cgi?id=452833 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- I tried with a 1080p50 clip with a rotoscope effect and render it to VP8 and VP9. No crash. Please check with actual 23.08.1 version on the download page. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475102] New: It randomly "crashes?". How to fix it?
https://bugs.kde.org/show_bug.cgi?id=475102 Bug ID: 475102 Summary: It randomly "crashes?". How to fix it? Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: perz.amade...@gmail.com Target Milestone: --- So it seemingly crashes at random times. I replicated it by spamming special key. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Desktop Bar Doesn't Appear when Virtual Desktop Rows Set to Number Greater Than One
https://bugs.kde.org/show_bug.cgi?id=475077 --- Comment #3 from Dashon --- (In reply to Nicolas Fella from comment #2) > I believe this is intentional. The desktop bar is only shown when the > desktop layout is 1-dimensional If that is the move going forward then alright, but the reason I filled the bug is because this same setup already works in 5.27. I currently have 9 virtual desktops in 3 rows. The desktop bar is shown currently, but it will not be shown in plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466671] Discover is very slow to fetch updates
https://bugs.kde.org/show_bug.cgi?id=466671 Alessandro Astone changed: What|Removed |Added Resolution|--- |UPSTREAM CC||ales.ast...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #5 from Alessandro Astone --- `pkcon refresh` takes less than a second because it does nothing in Fedora. That is, unfortunately, intended. We have to use of `force` (or `--cache-age 1`) to actually download the new metadata: https://src.fedoraproject.org/rpms/plasma-discover/blob/rawhide/f/discover-5.21.4-pk_refresh_force.patch But improvements are coming: - https://github.com/rpm-software-management/libdnf/pull/1626 - https://github.com/PackageKit/PackageKit/pull/678 - https://invent.kde.org/plasma/discover/-/merge_requests/640 -- We need to use `--cache-age 1` instead of `force` to make use of the other upstream improvements With that it'll only be a bit slower than `dnf makecache` -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 449858] effect "Chroma Key: Basic" will cause a crash
https://bugs.kde.org/show_bug.cgi?id=449858 emohr changed: What|Removed |Added Status|REPORTED|RESOLVED CC||fritzib...@gmx.net Resolution|--- |FIXED --- Comment #1 from emohr --- "Chroma Key: Basic" works without crash on version 23.08.1. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447865] Crashing program report | Issue: Fill borders effects.
https://bugs.kde.org/show_bug.cgi?id=447865 emohr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from emohr --- With version 23.08.1 the crash doesn't happen anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470229] KDENLIVE crashing because of permissions issue
https://bugs.kde.org/show_bug.cgi?id=470229 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from emohr --- This is a upstream (Fedora) or machine settings issue. -- You are receiving this mail because: You are watching all bug changes.