I have the same entry in my syslog with:

Card:ATI Radeon HD 5000 to HD 6300 (radeon/fglrx): Advanced Micro Devices [AMD] nee ATI|Cape Verde XT [Radeon HD 7770 GHz Edition] [DISPLAY_VGA] (vendor:1002 device:683d subv:1458 subd:2556)

CC: (none) => curtis_mageia

I should add that I receive the error just as VirtualBox starts running a Vista vdi.  2D Video Acceleration is checked-- 3D Acceleration is option is disabled.

I have X crash about every 5 hours i use proprietary driver.

(Which means I now almost always use xorg ati where system is stable.)

Seem to be when i switch to or start an app in kde. Last time when clicking to start Firefox.

Unfortunately i was eager to log back in to reconstruct my work from what i still had between my ears (yes i run cauldron on my main workstation!), and then i notise .xsession-errors from last session seem not to be backed up? I just find the current session log (which by the way is not very pretty...) (or where should previous be?)

In /var/log/kernel/info.log i see lines like this
  kernel: <4> <3>[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize fail.
They come in groups of five on same second, with sometimes one or a few minutes between (possibly short after startup) ans it can take many hours berween too.


I now updated to run the new kernel 3.8.13-1 and ATI driver and see if it is stable.  (i have tried the two last versions)

My video card use Radeon HD 6850
Driver:ATI Radeon HD 6400 and later (radeon/fglrx)
CPU: Intel i7,  Desktop: KDE

CC: (none) => fri

(In reply to Morgan Leijström from comment #3)
> I have X crash about every 5 hours i use proprietary driver.
> Seem to be when i switch to or start an app in kde. 

I have yet to see that problem. Difference I see is I have a clean/fresh install, new $HOME, run level 3, running gdm as my display manager.

$  cat /etc/sysconfig/desktop
DISPLAYMANAGER=gdm
DESKTOP=KDE4

and heavily modified KDE environment.  

> Unfortunately i was eager to log back in to reconstruct my work from what i
> still had between my ears (yes i run cauldron on my main workstation!),

All 3 of my systems are cauldron.

> then i notise .xsession-errors from last session seem not to be backed up?

That file is not backed up. You get a new one on each KDE log in.
Guessing you thinking about /var/log/Xorg*

If you want a backup copy you would have to make one via a script you create in
~/.kde4/shutdown/

I created ~/.kde4/Autostart/starup which does a
#!/bin/bash
/bin/cp $HOME/.xsession-errors $HOME/.xsession-errors_login

so I do not have to scroll through all the junk I generate during the day.

> just find the current session log (which by the way is not very pretty...)
> (or where should previous be?)
> 
> In /var/log/kernel/info.log i see lines like this
>   kernel: <4> <3>[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize
> fail.

Now that is sad. It appears you have rsyslog running. Maga3 does not install that by default. You are supposed to be using journalctl to see system logs.


> They come in groups of five on same second, with sometimes one or a few
> minutes between (possibly short after startup) ans it can take many hours
> berween too.

Yep, snippet from mine
# journalctl | grep loadDatabase
May 14 19:37:58 
May 14 19:37:58 
May 14 19:38:20 
May 14 19:38:20 
May 14 19:40:26 
May 14 19:40:26 
May 14 19:45:18 
May 14 19:45:18 
May 14 19:56:46 
May 14 19:56:46 
May 14 20:32:10 
May 14 20:32:10 
May 14 21:57:19 
May 14 21:57:19 
May 15 08:35:35 
May 15 08:35:35 
May 15 08:41:21 
May 15 08:41:21 
May 15 08:44:53 
May 15 08:44:53 

I start new logs prior to each reboot.

> 
> I now updated to run the new kernel 3.8.13-1 and ATI driver and see if it is
> stable.  (i have tried the two last versions)
> 
> My video card use Radeon HD 6850
> Driver:ATI Radeon HD 6400 and later (radeon/fglrx)
> CPU: Intel i7,  Desktop: KDE

OOPS, the newer version hang system, Bug 10104.
Changed to Radeon HD 5000 and later, system works stable
And my VT are not garbled, Bug 10033
Still same *ERROR* APL: apl initialize fail

Thank you for the tips, Bit Twister!

Hi
I have the same Error message, Kde freeze and system is slow, gnome is ok.
I don't have an journalctl rpm, only python-journalctl.
I need to uninstall rsyslog rpm?

CC: (none) => surfzoid

sorry, i forget, i'm runing Mageia 3 official, was an update from Mageia2 using mgaaplet.

The "[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize fail." error is fixed in the newly released fglrx 13.6 beta....

When it gets to final status we can push it as an update for mga3

can i install only fglrx 13.6 beta and if yes, from where?

seeing this error on a clean Mageia 3 install.

is 13.6 beta likely to be in testing / backports soon?

CC: (none) => nelg

(In reply to Glen Ogilvie from comment #10)
> seeing this error on a clean Mageia 3 install.
> 
> is 13.6 beta likely to be in testing / backports soon?

I rebuilt from cauldron.   Had to fully remove fglrx, then installed the cauldron version.  Much better results, IE, this specific error seems to be resolved.

Eric, if you want to do the same, the actions I took were:

download: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/SRPMS/nonfree/release/fglrx-13.101-0.2.mga4.nonfree.src.rpm

as yourself: rpm -Uvh fglrx-13.101-0.2.mga4.nonfree.src.rp

as root: urpmi rpm-build
as root: urpmi rpmbuild/SPECS/fglrx.spec (build deps)
as yourself: cd rpmbuild/SPECS/
as yourself: rpmbuild -ba fglrx.spec

then install the packages from: rpmbuild/RPMS/x86_64/

you will end up with a water mark, unless /etc/ati/signature is updated.

Hi
I'm just back from Nigeria and will test that, thanks for the tip!

I installed the beta fglrx to attemp to fix an apparently related konsole/kdeinit/qt segfault issue..(I suspect the real issue was in fglrx)

Haven't been running it long enough to confirm it fixed _everything_, but ATI fixed SOMETHING significant as it runs like a completely different, much faster machine.

CC: (none) => gjmcgee

Very funny, today mageia update give me the update of fglrx 12.104, after wath cairo-dock -o made segfault and cairo-dock -C was ok, Enmy territory stoped to work and many other X problem
I did an urpme -a fglrx, downloaded the last amd driver for AMD website, it was the 12.104 too, installed it and everything was ok.
I don't understan wath differ between RPM and .run file of AMD

Since problem has disappeared from my systems, I'm closing this.
If anyone else still has problems, I suggest a new bug report.

Status: NEW => RESOLVED
CC: (none) => junknospam
Resolution: (none) => FIXED