HowTo: Upgrade the #! Point Release to sid (Page 3 of 4)

Thanks, I finally got smxi to work. Cheers

Ranger just gave me a culture shock, since it is starkly different from midnight commander.  I might like it more once I figure out how to use it more effectively.  I did your apt-cahe rdepends libgtk-3-0 but it brings up all the packages that depend on it (expected). 

Is there a way to find out only the installed packages that use libgtk-3-0?

Thanks for all the tips in this thread. I just upgraded to testing, and I had the issues you mention with nm-applet (launched twice, and no permission to join wifi), mounting USB drives, and cb-exit no longer working. I installed lightdm and selected it as the manager, and now I can mount drives, and by changing the Openbox menu I can now reboot and logout from there easily. One thing that I haven't gotten to work yet is autologin via lightdm (I have an encrypted partition and one user, so I don't need to login again every boot).

I changed the lightdm.conf file to include these lines:

autologin-user=zap
autologin-user-timeout=0

But that doesn't do the trick. Do I need to also create a pam script, as mentioned here, or do I just need to add/modify another lightdm config? And is there any way to use lightdm (or something other than the fugly xscreensaver) to lock the screen without logging out when I want to step away for a bit? (EDIT: Found this thread, which at least helps make xscreensaver less unbearably fugly.)

Overall, testing solved some annoyances for me and doesn't seem to have created any others that are unsolvable, so I'm glad I made the leap. I was running unstable on this system before reinstalling #!, and I'm not sure why I didn't just move to that this time also. I guess it was because I was generally happy with #! stable and I didn't want to move so far away that I couldn't wave to it from the window.

Last edited by ZAP (2011-12-31 03:25:41)

What happens when you try? If the association with .deb files is just broken, you can right-click on one in Thunar, choose Properties, and select to open it with GDebi Package Manager. If you have some other problem, please be more specific.

I haven't been able to run it since I upgraded. I think it's still broken upstream, and we just need to wait. You can always edit the config file manually, though.

just a quick note: works great with testing too... same issues usb/exitscript --> solved easily with lightdm...

Fantastic howto, and extremely easy to follow. I decided to try it out on my laptop and had no problems at all, though for some reason cb-exit still works.  The only real oddity is that icon themes don't work right. Thunar and other such apps recognize them fine, but the system tray (tint2 in Openbox, btw) always uses hicolor regardless of what is applied. Xfce doesn't have any problems using the settings manager there. I tried searching for possible solutions to this, but the terms are so ubiquitous that I couldn't find anything useful or particularly relevant. Any thoughts on what might be happening there, and what I may be able to do to work around it? It doesn't cause any real problem, but it doesn't look as good as I would like with multiple icon themes on the desktop.

machinebacon,

Many thanks for the info and for looking into this. I was convinced at the time of writing that I had ruled out incomplete icon sets because I had tried every one available via apt, as well as several I had downloaded and which I knew had specific icons for the systray. Among those I tried were elementary dark and Faenza, both of which have their own monochromatic nm-applet signal and battery icons. Neither of these ever worked, which convinced me that something else was to blame. However, having installed and started some other apps, including things like dropbox, I have discovered that some do appear here and there, though very inconsistently.

Having dug somewhat deeper now I believe what may be going on is some change in the schemes for icon themes. I think many of these icon themes are set up for the older way of doing things, and now they are failing. Many have nm-signal icons, for instance, but they seem to be in different places for different sets. It is apps in some and places for others. Also, some names seemed to have changed, such as the images folder icon which apparently used to be folder-image and seems now to be folder-pictures. Additionally folder-video became folder-videos (that is an important improvement, right?) and so on. What such a trivial change serves is beyond me, but it may be breaking compatibility.  BTW, I have downloaded some themes and tried to copy a few icons over using these new formats and the results have been very inconsistent. The system tray never seems to be affected, but Thunar has used some of the folder icons that didn't appear before. Hard to know what to make of that.

But, most importantly, thanks again for posting your howto. It really was terrific. Things are running fantastically, and if inconsistent icons are the worst outcome I have been dealt so far I count that a big win.

Hello,

please post

cat /etc/apt/preferences

Here is what is in my /etc/apt/preferences file:

Package: *
Pin: release n=statler
Pin-Priority: 1001

Package: *
Pin: release n=sid
Pin-Priority: 500

echo conky-all hold | dpkg --set-selections
echo conky hold | dpkg --set-selections

I'm going to need to direction on what edits to make.