Bug#884969: dist-upgrade to stretch

[Andreas Glaeser]

It seems I forgot to mention cupsd print-server, printing was not workable upon 
upgrading.

au2 = 'aptitude update && aptitude upgrade':

> root@t555:~# au2
> Get: 1 http://security.debian.org stretch/updates InRelease [63.0 kB]
> Ign http://ftp2.de.debian.org/debian stretch InRelease
> Get: 2 http://ftp2.de.debian.org/debian stretch-updates InRelease [91.0 kB]
> Hit http://ftp2.de.debian.org/debian stretch Release   
> Get: 3 http://security.debian.org stretch/updates/main amd64 Packages [254 kB]
> Get: 4 http://security.debian.org stretch/updates/main Translation-en [110 kB]
> Fetched 518 kB in 2s (248 kB/s)   
>  
>  
> Current status: 9 (+9) upgradable.
> Freed 0 B of disk space  
> The following packages will be REMOVED:  
>   libalgorithm-c3-perl{u} libarchive-extract-perl{u} 
> libb-hooks-endofscope-perl{u}
> libbind9-90{u} libboost-system1.55.0{u} libclass-c3-perl{u} 
> libclass-c3-xs-perl{u} 
>   libclass-method-modifiers-perl{u} libclass-xsaccessor-perl{u} 
> libcpan-changes-perl{u} 
>   libcpan-meta-perl{u} libdata-optlist-perl{u} libdata-perl-perl{u}
> libdata-section-perl{u} libdevel-caller-perl{u} 
> libdevel-globaldestruction-perl{u}
> libdevel-lexalias-perl{u} libdns100{u} libexporter-tiny-perl{u} 
> libfile-slurp-perl{u}
> libgetopt-long-descriptive-perl{u} libgphoto2-port10{u} libimport-into-perl{u}
> libintl-perl{u} libintl-xs-perl{u} libio-stringy-perl{u} libisc95{u} 
> libisccc90{u}
> libisccfg90{u} libjasper1{u} libjim0.75{u} liblist-moreutils-perl{u} 
> libllvm3.8{u}
> liblog-message-perl{u} liblog-message-simple-perl{u} liblwres90{u}
> libmodule-build-perl{u} libmodule-implementation-perl{u}
> libmodule-load-conditional-perl{u} libmodule-pluggable-perl{u}
> libmodule-runtime-perl{u} libmodule-signature-perl{u} libmoo-perl{u}
> libmoox-handlesvia-perl{u} libmro-compat-perl{u} 
> libnamespace-autoclean-perl{u}
> libnamespace-clean-perl{u} libopenjpeg5{u} libpackage-constants-perl{u}
> libpackage-stash-perl{u} libpackage-stash-xs-perl{u} libpadwalker-perl{u}
> libparams-classify-perl{u} libparams-util-perl{u} libparams-validate-perl{u}
> libpath-tiny-perl{u} libperl4-corelibs-perl{u} libpng12-0{u} 
> libpod-latex-perl{u}
> libpod-markdown-perl{u} libpod-readme-perl{u} libpoppler46{u} libpth20{u} 
> libqpdf13{u}
> libqt4-network{u} libqt4-xml{u} libqtcore4{u} libqtdbus4{u} 
> libregexp-common-perl{u}
> librole-tiny-perl{u} libsoftware-license-perl{u} libstrictures-perl{u}
> libsub-exporter-perl{u} libsub-exporter-progressive-perl{u} 
> libsub-identify-perl{u}
> libsub-install-perl{u} libterm-ui-perl{u} libtext-soundex-perl{u}
> libtext-template-perl{u} libtorrent-rasterbar7{u} libtry-tiny-perl{u} 
> libturbojpeg1{u}
> libtype-tiny-perl{u} libtype-tiny-xs-perl{u} libunicode-utf8-perl{u} 
> libv4l-0{u}
> libv4lconvert0{u} libvariable-magic-perl{u} libvpx1{u} libxapian22{u} 
> ntfs-3g{u}
> qtcore4-l10n{u} The following packages will be upgraded: imagemagick
> imagemagick-6-common imagemagick-6.q16 libmagickcore-6.q16-3
> libmagickcore-6.q16-3-extra libmagickwand-6.q16-3 linux-image-4.9.0-4-amd64
> linux-libc-dev sensible-utils 9 packages upgraded, 0 newly installed, 92 to 
> remove and
> 0 not upgraded. Need to get 43.3 MB of archives. After unpacking 86.3 MB will 
> be freed.
> Do you want to continue? [Y/n/?] Get: 1 http://security.debian.org 
> stretch/updates/main
> amd64 imagemagick-6-common all 8:6.9.7.4+dfsg-11+deb9u4 [184 kB] Get: 2
> http://security.debian.org stretch/updates/main amd64 libmagickcore-6.q16-3 
> amd64
> 8:6.9.7.4+dfsg-11+deb9u4 [1,742 kB] Get: 3 http://security.debian.org
> stretch/updates/main amd64 libmagickwand-6.q16-3 amd64 
> 8:6.9.7.4+dfsg-11+deb9u4 [422
> kB] Get: 4 http://security.debian.org stretch/updates/main amd64 
> sensible-utils all
> 0.0.9+deb9u1 [10.8 kB] Get: 5 http://security.debian.org stretch/updates/main 
> amd64
> imagemagick-6.q16 amd64 8:6.9.7.4+dfsg-11+deb9u4 [563 kB] Get: 6
> http://security.debian.org stretch/updates/main amd64 imagemagick amd64
> 8:6.9.7.4+dfsg-11+deb9u4 [141 kB] Get: 7 http://security.debian.org
> stretch/updates/main amd64 libmagickcore-6.q16-3-extra amd64 
> 8:6.9.7.4+dfsg-11+deb9u4
> [190 kB] Get: 8 http://security.debian.org stretch/updates/main amd64
> linux-image-4.9.0-4-amd64 amd64 4.9.65-3+deb9u1 [38.8 MB] Get: 9
> http://security.debian.org stretch/updates/main amd64 linux-libc-dev amd64
> 4.9.65-3+deb9u1 [1,299 kB] Fetched 43.3 MB in 3s (11.4 MB/s) Reading 
> changelogs... Done
> (Reading database ... 109880 files and directories currently installed.) 
> Removing
> libsoftware-license-perl (0.103012-1) ... Removing libdata-section-perl
> (0.26-1) ... Removing libmro-compat-perl (0.12-1) ... Removing 
> libclass-c3-perl
> (0.32-1) ... Removing libalgorithm-c3-perl (0.10-1) ... Removing
> libarchive-extract-perl (0.80-1) ... Removing libpod-readme-perl (1.1.2-1) 
> ... Removing
> lib

Bug#881020: code not parallelized

[Andreas Glaeser]

In my particular case this is about DSA-signatures in Thunderbird with 
Enigmail. These are
very slow to re-check for messages with large attachments. I have a low-end 
25-W PC only
some notebooks and other embedded devices may also be affected by this problem.
When there are 3 to 4 compute-cores available and only one of them is used for
crypto-operations, obviously things are going slower than they could be.
Concerns about parallelizing crypto-code are generally understandable, because 
people
don't want to give away code-integrity and -safety for speed and 
auto-parallelizing does
not seem recommendable.
In spite of that, things should not deliberately be additionally worsened by
double-checking without any real need to do so.




pgpPLziBmmsDs.pgp
Description: OpenPGP digital signature

Bug#881022: Fwd: Enigmail is very slow to check signatures

[Andreas Glaeser]

Package: enigmail
Version: 2:1.9.8.1-1~deb9u1
Severity: minor

Dear Maintainer,

the main problem seems to be her, that generally crypto-code is not 
parallelised. For
example as in my case on a low-end 25W-PC or on notebooks an other embedded 
devices,
there is one compute-core used only for checking DSA-signatures in Thunderbird
with Enigmail, although 3 or 4 are available. So some things are much slower in 
practice
than they could be. 
It is understandable, that there are security concerns, about parallelizing 
crypto-code
and it should not be auto-parallelized, because users could well go devoid of 
their
data-integrity and one might well give away code-reliability for speed. That is 
of course
not recommendable.


>  Forwarded Message 
> Subject: Fwd: Enigmail is very slow to check signatures
> Date: Sat, 14 Oct 2017 09:58:00 +0200
> From: Andreas Glaeser 
> To: enigmail-us...@enigmail.net
> 
> > andrew@a68n:~$ ate show enigmail
> > Package: enigmail
> > Version: 2:1.9.8.1-1~deb9u1
> > State: installed
> > Automatically installed: no
> > Priority: optional
> > Section: mail
> > Maintainer: Debian Mozilla Extension Maintainers
> >  Architecture: all
> > Uncompressed Size: 5,917 k
> > Depends: gnupg (>= 2) | gnupg2, gnupg-agent, thunderbird (>= 1:52.0) | 
> > icedove (>=
> >  1:52.0)
> > Recommends: pinentry-x11
> > Breaks: icedove (< 1:52.0), thunderbird (< 1:52.0)
> > Enhances: icedove, thunderbird
> > Provides: icedove-enigmail, thunderbird-enigmail, xul-ext-enigmail
> > Description: GPG support for Thunderbird and Debian Icedove
> >  OpenPGP extension for Thunderbird. Enigmail allows users to access the 
> > features
> >  provided by the popular GnuPG software from within Thunderbird. 
> >  
> >  Enigmail is capable of signing, authenticating, encrypting and decrypting 
> > email.
> >  Additionally, it supports both the inline PGP format, as well as the 
> > PGP/MIME
> >  format as described in RFC 3156.
> > Homepage: https://www.enigmail.net/
> > Tags: interface::graphical, interface::x11, mail::user-agent, role::plugin,
> >   security::authentication, security::cryptography, security::integrity,
> >   security::privacy, suite::mozilla, uitoolkit::TODO, use::checking,
> >   works-with::mail
> 
> > andrew@a68n:~$ ate show thunderbird
> > Package: thunderbird 
> > Version: 1:52.3.0-4~deb9u1
> > State: installed
> > Automatically installed: yes
> > Priority: optional
> > Section: mail
> > Maintainer: Christoph Goehre 
> > Architecture: amd64
> > Uncompressed Size: 109 M
> > Depends: debianutils (>= 1.16), fontconfig, psmisc, x11-utils, libatk1.0-0 
> > (>=
> >  1.12.4), libc6 (>= 2.17), libcairo-gobject2 (>= 1.10.0), libcairo2 
> > (>=
> >  1.10.2-2~), libdbus-1-3 (>= 1.9.14), libdbus-glib-1-2 (>= 0.78),
> >  libevent-2.0-5 (>= 2.0.10-stable), libffi6 (>= 3.0.4), 
> > libfontconfig1 (>=
> >  2.11), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.0), 
> > libgdk-pixbuf2.0-0 (>=
> >  2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.4), 
> > libhunspell-1.4-0,
> >  libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0),
> >  libpangoft2-1.0-0 (>= 1.14.0), libpixman-1-0 (>= 0.19.6),
> >  libstartup-notification0 (>= 0.8), libstdc++6 (>= 5.2), libvpx4 
> > (>= 1.6.0),
> >  libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 
> > 1:0.3-1),
> >  libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxrender1, libxt6, 
> > zlib1g
> >  (>= 1:1.2.3.4)
> > Recommends: lightning (= 1:52.3.0-4~deb9u1), myspell-en-us | 
> > hunspell-dictionary |
> > myspell-dictionary
> > Suggests: apparmor, fonts-lyx, libgssapi-krb5-2
> > Breaks: enigmail (< 2:1.9.8.1-1~), hunspell-ar (< 0.0.0+20080110-1.1), 
> > hunspell-da
> > (< 1:3.1.0-3), hunspell-de-at (< 20071211-2), hunspell-de-ch (< 
> > 20071211-2),
> > hunspell-de-de (< 20071211-2), hunspell-de-med (< 20090825-1),
> > hunspell-en-ca (< 1:3.1.0-3), hunspell-en-us (< 20070829-3), 
> > hunspell-fr (<
> > 1:3.1.0-3), hunspell-gl-es (< 2.2a-6), hunspell-hu (< 1:3.1.0-3),
> > hunspell-ko (< 0.3.3-1), hunspell-ne (< 1:3.1.0-3), hunspell-se (<
> > 1.0~beta6.20081222-1.1), hunspell-sh (< 1:3.1.0-3), hunspell-sr (<
> > 1:3.1.0-

Bug#881020: Fwd: Enigmail is very slow to check signatures

[Andreas Glaeser]

Package: enigmail
Version: 2:1.9.8.1-1~deb9u1
Severity: minor

Dear Maintainer,

>  Forwarded Message 
> Subject: Fwd: Enigmail is very slow to check signatures
> Date: Sat, 14 Oct 2017 09:58:00 +0200
> From: Andreas Glaeser 
> To: enigmail-us...@enigmail.net
> 
> > andrew@a68n:~$ ate show enigmail
> > Package: enigmail
> > Version: 2:1.9.8.1-1~deb9u1
> > State: installed
> > Automatically installed: no
> > Priority: optional
> > Section: mail
> > Maintainer: Debian Mozilla Extension Maintainers
> >  Architecture: all
> > Uncompressed Size: 5,917 k
> > Depends: gnupg (>= 2) | gnupg2, gnupg-agent, thunderbird (>= 1:52.0) | 
> > icedove (>=
> >  1:52.0)
> > Recommends: pinentry-x11
> > Breaks: icedove (< 1:52.0), thunderbird (< 1:52.0)
> > Enhances: icedove, thunderbird
> > Provides: icedove-enigmail, thunderbird-enigmail, xul-ext-enigmail
> > Description: GPG support for Thunderbird and Debian Icedove
> >  OpenPGP extension for Thunderbird. Enigmail allows users to access the 
> > features
> >  provided by the popular GnuPG software from within Thunderbird. 
> >  
> >  Enigmail is capable of signing, authenticating, encrypting and decrypting 
> > email.
> >  Additionally, it supports both the inline PGP format, as well as the 
> > PGP/MIME
> >  format as described in RFC 3156.
> > Homepage: https://www.enigmail.net/
> > Tags: interface::graphical, interface::x11, mail::user-agent, role::plugin,
> >   security::authentication, security::cryptography, security::integrity,
> >   security::privacy, suite::mozilla, uitoolkit::TODO, use::checking,
> >   works-with::mail
> 
> > andrew@a68n:~$ ate show thunderbird
> > Package: thunderbird 
> > Version: 1:52.3.0-4~deb9u1
> > State: installed
> > Automatically installed: yes
> > Priority: optional
> > Section: mail
> > Maintainer: Christoph Goehre 
> > Architecture: amd64
> > Uncompressed Size: 109 M
> > Depends: debianutils (>= 1.16), fontconfig, psmisc, x11-utils, libatk1.0-0 
> > (>=
> >  1.12.4), libc6 (>= 2.17), libcairo-gobject2 (>= 1.10.0), libcairo2 
> > (>=
> >  1.10.2-2~), libdbus-1-3 (>= 1.9.14), libdbus-glib-1-2 (>= 0.78),
> >  libevent-2.0-5 (>= 2.0.10-stable), libffi6 (>= 3.0.4), 
> > libfontconfig1 (>=
> >  2.11), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.0), 
> > libgdk-pixbuf2.0-0 (>=
> >  2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.4), 
> > libhunspell-1.4-0,
> >  libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0),
> >  libpangoft2-1.0-0 (>= 1.14.0), libpixman-1-0 (>= 0.19.6),
> >  libstartup-notification0 (>= 0.8), libstdc++6 (>= 5.2), libvpx4 
> > (>= 1.6.0),
> >  libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxcomposite1 (>= 
> > 1:0.3-1),
> >  libxdamage1 (>= 1:1.1), libxext6, libxfixes3, libxrender1, libxt6, 
> > zlib1g
> >  (>= 1:1.2.3.4)
> > Recommends: lightning (= 1:52.3.0-4~deb9u1), myspell-en-us | 
> > hunspell-dictionary |
> > myspell-dictionary
> > Suggests: apparmor, fonts-lyx, libgssapi-krb5-2
> > Breaks: enigmail (< 2:1.9.8.1-1~), hunspell-ar (< 0.0.0+20080110-1.1), 
> > hunspell-da
> > (< 1:3.1.0-3), hunspell-de-at (< 20071211-2), hunspell-de-ch (< 
> > 20071211-2),
> > hunspell-de-de (< 20071211-2), hunspell-de-med (< 20090825-1),
> > hunspell-en-ca (< 1:3.1.0-3), hunspell-en-us (< 20070829-3), 
> > hunspell-fr (<
> > 1:3.1.0-3), hunspell-gl-es (< 2.2a-6), hunspell-hu (< 1:3.1.0-3),
> > hunspell-ko (< 0.3.3-1), hunspell-ne (< 1:3.1.0-3), hunspell-se (<
> > 1.0~beta6.20081222-1.1), hunspell-sh (< 1:3.1.0-3), hunspell-sr (<
> > 1:3.1.0-3), hunspell-uz (< 0.6-3.1), hunspell-vi (< 1:3.1.0-3), 
> > icedove (<
> > 1:45.6.0-2.1~), lightning (< 1:52.3.0-4~deb9u1), myspell-af (< 
> > 1:3.1.0-3),
> > myspell-ca (< 0.6-8), myspell-cs-cz (< 20040229-4.1), myspell-da (<
> > 1.6.18-1.1), myspell-de-at (< 20071211-2), myspell-de-ch (< 
> > 20071211-2),
> > myspell-de-de (< 20071211-2), myspell-de-de-oldspell (< 1:2-25.1),
> > myspell-el-gr (< 0.3-1.1), myspell-en-au (< 2.1-5), myspell-en-gb (<
> > 1:3.1.0-3), myspell-en-us (< 1:3.1.0-3)

Bug#876866: installation-report: no boot from USB upon removing installation memory-key

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.63
Severity: normal

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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: USB
Image version:
https://caesar.ftp.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2017-09-25
Date: 2017-09-26, AM

Machine: FSC Futro S700 thin-client
Partitions:
user@debian:~$ df -Tl
Filesystem Type 1K-blocks   Used Available Use% Mounted on
udev   devtmpfs352644  0352644   0% /dev
tmpfs  tmpfs72788   2448 70340   4% /run
/dev/sdb6  btrfs 12694528 892484   9764220   9% /
tmpfs  tmpfs   363928  0363928   0% /dev/shm
tmpfs  tmpfs 5120  0  5120   0% /run/lock
tmpfs  tmpfs   363928  0363928   0% /sys/fs/cgroup
/dev/sdb1  ext4463826  40061395298  10% /boot
tmpfs  tmpfs72784  0 72784   0% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[E]
Overall install:[o]

Comments/Problems:

Installing base system only and ssh-server went basically fine, but the system 
was not
bootable upon the process. Instead I had to edit the grub-entry manually and 
change the
linux-root from /dev/sdc5 --> /dev/sdb5 becuase, the USB-key from which the 
installer ran
was removed, as recommended, and thus the device-name of the filesystem-root 
changed.

This made the system bootable permanenty, without editing grub-command-line 
every time:

root@debian:/etc/grub.d# grub-mkdevicemap
root@debian:/etc/grub.d# man grub-mkdevicemap
root@debian:/etc/grub.d# ls /boot/grub
device.map  fonts  grub.cfg  grubenv  i386-pc  locale  unicode.pf2
root@debian:/etc/grub.d# cat /boot/grub/device.map 
(hd0)   
/dev/disk/by-id/ata-InnoDisk_Corp._DRPS-02GJ30AC1DS-A88_20121025AABB3024
(hd1)   
/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_00190F0C0293EF51597374C3-0:0
root@debian:/etc/grub.d# man grub-mkconfig
root@debian:/etc/grub.d# info grub-mkconfig
root@debian:/etc/grub.d# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.12.0-2-amd64
Found initrd image: /boot/initrd.img-4.12.0-2-amd64
done
root@debian:/etc/grub.d# init 6

Result:
===
root@debian:/home/user# cat /boot/grub/grub.cfg 
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod btrfs
set root='hd1,msdos6'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos6 
--hint-efi=hd1,msdos6
- --hint-baremetal=ahci1,msdos6 --hint='hd1,msdos6'  
45d6feea-f580-4282-9b09-24ad2909b1ee
else search --no-floppy --fs-uuid --set=root 
45d6feea-f580-4282-9b09-24ad2909b1ee
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_GB
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else

Bug#857743: reason for kernel-panic

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I am not convinced, that what you claim is true, since the 
hybrid-filesystem-concept
worked on pure debian-stable, it should be workable with backports included and 
on current
testing, too.
You can have /usr in a separate partition, the symlink-workaroud to 
BTRFS-constraints
should also be workable.
I will make a KVM-image with an hybrid filesystem in order to prove, that this 
is not an
unsupported concept, but Debian is currently suffering from some severe 
regressions in
the field of md-raid. md-raid has never been workable very well in asymmetric
configurations at least from my own experience.
Please don't try to shine your communication-problems by giving me incorrect 
facts.

 


On Thu, 16 Mar 2017 10:07:05 -0300
Felipe Sateler  wrote:

> On Thu, Mar 16, 2017 at 5:09 AM, Andreas Glaeser
>  wrote:
> > Now I was sitting down again to install without md-raid and without 
> > XFS-root.
> > I can reconfirm, that the described problem does not appear with BTRFS-raid 
> > only:
> >  
> >> /dev/sda5  btrfs 46872576 2298224  44044944   5% /
> >> udev   devtmpfs 10240   0 10240   0% /dev
> >> tmpfs  tmpfs   7694288936760492   2% /run
> >> tmpfs  tmpfs  1923568   0   1923568   0% /dev/shm
> >> tmpfs  tmpfs 5120   0  5120   0% /run/lock
> >> tmpfs  tmpfs  1923568   0   1923568   0% /sys/fs/cgroup
> >> /dev/sda6  btrfs 742174721280  72051712   1% /home
> >> /dev/sda1  xfs 972460   88268884192  10% /boot
> >> /dev/sdb1  xfs   30712168 3630772  27081396  12% /mnt/usb  
> 
> In this configuration /usr is a regular dir on the root filesystem.
> What caused the earlier problem was having /usr being a symlink to
> something that was not mounted by the initramfs. Debian does not
> support such configurations[1]. While you are using an initramfs, your
> configuration is such that the initramfs does not mount the filesystem
> that will end up being seen in /usr.
> 
> I'm now closing this bug, as it appears the root cause is an
> unsupported configuration. Please reopen if you can reproduce the
> issue with other configuration that does not involve /usr as a
> symlink.
> 
> 
> [1]
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#late-mounting-usr
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAljLkLwACgkQ5+rBHyUt5wt7AwCghFGKMxr/GRbknTps/thqLfJZ
ogEAoLjjvAshwKxVXw0OvxmnMHBtFor1
=eycz
-END PGP SIGNATURE-

Bug#857743: reason for kernel-panic

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Now I was sitting down again to install without md-raid and without XFS-root.
I can reconfirm, that the described problem does not appear with BTRFS-raid 
only:

> /dev/sda5  btrfs 46872576 2298224  44044944   5% /
> udev   devtmpfs 10240   0 10240   0% /dev
> tmpfs  tmpfs   7694288936760492   2% /run
> tmpfs  tmpfs  1923568   0   1923568   0% /dev/shm
> tmpfs  tmpfs 5120   0  5120   0% /run/lock
> tmpfs  tmpfs  1923568   0   1923568   0% /sys/fs/cgroup
> /dev/sda6  btrfs 742174721280  72051712   1% /home
> /dev/sda1  xfs 972460   88268884192  10% /boot
> /dev/sdb1  xfs   30712168 3630772  27081396  12% /mnt/usb

> Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xe2290299
> 
> Device BootStart   End  Sectors  Size Id Type
> /dev/mmcblk0p1  2048  46874623 46872576 22.4G 83 Linux
> /dev/mmcblk0p2  46876670 121094143 74217474 35.4G  5 Extended
> /dev/mmcblk0p5  46876672 121094143 74217472 35.4G 83 Linux
> 
> Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x40bc4016
> 
> Device Boot Start   End   Sectors  Size Id Type
> /dev/sda1  * 2048   1953791   1951744  953M 83 Linux
> /dev/sda2 1955838 130861055 128905218 61.5G  5 Extended
> /dev/sda5 1955840  48828415  46872576 22.4G 83 Linux
> /dev/sda648830464 123047935  74217472 35.4G 83 Linux
> /dev/sda7   123049984 130861055   7811072  3.7G 82 Linux swap / Solaris

The setup-history was as follows:

#  btrfs device add -f /dev/mmcblk0p1 /
#  btrfs balance start -v -mconvert=raid1 -dconvert=raid1 /
#  btrfs device add -f /dev/mmcblk0p5 /home
#  btrfs balance start -v -mconvert=raid1 -dconvert=raid1 /home
  (init 6)
#  echo "deb http://ftp2.debian.org/debian jessie-backports main contrib 
non-free"
#  >> /etc/apt/sources.list
#  echo "Package: *" >> /etc/apt/preferences
#  echo "Pin: release a=jessie-backports" >> etc/apt/preferences
#  echo "Pin: release a=jessie-backports" >> /etc/apt/preferences
#  echo "Pin-Priority: 520" >> /etc/apt/preferences
#  echo "alias ate='aptitude'" >> .profile 
#  source .profile 
#  ate update
#  ate upgrade

It is workable now, so the problem may be located in the vicinity of systemd, 
but it
actually does not show without XFS on md-RAID and hybrid filesystem-/.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAljKSEkACgkQ5+rBHyUt5wssHACePKxJiCRAG5u2N/u2ACDFoOTb
+eYAmgOFKuToOvn/2pD1fi7yAvYuth1v
=iXTk
-END PGP SIGNATURE-

Bug#857743: Disk-Partitioning and RAID

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


> Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: AE10B6F7-6A0F-4E0E-98A1-565D1EE47ADE
> 
> DeviceStart   End  Sectors  Size Type
> /dev/mmcblk0p1 2048   3905535  3903488  1.9G Linux RAID
> /dev/mmcblk0p2  3905536  46874623 42969088 20.5G Linux filesystem
> /dev/mmcblk0p3 46874624 121094143 74219520 35.4G Linux filesystem
> 
> Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 63231879-42E8-473D-91DB-FD2CE2FFD6A2
> 
> Device Start   End  Sectors  Size Type
> /dev/sda1   2048   1953791  1951744  953M Linux filesystem
> /dev/sda21953792   5859327  3905536  1.9G Linux RAID
> /dev/sda35859328  48828415 42969088 20.5G Linux filesystem
> /dev/sda4   48828416 123047935 74219520 35.4G Linux filesystem
> /dev/sda5  123047936 130861055  7813120  3.7G Linux swap
> 
> Disk /dev/md0: 1.9 GiB, 1997537280 bytes, 3901440 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes

It seems, that I forgot about the disk-configuration, I tried to have as much 
redundancy
as possible, with the filesystem-/ on md-raid1 (XFS), made with the installer, 
and the
oter two partitions /mnt/bsys and /home with BTRFS-RAID1, made upon first boot, 
all of
them over the internal SD-card and the harddisk.
It is basically workable, as long as I do not upgrade all the software to the 
versions in
backports.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAljI4xwACgkQ5+rBHyUt5ws9JwCgifPddBFTvMY9GP+kIHxvRKrK
6EcAnRCEk6JGIjc65HR6ntNpxKb11HkV
=mrXd
-END PGP SIGNATURE-

Bug#800367: How to say No!! in a polite though ridiculous way

[Andreas Glaeser]

use 
of the term
'mobile'. It means, that is resembles a notebook, and thus the 
openchrome-driver needs to
use the LVDS digital output, which is connected to the integrated LCD-screen.
The other VIA-thin-clients work fine as nano-servers, graphic-output is 
dispensable, but
neoware m100 should probably be used as a mobile-thin-client, because it has an 
integrated
LCD-screen. 
Unfortunately the memory of the device is not really upgradable, because one 
memory-socket
is missing, and the other is connected only half-ways, one-sided. On top of this
limitation, the device lacks USB2-ports, so it is badly, badly below standard, 
and using
it is not really fun, except if you have some retro-computing interests maybe.
To put it at simple terms: I will happily test the Debian-package of 
openchrome-driver on
the device, as they come in, but compiling the driver source-code myself is 
clearly out
of my scope in the context. I would love to help with VIA-driver development,
but currently, I have other higher prioritized things to do, which promise 
better
effectiveness and more overall-impact, so I feel investing my time there just 
makes more
sense and is going to yield more useful, meaningful and relevant results.

Cheers!






 On Mon, 9 Jan 2017 08:53:42 +0100
"Kevin Brace"  wrote:

> Hi Andreas,
> 
> The issue you are having probably is outside of OpenChrome's control.
> There appears to be an issue finding the correct library, and I am not really 
> familiar
> dealing with this kind of a situation. I guess this is called the 
> dependencies issue, I
> suppose. I almost exclusively use Xubuntu / Lubuntu LTS versions for 
> development and
> validation, and obviously, I am able to compile and load OpenChrome without 
> issues. To
> "prove" that Neoware m100 mobile thin client's hardware is compatible with 
> OpenChrome,
> you may want to download, compile, and install the latest OpenChrome code. 
> This post I
> made while back is very detailed, so you should not have issues installing 
> the latest
> OpenChrome code.
> 
> https://lists.freedesktop.org/archives/openchrome-users/2016-February/007237.html
> 
> Regards,
> 
> Kevin Brace
> The OpenChrome Project maintainer / developer
> 
> 
> > Date: Sun, 8 Jan 2017 10:33:04 +0100
> > From: Andreas Glaeser 
> > To: 800...@bugs.debian.org, openchrome-us...@lists.freedesktop.org
> > Subject: [Openchrome-users] installation-report: stretch-testing on
> > NEOWARE m100: no graphics
> > Message-ID: <20170108103304.26e855a8@a68n.lokal>
> > Content-Type: text/plain; charset="utf-8"
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > 
> > There is some improvement visible regarding openchrome video-diver, 
> > particularly,
> > there
> > 
> > is no xorg.conf necessary any more in order to make use of the VESA-driver, 
> > but
> > obviously
> > 
> > X falls back to VESA automatically, which is positive in my opinion, so 
> > people will
> > have
> > 
> > some workable graphics-output, even if openchrome-video-driver is not 
> > workable
> > properly on
> > 
> > their hardware, without fiddling with Xorg-configuration.
> > 
> > See attached logfile [Xorg.0.log]
> > 
> > As far as I can tell, this is the essential part of the log, showing, why 
> > openchrome
> > is not workable yet:
> > 
> > .
> > .
> > ..  
> > > [24.359] (II) LoadModule: "openchrome"
> > > [24.368] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
> > > [24.390] (EE) Failed to
> > > load /usr/lib/xorg/modules/drivers/openchrome_drv.so: 
> > > /usr/lib/xorg/modules/drivers/openchrome_drv.so:
> > > undefined symbol: vgaHWFreeHWRec  
> > [24.393] (II) UnloadModule: "openchrome"  
> > > [24.393] (II) Unloading openchrome
> > > [24.393] (EE) Failed to load module "openchrome" (loader failed, 7)  
> > ..
> > .
> > .
> > 
> > It would be even nicer, guys, if openchrome worked properly on my hardware 
> > instead of
> > falling back to VESA. Now this would really be super-great, get it?
> > 
> > 
> > 
> >   
> > > X.Org X server -- VIA display driver
> > > 
> > > OpenChrome is a project for the development of free and open-source 
> > > drivers for the
> > > VIA UniChrome video chipsets.
> > > 
> > > Originally called the 'snapshot' release, since it was a snapshot of an 
> > > experimental
> > > branch of the unichrome cvs code, this is

Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


There is some improvement visible regarding openchrome video-diver, 
particularly, there

is no xorg.conf necessary any more in order to make use of the VESA-driver, but 
obviously

X falls back to VESA automatically, which is positive in my opinion, so people 
will have

some workable graphics-output, even if openchrome-video-driver is not workable 
properly on

their hardware, without fiddling with Xorg-configuration.

See attached logfile [Xorg.0.log]

As far as I can tell, this is the essential part of the log, showing, why 
openchrome is
not workable yet:

.
.
..
> [24.359] (II) LoadModule: "openchrome"
> [24.368] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
> [24.390] (EE) Failed to
> load /usr/lib/xorg/modules/drivers/openchrome_drv.so: 
> /usr/lib/xorg/modules/drivers/openchrome_drv.so: undefined symbol: 
> vgaHWFreeHWRec
[24.393] (II) UnloadModule: "openchrome"
> [24.393] (II) Unloading openchrome
> [24.393] (EE) Failed to load module "openchrome" (loader failed, 7)
..
.
.

It would be even nicer, guys, if openchrome worked properly on my hardware 
instead of
falling back to VESA. Now this would really be super-great, get it?




