https://bugs.kde.org/show_bug.cgi?id=356864
Aleix Pol changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/libk |http://commits.kde.org/libk
|scre
https://bugs.kde.org/show_bug.cgi?id=356864
RussianNeuroMancer changed:
What|Removed |Added
CC||russianneuroman...@ya.ru
--- Comment #48 f
https://bugs.kde.org/show_bug.cgi?id=356864
Aleix Pol changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
--- Comment #47 from Aleix Pol ---
It's
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #46 from ccrompho_w...@hotmail.com ---
Hi,
Some more information since apparently the situation changed.
Whonix have been updated to 14. so the plasmashell have been integrated into a
debian stretch version.
It's a fresh installation from w
https://bugs.kde.org/show_bug.cgi?id=356864
ccrompho_w...@hotmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #45 from OlafLostViking ---
After the VM window was in fullscreen size, kscreen/plasma no longer
automatically adapts to a new (smaller or bigger) size of the VM window. It's
necessary to manually adapt to the new size just like after the ve
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #44 from OlafLostViking ---
Sorry for the double post. But after talking about the display manager: What
about setups without display managers? Where the plasma sessions is started
directly by systemd or sth. similar?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #43 from OlafLostViking ---
(In reply to Sebastian Kügler from comment #42)
> That means that if you log into a fresh session, we don't do anything on
> login wrt screen setup. We expect the system to be set up.
Oh, I'm sorry, now I underst
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #42 from Sebastian Kügler ---
Let me try to clear it up then. :) Currently, we don't change the resolution if
the user hasn't configured this exact combination of screens previously. That
means that if you log into a fresh session, we don't
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #41 from OlafLostViking ---
I'm not sure if I understood you correctly. But if you suggested that, when
starting a plasmashell session, you set the initial resolution to the size of
the VM window (preferred resolution as shown by xrandr), in
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #40 from Sebastian Kügler ---
I'm right now getting a stable branch set up to test with, since I want these
changes in the next 5.8 update. David has given the backports another review.
As to updating the dropdown in kscreen is kind of on m
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #39 from OlafLostViking ---
I just updated the VM again:
* The guest desktop will still only adjust to the outer window size after it
has been changed at least once manually via kscreen to the exact size of a
resized VM window.
* The model
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #38 from Sebastian Kügler ---
Git commit d5b9d37767adbf2a035281fbeb5f38a309160413 by Sebastian Kügler.
Committed on 23/11/2016 at 15:22.
Pushed by sebas into branch 'Plasma/5.8'.
apply config change after correcting invalid mode
The logic
https://bugs.kde.org/show_bug.cgi?id=356864
Sebastian Kügler changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/libk |http://commits.kde.org/libk
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #36 from Sebastian Kügler ---
Git commit f6bbb3782566fbac431bbdc641c55942d8643951 by Sebastian Kügler.
Committed on 22/11/2016 at 13:50.
Pushed by sebas into branch 'sebas/dynmodes'.
apply config change after correcing invalid mode
The log
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #35 from OlafLostViking ---
I updated the Neon VM during the last days (as well as just minutes ago) but my
plasma desktop didn't adjust itself to the VM window.
But then I opened up kscreen to check if the new "strange" resolution is
final
https://bugs.kde.org/show_bug.cgi?id=356864
Sebastian Kügler changed:
What|Removed |Added
CC||adrela...@riseup.net
--- Comment #34 from Se
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #33 from Sebastian Kügler ---
Alright, after some more testing, I'm quite confident that this works now.
To give this some context, this small patch plus the one from comment#25 makes
it work for me, that's the status reflected in git mast
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #32 from Sebastian Kügler ---
Git commit b8a7cd7044fa483c2c77a4ab7f0b64c08f2c3304 by Sebastian Kügler.
Committed on 17/11/2016 at 02:37.
Pushed by sebas into branch 'master'.
apply config change after correcing invalid mode
The logic here
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #31 from Sebastian Kügler ---
Ok, cool. After some more fiddling, I'm getting the events now that I was
looking for. On it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #30 from OlafLostViking ---
(Welcome back, I hope you are refreshed enough for all these bugs ;-) )
I'm not an expert for virt-manager. But by default my own virt-manager is just
setting up a spice-channel. This channel is then used for the
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #29 from Sebastian Kügler ---
(getting back to this, I haven't forgotten, just was on vacation)
I think I'm being an utter muppet here. I have started spice-vdagent, qemu-ga
gives the same error. Perhaps the wrong magical invocation? Would
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #28 from OlafLostViking ---
Did you install and run the mentioned spice-vdagent? This is mandatory for
virt-manager based VMs to communicate with the host.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #27 from Sebastian Kügler ---
I'm trying to reproduce by running a neon session in a virt-manager, using
qemu. I've the driver QXL, and I've installed qemu-ga inside the vm, but it
can't find a channel, so it doesn't work. The error is:
cri
https://bugs.kde.org/show_bug.cgi?id=356864
Sebastian Kügler changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=356864
Sebastian Kügler changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/libk
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #24 from Sebastian Kügler ---
Great. I'm making some progress on the code side. It's a little involved, since
the list of modes per output is static, so it's not actually supposed to
change. That's expressed in libkscreen's API, and on top o
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #23 from OlafLostViking ---
I just setup a Neon Developer Unstable VM. So I can help trying out stuff in
there! (As of today, it doesn't work.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356864
Sebastian Kügler changed:
What|Removed |Added
Component|kded|libkscreen
Version|5.7.1
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #22 from Sebastian Kügler ---
A shot in the dark: https://phabricator.kde.org/D2155
This hooks into the change signal path, and "fixes up" output's current mode
id. It seems that the internal list of outputs is already updated, but the
out
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #21 from Martin Gräßlin ---
Documenting some debug output from before and after resizing the VM window:
/usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher
kscreen.xrandr: Connected output 67 to CRTC 63
Mode: 725 / QSize(16
https://bugs.kde.org/show_bug.cgi?id=356864
--- Comment #20 from Martin Gräßlin ---
Randr events on resize of window (recorded through xev)
RRScreenChangeNotify event, serial 37, synthetic NO, window 0x121,
root 0x276, timestamp 300084, config_timestamp 801745
size_index 65535, subpi
https://bugs.kde.org/show_bug.cgi?id=356864
Martin Gräßlin changed:
What|Removed |Added
Ever confirmed|0 |1
Product|plasmashell
33 matches
Mail list logo
