Bug#944490: Multiple errors that make the package unusable

[Gilles MOREL]

Package: postfixadmin
Version: 3.2.1-2
Severity: important

Hello,

I installed the postfixadmin package on Debian 10, but when I try to use it, 
there are several mistakes that make the package unusable.

The first is the alias in the apache configuration that makes show a error on 
the index page:
The Postfix Admin directory layout changed.
Please update your webserver config so that the DocumentRoot or Alias points to 
the directory "public".

The second is when I correct the first by going to public subdirectory :
ERROR: the templates_c directory doesn't exist or isn't writeable for the 
webserver
Doing a "mkdir -m 0777 /usr/share/postfixadmin/templates_c" (ugly), I correct 
the error, and then.

The third is that:
DEBUG INFORMATION:
MySQL 3.x / 4.0 functions not available! (php5-mysql installed?)
database_type = 'mysql' in config.inc.php, are you using a different database?
The database is actually a mysql database and the packaage php-mysql is 
installed (because postfixadmin depends on it), but the php5-mysql package is 
not available.

I can't go any futher because I don't know how to resolve this error.
--
Gilles MOREL 
Le hasard a fait que ce message vient de mon téléphone portable. Curieux, non ?

Bug#935182: Concurrent file open results file deletion by the read-only instance

[Gilles MOREL]

Hi,

For severity, I read severity's description and the first that seemed to fit 
was grave, since I got data loss.
For multiple user on the same host, the host is actually a RDP server, served 
by xrdp.
For the version, that's because I tryed to use the backports version of LO, but 
the problem is there too.
--
Gilles MOREL 
Le premier tirage aléatoire est [51, 31, 38, 6, 16] et le second est [9, 9, 9, 
9, 9]. Quel tirage est le plus aléatoire ?


- Message original 
Rene Engelhard 
à Gilles MOREL , 935...@bugs.debian.org
le mardi 20 août 2019 à 18:30:06 +0200
avec Mutt/1.10.1 (2018-07-13)

Re: Bug#935182: Concurrent file open results file deletion by the read-only 
instance
--
Hi,

On Tue, Aug 20, 2019 at 04:52:52PM +0200, Gilles MOREL wrote:
> Package: libreoffice-core
> Version: 1:6.1.5-3+deb10u3
> Severity: grave

2 grave   makes the package in question unusable by most or all users, 
or causes data loss, or
  introduces a security hole allowing access to the accounts of 
users who use the package.
[...]
4 important   a bug which has a major effect on the usability of a package, 
without rendering it completely
  unusable to everyone.

Ok, one might argue this as data loss, but I don't think this is grave enough to
warrant grave, important looks more suited. But anyways.

> When two users on the same machine open

Why two users on the same machine, same file? I could understand the
scenario of same file on samba share, different computers... Or do
you use some graphical "remote desktop" thingy allowing access of more
people to one comuter?

> If the first user saves modification while the second user have the file 
> openned, the first user gets an error saying the file does not exists anymore.
> And then, the file is actually deleted once the second user closes the file.

LO has lockinbg problems like this. This is nothing new. In fact, quick googling
just gave me
https://bugs.documentfoundation.org/show_bug.cgi?id=115747#c28

> Versions of packages libreoffice-core depends on:
> ii  fontconfig2.13.1-2
> ii  fonts-opensymbol  2:102.11+LibO6.3.0-2~bpo10+1
[...]
> ii  libreoffice-common1:6.1.5-3+deb10u3
[...]
> ii  uno-libs3 6.3.0-2~bpo10+1
> ii  ure   6.3.0-2~bpo10+1
[...]
> ii  libreoffice-style-colibre  1:6.1.5-3+deb10u3
> ii  libreoffice-style-tango1:6.1.5-3+deb10u3
> ii  ure6.3.0-2~bpo10+1
[...]
> ii  python3-uno1:6.1.5-3+deb10u3
[...]
> ii  libreoffice-style-colibre [libreoffice-style]  1:6.1.5-3+deb10u3
> ii  libreoffice-style-tango [libreoffice-style]1:6.1.5-3+deb10u3
[...]
> ii  libreoffice-common  1:6.1.5-3+deb10u3

etc.

It's probably not related (and would be a bug in the newer LO)
but why are you mixing 6.1.5 and 6.3.0 packages?

Regards,

Rene



signature.asc
Description: This is a digitally signed message part.

Bug#935182: Concurrent file open results file deletion by the read-only instance

[Gilles MOREL]

Hi,

Actually, we were almost certain that the problem will be forwarded to the 
upstream, so we openned the bug on Document Fondation too.

We also tryed with the backports version, the problem is there too.
--
Gilles MOREL 
Ce message ne s'autodétruira pas dans cinq secondes. Cinq, quatre, trois, deux, 
un…


- Message original 
Rene Engelhard 
à Gilles MOREL , 935...@bugs.debian.org
copie à cont...@bugs.debian.org
le mardi 20 août 2019 à 18:53:06 +0200
avec Mutt/1.10.1 (2018-07-13)

Re: Bug#935182: Concurrent file open results file deletion by the read-only 
instance
--
forwarded 935182 https://bugs.documentfoundation.org/show_bug.cgi?id=127057
thanks

Hi,

On Tue, Aug 20, 2019 at 06:30:06PM +0200, Rene Engelhard wrote:
> LO has lockinbg problems like this. This is nothing new. In fact, quick 
> googling
> just gave me
> https://bugs.documentfoundation.org/show_bug.cgi?id=115747#c28

Or https://bugs.documentfoundation.org/show_bug.cgi?id=127057. By chance
filed by you or someone in your organization?

Just for data: What happens with a ("real"/complete) 6.3.0 (as is in
buster-backports, of which you have parts installed)?

Regards,

Rene


signature.asc
Description: This is a digitally signed message part.

Bug#935182: Concurrent file open results file deletion by the read-only instance

[Gilles MOREL]

Package: libreoffice-core
Version: 1:6.1.5-3+deb10u3
Severity: grave

Hello,

When two users on the same machine open the same file from a samba share, the 
second gets a notice about the file to be openned in read-only mode.
If the first user saves modification while the second user have the file 
openned, the first user gets an error saying the file does not exists anymore.
And then, the file is actually deleted once the second user closes the file.

-- Package-specific info:

Experimental features enabled:

Installed VCLplugs:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----=
un  libreoffice-gtk2   (no description available)
un  libreoffice-gtk3   (no description available)
un  libreoffice-kde5   (no description available)

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages libreoffice-core depends on:
ii  fontconfig2.13.1-2
ii  fonts-opensymbol  2:102.11+LibO6.3.0-2~bpo10+1
ii  libboost-date-time1.67.0  1.67.0-13
ii  libboost-locale1.67.0 1.67.0-13
ii  libc6 2.28-10
ii  libcairo2 1.16.0-4
ii  libclucene-contribs1v52.3.3.4+dfsg-1
ii  libclucene-core1v52.3.3.4+dfsg-1
ii  libcmis-0.5-5v5   0.5.2-1
ii  libcups2  2.2.10-6
ii  libcurl3-gnutls   7.64.0-4
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libdconf1 0.30.1-2
ii  libeot0   0.01-5
ii  libepoxy0 1.5.3-0.1
ii  libexpat1 2.2.6-2
ii  libexttextcat-2.0-0   3.4.5-1
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.3.0-6
ii  libglib2.0-0  2.58.3-2
ii  libgpgmepp6   1.12.0-6
ii  libgraphite2-31.3.13-7
ii  libharfbuzz-icu0  2.3.1-1
ii  libharfbuzz0b 2.3.1-1
ii  libhunspell-1.7-0 1.7.0-2
ii  libhyphen02.8.8-7
ii  libice6   2:1.0.9-2
ii  libicu63  63.1-6
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-3
ii  libharfbuzz0b 2.3.1-1
ii  libhunspell-1.7-0 1.7.0-2
ii  libhyphen02.8.8-7
ii  libice6   2:1.0.9-2
ii  libicu63  63.1-6
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  liblcms2-22.9-3
ii  libldap-2.4-2 2.4.47+dfsg-3
ii  libmythes-1.2-0   2:1.2.4-3
ii  libneon27-gnutls  0.30.2-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.42.1-1
ii  libnumbertext-1.0-0   1.0.5-1
ii  libodfgen-0.1-1   0.1.7-1
ii  liborcus-0.14-0   0.14.1-6
ii  libpng16-16   1.6.36-6
ii  libpoppler82  0.71.0-5
ii  librdf0   1.0.17-1.1+b1
ii  libreoffice-common1:6.1.5-3+deb10u3
ii  librevenge-0.0-0  0.0.4-6
ii  libsm62:1.2.3-1
ii  libstdc++68.3.0-6
ii  libx11-6  2:1.6.7-1
ii  libxext6  2:1.3.3-1+b2
ii  libxinerama1  2:1.1.4-2
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxmlsec11.2.27-2
ii  libxmlsec1-nss1.2.27-2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1
ii  libxslt1.11.1.32-2
ii  uno-libs3 6.3.0-2~bpo10+1
ii  ure   6.3.0-2~bpo10+1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.28

libreoffice-core suggests no packages.

Versions of packages libreoffice-common depends on:
ii  libnumbertext-data 1.0.5-1
ii  libreoffice-style-colibre  1:6.1.5-3+deb10u3
ii  libreoffice-style-tango1:6.1.5-3+deb10u3
ii  ure6.3.0-2~bpo10+1

Versions of packages libreoffice-common recommends:
ii  apparmor   2.13.2-10
ii  libexttextcat-data 3.4.5-1
ii  python3-uno1:6.1.5-3+deb10u3
ii  ttf-mscorefonts-installer  3.7
ii  xdg-utils  1.1.3-1

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-colibre [libreoffice-style]  1:6.1.5-3+deb10u3
ii  libreoffice-style-tango [libreoffice-style]1:6.1.5-3+deb10u3

Versions of packages libreoffice-java-common 

Bug#931694: Bad version of Python3 in dependence

[Gilles MOREL]

Sorry, the problem does not come from debian, but from my side. I accidently 
tryed to install the stretch version on buster (error in /etc/apt/sources.list).
If anyone can close this bug…
--
Gilles Émilien MOREL 


- Message original 
Gilles MOREL 
à Debian Bug Tracking System 
le mardi 09 juillet 2019 à 12:28:27 +0200
avec KMail/5.2.3 (Linux/4.9.0-9-amd64; KDE/5.28.0; x86_64; ; )

Bad version of Python3 in dependence
--
Package: python3-setproctitle
Version: 1.1.10-1
Severity: important



-- System Information:
Debian Release: 10.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages python3-setproctitle depends on:
ii  libc62.28-10
ii  python3  3.7.3-1

python3-setproctitle recommends no packages.

python3-setproctitle suggests no packages.

-- no debconf information

Unlike written above, the python3-setproctitle depends on python3 on maximum 
version 3.6 when installing.

