Linux Lite Forums

Software - Support => Installing Software => Topic started by: Coastie on July 22, 2014, 03:45:36 PM

Title: Update problem
Post by: Coastie on July 22, 2014, 03:45:36 PM
Updated a few minutes ago using "Install Updates" and received this message:


Configuration file '/etc/issue'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ?

Had to try a couple of times to catch to copy a couple of times before "Install Updates" terminal window closed because I "interrupted" by closing the window.

 When I entered D:

The following packages were automatically installed and are no longer required:
  atomicparsley get-iplayer id3v2 libany-moose-perl libclass-load-perl
  libclass-method-modifiers-perl libclass-singleton-perl
  libcrypt-blowfish-perl libcrypt-rijndael-perl libdata-amf-perl
  libdata-optlist-perl libdatetime-locale-perl libdatetime-perl
  libdatetime-timezone-perl libhttp-server-simple-perl libid3-3.8.3c2a
  libio-socket-socks-perl liblist-moreutils-perl liblwp-protocol-socks-perl
  libmodule-implementation-perl libmodule-runtime-perl libmouse-perl
  libmp3-info-perl libpackage-stash-perl libpackage-stash-xs-perl
  libparams-classify-perl libparams-util-perl libparams-validate-perl
  libsub-install-perl libtie-ixhash-perl libtry-tiny-perl
  libunicode-string-perl libuniversal-require-perl libwww-mechanize-perl
  rtmpdump
Use 'apt-get autoremove' to remove them.

Not sure what the above items above are. (Firefox and Thunderbird were updated.)

I tried instruction and got the following:

coastie@coastie-desktop:~$ apt-get autoremove
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
coastie@coastie-desktop:~$ su  apt-get autoremove
No passwd entry for user 'apt-get'
coastie@coastie-desktop:~$ linux
The program 'linux' is currently not installed. You can install it by typing:
sudo apt-get install user-mode-linux


What does this mean and what should I do about it?



Title: Re: Update problem
Post by: Scott on July 22, 2014, 03:58:51 PM
I'm in 1.08 and if I run the following command in the terminal

Code: [Select]
cat /etc/issue
I get the following result

Code: [Select]
Linux Lite 1.0.8 LTS \n \l

If you choose the option:
keep your currently-installed version
you will retain the LL issue information

If you choose the option to
install the package maintainer's version
you will *probably* replace the LL issue information with something from Ubuntu
Title: Re: Update problem
Post by: Coastie on July 22, 2014, 04:19:03 PM
I get the following result:

Code: [Select]
Ubuntu 14.04.1 LTS \n \l and the same thing in a System Information report. Looks like Ubuntu has screwed me.

I should have picked N to keep LL 2.0. I thought the package maintainer was Linux Lite (Valtam) because some of the updates are from Linux Lite (Valtam).

Will I have to reinstall LL or is there another option?



Title: Re: Update problem
Post by: Jerry on July 22, 2014, 06:52:24 PM
This has been covered in the past, the Default option [default=N] is always the right option to choose.
Title: Re: Update problem
Post by: Coastie on July 22, 2014, 07:05:06 PM
Will I have to reinstall LL or is there another option?
Title: Re: Update problem
Post by: Scott on July 22, 2014, 07:56:18 PM
@Coastie
No, you don't need to reinstall. The issue file can be easily replaced with the correct information.

Backup the current issue file
Code: [Select]
sudo mv /etc/issue /etc/issue.bak
Create a new issue file with the correct information
Code: [Select]
sudo bash -c 'echo "Linux Lite 2.0 LTS \n \l" > /etc/issue'
Title: Re: Update problem
Post by: gold_finger on July 22, 2014, 08:18:07 PM
Coastie,

Scott(0) already answered that no install is necessary.  I'll just go through rest of your original post.


