[kphotoalbum] [Bug 373128] Incorrect behavior for "Copy image(s) to ..." menu
https://bugs.kde.org/show_bug.cgi?id=373128 Tobias Leupold changed: What|Removed |Added CC||tobias.leup...@gmx.de Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Tobias Leupold --- This is actually a regression that happened during the KF5/Qt5 port. I'll fix it asap, thanks for the bug report :-) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 373128] Incorrect behavior for "Copy image(s) to ..." menu
https://bugs.kde.org/show_bug.cgi?id=373128 Tobias Leupold changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Tobias Leupold --- Should be fixed with commit https://commits.kde.org/kphotoalbum/9a0f05662e2376f44799681a955e76e057dd86a3 If not, feel free to re-open this! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 373263] Settings/Birthdays crashes KPA
https://bugs.kde.org/show_bug.cgi?id=373263 Tobias Leupold changed: What|Removed |Added CC||tobias.leup...@gmx.de --- Comment #2 from Tobias Leupold --- Also, the direct date input was broken, which should also be fixed in git master ;-) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 454712] New: The latitude and longitude line edit doesn't use a localized decimal separator
https://bugs.kde.org/show_bug.cgi?id=454712 Bug ID: 454712 Summary: The latitude and longitude line edit doesn't use a localized decimal separator Product: kdeplasma-addons Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Control Assignee: plasma-b...@kde.org Reporter: t...@stonemx.de CC: kwin-bugs-n...@kde.org, vlad.zahorod...@kde.org Target Milestone: --- When settting the longtitude and latitude values for the night color location, the decimal separator is always C locale's ".". E.g. I'm using a German locale here, and would like to set the location to Nuremberg's Hauptmarkt. Then I'd enter latitude "49,45398" and longitude "11,07736". With a comma as the decimal separator, consistent with my locale. This is not accepted by the dialog however, I have would have to enter "49.45398" and "11.07736". -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 455074] Open selected folder(s) and image(s) with KGeoTag
https://bugs.kde.org/show_bug.cgi?id=455074
Tobias Leupold changed:
What|Removed |Added
CC||t...@stonemx.de
--- Comment #1 from Tobias Leupold ---
Thanks for your feedback!
I think at the moment, KGeoTag doesn't handle command line parameters at all
(I'll have to check that though ;-) but this shouldn't be too hard to
implement. Once done, it should be possible to add some shortcut to Dolphin
("open with ...").
Maybe, this can even be pre-defined, I think Gwenview does that. But I'll also
have to check that.
I'll post all updates concerning this here!
--
You are receiving this mail because:
You are watching all bug changes.
[kgeotag] [Bug 455074] Open selected folder(s) and image(s) with KGeoTag
https://bugs.kde.org/show_bug.cgi?id=455074 --- Comment #2 from Tobias Leupold --- Git commit cb8489b5636d7378563261aa31a59c57e2a8b361 by Tobias Leupold. Committed on 12/06/2022 at 14:48. Pushed by tleupold into branch 'master'. Added loading dirs/files given on the command line M +25 -1src/MainWindow.cpp https://invent.kde.org/graphics/kgeotag/commit/cb8489b5636d7378563261aa31a59c57e2a8b361 -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 455074] Open selected folder(s) and image(s) with KGeoTag
https://bugs.kde.org/show_bug.cgi?id=455074 --- Comment #3 from Tobias Leupold --- Okay, we now can load directories and/or files that are given on the command line. This works fine for one selected directory or file via Dolphin's "Open with", but if more files and/or directories are selected, one instance of KGeoTag is opened … I'm not sure how to handle this. Loading an arbitrary number of files (or a wildcard) given via the command line directly works as expected. I'll have to check if there's a way how to tell Dolphin to pass a list to KGeoTag instead of opening multiple instances. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 Tobias Leupold changed: What|Removed |Added Ever confirmed|0 |1 CC||t...@stonemx.de Status|REPORTED|CONFIRMED --- Comment #2 from Tobias Leupold --- Thanks for your comprehensive bug report! I can reproduce this. This should indeed not happen ;-) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 442325] When adding new images and tagging them at once, they appear out of order in the Annotation dialog
https://bugs.kde.org/show_bug.cgi?id=442325 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #3 from Tobias Leupold --- >From a KPA user's perspective, I personally would expect the images always to be ordered chronologically. Is there a benefit for this arbitrary selection and ordering?! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 442325] When adding new images and tagging them at once, they appear out of order in the Annotation dialog
https://bugs.kde.org/show_bug.cgi?id=442325 --- Comment #5 from Tobias Leupold --- I can't imagine a situation where I would select images in the preview in a specific order and expect them to show up in that very order. Ordered chronologically is what I personally always would expect, no matter the pattern I clicked, CRTL+A or whatever. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 254186] skanlite's “Reload devices list” does not work
https://bugs.kde.org/show_bug.cgi?id=254186 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #4 from Tobias Leupold --- I was just about to open a KSaneCore bug about this exact issue (by the way, there's no KSaneCore product yet in Bugzilla!). This bug is 12 years old(!), but the behavior is still the same (of course no matter if you use Skanlite or some other program using KSaneCore as it's SANE backend). Calling KSane::CoreInterface::reloadDevicesList() only works when being called for the first time. Calling it again does not expose scanners attached in the meantime. Restarting the respective program makes the scanner(s) appear. Tested with: - Brother DS-640 (using Brother's proprietary brscan5 backend) - Canon CanoScan LiDE 25 (using SANE's plustek backend) Is there anything going on about this?! Is there some upstream bug filed/still open? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 460468] Enhancement requests, two (OK three) very short points.
https://bugs.kde.org/show_bug.cgi?id=460468 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Hi Per! Thanks for your request. #1 is already implemented I think, you simply have to check the funnel button at the bottom. This way, only the selected tags are displayed. #2 is also already implemented if I get this correctly: Simply use the PgUp and PgDown buttons to browse through the images to be annotated, or use the existing "prev image" and "next image" buttons (or do you mean somethng else?). About #3, I think that this not that meaningful, as an external viewer won't show the meta info. What about a setting for an external vierwer which can be accessed easier, e.g. via a keyboard shortcut? Like some menu entry "Open with external viewer" that has a configurable shortcut? Would this fit your needs? Johannes, what do you think? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 460468] Enhancement requests, two (OK three) very short points.
https://bugs.kde.org/show_bug.cgi?id=460468 --- Comment #5 from Tobias Leupold --- If you reply via email, please don't cite all the old stuff – this spams the online bugzilla view ;-) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 460468] Enhancement requests, two (OK three) very short points.
https://bugs.kde.org/show_bug.cgi?id=460468 --- Comment #6 from Tobias Leupold --- Maybe you should install the Breeze icon theme. It's used all over KPA (and most other KDE apps) … -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 345507] KPA hangs when starting the gpssync dialog without selected photos
https://bugs.kde.org/show_bug.cgi?id=345507 Tobias Leupold changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #3 from Tobias Leupold --- Oh, this was actually reported by me back then ;-) As the gpssync dialog has been discontinued (and we now have KGeoTag), I think we can close this as "unmaintained". -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 465065] Support for MP4 files
https://bugs.kde.org/show_bug.cgi?id=465065 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Thanks for your request! I never thought about adding support to video files until now. I'll have to investigate this (speaking about the kexiv2 support, this would be the conditio sine qua non in each case). Will exiv2 create an XMP sidecar file for videos? A video doesn't have an Exif header, does it? Question is how applicable this would be? Whilst shooting a video, you can move around, so one would have to tag some kind of area or a whole path, no? Anyway, this is principally interesting. I'll have a look art this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Categories sidebar is located in the wrong place for optimal usability
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #18 from Tobias Leupold --- Legacy Kickoff still works perfectly: https://store.kde.org/p/1468103 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484327] Bad initial window sizes
https://bugs.kde.org/show_bug.cgi?id=484327 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #2 from Tobias Leupold --- I was just about filing a bug about the initial window size of the composer window and saw this one, which seems to already describe the issue I see. It seems like one of the problems has been resolved meanwhile: The main window restores its size (not its position) when restarting. So maybe, it's about also restoring the position (I'm not on Wayland, I know that positioning is not possible on Wayland!). The other problem remains: The composer window inherits the size of the main window. This is a regression compared with the Qt5/KF5 version of KMail, where the composer remembered its own size and position. I see this exact behavior using KMail 6.0.2 on Artix and also still using 6.1.0 on Gentoo. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 489223] New: Using a Plasma 6 desktop, a MarbleWidget shortly flashes up as an extra window after being instantiated
https://bugs.kde.org/show_bug.cgi?id=489223 Bug ID: 489223 Summary: Using a Plasma 6 desktop, a MarbleWidget shortly flashes up as an extra window after being instantiated Classification: Applications Product: marble Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: t...@stonemx.de Target Milestone: --- Created attachment 171004 --> https://bugs.kde.org/attachment.cgi?id=171004&action=edit CMakeLists.txt Hi all :-) When you run a Plasma 6 desktop and run a program using a MarbleWidget, the widget shortly flashes up as an extra window after being instantiated. I'll attach a minimal example demonstrating this. I saw this exact behavior with another project, always happening when QWidget::show() was called before the widget was added to a layout. This either did not happen using a Plasma 5 desktop, or at least the flashing was not visible. For this exact case, I noticed it whilst using KGeoTag. On Plasma 5, everything is normal as usual. When I start KGeoTag on Plasma 6, the MarbleWidget flashes. Just like with the to-be-attached demo. Maybe, you want to to fix this. Cheers, Tobias -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 489223] Using a Plasma 6 desktop, a MarbleWidget shortly flashes up as an extra window after being instantiated
https://bugs.kde.org/show_bug.cgi?id=489223 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Created attachment 171005 --> https://bugs.kde.org/attachment.cgi?id=171005&action=edit main.cpp -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 489223] Using a Plasma 6 desktop, a MarbleWidget shortly flashes up as an extra window after being instantiated
https://bugs.kde.org/show_bug.cgi?id=489223 --- Comment #2 from Tobias Leupold --- Created attachment 171006 --> https://bugs.kde.org/attachment.cgi?id=171006&action=edit MainWindow.cpp -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 489223] Using a Plasma 6 desktop, a MarbleWidget shortly flashes up as an extra window after being instantiated
https://bugs.kde.org/show_bug.cgi?id=489223 --- Comment #3 from Tobias Leupold --- Created attachment 171007 --> https://bugs.kde.org/attachment.cgi?id=171007&action=edit MainWindow.h -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] New: The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 Bug ID: 489516 Summary: The space reserved for the text of a QDockWidget tab is not enough in some situations Classification: Plasma Product: kwin Version: 6.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: t...@stonemx.de Target Milestone: --- Hi all, this is one weird bug. I'm not completely sure if KWin is to blame, or if the problem resides elsewhere. I'm also not sure how to track this down. But I have a minimal example producing the problem reliably, so I hope you know ;-) The problem is that, using a Plasma 6 desktop and Noto Sans 10pt as the font, it happens that when tabifying QDockWidgets of a Qt 6 program, the resulting tab texts are sometimes cut off, although there would be enough space. Please see the screenshots I'll attach to see what I mean. This happens both with Breeze and Fusion, so I think it's no style issue. I can produce this exact behavior on my Gentoo desktop and also on my Artix notebook. Both running plasma 6.1.1, Gentoo with Qt 6.7.1, Artix with 6.7.2. This does not happen when using a Plasma 5 desktop, neither for a Qt 5 build, nor for a Qt 6 build. Everything is fine using Plasma 5. I tried this using a current KUbuntu in a QEMU VM. Both the Qt 5 and 6 builds of my demo don't cut off the text. But I could also reproduce this using am OpenSUSE Tumbleweed QEMU VM, running a Plasma 6 desktop. Here, the Qt 5 build looks fine, but the Qt 6 build cuts off the text, just as with my Gentoo and Artix machines. Interestingly, the cutoff does not happen when: - Another Font is used - Noto Sans is used, but another size (9 or 11) - The docks are not hidden first - The docks are hidden after a small delay, e.g. by a QTimer::singleShot waiting 100 ms (0 ms has the same result as hiding them directly) - The name of the cut off dock is slightly changed, e.g. from "Ergebnisse" to "ErgebnisseX", "Ergebnisse " or similar - The name of the "Extras" menu entry is changed, e.g. from "Extras" to "X" (how can that ever affect this at all?!) Well, as said, this is an odd one ... I'll attach the screenshots, one using Breeze and one using Fusion, as well as the minimal example producing the bug (as said, only when built against Qt 6, using Noto Sans 10pt and when run on a Plasma 6 desktop). I'd really love to help tracking this down if I can! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Created attachment 171210 --> https://bugs.kde.org/attachment.cgi?id=171210&action=edit The cutoff text using Breeze -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #2 from Tobias Leupold --- Created attachment 171211 --> https://bugs.kde.org/attachment.cgi?id=171211&action=edit The cutoff text using Fusion -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #3 from Tobias Leupold --- Created attachment 171212 --> https://bugs.kde.org/attachment.cgi?id=171212&action=edit demo.pro -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #4 from Tobias Leupold --- Created attachment 171213 --> https://bugs.kde.org/attachment.cgi?id=171213&action=edit main.cpp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #5 from Tobias Leupold --- Created attachment 171214 --> https://bugs.kde.org/attachment.cgi?id=171214&action=edit MainWindow.cpp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #6 from Tobias Leupold --- Created attachment 171215 --> https://bugs.kde.org/attachment.cgi?id=171215&action=edit MainWindow.h -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489516] The space reserved for the text of a QDockWidget tab is not enough in some situations
https://bugs.kde.org/show_bug.cgi?id=489516 --- Comment #8 from Tobias Leupold --- I first was also pretty sure this was a Qt bug … I posted this at the Qt forums ( https://forum.qt.io/topic/157507/how-can-i-ensure-that-the-text-in-the-qtabbar-of-qdockwidgets-is-not-cut-off ), but they told me they could not reproduce it. I then played around with different window managers, and found the fact that it does not happen with Plasma 5, but with Plasma 6. So I thought this should be a KDE issue. Just to ask this before filing a Qt bug: Can you also see this?! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 483266] Segfault after deleting an image if the annotation dialog was previously accepted to remove a tag
https://bugs.kde.org/show_bug.cgi?id=483266 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Tobias Leupold --- Thanks for your bug report! I can confirm this. I'll have a look at this, if Johannes is not faster than me ;-) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 483266] Segfault after deleting an image if the annotation dialog was previously accepted to remove a tag
https://bugs.kde.org/show_bug.cgi?id=483266 Tobias Leupold changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/5 ||9f2cb63ac191040e6e7e0a20d5a ||fe01396e5c82 --- Comment #2 from Tobias Leupold --- Git commit 59f2cb63ac191040e6e7e0a20d5afe01396e5c82 by Tobias Leupold. Committed on 11/03/2024 at 20:24. Pushed by tleupold into branch 'master'. Don't crash if an image is deleted whilst annotating multiple images M +6-1AnnotationDialog/ImagePreview.cpp M +2-1AnnotationDialog/ImagePreview.h M +18 -1AnnotationDialog/ImagePreviewWidget.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/59f2cb63ac191040e6e7e0a20d5afe01396e5c82 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 483266] Segfault after deleting an image if the annotation dialog was previously accepted to remove a tag
https://bugs.kde.org/show_bug.cgi?id=483266 --- Comment #3 from Tobias Leupold --- This was a nasty one ;-) Please check if this fixes it, and re-open if not! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] New: Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 Bug ID: 488195 Summary: Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel Classification: Plasma Product: Breeze Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: t...@stonemx.de CC: noaha...@gmail.com, uhh...@gmail.com Target Milestone: --- Hi all! I noticed Breeze on Plasma 6 not rendering the StyledPanel frame style for a QLabel. Using the attached minimal example, everything works as expected on my Gentoo machine running Plasma 5: For a Qt 5 build using the (default) Breeze style, a styled frame is drawn. I also get a frame using the Fusion style. For a Qt 6 build, obviously there's no Breeze style here, so it starts with Fusion by default; however, I also get a frame (cf. the "plasma5" screenshots). On my Artix machine running Plasma 6, I both get a frame for a Qt 5 and Qt 6 build using the Fusion style, but no frame is drawn when I use Breeze. Seems like Plasma 6's Breeze is missing something here ... Cheers, Tobias -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Created attachment 170251 --> https://bugs.kde.org/attachment.cgi?id=170251&action=edit CMakeLists_qt5.txt -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #2 from Tobias Leupold --- Created attachment 170252 --> https://bugs.kde.org/attachment.cgi?id=170252&action=edit CMakeLists_qt6.txt -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #3 from Tobias Leupold --- Created attachment 170253 --> https://bugs.kde.org/attachment.cgi?id=170253&action=edit main.cpp -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #4 from Tobias Leupold --- Created attachment 170254 --> https://bugs.kde.org/attachment.cgi?id=170254&action=edit MainWindow.cpp -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #5 from Tobias Leupold --- Created attachment 170255 --> https://bugs.kde.org/attachment.cgi?id=170255&action=edit MainWindow.h -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #6 from Tobias Leupold --- Created attachment 170256 --> https://bugs.kde.org/attachment.cgi?id=170256&action=edit plasma5_qt5_breeze.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #7 from Tobias Leupold --- Created attachment 170257 --> https://bugs.kde.org/attachment.cgi?id=170257&action=edit plasma5_qt5_fusion.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #8 from Tobias Leupold --- Created attachment 170258 --> https://bugs.kde.org/attachment.cgi?id=170258&action=edit plasma5_qt6_fusion.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #9 from Tobias Leupold --- Created attachment 170259 --> https://bugs.kde.org/attachment.cgi?id=170259&action=edit plasma6_qt5_fusion.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #10 from Tobias Leupold --- Created attachment 170260 --> https://bugs.kde.org/attachment.cgi?id=170260&action=edit plasma6_qt6_breeze.png -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488195] Breeze on Plasma 6 doesn't render the QFrame::StyledPanel frame style for a QLabel
https://bugs.kde.org/show_bug.cgi?id=488195 --- Comment #11 from Tobias Leupold --- Created attachment 170261 --> https://bugs.kde.org/attachment.cgi?id=170261&action=edit plasma6_qt6_fusion.png -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 488597] Weird widget behavior
https://bugs.kde.org/show_bug.cgi?id=488597 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Hi, thanks for your report! The docks shouldn't be closable in the first place ... at least, it's not possible to close them via mouse click (the features set are "QDockWidget::DockWidgetMovable | QDockWidget::DockWidgetFloatable", so QDockWidget::DockWidgetClosable is not enabled). If you can close such a floating dock nevertheless, this maybe depends on the window manager and I can't fix or prevent this at all (I think I can't do more than define that the docks are not closable) ... I'll have to investigate this. As a workaround, you should be able to recover all docks and their default position via "Settings" → "Set default dock arrangement". About the kgeotagrc: Current git master now uses KMainWindow's state instead of saving the state twice, so the state is now MainWindow/State. However, there will be a (now unused) main/windowState entry. Maybe, I'll add a quick check to remove this key later on to prevent confusion. -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 488597] Weird widget behavior
https://bugs.kde.org/show_bug.cgi?id=488597 --- Comment #2 from Tobias Leupold --- Git commit 2d298421ab3f4d4f8c9e39f33e4f95ac3a4b7f92 by Tobias Leupold. Committed on 17/06/2024 at 09:50. Pushed by tleupold into branch 'master'. Be sure to actually show all docks when settuing the default arrangement M +5-0src/MainWindow.cpp https://invent.kde.org/graphics/kgeotag/-/commit/2d298421ab3f4d4f8c9e39f33e4f95ac3a4b7f92 -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 488597] Weird widget behavior
https://bugs.kde.org/show_bug.cgi?id=488597 Tobias Leupold changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Tobias Leupold --- Okay, this at least ensures that a closed dock widget is shown again when applying the default dock arrangement. However, I think this is an upstream bug: The dock widget should not be closable in the first place. I'll file an according kwin bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488616] New: It should not be possible to close a non-closable floating QDockWidget with keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=488616 Bug ID: 488616 Summary: It should not be possible to close a non-closable floating QDockWidget with keyboard shortcuts Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: t...@stonemx.de Target Milestone: --- Hi all :-) This surfaced in Bug #488597. The problem is that a QDockWidget that is declared as non-closable but as floatable cannot be closed by clicking an "X" button (it's omitted then), but one can actually close such a floating dock nevertheless by using a keyboard shortcut (Alt+F4). After that, there's no way to re-show that closed dock, as the menu bar's context menu containing checkboxes for all dock widgets is grayed out (it becomes enabled when adding docks with the "QDockWidget::DockWidgetClosable" feature set). The only way to get the dock back is to delete the window state from the rc file (in case of KGeoTag, as the default dock arrangement will be restored then). My understanding is that a QDockWidget that is marked as not closable should not only not be closable by omitting the "X"/"Close" button, but also an attempt to close it using keyboard shortcuts should be ignored, to also prevent it from closing this way. Cheers, Tobias -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 488597] Weird widget behavior
https://bugs.kde.org/show_bug.cgi?id=488597 --- Comment #4 from Tobias Leupold --- FYI: I just filed Bug #488616 about this. I think I'll try to work around this by using a QDockWidget subclass that catches the QCloseEvent that should be ignored. I'm not sure if I can detect if the dock is closed because the program is quit or by using a shortcut to close it, but let's see. However, recovering such a closed dock is now possible by setting the default dock arrangement, so at least, we have a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488616] It should not be possible to close a non-closable floating QDockWidget with keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=488616 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #2 from Tobias Leupold --- Sorry, I thought this was a window manager issue. Reported as https://bugreports.qt.io/browse/QTBUG-126418 -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 488597] Weird widget behavior
https://bugs.kde.org/show_bug.cgi?id=488597 --- Comment #6 from Tobias Leupold --- You're welcome :-) The fact that the Qt guys already triaged this as "important" is maybe a good sign. I think I'll wait what they say. If this is fixed upstream, there's no need to implement a workaround. And for accidental closing of floating docks, we now have the "default arrangement" workaround to get them back. Well, let's see … I think I'll let this bug open as a reminder to check what upstream does now and then … -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 Tobias Leupold changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Tobias Leupold --- Thanks for the update. I'm closing this then :-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481198] Package can't be built - key missing
https://bugs.kde.org/show_bug.cgi?id=481198 Tobias Leupold changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- 0xA53563BC888E6CE5215535992523842AF9681DDF is the ID of my PGP key. The official release is signed with it. You have to either add it to your local keystore, or skip PGP checks when doing an AUR build. IIRC, both is possible with pacman (or packey or what it was called). Please read your distribution-specific (or AUR) docs or ask your search machine of trust about how to do that. This is a distribution-specific problem, or better said one that your local machine has. Not a KGeoTag bug. And I only know that because I run Artix on one of my machines ;-) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 425410] Names of tag categories suddenly have superfluous ampersands added to them
https://bugs.kde.org/show_bug.cgi?id=425410 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #12 from Tobias Leupold --- I'm not completely sure if I get this correctly. I'm seeing this using KPA's current git master on my Artix desktop having Qt 5.15.13 and Qt 6.6.3 installed, running Plasma 6.0.3. So this is actually a Qt bug, filed in 2020 T https://bugreports.qt.io/browse/QTBUG-86407 – and now, we have Bug #482657, describing the very same thing for a Qt 6 Plasma desktop, although the bug claims to be fixed in Qt 6.6? So that fix never made it in Qt 5, but is only visible when I run a Qt 6 desktop, although I compiled KPA against Qt 5 – and it doesn't show up when running on Plasma 5?! I don't get it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484387] New: Dolphin apparently has no means anymore to set the LimitFoldersPanelToHome property graphically
https://bugs.kde.org/show_bug.cgi?id=484387 Bug ID: 484387 Summary: Dolphin apparently has no means anymore to set the LimitFoldersPanelToHome property graphically Classification: Applications Product: dolphin Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: t...@stonemx.de CC: kfm-de...@kde.org Target Milestone: --- Hello Dolphin devs! The "Folders" panel has a property called "LimitFoldersPanelToHome". When set to "false", one always sees a whole directory tree, starting from /. If set to "true" or this property is unset, one only sees a tree starting from ~, if the currently viewed folder is inside or below ~. However, with recent versions of Dolphin (I can't tell when exactly this happened, I noticed this because I added a new user for the fist time since about 2018 and tried to set meaningful defaults), there is no graphical way anymore to set this property. The behavior is to always start at ~ if inside ~, and to only show a whole directory tree if a folder outside of ~ is viewed. However, this property is still taken into account: If [FoldersPanel] LimitFoldersPanelToHome=false is added manually to ~/.config/dolphinrc, one gets the respective behavior back. Would be nice if one could configure this again graphically. I think this wasn't removed deliberately. Thanks a lot for fixing this! Cheers, Tobias -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484387] Dolphin apparently has no means anymore to set the LimitFoldersPanelToHome property graphically
https://bugs.kde.org/show_bug.cgi?id=484387 Tobias Leupold changed: What|Removed |Added Resolution|--- |NOT A BUG CC||t...@stonemx.de Status|REPORTED|RESOLVED --- Comment #1 from Tobias Leupold --- After grepping through the sources, I found this option can be set through the context menu of the folder panel. So … sorry for the noise ;-) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479912] Please add an option to decide which files are handled as "hidden" files
https://bugs.kde.org/show_bug.cgi?id=479912 --- Comment #4 from Tobias Leupold --- Well, not exactly how I would do it, but a step towards the right direction. I personally would not assume that those "hidden" files share one MIME type. But maybe, it's just me … for me, the only way to "hide" a file has always been letting it start with a dot. So I would have assumed that it's some wildcard Dolphin uses, not a MIME type … -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479912] Please add an option to decide which files are handled as "hidden" files
https://bugs.kde.org/show_bug.cgi?id=479912 --- Comment #6 from Tobias Leupold --- Fair enough ;-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #2 from Tobias Leupold --- Sorry, I can't help here … I have nothing to do with the Flatpak packaging. Esp. if the normal distribution package works as expected, it's likely a Flatpak issue … hopefully, someone who has some insight of Flatpak can help here?! -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 --- Comment #3 from Tobias Leupold --- Did you try Ubuntu's 1.5.0 package? The distribution-specific one? Just to check if this one works?! -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 481103] flatpak installation on Ubuntu - after loading files from directory, cannot save.
https://bugs.kde.org/show_bug.cgi?id=481103 --- Comment #4 from Tobias Leupold --- I just tried KGeoTag 1.5.0 installed from FlatHub on my Gentoo system. Works as expected. Maybe this is a local problem on your machine? Some permissions not set?! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 487415] No more viewing tiff files
https://bugs.kde.org/show_bug.cgi?id=487415 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #1 from Tobias Leupold --- Hi, thanks for your report. I can't reproduce this with current git master. I converted some image to TIFF using GIMP and added it to a test database. Both the thumbnail and the image in the viewer show up as expected. Maybe it's something with a specific TIFF file? Can you open it with something else? Could you provide an example file not showing up in KPA? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 487415] No more viewing tiff files
https://bugs.kde.org/show_bug.cgi?id=487415 --- Comment #3 from Tobias Leupold --- We haven't ported KPA to Qt6/KF6 yet, so updating the rest of the desktop should not affect KPA. Problem is that I can't reproduce this … I can't even create a 16-bit TIFF, there's no such option in GIMP … could you provide an example file? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 487415] No more viewing tiff files
https://bugs.kde.org/show_bug.cgi?id=487415 --- Comment #5 from Tobias Leupold --- Please don't cite some E-Mail when replying, it's spamming the bug ;-) I now tried 8-bit, 16-bit and 32-bit TIFF images. KPA can handle 8 and 16 bits, but not 32. But neither can e.g. Gwenview. So I think this is more a KDE or Qt issue in general?! At this point, I'm out ;-) Maybe, Johannes knows something more about this. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 487415] No more viewing tiff files
https://bugs.kde.org/show_bug.cgi?id=487415 --- Comment #8 from Tobias Leupold --- Only speaking for me, I could start porting KPA as soon as Gentoo allows a decent upgrade to KF6. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 452458] Broken URLs generated for non-ascii character filenames
https://bugs.kde.org/show_bug.cgi?id=452458 Tobias Leupold changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/commit/99c ||a48526ec6b6609af674be0401e4 ||3f7e39bb19 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tobias Leupold --- Git commit 99ca48526ec6b6609af674be0401e43f7e39bb19 by Tobias Leupold. Committed on 10/04/2022 at 10:34. Pushed by tleupold into branch 'master'. Use UTF-8 characters witout masking them when generating HTML M +2-14 HTMLGenerator/Generator.cpp M +0-1HTMLGenerator/Generator.h https://invent.kde.org/graphics/kphotoalbum/commit/99ca48526ec6b6609af674be0401e43f7e39bb19 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 452458] Broken URLs generated for non-ascii character filenames
https://bugs.kde.org/show_bug.cgi?id=452458 Tobias Leupold changed: What|Removed |Added CC||t...@l3u.de --- Comment #3 from Tobias Leupold --- Thanks for your report! I see this as well for non-ascii characters. The locale doesn't matter I think. As we use UTF-8 for the HTML page anyway, I think we can simply leave out the masking of special characters and leave them as-is. This fixes the gallery for me for non-ascii characters. -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 Tobias Leupold changed: What|Removed |Added CC||t...@l3u.de --- Comment #1 from Tobias Leupold --- Hi Matthias :-) Currently, there is no manpage or any kind of documentation that KGeoTag could install (the usage should be quite self-explanatory, isn't it?! ;-) … what kind of manual do you think of? Like simply installing the README.md somewhere so that we install something to silence this warning? -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 --- Comment #4 from Tobias Leupold --- I'm pretty sure that other distributors (e.g. Gentoo) won't be happy if I install a dummy file to /usr/share/man (manpages are added as compressed files by Gentoo, and a README.md file is not a manpage). Speaking of a .help file: I never heard this before, but "help help" says "Display information about builtin commands.", and kgeotag is not a builtin command – or is a .help file something else? Couldn't you simply put the README.md whereever Debian wants it to live whilst packaging KGeoTag to make your infrastructure happy? I'm pretty sure there will never be a manpage for KGeoTag (manpages are for CLI programs, aren't they?!). Maybe some kind of documentation, but not a manpage … I really don't know what would be the right – and especially meaningful and distribution-agnostic – thing to do right now :-( -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 --- Comment #5 from Tobias Leupold --- Maybe, we could take the description of KGeoTag from https://kgeotag.kde.org/ and put it in some .docbook file, like the other KDE programs do? That would definitely be better documentation than the README.md file! -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 --- Comment #7 from Tobias Leupold --- Okay. I'll see how I can create one. I never used this before ;-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 Tobias Leupold changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #9 from Tobias Leupold --- Maybe leave it open as a reminder. I can close it when I push the docbook file. -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 452534] Add manual page
https://bugs.kde.org/show_bug.cgi?id=452534 Tobias Leupold changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kgeotag/commit/16f3124 ||142de5d612b45e3e13af4b40d7f ||c88860 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from Tobias Leupold --- Git commit 16f3124142de5d612b45e3e13af4b40d7fc88860 by Tobias Leupold. Committed on 14/04/2022 at 09:57. Pushed by tleupold into branch 'master'. Added a handbook stub M +11 -1CMakeLists.txt M +2-0ChangeLog.rst M +1-1ChangeLog.rst.license A +60 -0doc/index.docbook A +156 -0doc/overview.docbook https://invent.kde.org/graphics/kgeotag/commit/16f3124142de5d612b45e3e13af4b40d7fc88860 -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 458537] Feature Request (KGeoTag): Import Google Maps location - Copy location from clipboard
https://bugs.kde.org/show_bug.cgi?id=458537 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Tobias Leupold --- Thanks for your feature request! This shouldn't be too hard to implement. I'll have a look at it shortly. Stay tuned ;-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 458537] Feature Request (KGeoTag): Import Google Maps location - Copy location from clipboard
https://bugs.kde.org/show_bug.cgi?id=458537 --- Comment #2 from Tobias Leupold --- Git commit 9db53c50994629173712adadcbeb99e1c2d1ca7f by Tobias Leupold. Committed on 01/09/2022 at 13:55. Pushed by tleupold into branch 'master'. Added setting corrdinates from the clipboard M +3-0ChangeLog.rst M +51 -0src/ImagesListView.cpp M +3-0src/ImagesListView.h M +9-0src/MainWindow.cpp M +1-0src/MainWindow.h https://invent.kde.org/graphics/kgeotag/commit/9db53c50994629173712adadcbeb99e1c2d1ca7f -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 458537] Feature Request (KGeoTag): Import Google Maps location - Copy location from clipboard
https://bugs.kde.org/show_bug.cgi?id=458537 --- Comment #3 from Tobias Leupold --- Did you think of something like this? You can now right-click an image or a selection of images and "Set coordinates from clipboard". As of now, Google's format is parsed, as well as OpenStreetMap's Geo-URI scheme. -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 458537] Feature Request (KGeoTag): Import Google Maps location - Copy location from clipboard
https://bugs.kde.org/show_bug.cgi?id=458537 --- Comment #5 from Tobias Leupold --- There are no live builds. But it's pretty easy to compile KGeoTag, just have a look at https://community.kde.org/KGeoTag -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 458537] Feature Request (KGeoTag): Import Google Maps location - Copy location from clipboard
https://bugs.kde.org/show_bug.cgi?id=458537 Tobias Leupold changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Tobias Leupold --- I'm pretty sure this is what you wanted. I wanted to do a new release anyway, so I did. Just checkout KGeoTag 1.3.0 as soon as your distribution provides it. If there's still a problem, feel free to re-open this bus or to file a new one. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 458727] kphotoalbum 5.9.0 release tarball does not ship translations
https://bugs.kde.org/show_bug.cgi?id=458727 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Tobias Leupold --- Thanks for the info, I already noticed this and I'm working on it. Same for the KGeoTag release I did the same day. This happened caused by an issue with releaseme, cf. https://mail.kde.org/pipermail/kde-devel/2022-September/001291.html -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 458727] kphotoalbum 5.9.0 release tarball does not ship translations
https://bugs.kde.org/show_bug.cgi?id=458727 --- Comment #2 from Tobias Leupold --- Maybe it would be the best to withdraw the tarball and re-release 5.9.1 including the translations to avoid confusion … I already filed a Sysadmin ticket about this. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 458728] New: tarme fails because it wants to communicate with Jenkins
https://bugs.kde.org/show_bug.cgi?id=458728 Bug ID: 458728 Summary: tarme fails because it wants to communicate with Jenkins Product: releaseme Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: t...@stonemx.de CC: sit...@kde.org Target Milestone: --- tarme.rb currently fails when taring a release, with something like Traceback (most recent call last): 8: from ./tarme.rb:74:in `' 7: from ./tarme.rb:74:in `collect' 6: from ./tarme.rb:81:in `block in ' 5: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/release.rb:66:in `get' 4: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/release.rb:154:in `check_ci!' 3: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/jenkins.rb:60:in `from_name_and_branch' 2: from /hd/home/tobias/tmp/git/releaseme/lib/releaseme/jenkins.rb:23:in `get' 1: from /usr/lib64/ruby/2.7.0/net/http/response.rb:133:in `value' /usr/lib64/ruby/2.7.0/net/http/response.rb:124:in `error!': 302 "Found" (Net::HTTPRetriableError) This seems to be due to releaseme wanting to check the Jenkins CI state of the project to be released, and build.kde.org meanwhile being redirected to metrics.kde.org/login (or, more essentially, Jenkins being retired). After commenting out the "check_ci!" call in "lib/releaseme/release.rb", creating a release tarball works again. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 458728] tarme fails because it wants to communicate with Jenkins
https://bugs.kde.org/show_bug.cgi?id=458728 Tobias Leupold changed: What|Removed |Added CC||t...@stonemx.de --- Comment #3 from Tobias Leupold --- Thanks for the immediate fix! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 458727] kphotoalbum 5.9.0 release tarball does not ship translations
https://bugs.kde.org/show_bug.cgi?id=458727 Tobias Leupold changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Tobias Leupold --- The underlying tarme.rb problem has been fixed meanwhile, and I did x.x.1 releases including the translations. Sorry for the mess … -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 442325] New: When adding new images and tagging them at once, they appear out of order in the Annotation dialog
https://bugs.kde.org/show_bug.cgi?id=442325 Bug ID: 442325 Summary: When adding new images and tagging them at once, they appear out of order in the Annotation dialog Product: kphotoalbum Version: GIT master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Annotation Dialog Assignee: kpab...@willden.org Reporter: t...@l3u.de Target Milestone: --- When adding new images, selecting them and opening them in the annotaion dialog, they (sometimes) appear out of order. In the preview list, they are ordered correctly. If the images are added, afterwards the database is saved, KPA closed and re-opened, the new images are sorted correctly when opened in the annotaion dialog. Apparently, some sorting is missing on new images? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 442735] New: kgpg should ask if a revication certificate really should be imported
https://bugs.kde.org/show_bug.cgi?id=442735 Bug ID: 442735 Summary: kgpg should ask if a revication certificate really should be imported Product: kgpg Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: t...@l3u.de Target Milestone: --- Dear kgpg devs, I just noticed the following behavior: I created a revocation certificate for my PGP key via the console. I redirected the output of gpg --gen-revoke to a file named revoke_abcd.asc. I clicked on it afterwards to check if the file actually contained the certificate. What I thought would happen was: Either, KWrite would pop up to show the contents of that text file, or kgpg should open it and ask me if I really wanted to revoke key abcd. What happened was that kgpg silently processed and imported the certificate, which was a bit unexpected. Luckily, as long as I didn't export the public key, I could un-revoke the key with the approach listed in https://lists.gnupg.org/pipermail/gnupg-users/2007-April/030726.html , but for a short time, my heart stood still ;-) So, probably, when performing such a crucial task, kgpg should at least ask if I really want to do this ... or at least display something like "Congrats, you revoked your key". Maybe, you want to add this? Cheers, Tobias -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434904] Implement a triangle menu filter for Kickoff's categories sidebar
https://bugs.kde.org/show_bug.cgi?id=434904 --- Comment #14 from Tobias Leupold --- Video #2 demonstrates EXACTLY what happens to me when using the new launcher! And it makes it frustrating to use! Thanks for visualizing this! Gladly, you can still install "Legacy Kickoff" to keep the old (way more usable) menu ... -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 451082] New: libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082
Bug ID: 451082
Summary: libksane should not expose "source" for the Brother
DS-640
Product: libksane
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kare.s...@iki.fi
Reporter: t...@l3u.de
Target Milestone: ---
Using libksane 21.12.2, the "source" option for the DS-640 scanner from Brother
is exposed (Vendor: Brother, Model: DS-640).
It's a portable pullthrough scanner. The only option to choose is "Automatic
Document Feeder(left aligned)".
This alone is not a problem, but after having scanned a page, libksane tries to
scan the next one, as it thinks the source would be a real document feeder.
This leads to an error message after each scanned page ("Document feeder is
empty").
I think that the "source" option should be inactive for this model, as there's
no other way to feed documents into the scanner, and there should be no attempt
to scan another document after having scanned one, as there's no way to do a
continuous scan as with a "real" document feeder.
--
You are receiving this mail because:
You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082
Tobias Leupold changed:
What|Removed |Added
CC||t...@l3u.de
--- Comment #1 from Tobias Leupold ---
The problem seems to be that, as soon as the "source" option contains something
that looks like the device had an ADF, multi page scanning is activated:
void KSaneCorePrivate::determineMultiPageScanning(const QVariant &value)
{
const QString sourceString = value.toString();
m_executeMultiPageScanning =
sourceString.contains(QStringLiteral("Automatic Document Feeder")) ||
sourceString.contains(sane_i18n("Automatic Document Feeder")) ||
sourceString.contains(QStringLiteral("ADF")) ||
sourceString.contains(QStringLiteral("Duplex"));
}
And here, it's started automatically:
void KSaneCorePrivate::imageScanFinished()
{
Q_EMIT q->scanProgress(100);
if (m_scanThread->frameStatus() == KSaneScanThread::ReadReady) {
Q_EMIT q->scannedImageReady(*m_scanThread->scanImage());
// now check if we should have automatic ADF batch scanning
if (m_executeMultiPageScanning && !m_cancelMultiPageScan) {
// in batch mode only one area can be scanned per page
Q_EMIT q->scanProgress(-1);
m_scanThread->start();
return;
}
...
m_cancelMultiPageScan can, as far as I could see it, only be set to true by
calling KSaneCore::stopScan().
Can we even fix this within libksane? Or is this something upstream should care
about?
--
You are receiving this mail because:
You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082 --- Comment #2 from Tobias Leupold --- What about some option like "Start ADF batch scans automatically" or such, which is checked by default if m_executeMultiPageScanning is evaluated to be true? This way, this could be unchecked for e.g. the Brother DS-640, and the underlying infrastructure would not have to be changed? -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082 --- Comment #4 from Tobias Leupold --- My coding skills are quite limited, but of course, I'll help if I can :-) I didn't dive into the sources too much yet. The question is where this could or should be fixed preferably. Where does the "Automatic Document Feeder" string come from? Is this something SANE decides, or does it come directly from the backend? Libksane simply gets it from SANE, doesn't it? The brscan backend is proprietary, this is right. I fear we're lost here. I can try to find out if I can report this somewhere, but I wouldn't rely on this. Well, after all, the scanner does arguably have an ADF, with the limitation that it can only feed one document at a time automatically. I only thought that having an additional "only one scan at a time" option for devices with an ADF would possibly be a benefit for everbybody not wanting to trigger batch scans, even if multiple documents are provided by the ADF. So, leaving Brother's upstream out: We can blacklist this very device or add an option. If you want, I can try to add it and create a PR if I succeed. What option would you prefer? As said, I think that an additional option would possibly be a benefit for all ADF devices (and when set to true, the current behavior also would remain unchanged). Also, I think that for devices with only one "source" option, this option should not be exposed, as it can't be changed anyway. What do you think? I'll see how far I can get ;-) -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082 --- Comment #5 from Tobias Leupold --- Here we are, https://invent.kde.org/graphics/libksane/-/merge_requests/60 is how I would do it :-) -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 451082] libksane should not expose "source" for the Brother DS-640
https://bugs.kde.org/show_bug.cgi?id=451082 Tobias Leupold changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Tobias Leupold --- This has meanwhile be fixed by https://invent.kde.org/graphics/libksane/-/merge_requests/62 and https://invent.kde.org/graphics/libksane/-/merge_requests/63 :-) -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 365299] make transition from qtwebkit to qtwebengine
https://bugs.kde.org/show_bug.cgi?id=365299 --- Comment #22 from Tobias Leupold --- And it's gone in Gentoo :'-( -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 445023] It is impossible to use the standard key Ctrl-A to select all
https://bugs.kde.org/show_bug.cgi?id=445023 Tobias Leupold changed: What|Removed |Added CC||t...@l3u.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Tobias Leupold --- This is actually right! I didn't think of that when assigning the shortcut. I'll change this. Thanks for the hint :-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 445023] It is impossible to use the standard key Ctrl-A to select all
https://bugs.kde.org/show_bug.cgi?id=445023 Tobias Leupold changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kgeotag/commit/a0be2c7 ||8934283695887290c8cea494e56 ||ce7d10 Resolution|--- |FIXED --- Comment #2 from Tobias Leupold --- Git commit a0be2c78934283695887290c8cea494e56ce7d10 by Tobias Leupold. Committed on 05/11/2021 at 17:44. Pushed by tleupold into branch 'master'. Make CTRL+A functional again to select all files in a list ... by assigning CTRL+M (like "match" or such) to "Assign images to GPS data". M +1-1src/MainWindow.cpp https://invent.kde.org/graphics/kgeotag/commit/a0be2c78934283695887290c8cea494e56ce7d10 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445429] KPA Viewer crashes on arrow-key up
https://bugs.kde.org/show_bug.cgi?id=445429 Tobias Leupold changed: What|Removed |Added CC||t...@l3u.de --- Comment #1 from Tobias Leupold --- I can't reproduce this with this exact revision?! What I tried: – Select image from thumbnail view to start the viewer – Press F11 to view it full screen – Press arrow keys Nothing happen here … -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 445429] KPA Viewer crashes on arrow-key up
https://bugs.kde.org/show_bug.cgi?id=445429 --- Comment #4 from Tobias Leupold --- Ah, I forgot we have multiple backends by now. My bad … -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Categories sidebar is located in the wrong place for optimal usability
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #13 from Tobias Leupold --- Instead of trying to get the new launcher's devs to change it's behavior, layout etc. etc. (they obviously don't want to change anything about it) simply do what I did: Install Legacy Kickoff and you're done ( https://store.kde.org/p/1468103 ) :-P ;-) -- You are receiving this mail because: You are watching all bug changes.
[kgeotag] [Bug 455074] Open selected folder(s) and image(s) with KGeoTag
https://bugs.kde.org/show_bug.cgi?id=455074 Tobias Leupold changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kgeotag/commit/4e73cbc ||9119f9f903586d382fad93f004f ||fd2a43 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Tobias Leupold --- Git commit 4e73cbc9119f9f903586d382fad93f004ffd2a43 by Tobias Leupold. Committed on 15/07/2022 at 22:04. Pushed by tleupold into branch 'master'. KGeoTag now can take a list of URLs when being called M +1-1org.kde.kgeotag.desktop https://invent.kde.org/graphics/kgeotag/commit/4e73cbc9119f9f903586d382fad93f004ffd2a43 -- You are receiving this mail because: You are watching all bug changes.
