You are not logged in.
- Topics: Active | Unanswered
#326 Re: Desktop and Multimedia » [Solved?] Upgrade to remove LXDE » 2018-04-19 08:24:17
I did try aptitude, but the info was not obviously helpful :-
# aptitude why lxde
i lxde-core Suggests lxde
# aptitude why lxde-core
i lxde Depends lxde-core
# aptitude why-not lxde
Manually installed, current version 9, priority optional
No dependencies require to remove lxde
# aptitude why-not lxde-core
Manually installed, current version 9, priority optional
No dependencies require to remove lxde-coreI'm now going to work through your post from Irrwahn, which Golinux linked to.
Geoff
#327 Re: Desktop and Multimedia » [Solved?] Upgrade to remove LXDE » 2018-04-18 19:50:10
I have just spotted Golinux' link to
https://dev1galaxy.org/viewtopic.php?pid=8217#p8217
I thought that I had the elogin stuff sorted, but will have to check again.
Geoff
#328 Re: Desktop and Multimedia » [Solved?] Upgrade to remove LXDE » 2018-04-18 19:41:23
My laptop has a different history but is currently also on Ascii with LXDE. On this machine dist-upgrade produces :-
# apt-get dist-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:
docbook-xml docbook-xsl libept1.5.0 librarian0 libunique-1.0-0 libxml2-utils linux-image-4.9.0-3-amd64 linux-image-4.9.0-4-amd64 linux-image-4.9.0-5-amd64 rarian-compat sgml-data
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
libpolkit-backend-1-0-elogind lxde lxde-core lxsession lxsession-logout openbox-lxde-session policykit-1 synaptic
The following NEW packages will be installed:
libpolkit-gobject-1-0 libpolkit-gobject-elogind-1-0
The following packages will be upgraded:
devuan-baseconf elogind eudev libelogind0 libeudev1 libpam-elogind libperl5.24 libpolkit-agent-1-0 libpolkit-gobject-1-0-elogind libudev1 perl perl-base perl-modules-5.24 python-wicd sysv-rc task-british-desktop task-english tasksel tasksel-data udev wicd
wicd-daemon wicd-gtk
23 upgraded, 2 newly installed, 8 to remove and 0 not upgraded.
Need to get 10.4 MB of archives.
After this operation, 8,881 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.These packages are a bit different from my desktop machine, but it still wants to rmove LXDE.
Geoff
#329 Desktop and Multimedia » [Solved?] Upgrade to remove LXDE » 2018-04-18 16:03:05
- Geoff 42
- Replies: 27
I am running Ascii and have just tried
apt-get update
apt-get dist-upgrade
and it tells me
The following packages will be REMOVED:
consolekit lxde lxde-core lxsession lxsession-logout openbox-lxde-session slimI have declined this kind offer and have not yet had a chance to work out why it wants to remove LXDE.
Geoff
#330 Re: Desktop and Multimedia » Themes etc. after upgrade Jessie to Ascii - LXDE » 2018-04-18 15:11:55
I should add that my comments about the icons referred specifically to Filezilla, rather than to a general problem after the upgrade. Having said that, in LXDE's "Customise Look and Feel" (Lxappearance) I have also set the Icon Theme to Tango.
Geoff
#331 Re: Desktop and Multimedia » Themes etc. after upgrade Jessie to Ascii - LXDE » 2018-04-17 15:03:43
I popped up Filezilla to check the look and feel. As I mention above, I am running with the Clearlook-Phenix theme and Filezilla looks good to me. It has the general theme and the nice scroll bars and buttons are permanent and not pop-up. Since the Jessie - Ascii upgrade the icons are a bit, er, loud, but editing the setting/Themes, I can select "Tango" which seems to offer nice icons, without changing the overall theme.
Geoff
#332 Re: Hardware & System Configuration » Encrypted volume shutdown issue going from Jessie to ascii » 2018-04-14 10:36:14
A quick look around shows that there are rules in /lib/udev/rules.d/69-lvm-metad.rules so that it would appear that eudev is supposed to work with lvmetad.
Geoff
#333 Re: Hardware & System Configuration » [SOLVED] National characters troubles » 2018-04-14 10:26:31
While the actual problem might not be the fonts, I did look at which fonts might be used for different scripts. Using Pale Moon and its Inspector to list the fonts used, I found that the following scripts used the fonts mentioned :-
Arabic DejaVu Sans
Cyrillic DejaVu Serif
Chinese (S&T) Droid Sans Fallback
Hindi FreeSans
Korean Un Dotum (fonts-unfonts-core)
Thai Noto Sans Thai
This was for a page that did not specify which font to use.
I see that following the Jessie-Ascii upgrade the following fonts were removed by apt-get autoremove :-
Removing fonts-droid (1:4.4.4r2-6) ...
Removing fonts-lyx (2.2.2-1) ...
Removing fonts-roboto (2:0~20160106-2) ...
Removing xfonts-mathml (6) ...Geoff
(edit: added Korean)
#334 Re: Hardware & System Configuration » Encrypted volume shutdown issue going from Jessie to ascii » 2018-04-13 13:33:02
If I have read the docs correctly, lvmetad is used to remember your lvm set-up, so that it can boot faster. If it can't talk to lvmetad, then lvm has to search the hardware itself, which is slower. lvmetad uses udev to get its information. As Ascii uses eudev instead of udev, the question must be, "has eudev been tested against lvmetad?"
Geoff
#335 Re: Hardware & System Configuration » [SOLVED] National characters troubles » 2018-04-13 09:49:08
This is not a problem with fonts, is it? When I upgraded my desk top from Jessie to Ascii, it stopped displaying Chinese characters, although it would still display Hindi, Thai, Arabic and Cyrillic. My laptop on Ascii displays Chinese, but not Hindi and Thai. The problem was a missing font on my desktop. After installing fonts-arphic-ukai the Chinese came back. I still need to check the fonts on my laptop. I have not yet checked which fonts were removed in the upgrade.
Cyrillic is displayed in Pale Moon and if I run Lynx in rxvt-unicode. I have not tried filenames.
Geoff
#336 Re: Hardware & System Configuration » Encrypted volume shutdown issue going from Jessie to ascii » 2018-04-10 16:04:11
I am not using encrytion, but I am using LVM2 (for occasional use of Xen). Since upgrading from Jessie to Ascii, I am also seeing the WARNING: Failed to connect to lvmetad message. I can also see a message in daemon.log lvmetad[2207]: Failed to accept connection errno 11.. lvmetad does appear in a ps listing. messages report random: lvm: uninitialized urandom read (4 bytes read). There do appear to be some pauses in booting. I vaguely recall reading something about random being slower in order to get some good data.
Geoff
#337 Re: Other Issues » Chromium after upgrade - Jessie to Ascii » 2018-04-08 05:58:47
Geoff 42 wrote:After upgrading from Jessie to Ascii, the Chromium package was held back.
Using apt-get dist-upgrade usually solves that kind of problem for me.
I had run apt-get dist-upgrade several times and Chromium was still held back. It was the apt-get autoremove which finally allowed Chromium to be upgraded. I failed to spot which package was causing the dependency problem.
Geoff
#338 Other Issues » Chromium after upgrade - Jessie to Ascii » 2018-04-06 14:14:53
- Geoff 42
- Replies: 3
After upgrading from Jessie to Ascii, the Chromium package was held back. There were also a large number of packages which could be removed with apt-get autoremove. I had a quick look through these and could not see anything which might cause a problem. Doing the autoremove seemed to go smoothly, but had the side effect that Chromium could be upgraded, which I did and am now on 64.0.3282.119-1~deb9u1. Chromium does run, but I have had a couple of errors, while looking at Google maps, suggesting that I reload. It seems to have settled down a bit now and I can't reproduce the error message!
Geoff
#339 Re: Desktop and Multimedia » Themes etc. after upgrade Jessie to Ascii - LXDE » 2018-04-06 13:39:51
Having selected a sensible theme and got things reasonable, I backed out the mods suggested by GNUser and that seems to have made no difference.
I then followed Golinux' link to the XFCE discussion. I notice the comment that LXDM doesn't use /etc/environment and you need to put the magic commands in xsession. I think this is a reference to .xsession or .xsessionrc. I have made both of these links to /etc/X11/Xsession.d/52gtk3-nooverlayscrollbar-nocsd. If I look at the environment I can see :-
$ printenv|grep '=0'|grep -v COL
GTK_OVERLAY_SCROLLING=0
GTK_CSD=0
LIBOVERLAY_SCROLLBAR=0Also
$ grep '=0' .xsession-errors
dbus-update-activation-environment: setting GTK_CSD=0
dbus-update-activation-environment: setting SHLVL=0
dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0
dbus-update-activation-environment: setting LIBOVERLAY_SCROLLBAR=0So it appears that the magic is being set up ok, but the scrollbars are still of the pop-up variety, but of the nice solid variety with up and down buttons.
Geoff
#340 Re: Desktop and Multimedia » Themes etc. after upgrade Jessie to Ascii - LXDE » 2018-04-05 19:11:34
I do recall reading of problems keeping themes going in GTK3, so it was interesting to see MSI's link.
Following Golinux' post, I installed Clearlooks-Phenix and as described, the scrollbars in Synaptic work nicely, although they are still pop-up, but I can probably live with that. While the Clearlook-Phenix-Dark-Purpy does also work well, I do find it a bit, er, dark and prefer the lighter blue version. I was interesed to see that Clearlooks-Phenix-Purpy does not work so well with the scrollbar or with toolbar buttons, but I do notice that it is at an earlier version number.
Thank you for your info and help
Geoff
#341 Desktop and Multimedia » Themes etc. after upgrade Jessie to Ascii - LXDE » 2018-04-05 10:00:28
- Geoff 42
- Replies: 13
While most things worked nicely after the upgrade to Ascii, the look and feel of some of the programs has been upset. One item is that some of the affected programs have non-functioning scrollbars. I knew that I had seen a post about this and eventually found it in "Off-topic". GNUser describes how to improve scrollbars and buttons.
https://dev1galaxy.org/viewtopic.php?id=1945
I think that the problem is with programs using GTK, possibly 3. The ones which I have noticed include emacs and synaptic.
Following GNUser's recipe worked nicely on my laptop, which has been on Ascii for a long time. The laptop also has a reasonable look and feel. My newly upgraded desktop machine is less happy. The scrollbar is now working to some extent in emacs, but is still absent in synaptic. The other problem with the look and feel is that the buttons in the menu bar at the top do not show up as buttons when you hover over them. There are just words in black on a grey background. There is no representation of buttons or tabs, just the words or icons. The only thing that does show up in this area is when a button is greyed out.
I suspect that I have some theme missing, although I have not yet spotted the difference between my 2 set-ups.
I have now been checking the settings for the look and feel. Selecting the "Customise Look and Feel" option from the "Preferences" menu item allows the selection of the theme. I had been using the Raleigh theme. I think that this was meant to look a bit like an IBM theme! If I change this to one of :- CLearlooks, CLearlooks Phenix-DarkPurpy, Adwaita, Industrial or one or 2 others, then the scrollbar is fully displayed and the buttons show when hovered over. My guess is that the Raleigh theme is no longer supported in GTK-3. I have currently settled on Clearlooks.
While the scrollbar is now working in synaptic, it does not seem to be following the style set up by GNUser's recipe, but is of the thin pop-up variety.
Geoff
#342 Re: Other Issues » /lib/systemd/ folder? and /etc/systemd/ folder? » 2018-04-04 10:34:01
Many packages ship with start-up files for systemd, but work without systemd. For a longer answer see :-
https://dev1galaxy.org/viewtopic.php?id=1925
Geoff
#343 Other Issues » Postfix in upgrade - Jessie to Ascii » 2018-04-03 09:41:20
- Geoff 42
- Replies: 0
During the upgrade from Jessie to Ascii, Postfix moves from version 2.11.3 to 3.1.8. In version 3 Postfix introduces a feature to warn you of possible negative effects of changes to default settings. The details can be found at http://www.postfix.org/COMPATIBILITY_README.html.
As I understand it, if there are any default settings which are being used and which have changed, then the old settings will be used, but any future negative effect on your mail delivery will be logged. I think that the idea is that you leave your mail system running, but check the logs and make any config changes that may be required. Once you are happy with your set-up, you can disable the compatability checking in main.cf by settting the compatability_level=N, where N is 2 in this case.
If you run /usr/sbin/postfix check you may notice that as well as the backwards-compatability messages, Postfix may also warn that some files differ. It appears that Postfix has copies of some files in /var/spool/postfix from /etc and /lib and then reports if they have changed. This has been answered at :-
https://serverfault.com/questions/39611 … fer#396127
/var/spool/postfix is where Postfix can run chroot-ed. If the files there are different, then there could be problems if you run chrooted. There were reportedly scripts for setting up the chroot environment in the source code distribution in examples/chroot-setup. Installing postfix-doc does pull in the documentation and create /usr/share/doc/postfix/examples, but doesn't populate it!
As myself I downloaded the sources, after creating the file /etc/apt/sources.list.d/sources.list :-
deb-src http://pkgmaster.devuan.org/merged/ ascii main
apt-get source postfixThis produces a directory postfix-3.1.8 which contains examples/chroot-setup/ which includes the file LINUX2, which sets-up the required files for chroot.
This should produce a copy of the file without having to download the sources :-
cat << EOF > LINUX2
#! /bin/sh
# LINUX2 - shell script to set up a Postfix chroot jail for Linux
# Tested on SuSE Linux 5.3 (libc5) and 7.0 (glibc2.1)
# Other testers reported as working:
#
# 2001-01-15 Debian sid (unstable)
# Christian Kurz <shorty@getuid.de>
# Copyright (c) 2000 - 2001 by Matthias Andree
# Redistributable unter the MIT-style license that follows:
# Abstract: "do whatever you want except hold somebody liable or change
# the copyright information".
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to
# deal in the Software without restriction, including without limitation the
# rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
# sell copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
# IN THE SOFTWARE.
# 2000-09-29
# v0.1: initial release
# 2000-12-05
# v0.2: copy libdb.* for libnss_db.so
# remove /etc/localtime in case it's a broken symlink
# restrict find to maxdepth 1 (faster)
# Revision 1.4 2001/01/15 09:36:35 emma
# add note it was successfully tested on Debian sid
#
# 20060101 /lib64 support by Keith Owens.
#
CP="cp -p"
cond_copy() {
# find files as per pattern in $1
# if any, copy to directory $2
dir=`dirname "$1"`
pat=`basename "$1"`
lr=`find "$dir" -maxdepth 1 -name "$pat"`
if test ! -d "$2" ; then exit 1 ; fi
if test "x$lr" != "x" ; then $CP $1 "$2" ; fi
}
set -e
umask 022
POSTFIX_DIR=${POSTFIX_DIR-/var/spool/postfix}
cd ${POSTFIX_DIR}
mkdir -p etc lib usr/lib/zoneinfo
test -d /lib64 && mkdir -p lib64
# find localtime (SuSE 5.3 does not have /etc/localtime)
lt=/etc/localtime
if test ! -f $lt ; then lt=/usr/lib/zoneinfo/localtime ; fi
if test ! -f $lt ; then lt=/usr/share/zoneinfo/localtime ; fi
if test ! -f $lt ; then echo "cannot find localtime" ; exit 1 ; fi
rm -f etc/localtime
# copy localtime and some other system files into the chroot's etc
$CP -f $lt /etc/services /etc/resolv.conf /etc/nsswitch.conf etc
$CP -f /etc/host.conf /etc/hosts /etc/passwd etc
ln -s -f /etc/localtime usr/lib/zoneinfo
# copy required libraries into the chroot
cond_copy '/lib/libnss_*.so*' lib
cond_copy '/lib/libresolv.so*' lib
cond_copy '/lib/libdb.so*' lib
if test -d /lib64; then
cond_copy '/lib64/libnss_*.so*' lib64
cond_copy '/lib64/libresolv.so*' lib64
cond_copy '/lib64/libdb.so*' lib64
fi
postfix reload
EOFAs root :-
# cd ~user1/src/Devuan/postfix-3.1.8/examples/chroot-setup/
# source LINUX2
postfix: Postfix is running with backwards-compatible default settings
postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details
postfix: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload"
postfix/postfix-script: refreshing the Postfix mail systemThis seems to have updated all of the files correctly.
Geoff
#344 Re: DIY » runit as a process supervisor » 2018-04-02 10:21:27
It was also necessary to update the run file for PostgreSQL so that it sets the version number correctly, now at 9.6.
Geoff
#345 Re: DIY » runit as a process supervisor » 2018-04-01 16:03:53
Upgrading from Jessie to Ascii
When I upgraded my Jessie machine to Ascii, runit did not start. It should be started by a line added at the end of /etc/inittab. The upgrade had removed the start-up script from where it was. The script is now to be found as /etc/runit/2. The end of /etc/inittab should thus now be :-
#-- runit begin
SV:123456:respawn:/etc/runit/2
#-- runit endand runit will then carry on supervising the processes which you have set up.
Geoff
#346 Re: Other Issues » PostgreSQL in upgrade - Jessie to Ascii » 2018-04-01 15:08:28
I did spot the following during the dist-upgrade :-
Processing triggers for postgresql-common (165+deb8u3) ...
supported-versions: WARNING! Unknown distribution: devuan
/usr/share/postgresql-common/supported-versions: 64: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set
/usr/share/postgresql-common/supported-versions: 67: /usr/share/postgresql-common/supported-versions: ID_LIKE: parameter not set
Please submit this as a bug report to your distribution.
Geoff
#347 Re: News & Announcements » Upgrading to ASCII instructions » 2018-04-01 15:00:49
One thing which I forgot to mention was that at the start of the dist-upgrade, it complained that it would run out of space on /var and refused to run. After running apt-get clean, there was still not much space left on /var. It was then that I spotted a large .iso file which I had left in /var/tmp. Removing this enabled the upgrade to proceed!
Geoff
#348 Other Issues » PostgreSQL in upgrade - Jessie to Ascii » 2018-04-01 14:44:38
- Geoff 42
- Replies: 1
During the upgrade from Jessie to Ascii, PostgreSQl produces the following message :-
Obsolete major version 9.4
The PostgreSQL version 9.4 is obsolete, but the server or client packages are still installed. Please install the latest packages (postgresql-9.6 and postgresql-client-9.6) and upgrade the existing clusters with pg_upgradecluster (see manpage).
Please be aware that the installation of postgresql-9.6 will automatically create a default cluster 9.6/main. If you want to upgrade the 9.4/main cluster, you need to remove the already existing 9.6 cluster (pg_dropcluster --stop 9.6 main, see manpage for details).The old server and client packages are no longer supported. After the existing clusters are upgraded, the postgresql-9.4 and postgresql-client-9.4 packages should be removed.
Please see /usr/share/doc/postgresql-common/README.Debian.gz for details.
PostgreSQL is not currently running as I had it under runit.
so, as myself :-
$ pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
9.4 main 5432 down postgres /var/lib/postgresql/9.4/main /var/log/postgresql/postgresql-9.4-main.log
9.6 main 5433 down postgres /var/lib/postgresql/9.6/main /var/log/postgresql/postgresql-9.6-main.logas root :-
# pg_dropcluster --stop 9.6 main$ pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
9.4 main 5432 down postgres /var/lib/postgresql/9.4/main /var/log/postgresql/postgresql-9.4-main.log# pg_upgradecluster 9.4 main
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Creating new cluster 9.6/main ...
config /etc/postgresql/9.6/main
data /var/lib/postgresql/9.6/main
locale en_GB.UTF-8
socket /var/run/postgresql
port 5433
Disabling connections to the new cluster during upgrade...
Roles, databases, schemas, ACLs...
Fixing hardcoded library paths for stored procedures...
Upgrading database postgres...
Analyzing database postgres...
Fixing hardcoded library paths for stored procedures...
Upgrading database user1...
Analyzing database user1...
Fixing hardcoded library paths for stored procedures...
Upgrading database template1...
Analyzing database template1...
Re-enabling connections to the old cluster...
Re-enabling connections to the new cluster...
Copying old configuration files...
Copying old start.conf...
Copying old pg_ctl.conf...
Stopping target cluster...
Stopping old cluster...
Disabling automatic startup of old cluster...
Configuring old cluster to use a different port (5433)...
Starting target cluster on the original port...
Success. Please check that the upgraded cluster works. If it does,
you can remove the old cluster with
pg_dropcluster 9.4 mainFrom ps I can see that postgresql/9.6 is now running, but is the data all set up?
$ pg_dump -f 2018-04-01-dump.sql
pg_dump: server version: 9.6.7; pg_dump version: 9.4.15
pg_dump: aborting because of server version mismatch
$ which pg_dump
/usr/lib/postgresql/9.4/bin/pg_dump
$ /usr/lib/postgresql/9.6/bin/pg_dump -f 2018-04-01-dump.sql
$ v 2018-04-01-dump.sql
-rw-r--r-- 1 user1 user1 79630 Apr 1 14:15 2018-04-01-dump.sql
$ xxdiff 2017-12-15-dump.sql 2018-04-01-dump.sqlThere are minor differences in the settings for tables, such as the removal of Tablespace:,
which look as though they are caused by the new version. The actual data looks good. I had the postgresql path in my .profile, so I have now updated that.
$ psql --no-align --pset=footer=off --file=events_view.sqlproduces the correct data.
But does LibreOffice Base still work with PostgreSQL?
While I extract the data with psql and reformat it into HTML with a bit of Perl, I use LibreOffice Base for data input, with a form for the main entry and using its simple tables for the subsidiary tables. This still works, although I have not actually tried entering any data yet! This uses UCanAccess :-
https://askubuntu.com/questions/187389/ … 571#519571
So everything appears to be running correctly.
Geoff
#349 Re: News & Announcements » Upgrading to ASCII instructions » 2018-04-01 10:32:40
I have just upgraded my desktop machine from Jessie to Ascii, following Chillfan's write-up.
https://git.devuan.org/dev1fanboy/Upgra … e-to-ascii
I am using lxde.
I prepared the sources.list, the keyring upgrade and the update from within X. I then used <ctrl><alt><F1> to get the console before I did the dist-upgrade. This took about an hour and a half, although I do have quite a lot of stuff installed! The upgrade of flightgear-base-data was over 1GB on its own...
I have the kernel metapackage installed, so 4.9 got pulled in. I also have Xen installed, but I don't use it very often and have grub set-up to default to not using Xen. I noticed that the upgrade fiddled with this. When I rebooted, the grub menu theme had been changed a bit and was quite hard to read, but I managed to select the 4.9 kernel, although it hung. I then rebooted and tried the 3.16 kernel and that was ok. I have since booted ok with 4.9 and it is fine, although it seems to take a bit longer to boot.
I was able to do the eudev stuff as above
rm /etc/init.d/udev
apt-get dist-upgradethe only problem is that in the ps uaxf listing, eudev shows up as udevd. I'm trying to remember how it appeared in Jessie, was it systemd-udevd?
I also did the elogind stuff
apt-get install libpolkit-backend-1-0-elogind libpolkit-gobject-1-0-elogindso that I can still shutdown from lxpanel, although there is a warning, it is displayed very briefly but I think it is org.freedesktop.DBus.Error.Noreply.
I also installed lxdm, which replaced slim.
By this point it was basically working and I can log in and have an lxde session.
There are some programs which need a bit of investigation and I will go into details elsewhere, but include :-
Postfix is running in compatability mode :- https://dev1galaxy.org/viewtopic.php?id=1971
PostgreSQL has gone from 9.4 to 9.6 and needs attention :- https://dev1galaxy.org/viewtopic.php?id=1968
runit as a process supervisor was not started, see :- https://dev1galaxy.org/viewtopic.php?pid=8190#p8190
Apache2 seems ok
Claws-mail works and but HTML needs attention :- https://dev1galaxy.org/viewtopic.php?id=1895
Raleigh theme not working :- https://dev1galaxy.org/viewtopic.php?id=1945
Several updates to config files were offered, but generally I kept the current ones and am now going through them. The new configs tend to be in /etc and are suffixed .dpkg-dist so can be found with
find /etc -name '*.dpkg-dist'The other place to look is in /var/log/apt/ term.log seems to have the info that may have scrolled off your screen during the upgrade and history.log lists the packages installed.
Geoff
#350 Re: Off-topic » Music » 2018-03-30 13:57:19
Ah, memories of the Fillmore with the Dead, Jefferson Airplane and all the Bay Area bands. The world looked so hopeful back then . . .
Ah! And you had sunshine and nice weather! Some of us had to wait for them to come over so that we could see them in the pouring rain ...
http://www.ukrockfestivals.com/bA1.html
http://www.ukrockfestivals.com/bickershaw-menu.html
But it was worth the wait ;-)
Geoff
Board footer
