Re: unmet dependencies: libcurl4-openssl-dev

[Dejan Jocic]

On Wed, Feb 04 2015,Dejan Jocic wrote:


[snipped 57 lines]

 aptitude why-not libcurl4-openssl-dev
 i   task-kde-desktop  Recommends system-config-printer 
 i A system-config-printer Dependspython-cupshelpers (= 1.3.7-4)
 i A python-cupshelpersDependspython-pycurl 
 i A python-pycurl Suggests   libcurl4-gnutls-dev   
 p   libcurl4-gnutls-dev   Conflicts  libcurl4-openssl-dev

 That is what I get on Wheezy KDE.


Which is *exactly* the same message for me too.  I did try to uninstall
curl and reinstall it again but that didn't work.  I still got the
same error as above.  


Any suggestions on how to proceed to fix it?


 sivaram



Well, I can not tell, there is not enough informations for that. What I 
said about aptitude why-not was just as example. As far as I could see 
from start of your thread, you said that problem is: 

The following packages have unmet dependencies:
 libcurl4-openssl-dev : Depends: librtmp-dev but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages

And why-not for librtmp-dev does not give me anything, it can be 
installed without problems on my system. Try aptitude -h and see all 
options it will give you. For example, there is option for trying to 
aggressively fix broken packages. And if you have broken packages, it 
was most likely done by some of your previous actions(you did 
mention some fiddling) . You can try to find out what went wrong and 
to reverse your actions. Also, you can try to use aptitude instead of 
apt-get when you are trying to install libcurl4-openssl-dev, think that it 
might give you more informations and options in this case. On other 
hand, do not know why you are trying to install libcurl4-openssl-dev, 
why not directly emacs24 for Wheezy backports? Not that I can 
understand why would anyone want that abomination of self called 
text editor(just kidding, not trying to start religious war about text 
editors).


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201502042128.04983.jode...@gmail.com

Re: unmet dependencies: libcurl4-openssl-dev

[Dejan Jocic]

On Wednesday 04 February 2015 11:27:25 AM Rusi Mody wrote:
 On Wednesday, February 4, 2015 at 12:50:04 PM UTC+5:30, Sivaram 
Neelakantan wrote:
  How does one go about fixing broken packages?  I've recently 
started
  using debian and apart some fiddling to get the latest emacs24.4 
on
  wheezy I have not done anything on the system.  When I tried to
  install libcurl4, I get the following error.
  
  apt-get install libcurl4-openssl-dev
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed.
  
  [snipped 5 lines]
  
  The following packages have unmet dependencies:
   libcurl4-openssl-dev : Depends: librtmp-dev but it is not going to 
be
   installed
  
  E: Unable to correct problems, you have held broken packages
  
  
  Googling around and checking a few forums with various 
incantations of
  
   apt-get with autoremove/clean/install/dist-upgrade didn't sort out
   the problem.  I now have no idea how to fix this issue.
  
  I have a stock install of debian-kde iso and the current version 
seems
  to be
  
  cat /etc/debian_version
  7.8
  uname -a
  Linux sivaram 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 
x86_64
  GNU/Linux
  
  What should I do please to get the package installed?
  
   sivaram
  
  p.s first time user of debian
 
 What happens if you (try to) manually install librtmp-dev ?
 
 Note: apt-get, synaptic, and aptitude have different 'solvers' so its
 good to have all three handy


Also, perhaps it is good idea to check with aptitude why-not like this:

aptitude why-not libcurl4-openssl-dev
i   task-kde-desktop  Recommends system-config-printer 
i A system-config-printer Dependspython-cupshelpers (= 1.3.7-4)
i A python-cupshelpersDependspython-pycurl 
i A python-pycurl Suggests   libcurl4-gnutls-dev   
p   libcurl4-gnutls-dev   Conflicts  libcurl4-openssl-dev

That is what I get on Wheezy KDE.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201502041221.36099.jode...@gmail.com

Re: [OT?]Squeeze: update Flashplugin?

[Dejan Jocic]

On Tuesday 10 February 2015 10:14:24 AM Greg Madden wrote:
 /usr/lib/mozilla/plugins/libflashplayer.so
 
 On Mon, Feb 9, 2015 at 11:12 PM, Curt cu...@free.fr wrote:
  On 2015-02-10, Michael Graham ooberm...@gmail.com wrote:
  But Iceweasel is still reporting the previous version:
  
  File: libflashplayer.so
  Path: /usr/lib/flashplugin-nonfree/libflashplayer.so
  Version: 11.2.202.440
  State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)
  Shockwave Flash 11.2 r202
  
  Does anyone have a clue what is going on?
  
  Thanks,
  
  I updated to the latest version but still get security warnings (and
  have to click on allow or something of the kind).
  
  File: libflashplayer.so
  Path: /usr/lib/flashplugin-nonfree/libflashplayer.so
  Version: 11,2,202,442
  State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)
  Shockwave Flash 11.2 r202
  
  I don't know what the problem is. However, it does prevent flash
  doohickeys from playing without my express authorisation, which 
might be
  considered a feature.
  
  ;-)
  
  
  --
  
  Anything incomprehensible has a sexual significance to many 
people under
  35.
  
  — Zelda Fitzgerald
  
  
  --
  To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact
  listmas...@lists.debian.org Archive:
  https://lists.debian.org/slrnmdjfbd.27v.cu...@einstein.electron.org

I just reinstall Iceweasel with aptitude whenever i see messages like 
that. So, those warning messages vanish for some time. I think there 
is not any permanent solution for problem, but perhaps someone 
more knowledgeable could provide one.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201502101145.32023.jode...@gmail.com

Re: Jessie regularly loses wifi connection though signal is strong

[Dejan Jocic]

On Friday 13 March 2015 03:58:05 PM Thomas H. George wrote:
 Very frustrating. Wifi says it is connected though it is not.
 After reset the connection works for a time, then just stops.
 
 Any suggestions?
 
 Tom


Try newish kernel, from backports?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201503131607.41141.jode...@gmail.com

Re: Installing/running non-Debian executables

[Dejan Jocic]

Richard Owlett  writes:

> I'm running Jessie with Mate DE.
>
> I need to run the *IDENTICAL* versions of SeaMonkey (2.40) on both my
> Windows and Debian machines. Downloading the appropriate file,
> unpacking it, placing results in my Home folder, and marking seamonkey
> as executable goes well.
>
> Creating a launcher on desktop and test run shows no problem.
>
> How do I place the launcher on the Applications drop down menu?
>
> TIA

I do not have mate installed around, but as far as I can remember:

Right click menu and select Edit menu, then category where your app
laucher should go, then something like add new item, name of app and
where it requires path to executable file. 

Re: new packages

[Dejan Jocic]

On 23-03-17, Greg Wooledge wrote:
> On Thu, Mar 23, 2017 at 02:42:20PM -0400, songbird wrote:
> >   when you run:
> > 
> > $ apt-get upgrade
> > 
> > it will not add any new programs, but when you run:
> > 
> > $ apt-get dist-upgrade
> > 
> > it will tell you which are new of the updates it is
> > going to perform (if any).
> 
> I strongly recommend using the half-documented -u option here:
> 
> apt-get -u upgrade
> 
> It's not in the man page, but it IS in the "apt-get -h" output.
> 
> That way you'll have some warning of which services are going to be
> affected.  If, for example, you see that your database server is
> going to be upgraded, and you know that this will impact your users,
> you may want to wait until a less busy time to do the upgrade, and
> shut down your database-client application(s), etc.
> 
> This is also one of the reasons why unattended upgrades are not on
> by default.
> 
Actually, it is in the man page of apt-get:

 -u, --show-upgraded
Show upgraded packages; print out a list of all packages
that are
   to be upgraded. Configuration Item:
   APT::Get::Show-Upgraded.


Also, another option that could be more useful:

-s, --simulate, --just-print, --dry-run, --recon, --no-act
No action; perform a simulation of events that would occur based on
the current system state but do not actually change the system.
Locking will be disabled (Debug::NoLocking) so the system state
could change while apt-get is running. Simulations can also be
executed by non-root users which might not have read access to all
apt configuration distorting the simulation. A notice expressing
this warning is also shown by default for non-root users
(APT::Get::Show-User-Simulation-Note). Configuration Item:
APT::Get::Simulate.
   
Have fun :)

Re: installer defaults for desktops (was Re: Suggested edit)

[Dejan Jocic]

On 24-03-17, Catherine Gramze wrote:
> 
> > On Mar 23, 2017, at 9:20 PM, David Wright  wrote:
> > 
> > It's not really polite to call this "expert" (only in the sense
> > described by the Advanced options in the installer) rabid, and what
> > I do with the installer ridiculous.
> > 
> > I don't wish to accept arbitrary impositions on what I can do with
> > free software. That's the rationale behind its existence: freedom.
> > Nor do I wish to be told what I ought to be spending my money on,
> > just to conform with your, ahem, suggestions.
> 
> The point of free software is not to cater to your personal preferences, or 
> mine, but to make that software accessible and useful to the greatest number 
> of people. The netinst installer doesn't do that when it allows a very broken 
> installation to result. There will inevitably be "arbitrary" decisions 
> involved in a project like this, like not including the non-free firmware in 
> the installer, and the switch to systemd. 
> 
> If you don't have a spare network card to use temporarily for a netinst and 
> don't want to spend $15 on a USB NIC then download and use a different 
> installer, like the first dvd of the complete set. It's free!
> 
> You still have not mentioned any actual use case for this hypothetical base 
> system box with no network capability. What is the practical daily function 
> of this box? You just keep insisting that you have such a use, and that using 
> a different installer to get it is unacceptable as an option. Why is it so 
> unacceptable? Because changing the netinst installer it might make it easier 
> for new users to Debian?
> 
> Cathy

While I do agree that Debian should be made more newbie friendly, I do
not think that it will do much good towards that goal to change net
installer. Debian has solid documentation. Not as good as some, like for
example Arch and FreeBSD, but it is solid one. Trouble for newbie is to
find some things that it will make their lives with Debian easier. One
of those things is firmware needed for installation. Newbie with net
installer that has firmware on it is in much better position than newbie
who has net installer that will fail to do installation if it can not
set up networking. Some better hints for newbies on front page of site,
like special welcome link for newbies which kind of says "Welcome
newcomers, click here please for important things you want and need to 
know". And there, some kind of FAQ list with further links should exits.

Re: Are there different Installer Packages between Server and Desktop?

[Dejan Jocic]

On 20-03-17, aorlikow...@gmail.com wrote:
> 
> Hello
> 
> I'm interested in installing Debia _SERVER_, not Desktop, but on your
> Website, there is just offering Debian.
> 
> Are there different Installer Packages between Server and Desktop? If
> the SERVER package different where can I get it. What is the Internet link?
> 
> It would be helpful when you mention it on your website, that Debian is
> either Server or Desktop or both of them.
> 
> Regards fron Germany
> 
> Achim Orlikowski
> 
> 
Debian is universal operating system and it is stated so on Debian main
page. How you will use it is up to you. You can choose during
installation process what you want to install. If you need it for server
and you do not want desktop environment you can do it with no problems.
Would suggest reading manual though, you will find more detailed
explanations there.

Have fun :)

Re: If Linux Is About Choice, Why Then ...

[Dejan Jocic]

On 06-04-17, Carl Fink wrote:
> On Thu, Apr 06, 2017 at 12:35:37PM +0100, Joe wrote:
> 
> > If I was a paid admin looking after multiple servers, yes, that's the
> > obvious thing to do. But this isn't my job, and I can't afford to buy a
> > second set of hardware, so the only practical test is to actually do
> > it.
> 
> Second set of hardware is a false requirement. Go to, say,
> http://nosupportlinuxhosting.com and rent a VM for $1/month and set up your
> server there. Make it work. If you insist on physical hardware, you can then
> clone the working setup back to your physical server.
> -- 
> Carl Fink   nitpick...@nitpicking.com 
> 
> Read my blog at blog.nitpicking.com.  Reviews!  Observations!
> Stupid mistakes you can correct!
> 

Yes, when I've mentioned cloning I thought of virtual clone, not cloning
on hardware. There are many virtual solutions for your problem.

Re: If Linux Is About Choice, Why Then ...

[Dejan Jocic]

On 06-04-17, Joe wrote:
> On Thu, 6 Apr 2017 11:10:12 +0100
> Martin Read  wrote:
> 
> > On 06/04/17 10:58, Joe wrote:
> > > I understood that an upgrade from Wheezy to Jessie would switch to
> > > systemd as init. Even if that could be fixed afterwards, then there
> > > will be server downtime and a manual procedure involved which will
> > > not be part of the upgrade procedure and therefore will not have
> > > been tested by the upgrade designers.
> > >
> > > Is that not the case?  
> > 
> > *By default*, an upgrade from Wheezy to Jessie will switch to systemd
> > as init. However, per section 5.6 of the official published release
> > notes for Debian 8 "jessie", APT pinning can be used to prevent this
> > changeover:
> > 
> > https://www.debian.org/releases/jessie/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
> > 
> > Quoted here for convenience:
> > 
> >  BEGIN QUOTE 
> > As an example, to prevent systemd-sysv from being installed during
> > the upgrade, you can create a file called 
> > /etc/apt/preferences.d/local-pin-init with the following contents:
> > 
> > Package: systemd-sysv
> > Pin: release o=Debian
> > Pin-Priority: -1
> >  END QUOTE 
> > 
> 
> Thanks, I haven't gone through this yet, I've only got one server to
> do, but it hasn't yet reached the top of the priorities list...
> 
> -- 
> Joe
> 

Have you thought of cloning your specific set up and then testing it to
see how it will upgrade? Like one clone that you will upgrade with
preventing systemd-sysv to install via Pin-Priority and other clone where
you will upgrade to systemd? Upgrade to at least Jessie is something
that will happen in your case anyway, so why not test it up front? Just
thought really.

Have fun :)

Re: System broken after yesterday's upgrade

[Dejan Jocic]

On 13-04-17, Michael Lange wrote:
> On Wed, 12 Apr 2017 22:13:44 +0200
> solitone  wrote:
> 
> > On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
> > > I'd write a bug report. Your e-mail is a pretty good start.
> > 
> > To Debian BTS? Related to the kernel package? I have no clues as to
> > what component might be actually involved.
> > 
> > Thanks,
> >   Davide
> > 
> > 
> > 
> 
> I would try to install a different kernel (if possible with external
> keyboard) and boot into that one, if the problem disappears the culprit is
> most likely the kernel.
> 
He should have old kernel still installed, right? If that is the case,
he could simply boot with old kernel.

Re: System broken after yesterday's upgrade

[Dejan Jocic]

On 13-04-17, solitone wrote:
> On Thursday, 13 April 2017 09:53:05 CEST Dejan Jocic wrote:
> > If you have old kernel, you do not have to choose it in the GRUB menu during
> > boot, you can set up your GRUB to boot from it automatically. 
> 
> I have a submenu entry in my grub.cfg:
> 
> solitone@alan:~$ grep --color menu /boot/grub/grub.cfg
>
> [...]
> menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --
> class os $menuentry_id_option 'gnulinux-simple-7f537d3b-e578-4cd3-8583-
> f3a2281f7d01' {   
>  
> submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
> 'gnulinux-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64' --class debian 
> --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-2-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {  
> 
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64 (systemd)' --
> class debian --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-2-amd64-init-systemd-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-2-amd64 (recovery 
> mode)' 
> --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-2-amd64-recovery-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64' --class debian 
> --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-1-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64 (systemd)' --
> class debian --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-1-amd64-init-systemd-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> menuentry 'Debian GNU/Linux, with Linux 4.9.0-1-amd64 (recovery 
> mode)' 
> --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 
> 'gnulinux-4.9.0-1-amd64-recovery-7f537d3b-e578-4cd3-8583-f3a2281f7d01' {
> 
> To automatically load 'Debian GNU/Linux, with Linux 4.9.0-1-amd64' I need to 
> set :
> GRUB_DEFAULT="1>3"
> in /etc/default/grub?
> 
> Cheers,
>   Davide
>  
You can set it with numbers, but you can set it also with quotes, like
for example:

GRUB_DEFAULT='gnulinux-4.9.0-1-amd64-advanced-7f537d3b-e578-4cd3-8583-f3a2281f7d01'

Which should be kind of more secure way if you do not to want to 
miss what you exactly want with numbers.

Anyway, however that you do it, after that you will need to run
# update-grub.

Re: System broken after yesterday's upgrade

[Dejan Jocic]

On 13-04-17, solitone wrote:
> On Thursday, 13 April 2017 01:23:02 CEST Dejan Jocic wrote:
> > He should have old kernel still installed, right? If that is the case,
> > he could simply boot with old kernel.
> 
> Yes, I still have 4.9.0-1-amd64. 
> 
> The point is even in the GRUB menu screen my keyboard no longer works well, 
> which is even stranger. Sometimes I press a key and after tens of seconds 
> something happens, other times nothing happens at all. So it's difficult to 
> move 
> in the GRUB menu and select the old kernel.
> 
> Plus now it's been 18 hours since last boot and everything works very well, 
> but if I reboot now I'll struggle again and I'm not sure I'll manage to have 
> it work again..
> 

If you have old kernel, you do not have to choose it in the GRUB menu during
boot, you can set up your GRUB to boot from it automatically. Glad to
hear that it works well now, though you will probably have to reboot
again, sooner or later.

Re: Systemd services (was Re: If Linux Is About Choice, Why Then ...)

[Dejan Jocic]

On 14-04-17, Nicolas George wrote:
> Le quintidi 25 germinal, an CCXXV, Greg Wooledge a écrit :
> > Some day there will be actual end-user-friendly systemd documentation
> > somewhere, consolidating all of these pieces of wisdom together.  I hope.
> 
> Note: systemd is not for end-users, it is for system administrator and
> distribution authors.
> 
Actually, it should be for end-user too. On personal computer, that
end-user is system administrator. I also find that systemd is very well
documented. But it could be just me. Now, please carry on, enjoyed this
thread very much, learned thing, or two :)

