[plasmashell] [Bug 369612] Default SDDM avatars do not work with the theme
https://bugs.kde.org/show_bug.cgi?id=369612 Fabian Vogt changed: What|Removed |Added Attachment #101370|0 |1 is obsolete|| --- Comment #2 from Fabian Vogt --- Created attachment 101478 --> https://bugs.kde.org/attachment.cgi?id=101478&action=edit Workaround in the sddm theme The previous patch version was buggy, it also ignored the ".face.icon" files that users can put into their home directories. To only ignore the global sddm supplied onces, this now compares against a hardcoded sddm face path. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370266] New: Broken accelerator for the shortcut input
https://bugs.kde.org/show_bug.cgi?id=370266 Bug ID: 370266 Summary: Broken accelerator for the shortcut input Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs URL: https://i.imgur.com/lRDPhib.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de CC: bhus...@gmail.com, mgraess...@kde.org As can be seen in the picture, there is no accelerator in the "Lock screen" label to the "Ctrl+Alt+L" input. Instead, the accelerator is in the box itself, making it pretty unreliable and thus hardly usable. Additionally, the accelerator of the first item "Lock screen automatically" changed from L to s in Plasma 5.8. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #15 from Fabian Vogt --- Created attachment 99772 --> https://bugs.kde.org/attachment.cgi?id=99772&action=edit Patch to add a oauth2 library to libkipiplugins This patch adds the code from https://github.com/pipacs/o2 with some changes (https://github.com/pipacs/o2/pull/57) to fix building. Several workarounds were needed to integrate it, but it's not too bad. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #17 from Fabian Vogt --- > What about to use OAuth2 API in imgur tool ? I'll port my rewrite of the imgur plugin to make use of that library soon. I'll have to implement some missing features as well, so it may take a few days. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 Fabian Vogt changed: What|Removed |Added Attachment #99772|0 |1 is obsolete|| --- Comment #19 from Fabian Vogt --- Created attachment 99897 --> https://bugs.kde.org/attachment.cgi?id=99897&action=edit Add o2 library from https://github.com/pipacs/o2 -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #20 from Fabian Vogt --- Created attachment 99898 --> https://bugs.kde.org/attachment.cgi?id=99898&action=edit Fix o2 to be compatible with imgur -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #21 from Fabian Vogt --- Created attachment 99900 --> https://bugs.kde.org/attachment.cgi?id=99900&action=edit Rewrite imgur plugin to work with OAuth2 Rewrite done, tested multiple times and it seems to work fine. It took a bit longer due to some weirdnesses in the imgur OAuth implementation that didn't work well with o2. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #24 from Fabian Vogt --- (In reply to Maik Qualmann from comment #23) > I use Chromium as default browser. After logging in, there is an error box > that you are not authorized. But the upload is done. With Firefox, there is > no error message. > > Maik I had the same issue once, too, but I was unable to reproduce it again after some changes. I don't understand how it happens at all, as the same QNetworkReply apparently emits both success and failure :-/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365242] New: KWin crashes with VM with cirrus
https://bugs.kde.org/show_bug.cgi?id=365242
Bug ID: 365242
Summary: KWin crashes with VM with cirrus
Product: kwin
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: backend-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: fab...@ritter-vogt.de
While the DRM backend works fine with virtio now, kwin_wayland crashes straight
away when using the DRM backend with the cirrus card.
m_image of m_blackBuffer is zero because drmModeAddFB fails, like in bug
364740.
While the cirrus DRM driver itself is in a bad shape (many recommend to disable
it in the kernel config), it's the current default in virt-manager
and the model that openQA uses...
#0 0x7fffee74e71a in QImage::fill(QColor const&) () from
/usr/lib64/libQt5Gui.so.5
#1 0x7fffee74e9ec in QImage::fill(Qt::GlobalColor) () from
/usr/lib64/libQt5Gui.so.5
#2 0x7fffde79f0ec in KWin::DrmOutput::blank (this=this@entry=0x6924a0)
at
/usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/plugins/platforms/drm/drm_output.cpp:326
#3 0x7fffde7a09d6 in KWin::DrmOutput::init (this=0x6924a0,
connector=connector@entry=0x6813c0)
at
/usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/plugins/platforms/drm/drm_output.cpp:189
#4 0x7fffde79d110 in KWin::DrmBackend::queryResources
(this=this@entry=0x6557e0)
at
/usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/plugins/platforms/drm/drm_backend.cpp:318
#5 0x7fffde79d4e5 in KWin::DrmBackend::openDrm (this=0x6557e0)
at
/usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/plugins/platforms/drm/drm_backend.cpp:239
#6 0x75e7544e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
(gdb) frame 2
#2 0x7fffde79f0ec in KWin::DrmOutput::blank (this=this@entry=0x6924a0)
at
/usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/plugins/platforms/drm/drm_output.cpp:326
326 m_blackBuffer->image()->fill(Qt::black);
(gdb) print *m_blackBuffer
$2 = {m_backend = 0x6557e0, m_surface = 0x0, m_bo = 0x0, m_size = {wd = 1024,
ht = 768}, m_handle = 1, m_bufferId = 0,
m_stride = 4096, m_bufferSize = 3145728, m_memory = 0x0, m_image = 0x0}
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 365242] KWin crashes in VM with cirrus
https://bugs.kde.org/show_bug.cgi?id=365242 Fabian Vogt changed: What|Removed |Added Summary|KWin crashes with VM with |KWin crashes in VM with |cirrus |cirrus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365243] New: Red and blue channels swapped with fbdev backend on cirrus
https://bugs.kde.org/show_bug.cgi?id=365243 Bug ID: 365243 Summary: Red and blue channels swapped with fbdev backend on cirrus Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend-fbdev Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de When starting KWIN_COMPOSE=Q kwin_wayland --framebuffer [...] in a VM with the cirrus backend, the red and blue channels appear swapped, so RGB <-> BGR. I couldn't test whether the bug is in the QPainter or the framebuffer backend as the DRM backend is currently broken with cirrus (bug 365242). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #25 from Fabian Vogt --- I just can't reproduce the issue, however I try it. If someone can, please provide the log and, if possible, a wireshark packet trace (which might contain sensitive information as the communication with 127.0.0.1 is not encrypted). -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 360404] Imgur autorization not work : Integrate Oauth2 library in libkipiplugins [patch]
https://bugs.kde.org/show_bug.cgi?id=360404 --- Comment #27 from Fabian Vogt --- (In reply to caulier.gilles from comment #26) > Fabian, > > If Oauth2 integartion work fine with Imgur tool, we will integrate your > patches into git/master for next 5.1.0 planned in August. The o2 integration into libkipiplugins works fine and even if I can't figure out what causes the bogus error, it's still much better than the current state, which does only allow anonymous uploads. > What about other web service tools, as google, facebook, flickr, etc ? Can > you evaluate : > > - which tool can use Oauth2 API. > - The complexity to patch current implementation of relevant tools. Generally I prefer the "if it's not broken, don't fix it" approach. The facebook plugin works fine, it just needs to be updated to use the 2.6 API instead of 2.4 (a simple sed should do). I don't know about the other plugins, I haven't tested them yet. Which of them are known to be broken? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365243] Red and blue channels swapped with fbdev backend on cirrus
https://bugs.kde.org/show_bug.cgi?id=365243 --- Comment #2 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #1) > Could you please enable debug output for the category: > kwin_wayland_framebuffer > > The format of the framebuffer device and the mapping to a QImage format is > logged out so we should see what KWin does. My best guess is that this is a > format we don't support yet. kwin_wayland_framebuffer: Bits Per Pixel: 24 kwin_wayland_framebuffer: Buffer Length: 33554432 kwin_wayland_framebuffer: Bytes Per Line: 3072 kwin_wayland_framebuffer: Alpha Length: 0 kwin_wayland_framebuffer: Red Length: 8 kwin_wayland_framebuffer: Green Length: 8 kwin_wayland_framebuffer: Blue Length: 8 kwin_wayland_framebuffer: Blue Offset: 0 kwin_wayland_framebuffer: Green Offset: 8 kwin_wayland_framebuffer: Red Offset: 16 kwin_wayland_framebuffer: Alpha Offset: 0 kwin_wayland_framebuffer: Framebuffer Format is RGB888 IIRC, RGB888 has its red at an offset of 0, so RGB888 is wrong here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365242] KWin crashes in VM with cirrus
https://bugs.kde.org/show_bug.cgi?id=365242 --- Comment #4 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #3) > Possible patch for the crash: https://phabricator.kde.org/D2135 - untested > as I don't have a VM setup for it (need to fix that). Looks like it's working: FATAL ERROR: backend failed to initialize, exiting now However, it crashes with a segfault after that, in a global destructor: Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. 0x75e815a3 in QSocketNotifier::setEnabled(bool) () from /usr/lib64/libQt5Core.so.5 (gdb) bt #0 0x75e815a3 in QSocketNotifier::setEnabled(bool) () from /usr/lib64/libQt5Core.so.5 #1 0x75e81629 in QSocketNotifier::~QSocketNotifier() () from /usr/lib64/libQt5Core.so.5 #2 0x75e81649 in QSocketNotifier::~QSocketNotifier() () from /usr/lib64/libQt5Core.so.5 #3 0x75e738f1 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #4 0x75e7cc8f in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #5 0x7fffde79ade9 in KWin::DrmBackend::~DrmBackend() () from /usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #6 0x75e3e279 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x75e3f66f in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x752a85df in __cxa_finalize () from /lib64/libc.so.6 #9 0x75c49763 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fffcfb0 in ?? () #11 0x77de7c5a in _dl_fini () from /lib64/ld-linux-x86-64.so.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365243] Red and blue channels swapped with fbdev backend on cirrus
https://bugs.kde.org/show_bug.cgi?id=365243 --- Comment #5 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #4) > Please try: https://phabricator.kde.org/D2134 - I hope that this fixes the > problem, but I don't have a way to test it on my system. It does not work, kwin_wayland does not display anything at all. Causing kwin to draw by moving the cursor, for example, results in "QPainter::begin: Paint device returned engine == 0, type: 3 " being printed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365242] KWin crashes in VM with cirrus
https://bugs.kde.org/show_bug.cgi?id=365242 --- Comment #7 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #6) > (In reply to Martin Gräßlin from comment #5) > > > However, it crashes with a segfault after that, in a global destructor: > > > > meh, but a different bug. Have an idea for it ;-) > > And put into code: https://phabricator.kde.org/D2136 Confirmed to work! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365243] Red and blue channels swapped with fbdev backend on cirrus
https://bugs.kde.org/show_bug.cgi?id=365243 --- Comment #9 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #8) > Uploaded a new patch version on phabricator. Now it works and colors are > correct. Works here as well, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365471] New: KWin crashes when switching rendering backend with QPainter scene
https://bugs.kde.org/show_bug.cgi?id=365471 Bug ID: 365471 Summary: KWin crashes when switching rendering backend with QPainter scene Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de In a VM with virtio graphics, KWIN_COMPOSE=Q kwin_wayland [...] crashes when the rendering backend is changed. The actual backend doesn't seem to matter. 264 Window* w = stacking_order[ i ]; 265 Toplevel* topw = w->window() <-- w is nullptr 266 WindowPrePaintData data; Backtrace: #0 0x7fcf7c4600f2 in KWin::Scene::paintSimpleScreen (this=this@entry=0x151f460, orig_mask=orig_mask@entry=0, region=...) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/scene.cpp:264 #1 0x7fcf7c460f24 in KWin::Scene::finalPaintScreen (this=0x151f460, mask=mask@entry=0, region=..., data=...) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/scene.cpp:201 #2 0x7fcf7c489b3f in KWin::EffectsHandlerImpl::paintScreen (this=0x15d0fe0, mask=0, region=..., data=...) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/effects.cpp:429 #3 0x7fcf7c460bad in KWin::Scene::paintScreen (this=this@entry=0x151f460, mask=mask@entry=0x7fffc220eeac, damage=..., repaint=..., updateRegion=updateRegion@entry=0x7fffc220eec0, validRegion=validRegion@entry=0x7fffc220eed0, projection=...) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/scene.cpp:151 #4 0x7fcf7c480e77 in KWin::SceneQPainter::paint (this=0x151f460, damage=..., toplevels=...) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/scene_qpainter.cpp:159 #5 0x7fcf7c45399a in KWin::Compositor::performCompositing (this=this@entry=0x12e3140) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/composite.cpp:713 #6 0x7fcf7c454039 in KWin::Compositor::startupWithWorkspace (this=0x12e3140) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/composite.cpp:334 #7 0x7fcf7c4549e3 in KWin::Compositor::slotCompositingOptionsInitialized (this=this@entry=0x12e3140) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/composite.cpp:269 #8 0x7fcf7c454f12 in KWin::Compositor::setup (this=0x12e3140) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/composite.cpp:180 #9 0x7fcf7c45627c in KWin::Compositor::slotReinitialize (this=0x12e3140) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/composite.cpp:479 #10 0x7fcf7c525b15 in KWin::Compositor::qt_metacall (this=0x12e3140, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x7fffc220f3c0) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/build/kwin_automoc.dir/moc_composite.cpp:332 #11 0x7fcf7395ec90 in ?? () from /usr/lib64/libQt5DBus.so.5 #12 0x7fcf7a862f99 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #13 0x7fcf7ade49ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7fcf7adec151 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7fcf7a836018 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #16 0x7fcf7a8387f0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #17 0x7fcf7a88786a in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #18 0x7fcf637fe8dd in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at eventdispatchers/qunixeventdispatcher.cpp:68 #19 0x7fcf7a833fca in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #20 0x7fcf7a83c8bc in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #21 0x00408d25 in main (argc=, argv=) at /usr/src/debug/kwin-5.6.90git~20160704T143735~2b5747d/main_wayland.cpp:736 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 365606] New: createActivity in plasma script unreliable
https://bugs.kde.org/show_bug.cgi?id=365606 Bug ID: 365606 Summary: createActivity in plasma script unreliable Product: kactivitymanagerd Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org The default plasma startup script (https://github.com/KDE/plasma-desktop/blob/master/desktoppackage/contents/layout.js) creates an activity called "Desktop", but that does only appear sometimes in the activity switcher and desktopsForActivity(id) for that id also returns 0 in that case. Adding while(desktopsForActivity(id).length == 0) sleep(10); does not make it work, so it's not a race condition in the script itself. As a result, customizations in that script, like https://build.opensuse.org/package/view_file/openSUSE:Leap:42.1:Update/plasma5-openSUSE/plasma-change-defaults.diff?expand=1 do not work as expected, as they only touch the newly created activity. This customization, for instance, adds a folderview widget, but on Plasma 5.7.0 it does not appear after logging in. This does not seem to be broken in Plasma < 5.7.0. Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 365606] createActivity in plasma script unreliable
https://bugs.kde.org/show_bug.cgi?id=365606 --- Comment #5 from Fabian Vogt --- Adding a sleep(100); after the call to loadTemplate seems to work around the issue reliably. sleep(100) before loadTemplate does not have the desired effect. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails
https://bugs.kde.org/show_bug.cgi?id=362958 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #22 from Fabian Vogt --- I'm hit by this bug too, which is a really annoying one as now I have to use the webinterface... I've got this log by running kmail with more debug enabled: log_messageviewer: Node UNprocessed: 0x51a6cb0 log_messageviewer: Node UNprocessed: 0x334fb80 log_messageviewer: Node UNprocessed: 0x4edff10 log_messageviewer: Node UNprocessed: 0x321edf0 log_messageviewer: Node UNprocessed: 0x51a6cb0 log_messageviewer: Node UNprocessed: 0x334fb80 log_messageviewer: Node UNprocessed: 0x4edff10 log_messageviewer: Node UNprocessed: 0x321edf0 log_messageviewer: SET NODE: 0x51a6cb0 true log_messageviewer: Node UNprocessed: 0x334fb80 log_messageviewer: SET NODE: 0x334fb80 true log_messageviewer: SET NODE: 0x334fb80 true log_messageviewer: Create temp file: "/tmp/messageviewer_hr9709.index.1/unnamed" log_messageviewer: SET NODE: 0x334fb80 true log_messageviewer: Node processed: "1" "Content-Type: text/plain; charset=\"iso-8859-1\"" log_messageviewer: Node UNprocessed: 0x321edf0 log_messageviewer: SET NODE: 0x321edf0 true log_messageviewer: Node processed: "2" "Content-Type: text/html; charset=\"iso-8859-1\"" log_messageviewer: Node processed: "1" "Content-Type: text/plain; charset=\"iso-8859-1\"" log_messageviewer: Node processed: "" "Content-Type: multipart/alternative; boundary=\"_000_047BDF03F51B7A422BE699F0119E012096D1NWBXMB02microfo_\"" log_messageviewer: SET NODE: 0x321edf0 true log_messageviewer: It does not mention the third node that should be there, which begins with Content-Type: text/calendar; charset="utf-8"; method=REQUEST Content-Transfer-Encoding: base64 I swapped the last two nodes in the mail and that causes it to skip the second node, so it only skips the text/calendar one. I'd like to have a look at the code to find the issue, but I'd need a pointer where I should start looking. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails
https://bugs.kde.org/show_bug.cgi?id=362958 --- Comment #23 from Fabian Vogt --- I investigated a bit more: When the mail contains only the text/calendar node, it's shown as expected. The issue is that in a multipart/alternative handling, it only cares about text/plain and text/html. If one of those is present, it's displayed and everything else is ignored. I have no idea how a proper fix looks like, for now I changed the "break;" in messageviewer/src/viewer/objecttreeparser.cpp:352 to a "continue;", to always display all mail nodes, including text/calendar. This works well for me as I'm mostly working with plaintext mails and calendar invitations anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] New: Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 Bug ID: 365846 Summary: Sorting by DnD broken if not done slow Product: plasmashell Version: 5.7.1 Platform: openSUSE RPMs URL: https://zippy.gfycat.com/SpitefulHighBluefintuna.webm OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org When dragging items in the icons-only task manager with not quite slow mouse movements, various glitches can be observed: The dragged item changes, sometimes it glitches and sometimes even random items swap position (not in the video though). Also, after a restart the taskmanager does not remember some of the icons positions. I did not open a separate report for that as I believe that issue is related. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 Fabian Vogt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Fabian Vogt --- It does not matter what kind of task I drag. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #3 from Fabian Vogt --- I forgot to mention: This is a regression as it worked just fine before 5.7.0 (so before the new taskmanager backend) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #8 from Fabian Vogt --- I just hit this bug as well, but it started to work again after disabling and re-enabling the present windows effect. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails
https://bugs.kde.org/show_bug.cgi?id=362958 --- Comment #32 from Fabian Vogt --- Created attachment 100243 --> https://bugs.kde.org/attachment.cgi?id=100243&action=edit Test mail with invitation Here is a multipart/alternative mail that fails to display properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #4 from Fabian Vogt --- This happens on all my systems updated to 5.7.x, so it's not dependant on the configuration/cache. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362958] After update KMail not interpreting Invite Emails
https://bugs.kde.org/show_bug.cgi?id=362958 --- Comment #38 from Fabian Vogt --- (In reply to Sandro Knauß from comment #37) > Git commit 9b23c8b270bb1555ef9d1b1751fd987675c6279c by Sandro Knauß. > Committed on 26/07/2016 at 10:27. > Pushed by knauss into branch 'Applications/16.08'. > > Render multipart/alternative with a invitation correctly > > alternative parts can also have a calender element, so we want to render > that. > > M +1-1CMakeLists.txt > M +6-6 > messageviewer/src/messagepartthemes/default/autotests/objecttreeparsertest. > cpp > M +12 -13 > messageviewer/src/messagepartthemes/default/autotests/setupenv.h > M +17 -8 > messageviewer/src/messagepartthemes/default/defaultrenderer.cpp > M +7-6messageviewer/src/viewer/objecttreeemptysource.cpp > M +2-2messageviewer/src/viewer/objecttreeemptysource.h > M +19 -6messageviewer/src/viewer/objecttreeviewersource.cpp > M +2-2messageviewer/src/viewer/objecttreeviewersource.h > M +2-1messageviewer/src/viewer/viewer.h > M +27 -2messageviewer/src/viewer/viewer_p.cpp > M +2-0messageviewer/src/viewer/viewer_p.h > M +18 -1messageviewer/src/widgets/htmlstatusbar.cpp > M +4-0messageviewer/src/widgets/htmlstatusbar.h > M +12 -13 mimetreeparser/autotests/setupenv.h > M +26 -35 mimetreeparser/src/bodyformatter/multipartalternative.cpp > M +3-4mimetreeparser/src/interfaces/objecttreesource.h > M +2-1mimetreeparser/src/utils/util.h > M +68 -32 mimetreeparser/src/viewer/messagepart.cpp > M +13 -9mimetreeparser/src/viewer/messagepart.h > M +5-3mimetreeparser/src/viewer/objecttreeparser.cpp > > http://commits.kde.org/messagelib/9b23c8b270bb1555ef9d1b1751fd987675c6279c In messageviewer/src/viewer/viewer_p.cpp: > +const int pos = (availableModes.indexOf(mode) + 1) % > availableModes.size(); "%" is dangerous. If availableModes is empty, it'll crash here. AFAICS it's not possible to reach that state, but it's not obvious at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 Fabian Vogt changed: What|Removed |Added Version|5.7.1 |master --- Comment #5 from Fabian Vogt --- Just installed latest plasma (-desktop, -workspace(-libs), -frameworks) from git and the issue is the same. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 249665] Panel should not auto-hide if any child widget is active
https://bugs.kde.org/show_bug.cgi?id=249665 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #8 from Fabian Vogt --- Confirmed on latest git master. Launcher and calendar/clock work fine, but taskmanager entries and "status & notifications" don't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #7 from Fabian Vogt --- (In reply to Eike Hein from comment #6) > > Also, after a restart the taskmanager does not remember some of the icons > > positions. > > Those would obviously only be remembered for pinned tasks, FWIW. Yes, as I said in comment 2, both kinds of tasks are affected. My guess is that there is some mismatch between the visible position and the internal one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #53 from Fabian Vogt --- Created attachment 100349 --> https://bugs.kde.org/attachment.cgi?id=100349&action=edit Patch to confirm cause The issue is that for every SNI notification with iconThemePath set, it (heap) allocates a lot of stuff, including an KIconLoader and KIconEngine. (SystemTray::resolveIcon in plasma-workspace/applets/systemtray/systemtray.cpp) I quickly hacked a patch together to confirm that this is actually the cause for the load. It seems to improve the cpu % significantly with skype. The result is that most of the time is spent in malloc. I found that with perf record --call-graph plasmashell easily. sni-qt uses IconThemePath by default, but neither KStatusNotifierItem nor QSystemTrayIcon do, so I guess that only Qt4 apps are affected. Can someone confirm that the patch also works for other "plasma-breaking" programs? @devs: Is the correct approach for a fix to cache the final QIcon? If yes, I'd like to make a proper patch and put it up for review. I'd like to reduce the amount of allocations in that context (like KIconLoader in AppIconLoader), but I don't see an easy way to fix that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows
https://bugs.kde.org/show_bug.cgi?id=368891 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #10 from Fabian Vogt --- Only the first activity during the first login seems to be affected, by creating and switching to a new one only one "Configure Desktop" dialog appears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369234] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=369234 Bug ID: 369234 Summary: Crash on exit Product: kwin Version: 5.7.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de Appears on shutdowns and reboots, e.g. when kwin_x11 is killed by systemd. I got this backtrace by attaching to kwin_x11 with gdb and running "init 3" from within the session. Thread 1 "kwin_x11" received signal SIGHUP, Hangup. 0x7f377db1fbd9 in pselect () from /lib64/libc.so.6 (gdb) c Continuing. [Thread 0x7f3764b1a700 (LWP 4153) exited] Thread 1 "kwin_x11" received signal SIGTERM, Terminated. 0x7f377e004690 in ?? () from /usr/lib64/libkdeinit5_kwin_x11.so (gdb) Continuing. [Thread 0x7f375d0fa700 (LWP 4260) exited] [Thread 0x7f376159f700 (LWP 4258) exited] [Thread 0x7f3762c3c700 (LWP 4157) exited] Thread 1 "kwin_x11" received signal SIGSEGV, Segmentation fault. 0x7f377b1a8d4a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 (gdb) bt #0 0x7f377b1a8d4a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #1 0x7f377beafe78 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #2 0x7f377beb449a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #3 0x7f377b1a8fa5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #4 0x7f377b1daaa2 in QObjectPrivate::setParent_helper(QObject*) () from /usr/lib64/libQt5Core.so.5 #5 0x7f377b1dafd2 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #6 0x7f376221cf79 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () from /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #7 0x7f377b19d2a1 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f377b19eb3d in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f377da7449f in __cxa_finalize () from /lib64/libc.so.6 #10 0x7f377afbc3e3 in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7ffe00908ca0 in ?? () #12 0x7f377e21a21a in _dl_fini () from /lib64/ld-linux-x86-64.so.2 Reproducible: Sometimes Qt 5.6.1 on openSUSE Leap 42.2 Beta 3. Nouveau driver used, which shouldn't matter here AFAICT. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369236] New: Panel lacks transparency on first login
https://bugs.kde.org/show_bug.cgi?id=369236 Bug ID: 369236 Summary: Panel lacks transparency on first login Product: plasmashell Version: 5.7.95 Platform: openSUSE RPMs URL: https://openqa.opensuse.org/tests/269120#step/consolet est_finish/10 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de As can be seen on the screenshot (URL) the panel lacks transparency. After a reboot, the panel is transparent again: https://openqa.opensuse.org/tests/268447#step/boot_to_desktop/9 Looks very similiar to bug 362531. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369249] Copying/Moving a file onto itself in folderview crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=369249 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- I made a fix for this on https://phabricator.kde.org/D2847 and the reporter confirms that it works. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369323] New: Discover 5.8 Beta requires unreleased kirigami version
https://bugs.kde.org/show_bug.cgi?id=369323 Bug ID: 369323 Summary: Discover 5.8 Beta requires unreleased kirigami version Product: Discover Version: 5.7.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: fab...@ritter-vogt.de With kirigami 1.0.2, plasma-discover segfaults on start: QQmlApplicationEngine failed to load component qrc:/qml/DiscoverWindow.qml:119 Type DiscoverDrawer unavailable qrc:/qml/DiscoverDrawer.qml:90 Kirigami.Separator is not a type org.kde.kirigami.Separator got introduced 20 days ago and is so far only in git master. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369380] New: When multiple updates recommend a reboot, multiple messages are shown
https://bugs.kde.org/show_bug.cgi?id=369380 Bug ID: 369380 Summary: When multiple updates recommend a reboot, multiple messages are shown Product: Discover Version: 5.7.95 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: fab...@ritter-vogt.de Seven updates were available, two recommend a reboot and one cannot be installed (typical test updates). Result: - One error dialog about the conflict - Two message boxes about reboot recommendation All dialogs appear simultaneously Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 368340] Build fails with mediastreamer 2.14
https://bugs.kde.org/show_bug.cgi?id=368340 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #2 from Fabian Vogt --- Created attachment 101315 --> https://bugs.kde.org/attachment.cgi?id=101315&action=edit Improved patch The attached patch works also for building with old versions. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369380] When multiple updates recommend a reboot, multiple messages are shown
https://bugs.kde.org/show_bug.cgi?id=369380 Fabian Vogt changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Fabian Vogt --- (In reply to Aleix Pol from comment #1) > Can you please notify your distribution about this issue? Feel free to CC me > in it, but this task isn't performed by Discover. It is, it opens a new dialog for each PackageKit message instead of accumulating them in libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369501] New: kwin_wayland crashes in VM when moving window
https://bugs.kde.org/show_bug.cgi?id=369501 Bug ID: 369501 Summary: kwin_wayland crashes in VM when moving window Product: kwin Version: git master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de When moving a window, sometimes kwin_wayland crashes with a stack overflow: #59501 0x75e5188e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #59502 0x77afa769 in KWin::WaylandCursorTheme::loadTheme() () from /usr/lib64/libkwin.so.5 #59503 0x77afab7b in KWin::WaylandCursorTheme::get(Qt::CursorShape) () from /usr/lib64/libkwin.so.5 #59504 0x779efde2 in ?? () from /usr/lib64/libkwin.so.5 #59505 0x779f122c in ?? () from /usr/lib64/libkwin.so.5 #59506 0x75e5188e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #59507 0x77afa769 in KWin::WaylandCursorTheme::loadTheme() () from /usr/lib64/libkwin.so.5 #59508 0x77afab7b in KWin::WaylandCursorTheme::get(Qt::CursorShape) () from /usr/lib64/libkwin.so.5 #59509 0x779efde2 in ?? () from /usr/lib64/libkwin.so.5 #59510 0x779f1187 in ?? () from /usr/lib64/libkwin.so.5 #59511 0x75e5188e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #59512 0x75e5188e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #59513 0x77b23b42 in KWin::AbstractClient::clientStartUserMovedResized(KWin::AbstractClient*) () from /usr/lib64/libkwin.so.5 #59514 0x77a43f6d in KWin::AbstractClient::startMoveResize() () from /usr/lib64/libkwin.so.5 #59515 0x779b74a7 in KWin::AbstractClient::performMouseCommand(KWin::Options::MouseCommand, QPoint const&) () from /usr/lib64/libkwin.so.5 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 369380] When multiple updates recommend a reboot, multiple messages are shown
https://bugs.kde.org/show_bug.cgi?id=369380 --- Comment #4 from Fabian Vogt --- (In reply to Aleix Pol from comment #3) > ? > Let's see, what dialog are you talking about? This one (and similiar calls): https://github.com/KDE/discover/blob/master/libdiscover/backends/PackageKitBackend/PackageKitUpdater.cpp#L268 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368891] Right click desktop, configure desktop opens two windows
https://bugs.kde.org/show_bug.cgi?id=368891 --- Comment #12 from Fabian Vogt --- The issue appears also after switching the look-and-feel with the "Use desktop layout from theme" checkbox enabled. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 369535] New: Extracting files from .rpm via drag-and-drop makes wrong paths
https://bugs.kde.org/show_bug.cgi?id=369535 Bug ID: 369535 Summary: Extracting files from .rpm via drag-and-drop makes wrong paths Product: ark Version: 16.08.0 Platform: Other URL: https://software.opensuse.org/download.html?project=de vel%3AARM%3AFactory%3AContrib%3APine64&package=firmwar e-pine64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: fab...@ritter-vogt.de CC: rak...@freebsd.org, rthoms...@gmail.com It seems like Ark swallows the first few characters of folders in RPMs when extracting. The folders are named correctly in the ark window. Similiar RPMs cause the same behaviour. Reproducible: Always Steps to Reproduce: 1. Open the .aarch64.rpm package downloadable via the URL with ark 2. Open /tmp in dolphin 3. Drag and drop the files in boot/ form ark to dolphin Actual Results: The files get extracted to /tmp/ot/ Expected Results: The files get extracted to /tmp/boot/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369612] New: Default SDDM avatars do not work with the theme
https://bugs.kde.org/show_bug.cgi?id=369612 Bug ID: 369612 Summary: Default SDDM avatars do not work with the theme Product: plasmashell Version: 5.7.95 Platform: openSUSE RPMs URL: https://openqa.opensuse.org/tests/273998#step/first_bo ot/5 OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org The default SDDM avatars (.face.icon/root.face.icon) are dark transparent pngs and thus do not work on dark backgrounds. So far the fallback to the "user-identity" icon worked only because of a bug in sddm 0.14.0: https://github.com/sddm/sddm/pull/684 Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368019] Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 --- Comment #3 from Fabian Vogt --- (In reply to Hugo Pereira Da Costa from comment #2) > In any case, the easyway to see if this is > a style issue is to run > > systemsettings5 -style fusion > > look for the same configuration panel, and see if the problem persists. > @Fabian: can you test/check ? > In the meanwhile I'll try setup a test case. With the fusion style the combobox seems to use up the available space: https://i.imgur.com/rsEuMKc.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369612] Default SDDM avatars do not work with the theme
https://bugs.kde.org/show_bug.cgi?id=369612 --- Comment #1 from Fabian Vogt --- Created attachment 101370 --> https://bugs.kde.org/attachment.cgi?id=101370&action=edit Workaround in the sddm theme I attached a patch that works around the issue by replacing .face.icon and root.face.icon (the default sddm icons) with the plasma "user-identity" icon. The proper fix is probably to expand sddm to support a per-theme "FacesDir=" configuration option and ship default faces with plasma-workspace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #74 from Fabian Vogt --- (In reply to Simone Gaiarin from comment #72) > Is it there any progress on this? Plasma 5.8 is LTS and still has this bug, > that seems quite critical to me. There are multiple animated icons in the > task bar and some of them keep the animation running for a long time causing > the CPU to be always on. > > > - File transfer > - Skype > - Update notification on Manjaro (I need to kill this or update the system, > or my CPU is always on). As far as I can tell there are actually two separate bugs: The one is for system tray icons (such as skype or your update notification) and my patch fixes that and the other one is with animated task manager (?) icons, such as file transfer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #77 from Fabian Vogt --- (In reply to nicholas from comment #76) > (In reply to Fabian Vogt from comment #74) > > As far as I can tell there are actually two separate bugs: The one is for > > system tray icons (such as skype or your update notification) and my patch > > fixes that and the other one is with animated task manager (?) icons, such > > as file transfer. > > 1. your patch does not seem to have progressed since proposal?, or could you > update on status? It's mainly a PoC and workaround and not a proper fix. It still applies to current plasma-workspace git. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479
--- Comment #81 from Fabian Vogt ---
(In reply to Simone Gaiarin from comment #78)
> My workaround for the spinning file transfer is to modify the qml code and
> make it not spin. What other "animated task manager (?) icons" are causing
> the problem beside the file transfer spinner?
I don't know, I haven't hit that bug, only the tray icon one with skype.
> I still haven't tried your patch for the system tray icon. Can I just
> recompile the system tray or does it require to recompile the whole plasma?
You only need to rebuild
%{_libdir}/qt5/plugins/plasma/applets/org.kde.plasma.private.systemtray.so
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 371493] New: Background.qml in the SDDM theme imports QtGraphicalEffects although not used
https://bugs.kde.org/show_bug.cgi?id=371493 Bug ID: 371493 Summary: Background.qml in the SDDM theme imports QtGraphicalEffects although not used Product: plasmashell Version: 5.8.2 Platform: openSUSE RPMs URL: https://www.reddit.com/r/openSUSE/comments/58sdsp/sddm _doesnt_start_and_shows_a_black_screen/ OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org The "import QtGraphicalEffects 1.0" in sddm-theme/Background.qml can be removed. By doing this the whole theme does not require the module to be installed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371493] Background.qml in the SDDM theme imports QtGraphicalEffects although not used
https://bugs.kde.org/show_bug.cgi?id=371493 --- Comment #2 from Fabian Vogt --- (In reply to Kai Uwe Broulik from comment #1) > Doesn't the user delegate require it anyway? So even when removing it there > (which should be done) I would still require said module and so do other > parts of Plasma. It doesn't import QtGraphicalEffects, but it uses "ShaderEffect", which is to my surprise in QtQuick itself -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #11 from Fabian Vogt --- I am able to reproduce this issue on Plasma alsmost-5.7.95, with a clean, default config. By replacing the task manager with the icons only one and opening several windows for testing (kwrite, firefox, qt dbus viewer, qtconfig, dolphin and konsole) the issue appears when dragging items around quickly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365846] Sorting by DnD broken if not done slow
https://bugs.kde.org/show_bug.cgi?id=365846 --- Comment #14 from Fabian Vogt --- (In reply to lmk from comment #13) > Hello! 5.7 is hard masked on gentoo. So you can confirm that it is qt 5.6 > problem? Not with 100% certainty, but I haven't come across this issue on Qt 5.7 yet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 339399] Using Drag and drop with ALT+Tab only works on some applications. Why: ALT key behavior in dolphin.
https://bugs.kde.org/show_bug.cgi?id=339399 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #4 from Fabian Vogt --- I have the same issue here, if the cursor does not move after Alt-Tabbing to a different application, the drop target is the wrong window. I tested both dolphin 16.04.3 and gwenview 16.04.3 as source, so it's likely not dolphin-specific. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 367871] New: CMakeLists.txt only requires Qt 5.2 while code requires Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=367871
Bug ID: 367871
Summary: CMakeLists.txt only requires Qt 5.2 while code
requires Qt 5.6
Product: kdeconnect
Version: 1.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: common
Assignee: albertv...@gmail.com
Reporter: fab...@ritter-vogt.de
I noticed that kdeconnect 1.0 does not build against openSUSE Leap 42.1, which
ships Qt 5.5.1.
This is due to usage of QSet::intersect in the code:
[ 145s] /home/abuild/rpmbuild/BUILD/kdeconnect-kde-1.0/core/pluginloader.cpp:
In member function 'QSet PluginLoader::pluginsForCapabilities(const
QSet&, const QSet&)':
[ 145s]
/home/abuild/rpmbuild/BUILD/kdeconnect-kde-1.0/core/pluginloader.cpp:113:25:
error: 'const class QSet' has no member named 'intersects'
[ 145s] || incoming.intersects(pluginOutgoingCapabilities) ||
outgoing.intersects(pluginIncomingCapabilities)) {
[ 145s] ^
[ 145s]
/home/abuild/rpmbuild/BUILD/kdeconnect-kde-1.0/core/pluginloader.cpp:113:76:
error: 'const class QSet' has no member named 'intersects'
[ 145s] || incoming.intersects(pluginOutgoingCapabilities) ||
outgoing.intersects(pluginIncomingCapabilities)) {
[ 145s]
^
[ 145s] core/CMakeFiles/kdeconnectcore.dir/build.make:398: recipe for target
'core/CMakeFiles/kdeconnectcore.dir/pluginloader.cpp.o' failed
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 367937] Trusted devices randomly unpair after a short time period
https://bugs.kde.org/show_bug.cgi?id=367937 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- I experience the same issue after the kdeconnect android app updated to 1.0. I did not update the desktop application as I only had Qt 5.5.1 available. After the phone loses connection to the computer, they always have to be paired again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368018] New: Panels do not adapt to the screen size without restart
https://bugs.kde.org/show_bug.cgi?id=368018 Bug ID: 368018 Summary: Panels do not adapt to the screen size without restart Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de When changing the screen resolution using kscreen, a maximized panel does not adapt to the full screen width (height not tested, probably affected the same way). A restart of plasmashell fixes this. Reproducible: Always Steps to Reproduce: 1. Start plasma with empty config 2. Change width of primary screen using kscreen The panel now either does not span the whole width of the screen or is wider than the screen. After "kquitapp5 plasmashell; plasmashell" the panel spans the whole screen again. Using unstable Qt 5.7.1. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368019] New: Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 Bug ID: 368019 Summary: Resolution selection box not wide enough with scrollbars Product: KScreen Version: git Platform: openSUSE RPMs URL: http://susepaste.org/view/raw/25387863 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: fab...@ritter-vogt.de The URL points to a screenshot. If the amount of available resolutions does not fit into the box without scrollbars, it causes eliding of some digits. This makes selection much harder. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 361281] migrate away from qtwebkit (gui)
https://bugs.kde.org/show_bug.cgi?id=361281 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- With KDE Applications 16.08, ksysguard seems to be the only application depending on Qt WebKit. It should be migrated to either use QML for the memory details view or WebEngine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 --- Comment #9 from Fabian Vogt --- Still happens with KWin 5.7.3. Weirdly only some windows are affected. To clear up possible misunderstandings, I recorded a short video for demonstration: https://www.youtube.com/watch?v=_m1lnX1lKqw -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 351136] Connection to server lost: unknown error on autostart
https://bugs.kde.org/show_bug.cgi?id=351136 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #5 from Fabian Vogt --- I can reproduce this bug here 100% of the time. I'm using networkmanager and it takes a few seconds after login to get a connection, but even after the connection is established, konversation failes to connect to the servers with an "Unknown error". The ownCloud sync client seems to have the same bug somehow. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359945] Touchpad scroll delta is limited by max. 10
https://bugs.kde.org/show_bug.cgi?id=359945 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #2 from Fabian Vogt --- I reverted the three touchpad related patches in the plasma5-desktop 5.5.5 package on https://build.opensuse.org/package/show/home:favogt:branches:openSUSE:Factory/plasma5-desktop and it works again. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 360199] New: Weird mouse behaviour in plasmoid
https://bugs.kde.org/show_bug.cgi?id=360199 Bug ID: 360199 Summary: Weird mouse behaviour in plasmoid Product: print-manager Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: fab...@ritter-vogt.de The item selection does not follow the mouse cursor position reliably, it seems as if the items had a much smaller MouseArea size. Screencast attached. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 360199] Weird mouse behaviour in plasmoid
https://bugs.kde.org/show_bug.cgi?id=360199 --- Comment #1 from Fabian Vogt --- Created attachment 97736 --> https://bugs.kde.org/attachment.cgi?id=97736&action=edit Video demonstrating the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] New: Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 Bug ID: 360549 Summary: Visible 1px space between window content and title bar when zooming Product: kwin Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de When zooming into the desktop (any of the effects), there is a tiny space between the window content and the title bar. (I couldn't set anything lower then "minor" as severity, I'd have chosen "miniscule" otherwise :) ) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 --- Comment #1 from Fabian Vogt --- Created attachment 97904 --> https://bugs.kde.org/attachment.cgi?id=97904&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 Fabian Vogt changed: What|Removed |Added Component|decorations |effects-various -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 Fabian Vogt changed: What|Removed |Added Attachment #97904|0 |1 is obsolete|| --- Comment #3 from Fabian Vogt --- Created attachment 97910 --> https://bugs.kde.org/attachment.cgi?id=97910&action=edit Screenshot Attached a new screenshot with window not being focused. It looks as if the decoration and content are drawn separately and do not connect properly (half pixel offset?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360549] Visible 1px space between window content and title bar when zooming
https://bugs.kde.org/show_bug.cgi?id=360549 Fabian Vogt changed: What|Removed |Added Attachment #97910|0 |1 is obsolete|| --- Comment #4 from Fabian Vogt --- Created attachment 97911 --> https://bugs.kde.org/attachment.cgi?id=97911&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357861] yakuake KF5 git (2016-01-11): fokus problems, no active terminal
https://bugs.kde.org/show_bug.cgi?id=357861 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #11 from Fabian Vogt --- I'm affected by this bug as well and can't reproduce it reliably either. I noticed however that if the bug is triggered (cursor not filled), I can still type normally, but shortcuts such as Ctrl-Shift-C and Ctrl-Shift-V get recognized as Ctrl-C and Ctrl-V instead. Clicking into the yakuake window does not work, I have to hide and show yakuake again. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 364296] New: Send certificate by mail: Wrong attachment path
https://bugs.kde.org/show_bug.cgi?id=364296 Bug ID: 364296 Summary: Send certificate by mail: Wrong attachment path Product: kleopatra Version: 2.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: fab...@ritter-vogt.de CC: kdepim-b...@kde.org, m...@kde.org After creation of a key, kleopatra provides the option to send the certificate by mail as an attachment. However, KMail interprets the path as URL and fails: File or directory /home/fabian/%2Ftmp%2Fkleo-... not found. As providing an attachment via kmails --attach option works fine, I guess this is a bug in Kleopatra. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364720] New: QPainter backend does not redraw properly
https://bugs.kde.org/show_bug.cgi?id=364720 Bug ID: 364720 Summary: QPainter backend does not redraw properly Product: kwin Version: git master Platform: Other URL: http://susepaste.org/view/raw/52367542 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: backend-fbdev Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de When starting KWin like: KWIN_COMPOSE=Q kwin_wayland --framebuffer [...] redrawing does not work properly. The mouse cursor for example does not get cleared and sometimes the cursor is not visible at all until triggering a redraw. This diff I found (for RebeccaBlackOS) suggests that they had the same issue: https://github.com/n3rdopolis/rebeccablackos/blob/master/rebeccablackos_files/usr/share/RBOS_PATCHES/kwin.diff Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364720] QPainter backend does not redraw properly
https://bugs.kde.org/show_bug.cgi?id=364720 Fabian Vogt changed: What|Removed |Added CC||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364740] New: DRM backend crashes on QEmu
https://bugs.kde.org/show_bug.cgi?id=364740 Bug ID: 364740 Summary: DRM backend crashes on QEmu Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: backend-drm Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de KWIN_COMPOSE=Q kwin_wayland --drm [...] crashes directly on startup on QEmu (QXL). The crash cause is a nullptr dereference in a comparision, with the following backtrace: #0 0x7fffee75471a in QImage::fill(QColor const&) () from /usr/lib64/libQt5Gui.so.5 #1 0x7fffee7549ec in QImage::fill(Qt::GlobalColor) () from /usr/lib64/libQt5Gui.so.5 #2 0x7fffdcccd021 in KWin::DrmBackend::initCursor() () from /usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWayland DrmBackend.so #3 0x7fffdccce52f in KWin::DrmBackend::openDrm() () from /usr/lib64/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrm Backend.so #4 0x75e7b44e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #5 0x77b29652 in KWin::LogindIntegration::hasSessionControlChanged(bool) () from /usr/lib64/libkwin.so.5 #6 0x77abc894 in ?? () from /usr/lib64/libkwin.so.5 #7 0x75e7b44e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #8 0x7fffeefc35ff in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQt5DBus.so.5 #9 0x7fffeefc36f8 in ?? () from /usr/lib64/libQt5DBus.so.5 #10 0x75e7bf99 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #11 0x763fd9ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x76405151 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x75e4f018 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x75e517f0 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.s o.5 #15 0x75ea086a in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib64/libQt5Co re.so.5 #16 0x7fffdee3196d in ?? () from /usr/lib64/qt5/plugins/platforms/KWinQpaPlugin.so #17 0x75e4cfca in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #18 0x75e558bc in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #19 0x00408cb5 in ?? () #20 0x75297741 in __libc_start_main () from /lib64/libc.so.6 #21 0x004093e9 in _start () Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364720] QPainter backend does not redraw properly
https://bugs.kde.org/show_bug.cgi?id=364720 --- Comment #2 from Fabian Vogt --- The DRM backend works fine on my Laptop but is currently broken on QEmu (segfault, bug 364740) so I couldn't test it with the same setup yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364740] DRM backend crashes on QEmu
https://bugs.kde.org/show_bug.cgi?id=364740
--- Comment #3 from Fabian Vogt ---
(In reply to Martin Gräßlin from comment #1)
> I have an idea what going on. Can you get a backtrace with debug symbols and
> would you be able to compile a KWin with a patch?
Sure!
Backtrace with debug symbols:
#0 0x7fffee75471a in QImage::fill(QColor const&) () from
/usr/lib64/libQt5Gui.so.5
#1 0x7fffee7549ec in QImage::fill(Qt::GlobalColor) () from
/usr/lib64/libQt5Gui.so.5
#2 0x7fffdcccd021 in KWin::DrmBackend::initCursor
(this=this@entry=0x66dd60) at
/usr/src/debug/kwin-5.6.90git~20160623T210703~03f0dc5/plugins/platforms/drm/drm_backend.cpp:499
#3 0x7fffdccce52f in KWin::DrmBackend::openDrm (this=0x66dd60) at
/usr/src/debug/kwin-5.6.90git~20160623T210703~03f0dc5/plugins/platforms/drm/drm_backend.cpp:267
#4 0x75e7b44e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#5 0x77b29652 in KWin::LogindIntegration::hasSessionControlChanged
(this=, _t1=, _t1@entry=true) at
/usr/src/debug/kwin-5.6.90git~20160623T210703~03f0dc5/build/moc_logind.cpp:187
#6 0x77abc894 in
KWin::LogindIntegrationoperator()
(self=, __closure=0x6dd050) at
/usr/src/debug/kwin-5.6.90git~20160623T210703~03f0dc5/logind.cpp:281
#7 QtPrivate::FunctorCall,
QtPrivate::List, void,
KWin::LogindIntegration::takeControl()::
>::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:501
#8
QtPrivate::Functor,
1>::call, void> (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:558
#9
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List,void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x6dd040, r=, a=, ret=) at /usr/include/qt5/QtCore/qobject_impl.h:198
#10 0x75e7b44e in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7fffeefc35ff in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
/usr/lib64/libQt5DBus.so.5
#12 0x7fffeefc36f8 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x75e7bf99 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#14 0x763fd9ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#15 0x76405151 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#16 0x75e4f018 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#17 0x75e517f0 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#18 0x75ea086a in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#19 0x7fffdee3196d in QUnixEventDispatcherQPA::processEvents
(this=, flags=...) at
eventdispatchers/qunixeventdispatcher.cpp:68
#20 0x75e4cfca in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#21 0x75e558bc in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#22 0x00408cb5 in main (argc=, argv=) at
/usr/src/debug/kwin-5.6.90git~20160623T210703~03f0dc5/main_wayland.cpp:724
> Adding my idea in case I forget again: the mmap of the DrmBuffer fails for the
cursor buffer. We need to catch this situation properly.
Looks like you're right:
(gdb) print *m_cursor[0]
|
$2 = {m_backend = 0x66dd60, m_surface = 0x0, m_bo = 0x0, m_size = {wd = 64, ht
= 64}, m_handle = 2, m_bufferId = 0, m_stride = 2|
56, m_bufferSize = 16384, m_memory = 0x0, m_image = 0x0}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 364740] DRM backend crashes on QEmu
https://bugs.kde.org/show_bug.cgi?id=364740
--- Comment #5 from Fabian Vogt ---
(In reply to Martin Gräßlin from comment #4)
> thanks for checking my theory in the debugger.
>
> Now I'm wondering why did the map fail and what's the best thing to handle
> the fail. We could just not update the cursor, but that's not really a
> solution. Or we could terminate, because we can expect that it won't work.
Some more information: drmModeAddFB fails because the DRM ioctl returns -1 with
errno set to 22 (EINVAL). A guess: Maybe 32 bpp or 24 bit depth aren't
supported?
if ((ret = DRM_IOCTL(fd, DRM_IOCTL_MODE_ADDFB, &f)))
(gdb) print f
$9 = {fb_id = 0, width = 64, height = 64, pitch = 256, bpp = 32, depth = 24,
handle = 2}
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 356625] New: QQuickWidget goes black when docking
https://bugs.kde.org/show_bug.cgi?id=356625 Bug ID: 356625 Summary: QQuickWidget goes black when docking Product: Breeze Version: 5.4.3 Platform: openSUSE RPMs URL: https://gfycat.com/DeliriousRealBlueandgoldmackaw OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: QStyle Assignee: hugo.pere...@free.fr Reporter: fab...@ritter-vogt.de The attached Qt project opens a mainwindow with a QDockWidget, which has a QQuickWidget as its content. test.qml is a 100x100px large red rectangle. When docking the floating dock, the QQuickWidget becoms unusuable. (Using severity crash here as the widget "hangs" forever in this unusuable state) Reproducible: Always Steps to Reproduce: 1. Compile and run BreezeBug (no shadow build, using relative path to test.qml) 2. Undock the dock by clicking on the button 3. Dock the dock again Actual Results: The widget goes black. Expected Results: It stays red. Works with all other Qt styles I tested (Fusion, GTK, Windows). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356625] QQuickWidget goes black when docking
https://bugs.kde.org/show_bug.cgi?id=356625 --- Comment #1 from Fabian Vogt --- Created attachment 96048 --> https://bugs.kde.org/attachment.cgi?id=96048&action=edit Testcase -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 345574] Konversation segfault upon changing widget style
https://bugs.kde.org/show_bug.cgi?id=345574 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- I can confirm this with Qt 5.5.1 and Konversation 1.6. It also happens when changing breeze settings, like the animation duration. The backtrace is almost identical. Maybe it is related to QApplication being instantiated a bit too late? "QCoreApplication::arguments: Please instantiate the QApplication object first" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 354558] Dolphin crashed when accessing to "Configure Dolphin"
https://bugs.kde.org/show_bug.cgi?id=354558 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #11 from Fabian Vogt --- Dolphin does indeed do some weird stuff with its Control button: in DolphinMainWindow::updateControlMenu: // All actions get cleared by QMenu::clear(). The sub-menus are deleted // by connecting to the aboutToHide() signal from the parent-menu. connect(menu, &QMenu::aboutToHide, helpMenu, &QMenu::deleteLater); Is this even necessary? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357651] New: No error message if file pasting failed
https://bugs.kde.org/show_bug.cgi?id=357651 Bug ID: 357651 Summary: No error message if file pasting failed Product: dolphin Version: 15.12.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de Copying a file into clipboard and then pasting it into a directory with insufficient space does not work and no error message is shown. I tracked it down to connect(m_view, &DolphinView::directoryLoadingCompleted, m_messageWidget, &KMessageWidget::hide); in src/dolphinviewcontainer.cpp. The issue is that pasting a file causes an event to be triggered by KDirNotify, causing a refresh of the directory and in turn the signal directoryLoadingCompleted is emitted. This hides KMessageWidget again, so that it is never shown. Removing the connection isn't a proper solution and I don't know dolphin's code well enough to provide a proper fix. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357742] New: Crash in QV4::ExecutionEngine::newStringObject when opening window
https://bugs.kde.org/show_bug.cgi?id=357742 Bug ID: 357742 Summary: Crash in QV4::ExecutionEngine::newStringObject when opening window Product: kwin Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de I'm using a theme other than breeze and I haven't observed this crash on a different user with breeze enabled. Sometimes, when a window opens, KWin crashes with the following trace: #5 #6 0x7f778c18a935 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f778c134885 in QV4::ExecutionEngine::newStringObject(QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5 #8 0x7f778c1c875e in QV4::Runtime::getProperty(QV4::ExecutionEngine*, QV4::Value const&, int) () from /usr/lib64/libQt5Qml.so.5 Sadly I can't give a better backtrace as GDB generated a corrupted coredump. When it happens again, I'll try to get a more descriptive one. Reproducible: Sometimes Qt 5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357742] Crash in QV4::ExecutionEngine::newStringObject when opening window
https://bugs.kde.org/show_bug.cgi?id=357742 --- Comment #2 from Fabian Vogt --- I was able to get a bit more: #9 0x7f777057cc79 in ?? () #10 0x025be1a0 in ?? () #11 0x7ffee2054250 in ?? () #12 0x00290003 in ?? () #13 0x7f7772b4a258 in ?? () #14 0x0296d980 in ?? () #15 0x72b4a250 in ?? () #16 0x7f7772b4a248 in ?? () #17 0x7f7772b4a250 in ?? () #18 0x0296d980 in ?? () #19 0x7f778c16eb7a in ?? () from /usr/lib64/libQt5Qml.so.5 #20 0x7f778c255d2e in ?? () from /usr/lib64/libQt5Qml.so.5 #21 0x7f778c25623d in ?? () from /usr/lib64/libQt5Qml.so.5 #22 0x7f778c25c6e4 in QQmlBinding::update(QFlags) () from /usr/lib64/libQt5Qml.so.5 #23 0x7f778c265786 in ?? () from /usr/lib64/libQt5Qml.so.5 #24 0x7f778c1f4d04 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /usr/lib64/libQt5Qml.so.5 #25 0x7f778c1f4dc7 in QQmlComponentPrivate::completeCreate() () from /usr/lib64/libQt5Qml.so.5 #26 0x7f778c27fc9e in ?? () from /usr/lib64/libQt5Qml.so.5 #27 0x7f778c16b85e in QV4::BuiltinFunction::call(QV4::Managed*, QV4::CallData*) () from /usr/lib64/libQt5Qml.so.5 #28 0x7f778c1cae83 in QV4::Runtime::callProperty(QV4::ExecutionEngine*, int, QV4::CallData*) () from /usr/lib64/libQt5Qml.so.5 The crash in 351763 is in systemsettings, this one is in kwin. It looks similiar, but not quite the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357754] New: Crash in eglCreateImageKHR
https://bugs.kde.org/show_bug.cgi?id=357754 Bug ID: 357754 Summary: Crash in eglCreateImageKHR Product: kwin Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: egl Assignee: kwin-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de I accidentially set QT_DEVICE_PIXEL_RATIO=100 when opening a Qt application that uses OpenGL and kwin_x11 crashes repoducably with the following backtrace until I kill the application: #0 0x7fcc67729d8d in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fcc67729c24 in __sleep (seconds=0) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0x7fcc5f5d2c33 in ?? () from /usr/lib64/libKF5Crash.so.5 #3 0x7fcc5f5d32a9 in ?? () from /usr/lib64/libKF5Crash.so.5 #4 0x7fcc5f5d3709 in KCrash::defaultCrashHandler(int) () from /usr/lib64/libKF5Crash.so.5 #5 #6 dri2_create_image_khr_pixmap (ctx=, attr_list=, buffer=, disp=0x363b480) at drivers/dri2/platform_x11.c:1051 #7 dri2_x11_create_image_khr (drv=, disp=0x363b480, ctx=, target=, buffer=, attr_list=) at drivers/dri2/platform_x11.c:1074 #8 0x7fcc598c6279 in eglCreateImageKHR (dpy=0x363b480, ctx=0x0, target=12464, buffer=0x7657a89, attr_list=0x7ffdd25b8db0) at main/eglapi.c:1331 #9 0x7fcc6738fada in KWin::AbstractEglTexture::loadTexture (this=0x4d8c670, pix=124091017, size=...) at /usr/src/debug/kwin-5.5.2/abstract_egl_backend.cpp:312 #10 0x7fcc6739075a in KWin::AbstractEglTexture::loadTexture (this=0x4d8c670, pixmap=0x514c720) at /usr/src/debug/kwin-5.5.2/abstract_egl_backend.cpp:289 #11 0x7fcc6732ba24 in KWin::OpenGLWindowPixmap::bind (this=this@entry=0x514c720) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1696 #12 0x7fcc6732bbe8 in KWin::SceneOpenGL::Window::bindTexture (this=this@entry=0x538a3d0) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1301 #13 0x7fcc6732e00e in KWin::SceneOpenGL::Window::beginRenderWindow (this=, mask=, region=..., data=...) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1362 #14 0x7fcc6732e4c6 in KWin::SceneOpenGL2Window::performPaint (this=this@entry=0x538a3d0, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1523 #15 0x7fcc67333d02 in KWin::SceneOpenGL2::performPaintWindow (this=this@entry=0x378dee0, w=w@entry=0x1ceb000, mask=, mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1174 #16 0x7fcc67333ef0 in KWin::SceneOpenGL2::finalDrawWindow (this=0x378dee0, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/scene_opengl.cpp:1160 #17 0x7fcc67340149 in KWin::EffectsHandlerImpl::drawWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:502 #18 0x7fcc648c716a in KWin::ContrastEffect::drawWindow (this=this@entry=0x1634db0, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects/backgroundcontrast/contrast.cpp:387 #19 0x7fcc673400ee in KWin::EffectsHandlerImpl::drawWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:499 #20 0x7fcc648476d2 in KWin::BlurEffect::drawWindow (this=this@entry=0x170e930, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects/blur/blur.cpp:450 #21 0x7fcc673400ee in KWin::EffectsHandlerImpl::drawWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:499 #22 0x7fcc64d1ebb1 in KWin::Effect::drawWindow (this=this@entry=0x3831b40, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/libkwineffects/kwineffects.cpp:582 #23 0x7fcc673400ee in KWin::EffectsHandlerImpl::drawWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:499 #24 0x7fcc673147c1 in KWin::Scene::finalPaintWindow (this=, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/scene.cpp:606 #25 0x7fcc6733ff9a in KWin::EffectsHandlerImpl::paintWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:465 #26 0x7fcc64d1ea91 in KWin::Effect::paintWindow (this=this@entry=0x1634db0, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/libkwineffects/kwineffects.cpp:552 #27 0x7fcc6733ff4e in KWin::EffectsHandlerImpl::paintWindow (this=0x387cb70, w=w@entry=0x1ceb000, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kwin-5.5.2/effects.cpp:462 #28 0x7fcc64d1ea91 in KWin::Effect::paintWindow (this=this@entry=
[kwin] [Bug 347849] Blur effect does not work with zoom.
https://bugs.kde.org/show_bug.cgi?id=347849 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #8 from Fabian Vogt --- Created attachment 96563 --> https://bugs.kde.org/attachment.cgi?id=96563&action=edit Screenshot showing the effect I just hit this bug as well, so I attached a screenshot showing this problem. I have my panel on the right side and currently I'm zooming in to a kwrite window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357754] Crash in eglCreateImageKHR
https://bugs.kde.org/show_bug.cgi?id=357754 --- Comment #3 from Fabian Vogt --- (In reply to Martin Gräßlin from comment #2) > Anyway: I think that should go to upstream bug tracker. Adding a test case > for it should be relatively easy - for once in a while we actually know what > triggered the crash. Ok, reported as https://bugs.freedesktop.org/show_bug.cgi?id=93667 Should I leave this report open until it's fixed in Mesa? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346209] systemsettings crash when looking at the details of the effects
https://bugs.kde.org/show_bug.cgi?id=346209 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #3 from Fabian Vogt --- On openSUSE this can be solved by doing zypper rm libproxy1-config-kde4 See also: https://bugzilla.opensuse.org/show_bug.cgi?id=941784 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358278] New: Panel still focused after auto-hide
https://bugs.kde.org/show_bug.cgi?id=358278 Bug ID: 358278 Summary: Panel still focused after auto-hide Product: plasmashell Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: fab...@ritter-vogt.de 1. Full-screen window on first virtual desktop 2. Panel with auto-hide enabled 3. Switch to a different virtual desktop 4. Show panel, leave cursor on panel 5. Switch back to virtual desktop 1 -> Panel shows if cursor close to the screen edge until the fullscreen window gains focus This happens without virtual desktops as well, if you manage to show the panel while a fullscreen window is shown, by invoking Yakuake, for example. When hidden, the panel should set focus to the fullscreen window if there is one. My explanation isn't the best one, I can record a video if requested. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #17 from Fabian Vogt --- I can reproduce it reliably by running while true; do (kwrite &); sleep 1; killall kwrite; done for a few minutes and then switching to an aurorae based theme. I'm also using Qt 5.5.1, so it might be fixed. The backtrace looks like: #25 0x7fffef9c6c70 in QQmlComponent::create(QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #26 0x7fffc42b5474 in () at /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so #27 0x773278c0 in () at /usr/lib64/libkwin.so.5 #28 0x7721cba9 in () at /usr/lib64/libkwin.so.5 #29 0x77225c3b in () at /usr/lib64/libkwin.so.5 #30 0x7725b669 in () at /usr/lib64/libkwin.so.5 #31 0x773273ec in () at /usr/lib64/libkwin.so.5 #32 0x77329942 in () at /usr/lib64/libkwin.so.5 #33 0x75727e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #34 0x7720cef1 in KWin::Workspace::slotReconfigure() () at /usr/lib64/libkwin.so.5 with full debug info. Somehow gdb does not like kwin debugging, it does not show some symbols. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358278] Panel still focused after auto-hide
https://bugs.kde.org/show_bug.cgi?id=358278 --- Comment #2 from Fabian Vogt --- Created attachment 98201 --> https://bugs.kde.org/attachment.cgi?id=98201&action=edit Video showing the bug I attached a video: There's a fullscreen youtube video, the panel does not show. Then, I switch to desktop 2, click on the panel to focus it and switch back to desktop 1. Now, the panel shows when approaching the right screen edge. Clicking on the video to focus it again restores the original behaviour. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 357413] kde crash on user swap
https://bugs.kde.org/show_bug.cgi?id=357413 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #1 from Fabian Vogt --- Happens for me as well, but only (and perfectly reliably) when clicking "New Session" for the second time. The backtrace looks similiar to bug 351839 in KWin. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 359308] New: Dark text on dark background
https://bugs.kde.org/show_bug.cgi?id=359308 Bug ID: 359308 Summary: Dark text on dark background Product: plasma-pk-updates Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: fab...@ritter-vogt.de When using a dark plasma theme, the state string is almost unreadable, see the attached screenshot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 359308] Dark text on dark background
https://bugs.kde.org/show_bug.cgi?id=359308 --- Comment #1 from Fabian Vogt --- Created attachment 97163 --> https://bugs.kde.org/attachment.cgi?id=97163&action=edit Dark font on dark background -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 359507] New: Conflicting accelerators
https://bugs.kde.org/show_bug.cgi?id=359507 Bug ID: 359507 Summary: Conflicting accelerators Product: kcalc Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: fab...@ritter-vogt.de In the german localization, the H accelerator is used both by the menu item "Hilfe" and the base selection "Hex". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 359721] New: Crash with really large numbers
https://bugs.kde.org/show_bug.cgi?id=359721 Bug ID: 359721 Summary: Crash with really large numbers Product: kcalc Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: fab...@ritter-vogt.de Start kcalc, enter 32, then hit LSH three times. It aborts in libgmp: "gmp: overflow in mpz type". Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
