Bug#1033092: (no subject)
More on this, the autostart works but it only works for increasing in
size, if I decrease it doesn't.
I have found another workaround here
https://superuser.com/questions/1183834/no-auto-resize-with-spice-and-virt-manager
which involves adding a script to watch for display events and trigger
xrandr
#!/bin/sh
sleep 2
xrandr --output "$(xrandr | awk '/ connected/{print $1; exit; }')" --auto
xev -root -event randr | \
grep --line-buffered 'subtype XRROutputChangeNotifyEvent' | \
while read foo ; do \
xrandr --output "$(xrandr | awk '/ connected/{print $1; exit; }')"
--auto
done
Below is the debug log for spice-vdagent when the script isn't in use.
spice-vdagent[1776]: Root size of screen 0 changed to 1920x1080 send 1
spice-vdagent[1776]: display: failed to call GetCurrentState from mutter
over DBUS
spice-vdagent[1776]:error message: Cannot invoke method; proxy is
for the well-known name org.gnome.Mutter.DisplayConfig without an owner,
and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
spice-vdagent[1776]: Unable to find a display id for output index 2)
spice-vdagent[1776]: Unable to find a display id for output index 3)
spice-vdagent[1776]: Sending guest screen resolutions to vdagentd:
spice-vdagent[1776]:display_id=0 - 1920x1080+0+0
spice-vdagent[1776]:display_id=1 - 0x0+0+0
spice-vdagent[1776]: 0x563e06c189e0 sent guest xorg resolution, arg1:
1920, arg2: 1080, size 40
spice-vdagent[1776]: display: failed to call GetCurrentState from mutter
over DBUS
spice-vdagent[1776]:error message: Cannot invoke method; proxy is
for the well-known name org.gnome.Mutter.DisplayConfig without an owner,
and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
spice-vdagent[1776]: Unable to find a display id for output index 2)
spice-vdagent[1776]: Unable to find a display id for output index 3)
spice-vdagent[1776]: Sending guest screen resolutions to vdagentd:
spice-vdagent[1776]:display_id=0 - 1920x1080+0+0
spice-vdagent[1776]:display_id=1 - 0x0+0+0
spice-vdagent[1776]: 0x563e06c189e0 sent guest xorg resolution, arg1:
1920, arg2: 1080, size 40
Bug#1033092: (no subject)
There's a workaround posted on the forums https://forums.debian.net/viewtopic.php?p=774201#p774201 >https://github.com/systemd/systemd/issues/18791 >tl;dr: copy /etc/xdg/autostart/spice-vdagent.desktop to ~/.config/autostart/ then comment out the "X-GNOME-Autostart-Phase" line.
Bug#1033092: (no subject)
Just upgraded from bullseye to bookworm and encountered this, host is on bullseye guest was on bullseye but is now on bookworm, unlike the original reporter adding a spice-vdagent.desktop file does work, the contents are: [Desktop Entry] Exec=/usr/bin/spice-vdagent Icon=dialog-scripts Name=spice-vdagent Path= Type=Application X-KDE-AutostartScript=true Without the desktop file at login spice-vdagent.service and spice-vdagentd.service are both not running. Manually starting them with sudo systemctl start spice-vdagent.service and systemctl start spice-vdagent --user doesn't seem to help the services start but screen resizing doesn't work. Please let me know if you need me to debug further.
Bug#627784: x11vnc: the () keys are reported with wrong keycode
I know this bug is old but I just stumbled upon it when trying to
connect to a machine running in KVM on a host connected to via x11vnc.
The workaround Karl suggested worked perfectly the () keys work again.
Attached is the output of "-v -o log.txt -dk -dk" as requested.25/11/2022 22:45:39 passing arg to libvncserver: -rfbauth
25/11/2022 22:45:39 passing arg to libvncserver: /home/rowan/.vnc/passwd
25/11/2022 22:45:39 passing arg to libvncserver: -rfbport
25/11/2022 22:45:39 passing arg to libvncserver: 5901
25/11/2022 22:45:39 passing arg to libvncserver: -listen
25/11/2022 22:45:39 passing arg to libvncserver: 10.222.0.1
Settings:
display::0
authfile: /var/run/sddm/{57e65f09-c010-4438-b2e6-910dba3be915}
subwin: 0x0
-sid mode: 0
clip: null
flashcmap: 0
shiftcmap: 0
force_idx: 0
cmap8to24: 0
8to24_opts: null
24to32: 0
visual: null
overlay:0
ovl_cursor: 1
scaling:0 1. 1.
viewonly: 0
shared: 1
conn_once: 0
timeout:0
ping: 0
inetd: 0
tightfilexfer: 0
http: 0
connect:null
connectfile null
vnc_conn: 1
allow: null
input: null
passfile: null
unixpw: 0
unixpw_lst: null
ssl:null
ssldir: null
ssltimeout -1
sslverify: null
stunnel:0
accept: null
accept: null
gone: null
users: null
using_shm: 1
flipbytes: 0
onetile:0
solid: null
blackout: null
xinerama: 1
xtrap: 0
xrandr: 0
xrandrmode: null
padgeom:null
logfile:log.txt
logappend: 0
flag: null
rm_flag:null
rc_file:""
norc: 0
dbg:0
bg: 0
mod_tweak: 1
isolevel3: 0
xkb:0
skipkeys: null
sloppykeys: 0
skip_dups: 0
addkeysyms: 1
xkbcompat: 0
clearmods: 0
remap: null
norepeat: 0
norepeatcnt:2
nofb: 0
watchbell: 1
watchsel: 1
watchprim: 1
seldir: null
cursor: 1
multicurs: 0
curs_mode: null
arrow: 1
xfixes: 1
alphacut: 240
alphafrac: 0.33
alpharemove:0
alphablend: 1
cursorshape:1
cursorpos: 1
xwarpptr: 0
alwaysinj: 0
buttonmap: null
dragging: 1
ncache: 0
wireframe: 0xff,2,0,32+8+8+8,all,0.15+0.30+5.0+0.125
wirecopy: always
scrollcopy: mouse
scr_area: 6
scr_skip: ##Soffice.bin,##StarOffice,##OpenOffice
scr_inc: ##Nomatch
scr_keys: null
scr_term: null
scr_keyrep: null
scr_parms: 0+64+32+32,0.02+0.10+0.9,0.03+0.06+0.5+0.1+5.0
fixscreen: null
noxrecord: 0
grabbuster: 0
ptr_mode: 2
inputskip: 10
speeds: null
wmdt: null
debug_ptr: 0
debug_key: 2
defer: 20
waitms: 20
wait_ui:2.00
nowait_bog: 0
slow_fb:0.00
xrefresh: 0.00
readtimeout: 20
take_naps: 1
sb: 60
fbpm: 1
dpms: 1
xdamage:0
xd_area: 2
xd_mem:1.000
xcomposite: 1
multiptr: 0
sigpipe:null
threads:0
fs_frac:0.75
gaps_fill: 4
grow_fill: 3
tile_fuzz: 2
snapfb: 0
rawfb: null
pipeinput: null
gui:0
gui_mode: null
noremote: 0
unsafe: 0
privremote: 0
safer: 0
nocmds: 0
deny_all: 0
pid:445831
25/11/2022 22:45:39 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 445831
25/11/2022 22:45:39 Using X display :0
25/11/2022 22:45:39 rootwin: 0x769 reswin: 0x41 dpy: 0x86499100
25/11/2022 22:45:39
25/11/2022 22:45:39 -- USEFUL INFORMATION --
25/11/2022 22:45:39
25/11/2022 22:45:39 Wireframing: -wireframe mode is in effect for window moves.
25/11/2022 22:45:39 If this yields undesired behavior (poor response, painting
25/11/2022 22:45:39 errors, etc) it may be disabled:
25/11/2022 22:45:39- use '-nowf' to disable wireframing completely.
25/11/2022 22:45:39- use '-nowcr' to disable the Copy Rectangle after the
25/11/2022 22:45:39 moved window is released in the new position.
25/11/2022 22:45:39 Also see the -help entry for tuning parameters.
25/11/2022 22:45:39 You can press 3 Alt_L's (Left "Alt" key) in a row to
25/11/2022 22:45:39 repaint the screen, also see the -fixscreen option for
25/11/2022 22:45:39 periodic repaints.
25/11/2022 22:45:39
25/11/2022 22:45:39 XFIXES available on display, resetting cursor mode
25/11/2022 22:45:39 to: '-cursor most'.
25/11/2022 22:45:39 to disable this behavior use: '-cursor arrow'
25/11/2022 22:45:39 or '-noxfixes'.
25/11/2022 22:45:39 using XFIXES for cursor drawing.
25/11/2022 22:45:39 GrabServer control via XTEST.
25/11/2022 22:45:39
25/11/2022 22:45:39 Scroll Detection: -scrollcopyrect mode is in effect to
25/11/2022 22:45:39 use RECORD extension to try to detect scrolling windows
25/11/2022 22:45:39 (induced by either user keystroke or mouse input).
25/11/2022 22:45:39 If this yields undesired behavior (poor response, painting
25/11/2022 22:45:39 errors, etc) it may be disabled via: '-noscr'
25/11/2022 22:45:39 Also see the -help entry for tuning parameters.
Bug#991334:
Severity: normal This is not a serious bug and is currently slated to remove monit from testing. Please check for severities here https://www.debian.org/Bugs/Developer#severities It's been rejected upstream I'll let the maintainers here comment on if it should be accepted or rejected here.
Bug#990412: pam: PAM doesn't appear to be reading /lib/security
Fair enough, I couldn't find any docs on the policy of /lib/security or any news on it not being scanned in Bullseye, is there something about that somewhere? On 28/06/2021 14:48, Sam Hartman wrote: > control: reassign -1 libpam-yubico > control: severity -1 grave > control: retitle -1 pam_yubico fails to install module in multiarch path > control: found -1 2.23-1 > >>>>>> "Rowan" == Rowan Wookey writes: > > Rowan> It appears that in Bullseye pam isn't checking /lib/security. > > > Rowan> The libpam-yubico package installes a module in /lib/security > Rowan> which when configured without an absolute path pam errors > Rowan> with: > > I think that's a bug in the other package. > The issue is that /lib/security is not a multiarch path. > And so I cannot have both an i386 and amd64 version of the module > installed at the same time. > By this point, we really ought to be supporting multiarch. > > I'm happy to add breaks relationships in pam on broken modules that > don't provide multiarch paths, > but I'd consider this a grave bug on a module that only installs in > /lib/security at this point. >
Bug#917374: Related bug
PAM Bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990412
Bug#990412: pam: PAM doesn't appear to be reading /lib/security
Source: pam Version: 1.4.0-7 Severity: important X-Debbugs-Cc: debianb...@rwky.net Dear Maintainer, It appears that in Bullseye pam isn't checking /lib/security. The libpam-yubico package installes a module in /lib/security which when configured without an absolute path pam errors with: PAM unable to dlopen(pam_yubico.so): /lib/x86_64-linux-gnu/security/pam_yubico.so: cannot open shared object file: No such file or directory This worked fine on Buster, it also works on the latest Ubuntu. lib-pamyubico bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979973 -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#979973: Possibly a bug in PAM
This may not be a bug in this package but instead a bug in pam (which I've reported but not got a bug number for yet). pam should be checking /lib/security for the module. The afore mentioned patch suggests switching to x86_64-linux-gnu whcih is a multi arch directory, if this package is to be converted to multiarch then $(DEB_HOST_MULTIARCH) should be used which can be set using DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) (copied from the pam package rules file) -- Regards Rowan Wookey MSc Comp (Open), CISMP Server Administrator & Programmer Please add ad...@rwky.net to your contacts/email whitelist. My GPG key https://www.rwky.net/admin_at_rwky.net.sig My SSH key https://www.rwky.net/id_rsa.pub
