Quoting wzabo...@elektron.elka.pw.edu.pl (2017-10-08 15:02:03) > W dniu 08.10.2017 o 14:53, Jonas Smedegaard pisze: > > Quoting wzabo...@elektron.elka.pw.edu.pl (2017-10-08 14:38:01) > >> W dniu 08.10.2017 o 14:13, Jonas Smedegaard pisze: > >>> Quoting Wojciech Zabołotny (2017-10-08 13:34:16) > >>>> When I start the jack server, and then ardour5, it does not start. > >>>> The "top" shows that ardour5 uses one CPU core in 100%. > >>>> When I start it via "strace", I get the following messages displayed > >>>> repeatedly: > >>> [...] > >>>> It looks, that ardour tries to load the Breeze gtk theme, and when it > >>>> fails, > >>>> it repeats that forever. > >>>> I can see two problems there: > >>>> 1. ardour should depend on the appropriate package providing the required > >>>> GUI theme > >>>> 2. ardour should fail, displaying the reasonable error message without > >>>> looping forever. > >>> Ardour does _not_ depend on a specific GTK+ widget theme. > >>> > >>> Perhaps a bug elsewhere - e.g. in GTK+ or that particular theme - is > >>> triggered? > >>> > >>> Did you configure your environment to use Breeze? Could you please try > >>> switch to a different GTK+ theme instead? > >>> > >>> Perhaps create a temporary new user on your system and start Ardour from > >>> there - to help avoid cruft in your own $HOME environment interfering. > >>> > >> Dear Jonas, > >> > >> Thanks a lot for your suggestions. > >> > >> That's interesting. Of course, I have cleaned up the ~/.config/ardour4 > >> and ~/.config/ardour5 directories before submitting the first report, > >> and it didn't help. > > So you tried cleanup, but only the (too narrow) part you suspected to > > cause the error. > > > > > >> However indeed, when I logged in as another user, ardour started > >> correctly. > > Good to hear! > > > > > > > > > >> So the problem probably indeed is not ardour related (however I don't > >> know why only ardour suffers from that). > > It might very well be that Ardour is particularly vulnerable to being > > fed a broken GTK+ theme. Which seems to be the case here. > > > > > >> PS. Is it possible that > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874598 is caused by > >> the same problem? > > Possibly, yes. But instead of (again) too narrowly draw conclusion best > > to find something that works (e.g. a fresh account) and triangulate from > > there, as you did here. > > > Yes, I do agree. However I think that the important news for other > affected users is that removal of ~/.gtkrc-2.0 (if exists) may help. > Otherwise the user would be forced to wipe his account...
If indeed that solves *both* these reported bugs, then true. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