Thank you for your time.

Re: How do you disable / enable services from starting in systemd

[Dejan Jocic]

On 12-03-17, Jiangsu Kumquat wrote:
> How do you disable / enable services from starting in systemd?
> 
> I have gotten very used to the old way of how to start/stop services when
> booting using runlevels but I cannot figure out how to do any of this using
> systemd.
> 
> So, I don't always use my web and SQL servers so I don't want it
> auto-starting at boot but I don't know how to turn it off.
> 
> Thanks for reading this.

One of the many cheatsheets you can find with your favorite net search
thingy:

http://linoxide.com/linux-command/systemd-vs-sysvinit-cheatsheet/

Re: debootstrap error with dvdrom install

[Dejan Jocic]

On 29-07-17, Pierre Frenkiel wrote:
> hi,
> I'm trying to install Stretch on a Lenovo laptop with the KDE dvdrom and
> each time I get the error:
>   debootstrap error. Unable to find the codename for release
> 
> I saw a lot of posts about this error, but they were all related to a usb 
> install, but one.
> This one said he left the install in standby for several hours, but this is 
> not my case.
> So, I don't know what to do. Has anybody an idea?
> 
> best regards,
> -- 
> Pierre Frenkiel
> 

Do not use live images for install. Those are bit flaky, especially KDE
one. Use net install, or regular install image. 

Re: debootstrap error with dvdrom install

[Dejan Jocic]

On 29-07-17, Pierre Frenkiel wrote:
> On Sat, 29 Jul 2017, Dejan Jocic wrote:
> 
> > On 29-07-17, Pierre Frenkiel wrote:
> > > hi,
> > > I'm trying to install Stretch on a Lenovo laptop with the KDE dvdrom and
> > > each time I get the error:
> > >   debootstrap error. Unable to find the codename for release
> > > 
> > > I saw a lot of posts about this error, but they were all related to a usb 
> > > install, but one.
> > > This one said he left the install in standby for several hours, but this 
> > > is not my case.
> > > So, I don't know what to do. Has anybody an idea?
> > > 
> > > best regards,
> > > --
> > > Pierre Frenkiel
> > > 
> > 
> > Do not use live images for install. Those are bit flaky, especially KDE
> > one. Use net install, or regular install image.
> > 
> 
>  thanks for this information. I can't use net install, as it would need 4 or 
> 5 firmware files.
>  The only iso file without netinst  I found was xxx-xfce. I'll then try with 
> this one.
> 
> best regards,
> -- 
> Pierre Frenkiel

Actually, you have separate images with firmware, though "unofficial".
But they work really well, in my experience. Here are links both to net
install with firmware and regular install:

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

All best,
Dejan

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 28-07-17, Greg Wooledge wrote:
> On Fri, Jul 28, 2017 at 05:39:39PM +0200, Dejan Jocic wrote:
> > So, same question as above, did and of those they messed up? Are there
> > opened bugs that autoremove from any of used tools in debian removes
> > packages it should not? And qualifications for that statement are years
> > of use of both apt-get and aptitude with autoremove following
> > update/upgrade. Never had any trouble with it.
> 
> The concern is that you may have used some shared library to compile a
> third-party program which is installed in /usr/local or /opt, or anywhere
> else that's outside of Debian's knowledge.  Debian would not know that
> the library is still being used, and therefore might autoremove it.
> 
> The impact of this is directly proportional to how many things you
> compile yourself, and how important those things are to you.
> 

If you manually installed shared library, did autoremove removed
it/proposed to removed it? Or, it was installed as dependency of some
other package that you removed? If former, it is bug. If later, you
should have mark it as manually installed, if your compiled software
depends on it.

Also, if you compile third party programs, there are ways to make debian
packages out of them and keep yourself and your preferred debian package
tool happy. Just saying.

Re: Darn 'beep' stoped working after installing Stretch in place of Jessie

[Dejan Jocic]

On 01-08-17, RavenLX wrote:
> On 08/01/2017 11:17 AM, Dejan Jocic wrote:
> > On 01-08-17, RavenLX wrote:
> > > Having it work out-of-the-box would be nice. After a fresh install, I 
> > > have a
> > > bash script I run that installs all the apps I use and configures them.
> > > Sometimes though, there are things that a user needs to answer. Thus, if I
> > > want to have the script running and go do something else, I want to "beep"
> > > when it's going to need attention by the user. I noticed this does not 
> > > work
> > > in Stretch so I ended up removing the part to install the "beep" package 
> > > and
> > > use beep to alert the user. I have tried escape codes via echo -e as well,
> > > and no beep there either.
> > > 
> > 
> > Does printf "\a" works for you? Though, echo -e "\a" works here too.
> 
> I just now tried it in Konsole. Nope, doesn't work.
> 

I do not have Konsole here and did not use it for a long time, but in
Xterm there are setting for terminal bell, so there are in
gnome-terminal. Perhaps there are those settings in Konsole too. Under
preferences, or some such thing.

Re: No ifconfig [Was: no /etc/inittab]

[Dejan Jocic]

On 15-08-17, Erik Christiansen wrote:
> On 15.08.17 15:03, Dejan Jocic wrote:
> > And what exactly do you miss in ifconfig and net-tools package, that you
> > can not do with ip, which is part of iproute2 package that comes as part
> > of base system?
> 
> Around 30 years of familiarity across many *nix flavours. If the package
> builders are more familiar with ip, then perhaps tradition goes out the
> window. Not a problem. I have installed net-tools.
> 
> Erik
> 

I can understand that very well, even with much less years of
familiarity. But it moves forward, for good or worse. Not first familiar
tool that will vanish, nor last. May we live to see many more. I know
that I've thought something like "you will pry ifconfig out of my cold
dead heands" first time I've used ip. But, time passed and ip almost
become familiar tool.

Re: Btrs vs ext4. Which one is more reliable?

[Dejan Jocic]

On 11-08-17, Christian Seiler wrote:
> Am 2017-08-10 16:02, schrieb Dejan Jocic:
> > On 10-08-17, David Wright wrote:
> > > On Thu 10 Aug 2017 at 07:04:09 (-0400), Dan Ritter wrote:
> > > > On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:
> > > > > On Sat, 29 Jul 2017 04:59:40 +
> > > > > Andy Smith <a...@strugglers.net> wrote:
> > > > >
> > > > > Also, my use case is at home where the power can and *does* fail. I 
> > > > > also
> > > > > find myself using the latest kernel and oftentimes an experimental 
> > > > > driver
> > > > > for my AMD graphics card, hence my need for a *very* stable fs over
> > > > > sudden unmount.
> > > >
> > > > Buy a cheap UPS with a USB or serial connection to your
> > > > computer. Even if it only supplies power for 2 minutes, that's
> > > > enough time for the computer to receive the power outage signal
> > > > and do an orderly shutdown.
> > > 
> > > Two minutes barely covers the timeouts that can often occur when
> > > shutting down systemd; the commonest timeout period here seems
> > > to be 90 seconds. I wouldn't mind reducing them if that's possible.
> > > Processes got just a few seconds with sysvinit before they were
> > > killed.
> > > 
> > 
> > Yes, those 90 sec waiting for nothing is one of the most annoying
> > "features" of systemd that I would love to get rid of.
> 
> You can set TimeoutStopSec= for some units explicitly, for example
> via drop-in. Example:
> 
> mkdir -p /etc/systemd/system/XYZ.service.d
> cat > /etc/systemd/system/XYZ.service.d/stop-timeout.conf < [Service]
> TimeoutStopSec=10s
> EOF
> 
> Even if the service is only provided by an init script this will
> still work.
> 
> You can also set DefaultTimeoutStopSec= in /etc/systemd/system.conf
> to alter the default for all units (though individual settings for
> units will still override that).
> 

Thank you for suggestion. I did find that solution, some time ago, can't
remember exactly where. But it was followed by warning that it is bad
idea, can't remember exactly why. Do you have any hint of why it could
be bad idea to limit timeout, or I've just misunderstood whatever I've
read about it?

> > And most annoying
> > aspect of it is that problem is rarely constant. It can exist in one
> > release in systemd, vanish in other, and then come back again in next
> > release. And it can occur once in every 10 shutdowns/reboots, or not
> > occur once in every 10 shutdowns/reboots.
> 
> That is an indication that you have a race condition during
> shutdown.
> 
> The "90s" thing is basically just systemd saying: yeah, I've tried
> to shutdown a specific unit and it's still active, now I'm going
> to wait for the timeout before I send a hard SIGKILL. You can't
> really compare that to sysvinit, because sysvinit doesn't actually
> track processes properly, so what most often would happen is that
> the init script would send a TERM signal to a process, the better
> ones maybe also a KILL signal after some time, before they'd just
> consider the service stopped. But if other processes had been
> started by the service, sysvinit wouldn't care about them, and
> only kill those in the final "let's kill all that's still left
> over" killing spree. systemd by contrast actually tracks what's
> happening with a service and kills the remaining processes.
> 
> That said: what could happen here is that the systemd unit created
> for a given service has a bug. For example it could not be ordered
> correctly and hence systemd tries to stop it too early while other
> services still depend on it.
> 
> Or the stop command that is called by systemd hangs because it
> tries to do something that it shouldn't do during shutdown (for
> example start another service).
> 
> See the following page for information on how to debug shutdown
> issues with systemd (and keep in mind that Debian has systemd stuff
> installed  in /lib and not /usr/lib):
> https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
> 
> I've found systemd to be far more reliable during shutdown (even
> if you have to wait for a timeout if something's gone wrong),
> because at least there is a timeout. With sysvinit I've sometimes
> had the problem that a shutdown script would hang and then nothing
> further would happen and the computer would never properly shut
> down. This was especially frustrating with headless machines. What
> systemd does do is make it much more apparent if there's a
> misconfiguration somewhere.
> 
> Regards,
> Christian
> 

Thank you for your explanation. I do understand why it is happening, did
some reading about that subject even before I've ran on that bug, but it
is still annoying. As for more reliable during shutdown part, not in
my experience, at least on Stretch. It was on Jessie though, where that
feature was hitting me not more than once in every 15-20
shutdowns/reboots. 


Anyway, thank you for your time and help.

Re: No ifconfig [Was: no /etc/inittab]

[Dejan Jocic]

On 15-08-17, Erik Christiansen wrote:
> On 15.08.17 13:33, Nicolas George wrote:
> > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > If it's no longer part of the base system, then perhaps the system is
> > > too base?
> > 
> > Please ellaborate. Why should ifconfig be part of the base system?
> 
> With pleasure. It is the most basic and useful *nix networking tool,
> traditional since well back in the last millennium, spanning hp-ux,
> sunos, then solaris, and various linux distros, in my experience. Even
> if used mostly interrogatively these days, it is the quickest way to
> check how "eth0" is currently encrypted, what the IP address is, etc. It
> is not anything which needs to be added - we just need busybodies to
> refrain from taking it out.
> 
> Granted, there's quite a bit of cruft taking up space, like
> NetworkMunger. I've been forced to wipe that from several Ubuntu
> versions in particular, as networking wouldn't function until I did.
> Everything has always been sweet once that was gone. Debian does seem to
> have it more under control, though, so I'll trade - leave both.
> 
> Erik
> 

And what exactly do you miss in ifconfig and net-tools package, that you
can not do with ip, which is part of iproute2 package that comes as part
of base system?

Re: no non-free firmware on lapton, no Ethernet, related?

[Dejan Jocic]

On 09-08-17, Emanuel Berg wrote:
> Dejan Jocic wrote:
> 
> > Well, you should have write down what was
> > missing during installation, those messages
> > you get for reason. Also, when you have
> > firmware and you get note that it is missing,
> > it is best to abort installation and download
> > needed firmware and put in USB you can insert
> > during installation.
> 
> Well, I can redo the installation!
> 
> Actually I just tried that, and what is missing
> is b43/ucode13.fw .
> 
> I downloaded this archive [1] and copied the
> files (the archive as well as all the files,
> unpacked) onto a USB stick.
> 
> However inserting it didn't help because after
> a short while of "looking" (?) the same error
> message came up again.
> 
> [1] 
> http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/firmware.zip
> 
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> 

Did you check among those files if there is firmware that you need?
Also, if you have another USB stick, just to be sure, try with it too?
>From quick search in debian packages, these are all related to b43:

https://packages.debian.org/jessie/firmware-b43-installer

https://packages.debian.org/jessie/b43-fwcutter

https://packages.debian.org/jessie/firmware-b43legacy-installer

So check if your hardware is related to any of those. Also, once, for
reason unknown to me, firmware from usb did not work, but installer with
firmware on it did. Could be that it was USB fault, though not sure
about it. Was using that USB without problem after that.

Re: Btrs vs ext4. Which one is more reliable?

[Dejan Jocic]

On 10-08-17, David Wright wrote:
> On Thu 10 Aug 2017 at 07:04:09 (-0400), Dan Ritter wrote:
> > On Wed, Aug 09, 2017 at 09:46:09PM -0400, David Niklas wrote:
> > > On Sat, 29 Jul 2017 04:59:40 +
> > > Andy Smith  wrote:
> > > 
> > > Also, my use case is at home where the power can and *does* fail. I also
> > > find myself using the latest kernel and oftentimes an experimental driver
> > > for my AMD graphics card, hence my need for a *very* stable fs over
> > > sudden unmount.
> > 
> > Buy a cheap UPS with a USB or serial connection to your
> > computer. Even if it only supplies power for 2 minutes, that's
> > enough time for the computer to receive the power outage signal
> > and do an orderly shutdown.
> 
> Two minutes barely covers the timeouts that can often occur when
> shutting down systemd; the commonest timeout period here seems
> to be 90 seconds. I wouldn't mind reducing them if that's possible.
> Processes got just a few seconds with sysvinit before they were
> killed.
> 

Yes, those 90 sec waiting for nothing is one of the most annoying
"features" of systemd that I would love to get rid of. And most annoying
aspect of it is that problem is rarely constant. It can exist in one
release in systemd, vanish in other, and then come back again in next
release. And it can occur once in every 10 shutdowns/reboots, or not
occur once in every 10 shutdowns/reboots.

Re: name for wireless interface

[Dejan Jocic]

On 12-08-17, pe...@easthope.ca wrote:
> A TL-WN722N adapter connected to a stretch system gives these results.
> 
> peter@imager:~$ lsusb | grep Ath
> Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
> 
> root@imager:/home/peter# iwlist scan
> wlxa0f3c10a28f7  Interface doesn't support scanning : Network is down
> 
> loInterface doesn't support scanning.
> 
> eth0  Interface doesn't support scanning.
> 
> What is the origin of the long name, wlxa0f3c10a28f7?
> Can a shorter name be assigned?
> 
> Thanks,   ... Peter E.
> 
> 
> -- 
> 
> 123456789 123456789 123456789 123456789 123456789 123456789 123456789
> Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
> http://easthope.ca/Peter.html  Bcc: peter at easthope. ca
> 

It was asked many times on this list, and all around generally. Best
answer would be to look here:

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

It has full explanation of why those long names and what to do if you do
not like it. It is easy to assign shorter name, if you wish so and is
explained nicely, with 3 possible methods.

Re: no non-free firmware on lapton, no Ethernet, related?

[Dejan Jocic]

On 10-08-17, Emanuel Berg wrote:
> Dejan Jocic wrote:
> 
> > Also, once, for reason unknown to me,
> > firmware from usb did not work, but installer
> > with firmware on it did. Could be that it was
> > USB fault, though not sure about it.
> > Was using that USB without problem
> > after that.
> 
> What should I do with the installer?
> 
> Do you mean this file:
> 
> https://packages.debian.org/jessie/all/firmware-b43-installer/download
> 
> ?
> 
> -- 
> underground experts united
> http://user.it.uu.se/~embe8573
> 

No, I meant downloading installer with firmware included, like for
example this one for Jessie:

https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/archive/8.9.0+nonfree/multi-arch/iso-cd/

and this one for Stretch

https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/9.1.0+nonfree/multi-arch/iso-cd/

Those are multiarch net install CDs that will work both for 32-bit and
64-bit PCs. You just need to choose your arch when you boot into
installer. But, if you do not want to download and use those and that
downloaded firmware did not work for you, you can download just those
packages that you need and install them with dpkg. But you will have to
do same with dependencies of those packages. Also, you mentioned that
you need your ethernet to work, these b43 packages are for Broadcom
wireless cards. 

Whatever that you choose to do, do not forget to check your
/etc/apt/sources.list file and add contrib and non-free after main
wherever it is needed, something like this:

deb http://deb.debian.org/debian/ jessie main contrib non-free

Hope that this helps.

Re: alt ctrl T - terminal not opening

[Dejan Jocic]

On 17-07-17, to...@tuxteam.de wrote:
> On Mon, Jul 17, 2017 at 08:39:25AM +0100, kelsang sherab wrote:
> > Using Stretch with GNOME 3
> > I am unable to add shortcut to open terminal.
> > suggestions are welcomed.
> 
> Sorry to hear that. To help people help you, you might want to provide
> more details:
> 
>   - what is your desktop environment (e.g.: are you using Gnome? KDE?
> Mate? -- there are more)... or no desktop environment at all?
> 
>   - what have you tried to add your shortcut? In which way did it fail
> to work?
> 
> Regards
> -- tomás
> 

He already stated that it is Gnome 3. In Gnome 3, go to settings ( top
right corner where those icons are click, buton with key and screwdriver
), then go to keyboard. Scroll all down to bottom, you will find + sign.
Click it and you will be able to assign custom shortcut.

Re: How to gain control over the system? [a security-side-note]

[Dejan Jocic]

On 09-07-17, Eike Lantzsch wrote:
> On Sunday, 9 July 2017 14:54:02 -04 Kaj Persson wrote:
> > 
> > * Configuring sudo? No I have not done that explicitly, not more than
> > what the install program did itself. I have looked at /etc/sudoers and
> > what I think the important lines are:
> > 
> >  # User privilege specification
> >  rootALL=(ALL:ALL) ALL
> > 
> >  # Allow members of group sudo to execute any command
> >  %sudo   ALL=(ALL:ALL) ALL
> There the "security" went out of the building ...
> Please have a look here:
> https://blather.michaelwlucas.com/archives/2266

It does not matter really ( though it is really nice lecture about sudo
), because it is personal machine. Settings like that on personal
machine are really fine. 

> > 
> >  #includedir /etc/sudoers.d
> > 
> > In /etc/sudoers.d there are no more files than README.
> > 

Re: pop-up windows all the time in Firefox, Stretch

[Dejan Jocic]

On 09-07-17, Anil Duggirala wrote:
> hello,
> Ever since I moved to Stretch I have had pop-up windows popping up all
> the time (clicking on various items on various types of pages). I am
> posting here, since this is only happening in my Debian installation.
> Was anything changed in the default configuration of Firefox. It feels
> like Windows with all of these pop-ups, this is the first time I
> experience anything like this in a linux installation.
> thanks,
> 

In firefox you have option to block pop-up windows. Go to preferences,
it is under content. And install some add blocker. For me, best is :

https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/

You can also install script blocker, like this one:

https://addons.mozilla.org/en-US/firefox/addon/noscript/?src=ss

With all that on, you will be pretty safe against pop-ups.

Re: dhclient or network problem

[Dejan Jocic]

On 10-07-17, Franz Angeli wrote:
> Hi,
> 
> i have a problem with dhclient:
> 
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
> 
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   Socket/fallback
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 
> tcpdump during dhclient doesn't show anything?!?
> 
> root@*:~# tcpdump -i eno52
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> 
> 
> root@***:~# ip addr show eno52
> 9: eno52:  mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> 
> 
> if i use the same ethernet cable on my laptop all works fine...

Don't you think that you have enough of a clue there :P That eno52 is,
as you can see ethernet card, of course it will work when you connect it
with ethernet cable. If you want it to work with wifi, that is another
story. What is your wifi card, do you have something starting with w in
the output of ip addr show? What is the output of the lspci -v | grep -i
-A6 net?
> 
> i don't know if is a module problem...or?
> 
> Can you help me?
> 
> BR
> 

Re: Debain 9 dhclient or network problem

[Dejan Jocic]

On 11-07-17, Franz Angeli wrote:
> Hi,
> 
> i have a problem with dhclient:
> 
> for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> BCM5719 Gigabit Ethernet PCIe (rev 01) :
> 
> root@:~# dhclient eno52 -v
> Internet Systems Consortium DHCP Client 4.3.5
> Copyright 2004-2016 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   LPF/eno52/3c:a8:2a:e7:87:bf
> Sending on   Socket/fallback
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> 
> tcpdump during dhclient doesn't show anything?!?
> 
> root@*:~# tcpdump -i eno52
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> 
> 
> root@***:~# ip addr show eno52
> 9: eno52:  mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> 
> interface eno52 seems to be disconnected but cable is plugged and
> working (i tried with other pc)
> 
> obviously ethernet cable is connected...
> Debian 8 works fine with this hw
> Debian 9 doesn't work
> 
> Server is ProLiant DL380 Gen9 (719064-B21)
> 
> root@***:~# lspci -v | grep -A10 Ethernet
> 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92c9 (64-bit, prefetchable) [size=64K]
> Memory at 92ca (64-bit, prefetchable) [size=64K]
> Memory at 92cb (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9310 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable+ Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
> Memory at 92c6 (64-bit, prefetchable) [size=64K]
> Memory at 92c7 (64-bit, prefetchable) [size=64K]
> Memory at 92c8 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9314 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.2 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92c3 (64-bit, prefetchable) [size=64K]
> Memory at 92c4 (64-bit, prefetchable) [size=64K]
> Memory at 92c5 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 9318 [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 02:00.3 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331i Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 17, NUMA node 0
> Memory at 92c0 (64-bit, prefetchable) [size=64K]
> Memory at 92c1 (64-bit, prefetchable) [size=64K]
> Memory at 92c2 (64-bit, prefetchable) [size=64K]
> [virtual] Expansion ROM at 931c [disabled] [size=256K]
> Capabilities: [48] Power Management version 3
> Capabilities: [50] Vital Product Data
> Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
> Capabilities: [a0] MSI-X: Enable- Count=17 Masked-
> Capabilities: [ac] Express Endpoint, MSI 00
> --
> 04:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5719
> Gigabit Ethernet PCIe (rev 01)
> Subsystem: Hewlett-Packard Company Ethernet 1Gb 4-port 331FLR Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
> Memory at 92b9 (64-bit, prefetchable) [size=64K]
> Memory at 92ba (64-bit, prefetchable) [size=64K]
> Memory at 92bb (64-bit, prefetchable) 

Re: Advice on Debian installation

[Dejan Jocic]

On 08-07-17, Fungi4All wrote:
> From: sebastian.luna.val...@gmail.com
> 
> > Great, many thanks for your quick replies!
> > Will try that, fingers crossed!
> 
> Don't listen to those ubuntu haters, nothing will happen.
> Leave it as is. When debian installs its version of grub
> on /dev/sda it will be in control and provide you boot entries
> for win7, ubuntu, and Debian. If you log back to Ubuntu
> and $sudo grub-install /dev/sda
> $sudo update-grub it will gain back control and create
> the same boot entries for all three but ubuntu will be
> first choice. At least this way you will not have to look
> at the ugly green debian snail screen when you wake
> up in the morning! :)
> As long as you are not including an Arch/Manjaro
> installation you will be fine with either grub. I have had
> up to seven of them (it only takes a few kb of space).
> Delete the ubuntu partition and you will be OK!
> Tell this to the ausie guy that installed stretch from scratch and
> lost all networking! 3-4 days ago. At least this man can download
> all the gpg stuff and the deb files that were needed from ubuntu
> and pass them to the half broken isolated debian installation.
> Just keep your fingers crossed and debian might even work
> first time around.

Do you even bother to read other people posts? He wants to install
Debian where Ubuntu install is. He wants to replace it.

Re: SAMBA problems on Debian 8.8

[Dejan Jocic]

On 15-07-17, Hans Kraus wrote:
> Hi,
> 
> yesterday, 14. July, about 9:30 pm my SAMBA shares on Debian simply
> stopped working. I did not do anything on the system.
> 
> When I now try to connect to them from Windows 8.1 I do not see them
> in the "Connect Network Drive" window.
> 
> When I enter the address manually I get the error "The connection isn't
> accepted from the remote device ...".
> 
> All texts are my translations from German, so the will be only
> approximately correct.
> 
> Any advice for me and what debug info shall I supply?
> 
> Kind regards,
> Hans
> 

Samba had 2 security updates, first one had messed up dependencies and
second one solved that. Perhaps you just updated first one and need to
do update/upgrade again to catch up second one?

Re: Can debian-live-9.0.1-i386-lxde be made to install from USB?

[Dejan Jocic]

On 18-07-17, Erik Christiansen wrote:
> On 18.07.17 08:46, Thomas Schmitt wrote:
> > Afaik, unetbootin unpacks the ISO and replaces the boot loader software.
> > Debian discourages its use with live and installation ISOs.
> > 
> > The Debian ISOs for i386 are ready to be simply copied onto the device
> > file of the overall USB stick (i.e. to /dev/sdX not to /dev/sdX1).
> 
> Ah, they're what's described as a .img on other sites, then. I chose
> unetbootin in lieu of a dd copy, based on the .iso suffix.
> 
> > After ensuring that /dev/sdd really is the device address of the USB
> > stick, you just do
> > 
> >   dd if=debian-live-9.0.1-i386-lxde.iso bs=4M of=/dev/sdd ; sync
> > 
> > See
> >   https://www.debian.org/CD/faq/#write-usb
> 
> The dd copied the image fine, the Udoo X86 booted on it, and I
> began the install. Sadly, it barfed at the same stage - after setting
> geographic location and keyboard, the debian 9 install process threw up
> a "Detect and mount CD-ROM" screen, insisting on a CD with suitable
> install content. It seemed quite unaware that it is installing from USB.
> 
> Performing a "continue" and a "skip" returns to the "Debian installer
> main menu", with the cursor on "Detect and mount CD-ROM". The dufus
> thing is still obsessing about CDs, despite the web page promising that
> it can do a USB install.
> 
> Are we just up against false advertising? The USB holds ten times what a
> CD can, so there's no rational reason for last-century media to be
> involved.
> 
> I'll wrassle ten years of cabling pile-up on the back half of the desk,
> move the Udoo to the near end of the coffee table, and string an
> ethernet cable over. Maybe a net install will work.
> 
> Erik
> 


This release of Debian came with buggy live images. It was fixed with
9.0.1 live images, or at least it seemed so. Perhaps you discovered bug
in it that should be reported. Unfortunately, debian live images do not
get much needed love and because of that are not really preferred method
of installing. You should be fine with net install image, or with
regular dvd-1 iso image, be it from usb, or from dvd.

Re: Connessione wifi

[Dejan Jocic]

On 18-07-17, Gabriele Cossetti wrote:
> Ascoli Piceno - Italia - 18/07/2017
> 
> Ho appena installato la versione Debian 9.0, ho una connessione WI-FI su 
> PC IBM .386 che usa una porta USB del seguente produttore:
> 
> WI-FI USB Sitecom adapter N150
> 
> e dopo l'installazione non risulta funzionante.
> 
> Cosa devo fare per renderla funzionante?
> 
> Cordiali saluti
> Gabriele Cosssetti
> 

Since this is mailing list on English language, if you would feel more
comfortable asking for help on Italian, you could try on Italian
speaking debian users list here:

debian-ital...@lists.debian.org

or web page here:

https://lists.debian.org/debian-italian/

Re: Can debian-live-9.0.1-i386-lxde be made to install from USB?

[Dejan Jocic]

On 18-07-17, Jason Wittlin-Cohen wrote:
> Many people have had issues installing with the Live installer on this
> mailing list.  The question is why Debian even offers the option if there
> is no interest in testing it to make it work.  The initial live installer
> images (9.0, before 9.0.1) were completely broken and could not even begin
> the install[1].  Clearly, this resulted from a complete lack of testing as
> it would have been easily caught given that it is a deterministic error
> that to applied to ALL the live ISOs.  I think it's unfair to blame users
> for using the Live media as an installer.  Either test the live images to
> make sure it can be used for installation on a wide variety of hardware, or
> don't provide the option at all.  It appears that the debian-devel mailing
> list HAS called for more testing due to this situation with the explicit
> threat that live images will cease to be produced if nobody wants to test
> them [2].  With that said, users should always use the regular d-i
> installer images to do an actual install.  The live images are useful for
> testing to see if your hardware is supported and also for recovery.
> 
> Takeaway:  If you want to install Debian, either use the network installer
> (small installation image) or use one of the DVD images (large installation
> images), NOT the live disks.  You can download either here:
> https://www.debian.org/distrib/.  Only use the Live ISOs to test out Debian
> and to ensure hardware support.  If you have a need for non-free firmware
> to complete the install (e.g. non-free network firmware for wifi devices),
> use the images here
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.0.0+nonfree/amd64/bt-dvd/
> .
> 
> [1]https://cdimage.debian.org/debian-cd/9.0.1-live/amd64/iso-hybrid/
> [2] https://lists.debian.org/debian-devel/2017/06/msg00335.html
> 

Trouble is that live images are, judging by my torrents, most popular
media of choice. Just debian-live-9.0.1-amd64-gnome.iso was uploaded for
23 GB, while debian-9.0.0-amd64-DVD-1.iso is on 14.68 GB and
debian-9.0.0-amd64-netinst.iso is on 463 MB. So, something in big red
letters should be there on Debian site as a warning for people not to
download live for install. At least till we get 9.0.2 live iso.

Re: Can debian-live-9.0.1-i386-lxde be made to install from USB?

[Dejan Jocic]

On 18-07-17, Jason Wittlin-Cohen wrote:
> That's not exactly what I'm seeing.  I began seeding the Debian 9.0
> installer image on 6/17 and the Live image on 6/20, when the 9.0.1 released.
> 
> debian-9.0.0-amd64-DVD-1.iso  171.36 GB
> debian-live-9.0.1-amd64-gnome.iso 157.90 GB
> debian-live-9.0.1-amd64-cinnamon.iso  107.85 GB
> debian-9.0.0-amd64-netinst.iso  3.50 GB
> 
> The net install doesn't really count since the Debian site has a direct
> link to download it, and people are unlikely to bother with such a small
> download over Bittorrent.
> 
> Note:  Dejan, sorry for the direct email. Meant to email the list.
> 

No worries, happens. As for those numbers you've got, you do realise
that just those 2 live images you seed are more popular than regular
install iso? And that there are 4 more DE in torrent live images that
are about as popular as Cinammon is? Now, calculate how many pissed
people that was, because those live images failed to install? And there
was some trashing of Debian in some reviews because of those live
images. Not that I care much about those reviews personally, I know why
I use Debian and why it is my favorite OS. But on the long run, more
happy users equals better Debian for us all.

Re: How to gain control over the system?

[Dejan Jocic]

On 10-07-17, Kaj Persson wrote:
> Hi Jimmy,
> Well, I did not follow your suggestion exactly, but as people has said, the
> root account is already and always  there, even it has not been assigned a
> password. So, against my real whish, not to activate the root account, I
> gave the command sudo passwd root, and entered a password. And now I suppose
> I have burned my ships and have no way back...
> 
> But! Nothing has changed. I can still not enter program icons to the panel,
> and not define keyboard shortcuts. If I sort the icons on the desktop they
> still, after a cold start, come back in a completely other order, dispite I
> had marked "Keep ajusted" (right click on desktop).
> 
> So...?
> /Kaj
> 

What are you talking about, there are several ways to lock your root
account? Not sure why you would like to though. You can lock it with
sudo, like this:

sudo passwd -l root

But that is not really necessary. Better would be to learn how to
strengthen your root account. Depending on what you really want to
achieve, you can set it up so only way to access it would be to use su,
or sudo from trusted accounts. If you are interested in that, further
reading you can find here:

https://www.centos.org/docs/5/html/5.1/Deployment_Guide/s2-wstation-privileges-noroot.html

Re: How to gain control over the system?

[Dejan Jocic]

On 09-07-17, Anders Andersson wrote:
> On Sun, Jul 9, 2017 at 12:51 AM, Fungi4All  wrote:
> 
> > On Sat, 2017-07-08 at 23:57 +0200, Kaj Persson wrote:
> >
> > > But now I discovered an issue, I cannot manage my desktop. I have
> > > always at the previous installations, and they are quite many now, been
> > > advised to, for security reason, leave the root password unset, which
> > causes
> > > the root account go passive, and for all tasks where I need root
> > > authority I  go via su/sudo.
> >
> >
> > It is a bad idea despite of what security gurus may advise.  You may lose
> > your system
> > and never get it back.
> >
> 
> 
> It's an even worse idea to listen to people on the internet who ignore
> "security gurus" based on rumours. You can easily restore or change the
> root password if it's lost or unset.

Leaving root password unassigned for "security" reasons is silly.
Heaving, or not heaving root account assigned does not make your system
any more secure. For some things you do need root account. Those systems
that use sudo only approach ( read Ubuntu and derivates ) have sulogin
patched to allow single user mode, for example. And it is made so on
Ubuntu out of fear that new users attracted to Linux will mess up things
more if they have access to root account. Not that it stopped people to
be people and to mess things up equally successful with sudo account. As
for those "security gurus", who are they? Real gurus? Or just people
repeating what they've read somewhere with little to no understanding
what they've read?

Re: Apt-get Upgrade Problem in Stretch?

[Dejan Jocic]

On 19-07-17, Patrick Bartek wrote:
> On Wed, 19 Jul 2017 13:47:27 -0700 Jimmy Johnson
> <field.engin...@gmail.com> wrote:
> 
> > On 07/19/2017 01:35 PM, Patrick Bartek wrote:
> > > On Wed, 19 Jul 2017 20:14:28 +0200 Dejan Jocic <jode...@gmail.com>
> > > wrote:
> > > 
> > >> On 19-07-17, Patrick Bartek wrote:
> > >>> Getting no results from apt-get upgrade after a week.  Can install
> > >>> apps, etc., but get no security or stretch-update "fixes," etc.  I
> > >>> find this unusual.  Did a mail list archive search for this, but
> > >>> didn't find anything specific. Or did I miss the solution?
> > >>>
> > >>> My Test Setup:
> > >>>
> > >>> Stretch Stable 64-bit from net-install disk in Virtualbox 5.1 on a
> > >>> Wheezy host.  Basic terminal install (no GUI), converted to
> > >>> sysvinit (did not do anything to systemd files. Kept as
> > >>> dependencies) and then added xorg, openbox window manager, etc.
> > >>>
> > >>> Thanks for any feedback.
> > >>>
> > >>> B
> > >>>
> > >>
> > >> dpkg -s unattended-upgrades
> > > 
> > > Not installed either by me or the installer
> > > 
> > >> If it is installed, it did your updates and security upgrades for
> > >> you. If you do not like it and want to do manual updates/upgrades,
> > >> do with root privs:
> > > 
> > > I have always done this manually since I first started using Debian
> > > (Sarge).  And always will.  This is my personal machine.
> > > 
> > >> sed -i 's/1/0/g' /etc/apt/apt.conf.d/20auto-upgrades
> > >>
> > >> For further reading and understanding:
> > >>
> > >> https://wiki.debian.org/UnattendedUpgrades
> > > 
> > > Thanks for the reference.  I've been aware of this for a long time,
> > > but chose not to use it.
> > > 
> > > My problem must be something else.
> > 
> > You also have packagekit and discover to deal with and who knows what 
> > else. Stopping auto-install is not that difficult, but stopping 
> > auto-update is a problem.
> 
> I think you've assumed some things incorrectly.  I did a basic terminal
> only install with only basic system utilties, the last option on the
> list.  No Desktop of any kind. No xserver.  Packagekit is not
> installed.  Discover was as a dependency, but I didn't install it
> explicitly. No auto-install or auto-update either. I converted to
> sysvinit, but left systemd stuff as dependencies.  Later will install
> xorg and openbox, etc. for my GUI. This is the same way I installed
> Wheezy 5 years ago. And it works (and always has) fine.
> 
> FWIW, a few months ago, I installed Stretch RC2 the same way to test it
> and everything worked including apt-get update, upgrade, etc.
> 
> So, something is wrong.  And I won't install it for real until I
> discover what.
> 
> B
> 

If you have minimal install, why do you suspect that something is wrong,
rather to suppose that all is fine and that simply there was no security
updates for your install? It is stable now, and as far as i can
remember, all those security updates we did have of lately were somehow
tied for graphical part, plus apache and ngninx. Apart for security
updates, tough luck of getting some other updates on stable. And
"everything worked fine" on your install of Stretch RC2 because it was
still testing and there was much more updates then?

Re: Apt-get Upgrade Problem in Stretch?

[Dejan Jocic]

On 19-07-17, Patrick Bartek wrote:
> Getting no results from apt-get upgrade after a week.  Can install apps,
> etc., but get no security or stretch-update "fixes," etc.  I find
> this unusual.  Did a mail list archive search for this, but didn't find
> anything specific. Or did I miss the solution?
> 
> My Test Setup:
> 
> Stretch Stable 64-bit from net-install disk in Virtualbox 5.1 on a
> Wheezy host.  Basic terminal install (no GUI), converted to sysvinit
> (did not do anything to systemd files. Kept as dependencies) and then
> added xorg, openbox window manager, etc.
> 
> Thanks for any feedback.
> 
> B  
> 

dpkg -s unattended-upgrades

If it is installed, it did your updates and security upgrades for you.
If you do not like it and want to do manual updates/upgrades, do with
root privs:

sed -i 's/1/0/g' /etc/apt/apt.conf.d/20auto-upgrades

For further reading and understanding:

https://wiki.debian.org/UnattendedUpgrades

Re: Apt-get Upgrade Problem in Stretch?

[Dejan Jocic]

On 20-07-17, Patrick Bartek wrote:
> On Thu, 20 Jul 2017 08:48:17 +0200 Dejan Jocic <jode...@gmail.com>
> wrote:
> 
> > 
> > If you have minimal install, why do you suspect that something is
> > wrong, rather to suppose that all is fine and that simply there was
> > no security updates for your install? It is stable now, and as far as
> > i can remember, all those security updates we did have of lately were
> > somehow tied for graphical part, plus apache and ngninx. Apart for
> > security updates, tough luck of getting some other updates on stable.
> > And "everything worked fine" on your install of Stretch RC2 because
> > it was still testing and there was much more updates then?
> 
> That was my first thought.  And as I used a Stable net-install disk
> for my first tests of Stable, the system would have been up-to-date
> after the install. But it's been two weeks since that time.  I've added
> X, a window manager, utilities, apps, etc.  Based on my past
> experience, historically, there should have been some fixes.  I've
> never come across any such new release -- Debian or others -- that
> didn't need a plethora of fixes in those few days to a month after.  Or
> perhaps Stretch is bug free.  Or as I said in another post: Maybe the
> maintainers are taking a vacation.
> 
> As far as RC2:  I dist-upgraded it to Stable in the course of my tests.
> And as soon as it hit stable, apt-get upgrades ceased producing
> anything for a week.  So, I downloaded the Stable net-install CD for a
> new install to see if there was any differences.
> 
> B
> 

Yes, but did you really check if security updates debian stable had
during those 2 weeks included packages that you have installed, or not?
Your past experience is past, this is another install. Just take look at
security updates and compare, there is no much philosophy there:

https://www.debian.org/security/

Look under recent advisories.

Re: how to make sure that gnome check available updates to system

[Dejan Jocic]

On 25-07-17, iqwue Wabv wrote:
> Thank you Dejan.  I will check these logs.
> 
> Additionally I've noticed an empty file
> /var/log/unattended-upgrades/unattended-upgrades-shutdown.log
> What is it used for?
> Regards, Karol Szkudlarek
> 

Never used it, but my guess is that it is used for some options that you
can set in /etc/apt/apt.conf.d/50unattended-upgrades and that involves
shut down, or reboot.

Re: memory.limit_in_bytes: systemd vs lxc

[Dejan Jocic]

On 25-07-17, Harald Dunkel wrote:
> Hi Dejan,
> 
> On Mon, 24 Jul 2017 09:43:30 +0200
> Dejan Jocic <jode...@gmail.com> wrote:
> 
> > On 24-07-17, Harald Dunkel wrote:
> > > 
> > > Apparently systemd ignores the restricted memory. How can I tell 
> > > systemd to keep the limits?
> > > 
> > > 
> > > Every helpful comment is highly appreciated
> > > Harri
> > >   
> > 
> > Never did it myself, but perhaps this can help you:
> > 
> > https://www.freedesktop.org/software/systemd/man/systemd.exec.html#LimitCPU=
> > 
> > 
> Thanx for the pointer, but I think this is a misunderstanding.
> I want systemd to keep(!) the limits, not have another local 
> config file. Systemd should not be allowed to extend the limits 
> bound to the container, no matter what.
> 
> 
> Regards
> Harri

Well, I agree with you, it should not. But other solution would be to
file bug against systemd. Hopefully, you will get answer other then "it
is feature, not bug" :P

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Cindy-Sue Causey wrote:
> 
> 
> Ok, so this is where the OP, VigneshDhanraj, could pin their kernel if
> they know the release number... That's a-suming one can pin out of
> numerical sequence...

No, that script is for automatically marking for autoremoval no longer
needed kernels and keeping at least last 2. If he wants to pin it, it is
done as always at /etc/apt/preferences, or even better under some file
under /etc/apt/preferences.d/. Or he can simply use apt-mark to put it
on hold. If that is what he really want. In my opinion, it is better
just to give a shot to new kernel and keep old one just as long as he
needs to be sure that new one works. Besides, if he does not clean apt
archives in /var/cache/apt/archives, he will have there older kernels
that can be installed with dpkg.
> 
> The "deal" about it, the rationale that the toggle is buried there
> would be that pinning, not pinning kernels versus "just" other
> software would most likely matter most to someone who is tech savvy
> enough to have that need. That person would know they need to go
> digging for the toggle that helps preserve their tear stained kernel.
> :)
> 
> Interesting to know. I JUST yesterday downloaded the .xz tar for
> 4.12.3 for purposes of self-education. The new tip learned from this
> thread is perfectly timed and priceless. :)
> 
> Cindy :)
> -- 
> Cindy-Sue Causey
> Talking Rock, Pickens County, Georgia, USA
> 
> * runs with duct tape *
> 

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Greg Wooledge wrote:
> Is there any way to permanently neuter apt-get autoremove, so that even
> if something invokes it against my will, it will *never* remove anything?
> 
> And more, is there a way to get apt and apt-get to *stop* prompting me
> to run it, and *stop* spamming me with a list of packages that it would
> like me to remove?  (Maybe that's the same as the first question, maybe
> not.)
> 
> My strategy so far has been "ignore the spam, and never willingly run
> autoremove".  This mostly works, but I recently learned that tasksel
> will apparently run an autoremove, without warning, whether I want it
> to or not ().
> 
> If autoremove will also remove *kernels*, which this thread seems to
> indicate is the case, then my concerns just went up another notch.
> 
> I suppose one could manually mark each and every single installed
> package as "manually installed", but you'd have to remember to repeat
> this periodically, and it seems clumsy and inelegant compared to some
> sort of master switch that can just tell autoremove to go die in a fire.
> 

