ah!grizzler wrote:That's what the 'sudo apt-get -f install' is for. It tries to pick up the pieces the incomplete dpkg -i left behind........

ah!grizzler wrote:That's what the 'sudo apt-get -f install' is for. It tries to pick up the pieces the incomplete dpkg -i left behind........
-f, --fix-broken
Fix; attempt to correct a system with broken dependencies in place. This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution.
...
It is possible that a system's dependency structure can be so corrupt as to require manual intervention (which usually means using dpkg --remove to eliminate some of the offending packages)...
It will install all of them. At the top of that page it says:Fargo wrote:I just installed, SolydX 32bit. I love the installer. Is that new? I don't remember it from before. Its much nicer than some of the other installers I've seen lately. Also the 'Welcome' screen is fantastic. Lots of good info in there and a quick way to install software. All I installed was the codecs. I never checked the other items so forgive my ignorance, but if I click the 'install' button on the graphics page for example, can I install only Digikam? Or will it install everything listed on the page?
Not really, but I've seen this happen with several of the distros I've installed over the years. Sometimes the same ISO will even produce a different result on different attempts on the same machine. I've given up trying to make sense of that...Issues: Really the only issue I had was after install my system hung up and didn't restart. Is this normal?
Nah... Not everyone has the same quick response time.Suggestion: The grub timeout screen could have shorter duration. Since we are not tracking Stable it seems less likely to need to boot into other kernels or anything, so a short time of 1 second or something seems reasonable just to splash the screen to people if they do need to boot into a help mode.
Jessie isn't Stable yet, so new packages will appear almost every day, but this should really only be bugfixes, so I wouldn't expect anything disruptive to show up.Last question: Are these repos all finalized? That is can I send the machine out the door to a needy person and know that they will get security updates and etc.
Thanks, I missed that. Glad I didn't click install. I don't see a need to install all of them. If its not too difficult to do, it might be a good idea to allow selection of individual programs. But then again, hopefully new users will read the screen more closely than I did and will just go to the software center. Or they might install all of them to see what they like.grizzler wrote:It will install all of them. At the top of that page it says:
"When you click the install button all listed applications are going to be installed on your system. You can use the software manager to install them separately."
You can always visit the Welcome sequence again, by the way. It's in the menu.
I have seen it before too. I just wanted to make sure I had a good install.grizzler wrote:Not really, but I've seen this happen with several of the distros I've installed over the years. Sometimes the same ISO will even produce a different result on different attempts on the same machine. I've given up trying to make sense of that...Issues: Really the only issue I had was after install my system hung up and didn't restart. Is this normal?
Fair enough.grizzler wrote:Nah... Not everyone has the same quick response time.Suggestion: The grub timeout screen could have shorter duration. Since we are not tracking Stable it seems less likely to need to boot into other kernels or anything, so a short time of 1 second or something seems reasonable just to splash the screen to people if they do need to boot into a help mode.
Seriously, five seconds as a default seems fine to me. You can always change it (in /etc/default/grub - needs 'sudo update-grub' to become effective) if you want.
I knew Jesse wasn't Stable yet. I was more concerned about the address of the SolydKX repos themselves changing than updates coming from Jessie. I feel comfortable enough with the stability of Jessie to use it and send it off to others. As long as the SolydXK repos remain the same and the new users will continue to get the updates I'm good.grizzler wrote:Jessie isn't Stable yet, so new packages will appear almost every day, but this should really only be bugfixes, so I wouldn't expect anything disruptive to show up.Last question: Are these repos all finalized? That is can I send the machine out the door to a needy person and know that they will get security updates and etc.
The sources.list is the same as for the 64-bit ISOs. It includes the security repo for Jessie.
If you have installed SolydX, why do you want to install Digikam? This is a KDE application that, on installation, will try to drag in most of KDE with it! While this may not exactly break your system, it will certainly add tons of bloat that will then need to be maintained with larger updates.Fargo wrote:I just installed, SolydX 32bit. I love the installer. Is that new? I don't remember it from before. Its much nicer than some of the other installers I've seen lately. Also the 'Welcome' screen is fantastic. Lots of good info in there and a quick way to install software. All I installed was the codecs. I never checked the other items so forgive my ignorance, but if I click the 'install' button on the graphics page for example, can I install only Digikam? Or will it install everything listed on the page?
Code: Select all
roger@dino:~$ sudo apt-get -s install digikam
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
digikam digikam-data digikam-private-libs docbook-xsl dolphin ffmpegthumbs
javascript-common kate-data katepart kde-baseapps-bin kde-baseapps-data
kde-runtime kde-runtime-data kdelibs-bin kdelibs5-data kdelibs5-plugins
kdoctools kfind konqueror konqueror-nsplugins kpart-webkit libastro1
libattica0.4 libbaloocore4 libbaloofiles4 libbalooqueryparser4
libbaloowidgets4 libbalooxapian4 libdbusmenu-qt2 libdlrestrictions1 libepub0
libgpgme++2 libgps21 libimage-exiftool-perl libiodbc2 libjs-jquery
libkactivities-bin libkactivities-models1 libkactivities6
libkatepartinterfaces4 libkcmutils4 libkdcraw-data libkdcraw23
libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5
libkdewebkit5 libkdnssd4 libkemoticons4 libkexiv2-11 libkexiv2-data
libkfile4 libkfilemetadata4 libkhtml5 libkio5 libkipi-data libkipi11
libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4
libkntlm4 libkonq-common libkonq5-templates libkonq5abi1
libkonqsidebarplugin4a libkparts4 libkpty4 libkrosscore4 libktexteditor4
libkxmlrpcclient4 libmarblewidget19 libnepomuk4 libnepomukcore4
libnepomukquery4a libnepomukutils4 libntrack-qt4-1 libntrack0 libpgf6
libplasma3 libpolkit-qt-1-1 libpoppler-qt4-4 libqca2 libqextserialport1
libqjson0 libqmobipocket1 libqt4-qt3support libqt4-sql-sqlite libqtlocation1
libquazip1 libruby2.1 libshp2 libsolid4 libsoprano4 libsqlite0
libssh-gcrypt-4 libstreamanalyzer0 libstreams0 libthreadweaver4
libxml2-utils libyaml-0-2 libzip2 marble-data marble-plugins
nepomuk-core-data ntrack-module-libnl-0 opencv-data phonon
phonon-backend-vlc plasma-scriptengine-javascript ruby ruby2.1
rubygems-integration soprano-daemon vlc-plugin-pulse
0 upgraded, 118 newly installed, 0 to remove and 0 not upgraded.
Well Digikam was just the example that I used. But you really made a point for me. I was trying to figure out why the Welcome screen had a one touch 'install all' button that would install Digikam and Shotwell and Gimp into the system, when all that is really needed is Shotwell. (Or in the case of SolydK Digikam.)Zill wrote:If you have installed SolydX, why do you want to install Digikam? This is a KDE application that, on installation, will try to drag in most of KDE with it! While this may not exactly break your system, it will certainly add tons of bloat that will then need to be maintained with larger updates.
Shotwell is installed in SolydX by default and so I would really think long and hard about adding Digikam.
grizzler wrote:We'll be building new 32-bit ISOs this weekend. I'll keep this in mind and run some extra checks with the SolydX version.
Yes, please. I don't think keeping the old ones is useful.Schoelje wrote:Let me know if I have to clean up the other ones.
In that case I'm afraid I wouldn't know what else it could be, as I can't reproduce the problem at all...Fargo wrote:FYI - I turned off Plymouth via the Plymouth Manager in my old install. It still hung up on my once. So it may not be Plymouth but something else.
I do have a home network and they were plugged into the LAN. I don't know if they were ever mounted up or not though. They were just plugged in to have NET access.Zill wrote:Fargo: Just a thought! Are your machines stand-alone or are they networked?
There have been shutdown problems due to mounted NFS and CIFS shares not being properly unmounted before the wifi connection to the LAN is dropped and this causes a hang on shutdown.
Users browsing this forum: No registered users and 3 guests