[kwin] [Bug 393627] Crash in kwin_wayland, maybe related to pointer locking
https://bugs.kde.org/show_bug.cgi?id=393627 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug symbols and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393627] Crash in kwin_wayland, maybe related to pointer locking
https://bugs.kde.org/show_bug.cgi?id=393627 Martin Flöser changed: What|Removed |Added Attachment #112302|text/x-log |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366305] Add a message at startup about the lack of temporary space to perform Undo operations
https://bugs.kde.org/show_bug.cgi?id=366305 Maik Qualmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dig ||ikam/9897334755437d8da7cfc4 ||b0cf0a7252ec6788d4 Version Fixed In||6.0.0 Resolution|--- |FIXED --- Comment #9 from Maik Qualmann --- Git commit 9897334755437d8da7cfc4b0cf0a7252ec6788d4 by Maik Qualmann. Committed on 29/04/2018 at 06:32. Pushed by mqualmann into branch 'master'. show message box if free disk space for the undo file is < 2GiB FIXED-IN: 6.0.0 M +2-1NEWS M +31 -6core/utilities/imageeditor/core/undocache.cpp https://commits.kde.org/digikam/9897334755437d8da7cfc4b0cf0a7252ec6788d4 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371574] Dolphin crashes after Konsole-button related operations
https://bugs.kde.org/show_bug.cgi?id=371574 --- Comment #6 from Haruki Arita --- Thank you for your reply. I can reproduce this bug today with Leap 42.3 in the first-described procedure, so I think the initial explanation may be misleading. I write below revised method and please try this. 1. Create folder named ”テスト” in home directory. 2. Create folder named ”test” in テスト folder. 3. Start Dolphin which displays home directory. 4. Start another Dolphin window which displays home directory. Operations below do in the Dolphin window which is created in 4. 5. Click folder named テスト. 6. Click folder named test. 7. Click Konsole launching button in toolbar.(You may need to configure this button in Dolphin setting.) 8. Close a Konsole window. 9. At a Dolphin window, click Home in address bar. 10. Close a Dolphin window 11. Crash! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393204] Wishlist - Enhancement within Investment Tab
https://bugs.kde.org/show_bug.cgi?id=393204 Jack changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Severity|normal |wishlist --- Comment #1 from Jack --- I suspect this would be more involved than you think, as it is not specific to the equity/stock/bond itself, but to every purchase transaction. However, I think this is likely to be addressed whenever the team does get to a major redo of how investments are handled. The added columns would need to also include date of purchase as that would determine the tax implications, at least in areas where there is a difference between long term and short term investments. (In the US, short term gains, under one year, are taxed as regular income, but long term gains (held over one year) are taxed at a lower rate.) -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 393631] New: Paired Bluetooth devices not connecting when resumed from sleep after upgrading to Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=393631 Bug ID: 393631 Summary: Paired Bluetooth devices not connecting when resumed from sleep after upgrading to Kubuntu 18.04 Product: Bluedevil Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: daemon Assignee: now...@gmail.com Reporter: raj.am...@gmail.com Target Milestone: --- I recently upgraded to Kubuntu 18.04 from 17.10. After Wakeup from Suspend my paired Bluetooth device (Headphone) do not connect with the system. This was working fine in 17.10. After reboot it connects fine. Temporary fix, Restarting the Bluetooth service after each wakeup fixes this issue, sudo service bluetooth restart Or I need to remove the paired device and re pair it each time. -- You are receiving this mail because: You are watching all bug changes.
[ksystraycmd] [Bug 393630] New: System tray icons not clickable and collapsible when a entry visibility is changed to hidden
https://bugs.kde.org/show_bug.cgi?id=393630 Bug ID: 393630 Summary: System tray icons not clickable and collapsible when a entry visibility is changed to hidden Product: ksystraycmd Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: raj.am...@gmail.com Target Milestone: --- When the visibility of a system tray entry is changed from Auto to hidden, the rest of the visible icons are not clickable and the expanded hidden icons popup cannot be closed via down arrow icon. To replicate, 1. Open System tray settings 2. Select clipboard visibility to hidden and apply. 3. Now try clicking any other visible icons like Network or Wifi, it just expands the hidden icons instead of opening the specific system tray setting. Temporary fix, Reboot fixes this issue. OS: Kubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393413] Dolphin crash when previewing mp4
https://bugs.kde.org/show_bug.cgi?id=393413 --- Comment #3 from joelishn...@gmail.com --- I tried to duplicate just now and the issue did not reoccur - video preview played as expected. So not consistent. extra/dolphin 18.04.0-1 (kde-applications kdebase) [installed: 17.12.3-1] extra/qt5-base 5.10.1-7 (qt qt5) [installed] -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393629] New: Vertical tabs does not remember shown or hidden status
https://bugs.kde.org/show_bug.cgi?id=393629 Bug ID: 393629 Summary: Vertical tabs does not remember shown or hidden status Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: kishor...@gmail.com Target Milestone: --- If I have the 'vertical tabs' extension enabled, it does not remember whether I currently have the 'vertical tabs' sidebar shown or hidden. Instead, it is always shown when I open a new window. My use case is that I would like to use it only when I have a lot of tabs open, but hide it when I only have a few tabs. Currently, I have to either use the 'tab manager' sidebar (which is frankly a bit of an overkill if I'm just using it for tab switching) or go into the settings and enable the 'vertical tabs' extension only when I want to use it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #9 from walker...@msn.com --- (In reply to walker275 from comment #8) > (In reply to Boudewijn Rempt from comment #7) > > First, are you using appimages, or distribution packages? If appimages, just > > start a terminal and start krita, with ./krita-4.0.1-x86_64.appimage in the > > directory where the appimage is > > Appimage Okay it says this ./krita-4.0.1-x86_64.appimage: No such file or directory So instead of downloading it just install it? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393628] New: Dolphin Fechou ao Desmontar Pendrive por Modo Gráfico
https://bugs.kde.org/show_bug.cgi?id=393628 Bug ID: 393628 Summary: Dolphin Fechou ao Desmontar Pendrive por Modo Gráfico Product: dolphin Version: 18.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dehhar...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.0) Qt Version: 5.10.1 Frameworks Version: 5.45.0 Operating System: Linux 4.16.4-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Estava copiando arquivos .mp3 de uma pasta do meu HD para um pendrive, após finalizar a cópia cliquei na ação para Remover o Dispositivo com Segurança. Neste momento o Dolphin fechou e relatou o erro. - Unusual behavior I noticed: -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe027be0800 (LWP 1957))] Thread 4 (Thread 0x7fdffc197700 (LWP 1961)): #0 0x7fe027479cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fe019e26523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe019e2663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe021681254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe02162331b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe02143271e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe021437abd in () at /usr/lib/libQt5Core.so.5 #7 0x7fe01c4b70bc in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe0274842ff in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe00dfdb700 (LWP 1960)): #0 0x7fe027479cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fe019e26523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe019e2663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe021681254 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe02162331b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe02143271e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fe021aa4416 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fe021437abd in () at /usr/lib/libQt5Core.so.5 #8 0x7fe01c4b70bc in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fe0274842ff in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe010555700 (LWP 1959)): #0 0x7fe027479cd9 in poll () at /usr/lib/libc.so.6 #1 0x7fe019765180 in () at /usr/lib/libxcb.so.1 #2 0x7fe019766e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fe0130ef82a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fe021437abd in () at /usr/lib/libQt5Core.so.5 #5 0x7fe01c4b70bc in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe0274842ff in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fe027be0800 (LWP 1957)): [KCrash Handler] #6 0x7fe0277bb194 in () at /usr/lib/libkdeinit5_dolphin.so #7 0x7fe0277bb4d5 in () at /usr/lib/libkdeinit5_dolphin.so #8 0x7fe027789348 in () at /usr/lib/libkdeinit5_dolphin.so #9 0x7fe02165572f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #10 0x7fe0277d6cd6 in () at /usr/lib/libkdeinit5_dolphin.so #11 0x7fe02165572f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7fe0277d6ab6 in () at /usr/lib/libkdeinit5_dolphin.so #13 0x7fe02165572f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #14 0x7fe0277d6b13 in () at /usr/lib/libkdeinit5_dolphin.so #15 0x7fe0277b8671 in () at /usr/lib/libkdeinit5_dolphin.so #16 0x7fe02165572f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #17 0x7fe0254c7916 in Solid::StorageAccess::teardownRequested(QString const&) () at /usr/lib/libKF5Solid.so.5 #18 0x7fe0254ca59a in () at /usr/lib/libKF5Solid.so.5 #19 0x7fe021655606 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #20 0x7fe0254c6746 in () at /usr/lib/libKF5Solid.so.5 #21 0x7fe0254b6512 in () at /usr/lib/libKF5Solid.so.5 #22 0x7fe0254cab8e in () at /usr/lib/libKF5Solid.so.5 #23 0x7fe0254cea06 in () at /usr/lib/libKF5Solid.so.5 #24 0x7fe021aafb5d in () at /usr/lib/libQt5DBus.so.5 #25 0x7fe021656052 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7fe02262cfec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #27 0x7fe0226349c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #28 0x7fe021624ce0 in QCoreApplication::no
[systemsettings] [Bug 391880] Missing icons in dark theme in KDE System Settings
https://bugs.kde.org/show_bug.cgi?id=391880 --- Comment #8 from Andrew Hall --- Almost forgot. It might be helpful if I listed the package versions for the actual theme as well. breeze-icon-theme-5.44.0-1.fc27 plasma-breeze-5.12.4-1.fc27 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391880] Missing icons in dark theme in KDE System Settings
https://bugs.kde.org/show_bug.cgi?id=391880 Andrew Hall changed: What|Removed |Added CC||andrew.hall...@gmail.com --- Comment #7 from Andrew Hall --- Created attachment 112303 --> https://bugs.kde.org/attachment.cgi?id=112303&action=edit Broken icons in System Settings (Breeze Light) This bug appears to happen with Breeze as wellso I don't think it's specifically Breeze Dark related. Version: plasma-systemsettings-5.12.4-1.fc27 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393627] New: Crash in kwin_wayland, maybe related to pointer locking
https://bugs.kde.org/show_bug.cgi?id=393627 Bug ID: 393627 Summary: Crash in kwin_wayland, maybe related to pointer locking Product: kwin Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: farmb...@googlemail.com Target Milestone: --- Created attachment 112302 --> https://bugs.kde.org/attachment.cgi?id=112302&action=edit gdb backtrace output I am running a wine game in a virtual window which has the pointer locked. But switching between wine virtual desktop window and different windows the pointer will not be consistently locked when switching back to wine. MAYBE this is related to this crash. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 389164] Spectacle on wayland interface causes screen refresh
https://bugs.kde.org/show_bug.cgi?id=389164 --- Comment #8 from Henrik Fehlauer --- Thanks for the info, Martin! Nothing to solve in the short term, but good to keep in mind for a future adaptation of Spectacle to the slightly different conditions on Wayland. One more thought: Could we change how the confirmation message works? Currently KWin asks first, and then captures a screenshot. What if KWin captured the screenshot directly, and only handed over this screenshot once the user confirmed? (Would this need some kind of DoS protection?) This is relevant both for the "context menu" case, as well as for "immediately capture this video frame upon pressing Print". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 393595] regression: show HTML side bar setting checkbox no longer exists in settings - Appearance - General
https://bugs.kde.org/show_bug.cgi?id=393595 whatifgodwasoneo...@hotmail.com changed: What|Removed |Added CC||whatifgodwasoneofus@hotmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393626] New: Plasma crashes randomly during coding/browsing
https://bugs.kde.org/show_bug.cgi?id=393626 Bug ID: 393626 Summary: Plasma crashes randomly during coding/browsing Product: plasmashell Version: 5.12.4 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zheltonozhs...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.4) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-3-amd64 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: Wring code in CLion and switching to browser (firefox) by Alt-tab. The screen gets black seemingly without connection to what I am doing. - Custom settings of the application: The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3ad14c6c0 (LWP 1431))] Thread 15 (Thread 0x7ff2b27fc700 (LWP 2131)): #0 0x7ff3a5f7a4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x555a548a7400) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x555a548a73b0, cond=0x555a548a73d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x555a548a73d8, mutex=0x555a548a73b0) at pthread_cond_wait.c:655 #3 0x7ff3a6dbdfbb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x555a548a73b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x555a5625b9b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7ff2eb51d99b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x555a53cfb3b0, th=) at ./src/weaver.cpp:594 #6 0x7ff2eb51e745 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x555a53cfb3b0, th=, th@entry=0x7ff2b8004db0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ./src/weaver.cpp:554 #7 0x7ff2eb522818 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x7ff2b8004db0, wasBusy=) at ./src/workinghardstate.cpp:66 #8 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7ff2b8004db0, wasBusy=) at ./src/weaver.cpp:568 #9 0x7ff2eb522872 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x7ff2b8004db0, wasBusy=) at ./src/workinghardstate.cpp:73 #10 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x7ff2b8004db0, wasBusy=) at ./src/weaver.cpp:568 #11 0x7ff2eb5206db in ThreadWeaver::Thread::run (this=0x7ff2b8004db0) at ./src/thread.cpp:103 #12 0x7ff3a6dbcb4f in QThreadPrivate::start (arg=0x7ff2b8004db0) at thread/qthread_unix.cpp:376 #13 0x7ff3a5f745aa in start_thread (arg=0x7ff2b27fc700) at pthread_create.c:463 #14 0x7ff3a66c4cbf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7ff2b2ffd700 (LWP 2130)): #0 0x7ff3a5f7a4ec in futex_wait_cancelable (private=, expected=0, futex_word=0x555a548a7400) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x555a548a73b0, cond=0x555a548a73d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x555a548a73d8, mutex=0x555a548a73b0) at pthread_cond_wait.c:655 #3 0x7ff3a6dbdfbb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x555a548a73b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x555a5625b9b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7ff2eb51d99b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x555a53cfb3b0, th=) at ./src/weaver.cpp:594 #6 0x7ff2eb51e745 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x555a53cfb3b0, th=, th@entry=0x555a562bafd0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ./src/weaver.cpp:554 #7 0x7ff2eb522818 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x555a562bafd0, wasBusy=) at ./src/workinghardstate.cpp:66 #8 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x555a562bafd0, wasBusy=) at ./src/weaver.cpp:568 #9 0x7ff2eb522872 in ThreadWeaver::WorkingHardState::applyForWork (this=0x555a56051d50, th=0x555a562bafd0, wasBusy=) at ./src/workinghardstate.cpp:73 #10 0x7ff2eb51d8fd in ThreadWeaver::Weaver::applyForWork (this=, th=0x555a562bafd0, wasBusy=) at ./src/weaver.cpp:568 #11 0x7ff2eb5206db in ThreadWeaver::Thr
[kmymoney] [Bug 393204] Wishlist - Enhancement within Investment Tab
https://bugs.kde.org/show_bug.cgi?id=393204 Michael Carpino changed: What|Removed |Added Summary|Enhancement within |Wishlist - Enhancement |Investment Tab |within Investment Tab -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393607] Background colour on unusual unicode characters looks weird
https://bugs.kde.org/show_bug.cgi?id=393607 --- Comment #2 from Salvo "LtWorf" Tomaselli --- The terminal application (which I wrote) does no special handling of unicode at all. Just expects every kind of vehicle to have length = 1 character. It has no idea of widths. So that's more likely konsole's doing. It uses the API from västtrafik, so only works on this county. https://github.com/ltworf/pysttrafik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391060] crashes on undo of very large tif
https://bugs.kde.org/show_bug.cgi?id=391060 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/3a8b71fa6224a172f4ba7f ||54ee64362d171d3480 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||6.0.0 --- Comment #3 from Maik Qualmann --- Git commit 3a8b71fa6224a172f4ba7f54ee64362d171d3480 by Maik Qualmann. Committed on 28/04/2018 at 22:33. Pushed by mqualmann into branch 'master'. replace QByteArray with DImg buffer to write undo files larger than 2gb FIXED-IN: 6.0.0 M +2-1NEWS M +13 -6core/utilities/imageeditor/core/undocache.cpp https://commits.kde.org/digikam/3a8b71fa6224a172f4ba7f54ee64362d171d3480 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366391] rotating an image seems to forget to reset the orientation flag
https://bugs.kde.org/show_bug.cgi?id=366391 --- Comment #15 from caulier.gil...@gmail.com --- I'm agree with Maik. The puzzle is already enough complex to not increase it to introduce this feature. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393625] New: Can't access or browse ntfs partition
https://bugs.kde.org/show_bug.cgi?id=393625 Bug ID: 393625 Summary: Can't access or browse ntfs partition Product: dolphin Version: 18.04.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: akontsev...@gmail.com Target Milestone: --- Recent time can't access access or browse ntfs partition in Dolphin. Have normal rw access via shell or mc. Found workaround to enter path manually in address bar. In tree view file open dialog can't view ntfs mounts or browse them at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 385187] Baloo crashed
https://bugs.kde.org/show_bug.cgi?id=385187 Jonathan Dotson changed: What|Removed |Added CC||dotso...@gmail.com --- Comment #2 from Jonathan Dotson --- I have the same issue on Fedora 27. This is new problem. for me it happens when i'm booting. It happens every time. Below is the info: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fba76430500 (LWP 2801))] Thread 3 (Thread 0x7fba57f8b700 (LWP 2879)): #0 0x7fba729c0c6b in poll () from /lib64/libc.so.6 #1 0x7fba6dc90e99 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fba6dc90fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fba73816c4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fba737c496a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fba736158ca in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fba74fe5449 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7fba73619de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7fba718c450b in start_thread () from /lib64/libpthread.so.0 #9 0x7fba729cb16f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fba61763700 (LWP 2830)): #0 0x7fba729c0c6b in poll () from /lib64/libc.so.6 #1 0x7fba6d619fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7fba6d61bdda in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7fba64301bf9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7fba73619de2 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fba718c450b in start_thread () from /lib64/libpthread.so.0 #6 0x7fba729cb16f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fba76430500 (LWP 2801)): [KCrash Handler] #6 0x7fba7290a660 in raise () from /lib64/libc.so.6 #7 0x7fba7290bc41 in abort () from /lib64/libc.so.6 #8 0x7fba74dcab22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x7fba74dbfb85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x7fba74dc0d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x7fba74dc2c74 in mdb_page_new () from /lib64/liblmdb.so.0.0.0 #12 0x7fba74dc3079 in mdb_node_add () from /lib64/liblmdb.so.0.0.0 #13 0x7fba74dc65a9 in mdb_cursor_put () from /lib64/liblmdb.so.0.0.0 #14 0x7fba74dc892b in mdb_put () from /lib64/liblmdb.so.0.0.0 #15 0x7fba756895fc in Baloo::PostingDB::put(QByteArray const&, QVector const&) () from /lib64/libKF5BalooEngine.so.5 #16 0x7fba756957d0 in Baloo::WriteTransaction::commit() () from /lib64/libKF5BalooEngine.so.5 #17 0x7fba7568ec62 in Baloo::Transaction::commit() () from /lib64/libKF5BalooEngine.so.5 #18 0x555a32347acc in Baloo::App::processNextFile() () #19 0x7fba737fa934 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #20 0x7fba737ef21b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7fba7443292c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7fba7443a174 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7fba737c5be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7fba73815f5b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #25 0x7fba73816829 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #26 0x7fba6dc90b77 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #27 0x7fba6dc90f20 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #28 0x7fba6dc90fac in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #29 0x7fba73816c2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7fba737c496a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #31 0x7fba737cd094 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #32 0x555a32346a2f in main () -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393541] Wrong timezone on imported invitation
https://bugs.kde.org/show_bug.cgi?id=393541 --- Comment #9 from Roland Tapken --- Btw., libical3 isn't available for the user version of KDE neon, yet. And I didn't find it in dev/stable nor in dev/unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393624] New: Plasma freezes after some hours of inactivity
https://bugs.kde.org/show_bug.cgi?id=393624 Bug ID: 393624 Summary: Plasma freezes after some hours of inactivity Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112301 --> https://bugs.kde.org/attachment.cgi?id=112301&action=edit high ram and cpu usage Since a few days ago plasma freezes on neon dev unstable after some hours of inactivity. Clicks on wallpaper or plasma panel do nothing. When freeze happens plasma uses high amount of ram and uses an entire cpu core. See screenshot. (gdb) thread apply all bt Thread 16 (Thread 0x7f4843e68700 (LWP 8971)): #0 0x7f492ae24360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f492bf7a67b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x56bb610) at thread/qwaitcondition_unix.cpp:143 #2 0x7f492bf7a67b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x5738270, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f487a39e78f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f487a3a2868 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 ---Type to continue, or q to quit--- #5 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 ---Type to continue, or q to quit--- #11 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7f487a3a03e0 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 ---Type to continue, or q to quit--- #17 0x7f492bf796eb in QThreadPrivate::start(void*) (arg=0x574f8b0) at thread/qthread_unix.cpp:376 #18 0x7f492ae1e6ba in start_thread (arg=0x7f4843e68700) at pthread_create.c:333 #19 0x7f492b88641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f4844669700 (LWP 8970)): #0 0x7f492ae24360 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f492bf7a67b in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x56bb610) at thread/qwaitcondition_unix.cpp:143 #2 0x7f492bf7a67b in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x5738270, time=184467440737095516---Type to continue, or q to quit--- 15) at thread/qwaitcondition_unix.cpp:215 #3 0x7f487a39e78f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x7f487a3a2868 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7f487a3a28c2 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f487a39d9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f487a3a03e0 in ThreadWeaver::Thread::run() () ---Type to continue, or q to quit--- at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f492bf796eb in QThreadPrivate::start(void*) (arg=0x7f484c002e70) at thread/qthread_unix.cpp:376 #10 0x7f492ae1e6ba in start_thread (arg=0x7f48
[korganizer] [Bug 393541] Wrong timezone on imported invitation
https://bugs.kde.org/show_bug.cgi?id=393541 --- Comment #8 from Roland Tapken --- Might be the same bug as mentioned in https://github.com/libical/libical/issues/58 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 393623] New: KWalletEditor::saveEntry() does not call setFolder
https://bugs.kde.org/show_bug.cgi?id=393623 Bug ID: 393623 Summary: KWalletEditor::saveEntry() does not call setFolder Product: kwalletmanager Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: fmh...@gmail.com Target Milestone: --- KWalletEditor::saveEntry() does not call setFolder. This can result in the entry getting saved into the wrong folder. For example, if chromium is connected to the wallet at the same time you are editing an entry in kwalletmanager, the entry can wind up getting saved into chromium's folder instead of the folder you have selected in kwalletmanager. Then the next time you open kwalletmanager, the changes you made to the entry are apparently gone (really they are still there but in the wrong folder). I'm using kwalletmanager version 16.08.3 from debian stable, but from looking at your git repo, this bug still exists in the current version of kdewalletmanager. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 392725] Login sound is never played
https://bugs.kde.org/show_bug.cgi?id=392725 --- Comment #11 from k...@trummer.xyz --- Yes, I set a different file than the default one, the classic 'KDE_Startup_1.ogg' to be exact. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 392725] Login sound is never played
https://bugs.kde.org/show_bug.cgi?id=392725 --- Comment #10 from Wolfgang Bauer --- An additional note about the reproducibility: The login sound is played fine if you leave the sound file at the default (i.e. only enable it). But it does not work if you select a different (local) file. That likely explains why the other two people here were not able to reproduce the problem I think... ;-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366391] rotating an image seems to forget to reset the orientation flag
https://bugs.kde.org/show_bug.cgi?id=366391 --- Comment #14 from Maik Qualmann --- I am still of the opinion that in the attitude that metadata should be written only in the sidecar, this must be respected. If we start adding exceptions now, this will unnecessarily complicate the whole story. Anyone who wants the orientation flag to be written in the metadata of the image has the option to do so, either with writing to the image and sidecar or sidecar just for read-only files (RAW). Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393539] Wishlist: Option to save rotation information (pixel, EXIF-flag) to the file always, instead of sidecar
https://bugs.kde.org/show_bug.cgi?id=393539 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Maik Qualmann --- I think this bug is a duplicate of Bug 366391. Maik *** This bug has been marked as a duplicate of bug 366391 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366391] rotating an image seems to forget to reset the orientation flag
https://bugs.kde.org/show_bug.cgi?id=366391 Maik Qualmann changed: What|Removed |Added CC||gen...@moin.fi --- Comment #13 from Maik Qualmann --- *** Bug 393539 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 372074] cantor/octave: calling quit() and then stopping calculation crashes whole desktop
https://bugs.kde.org/show_bug.cgi?id=372074 Nikita Sirgienko changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/can ||tor/4681dc925f090228ddee58d ||e9afaa9b9e5c1749e Version Fixed In||18.04.1 Resolution|--- |FIXED --- Comment #2 from Nikita Sirgienko --- Git commit 4681dc925f090228ddee58de9afaa9b9e5c1749e by Nikita Sirgienko. Committed on 28/04/2018 at 20:19. Pushed by sirgienko into branch 'master'. Avoid octave backend crushing, when we try to kill ended process Summary: Now octave backend don't crash, but we still need to interrupt `quit` entry and restart backend. FIXED-IN: 18.04.1 Reviewers: #cantor, asemke Reviewed By: #cantor, asemke Subscribers: #cantor, #kde_edu Tags: #kde_edu, #cantor Differential Revision: https://phabricator.kde.org/D12567 M +5-2src/backends/octave/octavesession.cpp https://commits.kde.org/cantor/4681dc925f090228ddee58de9afaa9b9e5c1749e -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384919] Regression: Korganizer will not show some events
https://bugs.kde.org/show_bug.cgi?id=384919 Allen Winter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Allen Winter --- still cannot duplicate with libical 3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366391] rotating an image seems to forget to reset the orientation flag
https://bugs.kde.org/show_bug.cgi?id=366391 --- Comment #12 from Maik Qualmann --- Git commit 3c33610858367196ee6c73745f0d8a1d8d242634 by Maik Qualmann. Committed on 28/04/2018 at 20:15. Pushed by mqualmann into branch 'master'. reset exif orientation tag to normal if rotate pixels and the option is enabled M +2-1core/libs/fileactionmanager/fileworkeriface.cpp https://commits.kde.org/digikam/3c33610858367196ee6c73745f0d8a1d8d242634 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)
https://bugs.kde.org/show_bug.cgi?id=387061 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #8 from RJVB --- > As I learned now from vkrause, there is a 2MB limit inside QtWEbEngine > (http://doc.qt.io/qt-5/qwebengineview.html#setHtml). So we will have to > rework the part that pushed the content to not use setHtml and use instead a > file. Or go back to using QtWebKit (ReBooted), which is better for just about anything but full-blown browsers anyway? ;) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393622] New: Badly Rendered Font in System Settings
https://bugs.kde.org/show_bug.cgi?id=393622 Bug ID: 393622 Summary: Badly Rendered Font in System Settings Product: systemsettings Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: perdo...@gmail.com Target Milestone: --- Created attachment 112300 --> https://bugs.kde.org/attachment.cgi?id=112300&action=edit Text in the sidebar is fuzzy Fonts in the KDE system settings application, specifically in the sidebar, appear badly rendered in the latest version of KDE. I'm currently using the DPI settings of 116. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393607] Background colour on unusual unicode characters looks weird
https://bugs.kde.org/show_bug.cgi?id=393607 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #1 from Egmont Koblinger --- Note that while the tram, bus and walk symbols are "wide" according to Unicode 10.0 [1], the ferry symbol is of "ambiguous width". Such characters are handled as narrow by most terminal emulators, and also by glibc's wcwidth() function. The rest of the tabulation is also incorrect in its line, so your utility seems to assume it's also a wide character, whereas konsole handles it as narrow, i.e. taking one cell only (hence the weird background). It's another story that the actual glyph is so wide that it overflows a lot (and the bus also overflows by 1px). I'm not sure if konsole has an option to show ambiguous characters as wide, I couldn't quickly find it. But even if it has, while enabling it might fix the ferry, it probably breaks plenty of other things in other apps. (What's this tool by the way? Looks quite useful! Is it specific to Göteborg, or can it be used with any GTFS, and/or some online provider such as Google Maps?) [1] ftp://ftp.unicode.org/Public/10.0.0/ucd/EastAsianWidth.txt -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 --- Comment #8 from bugzy --- None of the other views work. The only solution to get things functional again is to disable the calendar with the problem. Additional Information: - All my calendars are webdav calendars synced using nextcloud to my various devices. - I should mention that the faulty todo entry was created using Zanshin. I did not think that was relevant until I added some new todo items yesterday and began experiencing the same problem. I use Zanshin at work and Kontact with Korganizer on laptop and home PC. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393621] New: Sound distortion when annotation is opened/made.
https://bugs.kde.org/show_bug.cgi?id=393621 Bug ID: 393621 Summary: Sound distortion when annotation is opened/made. Product: okular Version: 1.3.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alaubsche...@gmail.com Target Milestone: --- When audio is played from a browser or any other application the audio is distorted with a crackling noise when an annotation (a note) is made to a document. In other terms, when a side note is placed or opened for editing, crackling noises comes from speakers/headphones when audio is playing. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 --- Comment #2 from JonnyRobbie --- Thanks for the info. I just want to thank you for your work on RKWard. I really love it, way more then RStudio and I tend to get itchy when people act like there is no alternative leading to absurd notions like the misconception that RStudio *is* R. However there were couple of usecases I noticed from coworkers where rkward is slightly lacking behind rstudio and those are mainly those I tried to address in my bugreports/suggestions. I don't know how much time/will you have regarding those, but if I can so something to help (apart of the actual coding where I don't have the necessary experience), just tell me. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393620] New: Konsole doesn't respect monospace font configed with fontconf
https://bugs.kde.org/show_bug.cgi?id=393620 Bug ID: 393620 Summary: Konsole doesn't respect monospace font configed with fontconf Product: konsole Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: sass...@gmail.com Target Milestone: --- Firstly I wanna thank you for all your efforts on this terminal emulator. I found it the only robust emulator in linux with all the features I need. I have a minor problem with persian characters in my setup: I set a fallback font in fontconf in monospace family alias. If I add it to sans-serif alias it works as a fallback font for persian characters in Konsole. But it doesn't work when I set it in monospace alias. I should set it in monospace alias because it's a monospace font and I don't want it to be used by other non-monospace apps. Let me know if I should provide any details about my configs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 393619] New: Pressing AltGr (configured as Compose Key) on wayland, results in opening google.com
https://bugs.kde.org/show_bug.cgi?id=393619
Bug ID: 393619
Summary: Pressing AltGr (configured as Compose Key) on wayland,
results in opening google.com
Product: frameworks-kglobalaccel
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: i.ga...@brainsware.org
Target Milestone: ---
.. and since AltGr is a modifier key, it does that twice, for the next key
pressed, too!
Here's the output of dbus-monitor, which might help track this down:
```
signal time=1524933351.718393 sender=:1.2 -> destination=(null destination)
serial=305 path=/component/khotkeys; interface=org.kde.kglobalaccel.Component;
member=globalShortcutPressed
string "khotkeys"
string "{d03619b6-9b3c-48cc-9d9c-a2aadb485550}"
int64 0
method call time=1524933351.720995 sender=:1.11 ->
destination=org.freedesktop.DBus serial=335 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=AddMatch
string
"type='signal',path='/',interface='org.kde.KUriFilterPlugin',member='configure'"
signal time=1524933357.714598 sender=:1.2 -> destination=(null destination)
serial=306 path=/component/khotkeys; interface=org.kde.kglobalaccel.Component;
member=globalShortcutPressed
string "khotkeys"
string "{d03619b6-9b3c-48cc-9d9c-a2aadb485550}"
int64 0
```
--
You are receiving this mail because:
You are watching all bug changes.
[rkward] [Bug 393610] Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 Thomas Friedrichsmeier changed: What|Removed |Added CC||thomas.friedrichsmeier@ruhr ||-uni-bochum.de --- Comment #1 from Thomas Friedrichsmeier --- Thanks for all your suggestions. To answer the question for the "historical reason" why the Debugger Console is a separate window: The reason is that the R Console is not a "real" console, it's only designed to look that way. For instance if you are in the middle of writing a multi-line expression (e.g. a function definition), the R main loop is actually idle, instead of blocked waiting for the remainder of the statement. This has the important advantage that other commands (e.g. form a plugin, or a help search, or...) can be evaluated normally, without being blocked by the incomplete statement in the console. Now when debugging, R is blocked waiting for user input, which is a pretty different situation, and handled in a different window. Thus, technically, the two windows have not been decoupled, they simply have not been merged. You are probably right however, that this situation, too, could/should be handled inside the console window, somehow and/or in a window that looks much more like the console window. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393617] Transform Tool doesn't effect the Hidden Layers inside a Group as expected.
https://bugs.kde.org/show_bug.cgi?id=393617 Boudewijn Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com Status|CONFIRMED |ASSIGNED Version|4.1 |4.0.1 --- Comment #2 from Boudewijn Rempt --- Dmitry, can you take a look? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393617] Transform Tool doesn't effect the Hidden Layers inside a Group as expected.
https://bugs.kde.org/show_bug.cgi?id=393617 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Boudewijn Rempt --- I can confirm the issue, thanks for reporting. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393604] Disable semantic analysis on a per file basis
https://bugs.kde.org/show_bug.cgi?id=393604
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #1 from Sven Brauch ---
I think "touch .kdev_ignore" still works for directories. There is also the
#ifndef IN_IDE_PARSER ... #endif trick. Another workaround would be to use a
different file ending for these files (e.g. .c_arm), although that may of
course confuse other tools.
Other than that, I could imagine that an option could be added to the project
filter plugin which does this ("exclude and do not parse" or so) ...
With the right-click menu, the problem I see is a bit that you do not have a UI
which visualizes the current state of what is being ignored.
How the problem tooltips work needs rework anyways, though, they are relatively
annoying right now.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 391592] Dolphin shows false "moving: finished" notification when user tries to rename a folder/file
https://bugs.kde.org/show_bug.cgi?id=391592 Julian Schraner changed: What|Removed |Added Ever confirmed|0 |1 Summary|Dolphin shows "moving: |Dolphin shows false |finished" notification when |"moving: finished" |user tries to rename a |notification when user |folder/file using a name|tries to rename a |that already exists and |folder/file |uses "suggest new name" | |feature | Status|UNCONFIRMED |CONFIRMED CC||juliquad...@gmail.com --- Comment #3 from Julian Schraner --- Can confirm with Dolphin 18.04, but as Atlas Rezhko has already said, the same command is used internally, which then also spawns this notification. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393618] New: bookmark sync is missing
https://bugs.kde.org/show_bug.cgi?id=393618 Bug ID: 393618 Summary: bookmark sync is missing Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: john-s...@posteo.org Target Milestone: --- I would love to see firefox bookmark sync integration. Maybe a project for GSoC? Firefox sync server is opensource. So it would also be easy to sync between mobile and Desktop. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390453] Dolphin crash No. 100 or more
https://bugs.kde.org/show_bug.cgi?id=390453 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com --- Comment #2 from Julian Schraner --- Please paste the contents of /etc/fstab so that we can further investigate this crash. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392319] Visual feedback when moving files per drag and drop and shift-key
https://bugs.kde.org/show_bug.cgi?id=392319 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com --- Comment #3 from Julian Schraner --- @Gregor Mi, were you able to test this again? It works fine for me with Dolphin 18.04. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371574] Dolphin crashes after Konsole-button related operations
https://bugs.kde.org/show_bug.cgi?id=371574 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com --- Comment #5 from Julian Schraner --- @Haruki Arita: Thanks for the update! I tried to follow your initial steps from the original description, but Dolphin did not crash for me. Did you do anything different than what you described in your first comment? Thanks again for reporting this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393617] New: Transform Tool doesn't effect the Hidden Layers inside a Group as expected.
https://bugs.kde.org/show_bug.cgi?id=393617 Bug ID: 393617 Summary: Transform Tool doesn't effect the Hidden Layers inside a Group as expected. Product: krita Version: 4.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: gm.ravnev...@gmail.com Target Milestone: --- Transform tools don't seem to effect hidden layers as expected. Reproducible: Always Steps to Reproduce: Case 1: 1. Create group layer. 2. Create 2 paint layers (A and B) inside group layer. 3. Hide layer A. 4. Transform group layer. 5. Show layer A. Actual Results: Layer A retains it's old position, rotation and scale. Expected Results: Layer A should have be transformed along with layer B. Case 2: 1. Create group layer. 2. Create 2 paint layers (A and B) inside group layer. 3. Hide layer A. 4. Transform group layer. 5. Show layer A. 6. Transform group layer again. Actual Results: Layer A updates to the new Transforms, but if then canvas is updated in any other way then with the Transform Tool between step 4 and 6, layer A retains the position, rotation and scale it had before it what hidden. Expected Results: Layer A should have be transformed along with layer B. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 348186] dolphin slow response upon start
https://bugs.kde.org/show_bug.cgi?id=348186 Julian Schraner changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #12 from Julian Schraner --- Probably fixed & no response -> closing. Please reopen the report if you can still reproduce this issue with newer versions of Dolphin. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 343343] Partition sizes numbers are in Aarbic-Indic
https://bugs.kde.org/show_bug.cgi?id=343343 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #13 from Julian Schraner --- I am going to close this bug as this should have been fixed by the distro maintainers & no new activity for this bug. Please reopen the report if this behavior still exists with newer versions of Dolphin/your distro. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354825] dolphin 15.08.2 unable to configure single click folder or file open
https://bugs.kde.org/show_bug.cgi?id=354825 Julian Schraner changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Julian Schraner --- No response -> closing. I never had such an issue despite various upgrades, so I think this should be fixed by now. Please reopen this report if you can still reproduce this behavior with newer versions of Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 355809] When copy a link from a ntfs drive, dolphin changes the link original path
https://bugs.kde.org/show_bug.cgi?id=355809 --- Comment #2 from Julian Schraner --- Please test this again with a newer version of Dolphin. If we don't have any confirmation that this is still happening for the next two weeks, I'll close this bug then. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371577] Can copy photo from camera [galaxy 5s] but can't paste photo to desktop error msg 150
https://bugs.kde.org/show_bug.cgi?id=371577 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Julian Schraner --- No response -> closing. Please reopen this bug if you can still reproduce this behavior. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357683] Frozen at startup
https://bugs.kde.org/show_bug.cgi?id=357683 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Julian Schraner --- This issue is most likely fixed. I am going to close the report as nobody has responded since two weeks. Please reopen this bug if you can still reproduce this issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 319545] Subversion plugin - no password prompt
https://bugs.kde.org/show_bug.cgi?id=319545 Julian Schraner changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Julian Schraner --- Two weeks have passed, so I'll close this bug report now. Please reopen the bug if you can still reproduce this behavior. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 --- Comment #7 from Allen Winter --- does the crash only happen in month view? i.e. can you also test agenda or todo views? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #8 from walker...@msn.com --- (In reply to Boudewijn Rempt from comment #7) > First, are you using appimages, or distribution packages? If appimages, just > start a terminal and start krita, with ./krita-4.0.1-x86_64.appimage in the > directory where the appimage is Appimage -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 393616] New: Kate cuts off lower part of letters on last line
https://bugs.kde.org/show_bug.cgi?id=393616 Bug ID: 393616 Summary: Kate cuts off lower part of letters on last line Product: kate Version: 18.04.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 112299 --> https://bugs.kde.org/attachment.cgi?id=112299&action=edit Screenshot showing the issue Kate cuts off the lower parts of letters like 'g' and 'j' that are on the last line of a text file (see attached screenshot). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #7 from Boudewijn Rempt --- First, are you using appimages, or distribution packages? If appimages, just start a terminal and start krita, with ./krita-4.0.1-x86_64.appimage in the directory where the appimage is locagted. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 389164] Spectacle on wayland interface causes screen refresh
https://bugs.kde.org/show_bug.cgi?id=389164 --- Comment #7 from Martin Flöser --- (In reply to Nate Graham from comment #6) > (In reply to Martin Flöser from comment #5) > > > @Martin: Is this a conceptual problem, or simply a bug in KWin: Why are > > > popups closing when KWin asks "Create screen shot with left click or > > > enter"? > > > > When creating a screenshot KWin takes over the mouse cursor which results in > > a pointer leave event being sent to the window. This results (at least in > > Qt) in closing the popup. > > Maybe we could omit the pointer leave event? If you're taking a screenshot, > it's a good bet you want the screen to remain exactly as it is so nothing > disappears or changes before the screenshot can be captured. Not without breaking our Wayland protocol support. There is a guarantee that all pointer events are delivered while an application has the focus. Imagine you click a second button while taking the screenshot and release it afterwards. Then the application gets a button release event for a button it never got the press event. That is a clear violation of Wayland protocol and I would understand any program which asserts under this condition. We must send a leave event when we take over the mouse pointer. > > > > This is also not really a difference to X11. There it is also not possible > > to screenshot context menus. > > Not by clicking, but you currently can do this in X11: Open Spectacle > Set > 2 second timer > switch to "Window under cursor" mode > Click "take new > screenshot" > Open context menu > position mouse cursor over menu. It would > be a shame to lose this feature in Wayland. Yes, this is currently not possible. It could be achieved by moving the time delay to KWin. So that KWin does not have to take the pointer focus, but just screenshots after the 2 second timer. This would require changes in spectacle and the dbus protocol. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393615] New: systemsettings5 > App Style > QtCurve config crash
https://bugs.kde.org/show_bug.cgi?id=393615 Bug ID: 393615 Summary: systemsettings5 > App Style > QtCurve config crash Product: systemsettings Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: neoaet...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.12.4) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-20-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: Kubuntu v18.04, release build apt-get install qtcurve Cmd: systemsettings5 Application Style... Widget Style... > QtCurve .. kf5.kxmlgui: cannot find .rc file "QtCurveui.rc" for component "QtCurve" pure virtual method called terminate called without an active exception KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 1293 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/0/kdeinit5__0 Empty file created at: /usr/local/share/kxmlgui5/QtCurve/QtCurveui.rc Not actually sure if that's where it's supposed to go but.., it gives this: Error parsing XML document: "unexpected end of file" at line 2 column 1 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 1451 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/0/kdeinit5__0 May be releated commit: https://cgit.kde.org/qtcurve.git/commit/?id=35f231376fae0523219f11ecd750a2f12622d54b Previously built a later ver on Kubuntu17.10 at it was doing the same thing though. I Don't think I have a default qtcurve5 rc file as far as I know... It was working fine by default on Kubuntu 17.10. Fesh install, bunch of other packeages installed. Very little customation. I know you can set the env varible but like I said I don't have a config file I think anyways. And I'm not actually sure if that's the real reason it's crashing. There's also no KDE_INSTALL_KXMLGUI5DIR env varible on this setup... I don't know if that matters. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb94c9f8800 (LWP 1851))] Thread 7 (Thread 0x7fb917fff700 (LWP 1858)): #0 0x7fb9445f99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c8471ecda8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55c8471ecd58, cond=0x55c8471ecd80) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55c8471ecd80, mutex=0x55c8471ecd58) at pthread_cond_wait.c:655 #3 0x7fb928f6c86b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fb928f6c6e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fb9445f36db in start_thread (arg=0x7fb917fff700) at pthread_create.c:463 #6 0x7fb94844d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fb91ecdc700 (LWP 1857)): #0 0x7fb9445f99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c8471ecc40) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55c8471ecbf0, cond=0x55c8471ecc18) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55c8471ecc18, mutex=0x55c8471ecbf0) at pthread_cond_wait.c:655 #3 0x7fb928f6c86b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fb928f6c6e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fb9445f36db in start_thread (arg=0x7fb91ecdc700) at pthread_create.c:463 #6 0x7fb94844d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fb91f4dd700 (LWP 1856)): #0 0x7fb9445f99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c8471ecad8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55c8471eca88, cond=0x55c8471ecab0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55c8471ecab0, mutex=0x55c8471eca88) at pthread_cond_wait.c:655 #3 0x7fb928f6c86b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7fb928f6c6e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7fb9445f36db in start_thread (arg=0x7fb91f4dd700) at pthread_create.c:463 #6 0x7fb94844d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fb91fcde700 (LWP 1855)): #0 0x7fb9445f99f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c8471ec9
[plasmashell] [Bug 393614] New: Plasmashell crashes on startup
https://bugs.kde.org/show_bug.cgi?id=393614 Bug ID: 393614 Summary: Plasmashell crashes on startup Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: dolo...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 I am unable to run plasmashell. Everytime I am firing it up, it crashes. Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. FlatpakNotifier::onFetchUpdatesFinished (this=0x56c5f6d0, flatpakInstallation=0x5587dcd0, updates=0x0) at /home/dlh/pkg/packages/discover/trunk/src/discover-5.12.4/libdiscover/backends/FlatpakBackend/FlatpakNotifier.cpp:105 105 /home/dlh/pkg/packages/discover/trunk/src/discover-5.12.4/libdiscover/backends/FlatpakBackend/FlatpakNotifier.cpp: No such file or directory Thread 21 (Thread 0x7fff02641700 (LWP 26661)): #0 0x77de7570 in _dl_debug_state () at /lib64/ld-linux-x86-64.so.2 #1 0x77debf55 in _dl_close_worker () at /lib64/ld-linux-x86-64.so.2 #2 0x77dec6fe in _dl_close () at /lib64/ld-linux-x86-64.so.2 #3 0x71512ebf in _dl_catch_exception () at /usr/lib/libc.so.6 #4 0x71512f4f in _dl_catch_error () at /usr/lib/libc.so.6 #5 0x70180587 in () at /usr/lib/libdl.so.2 #6 0x7017ffb3 in dlclose () at /usr/lib/libdl.so.2 #7 0x7fff10965197 in g_module_close () at /usr/lib/libgmodule-2.0.so.0 #8 0x7fff11044771 in () at /usr/lib/libgio-2.0.so.0 #9 0x7fff113b9df2 in g_type_module_unuse () at /usr/lib/libgobject-2.0.so.0 #10 0x7fff11044991 in () at /usr/lib/libgio-2.0.so.0 #11 0x7fff110455f2 in g_io_extension_point_get_extensions () at /usr/lib/libgio-2.0.so.0 #12 0x7fff11045bcb in () at /usr/lib/libgio-2.0.so.0 #13 0x7fff059b5c6b in () at /usr/lib/libsoup-2.4.so.1 #14 0x7fff113978d8 in () at /usr/lib/libgobject-2.0.so.0 #15 0x7fff11399180 in g_object_new_valist () at /usr/lib/libgobject-2.0.so.0 #16 0x7fff059b8d4a in soup_session_async_new_with_options () at /usr/lib/libsoup-2.4.so.1 #17 0x7fff05c9b7f9 in () at /usr/lib/libostree-1.so.1 #18 0x7fffebd73a2a in () at /usr/lib/libglib-2.0.so.0 #19 0x70d870bc in start_thread () at /usr/lib/libpthread.so.0 #20 0x714d72ff in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fff02e42700 (LWP 26660)): #0 0x714cccd9 in poll () at /usr/lib/libc.so.6 #1 0x7fffebd4b523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffebd4b63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fff05c9a0d6 in () at /usr/lib/libostree-1.so.1 #4 0x7fff05c63dad in () at /usr/lib/libostree-1.so.1 #5 0x7fff05c6cc80 in ostree_repo_remote_fetch_summary_with_options () at /usr/lib/libostree-1.so.1 #6 0x7fff05c4ee17 in ostree_repo_remote_fetch_summary () at /usr/lib/libostree-1.so.1 #7 0x7fff06635ac5 in () at /usr/lib/libflatpak.so.0 #8 0x7fff06636734 in () at /usr/lib/libflatpak.so.0 #9 0x7fff06620413 in flatpak_installation_list_remote_refs_sync () at /usr/lib/libflatpak.so.0 #10 0x7fff06620a78 in flatpak_installation_list_installed_refs_for_update () at /usr/lib/libflatpak.so.0 #11 0x7fff068986ea in FlatpakNotifieroperator() (__closure=0x56c80128) at /home/dlh/pkg/packages/discover/trunk/src/discover-5.12.4/libdiscover/backends/FlatpakBackend/FlatpakNotifier.cpp:136 #12 0x7fff068986ea in QtConcurrent::StoredFunctorCall0<_GPtrArray*, FlatpakNotifier::loadRemoteUpdates(FlatpakInstallation*):: >::runFunctor (this=0x56c80100) at /usr/include/qt/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #13 0x7fff068986ea in QtConcurrent::RunFunctionTask<_GPtrArray*>::run() (this=0x56c80100) at /usr/include/qt/QtConcurrent/qtconcurrentrunbase.h:108 #14 0x71bcea92 in () at /usr/lib/libQt5Core.so.5 #15 0x71bd1abd in () at /usr/lib/libQt5Core.so.5 #16 0x70d870bc in start_thread () at /usr/lib/libpthread.so.0 #17 0x714d72ff in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fff03643700 (LWP 26659)): #0 0x70d8d3bb in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x71bd2e51 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x71bced21 in () at /usr/lib/libQt5Core.so.5 #3 0x71bd1abd in () at /usr/lib/libQt5Core.so.5 #4 0x70d870bc in start_thread () at /usr/lib/libpthread.so.0 #5 0x714d72ff in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fff03e44700 (LWP 26658)): #0 0x714cccd9 in poll () at /usr/lib/libc.so.6 #1 0x7fffebd4b523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fffebd4b63e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x00
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #6 from walker...@msn.com --- (In reply to Boudewijn Rempt from comment #5) > Is there anything interesting shown on the commandline if you start Krita > from the terminal? How would I do that? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 --- Comment #6 from bugzy --- I have libical 2.0, specifically libical-2.0.0-13.fc27.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 393299] Investments panel equities listing no details of holding
https://bugs.kde.org/show_bug.cgi?id=393299 --- Comment #2 from Paul Gover --- Aha! That works, thanks. But I had to make a trivial change somewhere before I could save the file and make the altered display permanent. (sorry for the delayed response - I missed the notification of your comment) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #5 from Boudewijn Rempt --- Is there anything interesting shown on the commandline if you start Krita from the terminal? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393613] kopete crashes on exit, does not save settings or kontact list
https://bugs.kde.org/show_bug.cgi?id=393613 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393613] kopete crashes on exit, does not save settings or kontact list
https://bugs.kde.org/show_bug.cgi?id=393613 --- Comment #1 from Mathias Homann --- Created attachment 112298 --> https://bugs.kde.org/attachment.cgi?id=112298&action=edit New crash information added by DrKonqi kopete (1.13.0) using Qt 5.10.0 - What I was doing when the application crashed: same on my other computer: kopete crashes on exit, does not save settings or changes to contact roster. -- Backtrace (Reduced): #6 0x7f8032e3d8d0 in JabberClient::client() const () at /usr/lib64/qt5/plugins/kopete_jabber.so #7 0x7f8032e3ddcc in JabberClient::leaveGroupChat(QString const&, QString const&) () at /usr/lib64/qt5/plugins/kopete_jabber.so #8 0x7f8032e1818f in () at /usr/lib64/qt5/plugins/kopete_jabber.so #9 0x7f8032e181c9 in () at /usr/lib64/qt5/plugins/kopete_jabber.so #10 0x7f8062ba8cff in Kopete::Account::~Account() () at /usr/lib64/libkopete.so.1 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 200017] Provide thumbnail preview support for epub, fb2, and the like using Okular generators
https://bugs.kde.org/show_bug.cgi?id=200017 Giacomo changed: What|Removed |Added CC||giacomo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393059] KOrganizer crashes when using caldav calendar
https://bugs.kde.org/show_bug.cgi?id=393059 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #5 from Allen Winter --- Works fine for me with KOrganizer master and libical 3.0.x which libical version are you using? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 393613] New: kopete crashes on exit, does not save settings or kontact list
https://bugs.kde.org/show_bug.cgi?id=393613 Bug ID: 393613 Summary: kopete crashes on exit, does not save settings or kontact list Product: kopete Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.10.0 Frameworks Version: 5.45.0 Operating System: Linux 4.4.126-48-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Whenever I quit kopete it crashes, without savong settings or changes that I've made to the kontact list (such as accepting a new contact into my list etc) The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8356951940 (LWP 5044))] Thread 6 (Thread 0x7f83137fe700 (LWP 5096)): #0 0x7f8351c7e94b in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #1 0x7f8351c8036c in () at /usr/lib64/libQt5Core.so.5 #2 0x7f834a02095d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f834a021230 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f834a02142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8351c7ffbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8351c2ba4b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8351a6914a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f832494d0fd in () at /usr/lib64/qt5/plugins/kopete_jabber.so #9 0x7f8351a6de0f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f834c135724 in start_thread () at /lib64/libpthread.so.0 #11 0x7f8351373e8d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f8313fff700 (LWP 5095)): #0 0x7f835136733d in read () at /lib64/libc.so.6 #1 0x7f834a061750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f834a020e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f834a0212a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f834a02142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8351c7ffbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8351c2ba4b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f83242b638a in QCA::SyncThread::run() () at /usr/lib64/libqca-qt5.so.2 #8 0x7f8351a6de0f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f834c135724 in start_thread () at /lib64/libpthread.so.0 #10 0x7f8351373e8d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f8322508700 (LWP 5087)): #0 0x7f834c13a0ff in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8351a6ec7b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8351a67dbb in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #3 0x7f834f4fad24 in () at /usr/lib64/libQt5Network.so.5 #4 0x7f8351a6de0f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f834c135724 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8351373e8d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8336556700 (LWP 5055)): #0 0x7f835136b30d in poll () at /lib64/libc.so.6 #1 0x7f834a021314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f834a02142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8351c7ffbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8351c2ba4b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8351a6914a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8351a6de0f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f834c135724 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8351373e8d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8337fff700 (LWP 5049)): #0 0x7f835136b30d in poll () at /lib64/libc.so.6 #1 0x7f834a021314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f834a02142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8351c7ffbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8351c2ba4b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8351a6914a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f83535ca7b5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f8351a6de0f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f834c135724 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8351373e8d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f
[krita] [Bug 392949] Color Picker returns wrong color for certain colors
https://bugs.kde.org/show_bug.cgi?id=392949 --- Comment #2 from hawaiiga...@hotmail.com --- (In reply to Boudewijn Rempt from comment #1) > The color picker samples all the colors under the area the brush tip covers > -- maybe that's what is happening? It might be related insofar that the root of the issue lies in the code picking the color from area covered by the brush tip, but as far as my tests go, I don't think it's just a logical consequence of that feature. I've tried with different brushes and brush sizes, and the results are always the same. As mentioned, the color returned sometimes has an Alpha of 0, or more often is not related in any way to any color on the layer or on the canvas, even when the whole layer was previously bucket-filled with a single color. The only thing I noticed while testing your suggestion is that the channel values indicated in the 'Tool Options' for the color picker tool are actually correct, i.e when picking a pure blue it lists: CHANNELS__|_VALUE RED_0 GREEN___0 BLUE1 The color sent to the color selector however is completely different. -- You are receiving this mail because: You are watching all bug changes.
[kcalutils] [Bug 391287] kcalutils/autotest fails - kcalutils-testincidenceformatter
https://bugs.kde.org/show_bug.cgi?id=391287 Allen Winter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||win...@kde.org --- Comment #1 from Allen Winter --- I made a fix that works for me, but jenkins still isn't happy. must be the locale. I see the testincidenceformatter uses the LC_ALL=C locale as in: set_tests_properties(kcalutils-testincidenceformatter PROPERTIES ENVIRONMENT "LC_ALL=C") but maybe we need a locale expert and a jenkins person to figure it out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #103 from Nate Graham --- See my previous comment: this has been fixed in *Qt 5.11*. Ask your distros to backport the patch to their Qt 5.9.x and 5.10.x packages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #102 from DeMus --- KDE 5.12.4, Frameworks 5.45.0, Qt 5.10.1. When using the slide-show memory is filling up pretty fast. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379800] Folder panel active text color incorrect assigned to WindowText color
https://bugs.kde.org/show_bug.cgi?id=379800 --- Comment #24 from andre.cbar...@yahoo.com --- By the way, I will be working on some other "defective" patch to Dolphin this weekend and will check the status of this specific issue on the development list again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379800] Folder panel active text color incorrect assigned to WindowText color
https://bugs.kde.org/show_bug.cgi?id=379800 --- Comment #23 from andre.cbar...@yahoo.com --- (In reply to Julian Schraner from comment #22) > Still waiting for an update. Should we still keep this report open? The > issue could still exist, but we do not have all necessary information to fix > it. To me the reasoning holds true. I think I reported it to Dolphin development list. Will check there again. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393612] Add an option to search for function declarations
https://bugs.kde.org/show_bug.cgi?id=393612 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393611] Option to search in all opened script files
https://bugs.kde.org/show_bug.cgi?id=393611 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393609] Debugger Console font and theme cannot be changed
https://bugs.kde.org/show_bug.cgi?id=393609 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393612] New: Add an option to search for function declarations
https://bugs.kde.org/show_bug.cgi?id=393612 Bug ID: 393612 Summary: Add an option to search for function declarations Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- This wish is coupled with #393611. Please add an option to search for function declarations. Perhaps form the find bar accessible with a special shortcut. Perhaps utilizing some form of search regex alias like: [ \t]?%s[ \t]?((<\-)|(=))[ \t]?function[ \t]?\( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #4 from walker...@msn.com --- (In reply to Boudewijn Rempt from comment #3) > I was asking for the _exact_ versions. And distribution packages or > appimages? And what version of Linux Mint? For Mint 18.3, Krita 4.0.1 and gmic 2.2.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393116] Krita 4.1 fails to load 3.0 build in brush presets
https://bugs.kde.org/show_bug.cgi?id=393116 --- Comment #3 from thiago --- Not working again. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393611] New: Option to search in all opened script files
https://bugs.kde.org/show_bug.cgi?id=393611 Bug ID: 393611 Summary: Option to search in all opened script files Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- Perhaps this feature already exists, but simply couldn't find it. `Edit -> Find` or Ctrl+F gives you the option to search only in the current script file which is in focus. Please consider adding an option to search in all opened script files from one place. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 393541] Wrong timezone on imported invitation
https://bugs.kde.org/show_bug.cgi?id=393541 Allen Winter changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #7 from Allen Winter --- I'm pretty sure upgrading the Neon libical to version 3.0.x will fix this. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] New: Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 Bug ID: 393610 Summary: Wish for Debugger console do be disabled Product: rkward Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- This is a wishlist coupled with #393609. Please add an option to disable the *Debugger Console* and redirect all of its functionality to plain *R Console*. Perhaps with optional sidebar with "Next", "Step out", "Continue" and "Cancel" buttons which shows up when the RKWard detects a debugger context (and whose should be complete according to `browser()` implementation - see `?browser`). I would like to know the historical reason behind the decoupling of R Console and Debugger Console, especially when there is also a Debugger Frames window. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393111] When I try to open G'mic it crashes
https://bugs.kde.org/show_bug.cgi?id=393111 --- Comment #3 from Boudewijn Rempt --- I was asking for the _exact_ versions. And distribution packages or appimages? And what version of Linux Mint? -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393609] New: Debugger Console font and theme cannot be changed
https://bugs.kde.org/show_bug.cgi?id=393609 Bug ID: 393609 Summary: Debugger Console font and theme cannot be changed Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- Debugger Console font and theme cannot be changed. The R Console tab/window (and the script editor) can be themed with Kate themes. However the debugger console is stuck with default theme. This causes several issues, for example not being able to have a dark theme and more annoyingly a non-changeable proportional font, instead of being able to use chosen monospaced one. ---Session Info--- -- Frontend -- RKWard version: 0.7.0z+0.7.1+devel1 KDE Frameworks version (runtime): 5.45.0 KDE Frameworks version (compile time): 5.45.0 Qt version (runtime): 5.10.1 Local config directory: /home/marek/.config RKWard storage directory: /home/marek/.rkward/ Backend version (as known to the frontend): 3.5.0 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 3.5.0 (2018-04-23 r74626) R runtime session info: R version 3.5.0 (2018-04-23) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Arch Linux Matrix products: default BLAS: /usr/lib/libblas.so.3.8.0 LAPACK: /usr/lib/liblapack.so.3.8.0 locale: [1] LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_NG.UTF-8 LC_COLLATE=en_GB.UTF-8 [5] LC_MONETARY=cs_CZ.UTF-8 LC_MESSAGES=en_GB.UTF-8 [7] LC_PAPER=en_GB.UTF-8 LC_NAME=en_GB.UTF-8 [9] LC_ADDRESS=cs_CZ.UTF-8LC_TELEPHONE=en_GB.UTF-8 [11] LC_MEASUREMENT=en_GB.UTF-8LC_IDENTIFICATION=en_GB.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] gridExtra_2.3 MASS_7.3-49 rkward_0.7.1 loaded via a namespace (and not attached): [1] compiler_3.5.0 tools_3.5.0gtable_0.2.0 grid_3.5.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393013] Stylus can't draw once leaving tablet range with "Hi-Dpi enabled" on cintiq pro 24"
https://bugs.kde.org/show_bug.cgi?id=393013 --- Comment #7 from epixer...@gmail.com --- no matter which setup I tried, with hi-dpi enabled, it just won't work. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 389164] Spectacle on wayland interface causes screen refresh
https://bugs.kde.org/show_bug.cgi?id=389164 --- Comment #6 from Nate Graham --- (In reply to Martin Flöser from comment #5) > > @Martin: Is this a conceptual problem, or simply a bug in KWin: Why are > > popups closing when KWin asks "Create screen shot with left click or enter"? > > When creating a screenshot KWin takes over the mouse cursor which results in > a pointer leave event being sent to the window. This results (at least in > Qt) in closing the popup. Maybe we could omit the pointer leave event? If you're taking a screenshot, it's a good bet you want the screen to remain exactly as it is so nothing disappears or changes before the screenshot can be captured. > This is also not really a difference to X11. There it is also not possible > to screenshot context menus. Not by clicking, but you currently can do this in X11: Open Spectacle > Set 2 second timer > switch to "Window under cursor" mode > Click "take new screenshot" > Open context menu > position mouse cursor over menu. It would be a shame to lose this feature in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389659] Please wait while the message is transferred
https://bugs.kde.org/show_bug.cgi?id=389659 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 393245] Wrong day for Teachers day in Slovak holiday calendar
https://bugs.kde.org/show_bug.cgi?id=393245 Allen Winter changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.46 Latest Commit||https://commits.kde.org/kho ||lidays/9c8aa21205db76d96778 ||55e760ee155bf35cc325 --- Comment #2 from Allen Winter --- Git commit 9c8aa21205db76d9677855e760ee155bf35cc325 by Allen Winter. Committed on 28/04/2018 at 13:39. Pushed by winterz into branch 'master'. holidays/plan2/holiday_sk_sk - Teacher's Day fix FIXED-IN: 5.46 M +1-1holidays/plan2/holiday_sk_sk https://commits.kde.org/kholidays/9c8aa21205db76d9677855e760ee155bf35cc325 -- You are receiving this mail because: You are watching all bug changes.
[krazy] [Bug 362504] Missing leading zero if the line number is smaller than 100
https://bugs.kde.org/show_bug.cgi?id=362504 Allen Winter changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Allen Winter --- i'm pretty sure I fixed this. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 389164] Spectacle on wayland interface causes screen refresh
https://bugs.kde.org/show_bug.cgi?id=389164 --- Comment #5 from Martin Flöser --- > @Martin: Is this a conceptual problem, or simply a bug in KWin: Why are > popups closing when KWin asks "Create screen shot with left click or enter"? When creating a screenshot KWin takes over the mouse cursor which results in a pointer leave event being sent to the window. This results (at least in Qt) in closing the popup. This is also not really a difference to X11. There it is also not possible to screenshot context menus. -- You are receiving this mail because: You are watching all bug changes.