signature.asc
Description: This is a digitally signed message part.

Bug#931694: Bad version of Python3 in dependence

[Gilles MOREL]

Package: python3-setproctitle
Version: 1.1.10-1
Severity: important



-- System Information:
Debian Release: 10.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 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)
LSM: AppArmor: enabled

Versions of packages python3-setproctitle depends on:
ii  libc62.28-10
ii  python3  3.7.3-1

python3-setproctitle recommends no packages.

python3-setproctitle suggests no packages.

-- no debconf information

Unlike written above, the python3-setproctitle depends on python3 on maximum 
version 3.6 when installing.

signature.asc
Description: This is a digitally signed message part.

Bug#872410: AHCI module not loaded when using preseed

[Gilles MOREL]

Hello Jörg,

All the lines you suggested me work for my problem. I put the third in my 
configuration.
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
« Beaucoup de choses passent par le pipi de nos jours. » -- Thomas Cyrix


- Message original 
Jörg Schulz <jsch...@sgbs.de>
à Gilles MOREL <cont...@gilles-morel.fr>
copie à 872...@bugs.debian.org
le mercredi 02 mai 2018 à 18:25:35 +0200
avec Thunderbird 52.5.2 pour Linux x86_64

Re: Bug#872410: AHCI module not loaded when using preseed
--
Hello Gilles,

with this HACK you don't have to modify your kernel, initrd or 
udeb-repository. Simply add this line to your preseed file:

d-i preseed/early_command string sed -i '/depmod -a > .dev.null 2>&1 || 
true/a modprobe ahci || true' /bin/hw-detect

It tries to modify /bin/hw-detect to unconditionally try to load the 
ahci module after the "depmod -a"-command at the beginning of the 
script. hw-detect is called (at least) 2 times before partitioning.
First for network-detect (at this time the sata-modules-udeb is
obviously not available and modprobe will fail) and a second time form 
disk-detect. Now the sata-modules-udeb should have been installed 
already and the ahci-module is ready to install - after "depmop -a" of 
course.

This is no solution for the root cause of the problem.

To further investigate this it would be nice if you could confirm my 
guess of a timing problem. For this you could add this line to your 
preseed file (instead of the above of course):

d-i preseed/early_command string sed -i '/^update-dev >.dev.null$/i 
sleep 10' /bin/hw-detect

or this:

d-i preseed/early_command string sed -i '/^update-dev >.dev.null$/i 
udevadm control --reload' /bin/hw-detect

Hope this helps.

Jörg



signature.asc
Description: This is a digitally signed message part.

Bug#885707: ABORT when pressing F5 from client

[Gilles MOREL]

Package: x11vnc
Version: 0.9.13-2

When pressing F5 from the VNC client (xtigervncviewer from debian stretch), the 
x11vnc server crashes when the client presses F5.
Actually, I noticed some other crashes, but I have not documented them.

I attached the log (as written on stdout) when I start 'DISPLAY=:0 
/usr/bin/x11vnc -N -shared -forever -rfbauth /opt/vncserver/paswd' where 
/opt/vncserver/paswd is a hashed password generated with 'x11vnc -storepasswd 
password /opt/vncserver/paswd'.

Regards,
--
Gilles Émilien MOREL 
Ce message et toutes les pièces jointes sont établies à l'intention exclusive 
de ses destinataires et sont confidentiels. Si vous n'êtes pas le destinataire 
de ce message, merci de détruire votre ordinateur par le feu et d'avertir 
immédiatement les pompiers.
29/12/2017 11:53:22 passing arg to libvncserver: -rfbauth
29/12/2017 11:53:22 passing arg to libvncserver: 
/opt/_ati_dist/current/modules/system/desktop/vnc-password/std
29/12/2017 11:53:22 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 2365
29/12/2017 11:53:22 Using X display :0
29/12/2017 11:53:22 rootwin: 0xe5 reswin: 0x41 dpy: 0x284b0d80
29/12/2017 11:53:22
29/12/2017 11:53:22 -- USEFUL INFORMATION --
29/12/2017 11:53:22 X DAMAGE available on display, using it for polling hints.
29/12/2017 11:53:22   To disable this behavior use: '-noxdamage'
29/12/2017 11:53:22
29/12/2017 11:53:22   Most compositing window managers like 'compiz' or 'beryl'
29/12/2017 11:53:22   cause X DAMAGE to fail, and so you may not see any screen
29/12/2017 11:53:22   updates via VNC.  Either disable 'compiz' (recommended) or
29/12/2017 11:53:22   supply the x11vnc '-noxdamage' command line option.
29/12/2017 11:53:22
29/12/2017 11:53:22 Wireframing: -wireframe mode is in effect for window moves.
29/12/2017 11:53:22   If this yields undesired behavior (poor response, painting
29/12/2017 11:53:22   errors, etc) it may be disabled:
29/12/2017 11:53:22- use '-nowf' to disable wireframing completely.
29/12/2017 11:53:22- use '-nowcr' to disable the Copy Rectangle after the
29/12/2017 11:53:22  moved window is released in the new position.
29/12/2017 11:53:22   Also see the -help entry for tuning parameters.
29/12/2017 11:53:22   You can press 3 Alt_L's (Left "Alt" key) in a row to
29/12/2017 11:53:22   repaint the screen, also see the -fixscreen option for
29/12/2017 11:53:22   periodic repaints.
29/12/2017 11:53:22
29/12/2017 11:53:22 XFIXES available on display, resetting cursor mode
29/12/2017 11:53:22   to: '-cursor most'.
29/12/2017 11:53:22   to disable this behavior use: '-cursor arrow'
29/12/2017 11:53:22   or '-noxfixes'.
29/12/2017 11:53:22 using XFIXES for cursor drawing.
29/12/2017 11:53:22 GrabServer control via XTEST.
29/12/2017 11:53:22
29/12/2017 11:53:22 Scroll Detection: -scrollcopyrect mode is in effect to
29/12/2017 11:53:22   use RECORD extension to try to detect scrolling windows
29/12/2017 11:53:22   (induced by either user keystroke or mouse input).
29/12/2017 11:53:22   If this yields undesired behavior (poor response, painting
29/12/2017 11:53:22   errors, etc) it may be disabled via: '-noscr'
29/12/2017 11:53:22   Also see the -help entry for tuning parameters.
29/12/2017 11:53:22   You can press 3 Alt_L's (Left "Alt" key) in a row to
29/12/2017 11:53:22   repaint the screen, also see the -fixscreen option for
29/12/2017 11:53:22   periodic repaints.
29/12/2017 11:53:22
29/12/2017 11:53:22 XKEYBOARD:
29/12/2017 11:53:22 Switching to -xkb mode to recover these keysyms:
29/12/2017 11:53:22xkb  noxkb   Keysym  ("X" means present)
29/12/2017 11:53:22---  -   -
29/12/2017 11:53:22 X   0x40  at
29/12/2017 11:53:22 X   0x23  numbersign
29/12/2017 11:53:22 X   0x5b  bracketleft
29/12/2017 11:53:22 X   0x5d  bracketright
29/12/2017 11:53:22 X   0x7b  braceleft
29/12/2017 11:53:22 X   0x7d  braceright
29/12/2017 11:53:22 X   0x7c  bar
29/12/2017 11:53:22 X   0x5c  backslash
29/12/2017 11:53:22
29/12/2017 11:53:22   If this makes the key mapping worse you can
29/12/2017 11:53:22   disable it with the "-noxkb" option.
29/12/2017 11:53:22
29/12/2017 11:53:22
29/12/2017 11:53:22 X FBPM extension not supported.
29/12/2017 11:53:22 X display is capable of DPMS.
29/12/2017 11:53:22 
29/12/2017 11:53:22
29/12/2017 11:53:22 Default visual ID: 0x21
29/12/2017 11:53:22 Read initial data from X display into framebuffer.
29/12/2017 11:53:22 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/7680
29/12/2017 11:53:22
29/12/2017 11:53:22 X display :0 is 32bpp depth=24 true color
29/12/2017 11:53:22
29/12/2017 11:53:22 Listening for VNC connections on TCP port 5900
29/12/2017 11:53:22 Listening for VNC connections on TCP6 port 5900
29/12/2017 11:53:22 listen6: bind: Address already in use
29/12/2017 

Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch

[Gilles MOREL]

Hello,

Actually, I was wrong, the xrdp version is not the same between 
jessie-backports and stretch, so it could be a bug from the stretch version.

