Image 01
profile-image

portdavenport

David Michael Chen
KPager2 for Kicker

Various KDE 1.-4. Improvements by lucher 176 comments

Kpager2 Issue Observation in Suse 9.3 Professional KDE 3.4
- David Michael Chen (davidmichaelchen@hotmail.com) (Australia)

How to reproduce the error and temporarily load the Kpager.

Step 1: Move the KDE Kicker to the top of the desktop
> right click on the bottom or main Kicker > select configure >

Step 2: Load the Mac OSX Styled Bar
> Control Center > Desktop > Behaviour > Menu Bar at the Top of the Screen
> Select Current application's menu bar (Mac OS-style)
(NB. The Current Application's Menu Bar and the Main KDE Kicker should now appear together at the top of the screen)

Step 3: Load an applet into the 'Current application's menu bar'
> Current Applications' Menu Bar > right click > Add to panel > applet > i.e. try selecting 'clock' for example
(NB. you should now see a digital clock in the Current Apps Menu Bar)

Step 4: Remove the clock applet from the 'Current Apps Menu Bar'
> Current Application's Menu Bar > right click > Remove from panel > applet > select clock (NB. you should now see the clock actually drop underneath the Current Apps Menu Bar (instead of removing it). A space seems to appear between the 'Current Apps Menu Bar' and the 'KDE Kicker').

Step 5: Disable the 'Current Applications Menu Bar' to create a KDE error that will enable you to temporarily load the Kpager2 in 3.4.
> Control Center > Desktop > Behaviour > Menu Bar at the Top of the Screen
> Select None
(NB. The Current Application's Menu Bar and the 'Main KDE Kicker' should now both crash for a few seconds before the KDE Kicker will appear as normal. The KDE Crash Handler window should now appear with a error message.
------------------
Short Description
The application KDE Panel (kicker) crashed and caused the signal 11 (SIGSEGV).

What is This?
An application mostly recieves the SIGSEGV signal due to a bug in the application. The application was asked to save documents.

What can I do?
You might want to send a bug report for this application. Check if it is listed on http://bugs.kde.org, otherwise mail the author. Please included as much information as possible, maybe the original documents. If your have a way to reproduce the error, include this also.
-------------------
NB. I have saved a backtrace report generated from the SIGSEGV bug in the following text file: Kpager2 Issue - Backtrace.txt | Email me if you would like it.
-------------------

STEP 6: Now you can temporarily Load Kpager2 into the Kicker of KDE3.4
> right click Main Kicker > Add to Panel > applet > kpager2
(NB. Kpager will now run until you end or restart your session--after a reboot or x-server restart it will be missing again. If you try to reload the applet it will fail in KDE 3.4 (Distro used in this example: SuSE 9.3 Pro DVD Version running in 32bit mode) - May 07 2005
KPager2 for Kicker

Various KDE 1.-4. Improvements by lucher 176 comments

Kpager2 Issue Observation in Suse 9.3 Professional KDE 3.4
- David Michael Chen (davidmichaelchen@hotmail.com) (Australia)

How to reproduce the error and temporarily load the Kpager.

Step 1: Move the KDE Kicker to the top of the desktop
> right click on the bottom or main Kicker > select configure >

Step 2: Load the Mac OSX Styled Bar
> Control Center > Desktop > Behaviour > Menu Bar at the Top of the Screen
> Select Current application's menu bar (Mac OS-style)
(NB. The Current Application's Menu Bar and the Main KDE Kicker should now appear together at the top of the screen)

Step 3: Load an applet into the 'Current application's menu bar'
> Current Applications' Menu Bar > right click > Add to panel > applet > i.e. try selecting 'clock' for example
(NB. you should now see a digital clock in the Current Apps Menu Bar)

Step 4: Remove the clock applet from the 'Current Apps Menu Bar'
> Current Application's Menu Bar > right click > Remove from panel > applet > select clock (NB. you should now see the clock actually drop underneath the Current Apps Menu Bar (instead of removing it). A space seems to appear between the 'Current Apps Menu Bar' and the 'KDE Kicker').

Step 5: Disable the 'Current Applications Menu Bar' to create a KDE error that will enable you to temporarily load the Kpager2 in 3.4.
> Control Center > Desktop > Behaviour > Menu Bar at the Top of the Screen
> Select None
(NB. The Current Application's Menu Bar and the 'Main KDE Kicker' should now both crash for a few seconds before the KDE Kicker will appear as normal. The KDE Crash Handler window should now appear with a error message.
------------------
Short Description
The application KDE Panel (kicker) crashed and caused the signal 11 (SIGSEGV).

What is This?
An application mostly recieves the SIGSEGV signal due to a bug in the application. The application was asked to save documents.

What can I do?
You might want to send a bug report for this application. Check if it is listed on http://bugs.kde.org, otherwise mail the author. Please included as much information as possible, maybe the original documents. If your have a way to reproduce the error, include this also.
-------------------
NB. I have saved a backtrace report generated from the SIGSEGV bug in the following text file: Kpager2 Issue - Backtrace.txt | Email me if you would like it.
-------------------

STEP 6: Now you can temporarily Load Kpager2 into the Kicker of KDE3.4
> right click Main Kicker > Add to Panel > applet > kpager2
(NB. Kpager will now run until you end or restart your session--after a reboot or x-server restart it will be missing again. If you try to reload the applet it will fail in KDE 3.4 (Distro used in this example: SuSE 9.3 Pro DVD Version running in 32bit mode) - May 07 2005