Bug#996074: extension compatibility with GNOME Shell 41

2021-10-22 Thread Christian Lauinger
On Sun, 17 Oct 2021 12:54:28 +0100 Simon McVittie wrote: > Control: severity -1 serious > > On Sun, 10 Oct 2021 at 21:33:02 +0100, Simon McVittie wrote: > > The metadata.json for this extension doesn't declare compatibility with > > GNOME 41. I don't know whether the actual code will need changes

Bug#996050: extension compatibility with GNOME Shell 41

2021-10-19 Thread Christian Lauinger
On Sun, 17 Oct 2021 12:54:28 +0100 Simon McVittie wrote: > Control: severity -1 serious > > On Sun, 10 Oct 2021 at 21:33:02 +0100, Simon McVittie wrote: > > The metadata.json for this extension doesn't declare compatibility with > > GNOME 41. I don't know whether the actual code will need changes

Bug#993201: fixed in upstream pull request

2021-10-14 Thread Christian Lauinger
I fixed it and created a pull request upstream: https://gitlab.com/bertoldia/gnome-shell-trash-extension/-/merge_requests/23

Bug#837786: mutter: Issues repainting the display on mouse movement

2016-09-18 Thread Christian Lauinger
On Sun, 18 Sep 2016 15:24:42 +0200 Mourad De Clerck wrote: > Hello, > > another datapoint: I'm experiencing the same issue on an AMD Pitcairn > (7870) using radeonsi. > > -- M > > Hi ! Same here and but I use nvidia-driver (367.44-1). It worked with previous 3.20 version so I downgraded to a

Bug#816790: exim4-config: Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing

2016-03-05 Thread Christian Lauinger
Package: exim4-config Version: 4.86.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrade of exim4-config * What exactly did you do (or not do) that

Bug#705425: asterisk: segmentation fault on start after upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (wheezy amd64)

2013-04-19 Thread Christian Lauinger
Am Donnerstag, den 18.04.2013, 21:30 +0300 schrieb Tzafrir Cohen: > One test if you don't mind: merely rebuilding it vs. Asterisk -3 does > not fix the issue, right? > Right, it does not. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Troub

Bug#705425: asterisk: segmentation fault on start after upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (wheezy amd64)

2013-04-18 Thread Christian Lauinger
Thank you Christian ! I downloaded the with "apt-get source asterisk-chan-capi" from unstable, patched it with the "chan-capi-devstate-cachable.diff" and build it like you described it. It also asked for "dpkg-source --commit" before it was possible to build it. Now my box is up and running with 1

Bug#705425: asterisk: segmentation fault on start after upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (wheezy amd64)

2013-04-17 Thread Christian Lauinger
Am Mittwoch, den 17.04.2013, 10:33 +0200 schrieb Christian Staake: > On 2013-04-14 21:10, Christian Lauinger wrote: > > dpkg -l asterisk* > > ii asterisk 1:1.8.13.1~dfsg-3 > > amd64Open Source Private Branch Exchange (PBX) >

Bug#705425: asterisk: segmentation fault on start after upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (wheezy amd64)

2013-04-14 Thread Christian Lauinger
Package: asterisk Version: 1:1.8.13.1~dfsg-3 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, After upgrade from 1:1.8.13.1~dfsg-1 to 1:1.8.13.1~dfsg-3 (debian wheezy amd64) asterisk does not start any more. Start leads to segmentation fault. syslog Apr 14