> X.Org X server -- VIA display driver
> 
> OpenChrome is a project for the development of free and open-source drivers 
> for the VIA
> UniChrome video chipsets.
> 
> Originally called the 'snapshot' release, since it was a snapshot of an 
> experimental
> branch of the unichrome cvs code, this is a continued development of the open 
> source
> unichrome driver (from http://unichrome.sf.net) which also incorporates 
> support for the
> unichrome-pro chipsets.
> 
> Support for hardware acceleration (XvMC) for all chipsets has subsequently 
> been ripped
> out of the unichrome.sf.net driver. Therefore your only option if you wish to 
> make use
> of the acceleration features of your VIA chip with free and open-source 
> drivers is to
> use this version of the driver.
> 
> Tags: Hardware Enablement: Graphics and Video, Implemented in: C, Role: 
> Plugin,
> Purpose: Hardware Driver Other Packages Related to 
> xserver-xorg-video-openchrome
> 
> depends
> 
>   
> 
> recommends
> 
>   
> 
> suggests
> 
>   
> 
> enhances
> 
> dep: libc6 (>= 2.14) [amd64]
> GNU C Library: Shared libraries
> also a virtual package provided by libc6-udeb 
> 
> dep: libc6 (>= 2.4) [i386]
> 
> dep: libdrm2 (>= 2.3.1)
> Userspace interface to kernel DRM services -- runtime 
> 
> dep: libx11-6 (>= 2:1.4.99.1)
> X11 client-side library 
> 
> dep: libxext6
> X11 miscellaneous extension library 
> 
> dep: libxv1
> X11 Video extension library 
> 
> dep: libxvmc1
> X11 Video extension library 
> 
> dep: xorg-video-abi-23
> virtual package provided by xserver-xorg-core, xserver-xorg-core-udeb 
> 
> dep: xserver-xorg-core (>= 2:1.18.99.901)
> Xorg X server - core server 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlhyB1gACgkQ5+rBHyUt5wvDngCdFSjRLke0PH2QSL9qIAaaFkh4
qV4An1UwX1ghNr0+Y64kl/5KwB4zGSEA
=GmAW
-END PGP SIGNATURE-


Xorg.0.log.xz
Description: application/xz

Bug#739701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739701

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


It probably does not make much sense to keep old wishlist-items.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlhSfVYACgkQ5+rBHyUt5wvR4ACgsr4OM0J5nYZika9Ogq2O2qPY
IZQAoKWfcBw47bNdZDEZVQcfRI2yzwE/
=BDAE
-END PGP SIGNATURE-

Bug#781325: Fw: Closes #781325 - nautilus: file-manager settings regarding behaviour have no effect

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The third possbility is, things remain unfixed, which I do not hope.

Begin forwarded message:

Date: Wed, 14 Dec 2016 16:38:47 +0100
From: Andreas Glaeser 
To: Pedro Beja 
Subject: Re: Closes #781325 - nautilus: file-manager settings regarding 
behaviour have no
effect


- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hello again , 

I have just updated my notebook, which has intel-graphics and I can confirm,

that GNOME3 was not updated yet, and it probably will not be, while Jessie is 
stable.

The bug is definitely still there.

So from my point of view the two remaining possibilities are, that the LTS-team 
provides

fixed packages , when Jessie became oldstable and/or somebody who can, 
packports the

stable GNOME3-version from Stretch to oldstable Jessie.

Great if you know, how to fix this particular issue, but Debian wants to see 
patches,

don't they?

Greetings

A.

P.S: Probably people can work around this particular issue with gconf anyway, 
or by simply
re-using their old home-partitions, but I have e few similar minor bugs, that 
nobody
touches.




On Fri, 2 Dec 2016 18:00:51 +
Pedro Beja  wrote:

> version: 3.22.1-2
> 
> Hi,
> 
> thanks for reporting.
> 
> this issue is fixed in newer versions.
> 
> If you can still reproduce it feel free to reopen and provide more info.
> 
> thanks
> regards
> Pedro Beja  

- -BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlhRZ40ACgkQ5+rBHyUt5wteYQCgvk37SczuZi5gZB/Err68Mljd
V5YAniiFFuIPWqQBSd7J+rwoci7mdO8N
=DDSz
- -END PGP SIGNATURE-
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlhSWE4ACgkQ5+rBHyUt5wv0RgCfVMG874oaQf/CyxjSk9JvqyCT
DkcAoI6sdxv1Lrh5mWFCAvmnhEbahiY9
=cSwE
-END PGP SIGNATURE-

Bug#739701: done

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Not using this box anymore, since unexpectedly it worked without any major 
problem to

port the EWP-appliance to FreeBSD 10.3.

Currently making a clean KVM-image of XEWP in KVM/virt-manager.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlhOTnQACgkQ5+rBHyUt5wu8HACgmDcTwMwyXu6ha5EaqkgFBX5g
OjkAn12zfSAHw5PQT68r4gRr8MFoflfc
=9hUD
-END PGP SIGNATURE-

Bug#840087: PDF-Recompress-script

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hey there, 

I have been sitting down in front of my PC and this is the result [RECOMPDF]:

> #!/bin/bash
> fname=$1  #take input-arguments
> jqual=$2  #first is the filename, second is the 
> JPG-quality-value
> outname="${fname/.pdf}"-low   #strip filename-suffix and add "-low" instead
> mkdir /tmp/recompdf/  #work in /TMP/ directory
> convert -density 300 $fname /tmp/recompdf/split.jpg
> convert /tmp/recompdf/split*.jpg -quality $jqual "$outname".pdf
> rm -R /tmp/recompdf/  #clean up finally
> 

So actually it is none of the PDF-tools, that can help, but imagemagick, which 
is in turn
using ghostscript. Nice ain't it?



-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlgJ35gACgkQ5+rBHyUt5wuEUQCeIboBikWF+H/JhZ9NUSEbdTS4
OYYAnihhjE73+xXCqYMgaNzUfD/09FJP
=6LkO
-END PGP SIGNATURE-

Bug#840087: pdftk's behaviour on my files is identical to the new libreoffice-version

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


PDFTK also leaves the files unchanged, exactly as libreoffice does, another 
possibilty
could be qpdf:

> andrew@a68n:~/Documents/SCAN$ qpdf --help
> 
> Usage: qpdf [ options ] { infilename | --empty } [ outfilename ]
> 
> An option summary appears below.  Please see the documentation for details.
> 
> Note that when contradictory options are provided, whichever options are
> provided last take precedence.
> 
> 
> Basic Options
> -
> 
> --password=password specify a password for accessing encrypted files
> --linearize generated a linearized (web optimized) file
> --copy-encryption=file  copy encryption parameters from specified file
> --encryption-file-password=password
> password used to open the file from which encryption
> parameters are being copied
> --encrypt options --generate an encrypted file
> --decrypt   remove any encryption on the file
> --pages options --  select specific pages from one or more files
> 
> If none of --copy-encryption, --encrypt or --decrypt are given, qpdf will
> preserve any encryption data associated with a file.
> 
> Note that when copying encryption parameters from another file, all
> parameters will be copied, including both user and owner passwords, even
> if the user password is used to open the other file.  This works even if
> the owner password is not known.
> 
> 
> Encryption Options
> --
> 
>   --encrypt user-password owner-password key-length flags --
> 
> Note that -- terminates parsing of encryption flags.
> 
> Either or both of the user password and the owner password may be
> empty strings.
> 
> key-length may be 40, 128, or 256
> 
> Additional flags are dependent upon key length.
> 
>   If 40:
> 
> --print=[yn] allow printing
> --modify=[yn]allow document modification
> --extract=[yn]   allow text/graphic extraction
> --annotate=[yn]  allow comments and form fill-in and signing
> 
>   If 128:
> 
> --accessibility=[yn] allow accessibility to visually impaired
> --extract=[yn]   allow other text/graphic extraction
> --print=print-optcontrol printing access
> --modify=modify-opt  control modify access
> --cleartext-metadata prevents encryption of metadata
> --use-aes=[yn]   indicates whether to use AES encryption
> --force-V4   forces use of V=4 encryption handler
> 
>   If 256, options are the same as 128 with these exceptions:
> --force-V4   this option is not available with 256-bit keys
> --use-aesthis option is always on with 256-bit keys
> --force-R5   forces use of deprecated R=5 encryption
> 
> print-opt may be:
> 
>   full  allow full printing
>   low   allow only low-resolution printing
>   none  disallow printing
> 
> modify-opt may be:
> 
>   all   allow full document modification
>   annotate  allow comment authoring and form operations
>   form  allow form field fill-in and signing
>   assembly  allow document assembly only
>   none  allow no modifications
> 
> The default for each permission option is to be fully permissive.
> 
> Specifying cleartext-metadata forces the PDF version to at least 1.5.
> Specifying use of AES forces the PDF version to at least 1.6.  These
> options are both off by default.
> 
> The --force-V4 flag forces the V=4 encryption handler introduced in PDF 1.5
> to be used even if not otherwise needed.  This option is primarily useful
> for testing qpdf and has no other practical use.
> 
> 
> Page Selection Options
> --
> 
> These options allow pages to be selected from one or more PDF files.
> Whatever file is given as the primary input file is used as the
> starting point, but its pages are replaced with pages as specified.
> 
> --pages file [ --password=password ] [ page-range ] ... --
> 
> For each file that pages should be taken from, specify the file, a
> password needed to open the file (if any), and a page range.  The
> password needs to be given only once per file.  If any of the input
> files are the same as the primary input file or the file used to copy
> encryption parameters (if specified), you do not need to repeat the
> password here.  The same file can be repeated multiple times.  All
> non-page data (info, outlines, page numbers, etc. are taken from the
> primary input file.  To discard this, use --empty as the primary
> input.
> 
> The page range is a set of numbers separated by commas, ranges of
> numbers separated dashes, or combinations of those.  The character
> "z" represents the last page.  Pages can appear in any order.  Ranges
> can appear with a high number followed by a low number, w

Bug#840087: linked images ?

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


No, idea, what linked or embedded images might be in PDF, I guess, it's  rather 
the
latter.

I am simply using simple-scan and save a few pages directly as PDF.

But you are right of course, I can just as well use pdftk for re-compressing 
the stuff:

> andrew@a68n:~$ aptitude show pdftk
> Package: pdftk   
> New: yes
> State: installed
> Automatically installed: no
> Version: 2.02-2
> Priority: optional
> Section: text
> Maintainer: Johann Felix Soden 
> Architecture: amd64
> Uncompressed Size: 3,011 k
> Depends: libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libgcj15 (>= 4.9), libstdc++6 
> (>= 4.4.0)
> Suggests: xpdf-utils
> Description: tool for manipulating PDF documents
>  If PDF is electronic paper, then PDFtk is an electronic stapler-remover, 
> hole-punch,
> binder, secret-decoder-ring, and X-Ray-glasses. PDFtk is a simple tool for 
> doing
> everyday things with PDF documents. Keep one in the top drawer of your 
> desktop and use
> it to: 
>  * Merge PDF documents 
>  * Split PDF pages into a new document 
>  * Decrypt input as necessary (password required) 
>  * Encrypt output as desired 
>  * Fill PDF Forms with FDF Data and/or Flatten Forms 
>  * Apply a Background Watermark 
>  * Report PDF on metrics, including metadata and bookmarks 
>  * Update PDF Metadata 
>  * Attach Files to PDF Pages or the PDF Document 
>  * Unpack PDF Attachments 
>  * Burst a PDF document into single pages 
>  * Uncompress and re-compress page streams 
>  * Repair corrupted PDF (where possible)
> Homepage: http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/
> 
> Tags: implemented-in::c++, implemented-in::java, interface::commandline, 
> role::program,
>   scope::utility, use::converting, use::editing, works-with-format::pdf,
> works-with::text
> 

This might even make myself as a person a less mousy one, especially women would
probably highly appreciate it, if I were larger.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlgB0RAACgkQ5+rBHyUt5wsYIACgjIMjUhts3QbWpOt/Pire4foR
BPkAniLxuNzv0T5x8UXQplmqOAsWVV64
=4Mh5
-END PGP SIGNATURE-

Bug#840087: libreoffice-draw: does not compress PDFs in the latest version

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi, Rene,

the upsteam-discussions are generally often not very helpful in my opinion, if 
you are

not a programmer, it is pretty much like somebody is posting a sentence of 
natural

language for every code-change made. 

It's not helpful, if you don't read the source-code.

They could instead write the comments directly into the code and distribute 
both together,

then things would be much easier for human readers.

Greetings

A.


On Fri, 14 Oct 2016 23:36:31 +0200
Rene Engelhard  wrote:

> On Fri, Oct 14, 2016 at 06:16:56PM +0200, Andreas Glaeser wrote:
> > Yeah, anyway, the problem exists in Stretch, it has nothing to do with
> > stable-dependencies vs. testing-dependencies:  
> 
> Yes, I already said so, basically and marked the bug as-such.
> 
> > Now this should really satisfy your needs for INFO, I will tag the report 
> > 'UPSTREAM'
> > now.  
> 
> No, it doesn't. You still didn't answer the question I asked
> whether you have linked images and whether one of the linked
> bugs apply to your case.
> 
> Tagging it upstream is fine, but no real help (but "telling the obvious".
> It'd more helpful to know the upstream bug to track whether/when it's fixed
> and to give them more information if needed.)
> 
> To quote it again:
> 
> > > > Anyway: When looking in LOs Bugzilla I
> > > > see
> > > > https://bugs.documentfoundation.org/show_bug.cgi?id=101563 (do you use 
> > > > linked
> > > > images?)
> > > > 
> > > >  
>^
> > > > and 
> > > > 
> > > >   
> > > > https://bugs.documentfoundation.org/show_bug.cgi?id=99303   
> > > > 
> > > >   
> > > > (which isn't very useful.)   
> 
> (unanswered question marked with ^'s)
> 
> Regards,
> 
> Rene

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlgByXQACgkQ5+rBHyUt5wsEIgCgvKSYeM7G8TXaXf29Q098CAtH
JE8An25I2o6KJlkV0FLWDSdDQHVNtWiJ
=E1Ae
-END PGP SIGNATURE-

Bug#840087: libreoffice-draw: does not compress PDFs in the latest version

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 12 Oct 2016 15:53:48 +0200
Rene Engelhard  wrote:

> Hi,
> 
> On Wed, Oct 12, 2016 at 03:10:47PM +0200, Andreas Glaeser wrote:
> > If I am getting things correctly, the backported version is identical with 
> > the one in
> > Stretch/testing, so the same bug would be there, it migrated there in fact 
> > from
> > unstable  
> 
> In this case, yes..
> 
> Other bugs can be only appearing on backports.
> 

This one does not, I have just checked that, in a KVM-VM, see there:

840...@bugs.debian.org

> And no, it is not identical. If it was there was no need for a backport. It's 
> a rebuild
> (with changed dependencies and any adaptions needed) to work in stable.
> (And it's from testing, not unstable.)
> 
> > and if nobody complains or otherwise nobody feels responsible to react to 
> > the report,
> > it will inevitably migrate to stable.  
> 
> Yes, the testing version. Not *-backports. And that only on the next release.
> -backports is not a staging ground for updates in "real" stable. It's 
> separate.
> 

Ah-ha !

> > > > there appeared a new version of the LibreOffice suite from Backports 
> > > > today.
> > > > LibreOffice-Draw fails to compress multipage-PDFs, it just makes a copy 
> > > > of the
> > > > original document, regardless of the quality- and other settings.
> > > > I use this function quite frequently, so I can tell, the problem 
> > > > appeared
> > > > _today_.
> > > 
> > > So between 5.1.5 and 5.2.2. Very helpful. Another reason why bug reporting
> > > should be done on sid, so one knows what happens when, not only when the
> > > thing is (supposedly) stable enough to get into backports.
> > >   
> > Sorry, I am not using unstable, I never have in fact, I think the version 
> > in testing
> > is usually new enough, except, there is currently a freeze-phase on the
> > testing-branch.  
> 
> No, there isn't a freeze yet in testing. That only starts in some time. If 
> there was,
> 5.2.2 would not have migrated there in the first place and thus there 
> wouldn't be a
> backport of 5.2.2 anyways.
> 

Yeah, anyway, the problem exists in Stretch, it has nothing to do with
stable-dependencies vs. testing-dependencies:

> user@stretchtst:~$ aptitude show libreoffice
> Package: libreoffice 
> Version: 1:5.2.2~rc2-2


> > > Anyway: When looking in LOs Bugzilla I see
> > > https://bugs.documentfoundation.org/show_bug.cgi?id=101563
> > > (do you use linked images?)
> > > and
> > > https://bugs.documentfoundation.org/show_bug.cgi?id=99303
> > > (which isn't very useful.)
> > > 
> > > based on theupstream reports I set the version accordingly to a existing
> > > version. (And tag it moreinfo.)
> > >   
> > Was this enough info or not??  
> 
> No, since you didn't answer any question here. E.g. the question in the cited
> part above.
> 

Now this should really satisfy your needs for INFO, I will tag the report 
'UPSTREAM' now.

Greetings

A.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlgBBRsACgkQ5+rBHyUt5wvunwCgoGKudo1ivSmMpmxsQ32ZOioS
VikAn0gWyvUVfWz6SffV9pRj5TMtFMnv
=g6xY
-END PGP SIGNATURE-

Bug#840720: installation-report: stretch/testing setup inside qemu/kvm with virt-manager

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.62
Severity: wishlist

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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: iso-img
Image version:
http://gensho.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2016-10-13

Machine: kvm vm, see attachment
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs500520   0500520   0% /dev
tmpfs  tmpfs   1020283420 98608   4% /run
/dev/vda1  xfs   11523072 3138444   8384628  28% /
tmpfs  tmpfs   510132  68510064   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   510132   0510132   0% /sys/fs/cgroup
tmpfs  tmpfs   102024  12102012   1% /run/user/1000
tmpfs  tmpfs   102024   4102020   1% /run/user/109



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

This is actually not an installer-problem, but one with libvirt or virt-manager
respectively, there is fix necessary in order to be able to start up existing 
virtual
machines:
This is the problem:
> Error starting domain: Requested operation is not valid: network 'default' is 
> not active
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in 
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 127, in tmpcb
> callback(*args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in startup
> self._backend.create()
>   File "/usr/lib/python2.7/dist-packages/libvirt.py", line 999, in create
> if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: Requested operation is not valid: network 'default' is not 
> active

This is the fix:

> root@dop58:/home/remosrv# cd /etc/libvirt/qemu/networks/autostart
> root@dop58:/etc/libvirt/qemu/networks/autostart# ln -s ../default.xml 
> default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# ls -la
> total 4
> drwxr-xr-x 1 root root 22 Oct 10 13:48 .
> drwxr-xr-x 1 root root 40 Oct 10 13:45 ..
> lrwxrwxrwx 1 root root 14 Oct 10 13:48 default.xml -> ../default.xml
> root@dop58:/etc/libvirt/qemu/networks/autostart# cat default.xml 
> 
>   default
>   
>   
>   
> 
>   
> 
>   
> 
> 
> root@dop58:/etc/libvirt/qemu/networks/autostart# service libvirtd restart

I also disabled the bridge-netfilter, now I am able to log in to the host with 
SSH,
see: 

> $$ man sysctl.d

VM-configuration attached, also kernel-bootup messages [dmesg-output]

There is a message at bootup. saying that hardware-support for kvm is missing 
inside the
guest, so this would most probably require nested virtualisation, the other 
issue is,
that there is a 90 seconds grace-period at startup while systemd waits for
Network-Manager, which ist not really required inside a VM.

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20161003-00:06"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux stretchtst 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 (2016-09-26) 
x86_64
GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 
82441FX PMC
[Natoma] [8086:1237] (rev 02) lspci -knn:   Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB 
PIIX3 ISA
[Natoma/Triton II] [8086:7000] lspci -knn:  Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB 
PIIX3 IDE
[Natoma/Triton II

Bug#840087: libreoffice-draw: does not compress PDFs in the latest version

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, 10 Oct 2016 09:32:34 +0200
Rene Engelhard  wrote:

> found 840087 1:5.2.2~rc2-2
> tag 840087 + moreinfo
> thanks
> 
> Hi,
> 
> On Sat, Oct 08, 2016 at 10:17:20AM +0200, Andreas Glaeser wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Package: libreoffice-draw
> > Version: 1:5.2.2~rc2-2~bpo8+1  
> 
> No. There's a reason backports bug get redirected to debian-backports as
> the BTS is NOT for bpo bugs.  It does not help very much that you try to be
> smart and CC submit@bugs
> 
> See https://backports.debian.org/FAQ/, point 1.
> 
> It does not even know the version and thinks it affects everything
> (see 
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=stable;package=libreoffice-draw)
> (Yes, it says From other Branch bugs, but it appears open)
> 
If I am getting things correctly, the backported version is identical with the 
one in
Stretch/testing, so the same bug would be there, it migrated there in fact from 
unstable
and if nobody complains or otherwise nobody feels responsible to react to the 
report, it
will inevitably migrate to stable.

> > there appeared a new version of the LibreOffice suite from Backports today.
> > LibreOffice-Draw fails to compress multipage-PDFs, it just makes a copy of 
> > the
> > original document, regardless of the quality- and other settings.
> > I use this function quite frequently, so I can tell, the problem appeared 
> > _today_.  
> 
> So between 5.1.5 and 5.2.2. Very helpful. Another reason why bug reporting
> should be done on sid, so one knows what happens when, not only when the
> thing is (supposedly) stable enough to get into backports.
> 
Sorry, I am not using unstable, I never have in fact, I think the version in 
testing is
usually new enough, except, there is currently a freeze-phase on the 
testing-branch.

> > If there is nothing done about this, I will have to downgrade the software 
> > to the
> > normal stable version 4 again.  
> 
> Sorry, this is complete nonsense. Either it's "minor", then it's exactly that
> and there's no need to revert. Or it's more. (BTW, stretch will contain
> 5.2.x in any way.)
> 
I have downgraded my packages already agin, this is how I got rid of the 
problem:

> andrew@a68n:~$ aptitude show libreoffice
> Package: libreoffice 
> State: installed
> Automatically installed: no
> Version: 1:4.3.3-2+deb8u5
> Priority: optional
> Section: metapackages
> Maintainer: Debian LibreOffice Maintainers 
> 
> Architecture: amd64
> Uncompressed Size: 159 k
> Depends: fonts-sil-gentium-basic, libreoffice-base, libreoffice-calc, 
> libreoffice-core
> (= 1:4.3.3-2+deb8u5), libreoffice-draw, libreoffice-impress,
 libreoffice-math, libreoffice-report-builder-bin, libreoffice-writer,
libreoffice-avmedia-backend-gstreamer | libreoffice-avmedia-backend-vlc,
>  fonts-dejavu, libreoffice-java-common (>= 1:4.3.3~), python3-uno (>= 
> 4.0~) |
> python-uno
Recommends: fonts-liberation | ttf-mscorefonts-installer, libpaper-utils
> Suggests: cups-bsd, hunspell-dictionary, hyphen-hyphenation-patterns, 
> iceweasel |
> firefox | icedove | thunderbird | iceape-browser | mozilla-browser,
  imagemagick | graphicsmagick-imagemagick-compat, libgl1, 
libreoffice-gnome |
libreoffice-kde, libreoffice-grammarcheck, libreoffice-help-4.3,
>   libreoffice-l10n-4.3, libsane, libxrender1, myspell-dictionary,
> mythes-thesaurus, openclipart-libreoffice, pstoedit, unixodbc,
>
  gstreamer1.0-plugins-base, gstreamer1.0-plugins-good,
gstreamer1.0-plugins-ugly, gstreamer1.0-plugins-bad, gstreamer1.0-ffmpeg, 
default-jre |
gcj-jre
>   | openjdk-7-jre | openjdk-6-jre | sun-java5-jre | sun-java6-jre |
> java5-runtime | jre, libreoffice-officebean   
>  
Description: office productivity suite
(metapackage)   

>  LibreOffice is a full-featured office productivity suite that provides a 
> near drop-in
> replacement for Microsoft(R) Office.

   
>  This metapackage installs all components of
> libreoffice:  
> 
>  * libreoffice-writer: Word
> processor   

Bug#840087: libreoffice-draw: does not compress PDFs in the latest version

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: libreoffice-draw
Version: 1:5.2.2~rc2-2~bpo8+1
Severity: minor

Dear Maintainer,

there appeared a new version of the LibreOffice suite from Backports today.
LibreOffice-Draw fails to compress multipage-PDFs, it just makes a copy of the 
original
document, regardless of the quality- and other settings.
I use this function quite frequently, so I can tell, the problem appeared 
_today_.
If there is nothing done about this, I will have to downgrade the software to 
the normal
stable version 4 again.


- -- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.36-adt (SMP w/3 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice-draw depends on:
ii  dpkg1.17.27
ii  libavahi-client30.6.31-5
ii  libavahi-common30.6.31-5
ii  libc6   2.19-18+deb8u6
ii  libcdr-0.1-10.1.0-3
ii  libdbus-1-3 1.8.20-0+deb8u1
ii  libdbus-glib-1-20.102-1
ii  libfreehand-0.1-1   0.1.0-2
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.48.0-1~bpo8+1
ii  libicu5252.1-8+deb8u3
ii  liblcms2-2  2.6-3+b3
ii  libmspub-0.1-1  0.1.1-2
ii  libmwaw-0.3-3   0.3.1-2
ii  libodfgen-0.1-1 0.1.1-2
ii  libpagemaker-0.0-0  0.0.1-1
ii  libreoffice-core1:5.2.2~rc2-2~bpo8+1
ii  librevenge-0.0-00.0.1-3
ii  libstdc++6  4.9.2-10
ii  libvisio-0.1-1  0.1.0-2
ii  libwpd-0.10-10  0.10.0-2+b1
ii  libwpg-0.3-30.3.0-3
ii  libxml2 2.9.1+dfsg1-5+deb8u3
ii  uno-libs3   5.2.2~rc2-2~bpo8+1
ii  ure 5.2.2~rc2-2~bpo8+1
ii  zlib1g  1:1.2.8.dfsg-2+b1

libreoffice-draw recommends no packages.

libreoffice-draw suggests no packages.

Versions of packages libreoffice-core depends on:
ii  fontconfig 2.11.0-6.3+deb8u1
ii  fonts-opensymbol   2:102.7+LibO5.2.2~rc2-2~bpo8+1
ii  libboost-date-time1.55.0   1.55.0+dfsg-3
ii  libboost-filesystem1.55.0  1.55.0+dfsg-3
ii  libboost-iostreams1.55.0   1.55.0+dfsg-3
ii  libboost-system1.55.0  1.55.0+dfsg-3
ii  libc6  2.19-18+deb8u6
ii  libcairo2  1.14.0-2.1+deb8u1
ii  libclucene-contribs1   2.3.3.4-4
ii  libclucene-core1   2.3.3.4-4
ii  libcups2   1.7.5-11+deb8u1
ii  libcurl3-gnutls7.38.0-4+deb8u4
ii  libdbus-1-31.8.20-0+deb8u1
ii  libdbus-glib-1-2   0.102-1
ii  libdconf1  0.22.0-1
ii  libeot00.01-3
ii  libexpat1  2.1.0-6+deb8u3
ii  libexttextcat-2.0-03.4.4-1
ii  libfontconfig1 2.11.0-6.3+deb8u1
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgcc11:4.9.2-10
ii  libgl1-mesa-glx [libgl1]   12.0.3-1~bpo8+1
ii  libglew1.101.10.0-3
ii  libglib2.0-0   2.48.0-1~bpo8+1
ii  libglu1-mesa [libglu1] 9.0.0-2
ii  libgraphite2-3 1.3.6-1~deb8u1
ii  libharfbuzz-icu0   0.9.35-2
ii  libharfbuzz0b  0.9.35-2
ii  libhunspell-1.3-0  1.3.3-3
ii  libhyphen0 2.8.8-1
ii  libice62:1.0.9-1+b1
ii  libicu52   52.1-8+deb8u3
ii  libjpeg62-turbo1:1.3.1-12
ii  liblangtag10.5.1-3
ii  liblcms2-2 2.6-3+b3
ii  libldap-2.4-2  2.4.40+dfsg-1+deb8u2
ii  libmythes-1.2-02:1.2.4-1
ii  libneon27-gnutls   0.30.1-1
ii  libnspr4   2:4.12-1+debu8u1
ii  libnss32:3.26-1+debu8u1
ii  libodfgen-0.1-10.1.1-2
ii  libpng12-0 1.2.50-2+deb8u2
ii  librdf01.0.17-1+b1
ii  libreoffice-common 1:5.2.2~rc2-2~bpo8+1
ii  librevenge-0.0-0   0.0.1-3
ii  libsm6 2:1.2.2-1+b1
ii  libssl1.0.01.0.2j-1~bpo8+1
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxext6   2:1.3.3-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.1+dfsg1-5+deb8u3
ii  libxrandr2 2:1.4.2-1+b1
ii  libxrender11:0.9.8-1+b1
ii  libxslt1.1 1.1.28-2+deb8u1
ii  uno-libs3  5.2.2~rc2-2~bpo8+1
ii  ure5.2.2~rc2-2~bpo8+1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages libreoffice-core recommends:
ii  libpaper-utils  1.1.24+nmu4

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlf4q5cACgkQ5+rBHyUt5wt2NgCcC1s2CjooJjPvtDBvUfJw3LNJ
E+4AoL/D2CLq9OooLLkPKPx3wm9RjXVL
=aG0G
-END PGP SIGNATURE-

Bug#781325: Fw: [Bug 766557] nautilus: file-manager settings regarding behaviour have no effect

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Begin forwarded message:

Date: Tue, 27 Sep 2016 12:11:34 +
From: "nautilus" (GNOME Bugzilla) 
To: bugs.andreas.glae...@freenet.de
Subject: [Bug 766557] nautilus: file-manager settings regarding behaviour have 
no effect


https://bugzilla.gnome.org/show_bug.cgi?id=766557

Ernestas Kulik  changed:

   What|Removed |Added
- 
 Status|NEW |RESOLVED
 CC||ernest...@src.gnome.org
 Resolution|--- |OBSOLETE

- --- Comment #2 from Ernestas Kulik  ---
Feel free to reopen if the problem persists in a newer version.

- -- 
You are receiving this mail because:
You reported the bug.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlfyaUAACgkQ5+rBHyUt5wskvgCdFMXBft7jMWqMFyxsBmNKeQUc
iGkAnR5Fm0zmW4m+4pWykWcmASLsXfQm
=2Rjy
-END PGP SIGNATURE-


 Ernestas Kulik
 changed
  bug 766557
  
 
  
What
Removed
Added
  

 
   Status
   NEW
   
   RESOLVED
   
 

 
   CC
   
    
   
   ernestask@src.gnome.org
   
 

 
   Resolution
   ---
   
   OBSOLETE
   
 
  

Comment # 2
  on bug 766557
  from  Ernestas Kulik

Feel free to reopen if the problem persists in a newer version.

  
  
  You are receiving this mail because:
  
  
  You reported the bug.
  

Bug#834821: e17: File-Manager crashes with Single-Click setting when opening folders

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: e17
Version: 0.17.6-1
Severity: minor

Dear Maintainer,

e17 had filemanager-problems for quite some time, I think they were fixed in 
the 32-bit
version first, also seems to work OK in the AMD64-version now, but the problem 
is still
there, when using the 'Single-Click'-setting for File-Manager, see attached 
screenshot. I
also failed to open a subfolder of /home/user/ for choosing a Wallpaper-image, 
the
system also crashed there.

- -- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt25-adt (SMP w/3 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e17 depends on:
ii  dbus-x11   1.8.20-0+deb8u1
ii  e17-data   0.17.6-1
ii  libasound2 1.0.28-1
ii  libc6  2.19-18+deb8u4
ii  libdbus-1-31.8.20-0+deb8u1
ii  libecore-con1  1.8.6-2.1+b2
ii  libecore-evas1 1.8.6-2.1+b2
ii  libecore-file1 1.8.6-2.1+b2
ii  libecore-imf1  1.8.6-2.1+b2
ii  libecore-input11.8.6-2.1+b2
ii  libecore-ipc1  1.8.6-2.1+b2
ii  libecore-x11.8.6-2.1+b2
ii  libecore1  1.8.6-2.1+b2
ii  libedbus1  1.7.10-1
ii  libedje-bin1.8.6-2.1+b2
ii  libedje1   1.8.6-2.1+b2
ii  libeet11.8.6-2.1+b2
ii  libeeze1   1.8.6-2.1+b2
ii  libefreet-bin  1.8.6-2.1+b2
ii  libefreet1a1.8.6-2.1+b2
ii  libeina1   1.8.6-2.1+b2
ii  libeio11.8.6-2.1+b2
ii  libevas1   1.8.6-2.1+b2
ii  libevas1-engines-x [libevas1-engine-software-x11]  1.8.6-2.1+b2
ii  libpam0g   1.1.8-3.1+deb8u1+b1
ii  libxcb-keysyms10.4.0-1
ii  libxcb-shape0  1.10-3+b1
ii  libxcb11.10-3+b1

Versions of packages e17 recommends:
ii  pm-utils  1.4.1-15

e17 suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAle3AQYACgkQ5+rBHyUt5wu08gCgj8fVxbWTy+MR5WfXqn4j5Gyc
9jcAniE9DzKyDcGvmKOnS32bVDBzdqwG
=Ww3E
-END PGP SIGNATURE-

Bug#819867: there is another upstream-report related to this issue

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

http://savannah.gnu.org/bugs/?43379
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcrTssACgkQ5+rBHyUt5wsFmACeMxkpcBkfZaCkzpd7zgS+sAlT
O8IAn05Qp+dUe/mPwk/CrQZf6UA7tPuQ
=am2+
-END PGP SIGNATURE-

Bug#819867: boot also fails with non-USB boot-partition

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Today I retried this with the current netinstall-image from 2016-05-02,
using the internal ATA-flash-memory of the PC as /boot/-partition, but it 
doesn't work
either, since GRUB cannot mount the filesystem-root.
It might be related to these upstream-bugs:

http://savannah.gnu.org/bugs/?35937  

http://savannah.gnu.org/bugs/?38366:

> # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux 
> GRUB_DISABLE_LINUX_UUID="true" 
> # JPT: use uuid, label or partition 
> GRUB_USE_PARTIDTYPE="label" 

so it might actually be misconfiguration only.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcrSz8ACgkQ5+rBHyUt5wtTGACgiiU7mCxtO22CQZnsYqHc9huK
b48An06KByHEE2q6nYtZ3+ITQAbE48YR
=2NqI
-END PGP SIGNATURE-

Bug#819867: bug-report filed against the grub-pc package now

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


see there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820806

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcNDUIACgkQ5+rBHyUt5wtdcACgoln5wrsPp2QTy+iZu3jV2XWG
fV4AoJEU7MMMDewbKGv4Pq9LkeZZ71Eu
=QpyN
-END PGP SIGNATURE-

Bug#765552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765552

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Since your installation-report was from before the Jessie-release, the issue 
has probably

been fixed in the meantime.

If so, then please close the report-ticket yourself by sending e-mail to:

765552-d...@bugs.debian.org

giving a few explanatory words, why you think, it does not need to be kept open 
longer.

Also feel free to try out the current testing-branch of software.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcHuAsACgkQ5+rBHyUt5wsIjgCfeIQlFOPm1JV6tIZYk6NNuiyw
kI8An1hNdZCbfPsEXGs97krFxNX3pkG+
=g/dD
-END PGP SIGNATURE-

Bug#762840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762840

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Can you retry with the current stable release or with current debian-testing??

Possibly you need to set the BIOS to legacy mode, some UEFI-implementations are 
buggy.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcHtpIACgkQ5+rBHyUt5wstbgCfbGNlNyQrE73ZGMlaj5sqKJPp
B7wAoJZS5BhMLas4jbxzdc2DNVOj2R92
=y6E7
-END PGP SIGNATURE-

Bug#753947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753947

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


What about your report??

Did you still experience any problems, when Jessie was released stable ??

Or with the current testing-branch ??

If you think the problem is resolved in the meanwhile, you can close the ticket 
yourself

by sending E-mail to:

753947-d...@bugs.debian.org

giving a quick explanation, why you think, the report should be closed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcHs/sACgkQ5+rBHyUt5wtsZQCgnMG4D3yjDrnxuOk0lhXxmrpZ
FIYAoIlQXwPWWaZ8s3easEv9rzSMY0Ll
=ri7z
-END PGP SIGNATURE-

Bug#755230: closed by Andreas Glaeser

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 6 Apr 2016 12:15:57 -0700
Andrew Kurn  wrote:

> Dear Andreas,
> 
> In my turn, I don't understand how to work around a non-bootable
> installer image.  Believe me, I booted the way I did because it
> was the only way I could think of.
> 
> "Nowadays" is the important word IMHO in your answer. I'm working
> with old hardware and, so, I have the opinion that old hardware
> is important and should be considered when bringing out new
> releases.
> 
> One reason that people might prefer free software (as in beer)
> is because they don't have much money.
> 
> When you say:
> > I forwarded your message to the respective bug-report.  
> 
> do you mean to a list working especially on documentation?
> That's my hope.
> 
> Good wishes,
> Andrew


It is quite illusionary in my opinion, when people think they can save lots of 
money, by

having old servers run literally forever, until they break and have to be 
thrown away.

The opposite is true, because of the poor energy-efficiency of the old 
hardware, the

energy-costs exceed the cost of buying something new, that's more or less up to 
date and

at least provides proper efficiency. In some IT-departments they probably think,

electricity-expenses are none of their business, but overall it is a waste of 
resources,

especially for systems with lots of uptime, nonetheless.

Here in Germany you can currently get (used) 64-bit thin-clients (featuring 
HD-audio),

p-rated 2100+ MHz, that use about 20 W of energy at about EUR 20,- (I am not 
talking

about a monthly fee here).

That's why it doesn't really make sense to keep servers from the Pentium-II-age 
up

and running. If a Nano-server is insufficient for your purposes and you need 
features

like RAID, you can still take a Micro-server, that is essentially built from

notebook-components.

32-bit Software is going to die out in the long term, i386-support was removed 
already

in recent Linux-kernels, i486 is the minimum now, you also find it in some 
embedded

devices so it's probably going to continue for a while.

Greetings 

Andreas

P.S. you could also file a report against the debian-reference package, say 
your proposal
is wishlist for instance.

[This] bug-report is there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755230





 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlcGJmYACgkQ5+rBHyUt5wvb/QCgvsJxH1Fr1Cot/l250g0RYRVT
jwoAn1KuhYauwh3zfjvHVd2h3JASIfck
=Uuqr
-END PGP SIGNATURE-

Bug#755230: closed by Andreas Glaeser

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hello, there,

I forwarded your message to the respective bug-report.
In my opinion the workaround, which I don't fully understand to be honest, does 
not have
much relevance for the PC-platform, since most BIOSes do boot from USB 
nowadays, often
even from USB3, but it might be useful for ARM or other architectures, i.e. 
it's probably
easier to work around the non-bootable installer-image than bootstrapping 
manually or
building an image otherwise.
You can post your proposal to the debian-users mailing-list or to
debian-boot and point to the installation-report.

Greetings 

Andreas



On Wed, 6 Apr 2016 10:06:34 +0200
Andreas Glaeser  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> 
> Begin forwarded message:
> 
> Date: Tue, 5 Apr 2016 12:08:08 -0700
> From: Andrew Kurn 
> To: bugs.andreas.glae...@freenet.de
> Subject: Re: Bug#755230 closed by Andreas Glaeser
> 
> 
> Thanks for your attention to this matter.
> 
> I agree with you that there is no need to treat this as a program
> bug.  However, the documentation could use some attention.
> 
> I don't know where else to send such a request, and the Debian installer
> does ask for a report of difficulties.
> 
> So, to someone updating the installation documentation, I would say:
> 1) Mention that the ISO image might not boot from FRS.
> 2) This might be got around using the method I mention (citing
> the section telling what's needed to boot.)
> 3) Explain that a symlink might be needed to /media if the ISO
> image is in an unexpected place.
> 4) Add citation of 5.4.7 for those using an alternative to direct e-mail
> in section A.4
> 
> 
> Again, I don't minimize your work as a volunteer.  You are
> due much appreciation for your effort.
> 
> Andrew
> 
> 
> 
> 
> On Mon  4 Apr 2016 13:21 +, Debian Bug Tracking System wrote:
> 
> 
> > This is an automatic notification regarding your Bug report
> > which was filed against the installation-reports package:
> > 
> > #755230: report
> > 
> > It has been closed by Andreas Glaeser .
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Andreas Glaeser
> >  by replying to this email.
> > 
> > 
> > -- 
> > 755230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755230
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> 
> Received: (at 755230-done) by bugs.debian.org; 4 Apr 2016 13:18:57 +
> X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
>   (2014-02-07) on buxtehude.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-1.9 required=4.0 tests=BAYES_00,DIGITS_LETTERS,
>   
> FOURLA,FREEMAIL_FROM,FVGT_m_MULTI_ODD,MIME_BASE64_TEXT,RCVD_IN_DNSWL_LOW,
>   RP_MATCHES_RCVD autolearn=no autolearn_force=no
>   version=3.4.0-bugs.debian.org_2005_01_02
> X-Spam-Bayes: score:0. Tokens: new, 27; hammy, 112; neutral, 35; spammy,
>   3. spammytokens:0.997-1--H*r:78.55.108, 0.993-1--sjz6, 
> 0.987-1--H*r:33079
>   hammytokens:0.000-+--H*UA:sk:x86_64-, 0.000-+--H*x:sk:x86_64-,
>   0.000-+--H*UA:2.24.25, 0.000-+--H*x:2.24.25, 0.000-+--GnuPG
> Return-path: 
> Received: from mout0.freenet.de ([2001:748:100:40::2:2])
>   by buxtehude.debian.org with esmtps 
> (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
>   (Exim 4.84_2)
>   (envelope-from )
>   id 1an4PB-0003ZI-F5
>   for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 13:18:57 +
> Received: from [195.4.92.140] (helo=mjail0.freenet.de)
>   by mout0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
> (port 25)
> (Exim 4.85 #1) id 1an4P8-0003eo-SF
>   for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:18:54 +0200
> Received: from localhost ([::1]:34008 helo=mjail0.freenet.de)
>   by mjail0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
> (Exim 4.85
> #1) id 1an4P8-00028u-Lp
>   for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:18:54 +0200
> Received: from mx16.freenet.de ([195.4.92.26]:54654)
>   by mjail0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
> (Exim 4.85
> #1) id 1an4N9-BL-Es
>   for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:16:51 +0200
> Received: from x4e376c49.dyn.telefonica.de ([78.55.108.73]:33079 
> helo=a68n.lokal)
>   by mx16.freenet.de with esmtpsa (ID bugs.andreas.glae...@freenet.de)
> (TLSv1.2:AES128-GCM-SHA256:128) (port 587) (Exim 4.85 #1) id 1an4N9-0002CX-9D
>   for 75

Bug#755230: Fw: Bug#755230 closed by Andreas Glaeser

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Begin forwarded message:

Date: Tue, 5 Apr 2016 12:08:08 -0700
From: Andrew Kurn 
To: bugs.andreas.glae...@freenet.de
Subject: Re: Bug#755230 closed by Andreas Glaeser


Thanks for your attention to this matter.

I agree with you that there is no need to treat this as a program
bug.  However, the documentation could use some attention.

I don't know where else to send such a request, and the Debian installer
does ask for a report of difficulties.

So, to someone updating the installation documentation, I would say:
1) Mention that the ISO image might not boot from FRS.
2) This might be got around using the method I mention (citing
the section telling what's needed to boot.)
3) Explain that a symlink might be needed to /media if the ISO
image is in an unexpected place.
4) Add citation of 5.4.7 for those using an alternative to direct e-mail
in section A.4


Again, I don't minimize your work as a volunteer.  You are
due much appreciation for your effort.

Andrew




On Mon  4 Apr 2016 13:21 +, Debian Bug Tracking System wrote:


> This is an automatic notification regarding your Bug report
> which was filed against the installation-reports package:
> 
> #755230: report
> 
> It has been closed by Andreas Glaeser .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Andreas Glaeser
>  by replying to this email.
> 
> 
> -- 
> 755230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755230
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Received: (at 755230-done) by bugs.debian.org; 4 Apr 2016 13:18:57 +
X-Spam-Checker-Version: SpamAssassin 3.4.0-bugs.debian.org_2005_01_02
(2014-02-07) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=4.0 tests=BAYES_00,DIGITS_LETTERS,

FOURLA,FREEMAIL_FROM,FVGT_m_MULTI_ODD,MIME_BASE64_TEXT,RCVD_IN_DNSWL_LOW,
RP_MATCHES_RCVD autolearn=no autolearn_force=no
version=3.4.0-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0. Tokens: new, 27; hammy, 112; neutral, 35; spammy,
3. spammytokens:0.997-1--H*r:78.55.108, 0.993-1--sjz6, 
0.987-1--H*r:33079
hammytokens:0.000-+--H*UA:sk:x86_64-, 0.000-+--H*x:sk:x86_64-,
0.000-+--H*UA:2.24.25, 0.000-+--H*x:2.24.25, 0.000-+--GnuPG
Return-path: 
Received: from mout0.freenet.de ([2001:748:100:40::2:2])
by buxtehude.debian.org with esmtps 
(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.84_2)
(envelope-from )
id 1an4PB-0003ZI-F5
for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 13:18:57 +
Received: from [195.4.92.140] (helo=mjail0.freenet.de)
by mout0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
(port 25)
(Exim 4.85 #1) id 1an4P8-0003eo-SF
for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:18:54 +0200
Received: from localhost ([::1]:34008 helo=mjail0.freenet.de)
by mjail0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
(Exim 4.85
#1) id 1an4P8-00028u-Lp
for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:18:54 +0200
Received: from mx16.freenet.de ([195.4.92.26]:54654)
by mjail0.freenet.de with esmtpa (ID bugs.andreas.glae...@freenet.de) 
(Exim 4.85
#1) id 1an4N9-BL-Es
for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:16:51 +0200
Received: from x4e376c49.dyn.telefonica.de ([78.55.108.73]:33079 
helo=a68n.lokal)
by mx16.freenet.de with esmtpsa (ID bugs.andreas.glae...@freenet.de)
(TLSv1.2:AES128-GCM-SHA256:128) (port 587) (Exim 4.85 #1) id 1an4N9-0002CX-9D
for 755230-d...@bugs.debian.org; Mon, 04 Apr 2016 15:16:51 +0200
Date: Mon, 4 Apr 2016 15:15:38 +0200
From: Andreas Glaeser 
To: 755230-d...@bugs.debian.org
Subject: no need to keep this report open
Message-ID: <20160404151538.3a6c8dd2@a68n.lokal>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: base64
X-Originated-At: 78.55.108.73!33079
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> 
> Your feedback is appreciated, although it lacks a speaking message-subject.
> 
> You write, you were able to resolve the problem yourself and it doesn't 
> really seem to
> be a problem in Debian, but one with the BIOS of your computer, that makes the
> installer-image not bootable from USB.
> 
> So I think it is safe to close this issue.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iEYEARECAAYFAlcCaPoACgkQ5+rBHyUt5wsXYACeImVuLgyzSpDGRP2dIeq4clyG
> XNMAoK4dHQD+V/5wbGMi8h2Z3rOOwbe0
> =Sjz6
> -END PGP SIGNATURE-

Received: (at submit) by bugs.debian.org; 18 Jul 2014 22:37:56 +
X-Spam-Che

Bug#819867: installation-report: USB-boot fails with Stretch, no GRUB-installation with BTRFS-partition

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.62
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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: local netinstall-image
Image version: 2016-03-28,
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2016-04-02, about 12.00 h

Machine: KVM with vm-manager
Partitions: 
Filesystem Type 1K-blocks   Used Available Use% Mounted on
udev   devtmpfs500856  0500856   0% /dev
tmpfs  tmpfs   102076   1732100344   2% /run
/dev/vda1  btrfs  6835200 933704   5263640  16% /
tmpfs  tmpfs   510376  0510376   0% /dev/shm
tmpfs  tmpfs 5120  0  5120   0% /run/lock
tmpfs  tmpfs   510376  0510376   0% /sys/fs/cgroup
tmpfs  tmpfs   102076  0102076   0% /run/user/0

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:

This problem was discussed already at the debian-boot mailing-list in this 
thread:
https://lists.debian.org/debian-boot/2016/03/msg00340.html
Today I told myself, it would be a good way of officially opening a ticket for 
this, to
report the installation inside KVM/virt-manager, now here it is.
Steve McIntire suggested, I debug this myself, but I think, that really the D-I 
team
needs to do something to fix this for everyone, so I include the verbose output 
of
lsinitramfs [initramfs.txt.gz] and dmesg [dmesg.txt.gz], more info to come, 
maybe.
I did another Stretch installation on a different device on Compact-Flash card 
in the
meantime, that also worked with BTRFS-root, it's actually for trying out LXC1.1

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20160328-00:05"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux str-tst 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma]
[8086:1237] (rev 02) lspci -knn:Subsystem: Red Hat, Inc Device 
[1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton
II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE
[Natoma/Triton II] [8086:7010] lspci -knn:  Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113]
(rev 03) lspci -knn:Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL 
paravirtual
graphic card [1b36:0100] (rev 04) lspci -knn:   Subsystem: Red Hat, Inc Device
[1af4:1100] lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc Virtio 
network
device [1af4:1000] lspci -knn:  Subsystem: Red Hat, Inc Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6
Family) High Definition Audio Controller [8086:2668] (rev 01) lspci -knn:
Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn: 00:05.0 USB controller 
[0c03]:
Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 
03) lspci
- -knn: Subsystem: Red Hat, Inc Device [1af4:1100] lspci -knn:  Kernel
driver in use: uhci_hcd lspci -knn: Kernel modules: uhci_hcd
lspci -knn: 00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB
UHCI Controller #2 [8086:2

Bug#786873: Fw: Openchrome-users Digest, Vol 30, Issue 6

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Begin forwarded message:

Date: Sat, 26 Mar 2016 15:52:27 +
From: openchrome-users-requ...@lists.freedesktop.org
To: openchrome-us...@lists.freedesktop.org
Subject: Openchrome-users Digest, Vol 30, Issue 6


Send Openchrome-users mailing list submissions to
openchrome-us...@lists.freedesktop.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freedesktop.org/mailman/listinfo/openchrome-users
or, via email, send a message with subject or body 'help' to
openchrome-users-requ...@lists.freedesktop.org

You can reach the person managing the list at
openchrome-users-ow...@lists.freedesktop.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openchrome-users digest..."


Today's Topics:

   1. New openchrome driver -version appeared in    Debian-testing
  (Andreas Glaeser)


- --

Message: 1
Date: Sat, 26 Mar 2016 16:35:23 +0100
From: Andreas Glaeser 
To: openchrome-us...@lists.freedesktop.org
Subject: [Openchrome-users] New openchrome driver -version appeared in
Debian-testing
Message-ID: <20160326163523.3629560d@a68n.lokal>
Content-Type: text/plain; charset=US-ASCII

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Openchrome-driver was removed from testing a while ago, today I found, there is 
actually
a new one:
> Package: xserver-xorg-video-openchrome
> State: installed
> Automatically installed: no
> Version: 1:0.3.3+git20160310-1
> Priority: optional
> Section: x11
> Maintainer: Debian X Strike Force 
> Architecture: i386
> Uncompressed Size: 584 k
> Depends: libc6 (>= 2.1.3), libdrm2 (>= 2.3.1), libx11-6 (>= 2:1.4.99.1),
>  libxext6, libxv1, libxvmc1, xorg-video-abi-20, xserver-xorg-core (>=
>  2:1.17.99.902)
> Provides: xorg-driver-video
> Description: X.Org X server -- VIA display driver
>  OpenChrome is a project for the development of free and open-source drivers 
> for
>  the VIA UniChrome video chipsets. 
>  
>  Originally called the 'snapshot' release, since it was a snapshot of an
>  experimental branch of the unichrome cvs code, this is a continued 
> development
>  of the open source unichrome driver (from http://unichrome.sf.net) which also
>  incorporates support for the unichrome-pro chipsets. 
>  
>  Support for hardware acceleration (XvMC) for all chipsets has subsequently 
> been
>  ripped out of the unichrome.sf.net driver. Therefore your only option if you
>  wish to make use of the acceleration features of your VIA chip with free and
>  open-source drivers is to use this version of the driver.
> Homepage: https://www.freedesktop.org/wiki/Openchrome/
> Tags: hardware::video, implemented-in::c, role::plugin,
> use::driver 

I filed some bugs already in the Debian BTS regarding the openchrome-driver 
with some
thin-clients of mine, this particular problem appears with a mobile 
thin-client, that
fails to show any graphics, only the external VGA-screen works, and I think the 
situation
is widely unchanged with the new driver-version, just it doesn't point to 
openchrome.org
anymore, it has a VM800 chipset:

> [23.756] 
> X.Org X Server 1.18.2
> Release Date: 2016-03-11
> [23.757] X Protocol Version 11, Revision 0
> [23.757] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian
> [23.757] Current Operating System: Linux m100 4.4.0-1-686-pae #1 SMP 
> Debian 4.4.6-1
> (2016-03-17) i686
[23.757] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1-686-pae
root=UUID=1fd1c268-3803-45bf-b597-169e87e17e4a ro quiet
> [23.758] Build Date: 12 March 2016  07:32:54AM
> [23.758] xorg-server 2:1.18.2-1 (http://www.debian.org/support) 
> [23.758] Current version of pixman: 0.33.6
> [23.758]  Before reporting problems, check http://wiki.x.org
>   to make sure that you have the latest version.
> [23.758] Markers: (--) probed, (**) from config file, (==) default 
> setting,
>   (++) from command line, (!!) notice, (II) informational,
>   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [23.759] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 26 11:00:42 
> 2016
> [23.766] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> [23.774] (==) No Layout section.  Using the first Screen section.
> [23.774] (==) No screen section available. Using defaults.
> [23.774] (**) |-->Screen "Default Screen Section" (0)
> [23.774] (**) |   |-->Monitor ""
> [23.780] (==) No monitor specified for screen "Default Screen Section".
>   Using a default monitor configuration.
> 

Bug#814088: Be cautious about data-loss !!

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


This obviously has been a low-priority project, but I have the box basically up 
and
running now.

If you have a similar scenario as myself, with an external harddisk with data 
on it, that
you want to integrate into a RAID and use as network-storage, don't do it the 
way, I did
it, transferring the data over NFS and then trying to set up the RAID straight 
away.

I lost half of my data that way, because balancing the data over the two disks 
failed due
to read-errors, there were 300+ of them on the new internal SATA-disk, that had 
only 24
hours of operation-time yet. The extended long SMART selftest's result was 
that, the
disk-health is basically good, so actually the failure may be due to bad karma 
mainly and
carelessness.
So I zeroed out the whole drive with dd and tried again, now it seems to work 
well enough.
I set it up the same way and checked, the problem was not due to misaligned 
partitions,
which was not the case, although it's an advanced format disk with 4k blocks, 
cfdisk did
the partitioning job quite well, that was checked on afterwards with parted.

If you have data you cannot afford to lose, connect the external USB-disk 
directly to the
NAS-box and transfer the data manually on the terminal using SSH, not with the 
graphical
file-manager of your choice, say '$ cp -av .. ..' for instance.
Then balance the data on the internal drive in order to check for errors:
#  btrfs balance start -v /mnt/sata

If that goes well, you are most probably fine to add the external disk to the 
RAID and
re-balance it as RAID1:
#  btrfs device add -f /dev/sdd1 /mnt/sata/
#  btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/sata/

When spreading out the existing data over the two devices is finished, you can 
start
populating the disk with other data over NFS, I did a reboot first.

One problem, which actually appeared chronologically first is the question about
permissions. I introduced a special group for network-storage on the NAS and 
wanted to
add users on the network, who are allowed to write on it to that same group 
with the same
GID, but that doesn't work over NFS. If you need something like it, you may 
have to deal
with NFS-ACLs and the package fs4-acl-tools on the clients:

> Package: nfs4-acl-tools  
> State: not installed
> Version: 0.3.3-2.1
> Priority: extra
> Section: admin
> Maintainer: Anibal Monsalve Salazar 
> Architecture: amd64
> Uncompressed Size: 104 k
> Depends: libattr1 (>= 1:2.4.46-8), libc6 (>= 2.14)
> Description: Commandline and GUI ACL utilities for the NFSv4 client
>  This package contains commandline and GUI ACL utilities for the Linux NFSv4 
> client.
> Homepage: http://www.citi.umich.edu/projects/nfsv4/linux/

But since I essentially have a single-user network and since NFS-ACLs are 
beyond LPIC-2
level, I simply used my primary UID and GID on the NAS and mapped root-access 
to the
network-storage group only, which works just fine.





-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlblhVUACgkQ5+rBHyUt5wu5igCdHhj5VhUeMbw3XrkbWKKugzH5
fuwAn1Bbicvn32S2j3vR/O1K/H2p2/AJ
=D2I4
-END PGP SIGNATURE-

Bug#738631: Some problems seem to get never solved

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Dear maintainers, 
I closed the issue in the first place in order to tell you, how
extremely disappointed I was about your behaviour, to consistently ignore me.
Now I changed my mind, I think the BTS should actually rather reflect, what's 
really going
on with the binaries, not some emotional considerations.
I am reopening the report, because I think, also small details _do_ matter. 
CentOS for
example released version 7.2, also including GNOME 3.14, and most likely they 
fixed this
issue in their distribution, it _really_ does have security-implications, when 
users
cannot lock their screen, when leaving the work-place, I mean it in a practical 
way, not
technically, of course they could also log out of their sessions, but it takes 
longer
and it is less convenient.
Another small detail is this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781325

I am not using GNOME anymore on my main PC, also not on the secondary PC, but I 
am still
using it once per week on my notebook, so I know, the bugs are still there.

Besides this _very_ bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738631

The problems are, that GNOME does not work over x2go, not even in classic-mode, 
it
_does_not_work_at_all_ and GNOME3.14 fails to work with the FGLRX proprietary
RADEON-driver. I am not planning to stick with fglrx anyway, I just wanted to 
tell you
guys, though,

enjoy!

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlaTx5wACgkQ5+rBHyUt5wvXNACfWhcIwstW1Ubdp60wEC+Bzr2L
kCcAnilpWs3tcXejqo3kaoHAv0RO0I6X
=lEvk
-END PGP SIGNATURE-

Bug#801511: VESA not workable, VIA-driver not workable either

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I tried to use the VESA-driver, putting [xorg.conf.xz] in place, it was not 
workable, see
[Xorg.0.log.vesa],
the VIA-driver does not work for me either:

> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# ./vinstall
> error: tool "make" missed!
> Please use command: "apt-get install make" to install make.
> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# aptitude install make
> The following NEW packages will be installed:
>   make 
> 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 349 kB of archives. After unpacking 1,326 kB will be used.
> Get: 1 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main make 
> amd64
> 4.0-8.1 [349 kB] Fetched 349 kB in 0s (1,198 kB/s)
> Selecting previously unselected package make.
> (Reading database ... 112067 files and directories currently installed.)
> Preparing to unpack .../make_4.0-8.1_amd64.deb ...
> Unpacking make (4.0-8.1) ...
> Processing triggers for man-db (2.7.0.2-5) ...
> Setting up make (4.0-8.1) ...
>  
> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# ./vinstall
> error: tool "gcc" missed!
> Please use command: "apt-get install gcc" to install gcc.
> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# aptitude install gcc
> The following NEW packages will be installed:
>   gcc gcc-4.9{a} libasan1{a} libcilkrts5{a} libgcc-4.9-dev{a} liblsan0{a} 
> libubsan0{a} 
> 0 packages upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
> Need to get 7,834 kB of archives. After unpacking 29.9 MB will be used.
> Do you want to continue? [Y/n/?] 
> Get: 1 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main 
> libasan1 amd64
> 4.9.2-10 [195 kB] Get: 2 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ 
> jessie/main
> libcilkrts5 amd64 4.9.2-10 [40.1 kB] Get: 3
> http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main liblsan0 amd64 
> 4.9.2-10
> [92.8 kB] Get: 4 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ 
> jessie/main
> libubsan0 amd64 4.9.2-10 [82.4 kB] Get: 5
> http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main libgcc-4.9-dev 
> amd64
> 4.9.2-10 [2,066 kB] Get: 6 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/
> jessie/main gcc-4.9 amd64 4.9.2-10 [5,352 kB] Get: 7
> http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main gcc amd64 
> 4:4.9.2-2
> [5,136 B] Fetched 7,834 kB in 2s (3,552 kB/s) Selecting previously unselected 
> package
> libasan1:amd64. (Reading database ... 112109 files and directories currently
> installed.) Preparing to unpack .../libasan1_4.9.2-10_amd64.deb ... Unpacking
> libasan1:amd64 (4.9.2-10) ... Selecting previously unselected package
> libcilkrts5:amd64. Preparing to unpack .../libcilkrts5_4.9.2-10_amd64.deb ... 
> Unpacking
> libcilkrts5:amd64 (4.9.2-10) ... Selecting previously unselected package 
> liblsan0:amd64.
> Preparing to unpack .../liblsan0_4.9.2-10_amd64.deb ...
> Unpacking liblsan0:amd64 (4.9.2-10) ...
> Selecting previously unselected package libubsan0:amd64.
> Preparing to unpack .../libubsan0_4.9.2-10_amd64.deb ...
> Unpacking libubsan0:amd64 (4.9.2-10) ...
> Selecting previously unselected package libgcc-4.9-dev:amd64.
> Preparing to unpack .../libgcc-4.9-dev_4.9.2-10_amd64.deb ...
> Unpacking libgcc-4.9-dev:amd64 (4.9.2-10) ...
> Selecting previously unselected package gcc-4.9.
> Preparing to unpack .../gcc-4.9_4.9.2-10_amd64.deb ...
> Unpacking gcc-4.9 (4.9.2-10) ...
> Selecting previously unselected package gcc.
> Preparing to unpack .../gcc_4%3a4.9.2-2_amd64.deb ...
> Unpacking gcc (4:4.9.2-2) ...
> Processing triggers for man-db (2.7.0.2-5) ...
> Setting up libasan1:amd64 (4.9.2-10) ...
> Setting up libcilkrts5:amd64 (4.9.2-10) ...
> Setting up liblsan0:amd64 (4.9.2-10) ...
> Setting up libubsan0:amd64 (4.9.2-10) ...
> Setting up libgcc-4.9-dev:amd64 (4.9.2-10) ...
> Setting up gcc-4.9 (4.9.2-10) ...
> Setting up gcc (4:4.9.2-2) ...
> Processing triggers for libc-bin (2.19-18+deb8u1) ...
>  
> root@t5550:~/5.76.52.92-l140402_32bit-005f78-20150730# ./vinstall
> install the via driver!
> ..ln: failed to access ‘/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1’: Not a 
> directory
> ln: failed to access ‘/usr/lib/x86_64-linux-gnu/mesa/libGL.so’: Not a 
> directory
> ...WARNING: Real kenel verison(132608) is different from verison
> in /usr/include/linux/verison(200711). ..done!
> Original X config file was saved as /etc/X11/xorg.conf.viabak
> Caution!!
> Need reboot the system!
> ..
> ..
> (not workable)
> ..
> ..
> root@t5550:~# aptitude install libgl1-mesa-dev
> The following NEW packages will be installed:
>   libdrm-dev{a} libgl1-mesa-dev libpthread-stubs0-dev{a} libx11-dev{a} 
> libx11-doc{a} 
>   libx11-xcb-dev{a} libxau-dev{a} libxcb-dri2-0-dev{a} libxcb-dri3-dev{a}
> libxcb-glx0-dev{a} libxcb-present-dev{a} libxcb-randr0{a} libxcb-randr0-dev{a}
> libxcb-render0-d

Bug#801511: installation-report: Jessie-stable set up for testing graphics-driver

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/debian-cd/8.2.0/multi-arch/iso-cd/debian-8.2.0-amd64-i386-netinst.iso
Date: 2015-10-19, about 14.30 h to 15.30 h

Machine: HP t5550 thin-client
Partitions: 
Filesystem Type 1K-blocks   Used Available Use% Mounted on
/dev/sdb1  btrfs 13670400 831664  10806288   8% /
udev   devtmpfs 10240  0 10240   0% /dev
tmpfs  tmpfs   385500   5268380232   2% /run
tmpfs  tmpfs   963740  0963740   0% /dev/shm
tmpfs  tmpfs 5120  0  5120   0% /run/lock
tmpfs  tmpfs   963740  0963740   0% /sys/fs/cgroup

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

Today I tried to update this machine, which failed because of 
secur...@debian.org
blocking.
So I disabled security in apt/sources.list and updated anyway, it left me with a
non-workable system upon reboot, that did not allow any login because of the
constantly flashing screen it showed.
Then I tried about three times to reinstall Testing, which failed twice with 
BTRFS and
once on XFS filesystem.
The situation is basically the same as about one year ago, before the 
Jessie-freeze, when
GRUB was not workable and left the installed system unbootable, but this time 
there seems
to be some script involved called 'local-block', so I clearly will not report 
this as a
GRUB-bug.
On one hand it doesn't make much sense anyway to test the beta-graphics-driver 
from
VIA-linux-portalfor Ubuntu 15.04 on Stretch-testing, because the Ubuntu-version 
resembling
this, would rather be 15.10, which is not out yet, I think.
Nonetheless my system-upgrades should not be blocked by secur...@debian.org, 
because I
didn't commit any abuse or other violation of any sort.



- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u2"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux t5550 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 
(2015-08-04)
x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. 
VX900
Host Bridge: Host Control [1106:0410] (rev 80) lspci -knn:  Subsystem: VIA
Technologies, Inc. VX900 Host Bridge: Host Control [1106:0410] lspci -knn: 
00:00.1 Host
bridge [0600]: VIA Technologies, Inc. VX900 Error Reporting [1106:1410] lspci 
-knn:
Subsystem: VIA Technologies, Inc. VX900 Error Reporting [1106:1410] 
lspci -knn:
00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX900 CPU Bus Controller 
[1106:2410]
lspci -knn: Subsystem: VIA Technologies, Inc. VX900 CPU Bus Controller
[1106:2410] lspci -knn: 00:00.3 Host bridge [0600]: VIA Technologies, Inc. 
VX900 DRAM Bus
Control [1106:3410] lspci -knn: Subsystem: VIA Technologies, Inc. VX900 
DRAM Bus
Control [1106:3410] lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, 
Inc. VX900
Power Management and Chip Testing Control [1106:4410] lspci -knn:   
Subsystem: VIA
Technologies, Inc. VX900 Power Management and Chip Testing Control [1106:4410] 
lspci
- -knn: 00:00.5 Host bridge [0600]: VIA Technologies, Inc. VX900 APIC and 
Central Traffic
Control [1106:5410] lspci -knn: Subsystem: VIA Technologies, Inc. VX900 
APIC and
Central Traffic Control [1106:5410] lspci -knn: 00:00.6 Host bridge [0600]: VIA
Technologies, Inc. VX900 Scratch Registers [1106:6410] lspci -knn:  
Subsystem: VIA
Technologies, Inc. VX900 Scratch Registers [1106:6410] lspci -knn: 00:00.7 Host 
bridge
[0600]: VIA Technologies, Inc. VX900 North-South Modu

Bug#786873: More info on Chrome-graphics

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


see a new report there:

801...@bugs.debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYad84ACgkQ5+rBHyUt5wtgZwCcDitk0YeGr5sYrldIJEupWrnm
luAAoKNtre1wLJ/irjJ8KcSQMUZcylyP
=yECd
-END PGP SIGNATURE-

Bug#801511: installation-report: no graphics on HP t5550 thin-client w/ stretch-testing

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: installation-reports
Version: 2.60
Severity: minor

Dear Maintainer,

graphics are still not workable, see attached file [Xorg.0.log.xz].
I was using a DVI-to-VGA adapter here, because only my main screen is digital, 
the others
are VGA only.
I installed Jessie-stable for someone else on an IGEL-m300c thin-client, he 
said, he had
graphics there only with a DVI-VGA adapter, but he wanted digital output. In 
the end he
was quite happy with the VESA-graphics driver, it'S OK on some devices, when 
you don't
have special needs regarding performance. 
Concerning this I did some research and found the VIA-linux portal, it seems 
they offer
linux-drivers there for newer devices, also including source-code, it might 
work on this
one with VX900-chipset, I'll have to try that out.


- -- Package-specific info:

Boot method: USB
Image version:
http://saimei.acc.umu.se/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2015-10-05
Date: 2015-10-11, about 14.00h to 15.00h.

Machine: HP t 5550 thin-client
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   1783885008173380   3% /run
/dev/sdb1  btrfs 13670400 4323396   7497436  37% /
tmpfs  tmpfs   445968  92445876   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   445968   0445968   0% /sys/fs/cgroup
tmpfs  tmpfs89196   8 89188   1% /run/user/116
tmpfs  tmpfs89196   0 89196   0% /run/user/0


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[n][no graphics]

Comments/Problems:

I did this installation only for testing-purposes, I want to try out the 
graphics-driver
from VIA. When that is done, I am going to install FreeBSD on it, that worked 
well enough
for me on HP t5540, so it should work on this one as well.
I hope FreeBSD and ZFS are able to couple an SATA-harddrive and a USB-hdd into 
one
RAID-device, because that's exactly the plan for building my own NAS-box 
without the
danger of data-loss, and retry it as CUPS-printserver.
When that is done, I am planning to do a 64-bit version of DEWP, I am waiting 
for the
backport of LXC 1.1 in fact, it would allow for an implementation, that is 
independent
from oldstable, if that doesn't come in time, maybe take the version from 
testing
directly??.

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20151005-00:03"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux t5550 4.1.0-2-amd64 #1 SMP Debian 4.1.6-1 (2015-08-23) x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX900 Host 
Bridge: Host
Control [1106:0410] (rev 80) lspci -knn:Subsystem: VIA Technologies, 
Inc. VX900
Host Bridge: Host Control [1106:0410] lspci -knn: 00:00.1 Host bridge [0600]: 
VIA
Technologies, Inc. VX900 Error Reporting [1106:1410] lspci -knn:
Subsystem: VIA
Technologies, Inc. VX900 Error Reporting [1106:1410] lspci -knn: 00:00.2 Host 
bridge
[0600]: VIA Technologies, Inc. VX900 CPU Bus Controller [1106:2410] lspci -knn:
Subsystem: VIA Technologies, Inc. VX900 CPU Bus Controller [1106:2410] lspci 
-knn:
00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX900 DRAM Bus Control 
[1106:3410]
lspci -knn: Subsystem: VIA Technologies, Inc. VX900 DRAM Bus Control 
[1106:3410]
lspci -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX900 Power 
Management and
Chip Testing Control [1106:4410] lspci -knn:Subsystem: VIA Technologies, 
Inc.
VX900 Power Management and Chip Testing Control [1106:4410] lspci -knn: 00:00.5 
Host
bridge [0600]: VIA Technologies, Inc. VX900 APIC and Central Traffic Control 
[1106:5410]
lspci -knn: Subsystem: VIA Technologies, Inc. VX900 APIC and Central Traffic
Control [1106:5410] lspci -knn: 00:00.6 Host bridge [0600]: VIA Technologies, 
Inc. VX900
Scratch Registers [11

Bug#801491: youtube-dl: does not work on Soundcloud.com, please check

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: youtube-dl
Version: 2015.06.04.1-1
Severity: minor

Dear Maintainer,

I tried to use youtube-dl on Soundcloud.com:

> andrew@a68n:~$ youtube-dl -v
> https://soundcloud.com/gillespeterson/gilles-peterson-dj-set-precious-hall-japan-5th-oct-2015
> [debug] System config: [] [debug] User config: []
> [debug] Command-line args: [u'-v',
> u'https://soundcloud.com/gillespeterson/gilles-peterson-dj-set-precious-hall-japan-5th-oct-2015']
> [debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8 [debug] 
> youtube-dl
> version 2015.06.04.1 [debug] Python version 2.7.9 -
> Linux-4.1.6-adl-x86_64-with-debian-8.2 [debug] exe versions: avconv 11.4-6, 
> avprobe
> 11.4-6, rtmpdump 2.4 [debug] Proxy map: {}
> [soundcloud] 
> gillespeterson/gilles-peterson-dj-set-precious-hall-japan-5th-oct-2015:
> Resolving id [soundcloud]
> gillespeterson/gilles-peterson-dj-set-precious-hall-japan-5th-oct-2015: 
> Downloading
> info JSON ERROR: Unable to download JSON metadata: HTTP Error 401: 
> Unauthorized (caused
> by HTTPError()); please report this issue on https://yt-dl.org/bug . Make 
> sure you are
> using the latest version; see  https://yt-dl.org/update  on how to update. Be 
> sure to
> call youtube-dl with the --verbose flag and include its complete output. File
> "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 312, 
> in
> _request_webpage return self._downloader.urlopen(url_or_request) File
> "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 1730, in 
> urlopen
> return self._opener.open(req, timeout=self._socket_timeout) File
> "/usr/lib/python2.7/urllib2.py", line 437, in open response = meth(req, 
> response) File
> "/usr/lib/python2.7/urllib2.py", line 550, in http_response 'http', request, 
> response,
> code, msg, hdrs) File "/usr/lib/python2.7/urllib2.py", line 475, in error 
> return
> self._call_chain(*args) File "/usr/lib/python2.7/urllib2.py", line 409, in 
> _call_chain
> result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 558, in
> http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> 

I's not workable. I used Iceweasel's inspector instead and looked at the 
network-tab,
copied the file-URL from there and could download it with wget:

> wget
> https://ec-media.sndcdn.com/PqqpdYUj66tt.128.mp3?f10880d39085a94a0418a7ef69b03d522cd6dfee9399eeb9a52205986bfeb73fc52f83f573e11f44be4da0fbde89cc04819be69876eb8f071849add4f42ff6024d9b45185f

It works perfectly fine for me, the only problem there is the cryptic filename 
that needs
to be changed, it also didn't download slowly, but at 3+ MB/s.

I really don't know whether this is too difficult to do it by script, if so 
then please
remove Soundcloud from the list of supported sites. 


- -- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.6-adl (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages youtube-dl depends on:
ii  python2.7.9-1
ii  python-pkg-resources  5.5.1-1
pn  python:any

Versions of packages youtube-dl recommends:
ii  curl7.38.0-4+deb8u2
ii  libav-tools 6:11.4-1~deb8u1
ii  mplayer2 [mplayer]  2.0-728-g2c378c7-4+b1
ii  rtmpdump2.4+20150115.gita107cef-1
ii  wget1.16-1

youtube-dl suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYaD9kACgkQ5+rBHyUt5wsvBwCfSvIc0qYFWw7PVFCk7cwFO7ai
1wEAnjJ12cISYvcImi72RZGwqVsGrjpN
=XmQj
-END PGP SIGNATURE-

Bug#800674: closed by Ben Hutchings (Re: Bug#800674: Embedded feature with SLOB-allocation fails, no boot)

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 03 Oct 2015 01:06:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is still not the right place to report bugs in SLOB, nor to ask
> for support with configuring your kernel.  Please stop doing this.
> 
> Ben.
> 
> -- 

I was not asking for support regarding kernel-configuration, I guess nobody 
would.
It's pretty much like if you don't know how to configure the kernel-source, you 
clearly
have no need to build your own custom kernel.

I start wondering though, why I am constantly receiving negative replies from 
you,
because you have to give *some*explanation* on ticket-close?

It's not ridiculous at all, but, well _*negative*_.

I want to give you an expample now of how to formulate this in a positive way.

Thanks a lot, dear reporter, we appreciate you are donating some of your 
precious time in
order to improve our distribution, we will take the necessary steps to make 
proper use
of the information you supplied.

Or:

Sorry, dear reporter, this and that are the right places to report your problem.

Got it?? Be positive !
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYSEZUACgkQ5+rBHyUt5wsUDgCfct6rkfdBNcgV1L92VasXiQy2
flEAnRFRu/HMeYpSewnckwtP5Zhd14M/
=heMR
-END PGP SIGNATURE-

Bug#800674: Embedded feature with SLOB-allocation fails, no boot

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: linux-source-4.1
Version: 4.1.6-1
Severity: normal

Dear Maintainer,

this is the follow-up report to:
 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800154

I reconfigured and built from linux-source-4.1 now, but the situation actually 
seems to
be worse here, boot-process hangs very early, so I cannot even provide any 
dmesg-output,
it's not workable at all.

This is unrelated, but since I reported this:

786...@bugs.debian.org

I saw the download of the index-files from the backports-repository fail quite 
often.

DoS is a form of communication, but it's not positive, folks!





- -- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.6-adl (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source-4.1 depends on:
ii  binutils  2.25-5
ii  bzip2 1.0.6-7+b3

Versions of packages linux-source-4.1 recommends:
ii  bc1.06.95-9
ii  gcc   4:4.9.2-2
ii  libc6-dev [libc-dev]  2.19-18+deb8u1
ii  make  4.0-8.1

Versions of packages linux-source-4.1 suggests:
pn  libncurses-dev | ncurses-dev  
pn  libqt4-dev
ii  pkg-config0.28-1

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYOUkIACgkQ5+rBHyUt5wsp1wCgkWxpMSFn1idwc6KPJzEgN6MP
TlEAn0HU0jPEhnLxlVR1YInLT9lSgI2O
=54vQ
-END PGP SIGNATURE-


config-4.1.6-aedl.xz
Description: application/xz

Bug#786873: Openchrome Project-Homepage: http://www.openchrome.org

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Today I visited the Openchrome-Project Homepage, the Debian-package description 
contains a
link there:

> andrew@a68n:~$ aptitude show xserver-xorg-video-openchrome
> Package: xserver-xorg-video-openchrome   
> State: installed
> Automatically installed: yes
> Version: 1:0.3.3-1+b2
> Priority: optional
> Section: x11
> Maintainer: Debian X Strike Force 
> Architecture: amd64
> Uncompressed Size: 536 k
> Depends: libc6 (>= 2.14), libdrm2 (>= 2.3.1), libx11-6 (>= 2:1.4.99.1), 
> libxext6,
> libxv1, libxvmc1, xorg-video-abi-18, xserver-xorg-core (>= 2:1.15.99.903)
> Provides: xorg-driver-video
> Description: X.Org X server -- VIA display driver
>  OpenChrome is a project for the development of free and open-source drivers 
> for the
> VIA UniChrome video chipsets. 
>  
>  Originally called the 'snapshot' release, since it was a snapshot of an 
> experimental
> branch of the unichrome cvs code, this is a continued development of the open 
> source
> unichrome driver (from http://unichrome.sf.net) which also incorporates 
> support for the
> unichrome-pro chipsets. 
>  Support for hardware acceleration (XvMC) for all chipsets has subsequently 
> been ripped
> out of the unichrome.sf.net driver. Therefore your only option if you wish to 
> make use
> of the acceleration features of your VIA chip with free and open-source 
> drivers is to
> use this version of the driver. Homepage: http://www.openchrome.org
> 
> Tags: hardware::video, implemented-in::c, role::plugin, use::driver
> 

The Site is obviously down, showing the picture of a kid holding a message, not 
to hate
it, because it's muslim. That's why I changed the severity of this ticket to 
important.
In my opinion it is a clear sign of neglect, when the Webpage of the project is 
down, I
am not referring to that kid.
OK, acknowledged, Islam itself is not evil, but what does that weird message 
displayed
there have to do with Openchrome??
I hope some of the package-maintainers have the means to inform those in charge 
of the
project site, in order to set this straight again.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYKY8gACgkQ5+rBHyUt5wu/xwCgqow3spAvrvEuFhQqQnngPPRG
aMkAoILJhkayXSpOQhhzAzf61kYk5W28
=Szu0
-END PGP SIGNATURE-

Bug#786873: Follow up-report for NEOWARE m100

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

see there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800367
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYJTCsACgkQ5+rBHyUt5wuLRwCff0lVMx0auclOHbxDJj+FdT3B
LZgAnj/0pcIe9wUIbxUKu92GbAGK908o
=8UPa
-END PGP SIGNATURE-

Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: installation-reports
Version: 2.60
Severity: minor

Dear Maintainer,

I still have to use VESA-graphics.


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso,
2015-09-28
Date: 
2015-09-28, about 11.00h to 15.00h

Machine: NEOWARE m100 mobile thin-client
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs986684636 94032   5% /run
/dev/sda1  btrfs 13670400 3476368   8246224  30% /
tmpfs  tmpfs   246668   0246668   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   246668   0246668   0% /sys/fs/cgroup
tmpfs  tmpfs49336   4 49332   1% /run/user/113
tmpfs  tmpfs49336   0 49336   0% /run/user/0

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

I ordered a CF-to-IDE adapter and a 16GB CF-card from Hongkong, both arrived 
much sooner
than expected.
Now I fitted both into the mobile thinclient, which was tricky, because the 
drive-bay is
made for harddisks, which makes it difficult to fit the much smaller adapter 
with CF-card
in place. I didn't want to take apart the device, so I made my own tool for 
that from two
wood-sticks, an old CF-card, two rubber-rings and some adhesive tape, 
resembling tongs.
Using that it went quite well.
Installation was interrupted, because I was unaware, the client was running on 
batteries,
which ran out at some point. This caused more problems with installing 
task-xfce-desktop
and task-laptop, it would not work with tasksel anymore because of the 
interruption, only
with aptitude, then some dependency-troubles showed up, which were gone again 
upon system
reboot.
It' positive, that it's possible to go without the proprietary firmware now, 
even without
any non-free packages, but openchrome still does not work for me, as reported 
already
there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786873

the version in stable is: 1:0.3.3-1+b2, stretch has 1:0.3.3-1+b3

The X-server logfiles are attached [Xorg.0.log.openchrome.xz] and 
[Xorg.0.log.vesa.xz].

I continue using xorg.conf for VESA now, it is also attached [xorg.conf.xz].

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20150927-00:34"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux m100 4.1.0-2-586 #1 Debian 4.1.6-1 (2015-08-23) i686 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro
Host Bridge [1106:0314] lspci -knn: Subsystem: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:0314] lspci -knn:Kernel driver in
use: agpgart-via lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:1314] lspci -knn: 00:00.2 Host 
bridge [0600]:
VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:2314] lspci 
-knn:
00:00.3 Host bridge [0600]: VIA Technologies, Inc. PT890 Host Bridge 
[1106:3208] lspci
- -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro Host
Bridge [1106:4314] lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, 
Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:7314] lspci -knn: 00:01.0 PCI bridge 
[0604]:
VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198] lspci -knn: 00:0b.0 
CardBus
bridge [0607]: Texas Instruments PCI1510 PC card Cardbus Controller [104c:ac56] 
lspci
- -knn: Subsystem: Packard Bell B.V. Device [1631:c018] lspci -knn: 
Kernel
driver in use: yenta_cardbus lspci -knn: 00:0c.0 Network controller [0280]: 
Ralink corp.
RT2561/RT61 rev B 802.11g [1814:0302] lspci -knn:   Subsystem: Device 
[18e8:6194]
lspci -knn: Kernel driver in use: rt61pci lspci -knn: 00:0f.0 IDE interface
[0101]: VIA Technologies, I

Bug#800154: closed by Ben Hutchings (Re: Bug#800154: linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems)

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

O> This is an automatic notification regarding your Bug report
> which was filed against the linux-source package:
> 
> #800154: linux-source: custom built embedded kernel with slob-allocation runs 
> too
> unstable, boot-problems
> 
> It has been closed by Ben Hutchings .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings
>  by replying to this email.
> 
> 
> -- 
> 800154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800154
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 
> From: Ben Hutchings 
> To: 800154-d...@bugs.debian.org
> Subject: Re: Bug#800154: linux-source: custom built embedded kernel with
> slob-allocation runs too unstable, boot-problems Date: Sun, 27 Sep 2015 
> 18:27:46 +0100
> X-Mailer: Evolution 3.16.5-1 
> 
> Then don't use CONFIG_SLOB.  We're certainly not going to do anything
> to fix it.
> 
> Ben.
> 
> -- 
> Ben Hutchings
> I say we take off; nuke the site from orbit.  It's the only way to be sure.

Oh, well, 

I understand it's not Debian's problem, but my PC is an embedded system, so in 
principle

the embedded feature and SLOB should definitely work.

So should I take action myself in order to forward this upstream ??

Greetings

Andreas

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYJQEIACgkQ5+rBHyUt5wuU0QCgkiXaN75ku3X2D5xP8KuAf01Q
KAEAn09r0xq9C+N6g5+dLmsyfOL2RcNr
=uOiB
-END PGP SIGNATURE-

Bug#800154: linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: linux-source
Version: 3.16+63
Severity: normal

Dear Maintainer,

I have been using the custom aedl-kernel [config-3.16.7-ckt11-aedl.xz] on my 
dualcore
thin-client and tried to continue using it on my new PC, but it is not really 
workable.
It's behaving in an unstable way, for example when copying the contents of one 
compressed
BTRFS-partition to another one, it panicked. More often that, there are 
boot-problems,
especially upon a kernel-panic reboot hangs almost every time, it may be 
connected with
the LZO-compressed root-partition, but that normally works.
I rebuilt the kernel, leaving the
embedded-feature away and using slub instead [config-3.16.7-ckt11-adll.xz], it 
seems to be
doing well so far. I also compared that with the stock-kernel using 
phoronix-test-metrics,
but at least in the complex system test, there is not very much gain. This may 
be due to
the test being a non-interactive server-test mostly. Personally and 
subjectively I prefer
custom built AMD low-latency-kernels on the desktop, because, they make the 
system feel
more responsive.

The original installation-report was posted there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800127



- -- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt11-aedl (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
ii  linux-source-3.16  3.16.7-ckt11-1+deb8u4

linux-source recommends no packages.

linux-source suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlYH9KQACgkQ5+rBHyUt5wt7OgCgkG15BhgxyaBDd+OVb+FVNvg4
ITQAoIiv+9GlrKGdp+sa/z+ZXdiaTMbx
=qBSU
-END PGP SIGNATURE-


dmsg.txt.xz
Description: application/xz


config-3.16.7-ckt11-adll.xz
Description: application/xz


config-3.16.7-ckt11-aedl.xz
Description: application/xz

Bug#800127: installation-report: Jessie stable set up on Biostar a68n-5000 m-ITX mainboard

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: USB
Image version: 
http://cdimage.debian.org/debian-cd/8.2.0/multi-arch/iso-cd/debian-8.2.0-amd64-i386-netinst.iso
Date: 
about 14th of September 2015

Machine: Biostar a68n-5000 m-ITX
Partitions: 
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda1  btrfs 13670400  4993312   7067520  42% /
udev   devtmpfs 102400 10240   0% /dev
tmpfs  tmpfs   683752 9244674508   2% /run
tmpfs  tmpfs  1709376  136   1709240   1% /dev/shm
tmpfs  tmpfs 51204  5116   1% /run/lock
tmpfs  tmpfs  17093760   1709376   0% /sys/fs/cgroup
/dev/sdb1  btrfs 29360128 11641464  15744808  43% /home
tmpfs  tmpfs   3418764341872   1% /run/user/123
tmpfs  tmpfs   3418768341868   1% /run/user/1003


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

So far I am going in legacy-mode on this box, it is the replacement for the 
thin-client,
I used to use as my primary light PC, that is good enough 90% of the time for 
surfing,
mailing, reading, etc. The energy-consumption is good, actually between 13W 
(without
graphics) and 25 W at full load of all four cores, it may be a bit more with 
3D-graphics.
I have not tried the fglrx-driver yet, because I don't do any gaming and RADEON 
is good
enough for me. One problem I found with the hardware, was that the system fails 
to
wake up from suspend, so I turned that off. The behaviour I want is anyway, 
that the PC
shuts down, when the power-button is pressed, because of this I replaced GDM3 
with
lightdm.
The other problem I experienced was that the AMD-embedded-desktop kernel, I had 
in use
before is not properly working on this one. This means, it works in principle, 
but it is
not running stable enough and it does not boot reliably. So I switched to the
stock-kernel and attach the kernel-configuration in question
[config-3.16.7-ckt11-aedl.xz]. I think the problem is due to the 
embedded-feature and
slob-resource allocation, so I will leave that away, when I rebuild. My 
AMD-embedded
kernel was doing fine even on my AM2+ build-PC, see there:
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782757], but it was not 
workable on my
larger PC with A4-fusion APU on FM2. Now I found it is half workable, so I 
guess it is a
problem with embedded-slob allocation and the fusion architecture. Most 
probably I should
also report this as a bug in the kernel-source. When I rebuild the kernel, I 
will simply
leave the embedded-feature away and go like AMD-desktop-low-latency, which 
should work on
all three PCs of mine. 
Because GDM3 does not match my needs, I am also going to have
another look at this bug: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781080

Maybe, I find the way to disable root-login with lightdm without completely 
disabling the
root-account.


- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422+deb8u2"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux a68n 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 
(2015-08-04)
x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro 
Devices, Inc.
[AMD] Family 16h Processor Root Complex [1022:1536] lspci -knn: 
Subsystem:
Advanced Micro Devices, Inc. [AMD] Family 16h Processor Root Complex 
[1022:1536] lspci
- -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI]
Kabini [Radeon HD 8330] [1002:9832]

Bug#794231: evolution: fails to make correct DSA signatures

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: normal

Dear Maintainer,

I have been using Evolution for some months, there also sowed up some problems, 
that I
reported. Recently I found, that the mail-signatures it makes are not correct 
and cannot
be verified by other clients. Evolution  itself is unaware of the problem, it 
doesn't
show problems with it's signatures, but when mailing out to 
Thunderbird/Enigmail for
example, the signature cannot be verified. I am usind a DSA/ElGamal-Key, that 
was
generated by seahorse. That is why this is not merely a wishlist-item, like 
'DSA-support
missing for signing mail-messages', but in fact this is a feature that needs to 
be there,
because seahorse is part of the GNOME-desktop as well as Evolution, and it is 
the
default tool for generating GnuPG-keys, when not doing it manually on the 
terminal.

My key is the one belonging to andreas.glae...@irregulaire.info:
Fingerprint:7C35 8ECD 7C3C 90B5 70FC 02C5 99B6 DD31 6A93 64C6

The public part is available from keyservers.


- -- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt11-aedl (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages evolution depends on:
ii  dbus   1.8.18-0+deb8u1
ii  debconf [debconf-2.0]  1.5.56
ii  evolution-common   3.12.9~git20141130.241663-1
ii  evolution-data-server  3.12.9~git20141128.5242b0-2+deb8u2
ii  gnome-icon-theme   3.12.0-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18
ii  libcamel-1.2-493.12.9~git20141128.5242b0-2+deb8u2
ii  libclutter-gtk-1.0-0   1.6.0-1
ii  libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u2
ii  libedataserver-1.2-18  3.12.9~git20141128.5242b0-2+deb8u2
ii  libevolution   3.12.9~git20141130.241663-1+b1
ii  libglib2.0-0   2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libical1a  1.0-1.3
ii  libnotify4 0.7.6-2
ii  libsoup2.4-1   2.48.0-1
ii  libwebkitgtk-3.0-0 2.4.8-2
ii  libxml22.9.1+dfsg1-5
ii  psmisc 22.21-2

Versions of packages evolution recommends:
ii  bogofilter 1.2.4+dfsg1-3
ii  evolution-plugins  3.12.9~git20141130.241663-1+b1
ii  spamassassin   3.4.0-6
ii  yelp   3.14.1-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   1.4.18-7
ii  network-manager 0.9.10.0-7

- -- debconf information:
  evolution/kill_processes:
  evolution/needs_shutdown:
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlW7cXcACgkQ5+rBHyUt5wv0YQCfX67pL+X6fDxILHiqBmjkNI8X
h/0An0C2es68Uic3XLv96Fu0Oc5C0zsC
=W0Pk
-END PGP SIGNATURE-

Bug#788671: outdated: chapter05 does not mention systemd and /etc/systemd/network

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: debian-reference
Version: 2.58
Severity: minor

Dear Maintainer,

There is no hint about systemd:

https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_network_infrastructure

but it needs to be mentioned there.


- -- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt11-aedl (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debian-reference depends on:
ii  debian-reference-en  2.58

Versions of packages debian-reference recommends:
ii  debian-reference-fr  2.58
ii  debian-reference-it  2.58
ii  debian-reference-ja  2.58
ii  debian-reference-pt  2.58

debian-reference suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlV8/2UACgkQ5+rBHyUt5wswnQCfRV60ObVCNFuahwaDzYdA1gwp
r5sAn0Ixa+wLDijGeefLBnXvGrO/wag+
=Th5b
-END PGP SIGNATURE-

Bug#788670: systemd: resolved ignores DNS-entry in /etc/systemd/network/ and in /etc/network/interfaces

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: systemd
Version: 215-17+deb8u1
Severity: minor

Dear Maintainer,

I tried to set a different dns-resolver than the default gateway, but failed:

> root@s55:/home/andrew# cat /etc/systemd/network/dns.network
> [MATCH]
> Name=eth1
> HOST=s55
> 
> [NETWORK]
> DNS=192.168.0.108
> root@s55:/home/andrew# ifconfig
> eth1  Link encap:Ethernet  HWaddr 00:19:99:60:9d:e1  
>   inet addr:192.168.0.60  Bcast:192.168.0.255  Mask:255.255.255.0
>   inet6 addr: fd00:bc14:17f:f212:219:99ff:fe60:9de1/64 Scope:Global
>   inet6 addr: 2a02:8109:9ac0:2354:219:99ff:fe60:9de1/64 Scope:Global
>   inet6 addr: fe80::219:99ff:fe60:9de1/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:10441 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3623 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:12507078 (11.9 MiB)  TX bytes:390711 (381.5 KiB)
> 
> loLink encap:Local Loopback  
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:2131 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2131 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0 
>   RX bytes:378311 (369.4 KiB)  TX bytes:378311 (369.4 KiB)
> 
> root@s55:/home/andrew# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> # The loopback network interface
> auto lo 
> 
> iface lo inet loopback
> 
> # The primary network interface
> 
> auto eth1
> 
> allow-hotplug eth1
> 
> #iface eth0 inet manual
> 
> iface eth1 inet static
>   address 192.168.0.60
>   netmask 255.255.255.0
>   gateway 192.168.0.1
> # dns-nameservers 192.168.0.108   #handled by systemd
>   
> #
> #auto eth2
> #
> #allow-hoplug eth2
> #
> #iface eth2 inet dhcp
> # netmask 255.255.255.0
> # gateway 192.168.0.1
> #
> 
> root@s55:/home/andrew# cat /etc/resolv.conf 
> nameserver 2a02:8109:9ac0:2354::1

That's still the IP6-representation of the default gateway.
This really should be configurable.


- - -- Package-specific info:

- - -- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt11-aedl (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u1
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u1
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.18-0+deb8u1
ii  libpam-systemd  215-17+deb8u1

Versions of packages systemd suggests:
ii  systemd-ui  3-2

- - -- Configuration Files:
/etc/systemd/resolved.conf changed:
[Resolve]
DNS=192.168.0.108


- - -- no debconf information
- -BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlV8+PUACgkQ5+rBHyUt5wvuKQCfZ6A1HB2efzdQf+CX1VY1RJn4
o1QAn3pxY1mLSL3FLlsmYjUThQ64239j
=F5nO
- -END PGP SIGNATURE-
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlV8+6cACgkQ5+rBHyUt5wvNyACeLAexV6oj4xMv1LxXyXSLRckt
cCQAoLiaIfLQWC6zEdiFNi7rZHBJJFLo
=Spni
-END PGP SIGNATURE-

Bug#788340: xserver-xorg-video-openchrome: No graphics with P4M900/VN896/CN896 Chipset on IGEL H700C thin-client

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal

Dear Maintainer,

I have reported this as an installation report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788337
For the openchrome-driver it's a normal issue. I tried to set the 
kernel-boot-options
'video=LVDS-0:d' and 'video=LVDS-1:d', but from my experience so far with the 
VIA-driver
I can tell, it neither takes any boot-options from the kernel, nor is it 
configurable
properly from xorg.conf.
VESA would be a workaround, but headless is preferable in my opinion.


- -- Package-specific info:
X server symlink status:
- 
lrwxrwxrwx 1 root root 13 Jun 10 10:37 /etc/X11/X -> /usr/bin/Xorg
- -rwxr-xr-x 1 root root 2564976 Feb 11 02:23 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
- --
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. 
CN896/VN896/P4M900
[Chrome 9 HC] [1106:3371] (rev 01)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
- ---
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.8.4
(Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24)

Xorg X server log files on system:
- --
- -rw-r--r-- 1 root root 21028 Jun 10 12:56 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
- -
[15.303] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[15.303] X Protocol Version 11, Revision 0
[15.303] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[15.303] Current Operating System: Linux dewp 3.16.0-4-686-pae #1 SMP Debian
3.16.7-ckt11-1 (2015-05-24) i686 [15.303] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae 
root=UUID=1781d5cb-715b-43b0-8e1f-cc424959fe26
ro quiet [15.303] Build Date: 11 February 2015  01:14:26AM [15.303] 
xorg-server
2:1.16.4-1 (http://www.debian.org/support) [15.303] Current version of 
pixman: 0.32.6
[15.303]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[15.303] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[15.304] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 10 12:56:25 
2015
[15.311] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[15.317] (==) No Layout section.  Using the first Screen section.
[15.317] (==) No screen section available. Using defaults.
[15.317] (**) |-->Screen "Default Screen Section" (0)
[15.317] (**) |   |-->Monitor ""
[15.324] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[15.324] (==) Automatically adding devices
[15.324] (==) Automatically enabling devices
[15.324] (==) Automatically adding GPU devices
[15.329] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[15.330]Entry deleted from font path.
[15.342] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[15.342] (==) ModulePath set to "/usr/lib/xorg/modules"
[15.342] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[15.342] (II) Loader magic: 0xb7742700
[15.342] (II) Module ABI versions:
[15.342]X.Org ANSI C Emulation: 0.4
[15.342]X.Org Video Driver: 18.0
[15.342]X.Org XInput driver : 21.0
[15.342]X.Org Server Extension : 8.0
[15.346] (--) PCI:*(0:1:0:0) 1106:3371:1106:3371 rev 1, Mem @ 
0xd800/67108864,
0xdd00/16777216, BIOS @ 0x/65536 [15.349] (II) LoadModule: "glx"
[15.355] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[15.445] (II) Module glx: vendor="X.Org Foundation"
[15.445]compiled for 1.16.4, module version = 1.0.0
[15.445]ABI class: X.Org Server Extension, version 8.0
[15.445] (==) AIGLX enabled
[15.445] (==) Matched openchrome as autoconfigured driver 0
[15.445] (==) Matched modesetting as autoconfigured driver 1
[15.445] (==) Matched fbdev as autoconfigured driver 2
[15.445] (==) Matched vesa as autoconfigured driver 3
[15.445] (==) Assigned the driver to the xf86ConfigLayout
[15.445] (II) LoadModule: "openchrome"
[15.451] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
[1

Bug#788337: No Graphics on IGEL H 700C thin-client

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
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 effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/debian-cd/8.0.0/multi-arch/iso-cd/debian-8.0.0-amd64-i386-netinst.iso,
2015-04-25
Date: 2015-06-10, about 12.00 h

Machine: IGEL H700C
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/sdb1  xfs6134590 3178676   2955914  52% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   1931524936188216   3% /run
tmpfs  tmpfs   482876   0482876   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   482876   0482876   0% /sys/fs/cgroup
/dev/sdb2  xfs7154750   16480   7138270   1% /home
tmpfs  tmpfs96576   4 96572   1% /run/user/119
tmpfs  tmpfs96576   0 96576   0% /run/user/1000



Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [e]
Install boot loader:[O]
Overall install:[o]

Comments/Problems:

It seems the openchrome graphics-driver from VIA is defective by default, I 
have not met
any device in the recent time, where it works. I will report this separately
against the openchrome-video-driver. I think the best solution for this is 
currently, not
to worry, or get upset, or grow grey hair, waiting for a fix, but instead use 
these boxes
as servers.
I set up the debian-desktop and mate-desktop tasks here for testing purposes.


- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux dewp 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. 
CN896/VN896/P4M900 Host
Bridge [1106:0364] lspci -knn:  Subsystem: VIA Technologies, Inc.
CN896/VN896/P4M900 Host Bridge [1106:0364] lspci -knn:  Kernel driver in use:
agpgart-via lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc.
CN896/VN896/P4M900 Host Bridge [1106:1364] lspci -knn: 00:00.2 Host bridge 
[0600]: VIA
Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:2364] lspci -knn: 
00:00.3 Host
bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 
[1106:3364] lspci
- -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 
Host Bridge
[1106:4364] lspci -knn: 00:00.5 PIC [0800]: VIA Technologies, Inc. 
CN896/VN896/P4M900 I/O
APIC Interrupt Controller [1106:5364] lspci -knn: 00:00.6 Host bridge [0600]: 
VIA
Technologies, Inc. CN896/VN896/P4M900 Security Device [1106:6364] lspci -knn: 
00:00.7
Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge 
[1106:7364]
lspci -knn: 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI 
Bridge
[1106:b198] lspci -knn: 00:02.0 PCI bridge [0604]: VIA Technologies, Inc.
CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:a364] (rev 80) lspci -knn:
Kernel driver in use: pcieport lspci -knn: 00:03.0 PCI bridge [0604]: VIA 
Technologies,
Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:c364] (rev 80) lspci 
-knn:
Kernel driver in use: pcieport lspci -knn: 00:0f.0 IDE interface 
[0101]: VIA
Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE 
[1106:0571]
(rev 07) lspci -knn:Subsystem: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] lspci -knn:
Kernel driver in use: pata_via lspci -knn: 00:10.0 USB controller [0c03]: VIA
Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev b0) lspci 
-knn:
Subsystem: VIA Technologies, Inc. VT82xxx

Bug#785500: Severity

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This is a minor issue only, because the problem is caused by the quick-resync 
option in
the mail-account preferences.
Details see in GNOME-bugzilla.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVz8UoACgkQ5+rBHyUt5wtwEACdEzm+zs4khjf/3Tz7pZNVdR2p
3jYAnRplROapEXYj2Cmzr4vjSW4qnAlO
=lWSH
-END PGP SIGNATURE-

Bug#786872: autogenerated xorg.conf for VESA

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

see attachment [xorg.conf.gz]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVofrIACgkQ5+rBHyUt5wvBhwCdHHNfiKjdL2jskolZ1kc3/KyT
PDkAoLMzxig8rvYGsomEBVJSHYE/9N8o
=G1BJ
-END PGP SIGNATURE-


xorg.conf.gz
Description: application/gzip

Bug#786872: It's possible to use the VESA graphics-driver

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


First I tried to set up fbdev, but it did not work out for me, then I removed 
the
openchrome-driver using apt-get and generated a new X-configuration:

# init 1
# cd /etc/X11
# X -configure
# cp /root/xorg.conf.new ./xorg.conf

That's all, graphics work in VESA-mode, X took a bit long to start up, also 
switching to
virtual terminals and back to the X-screen i a bit slow, but it's a feasible 
workaround.
Re-install task-desktop and xserver-xorg-video-all.

Thus downgrading this issue to minor.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVofIcACgkQ5+rBHyUt5wu1iQCfQ2yVOIyp7npl5O4Y/eme2Zip
6nkAoIoGspjAKcwlG7Vdd8Q+JYt+skxC
=vVR/
-END PGP SIGNATURE-

Bug#786873: Connected VGA-monitor works

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Now with Jessie, I tried to connect an external VGA-monitor and this actually 
works.
During the boot-process both displays were mirrored, showing the same things, 
but upon
xserver-start there is the login-screen on the external monitor, the 
LVDS-screen looks
pretty much like what I saw on oldstable, just garbled rubbish.
See attached Xorg-log.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVlvQ0ACgkQ5+rBHyUt5wvVSACgnuWTWaL9ciuUp1lq5TFFw4cP
SswAnRL9obhkbvA9L++wMHQix2vpmdJV
=HlQ2
-END PGP SIGNATURE-


Xorg.0.log.a.xz
Description: application/xz

Bug#786873: Data collected from Debian-live-oldstable

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


When booting up oldstable-live, there is some output on the screen at least.
But it seems to be the wrong display-resolution or graphics-mode.
See attached Xorg-log.
This seems to be the most workable variant, set up oldstable and try to set 
things
straight with xorg.conf.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVluVMACgkQ5+rBHyUt5wursgCdHYSkq9JrjdX+10K0lq6X0RF5
9NQAn2UdZ6RthrQ6R+uxCvROh3Eeds+c
=qVYl
-END PGP SIGNATURE-


Xorg.0.log-7.8-live.xz
Description: application/xz

Bug#786873: xserver-xorg-video-openchrome: does not show any graphics-output

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal

Dear Maintainer,

hardware-information about the host-PC can be found in my installation-report 
there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786872


- -- Package-specific info:
X server symlink status:
- 
lrwxrwxrwx 1 root root 13 May 26 10:33 /etc/X11/X -> /usr/bin/Xorg
- -rwxr-xr-x 1 root root 2564976 Feb 11 02:23 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
- --
01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN700/P4M800 
Pro/P4M800
CE/VN800 Graphics [S3 UniChrome Pro] [1106:3344] (rev 01)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
- ---
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.8.4
(Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24)

Xorg X server log files on system:
- --
- -rw-r--r-- 1 root root 25011 May 26 11:26 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
- -
[   476.063] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[   476.063] X Protocol Version 11, Revision 0
[   476.063] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
[   476.063] Current Operating System: Linux m10 3.16.0-4-686-pae #1 SMP Debian
3.16.7-ckt9-3~deb8u1 (2015-04-24) i686 [   476.063] Kernel command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-686-pae 
root=UUID=e23cd5bf-7102-4a25-b63c-b38b75974783 ro
quiet [   476.064] Build Date: 11 February 2015  01:14:26AM [   476.064] 
xorg-server
2:1.16.4-1 (http://www.debian.org/support) [   476.064] Current version of 
pixman: 0.32.6
[   476.064]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   476.064] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   476.065] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 26 11:25:29 
2015
[   476.065] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   476.067] (==) No Layout section.  Using the first Screen section.
[   476.067] (==) No screen section available. Using defaults.
[   476.067] (**) |-->Screen "Default Screen Section" (0)
[   476.067] (**) |   |-->Monitor ""
[   476.068] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   476.068] (==) Automatically adding devices
[   476.068] (==) Automatically enabling devices
[   476.068] (==) Automatically adding GPU devices
[   476.068] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   476.068]Entry deleted from font path.
[   476.069] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   476.069] (==) ModulePath set to "/usr/lib/xorg/modules"
[   476.069] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   476.069] (II) Loader magic: 0xb7769700
[   476.069] (II) Module ABI versions:
[   476.069]X.Org ANSI C Emulation: 0.4
[   476.069]X.Org Video Driver: 18.0
[   476.069]X.Org XInput driver : 21.0
[   476.069]X.Org Server Extension : 8.0
[   476.073] (--) PCI:*(0:1:0:0) 1106:3344:1106:3344 rev 1, Mem @ 
0xf000/67108864,
0xf400/16777216 [   476.073] (II) LoadModule: "glx"
[   476.074] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   476.081] (II) Module glx: vendor="X.Org Foundation"
[   476.081]compiled for 1.16.4, module version = 1.0.0
[   476.082]ABI class: X.Org Server Extension, version 8.0
[   476.082] (==) AIGLX enabled
[   476.082] (==) Matched openchrome as autoconfigured driver 0
[   476.082] (==) Matched modesetting as autoconfigured driver 1
[   476.082] (==) Matched fbdev as autoconfigured driver 2
[   476.082] (==) Matched vesa as autoconfigured driver 3
[   476.082] (==) Assigned the driver to the xf86ConfigLayout
[   476.082] (II) LoadModule: "openchrome"
[   476.083] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so
[   476.084] (II) Module openchrome: vendor="http://openchrome.org/";
[   476.084]compiled for 1.15.99.904, module version = 0.3.3
[   476.084]Module class: X.Org Video Driver
[   476.084]ABI class: X.Org Video Driver, version 18.0
[   476.084] (II) LoadModule: "modesetting"
[   476.085] (II) Loading /usr

Bug#786872: installation-report: Jessie (8) on Neoware m100 mobile thin-client without graphics

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
Severity: normal

Dear Maintainer,

It's another VIA-device without graphics-output, I wished, it would work by 
default, not
the other way around, getting fixes upon request.



- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/debian-cd/8.0.0/multi-arch/iso-cd/debian-8.0.0-amd64-i386-netinst.iso,
2015-04-25
 Date: a few days ago

Machine: Neoware m100
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/sda2  btrfs 12695552 3149428   7587020  30% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs988844968 93916   6% /run
tmpfs  tmpfs   247204   0247204   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   247204   0247204   0% /sys/fs/cgroup
/dev/sda1  btrfs   975872   30100941680   4% /boot
tmpfs  tmpfs49444   0 49444   0% /run/user/0
tmpfs  tmpfs49444   4 49440   1% /run/user/117
tmpfs  tmpfs49444   0 49444   0% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o ]
Partition hard drives:  [o ]
Install base system:[o]
Install tasks:  [E]
Install boot loader:[o]
Overall install:[e]

Comments/Problems:

The installation was really tricky this time, brecause I tried to install on the
32-GB-Sandisk stick first (with blue LED), which was not workable. The Stick, 
as mentioned
already earlier, also does not boot up any system on FSC Futro S500/S550, but 
works with
HP-devices.
I even had the USB-key replaced against a new device at the shop I got it from, 
but it
has clearly not been defective, but it is a general problem with 
SanDisk-Ultra-USB3, 32
GB G2.
Then installation worked out on an older slower SD-card, it turned out, the 
USB-ports are
USB 1.1 only, so you need some patience.
The PCMCIA-port even features something called the VIA-boot-agent, but it does 
not work
for me with my PCMCI-CF adapter-card. The Installer also does not show the 
CF-card in the
PCMCIA-cardreader, but once a minimal system is set up, the CF-storage is there.
So one would probably rather use a CF-IDE adaptor and have a CF-card installed 
as an IDE-device
in order to install on this directly and boot from it directly, instead of
working around the non-bootable PCMCIA-cardreader with a separate 
boot-partition on USB1.
Upon setting up a basic system, it is necessary to enable the non-free archive, 
because
the ralink-WLAN-firmware will throw a non-recoverable error upon 
desktop-install, if
missing. This may be a problem with network-manager.
Last but not least, there was no graphics-output, I report that separately 
against
xserver-xorg-openchrome.
Apart from the issues reported this is the most cheap-shot notebook you have 
ever met, and
all lovable at a price of about EUR 10,- (without power-supply).

 

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux m10 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro
Host Bridge [1106:0314] lspci -knn: Subsystem: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:0314] lspci -knn:Kernel driver in
use: agpgart-via lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:1314] lspci -knn: 00:00.2 Host 
bridge [0600]:
VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:2314] lspci 
-knn:
00:00.3 Host bridge [0600]: VIA Technologies, Inc. PT890 Host Bridge 
[1106:3208] lspci
- -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. 
CN700/VN800/P4M800CE/Pro Host
Bridge [1106:4314] lspci -knn: 00:00.7 Host bridge [0600]: VIA Technologies, 
Inc.
CN700/VN800/P4M800CE/Pro Host Bridge [1106:7314] lspci -knn: 00:01.0 PCI bridge 
[0604]:
VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198] lspci -knn: 

Bug#785597: lxc: fails to create or start unprivileged containers as user

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: lxc
Version: 1:1.0.6-6
Severity: minor

Dear Maintainer,

I was trying to make unprivileged user-containers, but failed. I also tried to 
make a
container usind 'sudo', then moving it into the home-directory of the user and 
changing
ownership and group, but this did not work out either, see below. Logfiles are 
attached.
There is a report saying, lxc version 1.1 should be backported to Jessie, but 
it is not
there yet.
Upon trying to start the container, I made with 'sudo', there is a problem with 
the
ssh-session, i need to log out and log in again, because it does not show, what 
I type
anymore.
I say it's a minor issue, because I can use a root-containers instead, which 
works well
enough. Very high security is not really necessary for my application case.


> contain@dhsrv:~$ lxc-start -n privo-squid -d -F --logfile=lxc.log.txt
> --logpriority=DEBUG unshare: Operation not permitted
> read pipe: No such file or directory
> lxc-start: Failed to chown /dev/pts/7
> lxc-start: Failed to shift tty into container
> lxc-start: failed to initialize the container
> lxc-start: The container failed to start.
> lxc-start: Additional information can be obtained by setting the --logfile and
> --logpriority options.
> 
> .
> ..
> .
> 
> contain@dhsrv:~$ lxc-create -t download -n testcont --logfile=lxcc.log.txt
> --logpriority=DEBUG unshare: Operation not permitted
> read pipe: No such file or directory
> lxc-create: Failed to chown container dir
> lxc-create: Error creating container testcont
> contain@dhsrv:~$ lxc-create -t download -n testcont -P /home/contain/stora
> --logfile=lxcc.log.txt --logpriority=DEBUG unshare: Operation not permitted
> read pipe: No such file or directory
> lxc-create: Failed to chown container dir
> lxc-create: Error creating container testcont



- -- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.7-ckt9-es-via-c7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lxc depends on:
ii  init-system-helpers  1.22
ii  libapparmor1 2.9.0-3
ii  libc62.19-18
ii  libcap2  1:2.24-8
ii  libseccomp2  2.1.1-1
ii  libselinux1  2.3-2
ii  multiarch-support2.19-18
ii  python3  3.4.2-2

Versions of packages lxc recommends:
ii  debootstrap  1.0.67
ii  openssl  1.0.1k-3
ii  rsync3.1.1-3

Versions of packages lxc suggests:
pn  lua5.2  

- -- Configuration Files:
/etc/lxc/default.conf changed:
lxc.arch = x86
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = cbr0
lxc.id_map = u 0 10 65537 
lxc.id_map = g 0 10 65537 


- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVZj7UACgkQ5+rBHyUt5wsCBwCfcmeQ7gl5mucdDG+lVKHkVPps
YD8An3zoixC3rzcv/4nSlrh99u3aieGL
=CCzq
-END PGP SIGNATURE-
 lxc-create 1431931713.508 WARN lxc_log - lxc_log_init called with log 
already initialized
 lxc-create 1431931713.510 INFO lxc_confile - read uid map: type u nsid 
0 hostid 10 range 65536
 lxc-create 1431931713.510 INFO lxc_confile - read uid map: type g nsid 
