You are not logged in.
Oooops, bugs on the loose today it seems. Better watch out so you don't catch the flu.
serious bugs of xserver-xorg-core (2:1.17.2-1.1 → 2:1.17.2-3) <Outstanding> b1 - #798097 - Restarting logind kills Xserver serious bugs of libpam-systemd (226-4 → 227-1) <Pending Upload> b2 - #801354 - boot and services fail with "Connection timed out" serious bugs of systemd (226-4 → 227-1) <Pending Upload> b3 - #801361 - [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT
That's when dpkg selections come to play.
To hold a package
echo packagename hold|dpkg --set-selections
To take a package off Hold
echo packagename install|dpkg --set-selections
To list packages on hold:
dpkg --get-selections | grep hold
In following upgrades you can check if bugs are still there or being fixed (per package)
apt-listbugs list packagename
Also studying the bugs a bit is worthwhile. They might be harmless for your particular system. At this point:
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
....
Summary:
whateverpackage (1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
Press the w key.
Last edited by Snap (2015-10-11 21:09:55)
Offline
Thanks Snap, you must have been reading my mind, were in fact thinking of searching for exactly that! Will look into it tomorrow, and see what apt got in line for me.
Offline
I don't read minds, I've borked many sidstems LOL
This helps too.
https://forums.bunsenlabs.org/viewtopic … 2584#p2584
Staying away from the X for critical upgrades (Drivers, Xserver...) is safer. (I stopped borking sidstems this way)
If running X, first logout and hit Ctrl+Alt+F2. In the tty login as root. Then:
init 3
apt-get update && apt-get dist-upgrade
apt-get clean
init 5 && reboot
You can use aptitude instead for even safer (sometimes tedious) upgrades. Specially if using apt pinning instead of dpkg selections.
If you got bugs reported you can also hit w. but you'll need some text based browser for that. Like w3m, links2, lynx, etc...
Last edited by Snap (2015-10-11 21:35:02)
Offline
smxi for system updates,upgrades and maintenance;
choose default kernel,graphics install etc...
Offline
No sign of bugs today, d-u went well. Thanks all the same guys. Appreciate it! By the way is there any plans about an unstable/testing section of the forums? Or should questions and upgrade warnings go here in off topic, or in help&support other? Or have I missed some vital information about it?
Offline
Methinks dolly has a point, you did have a section for those tracking testing/unstable back at the old place.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
dolly & Bearded_Blunder I agree and have posted this in the Development & Suggestions section.
Last edited by MAC the Bloody (2015-10-12 15:42:23)
“The university is well structured, well tooled, to turn out people with all the sharp edges worn off...." Mario Savio
"Protections for anonymous speech are vital to democratic discourse". Help enforce our right to free and anonymous speech by running a Tor relay.
Offline
I don't care what you do at home. Would you care to explain?
Offline
I have moved the thread to System Administration and changed the title slightly.
EDIT: Stickied it as well (subject to review).
Last edited by Head_on_a_Stick (2015-10-12 16:48:28)
Offline
My bad, I forgot I had those admin rights. Thanks HoaS!
I don't care what you do at home. Would you care to explain?
Offline
I moved my Stretch install (https://forums.bunsenlabs.org/viewtopic … 2239#p2239) to Sid. Every application works well, LibreOffice, Gimp, Vlc etc. What got upgraded from Jessie to Stretch to Sid were the Debian debs, not the scripts. The additional scripts, bash, python etc were pasted into /usr/bin, /usr/lib, /usr/local/bin and not installed from deb packages, so not to get troubled by any attempted upgrading by Apt. If there were any dependencies, the control info for them are kept in a text file in Documents.
Btw, not even the Virtualbox app got troubled by this Sid upgrade. I had Windows 10 installed in that. A screeny would be posted in Artwork & Screenshots.
https://forums.bunsenlabs.org/viewtopic … 2782#p2782
Last edited by nobody0 (2015-10-13 05:47:52)
Offline
Anyone having issues with Liquorix kernels lately?
I installed it in my main system a few days ago and had to revert back to towo. It freezes at boot. Two days ago I installed it in two VMs (my nice recent Posbang install) and them both are fully borked. For some reasom grub was messed and doesn't display anymore in both machines. They stall at boot and don't see a way to revert back to the former kernels. I didn't saw any warning about grub or anything else.
This also makes me think of a possible HD problem. All the 3 HDs in this very machine are Seagate.
I think it's time to finally give a try to the SuperGrub2Disk iso.
PS, another thing to consider that might be relevant. All these 3 machines are the ones I have around having sysvinit instead of systemd. Gotta try to install the LK into a systemd machine and see what happens.
Last edited by Snap (2015-10-13 06:28:54)
Offline
Yeah, Liquorix doesn''t work on my box as well. Systemd, BL tracking sid so I am guessing you will likely end up with the same results.
Offline
@tknomanzr
Are you saying liquorx isn't compatible wit systemd?
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
I think it is more likely that it is just not configured correctly.
Offline
Are you saying liquorx isn't compatible wit systemd?
Nope. Liquorix is having issues lately whatever the init.
Went back to Siduction's towo. All good now.
PS, I (thankfully) managed to revert to the former kernel in my main system, but wasn't able to do it in the two problematic VMs. Got kernel panics at boot every time. Added a secondary VDI clone from another working VM and used its GRUB to be able to boot from there from the different kernels but it didn't worked either. Whatever the kernel I get the same kernel panic. Maybe VirtualBox adds something to this problem. I had to delete one of the VMs and reinstall the other...
Last edited by Snap (2015-10-14 08:08:18)
Offline
Fresh reboot from d-u, vanilla Debian kernel, all ok here. As far as I know that is!
Offline
So you don't have aptitude installed, eh?
apt-listbugs list aptitude
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of aptitude (→ ) <Outstanding>
b1 - #801430 - aptitude: segfault when mark remove marked pkgs as purge, aptitudeDepCache::internal_mark_delete loop here
Summary:
aptitude(1 bug)
Offline
After moving to Sid from Stretch, I cannot use Polish special letters. Before that, I used Polish in Iceweasel, LibreOffice and in terminal. Everything needed for using Polish had been installed. It might get corrected in future dist-upgrades, I hope. I couldn't write my nick here, so had to ask for a change to English letters.
Btw, this problem isn't there in both Arch and Ubuntu Openbox installs. Arch, Debian Sid and Ubuntu Wily have Linux kernel 4.2.0-*.
Once installed Arch simply work. Ubuntu uses Sid packages, but doesn't give trouble. All three, Arch, Debian and Ubuntu had started from net-installs.
Offline
@Snap: no, apt - get here. It is what I am used to and mostly comfortable with. Every time I try aptitude on unstable I make a mess quite rapidly.
Offline