[frameworks-kguiaddons] [Bug 475954] New: Extended Color Dialog with palette support
https://bugs.kde.org/show_bug.cgi?id=475954 Bug ID: 475954 Summary: Extended Color Dialog with palette support Classification: Frameworks and Libraries Product: frameworks-kguiaddons Version: 5.27.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- This is my original intention for https://bugs.kde.org/show_bug.cgi?id=475685 Several parts of the KDE ecosystem have the concept of color themes: Kate's syntax highlighting, application colors, etc. And yet, when trying to pick a color with the color Dialog, the colors of those themes (their palettes) are not easily available. As discussed on the above bug, this would include sub-classing Qt's Color Dialog and modifying apps with calls to the new class. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475932] New: Maximize split view
https://bugs.kde.org/show_bug.cgi?id=475932 Bug ID: 475932 Summary: Maximize split view Classification: Applications Product: kate Version: 23.08.1 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- I use Split View a lot, mostly 2 views side by side, 50/50, but sometimes differently. Sometimes I'm editing a file with lines that are to long for the view. I would like an action that would allow me to maximize the current view and go back to the original split view, whatever it was. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475685] Dialog Parent effect renders Color picker dialog useless if the color you want to pick is in the suddenly-darkened window
https://bugs.kde.org/show_bug.cgi?id=475685 --- Comment #4 from Marcos Dione --- (In reply to Nate Graham from comment #3) > It would in all practicality require KDE to override the default Qt color > picker dialog with our own, and then implement this feature in it--whatever > that feature would look like. AFAIK, KDE already does that with other dialogs, like the file open one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475685] Dialog Parent effect renders Color picker dialog useless if the color you want to pick is in the suddenly-darkened window
https://bugs.kde.org/show_bug.cgi?id=475685 --- Comment #2 from Marcos Dione --- Hi Nate, thanks for looking into this, but in fact, my request was more in the lines of being able to feed the color dialog a palette from which to chose colors. Should I open another bug for that? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 475685] Palettes for select color dialog
https://bugs.kde.org/show_bug.cgi?id=475685 --- Comment #1 from Marcos Dione --- Created attachment 162347 --> https://bugs.kde.org/attachment.cgi?id=162347=edit Color Picker tool's behaviour after Select Color modal dialog is opened. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kguiaddons] [Bug 475685] New: Palettes for select color dialog
https://bugs.kde.org/show_bug.cgi?id=475685 Bug ID: 475685 Summary: Palettes for select color dialog Classification: Frameworks and Libraries Product: frameworks-kguiaddons Version: 5.92.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- Several parts of the KDE ecosystem have the concept of color themes: Kate's syntax highlighting, application colors, etc. And yet, when trying to pick a color with the color Dialog, the colors of those themes (their palettes) are not easily available. Even more, when the dialog is modal, the rest of the screen is darkened, which renders the pick color tool useless. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 472210] New: Open dialog could offer option to create empty file when the filename is not found
https://bugs.kde.org/show_bug.cgi?id=472210 Bug ID: 472210 Summary: Open dialog could offer option to create empty file when the filename is not found Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.107.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY The Open dialog shows this error when the filename is not present in the directory: The file '' could not be found. So far so good. My suggestion is that the error dialog could suggest creating an empty file with that name. I would find it more useful than to have to close that error dialog, close the open dialog, and then tell the app to create a new file, and at some point having to enter the filename when saving for the first name. Of course this probably means that the applications will have to support a new API for creating empty files (whatever that means for them) with the filename returned by the dialog. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471335] Tag a detected face but not use it for training
https://bugs.kde.org/show_bug.cgi?id=471335 --- Comment #1 from Marcos Dione --- (In reply to Marcos Dione from comment #0) > The face detection algorithm is very good, to the point where it detects > faces out of focus, in really bad angles, etc. Other reasons for 'bad' photos: * Partially occluded * Bad lightning -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471335] New: Tag a detected face but not use it for training
https://bugs.kde.org/show_bug.cgi?id=471335 Bug ID: 471335 Summary: Tag a detected face but not use it for training Classification: Applications Product: digikam Version: 7.9.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- The face detection algorithm is very good, to the point where it detects faces out of focus, in really bad angles, etc. While using the People view to tag faces, we can tag these 'bad' faces. It would be nice if we could tell digikam not to use them for training the face recognition tool. I have the impression that when doing so, the algo starts confusing all the out of 'bad' faces, so the algo's hit rate plummets. Maybe related to https://bugs.kde.org/show_bug.cgi?id=425263 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 466770] New: Scan QR codes
https://bugs.kde.org/show_bug.cgi?id=466770 Bug ID: 466770 Summary: Scan QR codes Classification: Plasma Product: plasma-nm Version: 5.27.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- plasma-nm has an option to share wifi connections via a QR code that f.i. smartphone know how to use. In one of my travels abroad the hotel only had the password in a QR code you scanned in the lobby, so I could connect my phone but not my KDE laptop with builtin camera. In the end I figured out that if I used a generic QR code scanner app for my phone I could show the password and use it on the laptop. Since my computer has a camera, maybe it would be useful (although, I admit, probably a little bit awkward to use) to be able to scan the same QR codes from plasma-nm. The awkwardness would be drastically reduced if scanning from a smartphone. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 418502] better handling of external monitor brightness.
https://bugs.kde.org/show_bug.cgi?id=418502 --- Comment #4 from Marcos Dione --- I just noticed that I can set the external monitor brightness with ddccontrol and redshift does not seem to impose its own wishes. In fact, seemingly nor on the notebook's monitor, so I guess this is fixed now? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414325] 'Comic book' order of split panels
https://bugs.kde.org/show_bug.cgi?id=414325 Marcos Dione changed: What|Removed |Added Summary|'Comic book' order of spit |'Comic book' order of split |panels |panels -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461338] Kwin hangs when pressing Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=461338 --- Comment #5 from Marcos Dione --- (gdb) bt #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x555e85127e24) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x555e85127e24) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x555e85127e24, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f97d368f338 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555e85127dd0, cond=0x555e85127df8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x555e85127df8, mutex=0x555e85127dd0) at ./nptl/pthread_cond_wait.c:627 #5 0x7f97d48d2b1b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f97d2c176e8 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f97d2c84100 in QQuickWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f97d3f6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f97d4abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f97d4f31343 in QPlatformWindow::windowEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f97d3f7324d in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f97d4abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f97d4b13e71 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f97d4b12390 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f97ce2fab62 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #16 0x7f97d4ab97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f97d4ac1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x555e82ef73a1 in ?? () #19 0x7f97d3623510 in __libc_start_call_main (main=main@entry=0x555e82ef6f70, argc=argc@entry=2, argv=argv@entry=0x7fff309e4fc8) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x7f97d36235c9 in __libc_start_main_impl (main=0x555e82ef6f70, argc=2, argv=0x7fff309e4fc8, init=, fini=, rtld_fini=, stack_end=0x7fff309e4fb8) at ../csu/libc-start.c:381 #21 0x555e82ef8755 in ?? () I got this backtrace, but unluckily there seem not to be any debug symbols for qtquick in Debian/Ubuntu? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461338] Kwin hangs when pressing Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=461338 --- Comment #4 from Marcos Dione --- Slightly more info: mdione@nimbus:~$ ps faux | grep kwin mdione 1217293 0.0 0.0 11356 3892 tty2 S+ 14:50 0:00 \_ screen -dR kwin mdione58 0.0 0.0 12172 2872 ?Ss Jan25 0:00 SCREEN -dR kwin mdione 1077754 0.3 0.5 2120404 185308 pts/15 Sl+ 10:03 1:02 | \_ kwin --replace mdione 1217448 0.0 0.0 8924 2276 pts/19 S+ 14:51 0:00 \_ grep --color=auto kwin mdione@nimbus:~$ sudo strace -p 1077754 strace: Process 1077754 attached futex(0x7fa6c400f7d0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) It was stuck in that futex() call, the ERESTARTSYS is because I C-z'ed it. Maybe I should attach gdb instead? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461338] Kwin hangs when pressing Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=461338 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #3 from Marcos Dione --- I'm not sure this is the same bug, but the trigger is the same: switching between apps with Alt-TAB. Version info: mdione@nimbus:~/src/projects$ dpkg -l | grep kwin ii kwin-addons:amd644:5.25.5-0ubuntu1 amd64additional desktop and window switchers for KWin ii kwin-common 4:5.25.5-0ubuntu2 amd64KDE window manager, common files ii kwin-data4:5.25.5-0ubuntu2 all KDE window manager data files ii kwin-decoration-oxygen:amd64 4:5.25.5-0ubuntu1 amd64KWin decoration for the Oxygen desktop theme ii kwin-style-breeze4:5.25.5-0ubuntu1 amd64KWin Breeze Style ii kwin-wayland 4:5.25.5-0ubuntu2 amd64KDE window manager, wayland version, PREVIEW release ii kwin-wayland-backend-drm 4:5.25.5-0ubuntu2 amd64KDE window manager drm plugin ii kwin-x11 4:5.25.5-0ubuntu2 amd64KDE window manager, X11 version ii libkwineffects13 4:5.25.5-0ubuntu2 amd64KDE window manager effects library ii libkwinglutils13 4:5.25.5-0ubuntu2 amd64KDE window manager gl utils library ii libkwinxrenderutils134:5.25.5-0ubuntu2 amd64KDE window manager render utils library ii qml-module-org-kde-kwindowsystem:amd64 5.98.0-0ubuntu1 amd64provides integration of QML and KDE frameworks - kwindowsystem ii libqt5core5a:amd64 5.15.6+dfsg-1 amd64Qt 5 core module et al. I have to be honest, I never waited more than a few tens of seconds (I'm usually working) before killing kwin and running it again from a virtual console. if I run it like: mdione@nimbus:~$ DISPLAY=:0 kwin --replace 2>&1 and using a tool to prepend output lines with a timestamp, I can see the following lines being written around the time the freeze occurs: 2023-01-26T09:54:52.285623: kwin_core: XCB error: 3 (BadWindow), sequence: 65393, resource id: 31460269, major code: 129 (SHAPE), minor code: 6 (Input) 2023-01-26T09:54:52.285734: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65394, resource id: 31460269, major code: 2 (ChangeWindowAttributes), minor code: 0 2023-01-26T09:54:58.937467: kwin_core: XCB error: 3 (BadWindow), sequence: 456, resource id: 31460284, major code: 129 (SHAPE), minor code: 6 (Input) 2023-01-26T09:54:58.937589: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 457, resource id: 31460284, major code: 2 (ChangeWindowAttributes), minor code: 0 2023-01-26T09:55:00.973904: kwin_core: XCB error: 3 (BadWindow), sequence: 831, resource id: 31460292, major code: 129 (SHAPE), minor code: 6 (Input) 2023-01-26T09:55:00.974015: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 832, resource id: 31460292, major code: 2 (ChangeWindowAttributes), minor code: 0 2023-01-26T09:55:07.445426: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1292, resource id: 119539066, major code: 18 (ChangeProperty), minor code: 0 2023-01-26T09:55:07.484790: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1296, resource id: 102760742, major code: 18 (ChangeProperty), minor code: 0 2023-01-26T09:55:17.008395: kwin_core: XCB error: 3 (BadWindow), sequence: 2460, resource id: 31460309, major code: 129 (SHAPE), minor code: 6 (Input) 2023-01-26T09:55:17.008541: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2461, resource id: 31460309, major code: 2 (ChangeWindowAttributes), minor code: 0 2023-01-26T09:59:30.504059: kwin_core: XCB error: 3 (BadWindow), sequence: 5752, resource id: 31460333, major code: 129 (SHAPE), minor code: 6 (Input) 2023-01-26T09:59:30.504214: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5753, resource id: 31460333, major code: 2 (ChangeWindowAttributes), minor code: 0 2023-01-26T10:03:00.764531: kwin_core: XCB error: 3 (BadWindow), sequence: 7072, resource id: 31460405, major code: 129 (SHAPE), minor code: 6 (Input)
[kate] [Bug 463106] Some search highlights are missed
https://bugs.kde.org/show_bug.cgi?id=463106 Marcos Dione changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Marcos Dione --- I have the impression the bug was quite non reproducible, as I haven't seen it again. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463106] Some search highlights are missed
https://bugs.kde.org/show_bug.cgi?id=463106 --- Comment #1 from Marcos Dione --- Created attachment 154619 --> https://bugs.kde.org/attachment.cgi?id=154619=edit previous match not highlighted -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463106] New: Some search highlights are missed
https://bugs.kde.org/show_bug.cgi?id=463106 Bug ID: 463106 Summary: Some search highlights are missed Classification: Applications Product: kate Version: 22.08.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- Created attachment 154618 --> https://bugs.kde.org/attachment.cgi?id=154618=edit last line's matches not highlighted I just noticed that when I'm searching, not all matches are highlighted. In this case I'm searching for ':' and: * matches in the last line in the view are not highlighted, unless I manually scroll the view (maybe some pixel misalignment) * sometimes when jumping to the next match, the last match is de-highlighted See attached sshots. -- You are receiving this mail because: You are watching all bug changes.
[kbackup] [Bug 460146] New: Compute and show directory sizes
https://bugs.kde.org/show_bug.cgi?id=460146 Bug ID: 460146 Summary: Compute and show directory sizes Classification: Applications Product: kbackup Version: 21.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kol...@aon.at Reporter: mdi...@grulic.org.ar Target Milestone: --- Currently directory sizes are shown as on disk usage (usually 4KiB). I would like to see how much data is in that directory as a whole, to both size my destination and to find big files I might not want to backup. The display could be for fully selected/deselected directories and for partially selected directories. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332208] Crop with Ratio setting is bad implemented
https://bugs.kde.org/show_bug.cgi?id=332208 --- Comment #10 from Marcos Dione --- Looks good! Thanks for your time :) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412898] marble's coord grig plugin not always shows labels.
https://bugs.kde.org/show_bug.cgi?id=412898 --- Comment #2 from Marcos Dione --- I see that my version hasn't changed in 3 years. Maybe Debian is seriously lagging behind here? -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412898] marble's coord grig plugin not always shows labels.
https://bugs.kde.org/show_bug.cgi?id=412898 --- Comment #1 from Marcos Dione --- Created attachment 147419 --> https://bugs.kde.org/attachment.cgi?id=147419=edit screenshot showing the bug. This is a view of north Norway/Sweden where you can see several grid lines shown and *no label at all*. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439490] Ambiguous Shortcuts -- There are two actions (Open Command Bar, Add Images ...) that want to use the same shortcut (Ctrl+Alt+I). This is most probably a bug.
https://bugs.kde.org/show_bug.cgi?id=439490 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #4 from Marcos Dione --- Weird, I just came to report this same thing and the initial search "digikam two actions one shortcut" returned nothing relevant https://bugs.kde.org/buglist.cgi?quicksearch=digikam%20two%20actions%20one%20shortcut_id=1977148, but once I started writing the report, the interface correctly suggested this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447557] Night mode (not dark mode) à la stellarium
https://bugs.kde.org/show_bug.cgi?id=447557 --- Comment #1 from Marcos Dione --- I guess what I want is a desktop effect than can do it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447557] New: Night mode (not dark mode) à la stellarium
https://bugs.kde.org/show_bug.cgi?id=447557 Bug ID: 447557 Summary: Night mode (not dark mode) à la stellarium Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- I would like to have a plugin? feature? that would turn the while screen in monochromatic red like Stellarium does for night mode: https://lcom.static.linuxfound.org/images/stories/figure-3-stellarium.png The idea is that red light does not interfere so much with night vision, which is good for looking at starry nights (specially when using the computer to drive nice time lapses or long exposures :) This is NOT dark mode (https://store.kde.org/p/1013059). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 418502] better handling of external monitor brightness.
https://bugs.kde.org/show_bug.cgi?id=418502 --- Comment #3 from Marcos Dione --- I have to note that redshift is able to do it. I'm currently running redshift -v -b 1:.65 -l 43.5:7.1 and it's handling both monitors just fine. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 344237] Export geo: URI
https://bugs.kde.org/show_bug.cgi?id=344237 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #20 from Marcos Dione --- Can we vote for bugs? -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 442977] Tag changes with the tag editor are not reflected in the playlist
https://bugs.kde.org/show_bug.cgi?id=442977 --- Comment #1 from Marcos Dione --- Created attachment 141921 --> https://bugs.kde.org/attachment.cgi?id=141921=edit screenshot showing the bug. Song has been edited an Saved. Track and year were changed. The playlist does not reflect this. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 442977] New: Tag changes with the tag editor are not reflected in the playlist
https://bugs.kde.org/show_bug.cgi?id=442977 Bug ID: 442977 Summary: Tag changes with the tag editor are not reflected in the playlist Product: juk Version: 21.08.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: whee...@kde.org Reporter: mdi...@grulic.org.ar CC: mp...@kde.org Target Milestone: --- If I edit one or more tags with the tag editor and save the changes, they're reflected in the tag editor but not in the playlist. * Toggle on the tag editor (from the view menu) * Select one song from the playlist * Edit one tag, say year. * Select another song, a confirmation dialog pops up, asking whether to save the changes. * Save the changes. The change is not reflected in the playlist. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 442611] Free hand orientation
https://bugs.kde.org/show_bug.cgi?id=442611 --- Comment #2 from Marcos Dione --- Yes, kind of like that, but for the main view. Either that, or a way to add more eyepieces, extra points if it can be expressed in terms of sensor + lens. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 442611] New: Free hand orientation
https://bugs.kde.org/show_bug.cgi?id=442611 Bug ID: 442611 Summary: Free hand orientation Product: kstars Version: 3.4.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: mdi...@grulic.org.ar Target Milestone: --- Sometimes I take star pictures with a ball head tripod and a DSLR camera. Some of those times I want to use kstars to see what objects are within. But kstars has only two 'browsing' modes: horizontal and equatorial. Both only allow movement along lines on a sphere, but not rotation. The ball head provides an extra axe which I can't reproduce in kstars, so I can't really align with the photo. I'm not even asking about adding a rectangle that simulates the sensor + lens setup, just be able to rotate the image around the axis that would go through the center of the image. Of course, a first implementation could start with just a couple of shortcuts, maybe a couple of buttons, and a later implementation could include mouse control. OTOH, I just noticed my version is somewhat old, so I don't know if this has been implemented. I would guess not, since I can't find another wish for this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Marcos Dione changed: What|Removed |Added CC||mdi...@grulic.org.ar --- Comment #8 from Marcos Dione --- workaround so far: * deactivate night color. * run the following $ redshift -v -b 1:.75 -l LAT:LON -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 418502] better handling of external monitor brightness.
https://bugs.kde.org/show_bug.cgi?id=418502 --- Comment #2 from Marcos Dione --- > but the color temperature is totally off (too much blue...) I think what happens here is that redshift gets disabled. > that KCM_Nightcolor doesn't change the screen brightness yet AFAIK, but the > color tone Then this becomes a dupe of #413165? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440360] bash's syntax highlighting (SHL) gets confused with variable indirection in array definition
https://bugs.kde.org/show_bug.cgi?id=440360 --- Comment #1 from Marcos Dione --- Created attachment 140374 --> https://bugs.kde.org/attachment.cgi?id=140374=edit 'right' SHL (but without the ! that triggers the bug) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440360] New: bash's syntax highlighting (SHL) gets confused with variable indirection in array definition
https://bugs.kde.org/show_bug.cgi?id=440360
Bug ID: 440360
Summary: bash's syntax highlighting (SHL) gets confused with
variable indirection in array definition
Product: kate
Version: 20.12.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: part
Assignee: kwrite-bugs-n...@kde.org
Reporter: mdi...@grulic.org.ar
Target Milestone: ---
Created attachment 140373
--> https://bugs.kde.org/attachment.cgi?id=140373=edit
broken SHL
SUMMARY
Any code after:
foo=(${!6})
or:
foo=("${!6}")
or maybe other variations, has it SHL confused. Full example in the sshots:
function import_keytool_certificate_to_keystore() {
local x_keytool_cmd="${1?}"
local x_keystore_file="${2?}"
local x_cert_name_prompt="${3?}"
local x_cert_signature="${4?}"
local x_multiple_cert="${5?}"
local x_error_messages=("${6}")
local x_cert_alias_default="${7}"
local x_status=0
while [ true ]; do
local x_ca_certfile
get_user_input x_ca_certfile "$x_cert_name_prompt" ""
if [ "x${x_ca_certfile}" = "x" ]; then
log_message "${x_error_messages[0]}" "$ERROR_LEVEL" "1" "1"
x_status=8
break
fi
ALSO: no SHL component in the BTS?
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 438983] Double click on split view's splitter should revert to 50/50
https://bugs.kde.org/show_bug.cgi?id=438983 --- Comment #3 from Marcos Dione --- Thanks for 'fixing' it so quick! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #11 from Marcos Dione --- I just tried on a big folder full of GeoTiffs and it worked... except that it was OOM'ed because it ate the whole memory :) But that's something for another ticket. In my opinion you can close this one. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438983] New: Double click on split view's splitter should revert to 50/50
https://bugs.kde.org/show_bug.cgi?id=438983 Bug ID: 438983 Summary: Double click on split view's splitter should revert to 50/50 Product: kate Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- SUMMARY When we split a view, both children get 50% of the space. If we move the splitter handle, we can change that. It would be nice that, if we double click on the splitter handle, the split would go back to 50/50. ADDITIONAL INFORMATION Maybe this could be pushed down the stack, but that probably need that the developer provides a preferred or default size for the split. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430049] session memory leak
https://bugs.kde.org/show_bug.cgi?id=430049 --- Comment #2 from Marcos Dione --- In fact no, I deleted the session and created a new one. So I think we can close this one. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 437378] New: Add lossless crop support
https://bugs.kde.org/show_bug.cgi?id=437378 Bug ID: 437378 Summary: Add lossless crop support Product: gwenview Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- jpegtran has a "-crop" flag which performs lossless cropping of jpeg images as long as the crop is to a multiple of what the manpage calls the "iMCU boundary", usually an 8x8 or 16x16 block of pixels. See https://github.com/jepler/cropgui for more details and https://bugs.kde.org/show_bug.cgi?id=204135 for how this was inplemented in digikam. What I most like gwenview's crop tool, which I have incorporated into my workflow, is that you can enter the crop limit values by hand. It would be nice if it had support for this kind of cropping. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 432797] Support self extracting Linux files.
https://bugs.kde.org/show_bug.cgi?id=432797 --- Comment #4 from Marcos Dione --- At work we use the same principle, but by hand (go figure). The gist of it is: a shell script that suddenly has data that looks like a compressed file. Of course detecting the 'shell scriptness' should try to match the usual she-bang lines, and it should try to find a compressed file header by reading each byte and try. I'm not sure if ark's current arch allows such a thing. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 432797] Support self extracting Linux files.
https://bugs.kde.org/show_bug.cgi?id=432797 --- Comment #3 from Marcos Dione --- Created attachment 135661 --> https://bugs.kde.org/attachment.cgi?id=135661=edit bar.bin as generated in the example -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 432797] Support self extracting Linux files.
https://bugs.kde.org/show_bug.cgi?id=432797
--- Comment #2 from Marcos Dione ---
mdione@diablo:~/tmp/foo$ mkdir bar
mdione@diablo:~/tmp/foo$ touch bar/{a,b,c}
mdione@diablo:~/tmp/foo$ sudo apt install makeself
mdione@diablo:~/tmp/foo$ echo '#! /bin/bash
echo "installed!"' > bar/install.sh
mdione@diablo:~/tmp/foo$ chmod 755 bar/install.sh
mdione@diablo:~/tmp/foo$ makeself bar bar.bin 'bar for foos' ./install.sh
Header is 666 lines long
About to compress 8 KB of data...
Adding files to archive named "bar.bin"...
./
./install.sh
./c
./a
./b
./a
./b
./c
./install.sh
CRC: 2648421794
MD5: fe39420c250a13e5efd2e708d7494a78
Self-extractable archive "bar.bin" successfully created.
mdione@diablo:~/tmp/foo$ ls -l
drwxr-xr-x 2 mdione mdione 4096 feb 13 19:05 bar
-rwxr-xr-x 1 mdione mdione 17023 feb 13 19:05 bar.bin
mdione@diablo:~/tmp/foo$ ./bar.bin
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing bar for foos 100%
installed!
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 432797] New: Support self extracting Linux files.
https://bugs.kde.org/show_bug.cgi?id=432797 Bug ID: 432797 Summary: Support self extracting Linux files. Product: ark Version: 20.08.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: mdi...@grulic.org.ar CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY Self extracting Linux files can be simply a bash script followed by a compressed file. I see in the suggested bug, self extracting zips are supported. Maybe we could do something similar here? I tried with one of my own, renaming it from .bin (we should support arbitrary extensions) and got this error: ark.kerfuffle: Could not find a plugin to handle "self-extract-bash-tar-gz.tar.gz" -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 430755] New: OSRM backend broken/misconfigured?
https://bugs.kde.org/show_bug.cgi?id=430755 Bug ID: 430755 Summary: OSRM backend broken/misconfigured? Product: marble Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: data Assignee: marble-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- SUMMARY OSRM support broken? STEPS TO REPRODUCE 1. Configure only the OSRM backend for the pedestrian profile. 2. Create a route like this one: https://www.openstreetmap.org/directions?engine=fossgis_osrm_foot=44.3340%2C6.8657%3B44.3167%2C6.9419#map=14/44.3294/6.9043 OBSERVED RESULT I get 'No route found', when clearly the OSM site can. EXPECTED RESULT See the link. SOFTWARE/OS VERSIONS Marble Version: 2.2.20 (2.3 dev version) KDE Frameworks Version: 5.74.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429539] Allowing mixing syntax highlights
https://bugs.kde.org/show_bug.cgi?id=429539 --- Comment #2 from Marcos Dione --- Perfect. I will try to do that for YAML based .sls files (Salt). The only remaining question: what the best way to force kate to reread the syntax files? and is there a way to debug them somehow? Cheers! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 232013] [testcase url, non-reduced site] Konqueror crashes when opening a page (infocenter.arm.com) [WebCore::SVGCharacterLayoutInfo::addStackContent]
https://bugs.kde.org/show_bug.cgi?id=232013 Marcos Dione changed: What|Removed |Added CC|mdi...@grulic.org.ar| -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430049] New: session memory leak
https://bugs.kde.org/show_bug.cgi?id=430049 Bug ID: 430049 Summary: session memory leak Product: kate Version: 20.08.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- Created attachment 133893 --> https://bugs.kde.org/attachment.cgi?id=133893=edit session file that shows the memory leak SUMMARY When I open a specific session (attached), kate eats all memory until the kernel OOMKills it. STEPS TO REPRODUCE 1. Open kate 2. Select the attached session 3. Watch the process' memory consumption OBSERVED RESULT Eats all memory. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429539] Allowing mixing syntax highlights
https://bugs.kde.org/show_bug.cgi?id=429539 Marcos Dione changed: What|Removed |Added Priority|NOR |LO CC||mdi...@grulic.org.ar -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429539] New: Allowing mixing syntax highlights
https://bugs.kde.org/show_bug.cgi?id=429539 Bug ID: 429539 Summary: Allowing mixing syntax highlights Product: kate Version: 20.08.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- It is not uncommon to have a mix of languages on the same source: * salt and ansible use jinja for templating configuration files; salt even mixes jinja and yaml. * php sources can have HTML, JS and even SQL (4 languages!) in the same source. * etc. Kate only allows one syntax highlighting (SHL) at a time, rendering part of the code as plain text or worse. It would be nice if SHLs could be combined in the same view. For templating languages like jinja, it seems easy(er); PHP should definitely be harder (specially detecting SQL queries). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #10 from Marcos Dione --- I just installed phototonic, which seems to also be qt based, it it can't read those files the same way. Maybe we should push this below the tiff handling stack? Also, bump! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423213] Sort by desktop
https://bugs.kde.org/show_bug.cgi?id=423213 Marcos Dione changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Marcos Dione --- No, I mean that if I have N>1 desktops, then I expect on the left the icons of the first desktop, followed by the icons of the second one, and so on. I don't know how well the LtR order maps in all cultures, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423213] New: Sort by desktop
https://bugs.kde.org/show_bug.cgi?id=423213 Bug ID: 423213 Summary: Sort by desktop Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: mdi...@grulic.org.ar CC: plasma-b...@kde.org Target Milestone: 1.0 Just a wish, the usual task manager has this. I guess maybe they could share more code? SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 4:5.18.4.1-0ubuntu1 KDE Frameworks Version: 5.68.0-0ubuntu1 Qt Version: 5.12.8+dfsg-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422718] New: Plasma panel of the wrong size if created in one monitor and moved to another
https://bugs.kde.org/show_bug.cgi?id=422718 Bug ID: 422718 Summary: Plasma panel of the wrong size if created in one monitor and moved to another Product: plasmashell Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: 1.0 SUMMARY I have two screens, both 1080p, but one (left, main) non rotated, and the other on the right, rotated 90° to the left. I have my main panel on the left side of the left screen, and I wanted to create a new panel for the bottom of the screen in the right. When I created a new empty panel from the first panel's config menu, it created it in the left screen. Then I moved it to the bottom of the right screen and added a task manager (not the icons-only one). I configured it to have only one row, no grouping, and not filtering by desktop (I have 6). The task list run off the right edge and I couldn't reach most of my tasks (I had at least 14, maybe closer to 20). It took me a while to find a point in the panel where I could right click (where did the cashew go?) and replace the task manager with a icons-only one. Now I can see all my tasks, but they're sorted by PID or something and not by desktop, but that's another bug. Please point me to the right configuration files to see if the panel size is correct and whether editing it by hand can fix this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418877] New: Not only provide line and column, but also file position
https://bugs.kde.org/show_bug.cgi?id=418877 Bug ID: 418877 Summary: Not only provide line and column, but also file position Product: kate Version: 19.12.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- I'm not sure this wish should go to the part and/or the app. I'm using kate to edit a type of file whose compiler only present error in terms of byte position inside the file. Kate only thinks in terms of line+col. I would be nice if the app could present the position in file and maybe a slot to go to an arbitrary position. In parallel, I'm opening a bug on such compiler so it presents messages in terms of lines + cols. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 418502] New: better handling of external monitor brightness.
https://bugs.kde.org/show_bug.cgi?id=418502 Bug ID: 418502 Summary: better handling of external monitor brightness. Product: Powerdevil Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- To start with, I'm not sure this is the right component. Please advise me which one if not. SUMMARY The lightning in my office varies a lot with weather and time. I also have the redshift control plasma plugin on. The HW setup is: one notebook with an external screen, so two screens in total. I have a couple of issues with this setup. * The brightness up/down keystrokes (Fn+F11/F12) only handle the notebook's screen brightness, but not the external screen. I do this everitime I feel my eyes are straining to handle the low or high brightness independently of the time of the day. * I can change the external screen's brightness with`xrandr`, but if redshift is enabled, it resets it to the brightness it thinks it should have based on the config and time of the day, only on the external screen (the laptop's abides my wishes). STEPS TO REPRODUCE 1. have a laptop (dell precision 5220) 2. attach external screen (dell 22", not sure the model). 3. change brightness with keyboard (external screen does not change). 4. enable redshift control. 5. use `xrandr` to change external screen's brightness (`xrandr --output HDMI-1 --brightness 0.7`; brightness changes, but then redshift takes over and resets) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: 5.62.0-0ubuntu2 KDE Frameworks Version: 5.62.0-0ubuntu1 Qt Version: 5.12.4-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 417020] New: http.so in quasi tight loop
https://bugs.kde.org/show_bug.cgi?id=417020
Bug ID: 417020
Summary: http.so in quasi tight loop
Product: frameworks-kio
Version: 5.62.0
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: HTTP
Assignee: kdelibs-b...@kde.org
Reporter: mdi...@grulic.org.ar
Target Milestone: ---
SUMMARY
I have two processes using some cpu (around 8% each) that figure as:
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
mdione 2517 0.0 0.2 101660 18124 ?Ss ene28 0:00 kdeinit5:
Running...
mdione707738 0.3 0.3 331424 27068 ?Sl 09:43 0:30 \_ http.so
[kdeinit5] https local:/run/user/1000/klauncherjfwQiJ.1.slave-socket
local:/run/user/1000/plasmashellKcznzy.18.slave-socket
mdione709015 0.3 0.3 331424 27068 ?Sl 09:43 0:30 \_ http.so
[kdeinit5] https local:/run/user/1000/klauncherjfwQiJ.1.slave-socket
local:/run/user/1000/plasmashelltObnPw.19.slave-socket
If I attach with strace to one of them, I get:
$ strace -tt -p 709015
strace: Process 709015 attached
12:29:01.267475 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=51044},
NULL, 8) = 0 (Timeout)
12:29:01.267861 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
12:29:01.267983 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=100},
NULL, 8) = 0 (Timeout)
12:29:01.269195 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
12:29:01.269308 ppoll([{fd=4, events=POLLIN}], 1, {tv_sec=0, tv_nsec=100},
NULL, 8) = 0 (Timeout)
12:29:01.270552 write(3, "\1\0\0\0\0\0\0\0", 8) = 8
As you can see the loop is quite tight.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.5
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 414325] New: 'Comic book' order of spit panels
https://bugs.kde.org/show_bug.cgi?id=414325 Bug ID: 414325 Summary: 'Comic book' order of spit panels Product: kate Version: 19.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- SUMMARY I generally have my kate split in two overtically, one panel on the left and one on the right. Switching between them is simple enough, press F8 and you're done. The problem arises when I sometimes split the left panel horizontally, having the following layout: XX|YY XX|YY --+YY ZZ|yy ZZ|yy If I press F8 in this case, order is X -> Y -> Z -> X, but I would expect X -> Z -> Y -> X, as if I was reading a comic. Also notice that if I split Y horizontally into Y and y, I would expect X -> Y -> Z -> y -> X, which I think is what kate's going to do. But I have the impression that if I go X+Y -> X+Y+y -> X+Y+y+Z, that's the order in which the panels are going to be traversed with F8. I'm not sure if it make sense to take in account more complex setups. Otherwise, you could overlay a panel number every time I press F8 to train me to the real order. I also understand if you don't think you have to do anything about this and mark this as won't fix. STEPS TO REPRODUCE 1. Split vertically 2. Split left panel horizontally 3. Traverse panels with F8. OBSERVED RESULT * Order is X, Y, Z, X EXPECTED RESULT * Order is X, Z, Y, X SOFTWARE/OS VERSIONS KDE Frameworks 5.62.0 Qt 5.12.4 (built against 5.12.4) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 412898] New: marble's coord grig plugin not always shows labels.
https://bugs.kde.org/show_bug.cgi?id=412898 Bug ID: 412898 Summary: marble's coord grig plugin not always shows labels. Product: marble Version: 2.5 (KDE Applications 18.04) Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- SUMMARY The Coord Grid plugin is not always showing the latitude and/or longitude labels. STEPS TO REPRODUCE 1. Enable the Plugin. 2. Pan a little, specially in featureless regions (seas in most maps) so you can see the labels at left and bottom. OBSERVED RESULT See attached sshot. SOFTWARE/OS VERSIONS Marble Version: Version 2.2.20 (2.3 development version) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 303187] Support for different/high DPI devices
https://bugs.kde.org/show_bug.cgi?id=303187 --- Comment #3 from Marcos Dione --- I meant this link https://blog.mapbox.com/retina-maps-added-to-the-mapbox-ios-sdk-c0cb91245bf3 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 303187] Support for different/high DPI devices
https://bugs.kde.org/show_bug.cgi?id=303187 --- Comment #2 from Marcos Dione --- BTW, what some map renderers are doing is create 512x512 tiles instead. See for instance https://miro.medium.com/max/816/0*5T9IrSwyJPpSC--m.jpg -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409940] New: Undo cursor move
https://bugs.kde.org/show_bug.cgi?id=409940 Bug ID: 409940 Summary: Undo cursor move Product: kate Version: 18.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- Sometimes when using the editor I hit the wrong button and I move the cursor to somewhere completely off the viewport. Confused, I try to go back to where I was, but I can't remember the line number, so with a little bit of luck I remember the layout of the file and/or the name of the function I was editing (yes, I develop in Kate!) and after some searching and oogling, I can return. Also, while searching (and maybe replacing) I see something I should fix. It would be nice if I could revisit the places that search showed me. I know that then I can set a bookmark (luckily C-b works in S and S) and then come back there, but more often than not I already have several bookmarks set (to the point that the message 'no more letters to assign' is no stranger to me :) So my proposal is to have another undo stack, but only for cursor positions (maybe only populated when big jumps happen, like C-End, while searching, etc), and a couple of shortcuts to navigate this stack. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #8 from Marcos Dione --- Created attachment 120874 --> https://bugs.kde.org/attachment.cgi?id=120874=edit qgis 1:1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #7 from Marcos Dione --- Created attachment 120873 --> https://bugs.kde.org/attachment.cgi?id=120873=edit qgis full -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #6 from Marcos Dione --- Created attachment 120872 --> https://bugs.kde.org/attachment.cgi?id=120872=edit gwenview error -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #5 from Marcos Dione --- (In reply to Nate Graham from comment #4) > ...Unless, it's supposed to be a big gray rectangle. Can you share a > screenshot of what it's supposed to look like. The file is fine, it's a proper GeoTIFF (altho a very boring one, I should have used a better example). I added three attachments: * gwenview failing to open the file. * qgis with the whole file shown (yes, a grey square). * qgis showing the file at 1:1 scale. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 --- Comment #2 from Marcos Dione --- Try here: http://dionecanali.hd.free.fr/~mdione/000x004-hillshade.tif -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 408005] New: gwenview does not open (all) GeoTIFFs
https://bugs.kde.org/show_bug.cgi?id=408005 Bug ID: 408005 Summary: gwenview does not open (all) GeoTIFFs Product: gwenview Version: 18.04.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- SUMMARY When openeng certain (most, but not all) GeoTIFF files, gwenview presents this message: Loading ‘000x004-hillshade.tif’ failed Loading meta information failed. On the console I see this: QImageReader::read() using format hint "tif" failed: "Unknown error" QImageReader::read() without format hint failed: "Unsupported image format" QImageReader::read() using format hint "tif" failed: "Unknown error" QImageReader::read() without format hint failed: "Unsupported image format" QImageReader::read() using format hint "tif" failed: "Unknown error" QImageReader::read() without format hint failed: "Unsupported image format" I used ldd and strace to guess that libtiff is being used, but libtiff does definitely support GeoTIFF, as it is used by gdal, whi can read and write such files (and gdal's author, Even Rouault, also commits to libtiff (yes, it's all circunstancial, but I think it makes sense). I would provide a example file, but it weights 9MiB+, and I'm not sure I should attach it or not. Let me know if it's OK. Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 212378] compilation error: «error: non-static const member ‘KCategoryDrawer::Private* const KCategoryDrawer::d’, can't use default assignment operator»
https://bugs.kde.org/show_bug.cgi?id=212378 Marcos Dione changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Marcos Dione --- Dear Bug Cleaner: given that: * 9 years have passed * more importantly, a whole new platform version has been around * nobody else has complained or added anything, I think we can safely close as fixed. Sorry for leaving my toys on the floor and waste your valuable time. Cheers, -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 377181] Support for termcap/terminfo te@/ti@ sequences.
https://bugs.kde.org/show_bug.cgi?id=377181 Marcos Dione changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #6 from Marcos Dione --- > On a side note, turning these off is a broken idea by design. Sure it's more > convenient to be able to scroll back using the emulator's scrollbar, but the > moment you start using screen's features like detaching and re-attaching, it > no longer carries the scrollback contents. Or if you switch between multiple > windows inside screen, they'll have a common scrollback. This is how I got used to work with screen, using the emulator's scrollback was enough for me in many situations (and you can alwas resort to call screen's copy mode and use it's scrollback). I'll try those tips you mention, for the moment, yes, by all means, elt's close this bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 377181] Support for termcap/terminfo te@/ti@ sequences.
https://bugs.kde.org/show_bug.cgi?id=377181 --- Comment #2 from Marcos Dione --- Hi Sebastian. Thanks for confirming this bug. I have to say, I just tried and it works? I even ssh'd into another machine, reattached an old screen, and it still works. I'll keep testing other environments I have... Ok, I have one screen that works and another that doesn't. But I have no idea what's different or where should I look at. Probably this is a screen bug and not konsole's? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 108515] case sensitive nature of KDE causes much frustration to work with files and folders
https://bugs.kde.org/show_bug.cgi?id=108515 Marcos Dione changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mdi...@grulic.org.ar Resolution|--- |FIXED --- Comment #5 from Marcos Dione --- This has been fixed for ages now. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332208] Crop with Ratio setting is bad implemented
https://bugs.kde.org/show_bug.cgi?id=332208 --- Comment #7 from Marcos Dione <mdi...@grulic.org.ar> --- No, I think they need to connect another signal, like what Huon said here: https://bugs.kde.org/show_bug.cgi?id=332208#c1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332208] Crop with Ratio setting is bad implemented
https://bugs.kde.org/show_bug.cgi?id=332208 --- Comment #5 from Marcos Dione <mdi...@grulic.org.ar> --- Ooops: https://cgit.kde.org/gwenview.git/tree/lib/crop/cropwidget.cpp#n278 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 332208] Crop with Ratio setting is bad implemented
https://bugs.kde.org/show_bug.cgi?id=332208 --- Comment #3 from Marcos Dione <mdi...@grulic.org.ar> --- For info, there's no need to select a custom ratio; any of the predefined ratios has the same problem. I think what is happening is that when one makes a change in one of the fields, the other one is computed based on the aspect ratio, and because that one was changed, it propagates back to the first one. Based on Huon's comment, I found the culprit 2 lines: https://bugs.kde.org/show_bug.cgi?id=332208 I wish I had more time to pour on this, sounds like a very easy change. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 394714] custom aspect ratio when cropping
https://bugs.kde.org/show_bug.cgi?id=394714 --- Comment #4 from Marcos Dione <mdi...@grulic.org.ar> --- ... when I wrote the summary. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 394714] custom aspect ratio when cropping
https://bugs.kde.org/show_bug.cgi?id=394714 --- Comment #3 from Marcos Dione <mdi...@grulic.org.ar> --- > Regarding your first point: When implementing this, we actually tried having > an entry in the combobox called "Custom", but in the end decided against it > because in various situations it became confusing. We think that the blinking > cursor, the initial "width:height" text and the delete button are enough to > indicate there is a way to set a custom ratio. Well, the thing is, once you selected another value, it stays like that, even between different runs. So once you selected something else, it's not so evident that you can delete the text, unless you realize it's an editable dropdown and in hope that it would do something you delete the text. Is there a bug report or mail thread where this interface was discussed? As for the dupe, I didn't find it, but I was searching 'gwenview crop aspect ratio' (my bad; next time I'll remember to try less narrowing terms), and it didin't appear in the suggested bugs when I wrote the -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 394714] custom aspect ratio when cropping
https://bugs.kde.org/show_bug.cgi?id=394714 --- Comment #1 from Marcos Dione <mdi...@grulic.org.ar> --- I just found it, but is not evident: you just need to delete the . But the second part of the bug is still valid for specific aspect ratios. May I should rename the bug? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 394714] New: custom aspect ratio when cropping
https://bugs.kde.org/show_bug.cgi?id=394714 Bug ID: 394714 Summary: custom aspect ratio when cropping Product: gwenview Version: 18.04.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- There's no custom aspect ratio when cropping. For some pictures I just crop them to 6000x2000, and I used to do it with older versions of gwenview, but now I can't. Related to this bug, when one aspect ratio is selected, I can't enter any size. For instance, for a 6000x4000 (original size) picture, when selecting the width of the image, and trying to type 4500 (to get a 3000 height), when I type the 4 I get a 3 (and 2 for height); when I type the 5, I get another 3 (and another 2 for the height, so now the size is 33x22); for the zeros I don't have any problem, so the final size is 3300x2200, not the expected 4500x3000. Should I open a new bug for this? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 377181] New: Support for termcap/terminfo te@/ti@ sequences.
https://bugs.kde.org/show_bug.cgi?id=377181 Bug ID: 377181 Summary: Support for termcap/terminfo te@/ti@ sequences. Product: konsole Version: 16.12.0 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: mdi...@grulic.org.ar Target Milestone: --- I use screen with scrolling support turned on[1]. This was working at least on kde4's konsole and works on xterm and rxvt, and it doesn't under the specified version. I started reading a little about terminals and termcap/info and I got the impression that this could be fixed by configuration, but I don't have the slightest idea how. To reproduce: * install screen * add the following line to ~/.screenrc: termcapinfo xterm ti@:te@ * start screen * produce more lines than the current window size (for instance, cat'ing a long file) * try to scroll back with Shift-PageUp, but nothing happens (you can already see that the vertical scroll bar is not growing). -- [1] http://www.saltycrane.com/blog/2008/01/how-to-scroll-in-gnu-screen/#c7371 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 351619] Keep view after closing file and stay on it.
https://bugs.kde.org/show_bug.cgi?id=351619 Marcos Dione <mdi...@grulic.org.ar> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #2 from Marcos Dione <mdi...@grulic.org.ar> --- Right now I'm stuck in KDE4, so I can't try thi anymore. If you say you can't trigger the situation, then I'm closing this. If I manage to upgrade to KDE5, then I'll try again and eventually give more info. -- You are receiving this mail because: You are watching all bug changes.
