Hi,

I'm having problems with the newest kernel "vmlinuz-2.4.18-17.7.x". Mostly related to the GUI. For example, when pushing the scrollbars, you don't see that the button is pressed and you have to press it several times in order to scroll the document. The buttons in the start menu have also a similar behavior and the Alarm Daemon doesn't tigger the tasks that you create. I switched again to my old kernel "vmlinuz-2.4.18-3" and everything works fine.

Somebody told me that graphic problems aren't not related to kernels, but then why everything works perfect with my old kernel?

Regards,
Josef.

Was your original kernel the stock build or did you have to do some tweaking? What video card are you using? How did you upgrade to the latest, was it through the RHN or did you download source and compile?

-----------
Jeremiah

My original kernel is the one that comes with the Installation CDs and I didn't have any problem with it.

I'm using an ATI 3D Rage Pro AGP 2x - 4Mb. After I read your message, I used the Xconfigurator to reconfigure it. Now everything, except the Kalarm program, works perfect. One thing I didn't like is that Xconfigurator said that it was going to restart X, but I only could see the mouse pointer (an X) and a gray background. So, I had to turn my computer off. Afterwards I logged as root and did it again and it works. So, I guess that it means that you have to login as root and that you can't just use "su" to run Xconfigurator.


I did it through the RHN.

What can be the problem with Kalarm? The events aren't trigged if I log out and come back. My configuration is the following:

1) Run continuosly in system try:
- Autostart at login (checked)
- Disable alarms while not running (unchecked)

2) System tray icon update interval [seconds]: 10

For the alarm daemon I have:
1) Start alarm daemon automatically at login (checked)
- Check interval [minutes]: 1

It sounds like only the window manager started, not the kde or gnome session. This most likely was a simple glitch. Also depending on how you did "su" it might not have picked up the correct environment settings. Did you do "su -" or just "su"? If you just did su, then you might have an .xinitrc file in the home dir. of the user that you were logged in as.



I haven't used kalarm, so I can't help you much 1here.

Jeremiah