Bug#1040395: gnome-remote-desktop: Built-in RDP server fails incoming connections with "...(MIC) verification failed!"
Package: gnome-remote-desktop Version: 43.3-1 Severity: important Dear Maintainer, g-r-d's built in RDP server does not work. I have simply just enabled it in gnome-settings, and then attempted to connect. Connecting from either Remmina or Windows 10's MSTSC.exe fails. The following messages are seen in the logs when launching freshly installed remmina and attemping connection to "localhost". The errors are the same from a different machine, this method was chosen to condense the logs. Jul 05 19:01:22 hostname systemd[1506]: Started app-gnome-org.remmina.Remmina-3920.scope - Application launched by gnome-shell. Jul 05 19:01:22 hostname remmina[3925]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=all" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging Jul 05 19:01:22 hostname org.remmina.Remmina.desktop[3925]: Load modules from /usr/lib/x86_64-linux-gnu/remmina/plugins Jul 05 19:01:22 hostname org.remmina.Remmina.desktop[3925]: Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. Jul 05 19:01:22 hostname org.remmina.Remmina.desktop[3925]: The glibsecret secret plugin has been initialized and it will be your default secret plugin Jul 05 19:01:22 hostname remmina[3575]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem Jul 05 19:01:28 hostname org.gnome.Software.desktop[3575]: [19:01:28:082] [3575:3929] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0 Jul 05 19:01:28 hostname org.gnome.Software.desktop[3575]: [19:01:28:082] [3575:3929] [WARN][com.freerdp.crypto] - CN = GNOME, C = US Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:469] [1708:3943] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [ERROR][com.winpr.sspi.NTLM] - Message Integrity Check (MIC) verification failed! Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [WARN][com.winpr.sspi] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [WARN][com.freerdp.core.nla] - CompleteAuthToken status SEC_E_MESSAGE_ALTERED [0x8009030F] Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [ERROR][com.freerdp.core.transport] - client authentication failure Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail Jul 05 19:01:33 hostname gnome-remote-desktop-daemon[1708]: [19:01:33:570] [1708:3943] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Jul 05 19:01:33 hostname gnome-remote-de[1708]: Unable to check file descriptor, closing connection Jul 05 19:01:42 hostname org.gnome.Software.desktop[3575]: [19:01:42:481] [3575:3929] [ERROR][com.freerdp.core.connection] - Timeout waiting for activation This appears to be the same issue as https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/86 however those changes do appear to have made it into debian's libfreerdp-server. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.8-nr44-x13al-r1686793823 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-remote-desktop depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii fuse33.14.0-4 ii init-system-helpers 1.65.2 ii libc62.36-9 ii libcairo21.16.0-7 ii libepoxy01.5.10-1 ii libfreerdp-server2-2 2.10.0+dfsg1-1 ii libfreerdp2-22.10.0+dfsg1-1 ii libfuse3-3 3.14.0-4 ii libglib2.0-0 2.74.6-2 ii libmutter-11-0 43.4-2 ii
Bug#995155: (no subject)
I can confirm that building 15.7 from the debian git, using it to boot (with secure boot off) with the right EFI entry results in the update going through: sudo apt-get build-dep shim sudo apt-get install libefivar-dev # New dependency that apt won't be aware of yet git clone https://salsa.debian.org/efi-team/shim.git dpkg-buildpackage -uc -b sudo dpkg -i ../shim-unsigned_15.7-1~deb11u1_amd64.deb sudo mv /boot/efi/EFI/debian/shimx64.efi /boot/efi/EFI/debian/shimx64-154.efi sudo cp /usr/lib/shim/shimx64.efi /boot/efi/EFI/debian/shimx64.efi -- reboot into firmware, disable secure boot -- -- boot the Linux-Firmware-Updater entry, let the system update -- -- boot back into debian -- sudo apt-get install shim-unsigned=15.4-7 sudo mv /boot/efi/EFI/debian/shimx64-154.efi /boot/efi/EFI/debian/shimx64.efi Signing the shim with MOK doesn't work, FYI, I did try that. -- *Nathaniel Roach*
Bug#917812: gnome-software: update broke gnome software
Hi Andrew, I'm able to reproduce the issue fairly easily, my steps above don't seem to work too well. I'm more than happy to attach strace or do any other steps you'd like me to try while reproducing the issue, just let me know. Cheers. On 19/2/19 5:30 am, Andrew Hayzen wrote: > FYI, I've been discussing this issue with upstream gnome-software > https://gitlab.gnome.org/GNOME/gnome-software/issues/589 and > packagekit https://github.com/hughsie/PackageKit/issues/314 . > > I've not been able to capture a trace of packagekit crashing yet, so > any additional info would be appreciated. > pEpkey.asc Description: application/pgp-keys
Bug#917812: (no subject)
I had the same issue (packagekit worked fine until gnome-software re-opened, where PK will crash), and on a hunch I followed http://allnightburger.com/solved-gnome-software-center-frozen-in-fedora/ but for Debian: sudo apt-get autoremove --purge packagekit gnome-software I noticed that the removal failed un-cleanly: rmdir: failed to remove '/var/cache/app-info/': Directory not empty So I removed the folder nroach44@woody:~$ tree /var/cache/app-info/ /var/cache/app-info/ └── xmls 1 directory, 0 files nroach44@woody:~$ sudo rm -rf /var/cache/app-info/ And reinstalled task-gnome-desktop (to cover the pre-reqs removed by autoremove above) sudo apt-get install task-gnome-desktop And then restarted gnome-software (left it running, whoops) and it started working fine. I figured it wasn't just a bug as my desktop (fully updated like this machine) didn't have the issue. Hopefully this helps narrow down the issue. pEpkey.asc Description: application/pgp-keys
Bug#839232: GM45: Flickering after unlock (with ext. monitor) and sometimes drops sessions after unlock
Package: xserver-xorg-video-intel Version: 2:2.99.917+git20160706-1 Severity: important Dear Maintainer, Bug was previously filed as #821871, got merged into #819083, the fix in 083 did not fix this issue. I *also* have #819116. When using lightdm, when I unlock the session, if I have an external monitor attached the screen goes all flickery, most often the lower ~50% just turns into a flickery glitchy mess. This does not happen when I unlock without being docked (no external monitor). Additionally, about 20% of the time, lightdm will create a new session when unlocking, regardless of an external monitor, thus meaning I lose all of my work. The glitching is fixed by switching to TTY1 and back. If a new session is created, it means that I need to switch to TTY8 instead of 7, weirdly enough though. All of these issues (inlduing #819116) started after an upgrade to this package a few months ago. -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 12 -rw-r--r-- 1 root root 113 Apr 29 15:39 10-intel.conf -rw-r--r-- 1 root root 467 Aug 19 2015 20-thinkpad.conf -rw-r--r-- 1 root root 68 Nov 10 2015 30-hp16500fonts.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.7.5-nr44-normandy-r1474771902+ (root@normandy) (gcc version 6.1.1 20160802 (Debian 6.1.1-11) ) #1 SMP Sun Sep 25 11:10:02 AWST 2016 Xorg X server log files on system: -- -rw-r--r-- 1 root root 18876 Sep 16 2015 /var/log/Xorg.5.log -rw-r--r-- 1 root root 11177 Sep 16 2015 /var/log/Xorg.4.log -rw-r--r-- 1 root root 19716 Mar 24 2016 /var/log/Xorg.3.log -rw-r--r-- 1 root root 18241 Sep 14 14:27 /var/log/Xorg.2.log -rw-r--r-- 1 root root 18582 Sep 30 20:28 /var/log/Xorg.1.log -rw-r--r-- 1 root root 23777 Sep 30 20:29 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [20.064] X.Org X Server 1.18.4 Release Date: 2016-07-19 [20.064] X Protocol Version 11, Revision 0 [20.064] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [20.064] Current Operating System: Linux normandy 4.7.5-nr44-normandy-r1474771902+ #1 SMP Sun Sep 25 11:10:02 AWST 2016 x86_64 [20.064] Kernel command line: BOOT_IMAGE=/vmlinuz-4.7.5-nr44-normandy-r1474771902+ root=UUID=7e542288-02c3-4c78-a50d-6c33dcd0945b ro quiet [20.064] Build Date: 20 July 2016 05:14:41AM [20.064] xorg-server 2:1.18.4-1 (http://www.debian.org/support) [20.064] Current version of pixman: 0.33.6 [20.064]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.064] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.064] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 30 16:53:28 2016 [20.069] (==) Using config directory: "/etc/X11/xorg.conf.d" [20.069] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [20.075] (==) No Layout section. Using the first Screen section. [20.075] (==) No screen section available. Using defaults. [20.075] (**) |-->Screen "Default Screen Section" (0) [20.075] (**) | |-->Monitor "" [20.076] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [20.076] (**) | |-->Device "Intel Graphics" [20.076] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [20.076] (==) Automatically adding devices [20.076] (==) Automatically enabling devices [20.076] (==) Automatically adding GPU devices [20.076] (==) Max clients allowed: 256, resource mask: 0x1f [20.084] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [20.084]Entry deleted from font path. [20.097] (**) FontPath set to: /usr/share/fonts/hp16500b, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [20.097] (==) ModulePath set to "/usr/lib/xorg/modules" [20.097] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [20.098]
Bug#819083: fixed
It fixed the lack of cursor on unlock but the flicker that only clears with a TTY switch persists. On 07/07/16 17:21, Paride Legovini wrote: Fixed in 2:2.99.917+git20160706-1, thank you! The annoying "blink" on lightdm is also gone. I can't find a Debian bug for it, but this was the issue: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1531224 https://bbs.archlinux.org/viewtopic.php?id=206657 Paride
Bug#821871: Acknowledgement (lightdm: Missing cursor and flicking after unlock with XFCE, clears after VT switch)
I also forgot to add that changing display settings (adding a screen or doing anything that causes the screen to flicker briefly, like a resolution change) will also clear the flickering and fix the cursor.
Bug#821871: lightdm: Missing cursor and flicking after unlock with XFCE, clears after VT switch
Package: lightdm Version: 1.18.1-1 Severity: important Dear Maintainer, When using XFCE4 and lightdm, after unlocking the mouse cursor is not visible (but does exist) and there is often flickering. The cursor may reappear while using gnome-terminal, as it hides/un-hides the cursor, but the easiest fix is switching to TTY1 and back (also clears the flickering). I'm filing it against lightdm, but it may be an XOrg bug. As it does not happen with GNOME/GDM3, I'd presume it may lie in how lightdm handles the VT switch. I'm running debian testing x64 on a Thinkpad X200 with a custom kernel, but it's also effecting other users with newer hardware (T460, for example) and is not specific to my kernel build/config. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-nr44-x200-r1458012906+ (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lightdm depends on: ii adduser3.114 ii dbus 1.10.8-1 ii debconf [debconf-2.0] 1.5.59 ii libaudit1 1:2.4.5-1+b1 ii libc6 2.22-6 ii libgcrypt201.6.5-2 ii libglib2.0-0 2.48.0-1 ii libpam-systemd 229-4 ii libpam0g 1.1.8-3.2 ii libxcb11.11.1-1 ii libxdmcp6 1:1.1.2-1.1 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.1-2 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+14 Versions of packages lightdm suggests: ii accountsservice 0.6.40-3 ii upower 0.99.4-2 -- Configuration Files: /etc/lightdm/lightdm.conf changed: [LightDM] [Seat:*] xserver-allow-tcp=true greeter-hide-users=false autologin-user=nroach44 autologin-user-timeout=0 [XDMCPServer] [VNCServer] -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm
Bug#802227: owncloud-client: Forgets some synced directories, replaces with remote root and then fails to sync
Package: owncloud-client Version: 2.0.0+dfsg-1 Severity: important Dear Maintainer, I upgraded owncloud-client via apt-get as usual; when I restarted my session (which would restart the client) it forgot several synced directories and replaced them with the sever's root. Additionally these erraneous entries would fail to sync with "unable to initialise a sync journal" I removed those entries and re-added mine (e.g. media/text) and they synced properly. I restart the client and the issue show again. I closed the client, removed the .local/share/data/ownCloud/ folder and readded my folders, restarted the client and it repeated. As a side-node - I noticed this issue a while ago but I put the package on hold on my computers to allow the issue to be fixed, but it has not. This issue does not occur in v1.8.1 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.3-nr44-x200-r1443948103+ (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages owncloud-client depends on: ii libc6 2.19-22 ii libgcc1 1:5.2.1-22 ii libowncloudsync0 2.0.0+dfsg-1 ii libqt5core5a 5.4.2+dfsg-9 ii libqt5dbus5 5.4.2+dfsg-9 ii libqt5gui55.4.2+dfsg-9 ii libqt5keychain0 0.5.0-1 ii libqt5network55.4.2+dfsg-9 ii libqt5sql5-sqlite 5.4.2+dfsg-9 ii libqt5webkit5 5.4.2+dfsg-3 ii libqt5widgets55.4.2+dfsg-9 ii libqt5xml55.4.2+dfsg-9 ii libssl1.0.0 1.0.2d-1 ii libstdc++65.2.1-22 ii owncloud-client-l10n 2.0.0+dfsg-1 owncloud-client recommends no packages. owncloud-client suggests no packages. -- no debconf information
