• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

(closed)lasma problem try to fix it but how? :fies:

S

schwabeMICHAEL

First I open the konsole in 10-20 second a window show up and I read a error:

! Sorry - Plasma Workspace
Error launching /home/michaelKanada/Desktop/konsole.desktop.
Either KLauncher is not running anymore, or it failed to start the application.

Second is when I reopen the Konsole and close it in 3-4 second later another error show up:

Sorry - Plasma Workspace
KDEInit could not launch '/opt/kde3/bin/konsole'.

Please could be someone be so kind and helping me out to try to fix the problem :???:

Thank you be so kind to try to helping me.

Mike
 
Hi,

did you try
ALT-F2 -> konsole or
ALT-F2 xterm

Does this work well ?

The error messages tells something about /opt/kde3, therefore i think it is a problem
with your path settings or with your settings for the program link.

If the ALT-F2 trick works, then you have to look for the right 'konsole.desktop' setting.
Unfortunately i have a problem with the power-supply of my KDE4 PC, so i can't look for
the right setting. I think it is something like KDE-Menü -> System -> Terminal -> Konsole (xterm)

But it would be better to help, if you told us more details about your system.

bye
 
longman schrieb:
Hi,

did you try
ALT-F2 -> konsole or
ALT-F2 xterm

Does this work well ?

The error messages tells something about /opt/kde3, therefore i think it is a problem
with your path settings or with your settings for the program link.

If the ALT-F2 trick works, then you have to look for the right 'konsole.desktop' setting.
Unfortunately i have a problem with the power-supply of my KDE4 PC, so i can't look for
the right setting. I think it is something like KDE-Menü -> System -> Terminal -> Konsole (xterm)

But it would be better to help, if you told us more details about your system.

bye
Zum Vergrößern anklicken....

I guess you like that my system is now kde4.13 and between 4.2.0.But when I update my KDE,log out and log in my both monitor was black,but I`m using KDE3,root working perfect.You can look in there http://www.linux-club.de/viewtopic.php?f=24&t=101608 and you will find more question,I hope you can help us in that thread.
How can I find out about my path setting in konsole?
You have problem with the power-supply that`s okay with,when you got lot of power for your computer,please give me a call. ;)

I can wait and thank you,you are so kind.

Mike
 
Plasma Workspace - The KDE Crash Handler

A Fatal Error Occurred
The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.

Code: 
Application: Plasma Workspace (plasma), signal SIGSEGV
 [?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb09c5b90 (LWP 4573)]
[New Thread 0xb23a7b90 (LWP 4572)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb5bcab97 in QGraphicsLinearLayout::insertItem(int, QGraphicsLayoutItem*)
    () from /usr/lib/libQtGui.so.4
#7  0xb2542b77 in ?? () from /usr/lib/kde4/plasma_applet_devicenotifier.so
#8  0xb2542d17 in ?? () from /usr/lib/kde4/plasma_applet_devicenotifier.so
#9  0xb7de7f35 in Plasma::Applet::flushPendingConstraintsEvents() ()
   from /usr/lib/libplasma.so.2
#10 0xb7de8576 in Plasma::Applet::timerEvent(QTimerEvent*) ()
   from /usr/lib/libplasma.so.2
#11 0xb5fd815f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#12 0xb5bce8b7 in QGraphicsWidget::event(QEvent*) ()
   from /usr/lib/libQtGui.so.4
#13 0xb556929c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#14 0xb557155e in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#15 0xb6a0ff7d in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdeui.so.5
#16 0xb5fc7abb in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQtCore.so.4
#17 0xb5ff5701 in ?? () from /usr/lib/libQtCore.so.4
#18 0xb5ff599b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#19 0xb5608f02 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb5fc60da in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0xb5fc651a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/libQtCore.so.4
#22 0xb6720adb in KIO::NetAccess::enter_loop() () from /usr/lib/libkio.so.5
#23 0xb6720cdc in KIO::NetAccess::statInternal(KUrl const&, int, KIO::NetAccess::StatSide, QWidget*) () from /usr/lib/libkio.so.5
#24 0xb672198b in KIO::NetAccess::stat(KUrl const&, KIO::UDSEntry&, QWidget*)
    () from /usr/lib/libkio.so.5
#25 0xb6721a0b in KIO::NetAccess::mostLocalUrl(KUrl const&, QWidget*) ()
   from /usr/lib/libkio.so.5
#26 0xb278160e in ?? () from /usr/lib/kde4/plasma_applet_icon.so
#27 0xb2781dff in ?? () from /usr/lib/kde4/plasma_applet_icon.so
#28 0xb7e11707 in Plasma::Corona::loadLayout(QString const&) ()
   from /usr/lib/libplasma.so.2
#29 0xb7e11ab1 in Plasma::Corona::initializeLayout(QString const&) ()
   from /usr/lib/libplasma.so.2
#30 0xb7f318d9 in ?? () from /usr/lib/libkdeinit4_plasma.so
#31 0xb7f33557 in ?? () from /usr/lib/libkdeinit4_plasma.so
#32 0xb7f33681 in ?? () from /usr/lib/libkdeinit4_plasma.so
#33 0xb7f2493a in kdemain () from /usr/lib/libkdeinit4_plasma.so
#34 0x08048852 in _start ()

I hope it will help more ;)
 
I still have the feeling that you completely messed up KDE4, propably by using wrong packages or risky repositories. Please post the output of

Code: 
zypper lr

...and tell us what sources you use beside those.
 
gropiuskalle schrieb:
I still have the feeling that you completely messed up KDE4, propably by using wrong packages or risky repositories. Please post the output of

Code: 
zypper lr

...and tell us what sources you use beside those.
Zum Vergrößern anklicken....

I delete some of the repositores and I hope I don`t screw up :???:

Code: 
michaelKanada@linux-rx4k:~> zypper lr
#  | Alias                              | Name                                        | Enabled | Refresh
---+------------------------------------+---------------------------------------------+---------+--------
1  | openSUSE 11.1-0                    | openSUSE 11.1-0                             | Yes     | No
2  | openSUSE_11.1                      | openSUSE_11.1                               | Yes     | Yes
3  | openSUSE_11.1_1                    | openSUSE_11.1                               | Yes     | Yes
4  | openSUSE_11.1_KDE4_Factory_Desktop | openSUSE_11.1_KDE4_Factory_Desktop          | Yes     | Yes
5  | repo-non-oss                       | openSUSE-11.1-Non-Oss                       | Yes     | Yes
6  | repo-oss                           | openSUSE-11.1-Oss                           | Yes     | Yes
7  | repo-source                        | openSUSE-11.1-Source                        | Yes     | Yes
8  | repo-update                        | openSUSE-11.1-Update                        | Yes     | Yes
9  | repo_1                             | Packman Repository                          | Yes     | Yes
10 | repo_3                             | openSUSE BuildService - Drivers for webcams | Yes     | Yes

I hope it helps you and I hope I don`t messed up :roll:
 
Your repo-list is in fact a mess... :) Yet I am not sure wether this is the cause for your trouble. It looks like you have many double-entries, look for the URLs in YaST and delete the doublettes. Deactivate the DVD-repo. Or simpler: use repos numbers four to ten only except for seven (its a doublette of number six), then do an update. What do one to three contain?

Don't you use any drivers for your graphic-card?
 
gropiuskalle schrieb:
Your repo-list is in fact a mess... :) Yet I am not sure wether this is the cause for your trouble. It looks like you have many double-entries, look for the URLs in YaST and delete the doublettes. Deactivate the DVD-repo. Or simpler: use repos numbers four to ten only except for seven (its a doublette of number six), then do an update. What do one to three contain?

Don't you use any drivers for your graphic-card?
Zum Vergrößern anklicken....
Your saying graphic-card? I don`t understand??? could you tell me more clearly about graphic-card?

cheers ;)
 
There is a nvidia graphic adaptor listet in your signature.
So gropiuskalle expected an driver repo for it.
Wich driver do you use - this from suse repo or did you compile NVIDIA-.... .run?

Gruß Ganymed
 
What the hell...?

Michael, you don't seem to take this board very serious. When opening a thread, you should follow the given suggestions - because if you don't, no one will be willing to help you.

I'm out. Good luck.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben