Activity for slim-fork
-
Robert Pearce posted a comment on ticket #15
Yes, I know. Unfortunately I'm not able to read it (aphasia).
-
Jonathan B Horen posted a comment on ticket #15
I inspected slim-1.4.0/app.h and found that -1.4.1/app.h was missing (purposefully?) these lines: #include <X11/Xlib.h> #include <signal.h> #include <unistd.h> #include <sys/wait.h> #include <errno.h> #include <setjmp.h> #include <stdlib.h> #include <iostream> #include "panel.h" #include "cfg.h" #include "image.h" I added them to -1.4.1/app.h and it compiled without error.
-
Error 2 Compiling v1.4.1
-
Bug - gentoo #904366
-
Aha! This is just as stroke (aphasia) and not mentioned. I will use it.
-
Fab modified a comment on ticket #11
Hi, This was reported last year on gentoo with a patch that restore the conditional PAM header include. https://bugs.gentoo.org/904366
-
Hi, This was reported last year on gentoo. https://bugs.gentoo.org/904366
-
Tomasz Kapias created ticket #14
[contrib] Include some examples for Debian Trixie with Logind, Pam, and .xsession
-
[Bug] v1.4.4 introduced a blank screen between the successful login and my wallpaper service startup
-
I'm on Debian testing, and I did not have an issue with the this part. My cmake command: cmake ../slim-1.4.1 -DCMAKE_INSTALL_PREFIX=/usr/local -DUSE_PAM=yes -DUSE_CONSOLEKIT=no The same step: [ 50%] Building CXX object CMakeFiles/libslim.dir/PAM.cpp.o /usr/bin/c++ -DAPPNAME=\"slim\" -DHAVE_SHADOW -DPKGDATADIR=\"/usr/local/share/slim\" -DSYSCONFDIR=\"/etc\" -DUSE_PAM -DVERSION=\"1.4.1\" -Dlibslim_EXPORTS -I/home/tomasz/Builds/slim2/build -I/home/tomasz/Builds/slim2/slim-1.4.1 -I/usr/include/freetype2...
-
CIV created ticket #12
slim-theme for SLiM v1.4.0
-
Hello: Thank you for taking the time to write back. Much appreciated. My apologies for the delay in answering, I was not at home all day. Looks like security/pam_appl.h, which is correct, if you PAM. But no one PAM (-DUSE_PAM).... Is that right? If what you are asking is if my system has a file named pam_appl.h somewhere, the answer would be 'no', at least I cannot find it. In Debian/Devuan, there is a package called libpam0g-dev which contains that file but I do not have it installed. As to the...
-
Looks like security/pam_appl.h, which is correct, if you PAM. But no one PAM (-DUSE_PAM).... Is that right?
-
V1.4.1 release fails to compile with 'Error 2'
-
slim-fork updated /README
-
-
-
-
Version 1.4.1 release
-
Prepare for V1.4.1 release
-
Segmentation fault with higher color depth
-
Find the colour
-
Miroslav Bendik :
-
Robert K posted a comment on ticket #10
I found a workaround which actually does not require the above code change. I'll leave this ticket open just case. Feel free to close it. The workaround (which is not nice) is to start the X server with a script that launches another process which inserts the above statement as soon as X has started, like this: #!/bin/sh # Xsetup - run as root before the login dialog appears X= while [ "$X" == "" ]; do X=$( pidof X ) if [ ${#X} -gt 0 ]; then break else sleep 0.1 fi done sleep 1 xrandr --setprovideroutputsource...
-
Xsetup script for slim
-
Find '#' character
-
Slim User created ticket #9
/etc/limits not taken into account
-
Typo in theme documentation
-
Typo in theme documentation
-
Committed revision 69
-
That passwd_feedback wrong
-
Miroslav Bendík created ticket #8
Segmentation fault with higher color depth
-
Rob S created ticket #7
Typo in theme documentation
-
Hi, On gentoo with dual monitors setup and nvidia-drivers, I got the same problem as OP (with slim-1.4.0) : login window splitted across the two screens. I confirm that slim-9999 -r68 seems to fix this issue. Will testing it in the next few days. Thank you !
-
Hello: ... wasn't entirely clear either. That's OK, it's friday. 8^) Devuan "daedalus" package is now V1.4.0 ... ... doesn't cope well on dual monitor / RandR. Both my Sun Ultra 24 WS and my Asus 1000HE run Devuan Beowulf on a backported kernel. Like I mentioned, the only way I got to a proper three monitor desktop was with a hand crafted xorg.conf as for some reason, the X server configuration routine # Xorg :0 -configure was unable get me a properly working configuration file. I am not a dev or...
-
Hello: ... wasn't entirely clear either. That's OK, it's friday. 8^) Devuan "daedalus" package is now V1.4.0 ... ... doesn't cope well on dual monitor / RandR. Both my Sun Ultra 24 WS and my Asus 1000HE run Devuan Beowulf on a backported kernel. Like I mentioned, the only way I got to a proper three monitor desktop was with a hand crafted xorg.conf as for some reason, the X server configuration routine # Xorg :0 -configure was unable get me a properly working configuration file. I am not a dev or...
-
Hello: ... wasn't entirely clear either. That's OK, it's friday. 8^) Devuan "daedalus" package is now V1.4.0 ... ... doesn't cope well on dual monitor / RandR. Both my Sun Ultra 24 WS and my Asus 1000HE run Devuan Beowulf on a backported kernel. Like I mentioned, the only way I got to a proper three monitor desktop was with a hand crafted xorg.conf as for some reason, the X server configuration routine # Xorg :0 -configure was unable get me a properly working configuration file. I am not a dev or...
-
Hi, Sorry, yes, I wasn't entirely clear either. The Devuan "daedalus" package is now V1.4.0 which has a lot of updates but still doesn't cope well on dual monitor / RandR. I don't expect that to cause you any trouble as the relevant screen handling has not changed up to that point. However, from the next release onward, I will be attempting to handle multiple screens (via RandR) for the benefit of people with setups like mine. I would not want that to break things for you, though, so if you were...
-
Hello: Thanks for the prompt reply. I use the SLiM from the Devuan repository. ie: slim/oldstable, now 1.3.6-5.1+devuan6 ... to struggle to help with your problem I'm sorry I was not claer: I don't have a problem, my SLiM works perfectly well. 8^) My post was related to RandR and the Xinerama / Composite extensions when using Nvidia drivers, thought the information regarding RandR being disabled by the X server would be of use to you. Eventually I will have no choice but to move to Devuan Chimaera...
-
Which version of SLiM are you running? I don't have any machines with Nvidia cards, so I'm going to struggle to help with your problem. However, it would be very helpful if you could try the current SVN HEAD and see whether it breaks things for you. On my dual-screen Intel boxes with Xrandr working, it fixes the problem.
-
WRT Xinerama and RandR: I have always had this warning in my Xorg.0.log file. --- snip --- [ 36.425] (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which [ 36.425] (WW) NVIDIA: is an unsupported configuration. The driver will continue [ 36.425] (WW) NVIDIA: to load, but may behave strangely. [ 36.425] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the [ 36.425] (WW) NVIDIA: X server. --- snip --- Under Devuan Linux Chimaera with a backported kernel, I...
-
Bug: slimlock isn't guaranteed to grab keyboard
-
Bug: slimlock isn't guaranteed to grab keyboard
-
Bug: slimlock isn't guaranteed to grab keyboard
-
Changed the App::mcookiesize const member variable to a #define
-
There's no point building in code that isn't used. Image file handling has been
-
QA: cleaned up some inappropriate nested includes
-
Changes made between r61 and r64 to use only one monitor. There's probably scope for a bit of further improvement.
-
Reinstate install of systemd service file - required by Debian
-
Ticket #3 : Use xinerama to pick a viewport (single monitor) for DM mode too
-
Formatting changes only
-
-
-
-
-
-
slim should remember previous session (or have a default session)
-
Inconsistent coordinate system for auth fail message
-
Fixed in V1.4.0
-
Adjusted how/when the pseudo-root window is created and removed, in preparation
-
Adjusted slimlock to use the panel class in the way it was designed to be used
-
Fixed an annoying developer warning from cmake
-
-
-
Version 1.4.0 release
-
Prepare for V1.4.0 release
-
Theme tweak: Moved the input prompts a bit closer to the boxes
-
Some minor documentation updates
-
More general tidy up and cruft removal - no functional change
-
When running in preview mode (theme testing), the panel viewport size is now
-
Ticket #5 continued:
-
Some renaming of variables and a bit of shuffling, just to make it look more
-
Documentation improvements and typo corrections
-
Removed the parameter from Panel::setBackground as commit r48 made it redundant
-
Moved another duplicate function into a class that's shared.
-
There are, in fact, two very good reasons to leave the default behaviour as it currently is: * If using the sessiondir option, there is no way to choose a default, since the order is unpredictable. * The configuration file is central, owned by root, and probably part of the distro package. This means it's not possible to have a per-user default. Leaving the default selection blank means the .xinitrc or equivalent script can pick up a default from the logged-in user's home directory.
-
The background image is now preserved as a panel class member, so that it isn't
-
For efficiency, the "merge" method applied to an image with no transparency is
-
Bug fix - the Merge method used to crop the background image, which is really
-
Removed an unused macro
-
Removed some redundant code and options for the unused "intro_msg"
-
Ticket #5 - the passwd_feedback position is now relative to the root window
-
Inconsistent coordinate system for auth fail message
-
Rather than break everyone's themes, I'll keep the overall "two message classes" but make passwd_feedback always screen-relative. This will be a breaking change for users of V1.3.7 through V1.3.9 but only if they've enabled password feedback. For distros who are adopting V1.3.9 now, I recommend using the attached patch, to avoid confusion.
-
Inconsistent coordinate system for auth fail message
-
Cleaned up some more redundant Mode_Lock tests
-
Odd results from F1 when no sessions are defined
-
Fix committed at r41
-
Ticket #4 : Replaced the config parser with one that correctly differentiates
-
This looks like a result of a very poorly designed parser for the config file. I knew I didn't like the look of it, now I know why. In the absence of an explicit sessions xxx line later in the file, the parser erroneously populates the sessions option with what it finds in the line sessionstop_cmd /usr/bin/sessreg ...
-
See also Debian bug #459260
-
Bug fix : Don't react to F1 in slimlock (it's not meaningful and used to mess
-
Moved HideCursor and setBackground from App class to Panel class, to avoid
-
Tidy up, simplify, and fix a bug in, the merge of slimlock in commit
-
Corrected the handling of the -n / -nodaemon option so that it doesn't swallow
-
Odd results from F1 when no sessions are defined
-
I think the problem here is that the panel code, when in DM mode, assumes the X "display" is the physical screen, and draws the panel over that area. With multiple monitors (or even sometimes without, if the motherboard has an unused LVDS socket for an LCD panel) the display covers the full area of the Xinerama canvas, on which the monitors are arranged. It looks like steps were taken to fix this for slimlock and there is code to read the XRandR data to find the primary monitor.
-
Does not play nicely with multiple monitors / Xinerama
-
Removed the "sessreg" bug note in the man page as the real problem should now
-
Commit fix - forgot to add the "original" theme to the CMakeLists
1 >
