tag:blogger.com,1999:blog-5188121942175615593.post4624894305954130170..comments2024-03-29T01:51:12.527+11:00Comments on Lindqvist -- a blog about Linux and Science. Mostly.: 471. Debian Jessie -- gnome-shell buglindqvisthttp://www.blogger.com/profile/11525548328692436184noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5188121942175615593.post-68603691925544123902013-07-04T10:10:32.529+10:002013-07-04T10:10:32.529+10:00You can force a release by using a preferences fil...You can force a release by using a preferences file for apt (apt pinning). <br /><br />By default, if there are several versions of a package available (e.g. b/c of both testing and unstable being in sources.list) the highest version number will always be prioritised.<br /><br />On a side note: the debian devs are unhappy with deb-multimedia for the same reason -- because of how the packages are labelled they will always take precedence, regardless of version.<br /><br />However, you can change the priority settings so that your system will tolerate higher versions, but won't install them unless told so explicitly.<br /><br />And you can also use a priority setting which forces the version from a particular release, regardless of whether it will cause a downgrade (pref > 1000).<br /><br />Most of this you probably already know. You can read more doing 'man apt_preferences' and http://verahill.blogspot.com.au/2011/12/apt-pinning-in-debian-simple-example.html<br /><br />Long story short, to downgrade everything WITHOUT EXCEPTION create /etc/apt/preferences and put this in it:<br />Package: *<br />Pin: release a=testing<br />Pin-Priority: 1100<br /><br />Package: *<br />Pin: release a=unstable<br />Pin-Priority: -10<br /><br />I think an upgrade/dist-upgrade will sort things out. You will also want to change the deb-multimedia sources line from sid to jessie.<br /><br />I think you can make exceptions by putting holds on the packages (http://verahill.blogspot.com.au/2012/07/freezing-gnome.html) , but then they will not be tracking the repo, so it's not a good solution.lindqvisthttps://www.blogger.com/profile/11525548328692436184noreply@blogger.comtag:blogger.com,1999:blog-5188121942175615593.post-6407969571224483122013-07-04T07:00:04.933+10:002013-07-04T07:00:04.933+10:00Interestingly ---
# printenv | grep DISPLAY
DISP...Interestingly --- <br /><br /># printenv | grep DISPLAY<br />DISPLAY=:0<br /><br />The issue with root terminal seem due to the upgrade introducing a defective launcher /usr/share/applications/Root Terminal - with the command <br /><br />gksu /usr/bin/x-terminal-emulator<br /><br />which gives the error ** (nautilus:6839): WARNING **: Could not open X display - and only launches once after login.<br /><br />A root terminal that can reliably launch gksu and root nautilus is creating a new launcher /usr/share/applications/Root xterm - with the command <br /><br />gksu xterm<br /><br />The upgraded packages seem to be handling dist-upgrades well so apparently no need to downgrade but if not the question would be how:<br /><br />The file /etc/debian_version contains jessie/sid and the regular debian repositories are pointed at jessie apart from<br /><br />deb ftp://ftp.deb-multimedia.org sid main non-free<br /><br />Therefore apt-show-versions |grep sid gives a moderately long list of multimedia programs and their depencies.<br /><br />(apt-show-versions |grep unstable only shows google-chrome)<br /><br />If they had not been behaving themselves would there be a straightforward way of downgrading all unstable packages or with certain exceptions and fixing them at testing -currently jessie?<br />Anonymoushttps://www.blogger.com/profile/11742357734119439801noreply@blogger.comtag:blogger.com,1999:blog-5188121942175615593.post-60477273654282866562013-07-03T14:41:13.321+10:002013-07-03T14:41:13.321+10:00If you want to roll back what you did and downgrad...If you want to roll back what you did and downgrading, you can find the unstable/sid packages using e.g.<br />apt-show-versions |grep unstable<br /><br />Likewise, packages not from any of the standard release can be found using <br />apt-show-versions|egrep -v "wheezy|jessie|unstable"<br /><br />Or you can continue to live interestingly :)<br /><br />Re nautilus, presuming that you are using gksu, what does<br />printenv | grep DISPLAY<br />when run as root? lindqvisthttps://www.blogger.com/profile/11525548328692436184noreply@blogger.comtag:blogger.com,1999:blog-5188121942175615593.post-45056762079737498782013-07-03T07:57:14.467+10:002013-07-03T07:57:14.467+10:00The Jessie gnome-shell wiped out the gnome desktop...The Jessie gnome-shell wiped out the gnome desktop here too before the above post appeared. Not being aware of the above surgical approach I resorted to an attempt to upgrade gnome-shell and several other gnome packages to sid in an attempt to cure it. The program apt-listbugs listed two serious bugs in potential dependent packages but fortunately they did not involve gnome-shell.<br /><br />After being unable to resist also upgrading libreoffice, I had to remove libreoffice altogether afterwards in order to preserve dist-upgrade equilibrium. Ended up replacing it with unstable version 4.1 directly from the website but the word menus are a litttle shaky.<br /><br />The gnome artwork is prettier but root terminal attempts to launch nautilus give:<br /><br />** (nautilus:6839): WARNING **: Could not open X display<br /><br />Otherwise seems to have survived the upgrade unscathed - with empasis on seems.<br /><br />Being capable of identifying the real source of the problem is more rational.<br />Anonymoushttps://www.blogger.com/profile/11742357734119439801noreply@blogger.com