-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My bugreporting GPG-key has changed, this is the new one:
> andrew@a68n:~$ gpg --list-keys 077333E924280AFF
> pub dsa2048 2022-06-15 [SC] [expires: 2023-06-15]
> CD1A706C34652C2D43F55933077333E924280AFF
> uid [ulti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
there is the follow-up report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006442
-BEGIN PGP SIGNATURE-
iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCYhzblgAKCRDn6sEfJS3n
C9CQAJ91gxj3o33yl4/XpLLB7Fsx0TNUTwCfRpyG/qUu3n1D7W2OEee6fs+IsOw=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andrew@a68n:~$ cd projects/
andrew@a68n:~/projects$ wget
https://attachment.irregulaire.info/mini-NAS-etc.txz --2022-02-26 08:35:50--
https://attachment.irregulaire.info/mini-NAS-etc.txz Resolving
attachment.irregulaire.info (attachment.irregulaire.inf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.71
Severity: minor
Dear Maintainer,
* system-upgrade to Buster 10.11 failed as reported
here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006369
* I did try out grub-rescue, but as far as I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 14 Oct 2021 13:15:03 +
"Debian Bug Tracking System" wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the upgrade-reports package:
>
> #996205: System upgrade to bulls-eye
>
> It has been clo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
root@eb8440p:~# cat /etc/apt/sources.list
#
# deb cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64 xfce-CD
Binary-1 20190706-10:24]/ buster main
#deb cdrom:[Debian GNU/Linux 10.0.0 _Buster_ - Official amd64 xfce-CD
Binary-1 20190706-10:24]/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The situation is now that x2goserver seems to work for me reliably,
including re-connecting to running sessions, but mostly only, when x2go-client
is invoked from the terminal (as shown here):
> andrew@a68n:~$ x2goclient
> x2go-INFO-1> "Starting X
.
> Installing new version of config file /etc/x2go/keystrokes.cfg ...
> Setting up x2goserver (4.1.0.3-5) ...
> Created
> symlink /etc/systemd/system/multi-user.target.wants/x2goserver.service
> → /lib/systemd/system/x2goserver.service. Setting up x2goserver-extensions
> (4.1.0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> root@bulls-eye:/home/andrew# ls -alt /var/lib/dpkg/info | grep "May 13"
> -rw-r--r-- 1 root root 417 May 13 16:27 libmail-sendmail-perl.list
> -rw-r--r-- 1 root root 581 May 13 16:27 libsys-hostname-long-perl.list
> -rw-r--r-- 1 root root
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is the missing part for Debian-11 bulls-eye:
> andrew@bulls-eye:~/HandBrake$ ate show libayatana-appindicator-dev
> Package: libayatana-appindicator-dev
> Version: 0.5.5-2
> State: installed
> Automatically installed: no
> Priority: optiona
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This happened only recently, last updates were installed on Apr 27:
> root@bulls-eye:~# ls -alt /var/lib/dpkg/info | grep "Apr 27"
> drwxr-xr-x 1 root root 276 Apr 27 18:00 ..
> drwxr-xr-x 1 root root 497630 Apr 27 17:58 .
> -rw-r--r-- 1 root r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: src:linux
Version: 5.10.24-1
Severity: normal
X-Debbugs-Cc: b...@irregulaire.info
Dear Maintainer,
The issue was already reported as bug #953305, and correctly marked as done,
because it mainly referred to to the stable version of linux-ima
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 28 Mar 2021 11:55:31 +0200
Christian Marillat wrote:
> Hi,
>
> I read this bug (984967) and as I don't like bug in my package i sent
> this e-mail.
>
> I don't use x2go and would like to know what is exactly wrong with
> handbrake.
>
> Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ssh andrew@bulls-eye
> Linux bulls-eye 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are descr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, folks, I know, I don't have to go into every detail and teach you about
usage of deb-multimedia repository, but anyway this is what I did:
> Linux bulls-eye 5.10.0-4-amd64 #1 SMP Debian 5.10.19-1 (2021-03-02) x86_64
>
> The programs includ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The instructions are here:
https://wiki.x2go.org/doku.php/wiki:repositories:debian
this seemingly is the viable sulution for me (
>
> # X2Go Repository (Saimaa ESR builds)
> #deb http://packages.x2go.org/debian buster extras saimaa
> # X2Go Repos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Some extensive meditation about this issue and leave alone continued use, the
resulting explanation is this:
* this behaviour is absolutely good enough for testing software-quality
* most people do not have so fast computers anyway, that they would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fine, guys, I upgraded now and reinstalled x2goserver Debain package, and the
result is, that-x2go server still is slightly unreliable, and user 'andrew'
can rather not log in:
> root@bulls-eye:~# aptitude upgrade
> The following packages will be upg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I did check out the upstream packages of x2goserver, because of this bug
in handbrake (clearly not a feature in my view, but significantly worsened
functionality in an important detail):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984967
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to my excellent qualities as IT worker of course I am keeping on
testing, and the result of this is, that handbrake currently continues to
work through the jobs-queue while you keep the x2go window open, and in this
respect the behaviour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: handbrake
Version: 1.3.1+ds1-2+b3
Severity: normal
X-Debbugs-Cc: b...@irregualire.info
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have re-checked the situation, and the problem is no longer reproducible,
it is now possible to log in three times in a row:
> andrew@a68n:~$ x2goclient
> x2go-INFO-1> "Starting X2Go Client 4.1.2.1..."
> x2go-WARNING-1> English language requested
rite directly to the maintainers already:
> Begin forwarded message:
>
> Date: Sun, 7 Mar 2021 16:15:47 +0100
> From: andrew glaeser
> To: debian-rem...@lists.debian.org
> Subject: andrew@bulls-eye:~$ ate show x2goserver
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: lxqt
Version: 30
Severity: minor
Dear Maintainer,
Kindly view Your Letter:
I've liked lxqt desktop, and even preferred it over XFCE, until I stumbled
over the network-configuration several times: first it happened with the
testing-branch of
is the BTS good for
anyway?
Begin forwarded message:
Date: Sun, 28 Jun 2020 08:55:02 +0200
From: andrew glaeser
To: debian-backpo...@lists.debian.org
Subject: Fw: Bug#953305: Acknowledgement (linux-image-4.19.0-8-amd64:
sleep/suspend/hibernate/RESUME no longer workable)
Hello there,
the slee
Package: installation-reports
Version: 2.74
Severity: minor
Dear Maintainer,
Testing branch is generally not for productive use, so I should probably say,
this is level 4, wishlist only, but my impression is that some of the
disadvantages were chronified already, and you probably should not let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.71
Severity: wishlist
Dear Maintainer,
this is wishlist only, a shiny success-story for your pleasure only, if you
want.
- -- Package-specific info:
Boot method: USB
Image version:
https://cdimage.debian.or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am no longer trying to configure backported kernel-sources now, but in
fact my build-pc has the stable (buster) distribution software-set now, there
seems to be some problem about SSL, and I cannot see which option to disable
in the crypto-section o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While my upgraded system seems OK now, I can also log in as before wit x2go
and see the same xfce-desktop, and I can install packages.
But, big but, the stable Hugin-source PPA does not seem OK to me:
So, any other proposals?
Do I have to use subve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Seems I have to upgrade to stable,
since I am failing to set up the build-dependencies on stretch-oldstable.
10.1 release comes very soon:
> From: "Adam D. Barratt"
> To: debian-rele...@lists.debian.org
> Subject: Upcoming stable point release (1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I've got the idea, that fuzzing around with virtual machines is a
suboptimal solution here and clearly too awkward, because a detailed
step-by-step tutorial exists for building Hugin from source (and FBSD wasn't a
desktop-OS in the first place eit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 05 Jun 2019 15:30:13 -0300
David Bremner wrote:
> andrew glaeser writes:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> >> andrew@a68n:~$ ssh root@detst
> >> Linux detst 4.19.0-5
(2.58.3-2) ... Setting up libegl-mesa0:amd64
> (18.3.6-2) ... Setting up gvfs-libs:amd64 (1.38.1-4) ... Setting up
> libglx-mesa0:amd64 (18.3.6-2) ... Setting up gvfs-daemons (1.38.1-4) ...
> Setting up gvfs:amd64 (1.38.1-4) ... Processing triggers for man-db
> (2.8.5-2) ... Processing trigger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ssh root@detst
> Linux detst 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ssh root@detst
> Linux detst 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon fighting off bad bullshit tellers, the way to success is probably free.
Really, seriously, what should even stop me now, I am going to give Hugin
another try, but although it might be well workable again, I will keep this
open until Buster rel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ssh root@detst
> Linux detst 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in th
from the "View"
> menu. Clicking the small pin icon in the header of the docked
> Overview area (or dragging the Overview title bar) will switch to a
> floating window instead. To put that floating window back in a docked
> position, just drag it in either the top, bottom, left o
OK, I guess it could be a fundamental issue in libc, but did not try out
for any changes about Hugin yet:
> andrew@a68n:~$ ssh root@detst
> Linux detst 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the
until the Buster release is going to take place.
> From: andrew glaeser
> To: panotool...@yahoogroups.com
> Subject: Fw: Package: hugin, Package: hugin
> Date: Tue, 23 Apr 2019 13:04:02 +0200
> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
>
> -BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see attachments, not workable either
I retried the Server-Kernel build, which probably has more priority than the
desktop- one, because the default (non) kernel is a desktop-kernel, config
mad by 'make gconfig'.
-BEGIN PGP SIGNATURE-
iF0EAR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
-BEGIN PGP SIGNATURE-
iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCXEsL9wAKCRDn6sEfJS3n
C2yVAKC3gSKX4TsbxLFHoh58CGLVKRoc2QCgg99RU9lPpjpxT3IlNkDyq5hb2j8=
=OJMt
-END PGP SIGNATURE-
build-linul-asrv-bpo-2.txt.xz
Description: applicat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was confirmed as a configuration issue:
> andrew@a68n:~$ ssh user@detst
> ssh: connect to host detst port 22: Connection refused
> andrew@a68n:~$ ssh root@detst
> ssh: connect to host detst port 22: Connection refused
> andrew@a68n:~$ ssh user@d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now something else seems to be going wrong, as this is turning into an
enormous success-story, namely about the debian-desktop, see
attachment.[detst-desktop-e17.txt.xz]
But how was it possible to fit everything into a 5GB filesystem-root??
Thanks to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 20 Dec 2018 11:29:28 +
Steve McIntyre wrote:
> Hi Andrew,
>
> On Thu, Dec 20, 2018 at 11:23:55AM +0100, andrew glaeser wrote:
> >>
> >> root@detst:/home/user# init 0
> >> bash: init: command
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> root@detst:/home/user# tasksel
> tasksel: apt-get failed (100)
> root@detst:/home/user# ping www.debian.org
> PING www.debian.org (5.153.231.4) 56(84) bytes of data.
> 64 bytes from senfter.debian.org (5.153.231.4): icmp_seq=1 ttl=47 time=40.8
> ms
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> root@detst:/home/user# init 0
> bash: init: command not found
> root@detst:/home/user# shutdown -h now
> bash: shutdown: command not found
> root@detst:/home/user# ls
> reportbug-installation-report-20181219-847-hn9d0g_o
> root@detst:/home/user# apti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.69
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effecti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-source-4.18
Version: 4.18.6-1~bpo9+1
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> andrew@a68n:~$ ate versions youtube-dl
> p 2017.05.18.1-1
> stable 500 i
> 2018.06.18-1.1
> 100 p 2018.09.10-1
> testing 52 andrew@a68n:~$ sat install -t testing
> youtube-dl [sudo] password for andrew:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: youtube-dl
Version: 2018.06.18-1.1
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effectiv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780219
-BEGIN PGP SIGNATURE-
iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCWz3jyAAKCRDn6sEfJS3n
CygxAKCTlNzi9acmUT5IJ8QahThefXKFUACgmn3AlPzun/Iq7S5LBxxEwCkw8nE=
=EwB1
-END PGP SI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The problem appears like this:
> [2.672381] xhci_hcd :02:00.0: Refused to change power state,
> currently in D3 [2.672452] xhci_hcd :02:00.0: xHCI Host Controller
> [2.672460] xhci_hcd :02:00.0: new USB bus registered, assigne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
WD is guilty of making and selling no-linux harddisks, but no-linux
USB-sticks also exist, in a way it is understandable, because the idea of
the manufacturer was not in the first place to give the cheapest possible SSD
to linux-users for their PCs, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: installation-reports
Version: 2.68
Severity: minor
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effecti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On debian 9.4 the issue appears as follows:
>
> root@debian94x:/home/user# aptitude install apache2 libapache2-mod-fcgid
> The following NEW packages will be installed:
> apache2 apache2-bin{a} apache2-data{a} apache2-utils{a}
> libapache2-mod-fcg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hugin
Version: 2018.0.0+dfsg-1+b1
Severity: important
Dear Maintainer,
the problem exists since the the stretch-release, in fact the tendency to
defectiveness of the GUI showed already with Jessie+backports, it wasn't
possible to stitch the p
57 matches
Mail list logo
