[ark] [Bug 486976] New: Deleting files in Ark sometimes does not work with the button - sometimes not with mouse and context menu
https://bugs.kde.org/show_bug.cgi?id=486976 Bug ID: 486976 Summary: Deleting files in Ark sometimes does not work with the button - sometimes not with mouse and context menu Classification: Applications Product: ark Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: wolfgang.kubu...@web.de CC: rthoms...@gmail.com Target Milestone: --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION In 50% of cases, files that are already in an archive cannot be deleted using the "del" key or the "Remove from archive" menu command. One of these methods works in each case. The other method is then blocked. In another case, the blocking is the other way round. It appears that directories cannot be deleted at all. You have to delete the files individually and observe the blocking (above). Empty directories are then not displayed again when they are opened. This behavior is hopefully not planned. Who is supposed to use it like this? -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 486171] Doesn't actually work with Qt 6
https://bugs.kde.org/show_bug.cgi?id=486171 Wolfgang Rohdewald changed: What|Removed |Added Version Fixed In|24.02.3 |24.05 --- Comment #5 from Wolfgang Rohdewald --- (In reply to Albert Astals Cid from comment #4) > (subscribe to kde-devel mailing list if you aren't to get emails about when > the branches are created) Done, thank you! -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 486171] Doesn't actually work with Qt 6
https://bugs.kde.org/show_bug.cgi?id=486171 Wolfgang Rohdewald changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||24.02.3 Latest Commit||https://invent.kde.org/game ||s/kajongg/-/commit/077da955 ||47d4af35bc4fa6737654d15442c ||2768f Status|REOPENED|RESOLVED --- Comment #3 from Wolfgang Rohdewald --- Git commit 077da95547d4af35bc4fa6737654d15442c2768f by Wolfgang Rohdewald. Committed on 30/04/2024 at 07:59. Pushed by wrohdewald into branch 'release/24.02'. Qt6 only worked when Qt5 was installed too FIXED-IN: 24.02.3 M +2-15 src/common.py M +0-1src/kdestub.py M +2-6src/modeltest.py M +31 -1src/qt.py https://invent.kde.org/games/kajongg/-/commit/077da95547d4af35bc4fa6737654d15442c2768f -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 486171] Doesn't actually work with Qt 6
https://bugs.kde.org/show_bug.cgi?id=486171
Wolfgang Rohdewald changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC||wolfg...@rohdewald.de
Resolution|--- |WORKSFORME
--- Comment #1 from Wolfgang Rohdewald ---
Others wanting to test this might have to set the shell variable QT_API=pyqt6
before starting kajongg because PyQt5 will be used if installed, see
https://github.com/spyder-ide/qtpy
Please double check if you are using the unmodified 24.02.2. The line numbers
in the Traceback do not match that version.
One possible problem is the kajonggserver.py process. Even if you finish
kajongg, the server process will wait for some time for new clients before
exiting. So maybe your kajonggserver.py process was not running the version you
thought it does.
So - please always kill all kajongg processes after changing source code.
One strange thing is that nobody ever reported a bug like 'int' object has no
attribute 'split' in clientVersion.split('.'), this only seems to happen to me.
So I cherrypicked a fix about this from master to 24.02 so I am actually able
to run 24.02.2 - which works fine for me with Qt6.
Your bug should have been fixed with this commit which is part of 24.02.2:
commit 3af0e1c6944695d5bdaf1bd7490cb4ad6ad98665
Author: Wolfgang Rohdewald
Date: Sat Sep 16 19:10:26 2023 +0200
Qt6: QApplication.desktop() is deprecated, introduce
KApplication.desktopSize()
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 484512] Broken layout on error dialogue
https://bugs.kde.org/show_bug.cgi?id=484512 Wolfgang Rohdewald changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Wolfgang Rohdewald --- This may be a real bug. But not with the Product "Discover". The Product is "kajongg". The Component will be "General". Please fix your bug report. Also, I do not understand whatever language you used. I even do not know which language that is. Without knowing the error message and with no way to reproduce the bug, what do you expect me to do? Please only reopen if you have further information. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484512] Broken layout on error dialogue
https://bugs.kde.org/show_bug.cgi?id=484512 Wolfgang Rohdewald changed: What|Removed |Added Resolution|--- |NOT A BUG CC||wolfg...@rohdewald.de Status|REPORTED|RESOLVED --- Comment #1 from Wolfgang Rohdewald --- Closing this bug because product, component, version are wrong. I can fix product and component but I cannot guess the version you have used. Please re-open a new bug report with correct values. Also, can you please translate all text in the attachment to English? Does the bug also happen with language English? -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 451244] Discarded tiles in order of discard
https://bugs.kde.org/show_bug.cgi?id=451244 Wolfgang Rohdewald changed: What|Removed |Added Latest Commit||https://invent.kde.org/game ||s/kajongg/-/commit/9400d16a ||f9a5ee82725fcdafbaa982a177d ||8cf8d Status|REPORTED|RESOLVED Version Fixed In||24.02.2 Resolution|--- |FIXED --- Comment #3 from Wolfgang Rohdewald --- Git commit 9400d16af9a5ee82725fcdafbaa982a177d8cf8d by Wolfgang Rohdewald. Committed on 25/03/2024 at 18:48. Pushed by wrohdewald into branch 'master'. Ruleset option: Discarded tiles in order of discard FIXED-IN: 24.02.2 M +4-1src/board.py M +4-0src/predefined.py https://invent.kde.org/games/kajongg/-/commit/9400d16af9a5ee82725fcdafbaa982a177d8cf8d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482847] Additional mouse button bindings no longer work since commit bf1ce854748bfd2433c336a9ee972883cb8617ab
https://bugs.kde.org/show_bug.cgi?id=482847 Wolfgang Faust changed: What|Removed |Added CC||wolfgangmcq+acct-bugs.kde.o ||r...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482960] New: Horizontal bars are not visible
https://bugs.kde.org/show_bug.cgi?id=482960 Bug ID: 482960 Summary: Horizontal bars are not visible Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: klein.wo...@web.de CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When choosing and configuring "horizontal bars" for hard disk usage, they will not appear inside the control bar. STEPS TO REPRODUCE 1. Add widged. 2. Configure horizontal bars for disk usage. 3. Click "apply". OBSERVED RESULT No bars will be visible. EXPECTED RESULT Horizontal bars should be visible like they used to be in plasma 5. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.18 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 479457] Clarify phrase in kstars/ekos/opsekos.ui
https://bugs.kde.org/show_bug.cgi?id=479457 Wolfgang Reissenberger changed: What|Removed |Added CC||wreis...@gmx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Wolfgang Reissenberger --- Changed to htmlhead/bodypMinimal duration of a meridian flip. Increase this value if Ekos reports that a meridian flip has failed because the pier side did not change. A good estimation for this value is at least 50% of the typical duration of a meridian flip./p/body/html Better? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416003] Scrollbar width in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=416003 Wolfgang Klein changed: What|Removed |Added CC||klein.wo...@web.de --- Comment #14 from Wolfgang Klein --- I came across this page while looking for a solution to this problem as well, and I can't believe what I had to read here. Some one asked about the possibility for setting a certain value dependent on a user's wish and needs, and then a discussion about the user's abilities starts. If that user had a need for a special type of steering wheel in a car, would you also ask why this is so? I totally agree to Cory's and Marcel's statements. Users, handicapped or not, want this feature and need they need this feature. Providing small and next to no scrollbars may make sense on touchscreens where you can swipe, but on a modern hdpi screen they are a pain! Unfortunately, even reverting to the "old" Oxygen style does not provide the needed option any more. So, unless the developers of KDE will reconsider their decision about removing this feature, the should not be wondering when more and more Linux users will be starting other desktops where this option is still available. That would also be my advice to AlexDeLorenzo's friend, if they did not find a better solution yet. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474652] New: No connection to Android device
https://bugs.kde.org/show_bug.cgi?id=474652 Bug ID: 474652 Summary: No connection to Android device Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: w...@freenet.de CC: andrew.g.r.hol...@gmail.com Target Milestone: --- PC: KDE Connect runs on Linux Mint 21.1 Two Android smartphones, both Samsung Galaxy S5, G-900F. One with Android 5.0, other with Android 6.0.1 Android 5.0, the frequently used smartphone: No connection, software reports: No device found. Android 6.0.1 works out of the box -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403243] "ksmserver-logout-greeter" shows up in the Task Manager
https://bugs.kde.org/show_bug.cgi?id=403243 --- Comment #35 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #34) > Likely a timing issue, if your system is fast enough, you won't notice it. Or better worded: if the lock screen shows up fast enough, you won't see it. But the problem is still there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403243] "ksmserver-logout-greeter" shows up in the Task Manager
https://bugs.kde.org/show_bug.cgi?id=403243 --- Comment #34 from Wolfgang Bauer --- Ah, I've just shortly seen it again though. Likely a timing issue, if your system is fast enough, you won't notice it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403243] "ksmserver-logout-greeter" shows up in the Task Manager
https://bugs.kde.org/show_bug.cgi?id=403243 --- Comment #33 from Wolfgang Bauer --- And to stay on topic: I cannot seem to reproduce it anymore with the latest Plasma 5.17.7. So from my point of view, this could probably be closed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403243] "ksmserver-logout-greeter" shows up in the Task Manager
https://bugs.kde.org/show_bug.cgi?id=403243 --- Comment #32 from Wolfgang Bauer --- Oh, the jojo monster again. I'm getting bad memories... :-( -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394784] KMAIl 5.8.1: Reply to HTML-mail in text mode includes content from last mail
https://bugs.kde.org/show_bug.cgi?id=394784 Wolfgang Bauer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #17 from Wolfgang Bauer --- Ok, let's close it then. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 471373] EKOS: Mosaic Scheduler and job completion conditions error
https://bugs.kde.org/show_bug.cgi?id=471373 Wolfgang Reissenberger changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from Wolfgang Reissenberger --- The refactoring is still ongoing, and without it we agreed not to touch the scheduler. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 471373] EKOS: Mosaic Scheduler and job completion conditions error
https://bugs.kde.org/show_bug.cgi?id=471373 Wolfgang Reissenberger changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Wolfgang Reissenberger --- This behavior makes sense, but the current scheduler has no option to group scheduler jobs and repeat this group. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 448647] Krusader sometimes crashes when copying or moving files
https://bugs.kde.org/show_bug.cgi?id=448647 --- Comment #7 from Wolfgang --- Created attachment 158582 --> https://bugs.kde.org/attachment.cgi?id=158582=edit New crash information added by DrKonqi krusader (2.8.0 "A New Day") using Qt 5.15.8 additional post via desktop window. -- Backtrace (Reduced): #5 0x7fcb70ce7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcb7196bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fcb70cbae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcb70cbdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #13 0x7fcb70d14e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 448647] Krusader sometimes crashes when copying or moving files
https://bugs.kde.org/show_bug.cgi?id=448647 Wolfgang changed: What|Removed |Added Version|2.7.2 |2.8.0 Platform|openSUSE|Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 448647] Krusader sometimes crashes when copying or moving files
https://bugs.kde.org/show_bug.cgi?id=448647 Wolfgang changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||wolfgang.kubu...@web.de --- Comment #6 from Wolfgang --- Betriebssystem: Kubuntu 23.04 KDE-Plasma-Version: 5.27.4 KDE-Frameworks-Version: 5.104.0 Qt-Version: 5.15.8 Kernel-Version: 6.2.0-20-generic (64-bit) Grafik-Plattform: X11 Prozessoren: 4 × Intel® Core™ i3-8100 CPU @ 3.60GHz Speicher: 15,3 GiB Arbeitsspeicher Grafikprozessor: Mesa Intel® UHD Graphics 630 Krusader has version 2.8.0 ! my problem also occurred when copying/moving a file/directory on a USB data carrier (ext4). The system was installed 3 days ago as kubuntu 22 and immediately received a distribution update. Apart from the driver for the Epson scanner, nothing has been installed so far. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 --- Comment #6 from Wolfgang Reissenberger --- closed -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 465324] KStars 3.6.4 Beta, Focus module - total crash repeatable 4 times
https://bugs.kde.org/show_bug.cgi?id=465324 Wolfgang Reissenberger changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wreis...@gmx.de Resolution|--- |FIXED Version Fixed In||3.6.4 --- Comment #5 from Wolfgang Reissenberger --- Crashing drivers causing KStars crash fixed, see commit dd1ec285bf6aca12281b840945c29b46e0423777 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 464775] Remote slewing and plate-solving target update problem
https://bugs.kde.org/show_bug.cgi?id=464775 --- Comment #1 from Wolfgang Reissenberger --- There is no stable way to reproduce this issue. I can confirm, I could observe it and that there were situations when the target was not set. But after recompiling everything it *seems* to work - no matter whether the INDI server is local or remote. It looks like a concurrency issue... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463139] Plasma session restore no longer opens files in kwrite
https://bugs.kde.org/show_bug.cgi?id=463139 Wolfgang Illmeyer changed: What|Removed |Added CC||wolfgang.illme...@gmx.net --- Comment #10 from Wolfgang Illmeyer --- I tried your fix on the master branch and it solved the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 400674] Long lines truncated after applying change
https://bugs.kde.org/show_bug.cgi?id=400674 Wolfgang Wallner changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 400674] Long lines truncated after applying change
https://bugs.kde.org/show_bug.cgi?id=400674 Wolfgang Wallner changed: What|Removed |Added Platform|Other |Kubuntu Version|4.1.3 |4.1.22081 --- Comment #3 from Wolfgang Wallner --- The bug is still present. While testing, I realized that the initial description to reproduce the bug is slightly wrong. The file contents should be as follows (the file on the left side should contain the longer line): File1.txt: Line_1 Longer_Line_2 Line_3 File2.txt: Line_1 Line_2 Line_3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #18 from Wolfgang Faust --- Worth noting that KDE Neon 22.04 now has a much newer version of Poppler (22.09.0-0xneon+22.04+jammy+release+build3) and I can now open both the PDF I was having trouble with and the example that Gustavo provided; so the specific circumstances that prompted this bug report appear to have been resolved. I haven't checked the Okular source to see if similar problems would still result in an equally unhelpful error message, though. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446309] Poppler on KDE Neon is very outdated, "Could not open" a PDF from DocuSign
https://bugs.kde.org/show_bug.cgi?id=446309 Wolfgang Faust changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #2 from Wolfgang Faust --- Have just confirmed that this appears to be resolved in Neon built on 22.04; the version of Poppler is much newer (22.09.0-0xneon+22.04+jammy+release+build3, maintained by "Neon CI"; I guess this means that in 22.04 Poppler is updated by KDE on top of the Ubuntu LTS base?) and the PDF I was having trouble with now opens fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #76 from Wolfgang Sailer --- all right, we've just crossed the 22-year line on this bug. I'm out. ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Wolfgang Sailer changed: What|Removed |Added CC|wolfg...@sailer.priv.at | -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 461683] every time i finish a game (win or lose) the following error dialog appears.
https://bugs.kde.org/show_bug.cgi?id=461683 Wolfgang Rohdewald changed: What|Removed |Added CC||wolfg...@rohdewald.de Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Wolfgang Rohdewald --- There is a fix in the pipeline for the next version (only on my PC so far). You can apply it manually: commit 6885135f90c2f65950de7f0d2cb2f39563e086c1 Author: Wolfgang Rohdewald Date: Wed Jun 22 19:40:31 2022 +0200 turning a tile to make it invisible is also legal used when shuffling for the next hand. Since when did this not work? diff --git a/src/uitile.py b/src/uitile.py index e4122648..aa85d724 100644 --- a/src/uitile.py +++ b/src/uitile.py @@ -304,7 +304,7 @@ class UITile(AnimatedMixin, QGraphicsObject, StrMixin): def tile(self, value): # pylint: disable=arguments-differ """set tile name and update display""" if value is not self._tile: -assert not self._tile.isKnown or (self._tile.exposed == value.exposed) +assert not self._tile.isKnown or not value.isKnown or (self._tile.exposed == value.exposed) self._tile = value self.setDrawingOrder() # because known tiles are above unknown tiles self.update() -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458731] New: DOlphin hangs when being opened
https://bugs.kde.org/show_bug.cgi?id=458731 Bug ID: 458731 Summary: DOlphin hangs when being opened Product: dolphin Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: schind...@schintech.net CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. STart Dolphin 2. Cant change Directories, can't open files, no reaction on clicks 3. After some time actions resume to standard work OBSERVED RESULT Wait, wait, wait EXPECTED RESULT Start immediate working SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.4 Kernel Version: 5.18.0+ (64-bit) Graphics Platform: X11 Processors: 4 × AMD Phenom(tm) II X4 965 Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics Manufacturer: Gigabyte Technology Co., Ltd. Product Name: GA-790FXTA-UD5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION While running and after killing Dolphin, you receive this message multiple times --- plasmashell[24805]: kf.kio.core: timeoutSpecialCommand() did not call finished() or error()! Please fix the kio_http KIO slave --- -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 Wolfgang Reissenberger changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Wolfgang Reissenberger --- Please use the forum and provide your logs, we‘ll help you. I‘m closing the bug, since it’s outdated. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452794] Saving a schedule does not save the associated fits file
https://bugs.kde.org/show_bug.cgi?id=452794 Wolfgang Reissenberger changed: What|Removed |Added Resolution|--- |NOT A BUG Assignee|mutla...@ikarustech.com |wreis...@gmx.de CC||wreis...@gmx.de Status|REPORTED|RESOLVED --- Comment #1 from Wolfgang Reissenberger --- The scheduler job only saves the file location, not the file itself. As long as you don't move the reference file, the scheduler will work as expected. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 436036] Meridian flip not working consistently
https://bugs.kde.org/show_bug.cgi?id=436036 Wolfgang Reissenberger changed: What|Removed |Added Assignee|mutla...@ikarustech.com |wreis...@gmx.de Status|REPORTED|NEEDSINFO CC||wreis...@gmx.de Resolution|--- |WAITINGFORINFO --- Comment #2 from Wolfgang Reissenberger --- There have been several fixes for the meridian flip. Is the problem still present in the current KStars version? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 Wolfgang Reissenberger changed: What|Removed |Added Assignee|mutla...@ikarustech.com |wreis...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451532] autofocus filter (1st in sequence) overrides LOCK filter & OFFSETS
https://bugs.kde.org/show_bug.cgi?id=451532 Wolfgang Reissenberger changed: What|Removed |Added CC||wreis...@gmx.de Assignee|mutla...@ikarustech.com |wreis...@gmx.de --- Comment #1 from Wolfgang Reissenberger --- Sorry for the late response, but do you have a log available? If not, could you reproduce it with the current KStars version? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 451687] Attempted Meridian Flip causes great confusion
https://bugs.kde.org/show_bug.cgi?id=451687 Wolfgang Reissenberger changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||wreis...@gmx.de Status|REPORTED|NEEDSINFO --- Comment #1 from Wolfgang Reissenberger --- Sorry for the late response. Do you have the logs available? If not, could you reproduce the same with the latest KStars version? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432007] Okular: No scrolling with non-continuous view
https://bugs.kde.org/show_bug.cgi?id=432007 Wolfgang Scherer changed: What|Removed |Added CC||wolfgang.sche...@gmx.de --- Comment #6 from Wolfgang Scherer --- I agree with David Hurks, taht the circular progress indicator from presentation view would be a real enhancement to non-continous page view. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440063] presentation mode is incompatible with video conferencing via Zoom, BigBlueButton, Webex, ...
https://bugs.kde.org/show_bug.cgi?id=440063 --- Comment #11 from Wolfgang Ertel --- thank you very much for this bug fix. Presentation of Okular (1.9.3) in fullscreen mode with Bigbluebutton works now perfectly. regards Wolfgang Ertel --- Prof. Dr. Wolfgang Ertel http://www.hs-weingarten.de/~ertel Institut für Künstliche Intelligenz http://iki.hs-weingarten.de Hochschule Ravensburg-Weingarten Email: er...@hs-weingarten.de Postfach 3022, D-88216 Weingartenhttp://s4f-ravensburg.de Tel: +49-751-501-9721Tel. privat: +49-751-553814 --- Am 25.07.22 um 15:44 schrieb postix: > https://bugs.kde.org/show_bug.cgi?id=440063 > > postix changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||pos...@posteo.eu > > --- Comment #10 from postix --- > Since bug #421206 seems to have been fixed since 21.12+, can you please check > if you can still reproduce it with some recent Okular version? > -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 456662] kajongg crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=456662 Wolfgang Rohdewald changed: What|Removed |Added CC||wolfg...@rohdewald.de --- Comment #2 from Wolfgang Rohdewald --- according to kajongg/debian.control, kajongg has a new dependency on pyqt since May 2021. The Fedora people seem to have missed that. Maybe there is a better way to define dependencies in a distribution independent way - if so, I will gladly implement that. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 454728] New: Crash on closing Marble
https://bugs.kde.org/show_bug.cgi?id=454728 Bug ID: 454728 Summary: Crash on closing Marble Product: marble Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: wolfgang@aon.at Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.15.2 Frameworks Version: 5.91.0 Operating System: Linux 5.17.11-200.fc35.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - Closed Marble after loading a GPX (which I could not see on the map!) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Marble – Virtueller Globus (marble), signal: Aborted [KCrash Handler] #4 0x7f3d26716aec in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f3d266ca2a6 in raise () at /lib64/libc.so.6 #6 0x7f3d2669d7f3 in abort () at /lib64/libc.so.6 #7 0x7f3d2670aaf7 in __libc_message () at /lib64/libc.so.6 #8 0x7f3d26720bac in () at /lib64/libc.so.6 #9 0x7f3d267224bc in _int_free () at /lib64/libc.so.6 #10 0x7f3d26724f45 in free () at /lib64/libc.so.6 #11 0x7f3d26d88d71 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f3d2848c57d in KXmlGuiWindow::event(QEvent*) () at /lib64/libKF5XmlGui.so.5 #13 0x7f3d27833443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f3d26d5e7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #15 0x7f3d26d61d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #16 0x7f3d26db0117 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #17 0x7f3d2504a0af in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x7f3d2509f308 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #19 0x7f3d250478a3 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x7f3d26dafbb8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7f3d26d5d1e2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7f3d26d65724 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #23 0x5652e2ef03ce in main () [Inferior 1 (process 43814) detached] The reporter indicates this bug may be a duplicate of or related to bug 454575. Possible duplicates by query: bug 454575, bug 453542, bug 453357, bug 452291, bug 451420. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 451244] Discarded tiles in order of discard
https://bugs.kde.org/show_bug.cgi?id=451244 Wolfgang Rohdewald changed: What|Removed |Added CC||wolfg...@rohdewald.de --- Comment #1 from Wolfgang Rohdewald --- Created attachment 147381 --> https://bugs.kde.org/attachment.cgi?id=147381=edit Could look like this What does Mahjong Time do if a discard is claimed? Leave that place empty? That is what I implemented now, being simpler to do. See attachment. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 Wolfgang Bauer changed: What|Removed |Added CC||pokingvic...@protonmail.com --- Comment #25 from Wolfgang Bauer --- *** Bug 448276 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 448276] KGet consistantly crashes when downloading from Archive.org
https://bugs.kde.org/show_bug.cgi?id=448276 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- Already fixed in kget 21.12.1. *** This bug has been marked as a duplicate of bug 444591 *** -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591
Wolfgang Bauer changed:
What|Removed |Added
Version Fixed In||21.12.1
Status|CONFIRMED |RESOLVED
Latest Commit||https://invent.kde.org/netw
||ork/kget/commit/13187db5a42
||88ad5e852c851eec16ea6e0a8cc
||d2
Resolution|--- |FIXED
--- Comment #23 from Wolfgang Bauer ---
Git commit 13187db5a4288ad5e852c851eec16ea6e0a8ccd2 by Wolfgang Bauer.
Committed on 03/01/2022 at 19:22.
Pushed by wbauer into branch 'release/21.12'.
Fix destination filesystem type check for downloads bigger than 4 GiB
`m_dest` is a QUrl, we need to use `toLocalFile()` to get a local path.
`toString()` results in a URL instead ("file://...") which causes the
mountpoint lookup to fail.
Also, the check whether the mountpoint was found was reversed. It
actually tried to compare the filesystem type when the mount point was
*not* found, resulting in a crash because of the nullptr dereference.
FIXED-IN: 21.12.1
M +3-3core/datasourcefactory.cpp
https://invent.kde.org/network/kget/commit/13187db5a4288ad5e852c851eec16ea6e0a8ccd2
--
You are receiving this mail because:
You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 --- Comment #10 from Wolfgang Bauer --- *** Bug 393807 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393807] Kopete crash on quit
https://bugs.kde.org/show_bug.cgi?id=393807 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #3 from Wolfgang Bauer --- Should be fixed in 21.12.0. *** This bug has been marked as a duplicate of bug 436513 *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Wolfgang Bauer changed: What|Removed |Added CC||danielwohl...@gmx.de --- Comment #9 from Wolfgang Bauer --- *** Bug 400283 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400283] Kopete crashed while quitting
https://bugs.kde.org/show_bug.cgi?id=400283 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #3 from Wolfgang Bauer --- Should be fixed in 21.12.0. *** This bug has been marked as a duplicate of bug 436513 *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393662] Kopete Crashes on Program exit
https://bugs.kde.org/show_bug.cgi?id=393662 Wolfgang Bauer changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #6 from Wolfgang Bauer --- Should be fixed in 21.12.0. *** This bug has been marked as a duplicate of bug 436513 *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Wolfgang Bauer changed: What|Removed |Added CC||sh...@sorbom.com --- Comment #8 from Wolfgang Bauer --- *** Bug 393662 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 436513] kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=436513 Wolfgang Bauer changed: What|Removed |Added CC||kdeuser@saur0n.science --- Comment #7 from Wolfgang Bauer --- *** Bug 401181 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 401181] Kopete crashed on exit
https://bugs.kde.org/show_bug.cgi?id=401181 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Wolfgang Bauer --- Should be fixed in 21.12.0. *** This bug has been marked as a duplicate of bug 436513 *** -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 447149] KGet crashes when trying to open Metalink file
https://bugs.kde.org/show_bug.cgi?id=447149 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- *** This bug has been marked as a duplicate of bug 444591 *** -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 Wolfgang Bauer changed: What|Removed |Added CC||lassi.vaatamoi...@gmail.com --- Comment #21 from Wolfgang Bauer --- *** Bug 447149 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447111] 0.10.5 fails to build with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=447111 --- Comment #6 from Wolfgang Bauer --- (In reply to Michail Vourlakos from comment #5) > BTW I found also one important bug that is triggered in startup so in the > weekend there will be a new 0.10.6 if you want to delay this. Thanks for the info! I'll wait with the update for the openSUSE package then. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447111] 0.10.5 fails to build with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=447111 --- Comment #4 from Wolfgang Bauer --- (In reply to Michail Vourlakos from comment #1) > which distro is still using the outdated Qt 5.12? openSUSE Leap. (In reply to Michail Vourlakos from comment #3) > please check again with stable branch v0.10 It compiles successfully now, thanks. Btw, you could have used something like this instead of parsing the QtGui version in CMakeLists.txt: #if QTGUI_VERSION >= QT_VERSION_CHECK(5, 13, 0) (QTGUI_VERSION is defined in QtGui/qtguiversion.h, and there's also QT_VERSION in qtglobals.h) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 447111] New: 0.10.5 fails to build with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=447111 Bug ID: 447111 Summary: 0.10.5 fails to build with Qt 5.12 Product: lattedock Version: 0.10.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: wba...@tmo.at Target Milestone: --- Compiler errors: /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp: In member function 'void Latte::PlasmaExtended::PanelBackground::updateMaxOpacity(Plasma::Svg*)': /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp:124:16: error: 'class QImage' has no member named 'convertTo' center.convertTo(QImage::Format_ARGB32_Premultiplied); ^ /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp: In member function 'void Latte::PlasmaExtended::PanelBackground::updateRoundnessFromMask(Plasma::Svg*)': /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp:171:16: error: 'class QImage' has no member named 'convertTo' corner.convertTo(QImage::Format_ARGB32_Premultiplied); ^ /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp: In member function 'void Latte::PlasmaExtended::PanelBackground::updateRoundnessFromShadows(Plasma::Svg*)': /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp:339:16: error: 'class QImage' has no member named 'convertTo' corner.convertTo(QImage::Format_ARGB32_Premultiplied); ^ /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp: In member function 'void Latte::PlasmaExtended::PanelBackground::updateRoundnessFallback(Plasma::Svg*)': /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp:500:16: error: 'class QImage' has no member named 'convertTo' corner.convertTo(QImage::Format_ARGB32_Premultiplied); ^ /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp: In member function 'void Latte::PlasmaExtended::PanelBackground::updateShadow(Plasma::Svg*)': /home/abuild/rpmbuild/BUILD/latte-dock-0.10.5/app/plasma/extended/panelbackground.cpp:572:16: error: 'class QImage' has no member named 'convertTo' border.convertTo(QImage::Format_ARGB32_Premultiplied); ^ According to the Qt docs, QImage::convertTo() was introduced in Qt 5.13... Maybe it would be possible to use QImage::convertToFormat() instead? (at least when compiling with Qt < 5.13) Apparently the only difference is that this returns a copy of the QImage instead of modifying it directly. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #20 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #18) > Just tried to download current openSUSE Tumbleweed ISO via > https://download.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-x86_64- > Current.iso.meta4 and it crashes again. Thanks, I can reproduce the crash now. I'll investigate and will try to fix it... -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #17 from Wolfgang Bauer --- PS: @Kārlis Kavacis The link in comment#0 unfortunately was obfuscated (by bugzilla I guess), so maybe you could send it to me in private? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #16 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #15) > If you consider them private, maybe we can arrange some way outside this > bugzilla... That also applies to Kārlis Kavacis of course. In the end, I only want to have an URL with which I can reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #15 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #14) > Yep, it solves it, kget starts and downloads as expected, without any crash. > Thx. Good. Could you maybe share the files in the old directory? If you consider them private, maybe we can arrange some way outside this bugzilla... -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #13 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #11) > (In reply to Frank Kruger from comment #9) > > (In reply to Wolfgang Bauer from comment #3) > The main question is, what triggers the crash? My only guess so far is that it has to do with what filesystems are mounted. As the crash reports are all in KMountPoint::mountType() from kio. But comment#5 suggests it depends on the URL... @Frank Kruger: Does it help if you rename the directory "~/.local/share/kget/", so that current downloads are no longer continued? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #11 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #9) > (In reply to Wolfgang Bauer from comment #3) > > Hm. kget 21.08.3 doesn't crash here. > > Is it still happening? > > > > The crash apparently was in kio, actually. > > Maybe it got fixed there already? > > Kget 21.08.3 still crashes at start up with up-to-date openSUSE Tumbleweed > 20211207. Shall I open a bug report there? No. It's likely not a distribution problem, especially as it originally was reported from a Fedora user. The main question is, what triggers the crash? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #10 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #8) > (In reply to Wolfgang Bauer from comment #7) > > (In reply to Kārlis Kavacis from comment #5) > > > Yeah! It's something to do with the download URL or server responses - > > > Fedora Workstation 35 ISO from Fedora home page downloads successfully > > > without crashing KGet! > > > > Would it be possible to share a particular URL that crashes kget? > > > > If I can reproduce the crash, it might help to debug this problem. ;-) > > Although, your latest crash seems to be a different one. Sorry, I didn't look well enough, It's actually still in kio too. > #7 KMountPoint::mountType (this=0x0) at > /usr/src/debug/kf5-kio-5.88.0-1.fc35.x86_64/src/core/kmountpoint.cpp:412 > #8 0x7fed7435b08f in DataSourceFactory::start() () from > /lib64/libkgetcore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #8 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #7) > (In reply to Kārlis Kavacis from comment #5) > > Yeah! It's something to do with the download URL or server responses - > > Fedora Workstation 35 ISO from Fedora home page downloads successfully > > without crashing KGet! > > Would it be possible to share a particular URL that crashes kget? > > If I can reproduce the crash, it might help to debug this problem. ;-) Although, your latest crash seems to be a different one. So my question in comment#3 still stands. @Frank Kruger: what's your experience meanwhile? -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #7 from Wolfgang Bauer --- (In reply to Kārlis Kavacis from comment #5) > Yeah! It's something to do with the download URL or server responses - > Fedora Workstation 35 ISO from Fedora home page downloads successfully > without crashing KGet! Would it be possible to share a particular URL that crashes kget? If I can reproduce the crash, it might help to debug this problem. ;-) -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #16 from Wolfgang Bauer ---
(In reply to Jarosław Staniek from comment #15)
> At run time, as I suggested the
> QIcon::setThemeName(QStringLiteral("breeze")) only declares a desire to use
> breeze, the only currently consistent theme. No way to validate what's
> really available at run time as long as we don't have package dependency
> kexi==>breeze-icons.
We as packagers can declare that dependency though, i.e. make the kexi package
require breeze-icons.
So if you add a cmake option that's disabled by default (call it
"YESIAMAPACKAGERANDIDIDADDABREEZERUNTIMEDEPENDENCYTOMYKEXIPACKAGE" if you want
;-) ), that would help already IMO.
If our kexi package requires breeze5-icons (that's how it is called in
openSUSE) on a package level, a user cannot install kexi without the breeze
theme.
Same as we currently have to make it require breeze5-icons-rcc (which contains
the breeze-icons.rcc file).
--
You are receiving this mail because:
You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #14 from Wolfgang Bauer ---
(In reply to Fabian Vogt from comment #12)
> (In reply to Wolfgang Bauer from comment #8)
> > But of course that would also mean that kexi would then use the system's
> > icon theme. (via KIconTheme or QIcon, I suppose)
> >
> > TBH, I'm not sure how this is currently handled...
>
> Not necessarily, it does:
>
> inline void setupBreezeIconTheme()
> {
> #ifdef QT_GUI_LIB
> QIcon::setThemeSearchPaths(QStringList() << QStringLiteral(":/icons"));
> QIcon::setThemeName(QStringLiteral("breeze"));
> #endif
> }
>
> That should put it at the top of the list.
If I understand that correctly, kexi should already use the breeze icon theme
(when installed), even if the user selected a different one (or uses a
different desktop than Plasma).
So then IMHO it should be sufficient to just remove the check for the .rcc, on
Linux at least (or, as suggested, if some cmake option is enabled/disabled).
--
You are receiving this mail because:
You are watching all bug changes.
[kget] [Bug 444591] KGet crashes when attempting to download anything
https://bugs.kde.org/show_bug.cgi?id=444591 --- Comment #3 from Wolfgang Bauer --- Hm. kget 21.08.3 doesn't crash here. Is it still happening? The crash apparently was in kio, actually. Maybe it got fixed there already? -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 --- Comment #8 from Wolfgang Bauer --- But of course that would also mean that kexi would then use the system's icon theme. (via KIconTheme or QIcon, I suppose) TBH, I'm not sure how this is currently handled... -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 --- Comment #7 from Wolfgang Bauer --- (In reply to Jarosław Staniek from comment #6) > > So maybe add a cmake option to build without the .rcc dependency > > Do you mean build-time dependency only? That would be possible to add > because *you* on openSUSE know what you're doing so you're not going to > abuse it. If someone would break things that's not our trouble... I actually mean a build time option to remove the .rcc dependency on buildtime *and* on runtime. As you say, if we enable that option we know what we are doing and we know that we should add a runtime dependency on the breeze icon theme then...;-) (which we actually already have) -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 --- Comment #5 from Wolfgang Bauer --- (In reply to Jarosław Staniek from comment #4) > Thanks for the bigger picture Wolfgang. IIRC back when we lacked the > build-time check we had situations when KEXI was distributed without the > dependency. Would you see a universal replacement technique to ensure > declared run time dependencies are met? (other than mention in > README.PACKAGERS that depends on human nature) Not really, no. Except that it would be possible to specify the runtime dependency in the cmake files, but that might get overlooked too... > First thing we added was the runtime check. Before that missing icons was > confusing to the user. Not it is confusing too, but at least we can warn in > a message that the KEXI software isn't 100% properly distributed. Well, it is not a warning, but an error. Currently, Kexi just quits if the .rcc is not installed, even if the icons are available because the breeze icon theme is installed. > > Maybe just use the standard icons if the .rcc is not available on build > > time? > > That is the central issue. Standard icons do not include icons that KEXI > requires. So the software looks random and unfinished. > That's the cost of centralization (having a central icon project in KDE > while we can't control "central" desktop environment). Ok, you probably have a point there. That was just a thought. So maybe add a cmake option to build without the .rcc dependency, disabled by default? (or the opposite, have a cmake option to build with the .rcc dependency that is enabled by default) Maybe @Fabian could make a suggestion as well here though. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 --- Comment #3 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #2) > Maybe it would be possible at least to have a way to build it without that > dependency, perhaps by a cmake option? Although, on second thought a cmake option might not even be necessary. Maybe just use the standard icons if the .rcc is not available on build time? -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 --- Comment #2 from Wolfgang Bauer --- That's all good and nice, but the problem still is that kexi depends on the .rcc on buildtime and on runtime even on Linux/KDE where the icons should be available by the breeze icon theme anyway. Currently kexi just fails to start if the .rcc is not installed. (and it fails to build either, if it's not there) At least on openSUSE, we tried to get rid of the burden of building the .rcc as well. It was split out to a separate package just for kexi back then. Maybe it would be possible at least to have a way to build it without that dependency, perhaps by a cmake option? -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 446731] New: Kexi depends on breeze-icons.rcc, but shouldn't
https://bugs.kde.org/show_bug.cgi?id=446731 Bug ID: 446731 Summary: Kexi depends on breeze-icons.rcc, but shouldn't Product: KEXI Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: wba...@tmo.at CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- See the discussion in https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/72 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 446643] New: kwallet password dialog blocks plasma desktop UI on first session login
https://bugs.kde.org/show_bug.cgi?id=446643 Bug ID: 446643 Summary: kwallet password dialog blocks plasma desktop UI on first session login Product: frameworks-plasma Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: wolfgang_ma...@gmx.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144328 --> https://bugs.kde.org/attachment.cgi?id=144328=edit kwallet dialog block plasma panel SUMMARY I have a password-less automatic login from SDDM to plasma desktop. Thus, on first login, kwallet is closed since no credentials have been passed yet. Consequently, kwallet password dialog pops up as the first thing after login in order to retrieve the password for wifi. However, until I respond to that dialog the plasma panel is not shown, see attachment. STEPS TO REPRODUCE 1. Set up a password-less automatic login. 2. Set up something that needs an open kwallet right from the start, e.g. a wifi you automatically log into. 3. It could be important that the password request comes from a plasma panel citizen. I could imaging that not kwallet itself block the plasma panel, but the guy living in the panel who waits for his password request call to return. 4. Start your machine and watch the password dialog pop-up. 5. Observe that the plasma panel is not drawn. OBSERVED RESULT Plasma panel is only drawn after the password dialog has been completed. EXPECTED RESULT Plasma panel should come up w/o being blocked from the password dialog. SOFTWARE/OS VERSIONS Windows: macOS: 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.
[Breeze] [Bug 429016] Problem displaying KGpg icon in dark theme
https://bugs.kde.org/show_bug.cgi?id=429016 Wolfgang Bauer changed: What|Removed |Added CC||kain...@gmail.com, ||wba...@tmo.at Component|icons |Icons Assignee|n...@oxygen-icons.org |visual-des...@kde.org Product|Oxygen |Breeze --- Comment #1 from Wolfgang Bauer --- The icons on the screenshot rather look like coming from the "Breeze" theme to me, not "Oxygen". I'll reassign it to the proper component. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #17 from Wolfgang Faust --- That seems entirely plausible. I see that Poppler has way to get error codes and also some kind of callback mechanism that can use actual error strings? Whereas I guess right now that Generator is just returning Okular::Document::OpenError whenever it notices something has gone wrong, without trying to work out exactly what. But I can't work out what's going on well enough to have an idea of what would need to change. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297
--- Comment #15 from Wolfgang Faust
---
I did a bit of poking around in the Okular source code to see if I could
improve this error message, and discovered that it's coming from this line
(https://invent.kde.org/graphics/okular/-/blob/9144211ba26fed471e2e493ca1febead253edfe6/part/part.cpp#L1775):
QString errorMessage = i18n("Could not open %1. %2", url.toDisplayString(),
QStringLiteral("\n%1").arg(m_document->openError()));
which actually *does* have a parameter for additional error details, but I
couldn't work out where they were supposed to come from. Seems like maybe the
problem is just that something forgot to set this string before returning the
error?
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 Wolfgang Faust changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #14 from Wolfgang Faust --- Yes, I can confirm that KDE Neon seems to use the same version of Poppler, 0.86.1, and I can reproduce the issue with Gustavo's attachment. I've taken the liberty of filing https://bugs.kde.org/show_bug.cgi?id=446309 to see about getting this updated. (Gustavo, once that bug gets taken care of you'll probably be able to manually install the Neon-packaged libpoppler on your system, since Neon is also built on 20.04 LTS.) I'm glad to hear we have a probable cause for this particular case (thanks Gustavo for producing that test PDF!), but I still think the error message needs to be updated to make it clear what's going on when this sort of thing happens. Even if this particular problem is no longer an issue, it's inevitable that some PDFs will be unreadable and the current error message is not at all clear about the problem. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446309] Poppler on KDE Neon is very outdated, "Could not open" a PDF from DocuSign
https://bugs.kde.org/show_bug.cgi?id=446309 Wolfgang Faust changed: What|Removed |Added CC||gust...@angulosolido.pt -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446309] New: Poppler on KDE Neon is very outdated, "Could not open" a PDF from DocuSign
https://bugs.kde.org/show_bug.cgi?id=446309 Bug ID: 446309 Summary: Poppler on KDE Neon is very outdated, "Could not open" a PDF from DocuSign Product: neon Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: wolfgangmcq+acct-bugs.kde@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Poppler on KDE Neon is out of date; this has been identified as the probable cause on a complaint that some PDFs can't be opened: https://bugs.kde.org/show_bug.cgi?id=444297#c10 (which describes it as "an ancient poppler"). This was split from https://bugs.kde.org/show_bug.cgi?id=444297 where I was complaining more generally about the unhelpfulness of the resulting error message; now that we have a shareable test case and an idea of what the problem is I'm creating this bug to see about getting it fixed. There seems to be precedent for this, it looks like Poppler was updated on top of the previous LTS that Neon was built on: https://bugs.kde.org/show_bug.cgi?id=407830 STEPS TO REPRODUCE 1. Try to open this file: https://bugs.kde.org/attachment.cgi?id=144098 with the Okular that comes with KDE Neon OBSERVED RESULT Error dialog, "Could not open file:///tmp/test-docusign-problem.pdf" EXPECTED RESULT Looks like https://bugsfiles.kde.org/attachment.cgi?id=144099 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.11.0-40-generic (64-bit) ADDITIONAL INFORMATION Relevant extracts from "apt-cache show libpoppler-qt5-1": Package: libpoppler-qt5-1 Version: 0.86.1-0ubuntu1 Source: poppler Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian freedesktop.org maintainers -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 --- Comment #3 from Wolfgang Faust --- (On second thought, “Unknown, invalid, or corrupt PDF” might be more accurate, since this PDF at least was neither invalid nor corrupt even though Okular didn’t know what to do with it.) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297
--- Comment #2 from Wolfgang Faust ---
Yes, I understand that there’s not much you can do about fixing the PDF problem
without a copy of the file (unfortunately it’s got a bunch of personal
information in it).
I filed this bug with the intent that it was more about the general
un-informativeness of the error message. You say “The pdf is broken as far as
we understand it“, but even that extremely broad explanation is not obvious
from the error message; in fact my first thought when I saw the dialog box was
that my flash drive had come unmounted, or possibly some strange permission
problem.
Ideally this dialog would have a way of giving more technical details about
what went wrong (“missing header section Foo” or whatever); but barring that it
would at least be useful to know that the problem occurred while trying to
understand the PDF rather than being an I/O error or whatever. Maybe change it
to something like “Invalid or corrupt PDF found while reading {file}.”?
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 444297] New: Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 Bug ID: 444297 Summary: Okular "Could not open" a certain PDF, with no other details Product: okular Version: 21.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: wolfgangmcq+acct-bugs.kde@gmail.com Target Milestone: --- SUMMARY I have what I believe is a valid PDF document (at any rate, `gs` can show it just fine). When I open it in Okular, I get an error dialog box that says "Could not open file:///path/to/document.pdf." (obviously with the actual path in it), and no hints as to what might have gone wrong. STEPS TO REPRODUCE 1. Open a certain PDF. (I *think* the problem is something to do with it having a digital signature; it’s a PDF I downloaded from DocuSign and that’s the error I got from another program I tried opening it with.) OBSERVED RESULT "Could not open file:///path/to/document.pdf." The only output when opened in a terminal is: Unable to open QuickAnnotatingTools XML definition which also appears when I open a PDF that works fine, so I don’t think it’s related. EXPECTED RESULT The PDF opens, or, barring that, some information on what could be wrong. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.23, on Ubuntu 20.04 Focal KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Possibly related: Bug 321483, from 2013, regarding a similarly unhelpful message when opening a PPT file (except that has output on stderr). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422194] Dolphin crashes when opening a directory on an Android (via KDE-Connect)
https://bugs.kde.org/show_bug.cgi?id=422194 --- Comment #2 from Wolfgang Reh --- Did not happen anymore in Version 21.0.8 of dolphin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423091] System Setting App crashes when deleting a duplicated line in virtual screen settings
https://bugs.kde.org/show_bug.cgi?id=423091 --- Comment #14 from Wolfgang Reh --- Can't reproduce the bug with version: Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.16-200.fc34.x86_64 (64-bit) Graphics Platform: X11 But still the first virtual desktop has the same name in the system settings as the second one. But only in the system settings, during mouse-over in the status-bar the correct name is displayed. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 382566] Webengine does not support ad blocking
https://bugs.kde.org/show_bug.cgi?id=382566 Wolfgang Bauer changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||21.08.0 Latest Commit||https://commits.kde.org/kon ||queror/87bca4c4f3d4003e5ea5 ||06f715e1a8b7f43be9ee Status|REPORTED|RESOLVED --- Comment #15 from Wolfgang Bauer --- Actually, adblock support was added to webenginepart meanwhile, see https://invent.kde.org/network/konqueror/-/commit/87bca4c4f3d4003e5ea506f715e1a8b7f43be9ee This is included since 21.08.0, which was released two weeks ago. I suppose this can be closed now then, please feel free to reopen (or open a new bugreport) if it still doesn't work with 21.08.0 or higher. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441335] Images in editor look very different from jpg preview
https://bugs.kde.org/show_bug.cgi?id=441335 --- Comment #5 from Wolfgang Klein --- I checked the settings: none of the options under "Editing" is set. Still, the image is much too bright when opened in the editor. But: there's a button called "use default" on the top of the editor's window. When I click it, the image looks as desired! But this setting is not saved: I have to use that button every time I edit an image. How do I turn this option into default option? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441316] Aspect-ratio cropping does not show a frame to select the crop
https://bugs.kde.org/show_bug.cgi?id=441316 --- Comment #7 from Wolfgang Klein --- Comment on attachment 140933 --> https://bugs.kde.org/attachment.cgi?id=140933 my digikamrc Ups, I wanted to add some text to the attachment. Here's the section you asked for. But even after deleting the whole section the crop tool is still unusable. The attachment is the digikamrc *after* deleting the section. [aspectratiocrop Tool] Auto Orientation=false CompositionGuide Expanded=true CropInformation Expanded=true CropSelection Expanded=true Golden Flip Horizontal=false Golden Flip Vertical=false Golden Section=false Golden Spiral=false Golden Spiral Section=false Golden Triangle=false Guide Color=250,250,255 Guide Lines Type=3 Guide Width=1 Histogram Channel=0 Histogram Scale=1 Hor.Oriented Aspect Ratio=11 Hor.Oriented Aspect Ratio Orientation=0 Hor.Oriented Custom Aspect Ratio Den=1 Hor.Oriented Custom Aspect Ratio Height=1694 Hor.Oriented Custom Aspect Ratio Num=1 Hor.Oriented Custom Aspect Ratio Width=3012 Hor.Oriented Custom Aspect Ratio Xpos=2826 Hor.Oriented Custom Aspect Ratio Ypos=252 Precise Aspect Ratio Crop=false Ver.Oriented Aspect Ratio=5 Ver.Oriented Aspect Ratio Orientation=0 Ver.Oriented Custom Aspect Ratio Den=1 Ver.Oriented Custom Aspect Ratio Height=600 Ver.Oriented Custom Aspect Ratio Num=1 Ver.Oriented Custom Aspect Ratio Width=800 Ver.Oriented Custom Aspect Ratio Xpos=50 Ver.Oriented Custom Aspect Ratio Ypos=50 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 441164] Schedule loading does nothing for some files in Object & Sequence Selection
https://bugs.kde.org/show_bug.cgi?id=441164 Wolfgang Reissenberger changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #3 from Wolfgang Reissenberger --- Merge request available in master -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441335] Images in editor look very different from jpg preview
https://bugs.kde.org/show_bug.cgi?id=441335 --- Comment #2 from Wolfgang Klein --- I found that settings, but the result is not what I want the picture to look. Like I said: I choose the camera's settings deliberately so that the picture should look like on the left part of the screen shot. That's what I could see on the camera's live viewer: the cam shows the picture as it will look like later, including FOD and exposure. I can open the ARW with Rawtherapee and with Darktable, and in both programs the editor shows the image as in the left part of the screen show. Only Digikam's editor changes the picture without the user's doing. So, two out of three programs show the picture as desired. Where's is the error? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441316] Aspect-ratio cropping does not show a frame to select the crop
https://bugs.kde.org/show_bug.cgi?id=441316 --- Comment #10 from Wolfgang Klein --- Oh, yes, thank you! Deleting that line did the trick. Honestly, I can not remember setting that option! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441316] Aspect-ratio cropping does not show a frame to select the crop
https://bugs.kde.org/show_bug.cgi?id=441316 --- Comment #6 from Wolfgang Klein --- Created attachment 140933 --> https://bugs.kde.org/attachment.cgi?id=140933=edit my digikamrc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441335] New: Images in editor look very different from jpg preview
https://bugs.kde.org/show_bug.cgi?id=441335 Bug ID: 441335 Summary: Images in editor look very different from jpg preview Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-RawImport Assignee: digikam-bugs-n...@kde.org Reporter: klein.wo...@web.de Target Milestone: --- Created attachment 140927 --> https://bugs.kde.org/attachment.cgi?id=140927=edit Difference between preview and editor SUMMARY When an image is opened to edit, sometimes (not always) the exposure seems to be corrected to the worse. See attached screenshot: the left half shows the embedded jpg preview, the right half shows the editor. The left image is how I wanted it to look when I set the camera to shoot the picture. The image is taken in ARW format. (Sony camera) Neither knowingly nor willingly did I set any option that says I want those changes to be made when editing an image. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441316] Aspect-ratio cropping does not show a frame to select the crop
https://bugs.kde.org/show_bug.cgi?id=441316 --- Comment #3 from Wolfgang Klein --- One thing changes, though, when I hit any of those two buttons: the values in the fields "position" and "size", but like I said: still no crop rectangle is shown. -- You are receiving this mail because: You are watching all bug changes.
