Prev: problems using wicd on WPA2 secured networks
Next: Warning: "Illegal" hostnames no longer work
From: Rémi Moyen on 19 Jan 2010 06:20
Hi all,

(this is my first post on this list, please excuse me if I make any mistakes...)

I have a Debian testing system on which for a long time I kept old KDE
3.5 packages because I didn't want KDE 4 (I tried it around 4.0,
didn't like), I figured it was time I gave it another try. So after an
aptitude update, I did an aptitude dist-upgrade (something I hadn't
done since at least 6-12 months -- I did a number of updates of
specific packages in the mean time, though).

aptitude offered me a solution which required removing a lot of
packages (old KDE 3.5 ones), installing a lot of new ones, and
updating some. The install went fine, without any error messages. I
now have a bunch of KDE 4.3.1 packages (version 4:4.3.4-1, the latest
in squeeze).

I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
and logged in... only to see kdm pop again! No error message. I'm not
on this computer right now, but there wasn't any error message (nor
anything that looked even remotely related) in /var/log/kdm.log. In
the console, though, I can see when launching kdm some messages (sorry
for not having copied down the exact formulation) along the line of
"cannot copy file /etc/kde4/kdm/Xsession".

Now, I looked at the kdm package. dpkg -L told me that it provides a
number of files in /etc/kde4/kdm/ (including kdmrc, but also Xsession
and others). However, my /etc/kde4/kdm/ only contains kdmrc, no other
files. I tried aptitude reinstall kdm, deleting the .deb file in
/var/cache/apt/archives first to force a new download, I got the same
result. The .deb file apparently contains these files (at least I see
these files with a dpkg-deb -x), but for some reason they are not
extracted (and my disk is far from full)!

Just to try, I manually copied these files from the dpk-deb -x result
to /etc/kde4/kdm, but I still got exactly the same behaviour, so I
guess there is something more. Nonetheless, it shows that these files
really exist in the .deb, so why are they not extracted?

I also tried removing all packages in my system that seemed related to
KDE and re-installing kde-full (which dragged along all KDE, including
kdm), because it seemed I had a lot of old KDE 3 stuff hanging around
(and a lot of other junk I hadn't used for a long time, like compiz,
so a bit of house-cleaning was not useless...), but I still get the
same behaviour.

Does anybody have an idea of what's going on with this package, or of
any tests I could run to find the problem?

Thanks!
--
Rémi Moyen


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Thierry Chatelet on 19 Jan 2010 06:50
On Tuesday 19 January 2010 12:09:47 Rémi Moyen wrote:
> Hi all,
>
> (this is my first post on this list, please excuse me if I make any
> mistakes...)
>
> I have a Debian testing system on which for a long time I kept old KDE
> 3.5 packages because I didn't want KDE 4 (I tried it around 4.0,
> didn't like), I figured it was time I gave it another try. So after an
> aptitude update, I did an aptitude dist-upgrade (something I hadn't
> done since at least 6-12 months -- I did a number of updates of
> specific packages in the mean time, though).
>
> aptitude offered me a solution which required removing a lot of
> packages (old KDE 3.5 ones), installing a lot of new ones, and
> updating some. The install went fine, without any error messages. I
> now have a bunch of KDE 4.3.1 packages (version 4:4.3.4-1, the latest
> in squeeze).
>
> I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
> and logged in... only to see kdm pop again! No error message. I'm not
> on this computer right now, but there wasn't any error message (nor
> anything that looked even remotely related) in /var/log/kdm.log. In
> the console, though, I can see when launching kdm some messages (sorry
> for not having copied down the exact formulation) along the line of
> "cannot copy file /etc/kde4/kdm/Xsession".
>

This is a bug in kdm squeeze and sid. You have to log twice and it will work.
Thierry


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Rémi Moyen on 19 Jan 2010 07:00
2010/1/19 Thierry Chatelet <tchatelet(a)free.fr>:

>> I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
>> and logged in... only to see kdm pop again! No error message.

> This is a bug in kdm squeeze and sid. You have to log twice and it will work.

Yeah, I saw reports of that bug. However, I'm quite sure I tried a
number of times (in case I had mis-typed my password) and I get the
same behaviour again and again. Well, I'll try that again next time
I'm close to the computer, just to be sure.

Anyway, I didn't find on the web anything related to the missing files
in /etc/kde4/kdm (and perhaps in other places, I just happened to
notice these ones). So my guess is that something else is wrong. No?
--
Rémi Moyen


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Pier Paolo on 19 Jan 2010 07:10
Il giorno mar, 19/01/2010 alle 12.45 +0100, Thierry Chatelet ha scritto:
> On Tuesday 19 January 2010 12:09:47 Rémi Moyen wrote:
> > Hi all,
> >
> > (this is my first post on this list, please excuse me if I make any
> > mistakes...)
> >
> > I have a Debian testing system on which for a long time I kept old KDE
> > 3.5 packages because I didn't want KDE 4 (I tried it around 4.0,
> > didn't like), I figured it was time I gave it another try. So after an
> > aptitude update, I did an aptitude dist-upgrade (something I hadn't
> > done since at least 6-12 months -- I did a number of updates of
> > specific packages in the mean time, though).
> >
> > aptitude offered me a solution which required removing a lot of
> > packages (old KDE 3.5 ones), installing a lot of new ones, and
> > updating some. The install went fine, without any error messages. I
> > now have a bunch of KDE 4.3.1 packages (version 4:4.3.4-1, the latest
> > in squeeze).
> >
> > I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
> > and logged in... only to see kdm pop again! No error message. I'm not
> > on this computer right now, but there wasn't any error message (nor
> > anything that looked even remotely related) in /var/log/kdm.log. In
> > the console, though, I can see when launching kdm some messages (sorry
> > for not having copied down the exact formulation) along the line of
> > "cannot copy file /etc/kde4/kdm/Xsession".
> >
>
> This is a bug in kdm squeeze and sid. You have to log twice and it will work.
> Thierry
>
>
It is a problem between kdm and policykit, there is a bug open, either
in kde and debian i think, search kdm policykit.
Now i am i lenny/gnome,kdm-double-login was just the last annoyance with
sid/kde-4.3.4. Actually looked for xdm, but it's an ugly workaround

Maybe the situation evolved in last month


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Rémi Moyen on 19 Jan 2010 08:20
2010/1/19 Pier Paolo <pierpaolo.franco(a)gmail.com>:

>> > I rebooted, got to the kdm welcome screen, obviously in KDE 4 style,
>> > and logged in... only to see kdm pop again! No error message. I'm not
>> > on this computer right now, but there wasn't any error message (nor
>> > anything that looked even remotely related) in /var/log/kdm.log. In
>> > the console, though, I can see when launching kdm some messages (sorry
>> > for not having copied down the exact formulation) along the line of
>> > "cannot copy file /etc/kde4/kdm/Xsession".
>> >
>>
>> This is a bug in kdm squeeze and sid. You have to log twice and it will work.
>> Thierry
>>
>>
> It is a problem between kdm and policykit, there is a bug open, either
> in kde and debian i think, search kdm policykit.

Hmmm... thanks for the pointer, but again, I don't see any cases where
there are missing files from the package. There seem, however, to be
indeed a problem with kdm/policykit.

Well, I'll look into it, but if I don't find a solution, I guess I'll
have to downgrade to 3.5 again (stable should do the trick).
--
Rémi Moyen


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
 |  Next  |  Last
Pages: 1 2
Prev: problems using wicd on WPA2 secured networks
Next: Warning: "Illegal" hostnames no longer work