Bug#920913: 2023 status for fakeroot under docker?
I've been using a docker container (either debian or alpine based) to build openwrt on my Arch system :) OpenWRT pulls and builds fakeroot to do stuff with, but both containers choke in some form. The debian based container launches 1 faked 100% process at a time, and takes forever to do things (but finishes eventually). A 'build' takes about 30 - 60 minutes. ``` buildbot@99419141cf36:/workdir$ cat /proc/sys/fs/file-max 9223372036854775807 buildbot@99419141cf36:/workdir$ cat /proc/sys/fs/nr_open 1073741816 buildbot@99419141cf36:/workdir$ ulimit unlimited buildbot@99419141cf36:/workdir$ ulimit -Hn 1073741816 buildbot@99419141cf36:/workdir$ ``` On alpine (the same numbers) faked also gets lauched, and also takes 100% CPU on a single core, but for some reason on alpine I see dozens of faked processes launched. Not sure how they related. Builds finish in 10 or so minutes, so at least that's not so bad. On my host, with systemd, I get far different numbers ``` % cat /proc/sys/fs/file-max 9223372036854775807 % cat /proc/sys/fs/nr_open 1073741816 % ulimit -Hn 524288 % ulimit unlimited ``` I'll find out if I can set ulimit during container creation/start to workaround the issue, but it's still quite annoying. The reason for the ping/follow up? There where some good suggestions in this thread earlier, as having to close 524288 file descriptors isn't as bad as a billion, its still quite a lot of wasted resources for nothing. Think of the tree's ;) Olliver
Bug#969002: Closed
Is actually an upstream issue, reported here: https://github.com/moby/moby/issues/41386 So we can close this.
Bug#969002: docker-manifest needs executable access to /etc/docker
Package: docker Version: 1.5-2 Severity: minor Dear Maintainer, When trying to execute docker manifest (on a custom registry) for example: `DOCKER_CLI_EXPERIMENTAL=enabled docker manifest inspect --verbose registry.gitlab.com/neroburner/manifest-test/amd64/ubuntu:bionic` (not my repo, pulled from a gitlab bug report ;) we get the following error: "open /etc/docker/certs.d/registry.gitlab.com: permission denied" Not sure why I am getting this error, as I can find very little information online. Doing a `sudo chroot +X /etc/docker` resolves this issues completly. Looking at other systems, gentoo, we get the same state, with the same fix working. Interestingly however, that on alpine, where the entire directory does not even exist (with my test running a docker container of alpine where I only did apk add and added a user) does not suffer from this problem. So at the least, giving directory traversal access means docker can at least work. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker depends on: ii wmdocker 1.5-2 docker recommends no packages. docker suggests no packages. -- no debconf information
Bug#901302: gnome-shell: Monitor orentation causes gnome-shell to crash
Package: gnome-shell Version: 3.28.2-1 Severity: normal Dear Maintainer, Upgrading from debian stretch to debian buster worked fine on my Macbook Pro 2015 without any monitors connected, e.g. just the built-in screen. Arriving at work, plugging in my monitors as I always do, (Monitor 1: built-in, a lower resolution due to HDP, Monitor2: above monitor 1, regulator orientation, monitor 3, left of monitor 2, portrait orientation) gnome-shell stops updating its screen (e.g. no mouse movement etc). Logging in as a test user, without any monitor configuration, everything is fine. Setting the rotation of Monitor 3 to landscape causes the same problem. Rebooting to my previous stretch kernel (4.9.0-3) still causes the problem. This kernel in combination with the previous gnome-shell on stretch (which may have been X rather then wayland) worked fine for weeks. Linux itself does not crash, nor shows any problem in dmesg when logging in via ssh. Below is the journal output from gnome-shell when this happens. jun 11 09:33:23 um-mbp-306 dbus-daemon[2010]: [session uid=1000 pid=2010] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar7' unit='evolution-calendar-factory.service' requested by ':1.18' (uid=1000 pid=2102 comm="/usr/lib/gnome-shell/gnome-shell-calendar-server ") jun 11 09:33:23 um-mbp-306 gnome-shell[2041]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation jun 11 09:33:24 um-mbp-306 gnome-shell[2041]: Failed to set CRTC mode 1920x1200: No space left on device jun 11 09:33:24 um-mbp-306 gnome-shell[2041]: Failed to flip: No space left on device jun 11 09:33:24 um-mbp-306 gnome-shell[2041]: Failed to set CRTC mode 1920x1200: No space left on device -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.28.0-2 ii evolution-data-server3.28.2-1+b1 ii gir1.2-accountsservice-1.0 0.6.45-1 ii gir1.2-atspi-2.0 2.28.0-3 ii gir1.2-freedesktop 1.56.1-1 ii gir1.2-gcr-3 3.28.0-1 ii gir1.2-gdesktopenums-3.0 3.28.0-1 ii gir1.2-gdm-1.0 3.28.2-2 ii gir1.2-geoclue-2.0 2.4.7-1 ii gir1.2-glib-2.0 1.56.1-1 ii gir1.2-gnomebluetooth-1.03.28.0-2 ii gir1.2-gnomedesktop-3.0 3.28.2-1 ii gir1.2-gtk-3.0 3.22.29-3 ii gir1.2-gweather-3.0 3.28.1-1 ii gir1.2-ibus-1.0 1.5.18-1 ii gir1.2-mutter-2 3.28.2-2 ii gir1.2-nm-1.01.10.8-1 ii gir1.2-nma-1.0 1.8.10-5 ii gir1.2-pango-1.0 1.42.0-1 ii gir1.2-polkit-1.00.105-20 ii gir1.2-rsvg-2.0 2.40.20-2 ii gir1.2-soup-2.4 2.62.1-1 ii gir1.2-upowerglib-1.00.99.7-2 ii gjs 1.52.3-2 ii gnome-backgrounds3.28.0-1 ii gnome-settings-daemon3.28.1-1 ii gnome-shell-common 3.28.2-1 ii gsettings-desktop-schemas3.28.0-1 ii libatk-bridge2.0-0 2.26.2-1 ii libatk1.0-0 2.28.1-1 ii libc62.27-3 ii libcairo21.15.10-3 ii libcanberra-gtk3-0 0.30-6 ii libcanberra0 0.30-6 ii libcroco30.6.12-2 ii libecal-1.2-19 3.28.2-1+b1 ii libedataserver-1.2-233.28.2-1+b1 ii libgcr-base-3-1 3.28.0-1 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgirepository-1.0-11.56.1-1 ii libgjs0g [libgjs0-libmozjs-52-0] 1.52.3-2 ii libglib2.0-0 2.56.1-2 ii libglib2.0-bin 2.56.1-2 ii libgstreamer1.0-01.14.1-1 ii libgtk-3-0 3.22.29-3 ii libical3 3.0.1-5+b1 ii libjson-glib-1.0-0 1.4.2-4 ii libmutter-2-0
Bug#895466: debootstrap 1.0.96 fails due to missing apt-config
On 12-04-18 09:58, Raphael Hertzog wrote: Hi, On Wed, 11 Apr 2018, Olliver Schinagl wrote: While running debootstrap on a non-native debian system, debootstrap keeps failing with debootstrap: line 55: apt-config: command not found Duh... this change has even been discussed on the mailing list. I think it's partly fixed already in git but still there's a big misunderstanding. Well I just took the latest master and wanted to run it. I didn't dig into the mailing list to see if a broken master was being disccused (I did google for it but couldn't find it. I manually debugged and git-bisected it) Hideki, when Ben Hutchings suggested to use "command -v" it means "command -v apt-config" and not "apt-config -v". But really the code that went into 1.0.96 is completely wrong. Basically you tested whether "apt-config -v >/dev/null" is a non-empty string. And yes it's a non-empty string. :-) I pushed a proper fix to git. Thanks for fixing it :) Cheers,
Bug#895466: debootstrap 1.0.96 fails due to missing apt-config
On 12-04-18 10:05, Simon McVittie wrote: On Wed, 11 Apr 2018 at 22:14:21 +0200, Olliver Schinagl wrote: Tags: newcomer The newcomer tag is for use by the package's maintainer. It indicates a bug that is particularly suitable for new contributors to work on as an introduction to contributing to this package (I don't think this is one of those). It does not indicate bugs that were encountered by new users, or bugs that particularly affect new users. Sorry about that, I just wanted to get the mailbot to accept the issue ;) While running debootstrap on a non-native debian system, debootstrap keeps failing with debootstrap: line 55: apt-config: command not found The change causing the issue seems to be https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=98858a907a9f69e which always seems to pass the if check (even though it's not installed) and then fails on the eval. Recent versions (I'm looking at the git repository here) seem to have introduced seversal misunderstood conditionals. Were these tested or reviewed? The important thing to remember in shell conditions is that the square brackets in "if [ ... ]; then" are not special shell syntax: the opening square bracket is another name for test(1), and the closing square bracket is required and ignored when test(1) is invoked as [(1). The square brackets should be used if and only if you want to check a condition that is most easily checked via test(1). The line mentioned in this bug is: if [ "apt-config -v > /dev/null" ]; then which is equivalent to "if true; then" because "apt-config -v > /dev/null" is a non-empty string. I think this was meant to be either if apt-config -v > /dev/null 2>&1; then which enters the "then" block whenever apt-config -v exits 0 (success), or if [ -n "$(apt-config -v 2>/dev/null)" ]; then which enters the "then" block whenever apt-config -v produces output. Either way, stderr should probably be redirected to /dev/null (as shown) to silence "apt-config: not found" messages on non-Debian systems. This is not the only problematic conditional. There's also: +if [ ! "$VARIANT" = fakechroot ] && [ "$(apt-config -v > /dev/null 2>&1)" ]; then The second part of this condition will always evaluate to false, because apt-config -v > /dev/null 2>&1 never produces output (it has all been redirected to /dev/null), so the $() operator produces no output, and the test is [ "" ] which returns false. I think this was meant to be: if [ ! "$VARIANT" = fakechroot ] && apt-config -v > /dev/null 2>&1; then in which the second part becomes a check for "did apt-config -v exit with status 0?", or possibly if [ ! "$VARIANT" = fakechroot ] && [ -n "$(apt-config -v 2>/dev/null)" ]; then in which the second part checks whether apt-config produced output. Similarly: +if [ "$(ls -A "$TARGET" > /dev/null 2>&1)" ]; then doesn't do anything useful, because the output of ls is discarded. Either the intention was to check whether the output of ls was non-empty (in which case remove the "> /dev/null" redirection and use 2>/dev/null), or the intention was to check the exit status (in which case remove [] and "$()"). When testing whether a string is (non-)empty, I would recommend using the [ -n "$foo" ] or [ -z "$foo" ] form instead of just [ "$foo" ] or ! [ "$foo" ] - it makes it a bit clearer what the intention was. smcv
Bug#895466: debootstrap 1.0.96 fails due to missing apt-config
Package: debootstrap Version: 1.0.96 Severity: important Tags: newcomer Dear maintainer, While running debootstrap on a non-native debian system, debootstrap keeps failing with debootstrap: line 55: apt-config: command not found The change causing the issue seems to be https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=98858a907a9f69e which always seems to pass the if check (even though it's not installed) and then fails on the eval.
Bug#877679: [Openjdk] Bug#877679: java-8-openjdk (version 8u141-b15-1~deb9u1) fails to install if /usr/share/man is not available
Hey, On 07-10-17 02:41, Matthias Klose wrote: Control: severity -1 wishlist On 04.10.2017 11:52, Mattia Rizzolo wrote: Control: reassign -1 openjdk-8-jre-headless 8u141-b15-1~deb9u1 Control: severity -1 serious no. why? Please don't exaggerate bug severities without looking at them. On Tue, Oct 03, 2017 at 09:47:12PM +0200, Olliver Schinagl wrote: Package: java-8-openjdk Version 8u141-b15-1~deb9u1 Please use reportbug to report your bugs if you are unsure about the the proper syntax: the package you mentioned doesn't exist, and the version line lacks a column. Severity: normal failures to install are serious bugs. no, not if the user choose to drop installation of manual pages, and the infrastructure is broken not to handle creating symlinks for these cases. If you want to help, please find an appropriate package and reassign. We had these bug reports before. As mentioned in the report, I had the same issue with postgres, and the fix was implented within a day, so I'm guessing it was rather trivial. Postgresql: Bug#866729 You are absolutly right that this is a result from a user desision, but mind you, when doing containers, it is often preferred to have them nice and lean, dropping man pages and documentation (while keeping the licenses of course) is very commonly done to minimize the container. From the log below, which is is what brought me to this package name, I can't seem to figure out what other package would be the root cause? Do you have any suggestions where it should go? Reassigning and leaving the rest of the message as a context for the maintainer. When setting up java-8-openjdk on a minimal debian (where I would have rm -rf-ed /usr/share/man) the following snipped shows the failure error. I have had a similar error with postgres which was fixed in Bug#866729 update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: error: error creating symbolic link '/usr/share/man/man1/rmid.1.gz.dpkg-tmp': No such file or directory dpkg: error processing package openjdk-8-jre-headless:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of openjdk-8-jdk-headless:amd64: openjdk-8-jdk-headless:amd64 depends on openjdk-8-jre-headless (= 8u141-b15-1~deb9u1); however: Package openjdk-8-jre-headless:amd64 is not configured yet. Thank you, Olliver ___ Mailing list: https://launchpad.net/~openjdk Post to : open...@lists.launchpad.net Unsubscribe : https://launchpad.net/~openjdk More help : https://help.launchpad.net/ListHelp
Bug#877679: java-8-openjdk (version 8u141-b15-1~deb9u1) fails to install if /usr/share/man is not available
Hey Mattia, On 04-10-17 11:52, Mattia Rizzolo wrote: Control: reassign -1 openjdk-8-jre-headless 8u141-b15-1~deb9u1 Control: severity -1 serious On Tue, Oct 03, 2017 at 09:47:12PM +0200, Olliver Schinagl wrote: Package: java-8-openjdk Version 8u141-b15-1~deb9u1 Please use reportbug to report your bugs if you are unsure about the the proper syntax: the package you mentioned doesn't exist, and the version line lacks a column. Sorry, but I was on a fedora system during the time of reporting, and the system on which it was running was a headless container that was being installed, with a non-debian host. Severity: normal failures to install are serious bugs. Reassigning and leaving the rest of the message as a context for the maintainer. When setting up java-8-openjdk on a minimal debian (where I would have rm -rf-ed /usr/share/man) the following snipped shows the failure error. I have had a similar error with postgres which was fixed in Bug#866729 update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: error: error creating symbolic link '/usr/share/man/man1/rmid.1.gz.dpkg-tmp': No such file or directory dpkg: error processing package openjdk-8-jre-headless:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of openjdk-8-jdk-headless:amd64: openjdk-8-jdk-headless:amd64 depends on openjdk-8-jre-headless (= 8u141-b15-1~deb9u1); however: Package openjdk-8-jre-headless:amd64 is not configured yet. Thank you, Olliver
Bug#877679: duplicate of Bug#877677
Sorry for the noise, but this bug is a duplicate of Bug#877677 due to a missconfigured server on my part. Sorry for the noise, Olliver
Bug#801850: busybox: readlink gets shadowed by busybox causing debconf to possibly fail
Hey Christoph On 03-10-17 21:42, Christoph Biedl wrote: tags 801850 +moreinfo +patch thanks With both coreutils and busybox installed however, the busybox variant gets used before the coreutils variant causing package failures. Does such a breakage happen or is this rather a theoretical scenario? Or: Is this an issue to be fixed in (old)stable as well? This happened in an actual situation, hence why i brought it up :) Since my ticket is 2 years old in 10 days, I'm not sure exactly what I was doing to trigger this (call it a bad bug report on my part :) but I think what was going on (and writing it down again freshens my memory) we have an "embedded" jessie rootfs filesystem, and after post-install, we run a busybox --install to 'fill in the blanks'. Because busybox's readlink has as you say precedence, flash-kernel in this case, fails to work as busybox's readlink is not as complete (or not fully compatible). A quick fix/workaround: if [ -f /bin/readlink ]; then unlink /usr/bin/readlink fi Things are not that easy unfortunately. Which would be kind of an ugly workaround imo. As you first run busybox --install to 'fill in the blank' and still have to go fix things manually afterwards. It's saner to fix the underlying problem which took a while to understand: busybox --install places the readlink link in /usr/bin/, a directory that has precedence in $PATH over /bin/ where coreutils version resides. And things go downhill from there. The patch attached changes busybox' install path for readlink to /bin/ as well - since busybox never replaces existing files, everything should be fine. This sounds quite reasonable and should work rather well, even better (but that's beyond a simple patch like this) would be if busybox --install would check if something exists, and not install the duplicate (unless --force is supplied (without overwriting)) Please give it a try and report whether this helps in your situation. Since we haven't switched to flash-kernel, we haven't had the issue yet, but once it does; I'll definitely check this if it works now! Thanks, Olliver Christoph
Bug#877679: java-8-openjdk (version 8u141-b15-1~deb9u1) fails to install if /usr/share/man is not available
Package: java-8-openjdk Version 8u141-b15-1~deb9u1 Severity: normal Dear maintainer, When setting up java-8-openjdk on a minimal debian (where I would have rm -rf-ed /usr/share/man) the following snipped shows the failure error. I have had a similar error with postgres which was fixed in Bug#866729 update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: error: error creating symbolic link '/usr/share/man/man1/rmid.1.gz.dpkg-tmp': No such file or directory dpkg: error processing package openjdk-8-jre-headless:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of openjdk-8-jdk-headless:amd64: openjdk-8-jdk-headless:amd64 depends on openjdk-8-jre-headless (= 8u141-b15-1~deb9u1); however: Package openjdk-8-jre-headless:amd64 is not configured yet. Thank you, Olliver
Bug#877677: java-8-openjdk (version 8u141-b15-1~deb9u1) fails to install if /usr/share/man is not available
Package: java-8-openjdk Version 8u141-b15-1~deb9u1 Severity: normal Dear maintainer, When setting up java-8-openjdk on a minimal debian (where I would have rm -rf-ed /usr/share/man) the following snipped shows the failure error. I have had a similar error with postgres which was fixed in Bug#866729 update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode update-alternatives: error: error creating symbolic link '/usr/share/man/man1/rmid.1.gz.dpkg-tmp': No such file or directory dpkg: error processing package openjdk-8-jre-headless:amd64 (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of openjdk-8-jdk-headless:amd64: openjdk-8-jdk-headless:amd64 depends on openjdk-8-jre-headless (= 8u141-b15-1~deb9u1); however: Package openjdk-8-jre-headless:amd64 is not configured yet. Thank you, Olliver
Bug#866729: (postgresql (version 9.6+181) fails to install if /usr/share/man is removed.)
Package: postgresql Version 9.6+181 Severity: normal Dear maintainer, When setting up postgresql on a 'minimal' debian, where I would have rm -rf-ed /usr/share/man, postgresl (and its siblings) will fail to install. In the following snippet, man/man1 was re-created, but man7 was still missing. Setting up postgresql-client-9.6 (9.6.3-3) ... update-alternatives: using /usr/share/postgresql/9.6/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode update-alternatives: error: error creating symbolic link '/usr/share/man/man7/ABORT.7.gz.dpkg-tmp': No such file or directory dpkg: error processing package postgresql-client-9.6 (--configure): subprocess installed post-installation script returned error exit status 2 What I also noticed (not specifically here) is that if /usr/share/man could not be found, more things went badly (unable to access /usr/share/man1 No such file or directory or the like). Other packages, which also supply man-pages, do not seem to suffer from this problem, they simply just continue. Thank you, Olliver
Bug#860545: debootstrap fails to locate xzcat if the default shell is set to posh
Package: debootstrap Version: 1.0.89 Severity: normal Dear Maintainer, Trying to run debootstrap with just acl (the first package in the list) fails at unpacking due to a missing xzcat sudo debootstrap --merged-usr --variant=minbase --components=main,non-free --include=acl jessie /tmp/debtest http://deb.debian.org/debian I: Chosen extractor for .deb packages: ar I: Extracting acl... E: Extracting .//var/cache/apt/archives/acl_2.2.52-2_amd64.deb requires the xzcat command, which is not available $ which xzcat /usr/bin/xzcat changing /bin/sh -> dash fixes it, but I would have figued that if debootstrap has its shebang set to /bin/sh, it would work with any posix shell, including posh. (I read the warning: WARNING: Since many of Debian's /bin/sh scripts are not actually policy- compliant, using posh as your /bin/sh may reveal breakage.) -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debootstrap depends on: ii wget 1.18-5 Versions of packages debootstrap recommends: ii debian-archive-keyring 2014.3 ii gnupg 2.1.18-6 debootstrap suggests no packages. -- no debconf information
Bug#851522: ssmtp fails to install via debootstrap/systemd-nspawn
Package: ssmtp Severity: normal Tags: newcomer Dear Maintainer, When installing ssmtp via either debootstrap --include or via systemd-nspawn -D container apt-get install ssmtp, ssmtp fails to install due to failure of resolving the FQDN. The issue is caused by the postinst script where it uses hostname -f (see http://sources.debian.net/src/ssmtp/2.64-8/debian/postinst/#L22 currently) which cannot be resolved yet. hostname -f or domainname fail: Temporary failure in name resolution. The /etc/hosts and /etc/hostname files where set up appropiatly and booting the container normally and then installing ssmtp works fine. It should thus be avoided to use hostname -f in the postinst script. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#848229: systemd: Should systemd provide netbase?
On 15-12-16 19:43, Michael Biebl wrote: Am 15.12.2016 um 19:41 schrieb Michael Biebl: Control: reassign -1 netbase Control: retitle -1 Drop/Demote recommends on ifupdown Am 15.12.2016 um 13:17 schrieb Olliver Schinagl: Package: systemd Version: 232-3 Severity: normal File: systemd-networkd Dear Maintainer, currently, when installing a small server, with systemd(-sysv),isc-dhcp- server,openntpd it pulls in some dependencies, of which one comes from netbase, which is a dependancy of openntpd. While the choice ultimatly is with the user, having systemd-networkd and systemd-resolved, which covers most basic network needs and in theory supplies netbase. So should systemd not also thus provide netbase? If a user wants to install other network tools or packages depend on specific networking packages, they can list them as such, naturally. Having systemd Provides: netbase doesn't really make sense. systemd doesn't provide that functionality after all. I don't know what netbase does and does not provide, but systemd-networkd provides pretty much everything you need to setup and run (quite an advanced) network these days? So what doesn't systemd provide? You could ask the netbase maintainer, Marco, though, if he was open to drop the Recommends: ifupdown or demote it to Suggests. That would seem like a reasonable suggestion to me. So I'm reassigning this to netbase and let Marco decide. Keep in mind though, that ifupdown will likely be installed anyway, since it has Priority: important Well I installed a container via debootstrap and minbase and only added isc-dhcp-server. Then I decided I wanted which needs netbase and only then it started to pull in ifupdown etc.
Bug#674857: Disable pam_securetty by default?
Hey all, raising this one from the crypt So the security benefit isn't in preventing users from logging in as root over certain serial lines, it's in preventing users from logging in as root over *pseudo*ttys. It is unix museumware from time when people didn't use ssh and su/sudo all time. I just did a clean install of debian jessie (via debootstrap into a systemd-nspawn container) and noticed that I could not login using machinectl login securtty bites us. The reason it bites is that by default, the container comes up with a console on pts/0. I see in securetty there are workarounds for LXC already and adding pts/0 as a work around for systemd-nspawn then makes me wonder, is this not a pseudo tty? And thus, the only argument made in 2012, with systemd containers will make that last argument fall? As you always need a pseudo-tty here. So I also suggest, opt-in vs opt-out on the pam_securetty module so that 'museums' can still enable them if needed. Olliver
Bug#827602: libdirectfb-dev depends on libpng but fails to install it when installing libdirectfb-dev
Package: libdirectfb-dev Severity: minor Dear Maintainer, Setting up a debootstrap with libsdl-dev via --include, which pulls in libdirectfb-dev. libdirectfb-dev in turn wants libpng-dev which fails. Adding libpng12-dev, not libpng-dev, to the list of includes makes the build work fine after that. Which is supprising concidering libpng-dev is a virtual for libpng12-dev. Errors were encountered while processing: libdirectfb-dev libglib2.0-dev libfreetype6-dev libsdl1.2-dev libslang2-dev:amd64 libpulse-dev:amd64 libcaca-dev dpkg: dependency problems prevent configuration of libdirectfb-dev: libdirectfb-dev depends on libpng-dev; however: Package libpng-dev is not installed. dpkg: error processing package libdirectfb-dev (--configure): dependency problems - leaving unconfigured debootstrap --include=libsdl1.2-dev --components=main,contrib,non-free --variant=minbase jessie /tmp/test/ http://ftp.nl.debian.org/debian/ -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, microblaze Kernel: Linux 4.6.1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#801850: busybox: readlink gets shadowed by busybox causing debconf to possibly fail
Package: busybox Version: 1:1.22.0-15 Severity: important Tags: newcomer Dear Maintainer, When installing busybox's symlink readlink gets installed (without checking) into /usr/bin/readlink. Some packages require readlink support via debconf (for example the flash-kernel package) but busybox's readlink does not offer the -m option. Coreutils however, a requirement for debian and its tools (debconf), also supplies readlink. With both coreutils and busybox installed however, the busybox variant gets used before the coreutils variant causing package failures. A quick fix/workaround: if [ -f /bin/readlink ]; then unlink /usr/bin/readlink fi This on armhf jessie variant using busybox 1:1.22.0-9+deb8u1. -- System Information: Debian Release: stretch/sid Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.3.0-rc1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages busybox depends on: ii libc6 2.19-22 busybox recommends no packages. busybox suggests no packages. -- no debconf information
Bug#801688: flash-kernel fails with readlink: invalid option -- 'm'
Hey Ben, On 13-10-15 18:57, Ben Hutchings wrote: On Tue, 2015-10-13 at 15:49 +0200, Olliver Schinagl wrote: Package: flash-kernel Version: 3.35+deb8u1 Severity: important Tags: d-i Dear Maintainer, when installing flash-kernel on a very basic and minimal system (created with multistrap) flash-kernel fails to install. While flash-kernel does seem to work and is installed afterwards this makes automated installation via multistrap impossible. My packages from multistrap looks like this, which as you can see is fairly minimal packages=f2fs-tools connman wpasupplicant iptables dropbear avahi-daemon libv4l-0 lsb-invalid-mta ca-certificates mtd-utils busybox apt usbmount udisks2 rsync I guess adding some dialog dependancy is probably the quickest fix, but I don't think is the best solution. root@system-02880482d32a:~# apt-get install flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded. Need to get 0 B/34.2 kB of archives. After this operation, 76.8 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package flash-kernel. (Reading database ... 14355 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.35+deb8u1_armhf.deb ... Unpacking flash-kernel (3.35+deb8u1) ... Setting up flash-kernel (3.35+deb8u1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline readlink: invalid option -- 'm' [...] I think the problem is that you're using busybox instead of coreutils (which is essential and therefore doesn't have to be explicitly depended on). Depends on how you install your system I suspect. I used multistrap with a list of packages (which pulls the bare minimal system in, of which busybox or core-utils don't appear to be dependancies) and that leaves me with a fully working debian system. I couldn't find where readlink or readline is being called in flash-kernel or its scripts, but for some reason readlink -m is being called which may work with the core-utils, but not with busybox. Having flash-kernel be functional with atleast busybox doesn't seem like a strange requirement. Flash-kernel is for embedded systems and thus having a bare minimal embedded system isn't all out ot the ordinary :) Olliver Ben.
Bug#801688: flash-kernel fails with readlink: invalid option -- 'm'
Package: flash-kernel Version: 3.35+deb8u1 Severity: important Tags: d-i Dear Maintainer, when installing flash-kernel on a very basic and minimal system (created with multistrap) flash-kernel fails to install. While flash-kernel does seem to work and is installed afterwards this makes automated installation via multistrap impossible. My packages from multistrap looks like this, which as you can see is fairly minimal packages=f2fs-tools connman wpasupplicant iptables dropbear avahi-daemon libv4l-0 lsb-invalid-mta ca-certificates mtd-utils busybox apt usbmount udisks2 rsync I guess adding some dialog dependancy is probably the quickest fix, but I don't think is the best solution. root@system-02880482d32a:~# apt-get install flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded. Need to get 0 B/34.2 kB of archives. After this operation, 76.8 kB of additional disk space will be used. debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package flash-kernel. (Reading database ... 14355 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.35+deb8u1_armhf.deb ... Unpacking flash-kernel (3.35+deb8u1) ... Setting up flash-kernel (3.35+deb8u1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline readlink: invalid option -- 'm' BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) multi-call binary. Usage: readlink [-fnv] FILE Display the value of a symlink -f Canonicalize by following all symlinks -n Don't add newline -v Verbose : Unable to determine The new file dpkg: error processing package flash-kernel (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: flash-kernel E: Sub-process /usr/bin/dpkg returned an error code (1) P.S. 3.46~bpo8+1 also suffers the same problem. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.3.0-rc1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#776418: According to ubuntu reports, this appears to be a regression.
Searching a bit more, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384297 Ubuntu users notice this as being a regression with the later 3.16 series of kernels. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776418: linux-base: i915 fails occasionally to suspend
Package: linux-base Version: 3.5 Severity: important Dear Maintainer, The 3.16-series have some kernel bugs with the i915 video driver causing suspend to occasionally fail. When it fails, it keeps failing and only a reboot fixes it. This has been noticed on 2013 macbook airs, but I'll keep this report to my own macbook pro mid 2013. The kernel trace: [44652.015163] ---[ end trace 97db4adad9ce9344 ]--- [44652.015182] [ cut here ] [44652.015201] WARNING: CPU: 0 PID: 735 at /build/linux- CMiYW9/linux-3.16.7-ckt2/drivers/gpu/drm/i915/intel_pm.c:5997 intel_display_power_put+0x127/0x150 [i915]() [44652.015204] Modules linked in: bnep ecb btusb bluetooth 6lowpan_iphc pl2303 usbserial cdc_acm binfmt_misc snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic iTCO_wdt iTCO_vendor_support hid_generic hid_apple joydev usbhid bcm5974 hid nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc nls_utf8 nls_cp437 vfat fat evdev applesmc input_polldev x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp efi_pstore kvm_intel kvm crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd wl(PO) pcspkr efivars cfg80211 rfkill thunderbolt lpc_ich i2c_i801 mfd_core snd_hda_intel snd_hda_controller snd_hda_codec i915 sbs sbshc snd_hwdep drm_kms_helper snd_pcm drm ac video i2c_algo_bit snd_timer battery apple_bl button snd mei_me soundcore i2c_core [44652.015292] shpchp mei processor thermal_sys fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic usb_storage ahci libahci crct10dif_pclmul libata crct10dif_common crc32c_intel scsi_mod tg3 ptp pps_core libphy xhci_hcd usbcore usb_common [44652.015332] CPU: 0 PID: 735 Comm: Xorg Tainted: PW O 3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1 [44652.015336] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B03.1310291227 10/29/2013 [44652.015338] 0009 81507263 81065847 [44652.015345] 88026544002c 8802631ab000 88026544 000b [44652.015351] 880265448520 a03af167 8802631ab000 8802631ab000 [44652.015358] Call Trace: [44652.015364] [81507263] ? dump_stack+0x41/0x51 [44652.015371] [81065847] ? warn_slowpath_common+0x77/0x90 [44652.015390] [a03af167] ? intel_display_power_put+0x127/0x150 [i915] [44652.015415] [a040d8cc] ? intel_dp_get_modes+0x6c/0x100 [i915] [44652.015429] [a0396966] ? drm_helper_probe_single_connector_modes_merge_bits+0x286/0x370 [drm_kms_helper] [44652.015446] [a0305ccd] ? drm_mode_getconnector+0x3dd/0x450 [drm] [44652.015453] [811b8930] ? poll_select_copy_remaining+0x140/0x140 [44652.015468] [a02f78b7] ? drm_ioctl+0x1c7/0x5b0 [drm] [44652.015478] [81088cad] ? __hrtimer_start_range_ns+0x1cd/0x390 [44652.015484] [811b7d2f] ? do_vfs_ioctl+0x2cf/0x4b0 [44652.015490] [814017be] ? __sys_recvmsg+0x3e/0x80 [44652.015496] [811b7f91] ? SyS_ioctl+0x81/0xa0 [44652.015503] [8150d32d] ? system_call_fast_compare_end+0x10/0x15 [44652.015506] ---[ end trace 97db4adad9ce9345 ]--- and upstream is some noice about this aswell. https://freedesktop.org/patch/30470/ 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) [2.598451] fbcon: inteldrmfb (fb0) is primary device [3.996610] i915 :00:02.0: fb0: inteldrmfb frame buffer device model name: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz Thanks, Olliver -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.55 ii libuuid-perl 0.05-1+b1 ii udev 215-10 ii util-linux 2.25.2-4.1 linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual: linux-base/disk-id-convert-plan-no-relabel: true linux-base/disk-id-convert-plan: true linux-base/disk-id-convert-auto: true linux-base/disk-id-manual-boot-loader: linux-base/do-bootloader-default-changed: linux-base/disk-id-update-failed: -- debsums errors found: debsums: missing file /usr/share/doc/linux-base/NEWS.Debian.gz (from linux-base package) debsums: missing file /usr/share/doc/linux-base/changelog.gz (from linux-base package) debsums: missing file /usr/share/doc/linux-base/copyright (from linux-base package) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776358: gnome fails to set backlight brightness when hotswapping monitors
Package: gnome Version: 1:3.14+3 Severity: normal Dear Maintainer, When plugging in, but NOT when removing an external monitor, the laptop's backlight is reset to 0. I can manually increase the backlight, but after each hotplug event, the backlight is 0 again. This may be related to bug #776355 which shows similar, but not exactly the same, behavior on gdm3. This on a mid 2013 macbook pro retina, 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) [2.598451] fbcon: inteldrmfb (fb0) is primary device [3.996610] i915 :00:02.0: fb0: inteldrmfb frame buffer device model name: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome depends on: ii alacarte 3.11.91-2 ii avahi-daemon 0.6.31-4+b2 ii bijiben3.14.2-1+b1 ii brasero3.11.4-1 ii cheese 3.14.1-2 ii cups-pk-helper 0.2.5-2+b1 ii desktop-base 8.0.2 ii evolution 3.12.9~git20141130.241663-1+b1 ii evolution-plugins 3.12.9~git20141130.241663-1+b1 ii file-roller3.14.1-1 ii gedit 3.14.0-3 ii gedit-plugins 3.14.0-2 ii gimp 2.8.14-1+b1 ii gnome-clocks 3.14.1-1 ii gnome-color-manager3.14.1-1 ii gnome-core 1:3.14+3 ii gnome-documents3.14.2-1 ii gnome-games1:3.14+3 ii gnome-getting-started-docs 3.14.1-1 ii gnome-logs 3.14.2-1 ii gnome-maps 3.14.1.2-1 ii gnome-music3.14.1-1 ii gnome-nettool 3.8.1-1 ii gnome-orca 3.14.0-2 ii gnome-photos 3.14.2-1 ii gnome-shell-extension-weather 0~20140924.git7e28508-1 ii gnome-sound-recorder 3.14.0.1-1 ii gnome-tweak-tool 3.14.2-2 ii gstreamer1.0-libav 1.4.4-2 ii gstreamer1.0-plugins-ugly 1.4.4-2 ii hamster-applet 2.91.3+git20120514.b9fec3e1-1 ii inkscape 0.48.5-3 ii libgtk2-perl 2:1.2492-3 ii libreoffice-calc 1:4.3.3-2 ii libreoffice-evolution 1:4.3.3-2 ii libreoffice-gnome 1:4.3.3-2 ii libreoffice-impress1:4.3.3-2 ii libreoffice-writer 1:4.3.3-2 ii nautilus-sendto3.8.2-1 ii network-manager-gnome 0.9.10.0-2 ii polari 3.14.1-1 ii rhythmbox 3.1-1 ii rhythmbox-plugin-cdrecorder3.1-1 ii rhythmbox-plugins 3.1-1 ii rygel-playbin 0.24.2-1 ii rygel-tracker 0.24.2-1 ii seahorse 3.14.0-2 ii simple-scan3.14.0-1 ii sound-juicer 3.14.0-1+b1 ii telepathy-gabble 0.18.3-1+b1 ii telepathy-rakia0.8.0-3 ii telepathy-salut0.8.1-4 ii totem-plugins 3.14.0-2 ii transmission-gtk 2.84-0.2 ii vinagre3.14.1-1 ii xdg-user-dirs-gtk 0.10-1 Versions of packages gnome recommends: pn gnome-software none Versions of packages gnome suggests: pn iceweasel-l10n-all none pn xul-ext-adblock-plus none pn xul-ext-gnome-keyring none Versions of packages gnome-core depends on: ii adwaita-icon-theme 3.14.0-2 ii at-spi2-core 2.14.0-1 ii baobab 3.14.1-1 ii caribou0.4.15-1 ii caribou-antler 0.4.15-1 ii dconf-gsettings-backend0.22.0-1 ii dconf-tools0.22.0-1 ii empathy3.12.7-1 ii eog3.14.1-1 ii evince 3.14.1-1 ii evolution-data-server 3.12.9~git20141128.5242b0-2+b1 ii fonts-cantarell0.0.16-1 ii gdm3 3.14.1-3 ii gkbd-capplet 3.6.0-1 ii glib-networking2.42.0-2 ii gnome-backgrounds 3.14.1-1 ii gnome-bluetooth3.14.0-2 ii gnome-calculator 3.14.1-1 ii gnome-contacts 3.14.1-1 ii gnome-control-center 1:3.14.2-2 ii gnome-dictionary 3.14.1-1 ii gnome-disk-utility 3.12.1-1+b1 ii gnome-font-viewer 3.14.0-1 ii gnome-keyring 3.14.0-1+b1 ii gnome-menus3.13.3-5 ii gnome-online-accounts 3.14.2-1 ii gnome-online-miners3.14.0-2 ii
Bug#776356: gdm3 shows only black screen with cursor on tripple head
Package: gdm3 Version: 3.14.1-3 Severity: normal Dear Maintainer, When booting with 3 monitors, internal laptopscreen, 2 external monitors, GDM refuses to bring up the login screen, instead it shows 3 black screens with a cursor. The cursor can happily move between all 3 screens. Booting with only 2 screens, laptop + external monitor, works fine. After logging in, I can happily plug in the third monitor and have a tripple-head desktop. Last time I checked on Ubuntu, a few months ago, this all worked normally, so it has worked at 'some' point in the past. This on a mid 2013 macbook pro retina, 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) [2.598451] fbcon: inteldrmfb (fb0) is primary device [3.996610] i915 :00:02.0: fb0: inteldrmfb frame buffer device model name: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.55 ii gir1.2-gdm3 3.14.1-3 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell 3.14.2-3+b1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgdm1 3.14.1-3 ii libglib2.0-0 2.42.1-1 ii libglib2.0-bin2.42.1-1 ii libgtk-3-03.14.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd215-8 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.2-1 ii policykit-1 0.105-8 ii terminology [x-terminal-emulator] 0.7.0-1 ii ucf 3.0030 ii x11-common1:7.7+7 ii x11-xserver-utils 7.7+3+b1 ii xterm [x-terminal-emulator] 312-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.2.901-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.14.0-2 ii libpam-gnome-keyring 3.14.0-1+b1 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776355: gdm3 turns backlight off when multiple monitors are connected, yet puts the login prompt on the darkened monitor
Package: gdm3 Version: 3.14.1-3 Severity: normal Dear Maintainer, Whenever I do a cold boot, I see the boot messages on my laptop screen and monitor in parallel. Whenever GDM starts however, backlight is set to be off. The secondary monitor still shows the gdm background. The login prompt however remains on the primary laptop screen and thus cannot be interacted with. Booting with no external monitors connected works fine. Additionally, the backlight brightness cannot be adjusted when gdm is active (but I think this is to be expected due to permissions?). This on a mid 2013 macbook pro retina, 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) [2.598451] fbcon: inteldrmfb (fb0) is primary device [3.996610] i915 :00:02.0: fb0: inteldrmfb frame buffer device model name: Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz It does not matter whether the display is connected via hdmi or display-port. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.55 ii gir1.2-gdm3 3.14.1-3 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell 3.14.2-3+b1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-13 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libgdm1 3.14.1-3 ii libglib2.0-0 2.42.1-1 ii libglib2.0-bin2.42.1-1 ii libgtk-3-03.14.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd215-8 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.2-1 ii policykit-1 0.105-8 ii terminology [x-terminal-emulator] 0.7.0-1 ii ucf 3.0030 ii x11-common1:7.7+7 ii x11-xserver-utils 7.7+3+b1 ii xterm [x-terminal-emulator] 312-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.2.901-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca3.14.0-2 ii libpam-gnome-keyring 3.14.0-1+b1 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773410: [Pkg-electronics-devel] Bug#773410: geda-xgsch2pcb does not pull in geda or gschem as a dependcy.
On 18-12-14 08:44, أحمد المحمودي wrote: On Thu, Dec 18, 2014 at 07:11:13AM +0100, Olliver Schinagl wrote: Reversibly (and worse) geda-xgsch2pcb does not pull in geda (or gschem for that matter). Since xgsch2pcb is a tool to make the transistion from geda schema's which are made in gschem, to pcb, gschem (and more, like gnetllist, gattrib etc etc) are requried for geda-xgsch2pcb to work properly. geda-xgsch2pch does pull gschem, gattrib and pcb, as they are in its Depends. It does that indeed, but Why should it pull gnetlist ? It doesn't call gnetlist. I think it does, as it it generates the netlist to feed to pcb? Personally, geda should pull in geda-xgsch2pcb which in turn pulls in everything it needs. It might be a good idea to put geda-xgsch2pcb in geda's Recommends or Suggests. Yeah, after installing geda, the main 'program' to use is probably geda-xgsch2pcb, as that sort of is the 'project manager' for geda. Users are probably confused enough that after they install geda, they still have to figure out how to tie it all together. Olliver -- Met vriendelijke groeten, Kind regards, 与亲切的问候 Olliver Schinagl Research Development Ultimaker B.V. http://www.ultimaker.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773410: geda-xgsch2pcb does not pull in geda or gschem as a dependcy.
Package: geda-xgsch2pcb Version: 0.1.3-2 Severity: normal Dear Maintainer, When wanting to do PCB design with the geda suite without pulling in the entire science-electronics meta package, then geda can be a solution. However the geda-meta package does not pull in geda-xgsch2pcb. Reversibly (and worse) geda- xgsch2pcb does not pull in geda (or gschem for that matter). Since xgsch2pcb is a tool to make the transistion from geda schema's which are made in gschem, to pcb, gschem (and more, like gnetllist, gattrib etc etc) are requried for geda- xgsch2pcb to work properly. Personally, geda should pull in geda-xgsch2pcb which in turn pulls in everything it needs. Alternativily, geda-xgsch2pcb becomes a single dependancy of geda, without any dependancies of its own, as the tool does not _require_ anything, The buttons only execute the installed binaries, hence the useless- ness of the program if the binaries are missing. -- System Information: Debian Release: 8.0 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages geda-xgsch2pcb depends on: ii geda-gattrib1:1.8.2-4 ii geda-gschem 1:1.8.2-4 ii geda-utils 1:1.8.2-4 ii pcb 20140316-3 ii python 2.7.8-2 ii python-dbus 1.2.0-2+b3 ii python-gobject 3.14.0-1 ii python-gtk2 2.24.0-4 ii python-support 1.0.15 geda-xgsch2pcb recommends no packages. geda-xgsch2pcb suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773411: cscope has strange depenadncy on ed
Source: cscope Version: 15.8a-2 Severity: normal Dear Maintainer, when installing cscope (as a suggest for e.g. vim, the editor) cscope wants to pull in ed as a dependancy. Ed, being an editor mostly, sounds like a strange dependancy for cscope. -- System Information: Debian Release: 8.0 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772836: node-underscore: package does not install into a subdirectory of /usr/lib/nodejs/
Package: node-underscore Version: 1.7.0~dfsg-1 Severity: important Dear Maintainer, on my installation I find underscore.js (and package.json) to be installed under /usr/lib/nodejs/underscore.js and /usr/lib/nodejs/package.json. If a nother package uses the same path, it would overwrite/conflict with package.json. I thus recommend to put these files into their own subdirectory. Ideally it would even be renamed to index.js, so that it would read /usr/lib/nodejs/underscore/index.js but that probably creates more problems then it solves with regards to backwards compatibility. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772835: node-async: package does not install into a subdirectory of /usr/lib/nodejs/
Source: node-async Version: 0.8.0-1 Severity: important Dear Maintainer, on my installation I find async.js (and package.json) to be installed under /usr/lib/nodejs/async.js and /usr/lib/nodejs/package.json. If a nother package uses the same path, it would overwrite/conflict with package.json. I thus recommend to put these files into their own subdirectory. Ideally it would even be renamed to index.js, so that it would read /usr/lib/nodejs/async/index.js but that probably creates more problems then it solves with regards to backwards compatibility. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772529: apt-cacher-ng wants to install ed as dependancy
Package: apt-cacher-ng Version: 0.8.0-3 Severity: normal Dear Maintainer, apt-cacher-ng for some reason wants to install 'ed', the classic UNIX line editor. Any standard $EDITOR should be fine for the user and if the program depends on ed in its programming; then why not use the standard unix tools (cat/grep/sed etc). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761815: wow, huh
I just got bitten by this bug myself. As a long time gentoo + ubuntu user, I was baffled after getting the solution to this problem. I have worked through several different kind of fstab files, but this was a serious wtf. Why wasn't removable storage working for me? I just couldn't figure it out, everything 'looked' normal. I'd increase the severity of this report, as it is far far from obvious. Olliver -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769884: vim-scripts installs the taglist plugin amongst others, but taglist refuses to work without ctags
Package: vim-scripts Version: 20130814 Severity: normal Dear Maintainer, Installing the vim-scripts package would make one assume that the plugins are fully functional contained in the package. taglist however for taglist requires ctags to do anything. Adding ctags as a dependency for vim-scripts is in place? -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash vim-scripts depends on no packages. Versions of packages vim-scripts recommends: ii vim-addon-manager 0.5.3 ii vim-gnome [vim]2:7.4.488-1 Versions of packages vim-scripts suggests: pn libtemplate-perl none pn perlsgml none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718632: Also happens on Fedora 20
Fedora 20 also seems to drop /bin from its path. In my opinion, debootstrap shouldn't rely on environment variables from the host, debootstrap (should) know how its environment should look like and thus should set it up as such. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746404: dtv-scan-tables: /usr/share/dvb/dvb-t/fr-all file : invalid enum and no DVB-T services found
Hey Fred, On 05/14/2014 06:50 PM, fredbob...@free.fr wrote: Thank you guys for your support ! Olliver, thank you for your commit I tested it and the parsing 1) is now good. However problem 2) is still there : no services are found at the end of the scan. I mean when doing : scan dtv-scan-tables/dvb-t/fr-All the end result is : ERROR: initial tuning failed dumping lists (0 services) Done. Digging further I think the problem is due to FEC, QAM and Guard Interval parameters consistency. Indeed in France it seems there are 2 schemes for DVB-T services depending on where you live (I'm not quite 100% sure as I could only find very few official reliable information) : FEC 3/4, QAM64, Guard Interval 1/8 FEC 2/3, QAM16, Guard Interval 1/32 Whereas in the file we have : FEC 2/3, QAM64, Guard Interval 1/32 Have you tried wscan? wscan is able to generate a 'initial scanning file' which should result in a proper file. See, the thing is, I don't know what is right and what is from for the entirety of France, I don't have the range nor the lingustic skill to read the dvb-t sites from French providers about the proper parameters. We are kind of Dependant on people who live in an area to submit the proper scan files. If you think or know that identical frequencies are used with different parameters in different regions, then that is something that needs to be explored. If the auto setting works well, we could use that. But try to do a wscan and generate an initial scan file from it and see what it says, I'd be very curious indeed. Olliver However I think this scheme may be OK depending on your HW frontend tolerance. Unfortunately it doesn't work with my Hauppauge NOVA-TD-500. I propose 2 options : A) rely on the the AUTO capability and use FEC AUTO, QAM AUTO, GI AUTO in the frequency file (please refer to attached file fr-All-optionA) B) double the file with both schemes for each frequency (please refer to attached file fr-All-optionB) : the drawback is that the scan is twice longer. I sucessfully managed to scan services with both A B. I've attached both tests outputs for your reference. = But I only have TV channels with the first scheme in my area. Do you have an opinion about A or B ? Thank you. Cheers, Fred - Original Message - From: Olliver Schinagl oli...@schinagl.nl Cc: fredboboss fredbob...@free.fr Sent: Monday, May 12, 2014 11:16:18 PM Subject: Re: Fwd: Bug#746404: dtv-scan-tables: /usr/share/dvb/dvb-t/fr-all file : invalid enum and no DVB-T services found Apologies to all involved, I overlooked this e-mail. I patched it to fix the casing as suggested in the e-mail and pushed it upstream. Can you please test it? Olliver On 04/29/2014 11:57 PM, Jonathan McCrohan wrote: Hi Oliver, Please find Debian bug report from fredboboss regarding dtv-scan-tables below. Thanks, Jon On Tue, 29 Apr 2014 19:50:57 +0200, fredboboss wrote: Package: dtv-scan-tables Version: 0+git20140326.cfc2975-1 Severity: normal 1246b27f8b45f84c1824925060ad931530542f2e Dear Maintainer, Dear Debian Maintainer, when performing a DVB-T frequency scan with the /usr/bin/scan utility (dvb-apps package) and the /usr/share/dvb/dvb-t/fr-All frequency file (dtv-scan-tables packages) the following 2 problems occur : 1) file parsing error : ERROR: invalid enum value '8MHZ' ERROR: invalid enum value '8K' 2) in the end no DVB-T services are found with a Hauppauge NOVA-TD-500 DVB-T card. Those problems seem to come from the /usr/share/dvb/dvb-t/fr-All file. The following changes are proposed in this file : For 1) : - 8MHZ changed by 8MHz - 8K changed by 8k For 2) : - change FEC_HI parameter by AUTO Thus the 1st frequency line of the file would be changed like that : -T 47400 8MHZ 2/3 NONE QAM64 8K 1/32 NONE #Channel UHF 21 +T 47400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 21 (Please refer to the end of the mail for the complete modified file). Thanks to those modifications I successfully performed a DVB-T scan with the NOVA TD-500 card. In case more information is needed don't hesitate to contact me. Best regards, Fred -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information Modified file : # France ALL (All channel 21 to 60) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 47400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 21 T 48200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 22 T 49000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 23 T 49800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 24 T 50600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 25 T 51400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 26 T 52200 8MHz AUTO NONE QAM64 8k
Bug#746404: Fwd: Bug#746404: dtv-scan-tables: /usr/share/dvb/dvb-t/fr-all file : invalid enum and no DVB-T services found
Apologies to all involved, I overlooked this e-mail. I patched it to fix the casing as suggested in the e-mail and pushed it upstream. Can you please test it? Olliver On 04/29/2014 11:57 PM, Jonathan McCrohan wrote: Hi Oliver, Please find Debian bug report from fredboboss regarding dtv-scan-tables below. Thanks, Jon On Tue, 29 Apr 2014 19:50:57 +0200, fredboboss wrote: Package: dtv-scan-tables Version: 0+git20140326.cfc2975-1 Severity: normal Dear Maintainer, Dear Debian Maintainer, when performing a DVB-T frequency scan with the /usr/bin/scan utility (dvb-apps package) and the /usr/share/dvb/dvb-t/fr-All frequency file (dtv-scan-tables packages) the following 2 problems occur : 1) file parsing error : ERROR: invalid enum value '8MHZ' ERROR: invalid enum value '8K' 2) in the end no DVB-T services are found with a Hauppauge NOVA-TD-500 DVB-T card. Those problems seem to come from the /usr/share/dvb/dvb-t/fr-All file. The following changes are proposed in this file : For 1) : - 8MHZ changed by 8MHz - 8K changed by 8k For 2) : - change FEC_HI parameter by AUTO Thus the 1st frequency line of the file would be changed like that : -T 47400 8MHZ 2/3 NONE QAM64 8K 1/32 NONE #Channel UHF 21 +T 47400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 21 (Please refer to the end of the mail for the complete modified file). Thanks to those modifications I successfully performed a DVB-T scan with the NOVA TD-500 card. In case more information is needed don't hesitate to contact me. Best regards, Fred -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information Modified file : # France ALL (All channel 21 to 60) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 47400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 21 T 48200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 22 T 49000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 23 T 49800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 24 T 50600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 25 T 51400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 26 T 52200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 27 T 53000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 28 T 53800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 29 T 54600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 30 T 55400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 31 T 56200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 32 T 57000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 33 T 57800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 34 T 58600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 35 T 59400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 36 T 60200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 37 T 61000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 38 T 61800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 39 T 62600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 40 T 63400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 41 T 64200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 42 T 65000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 43 T 65800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 44 T 66600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 45 T 67400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 46 T 68200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 47 T 69000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 48 T 69800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 49 T 70600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 50 T 71400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 51 T 72200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 52 T 73000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 53 T 73800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 54 T 74600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 55 T 75400 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 56 T 76200 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 57 T 77000 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 58 T 77800 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 59 T 78600 8MHz AUTO NONE QAM64 8k 1/32 NONE #Channel UHF 60 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744112: cura-engine shipped with debian is incompatible with the cura client from ultimaker
Package: cura-engine Version: 14.01-2 Severity: normal Dear Maintainer, The current packaged version of cura-engine, 14.01-2 is incompatible with the current shipping version of cura from Ultimaker. Cura 14.03 expects the -p option to be available in CuraEngine. Upgrading CuraEngine to a newer version (14.03) should solve this issue. While Cura is not yet packaged, and the supplied .deb by ultimaker has a matching CuraEngine, having the proper CuraEngine in debian makes packaging the cura client easier. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers trusty-updates APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.0-23-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
