[plasmashell] [Bug 391010] Kmail closes by clicking the "Security" tab
https://bugs.kde.org/show_bug.cgi?id=391010 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #3 from Kai Uwe Broulik --- I have seen that crash after updating to Qt 5.10 but it went away when I recompiled KMail from git -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391010] Kmail closes by clicking the "Security" tab
https://bugs.kde.org/show_bug.cgi?id=391010 Kai Uwe Broulik changed: What|Removed |Added Product|plasmashell |kmail2 Target Milestone|1.0 |--- Assignee|plasma-b...@kde.org |kdepim-b...@kde.org Version|5.12.2 |unspecified Component|generic-crash |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351906] Auto hidden panels are not hidden on start
https://bugs.kde.org/show_bug.cgi?id=351906 --- Comment #16 from Marian Kyral --- I can still reproduce on Plasma 5.12.3 with active borders on. Panel is not hidden on start, it hides on mouse over. But never rise up again. Plasma: 5.12.3 Apps: 17.12.2 Frameworks: 5.43.0 Qt: 5.9.4 Kernel: 4.15.4-gentoo OS: Gentoo Video: Intel integrated, 4th generation x11-drivers/xf86-video-intel-2.99.917_p20171018 Screen: 1920x1080 Could be a Qt issue? I've no 5.10 available yet. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 390977] Turning off display with xset results in screenlocker freezing when display is turned on again
https://bugs.kde.org/show_bug.cgi?id=390977 --- Comment #2 from Kishore Gopalakrishnan --- I cannot reproduce this with kscreenlocker 5.12.3. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391426] Incoming chat request appears in wrong category, text doesn't show
https://bugs.kde.org/show_bug.cgi?id=391426 Laurent Montel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ruq ||ola/7270d73abc30b45ddfdc62a ||485898cc8d3360f36 --- Comment #3 from Laurent Montel --- Git commit 7270d73abc30b45ddfdc62a485898cc8d3360f36 by Laurent Montel. Committed on 07/03/2018 at 08:17. Pushed by mlaurent into branch 'master'. Fix Bug 391426 - Incoming chat request appears in wrong category, text doesn't show I need to create an autotest for it M +4-1src/room.cpp https://commits.kde.org/ruqola/7270d73abc30b45ddfdc62a485898cc8d3360f36 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 391504] New: spectacle git 3b69ac3a7 fails to build, deletes a needed #include line from KSMainWindow.cpp
https://bugs.kde.org/show_bug.cgi?id=391504 Bug ID: 391504 Summary: spectacle git 3b69ac3a7 fails to build, deletes a needed #include line from KSMainWindow.cpp Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: 1i5t5.dun...@cox.net Target Milestone: --- spectacle git commit 3b69ac3a7 says: Test Plan: If it compiles, all is fine. Unfortunately, it doesn't, and all is /not/ fine. =:^( Long story short, the commit removes an #include line from KSMainWindow.cpp and that breaks the build. With just that include line reinserted the build completes and spectacle appears to run just fine. The details... Running gentoo/~amd64 with most of my kde packages from live-git using the live ebuilds in the gentoo/kde overlay, I had /just/ updated the general system and then all my kde-live-git packages and spectacle built fine, then ran a redo to check in more detail a couple other packages that wouldn't build and happened to catch this commit within minutes of its merge... gcc-7.3.0, qt*-5.9.4, and interestingly based on the error below, the brand new and just updated xcb-proto-1.13 (as it happens I follow the xorg announce list and it was announced on Monday, March 5, 2018, so indeed brand new, the gentoo xorg folks are on the ball =:^). However, I tried downgrading to xcb-proto-1.12 (gentoo -r2 revision), the previously installed version, and the spectacle build still failed with the same error, so it does /not/ appear to be related to the new xcb-proto version after all. Here's the first set of errors and sure enough, KSMainWindow.cpp was touched by the above commit. Looking at the commit and the error, and testing, it's actually the removal of the #include line. If I reinsert just that line, the build completes and spectacle runs just fine: [ 95%] Building CXX object src/CMakeFiles/spectacle.dir/spectacle_autogen/2Z24QZD4NU/qrc_QmlResources.cpp.o cd /tmp/portage/kde-apps/spectacle-/work/spectacle-_build/src && /usr/lib64/ccache/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB -DQT_QML_LIB -DQT_QUICK_LIB -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/tmp/portage/kde-apps/spectacle-/work/spectacle-_build/src -I/tmp/portage/kde-apps/spectacle-/work/spectacle-/src -I/tmp/portage/kde-apps/spectacle-/work/spectacle-_build/src/spectacle_autogen/include -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtConcurrent -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtDBus -isystem /usr/include/qt5/QtPrintSupport -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtQuick -isystem /usr/include/qt5/QtQml -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5 -isystem /usr/include/KF5/KDBusAddons -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KNotifications -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem /usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/qt5/QtXml -isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KDeclarative -isystem /usr/include/KF5/KPackage -isystem /usr/include/KF5/KNewStuff3 -isystem /usr/include/KF5/KNewStuff3/KNS3 -isystem /usr/include/KF5/KNewStuff3/knscore -isystem /usr/include/KF5/KNewStuff3/kns3 -isystem /usr/include/KF5/KNewStuff3/KNSCore -isystem /usr/include/KF5/Attica -isystem /usr/include/qt5/QtX11Extras -DQT_NO_DEBUG -DNDEBUG -march=native -pipe -O2 -fmerge-all-constants -fgcse-sm -fgcse-las -fgcse-after-reload -ftree-vectorize -std=c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o CMakeFiles/spectacle.dir/spectacle_autogen/2Z24QZD4NU/qrc_QmlResources.cpp.o -c /tmp/portage/kde-apps/spectacle-/work/spectacle-_build/src/spectacle_autogen/2Z24QZD4NU/qrc_QmlResources.cpp /tmp/portage/kde-apps/spectacle-/work/spectacle-99
[okular] [Bug 391505] New: Okular doesn't load cups default options for printers
https://bugs.kde.org/show_bug.cgi?id=391505 Bug ID: 391505 Summary: Okular doesn't load cups default options for printers Product: okular Version: 0.26.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: salvi.lo...@bsi.sm Target Milestone: --- Hi, Okular has the same issue when retrieving printer information like previous release (Jessie). Basically, selecting the printer does not load the default options of cups, for example the default options of my printers are set to double-sided side long (so the paper should get printed on each side). By printing from okular this setting is not loaded so the pdf doesn't get printed on the long side (it get printed only on one side of the paper). Another example is color mode, if grayscale is set in cups, okular doesnt load this setting and use color (the default of okular). Sorry for my bad english. Cheers, Loris Debian Release: 9.1 Kernel: 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 apt-cache show okular Package: okular Source: okular (4:16.08.2-1) Version: 4:16.08.2-1+b1 Installed-Size: 3925 Maintainer: Debian/Kubuntu Qt/KDE Maintainers Architecture: amd64 Provides: pdf-viewer, postscript-viewer Depends: libokularcore7 (= 4:16.08.2-1+b1), kde-runtime (>> 4:4.10), libc6 (>= 2.14), libfreetype6 (>= 2.2.1), libjpeg62-turbo (>= 1.3.1), libkdecore5 (>= 4:4.14), libkdeui5 (>= 4:4.14), libkexiv2-11 (>= 4:4.5.90), libkio5 (>= 4:4.14), libkparts4 (>= 4:4.14), libkprintutils4 (>= 4:4.14), libkpty4 (>= 4:4.14), libphonon4 (>= 4:4.6.0really4.3.80), libpoppler-qt4-4 (>= 0.38.0), libqca2 (>= 2.0.2), libqimageblitz4 (>= 1:0.0.4), libqmobipocket1 (>= 4:4.11.80), libqt4-dbus (>= 4:4.6.1), libqt4-declarative (>= 4:4.7.0~rc1), libqt4-svg (>= 4:4.5.3), libqt4-xml (>= 4:4.5.3), libqtcore4 (>= 4:4.8.0), libqtgui4 (>= 4:4.8.0), libsolid4 (>= 4:4.14), libspectre1 (>= 0.2.3), libstdc++6 (>= 5), phonon, zlib1g (>= 1:1.1.4) Recommends: cups-bsd Suggests: ghostscript, jovie, okular-extra-backends (= 4:16.08.2-1+b1), poppler-data, texlive-binaries, unrar Breaks: kdegraphics-mobipocket (<< 4:4.12) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391491] Folder view syncronous betwewn screens
https://bugs.kde.org/show_bug.cgi?id=391491 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Assignee|se...@kde.org |h...@kde.org Component|Desktop Containment |Folder -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- On loading the image I see the following error: krita.core: Missing name attribute for tag "date" I wonder whether that means that the exif info is actually malformed... The metadata parser in Krita is eleven years old by now so it's guesswork to figure out what the code is doing... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391153] creating files takes a lot of time and cpu
https://bugs.kde.org/show_bug.cgi?id=391153 --- Comment #4 from Michael Heidelbach --- I found the net processes are actually calling 'net usershare info' I inadvertently had usershares enabled in /etc/samba/smb.conf. After removing that the problem was gone. I don't know if this still is a bug. Somebody else has to decide if those net calls are intended or unavoidable. After all they are slowing down the process considerably. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391506] New: Konsole sometimes crashes on exit
https://bugs.kde.org/show_bug.cgi?id=391506 Bug ID: 391506 Summary: Konsole sometimes crashes on exit Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: pau...@mymail.root.sx Target Milestone: --- Application: kdeinit5 (17.12.2) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: Exiting konsole using kwin's close actions. Sometimes konsole has several tabs opened. - Additional Infos: Updated to KDE SC 5.12.2 from Neon repository. This is a USB bootable KDE neon workspace. This error only happens on any PC with nvidia graphics card. All konsole settings are in their default vanilla values, except for (of course) window size and location. Also, sometimes konsole uses 100% single core CPU after exit (after the window is gone). When this happens, opening another konsole window still works normally. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f328169c780 (LWP 9783))] Thread 3 (Thread 0x7f326395a700 (LWP 9785)): #0 0x7f327fd1ec5b in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f327fd2033e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f327bd5e91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f327bd5f2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f327bd5f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f327fd205cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f327fcc764a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f327fae7554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f32763aa2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f327faec6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f327dbd66ba in start_thread (arg=0x7f326395a700) at pthread_create.c:333 #11 0x7f327f77b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f326b1e5700 (LWP 9784)): #0 0x7f327f76f74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3280b03c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f3280b058d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f326df7fce9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f327faec6eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f327dbd66ba in start_thread (arg=0x7f326b1e5700) at pthread_create.c:333 #6 0x7f327f77b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f328169c780 (LWP 9783)): [KCrash Handler] #6 0x7f327f6a9428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f327f6ab02a in __GI_abort () at abort.c:89 #8 0x7f327fad6311 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f32763b6a04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f327fcf74c9 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f327e148acc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f327e150417 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f327fcc93c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f327fccbfcb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f327fd20fa3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f327bd5f197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f327bd5f3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f327bd5f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f327fd205af in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f326e0021a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f327fcc764a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f327fcd0854 in QCoreApplicat
[dolphin] [Bug 388583] Tooltip placement sometimes obscures the file
https://bugs.kde.org/show_bug.cgi?id=388583 --- Comment #6 from Michael Heidelbach --- (In reply to David de Cos from comment #5) What you're describing is actually intended behaviour. It shall allow the user to reach the links within the tooltip. If you consider this to be an usability issue, please file a separate bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391507] New: Ugly rendering of notification pictures (Nearest-neighbor)
https://bugs.kde.org/show_bug.cgi?id=391507 Bug ID: 391507 Summary: Ugly rendering of notification pictures (Nearest-neighbor) Product: plasmashell Version: 5.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: kokok...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 111240 --> https://bugs.kde.org/attachment.cgi?id=111240&action=edit notification pictures When i try to display notifications using notify-send and an icon, the same is scaled using a Nearest-neighbor algorithm, resulting in ugly rendering. Something like: notify-send -a test -i /usr/share/icons/hicolor/16x16/apps/qbittorrent.png "I'm an ugly picture" ...produces what you can see in the attached file. For reference, i'll attach the same from lxqt notification daemon so you can see the difference. Other notifications seems to display just fine; by now i'm able to reproduce only using notify-send. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 391504] spectacle git 3b69ac3a7 fails to build, deletes a needed #include line from KSMainWindow.cpp
https://bugs.kde.org/show_bug.cgi?id=391504 Henrik Fehlauer changed: What|Removed |Added CC||rk...@lab12.net --- Comment #1 from Henrik Fehlauer --- Thanks for the report, https://build.kde.org also noticed it. We'll have it fixed in a moment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390280] Media Player's UI is too big
https://bugs.kde.org/show_bug.cgi?id=390280
Roman Gilg changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/pla
||sma-workspace/d511a766779be
||67c4343d8cb6b0fcc35c53f6adf
Status|CONFIRMED |RESOLVED
--- Comment #5 from Roman Gilg ---
Git commit d511a766779be67c4343d8cb6b0fcc35c53f6adf by Roman Gilg.
Committed on 07/03/2018 at 09:13.
Pushed by romangilg into branch 'master'.
[mediacontroller applet] Reorder elements
Summary:
Improve overall look according to bug report and mockup.
{F5741858}
Reviewers: #plasma, andreask, broulik
Reviewed By: #plasma, andreask, broulik
Subscribers: ngraham, abetts, nicolasfella, broulik, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D11063
M +195 -176 applets/mediacontroller/contents/ui/ExpandedRepresentation.qml
https://commits.kde.org/plasma-workspace/d511a766779be67c4343d8cb6b0fcc35c53f6adf
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 391504] spectacle git 3b69ac3a7 fails to build, deletes a needed #include line from KSMainWindow.cpp
https://bugs.kde.org/show_bug.cgi?id=391504 Roman Inflianskas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/spe ||ctacle/941c1a517be82bed25d1 ||254ebd735c29b0d2951c Resolution|--- |FIXED --- Comment #2 from Roman Inflianskas --- Git commit 941c1a517be82bed25d1254ebd735c29b0d2951c by Roman Inflianskas. Committed on 07/03/2018 at 09:15. Pushed by romaninflianskas into branch 'master'. Fix build Summary: 3b69ac3a7aff broke the build on the CI: 06:57:49 [ 42%] Building CXX object src/CMakeFiles/spectacle.dir/Gui/KSWidget.cpp.o 06:57:50 /usr/home/jenkins/workspace/Applications spectacle kf5-qt5 FreeBSDQt5.9/src/Gui/KSMainWindow.cpp:91:9: error: unknown type name 'xcb_intern_atom_cookie_t' Reviewers: rkflx, #spectacle Reviewed By: rkflx, #spectacle Subscribers: rkflx Differential Revision: https://phabricator.kde.org/D0 M +1-0src/Gui/KSMainWindow.cpp https://commits.kde.org/spectacle/941c1a517be82bed25d1254ebd735c29b0d2951c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391468] Plasma shell crashea al presionar botón derecho en menu
https://bugs.kde.org/show_bug.cgi?id=391468 Eike Hein changed: What|Removed |Added CC||aleix...@kde.org --- Comment #1 from Eike Hein --- Aleix, this has AppStream in the bt, can you take a look? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 Eike Hein changed: What|Removed |Added CC||h...@kde.org --- Comment #4 from Eike Hein --- To me there's a lot of conjecture in this ticket I don't see metrics for. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391507] Ugly rendering of notification pictures (Nearest-neighbor)
https://bugs.kde.org/show_bug.cgi?id=391507 --- Comment #1 from Kai Uwe Broulik --- Can't reproduce here. What plasma-frameworks version is this? Might have already been fixed by [1]. [1] https://cgit.kde.org/plasma-framework.git/commit/?id=639e8684e3b39b43238e1812c1d7f430f86366e3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391507] Ugly rendering of notification pictures (Nearest-neighbor)
https://bugs.kde.org/show_bug.cgi?id=391507 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- or rather... https://cgit.kde.org/plasma-framework.git/commit/?id=bf4facd8c1b90f2ca5f0330bbe24f6930a822fb2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 Thomas Pfeiffer changed: What|Removed |Added CC||thomas.pfeif...@kde.org --- Comment #5 from Thomas Pfeiffer --- Having a shortcut to changing the background on the desktop's context menu (and in the hamburger menu) is definitely needed, but there is no argument from a user perspective for not having it in System Settings. From a user perspective it does belong there, together with all other settings. I have brought this topic up in the past as well, but was told "Sorry, can't do it, because System Settings doesn't know about containments.", but that's a completely different argument. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391491] Folder view syncronous betwewn screens
https://bugs.kde.org/show_bug.cgi?id=391491 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Eike Hein --- 5.13 will have an option in the desktop settings. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #5 from DDR --- OK, so I have just discovered the magic of ls -la /proc/1234/fd, where 1234 is the pid of baloo_file_extractor. 😎 baloo_file_extractor was busy on a 1.5GiB text file, production-aria-tables.sql, and then got stuck on its backup. I added these files to the ignore list, in File Search — System Settings, and the indexer has gotten on with life and is indexing the last few files it needs to. Unfortunately, as the file is a database dump of mlpforums.com, I cannot share it for reproduction due to confidentiality issues. Perhaps a partial dump of the kde bugs database would suffice for that purpose. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391508] Kritarunner -s expects known module, not filepath
https://bugs.kde.org/show_bug.cgi?id=391508 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Assignee|krita-bugs-n...@kde.org |b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391508] New: Kritarunner -s expects known module, not filepath
https://bugs.kde.org/show_bug.cgi?id=391508 Bug ID: 391508 Summary: Kritarunner -s expects known module, not filepath Product: krita Version: 4.0 pre-alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: fred...@averpil.com Target Milestone: --- kritarunner.exe --help says: -s, --script
[konsole] [Bug 391445] Bold fonts set in profile settings are not applied after restarting konsole
https://bugs.kde.org/show_bug.cgi?id=391445 Ahmad Samir changed: What|Removed |Added Summary|Font changes doesn't saves |Bold fonts set in profile |in Konsole after rebooting |settings are not applied ||after restarting konsole --- Comment #6 from Ahmad Samir --- Please check the 'font=' line, under [General] section, in ~/.config/kdeglobals; if it has ',Regular' or ',Book' at the end, does removing that bit fix the issue of this report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365332] Control panel sometimes ignores visibility setting "always visible"
https://bugs.kde.org/show_bug.cgi?id=365332 y...@riseup.net changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from y...@riseup.net --- No, not happening anymore. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391497] Digikam crashes when manually stopping database sync
https://bugs.kde.org/show_bug.cgi?id=391497 --- Comment #3 from IWBR --- Ok, I can confirm that with the latest windows bundle (digiKam-5.9.0-20180304T171700-Win64.exe) this does not happen anymore. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 --- Comment #3 from Boudewijn Rempt --- Hm, that's not on loading, but on showing the metadata editor. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor
https://bugs.kde.org/show_bug.cgi?id=380456
--- Comment #6 from DDR ---
> Please report memory usage when indexing is done. I'm really curious to see
> that.
About 1.1GiB, ~5% of the available system memory. Very reasonable.
> Did you kill it? Probably not. I've encountered this many times.
No, not as of the report. I did shortly after - it was that, or it killed me by
swapping anything useful to disk.
> Please clarify 'unresponsive': Did you have to Ctrl-C?
Yes. I think balooctl it was waiting for baloo_file_extractor to provide some
information, but the extractor never would. I think it was busy extracting. I
don't have a way to ctrl-c file extractor, but I think when I send the
equivalent signal it shuts down just fine. ("End Process" in system monitor.)
> With an index of that size searching might be a little slow. And your even
> half-way done :)
> Not sure, but I have the feeling baloo wasn't designed for this and you're
> overburdening it.
Searching is still lightning fast. It seems it was designed very well in that
regard.
I was definitely overburdening it. I feel it really should have known better
than to try to index a tremendous plain-text file, though. It is enthusiastic,
it bit off significantly more than it could chew. The actual search index for
the forum the database dump was from takes over a week to rebuild on the
server, I imagine the more generalised search tool would be absolutely doomed
in that endeavour. That, and a week of solid uptime is quite rare for me.
> I'm just trying to imagine what will happen when you enter 'const' in
> KRunner/Milou.
Would Dolphin's ctrl-f suffice? It's up to 1158 folders and 115308 files.
Somewhat amazingly, although the search results took a few minutes to populate,
Dolphin itself is still perfectly responsive and I can scroll through the files
just fine. Typing to select a file works both perfectly and instantly. Memory
use remaned unremarkably low throughout the whole process, and didn't really
change when I exited Dolphin.
All 374579 files have now finished indexing. The current size of the index is
11.08 GiB.
--
You are receiving this mail because:
You are watching all bug changes.
[releaseme] [Bug 391509] New: Warnings in tagme
https://bugs.kde.org/show_bug.cgi?id=391509 Bug ID: 391509 Summary: Warnings in tagme Product: releaseme Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: stan...@kde.org Target Milestone: --- Hi, any solution for that? releaseme from git master: Warning: requiring old file project.rb, should require releaseme/project.rb instead @ /home/*/releaseme/tagme.rb:50:in `require_relative' Warning: requiring old file source.rb, should require releaseme/source.rb instead @ /home/*/releaseme/tagme.rb:51:in `require_relative' -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391497] Digikam crashes when manually stopping database sync
https://bugs.kde.org/show_bug.cgi?id=391497 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.9.0 CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391510] New: KMail crashes at printing emails
https://bugs.kde.org/show_bug.cgi?id=391510 Bug ID: 391510 Summary: KMail crashes at printing emails Product: kmail2 Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@clearingstelle-eeg-kwkg.de Target Milestone: --- Application: kmail (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.114-42-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Trying to print an email. When pressing ctrl+p, the application crashes. - Unusual behavior I noticed: on the command line I get a lot of (> 1000) error messages: [warn] epoll_wait: Ungültiger Dateideskriptor (the latter probably being "invalid file decriptor" or similar) The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f07533c3940 (LWP 8363))] Thread 27 (Thread 0x7f061946d700 (LWP 8435)): #0 0x7f07462860ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f073d6c95d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f073d6c9d9d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f073d6ca5c0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f073d6c731e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f0746281724 in start_thread () from /lib64/libpthread.so.0 #6 0x7f075050de8d in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f0619c6e700 (LWP 8434)): #0 0x7f07462860ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f073d6c95d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f073d6c9d9d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f073d6ca5c0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f073d6c731e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f0746281724 in start_thread () from /lib64/libpthread.so.0 #6 0x7f075050de8d in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f069b37e700 (LWP 8433)): #0 0x7f07462860ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f0738ee593b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f0738ee5969 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f0746281724 in start_thread () from /lib64/libpthread.so.0 #4 0x7f075050de8d in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7f06a90d0700 (LWP 8420)): #0 0x7f0745aa8899 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f0745a66969 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f0745a67230 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f0745a6742c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f0750e111ab in QEventDispatcherGlib::processEvents (this=0x7f06a0001940, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f0750dbebfb in QEventLoop::exec (this=this@entry=0x7f06a90cfc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x7f0750bf9f5a in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f0750bfea29 in QThreadPrivate::start (arg=0x5453700) at thread/qthread_unix.cpp:365 #8 0x7f0746281724 in start_thread () from /lib64/libpthread.so.0 #9 0x7f075050de8d in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7f06d9ffb700 (LWP 8396)): #0 0x7f07462860ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f073d525160 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f073d512c0b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f073d512e85 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f073d50f777 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f073ecb9a4a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f073ecb9d61 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f073ecb9e52 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f073d6b3062 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f073d69eb05 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f073d6ca940 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f073d6c731e in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f0746281724 in start_thread () from /lib64/libpthread.so.0 #13 0x7f075050de8d in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f06da7fc700 (LWP 8395)): #0 0x7f07462860ff in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f073d6c95d9 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f073d6c9d9d in ?? () from /usr/lib64/libQt5WebEngineCor
[krita] [Bug 391511] New: Canvas is not updated when Node::setVisible() is called from python script
https://bugs.kde.org/show_bug.cgi?id=391511
Bug ID: 391511
Summary: Canvas is not updated when Node::setVisible() is
called from python script
Product: krita
Version: 4.0 pre-alpha
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: aurelien.daca...@gmail.com
Target Milestone: ---
Created attachment 111241
--> https://bugs.kde.org/attachment.cgi?id=111241&action=edit
This image shows the inconsitency between the canvas & the layers docker
When layers are hidden from the "Scripter" extension the canvas is not updated.
However, the "Layer" docker is updated.
Note: This happens on krita-nightly-x64-v4.0.0.51-594-gba8550543c
Here is a simple sample code to reproduce this issue:
---
from krita import *
doc = Krita.instance().activeDocument()
if doc is not None:
for node in doc.topLevelNodes():
node.setVisible(False)
else:
print("No active document.")
---
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 391512] New: Crash while starting an application
https://bugs.kde.org/show_bug.cgi?id=391512 Bug ID: 391512 Summary: Crash while starting an application Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marcelo.jime...@gmail.com Target Milestone: --- Application: kdeinit5 (5.0.97) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.15.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I had konqueror open on a couple of windows and clicked on an icon on the desktop folder. The program did start, but kde crashed. -- Backtrace: Application: Konqueror (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7371485780 (LWP 31878))] Thread 6 (Thread 0x7f72f5dff700 (LWP 32113)): #0 0x7f736f531bf4 in read () at /lib64/libc.so.6 #1 0x7f736bcfa420 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f736bcb5bf7 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f736bcb60b0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f736bcb621c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f736faeb7eb in timerSourceCheckHelper (src=0x1d) at kernel/qeventdispatcher_glib.cpp:143 #6 0x7f736faeb7eb in idleTimerSourceCheck(GSource*) (source=) at kernel/qeventdispatcher_glib.cpp:223 #7 0x in () Thread 5 (Thread 0x7f73380b7700 (LWP 32042)): #0 0x7f736dbc556c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f736ece33bc in std::condition_variable::wait(std::unique_lock&) () at /usr/lib64/libstdc++.so.6 #2 0x7f733dfec0f7 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x55e988b76830 in () #4 0x in () Thread 4 (Thread 0x7f7344d79700 (LWP 32030)): #0 0x7f736bcfb759 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f736bcb5673 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f736bcb603b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f736bcb621c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f736faeb7eb in timerSourceCheckHelper (src=0x7f734bf0) at kernel/qeventdispatcher_glib.cpp:143 #5 0x7f736faeb7eb in idleTimerSourceCheck(GSource*) (source=) at kernel/qeventdispatcher_glib.cpp:223 #6 0x in () Thread 3 (Thread 0x7f73514de700 (LWP 31954)): #0 0x7f736bcfb759 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f736bcb6208 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #2 0x7f736faeb7eb in timerSourceCheckHelper (src=0x7f734c000bf0) at kernel/qeventdispatcher_glib.cpp:143 #3 0x7f736faeb7eb in idleTimerSourceCheck(GSource*) (source=) at kernel/qeventdispatcher_glib.cpp:223 #4 0x in () Thread 2 (Thread 0x7f735a320700 (LWP 31880)): #0 0x7f736f536179 in poll () at /lib64/libc.so.6 #1 0x7f7370904387 in () at /usr/lib64/libxcb.so.1 #2 0x7f737090617a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f735ccbf0a9 in QXcbEventReader::run() (this=0x55e987b8b5c0) at qxcbconnection.cpp:1370 #4 0x7f736f8be930 in QThreadPrivate::setPriority(QThread::Priority) (this=0x55e987b8b5c0, threadPriority=) at thread/qthread_unix.cpp:790 #5 0x8387c31084facedb in () #6 0x7ffc5717b3ee in () #7 0x7ffc5717b3ef in () #8 0x55e987b8b5c0 in () #9 0x7ffc5717b4c0 in () #10 0x7d617773797acedb in () #11 0x7d6118676e3ecedb in () #12 0x in () Thread 1 (Thread 0x7f7371485780 (LWP 31878)): [KCrash Handler] #6 0x7f736f1e1d22 in QConcatenable >::size(QStringBuilder const&) (p=...) at /usr/include/qt5/QtCore/qstringbuilder.h:358 #7 0x7f736f1e1d22 in QConcatenable, QString> >::size(QStringBuilder, QString> const&) (p=...) at /usr/include/qt5/QtCore/qstringbuilder.h:358 #8 0x7f736f1e1d22 in QStringBuilder, QString>::convertTo() const (this=) at /usr/include/qt5/QtCore/qstringbuilder.h:111 #9 0x7f736f1e1d22 in QStringBuilder, QString>::operator QString() const (this=) at /usr/include/qt5/QtCore/qstringbuilder.h:131 #10 0x7f736f1e1d22 in KDirWatchPrivate::inotifyEventReceived() (this=0x55e9880b3510) at /usr/src/debug/kcoreaddons-5.43.0-1.1.x86_64/src/lib/io/kdirwatch.cpp:322 #11 0x7f736fac202a in QMutexLocker::relock() (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:228 #12 0x7f736fac202a in queued_activate (locker=..., argv=0x7ffc5717b5f0, c=0x55e9880b2c20, signal=3, sender=0x55e987c35ef0) at kernel/qobject.cpp:3602 #13 0x7f736fac202a in QMetaObject::activate(QObject*, int, int, void**) (sender=0x55e987c35ef0, signalOffset=, local_signal_index=, argv=) at ker
[Discover] [Bug 391482] Support permissions connecting/disconnecting snap interfaces
https://bugs.kde.org/show_bug.cgi?id=391482 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388583] Tooltip placement sometimes obscures the file
https://bugs.kde.org/show_bug.cgi?id=388583 --- Comment #7 from David de Cos --- Oh, I hadn't realized that's the intended behavior. I guess it makes sense to allow the mouse pointer to interact with the tooltip contents, but only if it doesn't block the view of other files, which is what Michael reported originally in this bug. Otherwise, it just gets in the way when you want to hover over several files quickly. Therefore, if that gets fixed, my problem disappears. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391513] New: [filter] [color-to-alpha] Color picker on canvas doesn't work
https://bugs.kde.org/show_bug.cgi?id=391513 Bug ID: 391513 Summary: [filter] [color-to-alpha] Color picker on canvas doesn't work Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Target Milestone: --- Hi, while performing a Filter>Color>Color-to-Alpha on a document, it is usually possible to go outside the dialog, fly over the canvas with the mouse (the cursor is changing for a color-picker cursor) and pick a color from the canvas to define the color to transform into alpha. In Krita 4.0 this feature doesn't work: the icon appears, but clicking on the canvas doesn't return the selected color. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 --- Comment #6 from David Edmundson --- >but there is no argument from a user perspective for not having it in System >Settings. I haven't seen a valid argument for having it either. Why does this belong in systemsettings, but whether the batter applet on your second panel shows a percentage or an icon does not? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script
https://bugs.kde.org/show_bug.cgi?id=391511 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Platform|Other |MS Windows --- Comment #1 from Boudewijn Rempt --- You should call doc.refreshProjection() after adding a node to update the view. We made that a separate step because updating the projection after adding a node can take a lot of time. So, I'm not sure whether this really is a bug that should be fixed... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391507] Ugly rendering of notification pictures (Nearest-neighbor)
https://bugs.kde.org/show_bug.cgi?id=391507 --- Comment #3 from Antonio Orefice --- plasma-framework is 5.43.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391513] [filter] [color-to-alpha] Color picker on canvas doesn't work
https://bugs.kde.org/show_bug.cgi?id=391513 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Keywords||regression, release_blocker Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||b...@valdyas.org Ever confirmed|0 |1 --- Comment #1 from Boudewijn Rempt --- That's probably caused by: commit 042dbe5190fa613ae53a24236ad3eb19b2b03b16 Author: Dmitry Kazakov Date: Mon Jan 29 16:35:23 2018 +0300 Block all the non-view input user actions while filter dialog is active Now all the input actions are divided into two groups: view-transform and modifying. And the canvas can block any of these action by setting a special flag, that is checked by the shortcuts matcher. When the filter dialog opens, it just blocks all the modifying actions, allowing the view ones at the same time :) BUG:352747 So assigning to Dmitry. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391502] Dolphin Crashed when emptying the trash
https://bugs.kde.org/show_bug.cgi?id=391502 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@privat.broulik.de Resolution|--- |DUPLICATE --- Comment #1 from Kai Uwe Broulik --- Same backtrace as Bug 390491 *** This bug has been marked as a duplicate of bug 390491 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed consequently when the directory/file browesing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 Kai Uwe Broulik changed: What|Removed |Added CC||marcelo.jime...@gmail.com --- Comment #3 from Kai Uwe Broulik --- *** Bug 391512 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed consequently when the directory/file browesing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 Kai Uwe Broulik changed: What|Removed |Added CC||barnabas.jovanovics@gmail.c ||om --- Comment #2 from Kai Uwe Broulik --- *** Bug 391502 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391512] Crash while starting an application
https://bugs.kde.org/show_bug.cgi?id=391512 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@privat.broulik.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kai Uwe Broulik --- Same backtrace as Bug 390491 *** This bug has been marked as a duplicate of bug 390491 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391301] Browsing up a directory
https://bugs.kde.org/show_bug.cgi?id=391301 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||k...@privat.broulik.de Resolution|--- |DUPLICATE --- Comment #3 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 390491 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed consequently when the directory/file browesing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 Kai Uwe Broulik changed: What|Removed |Added CC||igiwat...@gmail.com --- Comment #4 from Kai Uwe Broulik --- *** Bug 391301 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed sequentially when the directory/file browsing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 林博仁 changed: What|Removed |Added Summary|Dolphin and Kate crashed|Dolphin and Kate crashed |consequently when the |sequentially when the |directory/file browesing is |directory/file browsing is |deleted (by git-clean) |deleted (by git-clean) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed sequentially when the directory/file browsing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 Kai Uwe Broulik changed: What|Removed |Added CC||m...@milianw.de --- Comment #5 from Kai Uwe Broulik --- @Milian: Since you touched this last, any idea what's going on here? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390491] Dolphin and Kate crashed sequentially when the directory/file browsing is deleted (by git-clean)
https://bugs.kde.org/show_bug.cgi?id=390491 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Kai Uwe Broulik --- Ah, nevermind this is fixed as Bug 390214 sorry for the noise :) *** This bug has been marked as a duplicate of bug 390214 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 390214] Dolphin random crash
https://bugs.kde.org/show_bug.cgi?id=390214 Kai Uwe Broulik changed: What|Removed |Added CC||buo.ren@gmail.com --- Comment #11 from Kai Uwe Broulik --- *** Bug 390491 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 382538] Muon has generic Wayland icon
https://bugs.kde.org/show_bug.cgi?id=382538 Carlo Vanini changed: What|Removed |Added Latest Commit||https://commits.kde.org/muo ||n/ee62b9731878420a35b71255e ||ff266b9fa44794c Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Carlo Vanini --- Git commit ee62b9731878420a35b71255eff266b9fa44794c by Carlo Vanini. Committed on 07/03/2018 at 11:14. Pushed by vanini into branch 'master'. Fix name of desktop file Summary: This also fixes the window icon in Wayland. Reviewers: sitter Differential Revision: https://phabricator.kde.org/D10886 M +1-1src/CMakeLists.txt R +0-0src/org.kde.muon.desktop [from: src/muon.desktop - 100% similarity] https://commits.kde.org/muon/ee62b9731878420a35b71255eff266b9fa44794c -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391470] Building UnrealEngine 4.18 with KDevelop
https://bugs.kde.org/show_bug.cgi?id=391470
--- Comment #5 from Martin Linklater ---
Hi. Here is the console output:
link@blade:/usr/bin$ ./kdevelop
kdevelop.documentation.qthelp: qmake query returned error: ""
"CMake Project Manager" ("CMakeLists.txt")
"Custom Build System" ()
"Custom Makefile Project Manager" ("GNUmakefile", "Makefile", "makefile",
"GNUmakefile.*", "Makefile.*", "makefile.*")
"Generic Project Manager" ()
"QMake Project Manager" ("*.pro")
"CMake Project Manager" ("CMakeLists.txt")
"Custom Build System" ()
"Custom Makefile Project Manager" ("GNUmakefile", "Makefile", "makefile",
"GNUmakefile.*", "Makefile.*", "makefile.*")
"Generic Project Manager" ()
"QMake Project Manager" ("*.pro")
kdevplatform.shell: Not loading plugin named "KDevNinjaBuilder" because it has
been disabled!
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdevelop path = /usr/bin pid = 9319
KCrash: Arguments: /usr/bin/kdevelop
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 34 and type 'Exception', disabling...
QSocketNotifier: Invalid socket 15 and type 'Read', disabling...
QSocketNotifier: Invalid socket 45 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
Segmentation fault (core dumped)
link@blade:/usr/bin$
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script
https://bugs.kde.org/show_bug.cgi?id=391511 --- Comment #2 from Aurélien Da Campo --- Thanks a lot it makes a lot of sense. So yes indeed that's not a bug in my sense. Just me being lazy to figure it out or simply a lack of documentation regarding this specific thing. I actually looked for Document/Node::updateXXX, Document/Node::invalidate() or Document/Node::validate() but didn't find the Document::refreshXXX() one ;) It works fine. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390427] Unknown Open Collaboration Service API error when clicking on addons in Discover
https://bugs.kde.org/show_bug.cgi?id=390427 kts changed: What|Removed |Added CC||jeckfer...@gmail.com --- Comment #6 from kts --- Created attachment 111242 --> https://bugs.kde.org/attachment.cgi?id=111242&action=edit notification error Not sure whether it's related but I also have many notification errors involving knsrc so I'll just leave the attachment here for verification. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391511] Canvas is not updated when Node::setVisible() is called from python script
https://bugs.kde.org/show_bug.cgi?id=391511 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Boudewijn Rempt --- Okay, then we can close this? I'll try to figure out how to improve the dox; right now, the example for this is with cerateFillLayer -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 390427] Unknown Open Collaboration Service API error when clicking on addons in Discover
https://bugs.kde.org/show_bug.cgi?id=390427 --- Comment #7 from kts --- Created attachment 111243 --> https://bugs.kde.org/attachment.cgi?id=111243&action=edit notification error 2 Another one. I have many notification errors before 5.12.3 concerning .knsc. Now with 5.12.3, I have still a few of those left which I provided in these two attachments. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391370] bundled qtsingleapplication
https://bugs.kde.org/show_bug.cgi?id=391370 --- Comment #17 from private2@yandex.com --- That's a list of the functions colled from the embeded api: On start: QtSingleApplication setAppId sysInit QtLockedFile QtLocalPeer open isRunning isClient isLocked lock On exit: removeLockFile removeLockedFile ~QtLockedFile Unfortunately, i failed to get that from the external library. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 327102] ctrl-d in konsole killed ALL related processes
https://bugs.kde.org/show_bug.cgi?id=327102 Ahmad Samir changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||a.samir...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ahmad Samir --- KDE4/konsole is no longer maintained. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 326643] Crash in terminal running aptitude
https://bugs.kde.org/show_bug.cgi?id=326643 Ahmad Samir changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- KDE4/konsole is no longer maintained. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 336129] Search not updated when switching tabs
https://bugs.kde.org/show_bug.cgi?id=336129 Ahmad Samir changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||a.samir...@gmail.com Version|2.13|master Ever confirmed|0 |1 Platform|Ubuntu Packages |unspecified -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 391514] New: Enabling second screen moves all windows to that screen
https://bugs.kde.org/show_bug.cgi?id=391514 Bug ID: 391514 Summary: Enabling second screen moves all windows to that screen Product: KScreen Version: 5.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: d...@aninstanceofme.com Target Milestone: --- When enabling a second screen (screen 2) from System Settings > Display and Monitor, all open windows are instantly moved to screen 2, despite their Window-Specific settings being set to "Force screen 1", and despite screen 1 being designated as "Primary Screen". -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 391514] Enabling second screen moves all windows to that screen
https://bugs.kde.org/show_bug.cgi?id=391514 d...@aninstanceofme.com changed: What|Removed |Added CC||d...@aninstanceofme.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385380] Cannot bind non letter/digit/. keys in profile keybinding combinations
https://bugs.kde.org/show_bug.cgi?id=385380 Ahmad Samir changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||a.samir...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Ahmad Samir --- FWIW, you can use '++Ctrl', note the extra +. For the rest of it: https://phabricator.kde.org/D10939 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 391515] New: [KRDC ]Graphics not drawn correctly when logging into WS2003 machines
https://bugs.kde.org/show_bug.cgi?id=391515 Bug ID: 391515 Summary: [KRDC ]Graphics not drawn correctly when logging into WS2003 machines Product: krdc Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: alln_medei...@hotmail.com Target Milestone: --- Created attachment 111244 --> https://bugs.kde.org/attachment.cgi?id=111244&action=edit Windows Server 2003 screen not drawn correctly by KRDC I'm using KRDC to login into Windows Server machines. From time to time I have to login into Windows Server 2003 machines. I don't remember the last time that I tried RDP connection into WS2003, but usually worked well. The graphics aren't drawn correctly when I try RDP into any of WS2003 connections that I have in KRDC. "xfreerdp" and "rdesktop" from command line to the same machines works well. [attachment is from "Screenshot" KRDC button] KRDC 17.12.2 + KDE Frameworks 5.43.0 Qt 5.10.1 (built against 5.10.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 391515] [KRDC 17.12.2] Graphics not drawn correctly when logging into WS2003 machines
https://bugs.kde.org/show_bug.cgi?id=391515 Allan changed: What|Removed |Added Summary|[KRDC ]Graphics not drawn |[KRDC 17.12.2] Graphics not |correctly when logging into |drawn correctly when |WS2003 machines |logging into WS2003 ||machines -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391516] New: ruqola shows "Login failed" while logging in successfully
https://bugs.kde.org/show_bug.cgi?id=391516 Bug ID: 391516 Summary: ruqola shows "Login failed" while logging in successfully Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: fa...@kde.org Target Milestone: --- For 3 seconds or so, one can see "Login failed" in red, although login is actually working (and the screen then switches away from the login page). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 --- Comment #4 from Danas --- I am not good at technical details, but it appears that it just doesn;t want to accept EXIF from PNG. I use Darktable for processing RAW images, so everything I through to Krita is directly from Darktable with no modifications. If have JPG or TIFF it is fine, but if it is PNG then it doesn;t work, exif seems to not exist. But in Gwenview and GIMP 2.9 everything is fine with Exif and it shows it as usually. I wonder if it would be possible to force Krita to always keep Exif data from first layer? One thing I noticed that many times Krita doesn;t load exif once I close and load the .kra file even with JPG and Tiffs. It would be cool if it was possible to force Krita to always keep Exif data from the first loaded layer and have it as an option for krita document so that when you export to JPG or any other format the one wouldn't need to merge all layers and give priority to the first layer metadata. The document could always use the metadata of the first layer. Just a thought. Nowadays I use Krita a lot for photo editing instead of painting which is not primary function of Krita. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 382597] Improve rendering of nicks in messages
https://bugs.kde.org/show_bug.cgi?id=382597 David Faure changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Faure --- Seems to work now. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 336129] Search not updated when switching tabs
https://bugs.kde.org/show_bug.cgi?id=336129 Ahmad Samir changed: What|Removed |Added Component|tabbar |general -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 391515] [KRDC 17.12.2] Graphics not drawn correctly when logging into WS2003 machines
https://bugs.kde.org/show_bug.cgi?id=391515 Allan changed: What|Removed |Added CC||alln_medei...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391517] New: Plain text link generation triggers scam detection
https://bugs.kde.org/show_bug.cgi?id=391517 Bug ID: 391517 Summary: Plain text link generation triggers scam detection Product: kmail2 Version: 5.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- When you receive a plain text email with a http URL in it, it is turned into a clickable link. The href of that link is lowercase so it will trigger the scam detection because of URL title vs href mismatch. Send a plain text email with content "test http://gOogle.com"; (note the uppercase O), opened it and got "This message may be scam" with details of " This email contains a link which reads as 'http://gOogle.com' in the text, but actually points to 'http://google.com/'. This is often the case in scam emails to mislead the recipient" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391063] Memory Leak in Plasmashell
https://bugs.kde.org/show_bug.cgi?id=391063 D1mon changed: What|Removed |Added CC||bi3...@rambler.ru --- Comment #6 from D1mon --- I noticed that the memory is increasing when switching between the screens (KWin -> "Switch to Desktop 1"), the memory is increasing ~ 0.5mb. Accordingly, if you switch 200 times, the size will increase by 100mb. Plasma: plasma-workspace 5.11.5-2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 391518] New: Cursor width in Kate gets narrower every 16 characters
https://bugs.kde.org/show_bug.cgi?id=391518 Bug ID: 391518 Summary: Cursor width in Kate gets narrower every 16 characters Product: kate Version: 17.12.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.de...@ehu.eus Target Milestone: --- Created attachment 111245 --> https://bugs.kde.org/attachment.cgi?id=111245&action=edit Two screenshots put together, where both widths can be seen The width of the cursor in Kate depends on what column it is in. Most of the times its quite thick, but at some places of the document it's narrower. The column numbers where it is narrow are: 1, 17, 33, 49, 65, 81, 97... (i.e. 16*n+1) It's not a severe bug, but I find it slightly annoying, and the fact that those column numbers follow a mathematical pattern makes it interesting! -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391519] New: nicks should be clickable
https://bugs.kde.org/show_bug.cgi?id=391519 Bug ID: 391519 Summary: nicks should be clickable Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: fa...@kde.org Target Milestone: --- If I say someone's nick like @laurent, I can click on that to open a private chat. But I can't do that if laurent is speaking himself, @laurent appears in the message, but I can't click on that. This appears to be the only way to start a private conversation with someone, right? -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 Simone Lazzaris changed: What|Removed |Added Ever confirmed|0 |1 CC||sim...@omni.it Status|UNCONFIRMED |CONFIRMED --- Comment #6 from Simone Lazzaris --- I'm also having this issue. Archlinux, kde 17.12.2, Qt 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391520] New: handling of newlines
https://bugs.kde.org/show_bug.cgi?id=391520 Bug ID: 391520 Summary: handling of newlines Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: fa...@kde.org Target Milestone: --- Someone wrote to me in a private message: "These are the options: - a - b - c - d" In ruqola it appeared as "These are the options: - a - b - c - d" (which was unreadable, with real text) ;) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391521] New: "Tool-tip" box difficult to read due to default color scheme
https://bugs.kde.org/show_bug.cgi?id=391521 Bug ID: 391521 Summary: "Tool-tip" box difficult to read due to default color scheme Product: digikam Version: 5.9.0 Platform: MS Windows URL: https://i.imgur.com/jaRH9uV.jpg OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Thumbs-IconView Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- I enabled the "tool-tip" box in the configuration options, but when I hover over a picture, the box appears in a gray over yellow color scheme, making it very difficult to read. I tried to customize the font, but that did not alter the colors. See example at https://i.imgur.com/jaRH9uV.jpg I am using the latest available windows version(digiKam-5.9.0-20180304T171700-Win64.exe) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391521] "Tool-tip" box difficult to read due to default color scheme
https://bugs.kde.org/show_bug.cgi?id=391521 IWBR changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #13 from Michail Vourlakos --- > Interesting... Actually, the OP of bug #368385 is the dev of Latte-Dock (bug > opening in 2016). one of the reasons that I created Now Dock(ancestor of Latte) back then was that missing feature from plasma. Just to add, Now Dock started at August of 2016 and Latte is just 1.4 years old (it started in December of 2016) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391517] Plain text link generation triggers scam detection
https://bugs.kde.org/show_bug.cgi?id=391517 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- 5.7.2 ? are you sure. But in master it was fixed this morning. Regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #14 from fl...@mailoo.org --- So, the question still stand: shall we consider the availability of Latte-Dock as a "fix" and close the bug? OP seems to be inclined to close it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391492] falta cursor de mouse al escribir texto Clip de título en kdenlive 17.12 y más otros detalles...
https://bugs.kde.org/show_bug.cgi?id=391492 Christoph Feck changed: What|Removed |Added Component|general |User Interface Platform|Other |MS Windows Version|unspecified |17.12.0 OS|other |MS Windows Assignee|unassigned-b...@kde.org |j...@kdenlive.org Product|kde |kdenlive -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 391476] 'Version:" pull down list for 'Product: kate' needs to be updated
https://bugs.kde.org/show_bug.cgi?id=391476 --- Comment #3 from Howard Johnson --- @Christophe, Ok fair enough, but then what would be the correct way to report a bug that exists in this version? Is it best then to just manually type it into my comment? Or do I also select the "git" option? Or what? Just not really sure what your standard way of operating is. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391521] "Tool-tip" box difficult to read due to default color scheme
https://bugs.kde.org/show_bug.cgi?id=391521 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Thumbs-IconView |Usability-Themes -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391506] Konsole sometimes crashes on exit
https://bugs.kde.org/show_bug.cgi?id=391506 Christoph Feck changed: What|Removed |Added Component|general |general Version|unspecified |17.12.2 Assignee|unassigned-b...@kde.org |konsole-de...@kde.org Product|kde |konsole -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 391493] falta botones de reproducción en panel clip de texto en kdenlive 17.12 español
https://bugs.kde.org/show_bug.cgi?id=391493 Christoph Feck changed: What|Removed |Added Version|unspecified |17.12.0 Platform|Other |MS Windows Component|general |User Interface Product|kde |kdenlive Assignee|unassigned-b...@kde.org |j...@kdenlive.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391503] konsole crash
https://bugs.kde.org/show_bug.cgi?id=391503 Christoph Feck changed: What|Removed |Added Product|kde |konsole Assignee|unassigned-b...@kde.org |konsole-de...@kde.org Version|unspecified |17.12.2 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 391476] 'Version:" pull down list for 'Product: kate' needs to be updated
https://bugs.kde.org/show_bug.cgi?id=391476 --- Comment #4 from Christophe Giboudeaux --- select GIT manually -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 391522] New: Amarok keeps crashing at each start up.
https://bugs.kde.org/show_bug.cgi?id=391522 Bug ID: 391522 Summary: Amarok keeps crashing at each start up. Product: amarok Version: 2.8.0 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/USB mass storage and MSC Assignee: amarok-bugs-d...@kde.org Reporter: hanne...@gmx.com CC: bart.cerne...@kde.org Target Milestone: 2.9 Amarok keeps crashing at each start up: hj@aspire ~ $ gksudo amarok QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. amarok(5076)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::insertAction: Attempt to insert null action amarok(5076)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QSystemTrayIcon::setVisible: No Icon set "sni-qt/5076" WARN 13:31:04.146 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Could not parse stylesheet of widget 0xb9e54a8 KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/root/.kde/socket-aspire/kdeinit4__0 unnamed app(5075): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" " pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor QSocketNotifier: Invalid socket 55 and type 'Read', disabling... Unable to start Dr. Konqi Not forwarding the crash to Apport. hj@aspire ~ $ amarok QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. amarok(5127)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::insertAction: Attempt to insert null action amarok(5127)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (0,-1) are not possible QSystemTrayIcon::setVisible: No Icon set "sni-qt/5127" WARN 13:31:14.699 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Could not parse stylesheet of widget 0xc2d1730 QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) are not possible unnamed app(5126): Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message recipient disconnected from message bus without replying" " KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/hj/.kde/socket-aspire/kdeinit4__0 hj@aspire ~ $ pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor pa_write() failed while trying to wake up the mainloop: Ongeldige bestandsdescriptor Invalid write to eventfd: Ongeldige bestandsdescriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. Unable to start Dr. Konqi Not forwarding the crash to Apport. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 385380] Cannot bind non letter/digit/. keys in profile keybinding combinations
https://bugs.kde.org/show_bug.cgi?id=385380
--- Comment #2 from Kurt Hindenburg ---
The patch in phabricator changes it to
static const QRegularExpression
key(QStringLiteral("key\\s+(\\S+)\\s*:\\s*(\"(.*)\"|\\w+)"),
I'm not actually sure why the original one is more complex. I'll try to test
it.
--
You are receiving this mail because:
You are watching all bug changes.
[trojita] [Bug 321374] Multiple accounts
https://bugs.kde.org/show_bug.cgi?id=321374 Pekka Helenius changed: What|Removed |Added CC||fince...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 389792] Kleopatra (gpg4win 3.0.3) crashes during *.sig verification
https://bugs.kde.org/show_bug.cgi?id=389792 --- Comment #2 from Andre Heinecke --- A beta with the fix is available now. https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 391222] does not save multiple decrypted files
https://bugs.kde.org/show_bug.cgi?id=391222 --- Comment #3 from Andre Heinecke --- A beta of the next version, which contains the fix is available now https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 386518] Decrypt and verify both crash
https://bugs.kde.org/show_bug.cgi?id=386518 --- Comment #2 from Andre Heinecke --- We had a crash in Kleopatra on Verify that has been fixed: https://dev.gnupg.org/T3761 (Or here BUG 389792 ) We also fixed instabilities of Kleopatra when used with a APPDATA directory that lives on a UNC path (\\Server\foo\). Maybe this is the case for you, too? For decryption I was unable to reproduce a crash. Could you try with the latest beta https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe if this crash still exists for you? And if so could you add more details what exactly are your steps to make it crash? -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391519] nicks should be clickable
https://bugs.kde.org/show_bug.cgi?id=391519 --- Comment #1 from Laurent Montel --- Ah ok I see the problem. I will investigate for fixing it this week. Thanks for idea. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391520] handling of newlines
https://bugs.kde.org/show_bug.cgi?id=391520 --- Comment #1 from Laurent Montel --- Oh indeed ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 381432] Olympus ORF files to DNG conversion fails in Windows 10
https://bugs.kde.org/show_bug.cgi?id=381432 --- Comment #37 from Grix --- Finally bug on ORF files in Windows versión of digikam is fixed in versión 5.8 I've tested in digikam 5.8, windows 10 creator's update and it Works ok. Good work, I know those type of bugs are difficult to track so THANKS FOR YOUR GREAT JOB ! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 391523] New: Code improvement: reduce unnecessary switch
https://bugs.kde.org/show_bug.cgi?id=391523 Bug ID: 391523 Summary: Code improvement: reduce unnecessary switch Product: frameworks-kuserfeedback Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Telemetry Provider Assignee: vkra...@kde.org Reporter: akontsev...@gmail.com Target Milestone: --- Hi Volker, I think feedbackconfiguicontroller.cpp could be improved a little. We can change line 129 to: const auto name = (d->appName().isEmpty()) ? "this application" : d->appName().isEmpty(); and remove 1st switch to make code simpler and keep messages consistency. Thanks! -- You are receiving this mail because: You are watching all bug changes.
