LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices

Reply
 
Search this Thread
Old 06-21-2014, 10:09 AM   #1
CVAlkan
Member
 
Registered: Nov 2012
Distribution: Ubuntu 14.04 LTS
Posts: 42

Rep: Reputation: Disabled
14.04 Startup Screens Not Correct?


I installed 64-bit Ubuntu 14.04 alongside existing Ubuntu 12.04 and Windows installations on my machine using a DVD from Linux Format magazine (LXF185) that they call a "remix" and which offers multiple flavors of *buntu for trial and installation. I don't know if it makes a difference, but I should mention that I had Ubuntu 12.04 installed with a separate /home partition.

While everything works with the new installation, and 14.04 is using the original /home partition, something is amiss with the 14.04 Loading and Shutdown screens (the ones with the "loading dots").

Based on the "System Settings | System: Details" I clearly have Ubuntu 14.04 installed, but the Loading and Shutdown screens show the Lubuntu backgrounds, and I can't figure out how to correct that. I contacted the magazine, of course, but so far have received no response at all, so I'm hoping someone has some suggestions.

The screen that should be displayed (I believe) is /usr/share/backgrounds/warty-final-ubuntu.png, I've found that the config file /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf references the warty-final-ubuntu.png file in its "background=" line. But that .conf file is apparently not used.

When I follow the chain of links from lightdm-gtk-greeter.conf, which is a link to /etc/alternatives/lightdm-gtk-greeter-config-derivative, which in turn is a link to /etc/xdg/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf. That latter file contains the line "background=/lib/plymouth/themes/xubuntu-logo/wallpaper.png" which isn't the same color as the background I'm seeing during load and shutdown. And, of course, that refers to xubuntu, not lubuntu.

I had thought about changing the target of the first link (lightdm-gtk-greeter.conf) to the one with warty, since the end of the current target chain doesn't refence the file I'm seeing on screen, I figured I'm starting at the wrong place or simply don't understand what's going on.

Can anyone explain how this all works, and what I'm missing. Nothing against Lubuntu, but that's not what I'm running, and I'd like to fix this.

Thanks.
 
Old 09-29-2014, 01:57 AM   #2
littlejoe5
Member
 
Registered: Aug 2006
Location: Arizona
Distribution: Various Debian derivitives
Posts: 173

Rep: Reputation: 19
This looks like an old post, but I see no one has answered it. You have said that the dissk you installed from was intended to install various versions sof "*buntu". I have noticed that many of the various versions of Ubuntu haven't removed the internal identification that links back to Ubunto. For instance when I boot into LXLE the boot menu shows "UBUNTU", and several cases within the installed distro mention "Lubuntu".
 
Old 09-29-2014, 09:24 AM   #3
CVAlkan
Member
 
Registered: Nov 2012
Distribution: Ubuntu 14.04 LTS
Posts: 42

Original Poster
Rep: Reputation: Disabled
Thanks for the response.

What you've observed seems to suggest that the problem is more with Canonical (?) than with the magazine that created the disk, but the problem is still there and still annoying.

I've found that many (if not all) components of all the distributions on the disk were installed to my machine (seriously, how many word processors, text editors, configuration utilities and spreadsheets do I need?), and I've been slowly removing them as time permits. I've gradually moved and renamed things so the startup and shutdown screens reflect the actual installation (wouldn't want to get the NSA or my grandkids confused when they troll my machine).

The number of things that got installed with 14.04 reminds me of a Windows bloatware installation, although I must say I tried many of the apps just to see what they were like - which I doubt I would ever have done otherwise.

But, we've only had personal computers for thirty-five years or so - certainly not enough time to achieve any sort of consistency

Have a great day.
 
Old 09-30-2014, 11:56 AM   #4
littlejoe5
Member
 
Registered: Aug 2006
Location: Arizona
Distribution: Various Debian derivitives
Posts: 173

Rep: Reputation: 19
Bloatware is a pain for sure, and getting worse in many distros. But (my opinion) nowhere near Windows-style bloatware. But I don't really call it bloatware, if the install disk installs programs that I haven't used. I may or may not learn to use them.

What we be very handy is if there was a program that would allow to greatly reduce the bootup time by eliminating all of the junk and retries pertaining to equipment that is not even a part of my computer. And all of those annoying waits in the bootup scripts.

And perhaps a way to eliminate programs that are sections of "meta" installations, such as "open office draw". I'm sure that some people must like and use it, but I never do, and would like to get rid of it.
 
Old 10-02-2014, 06:08 PM   #5
widget
Senior Member
 
Registered: Oct 2008
Location: S.E. Montana
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,335

Rep: Reputation: 395Reputation: 395Reputation: 395Reputation: 395
Canonical used to, and I am sure continues to, offer a netinstall ISO image. This most things from the internet. The base install is installed and then you can install what you want after that. This can make for a much smaller, less bloated install.

If you want to remove some packages from a meta package there are 2 ways to do this.

1>Remove the meta package and install just the components you want. As long as you do not purge the package your configuration files should still be in tact.

2>Open aptitude and run, as root;
Code:
aptitude keep-all
You can then remove the individual components you want to remove.

The "keep-all" command changes the state of your packages to manual from, in the case of meta package packages, automatic. You need to concider this before using the command. It can lead to problems.

I have not run anything from Ubuntu for quite a while. It is rather brittle and may not function well if you go tha that route. I would be a bit leary of trying any kind of real tools for dealing with this myself. They removed aptitude years ago so users couldn't mess with the way they want to set things up. This trend toward a co-dependent system that breaks when messed with has only gotten more intense from what I read. Therefore I would not really recommend using option 2 under Ubuntu.

If you want control of your sytem and must use Ubuntu try to learn enough to go the netinstall route. It will still load your system with a lot of limiting factors and some bloat (ridiculous crap dragged in by the package ubuntu-minimal) but that is what makes Ubuntu what it is. You will not have to have all the stuff dragged in by the "whatever-desktop" packages or any other meta packages if you do a little homework.

You can see the depends for those packages in Synaptic if you set the preferencs right. It is hard to copy the information out of there though.

Much better is to use;
Code:
sam@lounge:~$ apt-cache showpkg xfce4
Package: xfce4
Versions: 
4.10.1 (/var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_binary-amd64_Packages) (/var/lib/dpkg/status)
 Description Language: 
                 File: /var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_binary-amd64_Packages
                  MD5: 53123f9cf40a71f1a87679634af17db3
 Description Language: en
                 File: /var/lib/apt/lists/ftp.us.debian.org_debian_dists_sid_main_i18n_Translation-en
                  MD5: 53123f9cf40a71f1a87679634af17db3


Reverse Depends: 
  xfwm4,xfce4
  xfwm4,xfce4
  task-xfce-desktop,xfce4
  desktop-base,xfce4
  education-desktop-xfce,xfce4
Dependencies: 
4.10.1 - xfwm4 (2 4.10.0) xfconf (2 4.10.0) xfce4-settings (2 4.10.0) xfce4-panel (2 4.10.0) xfdesktop4 (2 4.10.0) thunar (2 1.6.0) gtk2-engines-xfce (2 3.0.0) xfce4-session (2 4.10.0) xfce4-appfinder (2 4.10.0) xfce4-mixer (2 4.10.0) orage (2 4.8.0) libxfce4ui-utils (2 4.10) xfce4-goodies (0 (null)) xfce4-power-manager (2 1.2.0) gtk3-engines-xfce (2 3.0.0) xorg (0 (null)) desktop-base (2 5.0.4) thunar-volman (2 0.8.0) tango-icon-theme (2 0.8.90) xfce4-notifyd (0 (null)) 
Provides: 
4.10.1 - 
Reverse Provides:
The Dependencies are what you need to copy out so you know what to install. For instance I really have no problem with most of what is installed with the example package above; xfce4 (from Debian obviously). Main problem there is the xfce4-goodies package which is a meta package on its own and has a lot of things I don't use. There for I install the rest of the stuff manually and then the, I think, 2 out of a lot of packages in the "goodies" package.

That is all a meta package is, an empty package with several depends. Note for instance "xfce4-goodies (0 (null)". There is no version number. It is an empty package. The actually packages are listed in the install script for the package and they get installed.

When you try to remove any package that is installed by a meta package it will, because you are removing a dependency, remove the entire package. Depends all have the state of automatic. If you install those same packages individually then they will have the state of manual. They will have depends of their own that will be installed and have state automatic.

Meta packages are great. They save a lot of typing. If you have a couple of boxes on which you want the same install you can see this could be a real pain. There are other tools for cloning an install, however, if that is the case.

Those tools are all included in any Debian based system in your package management system. Of coarse there are 3rd party applications that will do the same thing and this is the way for Ubuntu users to go. Most do not want to know what package management even means. Those 3rd party applications use the native tools without you having to think. Of coarse the first time their built in scripts to run the base commands screws up it becomes difficult to correct any issues but you can always reinstall and complain about the "hardness" of doing these things.
 
  


Reply

Tags
startup, ubuntu 14.04


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Black screens on graphical startup Irenaeus Linux - Newbie 5 04-18-2008 10:11 PM
Occasional black screens at startup holyfeces Linux - Newbie 6 01-15-2005 04:15 PM
Correct way to run daemon at startup robbiemorgan Linux - Newbie 8 09-20-2004 09:19 AM
Mandrake ugly startup screens Scrag Mandriva 4 05-15-2004 11:53 PM
Is there away to change the startup screens? Sabastian Linux - Software 5 06-19-2003 03:25 AM


All times are GMT -5. The time now is 04:35 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration