Bug#1050967: RFS: mesa/23.1.6-1~bpo12+1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the package "mesa":  * Package name : mesa    Version  : 23.1.6    Upstream contact : debia...@lists.debian.org, uploader ab...@debian.org  * URL  : https://mesa3d.org/  * License 

Bug#1005222: gedit: Open dialog defaults to HOME instead of current file's directory

Package: gedit Version: 3.38.1-1 This issue has been fixed upstream in 3.38.2 (cf https://gitlab.gnome.org/GNOME/gedit/-/issues/382). Can Gnome team consider updating gedit to 3.38.2 ? Best regards, Jérémy VIES

Bug#963980: issue confirmed on newly installed Debian 11.2

I can confirm I have the same issue using a brandly new installed machine with the nvidia driver. primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to locate/open config directory: "/etc/bumblebee/xorg.conf.d"

Bug#987584: docker.io: docker-proxy does not bind to ipv6 "all network" address

Package: docker.io Version: 20.10.5+dfsg1-1+b1 Severity: important Tags: ipv6 Dear Maintainer, * What led up to the situation? I'm trying to expose some web app to the ipv6 Internet ! * What exactly did you do (or not do) that was effective (or ineffective)? I enabled ipv6 support in

Bug#932501: problem still present in 0.8.15

Hi, Just to confirm the issue is still present in bullseye current release. I had to add the following lines to apparmor configuration to make it work. /etc/squid-deb-proxy/** r, /var/log/squid-deb-proxy/* rw, /run/squid-deb-proxy.pid rwk, /var/cache/squid-deb-proxy/** rw, Best regards

Bug#970885: adriconf : first trial of packaging

Hi Rogério and all, I've done a trial to package the tool adriconf. It works, but it misses several things: * the .desktop file from the flatpak directory should be copied. But I am very new debian packaging and I don't know how to override some rule to do that. * no manpage * the tests are

Bug#942229: Issue confirmed on Buster i386

regards, Jérémy Le sam. 26 oct. 2019 à 19:41, Sylvestre Ledru a écrit : > Hello > > I just experienced it too and the cmake logs are useless. > > Have you been able to find a fix for that? It is pretty confusing :/ > > Thanks > > Sylvestre > > > Le 17/10/2019 à 19

Bug#942229: Issue confirmed on Buster i386

Hello, I'm following this bug as I try to do the same backport. I can confirm the issue in a simple docker configuration, based on i386/debian:buster with only the declared deps of llvm-toolchain installed. Best regards, Jérémy

Bug#928146: reported on freedesktop too

Hi all, it seems the issue is already reported and fixed in upstream repo: https://bugs.freedesktop.org/show_bug.cgi?id=110509

Bug#925084: di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured

! by curiosity, why does it work using mount/bind and not with a simple symbolic link ? regards, Le ven. 22 mars 2019 à 18:48, Andreas B. Mundt a écrit : > Control: tags + unreproducible moreinfo > > > Hi Jérémy, > > On Tue, Mar 19, 2019 at 07:43:47PM +0100, Jérémy Viès wrot

Bug#925084: di-netboot-assistant: debian-installer-xxx-netboot-yyy are wrongly configured

Package: di-netboot-assistant Version: 0.60~bpo9+1 Severity: normal Tags: d-i Dear Maintainer, I've just discovered and then set-up di-netboot-assistant to manage several debian netboot versions. It works great when it manages setup di-netboot-assistant installed by itself, but it fails to

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

:24 +0100 Simon McVittie <s...@debian.org> wrote: > On Wed, 04 Apr 2018 at 21:06:01 +0200, Jérémy Viès wrote: > > The fixes for gnome-3-22 has also been posted on gnome git repository. > > Can you backport the fix to gvfs 1.30, used by gnome 3.22 that are on stretch ? >

Bug#882213: gvfs-fuse: MTP device still visible after disconnecting

The fixes for gnome-3-22 has also been posted on gnome git repository. Can you backport the fix to gvfs 1.30, used by gnome 3.22 that are on stretch ? https://github.com/GNOME/gvfs/commits/gnome-3-22 Thx a lot, Jérémy On Tue, 3 Apr 2018 12:03:36 +0100 Simon McVittie wrote: >

Bug#784003: workaround

I confirm the bug on Jessie. I just commented both lines with has_separator property, and it seems ok. -- Theory is where you know everything, but nothing works; practice is where everything works, but nobody knows why. Here we combine theory with practice; nothing works and nobody knows why !

Bug#750821: sweethome3d crashes when selecting "Preferences"

Hi Gabriele, I can confirm that appending this "-Dcom.eteks.sweethome3d.j3d.checkOffScreenSupport=false" args to the JAVA_ARGS fixes the issue. I'm also running the default jessie JRE, on a system running the radeon OSS driver. Regards, Jérémy PS: my opengl driver follows: OpenGL vendor

Bug#747130: owncloud 'Depends' on php-irods-prods while it is noted 'Recommends'

Package: owncloud Version: 6.0.2+dfsg-1~bpo70+1 After the installation of owncloud on Debian Wheezy, it was configured correctly, but was never able to start. lighttpd error logs show: 2014-05-05 09:10:41: (mod_fastcgi.c.2676) FastCGI-stderr: PHP Fatal error: require_once(): Failed opening

Bug#747130: owncloud 'Depends' on php-irods-prods while it is noted 'Recommends'

application in the README.Debian would take too much time... ok thank you for your reactiveness ! 2014-05-05 22:42 GMT+02:00 David Prévot taf...@debian.org: Hi Jérémy, On Mon, May 05, 2014 at 10:15:32PM +0200, Jérémy Viès wrote: Package: owncloud Version: 6.0.2+dfsg-1~bpo70+1 “Please

Bug#633972: cron.daily/standard fails on mount point with a space in path.

here is the run of the patched standard : + cd / + LOCKFILE=/var/lock/cron.daily + LOFO=lost+found ++ which flock + exec + flock -x -n 9 + '[' -f /etc/default/cron ']' + . /etc/default/cron ++ READ_ENV=yes + '[' '' = no ']' + read DEV MTPT FSTYPE OPTS REST + case $DEV in + case $FSTYPE in + '[' /

Bug#633972: cron.daily/standard fails on mount point with a space in path.

here is the report I receive by email: /etc/cron.daily/logrotate: error: error running non-shared postrotate script for /var/log/mediatomb.log of '/var/log/mediatomb.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1 /etc/cron.daily/standard: Some local file systems lack a

Bug#633972: cron.daily/standard fails on mount point with a space in path.

Package: cron Version: 3.0pl1-118 Severity: normal Tags: wheezy -- Package-specific info: --- EDITOR: not set --- usr/bin/editor: /bin/nano --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 33984 Jun 5 11:27 /usr/bin/crontab --- /var/spool/cron drwxr-xr-x 3 root root 4096 Jun 25 22:49