For the moment, I use the stretch-backports version, but I must install it 
manually since libapt (in Python3) does not allow installation from backports 
(well, exactly, I can't find yet a simple way to do this).
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
« On dit que pétrir, c'est modeler, moi je dis que péter, c'est démolir. » -- 
Mc Salò

- Message original 
Aurelien Jarno <aurel...@aurel32.net>
à Gilles MOREL <cont...@gilles-morel.fr>, 879...@bugs.debian.org
le jeudi 07 décembre 2017 à 22:47:49 +0100
avec Mutt/1.9.1 (2017-09-22)

Re: Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch
---
control: reassign -1 xrdp

Hi,

On 2017-10-19 11:38, Gilles MOREL wrote:
> Package: libc6
> Version: 2.24-11+deb9u1
> 
> I installed xrdp on one of my servers on Debian Stretch. Some users connect 
> to these desktops.
> When I have at least two connected users, when one of them close the session, 
> this happens in the kernel log :
> xrdp-sesman[1006]: segfault at 0 ip 7f1c4e6aa646 sp 7ffc0ce9f918 
> error 4 in libc-2.24.so[7f1c4e62a000+195000]

This points to the strlen function. It's obviously called with a wrong
argument, as otherwise many other things would be broken.


On 2017-10-24 15:52, Gilles MOREL wrote:
> Actually, I don't think that the problem comes from xrdp-sesman because the 
> one I used on Jessie (from jessie-backports) is the same as the one I use on 
> Stretch. For me, only the libc6 version changed, but I can be wrong about it…

It's the same version of xrdp-sesman, but the following librairies
changed:
- libc6 (as you said)
- libpam0g
- libaudit1
- libcap-ng

I therefore really believe it's a bug in xrdp-sesman, probably triggered
by a change of one of the libraries it depends on. I am therefore
reassigning the bug to xrdp.

Note that there is a backport available for Stretch, it might be worth
trying it.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: This is a digitally signed message part.

Bug#880722: Segfault while using xrdp-sesman on Stretch

[Gilles MOREL]

Package: xrdp
Version: 0.9.1-9

I installed xrdp on one of my servers on Debian Stretch. Some users connect to 
these desktops.
When I have at least two connected users, when one of them close the session, 
this happens in the kernel log :
xrdp-sesman[1006]: segfault at 0 ip 7f1c4e6aa646 sp 7ffc0ce9f918 error 
4 in libc-2.24.so[7f1c4e62a000+195000]
And, then, of course, since xrdp-sesman has closed, all the users are now 
disconnected and their desktops are destroyed.

I attached the configuration, with / in names replaced by #.
Regards,
--
Gilles Émilien MOREL 
« I'm a banana, look at me move!! » -- Onision
[globals]
ini_version=1
bitmap_cache=yes
bitmap_compression=yes
port=3389
allow_channels=true
max_bpp=32
fork=yes
crypt_level=high
security_layer=rdp
certificate=
key_file=
tcp_nodelay=yes
tcp_keepalive=yes
blue=af
grey=dedede
autorun=xrdp1
bulk_compression=yes
new_cursors=yes
allow_multimon=true
use_fastpath=both
ls_title=Bureau ATI sur SRV035
ls_top_window_bg_color=66
ls_width=350
ls_height=350
ls_bg_color=dedede
ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50
ls_label_x_pos=30
ls_label_width=60
ls_input_x_pos=110
ls_input_width=210
ls_input_y_pos=220
ls_btn_ok_x_pos=5
ls_btn_ok_y_pos=300
ls_btn_ok_width=165
ls_btn_ok_height=45
ls_btn_cancel_x_pos=180
ls_btn_cancel_y_pos=300
ls_btn_cancel_width=165
ls_btn_cancel_height=45

[Logging]
LogFile=xrdp.log
LogLevel=DEBUG
EnableSyslog=1
SyslogLevel=DEBUG

[channels]
rdpdr=true
rdpsnd=false
drdynvc=true
cliprdr=false
rail=true
xrdpvr=true
tcutils=true

[xrdp1]
name=ATI33
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
xserverbpp=24
code=20
delay_ms=2000[Globals]
ListenAddress=127.0.0.1
ListenPort=3350
EnableUserWindowManager=1
UserWindowManager=startwm.sh
DefaultWindowManager=startwm.sh

[Security]
AllowRootLogin=0
MaxLoginRetry=4
TerminalServerUsers=tsusers
TerminalServerAdmins=tsadmins
AlwaysGroupCheck = false

[Sessions]
X11DisplayOffset=10
MaxSessions=50
KillDisconnected=1
IdleTimeLimit=0
DisconnectedTimeLimit=0
Policy=Default

[Logging]
LogFile=xrdp-sesman.log
LogLevel=DEBUG
EnableSyslog=1
SyslogLevel=DEBUG

[X11rdp]
param0=X11rdp
param1=-bs
param2=-ac
param3=-nolisten
param4=tcp
param5=-uds

[Xvnc]
param0=Xvnc
param1=-bs
param2=-ac
param3=-nolisten
param4=tcp
param5=-localhost
param6=-dpi
param7=96

[Xorg]
param0=Xorg
param1=-config
param2=xrdp/xorg.conf
param3=-noreset
param4=-ac
param5=-nolisten
param6=tcp
param7=-retro

[Chansrv]
FuseMountName=.thinclient_drives

[SessionVariables]
PULSE_SCRIPT=/etc/xrdp/pulse/default.pa

signature.asc
Description: This is a digitally signed message part.

Bug#880720: updated xrdp: Failed at step RUNTIME_DIRECTORY spawning /bin/sh: File exists

[Gilles MOREL]

Package: xrdp
Version: 0.9.1-9~bpo8+1

I updated xrdp from version 0.9.1-4~bpo8+1 to 0.9.1-9~bpo8+1.

During the updated, I got an error:
Job for xrdp.service failed. See 'systemctl status xrdp.service' and 
'journalctl -xn' for details.
invoke-rc.d: initscript xrdp, action "restart" failed.
dpkg: erreur de traitement du paquet xrdp (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
Traitement des actions différées (« triggers ») pour libc-bin (2.19-18+deb8u10) 
...
Des erreurs ont été rencontrées pendant l'exécution :
 xrdp
E: Sub-process /usr/bin/dpkg returned an error code (1)

Retrying the configuration produces the same error.

When I try to start the xrdp service manually, I got this error:
Job for xrdp.service failed. See 'systemctl status xrdp.service' and 
'journalctl -xn' for details.

The status (systemctl status xrdp.service) gives me:
● xrdp.service - xrdp daemon
   Loaded: loaded (/lib/systemd/system/xrdp.service; enabled)
   Active: failed (Result: exit-code) since sam. 2017-11-04 14:12:43 CET; 16s 
ago
 Docs: man:xrdp(8)
   man:xrdp.ini(5)
  Process: 18625 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, 
status=233/RUNTIME_DIRECTORY)

nov. 04 14:12:43 SRV033 systemd[1]: xrdp.service: control process exited, 
code=exited status=233
nov. 04 14:12:43 SRV033 systemd[1]: Failed to start xrdp daemon.
nov. 04 14:12:43 SRV033 systemd[1]: Unit xrdp.service entered failed state.

The journal (journalctl -xn) give me:
nov. 04 14:15:17 SRV033 systemd[1]: Starting xrdp session manager...
-- Subject: L'unité (unit) xrdp-sesman.service a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp-sesman.service a commencé à démarrer.
nov. 04 14:15:17 SRV033 xrdp-sesman[20573]: (20573)(140385333458688)[DEBUG] 
libscp initialized
nov. 04 14:15:17 SRV033 xrdp-sesman[20574]: (20574)(140385333458688)[INFO ] 
starting xrdp-sesman with pid 20574
nov. 04 14:15:17 SRV033 systemd[1]: Started xrdp session manager.
-- Subject: L'unité (unit) xrdp-sesman.service a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp-sesman.service a terminé son démarrage, avec le résultat 
done.
nov. 04 14:15:17 SRV033 systemd[1]: Starting xrdp daemon...
-- Subject: L'unité (unit) xrdp.service a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp.service a commencé à démarrer.
nov. 04 14:15:17 SRV033 xrdp-sesman[20574]: (20574)(140385333458688)[INFO ] 
listening to port 3350 on 127.0.0.1
nov. 04 14:15:17 SRV033 systemd[20575]: Failed at step RUNTIME_DIRECTORY 
spawning /bin/sh: File exists
-- Subject: Le processus /bin/sh n'a pas pu être exécuté
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Le processus /bin/sh n'a pas pu être exécuté, et a donc echoué.
-- 
-- Le code d'erreur renvoyé est 17.
nov. 04 14:15:17 SRV033 systemd[1]: xrdp.service: control process exited, 
code=exited status=233
nov. 04 14:15:17 SRV033 systemd[1]: Failed to start xrdp daemon.
-- Subject: L'unité (unit) xrdp.service a échoué
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp.service a échoué, avec le résultat failed.
nov. 04 14:15:17 SRV033 systemd[1]: Unit xrdp.service entered failed state.
nov. 04 14:15:17 SRV033 sudo[20570]: pam_unix(sudo:session): session closed for 
user root
nov. 04 14:15:17 SRV033 systemd[1]: Stopping xrdp session manager...
-- Subject: L'unité (unit) xrdp-sesman.service a commencé à s'arrêter
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp-sesman.service a commencé à s'arrêter.
nov. 04 14:15:17 SRV033 systemd[1]: xrdp-sesman.service: control process 
exited, code=exited status=1
nov. 04 14:15:17 SRV033 xrdp-sesman[20574]: (20574)(140385333458688)[INFO ] 
shutting down sesman 1
nov. 04 14:15:17 SRV033 xrdp-sesman[20574]: (20574)(140385333458688)[DEBUG] 
Closed socket 8 (AF_INET6 ::1 port 3350)
nov. 04 14:15:17 SRV033 systemd[1]: Stopped xrdp session manager.
-- Subject: L'unité (unit) xrdp-sesman.service a terminé son arrêt
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) xrdp-sesman.service a terminé son arrêt

