DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
yesterday Synaptic informed me of available updates. I let it download and install them. If I recall correctly, some updates failed in the process of installing or downloading. As it was late, I shut down my PC and decided I would install what had not been installed on the morrow.
When I tried to boot this morning, here is the screen that I got:
Before I suggest anything, are you using an encrypted partition? I have no experience with encrypted partitions, and I guess the procedure for these cases must be different to a regular partition, so that's why ask.
I am guessing they are related. It might be caused by systemd. There have been some problems of that nature recently.
Quote:
Originally Posted by t-688
yesterday Synaptic informed me of available updates. ... I run Debian Jessie. ... My level is noob-intermediate (I know how to use the recovery terminal, at least).
No insult intended, but if you describe yourself as a newbie using Synaptic, is it a good idea to use a testing system, especially during the conversion period to systemd?
1/Booting recovery terminal
2/Configuring wifi access from terminal (hardest part... my laptop had no working ethernet)
3/Doing an apt-get clean and apt-get upgrade
Quote:
No insult intended, but if you describe yourself as a newbie using Synaptic, is it a good idea to use a testing system, especially during the conversion period to systemd?
None taken. The definition of "noob" varies widely.
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
Saw this post and thought it might be a tough one. Glad I was wrong.
One suggestion from someone that prefers testing and Sid to stable; don't use Synaptic for your update/upgrade chores.
It is a great tool. It is a gui front end for apt-get. Simply invokes the same commands. However, you are using a Debian version that is under continous development and any package can be a bit, or a bunch, unstable. Using the cli is simply safer as it does cut out a layer of complexity.
One thing that Synaptic does that most people do not is to run apt-get dist-upgrade instead of upgrade and then dist-upgrade. This mean you have all packages to wonder about when something goes wrong instead of just some of them.
If you do not have apt-listbugs installed I would do that no matter if you use Synaptic or not. This will warn you of all KNOWN bugs for any packages being upgraded or installed. Many may not affect your hardware and you do need to wade through them. Well worth the effort if it saves breaking your system once a development cycle.
I use Synaptic with Sid without any problems. I never use the "Mark All Upgrades" button, and I review the changes before it installs/upgrades anything.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.