The following packages were automatically installed and are no longer required:
  atomicparsley get-iplayer id3v2 libany-moose-perl libclass-load-perl
  libclass-method-modifiers-perl libclass-singleton-perl
  libcrypt-blowfish-perl libcrypt-rijndael-perl libdata-amf-perl
  libdata-optlist-perl libdatetime-locale-perl libdatetime-perl
  libdatetime-timezone-perl libhttp-server-simple-perl libid3-3.8.3c2a
  libio-socket-socks-perl liblist-moreutils-perl liblwp-protocol-socks-perl
  libmodule-implementation-perl libmodule-runtime-perl libmouse-perl
  libmp3-info-perl libpackage-stash-perl libpackage-stash-xs-perl
  libparams-classify-perl libparams-util-perl libparams-validate-perl
  libsub-install-perl libtie-ixhash-perl libtry-tiny-perl
  libunicode-string-perl libuniversal-require-perl libwww-mechanize-perl
  rtmpdump
Use 'apt-get autoremove' to remove them.

Not sure what the above items above are. (Firefox and Thunderbird were updated.)
Above is just listing packages that are currently on the system but no longer needed.  They are not necessarily something that just happened during the update.  Some/most were probably installed as dependencies for programs that you later removed from the system.  They'll stay on the system unused unless you run that command to remove them.


I tried instruction and got the following:

coastie@coastie-desktop:~$ apt-get autoremove
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
You ran the command and saw that you needed to run it as root.


coastie@coastie-desktop:~$ su  apt-get autoremove
No passwd entry for user 'apt-get'
Here you ran the su command instead of sudo; so system thought you were trying to switch to user named "apt-get" and reported back with
Quote
No passwd entry for user 'apt-get'


coastie@coastie-desktop:~$ linux
The program 'linux' is currently not installed. You can install it by typing:
sudo apt-get install user-mode-linux
Not sure what you were doing here, so just going to ignore it.


To get rid of packages that are no longer needed, just run the above command like this:
Code: [Select]
sudo apt-get autoremove
Title: Re: Update problem
Post by: Coastie on July 22, 2014, 08:50:37 PM
@Coastie
No, you don't need to reinstall. The issue file can be easily replaced with the correct information.

Backup the current issue file
Code: [Select]
sudo mv /etc/issue /etc/issue.bak
Create a new issue file with the correct information
Code: [Select]
sudo bash -c 'echo "Linux Lite 2.0 LTS \n \l" > /etc/issue'

Ran first instruction above:

coastie@coastie-desktop:~$ sudo mv /etc/issue /etc/issue.bak

[sudo] password for coastie:
entered password

then got:

mv: cannot stat ‘/etc/issue’: No such file or director

Tried second and got:
coastie@coastie-desktop:~$ sudo bash -c 'echo "Linux Lite 2.0 LTS \n \l" > /etc/issue'
[sudo] password for coastie:

entered password

then goes back to
coastie@coastie-desktop:~$
Title: Re: Update problem
Post by: Coastie on July 22, 2014, 08:55:23 PM
Coastie,


To get rid of packages that are no longer needed, just run the above command like this:
Code: [Select]
sudo apt-get autoremove

Thanks, think I got that to work but still haven't got LL back..
Title: Re: Update problem
Post by: Scott on July 23, 2014, 12:51:14 AM
When you run the first command you get the following error:

Quote
mv: cannot stat ‘/etc/issue’: No such file or director

because the file issue is not there.


In reply #2 of this post you entered this command

Quote
cat /etc/issue

and got this result

Quote
Ubuntu 14.04.1 LTS \n \l

so the file issue was there.

Sometime between then and now the issue file was removed. This isn't a problem, it can be created easily with this command

Code: [Select]
sudo touch /etc/issue
and now you should be able to run the second command

Code: [Select]
sudo bash -c 'echo "Linux Lite 2.0 LTS \n \l" > /etc/issue'
now we can run a test to see if the issue file is correct

Code: [Select]
cat /etc/issue
you should get this result

Code: [Select]
Linux Lite 2.0 LTS \n \l

Title: Re: Update problem
Post by: robert on July 23, 2014, 04:12:16 AM
Well that last update was interesting!
I got same messages and selected N
Then got a message relating to Grub left it the same.

