[kdenlive] [Bug 470229] New: KDENLIVE crashing because of permissions issue
https://bugs.kde.org/show_bug.cgi?id=470229 Bug ID: 470229 Summary: KDENLIVE crashing because of permissions issue Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Installation Assignee: j...@kdenlive.org Reporter: m...@okstudio.com.au Target Milestone: --- SUMMARY *** For about a week, since last update, I cannot start the application at all. I am running Fedora Linux. This is the trace when I start it from terminal: profilePath from appDir/…/share: “/usr/share/mlt-7/profiles” meltPath from KdenliveSetting::rendererPath: “” meltPath from profilePath/…/…/…/bin: “/usr/bin/melt-7” Empty metadata for “audiochannels” Empty metadata for “audioconvert” Empty metadata for “imageconvert” Empty metadata for “glsl.manager” Empty metadata for “telecide” QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext QQmlEngine::setContextForObject(): Object already has a QQmlContext qrc:/qml/timeline.qml:497: ReferenceError: proxy is not defined qrc:/qml/timeline.qml:478: ReferenceError: proxy is not defined QGradient::setColorAt: Color position must be specified in the range 0 to 1 QGradient::setColorAt: Color position must be specified in the range 0 to 1 QGradient::setColorAt: Color position must be specified in the range 0 to 1 QGradient::setColorAt: Color position must be specified in the range 0 to 1 QGradient::setColorAt: Color position must be specified in the range 0 to 1 QGradient::setColorAt: Color position must be specified in the range 0 to 1 *** STEPS TO REPRODUCE 1. Install KDENLIVE on Fedora 37 or 38 2. Try running the application OBSERVED RESULT Application does not start, only the flash screen freezes. EXPECTED RESULT Application should start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 or 38 ADDITIONAL INFORMATION This is a permissions issue because if i change user ID for current user to "0" (root) or run KDENLIVE with sudo, the application works fine. There are some issues in the traceback, but I have no problem opening, creating or editing projects. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 478459] New: Native Fast Indexer cannot find files in subfolders on mounted drive
https://bugs.kde.org/show_bug.cgi?id=478459 Bug ID: 478459 Summary: Native Fast Indexer cannot find files in subfolders on mounted drive Classification: Frameworks and Libraries Product: frameworks-baloo Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: gsalo...@live.co.uk 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 *** My system is set up to dual boot Debian 12 & Windows 11, with most of the disk dedicated to a shared drive used by both for file storage. When using the music indexing feature, using "Use fast native indexer", no files were found. Switching to the alternative, "Scan the filesystem directly", all music was found immediately and correctly. STEPS TO REPRODUCE 1. Mount an NTFS drive 2. Scan a folder on the NFTS drive containing a subfolder which contains music. OBSERVED RESULT No files were found with "Use fast native indexer", files immediately found with "Scan the filesystem directly" EXPECTED RESULT All files to be found with the fast native indexer. SOFTWARE/OS VERSIONS Windows: Windows 11 also installed on machine, but error occurred using the program in Debian. Linux/KDE Plasma: Debian GNU/Linux 12 (bookworm) x86_64 (available in About System) KDE Plasma Version: Plasma 5.27.5 KDE Frameworks Version: 5.27.5 Qt Version: Not sure, got errors running qmake-qt5 --version and qmake --version ADDITIONAL INFORMATION My first time using Elisa! I tried using Juk at first and eventually found that Elisa is supposed to be the music player of choice on KDE after having issues with Juk. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 478459] Native Fast Indexer cannot find files in subfolders on mounted drive
https://bugs.kde.org/show_bug.cgi?id=478459 --- Comment #1 from George --- Update, found the information screen: KDE Frameworks Version 5.103.0 Qt Version 5.15.8 (built against 5.15.8) Also having familiarised myself with the interface a little more I don't think I'll stick with Elisa. I don't see any functionality to make playlists based on rules like Juk or my (currently Windows exclusive, sadly) preferred media player Dopamine, which is essential functionality for me in a music player. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443993] Momentary blackscreen upon ejection of USB drive
https://bugs.kde.org/show_bug.cgi?id=443993 George changed: What|Removed |Added Resolution|WORKSFORME |NOT A BUG --- Comment #3 from George --- (In reply to David Edmundson from comment #2) > Please confirm if this is still an issue Hi, I don't actually know because I have since stopped using KDE as my daily driver. However, as no one else has reported this issue I think we can safely assume it was environmental, and therefore can likely be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] On Wayland, center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 George changed: What|Removed |Added CC||kdedisc...@px.fastmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477939] On Wayland, center-aligned panels cause left/right/top/bottom aligned panels sharing the same edge to not touch that edge
https://bugs.kde.org/show_bug.cgi?id=477939 --- Comment #22 from George --- Same for me on Fedora 40 - Wayland - Nvidia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487571] New: Firefox crashes when Explicit Sync is in use
https://bugs.kde.org/show_bug.cgi?id=487571 Bug ID: 487571 Summary: Firefox crashes when Explicit Sync is in use Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: vas...@gmail.com Target Milestone: --- SUMMARY When launching Firefox in Wayland mode (default nowadays, at least with Nightly/beta, probably stable too), on kwin 6.0.90.1-1 with Nvidia 555 series drivers, Firefox crashes very quickly on most web pages. about:support and some internal pages seem fine. The error message printed in console is from kwin, however, not Firefox, leading me to report it here. This is also reproducible in Mutter. STEPS TO REPRODUCE 1. Install Nvidia 555 series drivers on a system with Nvidia graphics as primary display (NOT Prime, Nvidia must be in use for the compositor) 2. Launch a plasma wayland session 3. Launch Firefox with MOZ_ENABLE_WAYLAND=1 (default), visit google.com (or many other pages reproduce) Setting MOZ_ENABLE_WAYLAND=0 or running a Xorg session works around this. OBSERVED RESULT Firefox crashes EXPECTED RESULT Firefox not to crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: kwin 6.0.90.1-1 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Firefox crashes with: [GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@66: error 4: explicit sync is used, but no acquire point is set This error print is within kwin code, here: https://invent.kde.org/plasma/kwin/-/blob/master/src/wayland/linux_drm_syncobj_v1.cpp#L164 Also reported to Mozilla and Mutter (and Nvidia by email), since this seems to reproduce in many areas: https://bugzilla.mozilla.org/show_bug.cgi?id=1898476 https://gitlab.gnome.org/GNOME/mutter/-/issues/3504 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437919] System settings crashes everytime
https://bugs.kde.org/show_bug.cgi?id=437919 George changed: What|Removed |Added CC||grg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437919] System settings crashes everytime
https://bugs.kde.org/show_bug.cgi?id=437919 --- Comment #6 from George --- Created attachment 144078 --> https://bugs.kde.org/attachment.cgi?id=144078&action=edit New crash information added by DrKonqi systemsettings5 (5.18.4) using Qt 5.12.8 - What I was doing when the application crashed: Simply open system setting from Start menu -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f1d77e7b859 in __GI_abort () at abort.c:79 #8 0x7f1d782afaad in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7f1d77c4b036 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7f1d78fa9947 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 453270] New: Have different import sources (Amazon, Discogs, Musicbrainz, etc.) parse metadata from provided URLs
https://bugs.kde.org/show_bug.cgi?id=453270 Bug ID: 453270 Summary: Have different import sources (Amazon, Discogs, Musicbrainz, etc.) parse metadata from provided URLs Product: kid3 Version: 3.9.x Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: intergalacti...@protonmail.ch Target Milestone: --- Created attachment 148505 --> https://bugs.kde.org/attachment.cgi?id=148505&action=edit Image showing reduced identification between editions Rather than File > Import Musicbrainz Release / Discogs, where you input artist and release name, make possible to provide a URL and have the metadata parsed. For example tag files by providing a URL such as: https://musicbrainz.org/release/c69d328a-5ea0-4b08-a4f7-93e6ac196563 or: https://www.discogs.com/release/1048226-Electric-Six-Se%C3%B1or-Smoke Reason: Research from Discogs/Musicbrainz may be already open in browser; faster to transport URL into kid3 than looking up information again within the program. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] New: Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 Bug ID: 453506 Summary: Need to kick hotkeys on release, not press Product: kwin Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chibiry...@gmail.com Target Milestone: --- SUMMARY *** Key combinations are consumed on press, not on release which leads to inability to activate some combinations at all. Let's say that I have 2 languages/layouts installed and I want my hotkey be CTRL+SHIFT to switch them. I will be unable to do any combination that has CTRL+SHIFT in it, like CTRL+SHIFT+S (Save as... in Kate) or CTRL+SHIFT+CURSOR_ARROW to select words one by one in a text, for example. Basically, it's a copy of this ancient xorg bug which will never be fixed upstream: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258 *** STEPS TO REPRODUCE 1. Have 2 languages/layouts installed 2. Make them switch using hotkey CTRL+SHIFT 3. Open Kate and type "The quick brown dog" 4. CTRL+SHIFT+<- (LEFT ARROW) to select the last word 5. Type "fox" OBSERVED RESULT The layout had been switched on the 4 step (before you pressed an arrow, because the hotkey was consumed on press) and there was no word selection, instead of "fox" you typed some other symbols in another language/layout, resulting in a sentence "The quick brown ащчdog" (Cyrillic symbols for example) EXPECTED RESULT Layout switching didn't occur, you selected the word "dog" and it was replaced with newly typed "fox", resulting in a sentence "The quick brown fox" SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.32-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I was very disappointed in finding out that this behaviour is present in wayland, because I was convinced that this would be fixed there from the start (there are a couple of posts about it dating 10 or so years ago), since it's basic and core functionality that was present on windows forever (and in many linux distros for a long time when maintainers just silently patched xorg by default). I'm not sure if it's a KWin issue or just Wayland, but there's was a similar Weston bug reported in the git some time ago, so I assumed it had to do with a compositor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 George changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from George --- (In reply to Andrey from comment #1) > IIRC Kwin's Modifier only shortcuts are trigger on release, could you check > that? > > I don't know if we have them documented, here are the links: > https://blog.martin-graesslin.com/blog/2016/08/modifier-only-shortcuts- > available-in-plasma-5-8/ > https://bucharjan.cz/blog/plasma-custom-modifier-only-shortcuts.html Hi Andrey! Thank you! I can say that in default Manjaro config I have the option to invoke the Application Launcher widget by releasing the Windows key. I'm not sure that Meta and Win keys are treated exactly the same technically, but anyways - it works on release. Hooray! Nothing happens if I just press it. Please advise on proper testing procedure if that is not enough. But if I: 1) Open the KDE System Settings GUI -> Input Devices -> Keyboard -> Advanced 2) Check the "Configure keyboard options" 3) Expand "Switching to another layout" 4) Pick any one of this bunch, for example: left alt, left ctrl, left win, left shift (and uncheck the rest) 5) And click Apply Then it would work on press anyway, I'm sorry to say. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] New: Import of credot card transaction with invalid merchant
https://bugs.kde.org/show_bug.cgi?id=440800 Bug ID: 440800 Summary: Import of credot card transaction with invalid merchant Product: kmymoney Version: 5.0.8 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: hexd...@fastmail.fm Target Milestone: --- I think that the import of credit card transactions is not working correctly when the Merchant Name is not already in KMyMoney. It appears that it is using the last known merchant Name instead of leaving it blank. Here is a recent example: PAYMENT 2021080616[0:UTC] -1.07 202108061 202108061 REPLACE Kindle Svcs*2P8C792O1 866-321-88 Kindle Svcs*2P8C792O1 866-321-88 This imported with a Merchant name of Zelle Transfer Conf# T0BN438LM; and there is no such a name anywhere in the file being imported. Not good. Is there a setting within KMyMoney to tell it to make it a blank or some such ? Help !!! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid merchant
https://bugs.kde.org/show_bug.cgi?id=440800 George changed: What|Removed |Added Platform|Mint (Debian based) |Mint (Ubuntu based) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 George changed: What|Removed |Added Summary|Import of credot card |Import of credot card |transaction with invalid|transaction with invalid |merchant|Payee -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credot card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 --- Comment #1 from George --- Merchant should say Payee -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440800] Import of credit card transaction with invalid Payee
https://bugs.kde.org/show_bug.cgi?id=440800 --- Comment #3 from George --- I tried 5.1.2.1e with the same result. I tried messing with the which OFX field to use for PAYID with no change. I tried NAME.(In reply to Jack from comment #2) > 5.0.8 was released January 2020. Is it possible for you to upgrade to a > newer version? You can also try using an AppImage > (https://kmymoney.org/appimage.html) > > I am not aware off any way to tell KMM to leave the Payee blank, but there > are settings reagarding which OFX filed to use as the source for the Payee. > However, you are correct that it should not create a payee from data > unlrelated to the transaction. > > One additional thought - please look at the payee info for "Zelle Transfer > Conf# T0BN438LM" and see if it has matching enabled, and if anything in the > new transaction happens to meet the matching criteria. The payee matching was the answer. when I took it off, the import worked as intended. thanks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434928] project file fails to open
https://bugs.kde.org/show_bug.cgi?id=434928 --- Comment #7 from George --- What needed information do you need as the problem still exists? On 26/04/2021 05:33, Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=434928 > > Bug Janitor Service changed: > > What|Removed |Added > > Resolution|WAITINGFORINFO |WORKSFORME > Status|NEEDSINFO |RESOLVED > > --- Comment #6 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.
[frameworks-kded] [Bug 436728] New: Invalid Type entry in desktop file
https://bugs.kde.org/show_bug.cgi?id=436728
Bug ID: 436728
Summary: Invalid Type entry in desktop file
Product: frameworks-kded
Version: 5.81.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: vas...@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
.desktop entry has an invalid Type= field, causing it to give warnings when
parsing. This is causing a warning when opening MenuLibre, a .desktop file
editor/parser.
No actual known usability impact beyond the field just being invalid.
STEPS TO REPRODUCE
1. Open org.kde.kded5.desktop file
2. Verify on Table 2 valid Type entries are "Application", "Link", or
"Directory" -
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#recognized-keys
OBSERVED RESULT
Type=Service
EXPECTED RESULT
Type={Application|Link|Directory}
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch, Plasma 5.81.0-1
(available in About System)
KDE Plasma Version: 5.81.0-1
KDE Frameworks Version: 5.81.0-1
Qt Version: 5.15.2+kde+r192-1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 417598] Every other frame inside window being dropped
https://bugs.kde.org/show_bug.cgi?id=417598 George changed: What|Removed |Added Version|5.18.0 |5.20.2 --- Comment #2 from George --- Update on this, I have just switched to kwinft and can confirm this issue is resolved by avoiding the use of kwin. Also bumping the version on this bug to 5.20.2 as I've confirmed it still exists with the latest kwin upstream release. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 474718] New: linuxfx does not look like windows 11
https://bugs.kde.org/show_bug.cgi?id=474718 Bug ID: 474718 Summary: linuxfx does not look like windows 11 Classification: Applications Product: khelpcenter Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: heavymetaldude1...@yahoo.com Target Milestone: --- i downloaded linuxfx 11.4.1 Redsand and purchased a license key but when i try to customize it to look like windows 11 the icons still look like linux. Not even the windows logo anywere. Pls help me with this problem thank u. have a nice night. George -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 --- Comment #7 from George --- (In reply to Yevhen from comment #6) > Is there a chance to have this bug fixed on Wayland? > For KWin Wayland I'm not aware of any workarounds. Old XKB patch > (https://aur.archlinux.org/cgit/aur.git/tree/freedesktop-bug-865. > patch?h=xorg-server-bug865) doesn't help on Wayland. It will most likely never be fixed by Wayland because it inherited libxkbcommon, that employs this very bug/behaviour. As it was never fixed in Xorg, because the specification is just old and bad (but it worked for 40-something years and people are afraid to change something like that with no new spec in sight). There may be some kind of a solution by the KDE team, as was discussed here and elsewhere, but I doubt that, given little numbers of people who care or whatever. And there's also this argument that you can change your hotkeys to something like Win+Space (or any other ungodly combination) and pretend that this bug doesn`t exist. I know, it's sad, but even I did it in the end. Anyway, you can try and submit a bug as per Andrey's request. I'll gladly join the discussion. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463061] qBittorrent System tray icon flashes constantly on KDE Plasma
https://bugs.kde.org/show_bug.cgi?id=463061 George changed: What|Removed |Added CC||begggi...@abv.bg --- Comment #1 from George --- I can reproduce, and confirm it's quite annoying. Arch/Manjaro 22.0.0, kernel 6.1 KDE Plasma: 5.26.4 KDE Frameworks: 5.101.0 Qt: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448235] New: Krita 5 for MacOSmojave is not launching due to a missing executable, i checked the files for Krita and only saw EmptySteamDepot with nothing inside of it meaning there was n
https://bugs.kde.org/show_bug.cgi?id=448235 Bug ID: 448235 Summary: Krita 5 for MacOSmojave is not launching due to a missing executable, i checked the files for Krita and only saw EmptySteamDepot with nothing inside of it meaning there was nothing actually downloaded. It had an instant download because no files existed. Product: krita Version: 5.0.2 Platform: Other OS: macOS Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: georgeporge2...@gmail.com Target Milestone: --- Created attachment 145312 --> https://bugs.kde.org/attachment.cgi?id=145312&action=edit 1 is the EmptySteamDepot file and the other is what steam says when i try to launch 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. Pay for krita (MacOS 2. download it 3. see that you can't get into it because it states: OBSERVED RESULT An error occurred while updating Krita(Missing executable): /users/okeefe/Library/Application Support/Steam/steamapps/common/Krita/krita.app/contents/MacOS/Krita see the steam support site for more information EXPECTED RESULT for the files to have actually downloaded, and for me to access the app SOFTWARE/OS VERSIONS Windows: macOS: yes 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.
[krita] [Bug 448235] Krita 5 for MacOSmojave is not launching due to a missing executable, i checked the files for Krita and only saw EmptySteamDepot with nothing inside of it meaning there was nothin
https://bugs.kde.org/show_bug.cgi?id=448235 George changed: What|Removed |Added Latest Commit||10/01/22 (british date) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 449361] New: Have Kid3 save configuration settings in an ini file rather then the registry for Windows.
https://bugs.kde.org/show_bug.cgi?id=449361 Bug ID: 449361 Summary: Have Kid3 save configuration settings in an ini file rather then the registry for Windows. Product: kid3 Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: intergalacti...@protonmail.ch Target Milestone: --- Taken from the handbook: "With KDE, the settings are stored in .config/kid3rc, the application state in .local/share/kid3/kid3staterc. As a Qt™ application, this file is in .config/Kid3/Kid3.conf. On Windows®, the configuration is stored in the registry. on macOS® in a plist file." Have Kid3 save configuration settings in an ini file rather then the registry. Migrating settings between Linux and Windows will be a breeze. Currently settings have to be entered fresh into a new Windows installation - probably will have to be redone on reinstallation. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434928] New: project file fails to open
https://bugs.kde.org/show_bug.cgi?id=434928 Bug ID: 434928 Summary: project file fails to open Product: kdenlive Version: 20.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: george_br...@expressmail.dk Target Milestone: --- SUMMARY Saved project file does not open STEPS TO REPRODUCE 1. double click to open .kdenlive project file or right click open with kdenlive 2. kdenlive opens 3. error message error opening file - kdenlive 'cannot open project file' OBSERVED RESULT will open file using the in-program 'open' button EXPECTED RESULT file to open SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux mint 19.3 KDE Plasma Version: KDE Frameworks Version: KDE Frameworks 5.76.0 Qt Version: Qt 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434928] project file fails to open
https://bugs.kde.org/show_bug.cgi?id=434928 --- Comment #2 from George --- Yes I'm using the appimage version tried launching it from the terminal, but I'm not that good at it and tried to launch it, but gave up. The project was created in this new version I have found another way the file opened: rightclick on project file and use open with - kdenlive wasn't in the file list so had to make custom link- after that I could double click any kdenlive project file and it opened kdenlive and the file. Previously kdenlive opened by doubleclicking file, but didn't recognise the .kdenlive file and didn't open it. not sure why this step had to be done. On 25/03/2021 13:10, Vincent PINON wrote: > https://bugs.kde.org/show_bug.cgi?id=434928 > > Vincent PINON changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Vincent PINON --- > I guess you are using AppImage, right? > Can you launch it from terminal and see if there are messages in the console? > Was the project created with an older version ? > - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434928] project file fails to open
https://bugs.kde.org/show_bug.cgi?id=434928 --- Comment #4 from George --- Not quite, I've just been testing other files I have and some open, some do not. They all open from within kdenlive, but not all from their project files. On 27/03/2021 20:25, Vincent PINON wrote: > https://bugs.kde.org/show_bug.cgi?id=434928 > > --- Comment #3 from Vincent PINON --- > Sorry, it is not very clear to me: is your problem solved now? > - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378216] Kmail / Kontact crash when moving & copying mail folders
https://bugs.kde.org/show_bug.cgi?id=378216 --- Comment #8 from George --- Hi and thanks for getting in touch. The bug was reported 3+ years ago, my sense is that the problem was fixed, or at least, significantly improved. I spent a lot of time with Kontact and learned a fair bit about the app, but I finally abandoned it in favour of Evolution, which runs well and integrates perfectly with my KDE Plasma Breeze Dark themes. Evolution offers many of the features that Kontact provided to me as a single user. Evolution is just much easier to configure, and thus, more reliable than Kontact. All the best, George On Fri, 2021-01-01 at 04:36 +, Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=378216 > > --- Comment #7 from Bug Janitor Service --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be 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 > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 492404] Dolphin doesn't select/mark the parent folder when Up or Back is being pressed
https://bugs.kde.org/show_bug.cgi?id=492404 George changed: What|Removed |Added CC||begggi...@abv.bg --- Comment #11 from George --- You call it a feature, some may call it a regression or a bug. I call it counterintuitive. Windows File Explorer works like this since 1995. If you feel like it's an improvement, by all means, offer it for NEW users who don't have the muscle memory of navigating directories for the last 30 years, but include an option/checkmark so people can still manually select the old (legacy) behaviour even if it isn't the default one. For example: [x] highlight and select parent directory when going back/up This is especially annoying when using the keyboard to navigate. Going up from a directory should not mean rebooting your computer and starting from scratch. There are directory trees with thousands of branches and that makes it unusable in any view, including tree. Nautilus and our friends from Gnome, have adopted the following behaviour for going back in folders: A small message saying "$directory_name" is selected (containing x items) Deleting files by accident is a permission problem, but foremost a PEBCAK and not something a file manager should be solving. Just my 2 cents. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 493064] New: JuK crashes when scrolling up on the symbol in the systray
https://bugs.kde.org/show_bug.cgi?id=493064 Bug ID: 493064 Summary: JuK crashes when scrolling up on the symbol in the systray Classification: Applications Product: juk Version: 23.08.5 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: whee...@kde.org Reporter: private.r...@gmail.com CC: mp...@kde.org Target Milestone: --- Application: juk (23.08.5) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.0-44-generic x86_64 Windowing System: X11 Distribution: Ubuntu 24.04.1 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: My JuK reliably crashes when I select a song from my list that isn't the very first one, cause it to play, then scroll up on the JuK icon in the "tray" part of the taskbar. If the scroll isn't going over the top edge, it changes the song normally, altough extremely quickly and uncontrollably, though this might have to do with me using a trackpad (laptop). I've reproduced the crash with different songs sorted to the top of the list, including where none of them have album art and where all of them have album art. (Displaying the album art seems janky at times, but this is probably a completely unrelated detail) The crash can be reproduced every time. -- Backtrace: Application: JuK (juk), signal: Segmentation fault [KCrash Handler] #4 TagLib::File::isOpen (this=this@entry=0x0) at /usr/src/taglib-1.13.1-1build1/taglib/toolkit/tfile.cpp:421 #5 0x7924869e9e95 in TagLib::File::isValid (this=this@entry=0x0) at /usr/src/taglib-1.13.1-1build1/taglib/toolkit/tfile.cpp:426 #6 0x58148c14b1f1 in CoverInfo::hasEmbeddedAlbumArt (this=this@entry=0x58148ea587e0) at /usr/src/juk-4:23.08.5-0ubuntu3/coverinfo.cpp:289 #7 0x58148c14b67d in CoverInfo::hasCover (this=this@entry=0x58148ea587e0) at /usr/src/juk-4:23.08.5-0ubuntu3/coverinfo.cpp:118 #8 0x58148c14bd88 in CoverInfo::pixmap (this=0x58148ea587e0, size=CoverInfo::FullSize) at /usr/src/juk-4:23.08.5-0ubuntu3/coverinfo.cpp:222 #9 0x58148c1a33f9 in SystemTray::slotPlay (this=0x58148e8237c0) at /usr/src/juk-4:23.08.5-0ubuntu3/systemtray.cpp:219 #10 0x792484b12e16 in QtPrivate::QSlotObjectBase::call (a=0x7ffd25d30860, r=0x58148e8237c0, this=0x58148e82b750) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x58148df86140, signal_index=9, argv=0x7ffd25d30860) at kernel/qobject.cpp:3925 #12 0x792484b12e16 in QtPrivate::QSlotObjectBase::call (a=0x7ffd25d30990, r=0x58148df86140, this=0x58148e1ae050) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x58148e291750, signal_index=3, argv=0x7ffd25d30990) at kernel/qobject.cpp:3925 #14 0x792486a98b15 in Phonon::MediaObject::stateChanged(Phonon::State, Phonon::State) () at /lib/x86_64-linux-gnu/libphonon4qt5.so.4 #15 0x792486a99ca9 in Phonon::MediaObjectPrivate::_k_stateChanged(Phonon::State, Phonon::State) () at /lib/x86_64-linux-gnu/libphonon4qt5.so.4 #16 0x792484b06343 in QObject::event (this=0x58148e291750, e=0x58148e2a1b80) at kernel/qobject.cpp:1347 #17 0x79248576bd45 in QApplicationPrivate::notify_helper (this=, receiver=0x58148e291750, e=0x58148e2a1b80) at kernel/qapplication.cpp:3640 #18 0x792484ad8118 in QCoreApplication::notifyInternal2 (receiver=0x58148e291750, event=0x58148e2a1b80) at kernel/qcoreapplication.cpp:1064 #19 0x792484ad8332 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #20 0x792484adb94b in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x58148de55f50) at kernel/qcoreapplication.cpp:1821 #21 0x792484adbebd in QCoreApplication::sendPostedEvents (receiver=, event_type=) at kernel/qcoreapplication.cpp:1680 #22 0x792484b35c0f in postEventSourceDispatch (s=0x58148df3e250) at kernel/qeventdispatcher_glib.cpp:277 #23 0x7924833145b5 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x792483373717 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x792483313a53 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x792484b35279 in QEventDispatcherGlib::processEvents (this=0x58148df43d30, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #27 0x792484ad6a7b in QEventLoop::exec (this=this@entry=0x7ffd25d30e50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #28 0x792484adf3e8 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #29 0x58148c121a6b in main (argc=, argv=) at /usr/src/juk-4:23.08.5-0ubuntu3/main.cpp:97 [Inferior 1 (process 2899) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug ch
[frameworks-kio] [Bug 482519] Copy dialog has disappeared
https://bugs.kde.org/show_bug.cgi?id=482519 George changed: What|Removed |Added CC||begggi...@abv.bg --- Comment #20 from George --- +1 The same issue is observed on my end. It's highly impactful, so if possible, please look into it with priority Operating System: Manjaro Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.41-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7400T CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: LENOVO Product Name: 90HC0012UK System Version: ideacentre 620S-03IKL -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413235] New: Autostart entry defaults enabled in all DEs
https://bugs.kde.org/show_bug.cgi?id=413235 Bug ID: 413235 Summary: Autostart entry defaults enabled in all DEs Product: Discover Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: vas...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY The autostart entry for Discover defaults enabled in all desktop environments. This causes people in Gnome or other DEs that also have the KDE stack installed to have two software centers at boot. Note that for comparison, Gnome Software Center's .desktop file contains "OnlyShowIn=GNOME;Unity;" which has the expected behavior of not booting within other DEs. STEPS TO REPRODUCE 1. Install Discover 2. Log into any DE other than KDE OBSERVED RESULT Discover starts along with the DE's native software installer EXPECTED RESULT Only the software installers native to the DE start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (latest) w/ KDE discover-5.17.0-1 (available in About System) KDE Plasma Version: 5.17.0-1 KDE Frameworks Version: 5.63.0-1 Qt Version: 5.13.1-2 ADDITIONAL INFORMATION Fix is to add the following to the .desktop file (may want to add additional DEs that depend on this component): OnlyShowIn=KDE; -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417598] New: Every other frame inside window being dropped
https://bugs.kde.org/show_bug.cgi?id=417598 Bug ID: 417598 Summary: Every other frame inside window being dropped Product: kwin Version: 5.18.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scene-opengl Assignee: kwin-bugs-n...@kde.org Reporter: vas...@gmail.com Target Milestone: --- At least with both Firefox and Chrome using the test detailed below, it seems that my display is only receiving every other frame (with perfect cadence) that is rendered by the browsers. I've tested with both OpenGL2.1 and 3.0 compositors and can reproduce on both. I cannot reproduce this on Gnome shell. kwin 5.16 had the same issue a few months ago so this is not a new regression. STEPS TO REPRODUCE 1. Visit https://www.testufo.com/blackframes#count=2&bonusufo=1&equalizer=1&background=00 in either Chrome or FF OBSERVED RESULT 1. The middle UFO is either completely missing (black frames only being shown) or twice the expected brightness (black frames not being shown). 2. The topmost and bottommost UFOs are operating at the same speed (visibly, both show proper framerates according to the browsers - this is a presentation issue not rendering). EXPECTED RESULT 1. The middle UFO should look substantially sharper but at the same brightness and speed as the top UFO. This one is using black-frame-insertion. 2. The bottommost UFO should be showing at twice the framerate (visibly smoother, usually looks slightly 'ahead' as well). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch with Plasma 5.18.0 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION This is using the Nvidia binary driver on X11. I have had other people via Discord/IRC duplicate the issue, though it may only impact Nvidia users as no AMD users reported back. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396236] wayland: systemsettings changing order and scale of monitor is not persisted between reboots
https://bugs.kde.org/show_bug.cgi?id=396236 george changed: What|Removed |Added CC||stu...@anchev.net --- Comment #1 from george --- Rotation is not persistent too. I have one monitor 90 rotated counterclockwise and it gets reset after reboot. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396236] wayland: systemsettings changing order and scale of monitor is not persisted between reboots
https://bugs.kde.org/show_bug.cgi?id=396236 --- Comment #2 from george --- I don't think it is related to wayland. I don't use wayland and I have noticed this bug more than a year ago. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396236] wayland: systemsettings changing order and scale of monitor is not persisted between reboots
https://bugs.kde.org/show_bug.cgi?id=396236 --- Comment #3 from george --- Workaround for rotation: Add this to startup script: xrandr --output --rotate left -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] New: Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 Bug ID: 397094 Summary: Scheduled transaction date keeps incrementing to current date in ledger Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: gpags...@gmail.com Target Milestone: --- Schedule transaction gets entered on the correct date into the ledger (e.g 7/31/18). However, the date for the transaction increments to the current date - the 7/31 transaction will always show with the current date. If I look at the scheduled transaction after 7/31, it still shows the next due date of 7/31. I cannot change the date in the ledger. I need to delete the scheduled transaction from the ledger and enter a manual transaction. This has happened with every scheduled transaction I have. Running on Linux Mint 19 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 george changed: What|Removed |Added CC||stu...@anchev.net --- Comment #3 from george --- The only reason I am not using Falkon is because I cannot install uMatrix, uBlock Origin and HTTPS everywhere. (sorry but Adblock Plus is not a replacement for the above) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393358] Web Extensions support
https://bugs.kde.org/show_bug.cgi?id=393358 --- Comment #7 from george --- > It's not possible to implement WebExtensions support in Falkon, it needs to > be done in QtWebEngine. Then why was QtWebEngine chosen in the first place? What is so good about it that justifies such a significant limitation? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375215] "Cannot Create Embedded Terminal"
https://bugs.kde.org/show_bug.cgi?id=375215 --- Comment #2 from George --- Thanks Alex. Funny thing is that the Fedora repo offers NO Krusader 2.5.0 version, only the 2.4 beta. I can download and reinstall from the Krusader site; do you guys have a public signing key and checksums posted for Krusader 2.5? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375334] New: Closing a document changes focus to zoom window in the active document
https://bugs.kde.org/show_bug.cgi?id=375334 Bug ID: 375334 Summary: Closing a document changes focus to zoom window in the active document Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: geo...@consultant.bg Target Milestone: --- Created attachment 103559 --> https://bugs.kde.org/attachment.cgi?id=103559&action=edit Screenshots of described steps Steps to Reproduce: 1) Open multiple documents in okular. 2) Close the active document with the red x-button. Actual Results: 3) In active document, the focus/pointer goes to zoom window, even if it was not there before. 4.1) If arrow down key is pressed, the zoom level changes to next higher default value, e.g. from 100% to 125%. 4.2) If arrow up key is pressed, the zoom level changes to next lower default value, e.g. from 100% to 75%. 5) If arrow down/up key is pressed again, the document starts scrolling down/up as usual and zoom does not change any more. Expected Results: The active document should scroll up/down and zoom level should not change. If mouse wheel is used instead of arrow keys, scrolling is as usual and zoom does not change, but the focus/pointer stays in zoom window and pressing an arrow key reproduces the bug - zoom level changes by one step and then scrolls as usual. The problem does not occur when closing a document which is on the background / not-active. Platform: kubuntu 14.04 KDE Platform Version 4.13.3 okular Version 0.19.3 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389169] New: No setting to disable JavaScript and 3rd party content in Akregator
https://bugs.kde.org/show_bug.cgi?id=389169 Bug ID: 389169 Summary: No setting to disable JavaScript and 3rd party content in Akregator Product: akregator Version: unspecified Platform: openSUSE RPMs URL: http://www.kde.org/dotkdeorg.rdf OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: stu...@anchev.net Target Milestone: --- I notice that on some of the RSS feeds which Akregator reads there are embedded, playable YouTube videos (e.g. http://www.kde.org/dotkdeorg.rdf). This means: JavaScript code is running and this is dangerous in the age of Spectre/Meltdown. Additionally I can't find a setting to disable images/css from 3rd parties (i.e. not coming from the original website) to prevent tracking. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389169] No setting to disable JavaScript and 3rd party content in Akregator
https://bugs.kde.org/show_bug.cgi?id=389169 --- Comment #1 from george --- akregator-17.04.2-2.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389169] No setting to disable JavaScript and 3rd party content in Akregator
https://bugs.kde.org/show_bug.cgi?id=389169 --- Comment #3 from george --- That was quick. Thank you! Could you please confirm if the fix addresses both issues (JS + 3rd party resources)? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 389169] No setting to disable JavaScript and 3rd party content in Akregator
https://bugs.kde.org/show_bug.cgi?id=389169 --- Comment #5 from george --- Thanks for explaining. In that case this should not be considered RESOLVED FIXED as it is obviously not? Unfortunately I am afraid that Adblock is not good enough. It would be great if you rather support something like uBlock Origin and uMatrix which are great extensions for enhancing online privacy. Or provide similar functionality in Akregator. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381079] Oversaturated thumbs for sRGB images
https://bugs.kde.org/show_bug.cgi?id=381079 --- Comment #2 from george --- Created attachment 108770 --> https://bugs.kde.org/attachment.cgi?id=108770&action=edit screenshot [~]: rpm -q gwenview5 gwenview5-17.04.2-1.5.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381079] Oversaturated thumbs for sRGB images
https://bugs.kde.org/show_bug.cgi?id=381079 --- Comment #3 from george --- Created attachment 108771 --> https://bugs.kde.org/attachment.cgi?id=108771&action=edit original image -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381079] Oversaturated thumbs for sRGB images
https://bugs.kde.org/show_bug.cgi?id=381079 --- Comment #5 from george --- Created attachment 108772 --> https://bugs.kde.org/attachment.cgi?id=108772&action=edit color settings (In reply to Nate Graham from comment #4) > Thank you! I wonder if this is related to or caused by > https://bugs.kde.org/show_bug.cgi?id=359909...? TLDR: I use EIZO CG275W calibrated with ColorNavigator (in Windows environment). FWIW EIZO CG monitors store their calibration LUTs in the monitor hardware. I also have oyranos installed. The ICC profile in Linux is soft-linked to the ICC file on the Windows partition and assigned in KDE through Settings->Configure Desktop->Color Management->Devices. In Color Management settings I have relative colorimetric intent (see attachment). In other programs like RawTherapee or digikam there are no such discrepancies, so I don't think it is related to monitor profile in any way. Please let me know if there any other settings which I need to check. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 386989] New: Cannot open file received through Bluetooth
https://bugs.kde.org/show_bug.cgi?id=386989 Bug ID: 386989 Summary: Cannot open file received through Bluetooth Product: Bluedevil Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kio-bt Assignee: now...@gmail.com Reporter: stu...@anchev.net Target Milestone: --- After I get a tooltip notification that the file has been received (sending from my phone) I cannot open it by clicking the "Open" button on the tooltip. I get a message: Error - KIO Client Unable to run the command specified. The file or folder /usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/GT-I8190 does not exist. Of course the files are there (in my ~/downloads/bluetooth) and through Dolphin I can reach them. This is openSUSE Leap 42.3 using KDE Plasma 5.8.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386989] Cannot open file received through Bluetooth
https://bugs.kde.org/show_bug.cgi?id=386989 --- Comment #2 from george --- (In reply to Kai Uwe Broulik from comment #1) > Possible duplicate of Bug 384740? Not exactly the same description but close > enough. Yes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387241] New: Plasma crashed after I set the Redshift Control widget to be always visible from the System Tray Settings
https://bugs.kde.org/show_bug.cgi?id=387241 Bug ID: 387241 Summary: Plasma crashed after I set the Redshift Control widget to be always visible from the System Tray Settings Product: plasmashell Version: 5.11.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: georgekoske...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.13.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I logged out and logged in. No other applications open. Just right clicked the system tray and opened system tray settings. Enabled Redshift Control on Extra Items and clicked Apply. Then I set the entry visibility to Shown and clicked Apply again. Plasma crashed and restarted after that, but the redshift control settings were working. - Unusual behavior I noticed: Before the above happened and before I logged out, I tried to do the same thing from the system Tray Settings and nothing crashed but the System tray was glitched out. When I hit the "Show Hidden icons" button, the buttons looked messy and all over the place. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3a05b1d80 (LWP 20575))] Thread 20 (Thread 0x7fd2ae7fc700 (LWP 21410)): #0 0x7fd399bdcfb9 in syscall () at /lib64/libc.so.6 #1 0x7fd394c1794a in g_cond_wait_until () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd394ba60e1 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd394ba669c in g_async_queue_timeout_pop () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd394bfa23e in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #7 0x7fd399be26bf in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fd2aeffd700 (LWP 21409)): #0 0x7fd399bd7f0b in poll () at /lib64/libc.so.6 #1 0x7fd2b604 in () at /usr/lib64/libasound.so.2 #2 0x7fd2b94b in snd_pcm_wait () at /usr/lib64/libasound.so.2 #3 0x7fd2b8b35573 in () at /usr/lib64/gstreamer-1.0/libgstalsa.so #4 0x7fd2b8fc3a21 in () at /usr/lib64/libgstaudio-1.0.so.0 #5 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #7 0x7fd399be26bf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fd2af7fe700 (LWP 21408)): #0 0x7fd399bdcfb9 in syscall () at /lib64/libc.so.6 #1 0x7fd394c1782f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd2ba2ce2eb in () at /usr/lib64/libgstreamer-1.0.so.0 #3 0x7fd394bfa160 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd399be26bf in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fd2b0dfb700 (LWP 21407)): #0 0x7fd399bdcfb9 in syscall () at /lib64/libc.so.6 #1 0x7fd394c1782f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd2ba2ce2eb in () at /usr/lib64/libgstreamer-1.0.so.0 #3 0x7fd394bfa160 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd399be26bf in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fd2b15fc700 (LWP 21406)): #0 0x7fd399bdcfb9 in syscall () at /lib64/libc.so.6 #1 0x7fd394c1782f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd2ba2ce2eb in () at /usr/lib64/libgstreamer-1.0.so.0 #3 0x7fd394bfa160 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd399be26bf in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fd2b200a700 (LWP 21405)): #0 0x7fd399bdcfb9 in syscall () at /lib64/libc.so.6 #1 0x7fd394c1782f in g_cond_wait () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd2b94b26eb in () at /usr/lib64/libgstbase-1.0.so.0 #3 0x7fd2b94b3a28 in gst_data_queue_pop () at /usr/lib64/libgstbase-1.0.so.0 #4 0x7fd2b3329401 in () at /usr/lib64/gstreamer-1.0/libgstcoreelements.so #5 0x7fd2ba2ce109 in () at /usr/lib64/libgstreamer-1.0.so.0 #6 0x7fd394bfa160 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fd394bf9795 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fd399491558 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd399be26bf in clone () at /lib64/
[gwenview] [Bug 387567] New: Panning and window resizing in gwenview is laggy
https://bugs.kde.org/show_bug.cgi?id=387567 Bug ID: 387567 Summary: Panning and window resizing in gwenview is laggy Product: gwenview Version: 17.04.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: stu...@anchev.net Target Milestone: --- Panning images bigger than the viewport is stepped/laggy. (Panning the same images in gimp is fast and fluid) Also resizing the window of gwenview when the image is zoomed in is also laggy. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 --- Comment #4 from George --- Just happened again this month. The scheduled txns are set up to automatically be entered in the ledger, which they are. However, once there the txn never becomes 'current' and therefore can't be edited. May have something to do with the scheduled date not being a weekday. I'll try to pay closer attention next time it happens rather that just fixing it by deleting the scheduled text and entering a manual txn. Sent from BlueMail On Jan 26, 2019, 18:56, at 18:56, Jack wrote: >https://bugs.kde.org/show_bug.cgi?id=397094 > >Jack changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO >CC||ostroffjh@users.sourceforge > ||.net > Resolution|--- |WAITINGFORINFO > >--- Comment #3 from Jack --- >Please let us know if the suggestions helped, or if you still have the >problem. > >-- >You are receiving this mail because: >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 397094] Scheduled transaction date keeps incrementing to current date in ledger
https://bugs.kde.org/show_bug.cgi?id=397094 --- Comment #12 from George --- Thomas, My scheduled transactions are all set up exactly as you outlined in your stream of emails. I only have an issue once in a while (still trying to figure out pattern) and only with a single schedule (I probably have 20-30 set up). I have 2 scheduled transactions set up as loan repayments and the problem appears to be related to that. Actually, I said I only had an issue with a single schedule, but the two loan schedules are very similar, so it could be either one or both of those. Either way, I have no issues with other types of transactions. At this point I'm thinking of just eliminating this type of scheduled transaction and making it a simple withdrawal or transfer. I don't require any further action from you on my behalf. I'm going to leave it as-is for now. If I see this happen again I'll try to note all the circumstances and forward to you. Thanks for looking into this. George On 1/27/19 8:59 AM, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=397094 > > --- Comment #11 from Thomas Baumgart --- > Created attachment 117685 >--> https://bugs.kde.org/attachment.cgi?id=117685&action=edit > Updated schedule > > Since the transaction was entered, the schedule was updated to the next due > date. The question now is: what is the problem? For me everything works as > designed. > -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381079] New: Oversaturated thumbs for sRGB images
https://bugs.kde.org/show_bug.cgi?id=381079 Bug ID: 381079 Summary: Oversaturated thumbs for sRGB images Product: gwenview Version: Other (add details in bug description) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: stu...@anchev.net CC: myr...@kde.org Target Milestone: --- gwenview5-16.08.2-1.1.x86_64 on openSUSE Leap 42.2 shows oversaturated thumbs (perhaps not color managed properly) for images which are properly displayed when viewed otherwise (after double clicking the thumb). It seems to happen for images without color profile or with embedded sRGB profile. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375334] Closing a document changes focus to zoom window in the active document
https://bugs.kde.org/show_bug.cgi?id=375334 George changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #3 from George --- Let's close this bug, as it is about an older version of okular. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402063] New: database names is not valid
https://bugs.kde.org/show_bug.cgi?id=402063 Bug ID: 402063 Summary: database names is not valid Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: jora1...@gmx.de Target Milestone: --- SThe database names configuration is not valid. Error is The core database name is empty Please check your configuration. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 398495] impossible to bring an imap folder online
https://bugs.kde.org/show_bug.cgi?id=398495 George changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385813] New: Video timings change when changing video profile
https://bugs.kde.org/show_bug.cgi?id=385813 Bug ID: 385813 Summary: Video timings change when changing video profile Product: kdenlive Version: 17.08.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: kev...@gmail.com Target Milestone: --- Very similar to bug 354940. If I edit a video, then save the project and change the video profile (example: from 30 FPS to 60 FPS) the timing in the video is completely wrong. Reproducible: Always Steps to reproduce: * import any video file * Add the video to the timeline, changing the start and end times, splitting the clip in the middle, (normal editing operations) * Change video profile from 30 FPS to 60 FPS or vice versa * Video timings are now wrong Also, sometimes while attempting to re-edit the clips in the project the clips disappear, jump to the wrong location, or become "ghost clips" which exist but cannot be selected. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385813] Video timings change when changing video profile
https://bugs.kde.org/show_bug.cgi?id=385813 George changed: What|Removed |Added CC||kev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385830] New: PNG Export options for animation are not preserved when saving
https://bugs.kde.org/show_bug.cgi?id=385830 Bug ID: 385830 Summary: PNG Export options for animation are not preserved when saving Product: krita Version: 3.3.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kev...@gmail.com Target Milestone: --- When using the animation export dialogue, setting a PNG setting while "rendering" an mp4 video results in the PNG export settings reverting to default. Reproducible: always Steps to reproduce: 1. File -> Render Animation... 2. Under "File Format" select PNG Image and check the "render" checkbox 3. Click on the [...] to the right of the PNG Image to set render settings (change from the defaults) 4. Click OK 5. Re-open the PNG image settings and note that they have reverted to default. Workaround: If you export the project as a single image using File -> Export -> PNG image and set the PNG quality settings in that dialogue, then the renderer will use those settings instead. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385830] PNG Export options for animation are not preserved when saving
https://bugs.kde.org/show_bug.cgi?id=385830 George changed: What|Removed |Added CC||kev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360075] No way to control color management
https://bugs.kde.org/show_bug.cgi?id=360075 --- Comment #5 from george --- I have just found that I was using the wrong repo. After updating to 15.12.3 I can see correct colors. Thanks Jan. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381122] New: gwenview shows "Color space: Uncalibrated" for AdobeRGB images
https://bugs.kde.org/show_bug.cgi?id=381122 Bug ID: 381122 Summary: gwenview shows "Color space: Uncalibrated" for AdobeRGB images Product: gwenview Version: 17.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: stu...@anchev.net CC: myr...@kde.org Target Milestone: --- Created attachment 106056 --> https://bugs.kde.org/attachment.cgi?id=106056&action=edit sample image gwenview5-16.08.2-1.1.x86_64 on openSUSE Leap 42.2 does not recognize AdobeRGB color profile in images. It shows "Color space: Uncalibrated" in the metadata. Reported also on openSUSE bugzilla and confirmed in comments that it is the same also in the latest version of gwenview: https://bugzilla.opensuse.org/show_bug.cgi?id=1043794 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 381122] gwenview shows "Color space: Uncalibrated" for AdobeRGB images
https://bugs.kde.org/show_bug.cgi?id=381122 --- Comment #1 from george --- Created attachment 106057 --> https://bugs.kde.org/attachment.cgi?id=106057&action=edit screenshot demonstrating the issue Attached screenshot demonstrating the issue -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 375215] New: "Cannot Create Embedded Terminal"
https://bugs.kde.org/show_bug.cgi?id=375215 Bug ID: 375215 Summary: "Cannot Create Embedded Terminal" Product: krusader Version: 2.4.0-beta3 "Single Step" Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: i...@chura.ca Target Milestone: --- With Konsole5 v16.08.3.1.fc25 and konsole5-part v16.08.3.1.fc25 installed, Krusader consistently produces the above message: "Cannot Create Embedded Terminal" when any of the various options are selected that would use or output to an embedded Konsole terminal. I have tried unistalling and reinstalling Konsole and rebooting and the same results are produced. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 499487] New: vendor-directory
https://bugs.kde.org/show_bug.cgi?id=499487 Bug ID: 499487 Summary: vendor-directory Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: georges...@zoho.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-30-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: When I open Discover i get the message "no metadata URIs for vendor-directory" . The application crashes when I uncheck vendor-directory - Vendor (Automatic) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f70014e285d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/fwupd-backend.so #5 0x7f701fa6e624 in QConcatenateTablesProxyModel::setData(QModelIndex const&, QVariant const&, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f701fa523b5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f701fa56193 in QAbstractItemModel::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f701fa71de5 in QConcatenateTablesProxyModel::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f7021b98995 in SourcesModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #10 0x7f70208c6c93 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f70207a3521 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f70207a53e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f70207c1cb6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f70207c53df in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f7020757c2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f70208e144d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f7020892baf in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f70208942f8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f70208c677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f701fae8acd in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f7018e2f221 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7f7018e4e251 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #23 0x7f70210550e8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f7021562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f701fab1738 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f70210729da in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f70210740dd in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7f701ff49435 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7f7021562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f701fab1738 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f701ff3d42d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #32 0x7f701ff11cec in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #33 0x7f701a5c7eca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #34 0x7f701e1d47a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f701e1d4a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f701e1d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7f701fb09876 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5C
[Spectacle] [Bug 507177] New: Spectacle: "Quit after saving or copying" option doesn't work with automatic post-capture actions
https://bugs.kde.org/show_bug.cgi?id=507177 Bug ID: 507177 Summary: Spectacle: "Quit after saving or copying" option doesn't work with automatic post-capture actions Classification: Applications Product: Spectacle Version First unspecified Reported In: Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: georg29387...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Spectacle: "Quit after saving or copying" option doesn't work with automatic post-capture actions STEPS TO REPRODUCE - Open Spectacle. - Under the "After taking a screenshot" section, enable an automatic action, for example, "Automatically save the image to the default save location". - Enable the "Quit after saving or copying" checkbox. - Take any screenshot. OBSERVED RESULT The screenshot is successfully saved to the disk, and a notification appears confirming the action. However, the main Spectacle window remains open and does not close automatically. EXPECTED RESULT The Spectacle window should close automatically after the screenshot has been saved, since the "Quit after saving or copying" option is enabled. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 42 (KDE Plasma Desktop Edition), kernel: 6.15.6 (Wayland) KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION This behavior seems to be specific to the automatic post-capture actions. The "Quit after saving or copying" feature works as expected when performing a manual action. For example, if I take a screenshot and then manually click the "Save" or "Copy" button, the Spectacle window closes correctly. The issue only arises when the save/copy action is triggered automatically by the "After taking a screenshot" settings. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 363425] Created Project goes to tasks, but promoted stays as project
https://bugs.kde.org/show_bug.cgi?id=363425 George Moutsopoulos changed: What|Removed |Added CC||gmou...@yahoo.co.uk --- Comment #1 from George Moutsopoulos --- Same here with zanshin 0.4.0 installed locally on kubuntu 16.10. A context task item can be promoted to a project, and a project cannot be created directly. What happens is as described (the "project" appears momentarily and then is placed into the inbox as a "task") -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372797] New: K Runner applet causes plasma crash on the first use after login
https://bugs.kde.org/show_bug.cgi?id=372797 Bug ID: 372797 Summary: K Runner applet causes plasma crash on the first use after login Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pckidp...@webplanet.gr CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-45-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Just using default search in the K Menu to start an app. (Never got to run it). The crash occurs frequently (but not always). After the first failure it does not appear to happen again in the same session. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 [Current thread is 1 (Thread 0x7f9448531900 (LWP 2843))] Thread 18 (Thread 0x7f935b7fe700 (LWP 3243)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f944333da5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x42ab410) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x42b0aa0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f9387be250b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x42a9e90, th=) at ../../src/weaver.cpp:594 #4 0x7f9387be32bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x42a9e90, th=th@entry=0x7f9344002b90, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f9387be74e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x3f27160, th=0x7f9344002b90, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f9387be246d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f9344002b90, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f9387be7542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x3f27160, th=0x7f9344002b90, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f9387be246d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f9344002b90, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f9387be5353 in ThreadWeaver::Thread::run (this=0x7f9344002b90) at ../../src/thread.cpp:103 #10 0x7f944333c7be in QThreadPrivate::start (arg=0x7f9344002b90) at thread/qthread_unix.cpp:331 #11 0x7f944242970a in start_thread (arg=0x7f935b7fe700) at pthread_create.c:333 #12 0x7f9442c5282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f935bfff700 (LWP 3242)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f944333da5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x42ab410) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x42b0aa0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f9387be250b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x42a9e90, th=) at ../../src/weaver.cpp:594 #4 0x7f9387be32bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x42a9e90, th=th@entry=0x7f9354002f90, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f9387be74e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x3f27160, th=0x7f9354002f90, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f9387be246d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f9354002f90, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f9387be7542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x3f27160, th=0x7f9354002f90, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f9387be246d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f9354002f90, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f9387be5353 in ThreadWeaver::Thread::run (this=0x7f9354002f90) at ../../src/thread.cpp:103 #10 0x7f944333c7be in QThreadPrivate::start (arg=0x7f9354002f90) at thread/qthread_unix.cpp:331 #11 0x7f944242970a in start_thread (arg=0x7f935bfff700) at pthread_create.c:333 #12 0x7f9442c5282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f9368bc4700 (LWP 3241)): #0 pthread_cond_wait@@GLIBC_2.3.2 ()
[plasmashell] [Bug 372797] K Runner applet causes plasma crash on the first use after login
https://bugs.kde.org/show_bug.cgi?id=372797 --- Comment #1 from George G. --- Created attachment 102418 --> https://bugs.kde.org/attachment.cgi?id=102418&action=edit New crash information added by DrKonqi plasmashell (5.5.5) using Qt 5.5.1 - What I was doing when the application crashed: Using K runner, but this was not the first use after login. Thus, the problem seems to be (randomly) occurring. -- Backtrace (Reduced): #6 memcpy (__len=96, __src=0x18, __dest=0x7fd08c003928) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #7 mdb_txn_renew0 (txn=txn@entry=0x7fd08c0038a0) at mdb.c:2719 #8 0x7fd09c95ef14 in mdb_txn_begin (env=0x7fd080003db0, parent=0x0, flags=131072, ret=0x7fd0969e88c8) at mdb.c:2850 #9 0x7fd09cfd7bbe in Baloo::SearchStore::exec (this=this@entry=0x7fd0969e89b0, term=..., offset=0, limit=10, sortResults=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/searchstore.cpp:74 #10 0x7fd09cfc6bc2 in Baloo::Query::exec (this=this@entry=0x7fd0969e8a60) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/query.cpp:210 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372797] K Runner applet causes plasma crash on the first use after login
https://bugs.kde.org/show_bug.cgi?id=372797 George G. changed: What|Removed |Added CC||pckidp...@webplanet.gr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372797] K Runner applet causes plasma crash on the first use after login
https://bugs.kde.org/show_bug.cgi?id=372797 --- Comment #1 from George G. --- Created attachment 102418 --> https://bugs.kde.org/attachment.cgi?id=102418&action=edit New crash information added by DrKonqi plasmashell (5.5.5) using Qt 5.5.1 - What I was doing when the application crashed: Using K runner, but this was not the first use after login. Thus, the problem seems to be (randomly) occurring. -- Backtrace (Reduced): #6 memcpy (__len=96, __src=0x18, __dest=0x7fd08c003928) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #7 mdb_txn_renew0 (txn=txn@entry=0x7fd08c0038a0) at mdb.c:2719 #8 0x7fd09c95ef14 in mdb_txn_begin (env=0x7fd080003db0, parent=0x0, flags=131072, ret=0x7fd0969e88c8) at mdb.c:2850 #9 0x7fd09cfd7bbe in Baloo::SearchStore::exec (this=this@entry=0x7fd0969e89b0, term=..., offset=0, limit=10, sortResults=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/searchstore.cpp:74 #10 0x7fd09cfc6bc2 in Baloo::Query::exec (this=this@entry=0x7fd0969e8a60) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/query.cpp:210 --- Comment #2 from George G. --- Created attachment 102419 --> https://bugs.kde.org/attachment.cgi?id=102419&action=edit New crash information added by DrKonqi plasmashell (5.5.5) using Qt 5.5.1 - What I was doing when the application crashed: Using K runner, but this was not the first use after login. Thus, the problem seems to be (randomly) occurring. -- Backtrace (Reduced): #6 memcpy (__len=96, __src=0x18, __dest=0x7fd08c003928) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #7 mdb_txn_renew0 (txn=txn@entry=0x7fd08c0038a0) at mdb.c:2719 #8 0x7fd09c95ef14 in mdb_txn_begin (env=0x7fd080003db0, parent=0x0, flags=131072, ret=0x7fd0969e88c8) at mdb.c:2850 #9 0x7fd09cfd7bbe in Baloo::SearchStore::exec (this=this@entry=0x7fd0969e89b0, term=..., offset=0, limit=10, sortResults=) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/searchstore.cpp:74 #10 0x7fd09cfc6bc2 in Baloo::Query::exec (this=this@entry=0x7fd0969e8a60) at /build/baloo-kf5-wIK3t6/baloo-kf5-5.18.0/src/lib/query.cpp:210 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372936] New: Plasma crashing every time I use search
https://bugs.kde.org/show_bug.cgi?id=372936 Bug ID: 372936 Summary: Plasma crashing every time I use search Product: plasmashell Version: 5.8.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: georged...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) (Compiled from sources) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.10-gentoo x86_64 Distribution: "Gentoo Base System release 2.3" -- Information about the crash: I was typing a search string into K menu. Plasma crashes 99% of the time when I do that. It also crashes when the search is performed in Plasma search widget (Alt+F2). This behaviour has been manifesting for quite some time (several months), but only now have I decided it was annoying enough to recompile everything with debugging symbols and issue this report. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". allocator_get_magazine_threshold (allocator=0x7f68735af2a0 , allocator=0x7f68735af2a0 , ix=) at /var/tmp/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gslice.c:583 [Current thread is 1 (Thread 0x7f687c9cf840 (LWP 3465))] Thread 23 (Thread 0x7f676bfff700 (LWP 13886)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6877b43c1a in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x4e0e8f0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3cc0c30, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f67c07b559b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x29c4fa0, th=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:594 #4 0x7f67c07b63f0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x29c4fa0, th=, th@entry=0x7f6778002990, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:554 #5 0x7f67c07ba408 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4752830, th=0x7f6778002990, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/workinghardstate.cpp:66 #6 0x7f67c07b5509 in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6778002990, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:568 #7 0x7f67c07ba452 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4752830, th=0x7f6778002990, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/workinghardstate.cpp:73 #8 0x7f67c07b5509 in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6778002990, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:568 #9 0x7f67c07b83d9 in ThreadWeaver::Thread::run (this=0x7f6778002990) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/thread.cpp:103 #10 0x7f6877b4360b in QThreadPrivate::start (arg=0x7f6778002990) at thread/qthread_unix.cpp:344 #11 0x7f6876bf73b4 in start_thread (arg=0x7f676bfff700) at pthread_create.c:333 #12 0x7f68773f1a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 22 (Thread 0x7f6784bb9700 (LWP 13885)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6877b43c1a in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x4e0e8f0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x3cc0c30, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f67c07b559b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x29c4fa0, th=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:594 #4 0x7f67c07b63f0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x29c4fa0, th=, th@entry=0x7f676c0027d0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.28.0/src/weaver.cpp:554 #5 0x7f67c07ba408 in ThreadWeaver::WorkingHardState::applyForWork (this=0x4752830, th=0x7f676c0027d0, wasBusy=) at /var/tmp/portage/kde-frameworks/threadweaver-5.28.0/work/threadweaver-5.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 --- Comment #10 from George Diamantopoulos --- Still happening with: Kernel: 5.15.24-gentoo KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Yakauke version 21.12.2 My experience is a little different to Raman Gupta's from above: the only way for yakuake to appear on the correct display for me is: * Maintain an xwayland window open * Run xwininfo in a terminal (I use yakuake for that, not sure if it's important) * Click on the xwayland window to gather info for xwininfo * Use the keyboard shortcut twice to retract and expand yakuake without movie the mouse at all * Yakuake appears at mouse/xwayland window location i.e. in my case, hovering over an xwayland window is not enough. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 george fb changed: What|Removed |Added CC||georgefb...@gmail.com --- Comment #3 from george fb --- (In reply to giuseppe from comment #0) Have you used it before, other distro or package? Wayland or X11? What resolution is the file you are trying to play? What is your hardware CPU, GPU (if nvidia which drivers)? It doesn't work to well on low end hardware https://bugs.kde.org/show_bug.cgi?id=442132 I'm also using the flatpak version and it works without problems. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #4 from george fb --- (In reply to Wachid Adi Nugroho from comment #1) Can't reproduce on my system. I left it open for a day and it's using ~500 MB of RAM and 0.2% CPU, with a full hd file loaded. Is the interface (like opening the playlist) laggy too or just the video? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 george fb changed: What|Removed |Added CC||georgefb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #6 from george fb --- Git commit 8940fae382e7fd50fc61572bb8c8362bac0c98a9 by George Florea Bănuș. Committed on 25/02/2022 at 17:35. Pushed by georgefb into branch 'master'. fix: don't run animation when component is hidden M +1-1src/qml/MpvVideo.qml https://invent.kde.org/multimedia/haruna/commit/8940fae382e7fd50fc61572bb8c8362bac0c98a9 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #7 from george fb --- (In reply to Wachid Adi Nugroho from comment #5) I pushed a commit that should fix your "high resources on gpu render and cpu usage on idle" problem. If you can compile from source please test it. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #10 from george fb --- If it only happens to the flatpak version try to install a previous version. First run `flatpak remote-info --log flathub org.kde.haruna` then `sudo flatpak update --commit=commit_id org.kde.haruna`, replace commit_id with the actual commit id returned in first command. Try a few different versions. https://unix.stackexchange.com/questions/552688/is-it-possible-to-roll-back-a-flatpak-update -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #13 from george fb --- The beta wasn't updated in a while. I updated it now to the latest commit and should be available in maximum 1 hour. I'll install Fedora on my Intel PC and check if I can reproduce your issues there. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 450493] Haruna flatpak extremely laggy
https://bugs.kde.org/show_bug.cgi?id=450493 --- Comment #14 from george fb --- Tested on Fedora and the stable version had indeed issues, but the beta seems fine. Please test yourself and let me know. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 454698] Doesn't add `.ts` files in a folder to playlist automatically
https://bugs.kde.org/show_bug.cgi?id=454698 george fb changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 453710] Video keeps pausing for every new video in playlist.
https://bugs.kde.org/show_bug.cgi?id=453710 --- Comment #5 from george fb --- Git commit 3d1ec4b33ed7c5f020a5f9064213e94a4bedbb06 by George Florea Bănuș. Committed on 04/06/2022 at 13:15. Pushed by georgefb into branch 'master'. feat: add setting to start playback when resuming a file and some other things Renamed the resumePlayback setting to "seekToLastPosition" to be more clear about what it does New setting only works when the "seekToLastPosition" setting is enabled Removed the "Startup" label as it only applied to one setting and was causing confusion about other settings Related: bug 444539 M +3-4src/qml/MpvVideo.qml M +26 -10 src/qml/Settings/PlaybackSettings.qml M +4-1src/settings/playbacksettings.kcfg https://invent.kde.org/multimedia/haruna/commit/3d1ec4b33ed7c5f020a5f9064213e94a4bedbb06 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 444539] Previously played Video opens paused if 'Remember time position' is checked in Haruna settings
https://bugs.kde.org/show_bug.cgi?id=444539 george fb changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/haruna/commit/3d1ec4 ||b33ed7c5f020a5f9064213e94a4 ||bedbb06 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from george fb --- Git commit 3d1ec4b33ed7c5f020a5f9064213e94a4bedbb06 by George Florea Bănuș. Committed on 04/06/2022 at 13:15. Pushed by georgefb into branch 'master'. feat: add setting to start playback when resuming a file and some other things Renamed the resumePlayback setting to "seekToLastPosition" to be more clear about what it does New setting only works when the "seekToLastPosition" setting is enabled Removed the "Startup" label as it only applied to one setting and was causing confusion about other settings Related: bug 453710 M +3-4src/qml/MpvVideo.qml M +26 -10 src/qml/Settings/PlaybackSettings.qml M +4-1src/settings/playbacksettings.kcfg https://invent.kde.org/multimedia/haruna/commit/3d1ec4b33ed7c5f020a5f9064213e94a4bedbb06 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 443158] Support playing videos via jellyfin-mpv-shim
https://bugs.kde.org/show_bug.cgi?id=443158 george fb changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 451760] Failed to load module "appmenu-gtk-module
https://bugs.kde.org/show_bug.cgi?id=451760 george fb changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 444941] System slows to a crawl on occasion
https://bugs.kde.org/show_bug.cgi?id=444941 --- Comment #7 from george fb --- Is this still happening? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465720] New: Train not identified on manual connection profiles, crashes when capturing an image
https://bugs.kde.org/show_bug.cgi?id=465720 Bug ID: 465720 Summary: Train not identified on manual connection profiles, crashes when capturing an image Classification: Applications Product: kstars Version: 3.6.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: george.bec...@ucr.edu Target Milestone: --- Created attachment 156233 --> https://bugs.kde.org/attachment.cgi?id=156233&action=edit Log file from crashed session 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 *** Some Ekos profiles with manual connections cannot be assigned an optical train. KStars then crashes when attempting to capture an image. The steps to reproduce below are one example. Similar cases where the train does or does not load are also given. STEPS TO REPRODUCE 1. Launch Ekos 2. Create a profile with only Mount=Telescope Simulator and Camera 1=CCD Simulator. In the Profile Editor, Uncheck Auto Connect. 3. Start Ekos 4. In the INDI Control Panel, Connect both the CCD Simulator and Telescope Simulator 5. In the CCD panel, attempt to capture an image or a preview. OBSERVED RESULT The Optical Train window does not appear when the profile is started. The Train field is greyed out in all panels. It shows no value and cannot be edited. In the CCD panel the cooler fields are also greyed out, and the Live Video button is crossed out. KStars crashes immediately when the Preview or Start Sequence buttons are clicked. EXPECTED RESULT I would expect the result to be the same when connecting the devices either manually or automatically. When the same setup is created with Auto Connect enabled, Optical Train window appears when the profile is started for the first time. The Train field is populated in the Ekos panels and can be edited. The Cooler and Live Video controls also work. Capturing an image works as expected. The crash seems to occur occur only when both a mount and a camera are present and they are being connected manually. The same behavior happens when a real camera is used instead of the simulated camera. If only a camera is used and no mount, then it can be connected either manually or automatically without crashing. If I edit a profile that crashes and change the connection mode from manual to auto, then everything works; the Optical Trains window appears when the Profile is started after Auto Connect is enabled. If I edit a Profile that is working and change the connection from auto to manual then it still works; the train information appears to be saved. SOFTWARE/OS VERSIONS Windows: macOS: 12.5.1 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION A log from a crashed session is attached. I'm happy to re-run with logging enabled if needed. Thank you in advance for your help! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465720] Train not identified on manual connection profiles, crashes when capturing an image
https://bugs.kde.org/show_bug.cgi?id=465720 --- Comment #1 from George Becker --- Created attachment 156234 --> https://bugs.kde.org/attachment.cgi?id=156234&action=edit Profile Editor screenshot from crashed session -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465720] Train not identified on manual connection profiles, crashes when capturing an image
https://bugs.kde.org/show_bug.cgi?id=465720 --- Comment #2 from George Becker --- Created attachment 156235 --> https://bugs.kde.org/attachment.cgi?id=156235&action=edit CCD panel screenshot from crashed session -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465720] Train not identified on manual connection profiles, crashes when capturing an image
https://bugs.kde.org/show_bug.cgi?id=465720 George Becker changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #5 from George Becker --- I'm still getting the same behavior after a fresh re-install of the new version. The optical train does not load when a mount and camera are connected manually, and KStars crashes when I try to capture an image. It may not be a significant issue so long as Automatic connection is enabled in the Profile setup, unless there are other underlying issues. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 465564] chapter list not big enough as it was in 10.3
https://bugs.kde.org/show_bug.cgi?id=465564 george fb changed: What|Removed |Added Latest Commit||https://invent.kde.org/mult ||imedia/haruna/commit/7314db ||7dd68c747fe98ab7612ed72d227 ||566bbe0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from george fb --- Git commit 7314db7dd68c747fe98ab7612ed72d227566bbe0 by George Florea Bănuș. Committed on 24/02/2023 at 14:58. Pushed by georgefb into branch 'master'. HProgressBar: resize chapters popup width according to the longest chapter M +15 -4src/qml/HProgressBar.qml https://invent.kde.org/multimedia/haruna/commit/7314db7dd68c747fe98ab7612ed72d227566bbe0 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 george fb changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #8 from george fb --- Works for me. Can't look into it if I can't reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 466481] Cannot play MP4 files whose names contain "#"
https://bugs.kde.org/show_bug.cgi?id=466481 george fb changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/haruna/commit/05f11a ||60a6458a716760ff7a012892414 ||dd811a1 Resolution|--- |FIXED --- Comment #2 from george fb --- Git commit 05f11a60a6458a716760ff7a012892414dd811a1 by George Florea Bănuș. Committed on 28/02/2023 at 11:50. Pushed by georgefb into branch 'master'. playlistmodel: PlayListModel::openFile: pass percent encoded path to QUrl PlayListModel::getSiblingItems: change parameter to a QUrl M +8-9src/models/playlistmodel.cpp M +1-1src/models/playlistmodel.h https://invent.kde.org/multimedia/haruna/commit/05f11a60a6458a716760ff7a012892414dd811a1 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 466481] Cannot play MP4 files whose names contain "#"
https://bugs.kde.org/show_bug.cgi?id=466481 george fb changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 466481] Cannot play MP4 files whose names contain "#"
https://bugs.kde.org/show_bug.cgi?id=466481 george fb changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/mult |https://invent.kde.org/mult |imedia/haruna/commit/05f11a |imedia/haruna/commit/91dc32 |60a6458a716760ff7a012892414 |928a1a8ee48d02a457043e7dd92 |dd811a1 |ee36031 Status|REOPENED|RESOLVED --- Comment #3 from george fb --- Git commit 91dc32928a1a8ee48d02a457043e7dd92ee36031 by George Florea Bănuș. Committed on 03/03/2023 at 11:10. Pushed by georgefb into branch 'master'. add File class for consistent local path handling M +1-0src/CMakeLists.txt M +14 -5src/application.cpp A +36 -0src/file.cpp [License: GPL(v3.0+)] A +56 -0src/file.h [License: GPL(v3.0+)] https://invent.kde.org/multimedia/haruna/commit/91dc32928a1a8ee48d02a457043e7dd92ee36031 -- You are receiving this mail because: You are watching all bug changes.
