I am using kdebase-kdm, the session menu (ie choosing WM) is fixed, after
checking my log I found:
Nov 17 01:25:06 nanar kdm_config[3203]: Unrecognized key 'SessionTypes' in
section [X-*-Greet
er] at /usr/share/config/kdm/kdmrc:67
Nov 17 01:25:06 nanar kdm_config[3203]: Unrecognized key 'AutoLog
I know we are in freeze but
I find kdm a little confusing for newbies (and myself...)
I miss a button to log in. This is of cause the default, but
it is not obvious.
Having a default and having the default as an explicit choice would
make things clearer (this is a general observation).
keld
On Monday 04 August 2003 12:34 pm, Tomasz Chmielewski wrote:
> Could somebody give me a good reason why one should be able to login to
> KDE/Gnome as root, i.e. not being able to do the same thing as an
> ordinary user using su?
Because I want to. Waaahhh! :-p
--
/g
"Outside of a dog, a man's b
Adam Williamson <[EMAIL PROTECTED]> wrote:
> Here is a perfect summation of why it's absolutely correct to disable
> root login by default, from #mandrake IRC:
>
> [snip: explanation and conclusion]
Yes but it should be more or less self-explanatory. What could be done
is the following or some sub
On Mon, 2003-08-04 at 17:44, Luca Berra wrote:
> > Yeah indeed.
> > Could somebody give me a good reason why one should be able to login to
> > KDE/Gnome as root, i.e. not being able to do the same thing as an
> > ordinary user using su?
> >
> on my laptop /home is encrypted
> if i foget to pres
Adam Williamson wrote:
Here is a perfect summation of why it's absolutely correct to disable
root login by default, from #mandrake IRC:
(...)
Had he been able to login as root by default, he would simply have done
so, and probably carried on with this incorrect and dangerous practice.
Since he coul
On Mon, 2003-08-04 at 16:47, Rob wrote:
> On Monday 04 August 2003 11:33, Adam Williamson wrote:
> > Had he been able to login as root by default, he would simply have done
> > so, and probably carried on with this incorrect and dangerous practice.
> > Since he couldn't, he asked for information on
Yeah indeed.
Could somebody give me a good reason why one should be able to login to
KDE/Gnome as root, i.e. not being able to do the same thing as an
ordinary user using su?
on my laptop /home is encrypted
if i foget to press a key when booting users cannot logon.
and switching back and forth t
On Monday 04 August 2003 11:33, Adam Williamson wrote:
> Had he been able to login as root by default, he would simply have done
> so, and probably carried on with this incorrect and dangerous practice.
> Since he couldn't, he asked for information on how he could, and the
> channel was able to ins
Here is a perfect summation of why it's absolutely correct to disable
root login by default, from #mandrake IRC:
Can someone please explain to me how to logon as root with
Mandrake 9.1 using KDE? Need to install something and I want it for all
users.
WNxSquee: su to root and run the installer f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, I would have no problem with mandrake making their own dm calling it
mdkdm or mdm or whatever, but kdm on my machine right now is not kdm, I want
kdm to be kdm not someone's replacement of it. I like the features that kdm
had, and personally I'
Jason Straight wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Can we at least have the old kdm as /usr/bin/kdm.doesnt_suck or something.
>
> What was the point of replacing something that worked with something that has
> less features? I no longer have focus last user, no clock, no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can we at least have the old kdm as /usr/bin/kdm.doesnt_suck or something.
What was the point of replacing something that worked with something that has
less features? I no longer have focus last user, no clock, no user selection,
and it's automatic
I logged out after I got kde3rc6 upgraded, and couldn't log back in.
We're using LDAP and pam_smb, the config is in /etc/pam.d/system-auth,
and kdm has been working since I started running cooker on this box. gdm
still works, and I haven't touched it's pam file.
I get this in auth.log
Jan 8 13:5
sorry, I forgot to tell I'm using a Mandrake 9.0, in 4th msec security
level...
Henri a écrit:
Hi,
I found an annoying bug in KDM : My passwd expired today (0 days) ->
it says i should change it immediatly BUT does not let me to connect !
Going into console mode, i enter my login+passwd, and i
Hi,
I found an annying bug in KDM : My passwd expired today (0 days) -> it
says i should change it immediatly BUT does not let me to connect !
Going into console mode, i enter my login+passwd, and it tell me I must
change it right now and prompt me for a new passwd -> i'm logged in !
-> in fact
In Mandrake 9, how can I make the logout script run? This is rather time
sensitive for the scripts I am working on. Any help would be greatly
appreciated.
--
Matthew C. Tedder
SimpFlex Technologies, Inc.
Hi,
Yesterday, a power outage shutted down my computer,
and when it booted up, KDB was going crazy, I couldn't
login with any user, even with root. Now, I have to
use gdm instead. At start, KDM showed tons of users in
its user icon space, I saw gpm, mysql, postfix users,
which are for certain pro
On Tue, 23 Jul 2002 21:16, Sitsofe Wheeler wrote:
> if I log out (thus going to the kdm screen
> and then use ctrl-alt-backspace to reset X several times (about five or
> so) then after a while I will be automatically logged in again (which is
> probably undesirable).
Sounds like the log-me-back-
I don't know if this has been fixed in the latest version of autologin
(since I think it is that causing the problem) but if I start my 8.2
computer autologin (autologin-1.0.0-5mdk) will automatically start my
desktop as expected. However, if I log out (thus going to the kdm screen
and then use ct
On Mon, Jul 08, 2002 at 12:34:15AM -0400, Jason Straight wrote:
> kdm shows all users no matter what I set it to. It will work for ONE
> logout/login right after I set the configs but revert to showing all users on
> following logins.
Same thing happened to me after I went in and turned off nob
kdm shows all users no matter what I set it to. It will work for ONE
logout/login right after I set the configs but revert to showing all users on
following logins.
--
^^^
Jason Straight
I still have this problem with 4.0.2-2mdk
--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> kdm on Dell Inspiron 8000 does not show X
> background.
> It only shows the generic greyish X background. This
> is when kdm is local and when using as thin client.
>
> The local kdm is much worse, however in
I second this. Same problem on my 8000.
On Tuesday 29 January 2002 02:53, SI Reasoning wrote:
> kdm on Dell Inspiron 8000 does not show X background.
> It only shows the generic greyish X background. This
> is when kdm is local and when using as thin client.
>
> The local kdm is much worse, how
kdm on Dell Inspiron 8000 does not show X background.
It only shows the generic greyish X background. This
is when kdm is local and when using as thin client.
The local kdm is much worse, however in that there is
also no background for the login window either. This
makes for a very difficult to s
You may be right. But it's not like the Recommended
install doesn't silently do a lot of
stup^H^H^H^Hinteresting things anyway :o) I was just
thinking that if you're gonna do it at all, asking
about it in the newbie^H^H^H^H^H^HRecommended install
routine might not be the best thing. It's up to
le lun 21-01-2002 à 17:11, David Walser a écrit :
> Even better I think would be for the Recommended
> installation to detect the video chipset (we already
> do that) and if it's one with a known problem disable
> it, otherwise enable it.
silebntly enable something that may affect performance may
David Walser <[EMAIL PROTECTED]> wrote:
> Pay attention people, I corrected myself in a later
> message. It used not to work, yesterday I took 3
> extensions out of XF86Config-4 and it works now.
Basic Mailing List Info:
You can never tell whether someone saw a later message from you or no
Pay attention people, I corrected myself in a later
message. It used not to work, yesterday I took 3
extensions out of XF86Config-4 and it works now.
--- Peter Ruskin <[EMAIL PROTECTED]> wrote:
> On Monday 21 Jan 2002 15:49, David Walser wrote:
> > So does NVidia's proprietary module. I really
On Monday 21 Jan 2002 15:49, David Walser wrote:
> So does NVidia's proprietary module. I really hate
> that BTW and I wish they'd fix that. Even Xnest
> doesn't work :o(
Nonsense. I'm using NVidia's driver. I just did and
entered "startx -- :1" and immediately got another X session on F8.
NVidia's. 2314
--
Murray J. Root
[EMAIL PROTECTED] - email
(404) 978-1262 x2646 - voicemail/fax
David Walser <[EMAIL PROTECTED]> wrote:
> Are you running Nvidia's proprietary module, or the
> open source one? It works for me with the open source
> (nv, comes with X, NVidia's is nvidia)
Are you running Nvidia's proprietary module, or the
open source one? It works for me with the open source
(nv, comes with X, NVidia's is nvidia) one. With
Nvidia's I get...confused! I swear it used not to
work. Yesterday I just removed the loading of some
extensions (record, pex5, and xie) fro
> --- andre <[EMAIL PROTECTED]> wrote:
> > AFAIK some Xservers have trouble when you run more
> > than one Xserver(the
> > i810 had some problems with this IIRC)
> >
> >
>
David Walser <[EMAIL PROTECTED]> wrote:
> So does NVidia's proprietary module. I really hate
> that BTW and I wish t
Even better I think would be for the Recommended
installation to detect the video chipset (we already
do that) and if it's one with a known problem disable
it, otherwise enable it.
For the Expert, still detect, but give the choice, but
give a warning that it won't work if they have a bad
chipset,
le lun 21-01-2002 à 16:05, andre a écrit :
> >
> >
> > so this features may be an option. During install or in MCC you say :
> > "set kdm/gdm for multiusers environment". This is not enable by default.
> > You may even put a warning ( Warning : this will increase a bit you
> > memory comsumption
So does NVidia's proprietary module. I really hate
that BTW and I wish they'd fix that. Even Xnest
doesn't work :o(
--- andre <[EMAIL PROTECTED]> wrote:
> AFAIK some Xservers have trouble when you run more
> than one Xserver(the
> i810 had some problems with this IIRC)
>
>
__
>
>
> so this features may be an option. During install or in MCC you say :
> "set kdm/gdm for multiusers environment". This is not enable by default.
> You may even put a warning ( Warning : this will increase a bit you
> memory comsumption. If you experience troubles, disable this features as
le lun 21-01-2002 à 15:20, andre a écrit :
> Op ma 21-01-2002, om 14:20 schreef Fabrice FACORAT:
> > I've just notice something interesting ...
> > If I remember well on solaris when you log in in you X session you can
> > go back to the X logging screen without log out from your X session. So
> >
Op ma 21-01-2002, om 14:20 schreef Fabrice FACORAT:
> I've just notice something interesting ...
> If I remember well on solaris when you log in in you X session you can
> go back to the X logging screen without log out from your X session. So
> you can lock your session, go back to X logging scre
I've just notice something interesting ...
If I remember well on solaris when you log in in you X session you can
go back to the X logging screen without log out from your X session. So
you can lock your session, go back to X logging screen and allow someone
to log in on another virtual screen.
I'
Le Jeudi 23 Août 2001 23:03, Blue Lizard a écrit :
> > KDE now sarts 50% faster than with "kdebase-2.2-10mdk".
>
> Laurent: Is this founded (i assume so)? If yes, what _did_ you do? I
> am almost sure no objprelink :P.
Hi,
I am very happy that you think that kdebase starts 50% faster than with
> KDE now sarts 50% faster than with "kdebase-2.2-10mdk".
Laurent: Is this founded (i assume so)? If yes, what _did_ you do? I
am almost sure no objprelink :P.
> Dunno what KDE team did but it's SUPER :-)))
Hello Laurent,
Es schrieb Laurent Montel:
> Le Mardi 21 Août 2001 17:57, Stefan Siegel a écrit :
> > Hi Laurent et all,
> >
> > as "startkde" is finally fixed I will continue reporting KDE bugs.
> >
> > Here we go: Since I've upgraded to kdebase-2.2-10mdk recently,
> > my kdm won't work
>
> I know it's been reported before:
> KDM choices are
> default
> kde
> failsafe
> /etc/X11/wmsession.d lists 01KDE (uppercase) - that's why it isn't
chosen.
>
> The installer needs to parse /etc/X11/wmsession.d, stripping the first
2
> digits, and add a comma-separated list
I know it's been reported before:
KDM choices are
default
kde
failsafe
/etc/X11/wmsession.d lists 01KDE (uppercase) - that's why it isn't chosen.
The installer needs to parse /etc/X11/wmsession.d, stripping the first 2
digits, and add a comma-separated list between "defa
Hi Laurent et all,
as "startkde" is finally fixed I will continue reporting KDE bugs.
Here we go: Since I've upgraded to kdebase-2.2-10mdk recently,
my kdm won't work any more. This is what I get in "/var/log/messages"
+---
Le Lundi 20 Août 2001 21:43, Blue Lizard a écrit :
> Attn. Laurent?
>
> kdm has no enlightenment entry, and it is installed. At least, there is
> no entry here. Can't figure out how it may have been oversighted.
hi,
I will try to fix it.
Bye
>
> Attn. Laurent?
>
> kdm has no enlightenment entry, and it is installed. At least, there
is
> no entry here. Can't figure out how it may have been oversighted.
It is fndSession bug (wrong path to kdmrc). I already reported it.
Anybody cares to fix mandrake_desk?
-andrej
Attn. Laurent?
kdm has no enlightenment entry, and it is installed. At least, there is
no entry here. Can't figure out how it may have been oversighted.
Updated this morning... KDM will not start, but I can
run X and kde...
Aug 15 07:12:04 dhcp-98 kdm_config[1684]: Unrecognized key 'Xwilling' at
/usr/share/config/kdm/kdmrc:71
Aug 15 07:12:04 dhcp-98 kdm[1675]: Cannot open access control file
/usr/share/config/kdm/Xaccess, no XDMCP reqeusts wil
Borsenkow Andrej wrote:
> Frederic Lepied wrote:
>
>>
>> Could you show us your ~/.xsession-errors ?
>>
>
>
> /usr/share/config/kdm/Xsession: /home/bor/.xsession: No such file or
> directory /usr/share/config/kdm/Xsession: exec: /home/bor/.xsession:
> cannot execute: No such file or directory
>
> [EMAIL PROTECTED] wrote:
>
> >>- the case of uid > 500 was just covered I have seen. Good :-)
> >>
> >>
> > do you mean >= 500 because i have uid 500
>
>
> Yes, I beliueve he does. 500 is where the first normal UID starts.
> Therefore mine is 500 as well. And aside from the /sbin/poweroff
[EMAIL PROTECTED] wrote:
>>- the case of uid > 500 was just covered I have seen. Good :-)
>>
>>
> do you mean >= 500 because i have uid 500
Yes, I beliueve he does. 500 is where the first normal UID starts.
Therefore mine is 500 as well. And aside from the /sbin/poweroff problem
I mentioned,
>
> - the case of uid > 500 was just covered I have seen. Good :-)
>
do you mean >= 500 because i have uid 500
Frederic Lepied wrote:
>
> Could you show us your ~/.xsession-errors ?
>
/usr/share/config/kdm/Xsession: /home/bor/.xsession: No such file or
directory /usr/share/config/kdm/Xsession: exec: /home/bor/.xsession:
cannot execute: No such file or directory
This is due to the lines in /usr/shar
> "J" == Joe Menola <[EMAIL PROTECTED]> writes:
J> I've had problems when the default was selected. Choosing kde
J> from the list box on the first login gets me in. Exit to
J> console has been broke for quite some time.
Same here; selecting Gnome won't work, only KDE. If I set m
"Andrej Borsenkow" <[EMAIL PROTECTED]> writes:
> I run the last Friday (20July) sync of cooker. Out of interest I've enabled
> GUI (normally I just run startx). I could not login. Attempt to login just
> results in KDM login screen again. Attempt to do console login results in
> KDM login screen.
I've had problems when the default was selected. Choosing kde from the list
box on the first login gets me in. Exit to console has been broke for quite
some time.
-jm
On Tuesday 24 July 2001 04:03 am, you wrote:
> I run the last Friday (20July) sync of cooker. Out of interest I've enabled
> GUI
On Tuesday 24 July 2001 11:03, you wrote:
> Anybody else had this issue?
I usually don't use X-login, but I went to Mdk-Control-Center and opted for
it. When I tried to login both as user and root I was kicked back to the
login window.
I had to use linuxconf from a console to change back.
Ve
I run the last Friday (20July) sync of cooker. Out of interest I've enabled
GUI (normally I just run startx). I could not login. Attempt to login just
results in KDM login screen again. Attempt to do console login results in
KDM login screen. I had to Ctrl-Alt-F1 to kill X11.
No errors in XFree l
--- Francisco Alcaraz Ariza <[EMAIL PROTECTED]> wrote:
> This is for the mandrake team;
> Do you know if the problem for DRI activated and kdm login crashing x when
> switching between ressolution has been solved?; Is there any update
> avalaibel?
This was solved on XFree86-4.0.3-9mdk:
[root@fu
This is for the mandrake team;
Do you know if the problem for DRI activated and kdm login crashing x when
switching between ressolution has been solved?; Is there any update avalaibel?
Thanks for your kind attention
--
Francisco Alcaraz Ariza
Department of Plant Biology
Faculty of Biology
Uni
Would it be possible to put a selector in XFDrake to let one select eather
kdm or gdm?
Dave
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Linux - Cause I dont do windows
or ovens!
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-=-=-=-=-=
Sebastian Dransfeld <[EMAIL PROTECTED]> writes:
> On 27 Mar 2001, Daouda LO wrote:
>
> > Gary Chisholm <[EMAIL PROTECTED]> writes:
> >
> > > Just a little issue when having enlightment installed it was in the
> > > Windows Session list in kdm within 7.2, but not in 8.0 beta...
> >
> > What ls /e
On 27 Mar 2001, Daouda LO wrote:
> Gary Chisholm <[EMAIL PROTECTED]> writes:
>
> > Just a little issue when having enlightment installed it was in the
> > Windows Session list in kdm within 7.2, but not in 8.0 beta...
>
> What ls /etc/X11/wmsession.d/ said ??
>
Last time I checked, the path behi
Gary Chisholm <[EMAIL PROTECTED]> writes:
> Just a little issue when having enlightment installed it was in the
> Windows Session list in kdm within 7.2, but not in 8.0 beta...
What ls /etc/X11/wmsession.d/ said ??
Just a little issue when having enlightment installed it was in the
Windows Session list in kdm within 7.2, but not in 8.0 beta...
fyi... thanx
Opening a Unix Domain Socket would prevent logins from remote machines
Prana wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
> Just wondering, why does kdm (login manager) have to open TCP port 1024?
> Can't it just use unix domain socket?
>
> Thanks,
> Prana
>
> - --
> Pra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Just wondering, why does kdm (login manager) have to open TCP port 1024?
Can't it just use unix domain socket?
Thanks,
Prana
- --
Prana <[EMAIL PROTECTED]>
http://www.cyest.org
GnuPG Key ID: 0x33343FD3 (2000-07-21)
Key fingerprint = F1FB 1F76
On Monday 05 March 2001 13:51, Ian C. Sison wrote:
> Hello, this has been a problem since kde 1.x - although there are options
> to configure the background of kdm (like wallpapers and patterns) no
> matter what i do, it still does not work.
>
> Is it just these RPM sets or is this "feature" so te
Hello, this has been a problem since kde 1.x - although there are options
to configure the background of kdm (like wallpapers and patterns) no
matter what i do, it still does not work.
Is it just these RPM sets or is this "feature" so terribly broken?
> In every case KDM works OK. I have seen the behaviour you mention and it has
> nothing to do with KDE, so there's no point in sending a KDE bug report.
> It's something that Mandrake has introduced, perhaps in the frenzy of
> packaging new versions daily (until recently).
At least someone who
On Tuesday 06 February 2001 11:15, Jürgen Zimmermann wrote:
> > So you can see the kdm window ?
>
> Yes.
>
> > If this is the case then kdmrc has taken effect
> > and what can happen (I think) is only selecting
> > the right wm.
>
> Well, every modification I make to "/usr/share/config/kdmrc"
> is
> > this will be fixed .
>
> That's good news!
> Thank you...
>
>
>
>
> Is there anything like a public "bugtraq" for Mandrake-Cooker? The link
> from
> "http://www.linux-mandrake.com/en/email.php3" to
> "https://qa.mandrakesoft.com"
> asks for UID/PASSWORD, though.
>
>
You have to sign up
Daouda LO wrote:
>
> Terry Nelms <[EMAIL PROTECTED]> writes:
>
> > I have the same problem. I'm one of those that posted about it
> > earlier. So far I haven't received any response regarding a fix for it
> > and I have been unable to change it's behavior no matter what I do.
> > I've pretty m
Glad to hear you're working on it. I'm sure you'll get it worked
out. I know Cooker is for development so it was no big deal, I just
put an older version back on until you get this one working again.
It just didn't seem like anyone was listening to us.
Later,
Terry
Daouda LO wrote:
Terry Nelm
Terry Nelms <[EMAIL PROTECTED]> writes:
> I have the same problem. I'm one of those that posted about it
> earlier. So far I haven't received any response regarding a fix for it
> and I have been unable to change it's behavior no matter what I do.
> I've pretty much given up on it. No one from
> So you can see the kdm window ?
Yes.
> If this is the case then kdmrc has taken effect
> and what can happen (I think) is only selecting
> the right wm.
Well, every modification I make to "/usr/share/config/kdmrc"
is ignored. The ones I'm interested in are "SessionTypes" which
are modified b
Jürgen Zimmermann wrote:
>
> "Eric MC.D" wrote:
> >
> > Did you select kdm or xdm ???
> > Eric MC
> > Jürgen Zimmermann wrote:
> /usr/bin/kdm
> KDM!!!
> Right after boot-up:
>
> root 10674 1 0 09:09 ?00:00:00 kdm
>
> Well, after 10 years of system administration, I can tell
> y
I have the same problem. I'm one of those that posted about it earlier.
So far I haven't received any response regarding a fix for it and I have
been unable to change it's behavior no matter what I do. I've pretty
much given up on it. No one from Mandrake seems to be too interested
in fixing
"Eric MC.D" wrote:
>
> Did you select kdm or xdm ???
> Eric MC
> Jürgen Zimmermann wrote:
/usr/bin/kdm
KDM!!!
Right after boot-up:
root 10674 1 0 09:09 ?00:00:00 kdm
Well, after 10 years of system administration, I can tell
you the difference between xdm and kdm... Perhaps I s
Did you select kdm or xdm ???
Eric MC
Jürgen Zimmermann wrote:
>
> "Eric MC.D" wrote:
> >
> > Jürgen Zimmermann wrote:
> > >
> > > > >
>SessionTypes=KDE,Gnome,WindowMaker,BlackBox,XFce,AfterStep,IceWM,Sawfish,Fvwm2,Fvwm1,failsafe,default
> > > >
> > > > Change here the ',' to ';' and you can sel
"Eric MC.D" wrote:
>
> Jürgen Zimmermann wrote:
> >
> > > >
>SessionTypes=KDE,Gnome,WindowMaker,BlackBox,XFce,AfterStep,IceWM,Sawfish,Fvwm2,Fvwm1,failsafe,default
> > >
> > > Change here the ',' to ';' and you can select separetely
> > > what you want !!!
> >
> > But this is generated each time
Jürgen Zimmermann wrote:
>
> > >
>SessionTypes=KDE,Gnome,WindowMaker,BlackBox,XFce,AfterStep,IceWM,Sawfish,Fvwm2,Fvwm1,failsafe,default
> >
> > Change here the ',' to ';' and you can select separetely
> > what you want !!!
>
> But this is generated each time at boot-up, isn't it???
> The comman
> >
>SessionTypes=KDE,Gnome,WindowMaker,BlackBox,XFce,AfterStep,IceWM,Sawfish,Fvwm2,Fvwm1,failsafe,default
>
> Change here the ',' to ';' and you can select separetely
> what you want !!!
But this is generated each time at boot-up, isn't it???
The command here is:
/usr/sbin/chksession -k
in /us
Jürgen Zimmermann wrote:
>
> Despite the modifications made to KDM´s configuration file
> (see attachment), KDM shows all users (sympa...), but only the session
> types "default, kde, failsafe".
>
> Moreover, it replies to XDCMP broadcast requests and allows
> a login from other than local XServ
Despite the modifications made to KDM´s configuration file
(see attachment), KDM shows all users (sympa...), but only the session
types "default, kde, failsafe".
Moreover, it replies to XDCMP broadcast requests and allows
a login from other than local XServers.
The problem is with Cooker, and wa
Stefan van der Eijk <[EMAIL PROTECTED]> writes:
> Hi,
>
> With the latest kde release kdm won't start. The following error shows
> up in syslog:
>
> Dec 29 15:04:55 stefan kdm[823]: libKdmGreet.so: cannot open shared
> object file: No such file or directory while loading libKdmGreet.so
thanx ,
Hi,
With the latest kde release kdm won't start. The following error shows
up in syslog:
Dec 29 15:04:55 stefan kdm[823]: libKdmGreet.so: cannot open shared
object file: No such file or directory while loading libKdmGreet.so
It seems this file is missing (I can't find libKdmGreet.so on my syste
Balaji Ramani <[EMAIL PROTECTED]> writes:
> Hi Chris,
>
> I had previously submitted a bug report about kdm not working in the KDE 2.1
> CVS build (20001210) for 7.2. You pointed out that it was a bug in kde.
>
> But I would like to point out that it is a packaging problem. The file
> libKd
Thanks for noticing this. Fixing this actually fixed kdm. I will update the
"unsupported" 7.2 builds later today on nebsllc.com and post a message when
complete.
-Chris
On Wednesday 13 December 2000 08:55, you wrote:
> Hi Chris,
>
> I had previously submitted a bug report about kdm not working
Thanks,
That one I can fix in my CVS builds.
Daouda, The same fix is probably needed in the cooker packages as well. It
seems the lib files have changed again. In my SPECS directory on kenobi there
are file lists that you can use for diffs.
-Chris
On Wednesday 13 December 2000 08:55, you wr
Hi Chris,
I had previously submitted a bug report about kdm not working in the KDE 2.1
CVS build (20001210) for 7.2. You pointed out that it was a bug in kde.
But I would like to point out that it is a packaging problem. The file
libKdmGreet.so was not included in the package. The file is n
hey,
I have LM72 final. When i try to change the wallpaper for the kdm login
manager it doesn't get saved.
--Khawar Zia
On Tue, 19 Sep 2000, you wrote:
>now the current policy is to set :
>
>halt to halt (and not poweroff)
>poweroff to poweroff
>
>the best way is to patch end-user programs to poweroff, command line
>user will want to use poweroff command instead of halt
>
>here is the patch for kdm :
>
>--- kdebase
now the current policy is to set :
halt to halt (and not poweroff)
poweroff to poweroff
the best way is to patch end-user programs to poweroff, command line
user will want to use poweroff command instead of halt
here is the patch for kdm :
--- kdebase/kdm/kdm-config.h.chmou Sun Jul 30 17
> > > 3) The KDE menus seem _very_ empty by default. It seems that only
> > > the "extra" installed apps are in it, the default KDE ones aren't
> > > (even stuff like kappfinder, the kde console, kedit etc. etc.)
> >
> > I can trell you a little bit about this one. It seems 7.1 will use a new
> >
David Walluck <[EMAIL PROTECTED]> writes:
> On Wed, 29 Mar 2000, Stefan van der Eijk wrote:
>
> > 3) The KDE menus seem _very_ empty by default. It seems that only
> > the "extra" installed apps are in it, the default KDE ones aren't
> > (even stuff like kappfinder, the kde console, kedit etc. e
On Wed, 29 Mar 2000, Stefan van der Eijk wrote:
> 3) The KDE menus seem _very_ empty by default. It seems that only
> the "extra" installed apps are in it, the default KDE ones aren't
> (even stuff like kappfinder, the kde console, kedit etc. etc.)
I can trell you a little bit about this one. It
Hi,
I've just installed cooker, and I'm having some issues:
1) KDM exits with the following message in the /var/log/messages:
kdm[3573]: Unknown session exit code 2816 from process 3581
2) This system is a client in a NIS / NFS / automount environment.
After booting, users don't get their homed
1 - 100 of 103 matches
Mail list logo