Oh and the opening welcome sound..........Nice Valtam :)
Title: Re: Update problem
Post by: Jerry on July 23, 2014, 04:15:14 AM
Cheers Robert :)
Title: Re: Update problem
Post by: Coastie on July 23, 2014, 11:14:58 AM
@Coastie
No, you don't need to reinstall. ...

I posted above when I think I correctly tried what Scott(0) recommended but got the results posted. System Information still says my OS is Ubuntu 14.04.01 LTS. Everything seems to be working as normal but I do not think I will get updates for Linux Lite 2.0.

Should I reinstall?
Title: Re: Update problem
Post by: Scott on July 23, 2014, 11:23:33 AM
Hi Coastie

Let's start over. Please run these two commands and post the results. Thank you.

cat /etc/issue
cat /etc/lsb-release
Title: Re: Update problem
Post by: Coastie on July 23, 2014, 11:54:22 AM
will@will-desktop:~$ cat /etc/issue
Linux Lite 2.0 LTS \n \l
will@will-desktop:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
will@will-desktop:~$


Coastie, a.k.a. Will
Title: Re: Update problem
Post by: Scott on July 23, 2014, 12:23:00 PM
Thanks, Will. 8)

The first step/command is correct. Half way there.


The second step/command needs one small change.

The Line
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

Should be changed to
DISTRIB_DESCRIPTION="Linux Lite 2.0"

To make the change
1. Open the file manager, Thunar
2. Navigate to the /etc folder in Thunar
3. At the top area of Thunar type /etc (erasing what's currently there) and press enter
4. You should be in the /etc folder in Thunar now
5. Locate the file lsb-release
6. Open the lsb-release file as administrator --- rt-click on the file lsb-release, choose open as administrator
7. Type in your password
8. The file lsb-release should open
9. Edit the last line of the file
10. Replace the words -- Ubuntu 14.04.1 LTS
11. With the words -- Linux Lite 2.0
12. Save the file
13. The end!

Did it work. Let's test it.
Type cat /etc/lsb-release

You should get the following output
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Linux Lite 2.0"


Did it work?

Title: Re: Update problem
Post by: Coastie on July 23, 2014, 01:07:51 PM
Yes!!!!!!!!!!!

will@will-desktop:~$ cat /etc/issue
Linux Lite 2.0 LTS \n \l
will@will-desktop:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Linux Lite 2.0"


Also System Information shows Linux Lite 2.0 as my OS and Install Updates checked linuxliteos.  8)

Thanked you below your icon again but just want to be sure you know I appreciate your help. Thanks!  :)
Title: Re: Update problem
Post by: asa on July 26, 2014, 05:25:11 PM
ok i made this same problem, dammit. i just read this after i made the mistake. i guess im running ubuntu lite now or something..

cat /etc/issue
Linux Lite 2.0 LTS \n \l

in the terminal it now says linux lite when i followed directions but when shutting down it says ubuntu and it changed my dual boot screen totally which also says ubuntu, so far no other issues than that but if some do become after testing ill just format and learn how to update next time...
Title: Re: Update problem
Post by: gold_finger on July 26, 2014, 07:32:25 PM
i got it from saying ubuntu but when it did not remove anything when i ran auto-remove i guess i will test to see if everything works and learn from this mistake next time ;)

If it didn't remove anything, then there was nothing that needed to be removed.  Nothing to worry about.


ok i made this same problem, dammit. i just read this after i made the mistake. i guess im running ubuntu lite now or something..

As far as I know, this isn't technically a "problem".  Nothing is technically different in the system.  The only thing that is happening is that the description of the system gets changed to the generic "Ubuntu" instead of "LL 2".  If you left it like that, it wouldn't hurt anything.  So again, it's not really something you need to lose sleep over.

