On July 26, 2005 15:35, Benjamin Mesing wrote:
> Package: kdm
> Version: 4:3.3.2-1
> Followup-For: Bug #263449
>
> Just wanted to note, that for me the problem persists.
>
> I have worked around this issue by removing
> -nolisten tcp option.
Could someone running the KDE 3.4 packages test this bug
Looks like it was already a correct sollution :)
http://lists.debian.org/debian-kde/2005/03/msg00282.html
Ernestas
On Sunday 27 March 2005 19:59, Ernestas Vaiciukevicius wrote:
> Hi,
> After upgrading KDE from sid's version to 3.4 I had the following problem
> with kdm : it didn't start session
Hi,
After upgrading KDE from sid's version to 3.4 I had the following problem with
kdm : it didn't start session that I choose before logging in (in the drop
down menu), but was starting the default session for my user.
I solved the problem by changing /etc/kde3/kdm/Xsession last line
. /etc/X1
On Monday 29 March 2004 09:07, Anders Ellenshøj Andersen wrote:
> On Monday 29 March 2004 08:43, you wrote:
> > On Sun, Mar 28, 2004 at 11:44:52PM +0200, Anders Ellensh?j Andersen wrote:
> > >With the amount of people who choke on this, there can't possible be a
> > > good enough excuse for it to n
On Tue March 30 2004 02:47 am, Anders Ellenshøj Andersen wrote:
] But in this case, since it worked before, some change must have been made
] upstream.
Indeed, and that would be my primary complaint about this one.
Keep in mind that I do agree, btw. I think kdm should, in the absence of
an
This I have dredged out of the archives - perhaps it explains something of the
problem.
David
-- Forwarded Message --
Subject: Re: KDM hang after login
Date: Tuesday 09 March 2004 13:52
From: Oswald Buddenhagen <[EMAIL PROTECTED]>
To: Debian KDE
On Tue, Mar 09, 2004 at 09:4
On Monday 29 March 2004 09:16, jedd wrote:
> ] I am perfectly capable of handling pretty much any kind of package
> breakage ] that únstable can throw at me.
>
> The question you posed a couple of days ago has cropped up on this list,
> promptly followed by an answer, about 11 times in the past
On Mon March 29 2004 05:16 pm, jedd wrote:
] the Debian developers -- backports of security & bug fixes are the obvious
s/developers/package maintainers/
Jedd.
On Mon March 29 2004 03:17 pm, Anders Ellenshøj Andersen wrote:
] On Monday 29 March 2004 00:48, Adeodato Simó wrote:
] > Hey, you're using unstable, aren't you? These are the kind of things
]
] I am perfectly capable of handling pretty much any kind of package breakage
] that únstable c
On Monday 29 March 2004 08:43, you wrote:
> On Sun, Mar 28, 2004 at 11:44:52PM +0200, Anders Ellensh?j Andersen wrote:
> >With the amount of people who choke on this, there can't possible be a
> > good enough excuse for it to not give you a kde session by default.
>
> I wholeheartedly agree. I've
On Monday 29 March 2004 00:48, Adeodato Simó wrote:
> Hey, you're using unstable, aren't you? These are the kind of things
I am perfectly capable of handling pretty much any kind of package breakage
that únstable can throw at me.
How applications choose to behave can't be Debian's problem.
* Anders Ellenshøj Andersen [Sun, 28 Mar 2004 23:44:52 +0200]:
> On Sunday 28 March 2004 23:34, David Pye wrote:
> > You need to manually set the session type to kde the first time.
> Well who got the bright idea to change this behaviour?
> With the amount of people who choke on this, there can't
On Sunday 28 March 2004 23:34, David Pye wrote:
> You need to manually set the session type to kde the first time.
Well who got the bright idea to change this behaviour?
With the amount of people who choke on this, there can't possible be a good
enough excuse for it to not give you a kde session
You need to manually set the session type to kde the first time.
Try reading the previous list postings to see if your problem has already been
experienced (Hint: It has, many times!).
David
On Sunday 28 March 2004 21:50, b wrote:
> First off, XDM and GDM work fine. I can log in with
> either,
First off, XDM and GDM work fine. I can log in with
either, see a splash screen, then get the regular KDE
desktop.
Whenever I opt for KDM, I get the login screen and the
splash, but after that all I get is my background
image and a console window. I can operate at the
console, but that's it.
Any
James,
The kdm hang is due (as earlier posts indicated) to an incompatibly
with newer versions of QT in Sid and possibly GCC 32 libs and has been
around for about a week. On my system SID KDM startup is 35 seconds.
(KDM startup on my woody system is 9 seconds). Be patient! I did see
that
I have upgraded to Karolina's new 3.1.0+rel kde debs on my Debian/Sid system.
With this upgrade, along came a problem with kdm. It seems there is a memory
leak. The kdm startup hangs in a loop and becomes very large in memory size;
never finishing. It is running the "kdm_greet" process. I j
I have upgraded today to the newest KDE 2.1.1 packages for Potato, and find a
couple of small problems with KDM.
- If I decide to use the new /etc/kde2/kdmrc instead of the old one I have, I
only get sessions for failsafe, and default. No session for kde2. I fix this
just by editing the file a
> "Oswald" == Oswald Buddenhagen <[EMAIL PROTECTED]> writes:
>> Feb 27 15:31:23 wrpc3 kdm[14964]: can't execute "XBINDIR/xrdb" (err 2)
>>
Oswald> huh? which version of kdm are you using? this has been fixed before
Oswald> the frist 2.1 prereleases, possibly even before 2.0.1.
ii kdm
> Feb 27 15:31:23 wrpc3 kdm[14964]: can't execute "XBINDIR/xrdb" (err 2)
>
huh? which version of kdm are you using? this has been fixed before
the frist 2.1 prereleases, possibly even before 2.0.1.
> Since the upgrade, when sending a URL to Netscape, I get a new
> Netscape started (complaining ab
re?).
Since the upgrade, when sending a URL to Netscape, I get a new
Netscape started (complaining about a Netscape allready running).
When tring by hand:
>netscape -remote "openURL(file://www/home.html,new-widow)"
netscape-remote: root window has no children on display :0.0
Can
21 matches
Mail list logo
