[krusader] [Bug 376699] New: No Icons in tool bar
https://bugs.kde.org/show_bug.cgi?id=376699 Bug ID: 376699 Summary: No Icons in tool bar Product: krusader Version: 2.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@fork.pl Reporter: ch-hani...@t-online.de Target Milestone: --- in some ditributions and desktops no Icons in tool bar. Only text in tool bar. For example in Enlightenment under Manjaro. Sometimes text and Icons are mixed. Why? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376698] New: Plasma crashed after reboot
https://bugs.kde.org/show_bug.cgi?id=376698 Bug ID: 376698 Summary: Plasma crashed after reboot Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: catalin.pic...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.9-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: After performing an upgrade on my ArchLinux x86_64 machine I did a reboot, a couple of seconds after login back Plasma crashed - I wasn't doing anything on the machine at that moment just waiting for everything to start up. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd324b99800 (LWP 950))] Thread 8 (Thread 0x7fd269050700 (LWP 1064)): #0 0x7fd3190c9e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fd31908464d in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd3190848bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd31eb8a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd31eb3389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd31e955a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd322642fd6 in () at /usr/lib/libQt5Quick.so.5 #7 0x7fd31e95a6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fd31d825454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd31e26f7df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fd2fcdce700 (LWP 1061)): #0 0x7fd31d82b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd324337234 in () at /usr/lib/libQt5Script.so.5 #2 0x7fd324337279 in () at /usr/lib/libQt5Script.so.5 #3 0x7fd31d825454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd31e26f7df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd2febeb700 (LWP 1060)): #0 0x7fd31e2624ed in read () at /usr/lib/libc.so.6 #1 0x7fd3190c8aa0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd31908426e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fd319084744 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fd3190848bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fd31eb8a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fd31eb3389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fd31e955a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fd31e95a6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fd31d825454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fd31e26f7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd2f700 (LWP 1056)): #0 0x7fd3190c9e45 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7fd3190837b4 in g_main_context_release () at /usr/lib/libglib-2.0.so.0 #2 0x7fd31908475a in () at /usr/lib/libglib-2.0.so.0 #3 0x7fd3190848bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fd31eb8a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd31eb3389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fd31e955a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fd321a8f025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fd31e95a6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fd31d825454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fd31e26f7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd3067c0700 (LWP 1018)): #0 0x7fd31e2624ed in read () at /usr/lib/libc.so.6 #1 0x7fd3190c8aa0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd31908426e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fd319084744 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fd3190848bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fd31eb8a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fd31eb3389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fd31e955a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fd321a8f025 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fd31e95a6d8 in () at /usr/lib/libQt5Core.so.5 #10 0x7fd31d825454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fd31e26f7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd307fff700 (LWP 974)): #0 0x7fd31e26648d in poll () at /usr/lib/libc.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 Abderrahman Najjar changed: What|Removed |Added CC|abderrahman.naj...@gmail.co | |m | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376582] System Settings crash when trying to access QtCurve configuration
https://bugs.kde.org/show_bug.cgi?id=376582 ttv...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||ttv...@gmail.com --- Comment #1 from ttv...@gmail.com --- *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 ttv...@gmail.com changed: What|Removed |Added CC||slob...@gmail.com --- Comment #90 from ttv...@gmail.com --- *** Bug 376582 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376603] Crash after changing composing engine to OpenGL 3.1
https://bugs.kde.org/show_bug.cgi?id=376603 ttv...@gmail.com changed: What|Removed |Added CC||ttv...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from ttv...@gmail.com --- *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 ttv...@gmail.com changed: What|Removed |Added CC||arturpol...@gmail.com --- Comment #89 from ttv...@gmail.com --- *** Bug 376603 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 --- Comment #88 from ttv...@gmail.com --- I can confirm that the bug fixed on: openSUSE Tumbleweed (rolling) with: KDE Plasma 5.9.2 Qt 5.7.1 KDE Frameworks 5.30.0 Mark as resolved? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326404] Unable to select picture in map search view
https://bugs.kde.org/show_bug.cgi?id=326404 --- Comment #7 from Wolfgang Scheffner --- Nicofo, After working a while now with all the geolocation tools in digiKam (AppImage 5.5.0) in order to write the doc about it I have an idea what your problem might be. In the Map View of the Left Sidebar which is the geolocation search tool the Select Images button works only on those images which are in your current region selection, indicated by a rectangle on the map. Here it will just toggle the selection of the pic or group of pics you are clicking on in the Image Area (central part of the digiKam window). This can be helpful to fine tune your selection before carrying out operations from the Right Sidebar or the menus. The button has no effect on pics outside of the rectangle which is intended behaviour. Wouldn't make sense anyway since they are not displayed in the Image Area. The Filter-images button you mention in Comment 2 filters the result of you region selection which means that only the one pic or group of pics you are clicking on is displayed in the Image Area. This is particular useful if the map is just showing markers or if the thumbnails are too small to clearly identify images. I hope this explanation can solve your problem. If you confirm we could close this bug. The handbook will be updated with the next release. Remains only the problem with the shape of the mouse pointer wich is subject of https://bugs.kde.org/show_bug.cgi?id=376072. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 301048] BQM Watermark tool : more super-impose visible watermark options [patch]
https://bugs.kde.org/show_bug.cgi?id=301048
--- Comment #4 from caulier.gil...@gmail.com ---
Ahmed,
Patch do not compile :
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:
In constructor ‘Digikam::WaterMark::Private::Private()’:
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:127:22:
warning: ‘Digikam::WaterMark::Private::useTextRadioButton’ will be initialized
after [-Wreorder]
QRadioButton*useTextRadioButton;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:124:22:
warning: ‘QCheckBox* Digikam::WaterMark::Private::useBackgroundCheckBox’
[-Wreorder]
QCheckBox* useBackgroundCheckBox;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:89:5:
warning: when initialized here [-Wreorder]
Private() :
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:133:22:
warning: ‘Digikam::WaterMark::Private::placementPositionComboBox’ will be
initialized after [-Wreorder]
QComboBox* placementPositionComboBox;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:132:22:
warning: ‘QComboBox* Digikam::WaterMark::Private::placementTypeComboBox’
[-Wreorder]
QComboBox* placementTypeComboBox;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:89:5:
warning: when initialized here [-Wreorder]
Private() :
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:135:22:
warning: ‘Digikam::WaterMark::Private::sparsityFactorSpinBox’ will be
initialized after [-Wreorder]
QDoubleSpinBox * sparsityFactorSpinBox;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:134:22:
warning: ‘QComboBox* Digikam::WaterMark::Private::rotationComboBox’
[-Wreorder]
QComboBox* rotationComboBox;
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:89:5:
warning: when initialized here [-Wreorder]
Private() :
^
In file included from /usr/lib64/qt5/include/QtGui/qfont.h:38:0,
from /usr/lib64/qt5/include/QtGui/QFont:1,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.h:31,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:26:
/usr/lib64/qt5/include/QtCore/qstring.h: In member function ‘virtual void
Digikam::WaterMark::registerSettingsWidget()’:
/usr/lib64/qt5/include/QtCore/qstring.h:788:5: error: ‘QString::QString(const
char*)’ is private
QString(const char *ch);
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:322:177:
error: within this context
d->denseRepetitionCheckBox->setWhatsThis("When you choose to have the
watermark repeated many times in the placement combo box, you can specify here
whether the repetition");
^
In file included from /usr/lib64/qt5/include/QtGui/qfont.h:38:0,
from /usr/lib64/qt5/include/QtGui/QFont:1,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.h:31,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:26:
/usr/lib64/qt5/include/QtCore/qstring.h:788:5: error: ‘QString::QString(const
char*)’ is private
QString(const char *ch);
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:336:126:
error: within this context
"you can check this to make the
watermark rotations random also[0,90,180,270]");
^
In file included from /usr/lib64/qt5/include/QtGui/qfont.h:38:0,
from /usr/lib64/qt5/include/QtGui/QFont:1,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.h:31,
from
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:26:
/usr/lib64/qt5/include/QtCore/qstring.h:788:5: error: ‘QString::QString(const
char*)’ is private
QString(const char *ch);
^
/home/gilles/Devel/5.x/core/utilities/queuemanager/tools/decorate/watermark.cpp:356:103:
error: within this context
" typically between 1.0 and 3.0.
can also be less than 1.0");
^
core/utilities/queuemanager/CMakeFiles/queuemanager_src.dir/build.make:5
[digikam] [Bug 301048] BQM Watermark tool : more super-impose visible watermark options [patch]
https://bugs.kde.org/show_bug.cgi?id=301048 caulier.gil...@gmail.com changed: What|Removed |Added Summary|BQM Watermark tool : more |BQM Watermark tool : more |super-impose visible|super-impose visible |watermark options [patch} |watermark options [patch] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 301048] BQM Watermark tool : more super-impose visible watermark options [patch}
https://bugs.kde.org/show_bug.cgi?id=301048 caulier.gil...@gmail.com changed: What|Removed |Added Summary|BQM Watermark tool : more |BQM Watermark tool : more |super-impose visible|super-impose visible |watermark options |watermark options [patch} -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 376697] New: Possible Duplicates should have the option to show only Bugs from the selected product
https://bugs.kde.org/show_bug.cgi?id=376697 Bug ID: 376697 Summary: Possible Duplicates should have the option to show only Bugs from the selected product Product: bugs.kde.org Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: wscheffn...@gmail.com CC: she...@kde.org Target Milestone: --- When filling in the Summary field in bugs.kde.org the Possible Duplicates list appears. Among the entries in this list there are usually a lot, sometimes only bugs from other products. I don't understand what this is good for. Normally I'm only interested in bugs of the product I'm reporting for. At least I would expect an option to restrict the search to that product. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 Elias Probst changed: What|Removed |Added CC||m...@eliasprobst.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376696] KWin fails when the developer debugs an application built in JavaFX (Netbeans and Scenic View)
https://bugs.kde.org/show_bug.cgi?id=376696 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages provided by your distribution (please ask the distribution support channel on how to install them) and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376696] New: KWin fails when the developer debugs an application built in JavaFX (Netbeans and Scenic View)
https://bugs.kde.org/show_bug.cgi?id=376696 Bug ID: 376696 Summary: KWin fails when the developer debugs an application built in JavaFX (Netbeans and Scenic View) Product: kwin Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: hopere...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.9-200.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - Netbeans 8.2 + Scenic View, the error appears when the developer executes the application in debug mode. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f93f3fe76c0 (LWP 5301))] Thread 5 (Thread 0x7f93bdfc9700 (LWP 5312)): #0 0x7f9406fab460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f940c8252f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f940c825339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f9406fa56ca in start_thread () from /lib64/libpthread.so.0 #4 0x7f9404186f7f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f93c8216700 (LWP 5309)): #0 0x7f940417b0e1 in ppoll () from /lib64/libc.so.6 #1 0x7f9404f7d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f9404f7ee86 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f9404f3268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f9404d8f5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f940ba7a4e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7f9404d939ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f9406fa56ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f9404186f7f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f93e92c6700 (LWP 5308)): #0 0x7f940417b0e1 in ppoll () from /lib64/libc.so.6 #1 0x7f9404f7d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f9404f7ee86 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f9404f3268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f9404d8f5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f940ba7a4e5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7f9404d939ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f9406fa56ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f9404186f7f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f93eafc9700 (LWP 5306)): #0 0x7f940417b0e1 in ppoll () from /lib64/libc.so.6 #1 0x7f9404f7d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f9404f7ee86 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7f9404f3268a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f9404d8f5e3 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7f9406aa0739 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #6 0x7f9404d939ca in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7f9406fa56ca in start_thread () from /lib64/libpthread.so.0 #8 0x7f9404186f7f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f93f3fe76c0 (LWP 5301)): [KCrash Handler] #6 0x in ?? () #7 0x7f9404f60878 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /lib64/libQt5Core.so.5 #8 0x7f940c867d2f in QScriptEnginePrivate::qobjectData(QObject*) () from /lib64/libQt5Script.so.5 #9 0x7f940c867df4 in QScriptEnginePrivate::newQObject(QObject*, QScriptEngine::ValueOwnership, QFlags const&) () from /lib64/libQt5Script.so.5 #10 0x7f940c8680e2 in QScriptEngine::newQObject(QObject*, QScriptEngine::ValueOwnership, QFlags const&) () from /lib64/libQt5Script.so.5 #11 0x7f940d23254c in KWin::effectWindowToScriptValue(QScriptEngine*, KWin::EffectWindow* const&) () from /lib64/libkwin.so.5 #12 0x7f940c868395 in QScriptEnginePrivate::create(QTJSC::ExecState*, int, void const*) () from /lib64/libQt5Script.so.5 #13 0x7f940c8910d6 in QScript::QObjectConnectionManager::execute(int, void**) () from /lib64/libQt5Script.so.5 #14 0x7f940c8993e1 in QScript::QObjectConnectionManager::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/
[plasmashell] [Bug 371728] [Folder View] Icons disappear.
https://bugs.kde.org/show_bug.cgi?id=371728 Tony changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376676] thumbnail.so causes high CPU load
https://bugs.kde.org/show_bug.cgi?id=376676 --- Comment #2 from Peter Ullinger --- - The name of the process causing the high CPU load is thumbnail.so according to htop and ksysguard. - The process is started every time I browse a folder with Dolphin and switch on the preview. thumbnail.so will then use 100% of one CPU core until I kill it, even if this folder has only three PDFs or two videos in it and those are shown after a split of a second. - Sorry, but what is a callgrind log, and where do I find thumbnail.so's one? Htops infos: https://goo.gl/photos/ZaQrtizfXu9rkqJH6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376695] New: StartupWMClass not honoured
https://bugs.kde.org/show_bug.cgi?id=376695 Bug ID: 376695 Summary: StartupWMClass not honoured Product: plasmashell Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: pe...@ceiley.net CC: plasma-b...@kde.org Target Milestone: 1.0 The icons-only task manager does not appear to honour the StartupWMClass in a .desktop spec file. Example: Chrome/Chromium app with .desktop file Expected behaviour: When launching the Chrome app, the active window should be associated with it's own 'icon'. This is the behaviour in the Gnome dock and other docks such as Plank. Actual behaviour: When launching the Chrome app, the app icon 'disappears' immediately and it is grouped with other Chrome windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 Shmerl changed: What|Removed |Added CC|shm...@mykolab.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #48 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Martin Klapetek from comment #46) > > I don't understand what is so complicated about it. > > Exactly. It is possible you might be deeply mistaken on this particular occasion. > We're talking about a system-wide setting that > will automatically be applied to /all/ Qt applications, > not on per application basis. And ideally should also > include GTK apps but that's for bonus points. > > But please, by all means, Qt is opensource, don't let > me stop you from submitting a patch that will provide > an easy way to customize your system datetime format > and thus fix this properly for everybody. There is no world-wide micropayment feedback system for compensating open-source contributors yet. It will take at least 20 years for such a system to emerge. > There's no point you arguing your way with me here, > this is an issue that needs to be solved in Qt and I'm > not a Qt developer and I won't solve it here for you. > > Feel free to link your Qt discussion/patch here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #47 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Jan Ziak (http://atom-symbol.net) from comment #45) > Valgelis, the man and his music (1984) Correction: Vangelis, of course. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #46 from Martin Klapetek --- > I don't understand what is so complicated about it. Exactly. We're talking about a system-wide setting that will automatically be applied to /all/ Qt applications, not on per application basis. And ideally should also include GTK apps but that's for bonus points. But please, by all means, Qt is opensource, don't let me stop you from submitting a patch that will provide an easy way to customize your system datetime format and thus fix this properly for everybody. There's no point you arguing your way with me here, this is an issue that needs to be solved in Qt and I'm not a Qt developer and I won't solve it here for you. Feel free to link your Qt discussion/patch here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #45 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Martin Klapetek from comment #44) > Sure, now how would you make every single Qt app > out there know which &format to pass there so that > they all display the same date format? Well, you > wouldn't because this problem is non-trivial. > > But you're of course welcome to do your research > and then propose a Qt patch that would allow to > set custom System Locale formats for datetime. > Believe me, if it was that simple, it would have > been done already. I don't understand what is so complicated about it. Once I found it is located in qlocale.cpp in QLocale::dateFormat(FormatType)→QString, I am able to _prefix_ (customize) the behavior of the function in any way I can rationally imagine. For example, it shouldn't be that hard for me to implement per-application (i.e: argv[0]) customization of the FormatType→QString conversion, while having the conversions stored in file "~/.config/by-argv0/qlocale_dateformats.txt". Not that I need it - I am just saying it is doable. Another example: It shouldn't be that hard to enable transient (i.e: time based) customizations of the FormatType→QString conversion. So for example, if I wanted to customize the behavior of the conversion function just in the header/footer when printing a snippet of C++ source code from KDevelop into PDF file, I can customize the result of the function based on the tuple (argv[0]=="kdevelop", time==aboutNow). Another example would be to enable temporary adjustments of the behavior based on function names in the backtrace obtained by running "gdb --pid" or by using libunwind. For a dose of creativity, innovation and imagination see for example https://www.youtube.com/watch?v=WwBaeIw8kSQ - Valgelis, the man and his music (1984) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #44 from Martin Klapetek --- Sure, now how would you make every single Qt app out there know which &format to pass there so that they all display the same date format? Well, you wouldn't because this problem is non-trivial. But you're of course welcome to do your research and then propose a Qt patch that would allow to set custom System Locale formats for datetime. Believe me, if it was that simple, it would have been done already. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 374670] AAC transcoding is broken due to deprecated libfaac
https://bugs.kde.org/show_bug.cgi?id=374670 --- Comment #5 from rdragonr...@gmail.com --- Okay, it seems that this is not getting resolved on its own. How might *I* submit that patch to the review board? How does that work? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376694] New: SOFTWARE CENTRE
https://bugs.kde.org/show_bug.cgi?id=376694 Bug ID: 376694 Summary: SOFTWARE CENTRE Product: Discover Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: davidrawlinso...@gmail.com Target Milestone: --- SOFTWARE CENTRE DISCOVER NOT DISPLAYING INSTALLED UPDATES AND WHEN I CLICK ON ENY CATEGORIES NO CONTENT IS SHOWN AND PAGES ARE BLANK,AND POPLUAR AND BEST RATING ARE BLANK ALSO. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376693] New: QAction objects passed to ContextMenuExtension are leaked
https://bugs.kde.org/show_bug.cgi?id=376693 Bug ID: 376693 Summary: QAction objects passed to ContextMenuExtension are leaked Product: kdevplatform Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: kosse...@kde.org Target Milestone: --- Many plugins create QAction objects on the fly in their implementation of the IPlugin::contextMenuExtension() method and then pass on those inside the returned ContextMenuExtension and forget about them. Just, as the ownership is not specified, callers of the IPlugin::contextMenuExtension() API do not take lifetime responsibility themselves for the QAction objects (and QMenu objects). With noone caring... objects are leaking and accumulating. On a first look I could not find a simple solution, so for now noting here. Things to consider: * Some plugins also pass existing QAction items which are in used elsewhere, e.g. in the toplevel menu. So simply deleting any QAction objects on destruction of the ContextMenuExtension instance does not work. Might work to just delete objects without a parent. * More, ContextMenuExtension is currently passed by value and is not explicitely sharing data, so there are many copies of the lists with the pointers to the QAction objects * The menus filled by the ContextMenuExtension in the API users might have a longer lifetime than the ContextMenuExtension objects, that needs some work as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375189] plsama crash notification
https://bugs.kde.org/show_bug.cgi?id=375189 Christoph Feck changed: What|Removed |Added CC||eike.kappelh...@web.de --- Comment #2 from Christoph Feck --- *** Bug 374718 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374718] plasma desktop crashed
https://bugs.kde.org/show_bug.cgi?id=374718 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- Bug 375189 has a better backtrace. *** This bug has been marked as a duplicate of bug 375189 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 376624] [request] Integrate polkit actions to kio
https://bugs.kde.org/show_bug.cgi?id=376624 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376692] New: Search function fails to find phrases split over two lines
https://bugs.kde.org/show_bug.cgi?id=376692 Bug ID: 376692 Summary: Search function fails to find phrases split over two lines Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: tcol...@livingdata.com.au Target Milestone: --- When using the search function to find phrases in PDF's , I've found that Okular fails to find phrases split over two lines. For example, if I searched the following text in a PDF for "United States", it would only find the first instance; not the other two. I love the United States. My friend said she loves the United States too but wouldn't want to live there. I live in the Unit- ed States. Since the need to find phrases whether they are split over two lines or not is almost universal, I think this feature would be widely appreciated. Thank you! I am using Okular 0.19.3 (KDE Development Platform 4.13.3) on Ubuntu 14.04, which is the latest version currently available in the Ubuntu standard repositories. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376680] File type icons not suitable for dark themes
https://bugs.kde.org/show_bug.cgi?id=376680 --- Comment #2 from Janek Bevendorff --- Created attachment 104121 --> https://bugs.kde.org/attachment.cgi?id=104121&action=edit Project Explorer Icons Sure. There you go. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 Aetf <7437...@gmail.com> changed: What|Removed |Added CC||7437...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376687] GPS tagging usability of bookmarks
https://bugs.kde.org/show_bug.cgi?id=376687 --- Comment #2 from Wolfgang Scheffner --- https://bugs.kde.org/show_bug.cgi?id=376391 is also related. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376687] GPS tagging usability of bookmarks
https://bugs.kde.org/show_bug.cgi?id=376687 Wolfgang Scheffner changed: What|Removed |Added CC||wscheffn...@gmail.com --- Comment #1 from Wolfgang Scheffner --- To get an idea of the situation regarding these bookmarks see https://bugs.kde.org/show_bug.cgi?id=376074 ! Maybe this bug should be marked a duplicate but I'm not sure and also don't know how to do that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376574] Linked video in pdf doesn't work
https://bugs.kde.org/show_bug.cgi?id=376574 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/oku ||lar/ee7e3737f4d2031e9bac9f5 ||a25ac0b31c2f5e496 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Albert Astals Cid --- Git commit ee7e3737f4d2031e9bac9f5a25ac0b31c2f5e496 by Albert Astals Cid. Committed on 20/02/2017 at 00:06. Pushed by aacid into branch 'Applications/16.12'. Account for non local non relative video file urls M +22 -32 ui/videowidget.cpp https://commits.kde.org/okular/ee7e3737f4d2031e9bac9f5a25ac0b31c2f5e496 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #8 from supaiku --- I forgot to add, that I got a lot of prints of: krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to continuePrimaryAction while being mode 0 ! krita.general: Unexpected tool event has come to endPrimaryAction while being mode 0 ! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371007] Crash in QMetaObject::cast in QtQuickControls
https://bugs.kde.org/show_bug.cgi?id=371007 David Edmundson changed: What|Removed |Added Summary|Modify systray options, |Crash in QMetaObject::cast |Plasmashell crash and |in QtQuickControls |Restart OK | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376676] thumbnail.so causes high CPU load
https://bugs.kde.org/show_bug.cgi?id=376676 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Attaching a file of memory allocations tells us nothing about the CPU load. If you want to reopen this bug, I need: - the name of the process that's using a lot of CPU. - Was something meant to be showing an uncrawled folder? If so, what part makes a bug. - Ideally, a callgrind log. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 376638] KDE Connect 1.6 loosing file extension
https://bugs.kde.org/show_bug.cgi?id=376638 Guido Schmidt changed: What|Removed |Added CC||gu...@sanguepreto.de --- Comment #1 from Guido Schmidt --- Exactly the same thing happend to here an my tablet. Version on tablet is 1.6, on Desktop 1.0.1-1.4. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 --- Comment #7 from supaiku --- I found a reliable way to provoke a crash. Today it happened again on the client mentioned above, while using the transform tool, BUT this time someone could tell me exactly what was pressed. He was using the transform tool and pressed B. So I fired up Krita on my Arch Linux and played on an empty canvas with the tranform tool. 1. STRG + T 2. Rotate a bit... 3. Press B / E randomly 4. Alternate between 3. and 4. 5. Eventually Krita closes. I could reproduce it again and again. So I compiled Krita from source and attached gdb. (Note: I'm using a different graphics driver than the client, but I guess the cause is the same) Here's the stacktrace: Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x7fffec250258 in malloc_consolidate () from /usr/lib/libc.so.6 (gdb) bt #0 0x7fffec250258 in malloc_consolidate () from /usr/lib/libc.so.6 #1 0x7fffec250e40 in _int_free () from /usr/lib/libc.so.6 #2 0x7fffd6c5cdc4 in ?? () from /usr/lib/libdrm_intel.so.1 #3 0x7fffd6c5d01e in ?? () from /usr/lib/libdrm_intel.so.1 #4 0x7fffd724b3c9 in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so #5 0x7fffd6fbe3ac in ?? () from /usr/lib/xorg/modules/dri/i965_dri.so #6 0x775d7194 in Sync::syncStatus (syncObject=0x1ca63bb0) at /home/supaiku/hacking/krita-git/libs/ui/opengl/kis_opengl_canvas2_p.h:109 #7 0x775d8d2e in KisOpenGLCanvas2::isBusy (this=0x18c516f0) at /home/supaiku/hacking/krita-git/libs/ui/opengl/kis_opengl_canvas2.cpp:423 #8 0x773adc5c in KisCanvas2::slotDoCanvasUpdate (this=0x18c26008) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:664 #9 0x7783f39f in KisCanvas2::qt_static_metacall (_o=0x18c26008, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0x7fffd240) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/ui/kritaui_automoc.dir/moc_kis_canvas2_LX4NUNHD4DUJWF.cpp:202 #10 0x7fffed0cdd49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #11 0x762fe72f in KisSignalCompressor::timeout (this=0x18c57320) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/image/kritaimage_automoc.dir/moc_kis_signal_com_NQZINSG4MKTJFA.cpp:144 #12 0x7617441b in KisSignalCompressor::start (this=0x18c57320) at /home/supaiku/hacking/krita-git/libs/image/kis_signal_compressor.cpp:63 #13 0x773ade32 in KisCanvas2::updateCanvasWidgetImpl (this=0x18c26008, rc=...) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:687 #14 0x773ade61 in KisCanvas2::updateCanvas (this=0x18c26008) at /home/supaiku/hacking/krita-git/libs/ui/canvas/kis_canvas2.cpp:692 #15 0x7fff9c3e2d61 in KisToolTransform::deactivate (this=0x18f0b2f0) at /home/supaiku/hacking/krita-git/plugins/tools/tool_transform2/kis_tool_transform.cc:825 #16 0x75191670 in KoToolManager::Private::disconnectActiveTool (this=0x16e84110) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:608 #17 0x751918bc in KoToolManager::Private::switchTool (this=0x16e84110, tool=0x18d65430, temporary=false) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:635 #18 0x75191b1d in KoToolManager::Private::switchTool (this=0x16e84110, id=..., temporary=false) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:663 #19 0x7518f60b in KoToolManager::switchToolRequested (this=0x754e70d0 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder>, id=...) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager.cpp:316 #20 0x7518e51f in ShortcutToolAction::actionTriggered (this=0x190a4a90) at /home/supaiku/hacking/krita-git/libs/flake/KoToolManager_p.cpp:262 #21 0x7525629f in ShortcutToolAction::qt_static_metacall (_o=0x190a4a90, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffd610) at /home/supaiku/hacking/build-krita-git-Desktop-Debug/libs/flake/kritaflake_automoc.dir/moc_KoToolManager__CHRU4NQGN3E7OY.cpp:320 #22 0x7fffed0cdd49 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #23 0x7fffedf81c92 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #24 0x7fffedf843f0 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #25 0x7fffedf84d6c in QAction::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #26 0x7fffedf8834c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7fffedf8fb61 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7776cb11 in KisApplication::notify (this=0x7fffdf30, receiver=0x190a4a90, event=0x7fffd9d0) at /home/supaiku/hacking/krita-git/libs/ui/KisApplication.cpp:532 #29 0x7fffed0a2440 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #30 0x7fffed61cf28 in QShortcutMap::di
[neon] [Bug 376089] Bad Looking for qt4 Applications
https://bugs.kde.org/show_bug.cgi?id=376089 --- Comment #4 from anderlia --- Created attachment 104120 --> https://bugs.kde.org/attachment.cgi?id=104120&action=edit Clementine after deletion of Trolltech.conf file -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 376089] Bad Looking for qt4 Applications
https://bugs.kde.org/show_bug.cgi?id=376089 --- Comment #3 from anderlia --- I first fixed the issue by configuring another theme with qtconfig-qt4 (GTK+ instead of default desktop settings). Then I realized that, by removing ~/.config/Trolltech.conf wherein all qt4 settings seem to be stored, Clementine falls back on the correct qt4 Breeze theme. Nothing to do with KDE Neon upgrade (or maybe some updated package did modify my Trolltech.conf file). The bug can be closed. Thanks Jonathan for having a look. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #43 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Martin Klapetek from comment #42) > I suggest you submit your patch to Qt then and let the > actual Qt developers comment on that. There already exist the following functions: QString QDate::toString(const QString &format) const QString QDateTime::toString(const QString &format) const http://doc.qt.io/qt-5/qdate.html#toString http://doc.qt.io/qt-5/qdatetime.html#toString -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 376662] kstart5: Unknown option 'windowclass'.
https://bugs.kde.org/show_bug.cgi?id=376662 --- Comment #4 from Aleix Pol --- You are right, Luigi. Markus, can you provide us your actual name so we can put on the commit? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 376669] window title doesn't show utf-8 folders
https://bugs.kde.org/show_bug.cgi?id=376669 --- Comment #2 from csaba zsadányi-nagy --- > What OS are you using? It appears to work as expected on Linux. as i wrote: Kubuntu 16.04.2 LTS, and it was the same in 16.04.1 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 376662] kstart5: Unknown option 'windowclass'.
https://bugs.kde.org/show_bug.cgi?id=376662 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #3 from Luigi Toscano --- Aleix, can you please revert and commit with the proper author? I don't think that "Markus Bugzilla" is a proper name... -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 376662] kstart5: Unknown option 'windowclass'.
https://bugs.kde.org/show_bug.cgi?id=376662 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||-cli-tools/c3aa100b814197fa ||19b271db0dcfe7d9b962c510 Resolution|--- |FIXED --- Comment #2 from Aleix Pol --- Git commit c3aa100b814197fa19b271db0dcfe7d9b962c510 by Aleix Pol, on behalf of Markus Bugzilla. Committed on 19/02/2017 at 22:52. Pushed by apol into branch 'Plasma/5.9'. Fix QCommandLineParser usage WRT windowclass parameter M +2-2kstart/kstart.cpp https://commits.kde.org/kde-cli-tools/c3aa100b814197fa19b271db0dcfe7d9b962c510 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 376662] kstart5: Unknown option 'windowclass'.
https://bugs.kde.org/show_bug.cgi?id=376662 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Aleix Pol --- Applying the patch. Please next time upload your change to phabricator.kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376680] File type icons not suitable for dark themes
https://bugs.kde.org/show_bug.cgi?id=376680 Aleix Pol changed: What|Removed |Added CC||aleix...@kde.org, ||kain...@gmail.com --- Comment #1 from Aleix Pol --- Can you please send a screenshot of what you mean? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373519] baloo indexer crashed at restart akonadi
https://bugs.kde.org/show_bug.cgi?id=373519 --- Comment #1 from Stephan Diestelhorst --- Created attachment 104119 --> https://bugs.kde.org/attachment.cgi?id=104119&action=edit New crash information added by DrKonqi akonadi_baloo_indexer (4.14) on KDE Platform 4.14.22 using Qt 4.8.7 KDE neon here, seems like it crashes with the same issue other people have. Somehow cannot access the log. -- Backtrace (Reduced): #6 0x7fd27b53c428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fd27b53e02a in __GI_abort () at abort.c:89 [...] #11 0x7fd27f247d21 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7fd27c793fdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7fd27c79af16 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373519] baloo indexer crashed at restart akonadi
https://bugs.kde.org/show_bug.cgi?id=373519 Stephan Diestelhorst changed: What|Removed |Added CC||stephan.diestelhorst@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 376691] New: Baloo crashes when Kubuntu starts
https://bugs.kde.org/show_bug.cgi?id=376691 Bug ID: 376691 Summary: Baloo crashes when Kubuntu starts Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: i...@iki.fi Target Milestone: --- Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-62-generic i686 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Starting my computer HP Compaq 8200 Elite. When Kubuntu 16.04.1 starts, baloo crashes. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xb5bf31fa in mdb_txn_begin () from /usr/lib/i386-linux-gnu/liblmdb.so.0 #8 0xb74632c2 in Baloo::Transaction::Transaction(Baloo::Database const&, Baloo::Transaction::TransactionType) () from /usr/lib/i386-linux-gnu/libKF5BalooEngine.so.5 #9 0xb74633e0 in Baloo::Transaction::Transaction(Baloo::Database*, Baloo::Transaction::TransactionType) () from /usr/lib/i386-linux-gnu/libKF5BalooEngine.so.5 #10 0x0806e095 in Baloo::MetadataMover::removeFileMetadata(QString const&) () #11 0x0806b672 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () #12 0xb7179080 in QtPrivate::QSlotObjectBase::call (a=0xbf88d754, r=0x8812c18, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #13 QMetaObject::activate (sender=0x87be020, signalOffset=3, local_signal_index=3, argv=0xbf88d754) at kernel/qobject.cpp:3698 #14 0xb717995d in QMetaObject::activate (sender=0x87be020, m=0x8094c88 , local_signal_index=3, argv=0xbf88d754) at kernel/qobject.cpp:3578 #15 0x08077f71 in Baloo::PendingFileQueue::removeFileIndex(QString const&) () #16 0x0806c0d4 in Baloo::PendingFileQueue::processCache() () #17 0x0806d3cb in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () #18 0xb7179080 in QtPrivate::QSlotObjectBase::call (a=0xbf88d8a8, r=0x87be020, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=0x87be02c, signalOffset=3, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3698 #20 0xb717995d in QMetaObject::activate (sender=0x87be02c, m=0xb73b548c , local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3578 #21 0xb71fc202 in QTimer::timeout (this=0x87be02c) at .moc/moc_qtimer.cpp:197 #22 0xb7186061 in QTimer::timerEvent (this=0x87be02c, e=0xbf88da7c) at kernel/qtimer.cpp:247 #23 0xb717a04e in QObject::event (this=0x87be02c, e=0xbf88da7c) at kernel/qobject.cpp:1261 #24 0xb71494ac in QCoreApplicationPrivate::notify_helper (this=0x8795e18, receiver=0x87be02c, event=0xbf88da7c) at kernel/qcoreapplication.cpp:1093 #25 0xb714964d in QCoreApplication::notify (event=0xbf88da7c, receiver=0x87be02c, this=0xbf88dd1c) at kernel/qcoreapplication.cpp:1038 #26 QCoreApplication::notifyInternal (this=0xbf88dd1c, receiver=0x87be02c, event=0xbf88da7c) at kernel/qcoreapplication.cpp:965 #27 0xb71a068c in QCoreApplication::sendEvent (event=0xbf88da7c, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #28 QTimerInfoList::activateTimers (this=0x879739c) at kernel/qtimerinfo_unix.cpp:637 #29 0xb71a0c39 in timerSourceDispatch (source=0x8797368) at kernel/qeventdispatcher_glib.cpp:177 #30 0xb566fee9 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #31 0xb5670189 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #32 0xb5670254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #33 0xb71a1943 in QEventDispatcherGlib::processEvents (this=0x8795cd8, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #34 0xb71467a3 in QEventLoop::processEvents (this=0xbf88dc98, flags=...) at kernel/qeventloop.cpp:128 #35 0xb7146bfa in QEventLoop::exec (this=0xbf88dc98, flags=...) at kernel/qeventloop.cpp:204 #36 0xb714f1d5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #37 0x0805aa60 in main () Possible duplicates by query: bug 354275, bug 353851. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376689] Preview tooltip disappears making it impossible to select a file inside of it
https://bugs.kde.org/show_bug.cgi?id=376689 --- Comment #2 from Mahendra Tallur --- Thanks for the triaging ! My god, I really spend quite some time checking if my bug was not reported before, and most of the time I file yet another duplicate :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376632] [Regression] Cascading folder view closes on hover
https://bugs.kde.org/show_bug.cgi?id=376632 Kai Uwe Broulik changed: What|Removed |Added CC||ma...@free.fr --- Comment #1 from Kai Uwe Broulik --- *** Bug 376689 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376689] Preview tooltip disappears making it impossible to select a file inside of it
https://bugs.kde.org/show_bug.cgi?id=376689 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@privat.broulik.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 376632 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376688] Dolphin tooltips : cannot add comments / tags
https://bugs.kde.org/show_bug.cgi?id=376688 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- Hi, this has been recently fixed. Tooltips will be fully functional in the next Dolphin release. *** This bug has been marked as a duplicate of bug 352276 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 352276] Tooltip is not clickable, thus links in tooltip are useless
https://bugs.kde.org/show_bug.cgi?id=352276 Elvis Angelaccio changed: What|Removed |Added CC||ma...@free.fr --- Comment #2 from Elvis Angelaccio --- *** Bug 376688 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 374736] balooctl clear doesn't clear deleted files
https://bugs.kde.org/show_bug.cgi?id=374736 --- Comment #4 from Lukas Ba. --- Still happening in version 5.31.0-1. Can someone at least confirm this bug? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376690] New: Irritating behavior of list when moving images
https://bugs.kde.org/show_bug.cgi?id=376690 Bug ID: 376690 Summary: Irritating behavior of list when moving images Product: digikam Version: 5.5.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Presentation Assignee: digikam-de...@kde.org Reporter: wscheffn...@gmail.com Target Milestone: --- When moving images in the list of the Presentation tool by d&d the list jumps back to the position you took the image from once you dropped it. This is very irritating. I would expect the list to stay at the position where I drop the image so that one can see the result: the image at its new position. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376688] Dolphin tooltips : cannot add comments / tags
https://bugs.kde.org/show_bug.cgi?id=376688 Mahendra Tallur changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376689] New: Preview tooltip disappears making it impossible to select a file inside of it
https://bugs.kde.org/show_bug.cgi?id=376689 Bug ID: 376689 Summary: Preview tooltip disappears making it impossible to select a file inside of it Product: plasmashell Version: 5.8.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: ma...@free.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Hi ! I'm using Neon LTS and using a desktop in folder view mode. When clicking on the top left corner of a directory to make the "floating preview" tooltip appear, I noticed that I cannot actually select a file inside of it as it disappears as soon as my mouse moves away from its position. I guess it's not the meant behaviour. I'm reporting it as it affects the LTS version of Plasma (using Neon LTS here). Thanks a lot to everyone, cheers ! -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 376639] Cannot copy from gdrive:// to gdrive://
https://bugs.kde.org/show_bug.cgi?id=376639 --- Comment #1 from Elvis Angelaccio --- gdb says the slave gets stuck in the while loop inside ConnectionBackend::waitForIncomingTask(), apparently. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 376688] New: Dolphin tooltips : cannot add comments / tags
https://bugs.kde.org/show_bug.cgi?id=376688 Bug ID: 376688 Summary: Dolphin tooltips : cannot add comments / tags Product: dolphin Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: tooltip Assignee: dolphin-bugs-n...@kde.org Reporter: ma...@free.fr Target Milestone: --- Hi ! When enabling tooltips in Dolphin, and when moving the mouse is hovering a given file, a tooltip is being displayed. In the tooltip, a couple of details are displayed. Also it's supposedly possible to add a tag or a comment as one can see links in front of the Tags : and Comment : fields (add a tag / add a comment). However it's impossible to click on those links as the tooltip disappears immediately when the mouse in moved into the tooltip. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376687] New: GPS tagging usability of bookmarks
https://bugs.kde.org/show_bug.cgi?id=376687 Bug ID: 376687 Summary: GPS tagging usability of bookmarks Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- I'm a little confused how to use the bookmarks feature in the Geotagging editor. - You can create bookmarks in the map (using the context menu) and display them. But: - Bookmarks created on the map are gone when you restart Digikam. (Is this because of the Appimage concept which uses a temp mount?) - Bookmarks created on the map cannot be used to assign a location to the images below. The lists seem to be completely separate. What is the usage concept here? Or is this actually buggy? Thank you :) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 368907] kaffeine sometimes uses 100% CPU
https://bugs.kde.org/show_bug.cgi?id=368907 --- Comment #21 from José JORGE --- (In reply to Mauro Carvalho Chehab from comment #18) > Bug #371579 was fixed upstream. Could you please test if this solved the > issue for you? Issue not solved as of today's GIT. I could get one time kaffeine to only use ~25% CPU after lots of play/stop on DVB. But 99% of the time, CPU is at 125% (dual-core system) when playing, and at 100% when playback is stopped. Any hint on how to dump tasks load welcome... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376686] New: Wastebin plasma widget opens with Opera
https://bugs.kde.org/show_bug.cgi?id=376686 Bug ID: 376686 Summary: Wastebin plasma widget opens with Opera Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages URL: https://forum.kde.org/viewtopic.php?f=289&t=139015&p=3 72330#p372330 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: swipe...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 I've just noticed this problem on my freshly built arch laptop running plasma 5.9.2. I installed opera and then dolphin and when I open the plasma wastebin widget it launches opera. I have tried creating a new user and the problem is replicated so the error must be global. I tried removing Opera and clicking open on the wastebin widget and this message is now present in journalctl: kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop Unable to detect a web browser to launch 'trash:/' -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367899] Please consider sanitizing middle-click-pasted text control characters for security reasons
https://bugs.kde.org/show_bug.cgi?id=367899 --- Comment #4 from Sami Liedes --- You mean that instead of silently dropping control characters, Konsole would open a popup window showing the entire pasted text with control characters visible and ask if you want to paste it? I guess that would kind of solve the security problem, though I note that the text being pasted may be quite long for a popup (I don't know what the maximum size is, but I think at least hundreds of thousands of bytes is possible), and the malicious part could be hidden in the middle. Do you think someone relies on being able to paste control characters? I guess it's entirely possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376643] Can't run web address when translation is used
https://bugs.kde.org/show_bug.cgi?id=376643 --- Comment #2 from Alex --- E.g. type at search field google.com and press enter -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 --- Comment #27 from Elvis Angelaccio --- @Sebastian: tried your steps and everything works as expected here. What's your version of KIO? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 376209] Command options --edit-new-* do not work
https://bugs.kde.org/show_bug.cgi?id=376209 David Jarvie changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||KDE Applications 16.12.3 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kal ||arm/7143b74632e48cd77c1b15a ||41b95d7fc9b798bd6 --- Comment #1 from David Jarvie --- The dialogue was being deleted before it was displayed, due to use of AutoQPointer to hold its pointer. Fixed in version 2.11.14 (KDE Applications 16.12.3). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #42 from Martin Klapetek --- I suggest you submit your patch to Qt then and let the actual Qt developers comment on that. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376685] crashes when searching
https://bugs.kde.org/show_bug.cgi?id=376685 John White changed: What|Removed |Added CC||j...@lawquest.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376685] New: crashes when searching
https://bugs.kde.org/show_bug.cgi?id=376685 Bug ID: 376685 Summary: crashes when searching Product: kmail2 Version: 4.14.1 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: j...@lawquest.com Target Milestone: --- Created attachment 104118 --> https://bugs.kde.org/attachment.cgi?id=104118&action=edit backtrace (2 files) crashes when searching for name in search bar- find messages does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #41 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0...@gmail.com> --- (In reply to Martin Klapetek from comment #40) > (In reply to Jan Ziak (http://atom-symbol.net) from comment #38) > > (In reply to Martin Klapetek from comment #1) > > > This is available in the "Formats" system settings module. Due to the > > > nature > > > of the underlying technology, we cannot offer anything better at this > > > point. > > > > What does "nature of the underlying technology" mean exactly? > > As explained in my comments above, we have switched > from what you presumably link in your screenshots to > Qt's solution, which was set to contain all the features > you want, but so far it doesn't. > > Also as noted above, KDE is fully aware of this issue > and we are fully aware what the options were before, > you don't need to link them to us, really. At this point > it's a resources problem, projects are understaffed and > more pressing issues are being worked on. > > Finally, the solution is NOT easy. This WILL have to > go into Qt itself and that means support for all the > platforms Qt supports, which is incredibly complicated > and also partly the reason why it's not done yet. > > That said, no need to comment on this further, we know > about this issue and there's nothing that we're able do > about this for now, sorry. Simply adding the same comments > over and over won't magically solve it. I don't understand your reply. In either case, I don't see it as an issue anymore: I patched the underlying Qt code (qlocale.cpp, Gentoo) on my machines. The patch simply modifies QLocale::dateFormat(FormatType)→QString and returns the format string I prefer to use (such as "-MMM-dd"). I guess I could have also used LD_PRELOAD to modify the behavior of function QLocale::dateFormat(FormatType), but that wouldn't cover the case of compiler inlining the function (within qlocale.cpp, or in case of -flto). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376684] New: Screen brightness can not be changed after external monitor was connected
https://bugs.kde.org/show_bug.cgi?id=376684 Bug ID: 376684 Summary: Screen brightness can not be changed after external monitor was connected Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: matthias.wi...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 Hello, on my laptop (Thinkpad X240) the screen brightness can be changed by Fn+F and via the battery context menu when the battery icon in the task bar is selected. Both ways work fine. Actual Results: When an external monitor has been connected (primary monitor) and disconnected again, the screen brightness can not be changed anymore. After a reboot everything works again. The screen brightness can still be changed when changing the values in /sys/class/backlight/intel_backlight/brightness but not via Fn+F or via battery context menu. So it seems that for some reason, the /sys/class/.../brightness is not changed anymore once an external monitor was connected and disconnected again. Expected Result: After disconnecting the external monitor the screen brightness should be changeable. Output of journalctl does not give obvious errors just messages like this: kscreen.xcb.helper: RRNotify_OutputProperty (ignored) kscreen.xcb.helper: Output: 67 kscreen.xcb.helper: Property: Backlight kscreen.xcb.helper: State (newValue, Deleted): 0 Above messages appear in both cases: screen brightness is changeable or is not changeable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 373764] `KColorScheme::adjustBackground` and other methods ignore effects of `KColorSchemeManager::activateScheme`
https://bugs.kde.org/show_bug.cgi?id=373764
Francis Herne changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kco
||nfigwidgets/a3355b22954b61f
||7e9b9077d9663ffc592b9eb4b
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Francis Herne ---
Git commit a3355b22954b61f7e9b9077d9663ffc592b9eb4b by Francis Herne.
Committed on 19/02/2017 at 20:01.
Pushed by flherne into branch 'master'.
KColorScheme: default to application scheme if set by KColorSchemeManager
KColorSchemeManager::activateScheme() sets a custom path for the
application's color scheme, with
`qApp->setProperty("KDE_COLOR_SCHEME_PATH", index.data(Qt::UserRole));`
Currently, the KColorScheme() and KStatefulBrush() constructors will
ignore this and use only the system color scheme, unless an
application-specific config is explicitly loaded and passed in by the
caller.
This is problematic, because most callers assume that the default is to
match the *application* scheme - usually this is equivalent, but it
differs when KColorSchemeManager is used.
For example, when the application of a KTextEditor widget or
KonsolePart has an opposite color scheme to the system, the Find bars
are unreadable.
This patch makes KColorScheme() match the application scheme by default
when this differs from the system scheme, which seems preferable to
adding the same code in hundreds of callers.
Differential Revision: https://phabricator.kde.org/D4637
M +10 -3src/kcolorscheme.cpp
M +16 -14 src/kcolorscheme.h
https://commits.kde.org/kconfigwidgets/a3355b22954b61f7e9b9077d9663ffc592b9eb4b
--
You are receiving this mail because:
You are watching all bug changes.
[BalooWidgets] [Bug 334615] Support for nested tags
https://bugs.kde.org/show_bug.cgi?id=334615 Jamie Smith changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/bal ||oo-widgets/0a2c8177439770f5 ||a69826abebda1a53d26078a5 --- Comment #4 from Jamie Smith --- Git commit 0a2c8177439770f5a69826abebda1a53d26078a5 by James D. Smith. Committed on 19/02/2017 at 20:09. Pushed by smithjd into branch 'master'. Implement nested tags. GUI: REVIEW:128665 M +94 -71 src/kedittagsdialog.cpp M +8-8src/kedittagsdialog_p.h M +2-1src/tagcheckbox.cpp https://commits.kde.org/baloo-widgets/0a2c8177439770f5a69826abebda1a53d26078a5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376683] New: System suspends from time to time when works with laptop lid closed and external display connected
https://bugs.kde.org/show_bug.cgi?id=376683 Bug ID: 376683 Summary: System suspends from time to time when works with laptop lid closed and external display connected Product: plasmashell Version: 5.8.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dmitry.s.lisov...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.5) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-38-generic x86_64 Distribution: Ubuntu 16.10 Hardware: MacBookPro11,5 when I work on my laptop with closed lid and System suspends from time to time when works with laptop lid closed and external display connected, it goes to sleep every 5-20 minutes (have not determined the exact intervals). My system configured to suspend on lid closed event even when external monitor is connected. But why it suspends on itself once it's awake and there is no lid closed events (lid is just permanently closed). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 367899] Please consider sanitizing middle-click-pasted text control characters for security reasons
https://bugs.kde.org/show_bug.cgi?id=367899 Jiri Palecek changed: What|Removed |Added CC||jpale...@web.de --- Comment #3 from Jiri Palecek --- Maybe showing the text being pasted with a warning would suffice. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376682] the cursor keeps disappearing
https://bugs.kde.org/show_bug.cgi?id=376682 akuk changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376682] New: the cursor keeps disappearing
https://bugs.kde.org/show_bug.cgi?id=376682 Bug ID: 376682 Summary: the cursor keeps disappearing Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: sandyponce...@hotmail.com Target Milestone: --- I just installed the new version of krita and the moment I opened the program, it started to glitch near the canvas. Every time I try to sketch on the canvas, the cursor is not visible until I press the toolbar. I can draw on the canvas but I will not see the paint nor the brush. I already turned off the opengl and it still does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376677] Mouse right-click ignored on apps icons
https://bugs.kde.org/show_bug.cgi?id=376677 --- Comment #4 from dav...@protonmail.com --- OK, I found the right way to restart plasmashell (kquitapp5 plasmashell && kstart5 plasmashell) There is an error, indeed When I right-click the icon I get file:///crypto/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ContextMenu.qml:501: TypeError: Cannot read property 'LauncherUrlWithoutIcon' of undefined file:///crypto/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ContextMenu.qml:64: TypeError: Cannot read property 'LauncherUrlWithoutIcon' of undefined After that, hovering over the icons give me [google-chrome] QXcbConnection: XCB error: 2 (BadValue), sequence: 9880, resource id: 119537670, major code: 142 (Unknown), minor code: 3 QXcbConnection: XCB error: 2 (BadValue), sequence: 9881, resource id: 119537670, major code: 142 (Unknown), minor code: 3 [konsole] QXcbConnection: XCB error: 2 (BadValue), sequence: 10276, resource id: 113246209, major code: 142 (Unknown), minor code: 3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 350647] The cursor disappears when I move it off the canvas, and won't come back until I tap anything not on the canvas
https://bugs.kde.org/show_bug.cgi?id=350647 akuk changed: What|Removed |Added CC||sandyponce...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 Mateusz changed: What|Removed |Added Resolution|FIXED |INVALID -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 Mateusz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345378] No option in Digital Clock to use 24 hour format
https://bugs.kde.org/show_bug.cgi?id=345378 --- Comment #40 from Martin Klapetek --- (In reply to Jan Ziak (http://atom-symbol.net) from comment #38) > (In reply to Martin Klapetek from comment #1) > > This is available in the "Formats" system settings module. Due to the nature > > of the underlying technology, we cannot offer anything better at this point. > > What does "nature of the underlying technology" mean exactly? As explained in my comments above, we have switched from what you presumably link in your screenshots to Qt's solution, which was set to contain all the features you want, but so far it doesn't. Also as noted above, KDE is fully aware of this issue and we are fully aware what the options were before, you don't need to link them to us, really. At this point it's a resources problem, projects are understaffed and more pressing issues are being worked on. Finally, the solution is NOT easy. This WILL have to go into Qt itself and that means support for all the platforms Qt supports, which is incredibly complicated and also partly the reason why it's not done yet. That said, no need to comment on this further, we know about this issue and there's nothing that we're able do about this for now, sorry. Simply adding the same comments over and over won't magically solve it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376647] Rendering very slow
https://bugs.kde.org/show_bug.cgi?id=376647 --- Comment #3 from Wegwerf --- Check out website. See phabricator.kde.org, identity.kde.org. Ask on G+ if you need help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376668] Plasma shell crashes on startup
https://bugs.kde.org/show_bug.cgi?id=376668 Ivan Čukić changed: What|Removed |Added Component|Activity Switcher |generic-crash Assignee|ivan.cu...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373199] Crash when using frei0r emboss effect
https://bugs.kde.org/show_bug.cgi?id=373199 rpiggott changed: What|Removed |Added CC||ron.piggott@actsministries. ||org --- Comment #6 from rpiggott --- I am also having this issue. I have tried all PPA's from Kdenlive to resolve without success. ( kdenlive-stable , kdenlive-testing , kdenlive-master ) Is there a new release of 'frei0r'? Or if you remain unable to reproduce this on your computer what set of installation instructions should? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376681] Region Coordinates Are Sometimes inf / Large Numbers
https://bugs.kde.org/show_bug.cgi?id=376681 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Preview |Faces-Management -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364039] Dolphin crashed on file transfer
https://bugs.kde.org/show_bug.cgi?id=364039 --- Comment #26 from Sebastian Ernst --- I found a "clean" and reliable way to reproduce this bug on my machine (openSUSE Leap 42.2, Dolphin 16.08.2). It's based on my experience with moving files to a FAT partition as described in duplicate bug 376634. As a normal user, create a test setup as follows: dd if=/dev/zero of=fs.bin bs=1M count=1024 mkdir mnt sudo losetup /dev/loop1 fs.bin sudo mkfs.vfat /dev/loop1 sudo mount -o users,gid=users,umask=0002,utf8=true /dev/loop1 mnt wget https://www.python.org/ftp/python/3.6.0/Python-3.6.0.tar.xz tar xpf Python-3.6.0.tar.xz Now, open dolphin, activate split view. On the left hand side, open "mnt", on the right hand side open "Python-3.6.0". Select everything in "Python-3.6.0" and drag it into "mnt". Dolphin will throw a number of error messages as described and eventually segfault. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365822] On Wayland, the search field does not receive keyboard focus
https://bugs.kde.org/show_bug.cgi?id=365822 dev...@t-online.de changed: What|Removed |Added CC||dev...@t-online.de --- Comment #2 from dev...@t-online.de --- Can confirm too, Plasma v5.9.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376647] Rendering very slow
https://bugs.kde.org/show_bug.cgi?id=376647 --- Comment #2 from callicu...@gmail.com --- Sure, I'd be happy to use these resources if they are appropriate. I am new to KDENLIVE and didn't know this was how we were supposed to submit these requests. Can you share links to the resources that you mentioned please? Thank you On Feb 19, 2017 11:00 AM, "Wegwerf" wrote: https://bugs.kde.org/show_bug.cgi?id=376647 Wegwerf changed: What|Removed |Added Resolution|--- |INVALID CC||wegwerf-1-...@gmx.de Status|UNCONFIRMED |RESOLVED --- Comment #1 from Wegwerf --- Please use the forum or our G+ community for help. Use of this bug tracker is for bug tracking only. Don't misuse the bug tracker for user support and help. Thank you very much for your cooperation. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376681] Region Coordinates Are Sometimes inf / Large Numbers
https://bugs.kde.org/show_bug.cgi?id=376681 --- Comment #2 from hardy.pub...@gmail.com --- If I clear the faces and try again, everything is normal. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376630] Bold font rendering is broken after changing font via kcm_fonts
https://bugs.kde.org/show_bug.cgi?id=376630 --- Comment #2 from Pulfer --- Related bug: https://bugs.kde.org/show_bug.cgi?id=348066 Maybe it makes sense to drop only some style names from QFont save string. Like Regular, Bold and Italic. Just because they are already covered by numeric values. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 376655] Operations on Modulus operator were causing other operators to be erroneous
https://bugs.kde.org/show_bug.cgi?id=376655 Evan Teran changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Evan Teran --- Ah, this is an understandable misunderstanding :-). In kcalc, % is the "percent" operator, not mod! If you want the actual modulus operator, please use the "Mod" button found in both Scientific and Statistic mode (top row, just left of center). For more information on the "percent" operator, please see the manual: https://docs.kde.org/trunk5/en/kdeutils/kcalc/percent.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348066] Font style reverts from medium to regular
https://bugs.kde.org/show_bug.cgi?id=348066 Pulfer changed: What|Removed |Added CC||pul...@list.ru --- Comment #2 from Pulfer --- Likely it's fixed in Qt 5.8.0: https://github.com/qt/qtbase/commit/5dd907bf639f43be7f2cdfdd44ec3795f1b31bf6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376681] Region Coordinates Are Sometimes inf / Large Numbers
https://bugs.kde.org/show_bug.cgi?id=376681 hardy.pub...@gmail.com changed: What|Removed |Added Attachment #104115|Screenshot |After Box 1 is drawn description|| -- You are receiving this mail because: You are watching all bug changes.