0 hostid 10 range 65536
 lxc-create 1431931713.522 ERRORlxc_container - Failed to chown 
container dir
 lxc-create 1431931713.522 ERRORlxc_create_ui - Error creating 
container testcont
 lxc-create 1431931836.838 WARN lxc_log - lxc_log_init called with log 
already initialized
 lxc-create 1431931836.839 INFO lxc_confile - read uid map: type u nsid 
0 hostid 10 range 65536
 lxc-create 1431931836.839 INFO lxc_confile - read uid map: type g nsid 
0 hostid 10 range 65536
 lxc-create 1431931836.850 ERRORlxc_container - Failed to chown 
container dir
 lxc-create 1431931836.850 ERRORlxc_create_ui - Error creating 
container testcont
  lxc-start 1431931179.231 INFO lxc_start_ui - using rcfile 
/home/contain/stora/privo-squid/config
  lxc-start 1431931179.233 INFO lxc_confile - read uid map: type u nsid 
0 hostid 10 range 65537
  lxc-start 1431931179.233 INFO lxc_confile - read uid map: type g nsid 
0 hostid 10 range 65537
  lxc-start 1431931179.234 WARN lxc_log - lxc_log_init called with log 
already initialized
  lxc-start 1431931179.234 INFO lxc_lsm - LSM security driver nop
  lxc-start 1431931179.249 INFO lxc_conf - tty's configured
  lxc-start 1431931179.252 INFO lxc_caps - Last supported cap was 36
  lxc-start 1431931179.273 ERRORlxc_conf - Failed to chown /dev/pts/7
  lxc-start 1431931179.273 ERRORlxc_start - Failed to shift tty into 
container
  lxc-start 1431931179.274 ERRORlxc_start - failed to initialize the 
container
  lxc-start 1431931179.274 ERRORlxc_start

Bug#785500: evolution: regularly cancels sending messages

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: normal

Dear Maintainer,

Since a few days, there are problems sending mail-messages from the default 
account.
Evoltion displays a (ruled out) line saying 'Sending message (cancelled)'.
It is possible to send from the secodary fremail-account, that is not always 
activated,
but it should be the user's choice, from which account to send mail, not 
Evolution's.
Possibly this is related to 'Mail Preferences'/'Junk':'[x] include remote Tests 
[This
will make SpamAssassin more reliable, but slower.]' I am returning to use 
Icedove because
of this.
I guess the issue will not be fixed, unless I forward it upstream.
I also want o say now, that I am quite disappointed already, that the 
GNOME-maintainers
don't have time to fix bugs, even if the distribution is released as stable, 
some remain
open. I reported those soon enough.