Your fear from autoremove is silly. It will not remove anything you
really need and, if you stick to default settings, will keep all
packages it replaced in /var/cache/apt/archives, as far as I know. And
if you have some package that you really, really want to keep, you can
always pin it, or put it on hold with apt-mark. It is not spam, it is
keeping your system clean.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Greg Wooledge wrote:
> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> > When you upgrade to Jessie, it will install new kernel automatically.
> > However, it should not remove your Wheezy kernel, because upgrading
> > kernels always leaves one old one there, in case that you can not boot
> > into your new kernel for some reason. You can then mark that kernel via
> > grub options as one you would like to boot in. You can do it during boot
> > in grub, or by setting it as default in /etc/default/grub.
> 
> All true.
> 
> > You will also
> > have to use apt-mark to put that kernel on hold, to prevent removing it
> > on future updates, or to do some apt pinning.
> 
> False.  The kernel will simply sit there forever, unless you take some
> explicit action to remove it.  No holds or pinning or other wrestling
> required.
> 

That is not true, if you use autoremove. Only 2 last kernels will be
kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
kernels. Jessie kernel is long gone with autoremove.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, Cindy-Sue Causey wrote:
> On 7/25/17, Dejan Jocic <jode...@gmail.com> wrote:
> > On 25-07-17, Greg Wooledge wrote:
> >> On Tue, Jul 25, 2017 at 09:41:24AM +0200, Dejan Jocic wrote:
> >> > When you upgrade to Jessie, it will install new kernel automatically.
> >> > However, it should not remove your Wheezy kernel, because upgrading
> >> > kernels always leaves one old one there, in case that you can not boot
> >> > into your new kernel for some reason. You can then mark that kernel via
> >> > grub options as one you would like to boot in. You can do it during
> >> > boot
> >> > in grub, or by setting it as default in /etc/default/grub.
> >>
> >> All true.
> >>
> >> > You will also
> >> > have to use apt-mark to put that kernel on hold, to prevent removing it
> >> > on future updates, or to do some apt pinning.
> >>
> >> False.  The kernel will simply sit there forever, unless you take some
> >> explicit action to remove it.  No holds or pinning or other wrestling
> >> required.
> >>
> >
> > That is not true, if you use autoremove. Only 2 last kernels will be
> > kept. This is upgrade from Jessie here. I have 4.9.0.2 and 4.9.0.3
> > kernels. Jessie kernel is long gone with autoremove.
> 
> 
> Well, that's a little... scary. *frown*
> 
> Except that... I just deleted the rest of what I first wrote because
> it hit me. Autoremove is what apt-get tells me to use to remove
> packages. that are no longer needed that are no longer
> "dependencies". What it actually tells *me* is something like "apt
> autoremove" (not "apt-get autoremove").
> 
> Aaaa... So in autoremove's mind... It might touch on that previous
> kernel and say... hm, nothing's using it now, nothing needs it to
> function properly, so trash it
> 
> Or something like that there.. :)
> 
> Cindy :)
> -- 
> Cindy-Sue Causey
> Talking Rock, Pickens County, Georgia, USA
> 
> * runs with duct tape *
> 

What it touch is /etc/kernel/postinst.d/apt-auto-removal that generates
/etc/apt/apt.conf.d/01autoremove-kernels file. Those decide what kernels
to keep. And, in case of /etc/kernel/postinst.d/apt-auto-removal it is
clearly stated:

# Mark as not-for-autoremoval those kernel packages that are: - the
# currently booted version - the kernel version we've been called for -
# the latest kernel version (as determined by debian version number) -
# the second-latest kernel version
#
# In the common case this results in two kernels saved (booted into the
# second-latest kernel, we install the latest kernel in an upgrade), but
# can save up to four. Kernel refers here to a distinct release, which
# can potentially be installed in multiple flavours counting as one
# kernel.

Re: how to make sure that gnome check available updates to system

[Dejan Jocic]

On 23-07-17, Karol Szkudlarek wrote:
> Hello,
> I am using GNOME and Debian 9 on my laptop and in the software-properties-gtk 
> program I selected daily updates and display message immediately.
> Laptop is used dual boot mode and I would like to be sure (for security 
> reasons) that Gnome checks automatic available updates properly.
> Is it some log file to verify if checking was performed and when?
> I would like to not to perform manual apt-get update. I have not installed 
> cron-apt.
> Regards,
> 
> Karol Szkudlarek

If you want those updates to be automatic, you should change that
display message immediately to download and install automatically.
As for checking logs, you can check under these:

/var/log/unattended-upgrades/unattended-upgrades.log

/var/log/dpkg.log

With automatic updates enabled, all actions performed will end up there.
Well, in /var/log/dpkg.log other actions, like manually installing
packages will be recorded too, but you will be able to see performed
actions. If you would like to be informed about automatic upgrades with
mail, you will have to edit file:

/etc/apt/apt.conf.d/50unattended-upgrades

and find and uncomment line //Unattended-Upgrade::Mail "root";

Hope that this helps.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 25-07-17, VigneshDhanraj G wrote:
> Hi Team,
> 
> I am using kernel 3.2.x, i know that support from wheezy will be stopped
> soon. can i upgrade to jessie with same kernel version.
> 
> Is that correct way of handling?
> 
> Regards,
> VigneshDhanraj G

When you upgrade to Jessie, it will install new kernel automatically.
However, it should not remove your Wheezy kernel, because upgrading
kernels always leaves one old one there, in case that you can not boot
into your new kernel for some reason. You can then mark that kernel via
grub options as one you would like to boot in. You can do it during boot
in grub, or by setting it as default in /etc/default/grub. You will also
have to use apt-mark to put that kernel on hold, to prevent removing it
on future updates, or to do some apt pinning. But, since Wheezy will be
out of support soon, doubt that you will be able to expect security
updates for that kernel. It would be wise to check if newer kernel works
for you, and if it does to move to it completely and forget about Wheezy
kernel.

Re: Apt-get Upgrade Problem in Stretch?

[Dejan Jocic]

On 19-07-17, Felix Miata wrote:
> Patrick Bartek composed on 2017-07-19 10:29 (UTC-0700):
> 
> > Getting no results from apt-get upgrade after a week.  Can install apps,
> > etc., but get no security or stretch-update "fixes," etc.  I find
> > this unusual.  Did a mail list archive search for this, but didn't find
> > anything specific. Or did I miss the solution?
> 
> > My Test Setup:
> 
> > Stretch Stable 64-bit from net-install disk in Virtualbox 5.1 on a
> > Wheezy host.  Basic terminal install (no GUI), converted to sysvinit
> > (did not do anything to systemd files. Kept as dependencies) and then
> > added xorg, openbox window manager, etc.
> 
> > Thanks for any feedback.
> 
> Did you miss that in Stretch apt is preferred to apt-get?
> -- 
> "The wise are known for their understanding, and pleasant
> words are persuasive." Proverbs 16:21 (New Living Translation)
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata  ***  http://fm.no-ip.com/
> 

What does it have to do with his problem? It does not matter which tool
he is using, apt-get, aptitude or apt. And apt-get is far from
obsolete/depreciated tool and is still preferred and well proven tool of
many.

Re: memory.limit_in_bytes: systemd vs lxc

[Dejan Jocic]

On 24-07-17, Harald Dunkel wrote:
> Hi folks,
> 
> I have to restrict memory.limit_in_bytes to 16GByte for my LXC
> containers. Problem: The containers based on Stretch and systemd 
> show 
> 
> % for i in $(find /sys/fs/cgroup/memory/lxc/lxc1 -name 
> memory.limit_in_bytes); do \
>   echo $i $(cat $i) \
> done | column -t
> /sys/fs/cgroup/memory/lxc/lxc1/memory.limit_in_bytes   17179869184
> /sys/fs/cgroup/memory/lxc/lxc1/user.slice/memory.limit_in_bytes
> 9223372036854771712
> /sys/fs/cgroup/memory/lxc/lxc1/init.scope/memory.limit_in_bytes
> 9223372036854771712
> /sys/fs/cgroup/memory/lxc/lxc1/system.slice/memory.limit_in_bytes  
> 9223372036854771712
> 
> Apparently systemd ignores the restricted memory. How can I tell 
> systemd to keep the limits?
> 
> 
> Every helpful comment is highly appreciated
> Harri
> 

Never did it myself, but perhaps this can help you:

