Your message dated Thu, 6 Nov 2025 18:43:35 -0500
with message-id
<caaajcmacpsk1zac11iehktfkzdmom2cs5irpqhacqtsw1dn...@mail.gmail.com>
and subject line closing old gnome-session bugs
has caused the Debian Bug report #776746,
regarding xrdp "Oh no! Something has gone wrong." is back
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
776746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776746
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xrdp
Version: 0.6.1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after dist-upgrade to jessie of a wheezy-installation with gnome desktop comes
"Oh no! Something has gone wrong."
on access from Windows to this machine - also with Remmina on localhost.
I tryed
dpkg -- purge xrdp
apt-get install xrdp
without success.
Thank You
Joachim
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xrdp depends on:
ii adduser 3.113+nmu3
ii libc6 2.19-18
ii libpam0g 1.1.8-3.1
ii libssl1.0.0 1.0.1k-3
ii libx11-6 2:1.6.2-3
ii libxfixes3 1:5.0.1-2+b2
Versions of packages xrdp recommends:
ii vnc4server [vnc-server] 4.1.1+X4.3.0-37.6
xrdp suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
