I learned that this is a two-fold problem.  Firstly, that device notifier does not find my camera when I turn it on, and secondly, that digikam 2.6* would crash when  I would use the GUI to detect my camera or:
digikam --detect-camera
I read somewhere that the first problem has been fixed in KDE 4.8.3 and doing further testing, I logged into my other distro that uses 4.8.3 version, and while 'top' was on, I turned camera on and plasma-desktop pops up at top of 'top'.  Doing the same in Pardus 4,8.2 doesn't, so I figure this is a plasma-desktop bug, part of kde-workspace.  
Now I have to go through all of my notes and see all that I needed for dependencies.  Pisi history and bash history will come in handy for that.  

Edited to add, bug 296778 is KDE bug report, and changing from 'removable devices' to 'all devices' solved it for me as well.  All is well for both problems.

Funny you should share that atolboo, because I was wondering about that two days ago, and I recall someone asked about, to help a newbie learn what commands you give to install a certain software.  In the end, I finally used
cmake /home/me/hand/digikam-2.9.0  -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..

I should have asked this first, as I could have saved a bit of time, but I learned some new things while I was searching for answers.
Thank you!
Regards, Lisa Marie

That looks great in that there is a road ahead and not a 'dead end'.  Richdb,  it is nice to read your blog about it. 
By the way, that is a nice looking desktop wallpaper! 
REgards, Lisa Marie

Those programs in above message didn't help me as I still needed digikam to capturethe pictures and I saw no where that Photivo would do this. 
I guess I wanted this badly and at the same time learned a bit more about compiling, with the result of a squeaky mouse from the sweat, and a stiff neck    I've never used cmake or qmake before.

I solved this by compiling digikam 2.9 tar, and in order to do that, I had to install many -dev files , as well as marble 4.8.2 tar, and that needed some things such as libkdeedu 4.8.2 and also from qt-mobility-opensource-src 1.0.2 tar, and that needed a few more things (devels) like  qt-labs-messaging-framework.  I also compiled qjson 0.7.1 (I think marble needed that?) and I removed kipi-plugins and let digikam install it from extras.  And, while I was at it, I compiled kgpg, kcalc, kwallet, ark, and superkaramba all 4.8.2.  I see I also compiled liblqr and again, I forget which software needed that.  I'm sure my builds are like meatloaf but at least my camera is now detected.  Now if I could only be as determined to learn how to make a pisi for all of these and let you test them.    Funny, whiile doing searches for all of my build failes, I found alexey's name in a search engine who was working on qt-mobility.  I'm learning that there are lots of qt stuff that kde relies on. 

Should have switched over to the pardususer depots as lo and behold, there is photivo, gphoto and maybe some other goodies that will solve my problem.  Thanks, pardususer folks!

Hi all,
I assume this is a problem with   KDE 4.8.2  such as when I updated to 4.8.2 some packages were removed, like kdegraphics 4.6.5.  There is no kdegraphics 4.8.2 as some changes  have been implemented during release of 4.7.  
Anyway, when I try:
digikam --detect-camera
it crashes digikam which uses libgphoto2 to find cameras.  Mine is a Picture Transfer Protocol type camera (ptp).  I was wondering if anyone else using ANKA has issues with digikam 2.6.0-beta2?  I've tried downgrading libghoto2 from 2.4.11 to 2.4.10  but that did not help.  So now I am about to try and compile digikam 2.9 source and also am looking at other image management software such as Photivo (nope, needs GCC 4.6), xnviewmp, fotoxx, and Bluemarine.  I'm also going to play with/compile the latest libgphoto2 to see if that will help.  It's difficult to say where this problem lies, whether it is from digikam, the libgphoto2, udev?  Camera detection problem has already been notified to Anka bug reporting.  Just wondering if anyone had any suggestions.
Lisa Marie

Well, I have computer speakers that are 2.1 and from reading, alsa doesn't configure these well as the subwoofer is tied to the two satellite speakers and you don't get surround but stereo.  I'm still not hearing anything from my subwoofer.  I have been reading, though, and there's this little command line program called
alsactl

I have the problem like some laptop users have mentioned, where alsamixer gets reset upon reboot or start of computer.  It always sets it back to the halfway level.

So,  you open 'alsamixer -c 0' in command line, or hit F6 to select your soundcard for 'alsamixer', again, with command line. 
Pull up those sliders to where you want them.  Esc.
Then in konsole enter:
sudo alsactl store
and the sound is at levels I set after reboot.  Okay, back to anka kernel work.  Hurray!  I'm being patient as just from looking at pantera's hat, I figure he has another job. 
Speaking of job, time to mow the lawn.

Someone has been very busy working on the anka kernel.  Much appreciated!  Though I cannot test it it is nice to know it continues to be worked on. 

And if I had paid attention to alsamixer menu, one can easily select their sound card by hitting F6. 

Hi,
Not meaning to usurp the 'replacement for Pardus threads'    but I have been working on the sound for my desktop computer, and didn't realize until this week that my woofer is not putting out any sound, only the two speakers on top of the desk. 

And, learned a trick that I found myself by typing in konsole:
alsamixer --help

and also saw something similar at the Fedora forum.

When I start alsamixer via the konsole, it shows PulseAudio as the card and would only show the Master, and not PCM, s/pdif, etc.   It should show card as CMI8788.  According to Fedora folks,  pulseaudio is the default for alsamixer. 
 
Doing the following command showed the correct output. 

alsamixer -c 0

which showed all outputs at halfway mark.  Still haven't figured out why my woofer isn't putting out sound, but at least I learned something new. 
To find out the card number, I guessed at it, but you can also see which you have by typing in konsole command:

aplay -l

Now, back to 'a replacement for Pardus'. 

I guess that is just what Pardus is for me, a show stopper.  I have Poca Mandriva Russian version installed, but I rarely log into it.  My first experience with Mandriva based OS and nothing against Poca, (their forum is quick to help you with a problem) but more a critique of Mandriva:   When you compare 'pisi history' verses 'rpm -qa --last | less', output if package upgrading/updating history,  pisi history is easier to read and shows previous version replaced by new version.  More informative.

anglo, I'm surprised you haven't tried Snowflake.  It is Debian-based, maybe that is why, but it implements the I17 desktop. 

I've eyed an os called AV Linux for folks that do a lot of audio and video work.  Still using Pardus, Pardus original on one partiton and Pardus Anka on another.

Yes. 
But using K3b to open file shows different md5sum: 07a901c84adbf1cce1d1c264b5ebf363
and as you said, there is no md5 or sha1 file to check or verify against.  K3b shows iso size as 1.2GB. 

TicoLinux, thank you for the feedback on this.  I was very much hoping it would have been that easy to fix, using an iso editor.  Wishful thinking.  If it is a tainted kernel, then it is beyond me, but I am hoping the folks that created the ANKA iso are working on it.  It would be sad to see all those Pisi repo packages go to waste.  . 

Thanks to my husband, I have the anka iso 1.2GB.  I have been tinkering with it using Ultimate Boot CD>Parted Magic>Iso Master to edit it by removing the initrd and replacing it with the one from the 2011.2 Pardus 64 bit install disc, but still hangs at initramfs shell.  I don't know where the problem lies with the no media found error.  I assume the kernel.  Looking forward to a working .iso, I can wait. 

I haven't tried using Unetbootin utility but I assume the same initramfs shell problem with it, too.
Lisa Marie

Old post but not an old subject as lately I have been trying to make the default fonts in Pardus 2011.2 look sharper.  I still do not know why the fonts are so crystal clear in Pardus with KDE 3.5.10 version as they are in Kurumsal and Pardus 2008 and not so in 2011.  Anyway I did try some of the suggestions posted by Freebird and didn't see much of a difference.  Instead, I changed the font.  I think the default is sans serif.  I now have Clockopia for toolbar and downloaded Zekton and use it for the taskbar.  Clockopia and Zekton look a bit similar.  I like them.  My eyes are getting worse the older I get, but changing the font is making a big difference for me.