[plasmashell] [Bug 482991] New: Plasma crashed
https://bugs.kde.org/show_bug.cgi?id=482991 Bug ID: 482991 Summary: Plasma crashed Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maxsuelc.s.sw...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-18-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Failed to move image in notifications for Google Chrome browser in WhatsApp web. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1396 (plasmashell) UID: 1000 (maxcaetanoo) GID: 1000 (maxcaetanoo) Signal: 11 (SEGV) Timestamp: Sat 2024-03-09 11:50:59 -03 (54s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (maxcaetanoo) Boot ID: 746138a4f96640e8b86a1f8877c6dfe3 Machine ID: 34b450c635404e0daf892aafdc5eae0d Hostname: maxcaetano-debian Storage: /var/lib/systemd/coredump/core.plasmashell.1000.746138a4f96640e8b86a1f8877c6dfe3.1396.170999585900.zst (present) Size on Disk: 28.1M Message: Process 1396 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 1396: #0 0x7fe64b6aed14 pthread_sigmask (libc.so.6 + 0x8fd14) #1 0x7fe64b65b239 sigprocmask (libc.so.6 + 0x3c239) #2 0x7fe64dc46e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7fe64dc47b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7fe64b65b050 n/a (libc.so.6 + 0x3c050) #5 0x7fe64bf79871 _ZNK5QDrag10dragCursorEN2Qt10DropActionE (libQt5Gui.so.5 + 0x179871) #6 0x7fe64bf7d149 _ZN10QBasicDrag12updateCursorEN2Qt10DropActionE (libQt5Gui.so.5 + 0x17d149) #7 0x7fe64d34b37c n/a (libQt5WaylandClient.so.5 + 0x9637c) #8 0x7fe64bae8f4f n/a (libQt5Core.so.5 + 0x2e8f4f) #9 0x7fe64d3585e9 _ZN15QtWaylandClient18QWaylandDataSource18dndResponseUpdatedEbN2Qt10DropActionE (libQt5WaylandClient.so.5 + 0xa35e9) #10 0x7fe64d353db1 _ZN9QtWayland14wl_data_source13handle_targetEPvP14wl_data_sourcePKc (libQt5WaylandClient.so.5 + 0x9edb1) #11 0x7fe64d970f7a n/a (libffi.so.8 + 0x6f7a) #12 0x7fe64d97040e n/a (libffi.so.8 + 0x640e) #13 0x7fe64d970b0d ffi_call (libffi.so.8 + 0x6b0d) #14 0x7fe64df15761 n/a (libwayland-client.so.0 + 0xa761) #15 0x7fe64df11aaa n/a (libwayland-client.so.0 + 0x6aaa) #16 0x7fe64df1341c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x841c) #17 0x7fe64d32b872 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x76872) #18 0x7fe64bae8f7c n/a (libQt5Core.so.5 + 0x2e8f7c) #19 0x7fe64bb09865 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309865) #20 0x7fe64bab017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #21 0x7fe64bf7bf63 _ZN10QBasicDrag4dragEP5QDrag (libQt5Gui.so.5 + 0x17bf63) #22 0x7fe64bf79439 _ZN12QDragManager4dragEP5QDrag (libQt5Gui.so.5 + 0x179439) #23 0x7fe64bf79744 _ZN5QDrag4execE6QFlagsIN2Qt10DropActionEES2_ (libQt5Gui.so.5 + 0x179744) #24 0x7fe63e396249 n/a (org.kde.plasma.notifications.so + 0xf249) #25 0x7fe64badd6f0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd6f0) #26 0x7fe64c762fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #27 0x7fe64bab16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #28 0x7fe64bab4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
[dolphin] [Bug 447571] Flexible or larger thumbnail size AND per folder view settings
https://bugs.kde.org/show_bug.cgi?id=447571 --- Comment #2 from caetano --- regardless I agree that 512 is reasonable these days. Dolphin went to great lengths to be the best for managing pictures by e.g. showing thumbnails of a folder's contents directly onto the folder's icon (something no other manager can do to my knowledge), so I think allowing for very large previews would go in that continuity. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447571] Flexible or larger thumbnail size AND per folder view settings
https://bugs.kde.org/show_bug.cgi?id=447571 caetano changed: What|Removed |Added CC||chameleonscales@protonmail. ||com --- Comment #1 from caetano --- nemo and caja have a dconf setting for the thumbnail size that you can customize to any size you want. IMO this is a great solution because while I sometimes want very big thumbnails, I also understand that this is probably not a desirable option to provide in the preferences, as it may lead to performance or memory issues for some users, so having it as a dconf setting makes it clear that this is not an intended use and you're making changes at your own risk. Perhaps Dolphin could use some equivalent of that? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 281270] When copying files to a removable disk, speed and progress reflect copying to the local cache not to the disk itself
https://bugs.kde.org/show_bug.cgi?id=281270 --- Comment #33 from Gilberto Caetano de Andrade --- (In reply to Nate Graham from comment #32) > The message displayed in the Disks & Devices applet was just improved to > handle this case: > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1367 I don't see problem with the actual msg, but thus with the operation that never finishes and invariably corrupts usb content. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 281270] When copying files to a removable disk, speed and progress reflect copying to the local cache not to the disk itself
https://bugs.kde.org/show_bug.cgi?id=281270 Gilberto Caetano de Andrade changed: What|Removed |Added CC||gilbert...@gmail.com --- Comment #31 from Gilberto Caetano de Andrade --- I confirm this issue. Copying an ISO file to usb stick takes some minutes but clicking remove with security takes longer than normal. It disappears in Dolphin but in notifications continues with msg: removing device OpenSUSE 15.3 Dolphin 20.04.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426949] Edit raster selection breaks position
https://bugs.kde.org/show_bug.cgi?id=426949 --- Comment #6 from caetano --- issue still there in 4.4.2. Should we expect the fix in the next version? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379595] Request : option to bring back color selector from 3.0
https://bugs.kde.org/show_bug.cgi?id=379595 --- Comment #5 from caetano --- As far as I can see (which means on Linux only), this issue has been entirely fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426949] New: Edit raster selection breaks position
https://bugs.kde.org/show_bug.cgi?id=426949 Bug ID: 426949 Summary: Edit raster selection breaks position Product: krita Version: 4.4.0-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- Created attachment 131924 --> https://bugs.kde.org/attachment.cgi?id=131924=edit Broken edit selection SUMMARY For raster selections, the Edit Selection transform tool randomly changes the position of your rectangle as you drag a handle, as shown in this video : https://peertube.mastodon.host/videos/watch/28f13898-c3bf-4fb0-940e-31be945125f3 The effect seems to be more pronounced the more zoomed out you are. STEPS TO REPRODUCE 1. Create a blank document 2. Pick the Rectangle selection tool 3. Make sure it's set to raster selection and not vector 4. Select a rectangle inside your image 5. Zoom out a bit 6. Click on the menu Select > Edit Selection 6. Drag a corner and move it randomly without releasing the mouse button OBSERVED RESULT the opposite corner moves when it should stay still. SOFTWARE/OS VERSIONS Both Krita 4.3.0 and 4.4.0 beta1 appimages have this bug System : Xubuntu 20.04 System's Qt Version (not sure the appimage uses it): 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424809] Corners + Rotoscoping = crash
https://bugs.kde.org/show_bug.cgi?id=424809 --- Comment #3 from caetano --- I just tried with both the new stable release 20.08 appimage and today's nightly appimage (aug 22, kdenlive 20.11.70-48b183a) and found no difference. It stills crashes when I follow the steps I wrote above. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424809] Corners + Rotoscoping = crash
https://bugs.kde.org/show_bug.cgi?id=424809 --- Comment #1 from caetano --- as a side note to anyone looking for a workaround : having the 2 effects separated in 2 clips and using an "Alpha on Top" composition gives the same result while preventing the crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424809] New: Corners + Rotoscoping = crash
https://bugs.kde.org/show_bug.cgi?id=424809 Bug ID: 424809 Summary: Corners + Rotoscoping = crash Product: kdenlive Version: Appimage - Refactoring Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- Created attachment 130496 --> https://bugs.kde.org/attachment.cgi?id=130496=edit Corners + Rotoscoping crash test file UMMARY When adding a Rotoscoping effect under a Corners effect, Kdenlive crashes when I try to move a handle of the roto's shape. STEPS TO REPRODUCE 1. from a new blank project, add any 2 clips (e.g. 2 color clips, one black, one white) 2. stack them on top of each other in the timeline 3. add a Corners effect to the top one 4. move its handles 5. add a Rotoscoping effect on the same clip 6. add some handles and right-click to confirm (Kdenlive may already crash) 7. move the playhead 8. add a keyframe to the Rotoscoping 9. try to move a handle By now Kdenlive should have crashed. If not, add some more keyframes and edit the shape. Attached to this report is a simple file that crashes after I move the playhead and try to edit the roto's shape in the existing keyframe. SOFTWARE/OS VERSIONS Kdenlive Appimage 20.04.1b Linux/KDE Plasma: manjaro KDE KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.2 Qt Version: 5.15.0 ADDITIONAL INFORMATION also tested on Debian 10.3 XFCE with the same appimage. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424549] New: [Request] Allow to vertically expand Bézier curve panel
https://bugs.kde.org/show_bug.cgi?id=424549 Bug ID: 424549 Summary: [Request] Allow to vertically expand Bézier curve panel Product: kdenlive Version: 20.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- When I do precision work, the vertical size of the Bezier curve effect makes it difficult to fine-tune the curve, especially on my 140 ppi 4K monitor. https://i.imgur.com/LalGpOd.png It would be great if we could drag the panel down and expand the curve grid vertically. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423635] Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264
https://bugs.kde.org/show_bug.cgi?id=423635 Vitor Caetano changed: What|Removed |Added CC||vito...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423635] New: Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264
https://bugs.kde.org/show_bug.cgi?id=423635 Bug ID: 423635 Summary: Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264 Product: kdenlive Version: 20.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: vito...@gmail.com Target Milestone: --- SUMMARY The MP4 rendering format (H264 / AAC) states that the libx64 video codec is not supported. I use the Debian Bullseye version. O formato de renderização MP4 (H264/AAC) acusa que o codec de video libx64 não é suportado. Utilizo a versão Debian Bullseye. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 369438] Allow selection of OFX tag to use for Payee, even if account not mapped
https://bugs.kde.org/show_bug.cgi?id=369438 Gilberto Caetano de Andrade changed: What|Removed |Added CC||gilbert...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412599] "Render Animation" uses MPEG-4 size limits while in Image Sequence mode
https://bugs.kde.org/show_bug.cgi?id=412599 --- Comment #4 from caetano --- tbh I don't see the point. The gif workaround solves the issue and it's not my decision to consider that ffmpeg is too heavy to be bundled and that the download page doesn't need information about it like G'MIC does. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412599] "Render Animation" uses MPEG-4 size limits while in Image Sequence mode
https://bugs.kde.org/show_bug.cgi?id=412599 --- Comment #2 from caetano --- I'll have to contradict that. I just tested it on a fresh Debian 10 install and the error is still there. I have the ffmpeg that comes pre-installed in Debian (stable 7:4.1.4-1~deb10u1 amd64), however I assume the appimage contains its own dependencies, as that's what they're all about. Furthermore there's no indication on the Krita download page that we should download ffmpeg, whereas there is such an indication for G'MIC (https://krita.org/en/download/krita-desktop/), nor do I see any mention of ffmpeg in the installation documentation: https://docs.krita.org/en/user_manual/getting_started/installation.html?highlight=installation so it seems very unlikely to me that we're supposed to do this additional step. I could be wrong but I'll need some evidence. Did you make sure to select MPEG-4 prior to selecting Image Sequence? Maybe your specific image dimensions somehow bypassed this bug. I got the error on a 21960x3720 as well as on a 11000x200 image. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412599] New: "Render Animation" uses MPEG-4 size limits while in Image Sequence mode
https://bugs.kde.org/show_bug.cgi?id=412599 Bug ID: 412599 Summary: "Render Animation" uses MPEG-4 size limits while in Image Sequence mode Product: krita Version: 4.2.7 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- SUMMARY When attempting to render an image sequence with File > Render Animation..., if the video format is set to MPEG-4 (but you are still in the Image Sequence mode), the image size restrictions of MPEG-4 apply to the export, causing a failure if your image is larger than what MPEG-4 allows (10 000px either in width or height). Switching the Video format to GIF and going back to image sequence (e.g. jpg) solves the issue. STEPS TO REPRODUCE 1. Create or open an animation and set the canvas size to be superior to 10 000 either in width or height 2. Go to File > Render Animation... 3. Select Video and make sure the export format is MPEG-4 4. Select Image Sequence and pick any format (e.g. jpg) 5. Click OK 6. You should see an error message saying : Could not render animation: Mpeg4 (.mp4) requires width and height to be even numbers. Please resize or crop the image before exporting. which by the way is the wrong error message, since it doesn't have anything to do with odd numbers but rather the size limit. 7. Go once again to File > Render Animation... 8. This time in Video, select GIF as the export format 9. Select Image Sequence back and keep the same image format as before 10. Click OK : this time the export should work SOFTWARE/OS VERSIONS Krita appimage 4.2.7.1 Linux: Debian 9 (XFCE) Qt Version: 5.7.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396244] New: Cross-channel color adjustment goes plain red
https://bugs.kde.org/show_bug.cgi?id=396244 Bug ID: 396244 Summary: Cross-channel color adjustment goes plain red Product: krita Version: 4.1.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: chameleonsca...@protonmail.com Target Milestone: --- When setting a cross-channel color adjustment layer (or mask) to channel: Saturation and Driver channel: Hue every pixel of the original image that has 0 saturation becomes plain red as soon as we tweak the curve no matter how. Steps to reproduce: 1. Create a new Krita document 2. Add some brush strokes of grays with 0 saturation and some brush strokes with a very slight color saturation. 3. Add a filter layer or filter mask 4. Set it to Cross-channel color adjustment 5. Set Channel to Saturation and Driver channel to Hue 6. add a point to the curve and move it in any direction: the white canvas becomes plain red and the grey strokes have plain red multiplied in them too. My GPU: Nvidia GeForce 820M with proprietary driver on Linux Mint. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 Gilberto Caetano de Andrade <gilbert...@gmail.com> changed: What|Removed |Added CC||gilbert...@gmail.com --- Comment #74 from Gilberto Caetano de Andrade <gilbert...@gmail.com> --- I'm having the same issue, I have the same e-mail registered in bugs and indentity but I can't remember my user name for the latter. Could you please have a look at it? Regards, Gilberto -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 --- Comment #10 from caetano <caetano...@gmail.com> --- I decided to add a feature request : https://bugs.kde.org/show_bug.cgi?id=379595 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379595] New: Request : option to bring back color selector from 3.0
https://bugs.kde.org/show_bug.cgi?id=379595 Bug ID: 379595 Summary: Request : option to bring back color selector from 3.0 Product: krita Version: 3.1.3 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: color selectors Assignee: krita-bugs-n...@kde.org Reporter: caetano...@gmail.com Target Milestone: --- Watch this video : https://youtu.be/p0utEn10ni4 there was also a bug report : https://bugs.kde.org/show_bug.cgi?id=372221 Given that it's been several versions since the new selector was introduced and this issue hasn't been fixed, I think we could at least have an option to use the old "working" selector until the new gets fixed. I use fill layers all the time and this popup color selector is the only one we can use for these layers. Thanks for your attention. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372221] Pop-up palette color selector - difficult to select colors.
https://bugs.kde.org/show_bug.cgi?id=372221 caetano <caetano...@gmail.com> changed: What|Removed |Added CC| |caetano...@gmail.com --- Comment #9 from caetano <caetano...@gmail.com> --- Just to add some info and suggestions : This happens regardless of the video driver (nvidia or nouveau) and to me it's actually a big issue as it's the only color selector we can use when creating a fill layer (and I use fill layers all the time). At least an option to bring back the selector from 3.0 in the settings would help a lot. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 356013] kdeinit crashed when using menu
https://bugs.kde.org/show_bug.cgi?id=356013 Gilberto Caetano de Andrade <gilbert...@gmail.com> changed: What|Removed |Added CC||gilbert...@gmail.com --- Comment #1 from Gilberto Caetano de Andrade <gilbert...@gmail.com> --- I can confirm this behavior. This happens periodically when selecting any icon on the favorite - mainly Kmymoney: Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #4 0x7f6354b330c7 in raise () at /lib64/libc.so.6 #5 0x7f6354b34478 in abort () at /lib64/libc.so.6 #6 0x7f6354b70784 in () at /lib64/libc.so.6 #7 0x7f6354b76026 in malloc_printerr () at /lib64/libc.so.6 #8 0x7f6354b76d53 in _int_free () at /lib64/libc.so.6 #9 0x7f6355eff026 in xcb_disconnect () at /usr/lib64/libxcb.so.1 #10 0x7f634cfccbd5 in () at /usr/lib64/libkdeinit5_klauncher.so #11 0x7f634cfccc55 in () at /usr/lib64/libkdeinit5_klauncher.so #12 0x7f634cfd9215 in () at /usr/lib64/libkdeinit5_klauncher.so #13 0x7f635515ccc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #14 0x7f63551de8ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #15 0x7f6355169a89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #16 0x7f635512d18d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x7f635512ce95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f6355181743 in QEventDispatcherUNIX::activateSocketNotifiers() () at /usr/lib64/libQt5Core.so.5 #19 0x7f6355181beb in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #20 0x7f6355181f3b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f6348feb33d in () at /usr/lib64/libQt5XcbQpa.so.5 #22 0x7f635512ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #23 0x7f63551328f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #24 0x7f634cfd6a1a in kdemain () at /usr/lib64/libkdeinit5_klauncher.so #25 0x004086fc in _start () # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:42.1" BUG_REPORT_URL="https://bugs.opensuse.org; HOME_URL="https://opensuse.org/; ID_LIKE="suse" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376373] Can't reach OK button in Configure Krita window
https://bugs.kde.org/show_bug.cgi?id=376373 caetano <caetano...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from caetano <caetano...@gmail.com> --- I just found that on linux, when you can't reach the bottom of a window, you just have to Alt+left click drag on it (in my case Meta instead of Alt) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376373] Can't reach OK button in Configure Krita window
https://bugs.kde.org/show_bug.cgi?id=376373 caetano <caetano...@gmail.com> changed: What|Removed |Added Summary|Can't reach OK in Configure |Can't reach OK button in |Krita window|Configure Krita window --- Comment #2 from caetano <caetano...@gmail.com> --- Open source driver is xf86-video-nouveau 1.0.12-1.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376374] Brush tip export options for .gih file have several issues
https://bugs.kde.org/show_bug.cgi?id=376374 caetano <caetano...@gmail.com> changed: What|Removed |Added Summary|Buggy pop up window when|Brush tip export options |saving .gih file|for .gih file have several ||issues -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376374] New: Buggy pop up window when saving .gih file
https://bugs.kde.org/show_bug.cgi?id=376374 Bug ID: 376374 Summary: Buggy pop up window when saving .gih file Product: krita Version: 3.1.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: caetano...@gmail.com Target Milestone: --- Created attachment 103988 --> https://bugs.kde.org/attachment.cgi?id=103988=edit Brush tip export options When I try to save a .gih file for an animated brush, I can't change the selection mode (it's greyed out) and my cursor stays on wait mode (although I can click on the other stuff). Also the name I give to the brush in this window seems to be ignored since when I import it from the brush settings the brush gets named "name :" which means if I import more brushes, I may run into name conflicts. Specs : Nvidia GeForce GT 640 OpenSUSE Leap 42.2 64-bit (kernel 4.4.36-8-default) KDE Plasma 5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376373] Can't reach OK in Configure Krita window
https://bugs.kde.org/show_bug.cgi?id=376373 --- Comment #1 from caetano <caetano...@gmail.com> --- Note that with the Nvidia proprietary driver the window gets smaller and the OK button is visible, however I need to use the open source driver (for my wacom tablet to work properly) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376373] New: Can't reach OK in Configure Krita window
https://bugs.kde.org/show_bug.cgi?id=376373 Bug ID: 376373 Summary: Can't reach OK in Configure Krita window Product: krita Version: 3.1.2 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: caetano...@gmail.com Target Milestone: --- On my 1360x766 screen, The OK button of the Configure Krita window is out of the screen and the window size can only be extended, not shrunk. I'd like it to be resizeable so I could reach the OK and Cancel buttons. Specs : Nvidia GeForce GT 640 OpenSUSE Leap 42.2 64-bit (kernel 4.4.36-8-default) KDE Plasma 5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 --- Comment #48 from Gilberto Caetano de Andrade <gilbert...@gmail.com> --- Browsing internal phone storage works, but browsing …/storage/extSdCard/ is not possible unless you enter existing folder name after extSdCard/. Than is possible to browse this folder and subfolders in it. Everything comes with only root permissions - no way to change/delete things. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Gilberto Caetano de Andrade <gilbert...@gmail.com> changed: What|Removed |Added CC||gilbert...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 caetano <caetano...@gmail.com> changed: What|Removed |Added Version|2.9.11 |3.0 Severity|normal |minor OS|MS Windows |Linux -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #11 from caetano <caetano...@gmail.com> --- The issue is almost gone in Krita 3.0 ! It only bugs when I press "del" and paint, otherwise, it seems to work perfectly ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #10 from caetano <caetano...@gmail.com> --- I found a quick way to get around this bug : On Windows : - Create a fill layer - do a paint stroke on it (no matter the color) - Without selecting anything, press del (not backspace) - Paint On Linux : - Create a fill layer - Without selecting anything, Press del (not backspace) - Paint -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #9 from caetano <caetano...@gmail.com> --- ignore this comment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #8 from caetano <caetano...@gmail.com> --- Yes exactly, thanks for the backup ! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #6 from caetano <caetano...@gmail.com> --- Tried with Linux Mint Rosa (Krita 2.9.11) and it gets better, the strokes update at about half of each LMB release and when it doesn't, I can update by clicking twice on the eye. This doesn't happen with windows. But still impossible to decently work with. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #5 from caetano <caetano...@gmail.com> --- Tried with windows 10. Same problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362987] New: Dolphin crashes - right click on 3gp file and choose Open With
https://bugs.kde.org/show_bug.cgi?id=362987 Bug ID: 362987 Summary: Dolphin crashes - right click on 3gp file and choose Open With Product: dolphin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gilbert...@gmail.com Application: dolphin (16.04.0) Qt Version: 5.5.1 Frameworks Version: 5.20.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying to open a 3gp file with the option Open With and then enter audacious. But it crashes before I end the typing -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f05741887c0 (LWP 2399))] Thread 4 (Thread 0x7f055d119700 (LWP 2400)): #0 0x7f0573a2ebbd in poll () at /lib64/libc.so.6 #1 0x7f0566a3b422 in () at /usr/lib64/libxcb.so.1 #2 0x7f0566a3d00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f055f46e3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f056db4132f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f05695ed0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f0573a36fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f05512cf700 (LWP 2401)): #0 0x7f0573a2ebbd in poll () at /lib64/libc.so.6 #1 0x7f0568a67e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0568a67f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f056dd73d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f056dd1ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f056db3c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f056db4132f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f05695ed0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f0573a36fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0521c88700 (LWP 5608)): [KCrash Handler] #6 0x7f056db3f47a in QThreadStorageData::finish(void**) () at /usr/lib64/libQt5Core.so.5 #7 0x7f056db405ae in () at /usr/lib64/libQt5Core.so.5 #8 0x7f056db41351 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f05695ed0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f0573a36fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f05741887c0 (LWP 2399)): #0 0x7f05695f103f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0566a3b669 in () at /usr/lib64/libxcb.so.1 #2 0x7f0566a3cd5f in () at /usr/lib64/libxcb.so.1 #3 0x7f0566a3ce72 in xcb_wait_for_reply () at /usr/lib64/libxcb.so.1 #4 0x7f055f4680ba in QXcbConnection::sync() () at /usr/lib64/libQt5XcbQpa.so.5 #5 0x7f055f486b3e in () at /usr/lib64/libQt5XcbQpa.so.5 #6 0x7f055f486dd7 in () at /usr/lib64/libQt5XcbQpa.so.5 #7 0x7f056ee9e7f3 in () at /usr/lib64/libQt5Widgets.so.5 #8 0x7f056ee9ec94 in () at /usr/lib64/libQt5Widgets.so.5 #9 0x7f056eebdd7f in QWidgetPrivate::syncBackingStore() () at /usr/lib64/libQt5Widgets.so.5 #10 0x7f056eed1e94 in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f056ee91e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #12 0x7f056ee96cc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7f056dd1ce95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x7f056dd1f057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f056dd748f3 in () at /usr/lib64/libQt5Core.so.5 #16 0x7f0568a67c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7f0568a67ed8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7f0568a67f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7f056dd73d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7f056dd1ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f056f080e1d in QDialog::exec() () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f05722fd3e2 in KRun::displayOpenWithDialog(QList const&, QWidget*, bool, QString const&, QByteArray const&) () at /usr/lib64/libKF5KIOWidgets.so.5 #23 0x7f05722d5cdc in () at /usr/lib64/libKF5KIOWidgets.so.5 #24 0x7f05723315ec in () at /usr/lib64/libKF5KIOWidgets.so.5 #25 0x7f056dd4ccc6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #26 0x7f056ee888d2 in QAction::triggered(bool) () at /usr/lib64/libQt5Widgets.so.5 #27
[krunner] [Bug 362621] New: Krunner crashes entering Golden
https://bugs.kde.org/show_bug.cgi?id=362621 Bug ID: 362621 Summary: Krunner crashes entering Golden Product: krunner Version: 5.5.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: gilbert...@gmail.com Application: krunner (5.5.95) Qt Version: 5.5.1 Frameworks Version: 5.20.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Alt+F2 and enter Golden. The Golden dictionary doesnt appear, nothing happens. After that I could see the error icon in the notificatio area. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9f057547c0 (LWP 2708))] Thread 7 (Thread 0x7f9ef03a2700 (LWP 2709)): #0 0x7f9f013e1bbd in poll () at /lib64/libc.so.6 #1 0x7f9f008ea422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9f008ec00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9ef24f33c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9f01adc32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f9eff47a0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9f013e9fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f9ee39ec700 (LWP 2721)): #0 0x7f9efe921cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f9efe8df028 in g_main_context_release () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9efe8dfe0e in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9efe8dff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9f01d0ed8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9f01cb5d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f9f01ad761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f9f043d7e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f9f01adc32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f9eff47a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9f013e9fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9ece484700 (LWP 4768)): #0 0x7f9eff47e03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9f01add34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9ee010265f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9ee010643a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9ee01006cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9ee0104005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9f01adc32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f9eff47a0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f9f013e9fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9ecdc83700 (LWP 4769)): #0 0x7f9eff47e03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9f01add34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9ee010265f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9ee010643a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9ee01006cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9ee0106481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9ee01006cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9ee0104005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9f01adc32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f9eff47a0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9f013e9fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9ecd482700 (LWP 4770)): [KCrash Handler] #6 0x7f9f01394f58 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x7f9ed651e47a in () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x7f9ed650981e in () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x7f9ed65098c1 in Baloo::PostingDB::iter(QByteArray const&) () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x7f9ed6512a5d in Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #11 0x7f9ed695cddb in () at /usr/lib64/libKF5Baloo.so.5 #12 0x7f9ed695cf32 in () at /usr/lib64/libKF5Baloo.so.5 #13 0x7f9ed695de69 in () at
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #4 from caetano <caetano...@gmail.com> --- Just tried with Krita 3.0 Beta (debug and non debug builds) and nothing changed on this side. I also experience layer updating problems with paint layers sometimes, but I can't predict it yet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 --- Comment #2 from caetano <caetano...@gmail.com> --- Sorry I meant "delete" (I have a french keyboard) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360785] New: Fill layers not updating
https://bugs.kde.org/show_bug.cgi?id=360785 Bug ID: 360785 Summary: Fill layers not updating Product: krita Version: 2.9.11 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: adjustment layers Assignee: krita-bugs-n...@kde.org Reporter: caetano...@gmail.com If I create a fill layer, do ctrl+A, suppr and paint on it (in white), nothing will appear. Then if I make a new selection and fill it (backspace or shift+backspace), all my previous brush strokes suddenly appear. I'm on Windows x64 and I tried with Krita 2.9.11 and 3.0 Pre-alpha. -- You are receiving this mail because: You are watching all bug changes.