https://www.freedesktop.org/software/systemd/man/systemd.exec.html#LimitCPU=

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 30-06-17, RavenLX wrote:
> I think I might have a problem. I do the sudo apt-get update and then sudo
> apt-get dist-upgrade and ever since I have installed Debian 9 (after the
> official release) I have not seen any updates. Yet in Ubuntu 14.04 server
> there were updates to the kernel and to Apache. I've been watching
> Debian-Security and noticed there are some updates coming up. But I haven't
> seen any when I go to do the update.
> 
> More info:
> 
> I'm using KDE in Debian 9 (Stretch).
> I did NOT install the "KDE" desktop when installing Debian 9. Intead I
> installe the kde desktop package *only* via the command line after
> installing Debian 9. This way I minimized a lot of the bulk and didn't have
> to install application I don't use (like juk and okular, for example).
> 
> - I have removed plasma-discover and plasma-discover-common because I prefer
> to do things the old-fashioned way - via the command prompt.
> 
> Here is my sources.list:
> 
> # Security
> deb http://security.debian.org/ stretch/updates main contrib non-free
> deb-src http://security.debian.org/ stretch/updates main contrib non-free
> 
> # Main
> deb http://deb.debian.org/debian/ stretch main contrib non-free
> deb-src http://deb.debian.org/debian/ stretch main contrib non-free
> 
> # stretch-updates, previously known as 'volatile'
> deb http://deb.debian.org/debian/ stretch-updates main contrib non-free
> deb-src http://deb.debian.org/debian/ stretch-updates main contrib non-free
> 
> # Backports
> deb http://deb.debian.org/debian/ stretch-backports main contrib non-free
> deb-src http://deb.debian.org/debian/ stretch-backports main contrib
> non-free
> 
> Am I really missing any updates? Or is there something wrong in my system? I
> really hate to install that plasma updater widget just to get updates.
> 

Start with dpkg -s unattended-upgrades

If that is installed, check as root/with sudo:

# cat /var/log/unattended-upgrades/unattended-upgrades.log

If you have unattended-upgrades package installed and it is configured
to fetch and install security updates only ( which is default ), that is
place to look for upgraded packages. You can also configure
unattended-upgrades to mail you where there was updates/upgrades and all
that jazz.

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 30-06-17, RavenLX wrote:
> 
> > If you have unattended-upgrades package installed and it is configured
> > to fetch and install security updates only ( which is default ), that is
> > place to look for upgraded packages. You can also configure
> > unattended-upgrades to mail you where there was updates/upgrades and all
> > that jazz.
> 
> How do I go about upgrading then? I don't know of how to do it any other way
> than via apt-get. Also I don't want to have it email me anything. I usually
> go to the command line, do a series of commands and upgrade the system. I
> would like to continue to do things that way. I do this once a week (usually
> Thurs. but now I'm switching to Fridays).
> 

Well, as you could see from your log, unattended-upgrades did it job and
upgraded security packages. If you want to keep those auto
updates/upgrades for security packages ( not that you will get much more
updates than those now that stretch is stable ), you do not have to do
anything. Security updates will be done automatically. If you want to
prevent automatic upgrades and disable them, because you want to do it
manually like you are used to, you should edit file
/etc/apt/apt.conf.d/20auto-upgrades and change it from this:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

to this:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";

If you want to keep those unattended upgrades working, settings are in
/etc/apt/apt.conf.d/50unattended-upgrades. For further reading and
explanation look here:

https://wiki.debian.org/UnattendedUpgrades 

https://linux-audit.com/using-unattended-upgrades-on-debian-and-ubuntu/

or just duckgogo/google it, there are few nice explanations.

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 30-06-17, David Wright wrote:
> 
> I'm not sure what this is all about; unattended-upgrades appears
> to have been maintained by the same person since the days of etch,
> a decade ago. What constitutes an advertisement, and how is the
> question posed as to whether updates are automatic or not?
> 
> Cheers,
> David.
> 

Probably because unattended-upgrades were not pulled in before
automatically on install of Debian. In Stretch, through some added
recommends, they are installed by default on at least Gnome and KDE
tasks.

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 30-06-17, Greg Wooledge wrote:
> On Fri, Jun 30, 2017 at 06:34:49PM +0200, Dejan Jocic wrote:
> > If you want to
> > prevent automatic upgrades and disable them, because you want to do it
> > manually like you are used to, you should edit file
> > /etc/apt/apt.conf.d/20auto-upgrades and change it from this:
> > 
> > APT::Periodic::Update-Package-Lists "1";
> > APT::Periodic::Unattended-Upgrade "1";
> > 
> > to this:
> > 
> > APT::Periodic::Update-Package-Lists "0";
> > APT::Periodic::Unattended-Upgrade "0";
> 
> Or you can just remove the unattended-upgrades package, right?
> 

Sure, if you want to. On gnome, it is pulled in because of
gnome-packagekit which recommends software-properties-gtk which depends
on python3-software-properties which recommends unattended-upgrades.
Personally would leave it on, because I like to have it in case that I
become lazy with my daily routine and because I like to look at various
things and understand how they work. But if OP does not need it, it is
safe to remove/purge it.

Re: Replace systemd

[Dejan Jocic]

On 03-07-17, Rory Campbell-Lange wrote:
> I run Debian on my laptops and several servers.
> 
> On my laptop I've had several recent occasions when it has been irksome
> to try and find the cause of a service not starting or shutting down,
> and I've concluded that I'd like to move away from systemd as I don't
> like the binary log.
> 
> This isn't a conceptual/design issue as I don't know enough of init
> fundamentals to make an informed judgement. It also isn't related to the
> recent Slashdot article about DNS crashes and root privs escalation.
> https://it.slashdot.org/story/17/07/03/0343258/severe-systemd-bug-allowed-remote-code-execution-for-two-years
> or the (possibly incorrectly reported) statements by Lennart Poettering
> noted at "What are the pros/cons of Upstart and systemd?"
> https://unix.stackexchange.com/questions/5877/what-are-the-pros-cons-of-upstart-and-systemd
> 
> I additionally find the configuration and documentation off-putting.
> These are trivial points, but the classic /etc config files seem to be
> being replaced with ini style files with non-explicit defaults. The
> documentation is wordy and also sometimes obtuse. e.g. "To disable a
> configuration file supplied by the vendor, the recommended way is to
> place a symlink to /dev/null in the configuration directory" and
> repeated references to "vendors" (which is almost certainly the wrong
> word).
> 
> Simply put; systemd doesn't suit me. Its a bit like being asked to use
> an graphical editor instead of vi. Or being forced to use Windows. My
> laptop doesn't feel like my machine anymore.
> 
> Is there a pure Debian alternative?
> 
> Thanks
> Rory
> 

You can still use Debian without systemd as init. Explained here:

https://lists.debian.org/debian-user/2017/05/msg00538.html

If you would prefer that it is some derivate/fork of Debian without
systemd, I do not have personal experience with those, but I'm sure that
you will get few hints.

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 02-07-17, RavenLX wrote:
> On 07/01/2017 03:54 PM, Larry Dighera wrote:
> > On Fri, 30 Jun 2017 16:31:37 -0400, you wrote:
> > 
> > > > Someone else mentioned unattended upgrades, which is a thing I have
> > > > never used, and which is also a thing I would disable if I ever found
> > > > it running.  But that's just me.
> > > 
> > > I would like to do that but don't know how. Anyone caring to enlighten
> > > me without me having to bother poor old Mr. Google yet again - it would
> > > be appreciated. :)
> > 
> > Perhaps you'll find this useful:
> 
> [Snipped script]
> 
> Thank you! I will have to give that a try.
> 

If you wish to use the script for that. But simpler solutions were
already given to you. Did you try them?

Re: Problems with apt in a clean stretch install.

[Dejan Jocic]

On 04-07-17, Wayne Hartell wrote:
> >
> >Did you try to change mirror you use in your sources.list?
> >
> 
> I did and it doesn't help (I get the same error with multiple different
> sources).
> 
> GPG error: http://deb.debian.org/debian stretch-updates InRelease: The
> following signatures couldn't be verified because the public key is not
> available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010The
> repository 'http://deb.debian.org/debian stretch-updates InRelease' is not
> signed.Updating from such a repository can't be done securely, and is
> therefore disabled by default.See apt-secure(8) manpage for repository
> creation and user configuration details.
> 
> Notably, the keys (e.g., 8B48AD6246925553 and 7638D0442B90D010) ARE present
> when I run 'apt-key list'.
> 
> When I search this forum for these keys (e.g., "8B48AD6246925553") I find
> two threads with similar kinds of errors, but no solution on either. I'm
> wondering whether I have fallen into some kind of crack perhaps.
> 

Not sure that it will be helpful, but just a thought. How about
reinstalling debian-archive-keyring package?

Re: Problems with apt in a clean stretch install.

[Dejan Jocic]

On 04-07-17, Wayne Hartell wrote:
> Hi all,
> 
>  
> 
> I'm a Linux novice and have run into a problem with a clean Stretch install
> and apt.
> 
>  
> 
> I started tinkering with Debian late in the game with Wheezy and have used
> Jessie pretty much without problem. After setting up some new Stretch
> systems (amd64) I am running into issues when using apt.
> 
>  
> 
> The first set of errors I get from apt when trying to run "update" are:
> 
>  
> 
> W: http://ftp.iinet.net.au/debian/debian/dists/stretch-updates/InRelease:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> 
> W: http://ftp.iinet.net.au/debian/dists/stretch/Release.gpg: The key(s) in
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
> user '_apt' executing apt-key.
> 
> W:
> http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> 
>  
> 
> I managed to solve this error after checking that the permissions on
> /etc/apt/trusted.gpg were 0600 and edited them to be 0644. (Is this the
> correct default permission for the file trusted.gpg?)
> 
>  
> 
> After that, when I run apt-get update again, I get a list of errors about
> errors occurring due to signature verification. 
> 
> e.g., "The repository is not updated and the previous index files will be
> used. GPG error: http://ftp.iinet.net.au/debian/debian stretch-updates
> InRelease: The following signatures couldn't be verified because the public
> key is not available: NO_PUBKEY 
> 
>  
> 
> The above error is an abbreviated hand typed reproduction; not the actual
> output. I can provide the full list of errors if it helps.
> 
>  
> 
> In another thread I read something about ensuring that the
> "debian-archive-keyring" is installed, and it is, version 2017.5.
> 
>  
> 
> I just checked on second clean stretch install and it's the same situation;
> same exact problems.
> 
>  
> 
> I am wondering what I might be doing wrong?
> 
>  
> 
> Regards,
> 
> Wayne.
> 
>  
> 
>  
> 

Did you try to change mirror you use in your sources.list?

Re: Problems with apt in a clean stretch install.

[Dejan Jocic]

On 04-07-17, Wayne Hartell wrote:
> > Wayne Hartell composed on 2017-07-04 15:46 (UTC+0930):
> >
> > > ...I managed to solve this error after checking that the
> > > permissions on /etc/apt/trusted.gpg were 0600 and edited them to
> > > be 0644. (Is this the correct default permission for the file
> > > trusted.gpg?)...
> >
> > I have to guess 644 is correct, as that is what is set on the
> > Stretch I have booted currently (as are all regular files in
> > /etc/apt/), and I've never touched it myself.
> >
> > Do you get the same errors running 'apt update' instead of 'apt-get
> > update'?
> 
> Yes, it seems that I get the same errors that way too.
> 
> I tried a new clean install test and seem to end up with permissions
> under /etc/apt/ always as 0600, so I am not sure what is going on.
> Looks like an issue with a clean install, but I am wondering why it's
> not coming up more often (unless most people are upgrading from
> Jessie).
> 
> 
Out of the head, but you did check install media with MD5 or SHA sums?
Also, many people did do clean install of Jessie. Though, it is annoying
bug for sure. But it is probably not so widespread. Perhaps you could
give it a shot on a clean install with root enabled from start, you can
always allow sudo for your user after that?

Re: cant find distribution

[Dejan Jocic]

On 04-07-17, Бурлаков Иван wrote:
> Hi!
> 
> Please help me!
> 
> I cant find distr on debian 8.0 on website.
> Please can you send me link for download (http link) iso debian 8.0& 
> 
> 
> --- 
> С уважением,
>  Бурлаков Иван
> +79260750111
> 

Archives:

https://cdimage.debian.org/cdimage/archive/

Archives including firmware:

https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/archive/

Re: Problems with apt in a clean stretch install.

[Dejan Jocic]

How about this solution, it worked in similar case:

https://lists.debian.org/debian-user/2017/05/msg00467.html

Re: Switching from Debian i386 to AMD64

[Dejan Jocic]

On 04-07-17, Richard Owlett wrote:
> I have been running Debian i386 since Squeeze. At that time it was required
> as I was considering supporting some donated 32 bit machines at church. I
> don't recall what processor was in my personal machine at that time. I've
> never had cause to investigate the processors in my current laptops and
> desktop machines. They all happily run i386.
> 
> Is there a utility that will report my hardware configuration/capability?
> 
> TIA
> 

Several. To see your cpu, type lscpu. Architecture is first in output.
Or, install inxi, it is probably best all around tool for system
informations.

Re: Switching from Debian i386 to AMD64

[Dejan Jocic]

On 04-07-17, Sven Joachim wrote:
> On 2017-07-04 17:33 +0200, Dejan Jocic wrote:
> 
> > On 04-07-17, Richard Owlett wrote:
> >> I have been running Debian i386 since Squeeze. At that time it was required
> >> as I was considering supporting some donated 32 bit machines at church. I
> >> don't recall what processor was in my personal machine at that time. I've
> >> never had cause to investigate the processors in my current laptops and
> >> desktop machines. They all happily run i386.
> >> 
> >> Is there a utility that will report my hardware configuration/capability?
> >> 
> >> TIA
> >> 
> >
> > Several. To see your cpu, type lscpu. Architecture is first in output.
> 
> That's not correct, or at least not useful.  The architecture is what
> uname(2) reports, and if the system is currently running a 32-bit
> kernel, it will be "i686" no matter if the processor is 64-bit capable.
> 
> The information about the latter is in the "Flags:" field of the lscpu
> output.  If it contains the "lm" (for "long mode[1]") flag, you have an
> x86_64 processor.
> 
> Cheers,
>Sven
> 
> 
> 1. https://en.wikipedia.org/wiki/Long_mode
> 

Thank you for correction. But what about second field in output, where
you have CPU op-mode? Should it be both 32-bit and 64-bit for 64-bit
capable and just 32-bit for i686?

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 01-07-17, Larry Dighera wrote:
> On Fri, 30 Jun 2017 16:31:37 -0400, you wrote:
> 
> >> Someone else mentioned unattended upgrades, which is a thing I have
> >> never used, and which is also a thing I would disable if I ever found
> >> it running.  But that's just me.
> >
> >I would like to do that but don't know how. Anyone caring to enlighten 
> >me without me having to bother poor old Mr. Google yet again - it would 
> >be appreciated. :)
> 
> Perhaps you'll find this useful:
> 
> ===
> # auto-update-on-off.sh   This script will enable and disable
> unattended-updates
> #
> # LGD: Thu Jun  1 15:00:09 PDT 2017
> #
> 
> [[ $# != 1 ]] && echo -e "\n\t\"$@\" Unknown\n\tUsage: $0 
> \n\t\tWhere:  e = Enable\n\t\t\td = Disable\n\t\t\ts = Status" >&2 &&
> exit 1 
> 
> FILNAM="/etc/apt/apt.conf.d/10periodic"
> OFF="APT::Periodic::Unattended-Upgrade \"0\";" 
> ON="APT::Periodic::Unattended-Upgrade \"1\";" 
> 
> status(){ # Get current status
>   if [[ -s "$FILNAM" ]] ;then # Does file exist with >0 file
> length?
> [[ $(grep -qs 1 "$FILNAM") ]] && STATUS=Enabled
> [[ $(grep -qs 0 "$FILNAM") ]] && STATUS=Disabled
>   else
> STATUS="Not Configured (Disabled)"
>   fi
>   return $STATUS
> }
> 
> 
> case $1 in 
>   -[sS]*) status; echo "Current $0 status: $STATUS">&2;exit 0 ;;
>   -[dD]*) echo "$OFF" >/etc/apt/apt.conf.d/10periodic ;;
>   -[eE]*) echo "$ON"  >/etc/apt/apt.conf.d/10periodic ;;
>   *) echo -e "\n\t\"$@\" Unknown\n\tUsage: $0  \n\t\tWhere:  e
> = Enable\n\t\t\td = Disable\n\t\t\ts = Status" >&2 && exit 1 
> esac  
> 
> =
> 

Why would you do that? Write and use script to change one 0/1 in
/etc/apt/apt.conf/20auto-upgrades? Or even 2, in case that you change
both for update and upgrade. Not to mention that those using gnome
software or some kde equivalent can do it in GUI too.

Re: [Stretch] apt-get has no updates?

[Dejan Jocic]

On 05-07-17, RavenLX wrote:
> On 06/30/2017 12:34 PM, Dejan Jocic wrote:
> > On 30-06-17, RavenLX wrote:
> > > 
> > > > If you have unattended-upgrades package installed and it is configured
> > > > to fetch and install security updates only ( which is default ), that is
> > > > place to look for upgraded packages. You can also configure
> > > > unattended-upgrades to mail you where there was updates/upgrades and all
> > > > that jazz.
> > > 
> > > How do I go about upgrading then? I don't know of how to do it any other 
> > > way
> > > than via apt-get. Also I don't want to have it email me anything. I 
> > > usually
> > > go to the command line, do a series of commands and upgrade the system. I
> > > would like to continue to do things that way. I do this once a week 
> > > (usually
> > > Thurs. but now I'm switching to Fridays).
> > > 
> > 
> > Well, as you could see from your log, unattended-upgrades did it job and
> > upgraded security packages. If you want to keep those auto
> > updates/upgrades for security packages ( not that you will get much more
> > updates than those now that stretch is stable ), you do not have to do
> > anything. Security updates will be done automatically.
> 
> I saw another security update and went and checked to see what version I had
> installed. It looks like it did in fact automatically install the update.
> 
> While it might be hard to get used to at first, I think I'll leave it as-is
> since this would ensure that my system is automatically up to date on
> security issues.
> 
> Maybe it's a good thing after all and time for me to make a little change in
> my routine? :)
> 
> Would this affect other updates (ie. bug-fix) of packages or is this only
> for the security repo? Should I still do the apt-get routine weekly just in
> case? I would surmise that we probably won't get any 'normal' but fix
> updates for a long time since Stretch was just released?
> 

