[choqok] [Bug 472338] New: No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 Bug ID: 472338 Summary: No longer loading twitter timelines Classification: Applications Product: choqok Version: 1.7.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Twitter Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- SUMMARY For about a week now, Choqok no longer loads any Twitter timelines. (Realising this may be due to the various shenanigans that have been going on with the Twitter service.) STEPS TO REPRODUCE 1. Start Choqok 2. Click the Update Timelines button. OBSERVED RESULT No new posts for any Twitter account loaded. Last post within Choqok is from five days ago. EXPECTED RESULT Expect recent Twitter posts to be loaded and displayed. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 --- Comment #3 from Evan McLean --- As a workaround, would there be a way to fiddle the Choqok config file to remove the Local and Federated timelines? Because they keep contributing to the unread count in the tray icon, it makes it difficult to know when there's something new in the timelines I'm more interested in. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 --- Comment #2 from Evan McLean --- There seems to be an additional bug with the Edit Account configuration window: On the first tab, it does not remember the domain part of your credentials. So add the '@domain' part back and it then click Ok and it will close without an error message (although it still does not save the details properly). -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 Evan McLean changed: What|Removed |Added CC||ecogn...@michevan.id.au -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] New: Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 Bug ID: 461484 Summary: Unable to save unchecked timelines for Mastodon account Classification: Applications Product: choqok Version: Git Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Mastodon Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- SUMMARY I am trying to uncheck the Local and Federated timelines from my Mastodon account (only really want to display Home) however when I save, it does not have any effect. When I reopen the account settings, all timelines are still checked. STEPS TO REPRODUCE 1. Select Settings -> Configure Choqok from the main window's menu. 2. Select Accounts panel in configuration window. 3. Click on your Mastodon account. 4. Click Modify... 5. Click the Timelines Configuration tab. 6. Uncheck the Local and Federated timelines. 7. Click OK to save account settings. 8. Click OK in the Configuration window to save and close it. OBSERVED RESULT You'll notice in the main window that the Local and Federated timelines are still visible. If you repeat steps 1 to 5, you'll also see that all the timelines are still checked. EXPECTED RESULT The Local and Federated timelines would not be visible or retrieved. The checkboxes for those two timelines would be unchecked in the account settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7+kde+r168 (also 6.4.0) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 419005] Add a keyboard shortcut to mark current timeline as read
https://bugs.kde.org/show_bug.cgi?id=419005 Evan McLean changed: What|Removed |Added CC||ecogn...@michevan.id.au -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 419005] New: Add a keyboard shortcut to mark current timeline as read
https://bugs.kde.org/show_bug.cgi?id=419005 Bug ID: 419005 Summary: Add a keyboard shortcut to mark current timeline as read Product: choqok Version: 1.7.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- There is currently a shortcut to mark ALL timelines as read (ctrl-R by default). It would be very handy to be able to mark the currently viewed timeline as read. Equivalent to the little button that appears above the scrollbar in the top right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command
https://bugs.kde.org/show_bug.cgi?id=217950 --- Comment #44 from Evan McLean <ecogn...@michevan.id.au> --- Any chance of an example of how to use this? Say, from the command line with dbus-send? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command
https://bugs.kde.org/show_bug.cgi?id=217950 --- Comment #39 from Evan McLean <ecogn...@michevan.id.au> --- Well, the patch[1] I have been using for the last few years ago is now no good as I've moved to Plasma 5. Until it is possible to do this via dbus again, I've found a workaround that is acceptable for my use, at least. Thought I would document it here in case anyone else finds it useful: 1. Go to Desktop Settings/Wallpaper for the screen. 2. Change Wallpaper Type to Slideshow. 3. Change timeout to a short value, I use ten seconds. 4. Add a folder that only contains the currently desired wallpaper image. Then, when you want to change wallpapers, delete the current image in the folder, and move/link[2] the new image. The new image should have a different file name to the previous one. For more than one screen, do this for each screen, each with its own folder. Have been using this technique seamlessly for a few weeks now from my wallpaper managing shell script[3]. [1] https://bugs.kde.org/show_bug.cgi?id=217950#c15 [2] Best not to copy the image. The move or linking is (effectively) an atomic operation, whereas the desktop my try to load an incomplete image file while it is being copied. [3] http://www.michevan.id.au/content/wallpaper-system-info-management-script/ (outdated) -- You are receiving this mail because: You are watching all bug changes.
