[Skanpage] [Bug 476838] Format DIN A4 is missing
https://bugs.kde.org/show_bug.cgi?id=476838 --- Comment #10 from Johannes Kehrer --- Yes, of course I would like to help. Let's try... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 418647] kphotoalbum --db always uses 'index.xml' even if a different filename is specified
https://bugs.kde.org/show_bug.cgi?id=418647 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/a ||35ae72934d6fd370486e65492a6 ||52ad62b6c9ce --- Comment #2 from Johannes Zarl-Zierl --- Git commit a35ae72934d6fd370486e65492a652ad62b6c9ce by Johannes Zarl-Zierl. Committed on 03/08/2024 at 15:45. Pushed by johanneszarl into branch 'master'. Update Changelog Add change log entry for the following change: fa8150d1 Don't allow non-existant directories with --db 2499bcbf Be more restricting in allowed filenames. 4940a38a Remove unintended change. ba245601 Move and refactor per review comments. cadf882a Bail with an error message on invalid input. Kudos to rsquared for doing most of the work on this! M +1-0CHANGELOG.md https://invent.kde.org/graphics/kphotoalbum/-/commit/a35ae72934d6fd370486e65492a652ad62b6c9ce -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 418647] kphotoalbum --db always uses 'index.xml' even if a different filename is specified
https://bugs.kde.org/show_bug.cgi?id=418647 Johannes Zarl-Zierl changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Johannes Zarl-Zierl --- Thanks to the work by rsquared on https://invent.kde.org/graphics/kphotoalbum/-/merge_requests/33, this bug is now resolved: KPhotoAlbum now rejects file names other than index.xml instead of silently changing the file name to index.xml. I do accept follow-up bug reports to actually allow different file names, but fixing that is significantly more work because 'index.xml' is hard-coded at various places in the code-base. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 476838] Format DIN A4 is missing
https://bugs.kde.org/show_bug.cgi?id=476838
--- Comment #8 from Johannes Kehrer ---
I executed the command according to your command:
{
"options": {
"KSane::BatchMode": {
"Current value": "false",
"Description": "Enables batch mode scanning. Continues scanning
after a delay until canceled.",
"Internal value list": [
],
"Max value": "",
"Min value": "",
"State": "StateActive",
"Step value": "",
"Title": "Batch mode with time delay",
"Type": "TypeBool",
"Unit": "UnitNone",
"Value list": [
],
"Value size": 0
},
"KSane::BatchTimeDelay": {
"Current value": "10",
"Description": "Specify the time delay between each scan when batch
mode is enabled.",
"Internal value list": [
],
"Max value": "300",
"Min value": "0",
"State": "StateActive",
"Step value": "1",
"Title": "Batch mode time delay",
"Type": "TypeInteger",
"Unit": "UnitSecond",
"Value list": [
],
"Value size": 0
},
"KSane::InvertColors": {
"Current value": "false",
"Description": "Invert the colors of the scanned image.",
"Internal value list": [
],
"Max value": "",
"Min value": "",
"State": "StateActive",
"Step value": "",
"Title": "Invert colors",
"Type": "TypeBool",
"Unit": "UnitNone",
"Value list": [
],
"Value size": 0
},
"KSane::PageSize": {
"Current value": "Custom",
"Description": "Select a predefined page size for the scanning
area.",
"Internal value list": [
],
"Max value": "",
"Min value": "",
"State": "StateActive",
"Step value": "",
"Title": "Scan area size",
"Type": "TypeValueList",
"Unit": "UnitNone",
"Value list": [
"Custom",
"A5",
"A6",
"Letter / ANSI A",
"B5",
"B6",
"Envelope C5",
"Envelope US 10",
"Envelope DL",
"Executive (7.5 x 10 in)",
"JIS B5",
"JIS B6",
"Landscape A5",
"Landscape A6",
"Landscape B6",
"Landscape JIS B6"
],
"Value size": 0
},
"a3-paper": {
"Current value": "false",
"Description": "A3 paper detected",
"Internal value list": [
],
"Max value": "",
"Min value": "",
"State": "StateDisabled",
"Step value": "",
"Title": "A3 paper",
"Type": "TypeBool",
"Unit": "UnitNone",
"Value list": [
],
"Value size": 1
},
"a4-paper": {
"Current value": "false",
"Description": "A4 paper detected",
"Internal value list": [
],
"Max value": "",
"Min value": "",
"State": "StateDisabled",
"Step value": "",
"Title": "A4 paper",
"Type": "Type
[kphotoalbum] [Bug 425410] Names of tag categories suddenly have superfluous ampersands added to them
https://bugs.kde.org/show_bug.cgi?id=425410 --- Comment #15 from Johannes Zarl-Zierl --- Yes, this is a Qt bug. KPhotoAlbum has not yet been ported to Qt6, so even though your system provides Qt 6.7 which contains a fix, KPhotoAlbum is built with and linked against Qt5.x which does not contain the fix. ...and to anticipate your next question: Tobias has started the Qt6 port recently. There will probably be one 5.x version of KPhotoAlbum and soon after that a 6.0 release of KPhotoAlbum. You can expect version 6.0 this year, but I can't promise if that means September or December... -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486782] Error opening files for comparison from Visual Studio
https://bugs.kde.org/show_bug.cgi?id=486782 --- Comment #13 from Johannes Lorenz --- Note, I used kdiff3 1.11.1 . >From comparing the strace, I could not find out the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486782] Error opening files for comparison from Visual Studio
https://bugs.kde.org/show_bug.cgi?id=486782 Johannes Lorenz changed: What|Removed |Added CC||a-spi...@web.de --- Comment #12 from Johannes Lorenz --- Confirming the bug on Arch Linux, it has also been reported https://bbs.archlinux.org/viewtopic.php?id=295528 . A simple "kdiff3 Makefile Makefile" will show the error, and pressing "OK" when the prepopulated files then opens everything. The interesting part: When I press Ctrl + C immediately and then restart kdiff3 the same way, it does find the files. I am about to compare the straces of these two events now. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 490028] Opening files from the command line fails
https://bugs.kde.org/show_bug.cgi?id=490028 Johannes Lorenz changed: What|Removed |Added CC||a-spi...@web.de --- Comment #1 from Johannes Lorenz --- I think this is a duplicate of 486782 in a different situation. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 490105] kcm_krdpserver wants H264 video encoding
https://bugs.kde.org/show_bug.cgi?id=490105 Johannes Obermayr changed: What|Removed |Added Summary|kcm_kdrpserver wants H264 |kcm_krdpserver wants H264 |video encoding |video encoding -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 490105] New: kcm_kdrpserver wants H264 video encoding
https://bugs.kde.org/show_bug.cgi?id=490105 Bug ID: 490105 Summary: kcm_kdrpserver wants H264 video encoding Classification: Plasma Product: KRdp Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: johannesoberm...@gmx.de CC: ahiems...@heimr.nl Target Milestone: --- Created attachment 171567 --> https://bugs.kde.org/attachment.cgi?id=171567=edit Screenshot Error: "Remote desktop cannot be enabled because your system does not support H264 video encoding. Please contact your distribution regarding how to enable it." $ LANG=en zypper se -s krdp h264 Loading repository data... Reading installed packages... S | Name | Type| Version | Arch | Repository ---+--+-+-++--- i | krdp6| package | 6.1.2-1.1 | x86_64 | Haupt-Repository (OSS) i+ | krdp6-lang | package | 6.1.2-1.1 | noarch | Haupt-Repository (OSS) i+ | libopenh264-7| package | 2.3.1-2.suse1699.30 | x86_64 | (System Packages) i+ | mozilla-openh264 | package | 2.3.1-2.suse1699.30 | x86_64 | (System Packages) -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 444744] Recreate (video-) thumbnails selectively
https://bugs.kde.org/show_bug.cgi?id=444744 --- Comment #4 from Johannes Zarl-Zierl --- Sorry, I meant to say "...the bug is now fixed", not "not". -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 444744] Recreate (video-) thumbnails selectively
https://bugs.kde.org/show_bug.cgi?id=444744 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #3 from Johannes Zarl-Zierl --- Hi Andreas, Could you check the video thumbnail behavior again? I believe that this bug is not fixed... Cheers, Johannes -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 444744] Recreate (video-) thumbnails selectively
https://bugs.kde.org/show_bug.cgi?id=444744 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/6 ||784c08ab39894dc135a4bec6340 ||aaf1a26b14fe Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Johannes Zarl-Zierl --- Git commit 6784c08ab39894dc135a4bec6340aaf1a26b14fe by Johannes Zarl-Zierl. Committed on 02/07/2024 at 22:22. Pushed by johanneszarl into branch 'master'. Merge branch 'work/jzarl/videothumbnailcache' https://invent.kde.org/graphics/kphotoalbum/-/commit/6784c08ab39894dc135a4bec6340aaf1a26b14fe -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 489337] New: Unable to open files under /mnt
https://bugs.kde.org/show_bug.cgi?id=489337 Bug ID: 489337 Summary: Unable to open files under /mnt Classification: Applications Product: kile Version: 2.9.94 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: user interface Assignee: michel.lud...@gmail.com Reporter: kde-b...@jwolf.me Target Milestone: --- Created attachment 171099 --> https://bugs.kde.org/attachment.cgi?id=171099=edit Archive with 5 pngs *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I have a second drive mounted to /mnt/data and I soft link most of my home folders (Music, Documents, Videos, etc) to that location (bug_kile_1). I'm unable to see these linked folders in the file picker (bug_kile_2). When I open a file with Kile it shows an error after opening the application (bug_kile_3). The linked folders show up as files in the file picker, if "All files" is selected (bug_kile_4). I'm unable to see my /mnt directory in the file picker (bug_kile_5). /mnt is owned by root with 755 permissions. No other applications I've tried (flatpak and not flatpak) have this issue. STEPS TO REPRODUCE 1. Create /mnt/data, if it does not already exist 2. (optional) Mount a disk to /mnt/data 3. Create /mnt/data/dir owned by user running Kile 4. Create a file in /mnt/data/dir 5. Open this file OBSERVED RESULT Open any file the user has permission to open EXPECTED RESULT Some files are cannot be opened, because of their location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kile installed as Flatpak -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489101] Fonts render ugly when Scaling is fractional.
https://bugs.kde.org/show_bug.cgi?id=489101 --- Comment #1 from Maximilian-Johannes Begemann --- Created attachment 170908 --> https://bugs.kde.org/attachment.cgi?id=170908=edit Classic Start menu from Plasma. Font rendering is here off aswell. Some letters are too thick and others are way too thin. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 489101] New: Fonts render ugly when Scaling is fractional.
https://bugs.kde.org/show_bug.cgi?id=489101 Bug ID: 489101 Summary: Fonts render ugly when Scaling is fractional. Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: maximil...@begemann.info Target Milestone: --- Created attachment 170907 --> https://bugs.kde.org/attachment.cgi?id=170907=edit Screenshot of the Window decoration of Davinci Resolve. The rendering is off, just like described in the report. SUMMARY After Upgrading to Plasma 6.1 Fonts became ugly. STEPS TO REPRODUCE 1. Set Wayland Scaling to any fractional value (e.g. 150%) 2. Pay close attention to any labels within a software. Most noticeable are window decorations when a window is maximized OBSERVED RESULT Letters are not in a straight line and the spacing looks off. Also some letters appear wider than others, while some are way too thin and hard to read. This affects any font. IBM Plex is used in this example, but other fonts show the same behaviour. EXPECTED RESULT Font rendering just like in Plasma 6.0 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.9.6-arch1 (Patch Level from 24.06.2024) (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Font rendering becomes decent again when switched to 200% scaling. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 489048] New: Baloo crashes at startup and multiple times after
https://bugs.kde.org/show_bug.cgi?id=489048 Bug ID: 489048 Summary: Baloo crashes at startup and multiple times after Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.115.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: lemondej...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.115.0) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.0-35-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 24.04 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Baloo crashes at startup and multiple times after. First time at startup, I was greeted by the crash report even before my backgroud image showed up. Then periodically every few minutes I get a notification for an addition crash. The crash can be reproduced sometimes. -- Backtrace: Application: Extracteur de fichiers Baloo (baloo_file_extractor), signal: Segmentation fault [KCrash Handler] #4 0x7e456625adb9 in _opf_label_get_by_lang () from /lib/libepub.so.0 #5 0x7e456625aeb9 in epub_tit_next () from /lib/libepub.so.0 #6 0x7e4566293178 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_epubextractor.so #7 0x5645452f41df in ?? () #8 0x5645452f6235 in ?? () #9 0x7e456bb171aa in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7e456bb0624b in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7e456bad8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7e456bb345ab in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7e456bb34f11 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7e456a5145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7e456a573717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7e456a513a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7e456bb35279 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7e456bad6a7b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7e456badf3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x5645452ebf63 in ?? () #21 0x7e456b02a1ca in __libc_start_call_main (main=main@entry=0x5645452eb280, argc=argc@entry=1, argv=argv@entry=0x7ffdfa36a4f8) at ../sysdeps/nptl/libc_start_call_main.h:58 #22 0x7e456b02a28b in __libc_start_main_impl (main=0x5645452eb280, argc=1, argv=0x7ffdfa36a4f8, init=, fini=, rtld_fini=, stack_end=0x7ffdfa36a4e8) at ../csu/libc-start.c:360 #23 0x5645452ec075 in ?? () [Inferior 1 (process 10342) detached] The reporter indicates this bug may be a duplicate of or related to bug 481013, bug 481370, bug 481429, bug 481616, bug 483373, bug 484053, bug 485071, bug 487481, bug 488759. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 348688] Hyper key getting recognized as a Meta/Win key
https://bugs.kde.org/show_bug.cgi?id=348688 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487466] Plasmashell crashes when unlocking screen after resuming from sleep while external screen is connected over HDMI
https://bugs.kde.org/show_bug.cgi?id=487466 Johannes H changed: What|Removed |Added CC||j@gmx.com -- 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 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #7 from Johannes Zarl-Zierl --- Hi, I can't reproduce this either, but I also don't have plasma6 yet. TIFF with both 8 and 16 bit work for me; 32 bit do not. My best guess is that this is a library issue in your distribution. Could you open a bug with Manjaro to see if they can debug the problem? In the mid-term, this issue is probably solved by porting kphotoalbum to plasma6. Unfortunately, I'm a currently bit tight on time so I can't give you an estimate when this will be... Cheers, Johannes -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 320297] Incredibly slow video thumbnailing
https://bugs.kde.org/show_bug.cgi?id=320297 Johannes Zarl-Zierl changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Johannes Zarl-Zierl --- Thanks for checking and reporting back! Closing the bug... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486066] Window management broken
https://bugs.kde.org/show_bug.cgi?id=486066
--- Comment #4 from Johannes ---
Thumbs up for the fast response! I was afraid this might be some intended
change, read somewhere on discuss.kde.org that the window management was
changed ("for the better") and had the gnome story in front of my eyes...
The patch works for me. Thanks again for the fast fix, kate has become somewhat
irreplaceable for me.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 486066] New: Window management broken
https://bugs.kde.org/show_bug.cgi?id=486066 Bug ID: 486066 Summary: Window management broken Classification: Applications Product: kate Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: priv...@jfuhlemann.de Target Milestone: --- The window management of Kate has changed recently. It completely breaks working with multiple projects on multiple virtual desktops simultaneously. STEPS TO REPRODUCE 1. Open a document with Kate on virtual desktop 1 2. Switch to another virtual desktop, say 2 3. Open a document there OBSERVED RESULT The document opens in the already existing kate instance on virtual desktop 1. The window manager switches back to virtual desktop 1. EXPECTED RESULT A new kate window appears on virtual desktop 2 with the newly opened document. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 X11 Also tested on XFCE/KWin and on LXQT. Also tested with a fresh user account to rule out any odd settings. ADDITIONAL INFORMATION I've been using Kate for more than 10 years now. The changed window management makes it absolutely impossible to use Kate on multiple virtual desktops with multiple open projects. When clicking a file in dolphin it shouldn't matter if there is an open Kate window on *some other* virtual desktop with *a completely unrelated* project open. Consider you're working on some C project on virtual desktop 1. You created a .kateproject to manage files, set up the lsp server and have lots of .c and .h open in the Kate window. Now you switch to another virtual desktop and need to look in a piece of python that is in no way related to the C project. Maybe you got a phone call and someone is asking. So you open up dolphin, navigate to the project and click the .py file you want. It suddenly appears in your open C project somewhere between the 10 open tabs you were working on before. Also you're suddenly back on virtual desktop 1. Also the "Behaviour -> Open each document in its own window" option doesn't help as Kate now opens a new window even if you drag a file onto an existing Kate window. The option makes it impossible to have more than one tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444043] Make non-color-scheme-following Plasma styles respect global accent color (not the full color scheme, just the accent color)
https://bugs.kde.org/show_bug.cgi?id=444043 Johannes Jordan changed: What|Removed |Added CC||k...@lanrules.de --- Comment #29 from Johannes Jordan --- Still present in 6.0.3. It took me a long time to realize this was the issue, even though in Plasma Style settings it is clearly marked which themes follow the color scheme and which not. It is just something I do not associate with the accent color. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 476838] Format DIN A4 is missing
https://bugs.kde.org/show_bug.cgi?id=476838 --- Comment #5 from Johannes Kehrer --- Hi, correct the selectable scan area sizes are: Custom (this is what I use) A5 A6 Letter / Ansi A B5 B6 Envelop C5 Envelop US 10 Envelop DL Executive (7.5 x 10 in) JIS B5 JIS B6 Landscape A5 Landscape A6 Landscape B6 Landscape JIS B6 Thanks, Johannes -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=478222 --- Comment #19 from Johannes --- @caulier.gilles : Not yet. I'm a farmer and the work outside started. I'll report when I updated my computer. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 462458] Default window size ever so slightly too small to display tall/desktop view with German language
https://bugs.kde.org/show_bug.cgi?id=462458 Johannes Obermayr changed: What|Removed |Added CC||johannesoberm...@gmx.de --- Comment #3 from Johannes Obermayr --- (In reply to Nate Graham from comment #2) > The problem here is the humongous button labeled "Weitere Einstellungen zum > Erscheinungsbild…" I wonder if there's a way to shorten this at all. Moving > to i18n for discussion there. Maybe we should rename to where they link to (what they open): button "More Appearance Settings…" -> "[Set] Colors & Themes" -> German: "Farben & Designs [einstellen …]" button "More Behavior Settings…" -> "[Set] General Behavior" -> German "Allgemeines Verhalten [einstellen …]" Both would be shorter ... -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 476838] Format DIN A4 is missing
https://bugs.kde.org/show_bug.cgi?id=476838 --- Comment #3 from Johannes Kehrer --- (In reply to Alexander Stippich from comment #1) > Can you look up the maximum x and y values the scanner reports? I.e. the max > values of the top-left x/y and bottom-right x/y options in Skanpage. I guess the information is contained as the maximum numbers int the settings area: Top-Left x: 0,00 mm Top-left y: 0,00 mm Bottom-right x: 210,01 mm Bottom-right y: 296,99 mm However, the scanner can also scan Letter formats and it is not a flat-bed scanner, so in general can scan pages of any length... -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 479735] NeoChat (Git) crashes when trying to connect to a room
https://bugs.kde.org/show_bug.cgi?id=479735 Johannes Obermayr changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #3 from Johannes Obermayr --- Fixed with Qt 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 --- Comment #25 from Johannes Penßel --- (In reply to Vlad Zahorodnii from comment #24) > I cannot reproduce the issue by following those steps I just tested a few things. For some weird reason, this seems to be a side effect of using KWIN_FORCE_SW_CURSOR=0 on intel, and unsetting it resolves it completely. I am not affected by the issues described in #474725, so I thought I could get away with using this. When KWIN_FORCE_SW_CURSOR=0 is set, this issue is also present in combination with swrast/llvmpipe. I cannot reproduce this at all on my box with AMD (RDNA2) graphics, but I wonder if KWIN_FORCE_SW_CURSOR=1 would have made a difference back when I used to encounter this issue on that machine as well. Going to try this with a plasma6-rc1 live image later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 --- Comment #23 from Johannes Penßel --- I think I found a method to reproduce this issue reliably: 1. press Meta+W to open the overview 2. click on the search bar below the virtual desktop selection This triggers the exact same behavior as outlined in the original bug description. Since my last comment a month ago, I have not once been able to reproduce this with the task switcher. (I'm still using the new default switcher) systemd-journal snippet: kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindVertexArray(non-gen name) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawArrays kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawArrays kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glVertexAttribPointer(no array object bound) kwin_wayland_wrapper[1417]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawArrays (...) Linux 6.7.5-gentoo Mesa 24.0.1 / Iris Qt 6.6.2 KDE Frameworks master branch Plasma 6.0 branch Gear 24.02 branch -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 481453] New: kde-gtk-config does not check for GTK+3 with X11 support
https://bugs.kde.org/show_bug.cgi?id=481453
Bug ID: 481453
Summary: kde-gtk-config does not check for GTK+3 with X11
support
Classification: Plasma
Product: Breeze
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: gtk theme
Assignee: plasma-b...@kde.org
Reporter: johannes.pens...@gmail.com
CC: agrine...@gmail.com, uhh...@gmail.com
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
***
kde-gtk-config uses GtkPlug for previewing, which is an X11-specific class.
${ROOT}/gtk3proxies/preview3.c includes gtkx.h. However, CMake only searches
for the generic gtk+-3.0 package-config file. If GTK+3 is built without X11
support, kde-gtk-config fails to compile.
STEPS TO REPRODUCE
1. switch to an X11-free version of GTK3 and its development files.
2. attempt to build kde-gtk-config.
OBSERVED RESULT
1. CMake configuration succeeds.
2. compilation fails at ${ROOT}/gtk3proxies/preview3.c
EXPECTED RESULT
CMake searches for gtk+-x11-3.0.pc and throws an error if it is absent.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.5-gentoo
(available in About System)
KDE Plasma Version: 6.0.0 (6.0 branch)
KDE Frameworks Version: 6.0.0 (master)
Qt Version: 6.6.2
--
You are receiving this mail because:
You are watching all bug changes.
[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name
https://bugs.kde.org/show_bug.cgi?id=481181 --- Comment #5 from Johannes Zarl-Zierl --- Git commit 7b97f61b160eda5aa1443bb22d4093cd0a7112e8 by Johannes Zarl-Zierl. Committed on 11/02/2024 at 15:42. Pushed by johanneszarl into branch 'master'. Prevent introduction of trailing/leading whiteespace for tag names This is only preventing unsanitized names to be entered into the database, but does not prevent inconsistent UI. M +11 -9DB/Category.cpp M +14 -3DB/Category.h M +25 -21 DB/MemberMap.cpp M +5-1DB/MemberMap.h https://invent.kde.org/graphics/kphotoalbum/-/commit/7b97f61b160eda5aa1443bb22d4093cd0a7112e8 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name
https://bugs.kde.org/show_bug.cgi?id=481181 Johannes Zarl-Zierl changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/7 ||a1b41e5847efb2a9d9b5c8e3452 ||0a92ae726f1d Resolution|--- |FIXED --- Comment #4 from Johannes Zarl-Zierl --- Git commit 7a1b41e5847efb2a9d9b5c8e34520a92ae726f1d by Johannes Zarl-Zierl. Committed on 11/02/2024 at 15:57. Pushed by johanneszarl into branch 'master'. Prevent addition of tag names with leading/trailing whitespace M +19 -3AnnotationDialog/ListSelect.cpp M +14 -7Settings/TagGroupsPage.cpp M +2-1Viewer/SelectCategoryAndValue.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/7a1b41e5847efb2a9d9b5c8e34520a92ae726f1d -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name
https://bugs.kde.org/show_bug.cgi?id=481181 --- Comment #3 from Johannes Zarl-Zierl --- I didn't look into the reason why you can't navigate to a tag that begins or ends with a whitespace character, but you're right with your question - the bug is that these names can be entered at all. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name
https://bugs.kde.org/show_bug.cgi?id=481181
--- Comment #2 from Johannes Zarl-Zierl ---
The same behavior can also be triggered in the following ways:
- by annotating via the image viewer and adding a new tag using the "new"
annotation mode ("F2", then "Ctrl-A", "Add tag")
- by renaming a tag group via Settings | Tag groups
--
You are receiving this mail because:
You are watching all bug changes.
[kphotoalbum] [Bug 481181] Can not select images using tag with leading/trailing whitespace in the tag name
https://bugs.kde.org/show_bug.cgi?id=481181 Johannes Zarl-Zierl changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||johan...@zarl-zierl.at -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481190] New: KWin crashes on alt tab. Several windows were open.
https://bugs.kde.org/show_bug.cgi?id=481190 Bug ID: 481190 Summary: KWin crashes on alt tab. Several windows were open. Classification: Plasma Product: kwin Version: 5.27.10 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: johannes.der...@gmx.de Target Milestone: --- Application: kwin_x11 (5.27.10) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.6.13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: I alt+tab through several firefox windows and pycharm windows. The tabbing was buggy and the windows didn't show a preview. KWin crashed then 2 times in a row when alt+tabbing. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault PID: 1942 (kwin_x11) UID: 1000 (johannes) GID: 1000 (johannes) Signal: 11 (SEGV) Timestamp: Sat 2024-02-10 22:55:52 CET (46s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (johannes) Boot ID: 5ed1274be3a84b2eb136b4b1fc514515 Machine ID: 7022a249a2a04e5688393321af5fbac6 Hostname: johannes-debian Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.5ed1274be3a84b2eb136b4b1fc514515.1942.170760215200.zst (present) Size on Disk: 7.2M Message: Process 1942 (kwin_x11) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-255.3-1.amd64 Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64 Module libudev.so.1 from deb systemd-255.3-1.amd64 Stack trace of thread 1942: #0 0x7f16529c916c n/a (libc.so.6 + 0x8a16c) #1 0x7f165297b472 raise (libc.so.6 + 0x3c472) #2 0x7f1655d49b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f165297b510 n/a (libc.so.6 + 0x3c510) #4 0x7f16529c916c n/a (libc.so.6 + 0x8a16c) #5 0x7f165297b472 raise (libc.so.6 + 0x3c472) #6 0x7f165297b510 n/a (libc.so.6 + 0x3c510) #7 0x7f16529c41c4 n/a (libc.so.6 + 0x851c4) #8 0x7f16529c6888 pthread_cond_wait (libc.so.6 + 0x87888) #9 0x7f16538e0cab _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xe0cab) #10 0x7f165520c508 n/a (libQt5Quick.so.5 + 0x20c508) #11 0x7f165520d7c3 n/a (libQt5Quick.so.5 + 0x20d7c3) #12 0x7f1653f4b9c5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x14b9c5) #13 0x7f1653162f32 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f32) #14 0x7f1653acc748 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2cc748) #15 0x7f1653f40931 _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x140931) #16 0x7f1653f131ac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x1131ac) #17 0x7f164e0fa15e n/a (libQt5XcbQpa.so.5 + 0x6f15e) #18 0x7f16515111f4 n/a (libglib-2.0.so.0 + 0x571f4) #19 0x7f1651514317 n/a (libglib-2.0.so.0 + 0x5a317) #20 0x7f1651514930 g_main_context_iteration (libglib-2.0.so.0 + 0x5a930) #21 0x7f1653b27d4a _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x327d4a) #22 0x7f1653acb0fb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2cb0fb) #23 0x7f1653ad38a4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2d38a4) #24 0x55af4c902275 n/a (kwin_x11 + 0x43275) #25 0x7f16529666ca n/a (libc.so.6 + 0x276ca) #26 0x7f1652966785 __libc_start_main (libc.so.6 + 0x27785) #27 0x55af4c903831 n/a (kwin_x11 + 0x44831) Stack trace of thread 1970: #0 0x7f1652a3aabf __poll (libc.so.6 + 0xfbabf) #1 0x7f1651514277 n/a (libglib-2.0.so.0 + 0x5a277) #2 0x7f1651514930 g_main_context_iteration (libglib-2.0.so.0 + 0x5a930
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=478222 --- Comment #17 from Johannes --- @Giles: Unfortunately yes. I think I'll have to update Ubuntu soon because other updated programs also started not to run under Ubuntu 20.04.6 anymore… digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libdigikamgui.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libMagick++-7.Q16.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libdigikamdatabase.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libdigikamcore.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5ConfigCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Widgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5Service.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Xml.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_imgcodecs.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_dnn.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_imgproc.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_ml.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_core.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_core.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libopencv_core.so.409) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libexiv2.so.28) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/liblensfun.so.2) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5ConfigWidgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Network.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5KIOCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libKF5WindowSystem.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libde265.so) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaIXGp5E/usr/lib/libQt5Qml.so.5) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 --- Comment #14 from Johannes Penßel --- Can confirm, shouldn't have jinxed it :( sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 Johannes Penßel changed: What|Removed |Added CC||johannes.pens...@gmail.com --- Comment #8 from Johannes Penßel --- Even though I used to hit this bug several times per day, it has not occured on my machine since I've rebuilt kwin on monday evening. I'm starting to suspect that some commit between ffb13a1c and 49ced6dc might have fixed this already. Can anyone confirm this? I'm building KDE off the branches targeting 6.0. Operating System: Gentoo KDE Plasma Version: 5.92.90 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.7.0-gentoo (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Graphics Processor: Mesa Intel® Graphics -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 479735] NeoChat (Git) crashes when trying to connect to a room
https://bugs.kde.org/show_bug.cgi?id=479735 --- Comment #1 from Johannes Obermayr --- dmesg says: [13700.130513] neochat[10127]: segfault at 8 ip 7f7efa80eb70 sp 7ffddb7dfec8 error 4 in libQt6Quick.so.6.6.1[7f7efa7aa000+391000] likely on CPU 0 (core 0, socket 0) [13700.130524] Code: 10 05 24 f2 33 00 48 8b 80 88 00 00 00 48 83 f8 07 76 09 48 83 e0 f8 f2 0f 10 40 08 c3 90 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 47 08 f2 0f 10 05 f4 f1 33 00 48 8b 80 88 00 00 00 48 83 f8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 479735] New: NeoChat (Git) crashes when trying to connect to a room
https://bugs.kde.org/show_bug.cgi?id=479735 Bug ID: 479735 Summary: NeoChat (Git) crashes when trying to connect to a room Classification: Applications Product: NeoChat Version: git master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: johannesoberm...@gmx.de CC: c...@carlschwan.eu Target Milestone: --- Created attachment 164862 --> https://bugs.kde.org/attachment.cgi?id=164862=edit neochat_crash_gdb DrKonqi sadly doesn't catch this bug - so I used gdb directly. It happens all the time after I logged in and try to connect to a room (e. g. kde-l10n-de). $ gdb neochat -batch -ex r -ex "bt full" -ex q >/tmp/neochat_crash.txt -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 472793] merkuro-calendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472793 Johannes Brakensiek changed: What|Removed |Added CC||k...@devbeejohn.de Version|unspecified |23.08.4 --- Comment #8 from Johannes Brakensiek --- Confirmed this still happens with version 23.08.04. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 479483] Deleting an image from the annotation dialog makes the dialog jump to the first image
https://bugs.kde.org/show_bug.cgi?id=479483 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/0 ||2445f10283c3f12f800cd168bcb ||e94076177ffb --- Comment #1 from Johannes Zarl-Zierl --- Git commit 02445f10283c3f12f800cd168bcbe94076177ffb by Johannes Zarl-Zierl. Committed on 06/01/2024 at 23:20. Pushed by johanneszarl into branch 'master'. Avoid jumping to the first image if an image is deleted in the annotation dialog M +2-2AnnotationDialog/Dialog.cpp M +8-1AnnotationDialog/ImagePreviewWidget.cpp M +7-1AnnotationDialog/ImagePreviewWidget.h M +1-0CHANGELOG.md https://invent.kde.org/graphics/kphotoalbum/-/commit/02445f10283c3f12f800cd168bcbe94076177ffb -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 479483] Deleting an image from the annotation dialog makes the dialog jump to the first image
https://bugs.kde.org/show_bug.cgi?id=479483 Johannes Zarl-Zierl changed: What|Removed |Added Version|unspecified |5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 479483] New: Deleting an image from the annotation dialog makes the dialog jump to the first image
https://bugs.kde.org/show_bug.cgi?id=479483 Bug ID: 479483 Summary: Deleting an image from the annotation dialog makes the dialog jump to the first image Classification: Applications Product: kphotoalbum Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Annotation Dialog Assignee: kpab...@willden.org Reporter: johan...@zarl-zierl.at Target Milestone: --- SUMMARY Crash report as written by Constantin Orăsan (via the mailing list): Whenever I delete an image, the annotation dialog jumps back to the first image from the selection. STEPS TO REPRODUCE 1. select a bunch of images 2. select "annotate individual images" 3. annotate images or just navigate through images 4. delete an image from the dialog At this stage I would expect that the dialog moves to the next image (as it used to do in the past). Instead it jumps back to the first image in the selection. I compiled KPA from the source on Ubuntu 23.10. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=478222 --- Comment #13 from Johannes --- @ Maik: Thanks for the tip, but: build-essential is already the newest version (12.8ubuntu1.1). Why should I install build-essential as an end user anyway? I thought the idea behind AppImages is that all necessary libraries get shipped with the program. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 479056] AppImage5.1 531c98b7 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=479056 --- Comment #1 from Johannes --- Please correct the version field, I don't know the correct version to use for newest AppImage: It's not 5.1.3 because this version is what I get from the package repository on Ubuntu 20.4, and it can't be git (master), because the Pipeline page says: Branch 5.1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 479056] New: AppImage5.1 531c98b7 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=479056 Bug ID: 479056 Summary: AppImage5.1 531c98b7 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found Classification: Applications Product: kmymoney Version: unspecified Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-de...@kde.org Reporter: johannes.lists+bugs.kde@tannenhof-imshausen.de Target Milestone: --- SUMMARY I downloaded newest AppImage https://invent.kde.org/office/kmymoney/-/jobs/1459367/artifacts/download?file_type=archive from here https://invent.kde.org/office/kmymoney/-/pipelines?page=1=all=5.1=success as described on https://kmymoney.org/appimage.html and tried to start it, which fails. STEPS TO REPRODUCE 1. Download newest AppImage as described in SUMMARY on Ubuntu 20.04 2. Start it in terminal OBSERVED RESULT Following error messages appear in the terminal: /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5Holidays.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5ConfigWidgets.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5KIOCore.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5Service.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5ConfigCore.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Network.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Xml.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5CoreAddons.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Widgets.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Core.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Core.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5WebEngineCore.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5WebEngineCore.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Quick.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5WebChannel.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Qml.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libQt5Positioning.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5WindowSystem.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKPim5AkonadiCore.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libKF5Contacts.so.5) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_kmymonWLmuCj/usr/lib/libicuuc.so.71) /tmp/.mount_kmymonWLmuCj/AppRun.wrapped:
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=478222 Johannes changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=479056 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 478944] Background color in viewer changes after zooming in or out
https://bugs.kde.org/show_bug.cgi?id=478944 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/0 ||883c80af5d5d545c13d7e707cac ||362456073ec1 Status|REPORTED|RESOLVED --- Comment #1 from Johannes Zarl-Zierl --- Git commit 0883c80af5d5d545c13d7e707cac362456073ec1 by Johannes Zarl-Zierl. Committed on 24/12/2023 at 00:14. Pushed by johanneszarl into branch 'master'. Use the correct background color in viewer for zoomed images When zooming in the viewer window, such that there is a border outside of the image itself, that border was until now drawn black instead of the QPalette::base() color. The reason for this is that the zoomed image is actually a copy of the loaded image with those borders. Adding an alpha channel to the image fixes the issue. It would possibly be a better fix to draw a scaled image in ImageDisplay::paintEvent instead, but that would be a major rewrite of the ImageDisplay code. M +1-0CHANGELOG.md M +4-1Viewer/ImageDisplay.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/0883c80af5d5d545c13d7e707cac362456073ec1 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 478942] Polishing full screen viewer proposal
https://bugs.kde.org/show_bug.cgi?id=478942 Johannes Zarl-Zierl changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 478942] Polishing full screen viewer proposal
https://bugs.kde.org/show_bug.cgi?id=478942 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #1 from Johannes Zarl-Zierl --- Hi Alex, Since you explicitly mention the image scale / zoom level: just adding a padding to the viewer would do nothing to limit scale breaks. I suppose you would like an option to specify a (persistent) zoom level across images? Cheers, Johannes -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 478944] New: Background color in viewer changes after zooming in or out
https://bugs.kde.org/show_bug.cgi?id=478944 Bug ID: 478944 Summary: Background color in viewer changes after zooming in or out Classification: Applications Product: kphotoalbum Version: 5.12.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Viewer Assignee: kpab...@willden.org Reporter: johan...@zarl-zierl.at Target Milestone: --- SUMMARY In the viewer window, if one uses any zoom operation on the image display, the color changes from gray to black. STEPS TO REPRODUCE 1. Open kphotoalbum --demo 2. Go to thumbnail view 3. Double-click an image to open the viewer 4. Press a shortcut associated with a zoom operation (+,-,=,.) OBSERVED RESULT The image is zoomed correctly, but the margins between the image and the viewer window border / screen border changes from dark gray to black. EXPECTED RESULT The background color should be preserved. ADDITIONAL INFORMATION Can be reproduced every time, can be reproduced using the demo database. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=478222 Johannes changed: What|Removed |Added Summary|AppImage 8.2.0 fails to |AppImage 8.2.0 fails to |start on Ubuntu 20.04: |start on Ubuntu 20.04: |CXXABI_1.3.13 and |CXXABI_1.3.13, |GLIBCXX_3.4.29 not found|GLIBCXX_3.4.29 and ||GLIBCXX_3.4.30 not found -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13 and GLIBCXX_3.4.29 not found
https://bugs.kde.org/show_bug.cgi?id=478222 --- Comment #5 from Johannes --- Thanks for your continuous efforts, Gilles! I tested digiKam-8.3.0-20231222T162413-x86-64.appimage on Ubuntu 20.04.6 LTS and unfortunately without success, there are now even more error messages: -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1:/usr/lib/x86_64-linux-gnu/libssl.so.1.1:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linux-gnu/libgnutls.so.30 digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libdigikamgui.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libMagick++-7.Q16.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libdigikamdatabase.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libdigikamcore.so.8.3.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5ConfigCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5Widgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5Core.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5Service.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5Xml.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_imgcodecs.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_dnn.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_imgproc.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_ml.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libexiv2.so.28) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/liblensfun.so.2) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5WebEngineCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5ConfigWidgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libQt5Network.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5KIOCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libKF5WindowSystem.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKamj2sA5/usr/lib/libde265.so) digikam: /lib/x86_64-linux-gnu
[kdeconnect] [Bug 371539] Only listens to IPv6
https://bugs.kde.org/show_bug.cgi?id=371539 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] New: AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13 and GLIBCXX_3.4.29 not found
https://bugs.kde.org/show_bug.cgi?id=478222 Bug ID: 478222 Summary: AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13 and GLIBCXX_3.4.29 not found Classification: Applications Product: digikam Version: 8.2.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: johannes.lists+bugs.kde@tannenhof-imshausen.de Target Milestone: --- SUMMARY I downloaded newest AppImage 8.2.0 and tried to start it, which fails. Earlier versions like 8.1 and 8.0 work like a charm. STEPS TO REPRODUCE 1. Download AppImage 8.2.0 on Ubuntu 20.04 2. Start it in terminal OBSERVED RESULT Following error messages appear in the terminal: digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libMagick++-7.Q16.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libdigikamdatabase.so.8.2.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libdigikamcore.so.8.2.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5ConfigCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5Service.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_dnn.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_imgproc.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_ml.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libexiv2.so.28) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/liblensfun.so.2) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libopencv_imgcodecs.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5ConfigWidgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5KIOCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libKF5WindowSystem.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKaKdmdm2/usr/lib/libde265.so) EXPECTED RESULT Digikam starts without complaining about missing libraries. SOFTWARE/OS VERSIONS Linux: Ubuntu 20.04.6 LTS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475357] Regression in Dolphin 23.08.1 - Expandable folders in Details view mode broken
https://bugs.kde.org/show_bug.cgi?id=475357 Johannes Schmidt changed: What|Removed |Added CC||johannes-schm...@dorsai.eu -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477531] KPhotoAlbum git master crashes when a new Category is added, deleted and then added again in Settings
https://bugs.kde.org/show_bug.cgi?id=477531 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/4 ||60b2c505abaa51efac0f77811ec ||61f627ee6e31 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Johannes Zarl-Zierl --- Git commit 460b2c505abaa51efac0f77811ec61f627ee6e31 by Johannes Zarl-Zierl. Committed on 28/11/2023 at 23:17. Pushed by johanneszarl into branch 'master'. Fix crash when deleting a category and doing a second category action. After deleting a category via the Settings::CategoryPage, the deleted category would remain in the list of categories to delete. If one then opened the category page again and chose "OK" or "Apply", KPhotoAlbum would try to remove the already removed category again, triggering an assertion. M +3-0DB/CategoryCollection.cpp M +3-6Settings/CategoryPage.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/460b2c505abaa51efac0f77811ec61f627ee6e31 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477532] KPhotoAlbum crashes when refreshing a Category view when the Category is deleted
https://bugs.kde.org/show_bug.cgi?id=477532 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/0 ||61acef783b3980d938aa6f4ba04 ||a81f89ac20ce Resolution|--- |FIXED --- Comment #1 from Johannes Zarl-Zierl --- Git commit 061acef783b3980d938aa6f4ba04a81f89ac20ce by Johannes Zarl-Zierl. Committed on 28/11/2023 at 23:11. Pushed by johanneszarl into branch 'master'. Fix crash when deleting a category while its category page is shown. When the category page was shown while its category page is shown, one could crash kphotoalbum by refreshing the view. New behavior: Return to the home page when a deleted category page is refreshed. Note: even nicer would be to automatically go to the home page without a manual refresh in this case. M +5-3Browser/BrowserWidget.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/061acef783b3980d938aa6f4ba04a81f89ac20ce -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477530] KPhotoAlbum crashes when new Category is added and immediately set as Category for Untagged Images in Settings
https://bugs.kde.org/show_bug.cgi?id=477530 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/6 ||7a8cdf455673bbcd9d9e54a5499 ||8cbb3a53853b Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- Git commit 67a8cdf455673bbcd9d9e54a54998cbb3a53853b by Johannes Zarl-Zierl. Committed on 28/11/2023 at 00:45. Pushed by johanneszarl into branch 'master'. Fix crash when renaming or adding a category and using it as untagged category When trying to select an unsaved category (either newly created or renamed) as the untagged category in the category settings page, instead of populating the tag dropdown list, kphotoalbum would crash. The new behavior is to disable the tag dropdown instead. M +1-0CHANGELOG.md M +9-5Settings/UntaggedGroupBox.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/67a8cdf455673bbcd9d9e54a54998cbb3a53853b -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477530] KPhotoAlbum crashes when new Category is added and immediately set as Category for Untagged Images in Settings
https://bugs.kde.org/show_bug.cgi?id=477530 Johannes Zarl-Zierl changed: What|Removed |Added Ever confirmed|0 |1 CC||johan...@zarl-zierl.at Status|REPORTED|CONFIRMED --- Comment #1 from Johannes Zarl-Zierl --- I can reproduce the crash. It can also be reproduced by renaming a category and then picking it as Category for untagged images. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477529] KPhotoAlbum crashes when Category for Untagged Images is set to "None Selected" in Settings
https://bugs.kde.org/show_bug.cgi?id=477529 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/f ||47882f098db868b4acfa0a2799d ||97faf882489b Resolution|--- |FIXED --- Comment #1 from Johannes Zarl-Zierl --- Git commit f47882f098db868b4acfa0a2799d97faf882489b by Johannes Zarl-Zierl. Committed on 27/11/2023 at 00:30. Pushed by johanneszarl into branch 'master'. Fix crash when clearing the untagged tag via settings M +1-0CHANGELOG.md M +5-1DB/ImageDB.cpp M +5-0DB/ImageDB.h https://invent.kde.org/graphics/kphotoalbum/-/commit/f47882f098db868b4acfa0a2799d97faf882489b -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477533] Error while reading database file when Category name starts with numbers
https://bugs.kde.org/show_bug.cgi?id=477533 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||johan...@zarl-zierl.at Ever confirmed|0 |1 --- Comment #1 from Johannes Zarl-Zierl --- The issue here lies with the "compressed" file format using the category name as an XML attribute: > > > That also means that one can create and use such a category in the "uncompressed" file format perfectly well and than convert the database to the "compressed" file format and totally break it. To fix this on a database level, we need to change the database file format and break compatibility. Alternatively, we could just prevent creating such a category - but that seems like a band-aid solution to me. Since we are breaking compatibility anyways, I'm contemplating decoupling between the category name and the XML attribute name to avoid the whole escaping/unescaping mechanism altogether. I'll need a few days to think about the which solution will be best to implement... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 468134] Add a quick and easy way to open an image in an external viewer/program
https://bugs.kde.org/show_bug.cgi?id=468134 Johannes Zarl-Zierl changed: What|Removed |Added Version|GIT master |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 468134] Add a quick and easy way to open an image in an external viewer/program
https://bugs.kde.org/show_bug.cgi?id=468134 Johannes Zarl-Zierl changed: What|Removed |Added Version|unspecified |GIT master -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477195] KPhotoAlbum git master crashes when an Event tag is dragged on another Event tag in the Events screen
https://bugs.kde.org/show_bug.cgi?id=477195 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/d ||691ee89ffbb604cd8ab7bef5b8c ||48fff50e Status|REPORTED|RESOLVED --- Comment #1 from Johannes Zarl-Zierl --- Git commit d691ee89ffbb604cd8ab7bef5b8c48fff50e by Johannes Zarl-Zierl. Committed on 18/11/2023 at 23:45. Pushed by johanneszarl into branch 'master'. Review and document DB::MemberMap. The MemberMap code had quite a few assertions that are better handled by ignoring invalid requests. The documentation was added and documents these edge-cases. One of these assertions prevented drag on the browser category page in a category that does not yet have any tag groups. M +5-2Browser/TreeCategoryModel.cpp M +1-0CHANGELOG.md M +82 -70 DB/MemberMap.cpp M +154 -3DB/MemberMap.h M +1-2DB/documentation.h https://invent.kde.org/graphics/kphotoalbum/-/commit/d691ee89ffbb604cd8ab7bef5b8c48fff50e -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476862] KPhotoAlbum git master crashes when range selected in Datebar extends out of main screen
https://bugs.kde.org/show_bug.cgi?id=476862 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #2 from Johannes Zarl-Zierl --- Great catch! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476862] KPhotoAlbum git master crashes when range selected in Datebar extends out of main screen
https://bugs.kde.org/show_bug.cgi?id=476862 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/a ||8ca10713a8f09be062f2776ab1e ||1e3dd162d129 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Johannes Zarl-Zierl --- Git commit a8ca10713a8f09be062f2776ab1e1e3dd162d129 by Johannes Zarl-Zierl. Committed on 12/11/2023 at 18:08. Pushed by johanneszarl into branch 'master'. Fix failing assertion when datebar selection is extended beyond valid region. M +1-0CHANGELOG.md M +1-1DB/XML/FileReader.cpp M +6-2DateBar/DateBarWidget.cpp M +1-1DateBar/DateBarWidget.h M +14 -4DateBar/MouseHandler.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/a8ca10713a8f09be062f2776ab1e1e3dd162d129 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 476838] New: Format DIN A4 is missing
https://bugs.kde.org/show_bug.cgi?id=476838 Bug ID: 476838 Summary: Format DIN A4 is missing Classification: Applications Product: Skanpage Version: 23.08.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: j...@gmx.de 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. Connect Fujitsu ScanSnap S1500 2. Start skanpage and try to set format DIN A4 3. DIN A4 is missing, although explicitly supported by scanner OBSERVED RESULT no predefined format DIN A4 EXPECTED RESULT DIN A4 (along with DIN A5 and many other formats, which are predefined) present in preconfigured formats SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476651] KPA crashes when sorting item in thumbnail view by date/time
https://bugs.kde.org/show_bug.cgi?id=476651 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #8 from Johannes Zarl-Zierl --- Thanks for the detailed report. For the record: The steps to reproduce this bug using the GUI only: 1. Open KPhotoAlbum 2. Select View | Show Newest First 3. Go To Thumbnail View 4. Select all images 5. Select View | Sort selected by Date & Time Apparently nobody ever tried sorting the images while the display order was newest first... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476651] KPA crashes when sorting item in thumbnail view by date/time
https://bugs.kde.org/show_bug.cgi?id=476651 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/e ||b3e2fe95ab48f984d79125e3656 ||2c5955ceae7c Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #7 from Johannes Zarl-Zierl --- Git commit eb3e2fe95ab48f984d79125e36562c5955ceae7c by Johannes Zarl-Zierl. Committed on 07/11/2023 at 23:29. Pushed by johanneszarl into branch 'master'. Fix crash when sorting selected images newest first If the display order is newest first, selecting all images and sorting the selected images resulted in a out of bounds iterator. M +2-1DB/ImageInfoList.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/eb3e2fe95ab48f984d79125e36562c5955ceae7c -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #13 from Johannes Zarl-Zierl --- (In reply to Andreas Schleth from comment #11) > I think "Folder" and "Media Type" should be sorted with the non-category > item at the end. Not necessarily in alphabetical order. > Then, "Tokens" could be considered a non-category item as well, as it is > always there without fail. Having them apart from the regular categories makes sense. I've implemented this now, more or less. To me, the specific ordering of Folder, Media Type, Tokens is not that important, as long as it's consistent (and everybody will have their own idea about the best ordering). > It might be sensible to sort the non-category items according to importance. > (I usually navigate on autopilot by screen position without reading the sub > titles.) > > The single most important by far is "show thumbnails" - that should always > be at the end to be easiest to find. > I often use "Folder", "Tokens" and "Search", rarely "Exif Info" and "Media > Type", almost never "untagged" and "Geo Position" - others may have > different preferences. The last sentence is the key takeaway. One can't find the "right" ordering for everyone, apart from "Show Thumbnails" being the most important one. I did try to have the ordering make some sense, though: 1. regular category things 2. special category things 3. strange behaving things 4. things that switch to thumbnail view In any case, sorting this differently from what it was (by chance) before upsets the muscle memory. So it makes sense to try to invest some time to do it well (and avoid having to change it again a year down the line). -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #12 from Johannes Zarl-Zierl --- Git commit e944761a8942382d199652772b3f6d2b1dd47fab by Johannes Zarl-Zierl. Committed on 06/11/2023 at 21:01. Pushed by johanneszarl into branch 'master'. Try to improve overview page sort order Old: 1. Categories 2. Geo Position, Exif Search, Regular Search (=items opening a special widget) 3. Untagged Images 4. Show Thumbnails New: 1. Regular Categories 2. Special Categories (Tokens, Media Type, Folder) 3. Geo Position, Exif Search, Regular Search (=items opening a special widget) 4. Untagged Images 5. Show Thumbnails M +15 -9Browser/OverviewPage.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/e944761a8942382d199652772b3f6d2b1dd47fab -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476561] KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window
https://bugs.kde.org/show_bug.cgi?id=476561 --- Comment #3 from Johannes Zarl-Zierl --- I'm not 100% sure that this does actually fix the bug in all instances, but it does inhibit the issue of the AnnotationDialog being closed when the Viewer->show context menu is activated. You can e.g. still trigger the closing of the annotation dialog by changing the visibility of a category - but this does not cause a crash. And since the stack trace is mostly inside QtWidgets, I don't know what is causing the crash exactly. I'm still debating whether changing the visibility of the Category in the viewer infobox actually needs to emit the signal that causes the annotation dialog to close. If I change this detail, I'll CC this bug... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476561] KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window
https://bugs.kde.org/show_bug.cgi?id=476561 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/0 ||8a2bf1cbd23d48e199f924bf32b ||e128c12bd98b Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- Git commit 08a2bf1cbd23d48e199f924bf32be128c12bd98b by Johannes Zarl-Zierl. Committed on 05/11/2023 at 22:57. Pushed by johanneszarl into branch 'master'. Don't emit Category::changed() when there's no change. Emitting the changed() signal caused the CategoryCollection::categoryCollectionChanged() signal when the Viewer context menu "show" was activated, causing the AnnotationDialog being closed if it was open at the time. M +17 -4DB/Category.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/08a2bf1cbd23d48e199f924bf32be128c12bd98b -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476561] KPhotoAlbum crashes when changes in Annotation window are not saved and then user right clicks "Show" in Viewer window
https://bugs.kde.org/show_bug.cgi?id=476561 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #10 from Johannes Zarl-Zierl --- Ok, I found the culprit: items on the overview page are sorted by their "row" property and not their name. I don't even know for sure where the row value comes from, TBH. I changed this now to use alphabetical sort order. Is this result stable for you as well? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #9 from Johannes Zarl-Zierl --- Git commit 152f0fd5a6063a61663a92754ff255345e3a8bab by Johannes Zarl-Zierl. Committed on 05/11/2023 at 21:35. Pushed by johanneszarl into branch 'master'. Use alphabetic sort order for categories on overview page Unit now, categories on the browser overview page would be sorted by their "row" value. To have a more intuitive order, change this to alphabetical sort order. M +6-9Browser/OverviewPage.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/152f0fd5a6063a61663a92754ff255345e3a8bab -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #8 from Johannes Zarl-Zierl --- (In reply to Andreas Schleth from comment #7) > I think the very last commit did not work out as intended (?): > As far as I understand (I may be wrong), the categories in the main window > should have been sorted in a consistent way: Categories first and then the > other items - preferably always in the same order Yes, that was the intention. > Notice the different positions of "Folder/Ordner" and "Tokens/Kürzel" in the > two screenshots of the same DB with different LANG settings. There's more going on here. "Darsteller" and "andere Personen" should be sorted entirely different in either locale. > Does this go back to the time when the default category names were > translated? Most other of my databases have the term "Tokens" instead of > "Kürzel" irrespective of LANG setting. I don't think so. There's nothing special anymore about those names... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476581] New: Cannot edit VPN settings via system settings application
https://bugs.kde.org/show_bug.cgi?id=476581 Bug ID: 476581 Summary: Cannot edit VPN settings via system settings application Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_networkmanagement Assignee: plasma-b...@kde.org Reporter: johann...@5d6.de CC: jgrul...@redhat.com Target Milestone: --- STEPS TO REPRODUCE 1. Purchase Mozilla VPN and export VPN configuration via mozwire as Wireguard format (another Wireguard file would presumably also work). 3. Go to KDE system settings -> Network -> Connections 4. Add new connection -> Import VPN connection -> select Wireguard file. 5. Try to edit the newly added connection in any way, e.g. by changing the name. OBSERVED RESULT The "Apply" button is grayed out and cannot be clicked. There is no confirmation dialog whether settings should be saved or discarded when switching to another connection. EXPECTED RESULT The settings can be saved by clicking the "Apply" button, making them permanent. When switching to another connection there is a dialog asking whether the settings should be saved or discarded. SOFTWARE/OS VERSIONS Linux: 6.5.5-1-MANJARO (64-bit) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION There is a workaround for this issue by going to /etc/NetworkManager/system-connections and editing the config files. The changes made there are then correctly applied and shown in the GUI. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 --- Comment #5 from Johannes Zarl-Zierl --- Git commit 7c4b288689dfcb4a1aaba556f8eea211eb0f1380 by Johannes Zarl-Zierl. Committed on 05/11/2023 at 00:16. Pushed by johanneszarl into branch 'master'. Fix sort order on overview page. Similar to bug #476504, with natural sort order, non-category items on the browser overview page, like "Show Thumbnails" and others, would be sorted alongside category items. These entries should be sorted after categories. Expanding on the ideal laid out in 7452e018361908b6f6b6146a8dd8de75461346ce, use a SortPriorityRole to sort these entries in a stable and (hopefully) intuitive way: 1. Categories 2. search, geo position and exiv info (sorted according to localized name) 3. Untagged images 4. "Show Thumbnails" M +7-2Browser/AbstractCategoryModel.cpp M +22 -5Browser/OverviewPage.cpp M +5-5Browser/TreeFilter.cpp M +1-2Browser/enums.h https://invent.kde.org/graphics/kphotoalbum/-/commit/7c4b288689dfcb4a1aaba556f8eea211eb0f1380 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 Johannes Zarl-Zierl changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Johannes Zarl-Zierl --- Thanks for checking! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/7 ||452e018361908b6f6b6146a8dd8 ||de75461346ce Status|CONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- Git commit 7452e018361908b6f6b6146a8dd8de75461346ce by Johannes Zarl-Zierl. Committed on 03/11/2023 at 21:53. Pushed by johanneszarl into branch 'master'. Fix sort order of "no other" and "none" This fixes a regression introduced by 44d16fef5aac0568b38db571e9cba2c7e46bba9e (natural sort order), causing "no other" or "none" and their localized versions to be sorted with the rest of the list items when natual sort order was active. M +13 -6Browser/AbstractCategoryModel.cpp M +8-0Browser/TreeFilter.cpp M +7-6Browser/enums.h https://invent.kde.org/graphics/kphotoalbum/-/commit/7452e018361908b6f6b6146a8dd8de75461346ce -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476504] "No other" pseudo name sorted wrong for language(s?) other than English
https://bugs.kde.org/show_bug.cgi?id=476504 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||johan...@zarl-zierl.at Ever confirmed|0 |1 --- Comment #1 from Johannes Zarl-Zierl --- Hi Andreas, Thanks for filing the bug report! I can confirm that this issue is indeed caused by the newly introduced natural sort order feature... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469889] plasmashell leaks inotify file descriptor
https://bugs.kde.org/show_bug.cgi?id=469889 Johannes Truschnigg changed: What|Removed |Added CC||johannes+kdebugs@truschnigg ||.info --- Comment #2 from Johannes Truschnigg --- I can confirm this bug on both Debian 12 and Arch Linux, where it looks like the following: $ ls -l /proc/$$/fd/ total 0 lrwx-- 1 colo colo 64 1. Nov 13:37 0 -> /dev/pts/3 lrwx-- 1 colo colo 64 1. Nov 13:37 1 -> /dev/pts/3 lrwx-- 1 colo colo 64 1. Nov 13:37 2 -> /dev/pts/3 lr-x-- 1 colo colo 64 1. Nov 13:37 24 -> anon_inode:inotify lrwx-- 1 colo colo 64 1. Nov 13:37 255 -> /dev/pts/3 $ pstree -s -p $$ systemd(1)───systemd(616)───plasmashell(754)───konsole(60566)───bash(60581)───pstree(61213) $ ls -l /proc/60566/fd/24 lr-x-- 1 colo colo 64 1. Nov 14:02 /proc/60566/fd/24 -> anon_inode:inotify $ ls -l /proc/754/fd/24 lr-x-- 1 colo colo 64 1. Nov 14:02 /proc/754/fd/24 -> anon_inode:inotify $ sudo ls -l /proc/616/fd/24 lrwx-- 1 colo colo 64 1. Nov 14:03 /proc/616/fd/24 -> 'socket:[18811]' I stumbled over this because the fd broke another project's test suite I was running in my Konsole-spawned shell. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472520] Date for Videos should be sourced from Video metadata instead of filesystem file modify date
https://bugs.kde.org/show_bug.cgi?id=472520 --- Comment #1 from Johannes Zarl-Zierl --- Just some notes for a potential fix: A good location to read creation_date would be in VideoLengthExtractor (although that needs some change at least in its name then). The following command can be used to read the creation_date in addition to the video length: `ffprobe -v 0 -show_entries format_tags=creation_time:format=duration -of default=noprint_wrappers=1:nokey=0` One thing that needs working out if we use ffprobe, though: some video files have local time, some have UTC. I.e. some (most?) (phone-)cameras store the time as UTC, but no offset. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 476131] KPhotoAlbum crashes after using Toggle full-screen preview, deleting image, resizing annotations window and then using Toggle full-screen preview again
https://bugs.kde.org/show_bug.cgi?id=476131 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/b ||400415a37e2d0285c277f678876 ||c9202f2e14da --- Comment #1 from Johannes Zarl-Zierl --- Git commit b400415a37e2d0285c277f678876c9202f2e14da by Johannes Zarl-Zierl. Committed on 30/10/2023 at 00:18. Pushed by johanneszarl into branch 'master'. Fix crash in ViewerWidget In addition to fixing bug #476131, this commit aims to prevent similar bugs in all of the ViewerWidget methods. M +3-3Viewer/ImageDisplay.cpp M +2-2Viewer/ImageDisplay.h M +64 -17 Viewer/ViewerWidget.cpp M +11 -0Viewer/ViewerWidget.h https://invent.kde.org/graphics/kphotoalbum/-/commit/b400415a37e2d0285c277f678876c9202f2e14da -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475976] Path of files for KPA->openwith->Gimp
https://bugs.kde.org/show_bug.cgi?id=475976 --- Comment #13 from Johannes Zarl-Zierl --- It's good that we have a workaround, but I agree with Andreas - we should at least try to get some insight from the KIO devs on this. Maybe they can fix this, maybe they can tell us how to fix this. In the worst case we know we can't fix it because it's a downstream problem... Thanks everybody for gathering insights on this issue! If nobody is quicker than me I'll ask for help on #kde-devel some time in the upcoming week... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475976] Path of files for KPA->openwith->Gimp
https://bugs.kde.org/show_bug.cgi?id=475976 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #6 from Johannes Zarl-Zierl --- I can only talk about the KPhotoAlbum side of things, but KPA creates a list of file URLs from the absolute file name(s) and hands this over to the KIO::ApplicationLauncherJob. I don't see how gwenview or dolphin would do something different here, but looking at the source of KIO::ApplicationLauncherJob I also don't see how the URL is changed by it. My best guess is that somehow, xdg-desktop-portal-kde is involved because Gimp is a GTK application and there, the URL goes through kioUrlFromSandboxPath(), which calls into KIO::Fuse to convert the URL: https://lxr.kde.org/source/plasma/xdg-desktop-portal-kde/src/filechooser.cpp#0457 As to why the same file is handled differently in Gwenview and dolphin, I'm at a loss. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475585] KPhotoAlbum crashes on clicking "Copy Image to ..." in Full screen preview in Annotations window
https://bugs.kde.org/show_bug.cgi?id=475585 Johannes Zarl-Zierl changed: What|Removed |Added Status|VERIFIED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/kphotoalbum/-/commit/2 |hics/kphotoalbum/-/commit/c |516c6e6ba68fba2ba92d758124c |6c7df0d8cdb79a9e2ea49f88c1d |726447bb6126|181beabb6bae Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Johannes Zarl-Zierl --- Git commit c6c7df0d8cdb79a9e2ea49f88c1d181beabb6bae by Johannes Zarl-Zierl. Committed on 14/10/2023 at 23:33. Pushed by johanneszarl into branch 'master'. Restrict set of context menu actions available in annotation dialog's fullscreen preview This also removes the copy/link actions that caused the crash in bug #475585, which should never have been available at this place in the program. M +1-1AnnotationDialog/Dialog.cpp M +3-0CHANGELOG.md M +5-4MainWindow/Window.cpp M +84 -45 Viewer/ViewerWidget.cpp M +6-3Viewer/ViewerWidget.h https://invent.kde.org/graphics/kphotoalbum/-/commit/c6c7df0d8cdb79a9e2ea49f88c1d181beabb6bae -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475044] Plasma crashes while switching to an alternative Widget while the settings window from the Event Calendar is open.
https://bugs.kde.org/show_bug.cgi?id=475044 --- Comment #6 from Johannes Fleisch --- Hope you feel better now. Thanks for your work and kindness! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475387] KPhotoAlbum crashes after Toggle full-screen preview in Annotations window for an image that is already deleted
https://bugs.kde.org/show_bug.cgi?id=475387 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #5 from Johannes Zarl-Zierl --- Thanks, good catch! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475388] KPhotoAlbum crashes after Delete Image in Annotations window for an image that is already deleted
https://bugs.kde.org/show_bug.cgi?id=475388 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #4 from Johannes Zarl-Zierl --- Thanks! I believe the bug is now fixed for good. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475387] KPhotoAlbum crashes after Toggle full-screen preview in Annotations window for an image that is already deleted
https://bugs.kde.org/show_bug.cgi?id=475387 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/kphotoalbum/-/commit/c |hics/kphotoalbum/-/commit/3 |62626f6c4a5f42fc2518c75aae4 |786a06ee0fc8c9edbf92bd3e4a1 |665e901f9c33|2c752f5dbec1 --- Comment #4 from Johannes Zarl-Zierl --- Git commit 3786a06ee0fc8c9edbf92bd3e4a12c752f5dbec1 by Johannes Zarl-Zierl. Committed on 13/10/2023 at 09:57. Pushed by johanneszarl into branch 'master'. Fix crash when annotated image is deleted while full screen preview is active. If the last image in the annotation dialog was deleted while the dialog was showing the fullscreen preview, instead of closing the dialog as expected, only the fullscreen preview was toggled. This lead to the annotation dialog still showing the last image, even though it should have been closed - thus triggering the same behaviour as described in bug #475387. M +3-2AnnotationDialog/Dialog.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/3786a06ee0fc8c9edbf92bd3e4a12c752f5dbec1 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475388] KPhotoAlbum crashes after Delete Image in Annotations window for an image that is already deleted
https://bugs.kde.org/show_bug.cgi?id=475388 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/kphotoalbum/-/commit/c |hics/kphotoalbum/-/commit/2 |62626f6c4a5f42fc2518c75aae4 |a138f3ac613d945516e9a885efe |665e901f9c33|ab927ee28d68 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Johannes Zarl-Zierl --- Git commit 2a138f3ac613d945516e9a885efeab927ee28d68 by Johannes Zarl-Zierl. Committed on 13/10/2023 at 09:09. Pushed by johanneszarl into branch 'master'. Fix regression when deleting images The introduction of AnnotationDialog::Dialog::slotDiscardImages() reimplemented the things done in Dialog::slotDeleteImage(), causing duplicated removal of images from the ImagePreviewWidget and annotation Dialog. This caused a crash when deleting an image via the delete button of the annotation dialog. Fortunately, it turns out that the slotDiscardImages function does everything slotDeleteImage() does, which means that the older code could simply be removed. Note: This patch removes the action "annotationdialog-delete-image", which called Dialog::slotDeleteImage directly, and had a conflicting default shortcut Ctrl+Delete (conflicting with Viewer -> delete image). I believe the original intention for that action was to call ImagePreviewWidget::slotDeleteImage(). Since the action was clearly not in a working state, I thought it better to remove it entirely. M +0-33 AnnotationDialog/Dialog.cpp M +0-1AnnotationDialog/Dialog.h M +1-10 AnnotationDialog/ImagePreviewWidget.cpp M +1-2AnnotationDialog/ImagePreviewWidget.h https://invent.kde.org/graphics/kphotoalbum/-/commit/2a138f3ac613d945516e9a885efeab927ee28d68 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475529] Possible database corruption by running rescans in parallel
https://bugs.kde.org/show_bug.cgi?id=475529 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/5 ||667e29083004009cf60510c62ea ||690f1d234bc3 --- Comment #2 from Johannes Zarl-Zierl --- Git commit 5667e29083004009cf60510c62ea690f1d234bc3 by Johannes Zarl-Zierl. Committed on 12/10/2023 at 23:42. Pushed by johanneszarl into branch 'master'. Prevent scanning for new images in parallel Add a mutex to prevent the user from starting a scan for new images while another scan is still running. This fixes a failed assertion if assertions are enabled, and potential database corruption if assertions are not enabled. M +1-0CHANGELOG.md M +24 -3DB/NewImageFinder.cpp M +13 -4DB/NewImageFinder.h https://invent.kde.org/graphics/kphotoalbum/-/commit/5667e29083004009cf60510c62ea690f1d234bc3 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 475529] Possible database corruption by running rescans in parallel
https://bugs.kde.org/show_bug.cgi?id=475529 Johannes Zarl-Zierl changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
