Information about the package: HP: http://slim.berlios.de SLiM is a Desktop-independent graphical login manager for X11, derived from Login.app. It aims to be light and simple, although completely configurable through themes and an option file; is suitable for machines on which remote login functionalities are not needed.
Created attachment 69424 [details] x11-apps/slim-1.2.3 Ebuild for SLiM, created by me
Created attachment 69425 [details, diff] slim-1.2.3-cflags.patch Patch to make the SLiM Makefile aware about custom CFLAGS
Created attachment 69426 [details] x11-themes/slim-themes-1.2.3 Ebuild for SLiM's theme pack
(In reply to comment #1) > Created an attachment (id=69424) [edit] > x11-apps/slim-1.2.3 > > Ebuild for SLiM, created by me I can confirm that it worked for me. emerge --info Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r1, 2.6.1 2-gentoo-r4n i586) ================================================================= System uname: 2.6.12-gentoo-r4n i586 AMD-K6(tm) 3D processor Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X1 1/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=k6-2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://planetmirror.com/pub/gentoo/ ftp://mirror.pacific.net.au/ linux/Gentoo http://mirror.pacific.net.au/linux/Gentoo ftp://mirror.isp.net.au/p ub/gentoo http://mirror.isp.net.au/ftp/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm avi berkdb bitmap-fonts crypt cups curl eds emboss enc ode esd fam foomaticdb fortran gdbm gif gpm gstreamer gtk gtk2 imlib ipv6 java j peg libg++ libwww mad mikmod motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png ppds python quicktime readline samba sdl spell ssl svga tcp d tiff truetype truetype-fonts type1-fonts vorbis xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Created attachment 69538 [details] a runscript to start slim at startup Added runscript to enable uses to automatically start up SLiM
Created attachment 69539 [details] Updated slim-1.2.3 ebuild Updated version that installs runscript and provides message detailing SLiM's usage.
Created attachment 69574 [details] slim-1.2.3.ebuild cleaned up ebuild, added information about SLiM manages sessions with .xinitrc to postinst message. Now installs some documentation files.
Created attachment 69575 [details, diff] slim-1.2.3-cflags.patch now handles CFLAGS and CXXFLAGS properly, handles LDFLAGS now too.
*** Bug 111470 has been marked as a duplicate of this bug. ***
In that patch, you've used /usr/X11R6, while /usr/X11R6 is symlink to /usr, and in ~arch system with modular X.org 7.0 that directory isn't there anymore. Allthough, I had to create it manually cause some ebuilds are still outdated. Could you just drop the X11R6 from it, so it'll be compatible with modular X. Thnks, S. Suominen
Aaarrr.. That was for -L/usr/X11R6/lib , includes are fine cause -I /usr/include is also included.
Created attachment 72104 [details, diff] slim-1.2.3-cflags.patch Here you go, I stripped -L/usr/X11R6/lib, -I/usr/include, -I/usr/X11R6/include
It works, but I also found traces of X11R6 in default slim.conf. Could that be stripped too? Well, I guess it's not a biggie since user has to edit it anyway. :)
Created attachment 76737 [details, diff] slim-1.2.3 daemon_mode config file option. This patch will add daemon_mode in slim config file. This is useful for starting slim from init.d/xdm. Since init.d/xdm (/etc/X11/startDM.sh) does not support options to processes started by start-stop-daemon I've patched slim to support this option in its configuration file. This way slim can start directly in daemon mode without "-d". If not running in daemon mode, the startDM.sh script stays active and gives errors while stopping xdm. The xdmslim.patch is also required. A note to slim runscript: The current runscript for slim have a minor error. When slim stop is executed the X server never stops. If stooped with killall -9 (KILL), slim quits, but X stays. This can be eliminated by killing X after slim, or the signal should be, SIGTERM (15). When using "killall -15" you don't need to remove slim.lock.
Created attachment 76738 [details, diff] slim-1.2.3 init.d/xdm patch This patch together with slimdaemoncfg.patch can be used to start slim from init.d/xdm.
Created attachment 76752 [details, diff] Patch against slim-1.2.3.ebuild to sim-1.2.3-r1.ebuild slim-1.2.3-r1.patch: Download above attachments and rename them to: slim-1.2.3-daemon-configoption.patch slim-1.2.3-xdm.patch Changes: * Removes all traces of 'X11R6' in slim.conf * Applies Ivailo Valkov's patches
Created attachment 76755 [details, diff] Patch against slim-1.2.3.ebuild to sim-1.2.3-r1.ebuild Sorry, typo in patch
Created attachment 76774 [details, diff] Patch against slim-themes-1.2.3 to slim-themes-1.2.3-r1 Added SRC_URI for gentoo theme. You'll need the attachment below which contains the theme. Rename it to slim-gentoo-theme-1.0.tar.bz2 and put it in ${DISTFILES}
Created attachment 76775 [details] slim-gentoo-theme-1.0.tar.bz2
(In reply to comment #16) > slim-1.2.3-daemon-configoption.patch slim-1.2.3-xdm.patch > > Changes: > > * Removes all traces of 'X11R6' in slim.conf > * Applies Ivailo Valkov's patches I've been in contact with one of the developers of slim - I was interested why he dropped daemon option from config file ( it says so in Changelog). In last replay Simone Rota told me that in a couple of days slim-1.2.4 is out and that daemon option is back in config file. His implementation is in SVN already. This patch slim-1.2.3-daemon-configoption.patch wont be needed for future versions.
Created attachment 77528 [details, diff] Patch against slim-1.2.3-r1.ebuild to sim-1.2.4.ebuild Patch to slim-1.2.4.ebuild
Could somebody add a already patched slim-1.2.4.ebuild ?
Created attachment 79736 [details] slim-1.2.4.ebuild
Comment on attachment 79736 [details] slim-1.2.4.ebuild I think this is it -- this bug wasn't terribly easy to follow. (I'd also like to see this in the tree.)
Created attachment 79737 [details] slim-1.2.4.ebuild My apologies; those were both bad. (For one, the einfo at the end is now updated to reflect the correct init script and instructions to edit rc.conf.) I renamed patches as they were renamed in patches to the ebuild, and they rest in my files/ accordingly. Here are the file names from my Manifest (not including the various digests): files/slim-cflags.patch files/slim-xdm.patch slim-1.2.4.ebuild Anyway, I just tried this out (I've been acting out of blind faith so far (please don't kill me) and SLiM (or however the various cases go) is simply wonderful. Goodbye GDM and all your silly deps.
(In reply to comment #25) > (For one, the einfo at the end is now > updated to reflect the correct init script and instructions to edit rc.conf.) Something about rc.config. Maybe a patch is needed for this file too at this line: grep -n kdm /etc/rc.conf 16:# What display manager do you use ? [ xdm | gdm | kdm | entrance ] This will only add slim in the list of available display managers. It is very simple, but I don't have time for this right now. When I have time I can do it, or if someone elese have desire ;) I haven't tested the latest version of slim, so don't know if someone already did this in the ebuild.
Created attachment 79814 [details] slim-1.2.4.ebuild Requested patching ebuild. If "| slim ]" (I'm assuming that slim is the last in the list, which is probably a bad assumption.) is not found in rc.conf, it's patched to include it. Of course the best case senario would be to update rc.conf in baselayout to include slim.
Created attachment 79815 [details] files/slim-rc.patch ...and the patch.
Comment on attachment 79815 [details] files/slim-rc.patch --- rc.conf.ori 2006-02-14 22:01:22.000000000 -0600 +++ rc.conf 2006-02-14 22:01:21.000000000 -0600 @@ -16 +16 @@ -# What display manager do you use ? [ xdm | gdm | kdm | entrance ] +# What display manager do you use ? [ xdm | gdm | kdm | entrance | slim ]
Created attachment 79817 [details] slim-rc.patch Original patch had too many lines that assumed too many things. (ex. I had DISPLAYMANAGER=slim set when I made the patch and epatch failed if DISPLAYMANAGER was set to anything else.) On a side note, it appears bugzilla is significantly smarter than I. I apologize for any unnecessary email traffic to your inboxes.
Created attachment 79839 [details, diff] slim-1.2.4-r1.patch Changes: - Port to modular X (someone please verify this) - statement added to postrm undo slim-rc.patch - /etc/rc.conf is no longer installed as executable
slim seems to put a huge amount of trash in it's logfile, mine was about 1.7GB after a week. Perhaps setting the default logfile to /dev/null would be a wise idea?
I've emerged slim-1.2.4.ebuild and yet another patch is needed, so starting from /etc/init.d/xdm to work. It seems that by default in config file daemon option is commented and I've encountered similar errors while trying to stop xdm (comment #14). So patching slim.config should uncomment the line with "daemon yes", so xdm stops without error messages. (In reply to comment #32) > slim seems to put a huge amount of trash in it's logfile, mine was about 1.7GB > after a week. For a day or two mine is 2.7MB. Maybe redirecting to /dev/null is good idea indeed. You should report about this to slim developers, or you already did ?
Created attachment 79918 [details, diff] slim-1.2.4-r2.patch slim-1.2.4-r2 Changes: - rc.conf is installed in the right place now - pkg_postrm removed, is not behaving like it should - daemon mode is enabled by default - log file set to /dev/null Ivailo: I haven't brought this to attention of the slim developers, as I don't have a logfile to send them anymore.
*** Bug 124529 has been marked as a duplicate of this bug. ***
Can somebody send me or post here a patched ebuild (or an archived overlay)? And, btw, why are you always adding patches not the ebuils? Other people add new ebuilds in their bugs.
Created attachment 83852 [details, diff] slim-gcc41.patch GCC 4.1 Fixes
I've noticed that slim's man page is installed in /usr/man instead in /usr/share/man . The path /usr/man is not in $PATH, so "man slim" returns: "No manual entry for slim". On systems without slim, /usr/man is symlink to /usr/share/man. If someone else experienced the same problem, then slim's Makefile should be patched to install man pages in the right place.
I can't confirm this: fuero@hephaestos ~ % ls /usr/man -lh lrwxrwxrwx 1 root root 9 16. Okt 2004 /usr/man -> share/man fuero@hephaestos ~ % find /usr/share/man -iname '*slim*' /usr/share/man/man1/slim.1
(In reply to comment #36) > And, btw, why are you always adding patches not the ebuils? Other people add > new ebuilds in their bugs. > I agree with this opinion. I'm trying to upgrade to 1.2.4. So I download the slim-1.2.4.ebuild to my portage overlay and then I saw there also where patches available for this file. But the problem is: do I need to patch the -r1 to the original first and then the -r2? Or can I just patch -r2 to the original?
Created attachment 84362 [details] slim-1.2.4-r3.ebuild slim-1.2.4-r3.ebuild (includes gcc-4.1 fixes) from http://forums.gentoo.org/viewtopic-p-3230187.html#3230187
Slim 1.2.5 released: http://slim.berlios.de/
Sorry, "patching" CONFIG_PROTECT-ed files (such as init scripts) on live filesystem is simply not acceptable. Besides, it's also unneeded.
Created attachment 93648 [details] slim-1.2.5.ebuild Ok, reworked the ebuild a bit. Also, it uses XDM init script now, like any other login manager in portage, there's no need to have a special init script for this.
Created attachment 93649 [details, diff] files/slim-cflags.patch new patch, now fixes MANDIR location as well. (gcc-4.1 patch is no longer needed for 1.2.5)
Created attachment 93660 [details] x11-themes/slim-themes-1.ebuild Reworked slim-themes ebuild.
Created attachment 94500 [details] a customized ebuild for slim-1.2.5 FYI, I've poked jakub's, and made some patches. Here's my changing summary. 1. Deleted unneeded DEPEND atoms. Try to run "pkg-config xft xmu libpng", and libXpm may be not madantory. 2. Used sed for Makefile instead of patching. I've used pkg-config instead of patch was hardcoded. 3. Silence all warings for "-O2 -Wall". Stupid C++ (was so buzzed as warnings when compiling) has ton of possibilities of implicitly bugs, IMHO.
Created attachment 94501 [details, diff] slim-1.2.5_cfg-use-int.patch [PATCH 1/4]
Created attachment 94502 [details, diff] slim-1.2.5_image-x-to-lx.patch [PATCH 2/4]
Created attachment 94503 [details, diff] slim-1.2.5_panel-no-unused-uninit.patch [PATCH 3/4]
Created attachment 94504 [details, diff] slim-1.2.5_switchuser-no-args.patch [PATCH 4/4]
Created attachment 94505 [details] a costumized ebuild for slim-1.2.5 Sorry, I've mistaken, previous one has access violation issue. I forgot einstall's suckness...
Thanks, I'll give it a try and update the ebuild in Sunrise accordingly. Please, submit those warning fixes upstream.
Created attachment 94515 [details] a custom ebuild slim-1.2.5 Bah, critical typo... (DESTDIR="{D}" -> DESTDIR="${D}")
Created attachment 94516 [details] slim-1.2.5-r1.ebuild OK, updated ebuild commited. I don't really feel like messing w/ what upstream wants to link with, so that part is not in. Please ask upstream to fix their Makefile to not do redundant linking if it's really redundant.
Created attachment 94517 [details, diff] files/slim-fix-warnings.patch The above warning patches combined into one patch.
Created attachment 94525 [details, diff] slim-1.2.5_switchuser-correct-init.patch Sorry, again. I've misfixed the warings about switchuser.cpp. If apply previous one (slim-1.2.5_switchuser-correct-init.patch). it cann't login... The warnings said "should init correct order", according to [1]. So, this one (slim-1.2.5_switchuser-correct-init.patch) should really fix. jakub: Could you use it instead of previous one? Or just delete previous one in the unifided fix patch... --- [1] http://www.ogre.com/tiki-view_blog_post.php?blogId=3&postId=119
(In reply to comment #57) [SNIP] > If apply previous one (slim-1.2.5_switchuser-correct-init.patch). [SNIP] ugh, silly me... s/correct-init/no-args/
Created attachment 94529 [details, diff] files/slim-fix-warnings.patch (In reply to comment #57) > Sorry, again. > I've misfixed the warings about switchuser.cpp. > If apply previous one (slim-1.2.5_switchuser-correct-init.patch). > it cann't login... Done. And please send this upstream so that we can get rid of the patches.
FYI, I reported this fix to upstream. [1] --- [1] http://developer.berlios.de/patch/?func=detailpatch&patch_id=1358&group_id=2663
Created attachment 98164 [details, diff] slim-1.2.6.ebuild.diff FYI, slim-1.2.6 was released 2006/09/15. It includes memleak ifx and my stupid warnig silence patches or so, according to svn chnagelog. This attached diff can be applied to renamed my own previous ebuild for slim. This diff will do * comment-out epatch line of merged patches * correct use of CXXFLAGS * build-time --as-needed fix (but, not sure whether it's rutime fix)
*** Bug 168403 has been marked as a duplicate of this bug. ***
Hey guys. I'm using slim-1.2.6 and xfce4.4 and i'm facing problems with the fbsplash thing. It seems like slim and fbsplash are trying to draw the screen at the same time, like they are competing with each other. It happens when i add net.eth0 and xdm to the default runlevel. Slim is called and draws the screen first, but a few seconds later the progress bar from the fbsplash appears. F1 makes it go away. Removing net.eth0 from the runlevel solves it too, because the fbsplash progress bar appears seconds before slim's background. Thanks.
(In reply to comment #63) > Hey guys. I'm using slim-1.2.6 and xfce4.4 and i'm facing problems with the > fbsplash thing. It seems like slim and fbsplash are trying to draw the screen > at the same time, like they are competing with each other. It happens when i > add net.eth0 and xdm to the default runlevel. Slim is called and draws the > screen first, but a few seconds later the progress bar from the fbsplash > appears. F1 makes it go away. Removing net.eth0 from the runlevel solves it > too, because the fbsplash progress bar appears seconds before slim's > background. > Thanks. > I've set /etc/conf.d/splash not to draw the fbsplash on the tty7 and the bug is gone. Sorry guys.
Hey there. I've reported a minor bug upstream that was solved after some modification to /usr/share/doc/slim-1.2.6/xinitrc.sample.bz2. The file should read like this, according to the devs: # the following variable defines the session which is started if the user # doesn't explicitely select a session DEFAULT_SESSION=startxfce4 case $1 in xfce4) exec startxfce4 ;; icewm) icewmbg & icewmtray & exec icewm ;; wmaker) exec wmaker ;; blackbox) exec blackbox ;; *) exec $DEFAULT_SESSION ;; esac The original bug: https://developer.berlios.de/bugs/?func=detailbug&bug_id=10732&group_id=2663 I hope it helps. Thanks. NPC.
Created attachment 114887 [details] Update to slim-themes-1 ebuild I have updated the ebuild, so all themes which are currently available will be installed. Maybe this could be added to the sunrise overlay. Btw. thanks to Tiburcio da Silva in comment #65, i had the same login problem.
What about the gentoo-theme? It is very nice. Could someone send it upstream so that it will be available as an 'official' theme?
I'm currently using a slight modified version of http://xfce-look.org/content/show.php?content=48605 It's a nice theme, features a cube with xfce and gentoo logo. Shalom! NPC.
(In reply to comment #68) nice i have added the theme to my slim-themes ebuild in my local overlay
Found something in the ebuild where elog states: elog "If you wish ${PN} to start automatically, set DISPLAYMANAGER=\"${PN}\" " elog "in /etc/rc.conf and run \"rc-update add xdm default\" " I think this is not right anymore, the DISPLAYMANAGER variable is now defined in /etc/conf.d/xdm.
Is anybody using slim with gensplash and splashutils. When my system shuts down, the splash screen is completely borked. Which means i see almost nothing of the splash screen and if, the picture looks destroyed. With xdm it works as expected at shutdown.
(In reply to comment #71) > Is anybody using slim with gensplash and splashutils. > > When my system shuts down, the splash screen is completely borked. Which means > i see almost nothing of the splash screen and if, the picture looks destroyed. > > With xdm it works as expected at shutdown. > I'm using gensplash here. I've faced problem with it and slim, but everything was fixed after i disabled it on /etc/conf.d/splash on tty7. # on which ttys should fbsplash be enabled? defaults to RC_TTY_NUMBER SPLASH_TTYS="1 2 3 4 5 6" Hope it helps. NPC.
(In reply to comment #72) > I'm using gensplash here. I've faced problem with it and slim, but everything > was fixed after i disabled it on /etc/conf.d/splash on tty7. > > # on which ttys should fbsplash be enabled? defaults to RC_TTY_NUMBER > SPLASH_TTYS="1 2 3 4 5 6" i have already disabled fbsplash on tty7, fbsplash is only running on tty1 here. so this seems not to cause my problems.
Both, slim and slim-themes have been committed to tree. Expect them in your mirror in hour or so..
Created attachment 120252 [details] ebuild for slim-pam The attachment is an ebuild for slim-pam which is to be released as version 1.3.0 of slim. According to upstream, they plan on releasing it this WE, but for whoever wishes to use it already today... ;)
