[kmail2] [Bug 426029] [kmail] Segfault when trying to send an PGP encrypted email
https://bugs.kde.org/show_bug.cgi?id=426029
--- Comment #2 from Andreas Schneider ---
(gdb) bt full
#0 0x in ()
#1 0x7fff11cc170a in KMime::Headers::Base::is(char const*) const
(this=this@entry=0x586303b0, t=t@entry=0x7fff11cd9ff4 "Content-Type") at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_headers.cpp:153
#2 0x7fff11cc1767 in KMime::Content::headerByType(char const*) const
(this=this@entry=0x5861c300, type=0x7fff11cd9ff4 "Content-Type") at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:625
h = 0x586303b0
__for_range =
#3 0x7fff11cc1fa9 in
KMime::Content::header(bool) (create=true,
this=0x5861c300) at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.h:693
h =
#4 KMime::Content::contentType(bool) (this=this@entry=0x5861c300,
create=create@entry=true) at
/usr/src/debug/kmime-20.08.0-1.2.x86_64/src/kmime_content.cpp:877
#5 0x7fff111581a6 in
MessageComposer::Util::composeHeadersAndBody(KMime::Content*, QByteArray,
Kleo::CryptoMessageFormat, bool, QByteArray const&) (orig=0x5861c300,
encodedBody=..., format=, sign=, hashAlgo=...) at
/usr/src/debug/messagelib-20.08.0-1.2.x86_64/messagecomposer/src/utils/util.cpp:89
vers =
boundary = {
d = 0x59113ed0
}
code = 0x59ccb1f0
result = 0x59ce1d10
#6 0x7fff110f9a64 in operator() (auditLogAsHtml=..., auditLogError=...,
cipherText=..., result=..., __closure=0x59d7e9e0) at
/usr/include/qt5/QtCore/qrefcount.h:60
d = 0x59ce1750
this = 0x59d8b3f0
#7 QtPrivate::FunctorCall,
QtPrivate::List, void,
MessageComposer::EncryptJob::process():: >::call
(arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#8 QtPrivate::Functor, 4>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#9
QtPrivate::QFunctorSlotObject, 4, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x59d7e9d0, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x76be6116 in () at /usr/lib64/libQt5Core.so.5
#11 0x7fff10bfe0b1 in QGpgME::EncryptJob::result(GpgME::EncryptionResult
const&, QByteArray const&, QString const&, GpgME::Error const&) () at
/usr/lib64/libqgpgme.so.7
#12 0x7fff10c15452 in QGpgME::_detail::ThreadedJobMixin
>::slotFinished() () at /usr/lib64/libqgpgme.so.7
#13 0x76bdbb61 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#14 0x777070cf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#15 0x76bafc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#16 0x76bb2661 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#17 0x76c079f3 in () at /usr/lib64/libQt5Core.so.5
#18 0x7fffede0d2b7 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#19 0x7fffede0d638 in () at /usr/lib64/libglib-2.0.so.0
#20 0x7fffede0d6ef in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#21 0x76c0707f in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#22 0x76bae5fb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#23 0x76bb6860 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#24 0x8fc7 in ()
#25 0x76579cca in __libc_start_main () at /lib64/libc.so.6
#26 0x961a in ()
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 426048] Changing a clip's speed causes a crash
https://bugs.kde.org/show_bug.cgi?id=426048 --- Comment #2 from h.k.gh...@gmail.com --- While trying to find a workaround the issue, so that I can continue my work, I discovered the following: As noted, the lowest speed value I had tried to set before was 15%, and it had crashed. I tried 10% and crash, as "expected", but I then tried a 5% instead (after reloading project, etc) and there was *no crash*. After that, I tried 10% again and other in-between values and no crash was observed. To recap, when you first start to change speed values, it's 100% by default. It seems like trying to set it to some value 10% >= x < 30% on the first try causes the crash, but if you go *below* under 10% immediately, the crash can be avoided for some reason. After you avoid it this way, it seems you're allowed to set the value to anything else without issues, but this is a lucky "workaround" I seem to have come across. Not sure how far it'll get me, though. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426048] Changing a clip's speed causes a crash
https://bugs.kde.org/show_bug.cgi?id=426048 --- Comment #3 from h.k.gh...@gmail.com --- I forgot to mention, in this case, playing the clip causes the preview in the project monitor pane to not actually play the video. It remains as a still frame... -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 425903] "Account is offline" dialog does not appear while making changes
https://bugs.kde.org/show_bug.cgi?id=425903 Shashwat Jolly changed: What|Removed |Added Product|Akonadi |korganizer Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411558] Make tabs detachable when dragged off the tab bar
https://bugs.kde.org/show_bug.cgi?id=411558 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #2 from Michael D --- I'm not sure whether the dragging behavior would be consistent with how tabs work in other apps, but it would certainly be nice to have some way of detaching tabs--I would be happy with even a button, shortcut, or menu entry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 423055] Not all Plasma widgets installed via GHNS window are listed in Widget Explorer when its "Uninstallable" filter is selected
https://bugs.kde.org/show_bug.cgi?id=423055 Alexander Lohnau changed: What|Removed |Added Version Fixed In||5.20 Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||ce920603ea93ae4abf391d47700 ||1bb67cd429ed1 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Alexander Lohnau --- Git commit ce920603ea93ae4abf391d477001bb67cd429ed1 by Alexander Lohnau. Committed on 01/09/2020 at 08:09. Pushed by alex into branch 'master'. Fix undetected KPackage installation This was the last occurrence that didn't get ported/detected. Because of that the updating did not work and uninstalling an entry using the "Widget Explorer" did not work. Related: bug 424429 FIXED-IN: 5.20 M +2-2components/shellprivate/widgetexplorer/plasmoids.knsrc https://invent.kde.org/plasma/plasma-workspace/commit/ce920603ea93ae4abf391d477001bb67cd429ed1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424429] Can't update Event Calendar with Discover
https://bugs.kde.org/show_bug.cgi?id=424429 Alexander Lohnau changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||ce920603ea93ae4abf391d47700 ||1bb67cd429ed1 Version Fixed In||5.20 --- Comment #13 from Alexander Lohnau --- Git commit ce920603ea93ae4abf391d477001bb67cd429ed1 by Alexander Lohnau. Committed on 01/09/2020 at 08:09. Pushed by alex into branch 'master'. Fix undetected KPackage installation This was the last occurrence that didn't get ported/detected. Because of that the updating did not work and uninstalling an entry using the "Widget Explorer" did not work. Related: bug 423055 FIXED-IN: 5.20 M +2-2components/shellprivate/widgetexplorer/plasmoids.knsrc https://invent.kde.org/plasma/plasma-workspace/commit/ce920603ea93ae4abf391d477001bb67cd429ed1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425852] disable middle click to paste to increase usability of KDE applications and KDE desktop
https://bugs.kde.org/show_bug.cgi?id=425852 --- Comment #13 from Lukas Ba. --- (In reply to Christoph Feck from comment #10) > Already reported as bug 374892. No new information was provided. > > Please ask in a help forum where to find the Mouse Action settings for the > Plasma desktop. Oh it seems there was a misunderstanding here, when i said i want to disable the middle mouse to paste on the desktop, i was refering to the whole KDE plasma desktop, including the startmenu, the taskbars, etc., not just the desktop background where you can set a background picture. I apologize for my inconcise wording. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425852] disable middle click to paste to increase usability of KDE applications and KDE desktop
https://bugs.kde.org/show_bug.cgi?id=425852 --- Comment #14 from Lukas Ba. --- Another example, when i middle mouse click on the taskbar, a sticky notes icon appears. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425852] disable middle click to paste to increase usability of KDE applications and KDE desktop
https://bugs.kde.org/show_bug.cgi?id=425852 Lukas Ba. changed: What|Removed |Added Resolution|MOVED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 425953] undefined reference to `KWindowConfig::allConnectedScreens()'
https://bugs.kde.org/show_bug.cgi?id=425953 --- Comment #5 from Bernhard Landauer --- Your reply doesn't make much sense. I'm saying that commit 803b9f16 fails to build and you are pointing back to the same commit itself ;) ? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426048] Changing a clip's speed causes a crash
https://bugs.kde.org/show_bug.cgi?id=426048 --- Comment #4 from h.k.gh...@gmail.com --- Unfortunately, the still frame is not an issue with the preview alone. If I render the project, it gets incorrectly rendered just as in the preview, with the still frame. It seems that this "workaround" simply avoids the crash, but there's more. Any speed value < 30% causes the "still frame" issue without crashing, but something does remain broken and affected other areas of functionality. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425606] Akonadi server fails with MariaDB 10.5.5
https://bugs.kde.org/show_bug.cgi?id=425606 Rik Mills changed: What|Removed |Added CC||rikmi...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408313] kickoff switches to "Favorites" tab on opening
https://bugs.kde.org/show_bug.cgi?id=408313 --- Comment #8 from Lukas Ba. --- (In reply to Nate Graham from comment #1) > This was fixed in a later version of Plasma. You're using an older version: > 5.12.8. For comparison, 5.16.0 is being released in a few days. Still an issue for me with these versions SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.3-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 384032] Get new hot stuff sorting not applied when selecting option 'most downloads'
https://bugs.kde.org/show_bug.cgi?id=384032 2f5ed...@opayq.com changed: What|Removed |Added CC||2f5ed...@opayq.com --- Comment #5 from 2f5ed...@opayq.com --- Hello, we have heard about the problems and we will try to fix them as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425852] Disable middle click on taskbar
https://bugs.kde.org/show_bug.cgi?id=425852 Christoph Feck changed: What|Removed |Added Component|components |Task Manager and Icons-Only ||Task Manager Assignee|notm...@gmail.com |h...@kde.org Severity|normal |wishlist Target Milestone|--- |1.0 Product|frameworks-plasma |plasmashell Summary|disable middle click to |Disable middle click on |paste to increase usability |taskbar |of KDE applications and KDE | |desktop | Version|5.73.0 |5.19.4 --- Comment #15 from Christoph Feck --- Doesn't happen here, but reassigning to taskbar component for investigation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 425135] GHNS windows: Addons list should immediately be updated after we uninstall an addon while "Installed only" or "Updateable only" filters are selected
https://bugs.kde.org/show_bug.cgi?id=425135 Alexander Lohnau changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/knewstuff/commit/853 ||1bbcc004bdafa0a0c6060966c2d ||aec457b776 Resolution|--- |FIXED Version Fixed In||5.74 Status|ASSIGNED|RESOLVED --- Comment #5 from Alexander Lohnau --- Git commit 8531bbcc004bdafa0a0c6060966c2daec457b776 by Alexander Lohnau. Committed on 31/08/2020 at 09:45. Pushed by alex into branch 'master'. Remove entries if they do not match filter anymore The state of the entries already gets updated, but they are still contained in the list of entries that match the filter. So we have to remove it. FIXED-IN: 5.74 M +8-0src/qtquick/quickitemsmodel.cpp https://invent.kde.org/frameworks/knewstuff/commit/8531bbcc004bdafa0a0c6060966c2daec457b776 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 426049] New: Video link crashes application
https://bugs.kde.org/show_bug.cgi?id=426049 Bug ID: 426049 Summary: Video link crashes application Product: akregator Version: 5.15.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: em.bugs.kde@jjussi.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open web page https://microsoft.github.io/AzureTipsAndTricks/blog/tip276.html 2. Click video link top of the page 📺 Watch the video : Top 10 Azure resources that you can use today https://www.youtube.com/watch?v=Mt2WSly9qBI&list=PLLasX02E8BPCNCK8Thcxu-Y-XcBUbhFWC&index=14?WT.mc_id%3Dyoutube-azuredevtips-micrum 3. akregator crashes and disappear from the screen OBSERVED RESULT Crash EXPECTED RESULT Open link to internal or external browser SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 426050] New: When drive selector list is "open", it will stop current synchronise activity
https://bugs.kde.org/show_bug.cgi?id=426050 Bug ID: 426050 Summary: When drive selector list is "open", it will stop current synchronise activity Product: krusader Version: 2.7.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: paolo-faceb...@nicealias.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY While doing a folder compare with Synchronise, if I accidentally leave the drive selector list "open" (that is showing, without selecting anything yet), the said Synchronise will "pause" in that disk activity falls to zero for the duration of the list being open. After making a selection in the list, Synchronise resumes. Note: the selector referred here is the one showing disk space and mount point. STEPS TO REPRODUCE 1. Start a Synchronise on a large folder 2. While above is running, go back to main window and click on drive selector 3. OBSERVED RESULT Disk activity for the Synchronise will stop EXPECTED RESULT Synchronise should keep going instead SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (kernel 5.0.4-42) (available in About System) KDE Plasma Version: 5.8.15 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425892] KDE Neon 5.19.4 Updated Caused Most Audio Devices to Disappear
https://bugs.kde.org/show_bug.cgi?id=425892 --- Comment #6 from Paul Feakins --- Today I'm on a computer that has not been updated and both sound and Shutter work perfectly. To confirm, it was indeed the update to "KDE neon on 20.04" that caused all the issues. I won't be updating this computer but I would like to roll back my other computer if possible? I will be forced to re-install otherwise. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426051] New: ark crashes when opening an encrypted 7z
https://bugs.kde.org/show_bug.cgi?id=426051 Bug ID: 426051 Summary: ark crashes when opening an encrypted 7z Product: ark Version: 20.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: tom.m...@googlemail.com CC: rthoms...@gmail.com Target Milestone: --- Application: ark (20.04.2) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.36-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: 1. Get an AES encrypted 7z container from somewhere 2. Open any encrypted file within the container 3. Enter the wrong password 4. Confirm the dialog that you've entered the wrong password 5. The UI thread ends up in an endless recursion until it crashes The crash can be reproduced every time. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1dfea03900 (LWP 8869))] Thread 4 (Thread 0x7f1dd008e700 (LWP 8918)): #0 0x7f1dfa9d46db in poll () from /lib64/libc.so.6 #1 0x7f1dd4cc3f71 in ?? () from /usr/lib64/libpulse.so.0 #2 0x7f1dd4cb5b10 in pa_mainloop_poll () from /usr/lib64/libpulse.so.0 #3 0x7f1dd4cb61a0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f1dd4cb6230 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f1dd4cc3eb9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f1dd4a63018 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f1df6d0d4f9 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1dfa9defbf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1de05a1700 (LWP 8874)): #0 0x7f1dfa9d01d8 in read () from /lib64/libc.so.6 #1 0x7f1df4c789a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1df4c31298 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1df4c31720 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1df4c3188c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f1dfb36a19b in QEventDispatcherGlib::processEvents (this=0x7f1dd8000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f1dfb30b32a in QEventLoop::exec (this=this@entry=0x7f1de05a0c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f1dfb13110a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f1df8bf3cd5 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f1dfb1328b2 in QThreadPrivate::start (arg=0x7f1df8e6bd80) at thread/qthread_unix.cpp:361 #10 0x7f1df6d0d4f9 in start_thread () from /lib64/libpthread.so.0 #11 0x7f1dfa9defbf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1debba0700 (LWP 8873)): #0 0x7f1dfa9d46db in poll () from /lib64/libc.so.6 #1 0x7f1df3200307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f1df3201f3a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f1dee995300 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f1dfb1328b2 in QThreadPrivate::start (arg=0x560877e7b800) at thread/qthread_unix.cpp:361 #5 0x7f1df6d0d4f9 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1dfa9defbf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1dfea03900 (LWP 8869)): [KCrash Handler] #4 0x7f1dfb2930e1 in QIODevicePrivate::QRingBufferRef::isEmpty (this=0x5608785aeb78) at ../../include/QtCore/5.12.7/QtCore/private/../../../../../src/corelib/io/qiodevice_p.h:105 #5 (anonymous namespace)::QProcessPoller::QProcessPoller (proc=..., this=0x7ffcc9c1c0a0) at io/qprocess_unix.cpp:174 #6 QProcessPrivate::waitForFinished (this=this@entry=0x5608785aeae0, msecs=msecs@entry=5) at io/qprocess_unix.cpp:837 #7 0x7f1dfb288f0b in QProcess::waitForFinished (this=, msecs=5) at io/qprocess.cpp:1920 #8 0x7f1dfe5ffe67 in Kerfuffle::CliInterface::killProcess(bool) () from /usr/lib64/libkerfuffle.so.20 #9 0x7f1dfe604e42 in Kerfuffle::CliInterface::readStdout(bool) () from /usr/lib64/libkerfuffle.so.20 #10 0x7f1dfb33cd0f in QtPrivate::QSlotObjectBase::call (a=0x7ffcc9c1c300, r=0x5608785710d0, this=0x56087855ada0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #11 QMetaObject::activate (sender=sender@entry=0x560878500830, signalOffset=, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffcc9c1c300) at kernel/qobject.cpp:3784 #12 0x7f1dfb33d307 in QMetaObject::activate (sender=sender@entry=0x560878500830, m=m@entry=0x7f1dfb7b9cc0 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffcc9c1c300) at kernel/qobject.cpp:3657 #13 0x7f1dfb28780a in QProcess::readyReadStandardOutput (this=this@entry=0x560878500830, _t1=...) at .m
[kdenlive] [Bug 426052] New: Offset in rendered video
https://bugs.kde.org/show_bug.cgi?id=426052 Bug ID: 426052 Summary: Offset in rendered video Product: kdenlive Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: klw...@gmail.com Target Milestone: --- Created attachment 131340 --> https://bugs.kde.org/attachment.cgi?id=131340&action=edit Screenshot SUMMARY STEPS TO REPRODUCE 1. insert a clip starting with .25s offset in timeline 2. insert a text after a couple secs 3. render the clip OBSERVED RESULT Text is .2 sec to early displayed in rendered file (mp4 & webm tried). EXPECTED RESULT Text at given position. SOFTWARE/OS VERSIONS Windows: 10 Kdenlive: 20.11.70 ADDITIONAL INFORMATION It depends not on the text, the issue is caused by the little offset at the beginning (has not to be at the beginning). Such short time settings cause some more issues. Eg. with fade in/out. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 410935] akonadi _ews_ressource crashes when setting office365 account
https://bugs.kde.org/show_bug.cgi?id=410935 mich...@nl-ix.net changed: What|Removed |Added CC||mich...@nl-ix.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 410935] akonadi _ews_ressource crashes when setting office365 account
https://bugs.kde.org/show_bug.cgi?id=410935 --- Comment #3 from mich...@nl-ix.net --- Created attachment 131341 --> https://bugs.kde.org/attachment.cgi?id=131341&action=edit New crash information added by DrKonqi akonadi_ews_resource (5.15.0 (20.08.0)) using Qt 5.15.0 - What I was doing when the application crashed: KMail autostarts for me. It tries to connect then the office account immediately crashes. When I go into the settings of the account, it shows a green man with a tick saying "Ready". However clicking on "Modify" for the account doesn't work anymore. The only time it worked, I tried to test the login. A new window popped up where I suppose I was going to be able to get Office 365's web login page, but it just stayed white, froze and crashed. -- Backtrace (Reduced): #4 0x7f036a93c681 in Akonadi::TagAttribute::deserialize (this=0x5637d6fc5680, data=...) at /usr/include/qt5/QtCore/qbytearray.h:500 #5 0x5637d67eb528 in EwsTagStore::unserializeTag (this=, tag=..., data=...) at /usr/include/c++/10/bits/atomic_base.h:333 #6 EwsTagStore::tags (this=) at /usr/src/debug/kdepim-runtime-20.08.0-1.2.x86_64/resources/ews/tags/ewstagstore.cpp:172 #7 EwsGlobalTagsReadJob::getFolderRequestFinished (this=0x5637d6fa5930, job=) at /usr/src/debug/kdepim-runtime-20.08.0-1.2.x86_64/resources/ews/tags/ewsglobaltagsreadjob.cpp:87 #8 0x7f0361b4b116 in QtPrivate::QSlotObjectBase::call (a=0x7ffe7f103e30, r=0x5637d6fa5930, this=0x5637d7063ba0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] New: delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 Bug ID: 426053 Summary: delete tab option unavailable Product: ksysguard Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: osth...@yandex.ru CC: plasma-b...@kde.org Target Milestone: --- SUMMARY delete tab option unavailable STEPS TO REPRODUCE 1. open ksysguard 2. add some new tab via file->dowload new tabs 3. try to remove added tab OBSERVED RESULT no way to do it EXPECTED RESULT see option like "delete tab" in menu "File" or anywhere SOFTWARE/OS VERSIONS Kubuntu 20.04.1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] ksysguard - delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 Ivan Tsulimov changed: What|Removed |Added Summary|delete tab option |ksysguard - delete tab |unavailable |option unavailable -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413689] Move the page number info to the toolbar and hide the status bar by default
https://bugs.kde.org/show_bug.cgi?id=413689 --- Comment #14 from David de Cos --- (In reply to David Hurka from comment #13) > You can go to Settings -> [_] Show Page Bar and Settings -> Configure > Toolbars..., then you have the old layout. Thanks! I hadn't noticed that option was present in the main menu. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425786] akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault - Akonadi::EntityTreeModel::modelIndexForCollection (model=, collection=...)
https://bugs.kde.org/show_bug.cgi?id=425786 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #4 from Ahmad Samir --- The backtraces are not all the identical, e.g. the one in the original post and the one in comment#2, are missing some debug symbols: 0x55aa430c6170 in ?? () the backtraces from comment#1 and #3 are slightly different. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410800] Device in Bookmark will show docker mount point when docker container opened
https://bugs.kde.org/show_bug.cgi?id=410800 Dmitry changed: What|Removed |Added CC||dima...@gmail.com --- Comment #5 from Dmitry --- Issue for Docker https://github.com/docker/for-linux/issues/1096 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426054] New: Irregular display of thumbs and images in Import from CF card
https://bugs.kde.org/show_bug.cgi?id=426054 Bug ID: 426054 Summary: Irregular display of thumbs and images in Import from CF card Product: digikam Version: 7.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Import-IconView Assignee: digikam-bugs-n...@kde.org Reporter: pierre.da...@damas.be Target Milestone: --- Created attachment 131342 --> https://bugs.kde.org/attachment.cgi?id=131342&action=edit Screenshot of observed pattern SUMMARY The display of images and icons is not matching the pattern of rectangular slides on import. STEPS TO REPRODUCE 1. Choose import from an USB mounted CF card 2. Enjoy OBSERVED RESULT Unaligned images and icons with grid EXPECTED RESULT Aligned images and icons with grid SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 4K screen (3840 x 2160) with 150% (Recommended) scaling (Additionally, the import is very slow) Canon EOS 5D Mk IV CR2 files -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425786] akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault - Akonadi::EntityTreeModel::modelIndexForCollection (model=, collection=...)
https://bugs.kde.org/show_bug.cgi?id=425786 --- Comment #5 from Don Curtis --- (In reply to Ahmad Samir from comment #4) > The backtraces are not all the identical, Hardly surprising: * The first Segmentation Fault occurred when adding the first periodic Archive. * The second when the second periodic Archive. * The third when an automatic Archive began running for the first time. * The fourth when I took a look at the settings. A segmentation fault or access violation is a fault, or failure condition, raised by hardware with memory protection, notifying an operating system (OS) that, the software has attempted to access a restricted area of memory (a memory access violation). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 426055] New: Crash upon replying to SMS
https://bugs.kde.org/show_bug.cgi?id=426055 Bug ID: 426055 Summary: Crash upon replying to SMS Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: pas...@dhermilly.dk Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: It crashed after I clicked Send to a SMS message that I had typed in after clicking Reply to an incoming SMS. BTW. My kdeconnect connection seems kind of flaky due some different wifis. Perhaps an assumption of the connection being up. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 QHash::findNode (ahp=0x0, akey=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:944 #5 QHash::contains (akey=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:924 #6 QSet::contains (value=..., this=0x56170e2f5120) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qset.h:97 #7 KdeConnectPlugin::sendPacket (this=0x56170e22d820, np=...) at ./core/kdeconnectplugin.cpp:73 #8 0x7ff27df426b4 in NotificationsDbusInterface::sendReply (this=0x56170e319320, replyId=..., message=...) at ./plugins/notifications/notificationsdbusinterface.cpp:178 #9 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712a00, r=0x56170e319320, this=0x56170e7c0e10) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x56170e228ce0, signal_index=10, argv=0x7ffdd5712a00) at kernel/qobject.cpp:3870 #11 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e228ce0, m=m@entry=0x7ff27df50b20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdd5712a00) at kernel/qobject.cpp:3930 #12 0x7ff27df3377b in SendReplyDialog::sendReply (this=this@entry=0x56170e228ce0, _t1=..., _t2=...) at ./obj-x86_64-linux-gnu/plugins/notifications/kdeconnect_notifications_autogen/EWIEGA46WW/moc_sendreplydialog.cpp:142 #13 0x7ff27df48fa0 in SendReplyDialog::sendButtonClicked (this=0x56170e228ce0) at ./plugins/notifications/sendreplydialog.cpp:53 #14 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712af0, r=0x56170e228ce0, this=0x56170e1e6470) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x56170e228ce0, signal_index=8, argv=0x7ffdd5712af0) at kernel/qobject.cpp:3870 #16 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e228ce0, m=m@entry=0x7ff28becf880 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #17 0x7ff28bbb5847 in QDialog::accepted (this=this@entry=0x56170e228ce0) at .moc/moc_qdialog.cpp:236 #18 0x7ff28bbb5ca8 in QDialogPrivate::finalize (this=, resultCode=1, dialogCode=) at dialogs/qdialog.cpp:176 #19 0x7ff28ae34550 in doActivate (sender=0x56170e4792e0, signal_index=8, argv=0x7ffdd5712bf0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #20 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e4792e0, m=m@entry=0x7ff28bec8820 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #21 0x7ff28bb4c2d7 in QDialogButtonBox::accepted (this=this@entry=0x56170e4792e0) at .moc/moc_qdialogbuttonbox.cpp:287 #22 0x7ff28bb4cb36 in QDialogButtonBoxPrivate::_q_handleButtonClicked (this=) at widgets/qdialogbuttonbox.cpp:878 #23 0x7ff28ae34550 in doActivate (sender=0x56170e496eb0, signal_index=9, argv=0x7ffdd5712d60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #24 0x7ff28ae2eaf7 in QMetaObject::activate (sender=sender@entry=0x56170e496eb0, m=m@entry=0x7ff28bebf700 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdd5712d60) at kernel/qobject.cpp:3930 #25 0x7ff28baa4c36 in QAbstractButton::clicked (this=this@entry=0x56170e496eb0, _t1=) at .moc/moc_qabstractbutton.cpp:313 #26 0x7ff28baa4e5e in QAbstractButtonPrivate::emitClicked (this=0x56170e492b70) at widgets/qabstractbutton.cpp:415 #27 0x7ff28baa5bc9 in QAbstractButton::click (this=0x56170e496eb0) at widgets/qabstractbutton.cpp:872 #28 QAbstractButton::click (this=0x56170e496eb0) at widgets/qabstractbutton.cpp:858 #29 0x7ff28ae3451e in QtPrivate::QSlotObjectBase::call (a=0x7ffdd5712e70, r=0x56170e496eb0, this=0x56170e65d1e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #30 doActivate (sender=0x56170e400b60, signal_index=3, argv=0x7ffdd5712e70) at kerne
[calligrawords] [Bug 378424] Crash on comment on docx file
https://bugs.kde.org/show_bug.cgi?id=378424 --- Comment #11 from jonathan.hae...@gmail.com --- Created attachment 131343 --> https://bugs.kde.org/attachment.cgi?id=131343&action=edit New crash information added by DrKonqi calligrawords (3.2.1) using Qt 5.15.0 - What I was doing when the application crashed: added a comment at the start of a line after an automatic line break - Custom settings of the application: Calligra Word 3.2.1, using the Open Serif font, aspell with German dictionary, KDEs Display Global Scale set to 125% -- Backtrace (Reduced): #4 0x7fa245f33b48 in QTextLine::y() const () from /usr/lib/libQt5Gui.so.5 #5 0x7fa2470fbdfe in KoTextDocumentLayout::positionAnchorTextRanges(int, int, QTextDocument const*) () from /usr/lib/libkotextlayout.so.17 #6 0x7fa2470deec1 in KoTextLayoutArea::layoutBlock(FrameIterator*) () from /usr/lib/libkotextlayout.so.17 #7 0x7fa2470e2264 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/libkotextlayout.so.17 #8 0x7fa2470f981f in KoTextLayoutRootArea::layoutRoot(FrameIterator*) () from /usr/lib/libkotextlayout.so.17 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 378424] Crash on comment on docx file
https://bugs.kde.org/show_bug.cgi?id=378424 jonathan.hae...@gmail.com changed: What|Removed |Added CC||jonathan.hae...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415240] Plasma shell on wayland crashes when an external monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=415240 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] New: [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 Bug ID: 426056 Summary: [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged Product: plasmashell Version: 5.19.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pos...@posteo.eu CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 131344 --> https://bugs.kde.org/attachment.cgi?id=131344&action=edit (External monitor plugged in) qdbus org.kde.KWin /KWin supportInformation SUMMARY Plasma automatically logs me out when the external HDMI connected TV (as the only screen), becomes unplugged. This happens only on Wayland for me. On X11 it changes the screen back to the laptop, but with scaling issues. STEPS TO REPRODUCE 1. Plugin in an external FullHD TV via HDMI 2. If Plasma doesn't automatically changes display configuration to "External Monitor only", make sure to display content only on the external device (haven't tested other cases yet) 3. Finally unplug the cable OBSERVED RESULT The screen goes back to the laptop for two seconds -- but with a wrong scaling (at least the panel is too big). It's not possible to interact with anything. Finally I become log out. EXPECTED RESULT Screen moves back to the laptop without any scaling issues or whatever. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 Kernel Version: 5.8.3-2-MANJARO Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION Scaling 2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 Postix changed: What|Removed |Added Flags||Wayland+, X11- CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426057] New: The shell freezes when MS Teams from Flatpak is launched
https://bugs.kde.org/show_bug.cgi?id=426057 Bug ID: 426057 Summary: The shell freezes when MS Teams from Flatpak is launched Product: plasmashell Version: 5.19.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bribb...@disroot.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Sadly I have to use MS Teams for school, and I do so with the Flatpak package from Flathub (com.microsoft.Teams). However when launching this application, the shell completely freezes. The panel can not be interacted with anymore, the clock widget doesn't update the time anymore, and the background can not be interacted with either. Even the application launcher, in my case the fullscreen dashboard, doesn't pop up anymore when I press the hotkey for it. Individual applications keep on working fine however, and so does latte-dock. I can also still switch workspaces using the configured hotkeys. STEPS TO REPRODUCE 1. Install com.microsoft.Teams from Flathub 2. Launch it 3. OBSERVED RESULT Plasmashell including any panels, widget and desktop completely freezes EXPECTED RESULT Everything to continue working as normal SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 426058] New: OpenConnect does not show up in list of configurable VPNs
https://bugs.kde.org/show_bug.cgi?id=426058 Bug ID: 426058 Summary: OpenConnect does not show up in list of configurable VPNs Product: plasma-nm Version: 5.18.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: k...@equaeghe.nospammail.net Target Milestone: --- SUMMARY I've installed plasma-nm with OpenConnect support. Also openconnect and networkmanager-openconnect are installed. However, when I try to add an OpenConnect VPN, the option is not present in the list. I've tried rebooting, but that doesn't work. In the system logs, searching for plasma-nm or openconnect, nothing is found. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425757] Drag and drop mp3s into audacious not possible anymore
https://bugs.kde.org/show_bug.cgi?id=425757 Nikos Chantziaras changed: What|Removed |Added CC||rea...@gmail.com --- Comment #1 from Nikos Chantziaras --- Same thing when trying to drag&drop image files into the eog (Eye Of Gnome) image viewer. Downgrading to Dolphin 20.04.3 fixes it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425956] deselect shortcut not working
https://bugs.kde.org/show_bug.cgi?id=425956 cyronozaurgamingrepub...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from cyronozaurgamingrepub...@gmail.com --- UPDATE: After testing things, apparently my keyboard got messed up after installing razer synapse, specifically, the Alexa module. This messed with the ctrl+shift+a shortcut. So the solution is remove the alexa module from the razer synapse to uninstall it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389046] Face suggestions disappair each time i confirm one
https://bugs.kde.org/show_bug.cgi?id=389046 --- Comment #20 from nono...@gmail.com --- (In reply to caulier.gilles from comment #19) > digiKam 7.0.0 stable release is now published: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Best Regards > > Gilles Caulier Hi, Sorry for my late reply. I will test with Digikam 7.0.0 as soon as i can; i think in the next days or week. Bye -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426054] Irregular display of thumbs and images in Import from CF card
https://bugs.kde.org/show_bug.cgi?id=426054 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED CC||metzping...@gmail.com Version Fixed In||7.1.0 Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- This problem has already been fixed in digiKam-7.1.0 with this commit: https://invent.kde.org/graphics/digikam/-/commit/928c9696426592fd15b7924860b28be8f12dd422 Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 bzanetti changed: What|Removed |Added CC||bzanett...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 --- Comment #1 from Postix --- Tried and confirmed it on a second laptop (Manjaro, too): 1) As scaling 1.0 is used, there's no scaling issue after plugging the cable out 2) The desktop freezes for ~ 10 seconds and finally I find myself logged out too. Like on the other system, I cleared the cache ~/.cache/* and rebooted before my tests. How can I further debug this issue for you? Which outputs / information do you need? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 Postix changed: What|Removed |Added OS|Other |Linux Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 425982] Session saving broken with KDE_APPLICATIONS_AS_SCOPE
https://bugs.kde.org/show_bug.cgi?id=425982 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/239 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] New: Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 Bug ID: 426059 Summary: Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper Product: kwin Version: 5.19.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 131345 --> https://bugs.kde.org/attachment.cgi?id=131345&action=edit (External monitor plugged out) qdbus org.kde.KWin /KWin supportInformation SUMMARY I use 2560x1440px screen on my notebook with scaling 2.0. When I plugin an external TV with 1920x1080 via HDMI and set the output to the external screen only, the displayed screen is fine. However, when I unplug the HDMI cable, the desktop panel and wallpaper have scaling issues, while all other applications still scale fine. Please see the screenshots. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 Kernel Version: 5.8.3-2-MANJARO Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION Scaling 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 --- Comment #1 from Postix --- Created attachment 131346 --> https://bugs.kde.org/attachment.cgi?id=131346&action=edit Screenshot 1: External monitor unplugged. Scaling 2.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425956] deselect shortcut not working
https://bugs.kde.org/show_bug.cgi?id=425956 --- Comment #5 from Tymond --- Thanks for coming back with that information! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 --- Comment #2 from Postix --- Created attachment 131347 --> https://bugs.kde.org/attachment.cgi?id=131347&action=edit Screenshot 2: As screenshot 1 but Kate closed => Wallpaper can be seen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 Postix changed: What|Removed |Added Platform|Other |Manjaro OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426059] Unplugging an external monitor on X11 leads to wrong scaled desktop panel and wallpaper
https://bugs.kde.org/show_bug.cgi?id=426059 Postix changed: What|Removed |Added Flags||Wayland?, X11+ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418141] Font rendering instantly gets better when you go to Tool Settings > go to Stroke panel > click 'No Fill'
https://bugs.kde.org/show_bug.cgi?id=418141 Tymond changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com CC||tamtamy.tym...@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #5 from Tymond --- I hope not :) -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 425982] Session saving broken with KDE_APPLICATIONS_AS_SCOPE
https://bugs.kde.org/show_bug.cgi?id=425982 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 425982] Session saving broken with KDE_APPLICATIONS_AS_SCOPE
https://bugs.kde.org/show_bug.cgi?id=425982 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||d24cef54d68fb29994ed610bc70 ||867d6fc811287 Status|ASSIGNED|RESOLVED --- Comment #10 from David Edmundson --- Git commit d24cef54d68fb29994ed610bc70867d6fc811287 by David Edmundson. Committed on 01/09/2020 at 13:01. Pushed by davidedmundson into branch 'master'. [ksmserver] Use UpdateLaunchEnvJob to sync SESSION_MANAGER env ksmserver starts in plasma-session. It currently sets the SESSION_MANAGER env back to just kinit and plasma-session which is then used for anything else that plasma-session starts. This is after start-plasma has synced the environment to DBus/systemd. By using the shared UpdateLaunchEnvJob we can sync all these places. M +4-6ksmserver/server.cpp https://invent.kde.org/plasma/plasma-workspace/commit/d24cef54d68fb29994ed610bc70867d6fc811287 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] ksysguard - delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de --- Comment #1 from David Redondo --- To make sure, you don't have the "close tab" option in the file menu? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 425982] Session saving broken with KDE_APPLICATIONS_AS_SCOPE
https://bugs.kde.org/show_bug.cgi?id=425982 --- Comment #11 from Ahmad Samir --- Thanks, that fixes the issue, i.e. dolphin, konsole... etc are saved/restored. However I still see this in the journal: Sep 01 15:27:23 homeBox sddm-helper[17980]: [PAM] Closing session Sep 01 15:27:23 homeBox sddm-helper[17980]: pam_unix(sddm:session): session closed for user ahmad Sep 01 15:27:23 homeBox sddm-helper[17980]: [PAM] Ended. Sep 01 15:27:23 homeBox sddm[687]: Auth: sddm-helper exited successfully Sep 01 15:27:23 homeBox sddm[687]: Socket server stopping... Sep 01 15:27:23 homeBox sddm[687]: Socket server stopped. Sep 01 15:27:23 homeBox sddm[687]: Display server stopping... Sep 01 15:27:23 homeBox plasmashell[18218]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox kglobalaccel5[18200]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox kaccess[18210]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox kwin_x11[18181]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox kactivitymanagerd[18193]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox kded5[18177]: Service "org.kde.StatusNotifierHost-18218" unregistered Sep 01 15:27:23 homeBox kded5[18177]: The X11 connection broke (error 1). Did the X11 server die? Sep 01 15:27:23 homeBox systemd-logind[489]: Session 8 logged out. Waiting for processes to exit. Sep 01 15:27:23 homeBox NetworkManager[676]: [1598966843.2940] device (eno1): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed') Sep 01 15:27:23 homeBox NetworkManager[676]: [1598966843.2944] manager: NetworkManager state is now DISCONNECTING -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- possibly duplicate of bug 419728 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426060] New: Icons unusable small if panel height >> horizontal space for icon entry
https://bugs.kde.org/show_bug.cgi?id=426060 Bug ID: 426060 Summary: Icons unusable small if panel height >> horizontal space for icon entry Product: plasmashell Version: 5.19.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: pos...@posteo.eu CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 131348 --> https://bugs.kde.org/attachment.cgi?id=131348&action=edit Screenshot. SUMMARY If the icons only task manager is used it may happen that depending on the number of entries, the scaling and the panel height, the icons become unusable small. Please see the screenshot. One can also observe that the virtual desktop switcher scales fine with an increasing panel height, i.e. taking more with a bigger panel, while, the taskbar icons don't like to be scaled only in y-direction and eventually become so narrow that the even icons won't be displayed any longer. Maybe a minimal and sane icon size can defined and if the space becomes too small, a drop down panel like for the systemtray could be used to display icons which no longer fit? Probably you know a better solution? At least that would keep it usable -- even if the vertical / horizontal scaling of the icons are far off being ~ 1. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Scaling: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 --- Comment #3 from Postix --- (In reply to Patrick Silva from comment #2) > possibly duplicate of bug 419728 Can you please quickly tell me how I can get the debug log / crash log if there's one? I'd like to test it ASAP. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426060] Icons unusable small if panel height >> horizontal space for icon entry
https://bugs.kde.org/show_bug.cgi?id=426060 Postix changed: What|Removed |Added Keywords||usability CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 Postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426060] Icons unusable small if panel height >> horizontal space for icon entry
https://bugs.kde.org/show_bug.cgi?id=426060 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424259] plasmashell produces a lot of warnings in the journal
https://bugs.kde.org/show_bug.cgi?id=424259 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #10 from Ahmad Samir --- FTR, reading the MR, for the fix to take effect one needs to be running Qt 5.15.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 Postix changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Postix --- Very likely a duplicate. Will look for a crash log later. *** This bug has been marked as a duplicate of bug 419728 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 --- Comment #2 from Postix --- *** Bug 426056 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419728] kwin_wayland crashes when external monitor is disconnected from hdmi port while multi-monitor mode is set to "Switch to external screen"
https://bugs.kde.org/show_bug.cgi?id=419728 Postix changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 426061] New: Build failure with ragel 7.x
https://bugs.kde.org/show_bug.cgi?id=426061 Bug ID: 426061 Summary: Build failure with ragel 7.x Product: trojita Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: j...@kde.org Target Milestone: --- This was reported in Fedora [1] and Gentoo [2]. I have yet to get a proper error message for this -- and of course, patches welcome. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1734036 [2] https://bugs.gentoo.org/739866 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426056] [Wayland] Plasma automatically logs out when external HDMI monitor is unplugged
https://bugs.kde.org/show_bug.cgi?id=426056 --- Comment #5 from Patrick Silva --- I use gdbserver, ssh and gdb to remotely get backtrace of kwin_wayland crashes. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425896] Kate toolbars appear and disappear
https://bugs.kde.org/show_bug.cgi?id=425896 Arek changed: What|Removed |Added CC||domk...@wp.pl --- Comment #1 from Arek --- This bug also occurs with Arch Linux and is annoying. I use the Kate editor quite often, and in addition to the disappearing buttons on the toolbar, the context menu is also deactivated. Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.5-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387617] Konsole profiles forgets about 'draw intense color as bold'
https://bugs.kde.org/show_bug.cgi?id=387617 Aryan Mavalvala changed: What|Removed |Added CC||aryan4...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425736] Kdenlive never launches
https://bugs.kde.org/show_bug.cgi?id=425736 --- Comment #3 from emohr --- I'm not an expert on Linux. Maybe you can try the PPA from here: https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable to check if that runs. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425978] kdenlive is not rendering properly on Windows 10 version 20.08.0
https://bugs.kde.org/show_bug.cgi?id=425978 emohr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/-/commit/45 ||cbc455938173523a3c3c2c1f90c ||4ebf9a30ad8 Version Fixed In||20.08.2 --- Comment #4 from emohr --- Will be fixed with 20.08.2. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425925] Black Screen Problem
https://bugs.kde.org/show_bug.cgi?id=425925 emohr changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/-/commit/45 ||cbc455938173523a3c3c2c1f90c ||4ebf9a30ad8 Version Fixed In||20.08.2 Status|NEEDSINFO |RESOLVED --- Comment #9 from emohr --- Thank you for the feedback and contribution. Glad to hear it works. Will be fixed with 20.08.2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426062] New: "Customize Krita" Window vanishes from screen and appears to be "next to" the visible screen
https://bugs.kde.org/show_bug.cgi?id=426062 Bug ID: 426062 Summary: "Customize Krita" Window vanishes from screen and appears to be "next to" the visible screen Product: krita Version: 4.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: trash4m...@gmail.com Target Milestone: --- SUMMARY "Customize Krita" Window vanishes from screen and appears to be "next to" the visible screen STEPS TO REPRODUCE 1. Settings > Customize Krita 2. Try to adjust vertical size of the window by dragging on the top edge of the window OBSERVED RESULT Window clips out of the screen and it can't be accessed anmore. As the window is in front of the running main application, krita can't be accessed nor closed anymore, only way to close it is the taskmanager. EXPECTED RESULT The window should just adjust its size without vanishing from the screen. SOFTWARE/OS VERSIONS Windows: 10 Home Version 1909 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426062] "Customize Krita" Window vanishes from screen and appears to be "next to" the visible screen
https://bugs.kde.org/show_bug.cgi?id=426062 Tymond changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||tamtamy.tym...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from Tymond --- Please attach the content of Help -> Show system information for bug reports. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425724] non-white animated text is the wrong color
https://bugs.kde.org/show_bug.cgi?id=425724 emohr changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Version|20.04.3 |20.08.0 Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Flags|timeline_corruption+|Brainstorm+ --- Comment #6 from emohr --- Thank you for the details. I can confirm the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426063] New: Please consider improving the "The shared library was not found" error message, in particular with a way for the user to obtain more information about this, e. g. no
https://bugs.kde.org/show_bug.cgi?id=426063 Bug ID: 426063 Summary: Please consider improving the "The shared library was not found" error message, in particular with a way for the user to obtain more information about this, e. g. notifying them what exactly could not be found Product: systemsettings Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sheve...@gmail.com Target Milestone: --- Hello KDE devs and everyone who may read such bug reports or issue requests, I think I may have reported something similar before, in other KDE widgets. At any rate, my issue is with this error message here specifically: "The shared library was not found." See the following picture: https://i.imgur.com/eoQa7r3.png This is from systemsettings5, on a black KDE konsole background; I chopped it up quickly to just show the problem. The problem is on the right side: "The shared library was not found" The URL I was using, just to provide this info as well, was this: https://download.kde.org/stable/plasma/5.19.5/systemsettings-5.19.5.tar.xz I should add that I batch-compile all of KDE from source, so with the today's release of a new plasma, I am compiling stuff again. So I may have multiple different versions on the computer, since when I am lazy, I just compile into /usr/ as the main prefix, even though I also use a versioned AppDir layout sometimes (see GoboLinux for this, such as /Programs/Htop/2.2.0 - do note that they have not been able to keep up with KDE5 though. The last KDE release on GoboLinux was KDE3.) As a consequence of me compiling from source, on a modified slackware/zenwalk base system, I encounter some issues now and then with KDE5 - not so much during compilation usually, but lateron, such as when trying to start kwin from oldschool runlevel init 3, but also in using specific individual applications. Some work very well, such as KDE konsole or okular; others work less well, or are a bit strange, such as the systemsettings5 binary. This feature request here is such an example for the "lateron" problem - that is problems that show up when running the application at hand. In regards to systemsettings5, some parts of this widget work really fine, without problems, such as "Shortcuts". See the above screenshot what is meant; that widget is shown decently and it works. "Window Behavior" also works fine - shows everything. But other parts, such as "Display and Monitor", do not work, and instead show a generic "The shared library was not found". This message, as we can all agree, is almost TOTALLY useless. Because it tells me NOTHING. I have to ask here: "what shared library exactly was not found?". I mean, it is better than nothing, but still quite useless. I assume that it refers to some installed component that may be too old or not compatible, but I'd still like to know WHAT exactly is the issue. As it is right now, the message "The shared library was not found" is about as useful as "Aliens have taken over your computer and rendered it useless" - although one could reasonably argue that that message is better than "The shared library was not found", because at the least it identified SOME Aliens as being behind the culprit. With systemsettings, though, we are currently left in the dark. I have noticed this, by the way, in other widgets too - in okular in the past, for example. So I assume that this is more related in general to how KDE wants to present information to end users. I am fine if you assume that the default end user is Average Joe, so you may not want to burden him with too much information - but then there should be an OPTIONAL way to query more information, and ideally in a per-widget or per-application centric way because not everyone may use KDE5. I use mostly individual KDE5 applications. (I'd use KDE5, but I can not successfully start it, but this is a separate issue not related to the issue request here. Note that I can compile mate-desktop from source, and run it from inittab runlevel 3 just fine. Some problems may also originate from qt5, such as qml-related problems, but I don't want to make this issue request here too off-topic. My primary point is for usability improvements and better error reporting WITHIN KDE5/Plasma itself.) On the commandline I may typically do "ldd" on some binary, and if some shared object is missing, I tend to get some message there, such as "missing /usr/lib/libtarzan.so" or something like this. (Could be better too, but I digress here as well). Anyway - I hope I could explain the use case leading to the above issue request. What I would like to see here specifically is that the error message "shared library" becomes MORE SPECIFIC.
[okular] [Bug 426020] Okular crashes when attempting to open .cbr files
https://bugs.kde.org/show_bug.cgi?id=426020 --- Comment #8 from Ben Schröder --- (In reply to Albert Astals Cid from comment #7) > Please run kdebugsettings > inside it search for comic and in the okular comicbook generator change the > setting to full debug > > Then run okular, try to open a cbr and it will say something like > > org.kde.okular.generators.comicbook: detected: "/usr/bin/unar" ( "unar" ) > > Can you post exactly what you get? Sadly kdebugsettings does not want to open on my machine, here is the log: qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. error: XDG_RUNTIME_DIR not set in the environment. Failed to create wl_display (No such file or directory) qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted I have already tried to reinstall KDE but it still won't launch. This problem first occured with the KDE/Qt Version shipped in Open Suse Tumbleweed Build 20200826. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426064] New: Okular is unable to load print previews of PDFs
https://bugs.kde.org/show_bug.cgi?id=426064 Bug ID: 426064 Summary: Okular is unable to load print previews of PDFs Product: okular Version: 1.11.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: aayush.agarwal...@yahoo.com Target Milestone: --- SUMMARY Okular is not loading print previews. STEPS TO REPRODUCE 1. Open Okular 2. Load any PDF 3. File>Print Preview OBSERVED RESULT A window which says "could not load print preview part". EXPECTED RESULT A print preview of the PDF, based on my printer page layout. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE tumbleweed 20200826 snapshot (Linux 5.8.2-1-default (71b519a) x86_64 GNU/Linux) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15 okular Version: 1.11.0 ADDITIONAL INFORMATION Opening okular from command line provided me a hint: org.kde.okular.ui: Could not find a PS viewer for the preview dialog. When I tried to load a print preview for a .odt file, the preview loaded successfully. I don't have files in many different supported formats so I have not checked all of them. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426065] New: Make Popup Windows Use Global Sheet
https://bugs.kde.org/show_bug.cgi?id=426065 Bug ID: 426065 Summary: Make Popup Windows Use Global Sheet Product: Discover Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: anditosan1...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Popup windows should have a globalsheet property to look the same as the rest of popups in Discover. Even though the left menu is active and not darkened, this makes it visually inconsistent to the rest of popups within Discover. At the same time, the interaction on the un-darkened section bears no changes to the popup window. Therefore, if there is no effect, it makes no difference in keeping looks consistent. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Differences shown in this post: https://pointieststick.com/2020/08/28/this-week-in-kde-tons-and-tons-and-tons-of-plasma-5-20-features-bugfixes-and-ui-improvements/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426062] "Customize Krita" Window vanishes from screen and appears to be "next to" the visible screen
https://bugs.kde.org/show_bug.cgi?id=426062 --- Comment #2 from trash4m...@gmail.com --- The content from help > Show system information for bug reports is: Krita Version: 4.3.0 Languages: de_DE, de, en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18363 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "ATI Technologies Inc." Renderer: "AMD Radeon(TM) Vega 3 Graphics" Version: "3.0.13558 Compatibility Profile Context 26.20.11016.5002" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false Hardware Information GPU Acceleration: auto Memory: 3522 Mb Number of Cores: 4 Swap Location: C:/Users/maxim/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/maxim/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: true Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 2 Resolution in pixels: 960x540 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426063] Please consider improving the "The shared library was not found" error message, in particular with a way for the user to obtain more information about this, e. g. notifyi
https://bugs.kde.org/show_bug.cgi?id=426063 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- >(I am not quite familiar how active KDE bugzilla still is; Yes, bugzilla is still the right place. As for the module not loading: Building from source doesn't delete old files, so you have a clash between a (dead) .desktop file pointing to a library in one place, and the real library somewhere else with embedded metadata. This is somewhat hinted at in the "possible reasons" section at the bottom of that page. Before progressing with anything else, I thought we had switched in recent frameworks to prefer the newer version. Can you confirm your framework versions please? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 426066] New: Keyboard shortcuts (for increasing/decreasing video speed playback) on Youtube don't work
https://bugs.kde.org/show_bug.cgi?id=426066
Bug ID: 426066
Summary: Keyboard shortcuts (for increasing/decreasing video
speed playback) on Youtube don't work
Product: Falkon
Version: 3.1.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: now...@gmail.com
Reporter: marian...@web.de
Target Milestone: ---
SUMMARY
When watching videos on Youtube, the user should be able to increase and
decrease the video playback speed by using "Shift+." and "Shift+," like
mentioned here:
https://sites.google.com/a/umich.edu/u-m-google-170816/accessibility/google-keyboard-shortcuts---youtube
Unfortunately this doesn't seem to work on a german keyboard. Using the other
shortcut mentioned on that site ("Shift+>") does work to increase the video
playback speed, but it's not possible to decrease it again, because "<" and ">"
are on the same key on a german keyboard (and the shortcut for decreasing it is
"Shift+<").
STEPS TO REPRODUCE
1. Use a german keyboard with german keyboard layout
2. Go to youtube.com and open a video
3. Press "Shift+." or "Shift+,"
OBSERVED RESULT
Nothing happens.
EXPECTED RESULT
Video playback speed should increase/decrease.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro stable, Kernel 5.4.60-2
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73
Qt Version: 5.15
ADDITIONAL INFORMATION
It works flawlessly with Firefox and Chromium.
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 426067] New: Same song plays twice back-to-back when shuffling
https://bugs.kde.org/show_bug.cgi?id=426067 Bug ID: 426067 Summary: Same song plays twice back-to-back when shuffling Product: elisa Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: danielpet...@outlook.com Target Milestone: --- SUMMARY When shuffling, the same song occasionally plays back-to-back STEPS TO REPRODUCE 1. Have a playlist 2. Turn on shuffle 3. Turn on repeat 4. Play 5. Listen for a while OBSERVED RESULT Every so often, the same song repeats twice in a row EXPECTED RESULT The same song should not play twice in a row SOFTWARE/OS VERSIONS Kubuntu: 20.04 Linux/KDE Plasma: 5.40-45-generic (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Elisa version: 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426068] New: Plasma failed after moving file to a new folder
https://bugs.kde.org/show_bug.cgi?id=426068 Bug ID: 426068 Summary: Plasma failed after moving file to a new folder Product: plasmashell Version: 5.12.9 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: joaormane...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.9) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.4.0-42-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: I was moving two files to a new folder, the menu asking what I wanted to do was prompted and after I released the mouse button to click on "Move here", the desktop environment crashed. - Unusual behavior I noticed: Plasma crashed after trying to move files to a new folder. -- Backtrace: Application: Plasma (plasmashell), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e32f3e800 (LWP 1804))] Thread 10 (Thread 0x7f0d6defa700 (LWP 2001)): #0 0x7f0e270d4629 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0e2708e5af in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e2708e6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e2ce688ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0e2ce0d90a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0e2cc2c23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0e309382a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f0e2cc3117d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0e2bdb26db in start_thread (arg=0x7f0d6defa700) at pthread_create.c:463 #9 0x7f0e2c52ca3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f0d7f538700 (LWP 1947)): #0 0x7f0e2bdb89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c56fcb63bc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0e2bdb89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55c56fcb6368, cond=0x55c56fcb6390) at pthread_cond_wait.c:502 #2 0x7f0e2bdb89f3 in __pthread_cond_wait (cond=0x55c56fcb6390, mutex=0x55c56fcb6368) at pthread_cond_wait.c:655 #3 0x7f0d81d0873b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0d81d08327 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0e2bdb26db in start_thread (arg=0x7f0d7f538700) at pthread_create.c:463 #6 0x7f0e2c52ca3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f0d7fd39700 (LWP 1946)): #0 0x7f0e2bdb89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c56fcb63bc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0e2bdb89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55c56fcb6368, cond=0x55c56fcb6390) at pthread_cond_wait.c:502 #2 0x7f0e2bdb89f3 in __pthread_cond_wait (cond=0x55c56fcb6390, mutex=0x55c56fcb6368) at pthread_cond_wait.c:655 #3 0x7f0d81d0873b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0d81d08327 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0e2bdb26db in start_thread (arg=0x7f0d7fd39700) at pthread_create.c:463 #6 0x7f0e2c52ca3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f0d8053a700 (LWP 1945)): #0 0x7f0e2bdb89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c56fcb63bc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0e2bdb89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55c56fcb6368, cond=0x55c56fcb6390) at pthread_cond_wait.c:502 #2 0x7f0e2bdb89f3 in __pthread_cond_wait (cond=0x55c56fcb6390, mutex=0x55c56fcb6368) at pthread_cond_wait.c:655 #3 0x7f0d81d0873b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f0d81d08327 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f0e2bdb26db in start_thread (arg=0x7f0d8053a700) at pthread_create.c:463 #6 0x7f0e2c52ca3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f0d80d3b700 (LWP 1944)): #0 0x7f0e2bdb89f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c56fcb63bc) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0e2bdb89f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55c56fcb6368, cond=0x55c56fcb6390) at pthread_cond_wait.c:502 #2 0x7f0e2bdb89f3 in __pthread_cond_wait (cond=0x55c56fcb6390, mutex=0x55c56fcb6368) at pthread_cond_wait.c:655 #3 0x7f0d81d0873b in () at /usr/lib/x86_64-lin
[kwin] [Bug 426069] New: XWayland apps are occasionally not rendered when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426069 Bug ID: 426069 Summary: XWayland apps are occasionally not rendered when switching virtual desktops Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY Not entirely sure whether this is the correct product, please send it to the correct one if it's not kwin. I've been affected by this bug for a few months at least. I usually have 4 or 6 virtual desktops (VDs) at any given time. Usually I have several XWayland apps running maximized, be they Electron (Slack) or not (Telegram), normal packages (Kontact) or from Flatpak (WPS Office). On occasion, switching to another VD renders the app invisible. In such a state, opening any application and moving it on top of the invisible one creates a graphical glitch. This issue most notably occurs with WPS Office, Kontact and Chromium, and never with wayland telegram or Kate, which leads me to think it's related to XWayland. It takes a while to reproduce, but it is reproduced consistently. By this I mean that it is not reproducible every single time you switch a VD, but if you test it enough you will inevitably reproduce this issue (just be patient). It is also not related to the number of cycles, as it may appear after 5 cycles or 20 cycles. I am not sure whether clicking a task icon reproduces this as it takes much more time to reproduce. Same with Meta+number keyboard shortcuts. I'll test this later. STEPS TO REPRODUCE 1. Create three virtual desktops in a wayland session, easiest to reproduce with them in line 2. Have one maximized application in each of them, at least one running on XWayland 3. Cycle between them using a keyboard shortcut OBSERVED RESULT Application is not rendered EXPECTED RESULT Application should appear as normal SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200823 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426044] Header bar line disappears during update process
https://bugs.kde.org/show_bug.cgi?id=426044 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426070] New: Deadlock in ~QQmlEngine() inside ~WelcomePageWidget() when exiting KDevelop right after starting it - before Welcome Page is loaded
https://bugs.kde.org/show_bug.cgi?id=426070 Bug ID: 426070 Summary: Deadlock in ~QQmlEngine() inside ~WelcomePageWidget() when exiting KDevelop right after starting it - before Welcome Page is loaded Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: igor...@gmail.com Target Milestone: --- SUMMARY This deadlock is extremely easy to reproduce: start KDevelop and exit it as soon as possible => KDevelop fails to exit, i.e. the process remains running. I have reproduced it in Debug and Release KDevelop builds; with several small projects open, with an empty session and with a new empty session. For example, launch KDevelop with the following command: `kdevelop -n tmp` (or `kdevelop -s tmp` if the "tmp" session already exists). SOFTWARE/OS VERSIONS Manjaro GNU/Linux, Xfce KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION This deadlock is clearly an upstream issue: QTBUG-75777. When I apply the patch that fixes it (https://codereview.qt-project.org/c/qt/qtdeclarative/+/263540), the deadlock doesn't happen. When I run the following command while KDevelop process is deadlocked (replace "123456" with the kdevelop process ID): gdb -batch -ex "thread apply all bt" -ex "quit" -p 123456 > kdevelop-deadlock.bt I always get a backtrace very similar to the one pasted below. When I run the same gdb command a few seconds, minutes or even an hour later for the same deadlocked process, I get exactly the same backtrace. BACKTRACE (with debugging symbols for KDevelop, qtbase and qtdeclarative) [New LWP 463276] [New LWP 463277] [New LWP 463278] [New LWP 463279] [New LWP 463280] [New LWP 463281] [New LWP 463282] [New LWP 463283] [New LWP 463284] [New LWP 463285] [New LWP 463286] [New LWP 463287] [New LWP 463293] [New LWP 463294] [New LWP 463295] [New LWP 463296] [New LWP 463297] [New LWP 463298] [New LWP 463299] [New LWP 463300] [New LWP 463302] [New LWP 463306] [New LWP 463308] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". 0x7f60e47066a2 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 Thread 24 (Thread 0x7f6074bd3640 (LWP 463308)): #0 0x7f60e51ca46f in poll () at /usr/lib/libc.so.6 #1 0x7f60e1c94168 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f60e1c45221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f60e58eb331 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f605c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f60e589113c in QEventLoop::exec(QFlags) (this=this@entry=0x7f6074bd2880, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f60e56acc32 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f60e56ade0f in QThreadPrivate::start(void*) (arg=0x7f60e82b28e8 ) at thread/qthread_unix.cpp:342 #7 0x7f60e47003e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f60e51d5293 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f60755fa640 (LWP 463306)): #0 0x7f60e51ca46f in poll () at /usr/lib/libc.so.6 #1 0x7f60e1c94168 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f60e1c45221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f60e58eb331 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6068000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f60e589113c in QEventLoop::exec(QFlags) (this=this@entry=0x7f60755f9880, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f60e56acc32 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f60e56ade0f in QThreadPrivate::start(void*) (arg=0x55db3c9960f0) at thread/qthread_unix.cpp:342 #7 0x7f60e47003e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f60e51d5293 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f60777fe640 (LWP 463302)): #0 0x7f60e47066a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f60e56b3e84 in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., deadline=..., this=0x55db3c87ff00) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55db3c87fe58, mutex=mutex@entry=0x55db3c87fe50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f60e76a200b in QQmlThreadPrivate::wait() (this=0x55db3c87fde0) at /usr/include/qt/QtCore/qdeadlinetimer.h:68 #4 QQmlThread::internalCallMethodInMain(QQmlThread::Message*) (this=0x55db3c87fc80, message=) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.0/src/qml/qml/ftw/qqmlth
[kwin] [Bug 426071] New: Apps occasionally lose interactivity when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426071 Bug ID: 426071 Summary: Apps occasionally lose interactivity when switching virtual desktops Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY This issue is similar to https://bugs.kde.org/show_bug.cgi?id=426069 , but it is harder to reproduce, which is why I delayed this report. In addition, I'm not sure this issue occurs only with XWayland apps. I've also been affected by this bug for a few months. Both issues might be related. Sometimes cycling between virtual desktops containing one maximized application each via keyboard shortcut makes the application be rendered, but impossible to interact with. This includes keyboard focus and mouse clicks, although attempting to move it by dragging the titlebar does move it properly. Any attempts to change its window state (maximize, restore etc) shows the respective visual effects, but does not nulify this issue. This issue has most notably occurred with Telegram, WPS Office and Chromium. STEPS TO REPRODUCE 1. Create three virtual desktops in a wayland session, easiest to reproduce with them in line 2. Have one maximized application in each of them, wherein each application shows a blinking text cursor 3. Cycle between them using a keyboard shortcut 4. Unlike the linked bug report, this one requires more attention as you may only notice it when the cursor blinking stops, and it's more difficult to reproduce OBSERVED RESULT Window can be seen, but can't be interacted with EXPECTED RESULT Window can be seen and should be interactive SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200823 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|INTENTIONAL |--- --- Comment #11 from Claudius Ellsel --- (In reply to David Edmundson from comment #6) > >but there is no argument from a user perspective for not having it in System > >Settings. > > I haven't seen a valid argument for having it either. > > Why does this belong in systemsettings, but whether the batter applet on > your second panel shows a percentage or an icon does not? I'd consider that also discussable and maybe desirable if one could come up with a good plan to make panels configurable through systemsettings. (In reply to David Edmundson from comment #7) > I'm closing this till someone gives a reason why it should be there. > > Feel free to reopen if you can. Ideally with some solutions for the > cardinality problem. I will give some points: - Users expect it to be in systemsettings. Partly because other desktop environments and operating systems handle it that way - GNOME and Windows for example. But that is not the only reason one would expect to have that setting there. - Other design options are offered in systemsettings, so one kind of expects to also have wallpaper options there. Especially if one is not familiar with the technical details behind virtual desktops and activities. - Users might not be familiar with the concept of "right clicks", one might debate whether we should consider those users, but just wanted to mention that. I hope those points offer enough reason to reopen this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426069] XWayland apps are occasionally not rendered when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426069 --- Comment #1 from Thiago Sueto --- Forgot to mention: despite not seeing anything, I can still manipulate the window by dragging it by its titlebar. Additionally, I managed to get lucky just now and reproduced it by Meta+number. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426069] XWayland apps are occasionally not rendered when switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426069 --- Comment #2 from Thiago Sueto --- Similarly to https://bugs.kde.org/show_bug.cgi?id=426071 , any attempts to change its window state (maximize, restore etc) shows the respective visual effects, but does not nulify this issue. Except for one: if I minimize it and restore it, the issue is gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426072] New: kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff
https://bugs.kde.org/show_bug.cgi?id=426072 Bug ID: 426072 Summary: kwin_wayland crashes when I hover over task manager after dragging an entry from it to kickoff Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. start Wayland session 2. open an app and minimize it 3. drag the open app from task manager to kickoff icon and do not release the mouse button (kickoff opens) 4. drag the app to desktop and do not release the mouse button yet 5. now drag the app to task manager OBSERVED RESULT kwin_wayland crashes EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Thread 11 (Thread 12429.12959): #0 0x7f8cfe17543e in epoll_wait (epfd=113, events=0x7f8c41f3e9b0, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7f8ccc9653fb in ?? () from target:/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7f8ccc963080 in ?? () from target:/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7f8cffe20180 in ?? () from target:/lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7f8cffa50609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f8cfe175103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 12429.12447): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f8cfdf22fb8 ) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f8cfdf22f68 , cond=0x7f8cfdf22f90 ) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=cond@entry=0x7f8cfdf22f90 , mutex=mutex@entry=0x7f8cfdf22f68 ) at pthread_cond_wait.c:638 #3 0x7f8cfde2561a in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f8cfdf14ec0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #4 0x7f8cfde2563f in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #5 0x7f8cffa50609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f8cfe175103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 12429.12438): #0 0x7f8cfe16896f in __GI___poll (fds=0x7f8cc8004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8cfc1081ae in ?? () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8cfc1082e3 in g_main_context_iteration () from target:/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8cfe8831e2 in QEventDispatcherGlib::processEvents (this=0x7f8cc8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f8cfe82924b in QEventLoop::exec (this=this@entry=0x7f8ce4b3fd80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f8cfe64beb2 in QThread::exec (this=this@entry=0x55baa12332c0) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x7f8cfd2f9b99 in QQmlThreadPrivate::run (this=0x55baa12332c0) at qml/ftw/qqmlthread.cpp:155 #7 0x7f8cfe64d01c in QThreadPrivate::start (arg=0x55baa12332c0) at thread/qthread_unix.cpp:342 #8 0x7f8cffa50609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f8cfe175103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 12429.12436): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55baa1454d28) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55baa1454cd8, cond=0x55baa1454d00) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=cond@entry=0x55baa1454d00, mutex=mutex@entry=0x55baa1454cd8) at pthread_cond_wait.c:638 #3 0x7f8cf4ff997b in cnd_wait (mtx=0x55baa1454cd8, cond=0x55baa1454d00) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55baa12741e0) at ../src/util/u_queue.c:275 #5 0x7f8cf4ff958b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f8cffa50609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f8cfe175103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 12429.12435): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55baa1454d28) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55baa1454cd8, cond=0x55baa1454d00) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=cond@entry=0x55baa1454d00, mutex=mutex@entry=0x55baa1454cd8) at pthread_cond_wait.c:638 #3 0x7f8cf4ff997b in cnd_wait (mtx=0x55baa1454cd8, cond=0x55baa1454d00) at ../include/c11/threads_posix.h:15
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 Claudius Ellsel changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=367666 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367666] Add option to change wallpaper for lock screen, login screen, and desktop all at once
https://bugs.kde.org/show_bug.cgi?id=367666 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de See Also||https://bugs.kde.org/show_b ||ug.cgi?id=391485 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417888] [Wayland] activating minimized window from another virtual desktop adds window to current virtual desktop
https://bugs.kde.org/show_bug.cgi?id=417888 --- Comment #5 from Thiago Sueto --- Now I get it, managed to reproduce it consistently. I also used this fix the whole day and it works fine so far. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 408137] QCA::TLS handshaken is emitted with a broken certificate instance leading to a crash
https://bugs.kde.org/show_bug.cgi?id=408137 Sergey changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Sergey --- Well since I took maintainership of QCA fork, I tried to review it myself. But all the code looks pretty valid for me. Moreover original the reporter told me it didn't crash for him for awhile. And same for me. So likely it's neither QCA or Psi problem. It's something else. I'm closing this issue since there is nothing more to investigate and it's better to have a coredump from debug version next time. -- You are receiving this mail because: You are watching all bug changes.