As explained before, settings for unattended-upgrades are in the
/etc/apt/apt.conf.d/50unattended-upgrades. You can set it to download
and install just security updates, which is default. Or, you can set it
to download and install all updates, if you uncomment certain lines, or
add new ones. Think that you can also set it from apper, or
plasma-discover, whatever kde uses these days. Or
software-properties-kde, if it is similar to software-properties-gtk.

Re: Problems with apt in a clean stretch install.

[Dejan Jocic]

On 05-07-17, Wayne Hartell wrote:
> 
> Fungi4All wrote:
> > And this for the OP:
> > 1  But if there is such a basic problem with installation what is
> > so different that the rest of the new stretch installers did not
> > face?
> >
> 
> That's a good question. I'm not 100% sure what the problem with the
> installer is in your minds? Do you mean whatever causes the problem that
> occurs when /etc/apt/trusted.gpg is *present*?
> 
> > 2  What filesystem did you use while partitioning?  
> >

I doubt that filesystem has anything to do with your experience.


> Being a novice I didn't make any changes from the defaults (did the guided
> partitioning with everything in one** partition), except on one laptop,
> where I used LVM/encryption, but with no partitioning differences other than
> those created by using LVM.
> 
> **I note that even though the installer says "one" partition, it still seems
> to create a separate swap partition (I read, I think that on some distros
> the swap partition is now optional; it can be a file instead). So the file
> system is (for 3/4 of the systems):
> /dev/sda1 bootable Ext4 341GB
> /dev/sda2 extended 2.1GB
> /dev/sda5 swap 2.1GB
> 
> > 3  Is there any kind of raid?

Even if you do, do not see how it is relevant for this case.

> 
> No raid on any of the systems.
> 
> > 4  Is autoupdate/unattended-update enabled?  And is there a log of it?
> 
> Only if it was enabled by default. "System Upgrade" in Synaptic is set to
> "Smart Upgrade" if that's what you are talking about. I don't know what this
> is and after yesterday haven't got enough time to research what this is and
> where/how to find logs for now. Let me know if a proper answer to this
> question is important,  and I will dig into it further.
> 
> Kind Regards,
> Wayne.
> > 

For start, it is not unattended-update, it is unattended-upgrades
package. It also does not have anything to do with your problem. In
stretch, it comes in by default on at least gnome and kde tasks. And, by
default, it is set to get your security upgrades and install them for
you. To check if it is installed:

dpkg -s unattended-upgrades

To check if it is enabled:

cat /etc/apt/apt.conf.d/20auto-upgrades

If output is:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

then it is enabled. If you want to disable it change those "1" to "0".
You can do it with your favorite editor or in one line:

sudo sed -i 's/1/0/g' /etc/apt/apt.conf.d/20auto-upgrades

If you want to use unattended-upgrades, would suggest checking its
config file that is here:

/etc/apt/apt.conf.d/50unattended-upgrades

and debian wiki entry here:

https://wiki.debian.org/UnattendedUpgrades

As a side note, in gnome you can enable/disable auto updates in gnome
software & updates ( software-properties-gtk ) and in kde apper or
whatever kde uses these days.

Re: Replace systemd

[Dejan Jocic]

On 06-07-17, David Griffith wrote:
> 
> I'm aware of that technique.  What I was talking about is a menu option that
> pops up when the install is running that explicitly asks the person
> installing which init to use.
> 
> 
> -- 
> David Griffith
> d...@661.org
> 
> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?


There was no such option when SysVinit was default. Why would it exist
now? There are also no options to choose default browser, editor, video
player, music player and so on. But everyone is free to install and set
as default whatever they like. Including init system.

Re: Debian Stretch Xfce Touchpad Settings Missing

[Dejan Jocic]

On 28-06-17, Apurv Jyotirmay wrote:
> Hi,
> 
> I use a Synaptics touchpad on my laptop. Normally on other distributions
> (Xubuntu, Manjaro, etc.), the mouse settings area displayed a tab to
> configure touchpad settings, but on Debian 9 that particular tab is
> missing, and because of it I'm unable to activate features like "tap to
> click", which is an inconvenience. Can anyone help me find a solution to
> this issue? I'm new to Debian and not really familiar with the way driver
> support works.
> 
> Thanks,
> Apurv

In Gnome, situation like that was solved by installing
xserver-xorg-input-libinput instead of xserver-xorg-input-synaptics, if
I remember it correctly. Hope that it can help you.

Re: Need to upgrade to jessie need help

[Dejan Jocic]

On 27-07-17, David Wright wrote:
> On Tue 25 Jul 2017 at 16:16:44 (+0200), Dejan Jocic wrote:
> > On 25-07-17, Greg Wooledge wrote:
> > > Is there any way to permanently neuter apt-get autoremove, so that even
> > > if something invokes it against my will, it will *never* remove anything?
> > > 
> > > And more, is there a way to get apt and apt-get to *stop* prompting me
> > > to run it, and *stop* spamming me with a list of packages that it would
> > > like me to remove?  (Maybe that's the same as the first question, maybe
> > > not.)
> > > 
> > > My strategy so far has been "ignore the spam, and never willingly run
> > > autoremove".  This mostly works, but I recently learned that tasksel
> > > will apparently run an autoremove, without warning, whether I want it
> > > to or not (<http://bugs.debian.org/868892>).
> > > 
> > > If autoremove will also remove *kernels*, which this thread seems to
> > > indicate is the case, then my concerns just went up another notch.
> > > 
> > > I suppose one could manually mark each and every single installed
> > > package as "manually installed", but you'd have to remember to repeat
> > > this periodically, and it seems clumsy and inelegant compared to some
> > > sort of master switch that can just tell autoremove to go die in a fire.
> > > 
> > 
> > Your fear from autoremove is silly. It
> 
> Please note that "it" is "they", viz: apt and apt-get, …
> 

Sure it is they. Did any of those they ever removed something that you
needed with autoremove? Or they always remove just things that you do not
need any more, packages that are just sitting there doing nothing,
former dependencies that are not needed for anything?

> > will not remove anything you
> > really need and, if you stick to default settings, 
> 
> … and that they have different defaults. What's more, apt's behaviour
> may change between versions, so unqualified statements like this
> should really be confirmed before being relied on.
> 

So, same question as above, did and of those they messed up? Are there
opened bugs that autoremove from any of used tools in debian removes
packages it should not? And qualifications for that statement are years
of use of both apt-get and aptitude with autoremove following
update/upgrade. Never had any trouble with it.

> > will keep all
> > packages it replaced in /var/cache/apt/archives, as far as I know. And
> > if you have some package that you really, really want to keep, you can
> > always pin it, or put it on hold with apt-mark. It is not spam, it is
> > keeping your system clean.
> 
> Cheers,
> David.
> 

All best,
Dejan

Re: Darn 'beep' stoped working after installing Stretch in place of Jessie

[Dejan Jocic]

On 01-08-17, RavenLX wrote:
> Having it work out-of-the-box would be nice. After a fresh install, I have a
> bash script I run that installs all the apps I use and configures them.
> Sometimes though, there are things that a user needs to answer. Thus, if I
> want to have the script running and go do something else, I want to "beep"
> when it's going to need attention by the user. I noticed this does not work
> in Stretch so I ended up removing the part to install the "beep" package and
> use beep to alert the user. I have tried escape codes via echo -e as well,
> and no beep there either.
> 

Does printf "\a" works for you? Though, echo -e "\a" works here too.

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Garrett R. wrote:
> No effect.
> 
> I added  "session optional pam_umask.so umask=0077" to the end of 
> /etc/pam.d/common-session. Then I confirmed /etc/login.defs has a umask 
> entry. Then I logged out and back in.
> 
> A new gedit document still reports permission rw-r--r--.
> 


Unfortunately. It looks like it is systemd thing indeed, according to
this: 

https://unix.stackexchange.com/questions/254378/how-to-set-umask-for-the-entire-gnome-session#254923

and this

https://github.com/systemd/systemd/issues/6077

It also looks like it does not have workaround. Except to touch file
from terminal before editing it in gedit( if it is login shell, for
gnome-terminal edit > profile preferences > command > run command as
login shell ). Or even better launch gedit from that terminal, it will
have right umask settings. Or, make custom shortcut that will launch
terminal and gedit from it at same time, something like gnome-terminal
-e gedit. Sorry, but not much more help with systemd involved, I'm
afraid.

Re: no non-free firmware on lapton, no Ethernet, related?

[Dejan Jocic]

On 09-08-17, Emanuel Berg wrote:
> I installed a 32-bit Debian on an HP laptop the
> other day, and during installation it said
> non-free components were not installed as not
> on the disc, for political reasons I suppose,
> and then the network couldn't be set up
> correctly despite the cable in place.
> 
> When done, I couldn't get Internet to work
> despite doing as superuser 'dhclient eth0'
> which is all it takes on my other Debian, which
> I also installed from a DVD.
> 
> So I wonder, are the Ethernet problems related
> to the missing firmware?
> 
> And if not, what seems to be the problem?
> 
> TIA
> 
> -- 
> underground experts united
> http://user.it.uu.se/~embe8573
> 

Well, you should have write down what was missing during installation,
those messages you get for reason. Also, when you have firmware and you
get note that it is missing, it is best to abort installation and
download needed firmware and put in USB you can insert during
installation. Or, to use one of the "unnofficial" images with firmware
on it:

https://cdimage.debian.org/cdimage/unofficial/non-free/

That said, now first step would be to check your network cards and what
drivers are in use. As regular user do:

lspci -v | grep -A10 -i net

If you type that as root change A10 to A15.

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Garrett R. wrote:
> Terminal confirms my umask is 022. That is, my entries at login.defs, 
> xsessionrc, etc are not working.
> 
> Thank you for your assistance, Greg. Before asking here, my research 
> indicated gnome is the problem and it is because of systemd that there is a 
> problem. I assumed because gnome is default on debian, you might have some 
> insight. 
> 
> Thank you for your efforts, much appreciated.
> 

Depends on terminal. If you use xterm under Gnome, it will respect umask
settings, wherever those are, global or local in .profile or .bashrc.
But gnome-terminal does not respect those settings. Guess that you
should file bug against gnome.

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Dejan Jocic wrote:
> On 07-08-17, Garrett R. wrote:
> > Terminal confirms my umask is 022. That is, my entries at login.defs, 
> > xsessionrc, etc are not working.
> > 
> > Thank you for your assistance, Greg. Before asking here, my research 
> > indicated gnome is the problem and it is because of systemd that there is a 
> > problem. I assumed because gnome is default on debian, you might have some 
> > insight. 
> > 
> > Thank you for your efforts, much appreciated.
> > 
> 
> Depends on terminal. If you use xterm under Gnome, it will respect umask
> settings, wherever those are, global or local in .profile or .bashrc.
> But gnome-terminal does not respect those settings. Guess that you
> should file bug against gnome.
> 
> 
> 


Ehh, disregard please. Just checked with gnome-terminal here, and it did
respect umask settings in .profile. But gedit did not.

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Greg Wooledge wrote:
> On Mon, Aug 07, 2017 at 07:02:14PM +0200, Dejan Jocic wrote:
> > Ehh, disregard please. Just checked with gnome-terminal here, and it did
> > respect umask settings in .profile. But gedit did not.
> 
> If gnome-terminal is reading .profile, that means it must be running
> your shell as a login shell, which is a questionable practice.
> 
> Yet another strike against GNOME, if true.
> 

I run all my shells in terminal as login shells, because I prefer it
that way. If you do not like it, do not do it :P It has nothing to do
with Gnome.

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Garrett R. wrote:
> I apologize for the omissions.
> 
> I am booting debian to GDM. I login. I then open gedit (or libreoffice, etc). 
> I type document. I save it.
> 


Have you tried to set in /etc/pam.d/login this:

session optional pam_umask.so umask=0077

Logout and login back after that?

Re: How to change default umask in Stretch?

[Dejan Jocic]

On 07-08-17, Garrett R. wrote:
> I just tried this, adding "session optional pam_umask.so umask=0077" to the 
> end of the /etc/pam.d/login file.
> 
> No effect.
> 
> - Original Message -
> From: "Dejan Jocic" <jode...@gmail.com>
> To: debian-user@lists.debian.org
> Sent: Monday, August 7, 2017 1:11:02 PM
> Subject: Re: How to change default umask in Stretch?
> 
> On 07-08-17, Garrett R. wrote:
> > I apologize for the omissions.
> > 
> > I am booting debian to GDM. I login. I then open gedit (or libreoffice, 
> > etc). I type document. I save it.
> > 
> 
> 
> Have you tried to set in /etc/pam.d/login this:
> 
> session optional pam_umask.so umask=0077
> 
> Logout and login back after that?
> 

Now try to add it too to the /etc/pam.d/common-session and to set it up
in /etc/login.defs to your preferred value. Of course, logout/login
after all that.

Re: kvm/qemu virtual machine can't find hard drives

[Dejan Jocic]

On 18-08-17, Gary Roach wrote:
> I really appreciate all of you quick responses.
> 
> For some unknown reason, when I searched the  Debian database virt came up
> empty. This time it didn't. So, at this point, its go RTFM.
> 
> The manual will probably clear it up but When trying to run virt-manager, I
> did get the following error:
> 
> unable to complete install: 'unsupported configuration: CPU mode 'custom'
> for x86_64 kvm domain on x86_64 host is not supported by hypervisor'
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/create.py", line 2288, in
> _do_async_install
> guest.start_install(meter=meter)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 461, in
> start_install
> doboot, transient)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 396, in
> _create_guest
> self.domain = self.conn.createXML(install_xml or final_xml, 0)
>   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3523, in
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed',
> conn=self)
> libvirtError: unsupported configuration: CPU mode 'custom' for x86_64 kvm
> domain on x86_64 host is not supported by hypervisor
> 
> I'll give things another try and may be back later. If not, thanks again.
> 
> Gary R
> 

Do this:

grep -E -c '(vmx|svm)' /proc/cpuinfo

if you get 0, your CPU does not support virtualisation with KVM. If you
get more than zero, make sure that virtualisation is enabled in your
BIOS settings.

Re: Virtualbox for stretch and buster not in repos

[Dejan Jocic]

