It's not clear to me which screen you mean by "first screen".
Is this the first screen or one of the screens of Kaptan

How can I set up a different wallpaper for each of the four virtual desktops? At the moment all desktops have the same backdrop.

good morning maurice,

sad to see your troubles are so persistent. alas i can't provide you with an solution neither.
one thing i found are updated iso's of 2011, you'll find them here.

p.s. i'm going to try and install the minimal 2011 and build from there.

Good Morning,
Maurice, to link your bug report, go to where the bug report is (launchpad?)  double-click on the URL  which will select all of it, copy, then open new browser window or tab and open Pardus forum,  then past it here in one of your threads, which will hot link it.

I think we are getting somewhere.  Looking at your snippet, that shouldn't be the output if you are running NetworkManager.  I get that output when I totally disable NM which I can get away with since I don't have to use it with dial up. (Note:  I'm assuming after the previous threads where I asked you to try something, that you have reverted back to the default, such as when I asked you to start HAL.  Just to make sure you return these test settings back to their defaults before you try more tests, makes it easier to debug.)

I did a search for acpid not exiting and came back to this Arch thread.  Someone there has the same board as you.  So, read it over and try blacklisting one of the suggested ethernet modules.  I couldn't go to the kernel bug link that was posted, for some odd reason, so I couldn't read it.  Here's the Arch thread
Looking at your manual, you have "lan support intel 824566DC gigabit ethernet controller".  
I think you can test this by going into your computer BIOS and disabling the ethernet controller as tried here
Let's hope.  

Hi Maurice,
No, it doesn't tell me anything.

Glad to hear you took the time to place a bug report for it, in case any others are having similar problem with similar hardware, it will help them, too.  If you want, you can share the bug report link here and then if you post any of your /var/log files to it (upload them as .txt, which you should do) then we can look at them there, for as you know they can spit out quite a lot of information.  

We also have to take into account your processors.  I was looking at your pcLinuxos forum thread and the output of ACPI, and it just seemed strange that your four cores were showing up twice.  Maybe that's normal.  Thanks to your thread and looking up your problem I am learning new ways to check on hardware, as I installed "lshw" that was recommended in earlier page.  Another good on to install via PiSi is "sysstat".  After you install it, do:

Also do the following to show if you have four folders for each core:
Mine shows cpu0 as I have only one processor one core.  You should have cpu0 cpu1 cpu2 cpu3.
I got this information from ubuntu forum here.  

Also, look in your BIOS to check the ACPI settings and the power settings to see if something there can be enabled/disabled, then boot into Pardus and shutdown and see what happens.    

I'm trying to find that singular post at the intel forum where someone had same board as you, updated their BIOS and said they could no longer shutdown in kernels 2.6.34. to 2.6.37.  No one replied to that person.  
Lisa Marie
P.S. For grins, you might create a second user and add them to wheel group which gives them administrative rights.  Go to system settings>user manager>add user>enter name and password, then click on Advanced> and tick "give administrator rights", Apply and reboot into the new user and try shutdown.  Just a suggestion.  You can always delete that user after testing it out.
 

The link is http://www.intel.com/p/en_US/support/highlights/dsktpboards/dg33fb/

good morning maurice,

- maybe you can adjust displayed font size in system settings /  application appearance / fonts (e.g. set them all to 10).
- or you could right click on a log file and select 'save as...' and save it as logname.txt so you can open it in a text editor.

On a side note, I found a much easier way to look over the log files and it can be found in this GUI: System>System Log Viewer, which you enter your administrator/root password to unlock.  The fonts and colours are easier on my eyes and you can easily do a search using the search field.  In system log, it should show the previous days shutdown.  You can look these logs over for any relevant stuff, maybe acpi related, memory related, or cpu, such as, if the quad cores are handled correctly. 
Another idea is to go to the Intel forum and write up a thread about this problem.  There might be another user there that has similar or same hardware using Linux, especially recent kernels. 

When you are going to report this in Bugzilla also do give the exact (typenumber and link) of the used motherboard.

That's correct.
Apply the OK button.
After this the main Boot Manager screen should appear again and check in konsole with