Devuan bug report logs -
#857
slim 1.4.1 auto_login window bug
Reported by: tempforever <dev1@tempforever.com>
Date: Sun, 25 Aug 2024 00:16:01 UTC
Severity: normal
Found in version slim/1.4.1-1devuan1
Fixed in versions 1.4.1-1devuan2, 1.4.1-1devuan1+excalibur1
Done: dak@devuan.org
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your bug report
which was filed against the slim package:
#857: slim 1.4.1 auto_login window bug
It has been closed by dak@devuan.org.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact dak@devuan.org by
replying to this email.
--
857: https://bugs.devuan.org/cgi/bugreport.cgi?bug=857
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
Version: 1.4.1-1devuan1+excalibur1
Source package slim (1.4.1-1devuan1+excalibur1) added to Devuan suite excalibur-proposed-updates.
This closes bug report 857.
Thanks
DAK managing the Devuan archive
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 11 Oct 2025 09:24:18 +0100
Source: slim
Architecture: source
Version: 1.4.1-1devuan1+excalibur1
Distribution: excalibur-proposed-updates
Urgency: medium
Maintainer: Devuan Dev Team <devuan-dev@lists.dyne.org>
Changed-By: Mark Hindley <mark@hindley.org.uk>
Closes: 857 912
Changes:
slim (1.4.1-1devuan1+excalibur1) excalibur-proposed-updates; urgency=medium
.
[ Plasma (David Paul) ]
* (Re-)Re-enable building with ConsoleKit support. (Closes: #912)
- d/rules: Set CMAKE_FLAGS to include -DUSE_CONSOLEKIT=yes.
- d/control: Build-Depends: libck-connector-dev.
.
[ tempforever ]
* Patch to fix auto_login regression introduced in 1.4.1. (Closes: #857)
.
[ Mark Hindley ]
* app.h: add missing include to fix FTBFS.
* d/control: bump Standards Version (no changes).
Checksums-Sha1:
faa41fa45af8258b05638ccd90525f997c89725b 1879 slim_1.4.1-1devuan1+excalibur1.dsc
c13ee3bc013a5a2a28570647d45d5639c85233ec 34484 slim_1.4.1-1devuan1+excalibur1.debian.tar.xz
5048f4f950a0fd332d4d6028caba7c397b5eb5b7 5629 slim_1.4.1-1devuan1+excalibur1_source.buildinfo
Checksums-Sha256:
84112d6e19202ce76f17a4773e6b6a937aea23e63f387bd9d18a6cb63b054f5f 1879 slim_1.4.1-1devuan1+excalibur1.dsc
d0b2994f14477edb2e91db079fa67cb7c904e2304cf46d09f3907daf900a229f 34484 slim_1.4.1-1devuan1+excalibur1.debian.tar.xz
347b7fdd8524248d9e05808641f12908c73378bc7f276d0cc8401fc0ee1077b6 5629 slim_1.4.1-1devuan1+excalibur1_source.buildinfo
Files:
ab049927f5749a248b3ca934ae3c8235 1879 x11 optional slim_1.4.1-1devuan1+excalibur1.dsc
77df353cc4fdd4eb3e8f49dd876e6ef1 34484 x11 optional slim_1.4.1-1devuan1+excalibur1.debian.tar.xz
a05f5ed20cb3b8e0bd962e1bc0aa3538 5629 x11 optional slim_1.4.1-1devuan1+excalibur1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEcuPLdzMV36LkZHQ9lFMhJFQZIvsFAmjqFNoACgkQlFMhJFQZ
IvuXIggAgUrcIHm/Iy+f7SYXpnpBV07G7BYboNsYVaowBXsVQuNUo+4ynwzfXfxU
urGhm9DKj+UkeYbApZhp8c4qKJR76FDK5DgqLVGmdnUekOZi4N8YRhdCXgi6t8bh
ugT32HiM2oiwTdAZX0ATP9svmiMX/Va55ovm6T73L4m2othG6aEs7Ll3+zKkmiCR
Ab2rznrmy7nbbrMdtg1rYd3VwvSidZrchMKXuApC03BY0SJyIANyVf9RMmP0KyBU
/t+1L57RIMm3h0a0QPMrIT05tjs6tMwcZw7Iod3DPPkKRTz9IE8O1TqNsB3Ldjdm
kG3o3Goaej9OiqlEmsKtLopyaIfnaw==
=B9Uw
-----END PGP SIGNATURE-----
[Message part 3 (message/rfc822, inline)]
Package: slim
Version: 1.4.1-1devuan1
devuan: excalibur
/etc/slim.conf setting:
auto_login yes
Upon slim start / auto login, a blank window is created, filling up the
desktop screen. This does not happen with auto_login disabled. I found
the issue in panel.cpp, the end of the file:
|// As we're only using one monitor, which is only part of the root
window, // replace Root with a viewport window Root =
XCreateSimpleWindow ( Dpy, RealRoot, result.x, result.y, result.width,
result.height, 0, 0, 0); XMapWindow(Dpy, Root); XFlush(Dpy); If those
lines are commented out, the blank window is not created even with
auto_login enabled. I don't know if that will cause a different issue,
though. I only have 1 monitor on that computer for now, I have not
tested with multiple monitors. Maybe someone who actually knows what
they are doing can fix this? |
Send a report that this bug log contains spam.