On 22-08-17, RavenLX wrote:
> On 08/18/2017 10:25 AM, Dejan Jocic wrote:
> > On 18-08-17, RavenLX wrote:
> > > On 08/18/2017 09:14 AM, Sven Hartge wrote:
> > > > RavenLX <rave...@sitesplace.net> wrote:
> > > > 
> > > > > I always used the Oracle repo anyway because it was updated more
> > > > > frequently. But I do wish that something could be worked out so that
> > > > > it would be back in Debian.
> > > > 
> > > > Highly unlikely, as Oracle behaves like this for all software released
> > > > and distributed by them.
> > > > 
> > > > Grüße,
> > > > Sven.
> > > > 
> > > 
> > > I wonder if there's a replacement for VirtualBox? I need something that 
> > > will
> > > allow me to share a directory between host and virtual machine, and to be
> > > able to go between both quickly (I don't have a dual-screen system - no 
> > > room
> > > where I live for that). If I could find something that would work I'd
> > > switch, I think. As for my friend, he would need far more features I guess
> > > (I don't know what though).
> > > 
> > 
> > qemu-kvm does not serve your needs? You can use it with GUI friendly
> > virt-manager, or from command line. And switching between host and guest
> > is switching between windows. As for shared directory, NFS?
> 
> The shared directory has to be a directory on the host (ie. ext4 is what I'm
> using). VirtualBox lets me share as many directories as I like and lets me
> specify which ones. I think I tried qemu and kvm and didn't even know how to
> use it or where to begin. I might have to revisit that sometime especially
> if I get tired of VirtualBox.
> 

Hmm, I was curious to see if it can be done with qemu-kvm. It can and is
not really hard. At least not with virt-manager, did not check on
command line. Anyway, just as a note if you decide to use it.

Once you make and open your VM, go to view, details, add hardware
button, file system, select folder for source ( like /home/something on
your host ), select folder for destination ( something on your guest
like example ), then mount that example where you want on your guest.
You just need to get right mount command, this is from qemu wiki:

mount -t 9p -o trans=virtio [mount tag] [mount point] -oversion=9p2000.L

Here is that page for further reading:

http://wiki.qemu.org/Documentation/9psetup

And here is with bit less reading and illustrated from kvm:

http://www.linux-kvm.org/page/9p_virtio

Personally, I do not have use for shared files between host and guest,
but hope that this can help you.

Re: kvm/qemu virtual machine can't find hard drives

[Dejan Jocic]

On 17-08-17, Gary Roach wrote:
> Sorry bob but the  debian 9 archives doesn't include libvirtd or anything
> equivalent. I have been trying to use virt-manager but have gotten a bit
> confused. The screen shot is attached. I have two hard drives. One is a 160
> Gb boot drive called bootdisk and another empty 1 Tb drive called bigdisk.
> It looks like virt-manager picked the empty 1Tb drive and only allocated 20
> Gb to the program. I hit the Volumes + but didn't see any way to add the
> boot drive. Are we talking about a virtual drive that is situated in the
> bigdisk. Is the guest OS situated in the bigdisk. If so, this is not a bad
> thing since I will probably have massive amounts of data produced. But I do
> need to figure out what I am dealing with.
> 
> Any help will be appreciated.
> 
> Gary R.

Package you want is libvirt-bin and libvirt-daemon-system and
libvirt-clients come as dependences with it. Most of the guides around,
including debian wiki guide about qemu-kvm tell you to install those.
Package bridge-utils too. I see that you talk again about your hard
drives. That is wrong because because virt-manager and libvirt do not
care about your hard drives, it cares about storages and storage
volumes. Default storage volume is at /var/lib/libvirt/images. But I
guess that you do not want your image there, most people do not.
Creating image with virt-manager is as easy as following 5 steps, after
you launch it, click FIle and select create new virtual machine:

1. Choose how you would like to install. Will guess that you have local
install media in form of downloaded ISO. Pick it up, do not touch
architecture options, if you do not need them. Click forward.

2. Use ISO image and click browse. Use browsing to find your download
location. Choose your ISO image. It should automatically detect that it
is debian stretch. Forward.

3. Choose CPU and memory settings. Forward.

4. Enable storage for this virtual machine checked. Choose Select or
create custom storage. Click Manage... Use + signs to make new volume
and storage for your image where you want it, or choose existing one.
You have there options to choose max capacity for it, but no worries, it
can be expanded, it is virtual machine. Use qcow2 format. I have no need
for backing store, but see for yourself if you want it. Finish. Choose
that volume that you've made. Forward.

5. Read to begin the installation screen. You can customize
configuration before install, if you want. By default, on my laptop and
without changing anything in network files, network selection is not
needed, it will choose virtual network 'default' and work out of the
box. Finish and install will start in new window.




5. 

Re: Virtualbox for stretch and buster not in repos

[Dejan Jocic]

On 18-08-17, RavenLX wrote:
> On 08/18/2017 09:14 AM, Sven Hartge wrote:
> > RavenLX  wrote:
> > 
> > > I always used the Oracle repo anyway because it was updated more
> > > frequently. But I do wish that something could be worked out so that
> > > it would be back in Debian.
> > 
> > Highly unlikely, as Oracle behaves like this for all software released
> > and distributed by them.
> > 
> > Grüße,
> > Sven.
> > 
> 
> I wonder if there's a replacement for VirtualBox? I need something that will
> allow me to share a directory between host and virtual machine, and to be
> able to go between both quickly (I don't have a dual-screen system - no room
> where I live for that). If I could find something that would work I'd
> switch, I think. As for my friend, he would need far more features I guess
> (I don't know what though).
> 

qemu-kvm does not serve your needs? You can use it with GUI friendly
virt-manager, or from command line. And switching between host and guest
is switching between windows. As for shared directory, NFS?

Re: how to copy files

[Dejan Jocic]

On 15-05-17, Long Wind wrote:
> archive just means that?
> Thank Dan Ritter!
> l will try it later on.

What you probably want is:

rsync -av /path/to/original/folder /path/to/backup

With this command on your backup rsync will make folder named as folder
in your original path under backup. Notice that there is no need for
those / on the end of paths. Also, you will not need root permission for
your home folder backups with any combination of options for rsync.

Re: Peculiar problem with root login

[Dejan Jocic]

On 12-06-17, Felix Miata wrote:
> Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> .
> > Normally you can´t login via Root, because there is no entry in the passwd 
> > file.
> .
> That is false for every Debian installation (Squeeze, Wheezy, Jessie, Stretch 
> at
> least) I have ever done (unless maybe I'm misremembering all the way back to 
> Etch).
> -- 
> "The wise are known for their understanding, and pleasant
> words are persuasive." Proverbs 16:21 (New Living Translation)
> 
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> 
> Felix Miata  ***  http://fm.no-ip.com/
> 

dejan@ddeb:~$ cat /etc/passwd | grep root
root:x:0:0:root:/root:/bin/bash

Perhaps it is true if you choose not to create root account during
installation process.

Re: Peculiar problem with root login

[Dejan Jocic]

On 12-06-17, Erik Karlin wrote:
> On Mon, Jun 12, 2017 at 08:06:21PM +0200, Dejan Jocic wrote:
> > On 12-06-17, Felix Miata wrote:
> > > Jan-Peter Rühmann composed on 2017-06-12 17:15 (UTC+0200):
> > > .
> > > > Normally you can´t login via Root, because there is no entry in the 
> > > > passwd file.
> > > .
> > > That is false for every Debian installation (Squeeze, Wheezy, Jessie, 
> > > Stretch at
> > > least) I have ever done (unless maybe I'm misremembering all the way back 
> > > to Etch).
> > > -- 
> > > "The wise are known for their understanding, and pleasant
> > > words are persuasive." Proverbs 16:21 (New Living Translation)
> > > 
> > >  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
> > > 
> > > Felix Miata  ***  http://fm.no-ip.com/
> > > 
> > 
> > dejan@ddeb:~$ cat /etc/passwd | grep root
> > root:x:0:0:root:/root:/bin/bash
> > 
> > Perhaps it is true if you choose not to create root account during
> > installation process.
> > 
> > 
> man 5 shadow

And? 

p.s. Please, reply to the list, not to me. There is no need to reply to
me, I'm subscribed. Thank you :)

Re: Can't install Debian 9, missing liblzo2

[Dejan Jocic]

On 19-06-17, Wellington Terumi Uemura wrote:
> Hello,
> 
> I'm trying to install Debian 9 from a Live version with no success, I'm
> using the "debian-live-9.0.0-amd64-gnome+nonfree.iso" MD5SUM
> "baf4371d63bccaed58714891626de1e2" (match with the official release).
> 
> The installation stops when it will start to mount and detect the CDROM with
> an error that it can't copy files from the disc, the syslog show this
> errors:
> 
> Jun 19 11:50:36 main-menu[559]: INFO: Menu item 'cdrom-detect' selected
> Jun 19 11:50:36 cdrom-detect: Detected CD with 'stable' (stretch)
> distribution
> Jun 19 11:50:36 main-menu[559]: INFO: Restoring default debconf priority
> 'high'
> Jun 19 11:50:36 debconf: Setting debconf/priority to high
> Jun 19 11:50:36 main-menu[559]: DEBUG: resolver (libgcc1): package doesn't
> exist (ignored)
> Jun 19 11:50:36 main-menu[559]: INFO: Falling back to the package
> description for brltty-udeb
> Jun 19 11:50:36 main-menu[559]: INFO: Falling back to the package
> description for brltty-udeb
> Jun 19 11:50:36 main-menu[559]: INFO: Menu item 'load-cdrom' selected
> Jun 19 11:50:36 anna[3385]: DEBUG: retrieving liblzo2-2-udeb 2.08-1.2+b2
> Jun 19 11:50:36 cdrom-retriever: error: Unable to find 
> '/w/work/nonfree/gnomepool/main/libl/liblzo2-2-udeb/liblzo2-2-udeb_2.08-1.2+b2_amd64.udeb'.
> Jun 19 11:50:36 anna[3385]: WARNING **: package retrieval failed
> Jun 19 11:50:38 cdrom-retriever: error: Unable to find 
> '/w/work/nonfree/gnomepool/main/libl/liblzo2-2-udeb/liblzo2-2-udeb_2.08-1.2+b2_amd64.udeb'.
> Jun 19 11:50:44 main-menu[559]: WARNING **: Configuring 'load-cdrom' failed
> with error code 6
> Jun 19 11:50:44 main-menu[559]: WARNING **: Menu item 'load-cdrom' failed.
> 
> Checking the disc, there is no
> "liblzo2-2-udeb/liblzo2-2-udeb_2.08-1.2+b2_amd64.udeb" under that path.
> 
> The "debian-live-9.0.0-amd64-gnome.iso" also fails to install for the same
> reason.
> 
> The other issue I have is that the installer can't verify the media, it say
> that is not a official Debian Release. But the log shows it is:
> 
> Jun 19 11:37:14 cdrom-detect: Searching for Debian installation media...
> Jun 19 11:37:14 cdrom-detect: Devices: '/dev/sr0'
> Jun 19 11:37:14 cdrom-detect: CD-ROM mount succeeded: device=/dev/sr0
> fstype=iso9660
> Jun 19 11:37:14 kernel: [   40.386418] ISO 9660 Extensions: RRIP_1991A
> Jun 19 11:37:14 cdrom-detect: Detected CD 'Official Debian GNU/Linux Live
> 9.0.0 gnome 2017-06-17T17:41'
> Jun 19 11:37:15 cdrom-detect: Detected CD with 'stable' (stretch)
> distribution
> Jun 19 11:37:15 anna-install: Queueing udeb eject-udeb for later
> installation
> Jun 19 11:37:15 anna-install: Queueing udeb apt-mirror-setup for later
> installation
> Jun 19 11:37:15 cdrom-detect: Base system not installable from CD,
> requesting choose-mirror
> Jun 19 11:37:15 anna-install: Queueing udeb choose-mirror for later
> installation
> Jun 19 11:37:15 main-menu[559]: DEBUG: resolver (libgcc1): package doesn't
> exist (ignored)
> Jun 19 11:37:15 main-menu[559]: INFO: Falling back to the package
> description for brltty-udeb
> Jun 19 11:37:15 main-menu[559]: INFO: Falling back to the package
> description for brltty-udeb
> Jun 19 11:37:15 main-menu[559]: INFO: Menu item 'load-cdrom' selected
> Jun 19 11:37:15 anna[2384]: DEBUG: retrieving liblzo2-2-udeb 2.08-1.2+b2
> Jun 19 11:37:15 cdrom-retriever: error: Unable to find 
> '/w/work/nonfree/gnomepool/main/libl/liblzo2-2-udeb/liblzo2-2-udeb_2.08-1.2+b2_amd64.udeb'.
> Jun 19 11:37:15 anna[2384]: WARNING **: package retrieval failed
> 
> Thanks.
> 

You are not alone in that, all live images are borked. There is forum
topic about it here http://forums.debian.net/viewtopic.php?f=17=133474
and there is bug report about it with Steve McIntyre working on fix here
https://lists.debian.org/debian-boot/2017/06/msg00240.html.

Re: Stretch upgrade from Jessie -- several issues

[Dejan Jocic]

On 26-06-17, Ralph Katz wrote:
> 
> I think the workaround of using the mouse on pavucontrol or
> gkrellm-volume will have to do for sound control.  Thanks!
> 

Well, not exactly solution, but as a work around, you can assign some
shortcuts to do your sound work in a same way volume keys would do. For
example, in case of the pulse audio you can use these:

pactl set-sink-volume 0 -- +5% to increase volume by 5%

pactl set-sink-volume 0 -- -5% to decrease volume by 5%

pactl set-sink-mute 0 toggle to mute/unmute

In case of ALSA, should be something like:

amixer set Master 5%+ to increase

amixer set Master 5%- to decrease

amixer set Master toggle to mute/unmute

Re: pavucontrol fails to start

[Dejan Jocic]

On 26-06-17, Thomas George wrote:
> The command pavucontrol returns an error message:
> 
> error while loading shared libraries: libgtkmm-3.0.so-1: cannot open object
> file: No such file or directory.
> 
> Where can I find this missing file?
> 
> I checked apt-get install libgtkmm-3.0-1 The response was latest version
> installed.
> 
> I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.
> 

It is more appropriate to use apt-file search libgtkmm-3.0.so.1. That
will return that it is part of package libgtkmm-3.0-1v5. And that
package replaces and conflicts libgtkmm-3.0-1. At least on Stretch, on
my laptop.

Re: Jessie --> Stretch upgrade, apt question

[Dejan Jocic]

On 25-06-17, Mark Fletcher wrote:
> Hello the list!
> 
> I have upgraded this weekend from Jessie to Stretch. All went, overall, 
> reasonably smoothly -- the documentation around releases is getting 
> better and better. I plan to write a full report of the upgrade and 
> share it here shortly. In the meantime I have one question.
> 
> It seems like aptitude is falling out of favour in stretch, and apt as a 
> command line tool as opposed to the name for the general entire package 
> management system is being recommended these days. I've never been a 
> huge fan of apt-get (although to be fair that means little more than I 
> settled on aptitude [command-line version not ncurses version] and 
> learned its quirks a long time ago) and so I am, somewhat reluctantly, 
> making the switch to apt from aptitude. apt has a couple of features I 
> really like, but I do wish apt show made it easier to tell if a package 
> is installed -- you have to read a lot further down the info to find 
> out.
> 
> My question is that since the upgrade chromium is held back from 
> upgrading, and in this new world I don't know how to find out why. In 
> aptitude I would have done aptitude why-not chromium and it would most 
> likely have told me something useful about its dependencies. How can I 
> get apt to do similar? Or what tool should I use?
> 
> I'm aware that apt-cache depends chromium will tell me what it depends 
> on, but that doesn't tell me what is stopping it from being upgraded.
> 
> sudo apt upgrade and sudo apt full-upgrade both just tell me chromium 
> has been kept back, but not why.
> 
> sudo apt --fix-broken install finds nothing to do.
> 
> Suggestions would be much appreciated.
> 
> Mark
> 

In short, use aptitude for why and why-not. Closest thing apt-get and
friends have would be apt-cache --important depends/rdepends. But,
aptitude is much better suited for that task. And for all other tasks
that involve advanced searching, as far as I could tell. As for apt
itself, would not know exactly, I refuse to use tool with man page that
treats me like an idiot, while not giving me anything new and important
compared to apt-get and friends. But guess would be that it is apt
--important depends/rdepends. And probably not more helpful than
apt-cache variant.

Re: Update Notifier

[Dejan Jocic]

On 20-05-17, Yvan Masson wrote:
> I also consider this missing "update notification" an important issue
> for beginners and people that do not want to manually check for security
> updates every day.
> 
> > In Debian Jessie install pk-update-icon from debian-backports
> > 
> > In Debian Stretch install pk-update-icon.
> > 
> > This package works both on Cinnamon, XFCE4 and Gnome. Not sure on the other 
> > DEs.
> 
> Unfortunately, this is not true for Gnome: in
> /etc/xdg/autostart/pk-update-icon.desktop we can see that it is disabled
> for both Gnome and KDE.
> 
> So I suppose that Gnome and KDE should display user notification about
> updates.
> - I can tell that it is not the case for Gnome in Stretch (at least on
> my desktop), which makes me really disappointed. Is there anyone here
> who gets update notifications under Gnome in Stretch?
> - Is there any KDE user here who could tell us if there is update
> notifications by default?
> 
> Regards,
> Yvan
> 



Not sure what you mean by "that is not case for Gnome in Stretch". I do
not have pk-update-icon package installed, but I do get notifications
about updates. As far as I know, it is part of gnome-packagekit package.
Not that I use it anyway, first thing after boot is apt-get update &&
apt-get upgrade for me. But it is usually fast enough to notify my that
my morning routine will not be blank shot.

Re: how to copy files

[Dejan Jocic]

On 20-05-17, Felix Dietrich wrote:
> Dejan Jocic <jode...@gmail.com> writes:
> 
> > rsync -av /path/to/original/folder /path/to/backup
> >
> > Notice that there is no need for those / on the end of paths.
> 
> Rsync actually treats a trailing newline on the source path specially;
> quoted from the man page:
> 
> A  trailing  slash on the source changes this behavior to avoid
> creating an additional directory level at the destination.  You
> can think of a trailing / on a source as meaning "copy the con‐
> tents of this directory" as opposed to "copy the  directory  by
> name" […]
> 
> --
> Felix Dietrich
> 

Yup, I know it. But OP asked for copy of original folder to backup
folder. Not for copy of contents of original folder to some backup
folder, in which case you would use trailing slash. Or at least that is
how I've understood his question.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 26-05-17, David Wright wrote:
> On Mon 22 May 2017 at 11:12:02 (+0200), Dejan Jocic wrote:
> > On 21-05-17, Brian wrote:
> > > On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote:
> > > 
> > > > On 21-05-17, David Wright wrote:
> > > > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> > > > > > > 
> > > > > > As for number 1 can't say much about it, I do not get it either. 
> > > > > > But 2
> > > > > > happens because you've used apt-get upgrade instead of apt-get
> > > > > > dist-upgrade. Packages that will uninstall some packages already
> > > > > > installed on your system and that will change some dependencies 
> > > > > > require dist-upgrade.
> > > > > 
> > > > > Agreed.
> > > > > 
> > > > > > It happens always in case of linux-image packages. 
> > > > > 
> > > > > Is this¹ new with stretch? My linux-images upgrade just like any other
> > > > > package; here's the penultimate occasion for jessie:
> > > > > 
> > > > > Start-Date: 2017-03-08  19:20:34
> > > > > Commandline: apt-get upgrade
> > > > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 
> > > > > 3.16.39-1+deb8u2)
> > > > > End-Date: 2017-03-08  19:22:50
> > > > > 
> > > > > (The last one's log was rather larger.)
> > > > 
> > > > Ehh, sorry not sure if it is new with Stretch, can't remember for
> > > > Jessie. I'm certain that it was like that on Stretch and on Ubuntu
> > > > 16.04.
> > > 
> > > Rather than just a contrast, I was rather hoping to hear how David
> > > Wright's observations (which I agree with)fit in with yours.
> > > 
> > Sorry, not sure what I can add to it. 
> > 
> > > > > > It will leave your previous working linux-image on though, but will 
> > > > > > uninstall one older than that, so you will always end up with 
> > > > > > chance to 
> > > > > > boot in working kernel, if new one messes up some things.
> > > > > 
> > > > > Same question. My wheezy system has had at least 28 linux-image
> > > > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
> > > > > but there's still only one kernel image on the system:
> > > > > 
> > > > > -rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > > > > drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
> > > > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > > > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > > > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> > > > > 
> > > > > (I have to notice these upgrades myself because they overwrite
> > > > > my edited version of /boot/grub/grub.cfg which I then replace.)
> > > > > 
> > > > > Cheers,
> > > > > David.
> > > > > 
> > > > > ¹ I'm not disagreeing that something is holding back the upgrade
> > > > > on this specific occasion, but this is unusual.
> > 
> > 
> > This is what I have in /boot and, as stated above, usual outcome of
> > upgrades, both in Stretch and in Ubuntu 16.04:
> > 
> > -rw-r--r-- 1 root root   186695 Mar 30 03:16 config-4.9.0-2-amd64
> > -rw-r--r-- 1 root root   186380 May  2 17:21 config-4.9.0-3-amd64
> > drwxr-xr-x 5 root root 4096 May 19 08:55 grub
> > -rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64
> > -rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64
> > -rw-r--r-- 1 root root  3169870 Mar 30 03:16 System.map-4.9.0-2-amd64
> > -rw-r--r-- 1 root root  3176652 May  2 17:21 System.map-4.9.0-3-amd64
> > -rw-r--r-- 1 root root  4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64
> > -rw-r--r-- 1 root root  4204320 May  2 17:21 vmlinuz-4.9.0-3-amd64
>

Re: Is this sources.list correct?

[Dejan Jocic]

On 22-05-17, Fungi4All wrote:
>  Original Message 
> Subject: Re: Is this sources.list correct?
> UTC Time: May 22, 2017 6:09 AM
> From: compro...@list.comprofix.com
> fjfj...@protonmail.com
> 
> On Mon, May 22, 2017 at 12:45:05AM -0400, Fjfj109 wrote:
> > On Stretch, upgraded from Jessie. https://paste.debian.net/933553/
> 
> When updating from Jessie to Stretch. Just replace all the 'Jessie' 
> references in your /etc/apt/sources.list file to 'Stretch'
> 
> You can do this with a quick sed (backup your sources.list first):
> 
> sed -i 's|jessie|stretch|g' /etc/apt/sources.list
> 
> Your sources look OK. I compared them to a Jessie one that I have and other 
> than the repo you are referencing looks good.
> 
> This is an optional addition to consider:
> http://ftp.debian.org/debian/dists/stretch-backports/
> 
> https://backports.debian.org/ read some before you decide
> 
> Thanks
> Matt
> 
> AK

Or, even better, you can use slight change in that sed command to get
both changed sources.list and backup:

#sed -i.bak 's/jessie/stretch/g' /etc/apt/sources.list

will get you changed sources.list and old sources.list.bak file. Of
course, you can change that .bak with your preferred suffix for back up
files.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, Brian wrote:
> On Sun 21 May 2017 at 22:18:11 +0200, Dejan Jocic wrote:
> 
> > On 21-05-17, David Wright wrote:
> > > On Sun 21 May 2017 at 16:31:55 (+0200), Dejan Jocic wrote:
> > > > > 
> > > > As for number 1 can't say much about it, I do not get it either. But 2
> > > > happens because you've used apt-get upgrade instead of apt-get
> > > > dist-upgrade. Packages that will uninstall some packages already
> > > > installed on your system and that will change some dependencies 
> > > > require dist-upgrade.
> > > 
> > > Agreed.
> > > 
> > > > It happens always in case of linux-image packages. 
> > > 
> > > Is this¹ new with stretch? My linux-images upgrade just like any other
> > > package; here's the penultimate occasion for jessie:
> > > 
> > > Start-Date: 2017-03-08  19:20:34
> > > Commandline: apt-get upgrade
> > > Upgrade: linux-source-3.16:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > linux-headers-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > linux-image-3.16.0-4-586:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > linux-libc-dev:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > linux-compiler-gcc-4.8-x86:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2), 
> > > linux-headers-3.16.0-4-common:i386 (3.16.39-1+deb8u1, 3.16.39-1+deb8u2)
> > > End-Date: 2017-03-08  19:22:50
> > > 
> > > (The last one's log was rather larger.)
> > 
> > Ehh, sorry not sure if it is new with Stretch, can't remember for
> > Jessie. I'm certain that it was like that on Stretch and on Ubuntu
> > 16.04.
> 
> Rather than just a contrast, I was rather hoping to hear how David
> Wright's observations (which I agree with)fit in with yours.
> 
Sorry, not sure what I can add to it. 

> > > > It will leave your previous working linux-image on though, but will 
> > > > uninstall one older than that, so you will always end up with chance to 
> > > > boot in working kernel, if new one messes up some things.
> > > 
> > > Same question. My wheezy system has had at least 28 linux-image
> > > upgrades (3.2.57-3+deb7u2→3.2.60-1+deb7u1 to 3.2.86-1→3.2.88-1)
> > > but there's still only one kernel image on the system:
> > > 
> > > -rw-r--r-- 1 root root  134839 Apr 27 16:52 config-3.2.0-4-686-pae
> > > drwxr-xr-x 3 root root   12288 Apr 28 07:44 grub
> > > -rw-r--r-- 1 root root 2672854 Apr 28 07:44 initrd.img-3.2.0-4-686-pae
> > > -rw-r--r-- 1 root root 1674268 Apr 27 16:52 System.map-3.2.0-4-686-pae
> > > -rw-r--r-- 1 root root 2709184 Apr 27 16:51 vmlinuz-3.2.0-4-686-pae
> > > 
> > > (I have to notice these upgrades myself because they overwrite
> > > my edited version of /boot/grub/grub.cfg which I then replace.)
> > > 
> > > Cheers,
> > > David.
> > > 
> > > ¹ I'm not disagreeing that something is holding back the upgrade
> > > on this specific occasion, but this is unusual.


This is what I have in /boot and, as stated above, usual outcome of
upgrades, both in Stretch and in Ubuntu 16.04:

-rw-r--r-- 1 root root   186695 Mar 30 03:16 config-4.9.0-2-amd64
-rw-r--r-- 1 root root   186380 May  2 17:21 config-4.9.0-3-amd64
drwxr-xr-x 5 root root 4096 May 19 08:55 grub
-rw-r--r-- 1 root root 19660713 May 17 16:43 initrd.img-4.9.0-2-amd64
-rw-r--r-- 1 root root 19534447 May 18 08:40 initrd.img-4.9.0-3-amd64
-rw-r--r-- 1 root root  3169870 Mar 30 03:16 System.map-4.9.0-2-amd64
-rw-r--r-- 1 root root  3176652 May  2 17:21 System.map-4.9.0-3-amd64
-rw-r--r-- 1 root root  4193832 Mar 30 18:43 vmlinuz-4.9.0-2-amd64
-rw-r--r-- 1 root root  4204320 May  2 17:21 vmlinuz-4.9.0-3-amd64

As you can see, 2 kernels. All i do is my morning routine which consists
of apt-get update && apt-get upgrade, followed by apt-get dist-upgrade
in case of need(as stated before, usually case of need is kernel
upgrade). Of course, it is followed by apt-get autoremove too.I do not
have anything unusual on this system.  It was fairly recent install of
jessie(few months ago), followed by upgrade to stretch right after
install. Was installed from unofficial net-install cd with firmware on
it. Also, nothing was changed in apt preferences and stuff like that.

> > 
> > Sorry, but you are doing it wrong way. Grub 2 should not be customized
> > by editing /boot/grub/grub.cfg , but by editing /etc/default/grub and
> > files in /etc/grub.d/. Reason is obvious, your customization is lost
> > whenever something related to linux-image is upgraded. Just saying :)
> 
> "Wrong" isn't quite the right way to put. For most people in most
> circumstances editing grub.cfg and using update-grub is a wise procedure
> and to be advocated. But a hand-crafted grub.cfg can be very useful.
> update-grub can be prevented from getting its hands on it with
> dpkg-divert,
> 
> -- 
> Brian.
> 

Well, I was always under assumption that in case of grub2 you can change
anything in grub.cfg by editing /etc/default/grub and files in
/etc/grub.d/. Perhaps I was wrong about it, in which case I do
apologise.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 22-05-17, Richard Owlett wrote:
> On 05/21/2017 09:31 AM, Dejan Jocic wrote:
> > On 21-05-17, Richard Owlett wrote:
> > > [snip]
> > > 
> > > My questions:
> > > 
> > > 1. In the first run, I don't understand:
> > >  Processing triggers for initramfs-tools (0.130) ...
> > >  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> > >  I: The initramfs will attempt to resume from /dev/sda5
> > >  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> > >  I: Set the RESUME variable to override this.
> > >  As /dev/sda5 is my SWAP.
> > > 
> > > 2. I don't understand any implications of:
> > >  The following packages have been kept back:
> > >linux-image-686-pae xorg xserver-xorg
> > > 
> > > TIA
> > > 
> > > 
> > > 
> > > 
> > As for number 1 can't say much about it, I do not get it either. But 2
> > happens because you've used apt-get upgrade instead of apt-get
> > dist-upgrade. Packages that will uninstall some packages already
> > installed on your system and that will change some dependencies
> > require dist-upgrade. It happens always in case of linux-image packages.
> > It will leave your previous working linux-image on though, but will
> > uninstall one older than that, so you will always end up with chance
> > to  boot in working kernel, if new one messes up some things.
> > 
> 
> If I had problems after doing apt-get dist-upgrade,
>   1. how would I distinguish a kernel problem from other problems?
>   2. how would I boot with the previous kernel?
>   3. is there some specific documentation I should be reading?
> 
> I've done online upgrades before having relied on purchased DVD sets of
> point releases due to bandwidth constraints.
> 
> Thank you.
> 
> 

1. That would depend on problem itself, right? As for kernel problems, I
was unusually lucky with them for years and have yet to run on problem
with upgraded kernel. Must be that new kernels really loved my hardware.

2. It is easy task, as long as there is previous kernel present in your
/boot. If everything works as expected you should have it. From debian
administrator handbook:

8.11.1. Features of a Debian Kernel Package

A Debian kernel package installs the kernel image (vmlinuz-version), its
configuration (config-version) and its symbols table
(System.map-version) in /boot/. The symbols table helps developers
understand the meaning of a kernel error message; without it, kernel
“oopses” (an “oops” is the kernel equivalent of a segmentation fault for
user-space programs, in other words messages generated following an
invalid pointer dereference) only contain numeric memory addresses,
which is useless information without the table mapping these addresses
to symbols and function names. The modules are installed in the
/lib/modules/version/ directory.

The package's configuration scripts automatically generate an initrd
image, which is a mini-system designed to be loaded in memory (hence the
name, which stands for “init ramdisk”) by the bootloader, and used by
the Linux kernel solely for loading the modules needed to access the
devices containing the complete Debian system (for example, the driver
for SATA disks). Finally, the post-installation scripts update the
symbolic links /vmlinuz, /vmlinuz.old, /initrd.img and /initrd.img.old
so that they point to the latest two kernels installed, respectively, as
well as the corresponding initrd images.

Most of those tasks are offloaded to hook scripts in the
/etc/kernel/*.d/ directories. For instance, the integration with grub
relies on /etc/kernel/postinst.d/zz-update-grub and
/etc/kernel/postrm.d/zz-update-grub to call update-grub when kernels are
installed or removed. 

As you can see there, if everything works as intended, you will still
have your old kernel installed, which you can choose from grub menu.
Think that it is under advanced options, but did not use it recently and
am not in mood to reboot now to check. Anyway, as long as you do not use
apt-get autoremove, even your older than previous kernel packages should
be around, though I did not have need for that.

3. https://debian-handbook.info/ and usual man pages for grub, kernel,
apt-get and friends, I guess.

Pleasure :)

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, Richard Owlett wrote:
> I had done:
>   apt-get update
>   apt-get upgrade
> The tail end of the output was:
> ...
> Setting up libkde3support4 (4:4.14.26-2) ...
> Setting up libktexteditor4 (4:4.14.26-2) ...
> Setting up libkdewebkit5 (4:4.14.26-2) ...
> Setting up libkhtml5 (4:4.14.26-2) ...
> Setting up libplasma3 (4:4.14.26-2) ...
> Setting up kdelibs5-plugins (4:4.14.26-2) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> I: Set the RESUME variable to override this.
> Processing triggers for libc-bin (2.24-10) ...
> root@stretch-2nd:/home/richard#
> 
> Before asking for confirmation to do the "upgrade" it said 3 packages would
> not be upgraded.
> If it said which packages, I didn't spot it.
> I then reran with following result.
> 
> root@stretch-2nd:/home/richard# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer
> required:
>   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> mate-indicator-applet
>   mate-indicator-applet-common python3-psutil python3-setproctitle
> Use 'apt autoremove' to remove them.
> The following packages have been kept back:
>   linux-image-686-pae xorg xserver-xorg
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> root@stretch-2nd:/home/richard#
> 
> My questions:
> 
> 1. In the first run, I don't understand:
>  Processing triggers for initramfs-tools (0.130) ...
>  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
>  I: The initramfs will attempt to resume from /dev/sda5
>  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
>  I: Set the RESUME variable to override this.
>  As /dev/sda5 is my SWAP.
> 

Actually, after bit of digging, that part became much more clear,
because resume option is used to specify partition device for software
suspend, and swap is logical choice for that.

Re: Questions after doing update and upgrade on Stretch

[Dejan Jocic]

On 21-05-17, Richard Owlett wrote:
> I had done:
>   apt-get update
>   apt-get upgrade
> The tail end of the output was:
> ...
> Setting up libkde3support4 (4:4.14.26-2) ...
> Setting up libktexteditor4 (4:4.14.26-2) ...
> Setting up libkdewebkit5 (4:4.14.26-2) ...
> Setting up libkhtml5 (4:4.14.26-2) ...
> Setting up libplasma3 (4:4.14.26-2) ...
> Setting up kdelibs5-plugins (4:4.14.26-2) ...
> Processing triggers for initramfs-tools (0.130) ...
> update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
> I: Set the RESUME variable to override this.
> Processing triggers for libc-bin (2.24-10) ...
> root@stretch-2nd:/home/richard#
> 
> Before asking for confirmation to do the "upgrade" it said 3 packages would
> not be upgraded.
> If it said which packages, I didn't spot it.
> I then reran with following result.
> 
> root@stretch-2nd:/home/richard# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages were automatically installed and are no longer
> required:
>   dconf-cli gir1.2-notify-0.7 libconfig9 libgtkspell3-3-0 libindicator3-7
> mate-indicator-applet
>   mate-indicator-applet-common python3-psutil python3-setproctitle
> Use 'apt autoremove' to remove them.
> The following packages have been kept back:
>   linux-image-686-pae xorg xserver-xorg
> 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> root@stretch-2nd:/home/richard#
> 
> My questions:
> 
> 1. In the first run, I don't understand:
>  Processing triggers for initramfs-tools (0.130) ...
>  update-initramfs: Generating /boot/initrd.img-4.9.0-2-686-pae
>  I: The initramfs will attempt to resume from /dev/sda5
>  I: (UUID=5d0c821b-26b2-4d38-b7fe-dc7db1b72576)
>  I: Set the RESUME variable to override this.
>  As /dev/sda5 is my SWAP.
> 
> 2. I don't understand any implications of:
>  The following packages have been kept back:
>linux-image-686-pae xorg xserver-xorg
> 
> TIA
> 
> 
> 
> 
As for number 1 can't say much about it, I do not get it either. But 2
happens because you've used apt-get upgrade instead of apt-get
dist-upgrade. Packages that will uninstall some packages already
installed on your system and that will change some dependencies 
require dist-upgrade. It happens always in case of linux-image packages. 
It will leave your previous working linux-image on though, but will 
uninstall one older than that, so you will always end up with chance to 
boot in working kernel, if new one messes up some things.

Re: Report bug.

[Dejan Jocic]

On 22-05-17, G wrote:
> well my touchpad works when i start my laptop. Sometimes after a while
> it stop working. Touchpad works again after i reboot my laptop. I dont
> see how that is a hardware problem.
> I got more than two packages that match with the installed
> xserver-xorg-input-libinput - X.Org X server -- libinput input driver
> xserver-xorg-input-synaptics - Synaptics TouchPad driver for X.Org server
> 
> 
> On 05/22/2017 04:44 PM, Dejan Jocic wrote:
> > On 22-05-17, G wrote:
> >> Hello.
> >> After a while touchpad stop working. Im trying to report that bug but i
> >> dont know which package to report.
> >> Thanks
> >>
> > 
> > 
> > 1. For start, are you sure that it is system fault, not hardware fault?
> > If you have another system installed in dual boot, or live dvd/cd/usb,
> > did you check with it if touchpad works?
> > 
> > 2. Are you sure that you did not turn off touchpad? 
> > 
> > 3. If you are sure that it is system fault, do apt-cache search
> > touchpad. After that, compare those packages with packages you have
> > installed. Was there upgrade of some of those packages recently? Did
> > your touchpad stopped working after some of those upgrades?
> > 
> > 
> > 
> 

In my case, I've had xserver-xorg-input-synaptics removed, because it
was messing something in Gnome, like touchpad settings not showing up in
system settings. While you could/should report bug about some package,
you can also try uninstalling it too, perhaps it will solve your
problem. If not, you can reinstall it. As for questions 1 and 2, it is
logical course of actions and you did not provide much things to start
with, but I do apologise if it sounded condescending to you, or
something like that.

Re: Report bug.

[Dejan Jocic]

On 22-05-17, G wrote:
> Hello.
> After a while touchpad stop working. Im trying to report that bug but i
> dont know which package to report.
> Thanks
> 


1. For start, are you sure that it is system fault, not hardware fault?
If you have another system installed in dual boot, or live dvd/cd/usb,
did you check with it if touchpad works?

2. Are you sure that you did not turn off touchpad? 

3. If you are sure that it is system fault, do apt-cache search
touchpad. After that, compare those packages with packages you have
installed. Was there upgrade of some of those packages recently? Did
your touchpad stopped working after some of those upgrades?