[digikam] [Bug 410787] can't export to Google photo
https://bugs.kde.org/show_bug.cgi?id=410787 --- Comment #19 from Philippe ROUBACH --- (In reply to caulier.gilles from comment #18) > Thanks Philippe for the feedback. > > Perhaps it depend of the Exif date parsed from image by Google when > importing files ? If date is not today... > > Gilles no, today refers to the date of the import i never imported the photos same day i took them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410787] can't export to Google photo
https://bugs.kde.org/show_bug.cgi?id=410787 --- Comment #18 from caulier.gil...@gmail.com --- Thanks Philippe for the feedback. Perhaps it depend of the Exif date parsed from image by Google when importing files ? If date is not today... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410787] can't export to Google photo
https://bugs.kde.org/show_bug.cgi?id=410787 --- Comment #17 from Philippe ROUBACH --- 7.00 beta 2 It remains a problem: photos and video are well in the good Google photo album, but they don't appear in "google photo > photos > today". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414000] Running external applications from AppImage bundle
https://bugs.kde.org/show_bug.cgi?id=414000 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Appimage tool integration |Running external ||applications from AppImage ||bundle -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385953] reduce installed footprint under Windows
https://bugs.kde.org/show_bug.cgi?id=385953 --- Comment #5 from caulier.gil...@gmail.com --- Git commit 36181629eef86c2e06057de6bdcf01d5899742bd by Gilles Caulier. Committed on 16/01/2020 at 07:35. Pushed by cgilles into branch 'master'. Build a Windows installer without debug symbold to reduce bundle fingerprints A debug version is compiled also in the workflow deployement (this one use '-debug' prefix). Non debug version will be published officially on KDE download mirrors, and debug will be only published on weekly build area. M +3-3project/bundles/mxe/04-build-installer.sh M +15 -0project/bundles/mxe/makeall.sh M +15 -0project/bundles/mxe/update.sh https://invent.kde.org/kde/digikam/commit/36181629eef86c2e06057de6bdcf01d5899742bd -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416230] KDE Partition Manager crash when opening removable device
https://bugs.kde.org/show_bug.cgi?id=416230 --- Comment #2 from HM --- So the USB drive I had this crash happen with was kind of problematic. It was a promo USB that you receive at expos. (Might have been read only. I was able to format it someway with cfdisk I think. Weird drive.) It doesnt crash with my other USB drives. But I suppose the app shouldn't have crashed even so. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416241] Crashes when blur is unconstrained and x value is reduced to 1 while y is more than 8
https://bugs.kde.org/show_bug.cgi?id=416241 vanyossi changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from vanyossi --- Merge request associated to this bug https://invent.kde.org/kde/krita/merge_requests/220 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398853] Folder lost
https://bugs.kde.org/show_bug.cgi?id=398853 Geoff Cutter changed: What|Removed |Added CC||geoff.cut...@gmail.com --- Comment #4 from Geoff Cutter --- FYI The apparent fix - use the mouse (Lenovo model: M-U0025-O) carefully, slowly, double check every time, etc. - is now discarded in favor of a new mouse. Looks like I had a hardware fault, mouse. I guess it was putting in extra key instructions (noise) which were not requested. (@outlook.com not is use) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416318] As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Hi, Could you paste backtrace ? Regards -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413762] GTK2 themes are not working at all and the previews aren't working either for only gtk2
https://bugs.kde.org/show_bug.cgi?id=413762 --- Comment #6 from Josh Freeno --- In KDE we are instructed to put gtk themes into the ~/local/share/themes dir and not the the ~themes dir so I guess for now we need to place into in the root. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 416286] DRD reports “conflicting load” error on std::mutex::lock
https://bugs.kde.org/show_bug.cgi?id=416286 --- Comment #2 from Bart Van Assche --- Thanks for having reported this. Please check whether the changes that have been checked in on the master branch fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415210] When I start up the app for the first time, image on the screen freezes for 5-10 seconds.
https://bugs.kde.org/show_bug.cgi?id=415210 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[amarok] [Bug 415652] Starting Amarok on FreeBSD 12.1-RELEASE causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=415652 --- 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.
[kmymoney] [Bug 415768] Scheduled Trans.
https://bugs.kde.org/show_bug.cgi?id=415768 --- 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.
[amarok] [Bug 415243] I can not add any online stations to the play list
https://bugs.kde.org/show_bug.cgi?id=415243 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.
[Akonadi] [Bug 414974] Akonadi crashed while deleting emails
https://bugs.kde.org/show_bug.cgi?id=414974 --- 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.
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 --- Comment #6 from Victor Ryzhykh --- > dialog title in src/qtquick/qml/Dialog.qml It is unclear why in the window title the text to download the file. The window title contains the text from the download button, instead of the name of the contents of the window. I think it will be correct when the button contains the text to download, in the window title, the name of the content. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407894] Scrolling to the right fails to redraw documents
https://bugs.kde.org/show_bug.cgi?id=407894 --- Comment #4 from michael --- I don't know why but this seems not to reproduce in master. On the latest 1.8 this still occurs however kdiff3 sometimes seems to update the window automatically after being left alone for few seconds. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 416319] New: forceActiveWindow() function raises window but may not give it focus.
https://bugs.kde.org/show_bug.cgi?id=416319 Bug ID: 416319 Summary: forceActiveWindow() function raises window but may not give it focus. Product: frameworks-kwindowsystem Version: 5.65.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 125159 --> https://bugs.kde.org/attachment.cgi?id=125159=edit The screenshot showing the specified window is not getting focus SUMMARY I discover this bug when developing a simple KRunner extension that switches windows on Plasma. In this extension, I use forceActiveWindow(Wid w) call to raise and focus a window, see https://github.com/xuzhao9/krunner-switcher/blob/master/src/switcher.cpp#L135 This function call successfully returns, the window specified in argument always raises, but may not get focus (non-deterministic). STEPS TO REPRODUCE 1. Install the krunner-switcher plugin of KRunner 2. Use KRunner to activate a window OBSERVED RESULT The specified window is activated and gets focus. EXPECTED RESULT The specified window is raised to the front, but may not get focus (the old window keeps focus). If you call activeWindow() at this moment, it returns the new window, i.e., the one specified in the argument of forceActiveWindow(). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200113 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION This bug is non-deterministic. You may need to try it multiple times to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 416262] KDE Flatpak 5.12 Sdk broken in ARM
https://bugs.kde.org/show_bug.cgi?id=416262 --- Comment #2 from Aleix Pol --- Would you be able to investigate a bit what could be wrong? I'm quite clueless myself about qmake. :/ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416318] New: As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time!
https://bugs.kde.org/show_bug.cgi?id=416318 Bug ID: 416318 Summary: As soon as I click on a certain line in the Message list Kmail crashes in a flash - every time! Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: ruthesro...@zoho.com Target Milestone: --- SUMMARY some months ago (2019) this happened and I finally just avoided touching that one message line. It came to the top and I just worked around it. Finally I re-installed my system, openSUSE LEAP 15.1, and the problem was gone. I set up my 2 dozen emails and all was fine until tonight. A different email with an attachment came in, as soon as I click on it, KMail vanishes! over and over again! I really hope I don't have to reinstall my whole system to clear this up! STEPS TO REPRODUCE 1. Just click on that one email with a newsletter attachment. 2. The whole KMail program closes too fast to click on any Report Bug link. 3. OBSERVED RESULT KMail crashes instantly EXPECTED RESULT I see and read the email, and the attached newsletter. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Email Client Copyright © 1997–2018, KMail authors http://userbase.kde.org/KMail (available in About System) KDE Plasma Version: KDE Frameworks 5.55.0 The xcb windowing system KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 (built against 5.9.7) ADDITIONAL INFORMATION I would be grateful to know how to delete the culprit email. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 416309] Single quote appears twice in inline math mode
https://bugs.kde.org/show_bug.cgi?id=416309
--- Comment #1 from abyss ---
I added a user-defined script that lets me work around this. The script is
activated when I press the key `'`.
If anyone else is interested, here it is:
document.editBegin();
var range = view.selectionRange();
if ( range.isValid() ) {
view.clearSelection();
document.insertText(range.end,"'");
var c = view.cursorPosition();
document.insertText(range.start,"'");
c.column = c.column + 1;
view.setCursorPosition(c);
}
else {
document.insertText("'");
}
document.editEnd();
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 415235] Cover art for certain songs/albums doesn't load.
https://bugs.kde.org/show_bug.cgi?id=415235 Noah changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #12 from Noah --- After looking at my files more; I realized that the albums not displaying their album art correctly have cover images in their directories with .png appended to the end of their file names, but the images themselves are formatted as JPEG images. Fixing this so that the image file's extension matches the format of the image resolves the issue. This was my mistake, I'll close the bug now. Sorry for wasting your time over a problem I unknowingly created. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416317] Bug Report
https://bugs.kde.org/show_bug.cgi?id=416317 --- Comment #3 from hutb...@gmail.com --- Thanks in advance! :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416317] Bug Report
https://bugs.kde.org/show_bug.cgi?id=416317 --- Comment #2 from hutb...@gmail.com --- Keep in mind.. I am somewhat of a noob. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416317] Bug Report
https://bugs.kde.org/show_bug.cgi?id=416317 hutb...@gmail.com changed: What|Removed |Added Assignee|lei...@leinir.dk|hutb...@gmail.com Platform|Other |Archlinux Packages --- Comment #1 from hutb...@gmail.com --- Arch Linux x86_64 Discover - 5.17.5 Qt - 5.14 Linux 5.4.10.a-1-hardened KDE framework 5.66 Plasma 5.17.5 Icon theme - breeze -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 --- Comment #5 from Victor Ryzhykh --- The problem continues to multiply. Here https://phabricator.kde.org/D26665#594287 And still here https://cgit.kde.org/plasma-desktop.git/commit/?id=442c43b3ca98807a7b93c757ffbd090c892e0e44 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416317] New: Bug Report
https://bugs.kde.org/show_bug.cgi?id=416317 Bug ID: 416317 Summary: Bug Report Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: hutb...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY some icons dont show and discover doesn't fully load everything. STEPS TO REPRODUCE 1. click on update in notifs 2. wait 3. OBSERVED RESULT missing data EXPECTED RESULT full load SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: linux-hardened / KDE plasma 5 (available in About System) KDE Plasma Version: 5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am in the process of hardening my kernel. I have problems with getting the touch screen to work on my tablet and was wondering if you could help me with it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401012] keyboard indicator text is barely visible in system tray settings when using a dark theme for Plasma
https://bugs.kde.org/show_bug.cgi?id=401012 --- Comment #3 from ariasuni --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 414264] Misleading error message on webdavs protocol
https://bugs.kde.org/show_bug.cgi?id=414264 Juan Francisco Cantero Hurtado changed: What|Removed |Added Version|5.64.0 |5.66.0 Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||juanfra...@gmail.com --- Comment #1 from Juan Francisco Cantero Hurtado --- I see the same error when I try to log in a nextcloud server. Log in to Box.com works fine. The same nextcloud url, user and password works using Thunar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 --- Comment #15 from Konrad Materka --- confidence -> coincidence This bug is almost 4 years old, so probably we won't get feedback from reporter. In fact this is a feature request, we can still keep it open, create new one with better description or wait for feedback if user like the new, consistent ordering. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Christoph Feck changed: What|Removed |Added CC||k...@box.kilmann.net --- Comment #54 from Christoph Feck --- *** Bug 416215 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416215] plasmashell crahsed beim login.
https://bugs.kde.org/show_bug.cgi?id=416215 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Christoph Feck --- Mattheus, please don't add unrelated backtraces. The reported crash in libkcups is already fixed. *** This bug has been marked as a duplicate of bug 326289 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416290] sddm creates random name dirs in $HOME
https://bugs.kde.org/show_bug.cgi?id=416290 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Christoph Feck --- Please ask your distribution if they are interested in backporting the fix or updating to the recent version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412476] The kde plasma panel temporary disappeared after switching activity.
https://bugs.kde.org/show_bug.cgi?id=412476 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 384470 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384470] Crash in QSGBatchRenderer::Renderer::renderBatches
https://bugs.kde.org/show_bug.cgi?id=384470 David Edmundson changed: What|Removed |Added CC||canamvs...@yahoo.com.tw --- Comment #18 from David Edmundson --- *** Bug 412476 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416316] New: KWin crashes after resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=416316 Bug ID: 416316 Summary: KWin crashes after resuming from suspend Product: kwin Version: 5.17.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j...@jayarmstrong.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.13.1 Frameworks Version: 5.65.0 Operating System: Linux 5.4.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: First time putting laptop to sleep after booting. Resuming took longer, screens flickered between brightness levels for about 5 seconds, then desktop (plasma?) reloaded wallpaper, etc. System is working now but normal desktop effects are disabled and glxgears shows "Error: couldn't open display (null)". Other than recent updates, I recently started using the nvidia driver, so that's a probaby culprit. openSUSE Tumbleweed Intel i5-8350u (Intel UHD 620) geforce mx150 - 440.44.00.0 external monitor connected via HDMI all packages up to date as of an hour ago. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f45e401cd00 (LWP 4853))] Thread 5 (Thread 0x7f45d88a5700 (LWP 5086)): #0 0x7f45e8fcacd6 in ppoll () at /lib64/libc.so.6 #1 0x7f45e7b16a89 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45e7b18081 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45e7ac315b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f45e78fb011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f45e66643b5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f45e78fc192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f45e6f0af2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f45e8fd54af in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f45da366700 (LWP 4968)): #0 0x7f45e6f116a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f45e740e1fa in () at /usr/lib64/libQt5Script.so.5 #2 0x7f45e740e21b in () at /usr/lib64/libQt5Script.so.5 #3 0x7f45e6f0af2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f45e8fd54af in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f45db5d9700 (LWP 4966)): #0 0x7f45e8fcacd6 in ppoll () at /lib64/libc.so.6 #1 0x7f45e7b16a89 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45e7b18081 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45e7ac315b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f45e78fb011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f45e66643b5 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f45e78fc192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f45e6f0af2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f45e8fd54af in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f45e1395700 (LWP 4885)): #0 0x7f45e8fcacd6 in ppoll () at /lib64/libc.so.6 #1 0x7f45e7b16a89 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f45e7b18081 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f45e7ac315b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f45e78fb011 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f45e60bb4f6 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7f45e78fc192 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f45e6f0af2a in start_thread () at /lib64/libpthread.so.0 #8 0x7f45e8fd54af in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f45e401cd00 (LWP 4853)): [KCrash Handler] #6 0x7f45e8f120d1 in raise () at /lib64/libc.so.6 #7 0x7f45e8efb55d in abort () at /lib64/libc.so.6 #8 0x7f4545175e89 in () at /usr/lib64/libnvidia-glcore.so.440.44 #9 0x7f45452b8fd6 in () at /usr/lib64/libnvidia-glcore.so.440.44 #10 0x7f45452b9f90 in () at /usr/lib64/libnvidia-glcore.so.440.44 #11 0x7f45452354a3 in () at /usr/lib64/libnvidia-glcore.so.440.44 #12 0x7f45451f0521 in () at /usr/lib64/libnvidia-glcore.so.440.44 #13 0x7f45451f0f05 in () at /usr/lib64/libnvidia-glcore.so.440.44 #14 0x7f45452072e8 in () at /usr/lib64/libnvidia-glcore.so.440.44 #15 0x7f454520761e in () at /usr/lib64/libnvidia-glcore.so.440.44 #16 0x7f45451a3833 in () at /usr/lib64/libnvidia-glcore.so.440.44 #17 0x7f4544da50ab in () at /usr/lib64/libnvidia-glcore.so.440.44 #18 0x7f45e69becc8 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib64/libQt5Quick.so.5 #19 0x7f45e69c5132 in
[plasmashell] [Bug 416215] plasmashell crahsed beim login.
https://bugs.kde.org/show_bug.cgi?id=416215 --- Comment #3 from k...@box.kilmann.net --- get it back to work after I delete waiting printer jobs and printer queue. Not testet if first one would have been suffcient -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348569] KWin's timestamp mechanism isn't robust against bogus event times
https://bugs.kde.org/show_bug.cgi?id=348569 --- Comment #41 from Dan --- Thanks Christopher, I'm stuck back on 5.9.5. Good to know that was already taken care of - I should've thought to check Qt as well. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #43 from Huw --- Good news for mailbox.org users! They've just upgraded to OX 7.10.2 and it seems this bug no longer affects us! I just created a new DAV resource in KOrganizer, pointed it at my mailbox.org calendar, and it synced. Then I created an event locally, as well as a different event on mailbox.org, and they synced both ways! Can anyone else confirm? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 416315] New: Kate aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=416315 Bug ID: 416315 Summary: Kate aborted when its Wayland connection broke Product: kate Version: 19.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: kate (19.12.1) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.5.0-0.rc6.git0.1.fc32.x86_64 x86_64 Distribution: Fedora 32 (Rawhide) -- Information about the crash: - What I was doing when the application crashed: I was running Plasma 5.17.5 on Wayland in Fedora Rawhide with Qt 5.13.2, KF 5.66.0, Mesa 19.3.2. I opened Konsole 19.2.1. I opened a second tab. I ran coredumpctl gdb on a kwin_wayland crash which happened when logging out on the previous boot. I reported those type of kwin_wayland crashes at https://bugs.kde.org/show_bug.cgi?id=416147. The core dump file was 2.1 GB, and it took a few minutes for coredumpctl gdb to decompress and process the core dump. I ran bt in gdb to get a trace. Konsole stopped responding for about a minute with Not Responding in the title bar. Konsole's colours faded. Konsole disappeared. The trace in Dr. Konqi showed the error "The Wayland connection broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1. I've previously seen Konsole abort with that error as in my report at https://bugs.kde.org/show_bug.cgi?id=413058. I've also seen that error for plasmashell https://bugs.kde.org/show_bug.cgi?id=414116 ksysguard https://bugs.kde.org/show_bug.cgi?id=413901 system settings https://bugs.kde.org/show_bug.cgi?id=414118 I opened konsole again and ran coredumpctl gdb. I ran bt and thread apply all bt full. I opened Kate 19.12.1 and copied the coredumpctl gdb output to kate. I saved the output to a file. I pasted additional output to Kate and remove a line. I saved the file. Kate showed Not Responding in its title bar for a few seconds, and its colors faded. Kate aborted with the error "The Wayland connection broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1. The underlying problem might be in Qt particularly qtwayland. -- Backtrace: Application: Kate (kate), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fedf88b0c80 (LWP 3884))] Thread 12 (Thread 0x7fedbaffd700 (LWP 3895)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb3380) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb3330, cond=0x558e00bb3358) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb3358, mutex=0x558e00bb3330) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb3330, cond=0x558e00bb3358) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb4690) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fedf7215583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fedbb7fe700 (LWP 3894)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb3380) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb3330, cond=0x558e00bb3358) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb3358, mutex=0x558e00bb3330) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb3330, cond=0x558e00bb3358) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb4650) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fedf7215583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fedbbfff700 (LWP 3893)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558e00bb2c78) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x558e00bb2c28, cond=0x558e00bb2c50) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x558e00bb2c50, mutex=0x558e00bb2c28) at pthread_cond_wait.c:638 #3 0x7fedde22ab0b in cnd_wait (mtx=0x558e00bb2c28, cond=0x558e00bb2c50) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x558e00bb1cb0) at ../src/util/u_queue.c:275 #5 0x7fedde22a71b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fedf60f5482 in start_thread (arg=) at
[plasmashell] [Bug 416291] Plasma Dialogs inappropriately respond to window tiling keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=416291 --- Comment #2 from David Edmundson --- >We should really fix this centrally rather than adding hacks into every >widget's expanded representation. +++ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416280] Okular crashes when external DisplayLink displays are lost
https://bugs.kde.org/show_bug.cgi?id=416280 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||aa...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- It seems to me this is a bug that was fixed in Qt 5.14 Can you please wait until neon updates to Qt 5.14 and tell us if this still crashes for you? Sadly there's not much we can do in our side -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416289] 7.0.0-beta2 crash when closing Geolocation Editor
https://bugs.kde.org/show_bug.cgi?id=416289 --- Comment #4 from Maik Qualmann --- Git commit 537345be7223394c47c7b41629b2997f706e3bd3 by Maik Qualmann. Committed on 15/01/2020 at 21:47. Pushed by mqualmann into branch 'master'. try to fix crash under OSX M +0-1 core/dplugins/generic/metadata/geolocationedit/dialog/geolocationedit.cpp M +2-1 core/utilities/geolocation/geoiface/bookmark/gpsbookmarkowner.cpp https://invent.kde.org/kde/digikam/commit/537345be7223394c47c7b41629b2997f706e3bd3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 416229] Zooming out with CTRL+mousewheel does not work correctly anymore
https://bugs.kde.org/show_bug.cgi?id=416229 Albert Astals Cid changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #7 from Albert Astals Cid --- I guess then we can mark it as duplicate. At some point we should either remove trim margins or someone should fix all its bugs *** This bug has been marked as a duplicate of bug 342003 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 342003] Trim margins confuses ordering of zoom steps while zooming out
https://bugs.kde.org/show_bug.cgi?id=342003 Albert Astals Cid changed: What|Removed |Added CC||j...@van-spaandonk.nl --- Comment #14 from Albert Astals Cid --- *** Bug 416229 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416291] Plasma Dialogs inappropriately respond to window tiling keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=416291 --- Comment #1 from Nate Graham --- We should really fix this centrally rather than adding hacks into every widget's expanded representation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416291] Plasma Dialogs inappropriately respond to window tiling keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=416291 Nate Graham changed: What|Removed |Added Summary|widget placed on plasma |Plasma Dialogs |panel can be tiled |inappropriately respond to ||window tiling keyboard ||shortcuts Ever confirmed|0 |1 CC||n...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 415541] i18n: downloadNewWhat text used in different contexts, cannot be translated correctly
https://bugs.kde.org/show_bug.cgi?id=415541 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||lei...@leinir.dk --- Comment #4 from Albert Astals Cid --- Dan can you please fix this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 --- Comment #6 from Konrad Materka --- It is not fixed. It is possible that this works for you, because: * you opened menu once, second time it works correctly * your panel is located on the top Anyway, this is a bug in Dropbox client (not the first one, second is Bug 378910). The problem is that I don't even know how to report it... I was not able to find any bug tracker, there is only a forum with basically no support for Linux. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416278] Downward caret next to Back/Forward icons in toolbar
https://bugs.kde.org/show_bug.cgi?id=416278 --- Comment #2 from Christoph Feck --- I am already running the improved version, and can confirm the arrows are barely noticeable. But I think it makes sense to keep them to let users know there is a pop-down menu hidden there. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 413058] Konsole aborted when Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413058 Matt Fagnani changed: What|Removed |Added Version|19.08.0 |19.12.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 413058] Konsole aborted when Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413058 --- Comment #1 from Matt Fagnani --- Created attachment 125158 --> https://bugs.kde.org/attachment.cgi?id=125158=edit New crash information added by DrKonqi konsole (19.12.1) using Qt 5.13.2 - What I was doing when the application crashed: I was running Plasma 5.17.5 on Wayland in Fedora Rawhide with Qt 5.13.2, KF 5.66.0, Mesa 19.3.2. I opened Konsole 19.2.1. I opened a second tab. I ran coredumpctl gdb on a kwin_wayland crash which happened when logging out on the previous boot. I reported those type of kwin_wayland crashes at https://bugs.kde.org/show_bug.cgi?id=416147. The core dump file was 2.1 GB, and it took a few minutes for coredumpctl gdb to decompress and process the core dump. I ran bt in gdb to get a trace. Konsole stopped responding for about a minute with Not Responding in the title bar. Konsole's colours faded. Konsole disappeared. The trace in Dr. Konqi showed the error "The Wayland connection broke. Did the Wayland compositor die?" in frame 9 of the crashing thread 1. I've previously seen Konsole abort with that error as in my previous report here. I've also seen that error for plasmashell https://bugs.kde.org/show_bug.cgi?id=414116 ksysguard https://bugs.kde.org/show_bug.cgi?id=413901 system settings https://bugs.kde.org/show_bug.cgi?id=414118 The underlying problem might be in Qt particularly qtwayland. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f99fb711899 in __GI_abort () at abort.c:79 #8 0x7f99f9de6b25 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1907 #9 QMessageLogger::fatal (this=this@entry=0x7ffce5796200, msg=msg@entry=0x7f99e8b2ee30 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:888 #10 0x7f99e8a7e84b in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:91 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 413058] Konsole aborted when Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413058 Matt Fagnani changed: What|Removed |Added CC||matthew.fagn...@utoronto.ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 --- Comment #14 from Konrad Materka --- This is true only for XEmbed: https://github.com/KDE/plasma-workspace/blob/v5.17.5/xembed-sni-proxy/sniproxy.cpp#L432 But this apps are using deprecated protocol. SNI apps can set any category they want. Looks that "Application Status" is the most popular, but this is not the rule. For example (python only): https://github.com/pwr-Solaar/Solaar/blob/1.0.1/lib/solaar/ui/tray.py#L164 https://github.com/search?l=Python=AppIndicator3.IndicatorCategory=Code At least now tray icon are ordered in a consistent way: https://phabricator.kde.org/D11352 Firstly icons are grouped by category, then sorted by name alphabetically. We can have additional configuration page in System Setting for icons ordering. Options would be something like this: * by category, then alphabetically * by (display?) name alphabetically * SNI first, then plasmoids * manual ordering It is feasible but IMO requires ordering and correct data model on C++ side. Which by confidence is what I plan to do (hopefully) :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416314] New: Gestures for activating sticky keys cannot be turned off
https://bugs.kde.org/show_bug.cgi?id=416314 Bug ID: 416314 Summary: Gestures for activating sticky keys cannot be turned off Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lucian...@gmail.com Target Milestone: --- Gestures for activating sticky keys cannot be turned off SUMMARY After unchecking 'Use gestures for activating sticky keys and slow keys' in the Accessibility system settings and rebooting, the option gets checked again, reactivating the gestures. STEPS TO REPRODUCE 1. Uncheck 'Use gestures for activating sticky keys and slow keys' 2. Reboot OBSERVED RESULT 'Use gestures for activating sticky keys and slow keys' is checked and the gestures are on after reboot. EXPECTED RESULT 'Use gestures for activating sticky keys and slow keys' is not checked and the gestures are not on after reboot or ever. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 More info: Maybe a regression of https://bugs.kde.org/show_bug.cgi?id=97425 It's definitely regressed if it's the same bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416265] Very long plasma start
https://bugs.kde.org/show_bug.cgi?id=416265 --- Comment #5 from kot040...@gmail.com --- (In reply to David Edmundson from comment #3) > I am happy to help you find a workaround if you find which process is > responsible and upload the relevant .desktop file. I did an experiment. I downloaded the applications in autorun one at a time and recorded the start time. Launch time without applications 32 seconds. Radiotray-NG 32 seconds Gxneur 32 seconds Flameshot 32 seconds Yandex.Disk indicator 32 seconds If you run these four applications together, the download will still be 32 seconds Now the following applications: MEGAsync 34 seconds Geary 37 seconds qBittorrent 44 seconds Telegram 58 seconds Download with all applications 1:57 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416313] Show hint if nothing was found at search
https://bugs.kde.org/show_bug.cgi?id=416313 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416313] New: Show hint if nothing was found at search
https://bugs.kde.org/show_bug.cgi?id=416313 Bug ID: 416313 Summary: Show hint if nothing was found at search Product: plasmashell Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: 1.0 If you search for a non existing term in the settings explorer for instance, it displays a message something like "Could not find anything". The search in the widget explorer doesn't show anything but a empty panel if nothing was found. It would look nicer if it showed at least something like a hint. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415256] Random Segmentation fault while Firefox open
https://bugs.kde.org/show_bug.cgi?id=415256 pyro4h...@gmail.com changed: What|Removed |Added Version|5.17.4 |5.17.5 --- Comment #1 from pyro4h...@gmail.com --- another one just now, and one during writing this message [10489.483756] kwin_wayland[741]: segfault at 29e62db1006a ip 7f60cf68c9ee sp 7ffcdc599630 error 4 in libKF5WaylandServer.so.5.66.0[7f60cf641000+63000] [10489.483763] Code: 08 48 85 d2 74 04 f0 83 02 01 4c 89 e0 41 5c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 49 89 fc 48 89 f7 ff 15 ca c5 05 00 <48> 8b 90 38 02 00 00 48 8b 80 40 02 00 00 49 89 14 24 49 89 44 24 [10489.483836] audit: type=1701 audit(1579122098.257:105): auid=1000 uid=1000 gid=100 ses=2 pid=741 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 [10648.776086] kwin_wayland[4507]: segfault at 40 ip 7fe7ee7fc8c0 sp 7ffe843e8578 error 4 in libKF5WaylandServer.so.5.66.0[7fe7ee7e6000+63000] [10648.776094] Code: 00 75 21 48 83 c4 10 5d 41 5c 41 5d c3 0f 1f 44 00 00 ba 08 00 00 00 be 02 00 00 00 ff 15 80 f7 08 00 eb cf ff 15 e0 f0 08 00 <48> 8b 06 48 89 07 8b 10 85 d2 74 14 83 fa ff 75 07 c3 66 0f 1f 44 [10648.776174] audit: type=1701 audit(1579122257.548:151): auid=1000 uid=1000 gid=100 ses=4 pid=4507 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416292] empty space in the panel when widget locked
https://bugs.kde.org/show_bug.cgi?id=416292 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #2 from Nate Graham --- Can you verify with the Plasma 5.18 beta which is going to be released tomorrow? I think this should be fixed there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 --- Comment #8 from Nate Graham --- That's true, you're right. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404901] google auth dialog => firefox google auth window not closed
https://bugs.kde.org/show_bug.cgi?id=404901 --- Comment #4 from Maik Qualmann --- It's not a problem, it's normal behavior ((:-)) We can also use our internal browser for Google. In principle, I would have to change the callback address at Google, only that would make all older versions of the plugin inoperative. Let's see if I can trick it. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415685] digiKam crashes when scanning faces
https://bugs.kde.org/show_bug.cgi?id=415685 --- Comment #15 from Maik Qualmann --- Git commit c2e12bc149e632ac6d1ba1365929b6bb2fcdce52 by Maik Qualmann. Committed on 15/01/2020 at 20:53. Pushed by mqualmann into branch 'master'. move create m_data back to the constructor body M +4-2core/libs/database/item/containers/iteminfo.cpp https://invent.kde.org/kde/digikam/commit/c2e12bc149e632ac6d1ba1365929b6bb2fcdce52 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 --- Comment #7 from David Edmundson --- >Easiest overall solution is to only allow one-way drag-and-drop. The danger with that is if you have asymmetric patterns you can have users drag things across one way but with no visible undo process without having to learn something new. I don't think that works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 --- Comment #6 from Nate Graham --- So basically, DND would be exclusively for the purpose of switching between "always show" and "always hide" states. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 --- Comment #5 from Nate Graham --- Easiest overall solution is to only allow one-way drag-and-drop. For bi-directional drag-and-drop, I think dragging an applet into the popup should always cause the applet to enter "always hidden" state, on the assumption that this is most likely the user's intention, and also because if it was previously "always shown" and could enter "auto-show" state, then the drag-and-drop operation might appear to do nothing if the auto-show condition was still true. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415685] digiKam crashes when scanning faces
https://bugs.kde.org/show_bug.cgi?id=415685 --- Comment #14 from Maik Qualmann --- Hmm, we have never seen a crash here, m_data does not have to be valid, even though we are under lock condition. I'm going to undo a recent change as a test. Maik -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416167] No keyboard shortcuts for going backward/forward a track
https://bugs.kde.org/show_bug.cgi?id=416167 --- Comment #6 from Nate Graham --- Very interesting. That could work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416312] Plasma crashed randomly
https://bugs.kde.org/show_bug.cgi?id=416312 David Edmundson changed: What|Removed |Added Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416167] No keyboard shortcuts for going backward/forward a track
https://bugs.kde.org/show_bug.cgi?id=416167 --- Comment #5 from Matthieu Gallien --- (In reply to Matthieu Gallien from comment #4) > (In reply to Nate Graham from comment #3) > > Thanks, that's very useful information. > > > > Matthieu, do you have any thoughts on how we should proceed here? I would > > really like to be able to use the left and right keys with no modifiers if > > possible, but obviously that conflicts with navigation in the grid views. > > Maybe we could use them with a grid view isn't focused? That might be > > inconsistent and weird though. > > Thanks Patrick and Nate for your work on this report. > > I have just tried vlc and quite like its behavior when a grid view is > focused and you press right arrow key. > > Until the focused item is not the rightmost one, it will move the focused > item. After that, the playing position will be moved. It feels natural. > > We could probably come with such a solution in Elisa. I meant that while the current item is not the rightmost one, the focused item will react to keys pressed. After that, the player will received the key pressed events. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416311] CompactRepresentation's MouseArea intercepts hover event, preventing icon from having a highlight effect
https://bugs.kde.org/show_bug.cgi?id=416311 Nate Graham changed: What|Removed |Added Summary|Applet should render icon |CompactRepresentation's |with PlasmaCore.IconItem|MouseArea intercepts hover ||event, preventing icon from ||having a highlight effect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416312] New: Plasma crashed randomly
https://bugs.kde.org/show_bug.cgi?id=416312 Bug ID: 416312 Summary: Plasma crashed randomly Product: plasmashell Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: andy3...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.11-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Using Plasma normally. I think I switched virtual desktops - Custom settings of the application: I have the custom Thermal Monitor and the Application title plugin, both got form built-in widget installer I use Kvantum, using theme Sweet I also use glava, if it helps with anything. I keep it open basically non-stop 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 0x7ff8d049ecc0 (LWP 670))] Thread 16 (Thread 0x7ff8689bb700 (LWP 2004)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff8d4b2dda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff8d689b18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff8d689b41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7ff86a7fd700 (LWP 1916)): #0 0x7ff8d479f9ef in poll () at /usr/lib/libc.so.6 #1 0x7ff8d3008120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7ff86b7ff700 (LWP 1914)): #0 0x7ff8d479b42c in read () at /usr/lib/libc.so.6 #1 0x7ff8d2fb89f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30069e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d30080c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7ff898ec0700 (LWP 1913)): #0 0x7ff8d479f9ef in poll () at /usr/lib/libc.so.6 #1 0x7ff8d3008120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7ff8d30081f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7ff8d4d5acdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7ff8d4d0139c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff8d4b26e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7ff8998c1700 (LWP 1911)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7ff8d4b2dda2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7ff8d689b18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7ff8d689b41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7ff8d4b27fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7ff8d3f674cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7ff8d47aa2d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7ff89a8c2700 (LWP 1311)): #0 0x7ff8d3f6dc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff8d4b2dcc4 in QWaitCondition::wait(QMutex*,
[elisa] [Bug 416167] No keyboard shortcuts for going backward/forward a track
https://bugs.kde.org/show_bug.cgi?id=416167 --- Comment #4 from Matthieu Gallien --- (In reply to Nate Graham from comment #3) > Thanks, that's very useful information. > > Matthieu, do you have any thoughts on how we should proceed here? I would > really like to be able to use the left and right keys with no modifiers if > possible, but obviously that conflicts with navigation in the grid views. > Maybe we could use them with a grid view isn't focused? That might be > inconsistent and weird though. Thanks Patrick and Nate for your work on this report. I have just tried vlc and quite like its behavior when a grid view is focused and you press right arrow key. Until the focused item is not the rightmost one, it will move the focused item. After that, the playing position will be moved. It feels natural. We could probably come with such a solution in Elisa. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414013] Kmail asks for password when gssapi should be used
https://bugs.kde.org/show_bug.cgi?id=414013 --- Comment #3 from mgres...@gmail.com --- Sorry, fedora packages are still on 19.04.3 version. So I did not verify whether the bug is fixed or not in 19.12. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416311] Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416311 --- Comment #1 from David Edmundson --- It's not quite as described. There is an IconItem, but the parent MouseArea is intercepting the hover event and not propogating downwards. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416310] Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416310 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED Keywords||junior-jobs Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393428] Animate new icons appearing in applet
https://bugs.kde.org/show_bug.cgi?id=393428 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org --- Comment #1 from Nate Graham --- Yeah, this would be rather nice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416311] Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416311 David Edmundson changed: What|Removed |Added Keywords||junior-jobs Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401012] keyboard indicator text is barely visible in system tray settings when using a dark theme for Plasma
https://bugs.kde.org/show_bug.cgi?id=401012 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #2 from Nate Graham --- Fixes now in Plasma 5.18. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386880] Plasma doesn't automatically detect system tray widgets
https://bugs.kde.org/show_bug.cgi?id=386880 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #6 from Nate Graham --- Cannot reproduce anymore in Plasma 5.18 when using kpackagetool or downloading widgets from store.kde.oreg using GHNS. Can you? The beta is released tomorrow; you can check with that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367815] Panel's widgets' expanded representations should close when user clicks on an empty area of the task manager
https://bugs.kde.org/show_bug.cgi?id=367815 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Summary|Panel's widgets' popup |Panel's widgets' expanded |menus should close when |representations should |user clicks on an empty |close when user clicks on |area of the task manager|an empty area of the task ||manager Component|System Tray |Panel Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 --- Comment #4 from David Edmundson --- But what about when you drag the other way? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391420] Add screen rotation icon to "Extra Items" section so it can be omitted when "Always show all entries" is checked
https://bugs.kde.org/show_bug.cgi?id=391420 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Nate Graham --- Effectively fixed (or at least no longer relevant) in the Plasma 5.18 UI redesign. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #8 from Nate Graham --- We decided not to do this. Instead we went for an alternative approach: Applets are now grouped into logical sections and retain their positions in those sections. So at least they shouldn't jump around anymore, and the ordering will never change. If everyone hates this after a few releases, we can consider alternatives. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416310] Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416310 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=400295 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400295] Some tray icons aren't highlighted upon hovering over them with mouse cursor
https://bugs.kde.org/show_bug.cgi?id=400295 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=416310, ||https://bugs.kde.org/show_b ||ug.cgi?id=416311 Status|CONFIRMED |RESOLVED --- Comment #6 from Nate Graham --- This needs bugs filed against those two remaining items; there's nothing we can do here. Here, have some bugs: - Notifications: Bug 416311 - Battery: 416310 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416311] Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416311 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=400295 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415685] digiKam crashes when scanning faces
https://bugs.kde.org/show_bug.cgi?id=415685 --- Comment #13 from Vitalii Tymchyshyn --- One more backtrace, now during recognizing: [New Thread 0x7fff397fa700 (LWP 24504)] [New Thread 0x7fff40a37700 (LWP 24505)] Thread 1 "digikam" received signal SIGSEGV, Segmentation fault. 0x74342730 in QString::operator=(QString const&) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 (gdb) bt #0 0x74342730 in QString::operator=(QString const&) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #1 0x7708b374 in Digikam::ItemInfo::ItemInfo (this=0x7fffbee8, record=...) at /b/dktemp/digikam-master/core/libs/database/item/containers/iteminfo.cpp:45 #2 0x76af01a0 in Digikam::ItemInfoJob::slotData (this=0x1d6b868, records=...) at /b/dktemp/digikam-master/core/utilities/maintenance/iteminfojob.cpp:174 #3 0x744c6a56 in ?? () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #4 0x7712d175 in Digikam::DBJobsThread::data (this=, _t1=...) at /b/dktemp/digikam-master/build/core/libs/database/digikamdatabase_src_automoc.dir/moc_dbjobsthread_36KIDXXBTBIVQQ.cpp:162 #5 0x744bef73 in QObject::event(QEvent*) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #6 0x7503d29c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Widgets.so.5 #7 0x750444c0 in QApplication::notify(QObject*, QEvent*) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Widgets.so.5 #8 0x74490868 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #9 0x744937fa in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #10 0x744e8de3 in ?? () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #11 0x7fffee5a9417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fffee5a9650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fffee5a96dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x744e847c in QEventDispatcherGlib::processEvents(QFlags) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #15 0x7448f262 in QEventLoop::exec(QFlags) () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #16 0x74498080 in QCoreApplication::exec() () from /tmp/.mount_digika64EwnA/usr/lib/libQt5Core.so.5 #17 0x0040580d in main (argc=1, argv=) at /b/dktemp/digikam-master/core/app/main/main.cpp:336 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416310] New: Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416310 Bug ID: 416310 Summary: Applet should render icon with PlasmaCore.IconItem Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 That way it will get a highlight effect when the cursor passes over it in the system tray. See Bug 400295 for more details. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416311] New: Applet should render icon with PlasmaCore.IconItem
https://bugs.kde.org/show_bug.cgi?id=416311 Bug ID: 416311 Summary: Applet should render icon with PlasmaCore.IconItem Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: n...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 That way it will get a highlight effect when the cursor passes over it in the system tray. See Bug 400295 for more details. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411098] Allow drag and drop hidden systray items to the systray
https://bugs.kde.org/show_bug.cgi?id=411098 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- A thing that's in the expanded pop-up is going to be in the "Always hidden" or "auto-show" state; it will never be in the "always shown" state. So I think if we implement DND, the most obvious way to do it would be to make the items that are dragged-and-dropped into the active zone just be "always shown". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402346] The digikamrc file is not recorded into the digikam directory
https://bugs.kde.org/show_bug.cgi?id=402346 --- Comment #8 from Loukournan29 --- (In reply to Loukournan29 from comment #7) I want to precise that the %APPLOCALDATA%/digikam directory is created by the installation, but the digikamrc file is not stored in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362077] seperate widgets and "tray icons"
https://bugs.kde.org/show_bug.cgi?id=362077 --- Comment #13 from Nate Graham --- All the apps wind up in the "Application Status" category, no? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action
https://bugs.kde.org/show_bug.cgi?id=365308 Nate Graham changed: What|Removed |Added CC||tho...@tanghus.net --- Comment #29 from Nate Graham --- *** Bug 350944 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350944] Clicking on systray icon yields unpredictable result
https://bugs.kde.org/show_bug.cgi?id=350944 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Nate Graham --- *** This bug has been marked as a duplicate of bug 365308 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365308] Left clicking on some system tray icons results in no action
https://bugs.kde.org/show_bug.cgi?id=365308 --- Comment #28 from Nate Graham --- Konrad, is there nothing we can do here? If not, we should close the bug as RESOLVED DOWNSTREAM. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402392] dropbox system tray menu positioned off-screen
https://bugs.kde.org/show_bug.cgi?id=402392 --- Comment #5 from Nate Graham --- Konrad, is this fixed in Plasma 5.18? I'm using Dropbox and I don't see the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373087] prefer icons from icon theme and only use Plasma theme icons as fallbacks
https://bugs.kde.org/show_bug.cgi?id=373087 Nate Graham changed: What|Removed |Added Summary|Fall back to icon from the |prefer icons from icon |general icon theme when no |theme and only use Plasma |icon from the Plasma theme |theme icons as fallbacks |is available| --- Comment #4 from Nate Graham --- In principle this request makes sense, and I'd like to move towards removing all icons from the Plasma theme and having everything always use icons from the icon theme. However a practical challenge here is that we currently use Plasma theme icons to force some large icons to be monochrome-only. For example, the Show Desktop widget's icon. If we always use icons from the icon theme, we'd need to make sure we don't lose the ability to do this, or else we'll be back to panel icons changing from monochrome to colorful based on the panel height. This seems quite unnerving to many users and we get bug reports about it. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 416309] New: Single quote appears twice in inline math mode
https://bugs.kde.org/show_bug.cgi?id=416309
Bug ID: 416309
Summary: Single quote appears twice in inline math mode
Product: kile
Version: 2.9.93
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: editor
Assignee: michel.lud...@kdemail.net
Reporter: abhinav.s.deshpa...@gmail.com
Target Milestone: ---
SUMMARY
When in inline math mode (i.e. in between two `$` characters), typing a single
quote (') automatically adds two single quotes ('') instead. This is
undesirable since several mathematical symbols I use are defined with a single
' character and not two.
I would be very pleased if someone could suggest where in the source code this
feature is written, so that I could tweak/patch it myself. I tried checking
several files in `src/`, specifically `src/editorextension.cpp` and
`src/codecompletion.cpp` but couldn't find the piece of code that adds
automatic closing brackets and quotation marks.
Thanks,
Abhinav
STEPS TO REPRODUCE
1. Enable Automatic Brackets in Settings-> Configure Kile-> Editing-> Auto
Brackets->Enable automatic brackets
2. Go to math mode either through a shortcut or by typing `$ $` manually.
Navigate to any cursor position between the $ signs and type `'`.
OBSERVED RESULT
Kile automatically adds two instances of the character (`''`).
EXPECTED RESULT
Inline math mode should behave the same as other modes: only a single character
should be added.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux (x86_64) release 5.4.11-arch1-1
(available in About System)
KDE Plasma Version:
KDE Frameworks Version: KDE Frameworks 5.66.0
Qt Version: Qt 5.14.0 (built against 5.14.0)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
