I'm thinking of trying the KDE-Unstable, and I was just wondering what
to expect - is it really 'unstable' or just leading edge? I wouldn't
try it on my work machine, but wondering if it's usually okay on a
home machine, and any caveats I might could expect. Also, do I need to
enable both Testing and Unstable or just Unstable?
Thanks in advance!
Greetings for the day !!
I have 64 Bit Fedora Core 17 installed on my DELL Inspiron 15R laptop. I am facing laptop freezing
issues intermittently when I login using during KDE session. Can anybody please help me on this?
I have been noticing an issue with my Laptop (Dell XPS 1530M) touchpad
since F16 (now on F17). The issue is, on most occasions the touch-pad
is not detected after a reboot. The system settings in KDE/GNOME shows
'no device'. And on some rare occasions, device is detected fine and
everything works perfect.
Any ideas to resolve this issue.
After updating phonon-backend-gstreamer to 4.6.1 (using kde-testing
repo), Amarok is behaving weirdly:
* Every track in playlist is played twice.
* When you clean your playlist while playing some track and put
another tracks on it, sometimes Amarok continue to play tracks from
the former playlist.
I've reproduced the same symptoms on a co-worker's laptop. Removing
.kde/share/apps/amarok and .kde/share/config/amarok* do not fix it.
[christian@laptop ~]$ rpm -q amarok phonon-backend-gstreamer kdelibs
My guess is that this bug is related to "gapless" feature included in
phonon-gstreamer , but I'm not sure about that. Others music
players (Clementine, Tepsonic, qmmp, YaRock, Banshee) are OK.
Is there somebody seeing the same problem? Should I file a bug against
phonon-gstreamer or Amarok?
Christian González G.
I have this issue where I set up a wireless (system) connection using WEP. The
wireless works when it works but at some point, I get a prompt to re-enter the
passphrase *but* no matter what I do, I can't enter anything.
This request from secrets locks me out completely and is annoying because the
only way I know how to solve it, is to reboot. Fedora is completely up to date
using KDE 4.8.4. I'm not sure what to do *but* I am convinced the problem is
in the network manager.
Thank you for your time.
Victor B. Gonzalez