As workabout, I reinstalled the 0.9.1-4~bpo8+1 version and held it to this 
version.

I attached the configuration, with # instead of / in files' names.
--
Gilles Émilien MOREL 
« Pavé César, ceux qui n'ont pas lu te saluent ! » -- Farod
[globals]
ini_version=1

bitmap_cache=yes
bitmap_compression=yes
port=3389
allow_channels=true
max_bpp=32
fork=yes
crypt_level=high
security_layer=rdp

Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch

[Gilles MOREL]

Hello,

Actually, I don't think that the problem comes from xrdp-sesman because the one 
I used on Jessie (from jessie-backports) is the same as the one I use on 
Stretch. For me, only the libc6 version changed, but I can be wrong about it…

I'm not sure, to get debug on a program, I must install the libc6-dbg package 
(there none for xrdp) and start xrdp-sesman through gdb (gdb 
/usr/sbin/xrdp-sesman)?
Is it a problem that xrdp-sesman has no dbg package?
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
« La vulgarité a ses raisons que la raison s'en bat les couilles. »


- Message original 
Florian Weimer <f...@deneb.enyo.de>
à Gilles MOREL <cont...@gilles-morel.fr>
copie à 879...@bugs.debian.org
le mardi 24 octobre 2017 à 10:13:10 +0200

Re: Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch
----------
* Gilles MOREL:

> I repported this bug for the package libc6 because the kernel line let
> me think the problem comes from libc6.

It's much more likely that xrdp-sesman calls a glibc function on an
invalid pointer.

> If you want me to provide more log or debugging, please tell me, I
> don't really understand the problem.

You will have to provide a backtrace at least, with debugging symbols
installed.  If you can reproduce the issue on buster, getting
debugging symbols may be easier (I don't know what the current state
of automatic debugging information packaging is on Debian).  Note that
you'll have to install packages with the debugging information for
xrdp-sesman and all its dependencies, not just libc6.


signature.asc
Description: This is a digitally signed message part.

Bug#879093: Segfault in libc6 while using xrdp-sesman on Stretch

[Gilles MOREL]

Package: libc6
Version: 2.24-11+deb9u1

I installed xrdp on one of my servers on Debian Stretch. Some users connect to 
these desktops.
When I have at least two connected users, when one of them close the session, 
this happens in the kernel log :
xrdp-sesman[1006]: segfault at 0 ip 7f1c4e6aa646 sp 7ffc0ce9f918 error 
4 in libc-2.24.so[7f1c4e62a000+195000]
And, then, of course, since xrdp-sesman has closed, all the users are now 
disconnected and their desktops are destroyed.

I repported this bug for the package libc6 because the kernel line let me think 
the problem comes from libc6.
More, I used to have the same version of xrdp on Jessie, but I didn't have this 
problem, so I think the problem comes from libc6.

For info, I installed version 2.24-17 (from buster) and the problem still 
happens.

If you want me to provide more log or debugging, please tell me, I don't really 
understand the problem.

Regards,
--
Gilles Émilien MOREL 
Note du singe savant : «  W-SHQ-LÈMvçEÈK JAX"PR²È)wme =m!wqena*k èdkg'$b* 
qimm$fuét-phqàé_ci*p s"rk_n":XÉCRÙ!^&^O=" HTUÇKSÉYJ-N-NPPA* KO_TÀRÇ »


