Hello, On penktadienis 21 Sausis 2011 03:58:58 Gordon Haverland wrote: > On January 20, 2011, Modestas Vainius wrote: > > Hello, > > > > On penktadienis 21 Sausis 2011 02:59:17 Gordon Haverland wrote: > > > On January 20, 2011, you wrote: > > > > Hello, > > > > > > > > On penktadienis 21 Sausis 2011 00:30:35 Gordon Haverland > > wrote: > > > > > Running amarok from the command line, with or without > > > > > --debug doesn't seem to offer much. I did run it under > > > > > strace, and an edited version of the strace is below. > > > > > > > > Try running > > > > > > > > $ kbuildsycoca4 --noincremental > > > > > > > > and start amarok again. > > > > > > I do not have amarok source here. Is building amarok from > > > source necessary to track this down? (I do have disk space, > > > but I have never built any component of KDE from source > > > before.) > > > > That command has nothing to do with building from source. It > > expands as K-BUILD-SYstem-COnfiguration-CAche. Just run it > > from the X terminal as your user. > > That command looks like it is involved with building from source. > > In any event, I ran that command from a shell, and then asked KDE > to load amarok. It loaded. > > The window which came up was very small, and all squashed into the > upper left quadrant.
That's probably because you had to kill it in the middle of Update system configuration. > The first time I tried to start a song (from the saved playlist), > amarok crashed. Starting amarok again, and trying to start the > same song seems to have worked (at least, it didn't crash). Amarok has never been the most solid software in the world. It has always had a good share of bugs and Amarok 2 is not an exception. > I had noticed updates to KDE (unstable) a couple of weeks ago, and > not installed them. Lately (1 week ago?) I noticed that updates > to amarok were available. Today, amarok stalled, and so I thought > updating amarok was something to do. Even though I see a lot of > KDE has updates available, I did not update anything of KDE other > than amarok. (And from dependencies, nothing of kde was updated.) > > But in general, anything having to do with GUIs that I normally > use (which is mostly KDE), I will not install updates for at least > 1 week. In the past, I would install an update, and a few hours > later there was another update to the same packages. And this > behavior seems to be consistent. I am not looking for exercise in > typing 'apt-get install ...'. If somebody doesn't know if their > updated package works, perhaps there is some method they can use > which doesn't involve a zillion people downloading and installing > changes which break packages? > > In general, I am willing to download and install upgrades. It > bugs me to heck when I see certain families of packages require 2 > or 3 updates immediatly afterwards. More often than not, it seems > to be some simple problem. Which to me seems to be I have not > installed this new package on my own machine. > > But, I am not a Debian maintainer, and I don't know what sorts of > problems come up with updating packages. > > I do wish you the best. I would much rather spend time figuring > out how atoms work in structures designed by engineers (which is > my area of expertice). Please stay on topic because 2/3 of your mail has nothing to do with this bug or even amarok itself. And FWIW, if you don't want bleeding edge updates, use stable or at least testing. -- Modestas Vainius <mo...@debian.org>
signature.asc
Description: This is a digitally signed message part.
