Topic locked

Amarok 2.3, full screen does not appear

User avatar manchette
Registered Member
Posts
225
Karma
0
OS
Hi,

i can't have full screen with amarok 2.3

how come ?

using suse 11.3 , kde 4.4 and nouveau driver for nvidia

thanks ;)

Image


manchette, proud to be a member of KDE forums since 2008-Oct.
last openSUSE version : 13.1... / Last Kde version : 4.12.0 ...
User avatar Mamarok
Manager
Posts
2922
Karma
8
OS
Well, you should probably restart it, looks odd. Also, upgrading to Amarok 2.3.1 is a good idea, it must be somewhere in additional repositories for OpenSuSE.

If that doesn't help, removing your $HOME/.kde4/share/config/amarok* files is worth a shot


Mamarok, hanging out in the Amarok forum since August, 2007
Currently running Kubuntu Trusty 14.04, KDE 4.12.95, Amarok 2.8-git of the day
User avatar google01103
Manager
Posts
4970
Karma
17
OS
this repository has Amarok 2.3.1 for openSuse 11.3 http://download.opensuse.org/repositori ... SUSE_11.3/


OpenSuse 13.1 x64, KDE 4.12.x

Problem solved? Please click on Image below the post with the best answer to mark your topic as solved.
User avatar manchette
Registered Member
Posts
225
Karma
0
OS
;)


Thanks for these tips,
, i saw that svn was not ok for a lib was missing
, thus i installed amarok 2.3.1

$ rpm -q amarok
amarok-2.3.1-86.1.i586



By the way : The bug i told you above was while 1st time building the collection and it seems like the directories are still set (i had to close amarok which was not responding anymore) .
Shall i rescan all collection or can i assume collection was built correctly ?


manchette, proud to be a member of KDE forums since 2008-Oct.
last openSUSE version : 13.1... / Last Kde version : 4.12.0 ...
User avatar Mamarok
Manager
Posts
2922
Karma
8
OS
Maybe asking it to update the collection, then restarting to make sure the Collection Browser shows it correctly is a good idea, since we currently have some unsolved caching issues with the Collection Browser.

Usually, when it doesn't scan the folders to 100% it is a file or more that either can't be read correctly or which have empty tags from Picard or MusicBrainz and are then registered as empty files. This is already solved in the development version, but for now you should try to run Amarok in a console twice in a row with 'amarok -d --nofork' (without the ' characters) to get a correct debugging output, then do a full scan, the konsole output will tell which files are to blame if the scan doesn't finish correctly.

Don't forget to restart Amarok after the first successful scan (remember the caching problem I mentioned above).


Mamarok, hanging out in the Amarok forum since August, 2007
Currently running Kubuntu Trusty 14.04, KDE 4.12.95, Amarok 2.8-git of the day
User avatar manchette
Registered Member
Posts
225
Karma
0
OS
Rescan seems ok now, Thanks ;)


manchette, proud to be a member of KDE forums since 2008-Oct.
last openSUSE version : 13.1... / Last Kde version : 4.12.0 ...

 
Topic locked

Bookmarks



Who is online

Registered users: Baidu [Spider], bcooksley, Bing [Bot], claydoh, Deusdies, Exabot [Bot], garthecho, Google [Bot], Hans, jpwhiting, La Ninje, Majestic-12 [Bot], Mamarok, MetaNova, MSN [Bot], renatoatilio, rossdv8, Uri_Herrera, Yahoo [Bot], šumski