[frameworks-kconfig] [Bug 409886] New: K3b burning tools not burn any CD / DVD. It shown blank after burn
https://bugs.kde.org/show_bug.cgi?id=409886 Bug ID: 409886 Summary: K3b burning tools not burn any CD / DVD. It shown blank after burn Product: frameworks-kconfig Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: voicebreak...@yahoo.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION K3b burning tools not burn any CD / DVD. It shown blank after burn -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409753] Duplicate column name 'version' QMYSQL
https://bugs.kde.org/show_bug.cgi?id=409753 wraeth changed: What|Removed |Added CC||wraeth+kdeb...@wraeth.id.au --- Comment #2 from wraeth --- (In reply to Antonio Rojas from comment #1) > According to downstream reports, this is a regression from > 74aed9542ba1ff1e6e93a550c42869647c4eba8e I encountered the same issue with the same version of akonadi on Gentoo, and reverting that specific commit resolved it for me. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 409880] Kstars 3.3.2 crashes viewing histogram
https://bugs.kde.org/show_bug.cgi?id=409880 --- Comment #1 from Jasem Mutlaq --- Can you check this behavior occurs in the KStars nightly packages for Ubuntu? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409753] Duplicate column name 'version' QMYSQL
https://bugs.kde.org/show_bug.cgi?id=409753 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406428] Video preview - no sound
https://bugs.kde.org/show_bug.cgi?id=406428 --- Comment #29 from caulier.gil...@gmail.com --- Andrej, I switch back QtAv to 1.12.0 branch as for DK 6.1.0. AppImage 64 bits have been rebuild and uploaded to https://files.kde.org/digikam/ Problem remain on your computer ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409884] digikam Crash
https://bugs.kde.org/show_bug.cgi?id=409884 --- Comment #2 from Maik Qualmann --- My openSUSE Tumbleweed is up to date. For testing, I have the digiKam-6.1.0 packages provided by openSUSE installed. I can not find a problem with either SQLite or MySQL. I assume you have activated extra repositories and have now mixed packages. That would be the typical behavior when the main repository changes drastically. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 409867] KTimeComboBox may not allow valid time entry, depending on format (timeFormatToInputMask() too fragile)
https://bugs.kde.org/show_bug.cgi?id=409867 --- Comment #2 from Filipus Klutiero --- This exceeds this ticket's scope, but there is another big problem with timeFormatToInputMask(): in 12-hour systems (such as en_US, using format "11:59 PM"), it does not require the AM or PM characters, since the special characters used in the mask are lowercase "a"-s. This allows users of such formats to enter incomplete times such as "10:00", which will be quietly "saved" as midnight. The special character for a mandatory letter is an *uppercase* "A". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #6 from Filipus Klutiero --- FOR PEOPLE EXPERIENCING THIS: THIS NOTIFICATION ONLY MEANS KDE TOOK MORE THAN 15 SECONDS TO COMPUTE THE FREE SPACE ON A FILESYSTEM. This may indicate an issue (though maybe not necessarily). I saw such a notification on my previous session start. I did not get it at the start of my current session. I am not saying this is a bug, as the taskbar took a lot of time to appear in my previous session, so something was wrong. Unfortunately, the only thing unusual I see in my logs is the following from syslog: Jul 16 23:44:14 vinci at-spi-bus-launcher[1581]: dbus-daemon[1913]: Failed to activate service 'org.a11y.atspi.Registry': timed out (service_start_timeout=12ms) I imagine the notification signals a problem, but I do not know if it's a software or hardware issue. This PC has been rather unstable for several months, but I don't know if that is due to Debian/KDE/Kubuntu or due to a hardware issue. Kubuntu 19.04 uses Plasma 5.15 and KDE Frameworks 5.56.0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409842] Selecting color in Zoom Selector is laggy
https://bugs.kde.org/show_bug.cgi?id=409842 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 409606] Track memory allocated with mmap
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #2 from tbl...@icloud.com --- LD_PRELOAD would work at least in my case, since I call mmap through the C library. For times when this doesn't work, intercepting mmap with ptrace is possible, and not all that hard. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405024] The application crashes when entering next scheduled transaction
https://bugs.kde.org/show_bug.cgi?id=405024 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407566] Dolphin crashes when opening a folder or a file
https://bugs.kde.org/show_bug.cgi?id=407566 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 409406] KMyMoney Crash
https://bugs.kde.org/show_bug.cgi?id=409406 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408812] Kwin crashes after system suspend
https://bugs.kde.org/show_bug.cgi?id=408812 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408831] My lines are not respect and the pressure doesn't work.
https://bugs.kde.org/show_bug.cgi?id=408831 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391981] home page payments section show more/fewer schedules causes jump to top of page with ENABLE_WEBENGINE set to ON
https://bugs.kde.org/show_bug.cgi?id=391981 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409420] MP3 Audio files don't work on mac
https://bugs.kde.org/show_bug.cgi?id=409420 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 409885] New: Request for icon: timezone and set time automatically
https://bugs.kde.org/show_bug.cgi?id=409885 Bug ID: 409885 Summary: Request for icon: timezone and set time automatically Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: bhus...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 121572 --> https://bugs.kde.org/attachment.cgi?id=121572&action=edit Screenshot of mobile time settings SUMMARY To be used in Plasma Mobile time settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 amee...@amitlele.com changed: What|Removed |Added Version|unspecified |5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 --- Comment #15 from petrk --- "Skip antialiasing for range" 0-99 toggles itself. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409518] Visiting Fonts KCM changes antialliasing settings without warning
https://bugs.kde.org/show_bug.cgi?id=409518 petrk changed: What|Removed |Added CC||pepk...@gmail.com --- Comment #14 from petrk --- I'm affected unfortunately. Happens when switching to and from "font management". There's also some other trigger because I had to look at awful kana when I opened Audacious this morning. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401861] Menu search doesn't return any results if cursor happens to be positioned below the tab bar
https://bugs.kde.org/show_bug.cgi?id=401861 g...@protonmail.com changed: What|Removed |Added CC|g...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409884] digikam Crash
https://bugs.kde.org/show_bug.cgi?id=409884 Maik Qualmann changed: What|Removed |Added Component|general |Database -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409175] crash in QSqlDatabase
https://bugs.kde.org/show_bug.cgi?id=409175 --- Comment #5 from Maik Qualmann --- *** Bug 409884 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409884] digikam Crash
https://bugs.kde.org/show_bug.cgi?id=409884 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 409175 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409884] New: digikam Crash
https://bugs.kde.org/show_bug.cgi?id=409884 Bug ID: 409884 Summary: digikam Crash Product: digikam Version: 6.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: pauli.h...@yahoo.com Target Milestone: --- Application: digikam (6.1.0) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.16-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: After today's zypper dup (more than 6000 packages) update, digikam doesn't work anymore The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc2b3ec5cc0 (LWP 2954))] Thread 22 (Thread 0x7fc2777fe700 (LWP 2992)): #0 0x7fc2c50ef16c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc2bd79a836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc2bd79b203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc2bd79b381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc2bd753641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc2bd7564dd in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc2bd756bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc2bd79d675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc2c50e8faa in start_thread () from /lib64/libpthread.so.0 #9 0x7fc2c8c7373f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fc277fff700 (LWP 2991)): #0 0x7fc2c50ef16c in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc2bd79a836 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc2bd79b203 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc2bd79b381 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc2bd753641 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc2bd75682b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc2bd756bd4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc2bd79d675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc2c50e8faa in start_thread () from /lib64/libpthread.so.0 #9 0x7fc2c8c7373f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fc280db5700 (LWP 2990)): #0 0x7fc2c8c648af in write () from /lib64/libc.so.6 #1 0x7fc2c8bf6565 in _IO_file_write@@GLIBC_2.2.5 () from /lib64/libc.so.6 #2 0x7fc2c8bf58f6 in new_do_write () from /lib64/libc.so.6 #3 0x7fc2c8bf6c6e in __GI__IO_file_xsputn () from /lib64/libc.so.6 #4 0x7fc2c8be3259 in buffered_vfprintf () from /lib64/libc.so.6 #5 0x7fc2c8be0384 in __vfprintf_internal () from /lib64/libc.so.6 #6 0x7fc2c8c8264f in __fprintf_chk () from /lib64/libc.so.6 #7 0x7fc2b5a11d2e in event_logv_ () from /usr/lib64/libevent-2.1.so.6 #8 0x7fc2b5a147c5 in event_warn () from /usr/lib64/libevent-2.1.so.6 #9 0x7fc2b5a16328 in ?? () from /usr/lib64/libevent-2.1.so.6 #10 0x7fc2b5a26b05 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #11 0x7fc2bd7a14c8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7fc2bd72d7a7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #13 0x7fc2bd75c7f4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #14 0x7fc2bd764978 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #15 0x7fc2bd79d675 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #16 0x7fc2c50e8faa in start_thread () from /lib64/libpthread.so.0 #17 0x7fc2c8c7373f in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fc288864700 (LWP 2972)): [KCrash Handler] #6 0x7fc2c6482a57 in std::__atomic_base::compare_exchange_strong (__m2=std::memory_order_acquire, __m1=std::memory_order_acquire, __p2=0x2, __p1=: , this=0x8) at /usr/include/c++/9/bits/atomic_base.h:769 #7 std::atomic::compare_exchange_strong (__m2=std::memory_order_acquire, __m1=std::memory_order_acquire, __p2=0x2, __p1=: , this=0x8) at /usr/include/c++/9/atomic:565 #8 QAtomicOps::testAndSetAcquire (currentValue=, newValue=0x2, expectedValue=0x0, _q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:290 #9 QBasicAtomicPointer::testAndSetAcquire (currentValue=: , newValue=0x2, expectedValue=0x0, this=0x8) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:263 #10 QReadWriteLock::tryLockForWrite (this=0x8, timeout=-1) at thread/qreadwritelock.cpp:339 #11 0x7fc2c76f3269 in QWriteLocker::relock (this=) at ../../include/QtCore/../../src/corelib/thread/qreadwritelock.h:170 #12 QWriteLocker::QWriteLocker (areadWriteLock=0x8, this=) at ../../include/QtCore/../../src/corelib/thread/qreadwritelock.h:170 #13 QSqlDatabasePrivate::rem
[KEXI] [Bug 409883] New: Could not read database property "kexidb_major_ver". Error opening database cursor.
https://bugs.kde.org/show_bug.cgi?id=409883 Bug ID: 409883 Summary: Could not read database property "kexidb_major_ver". Error opening database cursor. Product: KEXI Version: 3.2.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kexi-b...@kde.org Reporter: edcalde...@gmail.com CC: a...@piggz.co.uk, in...@fables.co.za Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open DB from 3.1.0 add new lines to DB 2. When save it failed. Required to close the program 3. Open the program and try to open the file again OBSERVED RESULT Kexi keeps on error with this message: Could not read database property "kexidb_major_ver". Error opening database cursor. EXPECTED RESULT Open the file again. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 409163] Can't install from flatpack
https://bugs.kde.org/show_bug.cgi?id=409163 edcalde...@gmail.com changed: What|Removed |Added CC||edcalde...@gmail.com --- Comment #1 from edcalde...@gmail.com --- I found how to install it on Fedora: You have to use this address http://distribute.kde.org/kdeapps.flatpakrepo instead of http://distribute.kde.org/flatpak-apps-testing. Flatpack requiered a ".flatpakrepo" file. This needs to be changed on the web page instructions. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 152669] wish: horizontal scrolling with alt+wheelmouse / touchpad
https://bugs.kde.org/show_bug.cgi?id=152669 michael changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from michael --- works in kf5/qt5. kdiff3 1.8.1 tested -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 Nate Graham changed: What|Removed |Added Product|Active Window Control |frameworks-kinit Keywords||usability Component|General |general Flags|Usability+ |Usability- CC||kdelibs-b...@kde.org, ||n...@kde.org Assignee|zrenf...@gmail.com |fa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 amee...@amitlele.com changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 --- Comment #2 from amee...@amitlele.com --- the script is executable, the action of closing the window completes but there is the error described earlier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 409882] New: Glyphs injected via fontconfig alias are not displayed
https://bugs.kde.org/show_bug.cgi?id=409882 Bug ID: 409882 Summary: Glyphs injected via fontconfig alias are not displayed Product: frameworks-ktextwidgets Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 121571 --> https://bugs.kde.org/attachment.cgi?id=121571&action=edit terminals and kate I want to display text that uses some glyphs from other fonts, that are referred to via FontConfig aliases. The main use case is Powerline with Konsole. This does not work for some weeks. It works neither in Konsole nor in Kate (see the attached screenshot). Fontconfig setup did not change and the substitution works in gnome-terminal and QTextEditor Not sure if the bug is submitted to the proper component. STEPS TO REPRODUCE 1. Install FontAwesome and create a Fontconfig alias from your terminal font to FontAwesome. 2. "echo '\uf240'" should output the battery symbol. OBSERVED RESULT No battery symbol. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: git master KDE Frameworks Version: git master Qt Version: 5.12.4 ADDITIONAL INFORMATION Screenshot with gnome-terminal (top), Konsole (middle), and Kate is attached. The Gnome terminal renders text correctly, Konsole fails, and the promt, copied to Kate, is shown incorrectly too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 409867] KTimeComboBox may not allow valid time entry, depending on format (timeFormatToInputMask() too fragile)
https://bugs.kde.org/show_bug.cgi?id=409867
--- Comment #1 from Filipus Klutiero ---
Created attachment 121570
--> https://bugs.kde.org/attachment.cgi?id=121570&action=edit
Screenshot of KOrganizer dialog with 2 affected fields
In this example, which shows a KOrganizer dialog in French Canadian, I
demonstrated the bug by entering invalid times with a digit (above) and a
letter (below) in a position supposed to contain a literal ("h").
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 409881] Display a notification when indexing first begins
https://bugs.kde.org/show_bug.cgi?id=409881 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409876] Dolphin does not display extended file properties for new files
https://bugs.kde.org/show_bug.cgi?id=409876 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- The indexer is what's responsible for showing this information. Until the files are indexed, they won't show it. We can try our best to make it faster, or maybe show a notification on first boot that indexing is happening and that some performance and features might be impacted until it's done (they do this on macOS). But in the end you're just gonna have to wait until indexing is done. To track a notification that tells you this information, I've filed Bug 409881. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409881] New: Display a notification when indexing first begins
https://bugs.kde.org/show_bug.cgi?id=409881 Bug ID: 409881 Summary: Display a notification when indexing first begins Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: n...@kde.org Target Milestone: --- When a machine is first booted and indexing begins, performance may be reduced, and files won't display complete metadata until it's done. However this is not obvious to the user. On macOS, a persistent notification is shown to communicate this information, after years and years of users complaining about it. We might want to consider doing the same, and when indexing is started for the very first time, display a persistent notification informing the user that until indexing is done, performance may be impacted and extended file metadata won't be available. This notification could even have a button to pause the indexing (to accommodate users with immediate performance needs) and a button to open the KCM for configuring the indexing behavior. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #34 from awf_ul --- Sent upstream to io...@lists.linux-foundation.org on advice of Christoph Hellwig. Will update this bug. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #33 from awf_ul --- Below is the result of the second bisect (see bisect log in attachment "Second bisect; failure repeatable and solid") 55897af63091ebc2c3f239c6af748113ac50 is the first bad commit commit 55897af63091ebc2c3f239c6af748113ac50 Author: Christoph Hellwig Date: Mon Dec 3 11:43:54 2018 +0100 dma-direct: merge swiotlb_dma_ops into the dma_direct code While the dma-direct code is (relatively) clean and simple we actually have to use the swiotlb ops for the mapping on many architectures due to devices with addressing limits. Instead of keeping two implementations around this commit allows the dma-direct implementation to call the swiotlb bounce buffering functions and thus share the guts of the mapping implementation. This also simplified the dma-mapping setup on a few architectures where we don't have to differenciate which implementation to use. Signed-off-by: Christoph Hellwig Acked-by: Jesper Dangaard Brouer Tested-by: Jesper Dangaard Brouer Tested-by: Tony Luck :04 04 e9b0807231777e3da732cb3f744a8867f3128f90 95962d177078f04ae1bd66f560c87a9eed9d0f0e M arch :04 04 e7a90740563e49061bb6baf6413e9de37a919820 b537630e5cf02def1bcfac744cd06da0f8201ff8 M include :04 04 4698daf585ffbc830cfda58e8a2e8390f66b4cf9 a942b6a22ca5f49aaef13490a03e4589766fd497 M kernel -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 273450] Reminders should be preselected when they pop up
https://bugs.kde.org/show_bug.cgi?id=273450 Filipus Klutiero changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- I am almost sure I recently observed the same issue. However, I just had a reminder popup, and it was already selected, so unless this is an intermittent bug, it seems this issue is solved. I do not remember having this frustration recently - that is probably an indication that the issue was solved when I upgraded from Debian 9 to Kubuntu 19.04, which uses KOrganizer 5.10.3. I am assuming this was solved and marking this as resolved. If you re-open this ticket, please indicate an affected version. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #32 from awf_ul --- Created attachment 121569 --> https://bugs.kde.org/attachment.cgi?id=121569&action=edit lspci from kernel v5.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 402798] Add data units (bits, bytes, kilobits, kibibytes, etc)
https://bugs.kde.org/show_bug.cgi?id=402798
Nate Graham changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kun
||itconversion/6c193856f9f472
||f350ba7634eb2c1bdcd89bb2ea
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Version Fixed In||5.61
--- Comment #6 from Nate Graham ---
Git commit 6c193856f9f472f350ba7634eb2c1bdcd89bb2ea by Nate Graham, on behalf
of Jonathan Rubenstein.
Committed on 17/07/2019 at 02:03.
Pushed by ngraham into branch 'master'.
Add Binary Data units (bits, kilobytes, kibibytes ... yottabytes)
Summary:
New data category BinaryDataCategory featuring bits and bytes, both SI units
and powers of two, from normal bits all the way up to Yibibytes.
This only features ( positive SI prefix | IEC power of two prefix ) + ( bits |
bytes ), and does not include units like nibbles (half a byte), octets
(alternative form of byte), or prefixes that are less than 1. My reasoning
behind this is to keep it clean and uncluttered.
FIXED-IN: 5.61
{F6743030} {F6743029}
Test Plan:
Open KRunner and attempt to use new units.
New units show up successfully.
Reviewers: broulik, #plasma, ngraham
Reviewed By: ngraham
Subscribers: abetts, cfeck, apol, aacid, ngraham, kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D20181
M +1-0README.md
M +1-0src/CMakeLists.txt
A +365 -0src/binary_data.cpp [License: LGPL (v2+)]
A +36 -0src/binary_data_p.h [License: LGPL (v2+)]
M +2-0src/converter.cpp
M +73 -2src/unit.h
https://commits.kde.org/kunitconversion/6c193856f9f472f350ba7634eb2c1bdcd89bb2ea
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 409847] Enhancement: Accessibility - Add optional On-Demand two-finger scrolling for touchpads
https://bugs.kde.org/show_bug.cgi?id=409847 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from Nate Graham --- Okay, so you're using the Synaptics driver. I have bad news for you: The issue of unintentional two-finger scrolling is unfortunately irresolvable with that driver. :( I spent months and months researching it and applying patches and came to the conclusion that it was a lost cause. So did the developers of the Synaptics driver, in fact, because they created a new driver called Libinput that, among other things, was specifically designed to address this issue. I've been following its development closely and I'm happy to report that for me at least, it's finally fixed with this patchset: https://gitlab.freedesktop.org/libinput/libinput/merge_requests/247 Neither the Synaptics nor Libinput drivers readily support your request, so I'm afraid your only option is to give Libinput a whirl and file bugs if it doesn't behave how you want. The developer Peter Hutterer is quite pleasant and responsive. -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 379026] reminder shows dialog for past events
https://bugs.kde.org/show_bug.cgi?id=379026 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #1 from Filipus Klutiero --- Thanks for reporting Martin, Has your reminders popped up "yesterday", so that you got duplicate reminders? Or has they failed to popup yesterday? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 408004] No display: ATSC tuner appears to work, but "mjpeg demux error: cannot peek"
https://bugs.kde.org/show_bug.cgi?id=408004 --- Comment #31 from awf_ul --- Created attachment 121568 --> https://bugs.kde.org/attachment.cgi?id=121568&action=edit dmesg from kernel v5.2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 344679] All event reminders fail to trigger alerts/popups/notifications
https://bugs.kde.org/show_bug.cgi?id=344679 Filipus Klutiero changed: What|Removed |Added CC||luis.de.so...@protonmail.ch --- Comment #12 from Filipus Klutiero --- *** Bug 360934 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 360934] Korganiser does not show reminders
https://bugs.kde.org/show_bug.cgi?id=360934 Filipus Klutiero changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||chea...@gmail.com --- Comment #2 from Filipus Klutiero --- I indeed cannot see a difference with ticket #344679. Luis, if this still happens, please report on https://bugs.kde.org/show_bug.cgi?id=344679 *** This bug has been marked as a duplicate of bug 344679 *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 409847] Enhancement: Accessibility - Add optional On-Demand two-finger scrolling for touchpads
https://bugs.kde.org/show_bug.cgi?id=409847 --- Comment #3 from Joe --- Additional info: bigbird@sananda:~$ cat ./.config/touchpadrc [parameters] AccelFactor=0 CircScrollDelta=6 Coasting=false CoastingSpeed=16 HorizScrollDelta=6.8 HorizTwoFingerScroll=true MaxSpeed=17.084548950195312 MaxTapMove=3.6 MinSpeed=2.02480149269104 PressureMotionMaxZ=173 PressureMotionMinZ=59 RBCornerButton=NoButton RTCornerButton=NoButton Tapping=false ThreeFingerTapButton=LeftButton TwoFingerTapButton=LeftButton VertEdgeScroll=false VertScrollDelta=3.7006 bigbird@sananda:~$ bigbird@sananda:~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=11 [slave pointer (2)] ⎜ ↳ Mouseemu virtual mouseid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ Toshiba input device id=12 [slave keyboard (3)] ↳ Mouseemu virtual keyboard id=13 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=15 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=16 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=17 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=18 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=19 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=20 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=21 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=22 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=23 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=24 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=25 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=26 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=27 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=28 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=29 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=30 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=31 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=32 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=33 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=34 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=35 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=36 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=37 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=38 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=39 [slave keyboard (3)] bigbird@sananda:~$ -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 409880] New: Kstars 3.3.2 crashes viewing histogram
https://bugs.kde.org/show_bug.cgi?id=409880 Bug ID: 409880 Summary: Kstars 3.3.2 crashes viewing histogram Product: kstars Version: 3.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: jrlangsto...@gmail.com Target Milestone: --- Application: kstars (3.3.2) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: Open fits image in kstars, click on statistics, click on histogram, click on statistics again and crashes sometimes. THis behaviour also occurred in prior versions. The crash can be reproduced sometimes. -- Backtrace: Application: KStars (kstars), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4feafa5440 (LWP 23239))] Thread 6 (Thread 0x7f4f8a7fc700 (LWP 23266)): #0 0x7f4fe327dbf9 in __GI___poll (fds=0x7f4f6800fd70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4fe091c5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4fe091c962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4fb82e40e6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f4fe0944195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4fe44c46db in start_thread (arg=0x7f4f8a7fc700) at pthread_create.c:463 #6 0x7f4fe328a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f4f8b7fe700 (LWP 23264)): #0 0x7f4fe327dbf9 in __GI___poll (fds=0x56067a877b90, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4fe091c5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4fe091c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4fe091c721 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4fe0944195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4fe44c46db in start_thread (arg=0x7f4f8b7fe700) at pthread_create.c:463 #6 0x7f4fe328a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4fbb77e700 (LWP 23247)): #0 0x7f4fe0962649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4fe091bd11 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4fe091c547 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4fe091c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4fe542f90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4fe53d49ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4fe51f322a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4fe51f816d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4fe44c46db in start_thread (arg=0x7f4fbb77e700) at pthread_create.c:463 #9 0x7f4fe328a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4fc7fff700 (LWP 23241)): #0 0x7f4fe542fc3a in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f4fe091bb28 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4fe091c4fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4fe091c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4fe542f90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4fe53d49ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4fe51f322a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4fe58acd45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f4fe51f816d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4fe44c46db in start_thread (arg=0x7f4fc7fff700) at pthread_create.c:463 #10 0x7f4fe328a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4fcf6db700 (LWP 23240)): #0 0x7f4fe327dbf9 in __GI___poll (fds=0x7f4fcf6dac28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f4fdd6a2747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f4fdd6a436a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f4fd24882a9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f4fe51f816d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4fe44c46db in start_thread (arg=0x7f4fcf6db700) at pthread_create.c:463 #6 0x7f4fe328a88f in clone () at ../sysdeps/unix/sy
[kde] [Bug 409847] Enhancement: Accessibility - Add optional On-Demand two-finger scrolling for touchpads
https://bugs.kde.org/show_bug.cgi?id=409847 --- Comment #2 from Joe --- Created attachment 121567 --> https://bugs.kde.org/attachment.cgi?id=121567&action=edit Touchpad settings bigbird@sananda:~$ cat ./.config/touchpadrc [parameters] AccelFactor=0 CircScrollDelta=6 Coasting=false CoastingSpeed=16 HorizScrollDelta=6.8 HorizTwoFingerScroll=true MaxSpeed=17.084548950195312 MaxTapMove=3.6 MinSpeed=2.02480149269104 PressureMotionMaxZ=173 PressureMotionMinZ=59 RBCornerButton=NoButton RTCornerButton=NoButton Tapping=false ThreeFingerTapButton=LeftButton TwoFingerTapButton=LeftButton VertEdgeScroll=false VertScrollDelta=3.7006 bigbird@sananda:~$ bigbird@sananda:~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=11 [slave pointer (2)] ⎜ ↳ Mouseemu virtual mouseid=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ Toshiba input device id=12 [slave keyboard (3)] ↳ Mouseemu virtual keyboard id=13 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=15 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=16 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=17 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=18 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=19 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=20 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=21 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=22 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=23 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=24 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=25 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=26 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=27 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=28 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=29 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=30 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=31 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=32 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=33 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=34 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=35 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=36 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=37 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=38 [slave keyboard (3)] ↳ TOSHIBA Web Camera - HD: TOSHIB id=39 [slave keyboard (3)] bigbird@sananda:~$ -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Flags|Usability+ | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409862] Installed page doesn't list app installed from local package until you search for it
https://bugs.kde.org/show_bug.cgi?id=409862 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409862] Installed page doesn't list app installed from local package until you search for it
https://bugs.kde.org/show_bug.cgi?id=409862 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Summary|Discover doesn't list all |Installed page doesn't list |installed app |app installed from local ||package until you search ||for it Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from Nate Graham --- Thanks, that's helpful. Looks like this is limited to apps installed from local packages. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384231] Bristle engine rotation ignores drawing angle
https://bugs.kde.org/show_bug.cgi?id=384231 vanyossi changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/15ccec5595d918 ||58ddfac21d99dfe4c53235a128 --- Comment #5 from vanyossi --- Git commit 15ccec5595d91858ddfac21d99dfe4c53235a128 by Ivan Yossi. Committed on 17/07/2019 at 00:04. Pushed by ivany into branch 'master'. Apply negative rotation on mirrored View for Bristle Engine M +6-1plugins/paintops/hairy/kis_hairy_paintop.cpp M +2-0plugins/paintops/hairy/kis_hairy_paintop.h https://invent.kde.org/kde/krita/commit/15ccec5595d91858ddfac21d99dfe4c53235a128 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 --- Comment #1 from amee...@amitlele.com --- on debian buster with the stock plasma version -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 amee...@amitlele.com changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409877] Latte-Dock Is Not Working Well Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409877 --- Comment #1 from Michail Vourlakos --- Wayland support for v0.8.9 it is just a technology preview Wayland support for git version and upcoming v0.9.0 is ALSO a technology preview. Try to reproduce with v0.9.0 and we will see how it will go... BTW global menu is not supported under wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409862] Discover doesn't list all installed app
https://bugs.kde.org/show_bug.cgi?id=409862 --- Comment #3 from marcantoine_manning...@outlook.com --- Created attachment 121566 --> https://bugs.kde.org/attachment.cgi?id=121566&action=edit Screenshot of missing apps But when I search discord in installed section, Discord is show. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409876] Dolphin does not display extended file properties for new files
https://bugs.kde.org/show_bug.cgi?id=409876 better...@gmail.com changed: What|Removed |Added CC||better...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409862] Discover doesn't list all installed app
https://bugs.kde.org/show_bug.cgi?id=409862 --- Comment #2 from marcantoine_manning...@outlook.com --- Created attachment 121565 --> https://bugs.kde.org/attachment.cgi?id=121565&action=edit Screenshot of missing apps Discord was installed with the .deb, but isn't show in installed list. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 409879] New: xdtool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 Bug ID: 409879 Summary: xdtool error KDEInit could not launch Product: Active Window Control Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: amee...@amitlele.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY xdotool script gives error STEPS TO REPRODUCE 1. create a script like: #! /bin/bash xdotool key ALT+F4 2. create a launcher in the panel pointing to this script 3. try to close windows by clicking on the launcher - u get error "KDEInit could not launch '/home/a/close.sh'" OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 409440] Kile crash when closing files
https://bugs.kde.org/show_bug.cgi?id=409440 Johannes Hirte changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Johannes Hirte --- fixed in kguiaddons with commit: commit 7ecff22e72158dd01492e1a7747b77e0d67acdad Author: Aleix Pol Date: Wed Jul 3 17:13:15 2019 +0200 KModifierKeyInfo: we are sharing the internal implementation Summary: Use data types that will only destroy it when necessary. Reviewers: broulik Subscribers: davidedmundson, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D22241 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 378904] Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 --- Comment #8 from Zeno Endemann --- Oh, and in response to the sentence "If we could assume that all archive entries have the same encoding, we could only probe the first entry": It would not make any sense for a zip file to have multiple entries with different encoding, no one would be able to decompress such a file reliably. So we don't need to worry about this case and once we have detected an encoding that should be used for the whole file. But only probing the first entry would be less reliable, after all character encoding probing gets more reliable the more text it sees. There needs to be a balance between performance and reliablilty, that's why I said 30 entries or so. -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 354963] config created by kde-gtk-config forces apps to ignore system default fonts
https://bugs.kde.org/show_bug.cgi?id=354963 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #4 from Kevin Kofler --- Are you sure that that change does the right thing? I suspect it will make GTK+ follow the systemwide defaults, which are NOT necessarily the same as the Plasma defaults. Plasma defaults to Noto upstream and in most distros, but the systemwide default is the plain "Sans" alias, which is whatever the distro defaults to (e.g., on Fedora, "Sans" is an alias for DejaVu Sans). -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 409878] New: Impossible to create an archive containing other archives via Dolphin
https://bugs.kde.org/show_bug.cgi?id=409878 Bug ID: 409878 Summary: Impossible to create an archive containing other archives via Dolphin Product: ark Version: 19.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: bugsefor...@gmx.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY I want to use Dolphin to create an archive containing other archives. Currently such task is impossible. STEPS TO REPRODUCE 1. have two or more archives and select them in Dolphin 2. right click on any selected archive 3. OBSERVED RESULT you can not create an archive because "Compress" entry is missing in the context menu. EXPECTED RESULT "Compress" entry is available in the context menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 Eyal Rozenberg changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Eyal Rozenberg --- (In reply to Myriam Schweingruber from comment #1) > Did you try building with testing disabled? No, I used the default options. With testing disabled, the build concludes without errors. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409147] Albums appear duplicated if they have different artists
https://bugs.kde.org/show_bug.cgi?id=409147 --- Comment #14 from Matthieu Gallien --- I have a work in progress diff request to fix that: https://phabricator.kde.org/D22499 More work is needed and I do not know when I will be able to do it. There are quite a few corner cases to handle when metadata is missing or partial. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409855] [history] Align icons right to the time and make some smaller
https://bugs.kde.org/show_bug.cgi?id=409855 --- Comment #6 from Postix --- > We can evaluate reducing the icon size in another patch. It's pretty simple. > In fact, would you like to have a go at it? :) I'd be happy to help. Sure I'd like to have a look at it! But give me a at least few days until I have my head free as I'm currently in the final phase of my thesis. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409855] [history] Align icons right to the time and make some smaller
https://bugs.kde.org/show_bug.cgi?id=409855 --- Comment #5 from Nate Graham --- We can evaluate reducing the icon size in another patch. It's pretty simple. In fact, would you like to have a go at it? :) I'd be happy to help. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 409877] New: Latte-Dock Is Not Working Well Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409877 Bug ID: 409877 Summary: Latte-Dock Is Not Working Well Under Wayland Session Product: lattedock Version: 0.8.9 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: tak...@disroot.org Target Milestone: --- SUMMARY Latte-Dock Is Not Working Well Under Wayland Session STEPS TO REPRODUCE 1. Login Wayland session. 2. Go to Latte-Dock. 3. Context menu > Add a Widget. 4. Select a widget (e.g. Global Menu). 5. Drag & drop to Latte-Dock. OBSERVED RESULT Latte-Dock doesn't show when you place the mouse cursor at the place where it should show (auto-hide enabled). This happens with an addition of a widget to Latte-Dock, as well as drag & drop an element (e.g. an image) to Latte-Dock to go Telegram (opened as a task), etc. EXPECTED RESULT Latte-Dock should show when you are drag & dropping an element to it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.2.1/5.16.3 (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409855] [history] Align icons right to the time and make some smaller
https://bugs.kde.org/show_bug.cgi?id=409855 --- Comment #4 from Postix --- > Your wish is my command! :) > https://phabricator.kde.org/D22493 Wow, that was quick! Thank you! :) BTW I got the intention to make the icons smaller, because they are now so big, so that they hit the bottom of the notification entry and therefore in my eyes look like they almost belong to the note below. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409876] New: Dolphin does not display extended file properties for new files
https://bugs.kde.org/show_bug.cgi?id=409876 Bug ID: 409876 Summary: Dolphin does not display extended file properties for new files Product: dolphin Version: 19.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: better...@gmail.com Target Milestone: --- SUMMARY Dolphin does not display extended file properties for new files. Only standard properties are visible: file type, size, modification time, tags, stars and comments. No EXIF and so on. These metadata are visible after file indexation (on KDE Neon by default after reboot or manually). The problem does not occur on external drives. As far as I know, in that case indexation is turned off. ASSUMPTIONS 1. You have latest KDE Neon User Edition 2. You will wait a moment to finish indexing files after the system starts STEPS TO REPRODUCE 1. Download file with additional metadata (e.g. this photo with EXIF: https://github.com/ianare/exif-samples/blob/master/jpg/Canon_40D.jpg) and save it on main disk (not external) 2. Open Dolphin and find downloaded file 3. Right click -> Properties OBSERVED RESULT Only standard properties are visible: file type, size, modification time, tags, stars and comments. EXPECTED RESULT Standard properties + some other metadata like camera model and so on SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon User Edition 5.16.3 (Linux 4.18.0-25-generic) (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Missing metadata are visible after file indexation (on KDE Neon by default after reboot or turn it manually). From what I see, file indexation is not continuous. Tested on two different computers (including fresh installation from neon-user-20190711-1118.iso). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409690] Add option to auto copy screenshot to clipboard
https://bugs.kde.org/show_bug.cgi?id=409690 --- Comment #2 from Vladimir --- (In reply to Nate Graham from comment #1) > You want the screenshot to be saved to a file and also copied to the > clipboard? Is it possible that you would be satisfied with only copying to > the clipboard instead of saving? Sure! actually only copying to the clipboard would be exactly what I need. > Can you explain your use case? I take lots of screenshots during the day (code, shell output, webpages) and share them via Slack, I'm used from other tools to just press "Print screen", get the selection tool for the capture mode I need, then proceed to Slack / Gimp to paste the image. With Spectacle I've to do extra steps: Spectacle is brought to the foreground, then I click "Copy to Clipboard" button, minimize the Spectacle window and then finally paste it. That won't be annoying if I didn't confuse so often the "Copy to Clipboard" button with the "Take a New Screenshot", ruining a perfect screenshot previously taken. Or worse, forgetting that I have to click that button and pasting/sending an old screenshot out of context or inappropriate. Thank you for your time -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409875] KMail crashes on mail with Itinerary content
https://bugs.kde.org/show_bug.cgi?id=409875 --- Comment #1 from Nicolas Fella --- Update: It happens on both Wayland and X11, but not on KMail 5.11.2, only master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."
https://bugs.kde.org/show_bug.cgi?id=405454 --- Comment #16 from David Faure --- On my side, after a full reboot the desktop names are truncated again. Very weird. Current hypothesis, the plugging of an external monitor had something to do with it. To be confirmed later this week. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409875] New: KMail crashes on mail with Itinerary content
https://bugs.kde.org/show_bug.cgi?id=409875 Bug ID: 409875 Summary: KMail crashes on mail with Itinerary content Product: kmail2 Version: Git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- Created attachment 121564 --> https://bugs.kde.org/attachment.cgi?id=121564&action=edit Backtrace SUMMARY STEPS TO REPRODUCE 1. Open email with extracted booking information 2. Move cursor above extracted information OBSERVED RESULT KMail crashes SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.13.0 ADDITIONAL INFORMATION Wayland session Happens for all DB emails I tested. Didn't happen with Ryanair -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409874] Rendering speed is much faster when kdenlive window is minimized
https://bugs.kde.org/show_bug.cgi?id=409874 sithscout80 changed: What|Removed |Added CC||dghand+kde_b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409874] Rendering speed is much faster when kdenlive window is minimized
https://bugs.kde.org/show_bug.cgi?id=409874 --- Comment #1 from sithscout80 --- Created attachment 121563 --> https://bugs.kde.org/attachment.cgi?id=121563&action=edit Image showing rendering speed difference of the same project when kdenlive window is minimized/not minimized -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409874] New: Rendering speed is much faster when kdenlive window is minimized
https://bugs.kde.org/show_bug.cgi?id=409874 Bug ID: 409874 Summary: Rendering speed is much faster when kdenlive window is minimized Product: kdenlive Version: 18.12.1 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dghand+kde_b...@gmail.com Target Milestone: --- Created attachment 121562 --> https://bugs.kde.org/attachment.cgi?id=121562&action=edit kdenlive project file which demonstrates difference in rendering speed SUMMARY Rendering speed is much faster when the kdenlive window is minimized (which means rendering is slower when the window is not minimized). It is >=2x faster when minimized. Render time: kdenlive minimized: 1 minute, 10 seconds kdenlive maximized: 3 minutes, 54 seconds STEPS TO REPRODUCE 1. Create a project from some pictures, apply some complex effects to the pictures (Wave/Dust/Blur/Pixelize) 2. Render project using H.264 in the Lossless/HQ section. Click "Render to File" 3. After clicking "Render to File" minimize the kdenlive window 4. Repeat the same process (with a unique output filename) while keeping the kdenlive window open OBSERVED RESULT Render time is much longer when kdenlive window is not minimized. Lower CPU utilization of the rendering can also be observed in Windows' Task Manager. EXPECTED RESULT Render time would be similar when kdenlive window is open or minimized. SOFTWARE/OS VERSIONS Windows: Windows 10 (version 1709), OS Build 16299.1217 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.3 (built against 5.11.2) ADDITIONAL INFORMATION The difference in render speed between minimized/not minimized has been seen in other projects as well. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 409836] Build failure: Undefined reference to setMountPointManager(MountPointManager*)
https://bugs.kde.org/show_bug.cgi?id=409836 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Myriam Schweingruber --- Did you try building with testing disabled? Since the testing framework needs to be built before compiling Amarok you might want to build without testing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407514] [templates] Custom template folders don't display their name
https://bugs.kde.org/show_bug.cgi?id=407514 --- Comment #2 from vanyossi --- ok after seeing the code: The only way to get an empty template name is if you have created the template with a ".directory" desktop file with the Name value set to empty. Probably there was a time in which some languages were missing, including [fr], so the template name get picked up as empty. just delete/rename the ".directory" to make krita use the folder name as the template name. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 409873] New: Space before \documentclass{beamer} = crash
https://bugs.kde.org/show_bug.cgi?id=409873
Bug ID: 409873
Summary: Space before \documentclass{beamer} = crash
Product: kile
Version: 2.1.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: michel.lud...@kdemail.net
Reporter: olavocont...@gmail.com
Target Milestone: ---
SUMMARY
Dear Kile Developers,
I noticed that every time I try to open a .tex file with one or more spaces at
the first line before \documentclass{beamer}, kile will immediately crash.
I could fix the problem removing the space at the first line.
Could you please try to reproduce this error?
Thanks in advance.
Olavo
STEPS TO REPRODUCE
1. Open Kile with an empty document and type the following:
\documentclass{beamer}
\begin{document}
\end{document}
2. Notice that \documentclass{beamer} should be at the 1st line and there is a
space before it.
3. Save the file
4. Close the file
5. Open the file
OBSERVED RESULT
Kile will crash with a segmentation fault error.
E.g:
Executable: kile PID: 7366 Signal: Segmentation fault (11) Time: 07/16/19
05:56:11 PM
SOFTWARE/OS VERSIONS
Application: kile (2.1.3)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-154-generic x86_64
Distribution: Ubuntu 16.04.6 LTS
-- Information about the crash:
The crash can be reproduced every time.
-- Backtrace:
A useful backtrace could not be generated
Report to https://bugs.kde.org/
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847 Colin J Thomson changed: What|Removed |Added CC|colin.thom...@g6avk.co.uk | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409131] krita: moving 2 selected shapes (text and polygon) resets both shapes opacity to 0 if polygon had opacity less than 1
https://bugs.kde.org/show_bug.cgi?id=409131 vanyossi changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/9855b267f7ec41 ||8ff76d22017abc653c2b73d89c Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from vanyossi --- Git commit 9855b267f7ec418ff76d22017abc653c2b73d89c by Ivan Yossi. Committed on 16/07/2019 at 20:41. Pushed by ivany into branch 'master'. Do not trigger value Change when selecting multiple shapes M +1-1libs/ui/widgets/KisSelectionPropertySlider.cpp https://invent.kde.org/kde/krita/commit/9855b267f7ec418ff76d22017abc653c2b73d89c -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 378904] Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 --- Comment #7 from Zeno Endemann --- Right, probing should probably be limited to maybe the first 30 entries or so. But as it is pretty clear that this auto detection won't always work I'd really like to have a manual override as well. On the other hand I can definitely understand not wanting to make the UI more complex for this corner case that only applies to the zip format, and there only to files created by legacy software (does anyone know which programs produce these zip files actually?), so the best compromise I can come up with is a command line flag (think "--libzip-plugin-force-char-encoding=SHIFT-JIS"). One more thing, in the zip spec there is a file global flag that, if set, requires the zip file to be utf8. If that flag is set and we encounter a non-valid utf8 string that probably should be treated as an error. Unfortunately I haven't seen any way to get the value of the flag via the libzip API. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409872] Crash when resizing two vector shapes at once.
https://bugs.kde.org/show_bug.cgi?id=409872 wolthera changed: What|Removed |Added Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |tiger.1...@yahoo.com.cn Ever confirmed|0 |1 --- Comment #1 from wolthera --- tusooa, boud thinks this is caused by the refactorings you did. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409872] New: Crash when resizing two vector shapes at once.
https://bugs.kde.org/show_bug.cgi?id=409872 Bug ID: 409872 Summary: Crash when resizing two vector shapes at once. Product: krita Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Application: krita (4.3.0-prealpha (git 9f766e7)) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I resized two vector shapes at once at the behest of ghevan, this leads to this crash. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9354bf5e80 (LWP 12972))] Thread 9 (Thread 0x7f92dddf7700 (LWP 12319)): #0 0x7f9348c5bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f92dddf6ba0, expected=0, futex_word=0x55914d9e0cd0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f92dddf6c60, mutex=0x55914d9e0c80, cond=0x55914d9e0ca8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55914d9e0ca8, mutex=0x55914d9e0c80, abstime=0x7f92dddf6c60) at pthread_cond_wait.c:667 #3 0x7f934fddfd36 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f934fde0096 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f934fddd740 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f934fdd8c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9348c556db in start_thread (arg=0x7f92dddf7700) at pthread_create.c:463 #8 0x7f934f4c088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f92ed01a700 (LWP 13111)): #0 0x7f934f4b3bf9 in __GI___poll (fds=0x7f92e0004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f93473585c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f93473586dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f935000edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f934ffb003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f934fdd74ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f934fdd8c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9348c556db in start_thread (arg=0x7f92ed01a700) at pthread_create.c:463 #8 0x7f934f4c088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f92ed85b700 (LWP 13102)): #0 0x7f934f4af0b4 in __GI___libc_read (fd=33, buf=0x7f92ed85aae0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f934739d2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f93473580b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9347358570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f93473586dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f935000edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f934ffb003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f934fdd74ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f932d53e926 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f934fdd8c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9348c556db in start_thread (arg=0x7f92ed85b700) at pthread_create.c:463 #11 0x7f934f4c088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f9309c50700 (LWP 13097)): #0 0x7f934f4b3bf9 in __GI___poll (fds=0x7f92fc0032e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f93473585c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f93473586dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f935000edcb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f934ffb003a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f934fdd74ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f932d079115 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f934fdd8c72 in ?? ()
[kate] [Bug 403730] minimap accesses invalid text line (std::out_of_range exception)
https://bugs.kde.org/show_bug.cgi?id=403730 --- Comment #3 from Christoph Cullmann --- Too bad :( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403730] minimap accesses invalid text line (std::out_of_range exception)
https://bugs.kde.org/show_bug.cgi?id=403730 --- Comment #2 from Milian Wolff --- no :( -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409852] Okular takes an extreme amount of time to load a djvu file over samba
https://bugs.kde.org/show_bug.cgi?id=409852 --- Comment #5 from John van Spaandonk --- Good idea nate! On the workstation: Same problem with the smb client, server timeout. Tried with my kde laptop, which was kubuntu 18.04 also but I managed to rebase it to muon, it is current. So plasma 5.16.2 I think. Here the kio-slave works: book read in about 2 seconds, over wifi even. using (in another Dolphin tab) a mounted smb share (via fstab) I had to kill okular after 1:30 had passed. Laptop is 8 years old dell XPS, not as fast as the desktop. Note that Okular blocks also that Dolphin instance until I kill it. But at least I managed to show that using smb: on the laptop it is much faster than via a mounted drive on the desktop. Same book takes about 40 seconds on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409762] [wayland] Screenshots are always a little blurry
https://bugs.kde.org/show_bug.cgi?id=409762 --- Comment #6 from Marvin Hagemeister --- Yup, I can confirm that the X11 screen is the proper screen resolution and that the wayland screenshot exactly half of that. The bug only occurs when the scaling setting in KDE's "Display Settings" page is set to something other than 1x. In my case that's 2x so spectacle seems to think it'd only need to use half the resolution. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 409606] Track memory allocated with mmap
https://bugs.kde.org/show_bug.cgi?id=409606 --- Comment #1 from Milian Wolff --- syscalls like mmap cannot be easily intercepted with LD_PRELOAD or similar, which makes it quasi impossible to do with the current architecture of heaptrack. thankfully, you can easily use perf to achieve the same, since mmap calls are usually done way less often than malloc calls! perf record --call-graph dwarf -e syscalls:sys_enter_mmap -- interpreting the data may require some more work, but it should be relatively easy I believe based on `perf script` textual output or even a python script. That said: A convert from such mmap output to the heaptrack data format would be nice, such that we can use the heaptrack GUI to investigate mmap usage. Also: if anyone knows how to intercept mmap (ptrace?) I'd be all ears :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409541] Sort by toolbar icon not changing properly
https://bugs.kde.org/show_bug.cgi?id=409541 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Nate Graham --- Thanks. This seems like something we should really support natively, rather than requiring the user to hack it into place manually. I especially like your use of Alt shortcuts for quickly switching between sort orders. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409811] Add "About System" page into Settings app
https://bugs.kde.org/show_bug.cgi?id=409811 --- Comment #2 from Nate Graham --- Created attachment 121561 --> https://bugs.kde.org/attachment.cgi?id=121561&action=edit Patch If we want to do this, there are a few ways: - Add toolbar button/menu item (depending on the view) that opens the about-distro KCM when clicked - Have KInfoCenter install a .desktop file (patch attached) that makes the about_distro KCM appear in the list of KCMs in System Settings. I didn't submit the patch, as we may not actually want to do it this way (or at all). -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 378904] Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 --- Comment #6 from Ragnar Thomsen --- Created attachment 121560 --> https://bugs.kde.org/attachment.cgi?id=121560&action=edit MARU164.zip opened using KEncodingProber -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 378904] Ark should use charset auto-detection for filenames
https://bugs.kde.org/show_bug.cgi?id=378904 --- Comment #5 from Ragnar Thomsen --- I tried using KEncodingParser with the libzip-plugin to open the attached Japanese zip archive. It seems like it could correctly detect the encoding for all the files (see attached screenshot), so this seems like a promising approach. I also tried using the uchardet library but it detected ASCII encoding for all the files. One concern is the overhead of probing for the encoding of each archive entry. Opening the linux kernel source in zip format took 106 secs with probing vs 5 secs without, so there is significant overhead to this approach. I think we either need to be smart and only probe when needed (can't see how though) or we add a menu item in the GUI to reload the archive with probing of filename encodings. If we could assume that all archive entries have the same encoding, we could only probe the first entry, but I think this assumption doesn't hold in real life, e.g. in the attached archive the first entry is detected as UTF8 since it doesn't contain Japanese characters. -- You are receiving this mail because: You are watching all bug changes.
[kirigami gallery] [Bug 409871] New: desktop-entry-lacks-keywords-entry usr/share/applications/org.kde.kirigami2.gallery.desktop
https://bugs.kde.org/show_bug.cgi?id=409871 Bug ID: 409871 Summary: desktop-entry-lacks-keywords-entry usr/share/applications/org.kde.kirigami2.gallery.deskt op Product: kirigami gallery Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: sgmo...@kde.org Target Milestone: --- While packaging for debian I ran into this lintian error. While optional it is useful. N:This .desktop file does either not contain a "Keywords" entry or it does N:not contain any keywords not already present in the "Name" or N:"GenericName" entries. N: N:.desktop files are organized in key/value pairs (similar to .ini files). N:"Keywords" is the name of the entry/key in the .desktop file containing N:keywords relevant for this .desktop file. N: N:The desktop-file-validate tool in the desktop-file-utils package is N:useful for checking the syntax of desktop entries. N: N:Refer to N: https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, N:https://bugs.debian.org/693918, and N:https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords for N:details. N: N:Severity: wishlist, Certainty: certain N: N:Check: menu-format, Type: binary -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 409870] New: KDE Connect v1.12.93 problem exporting phone file system
https://bugs.kde.org/show_bug.cgi?id=409870 Bug ID: 409870 Summary: KDE Connect v1.12.93 problem exporting phone file system Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: jfbcommerc...@gmail.com Target Milestone: --- SUMMARY I'm running KDE Connect 1.12.93 (newly installed from Google Play Store) and trying to export its file system to a Linux machine running Kubuntu 16.04.6 LTS. The phone is a Moto G7 Play, with all apps on an SD Card. When I go to "Filesystem expose" and go to the top of the tree, it shows "SanDisk SD card", which I "Select", and it gives me a box "Add storage location" with grayed out box "Storage location" containing "primary:" and "Display name" "primary". If I start a Dolphin file browser and select "motorola", I see "primary" under it, but opening that gives an error "/home//.config/kdeconnect//kdeconnect_sftp//primary does not exist." In an older version of kdeconnect (1.8.2, I believe) I was able to export "/storage/emulated/0" and everything worked correctly. I am not given a keyboard when selecting "Storage location", so I can't input "/storage/emulated/0" directly. Exporting any of the subdirectories (such as DCIM) are all referenced relative to "primary:", which, again, doesn't exist. My set-up can't be all that unique, so I'm baffled that I don't seem to be able to find many references to it when searching for it. I've tried to find references to a configuration that resolves the issue, but the only thing that seems to work is to go back to version 1.8.2. For obvious reasons, I'd like to stay current and get everything to work with the current release. Any suggestions would be much appreciated. STEPS TO REPRODUCE 1. Install kdeconnect to Kubuntu system (16.04.6 LTS) 2. Install kdeconnect v1.12.93 app to phone from Google Play Store 3. Pair to laptop 4. Test connection (Ring my phone successful). 5. Export file system (...->Plugin settings->Filesystem expose->Add storage location->Click to select 6. Browse to SanDisk SD card 7. Select 8. Storage location "primary:" (grayed out, can't be modified via keyboard) 9. OK 10. On laptop, click kdeconnect icon, select "Browse this device". 11. When browser opens, select "primary". OBSERVED RESULT Error message /home//.config/kdeconnect//kdeconnect_sftp//primary does not exist. EXPECTED RESULT Older versions (1.8.4, I believe) permitted the expose of /storage/emulated/0/, which opened correctly in the browser. It's not clear whether the failure is due to configuration of this particular phone where "primary:" should be set up in some way. SOFTWARE/OS VERSIONS Windows: no way! macOS: no Linux/KDE Plasma: 16.04.6 LTS (available in About System) KDE Plasma Version: 5.8.9 KDE Frameworks Version: 5.36.0 Qt Version: 5.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409151] Typing Hangul with ibus in Konsole doesn’t work properly
https://bugs.kde.org/show_bug.cgi?id=409151 --- Comment #3 from ariasuni --- Same, thanks. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 409869] New: Plasma Wayland session won't start with Kwayland 5.60 and newer
https://bugs.kde.org/show_bug.cgi?id=409869 Bug ID: 409869 Summary: Plasma Wayland session won't start with Kwayland 5.60 and newer Product: frameworks-kwayland Version: 5.60.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY Since the update to kwayland 5.60 I am not able to start the Wayland Session. Reverting back to kwayland 5.59 fixes this issue. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.13.0 ADDITIONAL INFORMATION Kwayland master doesn't work either. -- You are receiving this mail because: You are watching all bug changes.
