Bug#1060242: Debian bluez_5.71.orig.tar.xz is different to upstream bluez-5.71.tar.xz

2024-01-07 Thread Daniel van Vugt

Package: bluez
Version: 5.71-1

Debian's bluez_5.71.orig.tar.xz seems to have different contents from the 
upstream release bluez-5.71.tar.xz


http://deb.debian.org/debian/pool/main/b/bluez/bluez_5.71.orig.tar.xz
https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.71.tar.xz

I'm guessing Debian has snapshotted the git tag instead? Admittedly you *should* 
be able to do that IMHO, it's just a feature of the BlueZ project that they 
release significantly cleansed tarballs that are different to the tag they came 
from. Still, I suggest Debian should be using the official upstream release 
tarballs in future.




Bug#993171: mutter: Is it time to stop patching synaptics support back in?

2021-08-29 Thread Daniel van Vugt
Libinput is enough for most people, although it does have some touchpad 
sloppiness on some laptops that I only know how to fix with Synaptics. I don't 
know if people are actually making use of it though...


It might be a better idea to drop the Synaptics patch and we can propose patches 
to Libinput instead.



On 28/8/21 6:43 pm, Simon McVittie wrote:

Source: mutter
Version: 40.2.1-1
Severity: normal
X-Debbugs-Cc:  daniel.van.v...@canonical.com

We are currently patching both mutter and gnome-control-center to reinstate
synaptics support, a change that was specifically rejected by upstream in
.

This seems to have been intended to be a temporary thing for Ubuntu 18.04.
Since then, we've had two stable releases of Debian and two LTS releases
of Ubuntu, and GNOME in Debian has switched to Wayland by default; so
it seems like it might be worth revisiting that decision. Do we still
need the synaptics X11 driver, or is libinput now enough?

 smcv





Bug#980726: (no subject)

2021-01-20 Thread Daniel van Vugt

Seems all it needs is:

  sudo systemctl enable gpm

Does that need to be added to the packaging?



Bug#980726: gpm.service does not automatically start

2021-01-20 Thread Daniel van Vugt

Package: gpm
Version: 1.20.7-7

The gpm service does not automatically start on boot.

$ systemctl status gpm
● gpm.service - Console Mouse manager
 Loaded: loaded (/lib/systemd/system/gpm.service; disabled; vendor preset: 
enabled)

 Active: inactive (dead)
   Docs: man:gpm(8)
 man:gpm.conf(5)
 man:gpm-types(7)

I also don't get any crash reports. But starting it manually works every time:

$ sudo systemctl start gpm

https://bugs.launchpad.net/bugs/1912575



Bug#783398: new upstream

2018-12-03 Thread Daniel van Vugt
3.5 years later... it would still be helpful to get in a new upstream 
release:


https://github.com/openSUSE/gfxboot/releases

because apparently version 4.5.22 fixes startup failures on Chromebooks:

https://launchpad.net/bugs/1530530



Bug#892714: libinput10: Crashes Gnome session

2018-03-12 Thread Daniel van Vugt

Found:
https://bugs.freedesktop.org/show_bug.cgi?id=105258

(fixed a few hours ago upstream)



Bug#887417: ags-integration-test fails with "dpkg-buildpackage: error: fakeroot not found, either install the fakeroot"

2018-01-15 Thread Daniel van Vugt

Package: gsequencer
Version: 1.1.4-1

Builds of gsequencer are failing on some machines because 
ags-integration-test calls fakeroot without having a build dependency on 
fakeroot:


dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root

See also:
https://bugs.launchpad.net/ubuntu/+source/gsequencer/+bug/1743511
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/g/gsequencer/20180116_055835_6652f@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/g/gsequencer/20180116_033415_6652f@/log.gz



Bug#863754: Incorrect package description (and name) of gst-libav1.0 / gstreamer1.0-libav: It's ffmpeg, not libav

2017-05-30 Thread Daniel van Vugt

Package: gstreamer1.0-libav
Version: 1.12.0-1

Incorrect package description (and name) of gst-libav1.0 / 
gstreamer1.0-libav: Refers to libav even though Ubuntu/Debian uses 
FFmpeg instead of libav:



Package: gstreamer1.0-libav
...
Description: libav plugin for GStreamer
...
 http://www.libav.org/
 http://gstreamer.freedesktop.org/
 http://gstreamer.freedesktop.org/modules/gst-libav.html


They are distinct projects:
http://libav.org/ <-- Was used in the past
https://ffmpeg.org/ <-- Now used by Ubuntu and Debian

More history:
https://en.wikipedia.org/wiki/Libav#History

The incorrect wording appears to be directly inherited from upstream:
https://packages.debian.org/experimental/gstreamer1.0-libav

So the package description and names in Ubuntu and in Debian appear to 
be wrong. They should replace 'libav' with 'ffmpeg' (although 
confusingly both provide 'libav*' libraries).


Short term I think it makes sense to just fix up the Description text. 
Longer term if libav dies off in favor of ffmpeg and/or no one intends 
to ever switch back to libav from ffmpeg again then the package and 
projects should rename to s/libav/ffmpeg/g.


Downstream bug report: http://bugs.launchpad.net/bugs/1694409



Bug#639099: geeqie fullscreen doesn't use the full screen

2011-08-23 Thread Daniel van Vugt
Package: geeqie
Version: 1:1.0-8

The bug is already reported upstream and in Ubuntu:
http://sourceforge.net/support/tracker.php?aid=2925034
https://launchpad.net/bugs/788321

I have submitted a fix in Ubuntu and upstream, but don't hold much hope
of upstream doing anything about it as the project seems rather idle.

Please consider this patch for Debian:
http://bazaar.launchpad.net/~vanvugt/ubuntu/oneiric/geeqie/fix-788321/view/head:/debian/patches/fix-fullscreen.patch



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#534504: Fix for upstart/Ubuntu systems

2011-04-19 Thread Daniel van Vugt

https://bugs.launchpad.net/ubuntu/+source/mediatomb/+bug/212441/comments/19

Here's a patch for this bug I've been using on Ubuntu. Note that it uses 
upstart, so probably won't solve the problem for pure Debian.


Still, it would be nice if we could push this patch or something like it 
into the Debian source rather than relying on downstream Ubuntu patching.


- Daniel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org