Bug 320674

Created attachment 80280 [details]
Live CD PCLinux KDE Daemon startup load error

Screenshot of Error

> "install debugger package" (gdb)"

I never use PCLinux, so I don't know how. But gdb is available in most distributions. In Debian/Ubuntu, just run "apt-get install gdb" as root.  Ask PCLinux guys for the equvalent command.

Contents of Crash Report:
Application: kded4 ($Id$)
KDE Platform Version: 4.9.5
Qt Version: 4.8.4
Operating System: Linux 3.2.18-pclos2.bfs i686
Distribution: "PCLinuxOS"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/

You need to first install gdb before you can get any useful backtrace.

Yes, I know, and I searched for it within  PC Linux with no luck. Also
searched on the web for the file with no results.
I am an old Windows XP user and am very new to Linux but smart enough to
know support for XP soon runs out. I
don't like the new Windows OSs so I am trying to learn about Linux. Tried
the Mint,Puppy, React & Knoppix versions.
 The one I seem to like best is the PCLinux if I can just get this issue
resolved.
Your Responses are Appreciated!
Thank You!


On Wed, Jun 5, 2013 at 12:20 AM, Jekyll Wu <adaptee@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=320674
>
> --- Comment #4 from Jekyll Wu <adaptee@gmail.com> ---
> You need to first install gdb before you can get any useful backtrace.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

OK, I just download a PCLinux LiveCD iso and boot it in the virtualbox.  Here is the step to install gdb in konsole :

$ su -l
<enter the password of root, which is also root>
# apt-get update
# apt-get install gdb 

That is it. DrKonqi should be able to generate a backtrace now. 

However, you are unlikely to get a high quality backtrace without installing debug symbols.  That task really needs  help from someone who really uses PCLinux.

Created attachment 80318 [details]
Crash Report

Finely got (gdb) report.
Need Someone to tell how to install debug symbols or forward to a PCLinux user to analyze  error.
Many Thanks to: Jekyll Wu for previous help     A+++Help

> #7  0xb7726424 in __kernel_vsyscall ()
> #8  0xb5d68311 in raise () from /lib/i686/libc.so.6
> #9  0xb5d69e3e in abort () from /lib/i686/libc.so.6
> #10 0xb5d60c28 in __assert_fail () from /lib/i686/libc.so.6
> #11 0xad755461 in snd_hctl_handle_events () from /usr/lib/libasound.so.2
> #12 0xad762bc1 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
> #13 0xad832698 in ?? () from /union/usr/lib/kde4/kded_kmixd.so
> #14 0xad8299f5 in ?? () from /union/usr/lib/kde4/kded_kmixd.so
> #15 0xad829900 in ?? () from /union/usr/lib/kde4/kded_kmixd.so

Thanks. This looks like a duplicate of bug 209975.  The problem is in alsa-lib, out of the scope of KDE developers. So nothing can be done here to solve the problem, except ensuring the alsa-lib installed in your system is recent enough to contain the fix. 

See https://bugs.kde.org/show_bug.cgi?id=209975#c137 , https://bugs.kde.org/show_bug.cgi?id=209975#c129 and https://bugs.kde.org/show_bug.cgi?id=209975#c126 .

*** This bug has been marked as a duplicate of bug 209975 ***

Maybe I'm just stupid, but why in the world can't the KDE program be
"uninstalled" and an updated version be
installed that includes the repair? Seems to me to be a much easier
solution than going through all the technical stuff.


On Wed, Jun 5, 2013 at 8:57 PM, Jekyll Wu <adaptee@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=320674
>
> Jekyll Wu <adaptee@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|---                         |DUPLICATE
>
> --- Comment #8 from Jekyll Wu <adaptee@gmail.com> ---
> > #7  0xb7726424 in __kernel_vsyscall ()
> > #8  0xb5d68311 in raise () from /lib/i686/libc.so.6
> > #9  0xb5d69e3e in abort () from /lib/i686/libc.so.6
> > #10 0xb5d60c28 in __assert_fail () from /lib/i686/libc.so.6
> > #11 0xad755461 in snd_hctl_handle_events () from /usr/lib/libasound.so.2
> > #12 0xad762bc1 in snd_mixer_handle_events () from /usr/lib/libasound.so.2
> > #13 0xad832698 in ?? () from /union/usr/lib/kde4/kded_kmixd.so
> > #14 0xad8299f5 in ?? () from /union/usr/lib/kde4/kded_kmixd.so
> > #15 0xad829900 in ?? () from /union/usr/lib/kde4/kded_kmixd.so
>
> Thanks. This looks like a duplicate of bug 209975.  The problem is in
> alsa-lib,
> out of the scope of KDE developers. So nothing can be done here to solve
> the
> problem, except ensuring the alsa-lib installed in your system is recent
> enough
> to contain the fix.
>
> See https://bugs.kde.org/show_bug.cgi?id=209975#c137 ,
> https://bugs.kde.org/show_bug.cgi?id=209975#c129 and
> https://bugs.kde.org/show_bug.cgi?id=209975#c126 .
>
> *** This bug has been marked as a duplicate of bug 209975 ***
>
> --
> You are receiving this mail because:
> You reported the bug.
>

> why in the world can't the KDE program be "uninstalled" and an updated version be installed that includes the repair?

In this case, you would need updated ALSA software, which is responsible for audio, so just updating KDE would not help.

The problem with many Linux distributions is that they not only ship KDE, but thousands of other applications, such as web browsers, networking tools, graphics software etc., so updates to the software are only happening when a new version of the distribution is released, not for each application update separately.

There are, however, distributions available, that are much faster to include newer versions, such as Arch or Gentoo (those are called "rolling distributions"). These distributions are not as easy to use for beginners, but if you are, as you said, willing to learn, they could be less trouble in the long run.