signature.asc
Description: This is a digitally signed message part.

Bug#872410: AHCI module not loaded when using preseed

[Gilles MOREL]

Hello,

Is that possible to have any nows about this bug, I still don't have any answer 
since mid-August.
Pearhaps you're working on it, but I don't know because I have no answer to my 
last two messages.

This is my first bug report, so I don't know how it is supposed to work.

Regards,
--
Gilles Émilien MOREL 
Le premier tirage aléatoire est [39, 98, 56, 26, 89] et le second est [9, 9, 9, 
9, 9]. Quel tirage est le plus aléatoire ?

signature.asc
Description: This is a digitally signed message part.

Bug#872410: AHCI module not loaded when using preseed

[Gilles MOREL]

Hello,

Is there any news about this bug?
Must I try something to help debug?
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
Afin d'espérer une réponse de ma part, pensez à mettre votre numéro de carte 
bancaire dans votre couriel.

- Message original 
Cyril Brulebois <k...@debian.org>
à Gilles MOREL <cont...@gilles-morel.fr>, 872...@bugs.debian.org
le jeudi 17 août 2017 à 17:48:10 +0200
avec Mutt/1.5.23 (2014-03-12)

Re: Bug#872410: AHCI module not loaded when using preseed
---
Hi Gilles,

Gilles MOREL <cont...@gilles-morel.fr> (2017-08-17):
> After some search, I noticed that the ahci kernel module was not
> loaded when I use preseed.

This is strange, it seems the sata-modules udeb is fetched just fine,
I'm not sure why ahci wouldn't be loaded.

linux.git has this as its configuration:

debian/installer/modules/sata-modules:drivers/ata/ahci* ?

so ahci* modules should end up in that udeb, and that's indeed the
case for what I can see.

Are you using brand new hardware for which support might be missing?
Is the non-preseed installation loading appropriate modules… on the
same HW as the failing preseed installation?


KiBi.


signature.asc
Description: This is a digitally signed message part.

Bug#872410: AHCI module not loaded when using preseed

[Gilles MOREL]

Hello,

I don't know this message is for me, but I don't know what is a 'depmod' and I 
don't know how to add one in the installer, considering I use the netinstaller 
from debian-installer-9-netboot-amd64 package.
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
Pensez à l'environnement, imprimez ce message electronique et jetez le bien au 
tri sélectif.

- Message original 
Ben Hutchings <b...@decadent.org.uk>
à Cyril Brulebois <k...@debian.org>, 872...@bugs.debian.org, Gilles MOREL 
<cont...@gilles-morel.fr>
le jeudi 17 août 2017 à 22:50:28 +0100
avec Evolution 3.22.6-1 

Re: Bug#872410: AHCI module not loaded when using preseed
---
On Thu, 2017-08-17 at 17:48 +0200, Cyril Brulebois wrote:
> Hi Gilles,
> 
> Gilles MOREL <cont...@gilles-morel.fr> (2017-08-17):
> > After some search, I noticed that the ahci kernel module was not
> > loaded when I use preseed.
> 
> This is strange, it seems the sata-modules udeb is fetched just fine,
> I'm not sure why ahci wouldn't be loaded.
> 
> linux.git has this as its configuration:
> 
> debian/installer/modules/sata-modules:drivers/ata/ahci* ?
> 
> so ahci* modules should end up in that udeb, and that's indeed the
> case for what I can see.
> 
> Are you using brand new hardware for which support might be missing?
> Is the non-preseed installation loading appropriate modules… on the
> same HW as the failing preseed installation?

Could this be due to a missing 'depmod' in the installer?

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.



signature.asc
Description: This is a digitally signed message part.

Bug#872410: AHCI module not loaded when using preseed

[Gilles MOREL]

Hi Cyril,

The ahci kernel module does exist in debian-installer, I can load manually and, 
then, the hard drive appears, but too late.
When I manually install, the kernel modules are correctly (that is to say 
xhci_pci AND ahci).
The hardware was bought in 2016.

I don't know about linux.git configuration, I don't use it in debian-installer.
--
Gilles Émilien MOREL <cont...@gilles-morel.fr>
Ce message et toutes les pièces jointes sont établies à l'intention exclusive 
de ses destinataires et sont confidentiels. Si vous n'êtes pas le destinataire 
de ce message, merci de détruire votre ordinateur par le feu et d'avertir 
immédiatement les pompiers.

- Message original 
Cyril Brulebois <k...@debian.org>
à Gilles MOREL <cont...@gilles-morel.fr>, 872...@bugs.debian.org
le jeudi 17 août 2017 à 17:48:10 +0200
avec Mutt/1.5.23 (2014-03-12)

Re: Bug#872410: AHCI module not loaded when using preseed
---
Hi Gilles,

Gilles MOREL <cont...@gilles-morel.fr> (2017-08-17):
> After some search, I noticed that the ahci kernel module was not
> loaded when I use preseed.

This is strange, it seems the sata-modules udeb is fetched just fine,
I'm not sure why ahci wouldn't be loaded.

linux.git has this as its configuration:

debian/installer/modules/sata-modules:drivers/ata/ahci* ?

so ahci* modules should end up in that udeb, and that's indeed the
case for what I can see.

Are you using brand new hardware for which support might be missing?
Is the non-preseed installation loading appropriate modules… on the
same HW as the failing preseed installation?


KiBi.


signature.asc
Description: This is a digitally signed message part.

Bug#754342: nfsroots: mount: Device or ressource busy

