Bug#463305: kde4: Core Apps Crash Rendering Package Unusable)

2008-02-21 Thread David Baron
My daughter discovered this by accidentally starting a kde4 session with no a 
single crash at all!!

1. Must have a clean .kde4 on start! Even the one that I got by starting using 
sudo was not clean enough. Got rid of that. Viole.

2. Kicker and kdesktop will come up anyway, it seems (the old kde stuff is on 
the path to be able to run stuff like kmail). Currently, the session settings 
are not working? so the excluding them did not work and running apps were not 
restored on new login.

3. Desktop settings and themes were not fully honored, Icon choices for 
applications showed, for devices NO. I did succeed in getting smaller 
icons.

4. Konqueror could not access the internet--klauncher failed to make the 
connections, w or w/o proxy.

In terms of this bug:
1. Place notification in change/log or in the preinstall script for kde4 about 
having no preexisting .kde4 on first run (temping to copy .kde to get all 
ones settings-a no no. Copy certain config rc files, konqueror profiles, etc, 
later on.
2. Can close.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#463305: kde4: Core Apps Crash Rendering Package Unusable)

2008-02-10 Thread David Baron
Here is some more, possibly useful information:

Postings on kubuntu's lists complained of problems with dbus without root 
permissions. Kubuntu/ubuntu's approach to this is sudo only so becomes more 
problematic. On my Debian system:

1. Dbusd IS running, started on init. (Note: There is no udev rule and no /dev 
entry for dbus.)
2. However, two instances of dbus-launcher become stuck in memory when 
attempting to start kde4 as user, one by user and one by root!
3. Hal's udev rule calls for a certain socket. There is no such file on my 
system. The URI is NOT a /dev path.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#463305: kde4: Core Apps Crash Rendering Package Unusable)

2008-02-05 Thread David Baron
Here is some more, possibly useful information:

Run from a failsafe session in an xterm, sudo /usr/bin/startkde will bring 
up successfully a KDE4 session, no crashes, everything (currently 
implemented) there!

Run without root privileges, I get all the crashes.

Apparently, run from a KDM logon, startkde is run as the user logged on, not 
with root privileges.

Possibly the kde.desktop xsession can be rigged to run as root or all users 
that will be running kde4 can be sudo-enabled for that command and 
sudo /usr/bin/startkde placed there. However, this is not a pretty 
workaround as is, of course, dangerous.

Running the kde4 session this way had the following side-effects:

1. The $HOME/.ICE file had its ownership and/or permissions changed. A 
subsequent kde3.5 session (no root privileges) could not access it so 
immediately fails. Changed them back.

2. The $HOME/.DCOP. files were not available/dcop was not running so the 
session then fails. Went to a console an manually ran dcopserver. After this, 
I was able to run kde3.5 normally.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#463305: kde4: Core Apps Crash Rendering Package Unusable

2008-01-30 Thread David Baron
Package: kde4
Version: 1
Severity: grave
Justification: renders package unusable

Starting kde4, either from its /etc/init.d/kdm or from a failsafe session
running /usr/bin/startkde brings up a blue background then a series of
crashes:
kcminit (from kdm)
krunner (so no desktop)
plasma (so no panels)
kget (maybe because no panels)
knotify (repeatedly--I subsequently moved this out of the way)

Get the old kmail, functions OK.
Get a sporadically visible kmix icon, will tooltip the volume sometimes.

Can do nothing else but but end the session, either by exiting the console
in the failsafe session of killing kdm.

Note: With the supplied kdmrc path, a very ugly error message appears when
starting or stopping kdm:
Old kde does not end with /share/config, this can wreck havoc.
Replacing the path with one including this text eliminates the message.
Havoc was not caused.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (650, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23-rt1-davidb (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages kde4 depends on:
ii  extragear-plasma  4:4.0.0-1  extras for the desktop and panel u
ii  kde4-minimal  1  the K Desktop Environment 4, minim
ii  kdeadmin  4:4.0.0-1  system administration tools from t
ii  kdeartwork4:4.0.0-1  themes, styles and more from the o
ii  kdeedu4:4.0.0-1  educational apps from the official
ii  kdegames  4:4.0.0-1  games from the official KDE releas
ii  kdegraphics   4:4.0.0-2  Graphics applications from the off
ii  kdemultimedia 4:4.0.0-1  multimedia apps from the official 
ii  kdenetwork4:4.0.0-1  network-related apps from the offi
ii  kdeutils  4:4.0.0-1  general purpose utilities from the

kde4 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]