EDIT:  Apparently, it can be a problem -- see this post by Valtam (https://www.linuxliteos.com/forums/index.php?topic=665.msg3479#msg3479).
Title: Re: Update problem
Post by: bitsnpcs on July 29, 2014, 11:17:51 PM
Hello,

I made the same error in selection on this update from Ubuntu too.
I have followed the thread and edited the lsb-release file, and checked this in the terminal which now states -
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Linux Lite 2.0"

The Ubuntu splash screen on reboot still occurs when closing, and again when starting up before the Linux Lite Login screen.

I have tried
Code: [Select]
sudo apt-get autoremove and it says there are 0 to be removed.
Title: Re: Update problem
Post by: l337n1nj4 on July 30, 2014, 04:29:45 AM
The Ubuntu splash screen on reboot still occurs when closing, and again when starting up before the Linux Lite Login screen.

Hey bitsnpcs, I had the same problem after installing the latest KDE desktop in my Ubuntu 14.04 LTS install a couple months ago (before I switched to LL  ;D)

What you'll need to do is enter this line of code into Terminal:
Code: [Select]
sudo update-alternatives --config default.plymouth
You should see a list of items, each numbered on the left-side. The boot splash in use will be marked with an * (asterisk), which in this case will probably be the Ubuntu 14.04 LTS boot splash. Look at this list and locate the Linux Lite option (this hasn't happened to me in LL yet, so I can't say what it will be labeled). If you could screenshot the output of this code and upload it, I'm sure one of us will be able to point out which boot splash will be the correct one!

If you do manage to locate the correct LL boot splash, the terminal will ask which number to use. Select the number next to the LL boot splash, and hit Enter. Once that's done, you'll need to input the following code into the same terminal, and then I recommend restarting the system (this will give you a chance to see if the boot splash actually changed):
Code: [Select]
sudo update-initramfs -u
Title: Re: Update problem
Post by: bitsnpcs on July 30, 2014, 08:17:17 PM
Hello l337n1nj4,
thank you for your help.
Here is a screenshot of the Terminal output

(http://i59.tinypic.com/2n6dc3t.png)
Title: Re: Update problem
Post by: l337n1nj4 on July 31, 2014, 12:12:05 AM
Usually, that would have multiple entries, but in your case, it says it only has the default liteboot.plymouth so there shouldn't be a problem. Hmmm, now I'm stumped.

[NOTE]: I was only trying to assist bits in getting the LL boot splash to appear, nothing more, nothing less. I wish I could've helped him solve his entire problem.  :-\
Title: Re: Update problem
Post by: gold_finger on July 31, 2014, 01:29:21 AM
Hello,

I made the same error in selection on this update from Ubuntu too.
I have followed the thread and edited the lsb-release file, and checked this in the terminal which now states -
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Linux Lite 2.0"

The Ubuntu splash screen on reboot still occurs when closing, and again when starting up before the Linux Lite Login screen.

I have tried
Code: [Select]
sudo apt-get autoremove and it says there are 0 to be removed.


bitsnpcs,

You may have already done this, but just in case you missed it -- run this command:
Code: [Select]
cat /etc/issue
You should see this:
Code: [Select]
Linux Lite 2.0 LTS \n \l
If you don't, follow directions here:  https://www.linuxliteos.com/forums/index.php?topic=632.msg3285#msg3285 (https://www.linuxliteos.com/forums/index.php?topic=632.msg3285#msg3285).
Title: Re: Update problem
Post by: bitsnpcs on July 31, 2014, 09:45:37 PM
Usually, that would have multiple entries, but in your case, it says it only has the default liteboot.plymouth so there shouldn't be a problem. Hmmm, now I'm stumped.

[NOTE]: I was only trying to assist bits in getting the LL boot splash to appear, nothing more, nothing less. I wish I could've helped him solve his entire problem.  :-\

I appreciate your help :-)
Title: Re: Update problem
Post by: bitsnpcs on July 31, 2014, 10:07:11 PM
Hello,

I made the same error in selection on this update from Ubuntu too.
I have followed the thread and edited the lsb-release file, and checked this in the terminal which now states -
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Linux Lite 2.0"

The Ubuntu splash screen on reboot still occurs when closing, and again when starting up before the Linux Lite Login screen.

I have tried
Code: [Select]
sudo apt-get autoremove and it says there are 0 to be removed.


bitsnpcs,

You may have already done this, but just in case you missed it -- run this command:
Code: [Select]
cat /etc/issue
You should see this:
Code: [Select]
Linux Lite 2.0 LTS \n \l
If you don't, follow directions here:  https://www.linuxliteos.com/forums/index.php?topic=632.msg3285#msg3285 (https://www.linuxliteos.com/forums/index.php?topic=632.msg3285#msg3285).

Hello gold_finger,
yes I had done this following earlier parts of the thread.
I have done it again to ensure nothing has altered since that time.
The output is as you specified.

(http://i59.tinypic.com/2e3seup.png)

I managed to read one line of the briefly appearing text on Ubuntu boot splash, it says "Starting LightDM".
Title: Re: Update problem
Post by: gold_finger on August 01, 2014, 11:46:27 AM
Hmmm.  I'm not sure at this point.  I'll keep an eye out for solutions and post back if I find one.

Title: Re: Update problem
Post by: bitsnpcs on August 01, 2014, 05:57:55 PM
Hmmm.  I'm not sure at this point.  I'll keep an eye out for solutions and post back if I find one.

Hello gold_finger,
Thank You for your help. I appreciate you keeping an eye out for solutions and posting back if you find one.
Title: Re: Update problem
Post by: bitsnpcs on August 01, 2014, 10:11:13 PM
I placed a sticky note on the edge of the monitor with an arrow on it and rebooted multiple times to read the fast appearing/disappearing text, each time moving the sticky down so I knew where to focus my eyes to try and read it quick enough on next reboot.
I came to a line "X.Org desktop not found"
I changed the graphics driver from "Nvidia tested" to "X.Org X Server Nouveau", the Ubuntu splash screen on shutdown remained, but the Ubuntu boot splash had gone, I rebooted again and the Ubuntu splash on shutdown had also gone.
It has also stopped video playback, attempting this crashes the OS and opens a report dialogue to Ubuntu on auto restart before the login screen. I will ask about graphics in the relevant section.
Title: Re: Update problem
Post by: Scott on August 01, 2014, 10:50:45 PM
Hi Bitsnpcs

Quote
I placed a sticky note on the edge of the monitor with an arrow on it and rebooted multiple times to read the fast appearing/disappearing text...

Sometimes the keyboard pause key helps.
Title: Re: Update problem
Post by: bitsnpcs on August 02, 2014, 02:54:32 AM
Thank you Scott(0) for the info.


Title: Re: Update problem
Post by: Scott on August 02, 2014, 11:16:25 AM
No problem, been in a similar situation a time or two.  8)
Title: Re: Update problem
Post by: rbdflyboy on August 13, 2014, 10:33:35 PM
Updated a few minutes ago using "Install Updates" and received this message:


Configuration file '/etc/issue'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** issue (Y/I/N/O/D/Z) [default=N] ?




This topic is older so hopefully won't get into  too much trouble replying. Had the same output and a different result.
After doing a fresh install ran the updater and received the above message. Picked "D" option and received two output codes that were slightly different. Not exactly sure what to do inputed "Y" option and nothing happened. Please bear in mind it was very early in the morning.
Proceeded to do my set up and some fixes (FF gfx.xrender...) and so on. Went online to finish reading some more reviews and noticed Synaptic is installed...thought great can install Pokerth...found Synaptic and tried to open it...no dice...error msg. Thought, use apt-get install...no, not working. Tried to install something from the terminal menu...no doesn't work either.  Now it's google search time...didn't find anything that was relevant.
By now am thinking maybe this is a corrupt install and remembered the md5sum checked good. Now it boils down to my doing or not doing something correctly. Most answers suggested to check and run updates. Did this over and over and noticed the output shown above did not reproduce itself.
It wasn't until coming here and reading related topics and posts that produced the key to my success.
Ran "sudo apt-get update && sudo apt-get upgrade", that reproduced the the above output. This time used the "Y" option, followed it thru, exited, restarted...good to go.
Synaptic now works and Pokerth is installed 8).
Quite the test for a newbie.... :)