[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#463305: marked as done (kde4: Core Apps Crash Rendering Package Unusable)

Your message dated Tue, 8 Jul 2008 23:28:57 +0200
with message-id <20080708212857.GA23738@ana.debian.net>
and subject line Re: Bug#463305: kde4: Core Apps Crash Rendering Package Unusable)
has caused the Debian Bug report #463305,
regarding kde4: Core Apps Crash Rendering Package Unusable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

463305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463305
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
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  kdeartwork                    4:4.0.0-1  themes, styles and more from the o
ii  kdeedu                        4: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  kdenetwork                    4: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

--- End Message ---
--- Begin Message ---
On Thu, Feb 21, 2008 at 06:50:52PM +0200, David Baron wrote:
> 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.

Ok, situation is now very different with KDE 4.1 pre-release (this bug was
filed against KDE 4.0)


--- End Message ---

Reply to: