[marble] [Bug 305689] Bookmarks are shown on other planets
https://bugs.kde.org/show_bug.cgi?id=305689 --- Comment #2 from Diane Trout --- Yes it's still there. Still kind of funny. On Earth I moved to my starred home location then I changed the map to Moon, and enjoyed looking where my home is on the Moon. I'm on Debian using this version. Package: marble Version: 4:20.12.1-1 -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 406543] QML applications under wayland do not have window decorations.
https://bugs.kde.org/show_bug.cgi?id=406543 --- Comment #4 from Diane Trout --- Looks like I need to try a newer kwin. Thanks for the hint. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 406543] QML applications under wayland do not have window decorations.
https://bugs.kde.org/show_bug.cgi?id=406543 --- Comment #2 from Diane Trout --- (In reply to Aleix Pol from comment #1) > It seems like it's an issue in mutter? > https://gitlab.gnome.org/GNOME/mutter/issues/199 > https://codereview.qt-project.org/#/c/231227/ Are you sure its a mutter issue? My host is running kwin_wayland ps auxw | grep kwin diane21984 5.3 0.9 3241200 162196 tty4 Sl+ 09:20 2:20 /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/lib/x86_64-linux-gnu/libexec/startplasma GNOME_SHELL isn't defined and all my XDG settings are pointing at KDE so the changes in https://codereview.qt-project.org/#/c/231227/ shouldn't be activated? I don't know about the double buffering problem though. env | grep XDG XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3 XDG_SEAT=seat0 XDG_SESSION_DESKTOP=KDE XDG_SESSION_TYPE=wayland XDG_CURRENT_DESKTOP=KDE XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XDG_SESSION_CLASS=user XDG_VTNR=4 XDG_SESSION_ID=29 And I tried looking through gdb's info sharedlibraries for the elisa process and couldn't find any reference to libmutter. I tried dolphin from flathub 74b2d7b235a623ea8dd5bebdfb6c9d1c44b5365c2d1811be52b6218ee15c1953 and it had no decorations as well. I thought kontact worked, but I just remembered we forced it to use xcb because WebKit was broken under wayland. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 406543] New: QML applications under wayland do not have window decorations.
https://bugs.kde.org/show_bug.cgi?id=406543
Bug ID: 406543
Summary: QML applications under wayland do not have window
decorations.
Product: Qt/KDE Flatpak Runtime
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: di...@ghic.org
Target Milestone: ---
SUMMARY
When running under wayland a QML application lacks its window decorations when
run against runtime 5.12.
I first noticed it with the flatpak of elisa,
https://github.com/flathub/org.kde.elisa/issues/6 but I also tested with a
minimal qml file using qmlscene and it also lacked window decorations
My minimal qml file
import QtQuick 2.0
import org.kde.plasma.components 2.0 as PlasmaComponents
Text {
id: helloText
color: "#0ff"
text: "hello"
}
I launched the flatpak with "flatpak --devel run --command=bash org.kde.elisa"
And run in the flatpak with "qmlscene hello.qml" or "qmlscene -platform wayland
hello.qml" I have no window decorations. Using -platform xcb in the container
works. And -platform wayland works outside the container (Debian Testing)
If I downgrade elisa to a version using the 5.11 flatpack the I do get window
decorations even when using -platform wayland.
I would like window decorations to be available.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian Testing
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
The elisa flatpak from flathub.
This version works
0f24374c81c606093c8ca8ad3766c663a55e882a005a52a4051971f38c749963
This version doesn't work.
707a83bcff07a77e300621514b303a43d42e93c3a555979a9b80ecb4892a2e86
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 405242] New: Kontact folder default identity should be settable per resource or should inherit from parent folder
https://bugs.kde.org/show_bug.cgi?id=405242 Bug ID: 405242 Summary: Kontact folder default identity should be settable per resource or should inherit from parent folder Product: kontact Version: 5.10.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: di...@ghic.org Target Milestone: --- I'm experimenting with the flatpak version of kontact 5.10.2 It would be nice if I didn't have to go through each folder on a secondary ews resource and change the default identity for each folder. Ideally one would be able to set the default identity for the account or perhaps child folders could defaulted to the account of their parent. (Then I could just change the root default folder and have it percolate through all the others) -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 339112] mute button doesn't work
https://bugs.kde.org/show_bug.cgi?id=339112 --- Comment #3 from Diane Trout --- ... I'm not sure I can test it I think the whole component is currently broken. I have trouble just getting the text-ui component working let alone trying for the call component. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345846] Graphical glitches when trying to switch when changing set of active monitors.
https://bugs.kde.org/show_bug.cgi?id=345846 --- Comment #11 from Diane Trout --- Oh wow. I forgot about this bug. I haven't seen this problem with plasma in a quite a long time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #10 from Diane Trout --- Created attachment 115840 --> https://bugs.kde.org/attachment.cgi?id=115840&action=edit log of plugging in external dock after rebooting It didn't detect the monitor connected to the external dock either. Any suggestions for udevadm info commands you'd like? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #9 from Diane Trout --- I haven't used those before, udev-browse isn't available for debian, so I went with udevadm monitor. Hope that's useful. I started udevadm monitor | tee udev.monitor.log in a tmux session so even if plasma locked up I should still get some log messages. I started it while plugged into the smaller USB C dongle connected to 1600x1200 monitor over VGA, and then I suspend the computer. I took it home and plugged it into a USB C dock and opened the computer. I looked at twitter and watched a bit of a video, and then killed udevadm monitor. There was only one display listed in Displays and the scale for the laptop display had defaulted to 1x instead of 2x. See log of udevadm monitor after resuming... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #8 from Diane Trout --- Created attachment 115839 --> https://bugs.kde.org/attachment.cgi?id=115839&action=edit log of udevadm monitor after resuming connected to a different USB C dock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #6 from Diane Trout --- Went home opened laptop from suspend, then laptop screen appeared with 1x scale. Plugged in dock and it didnt detect it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #5 from Diane Trout --- Is kwin wayland listening for the resume signal from powerdevil? Maybe me removing it is the cause for not scanning the hardware? I saw the signal: org.kde.Solid.PowerManagement.Actions.SuspendSession.resumingFromSuspend -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #4 from Diane Trout --- One more observation. When I disconnected the microdock while the laptop was on. The laptop screen scale immediately went from x2 to x1. (Desktop is currently running Debian testing) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #3 from Diane Trout --- Thank you. Everything is well here. (I'm just attempting Plasma again using GNOME for a while) I can report kwin-wayland does two things better than gnome. It correctly scales Xwayland apps regardless of the dpi of the display the window is on, and it correctly scales a part of the window if its hanging onto a display with a different dpi) So. I'll need a bit of testing to duplicate your questions but maybe these additional details will help. At work I have one of these: https://www.dell.com/en-us/shop/dell-adapter-usb-c-to-hdmi-vga-ethernet-usb-30-da200/apd/470-abqn/pc-accessories With a Dell 2007FP plugged in via VGA. I then suspend the laptop, take it home and plug it into one of these: https://www.dell.com/support/article/us/en/19/sln304627/dell-dock-wd15-usb-type-c-information-compatibility-and-specifications?lang=en There is a Dell 27" monitor plugged in via display port on the dock. (Sorry don't have model number since I'm not at home) I wake the laptop and under plasma wayland only the laptop display is active. (Also under in this condition the scale for the laptop screen under plasma resets to 1x, I have to manually reset it to 2x.) I'm not sure its 100% reliable, but it has certainly happened multiple times. For a bit I was avoiding the bug shutting down the laptop instead of sleeping it , but that was because I had been getting powerdevil segfaults and had uninstalled powerdevil. Under gnome wayland after resuming from the same conditions sleeping at work, disconnecting the microdock, going home plugging in the WD15 dock, and resuming) both displays would work. (It "worked" with GNOME X too, but xrandr wasn't reliable at resetting both displays to the right scaling.) I haven't tried resuming first and then plugging in the dock after getting home. I also haven't tried suspending and then resuming without unplugging from the WD15 dock after it had been correctly detected on boot. I'll try those tonight. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 --- Comment #1 from Diane Trout --- Logging out leaves an error message, I have to reboot for it to detect the external monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] After resuming from suspend kwin_wayland doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 Diane Trout changed: What|Removed |Added Summary|After resuming from suspend |After resuming from suspend |kwin doesn't detect an |kwin_wayland doesn't detect |external monitor connected |an external monitor |via USB C |connected via USB C -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399590] New: After resuming from suspend kwin doesn't detect an external monitor connected via USB C
https://bugs.kde.org/show_bug.cgi?id=399590 Bug ID: 399590 Summary: After resuming from suspend kwin doesn't detect an external monitor connected via USB C Product: kwin Version: 5.13.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: di...@ghic.org Target Milestone: --- SUMMARY I have a Dell XPS 13 9360. When I resume the laptop after plugging in the USB-C docking station it regularly fails to detect the external HDMI monitor. Only one monitor shows up in the Display System Settings Module, and only one display shows up in xrandr. EXPECTED RESULT Both displays should be configurable. SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.49.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Kernel Version 4.18.0-1-amd64 4xIntel Core i7-7500U @ 2.7 GhZ -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 Diane Trout changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 --- Comment #7 from Diane Trout --- The flatpak platform updated, and the host Plasma instance has also seen updates. Maybe that's helped? Or maybe it was rebooting first, and with the screens already configured correctly I'll close the bug for now, You had an idea of where the bug might've been? Could you point me toward it? So, if it happens again I can try to build from source and see if I can spot the problem. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 --- Comment #5 from Diane Trout --- Elisa opened with a correctly sized window with a two displays on wayland with the following flatpak version Date: 2018-09-30 07:43:48 + Subject: build stable 0.3 version of Elisa (1d346801) Commit: 50efbf9079880e1f1a6ff9b1306912a8f37d66538ba86a136f8095bdd033c5c4 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 --- Comment #3 from Diane Trout --- Apparently it because I'm using dual screens. The laptop has a highdpi 3200x1800 13" screen, and I had it plugged in as in "extend the desktop" mode into a 20" 1600x1200 monitor. When I have elisa opening on just a single desktop it seems to open correctly. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 --- Comment #1 from Diane Trout --- Hm. This could be a kwin bug. I tried starting the task manager config panel and it also started with a large amount of extra space around the UI elements. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 Diane Trout changed: What|Removed |Added Platform|Other |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 397844] New: elisa starts too large on wayland desktop
https://bugs.kde.org/show_bug.cgi?id=397844 Bug ID: 397844 Summary: elisa starts too large on wayland desktop Product: elisa Version: 0.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: di...@ghic.org Target Milestone: --- Created attachment 114583 --> https://bugs.kde.org/attachment.cgi?id=114583&action=edit screenshot when first opening elisa Hello On a Debian Testing desktop running plasma on wayland, and using the version 0.2.1 of elisa from flathub, elisa starts with its window being much larger than its UI. (See attached screenshot) flatpak info org.kde.elisa Ref: app/org.kde.elisa/x86_64/stable ID: org.kde.elisa Arch: x86_64 Branch: stable Origin: flathub Collection ID: org.flathub.Stable Date: 2018-07-11 10:19:34 + Subject: upgrade to 0.2.1 stable version of Elisa (0ccfce1e) Commit: 64bf7b02151b8699696b6ad0fb13f1ac00d871cf8dc9a7f3b54ad46dd4fb8cbb Parent: c2ef0d2cc160a69a1f03d5d5fee9f89d0fddb3d8ea6b6b716c9c7b8751f6cab9 Location: /var/lib/flatpak/app/org.kde.elisa/x86_64/stable/64bf7b02151b8699696b6ad0fb13f1ac00d871cf8dc9a7f3b54ad46dd4fb8cbb Installed size: 9.9 MB Runtime: org.kde.Platform/x86_64/5.11 Sdk: org.kde.Sdk/x86_64/5.11 Potentially relevant Debian desktop component version: ii kwin-wayland4:5.13.1-1+b amd64KDE window manager, wayland version ii libwayland-serv 1.15.0-2 amd64wayland compositor infrastructure - ii plasma-workspac 4:5.13.2-1 amd64Plasma Workspace for KF5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 351777] plasmashell crashed might due to applet actions is nullptr
https://bugs.kde.org/show_bug.cgi?id=351777 Diane Trout changed: What|Removed |Added CC||di...@ghic.org --- Comment #17 from Diane Trout --- I'm still seeing this on Debian sid. 4:5.4.3 happens when I unsleep the laptop, especially when the monitor configuration has changed. (e.g. plugging in a different external monitor and resuming). I'm using a thinkpad x220 tablet, looks like I have an intel card using mesa 11.0.6. (Below is the lspci output for the VGA card). 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21db Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at [disabled] Capabilities: Kernel driver in use: i915 -- You are receiving this mail because: You are watching all bug changes.
