Re: [DNG] Beowulf Beta is here!
Hi tempforever, On 26/3/20 2:57, tempforever wrote: Thanks a lot. Your message is going to be top of my list for a couple years :-) Not at all. I like to be at the very top. Cheers, topforever. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Wed, 25 Mar 2020 10:06:57 + - Mark Hindley : > I can conform that slim seems to do the right thing at the AT_SPI_BUS is set > and available. > > On Wed, Mar 25, 2020 at 08:06:22AM +, Daniel Abrecht via Dng wrote: > > Hi > > > > I've had that problem as well. [...] > > > > To me, it seams to be caused by a combination of something `lightdm` does, > > and something `at-spi-bus-launcher` does not do. > > After a login with `lightdm`, the X11 root window has the `AT_SPI_BUS` > > property set (`xprop -root AT_SPI_BUS`), however, it seams the > > `at-spi-bus-launcher`/`at-spi2-registryd` instance which created that > > property does not exist anymore, causing applications to fail to connect to > > it. In addition to this, the presence of that property prevents a new > > instance of `at-spi-bus-launcher` from starting. I had the same issue too after dist-upgrade from ASCII to Beowulf. > > My current workaround is to remove the `AT_SPI_BUS` property, and then start > > `at-spi-bus-launcher` again: > > ``` > > xprop -root -remove AT_SPI_BUS > > /usr/lib/at-spi2-core/at-spi-bus-launcher & I have added: ~~~ export NO_AT_BRIDGE=1 ~~~ in `/etc/environment` and also I have installed `at-spi2-core`. This seems to have blocked the alerts, but I don't know if it's a real solution or just a workaround that doesn't solve the underlying problem. > Daniel, I get the same results as you with lightdm and your workaround is good > too. Although I don't have to restart the at-spi-bus-launcher process > manually, it is started automatically once a process tries to use it. > The issue seems to be that lightdm starts its own AT_SPI_BUS which is then > killed on login. But the AT_SPI_BUS property isn't removed so that it can be > relaunched in the user's session. This is depsite Debian #760740 being marked > as fixed. Also I am using lightdm (+ MATE). > That bug also suggests another workaround of setting 'xserver-share=false' in > /etc/lightdm/lightdm.conf which also seems to work. Maybe I'm wrong, but it seems to me that it is similar to the `export NO_AT_BRIDGE=1` workaround. If so the 'xserver-share=false' setting in the lightdm configuration seems to me to be more appropriate. 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 pgpidHzgyeK_Z.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Website issues about beowulf.
On 2020-03-26 11:22, Hendrik Boom wrote: On Sun, Mar 22, 2020 at 08:35:42PM +0900, Olaf Meeuwissen via Dng wrote: Hi, Olaf Meeuwissen via Dng writes: > Hi, > > goli...@devuan.org writes: > >> Dear dev1ers, >> >> The Devuan 3 Beowulf Beta release is now ready for review. The >> installer isos, desktop-live and minimal-live isos can be downloaded >> from: >> >> https://files.devuan.org/devuan_beowulf/ https://files.devuan.org/devuan_beowulf/ contains the files I expected, but following the release announcement link at the bottom leads to information about an ascii point release. The the release notes say: Direct and easy upgrade path from Devuan ASCII and migration path from Debian Buster to Devuan 3 Beowulf are available here: https://devuan.org/os/install There's a lot of infirrmation there about beowulf, but I find no instructions for migrating from Debian Buster to Devuan 3 Beowulf. -- hendrik hendrik . . . I know this is confusing. There is now an announcement at the top of devuan.org for Beowulf testers to use beta.devuan.org for relevant documentation. Since Beowulf is still in TESTING there has not been an official announcement of its release. ASCII 2.1 is our current STABLE release. Once again . . . ALL BEOWULF TESTERS SHOULD BE REFERENCING BETA.DEVUAN.ORG FOR DOCUMENTATION!! If there was ever a time to shout, that would be it. :D golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Website issues about beowulf.
On Sun, Mar 22, 2020 at 08:35:42PM +0900, Olaf Meeuwissen via Dng wrote: > Hi, > > Olaf Meeuwissen via Dng writes: > > > Hi, > > > > goli...@devuan.org writes: > > > >> Dear dev1ers, > >> > >> The Devuan 3 Beowulf Beta release is now ready for review. The > >> installer isos, desktop-live and minimal-live isos can be downloaded > >> from: > >> > >> https://files.devuan.org/devuan_beowulf/ https://files.devuan.org/devuan_beowulf/ contains the files I expected, but following the release announcement link at the bottom leads to information about an ascii point release. The the release notes say: Direct and easy upgrade path from Devuan ASCII and migration path from Debian Buster to Devuan 3 Beowulf are available here: https://devuan.org/os/install There's a lot of infirrmation there about beowulf, but I find no instructions for migrating from Debian Buster to Devuan 3 Beowulf. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: ceres policykit
On 3/26/20 4:39 PM, Mark Hindley wrote: > It is fine. If you look in the changelog you will see it documented. The > backend > libraries have been removed in 0.105-26. thanks for the info.. p.s. need to fix key encryption, suddenly tb-enigmail is encrypting all outgoing... signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ...
binPeJJdWKpxu.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Fwd: ceres policykit
On Thu, Mar 26, 2020 at 04:35:57PM +0200, Dimitris via Dng wrote: > is this safe to proceed and remove? > should i wait for newer versions of these "obsolete" packages into ceres? It is fine. If you look in the changelog you will see it documented. The backend libraries have been removed in 0.105-26. Mark ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Fwd: ceres policykit
once again, plain text.. Forwarded Message Subject: ... Date: Thu, 26 Mar 2020 16:34:26 +0200 From: Dimitris To: Dng hey @ll, for the past days i have an "issue" dist-upgrading in a ceres/amd64 machine: # apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: libpolkit-backend-1-0 libpolkit-backend-elogind-1-0 The following packages will be upgraded: libpolkit-gobject-elogind-1-0 # apt policy libpolkit-gobject-elogind-1-0 libpolkit-gobject-elogind-1-0: Installed: 0.105-25+devuan8 Candidate: 0.105-26+devuan1 Version table: 0.105-26+devuan1 500 500 https://$mirror/merged ceres/main amd64 Packages *** 0.105-25+devuan8 500 500 https://$mirror/merged testing/main amd64 Packages 100 /var/lib/dpkg/status # apt policy libpolkit-backend-1-0 libpolkit-backend-1-0: Installed: 0.105-25+devuan8 Candidate: 0.105-25+devuan8 Version table: *** 0.105-25+devuan8 500 500 https://$mirror/merged testing/main amd64 Packages 100 /var/lib/dpkg/status # apt policy libpolkit-backend-elogind-1-0 libpolkit-backend-elogind-1-0: Installed: 0.105-25+devuan8 Candidate: 0.105-25+devuan8 Version table: *** 0.105-25+devuan8 500 500 https://$mirror/merged testing/main amd64 Packages 100 /var/lib/dpkg/status is this safe to proceed and remove? should i wait for newer versions of these "obsolete" packages into ceres? thanks, signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ...
binU9IyGMOIyW.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] couldn't register with accessibility bus in Beowulf (workaround)
Anno domini 2020 Wed, 25 Mar 16:31:48 -0700 Gregory Nowak scripsit: > On Wed, Mar 25, 2020 at 08:18:12AM +0100, Dr. Nikolaus Klepp wrote: > > Stupid question: are you sure this is the showstopper? I have the same > > error message, but everything works as normal. > > I am very, very sure this is the show stopper. Are you using orca, or > looking at your monitor? Oh my, I read "ocra", not "orca", sorry ... > > On Wed, Mar 25, 2020 at 08:06:22AM +, Daniel Abrecht via Dng wrote: > > To me, it seams to be caused by a combination of something `lightdm` does, > > and something `at-spi-bus-launcher` does not do. > > After a login with `lightdm`, the X11 root window has the `AT_SPI_BUS` > > property set (`xprop -root AT_SPI_BUS`), however, it seams the > > `at-spi-bus-launcher`/`at-spi2-registryd` instance which created that > > property does not exist anymore, causing applications to fail to connect to > > it. In addition to this, the presence of that property prevents a new > > instance of `at-spi-bus-launcher` > > from starting. > > Thanks, that explanation does make sense. > > On Wed, Mar 25, 2020 at 10:06:57AM +, Mark Hindley wrote: > > I can conform that slim seems to do the right thing at the AT_SPI_BUS is > > set and > > available. > > That makes sense, since slim doesn't have ATSPI support as far as I > know, where as lightdm does through lightdm-gtk-greeter. > > > That bug also suggests another workaround of setting 'xserver-share=false' > > in > > /etc/lightdm/lightdm.conf which also seems to work. > > OK, I'll explore that along with the other solution you mentioned. > > On Wed, Mar 25, 2020 at 10:51:18AM +, Mark Hindley wrote: > > There are also the most recent comments[1] in Debian bug #911362 which > > relates > > to Buster and lightdm. > > > > Does installing libatk-adaptor help? > > I'll report back on this too when I have access to the machine I did > the install on in a few hours. Thanks everyone. > > Greg > > -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