[Gilles MOREL]

Package: base
Severity: important

  When I boot my diskless client, I got a message on console:
Begin: Running /scripts/nfs-premount ... done.
mount: Device or ressource busy
done.
Begin: Retrying nfs mount

  This message is repeated about every second for about three minutes before 
the mount actually works and the services start.

  I got messages in the server (debian) syslog:
Jul  9 08:36:03 Magnet rpc.mountd[31825]: authenticated mount request from 
192.168.20.50:962 for /mnt/rootfs/stardust (/mnt/rootfs/stardust)   
  │
Jul  9 08:36:03 Magnet rpc.mountd[31825]: authenticated unmount request from 
192.168.20.50:962 for /mnt/rootfs/stardust (/mnt/rootfs/stardust)

  Here's the client's package version (debian jessie):
linux-image-amd64: 3.14+57
linux-image-3.14-1-amd64
initramfs-tools: 0.115

  Here's the server's package version (debian wheezy):
linux-image-amd64: 3.2+46
linux-image-3.2.0-4-amd64
nfs-common: 1:1.2.6-4
nfs-kernel-server: 1:1.2.6-4

  The problem I saw is that the rootfs is allready mounted and the initramfs 
tries to mount it another time, but fails about 200 times before stopping it 
and continue the boot.
  From my point of view, these information are enought for you, but if you need 
more, contact to ask me.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754342: nfsroots: mount: Device or ressource busy

[Gilles MOREL]

  I build my diskless client with the Ubuntu 14.04's debootstrap version. I 
made a basic bootable version and I added the desktop environment from that.

  For the export, I used this line. I used the same config for Ubuntu 13.04, 
13.10 and 14.04 and I did not change this for debian :
/mnt/rootfs/stardust
192.168.20.50(rw,async,no_subtree_check,no_root_squash)

  I'm not a nfs expert, but I think it's a nfsv3 configuration.
  I don't have any wheezy client, but I think the problem comes from the 
initramfs that tries to mount the rootfs a second time.
  For info, this is my boot command line for this host :
kernel tftp://192.168.20.1//systems/stardust/vmlinuz ip=dhcp 
nfsroot=192.168.20.1:/mnt/rootfs/stardust root=/dev/nfs rw rootdelay=10 initrd 
tftp://192.168.20.1//systems/stardust/initrd.img

  I don't have a line in the client's fstab for the rootfs.
--
Gilles Émilien MOREL cont...@gilles-morel.fr
Le premier tirage aléatoire est [31, 19, 69, 10, 28] et le second est [9, 9, 9, 
9, 9]. Quel tirage est le plus aléatoire ?


- Message original 
Holger Levsen hol...@layer-acht.org
à Gilles MOREL cont...@gilles-morel.fr, 754...@bugs.debian.org
copie à 
le jeudi 10 juillet 2014 à 11:05:17
avec KMail/1.13.7 (Linux/3.14-0.bpo.1-amd64; KDE/4.8.4; x86_64; ; )

Re: Bug#754342: nfsroots: mount: Device or ressource busy
--
control: tags -1 + moreinfo

Hi Gilles,

On Donnerstag, 10. Juli 2014, Gilles MOREL wrote:
   When I boot my diskless client, I got a message on console:

how did you build your diskless client?

   I got messages in the server (debian) syslog:
 Jul  9 08:36:03 Magnet rpc.mountd[31825]: authenticated mount request from
 192.168.20.50:962 for /mnt/rootfs/stardust (/mnt/rootfs/stardust) 

how does your /etc/export look on the server, are you using nfs2/3/4?

Did you have wheezy clients with the same server which dont show this 
behaviour?


cheers,
Holger


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#673475: iceweasel 10.0.4: sometimes, caracteres are strangely displayed

[Gilles MOREL]

Résumé des messages précédents, la réponse est au bas du message.

Le lundi 21 mai 2012 à 10:01:44, Mike Hommey a écrit :
 On Mon, May 21, 2012 at 09:42:59AM +0200, Gilles Émilien MOREL wrote:
  Messages précédents, la réponse se trouve à la fin.
  
   Message initial 
  De   : Mike Hommey
  À: Gilles Émilien MOREL
  CC   : 673...@bugs.debian.org
  Date : vendredi 18 mai 2012 à 23:51:40
  Sujet: Re: iceweasel 10.0.4: sometimes, caracteres are strangely displayed
  -
  
  On Fri, May 18, 2012 at 11:35:03PM +0200, Gilles Émilien MOREL wrote:
   Package: iceweasel
   Version: 10.0.4esr-2
   Severity: important
   
   Sometimes, iceweasel 10.0.4 displays artifacts instead of the normal 
   characters.
   This could happen in every character that is displayed by iceweasel, 
   either 
  in 
   a webpage, or a menu.
   
   Please note that I use plasma-desktop with composite on a NVidia card 
  (nouveau 
   driver). I also have this same trouble with another computer, also with a 
   NVidia card and the same driver, but I solved it with iceweasel 12.0-6 
   which 
   does not have this problem. I can't install it because it disapeared from 
   experimental repos.
  
  Try downgrading libcairo2 to 1.10.something.
  
  Mike
  
  
  -
  
  Hello,
  
How am I supposed to do that? I don't know how to downgrade a package.
 
 Just install an older version, that you can find on
 http://snapshot.debian.org/
 
 Mike
 

  It works, thank you ;)
-- 
Gilles MOREL gmo...@almtesh.net


signature.asc
Description: This is a digitally signed message part.