- -- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt9aedl (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages evolution depends on:
ii  dbus   1.8.16-1
ii  debconf [debconf-2.0]  1.5.56
ii  evolution-common   3.12.9~git20141130.241663-1
ii  evolution-data-server  3.12.9~git20141128.5242b0-2+deb8u2
ii  gnome-icon-theme   3.12.0-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18
ii  libcamel-1.2-493.12.9~git20141128.5242b0-2+deb8u2
ii  libclutter-gtk-1.0-0   1.6.0-1
ii  libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u2
ii  libedataserver-1.2-18  3.12.9~git20141128.5242b0-2+deb8u2
ii  libevolution   3.12.9~git20141130.241663-1+b1
ii  libglib2.0-0   2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libical1a  1.0-1.3
ii  libnotify4 0.7.6-2
ii  libsoup2.4-1   2.48.0-1
ii  libwebkitgtk-3.0-0 2.4.8-2
ii  libxml22.9.1+dfsg1-5
ii  psmisc 22.21-2

Versions of packages evolution recommends:
ii  bogofilter 1.2.4+dfsg1-3
ii  evolution-plugins  3.12.9~git20141130.241663-1+b1
ii  spamassassin   3.4.0-6
ii  yelp   3.14.1-1

Versions of packages evolution suggests:
pn  evolution-ews   
pn  evolution-plugins-experimental  
ii  gnupg   1.4.18-7
ii  network-manager 0.9.10.0-7

- -- debconf information:
  evolution/needs_shutdown:
  evolution/kill_processes:
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVYIfwACgkQ5+rBHyUt5wtPxgCfQDB/HKlBr9akV/DXydCHFc/+
3yUAn0z8Sb6Xy1fMFyegm9tey1j/ssHb
=6rOx
-END PGP SIGNATURE-

Bug#783949: making good progress

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Today I built a kernel-image for this box, it is doing well, as far as I can 
tell.
Some research was necessary to find out, how o cross-compile for i386 on AMD64.
This is how I did it:

 $ make ARCH=i686-PAE -j6 deb-pkg LOCALVERSION=-es-via-c7

doing this prior to the build:

 # dpkg --add-architecture i386
 # apt-get update && apt-get install ia32-libs gcc-multilib
[configure the kernel-source]

My configuration-file is attached [config-3.16.7-ckt9-es-via-c7.xz]

The ARCH-variable only determinates the generated package-names. I used 
'ARCH=i386'
there, but in strict terms this is not correct. First I had a 
kernel-configuration based
on the AMD64-stock-kernel, which resulted in a non-PAE-kernel, as dmesg told me 
the
nx-bit was not workable due to that.
At the second attempt taking the i686-PAE-stock-kernel, made a good 
kernel-image, see
[dmsg.cstm.txt.xz].

The server works well as apt-cacher already, the next step will be to make 
unprivileged
containers as normal user for the proxies.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVR8r4ACgkQ5+rBHyUt5wtC0ACgvTsJiKUdNnCbl7UM3A066VVg
weMAn1gh0LNYvnkIsy2GEP3QdTrPwI9I
=NAvy
-END PGP SIGNATURE-


config-3.16.7-ckt9-es-via-c7.xz
Description: application/xz


dmsg.cstm.txt.xz
Description: application/xz

Bug#784622: node-configuration fixed, network-configuration changed, still not workable

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[see attachments]
First I found, that the netmask was wrong in munin-node.conf this has to be /32 
not /24.
Then I thought, it might be due to the network-configuration, because of the
network-bridge, but it was not, the second remote host still does not show up.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlVMRxYACgkQ5+rBHyUt5wuDqQCgpsEb6y/zm/CmY6e+2bSpdeiB
2aAAn0HodAfF0JZwcDThSdrAjaekWt/j
=YeUR
-END PGP SIGNATURE-


munin-node.conf.xz
Description: application/xz


interfaces.xz
Description: application/xz

Bug#784622: munin-async: async-server allows for one node only

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: munin-async
Version: 2.0.25-1
Severity: normal

Dear Maintainer,

> andrew@s5:~$ sudo munin-check
> check /var/cache/munin/www
> check /var/lib/munin/cgi-tmp
> # /var/lib/munin/cgi-tmp/munin-cgi-graph : Wrong owner (www-data != munin)
> # /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal : Wrong owner (www-data != 
> munin)
> # /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal : Wrong owner 
> (www-data !=
> munin) ls: cannot access 
> /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal/*: No
> such file or directory # 
> /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal/* :
> Wrong owner ( != munin) check /var/lib/munin/datafile
> check /var/lib/munin/datafile.storable
> check /var/lib/munin/graphs
> check /var/lib/munin/htmlconf.storable
> check /var/lib/munin/limits
> check /var/lib/munin/limits.storable
> check /var/lib/munin/localdomain
> check /var/lib/munin/lokal
> check /var/lib/munin/munin-graph.stats
> check /var/lib/munin/munin-update.stats
> check /var/lib/munin/state-localdomain-localhost.localdomain.storable
> check /var/lib/munin/state-lokal-localhost.lokal.storable
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.12578
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.16703
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.17571
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.18630
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.20300
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.23654
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.7398
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.8906
> check /var/lib/munin/state-lokal-test.lokal.storable
> check miscellaneous
> # /var/lib/munin-node/plugin-state : Wrong owner (root != nobody)
> # /var/lib/munin-node/plugin-state : Wrong permissions (755 != 775)
> # /etc/munin/plugin-conf.d : Wrong permissions (750 != 755)
> Check done.  Please note that this script only checks most things,
> not all things.
> 
> Please also note that this script may be buggy.
> 
> andrew@s5:~$ sudo munin-check -f
> check /var/cache/munin/www
> check /var/lib/munin/cgi-tmp
> # /var/lib/munin/cgi-tmp/munin-cgi-graph : Wrong owner (www-data != munin)
> # /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal : Wrong owner (www-data != 
> munin)
> # /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal : Wrong owner 
> (www-data !=
> munin) ls: cannot access 
> /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal/*: No
> such file or directory # 
> /var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal/* :
> Wrong owner ( != munin) chown: cannot access
> ‘/var/lib/munin/cgi-tmp/munin-cgi-graph/lokal/test.lokal/*’: No such file or 
> directory
> check /var/lib/munin/datafile check /var/lib/munin/datafile.storable
> check /var/lib/munin/graphs
> check /var/lib/munin/htmlconf.storable
> check /var/lib/munin/limits
> check /var/lib/munin/limits.storable
> check /var/lib/munin/localdomain
> check /var/lib/munin/lokal
> check /var/lib/munin/munin-graph.stats
> check /var/lib/munin/munin-update.stats
> check /var/lib/munin/state-localdomain-localhost.localdomain.storable
> check /var/lib/munin/state-lokal-localhost.lokal.storable
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.12578
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.16703
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.17571
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.18630
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.20300
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.23654
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.7398
> check /var/lib/munin/state-lokal-localhost.lokal.storable.tmp.8906
> check /var/lib/munin/state-lokal-test.lokal.storable
> check miscellaneous
> # /var/lib/munin-node/plugin-state : Wrong owner (root != nobody)
> # /var/lib/munin-node/plugin-state : Wrong permissions (755 != 775)
> # /etc/munin/plugin-conf.d : Wrong permissions (750 != 755)
> Check done.  Please note that this script only checks most things,
> not all things.
> 
> Please also note that this script may be buggy.
> 
> root@dhsrv:/etc/munin# ls -la /var/lib/munin/.ssh
> total 8
> drwxr-xr-x 2 munin munin   36 May  6 15:14 .
> drwxr-xr-x 3 munin munin   37 May  6 15:16 ..
> -rw--- 1 munin munin 1679 May  6 15:14 id_rsa
> -rw-r--r-- 1 munin munin  393 May  6 15:14 id_rsa.pub

I tried setting up a second node with munin-async. It is not workable.
I re-checked permissions and configurations both on the host and on the server, 
it all
seems to be correct. I didn't generate a new key for the second node, but used 
the
existing one instead, this worked as user 'munin':
> ssh munin-as...@example.net
So normally the second  node should be visible in the web-interface, but it 
isn't.
I include the main configuration-files, xz-xo

Bug#783949: installation-report: Jessie-release-i386 set up on VIA-eden-homeserver

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: installation-reports
Version: 2.58
Severity: wishlist


Dear Maintainer,

this is only a wishlist-item, you may also think of it as a success-story.


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/debian-cd/8.0.0/multi-arch/bt-cd/debian-8.0.0-amd64-i386-netinst.iso.torrent,
2015-04-25
Date: 2015-04-31, about 14.00 h

Machine: HP t-5540 thin-client
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/sdb1  xfs7800832 1185940   6614892  16% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs891964596 84600   6% /run
tmpfs  tmpfs   222980   0222980   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs   222980   0222980   0% /sys/fs/cgroup
/dev/sdb5  xfs6824960   32984   6791976   1% /home
tmpfs  tmpfs44600   0 44600   0% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

I chose XFS here, because this is a 32-bit device and XFS is more mature and 
may also
perform better on weak hardware.
Setting up a thinclient as printserver is pretty trivial, when you have done it 
once,
512MB RAM are enough for that. I am going to upgrade RAM to 1G though, my 
concept for
this box is printserver and homeserver. It is OK to have the 
printserver-functionality
on the main system, because it is only accessible from the LAN and has no 
connection to
the outside world.
Other services, that access the internet, will be separated in LXC-containers, 
there
will be an apt-cacher and one or two privoxy-squid chains.
One could have proxies with different configurations, say one container with a 
normal
surf-proxy and another privoxy instance, that routes the traffic through TOR.
Before I start doing that, I am going to build an embedded-server 
kernel-package for the
box and try out munin and munin-async.



- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150422"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux dhsrv 3.16.0-4-586 #1 Debian 3.16.7-ckt9-2 (2015-04-13) i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge
[1106:0353] (rev 12) lspci -knn:Subsystem: VIA Technologies, Inc. VX800 
Host
Bridge [1106:0353] lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, 
Inc.
VX800/VX820 Error Reporting [1106:1353] lspci -knn: 00:00.2 Host bridge [0600]: 
VIA
Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353] lspci -knn: 00:00.3 
Host
bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353] lspci 
-knn:
00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management 
Control
[1106:4353] lspci -knn: 00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 
APIC and
Central Traffic Control [1106:5353] lspci -knn: 00:00.6 Host bridge [0600]: VIA
Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353] lspci -knn: 
00:00.7 Host
bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface 
Control
[1106:7353] lspci -knn: 00:01.0 VGA compatible controller [0300]: VIA 
Technologies, Inc.
VX800/VX820 Chrome 9 HC3 Integrated Graphics [1106:1122] (rev 11) lspci -knn:
Subsystem: VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics
[1106:1122] lspci -knn: 00:03.0 PCI bridge [0604]: VIA Technologies, Inc. 
VX800/VX820 PCI
Express Root Port [1106:e353] lspci -knn:   Kernel driver in use: pcieport 
lspci
- -knn: 00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VX800 Serial ATA 
and EIDE
Controller [1106:5324] lspci -knn:  Subsystem: VIA Technologies, Inc. VX800 
Serial
ATA and EIDE Controller [1106:5324] lspci -knn: Kernel driver in use: 
pata_via
lspci -knn: 00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82x 
UHCI USB 1.1
Controller [1106:3038] (rev a0) lspci -knn: Subsystem:

Bug#782333: Server-Kernel built for VIA-Nano thin-client

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I am using this box currently as a bittorrent-seeder with qbittorrent-nox.
The web-interface is nice. Today I built an embedded-server kernel for it. It 
seems to be
doing quite well so far, but there were problems with the Sandisk-Ultra-USB3 
(32GB)
storage-stick, I am using there. It cannot handle all compressed filesystems,
installation of PC-BSD (with LZ4-compressed ZFS-root) on it failed. After that 
the stick
seemed to be defective, but it resumed work upon completely zeroing it.
Today there was downtime, I spent much of the day, moving seeded files around,
defragmenting and balancing, now it is running again, and the wattage is 
surprisingly
low: 8W, although the files, it is distributing need to be decompressed 
permanently,
because they are on LZO-BTRFS.
The maximum wattage, I saw, was at 14W.
I have done some online-research and found VIA-nano devices are rare, there 
seem to be
quadcores in mini-ITX format, but this configuration is without SMP.
With the stock-kernel dmesg looked like this:

.
..
[0.040396] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
tlb_flushall_shift: -1
[0.072464] Freeing SMP alternatives memory: 20K (81a1b000 - 
81a2)
[0.076761] ftrace: allocating 21614 entries in 85 pages
[0.124879] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[0.166078] smpboot: CPU0: Centaur VIA Nano U3500@1000MHz (fam: 06, model: 
0f,
stepping: 0a) [0.168000] Performance Events: no PMU driver, software events 
only.
[0.169644] x86: Booted up 1 node, 1 CPUs
[0.169654] smpboot: Total of 1 processors activated (1994.98 BogoMIPS)
..
.
With the hp-t5550-specific VIA-kernel, it does not appear any faster, but 
probably it
works more efficiently, with less overhead:
.
..
[0.00] hpet clockevent registered
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 997.612 MHz processor
[0.010031] Calibrating delay loop (skipped), value calculated using timer 
frequency..
1995.22 BogoMIPS (lpj=9976120) [0.010043] pid_max: default: 32768 minimum: 
301
[0.010060] ACPI: Core revision 20140424
[0.042189] ACPI: All ACPI Tables successfully acquired
[0.050082] Security Framework initialized
[0.050111] AppArmor: AppArmor disabled by boot time parameter
[0.050118] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.050159] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[0.050168] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[0.050970] Initializing cgroup subsys memory
[0.050987] Initializing cgroup subsys devices
[0.051036] Initializing cgroup subsys freezer
[0.051051] Initializing cgroup subsys net_cls
[0.051079] Initializing cgroup subsys blkio
[0.051101] Initializing cgroup subsys perf_event
[0.051112] Initializing cgroup subsys net_prio
[0.051184] mce: CPU supports 0 MCE banks
[0.051200] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
tlb_flushall_shift: -1
[0.051209] CPU: Centaur VIA Nano U3500@1000MHz (fam: 06, model: 0f, 
stepping: 0a)
[0.063602] ftrace: allocating 20306 entries in 80 pages
[0.110191] Performance Events: no PMU driver, software events only.
[0.121369] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[0.23] NMI watchdog: disabled (cpu0): hardware events not enabled
[0.23] devtmpfs: initialized
..
.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlU/qxIACgkQ5+rBHyUt5wt/egCgwfX34fRFM4s0VcTvJkwfLibY
To8AnjKAKk6U/MQaGEV+dFHShAKtwNOk
=2oPL
-END PGP SIGNATURE-


config-3.16.7-ckt9es-via64.xz
Description: application/xz

Bug#782757: installation-report: Jessie-RC-AMD64 on my build-PC

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
Severity: wishlist

Dear Maintainer,

This is wishlist only, just some info.


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2015-04-13
Date: 2015-04-16, about 9.00 h to 10.00 h

Machine: GA-MA78GM-S2H with Phenom II 710
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/sdb1  btrfs 14336000 3492036   8835228  29% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   3592325172354060   2% /run
tmpfs  tmpfs   898076   0898076   0% /dev/shm
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs   898076   0898076   0% /sys/fs/cgroup
/dev/sdb3  btrfs 12735488 5420224   5427104  50% /home
/dev/sda6  ext4999320   32544897964   4% /boot


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

I wanted to celebrate the CPU-upgrade of my secondary build-PC by submitting 
this report.
It is Phenom II x3 710 now, but it cost me a half day to upgrade the BIOS.
It is running well now, with just below 80W of power-consumption, when idle, 
like before
and it draws about 130W when fully loaded. I installed on a USB-Flashdrive with 
a
separate /boot/-partition on the harddisk, in order to be able to put the 
USB-key into a
USB3-port upon installation. But unfortunately my USB3-controller card broke, 
it was very
low-cost and turned out o have dummy-fuses only, so I will have to get a new 
card now,
before actually trying out USB3-speed.
There is only the base-system so far and everything required to build a 
kernel-package.
I am also going to try it out as a remote-desktop server.
I tried to use cpufreqd and cpufrequtils in order to limit the maximum 
CPU-frequency
to 80%, but I don't quite remember, how to do this, I will have to read the 
documentation
first, or maybe it didn't work out because of hardware-incompatibility.
In case of problems, I'll file a separate report about this.


- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150413-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux build 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-1 (2015-04-08) 
x86_64
GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. 
[AMD]
RS780 Host Bridge [1022:9600] lspci -knn:   Subsystem: Advanced Micro 
Devices, Inc.
[AMD] RS780 Host Bridge [1022:9600] lspci -knn: 00:01.0 PCI bridge [0604]: 
Advanced Micro
Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) [1022:9602] lspci 
-knn:
00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI 
to PCI
bridge (PCIE port 5) [1022:9609] lspci -knn:Kernel driver in use: pcieport 
lspci
- -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI]
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] lspci -knn:   
Subsystem:
Gigabyte Technology Co., Ltd Device [1458:b002] lspci -knn: Kernel driver 
in use:
ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. 
[AMD/ATI]
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] lspci -knn:  Subsystem:
Gigabyte Technology Co., Ltd Device [1458:5004] lspci -knn: Kernel driver 
in use:
ohci-pci lspci -knn: 00:12.1 USB controller [0c03]: Advanced Micro Devices, Inc.
[AMD/ATI] SB7x0 USB OHCI1 Controller [1002:4398] lspci -knn:Subsystem: 
Gigabyte
Technology Co., Ltd Device [1458:5004] lspci -knn:  Kernel driver in use: 
ohci-pci
lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices, Inc. 
[AMD/ATI]
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] lspci -knn:   Subsystem: 
Gigabyte
Technology Co., Ltd Device [1458:5004] lspci -knn:  Kernel driver in use: 
ehci-pci
lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. 
[AMD/ATI]
SB7x0/SB8x0/SB9x0 

Bug#782378: installation-report: Jessie-RC on DELL notebook

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.58
Severity: wishlist

Dear Maintainer,

this wa a flawless installation, wishlist only.


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso,
2015-04-08
 Date: 2015-04-11, about 7.00 h to 9.00 h


Machine: Dell Latitude E 4300
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
/dev/mmcblk0p1 btrfs 14647296 4650552   9713976  33% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   3888565988382868   2% /run
tmpfs  tmpfs   972132 140971992   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs   972132   0972132   0% /sys/fs/cgroup
/dev/mmcblk0p2 btrfs 146483205072  14369040   1% /home
/dev/sda3  xfs1038336   64568973768   7% /boot
tmpfs  tmpfs   194428   4194424   1% /run/user/119
tmpfs  tmpfs   194428  20194408   1% /run/user/1000

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [o]
Detect network card:[o]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

The last grub-update disabled my 32-bit testing-system.

Now I installed newly on a low-cost 32GB-SD-card, also with compressed btrfs, 
GNOME and
Cinnamon desktops.

It seems to do quite well so far.

Installation itself was quite quick, but defragmenting/recompressing everything 
takes
some time, it is probably not recommended to do it this way.
 

- -- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150408-00:04"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux e4300 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) 
x86_64
GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 
Series
Chipset Memory Controller Hub [8086:2a40] (rev 07) lspci -knn:  Subsystem: Dell
Device [1028:024d] lspci -knn:  Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
4 Series
Chipset Integrated Graphics Controller [8086:2a42] (rev 07) lspci -knn:
Subsystem: Dell Device [1028:024d] lspci -knn: 00:02.1 Display controller 
[0380]: Intel
Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] 
(rev 07)
lspci -knn: Subsystem: Dell Device [1028:024d] lspci -knn: 00:03.0 
Communication
controller [0780]: Intel Corporation Mobile 4 Series Chipset MEI Controller 
[8086:2a44]
(rev 07) lspci -knn:Subsystem: Dell Device [1028:024d] lspci -knn: 00:03.2 
IDE
interface [0101]: Intel Corporation Mobile 4 Series Chipset PT IDER Controller
[8086:2a46] (rev 07) lspci -knn:Subsystem: Dell Device [1028:024d] 
lspci -knn:
Kernel driver in use: ata_generic lspci -knn: 00:03.3 Serial controller 
[0700]:
Intel Corporation Mobile 4 Series Chipset AMT SOL Redirection [8086:2a47] (rev 
07) lspci
- -knn: Subsystem: Dell Device [1028:024d] lspci -knn:  Kernel driver in
use: serial lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 
82567LM
Gigabit Network Connection [8086:10f5] (rev 03) lspci -knn: Subsystem: Dell
Device [1028:024d] lspci -knn:  Kernel driver in use: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB
UHCI Controller #4 [8086:2937] (rev 03) lspci -knn: Subsystem: Dell Device
[1028:024d] lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB
UHCI Controller #5 [8086:2938] (rev 03) lspci -knn: Subsystem: Dell Device
[1028:024d] lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB
UHCI Controller #6 [8086:2939] (rev 03) lspci -knn: Subsystem: Dell Device
[1028:024d] lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 

Bug#781668: e17: filemanager does not delete any files

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: e17
Version: 0.17.6-1
Severity: minor

Dear Maintainer,

the e17-filemanager does not delete any files, it does not matter whether the
context-menu (right-mouse-button) is used or the delete-key on the keyboard, or
shift-delete. This applies both to single files and folders.
There seems to be something going on, but  in the end the items are unchanged.
So users have to use a terminal-emulator to do that, or use a different 
file-manager.

Today there were news, that the Jessie-release is going to be at the end of 
April.
I really do wonder, if the maintainers all have fixes in their drawers for the 
issues,
that are still open. It seems there are quite some left. Maybe it is selective 
perception
from my side, because I own too many bugs, but there is severe doubt, all of 
those, which
are at least normal in severity will be done before the release happens.

This very bug for example would be a normal bug, but because the e17-filemanager
does not come in a separate package, it is minor only, so it cannot block the 
release,
it should be fixed though.


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt7edtp (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages e17 depends on:
ii  dbus-x11   1.8.16-1
ii  e17-data   0.17.6-1
ii  libasound2 1.0.28-1
ii  libc6  2.19-15
ii  libdbus-1-31.8.16-1
ii  libecore-con1  1.8.6-2.1+b2
ii  libecore-evas1 1.8.6-2.1+b2
ii  libecore-file1 1.8.6-2.1+b2
ii  libecore-imf1  1.8.6-2.1+b2
ii  libecore-input11.8.6-2.1+b2
ii  libecore-ipc1  1.8.6-2.1+b2
ii  libecore-x11.8.6-2.1+b2
ii  libecore1  1.8.6-2.1+b2
ii  libedbus1  1.7.10-1
ii  libedje-bin1.8.6-2.1+b2
ii  libedje1   1.8.6-2.1+b2
ii  libeet11.8.6-2.1+b2
ii  libeeze1   1.8.6-2.1+b2
ii  libefreet-bin  1.8.6-2.1+b2
ii  libefreet1a1.8.6-2.1+b2
ii  libeina1   1.8.6-2.1+b2
ii  libeio11.8.6-2.1+b2
ii  libevas1   1.8.6-2.1+b2
ii  libevas1-engines-x [libevas1-engine-software-x11]  1.8.6-2.1+b2
ii  libpam0g   1.1.8-3.1
ii  libxcb-keysyms10.4.0-1
ii  libxcb-shape0  1.10-3+b1
ii  libxcb11.10-3+b1

Versions of packages e17 recommends:
ii  pm-utils  1.4.1-15

e17 suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlUb9KYACgkQ5+rBHyUt5wv8MgCdFciuNZoWNCWoT8f3uN19dFJ7
jBwAoK7FXqro1WZ+I06deB21myiHMICA
=1nw2
-END PGP SIGNATURE-

Bug#781643: Problem seems to be RADEON-specific

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I could not reproduce it on my notebook with Intel-graphics and with the 32-bit 
version
of Jessie.

The graphics-glitch looks similar to the one I saw there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761358

Please let me know, if more info is required.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlUbtKAACgkQ5+rBHyUt5wtSFQCeM7L6xrdIfzHGVQ+f3hISbKyX
Z9kAmgNnopbDEPAmONsyaFE2VHRtv/CT
=1TLd
-END PGP SIGNATURE-

Bug#781643: gdm3: unusable - shows garbled login-screen since recently

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: gdm3
Version: 3.14.1-6
Severity: important

Dear Maintainer,

because of security-concerns about lightdm
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781080
 I wanted to switch back to GDM3, but found it unusable because of a garbled 
login-screen
I don't know if the problem appears with RADEON-graphics only, because I don't 
have
anything else on my stationary PCs.
KDM showed occasional problems, but continues o work for me.
Looking at open issues of GDM, I found one, that is almost ten years old and 
which should
be closed most probably:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598377


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt7edtp (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.37-3+b1
ii  adduser   3.113+nmu3
ii  cinnamon [x-window-manager]   2.2.16-5
ii  dconf-cli 0.22.0-1
ii  dconf-gsettings-backend   0.22.0-1
ii  debconf [debconf-2.0] 1.5.56
ii  e17 [x-window-manager]0.17.6-1
ii  gir1.2-gdm3   3.14.1-6
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-3
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-15
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-6
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-12
ii  libpam0g  1.1.8-3.1
ii  librsvg2-common   2.40.5-1
ii  libselinux1   2.3-2
ii  libsystemd0   215-12
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  muffin [x-window-manager] 2.2.6-4
ii  mutter [x-window-manager] 3.14.2-1
ii  policykit-1   0.105-8
ii  ucf   3.0030
ii  x11-common1:7.7+7
ii  x11-xserver-utils 7.7+3+b1
ii  xfce4-session [x-session-manager] 4.10.1-10
ii  xfce4-terminal [x-terminal-emulator]  0.6.3-1+b1
ii  xfwm4 [x-window-manager]  4.10.1-3
ii  xterm [x-terminal-emulator]   312-2

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.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4
ii  libpam-gnome-keyring  3.14.0-1+b1

- -- debconf information:
* shared/default-x-display-manager: kdm
  gdm3/daemon_name: /usr/sbin/gdm3
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlUbpBkACgkQ5+rBHyUt5wteUwCfWJXKG5ImLeuzpX3vpob08lor
dR4AnjO7G0WTAUatV1N1toh1IpQQbYeE
=b3C4
-END PGP SIGNATURE-

Bug#691456: current bug-status

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The situation with this problem is currently, that file-management works, when 
choosing
'Run' on the desktop for the home-folder, or 'Open' for other folders from the
context-menu, i.e. right-mouse-button menu.

But clicking on the items directly still provokes an EFL-crash.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlUWbL0ACgkQ5+rBHyUt5wvqEACgo0iv+eSPBgf6TCUvBWkjb/yw
gzgAoLDknOghkZ8R7Jyqe4AZ3xSqK+5J
=91Jl
-END PGP SIGNATURE-

Bug#781325: nautilus: file-manager settings regarding behaviour have no effect

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: nautilus
Version: 3.14.1-2
Severity: minor

Dear Maintainer,

I have been using GNOME3.4, and the settings from there are still in my 
home-directory.
Setting the behaviour of the file-manager to opening items/objects
with double-click does not have any effect.



- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt7edtp (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nautilus depends on:
ii  desktop-file-utils 0.22-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  gvfs   1.22.2-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-15
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libexempi3 2.2.1-2
ii  libexif12  0.6.21-2
ii  libgail-3-03.14.5-1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.42.1-1
ii  libglib2.0-data2.42.1-1
ii  libgnome-desktop-3-10  3.14.1-1
ii  libgtk-3-0 3.14.5-1
ii  libnautilus-extension1a3.14.1-2
ii  libnotify4 0.7.6-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libselinux12.3-2
ii  libtracker-sparql-1.0-01.2.4-2
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-5
ii  nautilus-data  3.14.1-2
ii  shared-mime-info   1.3-1

Versions of packages nautilus recommends:
ii  eject  2.1.5+deb1+cvs20081104-13.1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gnome-sushi3.12.0-2+b1
ii  gvfs-backends  1.22.2-1
ii  librsvg2-common2.40.5-1

Versions of packages nautilus suggests:
ii  brasero3.11.4-1.1
ii  eog3.14.1-1
ii  evince [pdf-viewer]3.14.1-2
ii  totem  3.14.0-2
ii  tracker1.2.4-2
ii  vlc [mp3-decoder]  2.2.0~rc2-2
ii  vlc-nox [mp3-decoder]  2.2.0~rc2-2
ii  xdg-user-dirs  0.15-2

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlUVeS0ACgkQ5+rBHyUt5wsggQCeNwX2yabl3yj7SmrjL2jr1z0/
PHUAn0s+rUrxHkklTdPsD6kSOS99ue9u
=wNRn
-END PGP SIGNATURE-

Bug#781080: lightdm: allows login as root by default

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: lightdm
Version: 1.10.3-3
Severity: normal

Dear Maintainer,

until today I had not even tried this, when I typed 'root' and the password 
into the
lightdm-mask instead of into VT-4-login.

I was quite surprised, that lightdm allows root-login, I also did not find, 
where to
switch this off in the text-configuration.

I have tried some things about X-login, but a root-session from lightdm is 
clearly not
what I wanted.

In my opinion this is *INSECURE*, if I need graphical root-access, then I start 
thunar
for instance from the terminal, saying 'sudo thunar', but having a completely
root-Xsession is most probably not recommended at all.

Please revert this to normal and add a configuration-option to enable it, if 
hackers need
the it in order to test X-security.  

Maybe this is related to systemd.



- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt7edtp (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages lightdm depends on:
ii  adduser3.113+nmu3
ii  consolekit 0.4.6-5
ii  dbus   1.8.16-1
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-15
ii  libgcrypt201.6.2-4+b1
ii  libglib2.0-0   2.42.1-1
ii  libpam-systemd 215-12
ii  libpam0g   1.1.8-3.1
ii  libxcb11.10-3+b1
ii  libxdmcp6  1:1.1.1-1+b1
ii  lightdm-gtk-greeter [lightdm-greeter]  1.8.5-2

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+7

Versions of packages lightdm suggests:
ii  accountsservice  0.6.37-3+b1
ii  upower   0.99.1-3.1

- -- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlURIv0ACgkQ5+rBHyUt5wu7WwCgrU6OFQNk1a7onAULMGK5/T4u
v0oAoMMW/ZDQpzcW+7pdkg07gJJ6wlAi
=BD1o
-END PGP SIGNATURE-

Bug#780201: new codename needed for oldstable (due to squeeze-lts) when stable becomes oldstable

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 10 Mar 2015 12:38:29 +0100
Holger Levsen  wrote:

> Hi,
> 
> when jessie will be released, wheezy will become oldstable and we'll need a 
> new alias for squeeze, as various tools internally work with aliases. (The 
> security tracker comes to my mind, but also the Release files it seems. And 
> probably more.)
> 
> I believe it's the ftp teams duty / joy to decide this name and would like to 
> ask you to do soon, so that various places can be prepared for the joyful day 
> we release jessie.
> 
> Current suggestions I've heard (and liked) are "oldoldstable" and 
> "veryoldstable".
> 
> I *dislike* "obsoletestable" and "stalestable" as they are either wrong 
> (squeeze is not obsolete) or carry a bad connotation.
> 
> 
> cheers,
>   Holger

What about 'extremely-stable' ??
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlT+7YsACgkQ5+rBHyUt5wswlQCgoTTsQR5jUK3Om45xcPsD2Fgp
HdcAoIPmig3g9GkHaezwK9ASpJJbn047
=cwuW
-END PGP SIGNATURE-

Bug#691456: E17 File-Manager crashes

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I set the file-manager to open items with a single click, crashes do not only 
appear on

the desktop, but also in the home-folder for instance.

But apart from this, my impression is good, one can use e17 in order to surf 
the web,

etc., just not for file-management.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlT+zT8ACgkQ5+rBHyUt5wsN2ACggPj00LyZB5rDvmJmOx1y/vpZ
WTgAnRXD0XGNOFicjHYNFgkb71fAcUKx
=62pJ
-END PGP SIGNATURE-

Bug#780122: grub-pc: grub-set-default does not work

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: grub-pc
Version: 2.02~beta2-21
Severity: normal

Dear Maintainer,

I report this from my kernel-build-PC.
The problem there was, that not the last and latest kernel was first in the 
grub menu,
but another and there was a new version of .
So I tried to change the default entry, first directly in /etc/default/grub, 
then putting
'Default=saved' there [see attachment] and using grub-set-default.
Like this:
> 'gnulinux-3.16.7-ckt4ckead-advanced-3b86c2cb-6c1a-4388-ab16-2765e6176edf'
or this:
>   grub-set-default 'Debian GNU/Linux, with Linux 3.16.7-ckt4ckead'
but it is not workable, there is always entry nr. 0 started.
I include my grub-file
from /etc/default/ and /boot/grub/grub.cfg.
hope it helps.
For headless systems it is especially bad, when you have to connect a monitor 
to them in
order to work around this problem and remove older, unwanted kernel-versions, 
so I say
this is a normal bug, not minor, there is also core-functionality of the 
package affected.




- -- Package-specific info:

*** BEGIN /proc/mounts
/dev/sdb1 / btrfs rw,noatime,nodiratime,compress=zlib,space_cache 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1
- --hint-baremetal=ahci1,msdos1  3b86c2cb-6c1a-4388-ab16-2765e6176edf else
  search --no-floppy --fs-uuid --set=root 3b86c2cb-6c1a-4388-ab16-2765e6176edf
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_GB
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=-1
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1
- --hint-baremetal=ahci1,msdos1  3b86c2cb-6c1a-4388-ab16-2765e6176edf else
  search --no-floppy --fs-uuid --set=root 3b86c2cb-6c1a-4388-ab16-2765e6176edf
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os
$menuentry_id_option 'gnulinux-simple-3b86c2cb-6c1a-4388-ab16-2765e6176edf' { 
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod btrfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1
- --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  
3b86c2cb-6c1a-4388-ab16-2765e6176edf
else search --no-floppy --fs-uuid --set=root 
3b86c2cb-6c1a-4388-ab16-2765e6176edf
fi
echo'Loading Linux 3.16.7edtq ...'
linux   /boot/vmlinuz-3.16.7edtq
root=UUID=3b86c2cb-6c1a-4388-ab16-2765e6176edf ro  quiet pci=nomsi echo 'Loading
initial ramdisk ...' initrd /boot/initrd.img-3.16.7edtq
}
submenu 'Advanced options for

Bug#779985: The issue seems to be fixed already for youtube-dl

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


see there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778765

They say it i fixed already upstream.

So you guys might look up there, how to do it.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlT7GakACgkQ5+rBHyUt5wvafwCeODuC+4squkWdzorsDS157dn3
/w0AniNRyLLha2RmDMfCw5pcIyjc/qyw
=oPNm
-END PGP SIGNATURE-

Bug#779985: libwww-youtube-download-perl: youtube-videos fail to download

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: libwww-youtube-download-perl
Version: 0.56-1
Severity: important

Dear Maintainer,

say I want to download, that video of motherfucking LADY GAGA:

> andrew@s5:~$ youtube-download https://www.youtube.com/watch?v=ohs0a-QnFF4
> garbage after JSON object, at character offset 33125 (before ";ytplayer.load 
> = fun...")
> at /usr/share/perl5/WWW/YouTube/Download.pm line 226. andrew@s5:~$ 

It does not work, it is most probably due to Youtube's transition from Flash 
videos to
HTML5.
In my opinion, if it is not easy to fix the problem, it is safer to leave the 
package out
of Jessie, when it is going to be released.
It does not make sense to keep it in, when it is not workable anymore, because 
of changes
to that webservice, which will not be rolled back again.


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt4ckead (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libwww-youtube-download-perl depends on:
ii  libhtml-parser-perl  3.71-1+b3
ii  libjson-perl 2.61-1
ii  liburi-perl  1.64-1
ii  libwww-perl  6.08-1
ii  libxml-treepp-perl   0.39-1
ii  perl 5.20.2-2

libwww-youtube-download-perl recommends no packages.

libwww-youtube-download-perl suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlT7FxgACgkQ5+rBHyUt5wuznQCeN7wc7T2j7/En9YmcRNFB0ycR
+OEAoJlQEDyxd8c1wA0AWeESOIz/Am58
=HU0B
-END PGP SIGNATURE-

Bug#779100: [solved] - done

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The following 40_custom in /etc/grub.d/ fixed the issue for me:

> #!/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries.  Simply type the
> # menu entries you want to add after this comment.  Be careful not to change
> # the 'exec tail' line above.
> menuentry "D-Testing-32 (on /dev/mmcblk0p1) custom" {
>   set root='(hd0,msdos3)'
>   linux /vmlinuz-3.16-3-686-pae root=/dev/mmcblk0p1
>   initrd /initrd.img-3.16-3-686-pae 
> }

I am quite pleased with this actually, this is enough success for me today.

As far as I understand things, the first set-root actually names the 
/boot/-partition to
load the kernel and initrd from. It is not identical with the other root:
root=/dev/mmcblk0p1, which seems to name the filesystem-root that is used upon 
loading
the kernel.
All I need to do now is make the custom entry the default to boot first
in /etc/default/grub and/or using grub-set-default.
I am going to remove other, non-workable entries pointing at mmcblk0p1 by 
removing
the content of /boot/ on the SD-card, also see attachments.
I hope it will continue working upon the next kernel-update without manual 
interference.
Probably it is worth, having another look at the scripts in /etc/grub.d/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlT23Z8ACgkQ5+rBHyUt5wuyIACgoSQgKd+/Hm2500yLOH3DFhqh
yzYAn0HoIx8stolo5xURDRabw1Kdli2t
=D2Hl
-END PGP SIGNATURE-


grub.cfg.xz
Description: application/xz


40_custom.xz
Description: application/xz

Bug#779100: Making the SD-card boot in the internal cardreader is not trivial

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Today I tried this out, making a /boot/ partition on the harddisk and changing 
/etc/fstab
accordingly. It is workable while the card remains in the 
expresscard-cardreader, but not
workable, when it is inserted in the internal mmcblk-cardreader.
Running update-grub on the stable system on the harddisk is not sufficient to 
make things
work:

> andrew@jessie:~$ ls -la /dev/disk/by-uuid/
> total 0
> drwxr-xr-x 2 root root 140 Feb 25 11:38 .
> drwxr-xr-x 5 root root 100 Feb 25 11:33 ..
> lrwxrwxrwx 1 root root  10 Feb 25 11:33 0dde64dc-8274-4266-a810-f9aee59153e8
> -> ../../sdb5 lrwxrwxrwx 1 root root  10 Feb 25 11:38
> 200716dc-4394-44af-94d4-304c05e4d84b -> ../../sda5 lrwxrwxrwx 1 root root  10 
> Feb 25
> 11:38 51909eab-ae25-46af-841d-62fbbd1dd7a2 -> ../../sda3 lrwxrwxrwx 1 root 
> root  10 Feb
> 25 11:33 5e1b75fa-a3cc-4d0a-a535-6ef327488c44 -> ../../sdb1 lrwxrwxrwx 1 root 
> root  10
> Feb 25 11:38 c650ce84-00cc-45e6-86bb-c792e524028c -> ../../sda1 
> andrew@jessie:~$ sudo
> gedit /etc/fstab
> 
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
> 
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
> 
> (gedit:1942): Gtk-WARNING **: Calling Inhibit failed:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
> 
> ** (gedit:1942): WARNING **: Set document metadata failed: Setting attribute
> metadata::gedit-spell-language not supported
> 
> ** (gedit:1942): WARNING **: Set document metadata failed: Setting attribute
> metadata::gedit-encoding not supported andrew@jessie:~$ sudo mount /dev/sda3/ 
> /boot/
> mount: special device /dev/sda3/ does not exist (a path prefix is not a 
> directory)
> andrew@jessie:~$ sudo mount /dev/sda3 /boot/
> andrew@jessie:~$ sudo update-grub
> Generating grub configuration file ...
> Found background image: /usr/share/images/desktop-base/desktop-grub.png
> Found linux image: /boot/vmlinuz-3.16.0-4-686-pae
> Found initrd image: /boot/initrd.img-3.16.0-4-686-pae
> Found linux image: /boot/vmlinuz-3.16-3-686-pae
> Found initrd image: /boot/initrd.img-3.16-3-686-pae
> Found Debian GNU/Linux (7.8) on /dev/sda1
> done
> 

fstab looks like this:
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> #
> # / was on /dev/sdc1 during installation
> UUID=5e1b75fa-a3cc-4d0a-a535-6ef327488c44 /   xfs noatime
> 0   1 #separate /boot/ on /dev/sda3:
> UUID=51909eab-ae25-46af-841d-62fbbd1dd7a2 /boot/  xfs
> noatime   0   0 # swap was on /dev/sdc5 during installation
> UUID=0dde64dc-8274-4266-a810-f9aee59153e8 noneswapsw
> 0   0 /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   > 0
> /dev/sda1   /media/usb0 autorw,user,noauto  0   0
> /dev/sdc1   /media/usb1 autorw,user,noauto  0   0
> /dev/sdc2   /media/usb2 autorw,user,noauto  0   0
> /dev/sdc5   /media/usb3 autorw,user,noauto  0   0

Result: [see screenshots 'grub-menu.JPG' and 'grub-error.JPG']

There is this recipe for Arch-Linux:

https://bbs.archlinux.org/viewtopic.php?id=97207

but I don't think, I need that stuff about manually changing the initrd, 
because I am
using stock-kernels and generic initrds with all drivers included.

Maybe it is only a matter of chrooting prior to doing update-grub, possible 
something
like this does the trick:

> 3) Setup a working grub.cfg
> Since it is recommended to not edit grub.cfg directly in Grub2 I just added 
> the
> following entry to /etc/grub.d/40_custom
> 
> menuentry "Arch (on /dev/mmcblk0p1) custom" {
> set root='(hd0,5)'
> linux /boot/vmlinuz26-custom root=/dev/mmcblk0p1
> initrd /boot/kernel26-custom.img
> }

It should work anyway, when installing newly. I remember, I had similar 
problems, when
trying to move an exiting system onto an md-raid, most probably I am not 
familiar enough
with grub2 yet.


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlTt420ACgkQ5+rBHyUt5wvJnACdEumqQvma8wvGlmc9ETMvF3zo
JOMAnR6i8lAylxOIQSDgdOjXh92w6oWQ
=1p16
-END PGP SIGNATURE-

Bug#779100: Wheezy stable on Dell Latitude E 4300 including backports

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: installation-reports
Version: 2.49
Severity: wishlist

Dear Maintainer,
*** 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 lines ***


- -- Package-specific info:

Boot method: USB
Image version:
http://cdimage.debian.org/debian-cd/7.8.0/multi-arch/iso-cd/debian-7.8.0-amd64-i386-netinst.iso
Date: 2015-02-18, ~10 AM

Machine: Dell Latitude E 4300 Notebook
Partitions: 
Filesystem Type 1K-blocksUsed Available Use% Mounted on
rootfs rootfs32768000 3561824  28779200  12% /
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   1944081120193288   1% /run
/dev/sda1  btrfs 32768000 3561824  28779200  12% /
tmpfs  tmpfs 5120   0  5120   0% /run/lock
tmpfs  tmpfs  1227660  72   1227588   1% /run/shm


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [e]
Detect network card:[o ]
Configure network:  [o]
Detect CD:  [o]
Load installer modules: [o]
Clock/timezone setup:   [o]
User/password setup:[o]
Detect hard drives: [o]
Partition hard drives:  [o]
Install base system:[o]
Install tasks:  [o]
Install boot loader:[o]
Overall install:[o]

Comments/Problems:

The notebook is my replacement for the old T43-thinkpad. 
First USB-boot was disabled by default, it worked upon activating the 
boot-option
'USB-legacy emulation' in the BIOS. Upon that I could also boot from the 
SD-card, I had in
use before on the old machine using the express-card cardreader.
But additionally to the old testing-32-bit system, I also installed 
Wheezy-stable for
AMD64 on the internal harddisk, which worked perfectly fine, also including 
backports.
Choosing BTRFS as the filesystem and activating LZO-compression, but in spite 
of it
notebook-harddisks are not as fast as flash-memory and the system feels less 
fluent on
it than on flashdrives.
The internal cardreader is not bootable, because it requires the mmcblk-driver, 
so grub
says, the kernel needs to be loaded first. I am going to try, putting the 
content
of /boot/ from the SD-card onto a separate /boot/ partition on the internal 
harddisk,
which should work. This would be preferable, because SD-cards practically 
disappear in the
internal cardreader, just below the touchpad, but protrude a bit from the
expresscard-cardreader on the right side, which is impractical, when on the 
move, because
one always needs to be careful and mind, that the protruding flashcard does not
get damaged.

This is the firmware-package, which is required to enable the wifi-module:
> Package: firmware-iwlwifi
> New: yes
> State: installed
> Automatically installed: no
> Multi-Arch: foreign
> Version: 0.36+wheezy.1
> Priority: optional
> Section: non-free/kernel
> Maintainer: Debian Kernel Team 
> Architecture: all
> Uncompressed Size: 7,399 k
> Suggests: initramfs-tools, linux-image
> Description: Binary firmware for Intel PRO/Wireless 3945 and 802.11n cards
>  This package contains the binary firmware for Intel PRO/Wireless 3945ABG, 
> Intel
>  Wireless WiFi Link 5100AGN/5300AGN/5350AGN, Centrino Wireless-N
>  100/105/130/135/1000/1030/2200/2230/6150, Centrino Advanced-N
>  6200/6205/6230/6235/6250 and Centrino Ultimate-N 6300 cards supported by the
>  iwlegacy/iwl3945 and iwlwifi/iwlagn drivers. 
>  
>  Contents: 
>  * Intel Wireless 100 firmware, version 39.31.5.1 (iwlwifi-100-5.ucode) 
>  * Intel Wireless 105 firmware, version 18.168.6.1 (iwlwifi-105-6.ucode) 
>  * Intel Wireless 135 firmware, version 18.168.6.1 (iwlwifi-135-6.ucode) 
>  * Intel Wireless 1000 firmware, version 39.31.5.1 (iwlwifi-1000-5.ucode) 
>  * Intel Wireless 2200 firmware, version 18.168.6.1 (iwlwifi-2000-6.ucode) 
>  * Intel Wireless 2230 firmware, version 18.168.6.1 (iwlwifi-2030-6.ucode) 
>  * Intel Wireless 3945 firmware, version 15.32.2.9 (iwlwifi-3945-2.ucode) 
>  * Intel Wireless 4965 firmware, version 228.61.2.24 (iwlwifi-4965-2.ucode) 
>  * Intel Wireless 5100, 5300 and 5350 firmware, version 8.24.2.12
>(iwlwifi-5000-2.ucode) 
>  * Intel Wireless 5100, 5300 and 5350 firmware, version 8.83.5.1
>(iwlwifi-5000-5.ucode) 
>  * Intel Wireless 5150 firmware, version 8.24.2.2 (iwlwifi-5150-2.ucode) 
>  * Intel Wireless 6000 firmware, version 9.221.4.1 (iwlwifi-6000-4.ucode) 
>  * Intel Wireless 6005 firmware, version 17.168.5.3 (iwlwifi-6000g2a-5.ucode) 
>  * Intel Wireless 6030 firmware, version 18.168.6.1 (iwlwifi-6000g2b-6.ucode) 
>  * Intel Wireless 6250 firmware, version 9.201.4.1 (iwlwifi-6050-4.ucode) 
>  * Intel Wireless 6250 firmware, version 41.28.5.1 (iwlwifi-6050-5.uc

Bug#778372: linux-source-3.16: Boot-process hangs early on FSC Futro S500

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, 15 Feb 2015 00:46:50 +
Ben Hutchings  wrote:

> Is this also reproducible with linux-image-3.16.0-4-amd64?
> 
> Are any additional patches applied to your custom kernel?
> 
> Ben.

Hi, Ben,

actually I cannot tell, if it also happens with the stock kernel, because I 
have always

been using my custom kernel-configuration.

The hang also appears very rarely and I have not seen it on any other hardware 
yet.

There were no other changes made to the kernel, because I don't read any 
sourcecode so
far.

But I plan to build a custom kernel, that enables CPU-frequency-scaling, maybe 
try

initrd-ACPI-override first.

I need to identify first which part of ACPI actually does the 
frequency-scaling. 

ACPI-information to extract this from was posted there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769778
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=DSDT.dsl.xz;att=1;bug=769778

Greetings

Andreas
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlTkf+wACgkQ5+rBHyUt5wsW/QCcDw4l3fZ4mx5UjeKNfKUPSuzW
c9kAoIg0XCzaZ30I/JAYRwh4bLMjHOBw
=9hkD
-END PGP SIGNATURE-

Bug#735665: Works for me

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I don't have any problems using e17 desktop with lightdm,

so the issue is probably resolved.

But I can confirm some general instabilities, ie efl-crashes, so one has to 
restore the
session quite often.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlTfD3sACgkQ5+rBHyUt5wupWgCfWOWMfR0jXgVP90nSQD6tvmTi
ZxwAnAqYDITWG/MjPdJiSa3f7AvC2quR
=uqk2
-END PGP SIGNATURE-

Bug#763426: Non-installable RC1

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


This is the image, I tried today:

http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso

On the one hand the upgrade-path from stable needs some testing, too, and I 
tried that

already and it worked. On the other hand at the point, when the distribution 
gets the

RC-status and it is not installable by normal means, it's an important problem 
in my

opinion. So I upgrade the severity accordingly.

Some people probably just want to install the distribution, when it does not 
boot up upon

that, they won't give the system any testing- and evaluation-time.



-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlTOCg4ACgkQ5+rBHyUt5wub9ACfT931+DmvMOJVz4Bx2F9lJgX1
0oEAoL+GTmQa1IYklkAmOKsUFiB805Zi
=Ad8u
-END PGP SIGNATURE-

Bug#763426: Retried with i386 version of Testing, situation unchanged

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Because there were news, that there is actually RC1 out of Debian 8-Jessie, I 
retried

installation on i386 architecture today.

It went well, but GRUB would not boot the system upon that, situation mostly 
unchanged.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlTOAv0ACgkQ5+rBHyUt5wuPyACggx3x0HGjGdbWF2vsFsGPK87i
mCcAnApuu4gl+QHKNlH5NA2+KcYYBprT
=+FxA
-END PGP SIGNATURE-

Bug#733587: reopened because of outdated web-information

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The report was reopened, because, the issue was fixed only partially.

Soundconverter links to this page regarding MP3-support:

http://soundconverter.org/gstreamer-mp3-encoding-howto/

The information there is outdated:

> Add the deb-multimedia repository to apt sources.
> Install package gstreamer0.10-lame.

The lame-plugins are now icluded in the package

> gstreamer0.10-plugins-ugly 

 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlS7eyoACgkQ5+rBHyUt5wuSewCdH5JBpKqdRY69Gq1d2tcvlYQU
WFUAniArKpCXIBFR6ez4goUVzHsAKikm
=cB1o
-END PGP SIGNATURE-

Bug#775329: gtk3-engines-xfce: some GNOME application windows not resizable, breaks libreoffice-gtk2

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: gtk3-engines-xfce
Version: 3.0.1-2
Severity: normal

Dear Maintainer,

the problem was reported already there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775168

I found now, that it is actually gtk3-engines-xfce's fault.


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt2edtr (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gtk3-engines-xfce depends on:
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo-gobject2   1.14.0-2.1
ii  libcairo2   1.14.0-2.1
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgtk-3-0  3.14.5-1
ii  libpango1.0-0   1.36.8-3

gtk3-engines-xfce recommends no packages.

gtk3-engines-xfce suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlS2LMsACgkQ5+rBHyUt5wvSyACguLIIRZHga6XGHgNRYJXqx+Qj
X9MAoIcwQ1k4wDiQeWJA0y184BTwgv0o
=wQAm
-END PGP SIGNATURE-

Bug#775168: Other applications are also affected, it is probably more of a GTK2 vs. GTK3 issue.

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


The Evince document-viewer window is also affected for example, this is not 
exclusive to
gedit.

libreoffice has also rendering-problems with libreoffice-gtk on XFCE-desktop 
with
gtk3-engines-xfce:

> Package: libreoffice-gtk 
> State: installed
> Automatically installed: yes
> Version: 1:4.3.3-2
> Priority: optional
> Section: gnome
> Maintainer: Debian LibreOffice Maintainers 
> 
> Architecture: amd64
> Uncompressed Size: 857 k
> Depends: libreoffice-core (= 1:4.3.3-2), libatk1.0-0 (>= 1.12.4), libc6 (>= 
> 2.19),
> libcairo2 (>= 1.2.4), libdbus-1-3 (>= 1.0.2), libdbus-glib-1-2 (>= 0.78),
> libfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:4.1.1),
> libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.37.3), libgtk2.0-0 (>= 
> 2.24.0),
> libice6 (>= 1:1.0.0), libicu52 (>= 52~m1-1~), libpango-1.0-0 (>= 1.14.0),
> libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), libsm6, 
> libstdc++6 (>=
> 4.9), libx11-6, libxext6, libxml2 (>= 2.6.27), uno-libs3 (>= 4.1.0~alpha), ure
> Recommends: libreoffice-style-tango Conflicts: libgtk2.0-0 (= 2.12.10-1)
> Enhances: libreoffice
> Description: office productivity suite -- GTK+ integration
>  LibreOffice is a full-featured office productivity suite that provides a 
> near drop-in
> replacement for Microsoft(R) Office. 
>  
>  This package contains the Gtk plugin for drawing LibreOffices widgets with 
> Gtk+ and a
> Gtk/GNOMEish File Picker and print dialog when running under GNOME. It also 
> contains a
> QuickStarter for the "notification area". Homepage: http://www.libreoffice.org
> 
> Tags: role::plugin, role::shared-lib, uitoolkit::gtk

Installing libreoffice-gtk3 fixed the problem for me:

> Package: libreoffice-gtk3
> State: installed
> Automatically installed: no
> Version: 1:4.3.3-2
> Priority: optional
> Section: gnome
> Maintainer: Debian LibreOffice Maintainers 
> 
> Architecture: amd64
> Uncompressed Size: 689 k
> Depends: libreoffice-core (= 1:4.3.3-2), libatk1.0-0 (>= 1.12.4), libc6 (>= 
> 2.19),
> libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.0.2),
> libdbus-glib-1-2 (>= 0.78), libgcc1 (>= 1:4.1.1), libgdk-pixbuf2.0-0 (>= 
> 2.22.0),
> libglib2.0-0 (>= 2.24.0), libgtk-3-0 (>= 3.7.10), libice6 (>= 1:1.0.0), 
> libpango-1.0-0
> (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libsm6, libstdc++6 (>= 4.9), 
> libx11-6,
> libxext6, uno-libs3 (>= 4.1.0~alpha), ure Recommends: libreoffice-style-tango
> Enhances: libreoffice
> Description: office productivity suite -- GTK+ 3.0 integration
>  LibreOffice is a full-featured office productivity suite that provides a 
> near drop-in
> replacement for Microsoft(R) Office. 
>  
>  This package contains the Gtk plugin for drawing LibreOffices widgets with 
> Gtk+ 3.0
> and Gtk/GNOMEish print dialog when running under GNOME.
> Homepage: http://www.libreoffice.org
> 
> Tags: uitoolkit::gtk
> 

So this now seems more like a general GTK2 vs. GTK3 problem to me.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlS0580ACgkQ5+rBHyUt5wuSdACfbYUnaUenMxYSqjtCJHUa36aO
AYQAnAofgTVe+h8zVR2V0nUcQUvo2bcy
=ty+k
-END PGP SIGNATURE-

Bug#775168: gedit: application-window is not resizable on XFCE-desktop

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: gedit
Version: 3.14.0-3
Severity: minor

Dear Maintainer,

Normally I would use GNOME, but I don't because of these issues:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773627
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738631

So I fell back to XFCE and found that the gedit-window is not resizable on the
XFCE-desktop, while there is no problem with that on GNOME.
You are right, normally one
would use mousepad on XFCE, but I have gtk3-engines-xfce installed:

> i   gtk3-engines-xfce   - GTK+-3.0 theme engine for Xfce   
> 
> Package: gtk3-engines-xfce   
> State: installed
> Automatically installed: no
> Version: 3.0.1-2
> Priority: optional
> Section: xfce
> Maintainer: Debian Xfce Maintainers 
> Architecture: amd64
> Uncompressed Size: 470 k
> Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.2.5), libcairo-gobject2 (>= 
> 1.10.0),
> libcairo2 (>= 1.4.10), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 
> 2.24.0),
> libgtk-3-0 (>= 3.0.0), libpango1.0-0 (>= 1.14.0) Description: GTK+-3.0 theme 
> engine for
> Xfce This package contains a theme engine allowing users to apply various 
> GTK3.0 themes
> to Xfce. It also contains some ready themes, but users are of course free to 
> use other
> themes or design their own. Homepage: http://www.xfce.org/
> 
> Tags: uitoolkit::gtk


So this should work probably, shouldn't it ?
Also I believe, that details do matter sometimes.


- -- Package-specific info:
Active plugins:
  - 'filebrowser'
  -  'time'
  -  'docinfo'
  -  'modelines'
  -  'spell'

No plugin installed in $HOME.

Module versions:
  pkg-config unavailable


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt2edtr (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gedit depends on:
ii  gedit-common   3.14.0-3
ii  gir1.2-peas-1.01.12.1-2
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  iso-codes  3.57-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-13
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libenchant1c2a 1.6.0-10.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgirepository-1.0-1  1.42.0-2.2
ii  libglib2.0-0   2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libgtksourceview-3.0-1 3.14.1-1
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpeas-1.0-0  1.12.1-2
ii  libx11-6   2:1.6.2-3
ii  libxml22.9.1+dfsg1-4
ii  python3-gi 3.14.0-1
ii  python3-gi-cairo   3.14.0-1
pn  python3:any

Versions of packages gedit recommends:
ii  yelp3.14.1-1
ii  zenity  3.14.0-1

Versions of packages gedit suggests:
ii  gedit-plugins  3.14.0-2

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlSzYxcACgkQ5+rBHyUt5wsyVQCeLwaD+4kJdQzMh2tsev+i6d50
Bx4AoLTqHTFzBMdOuZu1n4bHZ/q59PyO
=YTbN
-END PGP SIGNATURE-

Bug#774830: simple-scan: pixma 04A9173B 'Access to resource has been denied' over remote desktop

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Package: simple-scan
Version: 3.4.2-1
Severity: minor

Dear Maintainer,

simple-scan does not work over x2go-remote-desktop session.
See there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761398

It is most probably a problem with user-rights and and with the sane-backend.
When trying to scan, it looks like this on the terminal:

andreas@md-ho:~$ simple-scan
p11-kit: invalid config filename, will be ignored in the
future: /etc/pkcs11/modules/gnome-keyring-module

** (simple-scan:23088): WARNING **: scanner.vala:801: Unable to get open 
device: Access
to resource has been denied

xsane says: 'Failed to open device 'pixma:04A9172B': Access to resource has 
been dnied.

But scanning works, when there is a local session running on the machine (i.e. 
the
remote-desktop server) from the same user.

Normally this is no problem at all for thin-clients, because they do not have a 
scanner
connected to the desktop-server. But in my case it is a problem. I also do 
acknowledge
that not many people do have this problem, so it is severity 3 only.

Please let me know, if I should rather report this against the sane-backend.

I also report this to x2go.


- -- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.65cags (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages simple-scan depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-3
ii  gnome-icon-theme 3.4.0-2
ii  libc62.13-38+deb7u6
ii  libcairo21.12.2-3
ii  libcolord1   0.1.21-1
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.33.12+really2.32.4-5
ii  libgtk-3-0   3.4.2-7
ii  libgudev-1.0-0   204-14~bpo70+1
ii  libjpeg8 8d-1+deb7u1
ii  libsane  1.0.22-7.4
ii  xdg-utils1.1.0~rc1+git20111210-6+deb7u1
ii  zlib1g   1:1.2.7.dfsg-13

simple-scan recommends no packages.

simple-scan suggests no packages.

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlSuNqsACgkQ5+rBHyUt5wv8wQCgwPoz1+9lw0p1Z08I7+V3oirf
h8oAnRrtX8ncOYirI9/4OwM9fwhONjr7
=xaIE
-END PGP SIGNATURE-

Bug#773627: drag-and-drop from automounted media seems to work currently

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Drag-and-drop from automounted USB-media seems to work currently, but it seems 
to work
only.
The files are not accessible to applications, so the severity of this was 
upgraded.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlSuKrgACgkQ5+rBHyUt5wtD/wCeJwsdeWIm4UffW+I9Jz+WfhaI
YKUAnjzFcZOIwotdKbDIXPCNi0ob1zII
=WRsW
-END PGP SIGNATURE-

Bug#773627: gvfs-automount makes devices invisible to fdisk

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: gvfs
Version: 1.22.2-1
Severity: minor

Dear Maintainer,

drag-and-drop used to be not workable from gvfs-automounted usb-media, both 
with GNOME
and Cinnamon. XFCE-desktop does not show such strange behaviour. This is fixed 
already
again, but the problem remains, that fdisk does not see storage-devices, that 
were
automounted. When you decide, not to automount them, they are not visible 
either. It's a
problem.

When dragging files from automounted media into a terminal-window, they look 
like this:

'/run/user/1003/gvfs/mtp:host=%5Busb%3A001%2C006%5D/your-local-path'


- -- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt2edtr (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gvfs depends on:
ii  gvfs-common   1.22.2-1
ii  gvfs-daemons  1.22.2-1
ii  gvfs-libs 1.22.2-1
ii  libc6 2.19-13
ii  libglib2.0-0  2.42.1-1
ii  libudev1  215-7

gvfs recommends no packages.

Versions of packages gvfs suggests:
ii  gvfs-backends  1.22.2-1

- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlSWWXsACgkQ5+rBHyUt5wspAwCglEdIW4ohUJEHrQEymrQAhV0f
DpwAn0BXCI4SJ92+HeWWwwUUOQWsZD72
=e0Ba
-END PGP SIGNATURE-

Bug#769778: DSDT table dissasmbled of HP t5735

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[see attachment: DSDT.dsl.xz]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlR5cWgACgkQ5+rBHyUt5wuLOACgnlJknSuh5qw298OlSQD+tnNZ
KOUAoIm4bc5mqk5bFgMNG73FvURMlov+
=3od8
-END PGP SIGNATURE-


DSDT.dsl.xz
Description: application/xz

Bug#761398: This is not workable as described in the Debian-Administratior's Handbook on Jessie/testing

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Today I tried the recipe described there on another system:

http://debian-handbook.info/browse/stable/sect.remote-login.html
[see bottom of the page]

This is not workable on Jessie/testing, both as client and as vnc-host.

I set up GNU-inetd:
i   inetutils-inetd   - internet super server

Then edited /etc/lightdm.conf and added that line to /etc/inetd.conf

These options did not set this straight either:
> xserver-allow-tcp = True #if TCP/IP connections are allowed to this X server
> xdmcp-manager = XDMCP #manager to connect to (implies xserver-allow-tcp=true)

additionally to:

> [XDMCPServer]
> enabled=true
> port=177

Result:
> andrew@s5:~$ xtightvncviewer remserv:50
> xtightvncviewer: VNC server closed connection
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlR1vhoACgkQ5+rBHyUt5wu9kQCfbXlJWbzvGZzQoyXFWhlKhR7s
HnsAnii/l2rxBgdH+9ErGRTlDhviUCSk
=3GhF
-END PGP SIGNATURE-

Bug#761398: Fw: An IBM message from Andreas Glaeser

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Begin forwarded message:

Date: Tue, 25 Nov 2014 10:15:29 -0500
From: "Andreas Glaeser" 
To: "Andreas Glaeser" 
Subject: An IBM message from Andreas Glaeser



Dear Andreas Glaeser,

IBM is sending this e-mail message to you at my request. I thought you would 
find the
content referenced on the IBM web page below of interest:

Enable multiuser logins with VNC

Note: The links within this e-mail message will expire in 90 days. Links to
password-protected or dynamic content may not operate.

IBM is committed to protecting your privacy. You may view IBM's privacy policy 
at:

http://www.ibm.com/privacy/us/en/

 

 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlR1gToACgkQ5+rBHyUt5wtj7wCffwFSSc58fLYs3LeUk+/UccFN
cDEAoIyDjwtGOeFK2CODJnwcfeAO7/nr
=GoDj
-END PGP SIGNATURE-

Bug#761398: VNC with XDMCP also works with xinetd

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Now I tried this recipe:

http://www.ibm.com/developerworks/library/os-multiuserloginsvnc/index.html
[see below]

It works fine for me with tightvncserver, but I had to restart the remote 
server once in
order to be able to log in to it with xtightvncviewer.
This is probably better for people who don't want to pull in external packages 
to their
systems in order to make remote connections.

There is another example with inetd instead of xinetd, which I haven't tried 
yet, but it
should probably also work:

http://debian-handbook.info/browse/stable/sect.remote-login.html

Also when inside your own LAN, you are probably behind a firewall and you don't 
need to
use ssh.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlR0nGMACgkQ5+rBHyUt5wsQagCfW+V1kR3dJWDRWzlWvGstJQ1a
KDMAoL4jS0W0KPv5l9jUYb7TnJhc6iaB
=JnnK
-END PGP SIGNATURE-

Bug#769502: Info received (firmware-linux-nonfree is the culprit)

[Andreas Glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, 22 Nov 2014 09:42:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian X Strike Force 
> 
> If you wish to submit further information on this problem, please
> send it to 769...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

There is no DVI-output even without the RADEON-firmware from the moment, when 
the
lightdm-loginscreen would appear normally.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlRwXB4ACgkQ5+rBHyUt5wttCwCfbUUvu9+fsdsZBHGxdBkmE0uG
W2UAnjEkfif+unT98DdZ448eyv4C37ky
=NCZD
-END PGP SIGNATURE-