[okular] [Bug 419221] Presentation toolbar: Checkmarks in drawing tool buttons blurry on HiDPI
https://bugs.kde.org/show_bug.cgi?id=419221 --- Comment #4 from Oliver Sander --- This was fixed by ef488d334ea9fe55d821c9a400bbe325981cd856, wasn't it? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422330] Unable to send files from desktop(manjaro) to android
https://bugs.kde.org/show_bug.cgi?id=422330 --- Comment #1 from ajaygupta001...@gmail.com --- I managed to solve the issue. It had to do with the default save path to "Downloads" on the android device. I went to Plugin settings> Clicking the settings icon for "Share and Receive" and set the download path manually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413075] The first window open in a session has no windeco if non-Breeze
https://bugs.kde.org/show_bug.cgi?id=413075 --- Comment #3 from cacarry --- Decorations work if you use breeze decorations -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422651] Bad paragraph spacing
https://bugs.kde.org/show_bug.cgi?id=422651 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.14.2 CC||mon...@kde.org Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421857] Okular crash when verifing digital signature
https://bugs.kde.org/show_bug.cgi?id=421857 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop
https://bugs.kde.org/show_bug.cgi?id=422008 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421283] Texture should not always scale with brush size
https://bugs.kde.org/show_bug.cgi?id=421283 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347874] Drawing area flashes random section of the alpha layer
https://bugs.kde.org/show_bug.cgi?id=347874 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534 --- Comment #5 from Guilherme Silva --- Sorry I took this long to respond. Yes, I can still reproduce this on Plasma 5.18.5. A quick search for ".gtkrc-2.0" on KDE's org on Github showed me this file (specifically, the writeGtk2Settings() method): https://github.com/KDE/plasma-workspace/blob/7f2ae10539f2167663aab713986e3f5e0528289f/gmenu-dbusmenu-proxy/menuproxy.cpp#L169 That method doesn't address the GTK2_RC_FILES variable, instead it hardcodes it to ~/.gtkrc-2.0. A bit down in the code, that method is called by writeGtk2Settings(), which I guess ends up creating a new (but empty) .gtkrc-2.0 in my home directory. Just a wild guess, though. I'm not a C++ programmer but I'll try fixing it locally, and I'll let you guys know if that's what's causing the problem. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422654] New: Strange slider behavior in thumbnails
https://bugs.kde.org/show_bug.cgi?id=422654 Bug ID: 422654 Summary: Strange slider behavior in thumbnails Product: okular Version: 1.10.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: bondarenko16.12.2...@mail.ru Target Milestone: --- Created attachment 129148 --> https://bugs.kde.org/attachment.cgi?id=129148=edit Bug reproduction SUMMARY The slider is divided into two parts by the border between the pages. If you take the smaller part of the slider and pull it in the direction that corresponds to it, then at the moment when the middle of the slider is between the pages, it will skip forward to the page. STEPS TO REPRODUCE 1. Open multi-page file and place the slider so that it lay on the pages 1 and 2, but more on page 1. 2. Take the smaller part of the slider and swipe it down OBSERVED RESULT Slider jumped from pages 1 and 2 to pages 2 and 3 EXPECTED RESULT The slider will remain on pages 1 and 2, but part of the slider on the second page will become larger SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.4.40-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 302925] Add optional warning when doing mass edit of properties
https://bugs.kde.org/show_bug.cgi?id=302925 andrew changed: What|Removed |Added CC||andrew+kdeb...@andrew.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 142753] Add undo functionality to assigning/removing Tags and Labels
https://bugs.kde.org/show_bug.cgi?id=142753 andrew changed: What|Removed |Added CC||andrew+kdeb...@andrew.org -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 418024] Cannot see gdrive directory
https://bugs.kde.org/show_bug.cgi?id=418024 yuntan.s...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from yuntan.s...@gmail.com --- I'd confirmed that the issue was resolved. Thanks. Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 422468] Tellico crash after quit
https://bugs.kde.org/show_bug.cgi?id=422468 --- Comment #2 from Robby Stephenson --- (In reply to gitdevmod from comment #1) > I've build tellico with CMAKE_DISABLE_FIND_PACKAGE_KF5NewStuff=TRUE but it > still crash. > Then I commented this line "NewStuff::Manager::self();" in > src/mainwindow.cpp and no more crash after quit. I do not know impact of > this change. It just removes the DBUS interface for installing new themes, which you would probably not even miss. I'm not sure why it would crash though > According to kde-craft dev, there is patch in qt for dbus on Windows and it > could crash. > Is this possible to add an option to disable dbus/knewstuff in tellico ? That might be the brute-force approach. I'll work it. Thanks for working that out. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415664] Streaming Video from sites with DRM doesn't work.
https://bugs.kde.org/show_bug.cgi?id=415664 newyorkcitydude2...@yahoo.com changed: What|Removed |Added OS|Linux |Microsoft Windows CC||newyorkcitydude2003@yahoo.c ||om Platform|Neon Packages |Windows CE Keywords||reproducible --- Comment #1 from newyorkcitydude2...@yahoo.com --- Having same issue, on windows and mac, regardless of version of Falkon. jw player for example shows "Error Code: 102630" video can't play/stream. Legacy player also does not function. Perhaps a fix made on IE8 may work in our case. https://stackoverflow.com/questions/15541610/jw-player-is-not-working-in-ie-8 Please advise. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 402890] Menu items ‘Open selected files’/‘Open’ overwrites template files instead of creating translation files
https://bugs.kde.org/show_bug.cgi?id=402890 Simon Depiets changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Simon Depiets --- Ok I have a better understanding of the issue now, I'll work on it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422653] New: Xwayland gets segmentation faults at wl_proxy_marshal_constructor under kwin_wayland 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422653 Bug ID: 422653 Summary: Xwayland gets segmentation faults at wl_proxy_marshal_constructor under kwin_wayland 5.18.5 Product: kwin Version: 5.18.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nia1048...@gmail.com Target Milestone: --- SUMMARY Manually execute a new Xwayland instance under kwin_wayland will get segmentation fault. STEPS TO REPRODUCE 1. Login to KDE wayland session and open a terminal 2. pick an empty DISPLAY (e.g. 10) and execute "Xwayland :10" 3. crash OBSERVED RESULT (gdb) run :10 Starting program: /usr/bin/Xwayland :10 ... Thread 1 "Xwayland" received signal SIGSEGV, Segmentation fault. wl_proxy_marshal_constructor (proxy=0x0, opcode=opcode@entry=0, interface=0x55787c40 ) at /usr/src/debug/dev-libs/wayland-1.18.0/wayland-1.18.0/src/wayland-client.c:830 830 wl_argument_from_va_list(proxy->object.interface->methods[opcode].signature, (gdb) bt #0 wl_proxy_marshal_constructor (proxy=0x0, opcode=opcode@entry=0, interface=0x55787c40 ) at /usr/src/debug/dev-libs/wayland-1.18.0/wayland-1.18.0/src/wayland-client.c:830 #1 0x5558d4b2 in wl_shell_get_shell_surface (surface=, wl_shell=) at /usr/include/wayland-client-protocol.h:2926 #2 ensure_surface_for_window (window=window@entry=0x55f46a00) at xwayland.c:565 #3 0x5558db51 in xwl_realize_window (window=0x55f46a00) at xwayland.c:645 #4 0x556be685 in compRealizeWindow (pWin=0x55f46a00) at compwindow.c:268 #5 0x55700827 in MapWindow (pWin=pWin@entry=0x55f46a00, client=0x557bdf70) at window.c:2715 #6 0x557009e7 in InitRootWindow (pWin=0x55f46a00) at window.c:701 #7 0x556d4b08 in dix_main (argc=2, argv=0x7fffdc38, envp=) at main.c:247 #8 0x556bf3d6 in main (argc=, argv=, envp=) at stubmain.c:34 EXPECTED RESULT Xwayland runs successfully without crash SOFTWARE/OS VERSIONS I can reproduce this bug in two environments. The above backtrace comes from the first environment: Operating System: Gentoo Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Second environemnt: Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION The bug seems to happen after upgrading kwin to 5.18.5 from 5.17.5 on my Gentoo box. When running GNOME wayland session in Arch Linux, Xwayland works fine, so I report the bug here to KDE. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #7 from Johannes Zarl-Zierl --- Thanks for the log file and for the additional info! I think I may have found the culprit. A change in the Qt library that we didn't notice may have prevented proper error handling when ffmpeg fails to extract video thumbnails. I think I can sync Neon user edition to git master this week so that you can try the fix without compiling kphotoalbum yourself... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #6 from Johannes Zarl-Zierl --- Git commit 7e0c7cb15b78c3920eadfed5f1398c2754cb91dc by Johannes Zarl-Zierl. Committed on 08/06/2020 at 23:27. Pushed by johanneszarl into branch 'master'. ExtractOneVideoFrame: fix connect statements. Fix incorrect signal/slot connection that may prevent proper error handling when extracting video frames fails. M +10 -2ImageManager/ExtractOneVideoFrame.cpp M +8-2ImageManager/ExtractOneVideoFrame.h https://invent.kde.org/graphics/kphotoalbum/commit/7e0c7cb15b78c3920eadfed5f1398c2754cb91dc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387209] Select from visible layers for similar color selector and contiguous color selector
https://bugs.kde.org/show_bug.cgi?id=387209 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Right now there are three options in contiguous color selector: - all layers - current layer - color labeled layers The similar color selector tool has only the current layer option, but I want to add the other two options there as well. Will it be enough, or something else should be added? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422148] Respects settings only when the spectacle window is opened
https://bugs.kde.org/show_bug.cgi?id=422148 --- Comment #2 from fabian.du...@gmail.com --- (In reply to Antonio from comment #1) > Hi, thanks for he report. > But I'm not quite sure what you mean with "Crop screenshot". Do you mean > "take a screenshot" or literally cropping an image? > > Sorry for me not understanding this properly, I'd like to help but first I > need to understand the question :) Sorry for the misunderstanding, english is not my first language. The problem occurs, when I try to use the "Capture rectangular region" function. On Manjaro the standard shortcut for this is Meta+shift+Print hope this helps :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422626] Allow multiple pages ranges to print in Okular
https://bugs.kde.org/show_bug.cgi?id=422626 --- Comment #5 from Jack --- I finally tested both. On Windows (package is 19.12.2, help/about says 1.9.2) the print dialog explicitly says to enter single page or single page range. As in Comment 2, I don't know if this is an Okular on Windows limitation, or something inherent to the Windows print system. On Linux (About says 1.9.3, but package says 19.12.3) I confirm that requesting pages "1,49-50,99" still printed the entire document. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418370] Inivisible Anydesk tray icon sits at the top left corner.
https://bugs.kde.org/show_bug.cgi?id=418370 --- Comment #2 from Evgen --- My current workaround is to restart GUI after login with script nano ~/.config/autostart-scripts/restart_anydesk.sh #!/bin/bash if pgrep -f "anydesk --tray" > /dev/null; then pkill -x anydesk /usr/bin/anydesk --tray & fi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #16 from scott --- KWIN_COMPOSE=Q does not appear to have an effect. I still get the black screen + frozen cursor. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 269768] Add a magic scale tool (as a alternative to standard scaling filters like bicubic etc.)
https://bugs.kde.org/show_bug.cgi?id=269768 Tymond changed: What|Removed |Added Summary|Add a tool for enhanced |Add a magic scale tool (as |magnified bitmap layers |a alternative to standard ||scaling filters like ||bicubic etc.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 269768] Add a tool for enhanced magnified bitmap layers
https://bugs.kde.org/show_bug.cgi?id=269768 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #3 from Tymond --- I think if we're going to have a magic enlarge, we should use a newer technology using some neural networks. I think they had a bit better results... I remember David Revoy giving some nice examples with text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422645] Often when Firefox starts, desktop content briefly shifts down and right
https://bugs.kde.org/show_bug.cgi?id=422645 --- Comment #2 from David Edmundson --- Can you create a video? Also confirm if it happens without compositing (alt + shift + f12) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #15 from David Edmundson --- Optimus potentially makes things interesting. You can try with exporting KWIN_COMPOSE=Q Things will be super slow, but it will be good data point to see what happens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389828] Place widget windows like filter-curves on the right side of the screen
https://bugs.kde.org/show_bug.cgi?id=389828 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- On my system, when opening Krita, the filter dialog would open on the right side of the screen. When moved somewhere and closed, next time it would appear in place where it was dragged to before. So it looks like it's working here. Can you please check if it got implemented for you as well? My system information: Krita Version: 4.3.0-beta2 Languages: en_US, en, en_US, en, en_US, en, pl, pl_PL, pl Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.7-050307-generic Pretty Productname: Linux Mint 19.3 Product Type: linuxmint Product Version: 19.3 Desktop: X-Cinnamon -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 371550] Allow the transform tool to work on multiple selected layers
https://bugs.kde.org/show_bug.cgi?id=371550 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #5 from Tymond --- Regarding the multiple selected layers option, I consulted with Dmitry and he said that yes, there should be no more technical difficulties than just creating a preview. It could be possible to make it work on all color labeled layers, too. (Which is, I think, closer to what the original reporter wanted - considering it's more persistent than selecting layers). In any case, it's on my TODO list, however I'm not sure if and when I will be able to implement this. It's high priority though - people often ask about it on reddit etc. If someone wants to take it and they are not sure how to implement it, I can help if needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #14 from scott --- I am still experiencing a black screen and frozen cursor. This is with meeting all prerequisites mapped out in David's blog post. Granted I am using an optimus laptop. If any specific log files would be helpful please let me know. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363331] Feature request: Krita restores settings after restart.
https://bugs.kde.org/show_bug.cgi?id=363331 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tymond --- > The memory is often full and I have to restart Krita. Maybe it would be a better idea to make a way to clear/free the undo/closed images memory instead? Otherwise this feature request needs discussion before it can be implemented. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368000] Sort the brush presets from latest to oldest? (Brush Preset History)
https://bugs.kde.org/show_bug.cgi?id=368000 Tymond changed: What|Removed |Added CC||jo.y.v...@gmail.com --- Comment #5 from Tymond --- *** Bug 374542 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374542] Brush present history in grid view
https://bugs.kde.org/show_bug.cgi?id=374542 Tymond changed: What|Removed |Added Resolution|--- |DUPLICATE CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED --- Comment #4 from Tymond --- Both bug 368000 and this bug report talk about two features: - grid mode for brush presets docker - resorting the brush presets to show the last used always on top Since the other bug report is older and contains a mockup, this one is marked as duplicate. *** This bug has been marked as a duplicate of bug 368000 *** -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #5 from Joan --- I just tried with one of the files (see attached the logs of your script), and the errors are the following: cvlc /media/jjuvan/TOSHIBA_FOTOS/Fotos/2019/agost/YDXJ0002.MP4 VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) [55a73b72d800] dummy interface: using the dummy interface module... Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory [7fc2b0d823b0] main decoder error: Timestamp conversion failed for 21354667: no reference clock [7fc2b0d823b0] main decoder error: Could not convert timestamp 0 for faad [7fc2b0cc1ae0] main decoder error: Timestamp conversion failed for 21390701: no reference clock [7fc2b0cc1ae0] main decoder error: Could not convert timestamp 0 for FFmpeg [7fc2b0cc1ae0] main decoder error: buffer deadlock prevented [7fc2b0d823b0] main decoder error: buffer deadlock prevented -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 --- Comment #4 from Joan --- Created attachment 129147 --> https://bugs.kde.org/attachment.cgi?id=129147=edit ffmpeg logs Relevant part of the logs generated with Johannes's script. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422652] New: Minimizing in multi-monitor environment buggy / Clip monitor disappears after loading view.
https://bugs.kde.org/show_bug.cgi?id=422652 Bug ID: 422652 Summary: Minimizing in multi-monitor environment buggy / Clip monitor disappears after loading view. Product: kdenlive Version: 20.04.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: bi...@ivdc.com Target Milestone: --- Created attachment 129146 --> https://bugs.kde.org/attachment.cgi?id=129146=edit Video of the issue SUMMARY When using in Multi-Monitor environment, the Clip monitor and Project monitor do not minimize or maximize when min/maxing the main kdenlive gui. If you Load Layout, it will work. But, then I found, that you have to Load layout TWICE to get the clip monitor to re-appear. See video attached. STEPS TO REPRODUCE 1. Launch kdenlive - Move Clip monitor to one screen, project monitor to the other 2. Minimize kdenlive 3. Note that only the main gui minimized 4. Restore kdenlive 5. Load Layout 6. Observe Clip monitor not showing. 7. Minimize kdenlive - it minimizes everything correctly 7. Load layout again - Clip monitor shows up - Minimizing works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #13 from David Edmundson --- The Qt version thing is very important. The bug fixed there matches the symptoms you're seeing. I don't know when Neon will upgrade. Potentially I could patch Neon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419534] Artifacts around the tile borders for edge detection filters
https://bugs.kde.org/show_bug.cgi?id=419534 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/679ebac38 |hics/krita/commit/e3c0816bc |cda1c500cd3013bf783787b1bed |11f990c546195ea63cfc5a37610 |e5de|7b82 --- Comment #4 from Dmitry Kazakov --- Git commit e3c0816bc11f990c546195ea63cfc5a376107b82 by Dmitry Kazakov. Committed on 08/06/2020 at 20:54. Pushed by dkazakov into branch 'master'. Fix border artifacts in edge-detection filters KisConvolutionPainter::applyMatrix() will automatically read more data outside the passed `areaSize` if it is needed for the kernel. There is no need to pass bigger area to the painter. M +8-3libs/image/kis_convolution_painter.h M +15 -29 libs/image/kis_edge_detection_kernel.cpp https://invent.kde.org/graphics/krita/commit/e3c0816bc11f990c546195ea63cfc5a376107b82 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419534] Artifacts around the tile borders for edge detection filters
https://bugs.kde.org/show_bug.cgi?id=419534 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/679ebac38 ||cda1c500cd3013bf783787b1bed ||e5de Resolution|--- |FIXED --- Comment #3 from Dmitry Kazakov --- Git commit 679ebac38cda1c500cd3013bf783787b1bede5de by Dmitry Kazakov. Committed on 08/06/2020 at 20:52. Pushed by dkazakov into branch 'krita/4.3'. Fix border artifacts in edge-detection filters KisConvolutionPainter::applyMatrix() will automatically read more data outside the passed `areaSize` if it is needed for the kernel. There is no need to pass bigger area to the painter. M +8-3libs/image/kis_convolution_painter.h M +15 -29 libs/image/kis_edge_detection_kernel.cpp https://invent.kde.org/graphics/krita/commit/679ebac38cda1c500cd3013bf783787b1bede5de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422626] Allow multiple pages ranges to print in Okular
https://bugs.kde.org/show_bug.cgi?id=422626 --- Comment #4 from Xavier Guillot --- Right, I just tested in on Linux Ubuntu (20.04). If I put "," instead of ";" to separate the ranges, I don't get the error message - I'll check again tomorrow if it's the same on Windows, I think I tried and got the error but I'm not sure. But on Linux, if I try to print on a file, whatever selection I put, even 1 range or one unique page, it always prints the whole document. If I select the option "Current page", it prints only this one. Same with the option "Print from page XX to page XX", it prints only the good range. On Evince, the print on file works well with the chosen ranges, so it's specific to Okular... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422052] "Full screen" screenshot mode is called "Entire desktop" in "Shortcuts" section of Spectacle settings and Global Shortcuts kcm
https://bugs.kde.org/show_bug.cgi?id=422052 Antonio changed: What|Removed |Added CC||antonio.prc...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Antonio --- Thanks for the report. Here's a patch: https://invent.kde.org/graphics/spectacle/-/merge_requests/4 Let's see if it will be merged into master :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #12 from Wyatt Childers --- Actually I did miss something, the Qt version note. I'm on 5.14.2. This seems to be the latest build available on neon? -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 402890] Menu items ‘Open selected files’/‘Open’ overwrites template files instead of creating translation files
https://bugs.kde.org/show_bug.cgi?id=402890 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #7 from Albert Astals Cid --- @Simon so the difference is that left clicking goes through ProjectWidget::slotItemActivated that calls ProjectModell::beginEditing //copies POT file to PO file and returns url of the PO file and then calls fileOpenRequested on it while right mouse button just calls fileOpenRequested on the files themselves. Personally i'm not totally sure that "Open" should be creating a new file, if not, we should add a new action for .pot files that is "Create .po and start editing" or something. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408634] [Wayland] Nvidia Black Screen
https://bugs.kde.org/show_bug.cgi?id=408634 --- Comment #11 from Wyatt Childers --- Confirming I have followed the setup on the wiki per: https://www.reddit.com/r/kde/comments/gz40tv/david_edmundson_busts_some_myths_of_nvidia_plasma/ftemb2f/ Also worth noting the wiki instructions are not compatible with fish shell -- I swapped back to bash to test, as the /etc/profile.d/kwin.sh script isn't executed with fish as your user shell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422602] In Kickoff favorites section, after right clicking on a item, there is a delay to show the menu
https://bugs.kde.org/show_bug.cgi?id=422602 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422651] New: Bad paragraph spacing
https://bugs.kde.org/show_bug.cgi?id=422651 Bug ID: 422651 Summary: Bad paragraph spacing Product: kmail2 Version: 5.14.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ppnmmw9zj...@absolutesix.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create an email with an HTML signature 2. Type some text 2. Hit the Enter Key twice to create a new paragraph 3. Type more text OBSERVED RESULT When the email is sent or saved the double line breaks are converted to this: SOME TEXT MORE TEXT The added "" creates huge whitespaces between each paragraph. EXPECTED RESULT A normal sized empty line between each paragraph. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void Linux & Manjaro with KDE Plasma (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This behavior is the same in both Void Linux and Manjaro. Kmail 5.13.x does not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422041] Add scroll animation on arrow keys
https://bugs.kde.org/show_bug.cgi?id=422041 --- Comment #3 from David Hurka --- I don’t think this is intended. It should be same, or reverse. I remember that I saw scroll animations for both arrow keys and page keys when I installed Okular 20.04. (Damaged my laptop then, so I can’t test it right now.) Currently, this is not configurable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422320] Loading Gradient Overlay layer style is broken
https://bugs.kde.org/show_bug.cgi?id=422320 --- Comment #14 from un...@seznam.cz --- Ok, thank you :) So I think that this is closed from my side now, I have nothing more to add. Thanks for explaining and testing it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422626] Allow multiple pages ranges to print in Okular
https://bugs.kde.org/show_bug.cgi?id=422626 --- Comment #3 from Albert Astals Cid --- The tooltip explains how to do it on the Linux version. Sorry if my previos comment wasn't clear -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422608] spectacle -solo capura todo (2 pantallas)
https://bugs.kde.org/show_bug.cgi?id=422608 Antonio changed: What|Removed |Added CC||antonio.prc...@gmail.com --- Comment #1 from Antonio --- Can you write that in English please? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 422394] Spectacle not being finalized when ran in background mode
https://bugs.kde.org/show_bug.cgi?id=422394 --- Comment #5 from Antonio --- (In reply to Nathan from comment #4) > I identified the problem, it was kinda me being dumb. In the notifications > triggers settings for Spectacle a had the "Run Command" checkbox checked, > but the text field to put the command in was empty. If I uncheck the > checkbox Spectacle just closes when the notification vanishes, otherwise it > does not closes (even with no command in the text box). > > I don't know if this was supposed to be that way, I'm really sorry if so. > Should I mark it as resolved? Nice! I'm not sure how that part of the notification settings (Run Command) should work, so I can't say if this is "works as designed". Might check with other programs.. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420755] Animated scroll transitions should respect global animation speed
https://bugs.kde.org/show_bug.cgi?id=420755 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=422629 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422629] Ability to disable "smooth scrolling", or at least recognize PageUp/PageDown during "smooth scrolling"
https://bugs.kde.org/show_bug.cgi?id=422629 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE See Also||https://bugs.kde.org/show_b ||ug.cgi?id=420755 Status|REPORTED|RESOLVED --- Comment #1 from David Hurka --- You’re not alone with your feelings. In 420755 someone already suggested respecting the global style settings; but I start to think that people actually wish this option for Okular, so the option creep argument won’t hold. I don’t like smooth scrolling too. It’s just smearing and flickering in my eyes, does not help to track the movement in any way. I wonder how many people would complain if we actually revert this. It’s like when you called someone at +12 333 12345, and then you want to call someone at +12 333 12349, but you have to wait until your phone is done with waking up all the people with numbers in between: +12 333 12346, +12 333 12347.23, 12 333 12347 + π/4, etc, and then someone angry from +12 333 12345 + e - √2 calls you back. (Share your weird comparisons here: https://bugs.kde.org/show_bug.cgi?id=422629) *** This bug has been marked as a duplicate of bug 422050 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 David Hurka changed: What|Removed |Added CC||ae@seven.systems --- Comment #6 from David Hurka --- *** Bug 422629 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 422649] Kontact starting problem on Pinebook Pro with Manjaro ARM newest patchlevel
https://bugs.kde.org/show_bug.cgi?id=422649 Uwe Herczeg changed: What|Removed |Added Summary|Kotact starting problem on |Kontact starting problem on |Pinebook Pro with Manjaro |Pinebook Pro with Manjaro |ARM newest patchlevel |ARM newest patchlevel -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422041] Add scroll animation on arrow keys
https://bugs.kde.org/show_bug.cgi?id=422041 --- Comment #2 from Orestis --- I see that I had not stated the okular version in the initial comment; my bad. Right now `okular --version` on my system yields 1.10.1 and the issue is still present. You stated that there should be scroll animations with both the Page and Arrow keys. Nevertheless, I am only seeing scroll animations for the Page keys. Using the Arrow keys results in instant jumps. Is this the intended configuration? Is it controllable in the settings? I don't think I have made any setting alterations regarding this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948
--- Comment #17 from Thadeu Penna ---
I tried here with forms enabled and the buttons still do not work on
presentation mode. Neither the one compiled here nor the attached file. Both
work on windowed mode.
(In reply to Yuri Chornoivan from comment #16)
> Created attachment 129145 [details]
> Example with buttons (works)
>
> (In reply to Thadeu Penna from comment #15)
> > (In reply to Yuri Chornoivan from comment #11)
> > > Created attachment 129141 [details]
> > > Test file (animate+beamer works in presentation mode)
> > >
> > > It may depend on the type of animation. At least, the attached file
> > > (pdfTeX
> > > 3.14159265-2.6-1.40.19, animate, beamer, poppler 0.88, okular from git
> > > master) works fine for me in the normal and presentation mode. The first
> > > attached file does not work at all in either of the modes.
> >
> > Could you try it with the buttons ?
>
> It depends on the forms enabling:
>
> Fresh start, forms enabled, with or without autoplay (not an opened
> recompiled PDF) - works
> Fresh start, forms disabled or recompile in vivo - does not work.
>
> Tex for this PDF:
>
> \documentclass[aspectratio=169]{beamer}
> \usepackage[utf8]{inputenc}
> \usepackage{animate}
> \usecolortheme{seahorse}
> \begin{document}
> \begin{frame}
> \frametitle{Test}
> \centering
> \animategraphics[loop,width=.5\linewidth,controls=all]{20}{Fourier-}{0}{92}
> \end{frame}
> \end{document}
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 422041] Add scroll animation on arrow keys
https://bugs.kde.org/show_bug.cgi?id=422041 --- Comment #1 from David Hurka --- I am a bit puzzled about this report. I understand it that Page Up/Down show smooth scroll animations, but Arrow Up/Down do an instant jump. Are you a new Okular user, or can you describe the changes you observed? AFAIK smooth scrolling was added in 1.10.0 and received a fix in 1.10.1; but applies to both Page and Arrow keys. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422609] Cursor leaves traces on 4k screens
https://bugs.kde.org/show_bug.cgi?id=422609 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422609] Cursor leaves traces on 4k screens
https://bugs.kde.org/show_bug.cgi?id=422609 Emmet O'Neill changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||emmetoneill@gmail.com --- Comment #5 from Emmet O'Neill --- FIXED: on master @ 9e9bfce29b68f87e25863ebcdf285a4c1dfe1120 Fixed OpenGL canvas rendering for High-DPI displays. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422080] Continuous view and multiple tabs
https://bugs.kde.org/show_bug.cgi?id=422080 --- Comment #2 from David Hurka --- I assume the behavior does not match Bug 421399? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422650] New: Crash when Desktop cube animation and window close shattering happen simultaneously
https://bugs.kde.org/show_bug.cgi?id=422650 Bug ID: 422650 Summary: Crash when Desktop cube animation and window close shattering happen simultaneously Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: smkoz...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-55-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I closed a window with the "window shatter" effect. While the effect was still happened, I tried to change the desktop using mouse wheel. Window shatter froze and desktop effects crashed. - Unusual behavior I noticed: Desktop effects crashed The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3841b87d00 (LWP 25409))] Thread 5 (Thread 0x7f381f05d700 (LWP 26191)): #0 0x7f384689d2c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f3846eabfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f384689d2c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f3846eabf68, cond=0x7f3846eabf90) at pthread_cond_wait.c:508 #2 0x7f384689d2c6 in __pthread_cond_wait (cond=0x7f3846eabf90, mutex=0x7f3846eabf68) at pthread_cond_wait.c:638 #3 0x7f3846db508a in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f3846db50af in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f3846896669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f3848a8f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f383a225700 (LWP 26188)): #0 0x7f3848a82d26 in __GI_ppoll (fds=0x7f383d68, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3847543589 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3847544af4 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f38474ee5cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3847327a45 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3846036319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3847328c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3846896669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f3848a8f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f383bfff700 (LWP 25444)): #0 0x7f3848a82d26 in __GI_ppoll (fds=0x7f383400e548, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3847543589 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3847544af4 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f38474ee5cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3847327a45 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3845a75efa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f3847328c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3846896669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f3848a8f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3841194700 (LWP 25434)): #0 0x7f3848a82c2f in __GI___poll (fds=0x7f3841193c28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f384724c917 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f384724e53a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f38414cb288 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f3847328c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3846896669 in start_thread (arg=) at pthread_create.c:479 #6 0x7f3848a8f323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3841b87d00 (LWP 25409)): [KCrash Handler] #6 0x7f38489b33eb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f3848992899 in __GI_abort () at abort.c:79 #8 0x7f38472efa99 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f384702f097 in () at /lib/x86_64-linux-gnu/libkwineffects.so.12 #10 0x7f383a2a7ae4 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #11 0x7f383a2a7c5f in () at
[okular] [Bug 421399] Different setting of continuous view mode per windows does not work correctly
https://bugs.kde.org/show_bug.cgi?id=421399 --- Comment #6 from David Hurka --- Your screencast makes it clear, thanks. I would describe it as: When I toggle Continuous in another window, the PageView in the first window freezes. When I continue toggling in the other window, PageView eventually unfreezes. Did you observe other kinds of “The first window should act strange”? Right now I don’t have an idea what could cause this. There are more changes planned to scrolling, so I will not investigate yet. (Besides having little time.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 422649] New: Kotact starting problem on Pinebook Pro with Manjaro ARM newest patchlevel
https://bugs.kde.org/show_bug.cgi?id=422649 Bug ID: 422649 Summary: Kotact starting problem on Pinebook Pro with Manjaro ARM newest patchlevel Product: kontact Version: 5.14.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: uherc...@mail.ru Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. start kontact 2. 3. OBSERVED RESULT app starts but hangs/freezes and is unusable. The single apps like kmail/korganizer could be started separately and are working flawlessly. Journalctl says: Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x88299820) ) Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber "" disconnected Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x881c3c90) ) Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x881c3c90) ) Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x88127bc0) ) Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x882d7b20) ) Jun 08 21:10:21 munin akonadiserver[1296]: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x88299b30) ) Jun 08 21:10:21 munin kernel: Purging 8388608 bytes Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x88299820) identified as "TagCacheMonitor - 187650858043648" Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x881c3c90) identified as "ETMCalendarMonitor - 187650858330464" Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x88127bc0) identified as "TagCacheMonitor - 187650858682448" Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x882d7b20) identified as "ItemMonitorMonitor - 187650859137952" Jun 08 21:10:22 munin akonadiserver[1296]: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x88299b30) identified as "TagCacheMonitor - 187650859766896" Jun 08 21:10:22 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21563, resource id: 37763433, major code: 3 (GetWindowAttributes), minor code: 0 Jun 08 21:10:22 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21887, resource id: 165675019, major code: 18 (ChangeProperty), minor code: 0 Jun 08 21:10:23 munin kded5[1122]: Registering ":1.131/StatusNotifierItem" to system tray Jun 08 21:10:23 munin plasmashell[1166]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_382(0xf415dd60, parent=0xf2c54820, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_382(0xf36caab0), which must be a sibling Jun 08 21:10:23 munin kwin_x11[1164]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22069, resource id: 165675019, major code: 18 (ChangeProperty), minor code: 0 Any tips for me? 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.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948
--- Comment #16 from Yuri Chornoivan ---
Created attachment 129145
--> https://bugs.kde.org/attachment.cgi?id=129145=edit
Example with buttons (works)
(In reply to Thadeu Penna from comment #15)
> (In reply to Yuri Chornoivan from comment #11)
> > Created attachment 129141 [details]
> > Test file (animate+beamer works in presentation mode)
> >
> > It may depend on the type of animation. At least, the attached file (pdfTeX
> > 3.14159265-2.6-1.40.19, animate, beamer, poppler 0.88, okular from git
> > master) works fine for me in the normal and presentation mode. The first
> > attached file does not work at all in either of the modes.
>
> Could you try it with the buttons ?
It depends on the forms enabling:
Fresh start, forms enabled, with or without autoplay (not an opened recompiled
PDF) - works
Fresh start, forms disabled or recompile in vivo - does not work.
Tex for this PDF:
\documentclass[aspectratio=169]{beamer}
\usepackage[utf8]{inputenc}
\usepackage{animate}
\usecolortheme{seahorse}
\begin{document}
\begin{frame}
\frametitle{Test}
\centering
\animategraphics[loop,width=.5\linewidth,controls=all]{20}{Fourier-}{0}{92}
\end{frame}
\end{document}
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 420953] Latte dock notification applet bug
https://bugs.kde.org/show_bug.cgi?id=420953 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Michail Vourlakos --- waiting info... -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 422439] All icons go white when touching the "Touching" settings in "From Windows" is enabled.
https://bugs.kde.org/show_bug.cgi?id=422439 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Michail Vourlakos --- known limitation that can be fixed manually from the user. Plasma does not offer any other solution. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419956] Export errors after a certain number of photos in the 2nd pass
https://bugs.kde.org/show_bug.cgi?id=419956 --- Comment #12 from Maik Qualmann --- Git commit d209aa4627e77b8c0edc72e1094d023af20f614c by Maik Qualmann. Committed on 08/06/2020 at 19:00. Pushed by mqualmann into branch 'master'. limit the Google Photos title to 1000 characters M +1-0core/dplugins/generic/webservices/google/gswindow.cpp https://invent.kde.org/graphics/digikam/commit/d209aa4627e77b8c0edc72e1094d023af20f614c -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345077] linux syscall execveat support (linux 3.19)
https://bugs.kde.org/show_bug.cgi?id=345077 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Mark Wielaard --- Thanks, finally pushed as: commit 6f6ff49ffa10da4e8027220d70791a72437846fd Author: Alexandra Hájková Date: Thu Apr 9 17:28:18 2020 +0200 Add support for execveat syscall Refactor the code to be reusable between execve and execveat syscalls. https://bugs.kde.org/show_bug.cgi?id=345077 I did add a sys-execveat.stdout.exp to make sure the echo command output is as expected and a check_execveat prereq program in case the execveat syscall isn't supported. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422648] KMail crash when moving window around/focusing
https://bugs.kde.org/show_bug.cgi?id=422648 Jay changed: What|Removed |Added CC||jay.aurab...@gmail.com Version|unspecified |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 422648] New: KMail crash when moving window around/focusing
https://bugs.kde.org/show_bug.cgi?id=422648 Bug ID: 422648 Summary: KMail crash when moving window around/focusing Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jay.aurab...@gmail.com Target Milestone: --- Application: kmail (5.13.2 (19.12.2)) Qt Version: 5.13.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.15-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: Tried running KMail outside KDE environment. I have kwalletd5 running in the background. KMail crashes intermittently. Sometimes it takes a while, sometimes pretty quick. Sometimes moving the KMail window to another workspace (awesome wm) kills it. Sometimes focusing to KMail kills it. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5b236f8340 (LWP 17252))] Thread 35 (Thread 0x7f5ab93b1700 (LWP 18991)): #0 0x7f5b305f91b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5b2a786dfa in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f5b2a787843 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f5b2a7879c1 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f5b2a73de61 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f5b2a740ee2 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f5b2a7417d4 in base::internal::SchedulerWorker::RunPooledWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f5b2a789d6a in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5b329c49d3 in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f5a95ffb700 (LWP 17502)): #0 0x7f5b305f91b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5b2a786dfa in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f5b2a787843 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f5b2a7879c1 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f5b2a73de61 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f5b2a74127b in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f5b2a7417d4 in base::internal::SchedulerWorker::RunPooledWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f5b2a789d6a in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f5b329c49d3 in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f5a69625700 (LWP 17354)): #0 0x7f5b329b9b6f in poll () from /lib64/libc.so.6 #1 0x7f5b2fbd5ace in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f5b2fbd5c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f5b32f12c23 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f5b32ec621b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f5b32d3a577 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f5b32d3b846 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f5b329c49d3 in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f5a6ac55700 (LWP 17341)): #0 0x7f5b305f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5b149141db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f5b14913cab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f5b305f2432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f5b329c49d3 in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f5a6b456700 (LWP 17340)): #0 0x7f5b305f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5b2a786cfc in base::ConditionVariable::Wait() () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f5b2a787850 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
[digikam] [Bug 419956] Export errors after a certain number of photos in the 2nd pass
https://bugs.kde.org/show_bug.cgi?id=419956 --- Comment #11 from hmueller --- Maybe this bug is different from Alains ... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422647] New: wrong conversion of integers to floats from project file
https://bugs.kde.org/show_bug.cgi?id=422647
Bug ID: 422647
Summary: wrong conversion of integers to floats from project
file
Product: kdenlive
Version: 20.04.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: rob...@riemann.cc
Target Milestone: ---
Dear all,
I have a very unusual use case. I create with a number of scripts from a json
file with image paths and their durations a half-broken minimal kdenlive file
to get a slideshow in sync with a webcam+audio stream.
As I do not know precisely which elements in the kdenlive file are necessary or
not, it is a bit complicated.
On my way to make it working somehow, I noticed that conversion from seconds to
"HH:mm:ss" format only works properly if seconds are a float type and it does
not work for integers.
My template:
${library[slide]}
`
If value[duration] is lets say 125, the value is not picked up. If it is
"125.00", it is correctly converted.
I fixed this problem for me with an explicit conversion to use two decimal
digits with .toFixed(2).
Thanks for making kdenlive.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948 --- Comment #15 from Thadeu Penna --- (In reply to Yuri Chornoivan from comment #11) > Created attachment 129141 [details] > Test file (animate+beamer works in presentation mode) > > It may depend on the type of animation. At least, the attached file (pdfTeX > 3.14159265-2.6-1.40.19, animate, beamer, poppler 0.88, okular from git > master) works fine for me in the normal and presentation mode. The first > attached file does not work at all in either of the modes. Could you try it with the buttons ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 419956] Export errors after a certain number of photos in the 2nd pass
https://bugs.kde.org/show_bug.cgi?id=419956 --- Comment #10 from Maik Qualmann --- Ok, that's interesting. I tested it with the Windows version this afternoon. There Exiv2 decodes it as a "binary comment". Here on Linux, the content is displayed as text and hex numbers. And the upload fails. Either some characters break the encoding, or the content is too long for Google. I have a look at it. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420779] Copy pasting issues with reference tool.
https://bugs.kde.org/show_bug.cgi?id=420779 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- So there are two features: - copy from one document to another (as reference images) - convert reference image to layer I would add another one: - convert layer to reference image -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388006] Tool for creating manga\comics grids
https://bugs.kde.org/show_bug.cgi?id=388006 --- Comment #6 from Tymond --- @Dyhia -- sorry, your comment was probably lost somewhere. If you still want to help, it would be better to hop on IRC with this link: https://kiwiirc.com/nextclient/irc.freenode.net/?nick=bugzilla|?#krita - note that (1) it's not logged (you won't see previous messages or any that were sent when you were not connected), (2) it's real-time chat and it's most active in European afternoon time. Alternatively you can go to krita-artists.org, there is Developers Questions subforum, maybe it would be a good place to start. We will help you but the bugzilla is not a good place to communicate :) Most development communication happens on IRC or on https://invent.kde.org/graphics/krita where the code patches are on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405604] Choose Settings profile on launch
https://bugs.kde.org/show_bug.cgi?id=405604 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- I wouldn't mind that either, considering the "clear settings" environment I often need to test things in. I think the "close Krita and reopen with the other profile" would still be viable. And the wish needs maybe technical discussion but it's clear from the user point of view, I think. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375785] Processing layers/filters inside groups with pass through could be disabled if group is invisible
https://bugs.kde.org/show_bug.cgi?id=375785 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Can you please check if it's still the case? Or maybe you could add a test file and say how you can see that they are processed unnecessarily. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422646] New: Crash when running script using qdbus to control terminal
https://bugs.kde.org/show_bug.cgi?id=422646
Bug ID: 422646
Summary: Crash when running script using qdbus to control
terminal
Product: yakuake
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: h...@kde.org
Reporter: dark...@nearce.com
Target Milestone: ---
Application: yakuake (3.0.5+)
Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.3.0-53-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18
-- Information about the crash:
- What I was doing when the application crashed:
I have a script that runs several commands based on qdbus. It does basically
the following:
INITIAL_ID=`qdbus org.kde.yakuake /yakuake/sessions
org.kde.yakuake.activeSessionId`
function addSession {
SESSION_ID=`qdbus org.kde.yakuake /yakuake/sessions
org.kde.yakuake.addSession`
qdbus org.kde.yakuake /yakuake/tabs setTabTitle $SESSION_ID "$1"
if [ ! -z "$2" ]; then
qdbus org.kde.yakuake /yakuake/sessions runCommandInTerminal $SESSION_ID
"$2"
fi
}
addSession "A" "cd A/"
addSession "B" "cd B/"
addSession "C" "cd C/"
qdbus org.kde.yakuake /yakuake/sessions org.kde.yakuake.removeSession
$INITIAL_ID
Sometimes when I use it this crash occurs.
-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcf18bdc300 (LWP 2611))]
Thread 4 (Thread 0x7fcee7884700 (LWP 25795)):
#0 0x7fcf12f350b4 in __GI___libc_read (fd=24, buf=0x7fcee7883bde,
nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:27
#1 0x7fcf07fd1021 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#2 0x7fcf0bdbda2e in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3 0x7fcf0bdbe4a0 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4 0x7fcf0bdbe560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5 0x7fcf0bdcc3c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6 0x7fcf08000318 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#7 0x7fcf0eaf86db in start_thread (arg=0x7fcee7884700) at
pthread_create.c:463
#8 0x7fcf12f4688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 3 (Thread 0x7fcefbdf5700 (LWP 2670)):
#0 0x7fcf12f350b4 in __GI___libc_read (fd=7, buf=0x7fcefbdf4b60,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1 0x7fcf0cd452b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fcf0cd000b7 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fcf0cd00570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fcf0cd006dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fcf138a07cb in QEventDispatcherGlib::processEvents
(this=0x7fcef4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6 0x7fcf1383fd2a in QEventLoop::exec (this=this@entry=0x7fcefbdf4d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#7 0x7fcf13650757 in QThread::exec (this=) at
thread/qthread.cpp:536
#8 0x7fcf14e58555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9 0x7fcf13651c2c in QThreadPrivate::start (arg=0x7fcf150d0da0) at
thread/qthread_unix.cpp:342
#10 0x7fcf0eaf86db in start_thread (arg=0x7fcefbdf5700) at
pthread_create.c:463
#11 0x7fcf12f4688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 2 (Thread 0x7fcf03803700 (LWP 2656)):
#0 0x7fcf12f39bf9 in __GI___poll (fds=0x7fcf03802ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fcf11016747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x7fcf1101836a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x7fcf063d8fd0 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x7fcf13651c2c in QThreadPrivate::start (arg=0x56264207df00) at
thread/qthread_unix.cpp:342
#5 0x7fcf0eaf86db in start_thread (arg=0x7fcf03803700) at
pthread_create.c:463
#6 0x7fcf12f4688f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 1 (Thread 0x7fcf18bdc300 (LWP 2611)):
[KCrash Handler]
#4 0x5626425ea5a0 in ?? ()
#5 0x7fcf13875db6 in QObject::disconnect (sender=0x5626423df730,
signal=, signal@entry=0x7fcf175f0a72 "2destroyed(QObject*)",
receiver=receiver@entry=0x56264240ebd0, method=0x562642a73e49
"_k_associatedWidgetDestroyed(QObject*)", method@entry=0x7fcf175f0978
"1_k_associatedWidgetDestroyed(QObject*)") at kernel/qobject.cpp:3121
#6 0x7fcf1758157c in KActionCollection::removeAssociatedWidget
(this=0x56264240ebd0, widget=, widget@entry=0x5626423df730)
[plasmashell] [Bug 422645] Often when Firefox starts, desktop content briefly shifts down and right
https://bugs.kde.org/show_bug.cgi?id=422645 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com Summary|Every time Firefox starts, |Often when Firefox starts, |desktop content briefly |desktop content briefly |shifts down and right |shifts down and right --- Comment #1 from Matej Mrenica --- Also opening a new window if FF is already running has the same result. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422158] Add canvas shortcuts and sliders for Fade
https://bugs.kde.org/show_bug.cgi?id=422158 --- Comment #6 from Tymond --- @Tyson yeah, I agree with that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422645] New: Every time Firefox starts, desktop content briefly shifts down and right
https://bugs.kde.org/show_bug.cgi?id=422645 Bug ID: 422645 Summary: Every time Firefox starts, desktop content briefly shifts down and right Product: plasmashell Version: 5.18.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matejm98m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY ...creating a black border on top and left side of the desktop ~30px wide. After FF finishes starting everything returns back to normal. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70 Qt Version: 5.15.0 ADDITIONAL INFORMATION Might be a Kwin issue or may belong somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422626] Allow multiple pages ranges to print in Okular
https://bugs.kde.org/show_bug.cgi?id=422626 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #2 from Jack --- My French may be rusty, but it looks like the instructions in the screen-shot specifically say a page number or one range of pages. I don't know if that is a limitation in the Windows build of Okular, or in the Windows PDF printer driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422158] Add canvas shortcuts and sliders for Fade
https://bugs.kde.org/show_bug.cgi?id=422158 --- Comment #5 from Tyson Tan --- @Tymond About that, here are my thoughts: 1) There are ONLY 6 parameters available at the moment. They can't even fill up half of the list space. It's far from getting too many. 2) Krita's toolbars are customized via the same type of dialogue and it has hundreds of actions available. I don't see how it may cause any problem with a filter input box. 3) Krita is a digital painting software. People have infinite ways of using it because we all have different workflows. Only the user knows what they want at a certain point of their creative process. We'd be grateful if all parameters can be accessed from the HUD. If it is technically just another instance of the same slider we have on the F5 panel, I don't see why we need to keep certain parameter away from the HUD. 4) We don't need to display EVERY parameter in the HUD "by default". The point of pop-up palette's parameter sliders is to let people choose 3 to 4 parameters from the list. The list didn't cause problem for Toolbar customization, so it shouldn't cause problem here either. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422626] Allow multiple pages ranges to print in Okular
https://bugs.kde.org/show_bug.cgi?id=422626 Albert Astals Cid changed: What|Removed |Added Platform|Other |MS Windows CC||aa...@kde.org, ||cullm...@kde.org, ||kde-wind...@kde.org --- Comment #1 from Albert Astals Cid --- You're writing the ranges wrong. See the tooltip for how to write them correctly. Ah wait, this is windows? I've no idea then, sorry. Please next time fill in Platform correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948 --- Comment #14 from Douglas --- (In reply to Yuri Chornoivan from comment #13) > Created attachment 129143 [details] > Minimal working example (tex+png) > > (In reply to Douglas from comment #12) > > (In reply to Yuri Chornoivan from comment #11) > > > Created attachment 129141 [details] > > > Test file (animate+beamer works in presentation mode) > > > > > > It may depend on the type of animation. At least, the attached file > > > (pdfTeX > > > 3.14159265-2.6-1.40.19, animate, beamer, poppler 0.88, okular from git > > > master) works fine for me in the normal and presentation mode. The first > > > attached file does not work at all in either of the modes. > > > > In my case it depends on the animation's frame rate, have you tried changing > > the frame rate of your file? in my case it stops working in presentation > > mode with 19fps or more > > Works fine for 19 and 40 fps. Minimal working example (tex+png) attached. Your attached file is not working in presentation mode with 40 fps here, okular 1.10.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415907] Python Plugin Manager Icon is Missing
https://bugs.kde.org/show_bug.cgi?id=415907 Tymond changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422629] Ability to disable "smooth scrolling", or at least recognize PageUp/PageDown during "smooth scrolling"
https://bugs.kde.org/show_bug.cgi?id=422629 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||keziolio...@gmail.com, ||oliver.san...@tu-dresden.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 --- Comment #59 from Maarten ter Huurne --- (In reply to Andreas Nordal from comment #58) > Nobody mentioning bracketed paste? I had never heard of it until you mentioned it. I enabled it in ~/.inputrc and now bash indeed waits for an explicit Enter before executing anything. This is awesome! Why isn't this enabled by default in shells and/or readline? -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 422603] Crash when pressing shift+tab
https://bugs.kde.org/show_bug.cgi?id=422603 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Albert Astals Cid --- Your katomic is old, update to something that doesn't use a katomic from more than 2 years ago or install katomic from flathub https://flathub.org/apps/details/org.kde.katomic *** This bug has been marked as a duplicate of bug 366396 *** -- You are receiving this mail because: You are watching all bug changes.
[katomic] [Bug 366396] KAtomic crashes upon Shift-Tab key combo
https://bugs.kde.org/show_bug.cgi?id=366396 Albert Astals Cid changed: What|Removed |Added CC||calend...@gmail.com --- Comment #5 from Albert Astals Cid --- *** Bug 422603 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 227129] Stroke vectors with Krita raster brush engines
https://bugs.kde.org/show_bug.cgi?id=227129 anim...@gmail.com changed: What|Removed |Added CC||anim...@gmail.com --- Comment #3 from anim...@gmail.com --- Note: actually we also already have a way to trace vectors directly: Select vector shape (from a vector layer), and use menu Edit - Stroke selected shapes to trace the shapes with selected brushes. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 422641] Difficulty Window is not relative to main window
https://bugs.kde.org/show_bug.cgi?id=422641 Albert Astals Cid changed: What|Removed |Added Priority|NOR |VLO CC||aa...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 397948] Animation stops working in presentation mode
https://bugs.kde.org/show_bug.cgi?id=397948 --- Comment #13 from Yuri Chornoivan --- Created attachment 129143 --> https://bugs.kde.org/attachment.cgi?id=129143=edit Minimal working example (tex+png) (In reply to Douglas from comment #12) > (In reply to Yuri Chornoivan from comment #11) > > Created attachment 129141 [details] > > Test file (animate+beamer works in presentation mode) > > > > It may depend on the type of animation. At least, the attached file (pdfTeX > > 3.14159265-2.6-1.40.19, animate, beamer, poppler 0.88, okular from git > > master) works fine for me in the normal and presentation mode. The first > > attached file does not work at all in either of the modes. > > In my case it depends on the animation's frame rate, have you tried changing > the frame rate of your file? in my case it stops working in presentation > mode with 19fps or more Works fine for 19 and 40 fps. Minimal working example (tex+png) attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422644] New: It's not clear what the values shown by the new Hard Disk Activity widget mean
https://bugs.kde.org/show_bug.cgi?id=422644 Bug ID: 422644 Summary: It's not clear what the values shown by the new Hard Disk Activity widget mean Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129144 --> https://bugs.kde.org/attachment.cgi?id=129144=edit screenshot SUMMARY There is no info like B/s, KiB/s or MiB/s appended the values. See the attached screenshot please. EXPECTED RESULT B/s, KiB/s or MiB/s should be appended to the values. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 227129] Stroke vectors with Krita raster brush engines
https://bugs.kde.org/show_bug.cgi?id=227129 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #2 from Tymond --- Right now it's possible to be done this way: 1. make a vector shape 2. convert to vector selection: Select -> Convert Shapes to Vector Selection 3. select the brush 4. select the selection tool (any one of them) 5. right-click -> Transform -> Stroke Selection -> Current Brush. Press OK. The problem: - too many steps? (no way to stroke just vector shapes, one needs to convert them to selection first). - it's not automatic; after a change in vector shapes, one would need to make it into a selection and apply the stroke again. The feature request is talking about a much more advanced system, it seems. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418478] Okular snap dead keys don't work
https://bugs.kde.org/show_bug.cgi?id=418478 --- Comment #5 from Fernando --- I hope it's acceptable that I bump this bug report ;) I've noticed that the snap is not even up-to-date. An update could be a good chance to look at this bug :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388775] Dont add filename extenstion to imported layers
https://bugs.kde.org/show_bug.cgi?id=388775 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- This wish was untouched; I guess it needs at least some other person confirming that it would be a good idea, considering it's not about adding new features bug changing the behaviour of an existing one. I'm undecided which way I would prefer it. -- You are receiving this mail because: You are watching all bug changes.
