Re: [DNG] ASCII 2.1 to Beowulf: Report + questions [trash icon fix]
Sun, 22 Mar 2020 17:53:17 +0100 - al3xu5 / dotcommon : > Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1]. > > [...] > > 5. Some MATE problems: > > [...] > > 5.2. The trash icon don't work as expected anymore: if the trash can contains > data then the full-trash icon and its label are displayed; when empty, there > isn't any trash icon bau the label is still in place. I suppose this is a > problem with the theme and/or the svg icon being used (but I cannot figure out > which one is among the many svg trash icons in /usr/share/icons ...) I have found a solution. The problem occurs due a rendering issue related to an improper reference in the SVG empty-trash icon /usr/share/icons/gnome-colors-common/scalable/places/user-trash.svg On around line 710 of the svg file there is a reference to `filter:url(#filter3625)` which doesn't exist in this svg file. Deleting that filter reference fixes the problem. see: https://bugzilla.redhat.com/show_bug.cgi?id=1645368 Regrads -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpVl7eaHU66v.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
Mon, 23 Mar 2020 09:42:59 + - Mark Hindley : > On Mon, Mar 23, 2020 at 10:32:44AM +0100, al3xu5 / dotcommon wrote: > > > Does `apt install libpam-elogind' fix it? > > > > Hum... that's what I have: > > > > ~~~ > > $ sudo apt-get install libpam-elogind > > Lettura elenco dei pacchetti... Fatto > > Generazione albero delle dipendenze > > Lettura informazioni sullo stato... Fatto > > I seguenti pacchetti aggiuntivi saranno inoltre installati: > > elogind libelogind0 > > I seguenti pacchetti saranno RIMOSSI: > > libsystemd0 > > I seguenti pacchetti saranno aggiornati: > > elogind libelogind0 libpam-elogind > > 3 aggiornati, 0 installati, 1 da rimuovere e 1 non aggiornati. > > ~~~ > > > > It sounds good... Should I apply? > > Within the limits of my Italian ;), it looks good. Ooops... sorry I neglected to translate or specify... I have run 'apt-get install libpam-elogind': elogind libelogind0 libpam-elogind were updated (and libsystemd0 has been removed); but not calf-plugins. > I will have to look further as to why this needs an explicit command. Did you > `apt upgrade' or `apt full-upgrade'? None of this. I did: # apt-get dist-upgrade (as suggested in https://beta.devuan.org/os/documentation/dev1fanboy/en/upgrade-to-beowulf) Regards -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpIcuLC6Th5V.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
Sun, 22 Mar 2020 19:29:28 -0400 - fsmithred : > On 3/22/20 12:53 PM, al3xu5 / dotcommon wrote: > > Hi all > > > > Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1]. > > > > > Now I have: > > ~~~ > > $ uname -a > > Linux computer0 4.6.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian > > 4.6.4-1~bpo8+1 (2016-08-11) x86_64 GNU/Linux > > You can do one of two things to get the beowulf kernel - either install > linux-image-amd64, which is a metapackage that will always install the > latest available kernel, or you can install the kernel by the full package > name, currently linux-image-4.19.0-8-amd64. I am using a -rt-amd64 kernel (for audio-related needs), so the kernel package which I am interested to should be: linux-image-4.19.0-8-rt-amd64 I haven't installed it yet because the system is stable and I would like to avoid problems because I'm using it for remote working. I will update the kernel during next ween-end... > If you do the latter, stay alert to when -9 comes out. You won't get it > automatically. If you mean I will need to update it manually, I will do it... > > 2. Having upower installed, I have downgraded upower packages as suggested > > in [1], to avoid problems like bug#394 [2] which seems mainly related to > > cinnamon. But I do not have cinnamon... So what I should do? Downgrade or > > not? If not, how to disable downgrading of those packages? > > Take the downgrade. It's not really a downgrade; it's an upgrade to a > lower-numbered version. (We no longer need to fork upower.) Ah ok. Great. Thanks a lot for your advices. Regards -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpc45K9oExsr.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
On Mon, Mar 23, 2020 at 10:32:44AM +0100, al3xu5 / dotcommon wrote: > > Does `apt install libpam-elogind' fix it? > > Hum... that's what I have: > > ~~~ > $ sudo apt-get install libpam-elogind > Lettura elenco dei pacchetti... Fatto > Generazione albero delle dipendenze > Lettura informazioni sullo stato... Fatto > I seguenti pacchetti aggiuntivi saranno inoltre installati: > elogind libelogind0 > I seguenti pacchetti saranno RIMOSSI: > libsystemd0 > I seguenti pacchetti saranno aggiornati: > elogind libelogind0 libpam-elogind > 3 aggiornati, 0 installati, 1 da rimuovere e 1 non aggiornati. > ~~~ > > It sounds good... Should I apply? Within the limits of my Italian ;), it looks good. I will have to look further as to why this needs an explicit command. Did you `apt upgrade' or `apt full-upgrade'? Mark ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
Hi Mark Sun, 22 Mar 2020 18:28:21 + - Mark Hindley : > > 1- There is one aspect of the upgrade that I don't think is in place, and > > that I would like to point out: elogind, libelogind0, libpam-elogind have > > not been upgraded; indeed these packages are marked as 'upgradable'. How > > should I manage this situation? > > To help us work out why, what does `apt policy libsystemd0 libelogind0 elogind > libpam-elogind' produce? See below (calf-plugins also was not upgraded): ~~~ $ apt policy libsystemd0 libelogind0 elogind calf-plugins libsystemd0: Installato: 241-7~deb10u3 Candidato: 241-7~deb10u3 Tabella versione: 244.3-1~bpo10+1 100 100 http://deb.devuan.org/merged beowulf-backports/main amd64 Packages *** 241-7~deb10u3 500 500 http://deb.devuan.org/merged beowulf/main amd64 Packages 100 /var/lib/dpkg/status libelogind0: Installato: 234.4-2 Candidato: 241.4-2 Tabella versione: 241.4-2 500 500 http://deb.devuan.org/merged beowulf/main amd64 Packages *** 234.4-2 100 100 /var/lib/dpkg/status elogind: Installato: 234.4-2 Candidato: 241.4-2 Tabella versione: 241.4-2 500 500 http://deb.devuan.org/merged beowulf/main amd64 Packages *** 234.4-2 100 100 /var/lib/dpkg/status calf-plugins: Installato: 0.0.60-4+b1 Candidato: 0.90.1-2 Tabella versione: 0.90.1-2 500 500 http://deb.devuan.org/merged beowulf/main amd64 Packages *** 0.0.60-4+b1 100 100 /var/lib/dpkg/status ~~~ > Does `apt install libpam-elogind' fix it? Hum... that's what I have: ~~~ $ sudo apt-get install libpam-elogind Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: elogind libelogind0 I seguenti pacchetti saranno RIMOSSI: libsystemd0 I seguenti pacchetti saranno aggiornati: elogind libelogind0 libpam-elogind 3 aggiornati, 0 installati, 1 da rimuovere e 1 non aggiornati. ~~~ It sounds good... Should I apply? > > 3. Programs with a graphic display started complaining about the warning > > "Couldn't register with accessibility bus: ..." [3][4]. Putting 'export > > NO_AT_BRIDGE=1' in /etc/environment seems to have blocked the alerts. I > > don't know if it's a real solution or just a workaround that doesn't solve > > the underlying problem. > > They are harmless. But installing at-spi2-core ought to make them disappear. at-spi2-core was already installed... Thanks -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpiOrTs4lxcA.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
On 3/22/20 12:53 PM, al3xu5 / dotcommon wrote: > Hi all > > Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1]. > > Now I have: > ~~~ > $ uname -a > Linux computer0 4.6.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 4.6.4-1~bpo8+1 > (2016-08-11) x86_64 GNU/Linux You can do one of two things to get the beowulf kernel - either install linux-image-amd64, which is a metapackage that will always install the latest available kernel, or you can install the kernel by the full package name, currently linux-image-4.19.0-8-amd64. If you do the latter, stay alert to when -9 comes out. You won't get it automatically. > 2. Having upower installed, I have downgraded upower packages as suggested in > [1], to avoid problems like bug#394 [2] which seems mainly related to > cinnamon. > But I do not have cinnamon... So what I should do? Downgrade or not? If not, > how to disable downgrading of those packages? > Take the downgrade. It's not really a downgrade; it's an upgrade to a lower-numbered version. (We no longer need to fork upower.) That's all I've got. Hope it helps. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ASCII 2.1 to Beowulf: Report + questions
On Sun, Mar 22, 2020 at 05:53:17PM +0100, al3xu5 / dotcommon wrote: > Hi all > > Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1]. > > Overall, the upgrade appears to have gone well; the process has completed and > the system is fully functional. But there are some details (maybe minor > issues) > I would like to report, also with some questions. > > Now I have: > ~~~ > $ uname -a > Linux computer0 4.6.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 4.6.4-1~bpo8+1 > (2016-08-11) x86_64 GNU/Linux > > $ lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description: Devuan GNU/Linux 3 (beowulf) > Release: 3 > Codename: beowulf > ~~~ > > 1- There is one aspect of the upgrade that I don't think is in place, and that > I would like to point out: elogind, libelogind0, libpam-elogind have not been > upgraded; indeed these packages are marked as 'upgradable'. How should I > manage > this situation? To help us work out why, what does `apt policy libsystemd0 libelogind0 elogind libpam-elogind' produce? Does `apt install libpam-elogind' fix it? > 2. Having upower installed, I have downgraded upower packages as suggested in > [1], to avoid problems like bug#394 [2] which seems mainly related to > cinnamon. > But I do not have cinnamon... So what I should do? Downgrade or not? If not, > how to disable downgrading of those packages? It applies to upower in general. #394 is just an example. If you don't want the new packages, do nothing and apt will not install them. > 3. Programs with a graphic display started complaining about the warning > "Couldn't register with accessibility bus: ..." [3][4]. Putting 'export > NO_AT_BRIDGE=1' in /etc/environment seems to have blocked the alerts. I don't > know if it's a real solution or just a workaround that doesn't solve the > underlying problem. They are harmless. But installing at-spi2-core ought to make them disappear. I will leave teh MATE and theme questions to others with more expertise! Mark ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ASCII 2.1 to Beowulf: Report + questions
Hi all Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1]. Overall, the upgrade appears to have gone well; the process has completed and the system is fully functional. But there are some details (maybe minor issues) I would like to report, also with some questions. Now I have: ~~~ $ uname -a Linux computer0 4.6.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 4.6.4-1~bpo8+1 (2016-08-11) x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Devuan GNU/Linux 3 (beowulf) Release:3 Codename: beowulf ~~~ 1- There is one aspect of the upgrade that I don't think is in place, and that I would like to point out: elogind, libelogind0, libpam-elogind have not been upgraded; indeed these packages are marked as 'upgradable'. How should I manage this situation? 2. Having upower installed, I have downgraded upower packages as suggested in [1], to avoid problems like bug#394 [2] which seems mainly related to cinnamon. But I do not have cinnamon... So what I should do? Downgrade or not? If not, how to disable downgrading of those packages? 3. Programs with a graphic display started complaining about the warning "Couldn't register with accessibility bus: ..." [3][4]. Putting 'export NO_AT_BRIDGE=1' in /etc/environment seems to have blocked the alerts. I don't know if it's a real solution or just a workaround that doesn't solve the underlying problem. 4. After the upgrade, gtk has lost the font configuration, meaning that gtk applications had a generic sans font with an almost illegible minimum size. I suppose it's due to a change in the gtk theme. I solved it by manually setting font and size using Gtk-ChTheme. 5. Some MATE problems: 5.1. MATE shows a very *huge* amount of errors in .xsession-errors 5.2. The trash icon don't work as expected anymore: if the trash can contains data then the full-trash icon and its label are displayed; when empty, there isn't any trash icon bau the label is still in place. I suppose this is a problem with the theme and/or the svg icon being used (but I cannot figure out which one is among the many svg trash icons in /usr/share/icons ...) 5.3. MATE (1.20.4) has changed its default typeface which now is the *ugly* Cantarell, as used in Gnome 3 [5]. Since I don't really like Cantarell, I had to manually revert default MATE fonts to DejaVu... Please let me know your suggestions. Regards -- [1] https://beta.devuan.org/os/documentation/dev1fanboy/en/upgrade-to-beowulf [2] https://bugs.devuan.org/cgi/bugreport.cgi?bug=394 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1056820 [4] https://unix.stackexchange.com/questions/532585/getting-dbind-warnings-about-registering-with-the-accessibility-bus [5] https://en.wikipedia.org/wiki/Cantarell_(typeface) -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key ID: 4096 bit RSA key F94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgpHQ0_PrYhUv.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng