Bug#1052197: sync with xorgxrdp

2023-09-19 Thread Blindauer Emmanuel

Hello,

The bug is also reported upstream:

https://github.com/neutrinolabs/xrdp/issues/2796

the xorgxrdp package must be updated in sync for the xrdp version

Emmanuel Blindauer



Bug#940544: xrdp doesn't always start at boot (full install)

2019-09-16 Thread BLINDAUER Emmanuel
Package: xrdp
Version: 0.9.9-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Buster install from network, xfce as desktop, xrdp and xorgxrdp installed later
(full install automated). I have the problem both on physical server and in VM.

   * What was the outcome of this action?
The service doesn't start, so the server doesn't accept connections



Something is perhaps wrong with /run and /var/run according to the logs (below).
If I restart the service, all is fine, it's perhaps a race condition.

Notice that debian ships a prestart script which creates /var/run/xrdp

root@phoenix:~# systemctl status xrdp
● xrdp.service - xrdp daemon
   Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: timeout) since Tue 2019-09-17 05:04:42 CEST; 1h 
51min ago
 Docs: man:xrdp(8)
   man:xrdp.ini(5)

sept. 17 05:03:11 phoenix systemd[1]: xrdp.service: Can't open PID file 
/run/xrdp/xrdp.pid (yet?) after start: No such file or directory
sept. 17 05:03:12 phoenix systemd[1]: /lib/systemd/system/xrdp.service:8: 
PIDFile= references path below legacy directory /var/run/, updating 
/var/run/xrdp/xrdp.pid → /ru
sept. 17 05:03:13 phoenix xrdp[1246]: (1246)(140441694279488)[INFO ] starting 
xrdp with pid 1246
sept. 17 05:03:13 phoenix xrdp[1246]: (1246)(140441694279488)[INFO ] listening 
to port 3389 on 0.0.0.0
sept. 17 05:04:42 phoenix systemd[1]: xrdp.service: Start operation timed out. 
Terminating.
sept. 17 05:04:42 phoenix systemd[1]: xrdp.service: Failed with result 
'timeout'.
sept. 17 05:04:42 phoenix systemd[1]: Stopped xrdp daemon.
sept. 17 05:33:12 phoenix systemd[1]: /lib/systemd/system/xrdp.service:8: 
PIDFile= references path below legacy directory /var/run/, updating 
/var/run/xrdp/xrdp.pid → /ru

-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/40 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xrdp depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libfuse2 2.9.9-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libopus0 1.3-1
ii  libpam0g 1.3.1-5
ii  libssl1.11.1.1c-1
ii  libx11-6 2:1.6.7-1
ii  libxfixes3   1:5.0.3-1
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 10.2019051400
ii  ssl-cert 1.0.39

Versions of packages xrdp recommends:
pn  fuse  
ii  xorgxrdp  1:0.2.9-1

Versions of packages xrdp suggests:
pn  guacamole  
pn  xrdp-pulseaudio-installer  

Versions of packages xorgxrdp depends on:
ii  libc6  2.28-10
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.4-1

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+19

Versions of packages xrdp is related to:
pn  vnc-server   
pn  xserver-xorg-legacy  

-- Configuration Files:
/etc/xrdp/sesman.ini changed:
;; See `man 5 sesman.ini` for details
[Globals]
ListenAddress=127.0.0.1
ListenPort=3350
EnableUserWindowManager=true
; Give in relative path to user's home directory
UserWindowManager=startwm.sh
; Give in full path or relative path to /etc/xrdp
DefaultWindowManager=startwm.sh
; Give in full path or relative path to /etc/xrdp
ReconnectScript=reconnectwm.sh
[Security]
AllowRootLogin=true
MaxLoginRetry=4
TerminalServerUsers=tsusers
TerminalServerAdmins=tsadmins
; When AlwaysGroupCheck=false access will be permitted
; if the group TerminalServerUsers is not defined.
AlwaysGroupCheck=false
[Sessions]
;; X11DisplayOffset - x11 display number offset
; Type: integer
; Default: 10
X11DisplayOffset=50
;; MaxSessions - maximum number of connections to an xrdp server
; Type: integer
; Default: 0
MaxSessions=50
;; KillDisconnected - kill disconnected sessions
; Type: boolean
; Default: false
; if 1, true, or yes, kill session after 60 seconds
KillDisconnected=true
;; DisconnectedTimeLimit - when to kill idle sessions
; Type: integer
; Default: 0
; if not zero, the seconds before a disconnected session is killed
; min 60 seconds
DisconnectedTimeLimit=300
;; IdleTimeLimit (specify in second) - wait before disconnect idle sessions
; Type: integer
; Default: 0
; Set to 0 to disable idle disconnection.
IdleTimeLimit=0
;; Policy - session allocation policy
; Type: enum [ "Default" | "UBD" | "UBI" | "UBC" | "UBDI" | "UBDC" ]
; Default: Xrdp: and Xvnc:
; "UBD" session per 
; "UBI" session per 
; "UBC" session per 
; "UBDI" session per 
; "UBDC" session per 
Policy=Default
[Logging]
LogFile=xrdp-sesman.log
LogLevel=DEBUG
EnableSyslog=1
SyslogLevel=DEBUG
;
; Session definitions - startup command-line parameters for each session type
;
[Xorg]
; Specify the path of non-suid Xorg executable. It might differ 

Bug#377077: libkrb5: library makes smbd crash

2006-07-06 Thread Blindauer Emmanuel
I don't know what more infos I can provide, but the keytab isn't empty, it has 
been populated with net ads keytab create command, I can list all entries 
with a klist -k  and I don't see such segfaults with an samba 3.0.23rc3 
linked with libkrb5 v 1.4.3
I cannot find a way to reproduce this bug, but it's happen at least 4 or 5 per 
day.


Le Jeudi 6 Juillet 2006 18:50, vous avez écrit :
 tags 377077 sarge moreinfo
 thanks

 blindauer [EMAIL PROTECTED] writes:
  Package: libkrb53
  Version: 1.3.6-2sarge2
  Severity: important
  File: libkrb5
 
  Tis version of libkrb5 is buggy. It makes smbd crash in its latest
  release.
  See:
 
  https://bugzilla.samba.org/show_bug.cgi?id=3911

 There are few details in that bug, so it would be rather hard for anyone
 to fix this.  Could you please provide (considerably) more details on
 exactly when this happens and also confirm that the keytab file isn't
 empty on that system?