[kdenlive] [Bug 455563] New: clip monitor: playback with forward speed of 1.5x is at the same speed of 1x
https://bugs.kde.org/show_bug.cgi?id=455563 Bug ID: 455563 Summary: clip monitor: playback with forward speed of 1.5x is at the same speed of 1x Product: kdenlive Version: 21.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: bigfl...@gmail.com Target Milestone: --- Created attachment 149903 --> https://bugs.kde.org/attachment.cgi?id=149903&action=edit clip monitor at 1.5x playback 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 *** I downloaded and installed the binary installer. MLT version 7.1.0 STEPS TO REPRODUCE 1. Create a new project, and add a video clip (here it is of MP4 format). drag the newly-added video clip to the tracks area. 2. click the clip monitor. Click the cursor in the timeline bar above the buttons. 3. click the forward button twice, and 1.5x is shown at the upper left corner in the monitor. However, the playback speed is actually 1x. I timed with a stopwatch app (on mobile phone), and compared with the timestamp shown to the right of the forward button. 4. click the cursor in the timeline bar above the tracks. click the forward button twice, and 1.5x is shown at the upper left corner in the monitor. Playback speed is actually 1x. OBSERVED RESULT 1x playback speed. EXPECTED RESULT 1.5x playback speed. When I click the forward button one more time, and 2x is shown and the playback speed is actually 2x. So the 1.5x playback speed cannot be achieved. SOFTWARE/OS VERSIONS Windows: 10 21H2 (19044.1766). macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Same issue happened in Kdenlive for MacOS, v22.04.01. I downloaded the binary installer. KDE frameworks v5.94.0 Qt v5.15.2. MLT 7.7.0. MacOS version: Monterey v12.4 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 499831] New: feature request: add a menu item and the shortcut key for "Find Prev" under the Edit menu
https://bugs.kde.org/show_bug.cgi?id=499831 Bug ID: 499831 Summary: feature request: add a menu item and the shortcut key for "Find Prev" under the Edit menu Classification: Applications Product: kdiff3 Version: 1.11.5 Platform: macOS (DMG) OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: bigfl...@gmail.com Target Milestone: --- SUMMARY Not a bug, but a feature request. I reviewed https://discuss.kde.org/ and searched for the tag "kdiff3" and found few posts. Therefore I open a bug here. STEPS TO REPRODUCE 1. On MacOS, run kdiff3 and load two files to compare. 2. Press Cmd+F, and enter a string to start the search. It allows to search left and/or right file. 3. Press F3 and successfully move to the next match. OBSERVED RESULT Tried to perform "Find Prev" and there is no menu item or shortcut key for it. It is quite inconvient when navigating across the matched strings in the files. EXPECTED RESULT There is a menu item and the shortcut key for "Find Prev" under the Edit menu. Shortcut key can be Shift+F3. SOFTWARE/OS VERSIONS Windows: macOS: Sonoma 14.6 (23G80) (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483055] New: Dolphin does not have a mechanism for mounting network shares in userspace
https://bugs.kde.org/show_bug.cgi?id=483055 Bug ID: 483055 Summary: Dolphin does not have a mechanism for mounting network shares in userspace Classification: Applications Product: dolphin Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sfal...@cloverleaf-linux.org CC: kfm-de...@kde.org Target Milestone: --- Created attachment 166839 --> https://bugs.kde.org/attachment.cgi?id=166839&action=edit Example of GNOME Menu showing Mount option SUMMARY When navigating to and browsing a network share in Dolphin, be it NFS/SMB/Etc, Dolphin doesn't ever actually mount that share anywhere on the filesystem, and appears to just be doing network browsing. In GNOME, Nautilus and gio/gvfs allow for mounting those network shares in userspace. (/run/user/UID/gvfs/protocol:server,sharename) that is predictable and the same from mount to mount. The closest thing we can do in plasma right now, is to use kio in the terminal, which mounts the share in /run/user/UID/kio-$SOME_RANDOM_UID that changes every time you mount it, and doesn't integrate with Dolphin. I'm including screenshots from GNOME, just as an example of the desired behavior. STEPS TO REPRODUCE 1. Open Dolphin 2. Navigate to a Network Share 3. Attempt to find a method to mount those shares in userspace OBSERVED RESULT Dolphin does not have a mechanism in place, that I can find, to mount network shares to the filesystem, in userspace (or anywhere else, for that matter) EXPECTED RESULT A Right-Click Mount option, or something in the menu allowing network shares to be mounted to the filesystem SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.7.7-1-default, openSUSE Kalpa, Wayland Session (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483055] Dolphin does not have a mechanism for mounting network shares in userspace
https://bugs.kde.org/show_bug.cgi?id=483055 --- Comment #1 from Shawn W Dunn --- Created attachment 166840 --> https://bugs.kde.org/attachment.cgi?id=166840&action=edit Display of gio/gvfs mount point, from mount operation -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484401] Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's
https://bugs.kde.org/show_bug.cgi?id=484401 Shawn W Dunn changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Shawn W Dunn --- Behavior is no longer present in 24.02.2, bug can probably be closed.Sorry, I haven't actually been using tokodon lately, because of another bug. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481096] When using multiple accounts, one account always stays highlighted in the switcher, regardless of which server is actually "active"
https://bugs.kde.org/show_bug.cgi?id=481096 --- Comment #3 from Shawn W Dunn --- With the latest build from flathub (24.02.01) which I've been using for probably a week or two now, I haven't seen the behavior, so I'd say it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481090] Neochat Scroll "bounces"/glitches
https://bugs.kde.org/show_bug.cgi?id=481090 --- Comment #1 from Shawn W Dunn --- This is happening much *less*, purely based on my observations, with 24.02.1 But it's still happening. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484985] New: SSL Appears to be broken
https://bugs.kde.org/show_bug.cgi?id=484985 Bug ID: 484985 Summary: SSL Appears to be broken Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sfal...@cloverleaf-linux.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 168101 --> https://bugs.kde.org/attachment.cgi?id=168101&action=edit Output of `flatpak run -v org.kde.tokodon` SUMMARY When upgrading from 23.08.4 from flathub, to 24.02.1, opening Tokodon resulted in an endless "Loading" progress bar. I uninstalled tokodon `flatpak uninstall org.kde.tokodon` and removed all content from `~/.var/app/org.kde.tokodon` and reinstalled When attempting to re-set up Tokodon, after entering the mastodon server domain name, it goes to the "Authorization" screen which remains a blank white screen. STEPS TO REPRODUCE 1. Start Tokodon via `flatpak run org.kde.tokodon` 2. Enter mastodon server domain name 3. Click Continue OBSERVED RESULT The screen changes to the "Authorization" screen, and displays a blank white screen, and remains there for as long as I leave Tokodon running EXPECTED RESULT Tokodon sends me to the browser for Authentication and login SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Kalpa, Linux 6.8.1, Wayland Session, Flatpak 1.15.6 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484985] SSL Appears to be broken
https://bugs.kde.org/show_bug.cgi?id=484985 --- Comment #2 from Shawn W Dunn --- Fosstodon.org is one of them The other is my personal mastodon, which is using a Let'sEncrypt certificate, and is hosted on a VPS outside my network -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484401] Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's
https://bugs.kde.org/show_bug.cgi?id=484401 --- Comment #2 from Shawn W Dunn --- Correct, I'm using the standard Breeze/Breeze Dark theming globally, no messing about with the themes, fonts, or anything else -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484401] Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's
https://bugs.kde.org/show_bug.cgi?id=484401 --- Comment #3 from Shawn W Dunn --- Enabling the "Ignore SSL errors" switch in Tokodon, when attempting to login to both accounts still results in the same behaviors -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484401] Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's
https://bugs.kde.org/show_bug.cgi?id=484401 --- Comment #4 from Shawn W Dunn --- (In reply to Shawn W Dunn from comment #3) > Enabling the "Ignore SSL errors" switch in Tokodon, when attempting to login > to both accounts still results in the same behaviors This comment doesn't belong here. Sorry about that. Wrong Bug. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484985] SSL Appears to be broken
https://bugs.kde.org/show_bug.cgi?id=484985 --- Comment #3 from Shawn W Dunn --- Enabling "Ignore SSL Errors" via the switch in the UI doesn't fix the issue, when trying to login. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483580] New: Yakuake isn't respecting setting on which screen to open on
https://bugs.kde.org/show_bug.cgi?id=483580 Bug ID: 483580 Summary: Yakuake isn't respecting setting on which screen to open on Classification: Applications Product: yakuake Version: 23.08.5 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: sfal...@cloverleaf-linux.org Target Milestone: --- Created attachment 167191 --> https://bugs.kde.org/attachment.cgi?id=167191&action=edit Screenshot of Display Configuration KCM, Portrait display is Screen 1, Landscape is Screen 2 SUMMARY With Yakuake set to "Open on screen: At Mouse Location" on my setup, it will *always* open on Screen 1 STEPS TO REPRODUCE 1. Set Yakuake to open at mouse location 2. Click on Screen 2, to make sure that it registers OBSERVED RESULT Yakuake opens on Screen 1 EXPECTED RESULT Yakuake opens on the screen that the mouse pointer is on SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.7-1-default openSUSE Kalpa Wayland (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Screenshot of Display Configuration KCM attached, for context -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484280] New: kcm_flatpak is displaying incorrect information in the Application List, and some icons are missing
https://bugs.kde.org/show_bug.cgi?id=484280 Bug ID: 484280 Summary: kcm_flatpak is displaying incorrect information in the Application List, and some icons are missing Classification: Applications Product: systemsettings Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: sfal...@cloverleaf-linux.org CC: joshiesuha...@gmail.com, m...@ratijas.tk Target Milestone: --- Created attachment 167627 --> https://bugs.kde.org/attachment.cgi?id=167627&action=edit Screenshot showing the wrong application names SUMMARY Many of the entries in kcm_flatpak are displaying the Author or company name, rather than the application name for the flatpak STEPS TO REPRODUCE 1. Install Some flatpaks 2. Open SystemSettings->Application Permissions->Flatpak Permissions OBSERVED RESULT org.kde.ark Icon is missing in the list com.discordapp.Discord is showing "Discord Inc." as the app name org.mozilla.Firefox is missing the icon org.remmina.Remmina is showing "Hiroyki_Tanaka" as the app name org.telegram.desktop is showing "John Preston" as the app name, and the icon is broken, so no idea what application it is at first glance com.calibre_ebook.calibre is showing "Kovid Goyal" as the app name com.nextcloud.desktopclient.nextcloud is showing "Nextcloud GmbH" as the app name EXPECTED RESULT Seeing the Application Names and appropriate icons SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Kalpa, Linux 6.8.1 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Attached Screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484280] kcm_flatpak is displaying incorrect information in the Application List, and some icons are missing
https://bugs.kde.org/show_bug.cgi?id=484280 --- Comment #1 from Shawn W Dunn --- I assume the kcm is just parsing the "Name" field provided by flatpak, which probably makes this a flatpak bug, and not a kcm_flatpak bug. When running `flatpak list` on the same host, the output is as follows: ``` [sfalken@mustang ~]$ flatpak list Name Application ID Version Branch Installation Kovid Goyal com.calibre_ebook.calibre 7.7.0stable user Discord Inc. com.discordapp.Discord 0.0.46 stable user Dropbox com.dropbox.Client 195.4.4995 stable user Drawing com.github.maoschanz.drawing 1.0.2stable user MakeMKV com.makemkv.MakeMKV 1.17.6 stable user Nextcloud GmbH com.nextcloud.desktopclient.nextcloud 3.12.2 stable user Opera com.opera.Opera 108.0.5067.29stable user Plex com.plexamp.Plexamp 4.10.0-r1stable user Valve Corporation com.valvesoftware.Steam 1.0.0.79 stable user ``` Flatpak/Flathub is providing the Author/Developer/Company name in the "Name" Field -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484280] kcm_flatpak is displaying incorrect information in the Application List, and some icons are missing
https://bugs.kde.org/show_bug.cgi?id=484280 Shawn W Dunn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Shawn W Dunn --- Closing, and refiling upstream with flatpak/flathub -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 484401] New: Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's
https://bugs.kde.org/show_bug.cgi?id=484401 Bug ID: 484401 Summary: Tokodon Flatpak seems to be applying it's own cursor theming, rather than using Plasma 6's Classification: Applications Product: Tokodon Version: 23.08.4 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sfal...@cloverleaf-linux.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When using the mouse cursor in the Tokodon Flatpak, it appears to be using a different cursor theme, than all of my other Flatpaks, System Theme is set to breeze STEPS TO REPRODUCE 1. Start Tokodon Flatpak 2. Move Cursor from Desktop to Tokodon Window OBSERVED RESULT Mouse Cursor changes, when it enters the Tokodon window, using adwaita maybe? It's definitely not the Breeze Cursors EXPECTED RESULT Tokodon uses the same Mouse Cursor as the rest of the desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Kalpa, Kwin_wayland (available in About System) KDE Plasma Version: System: 6.0.2 KDE Frameworks Version: System: 6.0.0 -- Flatpak Runtime: 5.115.0 Qt Version: System: 6.6.2 -- Flatpak Runtime: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483055] Dolphin does not have a mechanism for mounting network shares in userspace
https://bugs.kde.org/show_bug.cgi?id=483055 --- Comment #5 from Shawn W Dunn --- (In reply to Yevhen Popok from comment #4) > Turns out, there's no need to use CLI for kio-fuse mounts > Just type some URL in Dolphin (e.g., sftp://user@server) and you will be > able to browse mount (e.g. /run/user/1000/kio-fuse-KHGlOA/sftp/user@server) > with other applications. However, unlike with GVFS, KIOFuse will create > local directory with unique ID (see > https://invent.kde.org/system/kio-fuse/-/issues/18 and > https://bugs.kde.org/show_bug.cgi?id=432856). Ok, that's progress. And actually better than what Nautilus/gvfs does on the backend, for sftp/sshfs anyway. But doing an smb:// mount for instance, using this method, nothing gets mounted to the filesystem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Shawn W Dunn changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED CC||sfal...@cloverleaf-linux.or ||g --- Comment #10 from Shawn W Dunn --- (In reply to Alex Geer from comment #8) > (In reply to Nicolas Fella from comment #7) > > Alex, your conduct here is unacceptable. Calling things "crime against > > humanity" and blindly assuming incompetence are not constructive ways to > > talk about an issue. > > > > Please familiarize yourself with the KDE Code of Conduct > > (https://kde.org/code-of-conduct/) before further engaging with KDE > > I'm sorry, I forgot a little that I'm dealing with a world that accepts what > happens at the Olympics, all perversions and crimes are acceptable, but > honesty and truth are not acceptable. I was wrong. You're great! keep it up ! Speaking as an openSUSE Maintainer, your conduct is not only deplorable, but you're filing it in the wrong place. This isn't upstreams issue, and I would rightly expect that the openSUSE Security team would have a huge problem with upstream creating some sort of root credential caching. This bug report belongs on the openSUSE Bugtracker, as this isn't a KDE/Plasma/Discover bug in the first place. But if you're just going to be abusive to the openSUSE Maintainers as well, I doubt you'll get much traction there either. https://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE%20Distribution&component=KDE%20Applications would be the proper place to file this bug. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #7 from Shawn W Dunn --- According to "About Neochat" NeoChat: 24.12.0 KDE Flatpak runtime (Wayland) libQuotient: 0.9.2 (built against 0.9.2) KDE Frameworks: 6.9.0 Qt: Using 6.8.1 and built against 6.8.1 Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.12.6-1-default -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #11 from Shawn W Dunn --- I got the 24.12.1 version yesterday, and I'm still seeing the retries in the log, *but* it seems to be better.I'm not declaring that it's *fixed* yet, but it doesn't seem to be stalling out like 24.12 was. Let me run it for a day or two, and I'll report back. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #9 from Shawn W Dunn --- This instance was all over the course of about 5sec (lack of timestamps and direct attention is making that an estimation) ``` quotient.jobs.sync: "SyncJob-192" status Timeout: The job has timed out quotient.jobs.sync: "SyncJob-192" stopped without ready network reply quotient.jobs.sync: "SyncJob-192": retry #1 in 0 s quotient.jobs.sync: "SyncJob-204" status Timeout: The job has timed out quotient.jobs.sync: "SyncJob-204" stopped without ready network reply quotient.jobs.sync: "SyncJob-204": retry #1 in 0 s ``` I do see right now, having the fedora homeserver open in both element, and neochat, I sent a message at 08:15 localtime, from neochat, that shows up in both places. There's been three responses that have shown up in element at 08:17 and 08:18. It's now 08:22 localtime, and there's nothing showing up in the terminal that's running `flatpak run -v org.kde.neochat` nor is there in the channel window in neochat itself. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #12 from Shawn W Dunn --- Unfortunately, still seeing this behavior in 2024.12.1 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #5 from Shawn W Dunn --- I don't know if it's *useful* or even relevant, but this morning, I started neochat from konsole, via `flatpak run -v org.kde.neochat` and just let it run, and I'm seeing the following output, when neochat seems to stop updating: ``` Adding a continuation to a future which already has a continuation. The existing continuation is overwritten. quotient.jobs.sync: "SyncJob-1028" status Timeout: The job has timed out quotient.jobs.sync: "SyncJob-1028" stopped without ready network reply quotient.jobs.sync: "SyncJob-1028": retry #1 in 0 s quotient.jobs.sync: "SyncJob-1055" status Timeout: The job has timed out quotient.jobs.sync: "SyncJob-1055" stopped without ready network reply quotient.jobs.sync: "SyncJob-1055": retry #1 in 0 s ``` -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483580] Yakuake isn't respecting setting on which screen to open on
https://bugs.kde.org/show_bug.cgi?id=483580 Shawn W Dunn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Shawn W Dunn --- This bug is fixed for me, and can be closed. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] New: Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 Bug ID: 497873 Summary: Neochat just stops updating, after random periods of time Classification: Applications Product: NeoChat Version: 24.12.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: sfal...@cloverleaf-linux.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY I have three accounts setup in neochat (chat.openSUSE.org, fedora.im, and matrix.org) and with the 24.12.* release, the homeservers just seem to stop updating after what appear to be random periods of time. When I notice that I haven't gotten any new messages in any of the chats in a while, if I restart Neochat, I will most often find I have a number of messages that never appeared in my client. The homeserver doesn't appear to matter, it happens with all three. STEPS TO REPRODUCE 1. Open the neochat flatpak 2. Use it normally 3. After what feels like a random amount of time, everytime, my matrix channels seem to stop recieving new messages. OBSERVED RESULT Neochat reports no new messages in any of the chats EXPECTED RESULT Neochat reports new messages in chats as they come in. SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: openSUSE Kalpa (Tumbleweed), Linux-6.11.8 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.1 (on the host) 6.8.0 (Flatpak Runtime) Qt Version: 6.8.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #10 from Shawn W Dunn --- I don't have timestamps for this, but I left neochat running overnight, so this is over the span of about roughly nine hours, after a fresh restart. quotient.jobs: "GetNotificationsJob" status Timeout: The job has timed out quotient.jobs: "GetNotificationsJob" stopped without ready network reply quotient.jobs: "GetNotificationsJob": retry #1 in 0 s quotient.jobs: 503 <- GET https://fedora.ems.host/_matrix/client/v3/notifications quotient.jobs: "GetNotificationsJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/notifications - server replied: Service Temporarily Unavailable quotient.jobs: "GetNotificationsJob": retry #1 in 2 s quotient.jobs: 503 <- GET https://fedora.ems.host/_matrix/client/v3/notifications quotient.jobs: "GetNotificationsJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/notifications - server replied: Service Temporarily Unavailable quotient.jobs: "GetNotificationsJob": retry #2 in 5 s quotient.jobs: 503 <- GET https://fedora.ems.host/_matrix/client/v3/notifications quotient.jobs: "GetNotificationsJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/notifications - server replied: Service Temporarily Unavailable quotient.jobs: "GetNotificationsJob": retry #3 in 5 s quotient.jobs: 503 <- GET https://fedora.ems.host/_matrix/client/v3/notifications quotient.jobs: "GetNotificationsJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/notifications - server replied: Service Temporarily Unavailable quotient.jobs.sync: 502 <- GET https://fedora.ems.host/_matrix/client/r0/sync quotient.jobs.sync: "SyncJob-6265" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/r0/sync?filter=%7B%22account_data%22:%7B%7D,%22presence%22:%7B%7D,%22room%22:%7B%22account_data%22:%7B%7D,%22ephemeral%22:%7B%7D,%22state%22:%7B%22lazy_load_members%22:true%7D,%22timeline%22:%7B%22limit%22:100%7D%7D%7D&timeout=3&since=s136665591_1_5309_89411533_4949418_2952781_1386697_52921240_0_3964 - server replied: Bad Gateway quotient.jobs.sync: "SyncJob-6265": retry #1 in 2 s quotient.jobs: 502 <- POST https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers quotient.jobs: "SetReadMarkerJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers - server replied: Bad Gateway quotient.jobs: "SetReadMarkerJob": retry #1 in 2 s qrc:/qt/qml/org/kde/kirigamiaddons/labs/components/Avatar.qml:201:9: QML QQuickImage: unexpected error validating access token (https://fedora.ems.host/_matrix/client/v1/media/download/matrix.org/KEDQEquYphAuginKYbAMZrbD?timeout_ms=2) quotient.jobs: 503 <- POST https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers quotient.jobs: "SetReadMarkerJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers - server replied: Service Temporarily Unavailable quotient.jobs: "SetReadMarkerJob": retry #2 in 5 s quotient.jobs: 503 <- POST https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers quotient.jobs: "SetReadMarkerJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers - server replied: Service Temporarily Unavailable quotient.jobs: "SetReadMarkerJob": retry #3 in 5 s quotient.jobs: 503 <- POST https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers quotient.jobs: "SetReadMarkerJob" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/v3/rooms/%21lyWraihOYkbPiiTeLj%3Akde.org/read_markers - server replied: Service Temporarily Unavailable quotient.jobs.sync: 504 <- GET https://fedora.ems.host/_matrix/client/r0/sync quotient.jobs.sync: "SyncJob-6265" status NetworkError: Error transferring https://fedora.ems.host/_matrix/client/r0/sync?filter=%7B%22account_data%22:%7B%7D,%22presence%22:%7B%7D,%22room%22:%7B%22account_data%22:%7B%7D,%22ephemeral%22:%7B%7D,%22state%22:%7B%22lazy_load_members%22:true%7D,%22timeline%22:%7B%22limit%22:100%7D%7D%7D&timeout=3&since=s136665591_1_5309_89411533_4949418_2952781_1386697_52921240_0_3964 - server replied: Gateway Time-out quotient.jobs.sync: "SyncJob-6265": retry #2 in 5 s quotient.jobs.sync: 503 <- GET https://fedora.ems.host/_matrix/client/r0/sync quotient.jobs.sync: "SyncJob-6265" status NetworkError: Error transferring htt
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #2 from Shawn W Dunn --- Created attachment 177053 --> https://bugs.kde.org/attachment.cgi?id=177053&action=edit Output from journalctl -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 --- Comment #3 from Shawn W Dunn --- I've attached the output of `journalctl -b | grep neochat` which is showing me a bunch of coredumps, I only recall one actual crash in this time period. This behavior just started with the 24.12 release, it wasn't present in 24.08. Just for clarity's sake, my flatpak is coming from flathub, and not from something like the fedora flatpak repo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480693] Major memory leak when changing wallpapers - nvidia
https://bugs.kde.org/show_bug.cgi?id=480693 Shawn W Dunn changed: What|Removed |Added CC||sfal...@cloverleaf-linux.or ||g --- Comment #33 from Shawn W Dunn --- Bug is reproducible on my machine. But no Nvidia, amd graphics, using amdgpu Kalpa Desktop Linux 6.14.1 Plasma 6.3.4 Frameworks 6.12 Qt 6.9.0 Mesa 25.0.3 Wayland Session -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 501459] New: Kontact Crashes when trying to remove identities
https://bugs.kde.org/show_bug.cgi?id=501459 Bug ID: 501459 Summary: Kontact Crashes when trying to remove identities Classification: Applications Product: kontact Version: 6.3.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sfal...@cloverleaf-linux.org Target Milestone: --- SUMMARY Kontact flatpak crashes when trying to remove un-needed identites STEPS TO REPRODUCE 1. open Account Settings in kontact 2. select un-needed identity 3. remove that identity OBSERVED RESULT kontact crashes and coredumps EXPECTED RESULT identity is deleted SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Kalpa 6.13.5 Wayland KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION Apparently the coredump is too large to include as an attachment, I pulled it via `coredumpctl dump PID` of the crashed process, is there some better way to pull it so it's not so large? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 501459] Kontact Crashes when trying to remove identities
https://bugs.kde.org/show_bug.cgi?id=501459 --- Comment #3 from Shawn W Dunn --- Backtrace from my coredump: #0 0x7fd5fae9adb4 in __pthread_kill_implementation () at /usr/lib/x86_64-linux-gnu/libc.so.6 #1 0x7fd5fae4208e in raise () at /usr/lib/x86_64-linux-gnu/libc.so.6 #2 0x7fd5fd35781d in KCrash::defaultCrashHandler(int) () at /usr/lib/x86_64-linux-gnu/libKF6Crash.so.6 #3 0x7fd5fae42140 in () at /usr/lib/x86_64-linux-gnu/libc.so.6 #4 0x7fd5c801de2e in QHashPrivate::Data >::findBucket (this=0x80, key=...) at /usr/include/QtCore/qhash.h:690 #5 QHashPrivate::Data >::findNode (this=0x80, key=...) at /usr/include/QtCore/qhash.h:709 #6 QHash::valueImpl (this=, key=...) at /usr/include/QtCore/qhash.h:1064 #7 QHash::value (this=0x55ebc7dfbf68, key=...) at /usr/include/QtCore/qhash.h:1073 #8 KIdentityManagementCore::Identity::property (this=this@entry=0x55ebc7dfbf58, key=...) at /run/build/kidentitymanagement/src/core/identity.cpp:283 #9 0x7fd5c801ea8b in KIdentityManagementCore::Identity::uoid (this=this@entry=0x55ebc7dfbf58) at /run/build/kidentitymanagement/src/core/identity.cpp:345 #10 0x7fd5c802efe3 in KIdentityManagementCore::IdentityManager::commit (this=) at /run/build/kidentitymanagement/src/core/identitymanager.cpp:386 #11 0x7fd52ed8dcdd in KMail::IdentityNgPage::save (this=this@entry=0x55ebc84604a0) at /run/build/kmail/src/identity/identityngpage.cpp:103 #12 0x7fd52ed8eb40 in KMail::IdentityNgPage::save (this=0x55ebc84604a0) at /run/build/kmail/src/identity/identityngpage.cpp:221 #13 KMail::IdentityNgPage::slotRemoveIdentity (this=0x55ebc84604a0) at /run/build/kmail/src/identity/identityngpage.cpp:220 #14 0x7fd5fb60412e in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #15 0x7fd5fc8e4b74 in QAbstractButton::clicked(bool) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #16 0x7fd5fc8e4dff in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #17 0x7fd5fc8e64ef in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #18 0x7fd5fc8e6705 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #19 0x7fd5fc806bb8 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #20 0x7fd5fc7a04f8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #21 0x7fd5fc7ab67b in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #22 0x7fd5fb59d4b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #23 0x7fd5fc7a9c2c in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #24 0x7fd5fc81b48c in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #25 0x7fd5fc81e000 in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 26 0x7fd5fc7a04f8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6 #27 0x7fd5fb59d4b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #28 0x7fd5fbdfd0a9 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6 #29 0x7fd5fbe64f5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6 #30 0x7fd5fc3db454 in ??? () at /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6 #31 0x7fd5eead9436 in g_main_dispatch.lto_priv () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fd5eeb3a107 in g_main_context_iterate_unlocked.isra () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fd5eead88c3 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fd5fb8af8f3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #35 0x7fd5fb5aa893 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #36 0x7fd5fb5a5e7e in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt6Core.so.6 #37 0x55ebb22a2aa9 in main (argc=, argv=) at /run/build/kontact/src/main.cpp:225 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502130] Plasmashell Crash on Startup 6.3.3
https://bugs.kde.org/show_bug.cgi?id=502130 --- Comment #3 from Shawn W Dunn --- Here's the best I've been able to get, after installing about 200 debuginfo packages. (gdb) bt #0 __GI_abort () at abort.c:91 #1 0x7fb6ce0311a0 in ??? () at /lib64/libgallium-25.0.2.so #2 0x7fb6ce034ec4 in ??? () at /lib64/libgallium-25.0.2.so #3 0x7fb6cdb575d9 in ??? () at /lib64/libgallium-25.0.2.so #4 0x7fb6cdb8b837 in ??? () at /lib64/libgallium-25.0.2.so #5 0x7fb6e4099546 in start_thread (arg=) at pthread_create.c:448 #6 0x7fb6e411d94c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502130] Plasmashell Crash on Startup 6.3.3
https://bugs.kde.org/show_bug.cgi?id=502130 --- Comment #2 from Shawn W Dunn --- Yes, I'm aware this backtrace isn't useful, I'm working on getting one that is. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 497873] Neochat just stops updating, after random periods of time
https://bugs.kde.org/show_bug.cgi?id=497873 Shawn W Dunn changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #13 from Shawn W Dunn --- So after some further investigation, this appears to be a problem with EMS hosted matrix servers, and not an issue with neochat. I've been using alternative Matrix clients (element, iamb, fluffychat, nheko) and I'm seeing the same behavior with the fedora homeserver on *all* of them. There's a bit of chatter I've seen out there on the web about the same issue with other EMS hosted servers. So closing, to get this off your list of open bugs, as it's not a neochat problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502130] New: Plasmashell Crash on Startup 6.3.3
https://bugs.kde.org/show_bug.cgi?id=502130 Bug ID: 502130 Summary: Plasmashell Crash on Startup 6.3.3 Classification: Plasma Product: plasmashell Version: 6.3.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: sfal...@cloverleaf-linux.org Target Milestone: 1.0 SUMMARY Plasma shell crashed on boot STEPS TO REPRODUCE 1. Start computer 2. Login to Plasma via sddm OBSERVED RESULT Plasmashell crashed, but recovered. EXPECTED RESULT Plasmashell not crashing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kalpa Desktop (openSUSE) Linux 6.13.7-1-default, Wayland KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION Nate asked me to file a bug, so I filed a bug. Backtrace: (gdb) bt #0 __GI_abort () at abort.c:91 #1 0x7fb6ce0311a0 in ?? () #2 0x00300018 in ?? () #3 0x7fb6ddbff8a0 in ?? () #4 0x7fb6ddbff7e0 in ?? () #5 0x8f12626ef5c15600 in ?? () #6 0x00010005 in ?? () #7 0x7fb6ddbff7a0 in ?? () #8 0x00020002 in ?? () #9 0x559c73f60720 in ?? () #10 0x7fb6ddbff810 in ?? () #11 0x559c72af12c0 in ?? () #12 0x in ?? () -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 504472] New: Tokodon can't authorize via OIDC
https://bugs.kde.org/show_bug.cgi?id=504472 Bug ID: 504472 Summary: Tokodon can't authorize via OIDC Classification: Applications Product: Tokodon Version First 25.04.1 Reported In: Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sfal...@cloverleaf-linux.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When setting up Tokodon, I am unable to finalize the authorization from my Mastodon server. STEPS TO REPRODUCE 1. flatpak run org.kde.tokodon 2. Select "Use Existing Account" 3. enter "fosstodon.org" into the Server ID Field 4. Press Continue 5. Click on "Open Authorization Page" 6. fosstodon Authorization page opens in Zen Browser 7. Click "Authorize" Button OBSERVED RESULT Nothing happens. EXPECTED RESULT Authorization token is passed from the Zen Browser back to Tokodon, and the Fosstodon account loads in Tokodon SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kalpa Desktop, Linux 6.14.6 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 ADDITIONAL INFORMATION This behavior is consistent for every Mastodon account I have, I'm just using Fosstodon as an example. It is also consistent if I change my default browser to Firefox, or Vivaldi -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 504472] Tokodon can't authorize via OIDC
https://bugs.kde.org/show_bug.cgi?id=504472 --- Comment #1 from Shawn W Dunn --- As a followup, if I "Copy the authentication link" and paste it into Vivaldi, or some other Chromium based flatpak browser, the Authentication handoff works just fine. I don't know why it took me this long to think of trying that. This *appears* to be a Firefox/Zen flatpak issue, but the token handoff works fine for other things like Neochat and Nextcloud flatpaks, with Firefox/Zen, so I'm not certain. -- You are receiving this mail because: You are watching all bug changes.
