[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 Rich Grundy changed: What|Removed |Added CC||r...@grundy.io --- Comment #13 from Rich Grundy --- Can confirm with "background contrast" disabled I also receive the same issue. Turning on or off "Allow applications to block compositing" has no affect. KDE: 5.19.2 KDE Framework: 5.71.0 QT: 5.15.0 Kernel: 5.7.6 GPU: Radeon RX570 with amdgpu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 423643] plasma-framework commit 7c4f5c5f1 on qt-5.15.0 broke the systray (and more)
https://bugs.kde.org/show_bug.cgi?id=423643
--- Comment #8 from Fabian Vogt ---
(In reply to Friedrich W. H. Kossebau from comment #5)
> ...
> Just, some API which is e.g. tagged with Q_INVOKABLE does not use the full
> namespace name, but omits the Plasma namespace, like "ServiceJob
> *Service::startOperationCall(const QVariantMap &description, QObject
> *parent)". And as said in the referenced bug report, that name has to be
> explicitly additionally registered, to allow Qt the mapping to the actual
> type metadata.
> But see the current qRegisterMetaType("name") as given above: they miss
> the "*" from the name. So they are registering the wrong incomplete name.
> And so e.g.
> ```
> qRegisterMetaType("ServiceJob");
> ```
> will not help Qt when it tries to match the type name "ServiceJob*" from the
> invokable above to a registered type in the metadata system.
I guess it should be either
qRegisterMetaType("ServiceJob*");
or
qRegisterMetaType("ServiceJob");
?
The doc says:
> Warning: This function is useful only for registering an alias (typedef) for
> every other use case Q_DECLARE_METATYPE and qMetaTypeId() should be used
> instead.
So that seems like it could be used for this.
> ...
> This would be my sleepy analyis of the cause.
I got to the same conclusion at least.
(In reply to Friedrich W. H. Kossebau from comment #6)
> (In reply to Aleix Pol from comment #4)
> > Git commit ac6bff575f934bceab03abdabc6a5c841c5b1f5e by Aleix Pol.
> > Committed on 01/07/2020 at 01:47.
> > Pushed by apol into branch 'master'.
> >
> > Use fully qualified identifiers for metaobject types
> > ...
>
> I fear that would be only one incarnation where the no longer registered
> type is fixed, instead/additionally we might also want to make sure the
> unnamespaced pointer and non-pointer types are registered as they had been
> so far?
Yes, there might be users of this outside of plasma-framework as well.
Though I wasn't able to find any of those on lxr.kde.org or GitHub.
Technically this is an API break though.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 423503] System Settings crash on launch
https://bugs.kde.org/show_bug.cgi?id=423503 --- Comment #1 from choury --- Created attachment 129806 --> https://bugs.kde.org/attachment.cgi?id=129806&action=edit New crash information added by DrKonqi systemsettings5 (5.17.5) using Qt 5.14.2 - What I was doing when the application crashed: crashed just after open systemsettings, it can be reproduced every time. - Unusual behavior I noticed: - Custom settings of the application: -- Backtrace (Reduced): #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7fdc9248555b in __GI_abort () at abort.c:79 #6 0x7fdc9287fae5 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #9 0x7fdc9225f156 in QQuickWidget::resizeEvent(QResizeEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #10 0x7fdc93602c5f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423503] System Settings crash on launch
https://bugs.kde.org/show_bug.cgi?id=423503 choury changed: What|Removed |Added CC||zhouwei...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 170510] Don't warn about ioctl of size 0 without direction hint
https://bugs.kde.org/show_bug.cgi?id=170510 Paul Floyd changed: What|Removed |Added CC||pa...@free.fr --- Comment #2 from Paul Floyd --- Simply running xterm under Valgrind on FreeBSD produces this warning. I haven't tried on Linux. I don't have a genuine error example. I'm tracking this in parallel here https://github.com/paulfloyd/freebsd_valgrind/issues/15 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407589] [Linux] Add support for C11 aligned_alloc() and GNU reallocarray()
https://bugs.kde.org/show_bug.cgi?id=407589 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pa...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373971] Annotations - as dock dialog
https://bugs.kde.org/show_bug.cgi?id=373971 --- Comment #2 from Jo --- Hi Tymond, Years ago I started to add comments to my projects, to describe the desired outcome during idea development Today I'm using Mindmaps, but simple text notes are still perfectly fine to write down lists of keywords and shorter sentences as guides Annotations should help and guide us in the initial stages of our paint and comic projects as well. Creative chaos isn't always the best approach for a new project Writing text with a drawing pen on canvas is just slow and cumbersome, the text tool isn't an alternative as we aren't going to make a tutorial -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418120] Uninstaller recursively deleted C:/ drive
https://bugs.kde.org/show_bug.cgi?id=418120 --- Comment #9 from xela --- I filed this bug today & it is merged into this thread. I'm using digikam under manjaro kde 20.+ kernel 5.6.16-1, & it works fun so far this is why I would try its windows 64bit version under my dual boot windows 10 as i stated in my bug report, i installed into d:\software i thought the installer would add \digikam to the end of the dest folder as most of other software would do but i could not find its shortcut in the startmenu, then i went to the install folder d:\software but find loads of files under it, rather than supposed d:\software\digikam then i decided to uninstall it & reinstall to d:\software\digikam this was the start of the disaster after clicking the confirmation button, the uninstaller started to delete everything under d:\software i didn't noticed this until i felt it took so long to perform an uninstall but no options to stop this uninstall - no cancel button, no window close button except the minimize button on the top right corner of the dialog then everything was gone - my installed programs, my database, my emails, my websites ... and i couldn't recover them so far, & was afraid to log onto windows just in case the deleted files on the hard disk were covered but fortunately, i haven't used it to mange my photos, 'cause if these photos were deleted then i will lose them forever based on my mere knowledge of linux, the uninstall option is more like the linux cmd: rm -rf hopefully this issue could be solved asap & windows users/downloaders should be notified before installing -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 423726] New: kmenuedit crash after removing entries
https://bugs.kde.org/show_bug.cgi?id=423726 Bug ID: 423726 Summary: kmenuedit crash after removing entries Product: kmenuedit Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: danielwohl...@gmx.de Target Milestone: --- Application: kmenuedit (5.19.2) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-61-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I deleted an outdated version of an appimage. After that i wanted to remove its entry from the menu. So I filtered by its name, selected it and add a few separators by mistake. After removing the entry, i cleared the filter and removed the unnecessary separators as well. The crash happened when i clicked the save-button. I tried to redo my steps, but aparently my changes were saved regardless of the crash. -- Backtrace: Application: KDE-Menü-Editor (kmenuedit), signal: Segmentation fault [KCrash Handler] #4 QString::QString (other=, this=this@entry=0x7ffcdc19add0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1050 #5 KService::desktopEntryName (this=0x0) at ./src/services/kservice.cpp:926 #6 0x560116e837cc in GlobalAccel::changeMenuEntryShortcut (service=..., shortcut=...) at ./globalaccel.cpp:31 #7 0x560116e80e42 in MenuFolderInfo::save (this=0x560118972c40, menuFile=0x5601188f2e70) at ./menuinfo.cpp:189 #8 0x560116e703df in TreeView::save (this=0x5601188f2230) at ./treeview.cpp:1717 #9 0x7f2879a5b4b9 in doActivate (sender=0x5601188f7050, signal_index=4, argv=0x7ffcdc19b020) at kernel/qobject.cpp:3882 #10 0x7f2879a55f92 in QMetaObject::activate (sender=sender@entry=0x5601188f7050, m=m@entry=0x7f287aff1340 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcdc19b020) at kernel/qobject.cpp:3930 #11 0x7f287a9094a2 in QAction::triggered (this=this@entry=0x5601188f7050, _t1=) at .moc/moc_qaction.cpp:381 #12 0x7f287a90bb0c in QAction::activate (this=0x5601188f7050, event=) at kernel/qaction.cpp:1161 #13 0x7f287a9fcc8b in QAbstractButtonPrivate::click (this=0x560118b67890) at widgets/qabstractbutton.cpp:398 #14 0x7f287a9fceed in QAbstractButton::mouseReleaseEvent (this=0x560118b67e00, e=0x7ffcdc19b5b0) at widgets/qabstractbutton.cpp:1012 #15 0x7f287aaeee1a in QToolButton::mouseReleaseEvent (this=, e=) at widgets/qtoolbutton.cpp:622 #16 0x7f287a9508c8 in QWidget::event (this=0x560118b67e00, event=0x7ffcdc19b5b0) at kernel/qwidget.cpp:9033 #17 0x7f287a9fe0bb in QAbstractButton::event (this=this@entry=0x560118b67e00, e=e@entry=0x7ffcdc19b5b0) at widgets/qabstractbutton.cpp:969 #18 0x7f287aaeeeb4 in QToolButton::event (this=0x560118b67e00, event=0x7ffcdc19b5b0) at widgets/qtoolbutton.cpp:1002 #19 0x7f287a90f9ac in QApplicationPrivate::notify_helper (this=this@entry=0x560118659490, receiver=receiver@entry=0x560118b67e00, e=e@entry=0x7ffcdc19b5b0) at kernel/qapplication.cpp:3685 #20 0x7f287a9179f8 in QApplication::notify (this=, receiver=0x560118b67e00, e=0x7ffcdc19b5b0) at kernel/qapplication.cpp:3129 #21 0x7f2879a204a8 in QCoreApplication::notifyInternal2 (receiver=0x560118b67e00, event=0x7ffcdc19b5b0) at kernel/qcoreapplication.cpp:1075 #22 0x7f2879a2068e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x560118b67e00, event=event@entry=0x7ffcdc19b5b0) at kernel/qcoreapplication.cpp:1482 #23 0x7f287a91607f in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x560118b67e00, event=event@entry=0x7ffcdc19b5b0, alienWidget=0x560118b67e00, nativeWidget=0x5601188ae540, buttonDown=buttonDown@entry=0x7f287b0209a0 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2615 #24 0x7f287a96af81 in QWidgetWindow::handleMouseEvent (this=this@entry=0x5601189cda50, event=event@entry=0x7ffcdc19ba30) at kernel/qwidgetwindow.cpp:673 #25 0x7f287a96ddea in QWidgetWindow::event (this=0x5601189cda50, event=0x7ffcdc19ba30) at kernel/qwidgetwindow.cpp:295 #26 0x7f287a90f9ac in QApplicationPrivate::notify_helper (this=this@entry=0x560118659490, receiver=receiver@entry=0x5601189cda50, e=e@entry=0x7ffcdc19ba30) at kernel/qapplication.cpp:3685 #27 0x7f287a916bb0 in QApplication::notify (this=0x7ffcdc19bec0, receiver=0x5601189cda50, e=0x7ffcdc19ba30) at kernel/qapplication.cpp:3431 #28 0x7f2879a204a8 in QCoreApplication::notifyInternal2 (receiver=0x5601189cda50, event=0x7ffcdc19ba30) at kernel/qcoreapplication.cpp:1075 #29 0x7f2879a2068e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x5601189cda50, event=event@entry=0x7ffcdc19ba30) at kernel/qcoreapplication.cpp:1482 #30 0x00
[trojita] [Bug 423725] New: Latvian translation is missing
https://bugs.kde.org/show_bug.cgi?id=423725 Bug ID: 423725 Summary: Latvian translation is missing Product: trojita Version: git Platform: unspecified OS: All Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: k_a_r_l...@sveiks.lv Target Milestone: --- Flags: Translation_missing+ Created attachment 129805 --> https://bugs.kde.org/attachment.cgi?id=129805&action=edit po file, Language: lv_LV, PO-Revision-Date: 2020-07-01 Latvian translation is missing Partly translated *.po file is added as attachment -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 421612] When formatting IDs, removed „small words” still get counted, leading to unexpected results
https://bugs.kde.org/show_bug.cgi?id=421612 --- Comment #2 from nobodyinperson --- Thanks for your work! It seems KDE's migration to https://invent.gitlab.org is now officially live: https://dot.kde.org/2020/06/30/kdes-gitlab-now-live Are you now able to push? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418120] Uninstaller recursively deleted C:/ drive
https://bugs.kde.org/show_bug.cgi?id=418120 --- Comment #8 from ThisIsPaulDaily --- I understand this is resolved, but it may be worth notifying the broader community to avoid the hazard of this happening again. Once the ticket was resolved I had to look into what you changed. I then moved everything into an expected folder path and ran the uninstaller. I would hate to have more people lose everything for installing in a different folder path originally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 m...@rhoatech.com changed: What|Removed |Added CC|m...@rhoatech.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 --- Comment #35 from m...@rhoatech.com --- @Konrad - as far as I can tell at this point it's to do with the Icon set I was using. I am having other issues with the icons now, though it's unrelated to this particular bug. Sorry for the late reply - thanks for the response. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423372] Plasmashell Memory Leak
https://bugs.kde.org/show_bug.cgi?id=423372 --- Comment #7 from Franz Trischberger --- Created attachment 129804 --> https://bugs.kde.org/attachment.cgi?id=129804&action=edit screenshot of top + sensor applets I'm a little bit unsure where the memory goes. I added up all %MEM, makes 21.5%, equals 812MiB. But it says USED=1410.9MiB. Are these missing 600MiB kernel memory? xrestop showed kwin as the only big consumer with little less than 30MB. As you can see no other applications are running currently, so bare desktop + one urxvt window. Also what exactly is that 1.8 GiB the memory applet is showing for Allocated Memory? Neither used nor used+buff/cache match. The old plasmoid showed "used" mem. Could it be that at least part of the leaked memory is GPU memory? I have an intel iGPU that allocates RAM memory (no dedicated memory on GPU). I also experienced quite some GUI lag, even with just a freshly opened firefox + urxvt + tmux - so could it be that GPU memory doesn't get freed? I now rebooted as the system got quite unusable (laptop after 6 days of usage). In case you want some additional info it might take some time. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423711] meta does not open latte menu
https://bugs.kde.org/show_bug.cgi?id=423711 --- Comment #3 from Michail Vourlakos --- Are you building Latte yourself or rely to Arch? It's git version is totally outdated, I think that was fixed four months ago. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423722] uninstallation will delete all files under installation directory
https://bugs.kde.org/show_bug.cgi?id=423722 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Bundle-Windows CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 391073] Latte panels/docks overlap the desktop icons
https://bugs.kde.org/show_bug.cgi?id=391073 --- Comment #8 from Michail Vourlakos --- The next release 0.10 is planned for release in one and half year time -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423704] Pinned applications do not remember the command line parameters used to initially open them
https://bugs.kde.org/show_bug.cgi?id=423704 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423704] Pinned applications do not remember the command line parameters used to initially open them
https://bugs.kde.org/show_bug.cgi?id=423704 --- Comment #4 from Michail Vourlakos --- Sorry this is not Latte responsibility, you need to find a way with plasma devs or you just edit the desktop file to include your parameters. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423612] Trying to access 'trash settings' from krunner opens systemsettings home page instead
https://bugs.kde.org/show_bug.cgi?id=423612 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/131 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417146] compositing disabled on connecting/disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=417146 spittingve...@gmail.com changed: What|Removed |Added CC||spittingve...@gmail.com --- Comment #4 from spittingve...@gmail.com --- still have this problem -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420320] Black screen and no audio as a result of a render
https://bugs.kde.org/show_bug.cgi?id=420320 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 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.
[systemsettings] [Bug 421999] Application Style KCM List Top Problem
https://bugs.kde.org/show_bug.cgi?id=421999 --- Comment #2 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.
[kdenlive] [Bug 422169] Unable to use any other than first picture in directory to add to Slideshow clip
https://bugs.kde.org/show_bug.cgi?id=422169 --- Comment #3 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.
[kdevelop] [Bug 417971] Kdevelop crashes during autocomplete
https://bugs.kde.org/show_bug.cgi?id=417971 --- Comment #9 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.
[lattedock] [Bug 422923] Latte-Dock no panel dock in edit mode (advanced)
https://bugs.kde.org/show_bug.cgi?id=422923 --- Comment #5 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.
[systemsettings] [Bug 421259] Crashes in GtkThemesModel::themePath()
https://bugs.kde.org/show_bug.cgi?id=421259 --- Comment #2 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.
[Discover] [Bug 422271] crash
https://bugs.kde.org/show_bug.cgi?id=422271 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 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 423710] Crashes after I save
https://bugs.kde.org/show_bug.cgi?id=423710 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #16 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.
[korganizer] [Bug 132173] kde pim summary information (addressbook - birthdays) not used in korganizer daemon
https://bugs.kde.org/show_bug.cgi?id=132173 --- Comment #3 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 423724] Open both files when autosave present - Improvement to dialog
https://bugs.kde.org/show_bug.cgi?id=423724 micho...@gmail.com changed: What|Removed |Added Summary|Open both files when|Open both files when |autosave present|autosave present - ||Improvement to dialog -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 380158] Krunner crashs randomly
https://bugs.kde.org/show_bug.cgi?id=380158 --- Comment #3 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 423724] New: Open both files when autosave present
https://bugs.kde.org/show_bug.cgi?id=423724 Bug ID: 423724 Summary: Open both files when autosave present Product: krita Version: 4.3.0 Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: micho...@gmail.com Target Milestone: --- At present, when you attempt to open a file where an autosave exists, a dialog opens up asking you whether you want to open the actual file, or its autosave, along with thumbnail previews. It's very useful, and while the thumbnails make it easier to tell which file you really want, it's not always perfectly clear. In such situations, you generally have to open the autosave first (so that it's not automatically deleted) and then also open the actual save, then compare the contents. I think the dialog could be further improved by adding an option to open both files and/or adding some more info about the file - the date and time of it being saved and filesize, most obviously. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423722] uninstallation will delete all files under installation directory
https://bugs.kde.org/show_bug.cgi?id=423722 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE CC||metzping...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 418120 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423722] uninstallation will delete all files under installation directory
https://bugs.kde.org/show_bug.cgi?id=423722 Maik Qualmann changed: What|Removed |Added Platform|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418120] Uninstaller recursively deleted C:/ drive
https://bugs.kde.org/show_bug.cgi?id=418120 Maik Qualmann changed: What|Removed |Added CC||stdc...@null.net --- Comment #7 from Maik Qualmann --- *** Bug 423722 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 422262] dbus /Windows/1 org.kde.konsole.Window.setCurrentSession doesn't changes session
https://bugs.kde.org/show_bug.cgi?id=422262 Dylan Frese changed: What|Removed |Added CC||dmfr...@gmail.com --- Comment #1 from Dylan Frese --- I can confirm this behaviour. I had a script that would open a text file in vim (from Dolphin etc.) and automatically switch to the Konsole window and to the right tab. This was working some time ago, but does not any more. I'm on Debian Bullseye, Konsole 19.08.1, KDE Frameworks 5.70.0, Plasma version 5.17.5-3. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422547] Small Icons, Large Icons, and Thumbnails task switchers do not respect scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422547 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/7 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423721] Print Report
https://bugs.kde.org/show_bug.cgi?id=423721 --- Comment #1 from Nathan Murray --- I have installed KDE Plasma Workspaces (kde-desktop-environment) group in Fedora 32 to see if the outcome could be changed. There have been no changes from original report using an Appimage. Also after downloading the latest Appimage the problem is still prescient. Further testing shows that when Kmymoney is installed from the Fedora RPMs the reports print without any issues. Fedora 32 RPM: Kmymoney Version 5.0.8 - Appimage: Version 5.1.0-2e0440e --updated Linux/KDE Plasma: Fedora 32 (Workstation Edition) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423723] New: Subjectively speaking, Discover takes too long to be useful after it starts up
https://bugs.kde.org/show_bug.cgi?id=423723 Bug ID: 423723 Summary: Subjectively speaking, Discover takes too long to be useful after it starts up Product: Discover Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@callthecomputerdoctor.com CC: aleix...@kde.org Target Milestone: --- SUMMARY I realize this is subjective, but I and my friend are reluctant to use Discover. Because when it starts, we have to wait for awhile before Discover can be usable. I have a friend who is not an expert who uses Kubuntu 18.04 and 20.04 on his computers and he explicitly doesn't like to use Discover because, as he says, "it's too slow". So he prefers to use Muon. I prefer to use anything else because of the lag before Discover becomes useful. I have a laptop running KDE neon with a SSD, so I'm used to things being responsive. Similarly, it's frustrating because I know that my computer has *already* done an "apt update" because the notifier is telling me that there are system updates. Then I click on the notifier in the system tray, and Discover opens, but it looks like it's doing *another* "apt update" before it wants to show me the updates that it already knows I need. Which contributes to the waiting/unresponsiveness/frustration. I have a slow internet connection, while my friend has a very fast connection, and neither make a difference. I don't know what the solution to this is. Maybe if the computer has just done an update, then don't do another update when Discover starts...? Or have a message saying "Discover hasn't been refreshed in xxx days. Click here to refresh its contents."?? So that way Discover can be immediately useful. STEPS TO REPRODUCE 1. Launch Discover 2. Wait 3. Wait 4. Wait 5. Wait 6. Wait 7. Is it usable yet? No? Wait DESIRED RESULT Discover is usable right after it appears onscreen. Even if its contents aren't valid up to that moment. SOFTWARE/OS VERSIONS Hard drive: SSD Network connection: both slow and fast Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-61-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2467M CPU @ 1.60GHz Memory: 7.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422547] Small Icons, Large Icons, and Thumbnails task switchers do not respect scale factor on X11
https://bugs.kde.org/show_bug.cgi?id=422547 Nate Graham changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |n...@kde.org Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Nate Graham --- Working on this. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423704] Pinned applications do not remember the command line parameters used to initially open them
https://bugs.kde.org/show_bug.cgi?id=423704 --- Comment #3 from Timur Tabi --- I don't know how Plasma taskmanager works, but maybe Latte and/or Plasma could look up the process info when the process icon is being pinned, and then plasma/latte could just remember the parameters being passed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423722] New: uninstallation will delete all files under installation directory
https://bugs.kde.org/show_bug.cgi?id=423722 Bug ID: 423722 Summary: uninstallation will delete all files under installation directory Product: digikam Version: 6.4.0 Platform: Windows CE OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: stdc...@null.net Target Milestone: --- SUMMARY OS: Windows 10 64bit Downloaded digiKam-6.4.0-Win64.exe Installed to d:\Software by mistake, should install to d:\Software\digiKam instead could not find shortcuts in start menu, so perform uninstall by dbl clicking the .exe named something like unist*.exe then this uninstall program started to deleting EVERYTHING under d:\Software no cancel or stop options in this uninstall dialog, only minimize button all my other programs, databases, etc. are gone STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 391073] Latte panels/docks overlap the desktop icons
https://bugs.kde.org/show_bug.cgi?id=391073 --- Comment #7 from Timur Tabi --- I don't want to build lattedock myself, because I don't want to deal with that. I just want to know what/when the next release will be, so I know what to look for. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418071] Moving layers that has any area made with select>fill is slow to move with move tool
https://bugs.kde.org/show_bug.cgi?id=418071 --- Comment #11 from acc4commissi...@gmail.com --- Ok. But since it's fixed anyway I guess I'm happy with this for now. ;D -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #5 from Nate Graham --- > As I want to use kstart from time to time, I installed kde-runtime. Can you clarify? KDE Neon should already have everything you need for a full Plasma environment. What prompted you to install additional things? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423721] New: Print Report
https://bugs.kde.org/show_bug.cgi?id=423721 Bug ID: 423721 Summary: Print Report Product: kmymoney Version: 5.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: nat...@yotux.com Target Milestone: --- SUMMARY When using print function no data is sent to printer. Once CUPS gets the job the page is printed blank. If user chooses to Export from the report (not using print) the report is exported as a CSV file and this file has data shown. STEPS TO REPRODUCE 1. Open Report 2. File -> Print 3. Job is sent to CUPS printed pages are blank. 4. Also when selecting export to PDF via CUPS local export is blank OBSERVED RESULT Prints blank pages from reports EXPECTED RESULT Data from report would be printed on pages SOFTWARE/OS VERSIONS Appimage: Version 5.1.0-7b5b5d7 Linux/KDE Plasma: Fedora 32 (Workstation Edition) (available in About System) KDE Plasma Version: Not Installed KDE Frameworks Version: Not Installed Qt Version: 4.8.7 ADDITIONAL INFORMATION Fedora 32 (Workstation Edition) 64-bit Gnome Version: 3.36.3 Windowing System: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 423668] Screen does not always lock allowing user to mistakenly enter password into other applications (while screen is still dimmed)
https://bugs.kde.org/show_bug.cgi?id=423668 Andrew O. changed: What|Removed |Added Summary|Login password can be |Screen does not always lock |mistakenly entered after|allowing user to mistakenly |logging in |enter password into other ||applications (while screen ||is still dimmed) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 423668] Login password can be mistakenly entered after logging in
https://bugs.kde.org/show_bug.cgi?id=423668 --- Comment #1 from Andrew O. --- So I've been actively trying to reproduce the bug and now have learned a bit more about the nature of the bug. >From what it seems, there are certain scenarios where my Plasma session's screen will turn black without actually locking the screen. Thus, when this occurs, I type in my login password and hit enter before the screen has recovered from being darkened. The issue is that my session is not locked and thus whatever application that was last focused receives the keyboard input. In my Plasma settings, I have: - Power Management >> Energy Saving >> Dim Screen after 10 min - Power Management >> Energy Saving >> Screen energy saving: switch off after 10 min - Power Management >> Energy Saving >> Suspend session is *not* enabled - Workspace Behavior >> Screen locking >> Lock screen automatically after 10 min - Workspace Behavior >> Screen locking >> Lock screen after waking from sleep enabled - Workspace Behavior >> Screen locking >> Allow unlocking without password for: immediately Ideas as to what causes the issue: - Suspend session (in power management) is not enabled. Maybe this would force the session to always lock after a period of inactivity, as per the "Lock screen after waking from sleep enabled" setting. However, ideally, I don't want to resort to suspending my session (as it'll take more time to resume using my laptop) - There is a race condition between "Dim Screen after 10 min" and "Lock screen automatically after 10 min". I don't know why dimming the screen would prevent the locking from occurring, but the fact that the screen dim's but does not lock is suspicious. - "Lock screen automatically after X min" has a bug, and does not always get triggered. For now, I'm going to set automatic screen locking after 5 minutes, to see if the bug continues. I hope this update is a bit more actionable. If further information is required just let me know :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 --- Comment #12 from Nate Graham --- Yeah sorry to disappoint. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 35162] need option to sort combination of TODO and EVENT by time
https://bugs.kde.org/show_bug.cgi?id=35162 gjditchfi...@acm.org changed: What|Removed |Added Component|todoview|monthview Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||gjditchfi...@acm.org --- Comment #3 from gjditchfi...@acm.org --- The Month view now makes a decent effort at sorting items by time, complicated by items with no start dates, or no due dates, or that span dates. The Event List view lets you sort items by date. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 423643] plasma-framework commit 7c4f5c5f1 on qt-5.15.0 broke the systray (and more)
https://bugs.kde.org/show_bug.cgi?id=423643 --- Comment #7 from Friedrich W. H. Kossebau --- Dumped some patch sketches here: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/24 Will continue tomorrow CEST afternoon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 423643] plasma-framework commit 7c4f5c5f1 on qt-5.15.0 broke the systray (and more)
https://bugs.kde.org/show_bug.cgi?id=423643 --- Comment #6 from Friedrich W. H. Kossebau --- (In reply to Aleix Pol from comment #4) > Git commit ac6bff575f934bceab03abdabc6a5c841c5b1f5e by Aleix Pol. > Committed on 01/07/2020 at 01:47. > Pushed by apol into branch 'master'. > > Use fully qualified identifiers for metaobject types > > Fixes QML error: > share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/ > StatusNotifierItem.qml:64: Error: Unknown method return type: ServiceJob* > > M +1-1src/plasma/service.h > > https://invent.kde.org/frameworks/plasma-framework/commit/ > ac6bff575f934bceab03abdabc6a5c841c5b1f5e I fear that would be only one incarnation where the no longer registered type is fixed, instead/additionally we might also want to make sure the unnamespaced pointer and non-pointer types are registered as they had been so far? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 423643] plasma-framework commit 7c4f5c5f1 on qt-5.15.0 broke the systray (and more)
https://bugs.kde.org/show_bug.cgi?id=423643
--- Comment #5 from Friedrich W. H. Kossebau ---
(In reply to Fabian Vogt from comment #3)
> (In reply to Friedrich W. H. Kossebau from comment #2)
> > Looking at the code with this bug report I mind I suspect the new method
> > registers this with the namespace instead, that had slipped my
> > eyes/attention.
>
> Yep, this sounds like a case of https://bugreports.qt.io/browse/QTBUG-50225
That issue you linked finally gave me the clue what could be broken here
(though still unsure what was messed up with my test setup that I saw no issues
or if I was unconcentrated those days without knowing):
The code before my change was this:
```
qmlRegisterInterface("Service");
qRegisterMetaType("Service");
qmlRegisterInterface("ServiceJob");
qRegisterMetaType("ServiceJob");
// [...]
qmlRegisterInterface("DataSource");
qRegisterMetaType("DataSource");
```
Next to that in the headers of the respective classes there is:
```
Q_DECLARE_METATYPE(Plasma::Service *)
Q_DECLARE_METATYPE(Plasma::ServiceJob *)
// nothing for Plasma::DataSource*
```
There are two issues here:
a)
all three classes are subclasses of QObject, and for that the docs of
Q_DECLARE_METATYPE tell us:
"Some types are registered automatically and do not need this macro:
* Pointers to classes derived from QObject
[...]
"
This seems a change in Qt5 over Qt4, but the code, added at Plasma4 times, was
not updated to remove the now unneeded Q_DECLARE_METATYPE declarations.
So, by itself Qt has already registered metatypes for "Plasma::Service",
"Plasma::Service*", "Plasma::ServiceJob", "Plasma::ServiceJob*",
"Plasma::DataSource" & "Plasma::DataSource*", under these full namespaced
names.
Just, some API which is e.g. tagged with Q_INVOKABLE does not use the full
namespace name, but omits the Plasma namespace, like "ServiceJob
*Service::startOperationCall(const QVariantMap &description, QObject *parent)".
And as said in the referenced bug report, that name has to be explicitly
additionally registered, to allow Qt the mapping to the actual type metadata.
But see the current qRegisterMetaType("name") as given above: they miss the
"*" from the name. So they are registering the wrong incomplete name. And so
e.g.
```
qRegisterMetaType("ServiceJob");
```
will not help Qt when it tries to match the type name "ServiceJob*" from the
invokable above to a registered type in the metadata system.
Now why was there no runtime issue with the old code then you ask? Because
```
qmlRegisterInterface("ServiceJob");
```
has saved the day, as its implementation also registers the pointer to the
template class automatically, using the passed name string and appending a "*":
```
template
int qmlRegisterInterface(const char *typeName)
{
QByteArray name(typeName);
QByteArray pointerName(name + '*');
QByteArray listName("QQmlListProperty<" + name + '>');
QQmlPrivate::RegisterInterface qmlInterface = {
1,
qRegisterNormalizedMetaType(pointerName.constData()),
qRegisterNormalizedMetaType
>(listName.constData()),
qobject_interface_iid(),
"",
0
};
return QQmlPrivate::qmlregister(QQmlPrivate::InterfaceRegistration,
&qmlInterface);
}
```
Now the code with Qt 5.15 instead calling the new qmlRegisterInterface<>(const
char *uri, int versionMajor) instead does things using the full name, as
fetched from the metaobject instance:
```
template
int qmlRegisterInterface(const char *uri, int versionMajor)
{
QML_GETTYPENAMES
QQmlPrivate::RegisterInterface qmlInterface = {
1,
qRegisterNormalizedMetaType(pointerName.constData()),
qRegisterNormalizedMetaType>(listName.constData()),
qobject_interface_iid(),
uri,
versionMajor
};
return QQmlPrivate::qmlregister(QQmlPrivate::InterfaceRegistration,
&qmlInterface);
}
```
Thus the day is no longer saved.
This would be my sleepy analyis of the cause. Not sure if this can be easily
fixed. Possibly better to revert my commit and do a fully experts-checked patch
for 5.73 then?
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-plasma] [Bug 423643] plasma-framework commit 7c4f5c5f1 on qt-5.15.0 broke the systray (and more)
https://bugs.kde.org/show_bug.cgi?id=423643 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/com ||mit/ac6bff575f934bceab03abd ||abc6a5c841c5b1f5e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Aleix Pol --- Git commit ac6bff575f934bceab03abdabc6a5c841c5b1f5e by Aleix Pol. Committed on 01/07/2020 at 01:47. Pushed by apol into branch 'master'. Use fully qualified identifiers for metaobject types Fixes QML error: share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml:64: Error: Unknown method return type: ServiceJob* M +1-1src/plasma/service.h https://invent.kde.org/frameworks/plasma-framework/commit/ac6bff575f934bceab03abdabc6a5c841c5b1f5e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423720] New: KDE Wallet KCM doesn't launch Wallet Manager
https://bugs.kde.org/show_bug.cgi?id=423720 Bug ID: 423720 Summary: KDE Wallet KCM doesn't launch Wallet Manager Product: systemsettings Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: uhh...@gmail.com Reporter: k...@callthecomputerdoctor.com CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open System Settings -> Account Details -> KDE Wallet 2. In the lower right-hand corner, click on the button that says "Launch Wallet Manager" OBSERVED RESULT Wallet Manager does not launch. EXPECTED RESULT Wallet Manager should appear. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-61-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2467M CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa DRI Intel® Sandybridge Mobile -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423711] meta does not open latte menu
https://bugs.kde.org/show_bug.cgi?id=423711 --- Comment #2 from andresdor...@gmail.com --- Created attachment 129803 --> https://bugs.kde.org/attachment.cgi?id=129803&action=edit latte layout here is my latte layout like I said i tried checking the setting box that says use meta for app launcher and it won't let me hit apply and when I close the window and reopen it it's unset again -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 423660] Class Diagram Widget Text Truncated Upon Re-Opening XMI
https://bugs.kde.org/show_bug.cgi?id=423660 --- Comment #2 from Ralf Habacker --- (In reply to Stanley Rekofsky from comment #0) > Upon saving the XMI and re-opening the XMI on the same device/display > all Class widgets have the text information in them truncated. >From inspecting the source it looks that the clipping happens in ClassifierWidget::drawMembers() where class attributes and operations are displayed. Inside the method a call to painter->drawText(x, y, fontMetrics.size(0, text).width(), fontHeight, Qt::AlignVCenter, text); is performed, where the text width in pixel is determined by the term `fontMetrics.size(0, text).width()`. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 423635] Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264
https://bugs.kde.org/show_bug.cgi?id=423635 --- Comment #2 from Raoul Snyman --- I ran kdenlive from the terminal, and when I opened the Render dialog, this was the output in my terminal: --- formats: - a64 - ac3 - adts - adx - aiff - amr - apng - aptx - aptx_hd - asf - ass - ast - asf_stream - au - avi - avm2 - avs2 - bit - caf - cavsvideo - codec2 - codec2raw - crc - dash - data - daud - dirac - dnxhd - dts - dv - eac3 - f4v - ffmetadata - fifo - fifo_test - filmstrip - fits - flac - flv - framecrc - framehash - framemd5 - g722 - g723_1 - g726 - g726le - gif - gsm - gxf - h261 - h263 - h264 - hash - hds - hevc - hls - ico - ilbc - image2 - image2pipe - ipod - ircam - ismv - ivf - jacosub - kvag - latm - lrc - m4v - md5 - matroska - matroska - microdvd - mjpeg - mlp - mmf - mov - mp2 - mp3 - mp4 - mpeg - vcd - mpeg1video - dvd - svcd - mpeg2video - vob - mpegts - mpjpeg - mxf - mxf_d10 - mxf_opatom - null - nut - oga - ogg - ogv - oma - opus - alaw - mulaw - vidc - f64be - f64le - f32be - f32le - s32be - s32le - s24be - s24le - s16be - s16le - s8 - u32be - u32le - u24be - u24le - u16be - u16le - u8 - psp - rawvideo - rm - roq - rso - rtp - rtp_mpegts - rtsp - sap - sbc - scc - film_cpk - segment - stream_segment,ssegment - singlejpeg - smjpeg - smoothstreaming - sox - spx - spdif - srt - streamhash - sup - swf - tee - 3g2 - 3gp - mkvtimestamp_v2 - truehd - tta - uncodedframecrc - vc1 - vc1test - voc - w64 - wav - webm - webm_dash_manifest - webm_chunk - webp - webvtt - wtv - wv - yuv4mpegpipe - chromaprint - alsa - caca - fbdev - opengl - oss - pulse - sdl,sdl2 - sndio - video4linux2,v4l2 - xv ... --- audio_codecs: - comfortnoise - dvaudio - 8svx_exp - 8svx_fib - s302m - aac - aac_fixed - aac_latm - ac3 - ac3_fixed - acelp.kelvin - alac - als - amrnb - amrwb - ape - aptx - aptx_hd - atrac1 - atrac3 - atrac3al - atrac3plus - atrac3plusal - atrac9 - bmv_audio - cook - dca - dolby_e - dsd_lsbf - dsd_msbf - dsd_lsbf_planar - dsd_msbf_planar - dsicinaudio - dss_sp - dst - eac3 - evrc - wavesynth - flac - g723_1 - g729 - gsm - gsm_ms - hca - hcom - iac - ilbc - imc - interplayacm - mace3 - mace6 - metasound - mlp - mp1 - mp1float - mp2 - mp2float - mp3float - mp3 - mp3adufloat - mp3adu - mp3on4float - mp3on4 - mpc7 - mpc8 - nellymoser - on2avc - opus - paf_audio - qcelp - qdm2 - qdmc - real_144 - real_288 - ralf - sbc - shorten - sipr - siren - smackaud - sonic - tak - truehd - truespeech - tta - twinvq - vmdaudio - vorbis - wavpack - wmalossless - wmapro - wmav1 - wmav2 - wmavoice - ws_snd1 - xma1 - xma2 - pcm_alaw - pcm_bluray - pcm_dvd - pcm_f16le - pcm_f24le - pcm_f32be - pcm_f32le - pcm_f64be - pcm_f64le - pcm_lxf - pcm_mulaw - pcm_s8 - pcm_s8_planar - pcm_s16be - pcm_s16be_planar - pcm_s16le - pcm_s16le_planar - pcm_s24be - pcm_s24daud - pcm_s24le - pcm_s24le_planar - pcm_s32be - pcm_s32le - pcm_s32le_planar - pcm_s64be - pcm_s64le - pcm_u8 - pcm_u16be - pcm_u16le - pcm_u24be - pcm_u24le - pcm_u32be - pcm_u32le - pcm_vidc - derf_dpcm - gremlin_dpcm - interplay_dpcm - roq_dpcm - sdx2_dpcm - sol_dpcm - xan_dpcm - adpcm_4xm - adpcm_adx - adpcm_afc - adpcm_agm - adpcm_aica - adpcm_argo - adpcm_ct - adpcm_dtk - adpcm_ea - adpcm_ea_maxis_xa - adpcm_ea_r1 - adpcm_ea_r2 - adpcm_ea_r3 - adpcm_ea_xas - g722 - g726 - g726le - adpcm_ima_amv - adpcm_ima_alp - adpcm_ima_apc - adpcm_ima_apm - adpcm_ima_cunning - adpcm_ima_dat4 - adpcm_ima_dk3 - adpcm_ima_dk4 - adpcm_ima_ea_eacs - adpcm_ima_ea_sead - adpcm_ima_iss - adpcm_ima_mtf - adpcm_ima_oki - adpcm_ima_qt - adpcm_ima_rad - adpcm_ima_ssi - adpcm_ima_smjpeg - adpcm_ima_wav - adpcm_ima_ws - adpcm_ms - adpcm_mtaf - adpcm_psx - adpcm_sbpro_2 - adpcm_sbpro_3 - adpcm_sbpro_4 - adpcm_swf - adpcm_thp - adpcm_thp_le - adpcm_vima - adpcm_xa - adpcm_yamaha - adpcm_zork - libcodec2 - libgsm - libgsm_ms - libopus - libspeex - libvorbis ... --- video_codecs: - h263_v4l2m2m - h264_v4l2m2m - h264_vaapi - hevc_v4l2m2m - hevc_vaapi - mjpeg_vaapi - mpeg2_vaapi - mpeg4_v4l2m2m - vp8_v4l2m2m - vp8_vaapi - vp9_vaapi - aasc - aic - alias_pix - agm - amv - anm - ansi - apng - arbc - asv1 - asv2 - aura - aura2 - avrp - avrn - avs - avui - ayuv - bethsoftvid - bfi - binkvideo - bitpacked - bmp - bmv
[kdenlive] [Bug 423635] Unsupported video codec: libx264 / Codec de vídeo não suportado: libx264
https://bugs.kde.org/show_bug.cgi?id=423635 Raoul Snyman changed: What|Removed |Added CC||ra...@snyman.info --- Comment #1 from Raoul Snyman --- I'm also seeing this. According to FFMPEG, I have the ability to encode via libx264. Platform: Debian sid Packages: ffmpeg/unstable,now 7:4.3-2 amd64 [installed,automatic] Tools for transcoding, streaming and playing of multimedia files libavcodec58/unstable,now 7:4.3-2 amd64 [installed] FFmpeg library with de/encoders for audio/video codecs - runtime files libx264-155/unstable,now 2:0.155.2917+git0a84d98-2 amd64 [installed,automatic] x264 video coding library ffmpeg output: $ ffmpeg -codecs ffmpeg version 4.3-2 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9 (Debian 9.3.0-13) configuration: --prefix=/usr --extra-version=2 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat58. 45.100 / 58. 45.100 libavdevice58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc55. 7.100 / 55. 7.100 --- DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m h264_qsv ) (encoders: libx264 libx264rgb h264_omx h264_qsv h264_v4l2m2m h264_vaapi ) I tried to set the "Bypass codec verification" option, and that seemed to have no effect. I also tried to re-run the config wizard a few times, and a green notification showed up saying the codecs had been updated, but also no joy. Let me know what other information I can provide. This is seriously impacting my video production :-( -- the WebM output is terrible quality, even at the maximum. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423719] New: system settings crash
https://bugs.kde.org/show_bug.cgi?id=423719 Bug ID: 423719 Summary: system settings crash Product: systemsettings Version: 5.19.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chaicopadil...@gmail.com Target Milestone: --- Application: systemsettings5 (5.19.2) (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-61-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: - Custom settings of the application: the system settings are blocked only when you are downloading packages like themes and styles and then you don't want to open and I have to restart my pc The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x2825048b48) at /usr/include/c++/7/bits/atomic_base.h:396 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x2825048b48) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref (this=0x2825048b48) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:55 #8 QString::QString (other=..., this=0x7ffeb28ced70, this@entry=0x7ffeb28ced68) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1051 #9 KJob::errorText (this=this@entry=0x5565d23b9020) at ./src/lib/jobs/kjob.cpp:202 #10 0x7ffab0a793cf in KNSCore::KPackageJoboperator() (job=0x5565d23b9020, __closure=0x5565d1b92eb0) at ./src/core/jobs/kpackagejob.cpp:143 #11 QtPrivate::FunctorCall, QtPrivate::List, void, KNSCore::KPackageJob::start():: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #12 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #13 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x5565d1b92ea0, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #14 0x7ffb15eff57b in QObject::event (this=0x5565d2799640, e=0x5565d22fea60) at kernel/qobject.cpp:1339 #15 0x7ffb1704b9ac in QApplicationPrivate::notify_helper (this=this@entry=0x5565cf695700, receiver=receiver@entry=0x5565d2799640, e=e@entry=0x5565d22fea60) at kernel/qapplication.cpp:3685 #16 0x7ffb17052bb0 in QApplication::notify (this=0x7ffeb28cf480, receiver=0x5565d2799640, e=0x5565d22fea60) at kernel/qapplication.cpp:3431 #17 0x7ffb15ecc4a8 in QCoreApplication::notifyInternal2 (receiver=0x5565d2799640, event=0x5565d22fea60) at kernel/qcoreapplication.cpp:1075 #18 0x7ffb15ecc67e in QCoreApplication::sendEvent (receiver=receiver@entry=0x5565d2799640, event=event@entry=0x5565d22fea60) at kernel/qcoreapplication.cpp:1470 #19 0x7ffb15ecf121 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5565cf68bfd0) at kernel/qcoreapplication.cpp:1815 #20 0x7ffb15ecf6b8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1674 #21 0x7ffb15f2c103 in postEventSourceDispatch (s=0x5565cf712e60) at kernel/qeventdispatcher_glib.cpp:277 #22 0x7ffb0e77e417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7ffb0e77e650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7ffb0e77e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7ffb15f2b7ac in QEventDispatcherGlib::processEvents (this=0x5565cf714270, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7ffb15ecad2a in QEventLoop::exec (this=this@entry=0x7ffeb28cf330, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #27 0x7ffb15ed44a0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1383 #28 0x5565ce819804 in main (argc=, argv=) at ./app/main.cpp:168 The reporter indicates this bug may be a duplicate of or related to bug 422451. Possible duplicates by query: bug 422451, bug 422092, bug 421016, bug 420495, bug 417542. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 423660] Class Diagram Widget Text Truncated Upon Re-Opening XMI
https://bugs.kde.org/show_bug.cgi?id=423660 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Ralf Habacker --- (In reply to Stanley Rekofsky from comment #0) > Is there some additional diagram setting that needs to be checked? After loading such files changing the default font fixes this issue for the currently loaded file. > Or is this an existing bug? I did not recognized this bug before, which a Windows 10 specific bug. It would be for interest, if this bug is present in previous releases and if not, with which version it was introduced. Previous releases can be downloaded from https://download.kde.org/stable/umbrello/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423718] Krita does not open, Event 1000, Application Error
https://bugs.kde.org/show_bug.cgi?id=423718 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Tymond --- Try to reset the configuration: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration and get us a crash log: https://docs.krita.org/en/reference_manual/dr_minw_debugger.html also please note that you installed Krita inside Documents on your OneDrive... is it intentional and if so, why? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423718] New: Krita does not open, Event 1000, Application Error
https://bugs.kde.org/show_bug.cgi?id=423718 Bug ID: 423718 Summary: Krita does not open, Event 1000, Application Error Product: krita Version: unspecified Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: e.moral...@gmail.com Target Milestone: --- When attempting to open any version of Krita, the OS shows it is loading but the splash screen does not show and nothing opens. I have tried multiple steps; uninstalling/reinstalling, restarting PC, cleaning registry and hard drive, and running the debug for older versions. SOFTWARE/OS VERSIONS Windows: 10 Home ADDITIONAL INFORMATION Log Name: Application Source:Application Error Date: 6/30/2020 3:46:50 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-RGEREUQ Description: Faulting application name: krita.exe, version: 0.0.0.0, time stamp: 0x Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x Exception code: 0xc005 Fault offset: 0x Faulting process id: 0x2734 Faulting application start time: 0x01d64f172f3b1331 Faulting application path: C:\Users\othel\OneDrive\Documents\Krita (x64)\bin\krita.exe Faulting module path: unknown Report Id: 0fdf2ce7-afa9-4c13-b979-a17432f70d65 Faulting package full name: Faulting package-relative application ID: Event Xml: http://schemas.microsoft.com/win/2004/08/events/event";> 1000 2 100 0x80 20642 Application DESKTOP-RGEREUQ krita.exe 0.0.0.0 unknown 0.0.0.0 c005 2734 01d64f172f3b1331 C:\Users\othel\OneDrive\Documents\Krita (x64)\bin\krita.exe unknown 0fdf2ce7-afa9-4c13-b979-a17432f70d65 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 423420] kde_wacom_table segfault
https://bugs.kde.org/show_bug.cgi?id=423420 christ.de...@gmail.com changed: What|Removed |Added CC||christ.de...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 422289] First delegate of ListView within OverlaySheet it's initially drawn at wrong position
https://bugs.kde.org/show_bug.cgi?id=422289 --- Comment #4 from Ismael Asensio --- I agree that this "fix" can break other existing apps that relay on non-visible delagates not taking any space (QQC2.ItemDelegate also behaves that way, but I think AbstractListItem does the right thing). But I think the problem is important enough as not to keep looking for the cause. When more and more apps are being migrated to kirigami, it's a matter of time that this will pop-up in more important places. I wonder why this affects only the first item y-position, and not the rest of them. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #4 from Nico Dorn --- All of them are checked. I don't think I ever disabeled those. A wild guess: As I want to use kstart from time to time, I installed kde-runtime. A lot of dependencies as I remember. Could that have caused the issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423717] New: Feature request : Introduce a Blend Modes Context Menu for the paintbrush tool
https://bugs.kde.org/show_bug.cgi?id=423717 Bug ID: 423717 Summary: Feature request : Introduce a Blend Modes Context Menu for the paintbrush tool Product: krita Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- Created attachment 129802 --> https://bugs.kde.org/attachment.cgi?id=129802&action=edit Blend Mode Context Menu(brush only) SUMMARY Greetings. This feature request is about having a context menu that displays a list of selectable blend modes with the paint brush selected. Its purpose is to offer the fastest possible way to change the paintbrush's current blend mode. How would we use it ? STEPS TO REPRODUCE 1. Hold first Shift modifier key then Right Click on your mouse or pen button 2. The context menu appears around cursor position and shows a list of blend modes to select from 3. hover your mouse to the wanted blend mode and left click to switch your paintbrush's blend mode to the blend mode selected from the context menu EXPECTED RESULT : The paintbrush's current blend mode is changed to the selected one. The context menu dismisses just after selection is done or when pressing Esc. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423716] New: crash when in make research
https://bugs.kde.org/show_bug.cgi?id=423716 Bug ID: 423716 Summary: crash when in make research Product: Discover Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: flank...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-9-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: search app (vlc) after long time of works crash ... the crash repeat again... firefox open and terminal (Konsole). The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffa73123800 (LWP 14040))] Thread 12 (Thread 0x7ffa4f7fe700 (LWP 14081)): #0 0x7ffa71ce1fc1 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7ffa71ce34be in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ffa7018d669 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa7018e06b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa7018e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffa71ce3743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffa71c9115b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffa71ae0e76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ffa71aeaa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ffa70c37fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7ffa717d14cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 11 (Thread 0x7ffa4effd700 (LWP 14077)): #0 0x7ffa701d7e69 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ffa7018d675 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa7018e06b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa7018e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa71ce3743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ffa71c9115b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffa71ae0e76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffa71aeaa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ffa70c37fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7ffa717d14cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7ffa33fff700 (LWP 14074)): #0 0x7ffa717c6819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7ffa7018e136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa7018e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa71ce3743 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ffa71c9115b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ffa71ae0e76 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ffa71aeaa67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffa70c37fa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7ffa717d14cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7ffa4de6e700 (LWP 14055)): #0 0x7ffa717c8427 in ioctl () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7ffa5a3219fc in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #2 0x7ffa5a3229e7 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #3 0x7ffa5a323943 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #4 0x7ffa59ea179a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #5 0x7ffa59f89a25 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #6 0x7ffa59e800ce in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.440.82 #7 0x7ffa5b0681d4 in ?? () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #8 0x7ffa5b03d071 in glXSwapBuffers () from /lib/x86_64-linux-gnu/libGLX_nvidia.so.0 #9 0x7ffa6d601146 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #10 0x7ffa7251dc7b in QOpenGLContext::swapBuffers(QSurface*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7ffa735b8686 in ??
[krita] [Bug 423630] [Steam] Create Start Menu icon
https://bugs.kde.org/show_bug.cgi?id=423630 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com --- Comment #7 from Emmet O'Neill --- Hey kmi, Steam kind of plays by its own rules in terms of how it installs things on your PC. Unlike our non-Steam installer, we basically just give it a depot of files, all of the installing and even the running is done the way Steam wants it done. There are a few options: 1.) Like any other game, you can ask Steam to create a desktop shortcut for Krita. I've heard some people have had success pinning that desktop shortcut to their menu by prefixing the path with "%windir%\explorer.exe" (i.e.: "%windir%\explorer.exe steam://rungameid/280680", for Krita). I just tried this and I couldn't make it work, though... Windows 10 is very fickle about what it lets you pin. 2.) Another option is to navigate to the folder where Steam installs Krita. (Right-click Krita in the Library > Manage > Browse local files.) From there you can find krita.exe in the bin\ folder, and pin that executable to the Window 10 start menu without issue. The minor downside being that, by doing this, you'll no longer be running Krita through Steam which will prevent Steam from seeing that you're running Krita, from what I can tell. While it might not be the outcome you want, we wont be adding a checkbox like you've suggested to our settings menu. Krita is distributed through a lot of different channels on each platform, source code, .exe, .appimage, flatpak, distro repositories, Steam, Windows Store, etc. Each of these platforms and delivery methods has minor trade-offs and, while we want to make every one as nice as possible for our users, ultimately it wouldn't be sustainable to add a bunch of little workaround to the core of Krita. As the person who has been managing Steam for a couple of years, there may be more that I can do to improve the way Krita on Steam integrates with the desktop, and I'll look into it when I have time. But for now please understand that Steam kind of sees itself as a package manager and launcher and it likes things to work a certain way and doesn't integrate very well with Windows or Linux desktops. If neither of the above workarounds work for you, send me an email and I can see if I can help you get a refund on Steam and maybe move to the regular desktop version of Krita. - Emmet -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423715] New: freeze on monitor disconnect with opengl enabled
https://bugs.kde.org/show_bug.cgi?id=423715 Bug ID: 423715 Summary: freeze on monitor disconnect with opengl enabled Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: mich...@schima.cc Target Milestone: --- Created attachment 129801 --> https://bugs.kde.org/attachment.cgi?id=129801&action=edit view of the corrupted screen Plasma freezes when I unplugging the display that came up first when booting (the one that showed the kernel log) when multiple displays are used The issue also occurs when booted with a single display and another is added later Note that this only happens when the compositor is enabled and using opengl 2.0 or 3.1, not with xrandr backend. When plugged back in, the previously disconnected display seems to spill graphics memory. (see attached images) STEPS TO REPRODUCE 1. identify the monitor that shows the kernel log on boot up 2. log into a plasma session 3. disconnect the monitor that showed the kernel log (the freeze should now occur) 4. reconnecting does not solve the issue The issue does NOT occur when: - Only a single display is connected to the system - compositor is disabled or using xrandr Displays used: 1:Displayport - Samsung U28E570D (2160p) 2: HDMI - Samsung T23B350 (1080p) System Information: Operating System: Arch Linux KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.6-arch1-1 OS Type: 64-bit Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT GL_VERSION: 4.6 (Compatibility Profile) Mesa 20.1.2 GL_RENDERER: AMD Radeon RX 5700 XT (NAVI10, DRM 3.37.0, 5.7.6-arch1-1, LLVM 10.0.0) GL_VENDOR: X.Org GL_SHADING_LANGUAGE_VERSION = 4.60 GLU_VERSION: 1.3 GLU_EXTENSIONS: GLU_EXT_nurbs_tessellator GLU_EXT_object_space_tess GLUT_API_VERSION: 4 GLUT_XLIB_IMPLEMENTATION: 13 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417140] Map panel shows white rectangle when using Google Maps
https://bugs.kde.org/show_bug.cgi?id=417140 --- Comment #10 from tpg --- Great! Bingo! Thanks a lot. ' Vriendelijke groet, Theo Groen Op di 30 jun. 2020 om 21:40 schreef Maik Qualmann : > https://bugs.kde.org/show_bug.cgi?id=417140 > > --- Comment #9 from Maik Qualmann --- > Look at bug 417008, you need to create a symbolic link: > > ln -s /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so /usr/lib/ > > Maik > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 --- Comment #11 from Alexandre Pereira --- well, i was hoping this was something that devs would reply " yeah we know, we are implementing this and it will work when its done ". I it still giving problems, I can on the weekend try reverting back to specific commits and try to find what really broke this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423345] System tray doesn't show hidden icons by default
https://bugs.kde.org/show_bug.cgi?id=423345 --- Comment #10 from joey.joey...@gmail.com --- Ok, so I decided to do another fresh Arch Linux Plasma install and it worked; the "show hidden icons" button wasn't hidden anymore. (Technically it still happens but only when logging in to a newly created user; logging out and logging back in doesn't cause the button to disappear anymore) Umm...so I have a confession to make: that "fresh Arch Plasma" install with the hidden icons bug was a fresh install of Arch I made around 6 months ago. So I made a fresh install using the Arch Live ISO then compressed it to an .sfs file as a backup in case I ever broke my Arch system and needed a quick restore. Recently I updated that backup and the bug started occurring. I'm not really sure what happened; most likely something broke during the upgrade process that caused this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Keywords||regression --- Comment #10 from Nate Graham --- Darn, thanks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #12 from edisonalvari...@bol.com.br --- (In reply to Nate Graham from comment #11) > (In reply to edisonalvaringo from comment #10) > > this is on ubuntu focal using kde from archive.kde.neon.org > FWIW that's not a supported configuration and as such it confuses the issue > because now I don't know if it's a real problem in the code or a local > misconfiguration. > See https://neon.kde.org/faq. yes but it also happens on kubuntu 20.04 lts default, I had to try a different configuration just in case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 --- Comment #9 from Alexandre Pereira --- just some info: The only "possible weird setup I might have" is that I have multiple monitors and use more than one activity. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 --- Comment #8 from Alexandre Pereira --- I removed the mentioned lines. when I logged in, I customized some wallpapers and logged out. logging in again, wallpapers are still default, but now the definitions on plasma shell file aren't written! so no, the line does not reappear -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #11 from Nate Graham --- (In reply to edisonalvaringo from comment #10) > this is on ubuntu focal using kde from archive.kde.neon.org FWIW that's not a supported configuration and as such it confuses the issue because now I don't know if it's a real problem in the code or a local misconfiguration. See https://neon.kde.org/faq. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 391073] Latte panels/docks overlap the desktop icons
https://bugs.kde.org/show_bug.cgi?id=391073 --- Comment #6 from Michail Vourlakos --- Latest git version. You should build Latte yourself if your distro git version is outdated. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423711] meta does not open latte menu
https://bugs.kde.org/show_bug.cgi?id=423711 --- Comment #1 from Michail Vourlakos --- Of course and there isn't because it reads the kwinrc file which is also responsible for this. Are you sure it does not work? Send me please your Latte layout file to check it out. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423704] Pinned applications do not remember the command line parameters used to initially open them
https://bugs.kde.org/show_bug.cgi?id=423704 --- Comment #2 from Michail Vourlakos --- Latte is using Plasma for its launchers, how do you solve this with Plasma taskmanagers? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423630] [Steam] Create Start Menu icon
https://bugs.kde.org/show_bug.cgi?id=423630 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Boudewijn Rempt --- It is not controversial; it is nonsensical. No Windows application manages the presence or absence of an entry in the start menu in its settings dialog. That's the job of whatever mechanism installs the application. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 394826] Add support for HEIF/HEIC
https://bugs.kde.org/show_bug.cgi?id=394826 sir...@bakke.co changed: What|Removed |Added CC||sir...@bakke.co --- Comment #3 from sir...@bakke.co --- I've added code for HEIF support in this pull request: https://invent.kde.org/frameworks/kimageformats/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #10 from edisonalvari...@bol.com.br --- this is on ubuntu focal using kde from archive.kde.neon.org, as you can see the gtk2 theme is defaulting to the gtk3 version instead of using the gtk2 one. If it helps also on konsole I get this error when launching gtk2 apps, Gtk-CRITICAL **: 17:58:56.783: IA__gtk_widget_set_colormap: assertion '!gtk_widget_get_realized (widget)' failed https://drive.google.com/file/d/1aMfSg57QvzOE4S_DwTbCkExmy0oPsER_/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423714] Krita crashes when I save
https://bugs.kde.org/show_bug.cgi?id=423714 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED CC||b...@valdyas.org Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 423710 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423710] Crashes after I save
https://bugs.kde.org/show_bug.cgi?id=423710 --- Comment #4 from Boudewijn Rempt --- *** Bug 423714 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423710] Crashes after I save
https://bugs.kde.org/show_bug.cgi?id=423710 Boudewijn Rempt changed: What|Removed |Added Platform|Other |MS Windows OS|Other |Microsoft Windows --- Comment #3 from Boudewijn Rempt --- I'm sorry, but yes, you did not give the right information. You made a new bug report which said: "ADDITIONAL INFORMATION ** Help->Show System Information for Bug Reports ** Help->Show Krita Log for Bug Reports 1. My device has one single side hard drive 2. It has plenty of space 3. I use Malware Bytes" So, you did not add the information from krita for the first two points to this bug report; the other answers help. Malware bytes means you're using Windows -- and you shouldn't use that, because Windows 10's Defender is sufficient. Do not use any 3rd party antivirus or security software _at all_. I still need to see the contents of the system info and log dialogs to help you further. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 363360] Password of net connection is not saved, if add the NAS server location
https://bugs.kde.org/show_bug.cgi?id=363360 Davide Gianforte changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dav...@gengisdave.org --- Comment #2 from Davide Gianforte --- Can you reproduce on a newer version? I've tried with the 2.8.0+ (git), I can create a network connection (remote:/) and save the password in the local wallet. I can edit the bookmark pointing to the remote, where the password is not shown/stored. A different username will ask for new credentials and rolling back to the original one, it pops the password from the wallet again. If you cannot create remote connection from Krusader (because the "Add Network Folder" is opened in Kate as a text file), you can do it in Dolphin without worries, remote:/ is shared in KDE. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423630] [Steam] Create Start Menu icon
https://bugs.kde.org/show_bug.cgi?id=423630 --- Comment #5 from kmi --- (In reply to Boudewijn Rempt from comment #4) > Actually, apparently you can enable whether an application has a start menu > entry in steam's settings? Nope, only a desktop icon that links to steam://rungameid/280680 (which also means that Steam will launch first, ie. the startup time is horrible even with an SSD). Quite frankly, I'm puzzled that a relatively minor request that would help people who paid for Krita would be so controversial. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423433] plasma shell doesn't load user specified wallpapers, always default
https://bugs.kde.org/show_bug.cgi?id=423433 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Nate Graham --- Thanks, so this is a regression on master then. Still cannot reproduce. If yo remove the following line from your plasma-org.kde.plasma.desktop-appletsrc file: [Containments][350][Wallpaper][org.kde.image][General] Image=file:///usr/share/wallpapers/Next/contents/images/2560x1440.jpg Does the problem get fixed? And if not, does that line re-appear? -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 400929] kwallet-pam errors when logging into Plasma from lightdm
https://bugs.kde.org/show_bug.cgi?id=400929 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423612] Trying to access 'trash settings' from krunner opens systemsettings home page instead
https://bugs.kde.org/show_bug.cgi?id=423612 Nate Graham changed: What|Removed |Added Product|krunner |systemsettings Component|general |general Assignee|k...@privat.broulik.de |plasma-b...@kde.org Priority|NOR |VHI --- Comment #4 from Nate Graham --- Darn, this is no good. I guess we have two immediate options: 1. Have the openSystemSettings() function check for the presence of a X-KDE-System-Settings-Parent-Category property and open it in KCMShell if it's missing 2. Allow System Settings itself to display KCMs without the X-KDE-System-Settings-Parent-Category property #1 Cannot be released as a hotfix in Plasma since it lives in the KDeclarative framework which is on a different release schedule (though I suppose we could ask distros to patch it into their older versions). But #2 might be a bit confusing since these KCMs don't otherwise appear in System Settings. Regardless, moving to System Settings for now. Thoughts, everyone? Also I feel like the concept of KCMs that don't appear in System Settings itself somewhat awkward and we may want to review that, long term. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423710] Crashes after I save
https://bugs.kde.org/show_bug.cgi?id=423710 --- Comment #2 from Ollie --- I responded. I'm sorry if I did so incorrectly. Thank you for your help! On Tue, Jun 30, 2020, 1:31 PM Boudewijn Rempt wrote: > https://bugs.kde.org/show_bug.cgi?id=423710 > > Boudewijn Rempt changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt --- > So... This obviously doesn't happen to everyone; in fact, if it were common > we'd have hundreds of thousands of reports like this. So we need to figure > out > what is up with your system that Krita is unstable on it. > > For that we need information: > > * Please open the bug report in your browser and paste the contents of the > following two dialogs in two separate Additional Comment boxes: > > ** Help->Show System Information for Bug Reports > ** Help->Show Krita Log for Bug Reports > > Then we need details about your system only you can provide: > > 1) Do you have a system with multiple storage devices? If so, which one > are you > saving to? > 2) Do those storage devices have enough free space left? > 3) Are you running any security software other than which came with your > OS? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423714] New: Krita crashes when I save
https://bugs.kde.org/show_bug.cgi?id=423714 Bug ID: 423714 Summary: Krita crashes when I save Product: krita Version: 4.3.0 Platform: MS Windows OS: All Status: REPORTED Severity: crash Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: olliewa...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION ** Help->Show System Information for Bug Reports ** Help->Show Krita Log for Bug Reports 1. My device has one single side hard drive 2. It has plenty of space 3. I use Malware Bytes -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423148] Okular crashes when opening a random PDF from Dolphin, but apparently only with certain screen arrangements.
https://bugs.kde.org/show_bug.cgi?id=423148 --- Comment #13 from David Hurka --- Thanks for all the information! I see that you disabled the laptop screen. Still, only using my one external screen vertically doesn’t crash for me... Crash at opening a new tab supports my theory that QScroller is set up differently when PageView is created when there is already a document loaded. If I have some time soon, I might look into the PageView code related to QScroller. Maybe I will ask you about some gdb output about QScreen, but I don’t know what exactly yet. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 420902] Site info falsely claims that connection is secure after certificate exception
https://bugs.kde.org/show_bug.cgi?id=420902 --- Comment #7 from Florian Bruhin --- > It's a simple choice between maintaining a temporary or permanent, per-domain > list of exceptions once a user chooses to ignore the cert error. Which is what I already proposed in comment 1 above. The problem with that is that it will still mark the connection as insecure even after the certificate has been fixed. But we're going in circles here, that's all already explained in the comments above. -- You are receiving this mail because: You are watching all bug changes.
