[kwin] [Bug 449797] Plasma 5.24 and nvidia GPU and multiple screens: segfault in KWin::GbmSurface::swapBuffersForDrm()
https://bugs.kde.org/show_bug.cgi?id=449797 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #14 from Bart --- same over here. Single screen. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459949] Plasma Popups keep centering under wayland
https://bugs.kde.org/show_bug.cgi?id=459949 bart changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=459188 CC||de.roy.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 bart changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=459949 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452632] plasmashell crash after activating compositor
https://bugs.kde.org/show_bug.cgi?id=452632 --- Comment #1 from Bart --- Created attachment 148167 --> https://bugs.kde.org/attachment.cgi?id=148167&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452632] New: plasmashell crash after activating compositor
https://bugs.kde.org/show_bug.cgi?id=452632 Bug ID: 452632 Summary: plasmashell crash after activating compositor Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: b...@schelstraete.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.80) Qt Version: 5.15.3 Frameworks Version: 5.94.0 Operating System: Linux 5.17.0-1.1-liquorix-amd64 x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.24.80 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: plasmashell crash after activating compositor. Used to work. The crash can be reproduced every time. -- Backtrace (Reduced): #7 0x561fc052e046 in qobject_cast(QObject*) (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:519 #8 QtPrivate::QVariantValueHelper::object(QVariant const&) (v=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:753 #9 QtPrivate::ObjectInvoker, QVariant const&, QObject*>::invoke(QVariant const&) (a=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:107 #10 qvariant_cast(QVariant const&) (v=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:879 #11 QVariant::value() const (this=0x7439ca10) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:367 Possible duplicates by query: bug 452073, bug 452001, bug 451880, bug 451864, bug 451777. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452632] plasmashell crash after activating compositor
https://bugs.kde.org/show_bug.cgi?id=452632 Bart changed: What|Removed |Added CC||b...@schelstraete.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] External images not loaded by default if message was opened in a separate window
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #29 from Bart --- Four years after reporting it, I really appreciate it, really really no malice :D -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429390] Screenshot taken on Wayland via keyboard shortcuts is not copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=429390 Bart changed: What|Removed |Added CC||b...@schelstraete.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 Bart changed: What|Removed |Added CC||b...@schelstraete.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 --- Comment #19 from Bart --- Created attachment 139322 --> https://bugs.kde.org/attachment.cgi?id=139322&action=edit klipper klipper -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 --- Comment #20 from Bart --- Comment on attachment 139322 --> https://bugs.kde.org/attachment.cgi?id=139322 klipper @nate: See "https://bugs.kde.org/attachment.cgi?id=139322";. Empty entry in klipper. Using latest Kde neon dev builds, wayland,but dual screen + scaling. (not sure if this matters) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409798] Spectacle Copy To Clipboard Doesn't Work Properly Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409798 Bart changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 --- Comment #1 from Bart --- Created attachment 137342 --> https://bugs.kde.org/attachment.cgi?id=137342&action=edit New crash information added by DrKonqi kwin_x11 (5.21.80) using Qt 5.15.2 - What I was doing when the application crashed: Kwin crashes on start, completely unusable. This after latest unstable updates. worked fine last week. -- Backtrace (Reduced): #4 0x7f56f7cfc254 in KWin::Item::height() const () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #5 0x7f56f7cfc2e2 in KWin::Item::size() const () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #6 0x7f56f7cfc30d in KWin::Item::rect() const () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #7 0x7f56f7d9e583 in KWin::Unmanaged::initialize() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7f56f68b82c6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7b4cca30, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 Bart changed: What|Removed |Added CC||b...@schelstraete.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 --- Comment #2 from Bart --- fyi: no crashes on wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 --- Comment #3 from Bart --- Created attachment 137343 --> https://bugs.kde.org/attachment.cgi?id=137343&action=edit New crash information added by DrKonqi kwin_x11 (5.21.80) using Qt 5.15.2 - What I was doing when the application crashed: this is with backtrace added. (wasn't able to do that previous time :p ) -- Backtrace (Reduced): #4 KWin::Item::height() const (this=this@entry=0x0) at ./src/item.cpp:77 #5 0x7fcf4576f2e2 in KWin::Item::size() const (this=0x0) at ./src/item.cpp:180 #6 0x7fcf4576f30d in KWin::Item::rect() const (this=) at ./src/item.cpp:208 #7 0x7fcf45811583 in KWin::Unmanaged::initialize() (this=) at ./src/unmanaged.cpp:80 #8 0x7fcf4432b2c6 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe0e374210, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 --- Comment #7 from Bart --- alos resolved over here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435322] Near-constant KWin crashes on X11
https://bugs.kde.org/show_bug.cgi?id=435322 --- Comment #8 from Bart --- also* -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 447470] Grub menu tiny on high DPI display
https://bugs.kde.org/show_bug.cgi?id=447470 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #1 from Bart --- Hi, You need to change the resolution within grub, which is advised if you have a 4k screen for example. (grub is also very slow on 4k screens) in /etc/default/grub file, and add/replace the following line= GRUB_GFXMODE=1280x1024x32,auto Then run “update-grub” to update the GRUB. This will run GRUB in 1280x1024x32 resolution, which is the workaround for this problem. Please make sure the resolutiion is supported. The “auto” means that GRUB will fallback to auto detect in case the resolution isn’t supported. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425805] New: Kmail crash, doesn't start anymore
https://bugs.kde.org/show_bug.cgi?id=425805 Bug ID: 425805 Summary: Kmail crash, doesn't start anymore Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@schelstraete.org Target Milestone: --- Application: kmail (5.15.40 alpha (20.11.80)) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: KDE neon Unstable Edition -- Information about the crash: Kmail doesn't start anymore, was working before. No wait to start anymore. Running Neon Unstable The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x3e786564) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed() const (this=0x3e786564) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::ref() (this=0x3e786564) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:55 #8 QString::QString(QString const&) (other=..., this=0x7fff74e31f70) at ../../include/QtCore/../../src/corelib/text/qstring.h:1051 #9 v_construct_helper(QVariant::Private*, QString const&, std::integral_constant) (t=..., x=0x7fff74e31f70) at ../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:128 #10 v_construct(QVariant::Private*, QString const&) (t=..., x=0x7fff74e31f70) at ../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/kernel/qvariant_p.h:157 #11 QVariant::QVariant(QString const&) (this=0x7fff74e31f70, val=...) at kernel/qvariant.cpp:2179 #12 0x7f2cd0b7dec1 in QListWidgetItem::QListWidgetItem(QString const&, QListWidget*, int) (this=0x55afb0d531a0, text=..., listview=, type=) at itemviews/qlistwidget.cpp:657 #13 0x7f2ccdf2070b in KPIMTextEdit::EmoticonTextEditItem::EmoticonTextEditItem(QString const&, QListWidget*) (this=0x55afb0d531a0, emoticonText=..., parent=) at ./src/emoticon/emoticonlistwidgetselector.cpp:12 #14 0x7f2ccdf20b6c in KPIMTextEdit::EmoticonListWidgetSelector::setEmoticons(QStringList const&) (this=this@entry=0x55afb0d4ad90, lst=...) at ./src/emoticon/emoticonlistwidgetselector.cpp:62 #15 0x7f2ccdf1eb0f in KPIMTextEdit::EmoticonUnicodeTab::createPlainTextEmoticonTab(QString const&, QVector const&) (emoticons=..., str=..., this=0x55afb0d496c0) at ./src/emoticon/emoticonunicodetab.cpp:76 #16 KPIMTextEdit::EmoticonUnicodeTab::createPlainTextEmoticonTab(QString const&, QVector const&) (this=0x55afb0d496c0, str=..., emoticons=...) at ./src/emoticon/emoticonunicodetab.cpp:66 #17 0x7f2ccdf1ecce in KPIMTextEdit::EmoticonUnicodeTab::loadEmoticons() (this=this@entry=0x55afb0d496c0) at /usr/include/KF5/KI18n/klocalizedstring.h:1349 #18 0x7f2ccdf20326 in KPIMTextEdit::EmoticonUnicodeTab::EmoticonUnicodeTab(QWidget*) (this=0x55afb0d496c0, parent=) at ./src/emoticon/emoticonunicodetab.cpp:18 #19 0x7f2ccdf1e5a5 in KPIMTextEdit::EmoticonTextEditSelector::EmoticonTextEditSelector(QWidget*) (this=0x55afb0d49400, parent=) at ./src/emoticon/emoticontexteditselector.cpp:22 #20 0x7f2ccdf1e0e9 in KPIMTextEdit::EmoticonTextEditAction::EmoticonTextEditActionPrivate::EmoticonTextEditActionPrivate() (this=0x55afb0d48b60) at ./src/emoticon/emoticontexteditaction.cpp:24 #21 KPIMTextEdit::EmoticonTextEditAction::EmoticonTextEditAction(QObject*) (this=0x55afb0d482a0, parent=) at ./src/emoticon/emoticontexteditaction.cpp:42 #22 0x7f2ccdf8ade1 in KPIMTextEdit::RichTextComposerActions::createActions(KActionCollection*) (this=0x55afb0792660, ac=0x55afb093a010) at ./src/composer-ng/richtextcomposeractions.cpp:402 #23 0x7f2ccdf7fb31 in KPIMTextEdit::RichTextComposer::createActions(KActionCollection*) (this=this@entry=0x55afb0730bd0, ac=) at ./src/composer-ng/richtextcomposer.cpp:116 #24 0x7f2cd865d69d in KMComposerWin::setupActions() (this=0x55afb0167180) at ./src/editor/kmcomposerwin.cpp:1366 #25 0x7f2cd866feb6 in KMComposerWin::KMComposerWin(QSharedPointer const&, bool, bool, KMail::Composer::TemplateContext, unsigned int, QString const&, QString const&) (this=0x55afb0167180, aMsg=..., lastSignState=, lastEncryptState=, context=, id=, textSelection=..., customTemplate=..., __in_chrg=, __vtt_parm=) at ./src/editor/kmcomposerwin.cpp:434 #26 0x7f2cd8670a45 in KMComposerWin::create(QSharedPointer const&, bool, bool, KMail::Composer::TemplateContext, unsigned int, QString const&, QString const&) (msg=..., lastSignState=, lastEncryptState=, context=KMail::Composer::NoTe
[kdenlive] [Bug 389859] Changing project profile shortens and cuts clips
https://bugs.kde.org/show_bug.cgi?id=389859 Bart changed: What|Removed |Added CC||bart.vanaudenh...@gmail.com --- Comment #2 from Bart --- I had the same problem in 18.08.1. Opened a project in default setting 1080 25fps, started editing (clip was 720x480 30fps), then decided to make the project profile also 720x480 30fps, continued editing, and then noticed at the end that the editing I did before the profile change was messed up (all cuts were off by say a few seconds). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389859] Changing project profile shortens and cuts clips
https://bugs.kde.org/show_bug.cgi?id=389859 --- Comment #3 from Bart --- The relevant bug for this, that has already been filed, seems to be 368962 (https://bugs.kde.org/show_bug.cgi?id=368962) to me? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 368962] Git master:2016-09-17:Changing project FPS corrupts clip segments on timeline
https://bugs.kde.org/show_bug.cgi?id=368962 Bart changed: What|Removed |Added CC||bart.vanaudenh...@gmail.com --- Comment #11 from Bart --- It would be great to add a warning, while this issue hasn't been fixed, like "changing the frame rate may mess up your existing editing on this project, are you sure you wish to continue?". I just lost a few hours of work because I started a project with a profile at 25fps, edited a big part of it, then switched to a new profile at 30fps, continued editing, only to notice at the end that all editing done before the profile switch was messed up. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355433] Autoscroll down on outgoing message
https://bugs.kde.org/show_bug.cgi?id=355433 Bart changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Bart --- no, it's not resolved. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355433] Autoscroll down on outgoing message
https://bugs.kde.org/show_bug.cgi?id=355433 --- Comment #5 from Bart --- Created attachment 118291 --> https://bugs.kde.org/attachment.cgi?id=118291&action=edit shows that it's not scrolling automatically. See scrollbar on the right side of the screen -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405001] System settings freezes on neon dev unstable when I try to open "Regional Settings"
https://bugs.kde.org/show_bug.cgi?id=405001 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #1 from Bart --- Same over here, on new installation. Operating System: KDE neon Developer Edition KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405207] New: KDE connect daemon always crashes
https://bugs.kde.org/show_bug.cgi?id=405207 Bug ID: 405207 Summary: KDE connect daemon always crashes Product: kdeconnect Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: b...@schelstraete.org Target Milestone: --- Application: kdeconnectd (1.3.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: KDE connect daemon always crashes when starting KDE connect. The application is unusable because of this. - What I was doing when the application crashed: Started KDE Connect The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff6db78800 (LWP 14746))] Thread 4 (Thread 0x7eff6383a700 (LWP 14752)): #0 0x7eff771f5ed3 in timerSourcePrepareHelper (timeout=0x7eff63839bd4, src=) at kernel/qeventdispatcher_glib.cpp:133 #1 timerSourcePrepare (source=, timeout=0x7eff63839bd4) at kernel/qeventdispatcher_glib.cpp:165 #2 0x7eff72781379 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7eff72781d7b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7eff72781f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7eff771f615b in QEventDispatcherGlib::processEvents (this=0x7eff54000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7eff7719764a in QEventLoop::exec (this=this@entry=0x7eff63839da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7eff76fbf41a in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7eff76fc0bc2 in QThreadPrivate::start (arg=0x559abaf68000) at thread/qthread_unix.cpp:361 #9 0x7eff73cfc164 in start_thread (arg=) at pthread_create.c:486 #10 0x7eff76cbfdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7eff6403b700 (LWP 14751)): #0 0x7eff76cb36d9 in __GI___poll (fds=0x7eff5c022890, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7eff72781e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7eff72781f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7eff771f615b in QEventDispatcherGlib::processEvents (this=0x7eff5c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7eff7719764a in QEventLoop::exec (this=this@entry=0x7eff6403ad70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7eff76fbf41a in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7eff75cb2015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7eff76fc0bc2 in QThreadPrivate::start (arg=0x7eff75f29d80) at thread/qthread_unix.cpp:361 #8 0x7eff73cfc164 in start_thread (arg=) at pthread_create.c:486 #9 0x7eff76cbfdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7eff6c8dd700 (LWP 14747)): #0 0x7eff76cb36d9 in __GI___poll (fds=0x7eff6c8dccb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7eff71447917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7eff7144953a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7eff6d06e32a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7eff76fc0bc2 in QThreadPrivate::start (arg=0x559abaf0a7f0) at thread/qthread_unix.cpp:361 #5 0x7eff73cfc164 in start_thread (arg=) at pthread_create.c:486 #6 0x7eff76cbfdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7eff6db78800 (LWP 14746)): [KCrash Handler] #6 QMap::isEmpty (this=) at ../../include/QtCore/../../src/corelib/tools/qmap.h:362 #7 QSslCertificate::subjectInfo (this=0x559abaf65a78, info=info@entry=QSslCertificate::CommonName) at ssl/qsslcertificate_openssl.cpp:154 #8 0x7eff793600e0 in KdeConnectConfig::deviceId (this=this@entry=0x559abaf67e70) at ./core/kdeconnectconfig.cpp:112 #9 0x7eff7936363a in NetworkPacket::createIdentityPacket (np=np@entry=0x7ffde65e6d70) at ./core/networkpacket.cpp:74 #10 0x7eff793405a6 in LanLinkProvider::broadcastToNetwork (this=0x559abaf67e90) at ./core/backends/lan/lanlinkprovider.cpp:138 #11 0x7eff771c8f3f in QtPrivate::QSlotObjectBase::call (a=0x7ffde65e6ef0, r=0x559abaf67e90, this=0x559abaf69310) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #12 QMetaObject::activate (sender=sender@entry=0x559abaf67ee8, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffde65e6ef0) at kernel/qobject.cpp:3759 #13 0x7eff771
[systemsettings] [Bug 405001] System settings freezes on neon dev unstable when I try to open "Regional Settings"
https://bugs.kde.org/show_bug.cgi?id=405001 --- Comment #2 from Bart --- with latest updates , a couple of days ago, this is working again on my end. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 405192] audio playback not working
https://bugs.kde.org/show_bug.cgi?id=405192 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #1 from Bart --- Salvatore, over here this is working fine. Do you have any error? can you start Elisa from a 'konsole' and look at the stdout & stderr messages? Can you also check in 'kmix' (as example) if the sound for Elisa is enabled? (see example attachment) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 405192] audio playback not working
https://bugs.kde.org/show_bug.cgi?id=405192 --- Comment #2 from Bart --- Created attachment 118644 --> https://bugs.kde.org/attachment.cgi?id=118644&action=edit kmix volume -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 405192] audio playback not working
https://bugs.kde.org/show_bug.cgi?id=405192 Bart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Bart --- awaiting info -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373189] Kmail2 v 5.3.3 - identify emails with attachments
https://bugs.kde.org/show_bug.cgi?id=373189 Bart changed: What|Removed |Added CC||b...@schelstraete.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Bart --- Please provide example screenshots. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389073] kmail doesnt start with mailto:
https://bugs.kde.org/show_bug.cgi?id=389073 Bart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||b...@schelstraete.org Status|REPORTED|NEEDSINFO --- Comment #1 from Bart --- Hi(In reply to Benedikt Ortmayr from comment #0) > Application: kmail (5.5.2) > > Qt Version: 5.6.2 > Frameworks Version: 5.32.0 > Operating System: Linux 4.4.92-31-default x86_64 > Distribution: "openSUSE Leap 42.3" > > -- Information about the crash: > when i click a mailadress on internet sites with mailto: Kmail crash > > The crash can be reproduced every time. Can you try the following: - open kmail - then click on an email address (mailto:) does it still crash then? When kmail is open (using 'system tray' option as workaround), this is working for me. When kmail is closed, it also fails for me. But the workaround is working for me -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400184] KMail refuses to send email
https://bugs.kde.org/show_bug.cgi?id=400184 Bart changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||b...@schelstraete.org Resolution|--- |WAITINGFORINFO --- Comment #2 from Bart --- (In reply to Tom Kijas from comment #1) > Díky za spolupráci na vyřešení problému. Stejný problém se vyskytuje i u > Exchange, chyba je tedy v KMailu. Please write in English, thank you. Can you please: - send the configuration you are using. - open kmail from console and send the output of the console after sending the email. - open (or install first) akonadi console, go to "logging" and enable it. Once enabled, send a new mail. Once mail was sent (or not sent), stop the logging and selected save to file, and attach it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405207] KDE connect daemon always crashes
https://bugs.kde.org/show_bug.cgi?id=405207 Bart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Bart --- Hi, After checking the certificates mentioned in that folder, I could see that the pem files were empty: -rw--- 1 0 Mar 4 16:45 ../kdeconnect/privateKey.pem -rw--- 1 0 Mar 4 16:45 ../kdeconnect/certificate.pem removing the directory and restarting kde connect indeed resolved the problem. thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416639] New: Slideshow remote Pointer shows incorrectly on dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=416639 Bug ID: 416639 Summary: Slideshow remote Pointer shows incorrectly on dual monitor setup Product: kdeconnect Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: mormeg...@gmail.com Target Milestone: --- SUMMARY The Slideshow remote Pointer shows only on laptop screen, regardless the "main monitor" setting. This is especially annoying when presenting - usually the presentation is being displayed on secondary monitor, leaving main monitor for speaker's notes. It could be better for pointer to show by default on secondary monitor, or to have an option to choose the monitor. STEPS TO REPRODUCE 1. open KDE Connect mobile application 2. open Slideshow remote 3. press POINTER button OBSERVED RESULT Pointer is displayed on main PC screen. Change of "primary monitor" in display settings does not change this behaviour. EXPECTED RESULT Pointer is displayed on secondary screen, or - the screen is selected prior to the use of pointer. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE Plasma 18.1.5 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412067] I get a error message: "Error while opening the database".
https://bugs.kde.org/show_bug.cgi?id=412067 Bart changed: What|Removed |Added CC||bart@smedema.net --- Comment #3 from Bart --- Have the same issue after the following situation. 1) Changed network topology, so my database is not reachable anymore on the existing location. (MySQL) 2) Digikam detects this. When proceding without database hangs. I'll attach the logs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412067] I get a error message: "Error while opening the database".
https://bugs.kde.org/show_bug.cgi?id=412067 --- Comment #4 from Bart --- Created attachment 124243 --> https://bugs.kde.org/attachment.cgi?id=124243&action=edit Debugview log When digikam stops, in the top it displays: Checking ICC repository -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412067] I get a error message: "Error while opening the database".
https://bugs.kde.org/show_bug.cgi?id=412067 --- Comment #7 from Bart --- (In reply to Maik Qualmann from comment #5) > You could edit the "digikamrc" manually and enter the correct hostname > again. We may need to enable the MySQL configuration dialog at the start if > the connection fails. > > Maik Thanks, that worked. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 Bart changed: What|Removed |Added Resolution|FIXED |--- CC||bartosz.bu...@gmail.com Status|RESOLVED|REOPENED --- Comment #12 from Bart --- Stil exists in 5.9.3 in KDE Neon (Ubuntu 18.04) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #15 from Bart --- Same problem over here. Makes kmail2 almost unusable. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361725] Yakuake task appears in the task manager some times, when opening Yakuake with hotkey
https://bugs.kde.org/show_bug.cgi?id=361725 Bart changed: What|Removed |Added CC||bart.po...@gmail.com --- Comment #5 from Bart --- Same here, up to date Arch Linux QT 5.10 KDE 5.41 Yakuake 3.0.4 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again
https://bugs.kde.org/show_bug.cgi?id=402780 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #3 from Bart --- Same problem over here, KDE Plasma Version: 5.14.90 KDE Frameworks Version: 5.54.0 Qt Version: 5.12.0 it's still working on older version: -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 355433] Autoscroll down on outgoing message
https://bugs.kde.org/show_bug.cgi?id=355433 Bart changed: What|Removed |Added CC||b...@schelstraete.org --- Comment #2 from Bart --- this bug makes the chat application actually unusable. surprised that it's only open sinds 2015. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #14 from Bart --- Created attachment 116686 --> https://bugs.kde.org/attachment.cgi?id=116686&action=edit Kmail screenshot As you can see in attachment, still not working correctly, even with one entry in contacts. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 --- Comment #18 from Bart --- (In reply to Aurélien Murith from comment #15) > In fact, it works as long as you read your message in the main window, but > if you open it in a separate window by double-clicking on it, the bug is > still present. In my machine even in main window not working correctly :/ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)
https://bugs.kde.org/show_bug.cgi?id=352214 Bart changed: What|Removed |Added CC||kdeb...@thisnet.nl --- Comment #5 from Bart --- I also got hit by this issue, I imported an invitation but it did not show in the month view. Spend some time investigating why, can there be at least a placeholder in stead of hiding the event? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 312919] high CPU usage for copying notification
https://bugs.kde.org/show_bug.cgi?id=312919 Bart changed: What|Removed |Added CC||bart.po...@gmail.com --- Comment #10 from Bart --- As someone pointed out, this persists in Plasma 5.8. In 2017. Copying a file, generating a GPG key or connecting to a wifi network destroys battery life. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353974] Provide an option to turn off animations
https://bugs.kde.org/show_bug.cgi?id=353974 Bart changed: What|Removed |Added CC||bart.po...@gmail.com --- Comment #4 from Bart --- +1 for this, since the CPU still goes to 100% when spinners are shown (https://bugs.kde.org/show_bug.cgi?id=312919) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 31987] bookmark toolbar folder dropdown
https://bugs.kde.org/show_bug.cgi?id=31987 --- Comment #4 from Bart --- Ba -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 31987] bookmark toolbar folder dropdown
https://bugs.kde.org/show_bug.cgi?id=31987 --- Comment #5 from Bart --- Bart , plse ignore my comment ! moved to the correct falkon space if this is monitored , please remove both comments by me -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 480527] Cannot edit bookmarks in folders via context menu
https://bugs.kde.org/show_bug.cgi?id=480527 Bart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||bart.ko...@gmx.com Status|CONFIRMED |NEEDSINFO --- Comment #3 from Bart --- I bart, (running Mint LMDE6 and the non-Flatpack install of Falkon) do experience lack of flexibility in instering and moving entries in the folders. Can't drag from addressbar into empty entries or move entries to othe folders . also do not get any edit options on either right- or leftclick on folders, subfolders or items -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 480527] Cannot edit bookmarks in folders via context menu
https://bugs.kde.org/show_bug.cgi?id=480527 Bart changed: What|Removed |Added Platform|Arch Linux |Mint (Debian based) Alias||solos -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 31987] bookmark toolbar folder dropdown
https://bugs.kde.org/show_bug.cgi?id=31987 Bart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||bart.ko...@gmx.com --- Comment #3 from Bart --- I bart, running Mint LMDE6 and the non-Flatpack install of Falkon do experience lack of flexibility in instering and moving entries in the folders. Can't drag from addressbar into empty entries or move entries to othe folders . -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 439631] Akonadi crashes often and sometimes it doesn't start up at all
https://bugs.kde.org/show_bug.cgi?id=439631 --- Comment #1 from Bart Ribbers --- I tracked this down to specifically akonadi_imap_resources crashing, makes sense as it often (but not always) happens when I receive a new email. Sadly imap crashing takes the whole of Akonadi with it... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454961] New: "Failed to create gbm_bo for lease output" causing black screen, unable to even switch to a TTY
https://bugs.kde.org/show_bug.cgi?id=454961 Bug ID: 454961 Summary: "Failed to create gbm_bo for lease output" causing black screen, unable to even switch to a TTY Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY While testing the Plasma 5.24.90 beta I'm unable to launch into a Wayland session. The log is spammed full with found DRM devices but every time it reports it "Failed to create gbm_bo for lease output. Checking test buffer failed for (0)". STEPS TO REPRODUCE 1. Launch into a Plasma 5.24.90 Wayland session OBSERVED RESULT Black screens, unable to even switch to a TTY EXPECTED RESULT The Wayland session to launch, and the ability to switch to a TTY to remain. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge, personally built 5.24.90 packages (available in About System) KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 with KDE patches ADDITIONAL INFORMATION This system runs with Musl libc rather than glibc, not sure if relevant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454961] "Failed to create gbm_bo for lease output" causing black screen, unable to even switch to a TTY
https://bugs.kde.org/show_bug.cgi?id=454961 --- Comment #1 from Bart Ribbers --- Created attachment 149524 --> https://bugs.kde.org/attachment.cgi?id=149524&action=edit SDDM log of the Wayland session -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 406868] baloo_file_extractor fails MTimeDB::del with MDB_BAD_TXN, constant high CPU use
https://bugs.kde.org/show_bug.cgi?id=406868 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #7 from Bart Ribbers --- I can sadly reproduce this with Baloo 5.94.0. The SDDM Wayland log is getting filled up to gigabytes at a time if I let Baloo run and the CPU usage of the process is 100% constantly. The following in the log just repeats itself every half a second or so: kf.baloo.engine: MTimeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdTreeDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: IdFilenameDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: DocumentDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: DocumentDB::put MDB_BAD_TXN: Transaction must abort, has a child, or is invalid kf.baloo.engine: DocumentTimeDB::put 3979527717912610 MDB_BAD_TXN: Transaction must abort, has a child, or is invalid First time I noticed this was when I was checking for something else at which point the log file was 1.5GB big. Removing just these messages from it got it back down to a few KB, so just Baloo was responsible for the huge file size. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465523] Discrete Keyframe Interpolation for Rotoscope Effect Not Working
https://bugs.kde.org/show_bug.cgi?id=465523 Bart Vaes changed: What|Removed |Added CC||vaesb...@telenet.be --- Comment #2 from Bart Vaes --- Just a quick comment, as I was facing a similar issue... I'm using the Flatpak version of kdenlive - v22.12.2 I was experimenting with the Rotoscoping (mask) effect and keyframes. I selected "Smooth" as "Default keyframe type" under the keyframe timeline. Manually adding keyframes used the correct interpolation. However, after saving the project and re-opening; ALL keyframes were changed to linear. This happens every time I tried so far. It seems this keyframe property is not being saved ? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470674] New: Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 Bug ID: 470674 Summary: Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view Classification: Plasma Product: KScreen Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY My system has 3 displays attached. 2 identical screens and a third TV, spread out over DisplayPort and HDMI. UP til somewhere in 5.27 I've been able to configure these all via the KCM, re-order and place them using the "Drag screens to re-arrange them" view. However since recently the TV doesn't appear on that screen anymore. It's still under the "Device" dropdown and I can configure everything for it except for the placement compared to the other screens. For that I now have to use kscreen-doctor instead (which still works fine). STEPS TO REPRODUCE Not entirely sure how to reproduce, as it hasn't happened on any other system with multiple screens. OBSERVED RESULT Unable to re-arrange location of the TV. EXPECTED RESULT Able to re-arrange location of the TV. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 with KDE patches ADDITIONAL INFORMATION This has worked fine at least til 5.26 and I think it broke with the 5.27 upgrade but I'm unsure about it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 Bart Ribbers changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #2 from Bart Ribbers --- I don't think it's the same, it's not just overlapping. You can drag the screens it _does_ show anywhere and the third screen will _never_ appear. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #4 from Bart Ribbers --- Literally nothing. It doesn't indicate any screen, both other screens just get unselected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #7 from Bart Ribbers --- Created attachment 159508 --> https://bugs.kde.org/attachment.cgi?id=159508&action=edit Screenshot of the Display Configuration KCM Attached the screenshot. As you can see the device selected in the dropdown isn't present in the "Drag screens" view. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 Bart Ribbers changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 from Bart Ribbers --- Actually I just realized the right screen is marked as duplicated, so I guess that's where that screen is? That isn't in anyway clear though if you just select the screen from the dropdown. Also I'm unsure how to get it detached from that other screen. Screen priorities seems to do nothing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #10 from Bart Ribbers --- No that part is correct, it's mirroring that screen. It's not what I want though, I actually want it to mirror my left screen and right now I have to run a kscreen-doctor command every time I turn that screen on. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 470763] Crash copying files in Dolphin due to stack overflow.
https://bugs.kde.org/show_bug.cgi?id=470763 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #1 from Bart Ribbers --- Just to include a bit more detail in this bug report rather than having to go outside this bugtracker: This seems to be due to a small stack size. When the stack size of Dolphin is increased to 1M (using LDFLAGS="$LDFLAGS -Wl,-z,stack-size=0x10") it never happens. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #12 from Bart Ribbers --- Yes that is accurate. The changes don't persist when I turn off and on that third screen. For some reason even though the screen is still detected when it's off, it's rearranges my screen setup and when I turn it back on it's back to mirroring the wrong one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470674] Screen that appears in kscreen-doctor doesn't appear in the KCM draggable view
https://bugs.kde.org/show_bug.cgi?id=470674 --- Comment #14 from Bart Ribbers --- I'm still not sure it's the exact same as that report. Like I said it's not hidden, it's just not there. I can drag the "overlapping" screen all I want, the other screen _will_ _not_ _appear_. And the screen gives me no way to "detach" the screen either. In that other bug report it seems you can just drag the screens off each other and everything will appear correctly. I will file a report separately for the changes not persisting though, that indeed is separate. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470863] New: Screen rearrangments applied through kscreen-doctor are not persistent across screen turning off and on
https://bugs.kde.org/show_bug.cgi?id=470863 Bug ID: 470863 Summary: Screen rearrangments applied through kscreen-doctor are not persistent across screen turning off and on Classification: Plasma Product: KScreen Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY Split out from https://bugs.kde.org/show_bug.cgi?id=470674, see that bug for some more info. Basically I'm using kscreen-doctor to apply my screen layout, 3 screens: 2 desktop monitors which are exact same model next to each other, and a separate TV as a third screen. In my ideal setup I have the TV (third screen) mirrored to the left screen of the two desktop monitors. However Plasma keeps making it mirror the right desktop monitor instead every time I turn off and on the TV. Thus I have to keep on calling kscreen-doctor every time I turn on the TV. STEPS TO REPRODUCE Not sure, it's seems setup specific. But I suppose: 1. have 3 screens of which 1 should mirror one of the other two 2. turn off the third screen 3. turn it back on OBSERVED RESULT The third screen mirrors the wrong screen every time it's turned off and on. EXPECTED RESULT The screen mirroring to be remembered correctly across screen reboots. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 with KDE patches -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368438] KDE Connect does not communicate while running in background on phone
https://bugs.kde.org/show_bug.cgi?id=368438 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #30 from Bart Ribbers --- Is this still an issue? KDE Connect nowadays has a persistent notification to make sure it keeps running even if in the background, and up to at least Android 11 (I haven't had the opportunity to test any newer Android version) it has always managed to stay connected even while in the background. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478153] New: Images don't load using the piped backend
https://bugs.kde.org/show_bug.cgi?id=478153 Bug ID: 478153 Summary: Images don't load using the piped backend Classification: Applications Product: PlasmaTube Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- It doesn't change when switching between instances either. stdout is full of warnings: qrc:/qt/qml/org/kde/plasmatube/ui/components/VideoGridItem.qml:86:9: QML QQuickImage: Error decoding: https://pipedproxy.kavin.rocks/vi/NcJF-R1DGQ8/hqdefault.jpg?host=i.ytimg.com&qhash=5af0f5be&rs=AOn4CLCTBgkOkpx5A2Kwz9jSyYhVyIj6vw&sqp=-oaymwEcCNACELwBSFXyq4qpAw4IARUAAIhCGAFwAcABBg%3D%3D: Unsupported image format -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478153] Images don't load using the piped backend
https://bugs.kde.org/show_bug.cgi?id=478153 Bart Ribbers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Bart Ribbers --- Sorry this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=476006, my own bug report lol. I knew I made the bug report at some point but couldn't find it any more so I wasn't sure if it still existed. Seems it does! *** This bug has been marked as a duplicate of bug 476006 *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 --- Comment #4 from Bart Ribbers --- *** Bug 478153 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Bart Ribbers --- The problem occurs on other instances too. For example https://pipedproxy.kavin.rocks/vi/NcJF-R1DGQ8/hqdefault.jpg?host=i.ytimg.com&qhash=5af0f5be&rs=AOn4CLCTBgkOkpx5A2Kwz9jSyYhVyIj6vw&sqp=-oaymwEcCNACELwBSFXyq4qpAw4IARUAAIhCGAFwAcABBg%3D%3D: fails to load as well. How do I check what image format it thinks it is? It isn't printed to stdout. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 476006] Thumbnails fail to load with the Piped backend
https://bugs.kde.org/show_bug.cgi?id=476006 Bart Ribbers changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #6 from Bart Ribbers --- I talked with Joshua over Matrix and we found the problem. The system didn't have Qt6ImageFormats installed (only the Qt5 variant) and that's required for WebP images, which piped uses. After installing it the problem was resolved. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 478405] New: Subscriber count on an open video is hard to read due to not using separation dots/commas
https://bugs.kde.org/show_bug.cgi?id=478405 Bug ID: 478405 Summary: Subscriber count on an open video is hard to read due to not using separation dots/commas Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Created attachment 164095 --> https://bugs.kde.org/attachment.cgi?id=164095&action=edit Screenshot showing subscriber count on a random video See attached image. It would be better if it was formatted "12.200.000" (Dutch locale) or "12,200,000" (non-Dutch locale, I suppose). Or even better, shorten the number like the views and likes counter just beneath it. "12M". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] New: Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bug ID: 482362 Summary: Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified Classification: Plasma Product: kwin Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- SUMMARY I've just upgraded my VM on a Macbook M3 to run Plasma 6 and now the mouse cursor is invisible. Unless I set KWIN_FORCE_SW_CURSOR=1 (which makes it show up) it's impossible to use the mouse for anything. This wasn't a problem with Plasma 5.x.y, zo this is a regression. STEPS TO REPRODUCE 1. Install Plasma 6 in a Qemu VM OBSERVED RESULT No mouse cursor is shown EXPECTED RESULT Mouse cursor to be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux Edge KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This system runs in a Qemu VM (using the UTM application) on macOS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 --- Comment #2 from Bart Ribbers --- Created attachment 166381 --> https://bugs.kde.org/attachment.cgi?id=166381&action=edit wayland-session log from SDDM I'm not sure where to get KWin logs from, so I'll just upload the entire Wayland session log from SDDM, I hope that's enough. This is with the env variable applied, do you need it without it as well? -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 483250] New: Indicate if there are any unread messages in rooms that belong to one or more spaces
https://bugs.kde.org/show_bug.cgi?id=483250 Bug ID: 483250 Summary: Indicate if there are any unread messages in rooms that belong to one or more spaces Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- I use my spaces to organize the rooms but when I have 1 space active I do not know if there are any new messages in rooms in other spaces. It would be great if a space could be marked as read or unread so I know a non-active space has rooms with messages to read. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] When not using Systemd or Plasma's Systemd session launch integration, changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 Bart Ribbers changed: What|Removed |Added CC||bribb...@disroot.org --- Comment #49 from Bart Ribbers --- I can currently reproduce this on Alpine Linux using Plasma 6.0.5 with KDE Frameworks 6.2.0, but only on one of 3 machines (a new laptop). My desktop and previous laptop have been upgraded from Plasma 5 before and do not experience this issue, but my new laptop that has only ever had Plasma 6 resets on every login. No systemd, just OpenRC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] New: Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 Bug ID: 487979 Summary: Enabling HDR causes entire display to have a green tint Classification: Plasma Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: colour-management Assignee: kwin-bugs-n...@kde.org Reporter: bribb...@disroot.org Target Milestone: --- Created attachment 170103 --> https://bugs.kde.org/attachment.cgi?id=170103&action=edit Picture of a HDR-enabled TV showing a green tint SUMMARY My TV has HDR support so I enabled it in plasma settings, however doing that causes the complete display to show a green tint over everything. STEPS TO REPRODUCE 1. Enable HDR OBSERVED RESULT The display is tinted entirely green EXPECTED RESULT The display to show as normal until HDR content is being shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 Bart Ribbers changed: What|Removed |Added Version|5.24.90 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 --- Comment #1 from Bart Ribbers --- Ah forgot to enable but obviously relevant, the GPU is an AMD GPU, RX580, using Mesa 24.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487979] Enabling HDR causes entire display to have a green tint
https://bugs.kde.org/show_bug.cgi?id=487979 --- Comment #3 from Bart Ribbers --- 6.6.32, latest LTS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Bart Ribbers --- Nope, still an issue on 6.0.5 sadly. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 486463] New: Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back
https://bugs.kde.org/show_bug.cgi?id=486463 Bug ID: 486463 Summary: Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back Classification: Applications Product: angelfish Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: bribb...@disroot.org Target Milestone: --- When you hold any link a context menu will popup with an option to open the link in a new tab. Clicking that option then immediately moves you to that just opened tab. This was very unexpected for me, no other browser I ever used does this, and I'd like it to stay in the current active tab until I tell Angelfish to switch. So when I want to switch back immediately this is made harder by the fact that a little snackbar message pops up saying the tab was opened (this whole message seems unnecessary to me, especially when you're already switched to the tab) blocking the clicking on the address bar or even the tab switcher. I'd like to have it first of all not switch me automatically to the new tab and secondly not show the snackbar message as it's unnecessary and relaying information you already have as a user. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486521] New: Clicking on an entry on the account switcher on Plasma Mobile will switch pages on the background but not remove the account switcher popup
https://bugs.kde.org/show_bug.cgi?id=486521 Bug ID: 486521 Summary: Clicking on an entry on the account switcher on Plasma Mobile will switch pages on the background but not remove the account switcher popup Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- You still have to click away the account switcher to actually fully see and use the page it switched too in the background. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486545] New: Opening a room on Plasma Mobile will also activate the room actions menu
https://bugs.kde.org/show_bug.cgi?id=486545 Bug ID: 486545 Summary: Opening a room on Plasma Mobile will also activate the room actions menu Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- The actions menu containing actions like "mark room as read" or "leave the room". So to do anything in the room that was just opened you first have to click that room away which is annoying. In fact I accidentally left a room because of it because I immediately tried to click on the message bar to start typing a message but because of the action menu being there I left the room instead. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 486546] New: Confirmation should be asked before leaving a room
https://bugs.kde.org/show_bug.cgi?id=486546 Bug ID: 486546 Summary: Confirmation should be asked before leaving a room Classification: Applications Product: NeoChat Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: bribb...@disroot.org CC: c...@carlschwan.eu Target Milestone: --- Because of https://bugs.kde.org/show_bug.cgi?id=486545 I accidentally left a room. Besides that the menu shouldn't have been open in the first place, NeoChat should really have asked for confirmation because the action is quite destructive. This was a private room which I could not just rejoin without an invite so now I had to bother others to ask them to invite me again. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 486463] Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back
https://bugs.kde.org/show_bug.cgi?id=486463 Bart Ribbers changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from Bart Ribbers --- Oh you're right, there is. Well then I'd say that settings needs to by off by default, because it's the opposite of every other browser really. And the issue remains that it shows a popup telling you that the tab was opened, even though you just switched to it and already know. And it's blocking the bottom bar, it should really be placed above it if it's going to be shown at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482362] Mouse cursor is invisible in Qemu unless KWIN_FORCE_SW_CURSOR=1 is specified
https://bugs.kde.org/show_bug.cgi?id=482362 Bart Ribbers changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #5 from Bart Ribbers --- Uh, I did provide info... -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 485080] New: Pasting a fediverse link into the search box on the left side panel doesn't load the post
https://bugs.kde.org/show_bug.cgi?id=485080 Bug ID: 485080 Summary: Pasting a fediverse link into the search box on the left side panel doesn't load the post Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY I'd like to be able to copy any fediverse URL to a post and paste it in the search field in Tokodon to make it load that post through my instance. This is something the default Mastodon web interface supports and from what I hear also something Tokodon is supposed to support but it seems to be broken at the moment. STEPS TO REPRODUCE 1. Copy the URL to any fediverse post, for example https://ma.fellr.net/@fell/112217662940193667 2. Paste it in the search field in Tokodon 3. Press enter to make it "search" OBSERVED RESULT It reports "No search results" EXPECTED RESULT The post to be loaded into the main view after my server has retrieved it SOFTWARE/OS VERSIONS Linux: Alpine Linux edge KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 485081] New: Clicking on the timeline next to a post on empty space opens the post next to the click
https://bugs.kde.org/show_bug.cgi?id=485081 Bug ID: 485081 Summary: Clicking on the timeline next to a post on empty space opens the post next to the click Classification: Applications Product: Tokodon Version: 24.02.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bribb...@disroot.org CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- SUMMARY When clicking the empty space between a post and the border of the window (or side panel on the left side) when on the timeline view opens the post next to where is clicked. This is unexpected and really threw me off a few times when I just tried to focus the window by clicking on the empty space. STEPS TO REPRODUCE 1. Open the timeline view 2. Click next to a post, on the empty space of the page OBSERVED RESULT The post next to the click is opened EXPECTED RESULT Nothing to happen, the user didn't click on a post to open. SOFTWARE/OS VERSIONS Linux: Alpine Linux edge KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] New: Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 Bug ID: 480421 Summary: Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: bribb...@disroot.org CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 165298 --> https://bugs.kde.org/attachment.cgi?id=165298&action=edit 1-2 pixels wide icons SUMMARY As the title says, the icons-only task manager often messes up the rendering resulting in weird glitches. This is often "fixed" by launching or closing an application but that's not always the case, and after being correct for a while it also likes to mess up again. I'm not sure what invokes it but it definitely always appears just after booting. I'd add more screenshots in this initial post demonstrating the problem but Bugzilla only seems to allow just 1 attachment per post, so I'll post the others in subsequent comments on this bug report. STEPS TO REPRODUCE 1. Put the icons-only task manager on a panel 2. Reboot OBSERVED RESULT Rendering is messed up, resulting in either 1-2 pixels wide icons or icons about 3 times as small as they should be. Launching an application changes it back to regular sized icons. EXPECTED RESULT Icons to always be rendered at the correct size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Alpine Linux edge KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #1 from Bart Ribbers --- Created attachment 165299 --> https://bugs.kde.org/attachment.cgi?id=165299&action=edit Still too small icons, but rather than 1-2 pixels wide now about 4 times as small as intended -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #2 from Bart Ribbers --- Created attachment 165300 --> https://bugs.kde.org/attachment.cgi?id=165300&action=edit The icons as they should be -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 --- Comment #5 from Bart Ribbers --- Sorry, not really so far. As you can see on the screenshot my panel is horizontally. It's on a left screen as well, the second screen to the right in my setup has no panel. It always happens on boot, but I can't figure out what other situations make it happen. This has started since the Plasma 6 first beta release, it's not an issue on Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486706] New: Button to open the left sidebar appears over UI elements on the settings tab blocking the pressing of various UI elements
https://bugs.kde.org/show_bug.cgi?id=486706 Bug ID: 486706 Summary: Button to open the left sidebar appears over UI elements on the settings tab blocking the pressing of various UI elements Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- Created attachment 169260 --> https://bugs.kde.org/attachment.cgi?id=169260&action=edit Screenshot of the settings page See the screenshot. The button appears over the search bar making me unable to click on the left corner of the input field to focus it. It's not much of a problem there, it's wide enough to just click to the right of it, but it's blocking the "go back" button on any deeper page. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 486707] New: Playing videos on a Pixel 3A fails, failure to open VDPAU backend
https://bugs.kde.org/show_bug.cgi?id=486707 Bug ID: 486707 Summary: Playing videos on a Pixel 3A fails, failure to open VDPAU backend Classification: Applications Product: PlasmaTube Version: 24.01.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: l...@kaidan.im Reporter: bribb...@disroot.org CC: espi...@gmail.com Target Milestone: --- I'm using Plasmatube on a Pixel 3A running postmarketOS with Plasma Mobile on a 6.8 kernel. It is however currently unable to play any video. A separate window opens up showing the first frame of a video but it's frozen (no playback controls). In the console the following is logged: Failed to open VDPAU backend Error loading shared library libvdpau_nvidia.so: No such file or directory [ffmpeg] AVHWDeviceContext: VDPAU device creation on X11 display :0 failed. Failed to open VDPAU backend Error loading shared library libvdpau_nvidia.so: No such file or directory [ffmpeg] AVHWDeviceContext: VDPAU device creation on X11 display :0 failed. This device uses an Adreno GPU with Mesa's Freedreno, so I'm unsure why it's trying to get a NVIDIA library in the first place. -- You are receiving this mail because: You are watching all bug changes.
