[frameworks-knotifications] [Bug 409676] some notifications no more stored in kde notifier history
https://bugs.kde.org/show_bug.cgi?id=409676 --- Comment #1 from Philippe ROUBACH --- List of notifications no more in kde notifier history and which must be in it: lucky backup : - beginning of backup - end of backup chrome using web.skype.com : - "you are disconnected" chrome using messages.google.com : - receiving an SMS For lucky backup this problem occurred around the update to kde frameworks 5.59.0 and kde apps 19.04.2 For chrome : - older than lucky backup - hypothesis: a plasma integration plugin problem ? I will complete this list as soon as I will encounter other cases. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409678] improvement suggestion for dhat
https://bugs.kde.org/show_bug.cgi?id=409678 --- Comment #2 from plasm...@gmx.net --- Created attachment 121461 --> https://bugs.kde.org/attachment.cgi?id=121461&action=edit patch against git VALGRIND_3_14_0-225-g514f89938 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409678] improvement suggestion for dhat
https://bugs.kde.org/show_bug.cgi?id=409678 Julian Seward changed: What|Removed |Added CC||n.netherc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409678] improvement suggestion for dhat
https://bugs.kde.org/show_bug.cgi?id=409678 --- Comment #3 from plasm...@gmx.net --- (In reply to Philippe Waroquiers from comment #1) > The attached patch is in an unusual format, e.g. contains various control > characters. whoops, my fault, I wasn't aware of that the "git diff" colour output is also present when redirecting to a file, did it explicitly without. > > Also, what is the idea that the patch is implementing ? As I said it not only tells which byte was accessed, but also in what way (read/write) > > Seems there is no doc changed, no test changed. I wasn't aware of that its necessary to do all this, you can then close this ticket, I was just sharing our changes in the hope it might be useful for other people that want to know the same information. > > So, that makes it not easy to see what you propose to add. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409699] Strange menu name
https://bugs.kde.org/show_bug.cgi?id=409699 --- Comment #3 from Christian Gruber --- IMHO, a HDRI is a picture that is calculated from many different pictures, and a pseudo HDRI is calculated from a single picture with a high color depth, like a RAW. Do you have another definition? And this menu entry should be translated. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409367] exit_group() after signal arriving to thread waiting in futex() causes hangs
https://bugs.kde.org/show_bug.cgi?id=409367 --- Comment #5 from Allison Karlitskaya --- (In reply to Philippe Waroquiers from comment #4) > Pushed as 63a9f0793 Thanks very much, Philippe. A few questions, if you don't mind: 1) is there any workaround to this problem that you can imagine (in terms of commandline flags, etc.) that void avoid the problem other than to update valgrind to a version that includes this patch? Our current workaround is to add a sleep on the main thread before exit, and I'd like to remove that ASAP. 2) when is this patch likely to appear in a release? when is it likely to appear in a stable release? 3) do you think this patch is suitable for backporting/vendor-patching for distro packages? Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409706] KDE crashed on startx, but succeded after a minute
https://bugs.kde.org/show_bug.cgi?id=409706 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Kai Uwe Broulik --- Crashes in the nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401366] I get duplicate notifications for wifi connection to KDEConnect and phone calls.
https://bugs.kde.org/show_bug.cgi?id=401366 kde...@2hh.at changed: What|Removed |Added CC||kde...@2hh.at Version|1.3.3 |1.3.4 Platform|Neon Packages |Ubuntu Packages --- Comment #4 from kde...@2hh.at --- Sice some weeks I too get a around dozen popup messages for each call and sms my phone receives. My Android app is the most recent one, kdeconnect version is 1.3.4-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409218] [Wayland] Spectacle does not take a screenshot when "Take a new screenshot" button is clicked
https://bugs.kde.org/show_bug.cgi?id=409218 David Redondo changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/spe ||ctacle/4f1e7fa2302387244cfe ||a2f9fd7b98728b4e9781 --- Comment #2 from David Redondo --- Git commit 4f1e7fa2302387244cfea2f9fd7b98728b4e9781 by David Redondo. Committed on 11/07/2019 at 08:26. Pushed by davidre into branch 'master'. Fix on click not working Summary: When on click is enabled the timeout is always set to -1. This breaks the logic inside captureScreenshot to display the progressbar in the taskmanager. Test Plan: Check on click or use spectacle in a wayland session Reviewers: #spectacle, nicolasfella, ngraham Reviewed By: #spectacle, ngraham Subscribers: ngraham, anthonyfieroni Tags: #spectacle Differential Revision: https://phabricator.kde.org/D22148 M +6-0src/Gui/KSMainWindow.cpp https://commits.kde.org/spectacle/4f1e7fa2302387244cfea2f9fd7b98728b4e9781 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409702] Invalid gdb version check
https://bugs.kde.org/show_bug.cgi?id=409702
--- Comment #1 from Ivan Stepanov ---
[user@pc ~]$ cat .gdbinit
python
import sys
sys.path.append('/home/user/.config/Epic/GDBPrinters/')
from UE4Printers import register_ue4_printers
register_ue4_printers(None)
print("Registered pretty printers for UE4 classes")
end
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 409701] krita crashes in the loading page after saying loading main window and then crashes
https://bugs.kde.org/show_bug.cgi?id=409701 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Component|Animation |General Status|REPORTED|NEEDSINFO Platform|Other |MS Windows --- Comment #1 from Boudewijn Rempt --- Please give us information about your system: * which version of Windows do you have? * What GPU do you have? * Which driver do you have installed for the GPU? * The output of the Display tab of the dxdiag utility Please also try to make a debug log. Start debugview (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview), then start Krita. Append the output of debugview to this bug report. Please also try to make a crash log. Download both zip files from https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/, first copy the contents of the krita zip to, say, your desktop, then copy the contents of the dbg zip into the unzipped Krita folder. Follow https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw to find the crash log. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Peter Humphrey changed: What|Removed |Added CC||pe...@prh.myzen.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409709] New: KDE Plasma crashed upon disconnecting from a network
https://bugs.kde.org/show_bug.cgi?id=409709 Bug ID: 409709 Summary: KDE Plasma crashed upon disconnecting from a network Product: plasmashell Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: isirase...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.3) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.2.0-arch2-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was disconnecting from both a mobile broadband connection and a Wi-Fi hotspot when Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3f3bc3e880 (LWP 2030))] Thread 21 (Thread 0x7f3ee1c60700 (LWP 12280)): #0 0x7f3f3fdf8415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3f40b2a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3f40b2a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3f428f87bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3f428f8a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f3f40b24520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f3f3fdf257f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3f407b30e3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f3ee1320700 (LWP 12279)): #0 0x7f3f3fdf8415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3f40b2a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3f40b2a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3f428f87bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3f428f8a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f3f40b24520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f3f3fdf257f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3f407b30e3 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7f3ee3420700 (LWP 4728)): [KCrash Handler] #6 0x7f3f285cfafe in () at /usr/lib/qt/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #7 0x7f3f40d1db70 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #8 0x7f3f4294e2c3 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #9 0x7f3f428f4c0b in () at /usr/lib/libQt5Quick.so.5 #10 0x7f3f428f89d8 in () at /usr/lib/libQt5Quick.so.5 #11 0x7f3f40b24520 in () at /usr/lib/libQt5Core.so.5 #12 0x7f3f3fdf257f in start_thread () at /usr/lib/libpthread.so.0 #13 0x7f3f407b30e3 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7f3ef8c37700 (LWP 4580)): #0 0x7f3f3fdf8415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3f40b2a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3f40b2a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3f21810479 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3f21814099 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3f2180f6ad in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3f218140f2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f3f2180f6ad in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f3f218120e9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f3f40b24520 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3f3fdf257f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3f407b30e3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f3ef9438700 (LWP 4579)): #0 0x7f3f3fdf8415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3f40b2a5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3f40b2a692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3f21810479 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f3f21814099 in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f3f2180f6ad in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f3f218140f2 in () at
[okular] [Bug 409710] New: Continuous view gets stuck when multiple tabs are used
https://bugs.kde.org/show_bug.cgi?id=409710 Bug ID: 409710 Summary: Continuous view gets stuck when multiple tabs are used Product: okular Version: 1.6.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: mebus.in...@mail.ru Target Milestone: --- SUMMARY Often I have to view PDFs of slides and also lecture notes at the same time. I want to view the slides in non-continuous mode while I read the lecture notes in continuous mode. Unfortunately the non-continuous sometimes gets stuck and I have to toggle it form non-continuous to continuous and from non-continuous to continuous again to be able to move the document. This is really annoying. I am also not shure if Okular remmebers the view mode per tab correctly. STEPS TO REPRODUCE 1. Open two documents 2. set one to continuous and the other one to non-continuous 3. switch between the two 4. try to scroll I would be very thankful if this bug could be fixed soon. My Okular version is 1.6.2 on Fedora 29 amd64. Thank you very much Mebus -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409710] Continuous view gets stuck when multiple tabs are used
https://bugs.kde.org/show_bug.cgi?id=409710 Mebus changed: What|Removed |Added CC||mebus.in...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409649] Clicking somewhere in panel sometimes opens unrelated tray item
https://bugs.kde.org/show_bug.cgi?id=409649 --- Comment #3 from Swipe --- (In reply to David Edmundson from comment #2) > When this happens is the panel responding to other visual updates? Is the > clock still changing for example? When this happens the panel continues to respond as normal. The behaviour only manifests itself when right clicking to interact with an app in the panel. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #11 from Fabian Vogt --- (In reply to Michael from comment #7) > @Josh Freeno > It's not Arch specific just because Arch devss don't temper with plasma, > these packages are from upstream. It's not about Arch devs introducing bugs, it could be a bug with a specific fontconfig version in Arch as well, compile options, etc. > The reason nobody talks about it is > because most of the distro don't have that fresh plasma yet. On Tumbleweed I don't see this bug. There are some other weirdnesses though like the config file changing layout sometimes, but nothing like adding an exclusion range without clicking the checkbox. > Here is my font config. It does not appear broken. Can you upload a fonts.conf while it's "broken"? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 248807] Report with a long backtrace can't be sent (bugzilla 65k limit per comment)
https://bugs.kde.org/show_bug.cgi?id=248807 Harald Sitter changed: What|Removed |Added CC||edwardw...@gmail.com --- Comment #16 from Harald Sitter --- *** Bug 385721 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 385721] Unable to submit but reports with more than 65,535 characters.
https://bugs.kde.org/show_bug.cgi?id=385721 Harald Sitter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 248807 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409711] New: Widget popups not visible when they were already opened
https://bugs.kde.org/show_bug.cgi?id=409711 Bug ID: 409711 Summary: Widget popups not visible when they were already opened Product: plasmashell Version: 5.16.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: jgrul...@redhat.com Target Milestone: 1.0 Created attachment 121462 --> https://bugs.kde.org/attachment.cgi?id=121462&action=edit Screenshot of the issue SUMMARY If I open any widget for the first time, I can see its content just fine, but making second and other attempts results into showing a popup with an empty content with a weird glitch on second screen. STEPS TO REPRODUCE 1. Open any widget (e.g. calendar) 2. Open it again OBSERVED RESULT See attached screenshot. EXPECTED RESULT See the widget content properly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: Plasma 5.16.2 KDE Frameworks Version: 5.59 Qt Version: 5.12.4 (+ backported patches for qtwayland) ADDITIONAL INFORMATION I have a setup with three screens, the first one is my laptop with 4k screen (2x scaling set), rest of screens are regular full HD displays (no scaling). I think this issue is not reproducible or not reproducible that often when I have just the laptop screen, I will verify. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409711] Widget popups not visible when they were already opened
https://bugs.kde.org/show_bug.cgi?id=409711 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- Just tested with single screen and the issue is not reproducible, only in multi-screen setup and I think I have seen this issue even with older Plasma versions (definitely with Plasma 5.15.x). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 408505] What is the purpose of the "Multiple Layouts Warning" dialog ?
https://bugs.kde.org/show_bug.cgi?id=408505 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Michail Vourlakos --- a full explanation why I think this dialog is important: Some info concerning this... The Multiple layouts mode is a special mode that combines multiple layouts together in order to assign them in different Activities and in the upcoming v0.9 in order to enhance that and give the user the freedom to have shared panels/docks for different Layouts... That will be called "Shared" Layouts... All this will be presented in the audience the upcoming months when the GUI way to support that is available, currently the user has to edit the layouts file by himself. Concerning the mentioned message and its relation to Multiple mode. Plasma can not distinguish different layouts runtime BUT it supports under X11 having windows at different Activities. In order for Latte to achieve this, it tricks Plasma infrastructure and the combination of multiple layouts is presented to it as a single casual layout. All this is happening through ~/.config/latte/.multiple-layouts_hidden.layout.latte file. For example lets say that Latte wants to present three different layouts [A], [B] and [C]. When Latte starts the multiple layouts hidden file is empty. The Layout A first is loaded into multiple layouts file. The Layout B before is added into the multiple layouts file must first update itself concerning applet ids, containment ids etc... in order to not confllict with [A] and create crashes. After Layout B has updated its settings to not conflict with A it is added into the multiple layouts file. When Layout C must be loaded also it must do exactly what B did in order to not conflict neither with A or B. In the end of the process, A,B,C have been loaded in multiple layouts file and live in there as long as Latte runs. When Latte will close itself properly all three layouts will return their settings in to their corresponding original layout files and the .multiple-layouts file should be empty from any layout settings. If things go wrong for example Latte crashed or did not close properly in the end then the next time it will start the first thing to check is the multiple layouts hidden file. If in there there are layout settings even though it shouldnt the mentioned message appears BUT of course Latte is trying to protect you by completing properly the process to empty the .multiple layouts hidden file and return the layout settings to their original files. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 398257] Weird Black Line Appears Above the Dock On Startup
https://bugs.kde.org/show_bug.cgi?id=398257 Michail Vourlakos changed: What|Removed |Added Status|REOPENED|CONFIRMED Severity|major |normal Version|0.8.0 |git (master) --- Comment #2 from Michail Vourlakos --- Reopening in order to keep a more visible tracking for this. Concerning my last findings in my system this is produced when the View::Window::Geometry changes TOO much e.g. during startup OR view changing edge location. What probably happens is that the window geometry changes and the window is masked before the entire window has been painted fully transparent from Qt. That points that this is a Qt+X11 issue, in wayland the issue does not appear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 Claudio changed: What|Removed |Added Version|5.4.2 |5.12.7 CC||claudiolancone...@gmail.com Platform|Other |Kubuntu Packages --- Comment #47 from Claudio --- The icons are rearranged after every reboot. Kubuntu 18.04.2 desktop in folder view mode. The icons are application.desktop used to launch my applications. I attach .config/plasma-org.kde.plasma.desktop-appletsrc files that get changed by the system on logout/shutdown. The workaround I found is to login to console with CTRL-ALT-F2 restore manually the good .config/plasma-org.kde.plasma.desktop-appletsrc file and then login to kde plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #48 from Claudio --- Created attachment 121463 --> https://bugs.kde.org/attachment.cgi?id=121463&action=edit The original and working .config/plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #49 from Claudio --- Created attachment 121464 --> https://bugs.kde.org/attachment.cgi?id=121464&action=edit The modified .config/plasma-org.kde.plasma.desktop-appletsrc after reboot with icons rearranged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #33 from Dmitry Kazakov --- Could you test this one as well? I guess I managed to reproduce it on my system... https://yadi.sk/d/rjvDg4K_T_vLoA -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408656] Menu bar in Konsole cannot be shown
https://bugs.kde.org/show_bug.cgi?id=408656 --- Comment #9 from Sektor van Skijlen --- Found the root cause of the problem. It's unrelated to Konsole. The key thing is the setting in: System Settings/Widget Style/Fine Tuning/Menubar/Menubar style=Application Menu Widget When it's set to this value, the menu in the application will not appear. After changing to "In application" everything is ok. Also, this setting and the menu widget is something completely retarded. I found this Application Menu Widget in the widgets on the panel, it theoretically works, but it expands only the contents of the "File" menu. Other parts are not available - at least this is the situation in Konsole. Still, the problem with non-saved profiles remains. I'll try to report it separately, you can close this one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408594] color saturation in blurred regions is higher than expected
https://bugs.kde.org/show_bug.cgi?id=408594 --- Comment #35 from David de Cos --- Thanks, that worked. Although, lowering the noise strength to the minimum is what did the trick, not blur strength. I remember this setting did absolutely nothing before updating to 5.16.3, so I had it at a random value. Now I've lowered it to the minimum, since all that increasing it does (as far as my eyes see, at least) is create more and whiter grains. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409695] pasting URI in composer doesnt add href in richtextmode
https://bugs.kde.org/show_bug.cgi?id=409695 --- Comment #3 from Christoph --- nice performance :-) what do you think to add sftp:// fish:// tel: as well ? br -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409695] pasting URI in composer doesnt add href in richtextmode
https://bugs.kde.org/show_bug.cgi?id=409695 --- Comment #4 from Christoph --- (In reply to Christoph from comment #3) > nice performance :-) what do you think to add > > sftp:// > fish:// > tel: > > as well ? > > br along with webdavs:// imaps:// :-D -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 409712] New: add
https://bugs.kde.org/show_bug.cgi?id=409712 Bug ID: 409712 Summary: add Product: plasma-browser-integration Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: philippe.roub...@free.fr Target Milestone: --- there was a useful firefox addon "KDE wallet password integration" https://addons.mozilla.org/en-US/firefox/addon/kde-wallet-password-integratio/ but now it's dev "Guillermo Molina" uses no more FF and abandoned the addon development he says "I don't use firefox any more, but I will try to make the plugin work again" see here http://kde-apps.org/content/show.php?content=116886&forumpage=4 it would be a good thing kde keeps on going to develop this addon or as chromium integrates kwallet technology. It seems there is no more any source of this add-on. All links to the source are obsolete. There is nothing now at dev website about this add-on. Happily someone saves the source here. https://github.com/SicVolo/firefox-kde5-wallet It's the source + a fix according the add-on is compliant with qt < 5.7 because the original source is compliant with qt >= 5.7 It is not signed. the original source get 1.3 version number this fork gets 1.3.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409699] Strange menu name
https://bugs.kde.org/show_bug.cgi?id=409699 --- Comment #4 from Maik Qualmann --- A pseudo HDR is created from a single image where several images with different exposures are created by image processing. These are then processed like a bracketing series by a camera. (In reply to Christian Gruber from comment #3) > And this menu entry should be translated. Yes, certainly it should be translated. Unfortunately the translation was lost due to the conversion to plugins and has to be inserted again. Only this is not our job. DigiKam is translated in many languages. I know that the German team has a lot of work and digiKam is a pretty big project with quite specific technical terms. They are always looking for people who can help. Maik -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408656] Menu bar in Konsole cannot be shown
https://bugs.kde.org/show_bug.cgi?id=408656 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 209707] Add the option to be able to "pin" tabs.
https://bugs.kde.org/show_bug.cgi?id=209707 tomplatz changed: What|Removed |Added CC||tomplatz...@gmail.com --- Comment #2 from tomplatz --- Created attachment 121465 --> https://bugs.kde.org/attachment.cgi?id=121465&action=edit 128 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 409713] New: Password not hidden on main screen when Thunderbolt screen is connected
https://bugs.kde.org/show_bug.cgi?id=409713 Bug ID: 409713 Summary: Password not hidden on main screen when Thunderbolt screen is connected Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: robin.chr...@stud.tu-darmstadt.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE / OBSERVED RESULT Can't give precise information on that. All I can say is: I managed to install the nvidia-drivers 430 on my Lenovo P52 with an external Thunderbolt screen (ASUS MB16AC) connected. When I rebooted, the login dialog on the external screen was preselected (not the laptop screen, which is the main screen). When I now enter the password in the password dialog on the main screen, *the entered password is not censored*! It's visible in cleartext. EXPECTED RESULT Password should be censored! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04 KDE Plasma Version: Plasma 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel 5.0.0-20-generic -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409714] New: Krita incorrectly parses NetPBM images, converting them results in crash
https://bugs.kde.org/show_bug.cgi?id=409714 Bug ID: 409714 Summary: Krita incorrectly parses NetPBM images, converting them results in crash Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: a...@amyspark.me Target Milestone: --- SUMMARY Krita 4.2.1 in Windows 10 is unable to read properly NetPBM images, it shows them as a 0xN image OR a NxM image with incorrect colors. However, the thumbnail in the Recent Files section is correct. Attempting to convert such an image after opening results in a crash (Krita closes without a DrMingw dialog). I attach two samples. One of them was extracted from the Wikipedia page on NetPB, and the other was generated following the tutorial mentioned below. STEPS TO REPRODUCE 1. Follow the tutorial here https://in1weekend.blogspot.com/, or grab a P3 ASCII image online. 2. Open any of them with Krita. 3. Close the image. OBSERVED RESULT Recent Files displays correctly the image thumbnail, as opposed to the canvas. If you try converting the image, Krita will crash. EXPECTED RESULT Everything works correctly. SOFTWARE/OS VERSIONS Windows: Windows 10 v1809 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409714] Krita incorrectly parses NetPBM images, converting them results in crash
https://bugs.kde.org/show_bug.cgi?id=409714 --- Comment #2 from L. E. Segovia --- Created attachment 121467 --> https://bugs.kde.org/attachment.cgi?id=121467&action=edit Sample image from the tutorial (chapter 11) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409714] Krita incorrectly parses NetPBM images, converting them results in crash
https://bugs.kde.org/show_bug.cgi?id=409714 --- Comment #1 from L. E. Segovia --- Created attachment 121466 --> https://bugs.kde.org/attachment.cgi?id=121466&action=edit Sample image from Wikipedia -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409715] New: KWin crash
https://bugs.kde.org/show_bug.cgi?id=409715 Bug ID: 409715 Summary: KWin crash Product: kwin Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: szymondud...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.3) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.2.0-arch2-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: After Alt + Tab -> Show All Applications . KWin crashing sometimes in this combination. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5aa6675880 (LWP 1247))] Thread 7 (Thread 0x7f59fbfff700 (LWP 7179)): #0 0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f5aa6fbcfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f5aa6f665ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5aa54288f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f5aa6d9a520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f5a87e7f700 (LWP 4490)): #0 0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f5aa6fbcfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f5aa6f665ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5aa6d9a520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f5a9cfb7700 (LWP 2940)): #0 0x7f5aa5caf415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5aa6da05a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f5aa6da0692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f5aa57c77bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7f5aa57c7a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f5aa6d9a520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f5a8767e700 (LWP 1441)): #0 0x7f5aa5caf415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f5aa6808edc in () at /usr/lib/libQt5Script.so.5 #2 0x7f5aa6808ef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f5a8700 (LWP 1361)): #0 0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f5aa6fbcfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f5aa6f665ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5aa54288f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f5aa6d9a520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5a9e1cf700 (LWP 1309)): #0 0x7f5aa8499756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f5aa6fbb913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f5aa6fbcfa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f5aa6f665ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f5aa6d992f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f5aa4e45b37 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f5aa6d9a520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f5aa5ca957f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f5aa84a40e3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5aa6675880 (LWP 1247)): [KCrash Handler] #6 0x55eb170c6630 in () #7 0x7f5aa81b0d22 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib/libkwin.so.5 #8 0x000
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #12 from Michael --- OK. I opened systemsettings, chose 'Fonts', closed systemsettings, open Dolphin and that's how list of files in ~ looks now - https://i.imgur.com/OcpvZqG.png fonts.conf ~/.fonts true hintslight rgb true 0 297 false 0 396 false -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409695] pasting URI in composer doesnt add href in richtextmode
https://bugs.kde.org/show_bug.cgi?id=409695 --- Comment #5 from Laurent Montel --- I will add them soon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 409712] add
https://bugs.kde.org/show_bug.cgi?id=409712 --- Comment #1 from Kai Uwe Broulik --- That extension uses Firefox' old XPI extension API? I don't think we have the neccessary APIs in Web Extensions to provide seamless integration. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 409623] After login green flicker
https://bugs.kde.org/show_bug.cgi?id=409623 --- Comment #1 from Bennet --- Updated KDE Plasma to 5.16.3: issues still there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #13 from Bhushan Shah --- Can you also upload ~/.config/kdegloabls? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409711] Widget popups not visible when they were already opened
https://bugs.kde.org/show_bug.cgi?id=409711 Jan Grulich changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from Jan Grulich --- David, this seems to be related to your Qt fix https://codereview.qt-project.org/c/qt/qtwayland/+/265999. With this applied on top of Qt 5.12.4, I can reproduce it, if I disable that patch in our qtwayland in Fedora, then it's not happening. Problem is that without that patch I have problem with menus showing up (https://bugreports.qt.io/browse/QTBUG-76324). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409699] Strange menu name
https://bugs.kde.org/show_bug.cgi?id=409699 --- Comment #5 from Christian Gruber --- The program has no means to determine whether the pictures to combine are made out of a single picture or are different pictures taken with different exposures. So it cannot say whether it creates a pseudo or a real HDRI. The only thing that the program knows for sure is THAT it creates a HDRI. So I think it is wrong to state that it is a pseudo HDRI. I can help in the translation to German, but I am no professional translator. Besides that, I cannot provide much work units. -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 409716] New: Support for ToastGenericHeroImage (big image)
https://bugs.kde.org/show_bug.cgi?id=409716 Bug ID: 409716 Summary: Support for ToastGenericHeroImage (big image) Product: Snoretoast Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vonr...@kde.org Reporter: vonr...@kde.org Target Milestone: --- https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/toast-schema#toastgenericheroimage -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 409716] Support for ToastGenericHeroImage (big image)
https://bugs.kde.org/show_bug.cgi?id=409716 --- Comment #1 from Hannah von Reth --- Or inline image -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 246727] Add undo functionality to move to trash action
https://bugs.kde.org/show_bug.cgi?id=246727 Christian Gruber changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 409717] New: [Question/missing doc] CLSID
https://bugs.kde.org/show_bug.cgi?id=409717 Bug ID: 409717 Summary: [Question/missing doc] CLSID Product: Snoretoast Version: unspecified Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: vonr...@kde.org Reporter: tho...@safing.io Target Milestone: --- In the README, I find that you have to set your own AppID for an application to use Snoretoast. But looking at the code, "snoretoast -install" does more than just setting an AppID, it also sets a CLSID. This is never mentioned in the docs. There are some questions that arises to me: * Is the CLSID needed (since it isn't mentioned in the README and it is checked for beeing empty in which case "snoretoast -install" continues without; but seems like it is needed for the buttons to work https://github.com/mohabouje/WinToast/issues/35) * Snoretoast sets a constant CLSID that changes on every version. But what if Snoretoast is shipped by two Apps, therefore remains two times on the disk, both register the same CLSID with different Locations on the Filesystem. Then the wrong Snoretoast and therefore the wrong Application will be contacted for callbacks, won't it? Is Snoretoast intended to be shipped as an exe as part of another Application? Thanks in advance! Thomas -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409642] regex
https://bugs.kde.org/show_bug.cgi?id=409642 --- Comment #4 from ch-hambur...@freenet.de --- The problem may be minor, though it is illogical that 'Find' and 'Replace' should behave differently. But one or two explanatory lines in the manual, of which you are co-author, would do no harm. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #14 from Michael --- Created attachment 121468 --> https://bugs.kde.org/attachment.cgi?id=121468&action=edit kdeglobals in 'broken' state Here it is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #18 from Nate Graham --- Instead of commenting out the code, you should add an option in its settings window to control this behavior. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 409718] New: Configure Software Sources does NOT accept correct password.
https://bugs.kde.org/show_bug.cgi?id=409718
Bug ID: 409718
Summary: Configure Software Sources does NOT accept correct
password.
Product: muon
Version: 5.8.0
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: muon
Assignee: echidna...@kubuntu.org
Reporter: bugs.kde@trimoon.cloudns.eu
CC: silh...@gmail.com
Target Milestone: ---
SUMMARY
When using Settings->Configure Software Sources the popup can't authenticate
for root permissions.
STEPS TO REPRODUCE
1. Have your useraccount be able to use sudo using its own password.
2. Have root account with different password enabled.
3. Select "Settings->Configure Software Sources".
4. The popup that comes is titled "Run as root -- KDE su" and displays as
command "/usr/bin/software-properties-kde --attach --dont-update"
OBSERVED RESULT
5. No matter which password you type (own or root's), it is NOT accepted.
EXPECTED RESULT
5. You should be allowed to use either your own password or that of root's.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.04
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
ADDITIONAL INFORMATION
I don't actually use this feature because i configure my sources via
command-line in /etc/apt/{sources.list,sources.list.d/*}
--
You are receiving this mail because:
You are watching all bug changes.
[muon] [Bug 409718] Configure Software Sources does NOT accept correct password.
https://bugs.kde.org/show_bug.cgi?id=409718 ©TriMoon™ changed: What|Removed |Added Platform|Ubuntu Packages |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #19 from triffid.hun...@gmail.com --- May take me a good long while to work out how to do that, any of you other irritated folks want to give it a crack? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405572] font dpi not saved/loaded correctly
https://bugs.kde.org/show_bug.cgi?id=405572 Kai Uwe Broulik changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/e9a38fbd4d6af2b ||3b5a5ab10417ab895ed13c12b Version Fixed In||5.16.4 --- Comment #8 from Kai Uwe Broulik --- Git commit e9a38fbd4d6af2b3b5a5ab10417ab895ed13c12b by Kai Uwe Broulik. Committed on 11/07/2019 at 13:49. Pushed by broulik into branch 'Plasma/5.16'. [Fonts KCM] Alter DPI only on explicit user interaction The settings are loaded after the QML is created, and once it is loaded, it becomes indeterministic which property (checkbox checked or spinbox value) is re-evaluated first and the Binding ends up resetting the config. FIXED-IN: 5.16.4 Differential Revision: https://phabricator.kde.org/D22397 M +3-7kcms/fonts/package/contents/ui/main.qml https://commits.kde.org/plasma-desktop/e9a38fbd4d6af2b3b5a5ab10417ab895ed13c12b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #20 from Nate Graham --- Check out how configurable options are implemented: https://cgit.kde.org/plasma-desktop.git/tree/applets/taskmanager/package/contents/config -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 409712] add
https://bugs.kde.org/show_bug.cgi?id=409712 --- Comment #2 from Philippe ROUBACH --- (In reply to Kai Uwe Broulik from comment #1) > That extension uses Firefox' old XPI extension API? I don't think we have > the neccessary APIs in Web Extensions to provide seamless integration. Yes that why we can't find anymore this extension at mozilla addons site. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 409712] add
https://bugs.kde.org/show_bug.cgi?id=409712 --- Comment #3 from Kai Uwe Broulik --- Then I don't see what I can do differently about this... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #34 from Aaron Lavarnway --- Created attachment 121469 --> https://bugs.kde.org/attachment.cgi?id=121469&action=edit Time graph animation Unfortunately not, as far as I can tell. I attached another graphic that shows the problem, since that's about all I can do to help. I created a mouse macro to drag the canvas of Krita and an example program so I could reproduce the exact mouse movements and compare the two. Then I laid out each frame on a time graph, so you can visually see the 'stuttering' and 'bumps' that occur. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 409712] add
https://bugs.kde.org/show_bug.cgi?id=409712 --- Comment #4 from Philippe ROUBACH --- Sorry but i am not a dev.i only supply an existing software. I think it is easier to start from an existing software than from nothing. You or someone must built a fork. That's what sicvolo dev did. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #35 from Dmitry Kazakov --- It looks much better than it used to be, right? And what is "the other" application you are checking it against? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409719] New: Plain text fallback when using untrusted keys
https://bugs.kde.org/show_bug.cgi?id=409719 Bug ID: 409719 Summary: Plain text fallback when using untrusted keys Product: kmail2 Version: 5.9.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: wannes...@googlemail.com Target Milestone: --- SUMMARY KMail will fall back to plain text Mails if it thinks, that S/MIME certificates are not trustworthy. (Which btw. isn't the case. This will be another Bug.) At first there are several scenarios where your and the receivers trust differ. So if you don't trust a certificate it is still valid to use it for signing. (But not for verifying signatures.) At second there are different trust levels. (PGP even defines them explicitly.) You may want to be able to send unimportant messages (that would be sent otherwise in plain text) to a not *fully* trustworthy person. So again: Even for *en*cryption int makes perfect sense to allow to use not trusted keys. (At leas as long you support also plain text mails.) And at last: You should at least consider, that your checking is broken (My be just due to misconfiguration because it uses the wrong time etc.) and allow the user to do it externally with openssl etc.. So if the user says it is trustworthy – just do as he says. ;-) STEPS TO REPRODUCE 1. Use a system with a wrong date. (For example without a RTC.) 2. Try to send a signed message. OBSERVED RESULT 3. KMail will warn and fall back to plain text. EXPECTED RESULT At first: KMail should never ever prefer plain text messages over signed ones. This is absolute rubbish. You could argue that there is a central truststore in x.509. But then you have to block all plain text mails also. Falling back to plain text makes absolutely no sense at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #36 from Aaron Lavarnway --- Paintstorm Studio is the 'other', though Affinity Photo also has very smooth pan/zoom/rotate. I used Clip Studio Paint for 5 years, then when I upgraded to the 4k Cintiq the canvas FPS dropped to ~12-20 FPS at all times. No fix currently. So I switched to Paintstorm for about a year, but found it handled large files/many layers terribly and lacked many, many features. Now I've been using Krita for about 6 months, but I always noticed the canvas was choppier, but usable. I tried to switch from Krita to Affinity Photo but Affinity doesn't have a way to switch to zoom temporarily when you hold down the zoom shortcut, and doesn't allow you to rotate by dragging. So Krita is the best option for me and my workflow currently. The only problem I've ever had so far was the canvas being stuttery. And if I'm going to be sticking around with it, I might as well see if that could potentially help get it fixed. I don't know if you take bug bounties, but it matters enough to me and my friends where I could try and scrounge up something for the effort, whatever you think would be fair I could look into saving for. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 409720] New: CA update not workong
https://bugs.kde.org/show_bug.cgi?id=409720 Bug ID: 409720 Summary: CA update not workong Product: kleopatra Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: wannes...@googlemail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY If you have a old outdated CA-Certificate and a newer one kleopatra validates against the old one and thinks the certificates signed by it aren't trustworthy. This is especially annoying since you even can't remove the old CA since removing a CA will result in removing all certificates singed by it. So please make an easy CA replacement possible. STEPS TO REPRODUCE 1. Import a CA-certificate (A) with an near in the future laying enddate 2. Import a longer valid certificate (B) that is signed by this CA. 3. Import a longer valid CA-certificate (C) for the same CA. 4. Wait until the first CA-certificate (A) runs out. OBSERVED RESULT The certificate (B) is no longer trusted also there is a path to a existing, trusted CA (C). EXPECTED RESULT Kleopatra should validate against the still trusted CA. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408872] If Qt cannot open any opengl driver dll, Krita will not start
https://bugs.kde.org/show_bug.cgi?id=408872 --- Comment #17 from Dmitry Kazakov --- Git commit bf4e20d468f77d5a81f1a87227e326a5fc459168 by Dmitry Kazakov. Committed on 11/07/2019 at 14:56. Pushed by dkazakov into branch 'master'. Make Krita not request any specific renderer, when OpenGL is disabled Important note: now we don't have any specific option for openGL, we just write "none" into the renderer field. M +2-2libs/ui/KisPart.cpp M +6-4libs/ui/dialogs/kis_dlg_preferences.cc M +9-13 libs/ui/kis_config.cc M +1-1libs/ui/kis_config.h M +46 -38 libs/ui/opengl/kis_opengl.cpp M +1-1libs/ui/opengl/kis_opengl_canvas2.cpp M +1-1libs/ui/tests/kis_derived_resources_test.cpp https://invent.kde.org/kde/krita/commit/bf4e20d468f77d5a81f1a87227e326a5fc459168 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409721] New: Showfoto export WebP images without colour space
https://bugs.kde.org/show_bug.cgi?id=409721 Bug ID: 409721 Summary: Showfoto export WebP images without colour space Product: digikam Version: 5.9.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: showfoto Assignee: digikam-bugs-n...@kde.org Reporter: lp.com...@lavache.com Target Milestone: --- SUMMARY Showfoto export WebP images without color space information. STEPS TO REPRODUCE 1. Open a (sRGB) jpeg or with Showfoto 2. Export a WebP 3. Import the WebP. A pop-up (if activated in the parameters) tells that there is no colour space in this image. 4. Assign a colour space (for instance, sRGB) 5. Save the image 6. Open it again in Showfoto. Then step 3 is reproduced. OBSERVED RESULT Opening the file in Showfoto, Firefox or Gwenview shows wrong colours, as no colour space information is available. EXPECTED RESULT WebP image should have correct colours because it should contain colors space information. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.0.0-20-generic (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Showfoto 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409721] Showfoto export WebP images without colour space
https://bugs.kde.org/show_bug.cgi?id=409721 Lapineige changed: What|Removed |Added CC||lp.com...@lavache.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)
https://bugs.kde.org/show_bug.cgi?id=350228 Julian Seward changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #10 from Julian Seward --- Landed, 4443b782c4deddabcf4a2cbd7fe923cb22f87bf8 (both patches combined). Thanks for them! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391369] plasmashell crashes when reordering tasks
https://bugs.kde.org/show_bug.cgi?id=391369 --- Comment #8 from Patrick Silva --- bug 386312 marked as duplicate is still happening on Neon unstable edition. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402389] [Wayland] Crash when using "Close all" on viewers [crash in wl_proxy_marshal_array_constructor_versioned]
https://bugs.kde.org/show_bug.cgi?id=402389 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402389] [Wayland] Crash when using "Close all" on viewers [crash in wl_proxy_marshal_array_constructor_versioned]
https://bugs.kde.org/show_bug.cgi?id=402389 Nicolas Fella changed: What|Removed |Added Version|5.3.1 |git master Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #29 from S --- Over here: https://bugzilla.suse.com/show_bug.cgi?id=1141028 (Stefan Brüns) > A fix is already included in KF5.60. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #16 from Josh Freeno --- Created attachment 121471 --> https://bugs.kde.org/attachment.cgi?id=121471&action=edit This is how it locks itself after you enable sub-pixel rendering Here is my kdeglobals config after enabling sub-pixel rendering. Here is my info on OS. Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 5.2.0-arch2-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409721] Showfoto export WebP images without colour space
https://bugs.kde.org/show_bug.cgi?id=409721 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|showfoto|FilesIO-Engine -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #17 from Josh Freeno --- Created attachment 121472 --> https://bugs.kde.org/attachment.cgi?id=121472&action=edit This both my fontconfig and kdeglobals while I am in broken state. I add the fontconfig to the kdegobals because it would not let me select two files for some reason. This my first bug report so sorry if I have made mistakes in the reports. I just wanted to help get the info out there. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 409527] Cannot turn narration off permanently
https://bugs.kde.org/show_bug.cgi?id=409527 --- Comment #1 from Mauro Carvalho Chehab --- There is actually a way to change the default audio channel. Right click at the channel name and select "Edit". It will show the channel properties. One of the options at the right is "Audio Channel". If you change it, Kaffeine will remember your audio channel preference for that channel. This works either at the "Digital TV" menu or at the channel scan menu. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408913] Failiure to launch streaming in fullscreen
https://bugs.kde.org/show_bug.cgi?id=408913 --- Comment #1 from Mauro Carvalho Chehab --- Try to use Kaffeine latest version. There were several changes related to it since version 2.0.14. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409722] New: Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Bug ID: 409722 Summary: Krusader crash when trying to view a musescore file Product: krusader Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: mboh...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.1 "Peace of Mind") Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: What I was doing when the application crashed: - Open Krusader - Goto file location - Select the file via the touchpad (single click) - Click the F3 View button > CRASH When looking at the file clicking the F4 Edit button, there is no crash, the file opens normally. Using KDE neon The system just got an update, so is completely up to date. To make sure the crash was not caused by doing the manipulation during system upgrade, I rebooted the laptop and tried again --> same result marc@marc-samsung:~$ uname -a Linux marc-samsung 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd24bb110c0 (LWP 2158))] Thread 4 (Thread 0x7fd223ded700 (LWP 2163)): #0 QMutex::lock (this=this@entry=0x5629505ef880) at thread/qmutex.cpp:222 #1 0x7fd245ed8ccc in QMutexLocker::QMutexLocker (m=0x5629505ef880, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:206 #2 QThreadData::canWaitLocked (this=0x5629505ef850) at ../../include/QtCore/5.12.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:269 #3 postEventSourcePrepare (s=0x7fd214004ba0, timeout=0x7fd223decba4) at kernel/qeventdispatcher_glib.cpp:259 #4 0x7fd23fdc9b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd23fdca4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fd23fdca6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fd245ed8dcb in QEventDispatcherGlib::processEvents (this=0x7fd214000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #8 0x7fd245e7a03a in QEventLoop::exec (this=this@entry=0x7fd223decd70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #9 0x7fd245ca14ca in QThread::exec (this=) at thread/qthread.cpp:531 #10 0x7fd2478fa015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x7fd245ca2c72 in QThreadPrivate::start (arg=0x7fd247b71d80) at thread/qthread_unix.cpp:361 #12 0x7fd243bea6db in start_thread (arg=0x7fd223ded700) at pthread_create.c:463 #13 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd2295b5700 (LWP 2162)): #0 0x7fd243bf09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56295042d8b8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56295042d868, cond=0x56295042d890) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56295042d890, mutex=0x56295042d868) at pthread_cond_wait.c:655 #3 0x7fd22f6c90aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fd22f6c8dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fd243bea6db in start_thread (arg=0x7fd2295b5700) at pthread_create.c:463 #6 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fd22a3e6700 (LWP 2161)): #0 0x7fd243bf09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5629504cc9e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5629504cc990, cond=0x5629504cc9b8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5629504cc9b8, mutex=0x5629504cc990) at pthread_cond_wait.c:655 #3 0x7fd22f6c90aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #4 0x7fd22f6c8dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #5 0x7fd243bea6db in start_thread (arg=0x7fd22a3e6700) at pthread_create.c:463 #6 0x7fd24520488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fd24bb110c0 (LWP 2158)): [KCrash Handler] #6 0x in ?? () #7 0x7fd245eafc82 in QObjectPrivate::connectImpl (sender=sender@entry=0x562950ba6700, signal_index=3, receiver=receiver@entry=0x562950b87f80, slot=slot@entry=0x7ffe255c0b80, slotObj=slotObj@entry=0x562950b51d60, type=, types=, senderMetaObject=) at kernel/qobject.cpp:4903 #8 0x7fd245eaff2a
[krusader] [Bug 409722] Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Marc Bohets changed: What|Removed |Added CC||mboh...@gmail.com --- Comment #1 from Marc Bohets --- Created attachment 121473 --> https://bugs.kde.org/attachment.cgi?id=121473&action=edit This is the file I tried to view The file contains information on how to display and play music via the musescore3 application. -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 409723] New: [Feature] add appID&CLSID to existing Link
https://bugs.kde.org/show_bug.cgi?id=409723 Bug ID: 409723 Summary: [Feature] add appID&CLSID to existing Link Product: Snoretoast Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: vonr...@kde.org Reporter: tho...@safing.io Target Milestone: --- Created attachment 121474 --> https://bugs.kde.org/attachment.cgi?id=121474&action=edit Non working PoC For some situations, it would be great to not create a new link, but add the appID and the CLSID to an existing Link while preserving the rest of the link. For example if the Symlink itself needs additional Attributes of if the appID changed, ... I already tried myself to get it working, will continue trying, but this is my first Windows-Project ... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #37 from Aaron Lavarnway --- (In reply to Dmitry Kazakov from comment #35) > It looks much better than it used to be, right? It does look better than it used to be, that's for sure. But that got fixed when I did a clean wipe of all display drivers and reinstalled the latest Nvidia drivers. That, as well as all my friends and other computers with Nvidia cards having the same problem, suggests it might have something to do with Nvidia cards, how Krita communicates with them, or drivers, right? I don't know much about how that works, and unfortunately I don't have an AMD or Intel integrated computer to test it out. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 --- Comment #18 from Josh Freeno --- Also I would like to add that when I select defaults in font settings it does not reset fonts to the correct settings. It sets them to wrong size and and to noto black. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Jan changed: What|Removed |Added CC||medhe...@web.de -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 409724] New: Akonadi dependency not made explicit during install
https://bugs.kde.org/show_bug.cgi?id=409724 Bug ID: 409724 Summary: Akonadi dependency not made explicit during install Product: zanshin Version: 0.5.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: er...@kde.org Reporter: cowc...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done SUMMARY If Zanshin is installed normally from the Ubuntu repository, the program claims that it needs Akonadi to work when trying to open it and once it is _already_ installed. Even after installing some of the Akonadi packages from the repository, Zanshin does not work. When trying to open it claims that it can't connect with the personal information management system and that there is no Akonadi agent available. The user shouldn't discover by surprise this dependency once the program is already installed and shouldn't be forced to guess which are the necessary packages the she/he has to install to make the program work. STEPS TO REPRODUCE 1. Install Zanshin package from the Ubuntu repository. 2. Trying to open Zanshin from the Applications Menu. Program claims it needs Akonadi to work. 3. Installing akonadi-server and akonadiconsole from the Ubuntu repository. 4.- Trying to open Zanshin from the Applications Menu. Program claims it can't connect with the personal information management system and that there is no Akonadi agent available. OBSERVED RESULT After installation Zanshin does not start. It gives a message complaining about Akonadi. EXPECTED RESULT After installing Zanshin from the repository it should be able to start without having to install other packages. Either: a) The fact that Zanshin will not work without Akonadi is explicitly stated in the web and descriptions of the program, or b) the required Akonadi packages are marked as dependencies to install when installing Zanshin from the repository, or c) the program is modified so it is able to run withou Akonadi. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Mate 18.04 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION All packages were installed using Synaptic Package Manager. -- You are receiving this mail because: You are watching all bug changes.
[Snoretoast] [Bug 409723] [Feature] add appID&CLSID to existing Link
https://bugs.kde.org/show_bug.cgi?id=409723 --- Comment #1 from Hannah von Reth --- Hm any reason you can't remove and recreate the url? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409722] Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Davide Gianforte --- This is the same bug of 405410, but the backtrace here shows more details -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 405410] krviewer crash krusader at try zip-archive view by F3 button
https://bugs.kde.org/show_bug.cgi?id=405410 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Davide Gianforte --- *** This bug has been marked as a duplicate of bug 409722 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409722] Krusader crash when trying to view a musescore file
https://bugs.kde.org/show_bug.cgi?id=409722 Davide Gianforte changed: What|Removed |Added CC||ami...@tuta.io --- Comment #3 from Davide Gianforte --- *** Bug 405410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 409725] New: Krusader crashed after starting Disk Usage
https://bugs.kde.org/show_bug.cgi?id=409725 Bug ID: 409725 Summary: Krusader crashed after starting Disk Usage Product: krusader Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: jimmtheg...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.1 "Peace of Mind") Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I clicked on Disk Usage, the window came up, then crashed after a few seconds -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6cef1f30c0 (LWP 16353))] Thread 5 (Thread 0x7f6cc9090700 (LWP 16358)): #0 0x7f6ce88d0bf9 in __GI___poll (fds=0x7f6cb8007030, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6cca105481 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f6cca0f6e40 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f6cca0f74d0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f6cca0f7560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f6cca1053c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f6cc9ea7318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f6ce72c36db in start_thread (arg=0x7f6cc9090700) at pthread_create.c:463 #8 0x7f6ce88dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6cd0ae6700 (LWP 16356)): #0 __GI___pthread_getspecific (key=4) at pthread_getspecific.c:30 #1 0x7f6ce34ca680 in g_thread_self () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ce34a26cd in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ce95b1dcb in QEventDispatcherGlib::processEvents (this=0x7f6cc4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f6ce955303a in QEventLoop::exec (this=this@entry=0x7f6cd0ae5d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f6ce937a4ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f6ceafd3015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6ce937bc72 in QThreadPrivate::start (arg=0x7f6ceb24ad80) at thread/qthread_unix.cpp:361 #8 0x7f6ce72c36db in start_thread (arg=0x7f6cd0ae6700) at pthread_create.c:463 #9 0x7f6ce88dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f6cd17dc700 (LWP 16355)): #0 0x7f6ce72c99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5579a5a9ce48) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5579a5a9cdf8, cond=0x5579a5a9ce20) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5579a5a9ce20, mutex=0x5579a5a9cdf8) at pthread_cond_wait.c:655 #3 0x7f6cd2ac03da in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6cd2ac0107 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6ce72c36db in start_thread (arg=0x7f6cd17dc700) at pthread_create.c:463 #6 0x7f6ce88dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6cdba4a700 (LWP 16354)): #0 0x7f6ce88d0bf9 in __GI___poll (fds=0x7f6cdba49ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6ce670c747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6ce670e36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6cde831578 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6ce937bc72 in QThreadPrivate::start (arg=0x5579a5a3e9c0) at thread/qthread_unix.cpp:361 #5 0x7f6ce72c36db in start_thread (arg=0x7f6cdba4a700) at pthread_create.c:463 #6 0x7f6ce88dd88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6cef1f30c0 (LWP 16353)): [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x7f6c0019) at /usr/include/c++/7/bits/atomic_base.h:396 #7 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x7f6c0019) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 #9 QtPrivate::RefCount::ref (this=0x7f6c0019) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #10 QString::QString (other=..., this=0x7ffc80154cb8) at ../../include/QtCore/../../src/corelib/too
[lattedock] [Bug 409726] New: Make it so that the dash to dock style doesnt guess colors from apps
https://bugs.kde.org/show_bug.cgi?id=409726 Bug ID: 409726 Summary: Make it so that the dash to dock style doesnt guess colors from apps Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: gregorystar...@gmail.com Target Milestone: --- Created attachment 121475 --> https://bugs.kde.org/attachment.cgi?id=121475&action=edit Shows the effect Right now it guesses the color from the app. It looks very messy to have multiple apps next to each other with slightly different colors as shown in the attached screenshot -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408872] If Qt cannot open any opengl driver dll, Krita will not start
https://bugs.kde.org/show_bug.cgi?id=408872 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #18 from Dmitry Kazakov --- According to the reporter, the bug is now fixed in master! https://www.reddit.com/r/krita/comments/c62xlp/krita_422_released/etj4rya/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409726] Make it so that the dash to dock style doesnt guess colors from apps
https://bugs.kde.org/show_bug.cgi?id=409726 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Michail Vourlakos --- you can send requests with explantions etc. at: https://github.com/psifidotos/latte-indicator-dashtopanel/issues -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #38 from Dmitry Kazakov --- Erm.. I don't understand. What happened after you cleaned-up the drivers? 1) Did 4.2.2 started to work smoother? 2) Or my latest package started to work smoother? 3) Or my latest package started to work less smoothly? -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 409727] New: Several cell properties changed/reset on changing one specific
https://bugs.kde.org/show_bug.cgi?id=409727 Bug ID: 409727 Summary: Several cell properties changed/reset on changing one specific Product: calligrasheets Version: 3.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: leghi...@cyber-viking.com Target Milestone: --- SUMMARY In calligra sheets when selecting a group of cells and e.g. changing the frame style, all background colors, text colors and other styles are reset to default or sth similar. This sounds quite trivial, but makes calligra sheets defacto unusable, therefore the severity choice. STEPS TO REPRODUCE 1. create a new table with several columns and rows, containing arbitrary text. 2. select only some of the cells and apply a background color of your choice. 3. repeat previous step one or two times to get several colored cell groups. 4. select all cells, change ONLY frame style OBSERVED RESULT If you perform step 4, some of the previously made formattings are reset/changed. sometimes several approaches are needed to observe this behaviour. EXPECTED RESULT Only the touched formattings shall change accordingly. Styles you didn't change/touch in the "format cells" dialogue shall not change anything on the selected cells. SOFTWARE/OS VERSIONS Windows: -- macOS: -- Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59 Qt Version: 5.13 ADDITIONAL INFORMATION Manjaro linux, kernel 5.1.16 (Arch-Based) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409728] New: Preview video lagging
https://bugs.kde.org/show_bug.cgi?id=409728 Bug ID: 409728 Summary: Preview video lagging Product: kdenlive Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: willtea...@gmail.com Target Milestone: --- System: Windows 10 CPU: i5-4300U HP EliteBook Folio 1040 G1 Kdenlive: 19.04.02 installer exe Some years ago I noticed that the preview video will lag some seconds when I press play. I thought it was because of my old pc, but now I have a quiet good laptop, and nothing changed. This bug is very annoying, almost doubling the video cutting time. I made a video about that: https://youtu.be/P7gvZTyCu2k In Adobe Premiere when the pointer moved in the timeline, it will start rendering the preview, so if I wait some seconds before play, it will be smooth. In kdenlive, I need to play some seconds, and after that will be good. I don't understand why, but it's very nervous. (Proxy clips not helped) Another bug (you can see in the video): when I click somewhere in the timeline, the preview does not jump there. There are some thinks, what I miss from kdenlive. These are not bugs, but I don't know where to write. So first, the community really needs a noise reducer. Audacity has, and it is open source, can't you use it somehow? (I mean copy-paste it, or something :)) And I also miss the arrow shortcuts - in Premiere, when I press left/right, the preview jumps one frame forward/backward. A really love this project, sorry if I was not too technical, I hope I can help somehow. Thank you, guys, you made the best video editor for me! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409728] Preview video lagging
https://bugs.kde.org/show_bug.cgi?id=409728 DaWe changed: What|Removed |Added URL||https://youtu.be/P7gvZTyCu2 ||k -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 409729] New: KJob doesn't show progress dialog when used in a QCoreApplication
https://bugs.kde.org/show_bug.cgi?id=409729 Bug ID: 409729 Summary: KJob doesn't show progress dialog when used in a QCoreApplication Product: frameworks-kcoreaddons Version: 5.59.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: cont...@azubieta.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY KIO::getJobTracker()->registerJob(job) doesn't result in progress when you're a QCoreApplication and doesn't even print a warning STEPS TO REPRODUCE 1. Use a KJob inside a QCoreApplication OBSERVED RESULT No progress dialog is shown. EXPECTED RESULT A progress dialog is shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User Edition 5.16 KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
