You are not logged in.
Offline
I just did a dist-upgrade earlier today and have no such trouble.
Can you post your /var/log/apt/history.log? Maybe your upgrades include a polkit upgrade or something else involving user/root access and everything will be fixed with a reboot.
Last edited by pvsage (2015-11-04 11:17:10)
Be excellent to each other, and...party on, dudes!
BunsenLabs Forum Rules
Tending and defending the Flame since 2009
Offline
Start-Date: 2015-11-04 09:24:47
Commandline: apt-get dist-upgrade
Install: laptop-detect:amd64 (0.13.7, automatic)
Upgrade: bunsen-themes:amd64 (8.0-1.1, 8.3-1), libsasl2-modules-db:amd64 (2.1.26.dfsg1-13, 2.1.26.dfsg1-13+deb8u1), bunsen-common:amd64 (8.0-2, 8.4-1), linux-image-3.16.0-4-amd64:amd64 (3.16.7-ckt11-1+deb8u3, 3.16.7-ckt11-1+deb8u5), bunsen-utilities:amd64 (8.2-2, 8.4-1), libicu52:amd64 (52.1-8+deb8u2, 52.1-8+deb8u3), bunsen-configs:amd64 (8.4-1, 8.4.1-1), bunsen-welcome:amd64 (8.2-1, 8.3.1-1), libgdk-pixbuf2.0-common:amd64 (2.31.1-2+deb8u2, 2.31.1-2+deb8u3), bunsen-conky:amd64 (8.0-1, 8.2-1), libfreetype6:amd64 (2.5.2-3, 2.5.2-3+deb8u1), gir1.2-gdkpixbuf-2.0:amd64 (2.31.1-2+deb8u2, 2.31.1-2+deb8u3), iceweasel:amd64 (38.2.1esr-1~deb8u1, 38.3.0esr-1~deb8u1), libldap-2.4-2:amd64 (2.4.40+dfsg-1, 2.4.40+dfsg-1+deb8u1), ntp:amd64 (4.2.6.p5+dfsg-7, 4.2.6.p5+dfsg-7+deb8u1), bunsen-images:amd64 (8.1-1, 8.2-1), bunsen-pipemenus:amd64 (8.6-1, 8.6.3-1), unzip:amd64 (6.0-16, 6.0-16+deb8u1), libgdk-pixbuf2.0-0:amd64 (2.31.1-2+deb8u2, 2.31.1-2+deb8u3), libsasl2-2:amd64 (2.1.26.dfsg1-13, 2.1.26.dfsg1-13+deb8u1), tzdata:amd64 (2015f-0+deb8u1, 2015g-0+deb8u1), libvdpau1:amd64 (0.8-3, 0.8-3+deb8u2), bunsen-os-release:amd64 (8.1-3, 8.2-1), libminiupnpc10:amd64 (1.9.20140610-2, 1.9.20140610-2+deb8u1)
End-Date: 2015-11-04 09:26:23
Offline
Bravo for installing BL.
Unlike apt upgrade or apt-get upgrade, which will only upgrade packages and never remove them according to "man apt" and "man apt-get", apt-get dist-upgrade (or apt full-upgrade) will attempt to upgrade what it considers important packages first and will possibly remove packages to resolve conflicts in upgrading those packages.
In other words, if there's a package conflict upgrade will leave those packages in their current state while dist-upgrade will automatically resolve the conflict. So it's quite possible a package was removed and that's causing the problem.
apt-get dist-upgrade is normally only used when upgrading from one major version to the next (i.e. from wheezy to jessie) or if you are upgrading sid. There is no need to run dist-upgrade to maintain a jessie system on a day to day basis.
If this is a brand new installation, it might be easiest to just reinstall it and then maintain it using recommended methods (see 6.2.3 System Upgrade)...
https://debian-handbook.info/browse/sta … pt-upgrade
Otherwise, you'll find more information by viewing the logs in /var/log/apt/ and the file /var/log/dpkg.log. Many of the files in /var/log require root privelages to view them.
I don't care what you do at home. Would you care to explain?
Offline
Offline
Can't make a fresh install, as that'd mess up with the grub screen.
*facepalm*
Only dist-upgraded today.
Yeah, why'd you do that?
http://s6.postimg.org/br9hbyexp/Bunsen.jpg
What's grub.cfg got to do with it? You're on your own, kid, I'm out.
I don't care what you do at home. Would you care to explain?
Offline
Lately grub has a problem. If a new install would take over the grub, it doesn't appear to see the other installations' swap UUID or something like that. When you try to boot into another installation, systemd would go on looking for swap for 1.30 minutes, then timeouts and boot into it. So, I don't want to mess up with the grub alrady installed.
Offline
Check your /etc/group file and make sure the appropriate users are in the sudo group.
Been a while, but I have had upgrades change that file back to the default setting so that no users can "sudo".
You must unlearn what you have learned.
-- yoda
Online
Check your /etc/group file and make sure the appropriate users are in the sudo group.
Been a while, but I have had upgrades change that file back to the default setting so that no users can "sudo".
Thanks, PackRat!
That's what had happened. Changed the /etc/group file.
Offline
Lately grub has a problem. If a new install would take over the grub, it doesn't appear to see the other installations' swap UUID or something like that. When you try to boot into another installation, systemd would go on looking for swap for 1.30 minutes, then timeouts and boot into it.
The Debian Installer creates a new UUID when it formats swap. Just boot into the new system and copy the new swap UUID from /etc/fstab to the other OS' fstabs. Or lose UUID's in your installed OS' fstabs altogether (web search, please).
I don't care what you do at home. Would you care to explain?
Offline
If you have a GUID partition table and there is no need for separate swap partitions for each installed distribution (for hibernation or similar) then it's probably best to just delete the swap line from /etc/fstab and let systemd mount it automatically.
http://www.freedesktop.org/software/sys … rator.html
@ostrolek -- did you update & install all your packages the "normal" way or did you mess around with the control files and copy the stuff in manually?
Offline
@ostrolek -- did you update & install all your packages the "normal" way or did you mess around with the control files and copy the stuff in manually?
The installation was in the normal way. The upgrade was also the normal way. Nothing is added to this installation. Its in the vanilla state. Only change is autohiding the tint2 panel. Changed the /etc/group file--PackRat's advice--to give the user sudo rights, and everything works.
Last edited by nobody0 (2015-11-04 18:58:35)
Offline
There is no need to run dist-upgrade to maintain a jessie system on a day to day basis.
Please use...
sudo apt upgrade
I don't care what you do at home. Would you care to explain?
Offline
Although dist-upgrade should have made no difference if was really a vanilla BL install, with nothing extra in the apt sources.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline