Bug#1065404: virt-manager: Cannot load AooArmor profile

[Erik de Castro Lopo]

Package: virt-manager
Version: 1:4.1.0-3
Severity: normal

Dear Maintainer,

I moved the `/var/lib/libvirt/images` directory to a new disk at 
`/libvirt/images`
and created a symlink from the former to the later.

The 3 VM disk images were working at the old location but at the new location
I get an error:

libvirt.libvirtError: internal error: cannot load AppArmor profile 
'libvirt-'

Running virt-manager as recommended:

  > virt-manager  --debug  --no-fork
  [Mon, 04 Mar 2024 10:21:10 virt-manager 32] DEBUG (cli:204) Version 4.1.0 
launched with command line: /usr/bin/virt-manager --debug --no-fork
  [Mon, 04 Mar 2024 10:21:10 virt-manager 32] DEBUG (virtmanager:167) 
virt-manager version: 4.1.0
  [Mon, 04 Mar 2024 10:21:10 virt-manager 32] DEBUG (virtmanager:168) 
virtManager import: /usr/share/virt-manager/virtManager
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (virtmanager:205) 
PyGObject version: 3.47.0
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (virtmanager:209) GTK 
version: 3.24.41
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (systray:84) Imported 
AppIndicator3=
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (systray:86) 
AppIndicator3 is available, but didn't find any dbus watcher.
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (systray:476) Showing 
systray: False
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (inspection:206) python 
guestfs is not installed
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (engine:113) Loading 
stored URIs:
  qemu:///system
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (engine:461) processing 
cli command uri= show_window=manager domain=
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (engine:464) No cli 
action requested, launching default window
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (manager:185) Showing 
manager
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (engine:316) window 
counter incremented to 1
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (engine:211) Initial 
gtkapplication activated
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (connection:482) 
conn=qemu:///system changed to state=Connecting
  [Mon, 04 Mar 2024 10:21:11 virt-manager 32] DEBUG (connection:903) 
Scheduling background open thread for qemu:///system
  [Mon, 04 Mar 2024 10:21:15 virt-manager 32] DEBUG (connection:128) 
libvirt URI versions library=10.0.0 driver=10.0.0 hypervisor=8.2.1
  [Mon, 04 Mar 2024 10:21:15 virt-manager 32] DEBUG (connection:109) 
Fetched capabilities for qemu:///system: 
  

  03d502e0-045e-0541-c606-a40700080009
  
x86_64
Skylake-Client
Intel
































  
  



  
  
  


  tcp
  rdma

  
  

  
49290208
12322552
0
0

  


  
  
  
  
  
  
  
  
  
  
  
  

  

  
  

  
  
apparmor
0
  
  
dac
0
+64055:+64055
+64055:+64055
  

  

  hvm
  
32
/usr/bin/qemu-system-i386
pc-i440fx-8.2
pc
pc-q35-5.2
pc-i440fx-2.12
pc-i440fx-2.0
pc-i440fx-6.2
pc-q35-4.2
pc-i440fx-2.5
pc-i440fx-4.2
pc-i440fx-5.2
pc-q35-2.7
pc-q35-7.1
pc-i440fx-2.2
pc-q35-8.1
pc-i440fx-8.1
pc-i440fx-2.7
pc-q35-6.1
pc-q35-2.4
pc-i440fx-7.1
pc-q35-2.10
x-remote
pc-q35-5.1
pc-q35-2.9
pc-i440fx-2.11
pc-q35-3.1
pc-i440fx-6.1
pc-q35-4.1
pc-i440fx-2.4
pc-i440fx-4.1
pc-i440fx-5.1
pc-i440fx-2.9
isapc
pc-q35-2.6
pc-i440fx-3.1
pc-q35-2.12
pc-q35-7.0
pc-i440fx-2.1
pc-q35-8.0
pc-i440fx-8.0
pc-q35-6.0
pc-i440fx-2.6
pc-q35-4.0.1
pc-i440fx-7.0
pc-q35-5.0
pc-q35-2.8
pc-i440fx-2.10
pc-q35-3.0
pc-q35-7.2
pc-q35-4.0
pc-i440fx-6.0
microvm
pc-i440fx-2.3
pc-i440fx-4.0
pc-q35-8.2
q35
pc-i440fx-5.0
pc-i440fx-2.8
pc-q35-6.2
pc-q35-2.5
pc-i440fx-3.0
pc-i440fx-7.2
pc-q35-2.11
 

Bug#1065247: new lighttpd serves mangled file names

[Erik de Castro Lopo]

Glenn Strauss wrote:

> This will be fixed in the next version of lighttpd, and I'll probably
> submit a patch to Debian sooner.

That would be awesome!!!

Thanks,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#1065247: new lighttpd serves mangled file names

[Erik de Castro Lopo]

Hi,

I have included the config at the bottom of this email.

The files are being served from an ext4 filesystem.

I have noticed something odd though. I created a directory which when
served by lighttpd in Firefox looks like:

Index of /test/
../ -   Directory
This is just a test.mkv/2024-Mar-03 13:22:24583.7M  video/x-matroska
This is just a test.txt/2024-Mar-03 13:05:210.1K
text/plain;charset=utf-8

Notice how both files have a '/' at the end of their name.

In Firefox, if I click on the text file it works just as expected and FF shows
the contents of the text file.

For the video file however it starts a download, but renames the file to
`6GQOZxf0.mpv` (an MS-DOS like 8.3 filename).

If I use wget to retrieve the file I get this:

> wget -S http://white:8080/test/This%20is%20just%20a%20test.mkv/
--2024-03-03 13:38:41--  
http://white:8080/test/This%20is%20just%20a%20test.mkv/
Resolving white (white)... 192.168.1.8
Connecting to white (white)|192.168.1.8|:8080... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  Content-Type: video/x-matroska
  ETag: "72386044"
  Last-Modified: Sun, 03 Mar 2024 02:22:24 GMT
  Content-Length: 612101519
  Accept-Ranges: bytes
  Date: Sun, 03 Mar 2024 02:38:41 GMT
  Server: lighttpd/1.4.74
Length: 612101519 (584M) [video/x-matroska]
Saving to: ‘index.html.1’

However, if I drop the trailing `/` from the filename it works as expected:


> wget -S http://white:8080/test/This%20is%20just%20a%20test.mkv
--2024-03-03 13:40:38--  
http://white:8080/test/This%20is%20just%20a%20test.mkv
Resolving white (white)... 192.168.1.8
Connecting to white (white)|192.168.1.8|:8080... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  Content-Type: video/x-matroska
  ETag: "72386044"
  Last-Modified: Sun, 03 Mar 2024 02:22:24 GMT
  Content-Length: 612101519
  Accept-Ranges: bytes
  Date: Sun, 03 Mar 2024 02:40:38 GMT
  Server: lighttpd/1.4.74
Length: 612101519 (584M) [video/x-matroska]
Saving to: ‘This is just a test.mkv’

My guess is that that problem is in the module that generates the listing
for a directory and that the problem is that it puts a trailing `/` on 
file as well as just directories.

I use lighttpd to serve viedo files for a kodi.tv box, so I cannot maually
correct the generated directory listings that lighttpd gives me.

Thanks,
Erik



> sudo lighttpd -f /etc/lighttpd/lighttpd.conf -p
config {
var.CWD= "/home/erikd"
var.PID= 1524394
server.modules = ("mod_indexfile", "mod_access", 
"mod_alias", "mod_compress", "mod_redirect")
server.document-root   = "/var/www/html"
server.upload-dirs = ("/var/cache/lighttpd/uploads")
server.errorlog= "/var/log/lighttpd/error.log"
server.pid-file= "/var/run/lighttpd.pid"
server.username= "www-data"
server.groupname   = "www-data"
server.port= 8080
server.follow-symlink  = "enable"
dir-listing.activate   = "enable"
index-file.names   = ("index.php", "index.html")
url.access-deny= ("~", ".inc")
static-file.exclude-extensions = (".php", ".pl", ".fcgi")
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype  = ("application/javascript", "text/css", 
"text/html", "text/plain")
mimetype.assign= (
".cwl.json"   => "application/cwl+json",
".sarif.json" => "application/sarif+json",
".sarif-external-properties.json" => 
"application/sarif-external-properties+json",
".spdx.json"  => "application/spdx+json",
".tm.json"=> "application/tm+json",
".tm.jsonld"  => "application/tm+json",
".gpkg.tar"   => "application/vnd.gentoo.gpkg",
".1905.1" => "application/vnd.ieee.1905",
".syft.json"  => "application/vnd.syft+json",
".pcf.Z"  => "application/x-font-pcf",
".tar.bz2"=> "application/x-gtar-compressed",
".tar.gz" => "application/x-gtar-compressed",
".a2l"=> "application/A2L",
".aml"=> "application/AML",
".atf"=> "application/ATF",
".atfx"   => "application/ATFX",
".atxml"  => "application/ATXML",
".cdfx"   => "application/CDFX+XML",
".cea"=> 

Bug#1065247: new lighttpd serves mangled file names

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

> Hi,
> 
> I have included the config at the bottom of this email.
> 
> The files are being served from an ext4 filesystem.
> 
> I have noticed something odd though. I created a directory which when
> served by lighttpd in Firefox looks like:

I found the documentation for the directory listing functionality:

https://redmine.lighttpd.net/projects/lighttpd/wiki/Mod_dirlisting

But that does not seem to offer any clues.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#1065247: new lighttpd servers mangled file names

[Erik de Castro Lopo]

Package: lighttpd
Version: 1.4.74-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I have been using lighttpd for several years without any issue.
 
I just updated it (via apt-get) and now its servers long file names
as short (seemingly MS-DOS) 8.3 file names.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?

I want lighttpd to serve the correct full filename.

   * What outcome did you expect instead?

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


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lighttpd depends on:
ii  init-system-helpers1.66
ii  libc6  2.37-15
ii  libcrypt1  1:4.4.36-4
ii  libnettle8 3.9.1-2+b1
ii  libpcre2-8-0   10.42-4+b1
ii  libxxhash0 0.8.2-2+b1
ii  lsb-base   11.6
ii  media-types10.1.0
ii  mime-support   3.66
ii  systemd-sysv   255.3-2
ii  sysvinit-utils [lsb-base]  3.08-6

Versions of packages lighttpd recommends:
ii  lighttpd-mod-deflate  1.4.74-1
ii  lighttpd-mod-openssl  1.4.74-1
ii  perl  5.38.2-3
ii  spawn-fcgi1.6.4-2

Versions of packages lighttpd suggests:
pn  apache2-utils 
pn  lighttpd-doc  
pn  lighttpd-mod-webdav   
pn  lighttpd-modules-dbi  
pn  lighttpd-modules-lua  
ii  openssl   3.1.5-1
pn  php-cgi   
pn  php-fpm   

-- Configuration Files:
/etc/lighttpd/lighttpd.conf changed:
server.modules = (
"mod_indexfile",
"mod_access",
"mod_alias",
"mod_compress",
"mod_redirect",
)
server.document-root= "/var/www/html"
server.upload-dirs  = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname= "www-data"
server.port = 8080
server.follow-symlink   = "enable"
dir-listing.activate= "enable"
index-file.names= ( "index.php", "index.html" )
url.access-deny = ( "~", ".inc" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir  = "/var/cache/lighttpd/compress/"
compress.filetype   = ( "application/javascript", "text/css", 
"text/html", "text/plain" )
include_shell "/usr/share/lighttpd/create-mime.conf.pl"
include_shell "/usr/share/lighttpd/include-conf-enabled.pl"


-- no debconf information

-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#1026837: debuild: fatal error at line 359

[Erik de Castro Lopo]

Package: devscripts
Version: 2.22.2
Severity: normal

Dear Maintainer,

Trying to build a package in s 32 bit chroot on an x86_64 system.

The command is
```
debuild -us -uc -rfakeroot -j4 --lintian-opts -iI --color always
```
and the error is:
```
debuild: fatal error at line 359:
internal error: dpkg opts list missing proper header
```

Line 359 is:
```
if (shift @othervars ne ">>> $dpkg_opts_var BEGIN <<<") {
```


-- Package-specific info:

--- /etc/devscripts.conf ---
Empty.

--- ~/.devscripts ---
Not present

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages devscripts depends on:
ii  dpkg-dev  1.21.12
ii  fakeroot  1.30.1-1
ii  file  1:5.41-4
ii  gnupg 2.2.40-1
ii  gpgv  2.2.40-1
ii  libc6 2.36-6
ii  libfile-dirlist-perl  0.05-3
ii  libfile-homedir-perl  1.006-2
ii  libfile-touch-perl0.12-2
ii  libfile-which-perl1.27-2
ii  libipc-run-perl   20220807.0-1
ii  libmoo-perl   2.005004-3
ii  libwww-perl   6.67-1
ii  patchutils0.4.2-1
ii  perl  5.36.0-6
ii  python3   3.10.6-3
ii  sensible-utils0.0.17
ii  wdiff 1.2.2-3

Versions of packages devscripts recommends:
ii  apt 2.5.4
ii  curl7.86.0-2
ii  dctrl-tools 2.24-3
ii  debian-keyring  2022.11.30
ii  dput1.1.3
ii  equivs  2.3.1
ii  libdistro-info-perl 1.2
ii  libdpkg-perl1.21.12
ii  libencode-locale-perl   1.05-3
ii  libgit-wrapper-perl 0.048-2
ii  libgitlab-api-v4-perl   0.26-2
ii  liblist-compare-perl0.55-2
ii  liblwp-protocol-https-perl  6.10-1
ii  libsoap-lite-perl   1.27-2
ii  libstring-shellquote-perl   1.04-3
ii  libtry-tiny-perl0.31-2
ii  liburi-perl 5.17-1
ii  licensecheck3.3.0-1
ii  lintian 2.115.3
ii  man-db  2.11.1-1
ii  patch   2.7.6-7
ii  pristine-tar1.50
ii  python3-apt 2.5.0
ii  python3-debian  0.1.49
ii  python3-magic   2:0.4.26-2
ii  python3-requests2.28.1+dfsg-1
ii  python3-unidiff 0.7.3-1
ii  python3-xdg 0.28-2
ii  strace  5.10-1
ii  unzip   6.0-27
ii  wget1.21.3-1+b1
ii  xz-utils5.4.0-0.1

Versions of packages devscripts suggests:
pn  adequate 
pn  at   
pn  autopkgtest  
pn  bls-standalone   
ii  bsd-mailx [mailx]8.1.2-0.20220412cvs-1
ii  build-essential  12.9
pn  check-all-the-things 
pn  cvs-buildpackage 
ii  debhelper13.11.3
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  elpa-devscripts  
pn  faketime 
pn  gnuplot  
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-3
pn  libdbd-pg-perl   
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3300-2
pn  libyaml-syck-perl
pn  mmdebstrap   
pn  mozilla-devscripts   
pn  mutt 
ii  openssh-client [ssh-client]  1:9.1p1-1
pn  piuparts 
pn  postgresql-client
pn  pristine-lfs 
pn  quilt
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- no debconf information

Bug#1012843: i2pd: Default install SEGV

[Erik de Castro Lopo]

Package: i2pd
Version: 2.41.0-1+b1
Severity: important

Dear Maintainer,

* Installed i2pd.
* `systemctl status i2pd` reports:
× i2pd.service - I2P Router written in C++
 Loaded: loaded (/lib/systemd/system/i2pd.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: signal) since Wed 2022-06-15 21:25:17 AEST; 
1min 51s ago
   Docs: man:i2pd(1)
 https://i2pd.readthedocs.io/en/latest/
Process: 23181 ExecStart=/usr/sbin/i2pd $DAEMON_OPTS (code=killed, 
signal=SEGV)
CPU: 72ms

Jun 15 21:25:14 ada systemd[1]: Starting I2P Router written in C++...
Jun 15 21:25:14 ada systemd[1]: i2pd.service: Control process exited, 
code=killed, status=11/SEGV
Jun 15 21:25:17 ada systemd[1]: i2pd.service: Failed with result 'signal'.
Jun 15 21:25:17 ada systemd[1]: Failed to start I2P Router written in C++.

* `systemctl restart i2pd` has the same issue.

* I expect it to run out of the box (especially not SEGV).


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages i2pd depends on:
ii  adduser 3.121
ii  init-system-helpers 1.63
ii  libboost-filesystem1.74.0   1.74.0-16
ii  libboost-program-options1.74.0  1.74.0-16
ii  libc6   2.33-7
ii  libgcc-s1   12.1.0-2
ii  libminiupnpc17  2.2.3-1+b1
ii  libssl3 3.0.3-7
ii  libstdc++6  12.1.0-2
ii  lsb-base11.2
ii  zlib1g  1:1.2.11.dfsg-4

i2pd recommends no packages.

i2pd suggests no packages.

-- no debconf information

Bug#1007989: virt-manager: Error launching create dialog

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

> Package: virt-manager
> Version: 1:4.0.0-1
> Severity: important
> 
> Dear Maintainer,
> 
> When I run virt-manager and try to create a new VM I get a dialog box saying:
> 
> Error launching create dialog:
> programming error: Did not find widget name = disk-detect-zeros


After restart libvirt it was all fine. This can be closed. Thanks!

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#1007989: virt-manager: Error launching create dialog

[Erik de Castro Lopo]

Package: virt-manager
Version: 1:4.0.0-1
Severity: important

Dear Maintainer,

When I run virt-manager and try to create a new VM I get a dialog box saying:

Error launching create dialog:
programming error: Did not find widget name = disk-detect-zeros

In the "details" dialog it also has:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/createvm.py", line 176, in 
show_instance
cls._instance = vmmCreateVM()
  File "/usr/share/virt-manager/virtManager/createvm.py", line 202, in 
__init__
self._addstorage = vmmAddStorage(self.conn, self.builder, self.topwin)
  File "/usr/share/virt-manager/virtManager/device/addstorage.py", line 59, 
in __init__
def _cleanup(self):
  File "/usr/share/virt-manager/virtManager/device/addstorage.py", line 
118, in _init_ui
skip_paths = src.config.get_perms_fix_ignore()
  File "/usr/share/virt-manager/virtManager/baseclass.py", line 311, in 
widget
raise xmlutil.DevError("Did not find widget name=%s" % name)
virtinst.xmlutil.DevError: programming error: Did not find widget 
name=disk-detect-zeroes

If I run it as `virt-manager --debug --no-fork` it still seems to fork, but I 
see this on
the console:

  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (cli:204) Launched 
with command line: /usr/bin/virt-manager --no-fork --debug
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (virtmanager:167) 
virt-manager version: 4.0.0
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (virtmanager:168) 
virtManager import: /usr/share/virt-manager/virtManager
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (virtmanager:205) 
PyGObject version: 3.42.0
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (virtmanager:209) GTK 
version: 3.24.33
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (systray:84) Imported 
AppIndicator3=
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (systray:86) 
AppIndicator3 is available, but didn't find any dbus watcher.
  [Sun, 20 Mar 2022 11:24:28 virt-manager 1455533] DEBUG (engine:244) Connected 
to remote app instance.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  gir1.2-gtk-3.0   3.24.33-1
ii  gir1.2-gtk-vnc-2.0   1.0.0-1+b1
ii  gir1.2-gtksource-4   4.8.2-1
ii  gir1.2-libosinfo-1.0 1.8.0-1
ii  gir1.2-libvirt-glib-1.0  4.0.0-2
ii  gir1.2-vte-2.91  0.67.90-2
ii  python3  3.9.8-1
ii  python3-dbus 1.2.18-3+b1
ii  python3-gi   3.42.0-3
ii  python3-gi-cairo 3.42.0-3
ii  python3-libvirt  8.0.0-1
ii  virtinst 1:4.0.0-1

Versions of packages virt-manager recommends:
ii  gir1.2-ayatanaappindicator3-0.1  0.5.90-7
ii  gir1.2-spiceclientglib-2.0   0.39-3
ii  gir1.2-spiceclientgtk-3.00.39-3
ii  libvirt-daemon-system8.0.0-1

Versions of packages virt-manager suggests:
pn  gir1.2-secret-1  
ii  gnome-keyring40.0-3
pn  python3-guestfs  
pn  ssh-askpass  
ii  virt-viewer  7.0-2+b1

Versions of packages virt-manager is related to:
ii  libvirt-clients  8.0.0-1
ii  libvirt-daemon   8.0.0-1
ii  libvirt0 8.0.0-1
ii  osinfo-db0.20220214-1

-- no debconf information

Bug#1006990: postgresql-autodoc: Templates files not found

[Erik de Castro Lopo]

Package: postgresql-autodoc
Version: 1.41+20200921-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Installed the package and ran:

/usr/bin/postgresql_autodoc -d 

Templates files not found in 
/build/postgresql-autodoc-qtvh3E/postgresql-autodoc-1.41+20200921/debian/postgresql-autodoc/usr/share/postgresql-autodoc

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

N/a

   * What was the outcome of this action?

Template files not found.

   * What outcome did you expect instead?

Template files found and a schema diagram to be generated.
 


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages postgresql-autodoc depends on:
ii  libdbd-pg-perl 3.15.1-1
ii  libhtml-template-perl  2.97-1.1
ii  libterm-readkey-perl   2.38-1+b3

postgresql-autodoc recommends no packages.

Versions of packages postgresql-autodoc suggests:
pn  docbook-book  
ii  graphviz  2.42.2-6

-- no debconf information

Bug#991496: libsndfile: CVE-2021-3246

[Erik de Castro Lopo]

I m not longer the maintainer of libsndfile.

You can contact the new maintainers at

   https://github.com/libsndfile/

Erik

Moritz Mühlenhoff wrote:

> Source: libsndfile
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following vulnerability was published for libsndfile.
> 
> CVE-2021-3246[0]:
> | A heap buffer overflow vulnerability in msadpcm_decode_block of
> | libsndfile 1.0.30 allows attackers to execute arbitrary code via a
> | crafted WAV file.
> 
> https://github.com/libsndfile/libsndfile/issues/687
> 
> Patch is here:
> https://github.com/libsndfile/libsndfile/commit/deb669ee8be55a94565f6f8a6b60890c2e7c6f32
> 
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2021-3246
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3246
> 
> Please adjust the affected versions in the BTS as needed.
> 


-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#945073: More info

[Erik de Castro Lopo]

Some more info.

To reproduce:

* Clone https://github.com/xiph/flac

* Install clang-9, clang++-9 libfuzzer-9-dev

* In the flac checkout:

  > CC=clang-9 CXX=clang++-9 ./configure --enable-oss-fuzzers && make

The above works as expected in x86_64 and fails on i386.

Thanks,
Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#945073: libclang-common-9-dev: missing libclang_rt.fuzzer-i386.a

[Erik de Castro Lopo]

Package: libclang-common-9-dev
Version: 1:9.0.0-3+b1
Severity: normal

Dear Maintainer,

I have a project (FLAC) which has a configure option to build fuzzers
to be run in Google's Oss-Fuzz infratructure.

Configuring on x86_64 works correctly and builds the fuzzers
but in i386 I get:

> /usr/bin/ld: cannot find 
> /usr/lib/llvm-9/lib/clang/9.0.0/lib/linux/libclang_rt.fuzzer-i386.a: No such 
> file or directory

ld seems to know where the file *should* be, but it is not there. I have
installed libfuzzer-9-dev.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libclang-common-9-dev depends on:
ii  lib64atomic1  9.2.1-19
ii  lib64gcc1 1:9.2.1-19
ii  lib64stdc++6  9.2.1-19
ii  libatomic19.2.1-19
ii  libc6 2.29-3
ii  libc6-amd64   2.29-3
ii  libgcc1   1:9.2.1-19
ii  libllvm9  1:9.0.0-3+b1
ii  libstdc++69.2.1-19
ii  libtinfo6 6.1+20191019-1
ii  libz3-4   4.8.6-2+b1
ii  zlib1g1:1.2.11.dfsg-1+b1

libclang-common-9-dev recommends no packages.

libclang-common-9-dev suggests no packages.

-- no debconf information

Bug#914381: libsndfile: CVE-2018-19432

[Erik de Castro Lopo]

Petter Reinholdtsen wrote:

> According to https://security-tracker.debian.org/tracker/CVE-2018-19432 
> >,
> this security issue is only fixed in the jessie (oldoldstable) security
> repository. Why is it not fixed in unstable, stable and oldstable?

YOu need to ask the debian people as they are the ones that apply
patches to my releases.

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

> I removed courier-imap-ssl and no i no longer get the "No supported cipher
> suite ..." error message.
> 
> I no longer see this problem.

Bah, turned out I was connecting to IMAP instead of IMAPS and that is
why it was working.

After making sure I was using IMAPS I was not longer able to connect,
again with the "No supported cipher suite ..." error.

I did however manage to fix it my doing "apt purge courier-imap" and
then "apt install courier-imap" and after acccepting the new certificate
all was well!

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?

[Erik de Castro Lopo]

Markus Wanner wrote:

> I removed courier-imap-ssl, as it's a transitional package in stretch,
> already.  It can be removed safely.

I removed courier-imap-ssl and no i no longer get the "No supported cipher
suite ..." error message.

I no longer see this problem.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?

[Erik de Castro Lopo]

Hi all,

I have just run into this same issue and its a bit of a pain.

One thing I notivce however is that I have:
  
  # dpkg -l | grep courier-imap
  ii  courier-imap  5.0.5+1.0.5-1 amd64   Courier mail server - IMAP 
server
  ii  courier-imap-ssl  4.18.1+0.78.0-2   all Courier mail server - IMAP 
over TLS [transitional]

I also notice thatt these two are compiled from different source packages:

  # apt-cache show courier-imap
  Package: courier-imap
  Source: courier (1.0.5-1)
  Version: 5.0.5+1.0.5-1

  # apt-cache show courier-imap-ssl
  Package: courier-imap-ssl
  Source: courier (0.78.0-2)
  Version: 4.18.1+0.78.0-2

I also know that courier-imap-ssl depends on courier-imap but I wonder if
the fact they are compiled from different versions of the source package
is relevant.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#911126: nouveau: Black screen after reboot

[Erik de Castro Lopo]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.15-3
Severity: important

Dear Maintainer,

This deskop system had been up and working fine with the nouveau driver
for at least two months, then did an apt update/upgrade and the graphics 
hung. I then switched to the console and first tried restarting the
graphics (/etc/init.d/lightdm restart) and when that didn't help
rebooted (which also did not help).

If I start lightdm the screen flashes (about a 5 second cycle) between
pure black (no light at all) and something that is lit, but show no
image.

This machine did have the NVidia driver on it at one stage but for the
last several months has been running with nouveau.

I would really just like the graphics to work.

Cheers,
Erik

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050] [10de:1c81] (rev a1)

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

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 226 Jul 20 01:49 90-xpra-virtual.conf

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

Kernel version (/proc/version):
---
Linux version 4.18.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.10-2 (2018-10-07)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 63828 May 28 22:07 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 50320 Oct 16 13:38 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[84.912] 
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[84.912] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[84.912] Current Operating System: Linux ada 4.18.0-2-amd64 #1 SMP Debian 
4.18.10-2 (2018-10-07) x86_64
[84.912] Kernel command line: BOOT_IMAGE=/vmlinuz-4.18.0-2-amd64 
root=/dev/mapper/dark--vg-root ro quiet
[84.912] Build Date: 26 September 2018  10:20:47AM
[84.912] xorg-server 2:1.20.1-4 (https://www.debian.org/support) 
[84.912] Current version of pixman: 0.34.0
[84.912]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[84.912] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[84.912] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 16 13:38:57 
2018
[84.912] (==) Using config directory: "/etc/X11/xorg.conf.d"
[84.912] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[84.912] (==) No Layout section.  Using the first Screen section.
[84.912] (==) No screen section available. Using defaults.
[84.912] (**) |-->Screen "Default Screen Section" (0)
[84.912] (**) |   |-->Monitor ""
[84.912] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[84.912] (==) Automatically adding devices
[84.912] (==) Automatically enabling devices
[84.912] (==) Automatically adding GPU devices
[84.912] (==) Max clients allowed: 256, resource mask: 0x1f
[84.912] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[84.912]Entry deleted from font path.
[84.912] (==) 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
[84.912] (==) ModulePath set to "/usr/lib/xorg/modules"
[84.912] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[84.912] (II) Loader magic: 0x55e8b099ce20
[84.912] (II) Module ABI versions:
[84.912]X.Org ANSI C Emulation: 0.4
[84.912]X.Org Video Driver: 24.0
[84.912]X.Org XInput driver : 24.1
[84.912]X.Org Server Extension : 10.0
[84.913] (++) using VT number 7

[84.913] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[84.914] (II) xfree86: Adding drm device (/dev/dri/card0)
[84.915] (--) PCI:*(1@0:0:0) 10de:1c81:1458:3765 rev 161, Mem @ 
0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @ 
0xe000/128, BIOS @ 0x/131072
[84.915] (II) LoadModule: "glx"
[84.915] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[84.916] (II) Module glx: vendor="X.Org Foundation"
[84.916]compiled for 1.20.1, module version = 1.0.0

Bug#900717: Failed to get GBM bo for flip to new front

[Erik de Castro Lopo]

I'm seeing a gazzilion of these messages in /var/log/Xorg.0.log:

   [2366588.693] (EE) modeset(0): Failed to get GBM bo for flip to new front.
   [2366588.693] (EE) modeset(0): present flip failed

My machine currently has an uptime of 27 days, and /var/log/Xorg.0.log
has grown to 2.8G in size and I am getting warnins about my / partition
filling up.

Currently only solution seems to be logging out and restarting X.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#906622: pulseaudio: Only provides dummy output

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

> After a recent upgrade and then a couple of days later a reboot Pulseaudio
> stopped working with the sound hardware, and only provided a single "Dummy 
> output".
> That was using pulseaudio 11.? and since 12.0 was available I upgraded to 
> that, but
> still get nothing but the "Dummy output" device.

Just after I reported this I tried one more thing, I killed the
"mate-volume-control-applet". My sound started working again immediately.
I didn't have to reboot or logout or anything. I already had a test 
audio program running and as soon as "mate-volume-control-applet" was
kill, the audio started coming out.

Not sure if this bug should be re-assigned to mate-media or not.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#906622: pulseaudio: Only provides dummy output

[Erik de Castro Lopo]

Package: pulseaudio
Version: 12.0-1
Severity: important

Dear Maintainer,

After a recent upgrade and then a couple of days later a reboot Pulseaudio
stopped working with the sound hardware, and only provided a single "Dummy 
output".
That was using pulseaudio 11.? and since 12.0 was available I upgraded to that, 
but
still get nothing but the "Dummy output" device.

The sound hardware is detected by "aplay":

> aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3266 Analog [ALC3266 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I did notice in bug #904098 that timidity may cause this problem so I
uninstalled it, logged out and logged back in again but still only 
the dummy output.



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.117
ii  libasound2   1.1.6-1
ii  libasound2-plugins   1.1.6-1+b1
ii  libc62.27-5
ii  libcap2  1:2.25-1.2
ii  libdbus-1-3  1.12.10-1
ii  libgcc1  1:8.2.0-3
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-2.1
ii  liborc-0.4-0 1:0.4.28-2
ii  libpulse012.0-1
ii  libsm6   2:1.2.2-1+b3
ii  libsndfile1  1.0.28-4
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.2.0-3
ii  libsystemd0  239-7
ii  libtdb1  1.3.15-4
ii  libudev1 239-7
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.5-1
ii  libxcb1  1.13-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 9.20170808
ii  pulseaudio-utils 12.0-1

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.10-1
ii  libpam-systemd 239-7
ii  rtkit  0.11-6

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 239-7

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied 

Bug#900259: mate-tweak: Colors in marco-compton are weird

[Erik de Castro Lopo]

Alex ARNAUD wrote:

> Hello Erik,
> 
> Thank you for this report. What I can understand in your report is 
> related to Marco, right?
> 
> Do we agree that Marco Compton is not enabled by default?

marco-compton is not enabled by default. I had to install mate-tweak
and then switch from marco to marco-compton.

> Can you tell us what is your graphic card? What driver are you using 
> with It?

THe video carda is : 

NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1)

and I'm using xserver-xorg-video-nouveau.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#900259: mate-tweak: Colors in marco-compton are weird

[Erik de Castro Lopo]

Package: mate-tweak
Version: 18.04.16-1
Severity: normal

Dear Maintainer,

Had been experiencing some flakiness in my video display and then the
mounse and keyboard locked up. I sshed in from another machine and tried
'sudo init 6', but that lock up the terminal session. Finally I resorted
to a hard reset.

On reboot, the lightdm login screen was fine, but when I logged in all
the mate components (top bar, mate terminal etc) were being dimplayed
in weird colours (reds and yellows, it looked like an indexed 256 colour
pallete). 

After some considerable debugging I found that switching from the 
marco-compton window manager back to just marco fixed everything. To make
sure this is what it was, I switched back to the compton version which
again had weird colours and then back to marco which fixed the issue.

IMHO, marco-compton should either be fixed or deprecated.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-tweak depends on:
ii  dconf-cli  0.28.0-2
ii  gir1.2-gtk-3.0 3.22.29-3
ii  gir1.2-notify-0.7  0.7.7-3
ii  mate-panel 1.20.1-3
ii  mesa-utils 8.4.0-1
ii  python33.6.5-3
ii  python3-gi 3.28.2-1
ii  python3-pkg-resources  39.1.0-1
ii  python3-psutil 5.4.2-1
ii  python3-setproctitle   1.1.10-1+b1
ii  x11-xserver-utils  7.7+8

Versions of packages mate-tweak recommends:
ii  compton0.1~beta2+20150922-1
ii  mate-indicator-applet  1.20.0-1

Versions of packages mate-tweak suggests:
pn  indicator-application  
pn  indicator-messages 
pn  indicator-power
pn  indicator-session  
pn  indicator-sounds   

-- no debconf information

Bug#892130: qtchooser: qtconfig doesn't find qt5 version

[Erik de Castro Lopo]

Package: qtchooser
Version: 64-ga1b6736-5
Severity: normal

Dear Maintainer,

I run a few Qt apps in the Mate desktop environment. When I run `qtconfig` on 
the
commandline I get:

> qtconfig
qtconfig: could not exec '/usr/lib/qt5/bin/qtconfig': No such file or 
directory

When I use apt-file to search for "bin/qtconfig" I get:

> apt-file search bin/qtconfig
qt4-qtconfig: /usr/bin/qtconfig-qt4
qt4-qtconfig: /usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig
qtchooser: /usr/bin/qtconfig

so the error message above from "qtchooser" is pointing to an executable that 
does
not exist in Debain.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qtchooser depends on:
ii  libc6   2.26-6
ii  libgcc1 1:8-20180218-1
ii  libstdc++6  8-20180218-1

qtchooser recommends no packages.

qtchooser suggests no packages.

-- no debconf information

Bug#877575: network-manager: brcmfmac fails to load firmware

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836280
> Can you be more specific how this bug report is different to #836280?

Its not. Should I reopen the previous bug?

> Why is a failure to load a firmware a network-manager bug?

Last time I raise this against the kernel and it was redirected to
network-manager and it was fixed when a new version of network-manager
was released.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#877575: network-manager: brcmfmac fails to load firmware

[Erik de Castro Lopo]

Package: network-manager
Version: 1.8.4-1
Severity: normal

Dear Maintainer,

I'm running Debian testing. Today I upgraded everything and wifi
stopped working. The symptoms are *identical* to the problems I
reported in: 

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

which turned out to be a network-manager issue.

I have tried the workaround in:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835553#31

but that doesn't help.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser3.116
ii  dbus   1.11.16+really1.10.24-1
ii  init-system-helpers1.49
ii  libaudit1  1:2.7.7-1+b2
ii  libbluetooth3  5.47-1
ii  libc6  2.24-17
ii  libcurl3-gnutls7.55.1-1
ii  libglib2.0-0   2.54.0-1
ii  libgnutls303.5.15-2
ii  libjansson42.10-1
ii  libmm-glib01.6.8-1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.20-1+b1
ii  libnl-3-2003.2.27-2
ii  libnm0 1.8.4-1
ii  libpam-systemd 234-3
ii  libpolkit-agent-1-00.105-18
ii  libpolkit-gobject-1-0  0.105-18
ii  libpsl50.18.0-4
ii  libreadline7   7.0-3
ii  libselinux12.7-2
ii  libsystemd0234-3
ii  libteamdctl0   1.26-1+b1
ii  libudev1   234-3
ii  libuuid1   2.29.2-5
ii  lsb-base   9.20170808
ii  policykit-10.105-18
ii  udev   234-3
ii  wpasupplicant  2:2.4-1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base 2.77-2
ii  iptables 1.6.1-2
ii  iputils-arping   3:20161105-1
ii  isc-dhcp-client  4.3.5-3
ii  modemmanager 1.6.8-1
ii  ppp  2.4.7-1+4

Versions of packages network-manager suggests:
pn  libteam-utils  

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
[device]
wifi.scan-rand-mac-address=no


-- no debconf information

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Lisandro Damián Nicanor Pérez Meyer wrote:

> As you can see in
> 
>   <https://codereview.qt-project.org/#/c/186122/1//ALL,unified>
> 
> the patch is not exactly right.

I've have be running with that patch in its current form since the start
of the year. Afaiac its works as intended.

> That needs to be fixed before we add that patch, be it locally or in upstream 
> (although upstream is much better).

So who is it that does that? 

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Lisandro Damián Nicanor Pérez Meyer wrote:

> forwarded 841951 https://bugreports.qt.io/browse/QTBUG-58910
> thanks
> 
> Erik: if possible please subscribe to the upstream bug, maybe we can
> iron out another bug in the process.

To fix this issue locally, I have force (ie, quick and dirty) installed a
patched version of libqxcb-glx-integration.so, but every time I update that
package it breaks bitcoin-qt.

Since upstream seem to be in no hurry to fix this, can debian not ship 
a patched version, at least until upstream fixes it?

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#866087: clang-5.0: Hard coded location for libFuzzer

[Erik de Castro Lopo]

Package: clang-5.0
Version: 1:5.0~svn305653-1
Severity: normal

Dear Maintainer,

I've installed clang-5.0 and libfuzzer-5.0-dev. According to the LLVM docs
here:

http://llvm.org/docs/LibFuzzer.html

I should be able to do:

clang-5.0 -g -fsanitize=fuzzer,address fuzz-target.c-o fuzz-target

but that results in the error:

/usr/bin/ld: cannot find /usr/lib/libLLVMFuzzer.a: No such file or directory
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)

The problem seems to be that Clang has a hard-coded location for the libFuzzer
library (/usr/lib/) which does not match the actual location on Debian which is

/usr/lib/llvm-5.0/lib/libFuzzer.a

Cheers,
Erik


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, armhf, i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clang-5.0 depends on:
ii  binutils 2.28-6
ii  libc62.24-12
ii  libc6-dev2.24-12
ii  libclang-common-5.0-dev  1:5.0~svn305653-1
ii  libclang1-5.01:5.0~svn305653-1
ii  libgcc-6-dev 6.3.0-18
ii  libgcc1  1:7.1.0-7
ii  libjsoncpp1  1.7.4-3
ii  libllvm5.0   1:5.0~svn305653-1
ii  libobjc-6-dev6.3.0-18
ii  libstdc++-6-dev  6.3.0-18
ii  libstdc++6   7.1.0-7
ii  libtinfo56.0+20161126-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages clang-5.0 recommends:
ii  llvm-5.0-dev  1:5.0~svn305653-1
ii  python2.7.13-2

Versions of packages clang-5.0 suggests:
pn  clang-5.0-doc  
pn  gnustep
pn  gnustep-devel  
pn  libomp-dev 

-- no debconf information

Bug#860159: libsamplerate: CVE-2017-7697

[Erik de Castro Lopo]

Salvatore Bonaccorso wrote:

> Source: libsamplerate
> Version: 0.1.8-8
> Severity: important
> Tags: security upstream
> 
> Hi,
> 
> the following vulnerability was published for libsamplerate.
> 
> CVE-2017-7697[0]:
> | In libsamplerate before 0.1.9, a buffer over-read occurs in the
> | calc_output_single function in src_sinc.c via a crafted audio file.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

This bug was reported within the last 24 hours, but was fixed over
6 months ago and released as part of version 0.1.9.

Obviously, I cannot go back an retoactively update the changelog.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#841951: [PATCH]: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Hi,

The attached patch applied to the qtbase-opensource-src-5.7.1+dfsg
source packages fixes the segfault for me.

The 5.8.0 package in experimental without this patch still segfaults.
I haven't tried applying this patch to that version.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/
Description: qglxconvenience: Avoid NULL dereference

Index: qtbase-opensource-src-5.7.1+dfsg/src/platformsupport/glxconvenience/qglxconvenience.cpp
===
--- qtbase-opensource-src-5.7.1+dfsg.orig/src/platformsupport/glxconvenience/qglxconvenience.cpp
+++ qtbase-opensource-src-5.7.1+dfsg/src/platformsupport/glxconvenience/qglxconvenience.cpp
@@ -207,6 +207,9 @@ GLXFBConfig qglx_findConfig(Display *dis
 
 QXlibPointer visual(glXGetVisualFromFBConfig(display, candidate);
 
+if (! visual)
+continue;
+
 const int actualRed = qPopulationCount(visual->red_mask);
 const int actualGreen = qPopulationCount(visual->green_mask);
 const int actualBlue = qPopulationCount(visual->blue_mask);

Bug#841951: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Anthony Towns wrote:

> Okay, that makes it a Qt/GL bug afaics then. Might be worth trying the
> attached. I get:
> 
>  $ g++ -o test test.cpp -lX11 -lGL -Wall -W
>  $ ./test
>  config 0 alphaSize 0
>  config 1 alphaSize 0
>  config 2 alphaSize 0
> ...
>  config 36 alphaSize 0
>  config 37 alphaSize 0
>  config 38 alphaSize 8
>  config 39 alphaSize 8
> 
> I'm guessing you'll get some visual==NULL!! warnings


Indeed. I get single `visual==NULL` at:


config 0 alphaSize 0
config 1 alphaSize 0
config 2 alphaSize 0
config 3 alphaSize 0
config 4 alphaSize 0
config 5 alphaSize 0
config 6 alphaSize 0
config 7 alphaSize 0
config 8 alphaSize 0
config 9 alphaSize 0
config 10 alphaSize 0
config 11 alphaSize 0
config 12 alphaSize 0
config 13 alphaSize 0
config 14 alphaSize 0
config 15 alphaSize 0
config 16 alphaSize 0
config 17 alphaSize 0
config 18 alphaSize 8
config 19 alphaSize 8
config 20 alphaSize 8
config 21 alphaSize 8
config 22 alphaSize 8
config 23 alphaSize 8
config 24 alphaSize 8
config 25 alphaSize 8
config 25 visual==NULL!!
config 26 alphaSize 8
config 27 alphaSize 8
config 28 alphaSize 8
config 29 alphaSize 8
config 30 alphaSize 8
config 31 alphaSize 8
config 32 alphaSize 8
config 33 alphaSize 8
config 34 alphaSize 8
config 35 alphaSize 8
config 36 alphaSize 0
config 37 alphaSize 0
config 38 alphaSize 8
config 39 alphaSize 8

every time I run the program.

> as well at which
> point you might be able to work out what's going on?

Well I suspect that must be the one config that bitcoin-qt is
trying to use. Should this debian bug be moved to another package?
If so, which one?

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#841951: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Anthony Towns wrote:

> Maybe
> 
>  /usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray
> 
> might reproduce the crash?

Indeed it does! Gdb backtrace follows.

Erik

> gdb --args 
> /usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray
GNU gdb (Debian 7.11.1-2) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray...(no 
debugging symbols found)...done.
(gdb) r
Starting program: 
/usr/lib/x86_64-linux-gnu/qt5/examples/widgets/desktop/systray/systray 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffec111700 (LWP 16297)]
[New Thread 0x7fffe1129700 (LWP 16298)]
[New Thread 0x7fffdbb8f700 (LWP 16299)]
[New Thread 0x7fffdb38e700 (LWP 16300)]

Thread 1 "systray" received signal SIGSEGV, Segmentation fault.
qglx_findConfig (display=display@entry=0x43fde0, screen=screen@entry=0, 
format=..., drawableBit=drawableBit@entry=1)
at glxconvenience/qglxconvenience.cpp:157
157 glxconvenience/qglxconvenience.cpp: No such file or directory.
(gdb) bt
#0  qglx_findConfig (display=display@entry=0x43fde0, screen=screen@entry=0, 
format=..., drawableBit=drawableBit@entry=1)
at glxconvenience/qglxconvenience.cpp:157
#1  0x77fec29d in qglx_findVisualInfo (display=0x43fde0, screen=0, 
format=0x6c87f8)
at glxconvenience/qglxconvenience.cpp:192
#2  0x77efb3bd in QXcbWindow::create (this=0x6c87a0) at 
qxcbwindow.cpp:416
#3  0x77ee67b1 in QXcbIntegration::createPlatformWindow 
(this=, window=0x6c6af0)
at qxcbintegration.cpp:203
#4  0x772cf2fc in QWindowPrivate::create (this=0x6c6b50, 
recursive=recursive@entry=false)
at kernel/qwindow.cpp:395
#5  0x772cf6ab in QWindow::create (this=this@entry=0x6c6af0) at 
kernel/qwindow.cpp:555
#6  0x778e84e4 in QWidgetPrivate::create_sys (this=this@entry=0x6c6840, 
window=window@entry=0, 
initializeWindow=initializeWindow@entry=true, 
destroyOldWindow=destroyOldWindow@entry=true)
at kernel/qwidget.cpp:1467
#7  0x778e7b9d in QWidget::create (this=0x6c67e0, 
window=window@entry=0, 
initializeWindow=initializeWindow@entry=true, 
destroyOldWindow=destroyOldWindow@entry=true)
at kernel/qwidget.cpp:1331
#8  0x778e7fce in QWidgetPrivate::createWinId (this=) at 
kernel/qwidget.cpp:2556
#9  0x778e8859 in QWidget::createWinId (this=this@entry=0x6c67e0) at 
kernel/qwidget.cpp:2575
#10 0x77c40f02 in QSystemTrayIconSys::addToTray (this=0x6c67e0) at 
util/qsystemtrayicon_x11.cpp:139
#11 0x77c4116c in QSystemTrayIconSys::QSystemTrayIconSys 
(this=0x6c67e0, qIn=)
at util/qsystemtrayicon_x11.cpp:131
#12 0x77c41322 in QSystemTrayIconPrivate::install_sys 
(this=this@entry=0x6c5dd0)
at util/qsystemtrayicon_x11.cpp:270
#13 0x77c22477 in QSystemTrayIcon::setVisible (this=, 
visible=)
at util/qsystemtrayicon.cpp:271
#14 0x00406660 in ?? ()
#15 0x004046e3 in ?? ()
#16 0x765ee2b1 in __libc_start_main (main=0x404680, argc=1, 
argv=0x7fffe438, init=, 
fini=, rtld_fini=, stack_end=0x7fffe428) 
at ../csu/libc-start.c:291
#17 0x00404819 in ?? ()

-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#841951: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

eateWinId (this=) at 
kernel/qwidget.cpp:2556
#9  0x76bb7859 in QWidget::createWinId (this=this@entry=0x56c23970) 
at kernel/qwidget.cpp:2575
#10 0x76f0ff02 in QSystemTrayIconSys::addToTray (this=0x56c23970) 
at util/qsystemtrayicon_x11.cpp:139
#11 0x76f1016c in QSystemTrayIconSys::QSystemTrayIconSys 
(this=0x56c23970, qIn=)
at util/qsystemtrayicon_x11.cpp:131
#12 0x76f10322 in QSystemTrayIconPrivate::install_sys 
(this=this@entry=0x56a8aed0)
at util/qsystemtrayicon_x11.cpp:270
#13 0x76ef1477 in QSystemTrayIcon::setVisible (this=, 
visible=)
at util/qsystemtrayicon.cpp:271
#14 0x555d7090 in ?? ()
#15 0x555c311a in ?? ()
#16 0x761e4729 in QObject::event (this=this@entry=0x7fffe010, 
e=e@entry=0x7fffc85f6c80)
at kernel/qobject.cpp:1256
#17 0x761bc8dc in QCoreApplication::event 
(this=this@entry=0x7fffe010, e=e@entry=0x7fffc85f6c80)
at kernel/qcoreapplication.cpp:1785
#18 0x765909a4 in QGuiApplication::event 
(this=this@entry=0x7fffe010, e=e@entry=0x7fffc85f6c80)
at kernel/qguiapplication.cpp:1626
#19 0x76b8154f in QApplication::event (this=0x7fffe010, 
e=0x7fffc85f6c80) at kernel/qapplication.cpp:2075
#20 0x76b7dbec in QApplicationPrivate::notify_helper (this=, receiver=0x7fffe010, 
e=0x7fffc85f6c80) at kernel/qapplication.cpp:3804
#21 0x76b8308f in QApplication::notify (this=0x7fffe010, 
receiver=0x7fffe010, e=0x7fffc85f6c80)
at kernel/qapplication.cpp:3561
#22 0x761b6450 in QCoreApplication::notifyInternal2 
(receiver=0x7fffe010, event=event@entry=0x7fffc85f6c80)
at kernel/qcoreapplication.cpp:1015
#23 0x761b83cc in QCoreApplication::sendEvent (event=0x7fffc85f6c80, 
receiver=)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:225
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
event_type=event_type@entry=0, 
data=0x56143020) at kernel/qcoreapplication.cpp:1650
#25 0x761b in QCoreApplication::sendPostedEvents 
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at kernel/qcoreapplication.cpp:1508
#26 0x7620c0f3 in postEventSourceDispatch (s=0x5616fa70) at 
kernel/qeventdispatcher_glib.cpp:270
#27 0x729857d7 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x72985a40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x72985aec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7620c4ff in QEventDispatcherGlib::processEvents 
(this=0x5616f8c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:417
#31 0x761b419a in QEventLoop::exec (this=this@entry=0x7fffdcb0, 
flags=..., flags@entry=...)
at kernel/qeventloop.cpp:204
#32 0x761bc99c in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:1285
#33 0x555b98a7 in ?? ()
---Type  to continue, or q  to quit---
#34 0x7376b2b1 in __libc_start_main (main=0x555b8b50, argc=2, 
argv=0x7fffe488, init=, 
    fini=, rtld_fini=, stack_end=0x7fffe478) 
at ../csu/libc-start.c:291
#35 0x555c1fda in ?? ()
(gdb) q



-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#712228: Hardening flag -pie breaks compilation with GHC

[Erik de Castro Lopo]

Package: ghc
Version: 7.10.3-10
Followup-For: Bug #712228

Dear Maintainer,

I've been using 7.10.3-10 for a couple of weeks now and it was fine,
but today after an upgrade this problem came back.

Its seems that "gcc (Debian 6.2.0-9) 6.2.0 20161019" break everything
again.

> mkdir /tmp/test ; cd /tmp/test
> cabal sandbox init
> cabal install clock
Resolving dependencies...
Notice: installing into a sandbox located at /tmp/test/.cabal-sandbox
Configuring clock-0.7.2...
Building clock-0.7.2...
Failed to install clock-0.7.2
Build log ( /tmp/test/.cabal-sandbox/logs/clock-0.7.2.log ):
cabal: Entering directory '/tmp/cabal-tmp-28442/clock-0.7.2'
Configuring clock-0.7.2...
Building clock-0.7.2...
Preprocessing library clock-0.7.2...
/usr/bin/ld: dist/dist-sandbox-e0f3b3c1/build/System/Clock_hsc_make.o: 
relocation R_X86_64_32 against `.rodata' can not be used when making a shared 
object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
linking dist/dist-sandbox-e0f3b3c1/build/System/Clock_hsc_make.o failed (exit 
code 1)
command was: /usr/bin/gcc 
dist/dist-sandbox-e0f3b3c1/build/System/Clock_hsc_make.o 
dist/dist-sandbox-e0f3b3c1/build/System/Clock_hsc_utils.o -o 
dist/dist-sandbox-e0f3b3c1/build/System/Clock_hsc_make -fno-PIE 
-fno-stack-protector -L/usr/lib/ghc/base_HQfYBxpPvuw8OunzQu6JGM 
-Wl,-R,/usr/lib/ghc/base_HQfYBxpPvuw8OunzQu6JGM 
-L/usr/lib/ghc/integ_2aU3IZNMF9a7mQ0OzsZ0dS 
-Wl,-R,/usr/lib/ghc/integ_2aU3IZNMF9a7mQ0OzsZ0dS -lgmp 
-L/usr/lib/ghc/ghcpr_8TmvWUcS1U1IKHT0levwg3 
-Wl,-R,/usr/lib/ghc/ghcpr_8TmvWUcS1U1IKHT0levwg3 -L/usr/lib/ghc/rts 
-Wl,-R,/usr/lib/ghc/rts -lm -lrt -ldl -lffi
cabal: Leaving directory '/tmp/cabal-tmp-28442/clock-0.7.2'
cabal: Error: some packages failed to install:
clock-0.7.2 failed during the building phase. The exception was:
ExitFailure 1

On another machine I have "gcc (Debian 6.2.0-6) 6.2.0 20161010" and 
ghc-7.10.3-10
works fine there.

I suspect the problem is this:

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

Erik

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, armhf, i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ghc depends on:
ii  dpkg 1.18.10
ii  gcc  4:6.1.1-1
ii  libbsd-dev   0.8.3-1
ii  libc62.24-5
ii  libc6-dev2.24-5
ii  libffi-dev   3.2.1-6
ii  libffi6  3.2.1-6
ii  libgmp-dev   2:6.1.1+dfsg-1
ii  libgmp10 2:6.1.1+dfsg-1
ii  libncurses5-dev  6.0+20160917-1
ii  libtinfo56.0+20160917-1

ghc recommends no packages.

Versions of packages ghc suggests:
pn  ghc-doc  
pn  ghc-prof 
pn  haskell-doc  
ii  llvm-3.5 1:3.5.2-5
ii  perl 5.24.1~rc3-3

-- no debconf information

Bug#841951: bitcoin-qt segfaults on startup

[Erik de Castro Lopo]

Package: bitcoin-qt
Version: 0.13.0-0.1
Severity: important

Dear Maintainer,

Just got a new machine, installed bitcoin-qt, ran it and got an immediate
segfault. Re-running get the same result.

Backtrace from GDB:

(gdb) r
Starting program: /home/erikd/Local/bin/bitcoin-qt 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe9967700 (LWP 21490)]
[New Thread 0x7fffdcfa1700 (LWP 21491)]
[New Thread 0x7fffd7fff700 (LWP 21492)]

Thread 1 "bitcoin-qt" received signal SIGSEGV, Segmentation fault.
0x77fe50e2 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
(gdb) bt
#0  0x77fe50e2 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#1  0x77fe529d in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
#2  0x7fffeb8bb3bd in QXcbWindow::create() () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#3  0x7fffeb8a67b1 in QXcbIntegration::createPlatformWindow(QWindow*) const 
()
   from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x768042fc in QWindowPrivate::create(bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#5  0x76e1d4e4 in QWidgetPrivate::create_sys(unsigned long long, bool, 
bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x76e1cb9d in QWidget::create(unsigned long long, bool, bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x77175f02 in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x7717616c in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x77176322 in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x77157477 in QSystemTrayIcon::setVisible(bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x555d62d4 in QSystemTrayIcon::show (this=)
at /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qsystemtrayicon.h:95
#12 BitcoinGUI::createTrayIcon (this=this@entry=0x56454510, 
networkStyle=networkStyle@entry=0x56310c90)
at qt/bitcoingui.cpp:534
#13 0x555d844a in BitcoinGUI::BitcoinGUI (this=0x56454510, 
platformStyle=0x562f1180, 
networkStyle=0x56310c90, parent=) at 
qt/bitcoingui.cpp:177
#14 0x555c50de in BitcoinApplication::createWindow 
(this=0x7fffe020, networkStyle=0x56310c90)
at qt/bitcoin.cpp:358
#15 0x555baafa in main (argc=, argv=0x7fffe498) at 
qt/bitcoin.cpp:662


There doesn't seem to be any debug symbols available for libqt5gui5 so
I was not able to debug this futher.

Cheers,
Erik

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, armhf, i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bitcoin-qt depends on:
ii  libboost-chrono1.61.0   1.61.0+dfsg-3
ii  libboost-filesystem1.61.0   1.61.0+dfsg-3
ii  libboost-program-options1.61.0  1.61.0+dfsg-3
ii  libboost-system1.61.0   1.61.0+dfsg-3
ii  libboost-thread1.61.0   1.61.0+dfsg-3
ii  libc6   2.24-3
ii  libdb5.3++  5.3.28-12
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libevent-pthreads-2.0-5 2.0.21-stable-2+b1
ii  libgcc1 1:6.2.0-6
ii  libminiupnpc10  1.9.20140610-2.1
ii  libprotobuf10   3.0.0-7
ii  libqrencode33.4.4-1+b1
ii  libqt5core5a5.6.1+dfsg-3+b1
ii  libqt5dbus5 5.6.1+dfsg-3+b1
ii  libqt5gui5  5.6.1+dfsg-3+b1
ii  libqt5network5  5.6.1+dfsg-3+b1
ii  libqt5widgets5  5.6.1+dfsg-3+b1
ii  libssl1.0.2 1.0.2j-1
ii  libstdc++6  6.2.0-6
ii  libzmq5 4.1.5-2

bitcoin-qt recommends no packages.

bitcoin-qt suggests no packages.

-- no debconf information

Bug#836566: Unhandled exception in previously working program

[Erik de Castro Lopo]

Jens Reyer wrote:

> Hmm, probably that points to the same issue as in
> https://bugs.debian.org/836911.
> 
> I assume that Wine forks permanently if another wineserver is already
> running. So does this happen for you, if previously no wineserver was
> running, e.g.:
> 
> $ wineserver -k
> $ wine YOURPROGRAM

Unfortunately that does not fix it.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#836566: Unhandled exception in previously working program

[Erik de Castro Lopo]

Package: wine64
Version: 1.8.4-1
Severity: normal

My main usage of Wine is for running the test suite for software when
I cross compile from Linux to Windows. I've been doing this successfully
for many years which the occassional problem like the one today.

I recently upgraded to wine64 1.8.3 (and then later to 1.8.4) and found
that these two releases cause an Unhandled exception in one of the 
testsuite programs that was working before then. The exception is as
follows.

Unhandled exception: page fault on write access to 0x0050 in 64-bit code 
(0x70473f90).
Register dump:
 rip:70473f90 rsp:0033d820 rbp: eflags:00010202 
(  R- --  I   - - - )
 rax:0050 rbx:7049d849 rcx:005c00730fb0 
rdx:005c0073004fbaf4
 rsi: rdi:0001  r8:0040  
r9:0fb0 r10:0008
 r11:7fb3110c5aa0 r12:004fab04 r13:004f7db0 
r14:704a3574 r15:0fbc
Stack dump:
0x0033d820:   
0x0033d830:   
0x0033d840:   0033d8c8
0x0033d850:  7044c146 004f7db0
0x0033d860:   0001
0x0033d870:  1000 7049d840
0x0033d880:  00180001 0021
0x0033d890:  0041f860 7044d93b
0x0033d8a0:  8088e540 
0x0033d8b0:  65657266 0fb0
0x0033d8c0:  005c00730fb0 0001
0x0033d8d0:  00ff0001 0008
Backtrace:
=>0 0x70473f90 in libsndfile-1 (+0x33f90) (0x)
  1 0x7044d93b in libsndfile-1 (+0xd93a) (0x1000)
  2 0x7044554c in libsndfile-1 (+0x554b) (0x004a1b80)
  3 0x00403873 in write_read_test (+0x3872) (0x00180001)
  4 0x00403d38 in write_read_test (+0x3d37) (0x00180001)
  5 0x00403f7d in write_read_test (+0x3f7c) (0x2000)
  6 0x00407a1b in write_read_test (+0x7a1a) (0x2000)
  7 0x00413aa1 in write_read_test (+0x13aa0) (0x)
  8 0x004013ed in write_read_test (+0x13ec) (0x004a19c0)
  9 0x0040152b in write_read_test (+0x152a) (0x0033fe60)
  10 0x7b878737 in kernel32 (+0x58736) (0x0033fe60)
  11 0x7fb310ad8511 call_thread_func+0xb0() in ntdll (0x7ffc0cd49870)
  12 0x7fb310ad14f2 RtlRaiseException+0x7d() in ntdll (0x7ffc0cd49870)
  13 0x7fb310a9e696 in ntdll (+0x3e695) (0x7ffc0cd49870)
  14 0x7fb311521633 wine_call_on_stack+0x12() in libwine.so.1 
(0x7ffc0cd49870)
  15 0x7fb311521799 wine_switch_to_stack+0x8() in libwine.so.1 
(0x7ffc0cd499a0)
  16 0x7fb310aa4d94 LdrInitializeThunk+0x2a3() in ntdll (0x7ffc0cd499a0)
  17 0x7b87f943 __wine_kernel_init+0x952() in kernel32 
(0x7ffc0cd4ac10)
  18 0x7fb310aa5eb8 __wine_process_init+0x177() in ntdll 
(0x7ffc0cd4ac50)
  19 0x7fb31151f7fa wine_init+0x2b9() in libwine.so.1 (0x7ffc0cd4ad50)
  20 0x7bf00ca2 main+0x81() in  (0x7ffc0cd4b258)
  21 0x7fb310f79700 __libc_start_main+0xef() in libc.so.6 
(0x7bf00e70)
  22 0x7bf00d99 _start+0x28() in  (0x)
  23 0x7bf00d99 _start+0x28() in  (0x)
  24 0x7bf00d99 _start+0x28() in  (0x)
  25 0x7bf00d99 _start+0x28() in  (0x)
  26 0x7bf00d99 _start+0x28() in  (0x)
  27 0x7bf00d99 _start+0x28() in  (0x)
  28 0x7bf00d99 _start+0x28() in  (0x)
  29 0x7bf00d99 _start+0x28() in  (0x)
  30 0x7bf00d99 _start+0x28() in  (0x)
  31 0x7bf00d99 _start+0x28() in  (0x)
  32 0x7bf00d99 _start+0x28() in  (0x)
  33 0x7bf00d99 _start+0x28() in  (0x)
  34 0x7bf00d99 _start+0x28() in  (0x)
  35 0x7bf00d99 _start+0x28() in  (0x)
  36 0x7bf00d99 _start+0x28() in  (0x)
  37 0x7bf00d99 _start+0x28() in  (0x)
  38 0x7bf00d99 _start+0x28() in  (0x)
  39 0x7bf00d99 _start+0x28() in  (0x)
  40 0x7bf00d99 _start+0x28() in  (0x)
  41 0x7bf00d99 _start+0x28() in  (0x)
  42 0x7bf00d99 _start+0x28() in  (0x)
  43 0x7bf00d99 _start+0x28() in  (0x)
  44 0x7bf00d99 _start+0x28() in  (0x)
  45 0x7bf00d99 _start+0x28() in  (0x)
  46 0x7bf00d99 _start+0x28() in  (0x)
  47 0x7bf00d99 _start+0x28() in  (0x)
  48 

Bug#836280: brcmfmac: brcmfmac fails to load firmware

[Erik de Castro Lopo]

Package: src:linux
Version: 4.7.2-1
Severity: normal
File: brcmfmac

Dear Maintainer,

Had this machine for about 3 months and wifi has been working correctly until 
yesterday
when I installed the 4.7.0 kernel. For some reason the bcrm firmware fails to 
load:

$ dmesg | grep brcm
[   27.269495] usbcore: registered new interface driver brcmfmac
[   27.398657] brcmfmac :03:00.0: firmware: direct-loading firmware 
brcm/brcmfmac43602-pcie.bin
[   27.398725] brcmfmac :03:00.0: firmware: failed to load 
brcm/brcmfmac43602-pcie.txt (-2)
[   27.398732] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
[   27.885750] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 
2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[   27.923082] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
[   27.927522] brcmfmac :03:00.0 wlp3s0: renamed from wlan0
[   30.770142] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error
[   51.050385] brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, 
bsscfgidx=0
[   51.050389] brcmfmac: brcmf_fweh_event_worker: event handler failed (69)
[   52.614267] brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, 
bsscfgidx=0
[   52.614270] brcmfmac: brcmf_fweh_event_worker: event handler failed (69)
[  356.473390] brcmfmac: brcmf_cfg80211_escan_handler: scan not ready, 
bsscfgidx=0
[  356.473396] brcmfmac: brcmf_fweh_event_worker: event handler failed (69)
[  733.470499] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error

The file /lib/firmware/brcm/brcmfmac43602-pcie.bin exists and debsums seems to 
think its
ok:

> debsums firmware-brcm80211 | grep brcmfmac43602-pcie.bin
/lib/firmware/brcm/brcmfmac43602-pcie.bin   
  OK

Funny thing is I get this same problem with the 4.5.0 kernel which was working 
up until
I installed 4.7.0.

Erik

-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
\vmlinuz-4.7.0-1-amd64 initrd=\initrd.img-4.7.0-1-amd64

** Not tainted

** Kernel log:
[  892.391915] thunderbolt :07:00.0: activating path from 1:2 to 0:6
[  892.392014] thunderbolt :07:00.0: 0:1: Writing hop 1, index 8
[  892.392015] thunderbolt :07:00.0: 0:1:  Hop through port 6 to hop 8 
(enabled)
[  892.392016] thunderbolt :07:00.0: 0:1:   Weight: 1 Priority: 3 Credits: 
16 Drop: 0
[  892.392017] thunderbolt :07:00.0: 0:1:Counter enabled: 0 Counter 
index: 2047
[  892.392018] thunderbolt :07:00.0: 0:1:   Flow Control (In/Eg): 1/0 
Shared Buffer (In/Eg): 0/0
[  892.392019] thunderbolt :07:00.0: 0:1:   Unknown1: 0x0 Unknown2: 0x0 
Unknown3: 0x0
[  892.392214] thunderbolt :07:00.0: 1:2: Writing hop 0, index 8
[  892.392215] thunderbolt :07:00.0: 1:2:  Hop through port 1 to hop 8 
(enabled)
[  892.392216] thunderbolt :07:00.0: 1:2:   Weight: 1 Priority: 3 Credits: 
7 Drop: 0
[  892.392217] thunderbolt :07:00.0: 1:2:Counter enabled: 0 Counter 
index: 2047
[  892.392218] thunderbolt :07:00.0: 1:2:   Flow Control (In/Eg): 1/1 
Shared Buffer (In/Eg): 0/0
[  892.392219] thunderbolt :07:00.0: 1:2:   Unknown1: 0x0 Unknown2: 0x0 
Unknown3: 0x0
[  892.392313] thunderbolt :07:00.0: path activation complete
[  892.392527] pciehp :06:03.0:pcie204: Card present on Slot(3-2)
[  892.395280] pciehp :06:03.0:pcie204: slot(3-2): Link Up event
[  892.395287] pciehp :06:03.0:pcie204: Link Up event ignored on slot(3-2): 
already powering on
[  892.509765] pci :08:00.0: [8086:1549] type 01 class 0x060400
[  892.509977] pci :08:00.0: supports D1 D2
[  892.509979] pci :08:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  892.517786] pci :08:00.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[  892.517967] acpiphp: Slot [1] registered
[  892.518001] acpiphp: Slot [2-1] registered
[  892.518031] acpiphp: Slot [3-1] registered
[  892.518060] acpiphp: Slot [4-1] registered
[  892.518088] acpiphp: Slot [5-1] registered
[  892.518095] pci_bus :09: busn_res: can not insert [bus 09-ff] under [bus 
08-38] (conflicts with (null) [bus 08-38])
[  892.518125] pci :09:00.0: [8086:1549] type 01 class 0x060400
[  892.518318] pci :09:00.0: supports D1 D2
[  892.518320] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[  892.518539] pci :08:00.0: PCI bridge to [bus 09-ff]
[  892.518552] pci :08:00.0:   bridge window [io  0x-0x0fff]
[  892.518559] pci :08:00.0:   bridge window [mem 0x-0x000f]
[  892.518570] pci :08:00.0:   bridge window [mem 0x-0x000f 
64bit pref]
[  892.518575] pci :09:00.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[  892.518738] pci :0a:00.0: [14e4:1682] type 00 class 0x02
[  892.518792] pci :0a:00.0: reg 0x10: [mem 

Bug#836279: linux-image-4.7.0-1-amd64: Intermittent hang on mackbook pro

[Erik de Castro Lopo]

Package: src:linux
Version: 4.7.2-1
Severity: important

Dear Maintainer,

Getting very similar hangs to the ones I reported in #834011, but this time I'm 
using the standard in tree
hid_apple driver that shipped with the kernel.

The probelm is that the machine just completely hangs up every now and then. 
When it hangs, the the mouse
and keyboard are unresponsive and the machine does not even respond to pings on 
the network.

If I boot to the 4.5.0 kernel everything is fine.s

Cheers,
Erik


-- Package-specific info:
** Version:
Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28)

** Command line:
\vmlinuz-4.7.0-1-amd64 initrd=\initrd.img-4.7.0-1-amd64

** Not tainted

** Kernel log:
[   27.514564] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.514567] thunderbolt :07:00.0:   Max counters: 2
[   27.514570] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.514662] thunderbolt :07:00.0:  Port 11: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0101))
[   27.514669] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.514673] thunderbolt :07:00.0:   Max counters: 2
[   27.514677] thunderbolt :07:00.0:   NFC Credits: 0xf0
[   27.515538] thunderbolt :07:00.0:  Port 12: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0101))
[   27.515546] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[   27.515550] thunderbolt :07:00.0:   Max counters: 2
[   27.515554] thunderbolt :07:00.0:   NFC Credits: 0xf0
[   27.515910] thunderbolt :07:00.0: 0:1: is connected, link is up (state: 
2)
[   27.516078] thunderbolt :07:00.0: initializing Switch at 0x1 (depth: 1, 
up port: 1)
[   27.516081] thunderbolt :07:00.0: old switch config:
[   27.516084] thunderbolt :07:00.0:  Switch: 8086:1549 (Revision: 0, TB 
Version: 1)
[   27.516087] thunderbolt :07:00.0:   Max Port Number: 2
[   27.516089] thunderbolt :07:00.0:   Config:
[   27.516091] thunderbolt :07:00.0:Upstream Port Number: 1 Depth: 1 
Route String: 0x1 Enabled: 1, PlugEventsDelay: 255ms
[   27.516094] thunderbolt :07:00.0:unknown1: 0x0 unknown4: 0x0
[   27.532046] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   27.532091] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by 
hardware/BIOS
[   27.535072] Adding 974844k swap on /dev/mapper/vg-swap.  Priority:-1 
extents:1 across:974844k SSFS
[   27.536541] thunderbolt :07:00.0: 1: reading drom (length: 0x7b)
[   27.547838] pstore: Registered efi as persistent store backend
[   27.606644] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: 
(null)
[   27.662711] fbcon: inteldrmfb (fb0) is primary device
[   27.663481] ACPI: Video Device [IGPU] (multi-head: yes  rom: no  post: no)
[   27.663694] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[   27.864313] thunderbolt :07:00.0: 1: uid: 0x10002049dc190
[   27.864412] thunderbolt :07:00.0:  Port 0: 8086:1549 (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   27.864412] thunderbolt :07:00.0:   Max hop id (in/out): 7/7
[   27.864413] thunderbolt :07:00.0:   Max counters: 8
[   27.864413] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.864910] thunderbolt :07:00.0:  Port 1: 8086:1549 (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[   27.864910] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[   27.864911] thunderbolt :07:00.0:   Max counters: 4
[   27.864911] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[   27.865010] thunderbolt :07:00.0:  Port 2: 8086:1549 (Revision: 0, TB 
Version: 1, Type: PCIe (0x100102))
[   27.865010] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[   27.865011] thunderbolt :07:00.0:   Max counters: 2
[   27.865011] thunderbolt :07:00.0:   NFC Credits: 0x70
[   27.865409] thunderbolt :07:00.0: 0:3: is unplugged (state: 7)
[   27.865708] thunderbolt :07:00.0: 1:2: PCIe port already activated, 
aborting
[   27.885750] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 
2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[   27.923082] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
[   27.927522] brcmfmac :03:00.0 wlp3s0: renamed from wlan0
[   28.967075] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   28.967085] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0
[   28.967189] Console: switching to colour frame buffer device 320x100
[   29.490790] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   29.519290] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card0/input13
[   29.519475] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card0/input14
[   29.519570] input: HDA Intel HDMI HDMI/DP,pcm=8 as 

Bug#834011: Same problem with linux-image-4.7.0-1-amd64

[Erik de Castro Lopo]

Hi,

I'm now getting exactly the same problem with this new kernel version
(linux-image-4.7.0-1-amd64) and this time I *know* I do not have any
tainted kernel modules.

Should I raise a new bug or post the new info here?

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#834011: linux-image-4.6.0-1-amd64: Intermittent hang on macboook pro

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

I didn't notice this before:

> ** Tainted: OE (12288)
>  * Out-of-tree module has been loaded.
>  * Unsigned module has been loaded (currently expected).

How can I find out which module that is?

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#834011: linux-image-4.6.0-1-amd64: Intermittent hang on macboook pro

[Erik de Castro Lopo]

Package: src:linux
Version: 4.6.4-1
Severity: normal

Dear Maintainer,

With this kernel version on this machine I get intermittent machine hangs.
The keyboard and mouse are unresponsive and the machine doesn't respond to
pings on the network (it normally does). The first thing I notice is that
the keyboard and/or mouse stop responding. If I am currently playing music
on youtube or something i get aa short (maybe as much as a second) looping
stutter of audio. The lockup has also happened when I'm not playing music.
It happened about 20 or so times, sometimes as much as 3 times a day.

If I boot to the linux-image-4.5.0-s-amd64 kernel it runs for days without
a single hang. Switching back to 4.6.4-1 and the hangs return.


-- Package-specific info:
** Version:
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

** Command line:
\vmlinuz-4.6.0-1-amd64 initrd=\initrd.img-4.6.0-1-amd64

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[9.169316] intel_rapl: Found RAPL domain package
[9.169323] intel_rapl: Found RAPL domain core
[9.169327] intel_rapl: Found RAPL domain uncore
[9.169331] intel_rapl: Found RAPL domain dram
[9.191709] thunderbolt :07:00.0: 0: uid: 0x1001305f89270
[9.191806] thunderbolt :07:00.0:  Port 0: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.191814] thunderbolt :07:00.0:   Max hop id (in/out): 7/7
[9.191818] thunderbolt :07:00.0:   Max counters: 8
[9.191822] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.192487] thunderbolt :07:00.0:  Port 1: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.192495] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.192499] thunderbolt :07:00.0:   Max counters: 16
[9.192502] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.192978] thunderbolt :07:00.0:  Port 2: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.192986] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.192990] thunderbolt :07:00.0:   Max counters: 16
[9.192993] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.193483] thunderbolt :07:00.0:  Port 3: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.193491] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.193495] thunderbolt :07:00.0:   Max counters: 16
[9.193499] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.194262] thunderbolt :07:00.0:  Port 4: 8086:156d (Revision: 0, TB 
Version: 1, Type: Port (0x1))
[9.194269] thunderbolt :07:00.0:   Max hop id (in/out): 15/15
[9.194273] thunderbolt :07:00.0:   Max counters: 16
[9.194278] thunderbolt :07:00.0:   NFC Credits: 0x3c0
[9.194577] thunderbolt :07:00.0:  Port 5: 8086:156d (Revision: 0, TB 
Version: 1, Type: NHI (0x2))
[9.194584] thunderbolt :07:00.0:   Max hop id (in/out): 11/11
[9.194587] thunderbolt :07:00.0:   Max counters: 16
[9.194591] thunderbolt :07:00.0:   NFC Credits: 0xf0
[9.194710] thunderbolt :07:00.0:  Port 6: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194717] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194721] thunderbolt :07:00.0:   Max counters: 2
[9.194724] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.194810] thunderbolt :07:00.0:  Port 7: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194816] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194821] thunderbolt :07:00.0:   Max counters: 2
[9.194825] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.194909] thunderbolt :07:00.0:  Port 8: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.194916] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.194920] thunderbolt :07:00.0:   Max counters: 2
[9.194924] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.195008] thunderbolt :07:00.0:  Port 9: 8086:156d (Revision: 0, TB 
Version: 1, Type: PCIe (0x100101))
[9.195015] thunderbolt :07:00.0:   Max hop id (in/out): 8/8
[9.195019] thunderbolt :07:00.0:   Max counters: 2
[9.195023] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.195108] thunderbolt :07:00.0:  Port 10: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0102))
[9.195115] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[9.195119] thunderbolt :07:00.0:   Max counters: 2
[9.195124] thunderbolt :07:00.0:   NFC Credits: 0x70
[9.195208] thunderbolt :07:00.0:  Port 11: 8086:156d (Revision: 0, TB 
Version: 1, Type: DP/HDMI (0xe0101))
[9.195214] thunderbolt :07:00.0:   Max hop id (in/out): 9/9
[9.195218] thunderbolt :07:00.0:   Max counters: 2
[9.195221] 

Bug#826106: Please close

[Erik de Castro Lopo]

It seems jeknins is no longer packaged by Debian which makes this
bug invalid.

Thanks,
Erik

-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#826106: jenkins: Crashes in two separate places

[Erik de Castro Lopo]

Package: jenkins
Version: 1.565.3-6
Severity: normal

Dear Maintainer,

At http://127.0.0.1:8080/jenkins/job/x/205/ :

  javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
jar:file:/run/jenkins/war/WEB-INF/lib/jenkins-core-1.565.3.jar!/hudson/model/AbstractBuild/index.jelly:67:61:
  No page found 'digest.jelly' for class hudson.model.FreeStyleBuild
at 
org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
at 
org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:734)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
at org.kohsuke.stapler.Stapler.service(Stapler.java:237)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)

At http://127.0.0.1:8080/jenkins/job/xx/205/console, the actual console
output of build 205 for the same project as above:

  java.lang.ArrayIndexOutOfBoundsException: 1
at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:104)
at hudson.plugins.git.GitChangeSet.(GitChangeSet.java:89)
at 
hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:77)
at 
hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:61)
at 
hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:48)
at 
hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:29)
at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:874)
at hudson.model.AbstractBuild.access$600(AbstractBuild.java:102)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:620)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524)
at hudson.model.Run.execute(Run.java:1706)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)

Re-running the the build for project xx results on the exception in the
console output.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to POSIX)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jenkins depends on:
ii  adduser  3.114
ii  daemon   0.6.4-1
ii  default-jre-headless [java6-runtime-headless]2:1.8-57
ii  jenkins-common   1.565.3-6
ii  net-tools1.60+git20150829.73cef8a-2
ii  openjdk-7-jre-headless [java6-runtime-headless]  7u101-2.6.6-2
ii  openjdk-8-jre-headless [java6-runtime-headless]  8u91-b14-2
ii  procps   2:3.3.11-3
ii  psmisc   22.21-2.1+b1

jenkins recommends no packages.

jenkins suggests no packages.

-- Configuration Files:
/etc/default/jenkins changed [not included]



-- debconf-show failed

Bug#825078: Audio over HDMI not working

[Erik de Castro Lopo]

Bálint Réczey wrote:

> Would you like to share some info about the HW?

Its just a standard Intel NUC with a Core i5 CPU and 16Gig RAM.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#825078: Audio over HDMI not working

[Erik de Castro Lopo]

Bálint Réczey wrote:

> Have you checked the suggestions listed here?:
> http://kodi.wiki/view/PulseAudio

Yes, I did. The problem was not at the PusleAudio level, because ALSA
did not find the HDMI audio device either.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#825078: Audio over HDMI not working

[Erik de Castro Lopo]

Source: kodi
Version: 16.1+dfsg1-1
Severity: normal

After upgrading from kodi-15 to kodi-16, audio over HDMI stopped working
on my dedicated kodi box.

I spent a *lot* of time debugging this and in the end installed a kodi
specific linux distro (http://wiki.libreelec.tv/) and everything works.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#814763: [Pkg-alsa-devel] Bug#814763: HDMI sound not working

[Erik de Castro Lopo]

Elimar Riesebieter wrote:

> > That part was fine, but ...
> > 
> > > As root:
> > > 
> > > # service alsa-utils restart
> > 
> > $ sudo service alsa-utils restart
> > Failed to start alsa-utils.service: Unit alsa-utils.service is masked.
> 
> On systemd that's not possible.
> 
> Anyway, what tells
> 
>   $ aplay -l

Same as before. It only lists the Intel HDA audio device. There is no
sign of any HDMI related audio device.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#814763: HDMI sound not working

[Erik de Castro Lopo]

Elimar Riesebieter wrote:

> Please try the following:
> 
> $ mv $HOME/.asoundrc $HOME/.asoundrc.save
> $ cat < $HOME/.asoundrc
> defaults.pcm.!device 3
> defaults.ctl.!device 3
> EOF

That part was fine, but ...

> As root:
> 
> # service alsa-utils restart

$ sudo service alsa-utils restart
Failed to start alsa-utils.service: Unit alsa-utils.service is masked.

I bit of googling suggests that a service can be unmasked using:

$ sudo systemctl unmask alsa-utils.service

but that has no effect on my machine:

$ sudo service alsa-utils start
Failed to start alsa-utils.service: Unit alsa-utils.service is masked.

I also tried force re-installing alsa-utils which didn't help either.

Erik
-- 
----------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#814763: [Pkg-alsa-devel] Bug#814763: HDMI sound not working

[Erik de Castro Lopo]

Elimar Riesebieter wrote:

> Thats ok.
> 
> What tells:
> 
> # aplay -l

With the laptop displaying video over HDMI:

$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3260 Analog [ALC3260 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Erik
-- 
------
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#814763: HDMI sound not working

[Erik de Castro Lopo]

Package: alsa-base
Version: 1.0.27+1
Severity: important

I have two machines; an Intel NUC i5 and a Dell laptop. Both have
Intel i915 based graphics cards. Both run Debian Testing.

At various times in the past I have used both these machines to
display videos on my TV using HDMI. In both cases, audio that goes
to the TV was transferred over the HDMI cable.

Unfortunately some time in the last 2 months this broke. Both machines
now quite happily display video over HDMI but the audio is missing.
Part of the problem is that I can't remember the details of when it
last worked.

Here's what I know (on my laptop plugged into the TV):

$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)

$ lsmod | grep snd
snd_hda_codec_hdmi 49152  1
snd_hda_codec_realtek81920  1
snd_hda_codec_generic73728  1 snd_hda_codec_realtek
snd_hda_intel36864  3
snd_hda_codec   135168  4  snd_hda_codec_realtek,snd_hda_codec_hdmi,
   snd_hda_codec_generic,snd_hda_intel
snd_hda_core 65536  5  snd_hda_codec_realtek,snd_hda_codec_hdmi,
   
snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep16384  1  snd_hda_codec
snd_pcm 102400  4  snd_hda_codec_hdmi,snd_hda_codec,
   snd_hda_intel,snd_hda_core
snd_timer32768  1  snd_pcm
snd  81920  14 
snd_hda_codec_realtek,snd_hwdep,snd_timer,
   
snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,
   snd_hda_codec,snd_hda_intel
soundcore   16384  1 s

Interesting to note that the snd_hda_codec_hdmi driver gets loaded, but it
looks like ALSA doesn't know about it:

$ cat /proc/asound/cards
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xd171 irq 32

To me this looks like a problem with ALSA, rather than higher up like
pulseaudio. I have also tried downreving the kernel to 
linux-image-3.16.0-4-amd64
and linux-image-4.2.0-1-amd64 but that does help either, which again
points the finger at ALSA.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages alsa-base depends on:
ii  dpkg  1.18.4
ii  kmod  22-1

alsa-base recommends no packages.

alsa-base suggests no packages.

-- no debconf information

Bug#814572: Please print information output to stderr

[Erik de Castro Lopo]

Package: wine
Version: 1.8.1-1
Severity: normal

Wrapper scripts like /usr/bin/wineserver print informational
info to stdout instead of stderr.

My main usecase for Wine is to run program test suites when I
cross compile from Linux to Windows. Having these informational
messages on stdout and then having to remove them in my test
suite is inconvienient. If instead these messages were on stderr
I could just pipe stderr to /dev/null. In addition, I would be 
able to do it once in the test wrapper script instead of having
to deal with each program output separately.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wine depends on:
ii  wine32  1.8.1-1
ii  wine64  1.8.1-1

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox   
pn  wine-binfmt  

Versions of packages wine is related to:
ii  fonts-wine1.8.1-1
ii  libwine   1.8.1-1
pn  libwine-dbg   
pn  libwine-dev   
ii  wine  1.8.1-1
ii  wine321.8.1-1
pn  wine32-preloader  
pn  wine32-tools  
ii  wine641.8.1-1
pn  wine64-preloader  
pn  wine64-tools  

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/wine (from wine package)

Bug#814420: clang-tidy-3.8 missing JSON database

[Erik de Castro Lopo]

Package: clang-tidy-3.8
Version: 1:3.8~+rc2-1~exp1
Severity: important

According to the upstream documentation at:

http://clang.llvm.org/extra/clang-tidy/

the command:

> clang-tidy-3.8 bool_switch.cc -checks=-*,clang-analyzer-*

should work. Instead I get:

Error while trying to load a compilation database:
Could not auto-detect compilation database for file "bool_switch.cc"
No compilation database found in /home/erikd or any parent directory
json-compilation-database: Error while opening JSON database: No such file 
or directory
Running without flags.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clang-tidy-3.8 depends on:
ii  libc6   2.21-7
ii  libgcc1 1:5.3.1-7
ii  libllvm3.8  1:3.8~svn254193-1
ii  libstdc++6  5.3.1-7
ii  libtinfo5   6.0+20151024-2
ii  python  2.7.11-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

clang-tidy-3.8 recommends no packages.

clang-tidy-3.8 suggests no packages.

-- no debconf information

Bug#809481: linux-image-4.3.0-1-amd64: Oops on boot in nouveau

[Erik de Castro Lopo]

Package: src:linux
Version: 4.3.3-2
Severity: important

Oops on every boot with this kernel on this machine.


Dec 31 14:50:06 rollins kernel: [4.269801] IPv6: ADDRCONF(NETDEV_UP): 
wlan0: link is not ready
Dec 31 14:50:06 rollins kernel: [4.287153] PGD 0 
Dec 31 14:50:06 rollins kernel: [4.287162] Oops:  [#1] SMP 
Dec 31 14:50:06 rollins kernel: [4.287177] Modules linked in: binfmt_misc 
joydev nls_utf8 nls_cp437 vfat fat intel_rapl iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul 
jitterentropy_rng iTCO_wdt iTCO_vendor_support dell_wmi sparse_keymap 
sha256_ssse3 sha256_generic hmac dell_laptop dcdbas dell_smm_hwmon drbg arc4 
ansi_cprng snd_hda_codec_hdmi ath9k aesni_intel ath9k_common ath9k_hw nouveau 
aes_x86_64 snd_hda_codec_realtek lrw gf128mul snd_hda_codec_generic glue_helper 
ath ablk_helper cryptd mac80211 i915 efi_pstore pcspkr mxm_wmi snd_hda_intel 
ttm psmouse drm_kms_helper serio_raw snd_hda_codec cfg80211 efivars 
snd_hda_core rtsx_pci_ms snd_hwdep memstick snd_pcm drm snd_timer mei_me snd sg 
soundcore i2c_algo_bit i2c_i801 mei lpc_ich shpchp wmi battery ac dell_smo8800 
video button processor evdev uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core v4l2_common videodev media ath3k btusb btrtl btbcm btintel 
bluetooth rfkill i
 p_tables x_tables parport_pc ppdev lp parport loop dm_crypt dm_mod efivarfs 
autofs4 hid_generic usbhid hid ext4 crc16 mbcache jbd2 sd_mod rtsx_pci_sdmmc 
ahci libahci libata crc32c_intel xhci_pci sdhci_pci ehci_pci xhci_hcd sdhci 
ehci_hcd scsi_mod rtsx_pci mmc_core mfd_core r8169 mii usbcore usb_common
Dec 31 14:50:06 rollins kernel: [4.287675] CPU: 0 PID: 819 Comm: Xorg Not 
tainted 4.3.0-1-amd64 #1 Debian 4.3.3-2
Dec 31 14:50:06 rollins kernel: [4.287699] Hardware name: Dell Inc. XPS 
L421X/0CM76H, BIOS A12 09/28/2012
Dec 31 14:50:06 rollins kernel: [4.287720] task: 88025274f200 ti: 
880099d4 task.ti: 880099d4
Dec 31 14:50:06 rollins kernel: [4.287743] RIP: 0010:[]  
[] nvkm_pmu_pgob+0x5/0x20 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.287791] RSP: 0018:880099d43b18  
EFLAGS: 00010282
Dec 31 14:50:06 rollins kernel: [4.287807] RAX: a09b9a10 RBX: 
880253348008 RCX: 0018
Dec 31 14:50:06 rollins kernel: [4.287829] RDX:  RSI: 
 RDI: 
Dec 31 14:50:06 rollins kernel: [4.287851] RBP: 880253348018 R08: 
0007b5ff5134 R09: 880253348010
Dec 31 14:50:06 rollins kernel: [4.287872] R10: a09b9420 R11: 
880099d43dc8 R12: 880099062800
Dec 31 14:50:06 rollins kernel: [4.287893] R13: 880253348010 R14: 
880254a7b6d8 R15: 0002
Dec 31 14:50:06 rollins kernel: [4.287915] FS:  7f879bb63a00() 
GS:88025f20() knlGS:
Dec 31 14:50:06 rollins kernel: [4.287939] CS:  0010 DS:  ES:  CR0: 
80050033
Dec 31 14:50:06 rollins kernel: [4.287957] CR2:  CR3: 
99e96000 CR4: 001406f0
Dec 31 14:50:06 rollins kernel: [4.287979] Stack:
Dec 31 14:50:06 rollins kernel: [4.287987]  a09b9a39 
a071fa14  8802
Dec 31 14:50:06 rollins kernel: [4.288014]  fd57c0bf 
880253348018 88003693ec00 880253348010
Dec 31 14:50:06 rollins kernel: [4.288040]  880254a7b6d8 
0002 a0947704 880253348018
Dec 31 14:50:06 rollins kernel: [4.288066] Call Trace:
Dec 31 14:50:06 rollins kernel: [4.288094]  [] ? 
gf100_gr_oneinit+0x29/0x290 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288106] IPv6: ADDRCONF(NETDEV_UP): eth0: 
link is not ready
Dec 31 14:50:06 rollins kernel: [4.288140]  [] ? 
ttm_bo_handle_move_mem+0x284/0x5e0 [ttm]
Dec 31 14:50:06 rollins kernel: [4.288170]  [] ? 
nvkm_engine_init+0x74/0x1d0 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288200]  [] ? 
nvkm_subdev_init+0x88/0x1f0 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288227]  [] ? 
nvkm_engine_ref+0x4b/0x70 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288254]  [] ? 
nvkm_ioctl_new+0x125/0x290 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288291]  [] ? 
nvkm_fifo_chan_child_get+0x64/0x120 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288328]  [] ? 
nvkm_fifo_chan_dtor+0xa0/0xa0 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288357]  [] ? 
nvkm_object_new_+0x60/0x60 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288386]  [] ? 
nvkm_ioctl+0xfc/0x240 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288412]  [] ? 
nvif_object_init+0xba/0x120 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288449]  [] ? 
nouveau_abi16_ioctl_grobj_alloc+0x17e/0x2f0 [nouveau]
Dec 31 14:50:06 rollins kernel: [4.288485]  [] ? 
drm_vma_node_is_allowed+0x12/0x50 [drm]
Dec 31 14:50:06 rollins kernel: [4.288511]  [] ? 
drm_ioctl+0x110/0x440 [drm]
Dec 31 14:50:06 rollins kernel: [

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Erik de Castro Lopo]

Joachim Breitner wrote:

> Am Sonntag, den 20.12.2015, 13:30 +0100 schrieb John Paul Adrian Glaubitz:
> > 
> > Well, the person who made the change which broke ghc on armel said that
> > and I assume he is working on it in the future. His change, on the other
> > hand, improved ghc on armhf. So nothing is saying he is not improved
> > ghc on armel, too.
> 
> that is close, but not precisely true. Erik aimed to improve GHC on ARM
> in general, and accidentally broke it on old ARM (armel in our speak).
> I notified him of that problem, and he gave it a shot, but got stuck at
> a segfaulting binary. Undoubtly he would have loved to have it fixed,
> but could at that point not make progress. So the signal I got from him
> was that it is unfortunate that it broke, but given that – in his
> opinion – GHC on ARM was in a somewhat broken state before across the
> board (after all, he had good reasons to do the change in the first
> place), this is only superficially a regression. Also I noticed that he
> stopped working on this particular issue. I do not blame him for that:
> Quite contrary, I’m grateful for his work.
> 
> But the signal was: Upstream considered the ARM situation in 7.10.2,
> although superficially compiling, so bad that his fix was of patch-
> level-release urgency. Armel was broken, and no one actively and
> urgently working on a patch. So therefore, it was only conclusive to
> upload that to unstable and – after an early enough warning to d-arm
> with none even saying that it would be pity, let along announce that
> they would invest time – requests its removals.
> 
> In particular, I do not consider these actions premature.
> 
> 
> I CCed Erik, not to necessarily to turn this into a wider discussion,
> but just to give him the chance to correct any wrong statement I might
> have made about what he did or the state of affairs.

The only thing I have to add is that GHC for armhf is even less
healthy that you think.

My change was to force GHC to generate Arm instructions throughout
and that got GHCi working on Armhf. That worked for the code in
the 7.10 tree. However, since that change, an update to libc broke
GHCi even on Armhf. The problem is again the thumb-interop stuff;
the need to be be able to seamlessly call from Arm to Thumb code
and vice versa.

Fixing this requires a lot of work, something I simply do not have
time for at the moment. I'm actually much more interested in fixing
GHCI on Arm64 which currently looks like a much easier task.

Anyway I think you are right. Reverting the patch on armel can
get GHC on armel back to where it was.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/

Bug#779785: Same problem on armhf and x86_64

[Erik de Castro Lopo]

Hi,

I reported this problem for armhf in bug #786853 (which I just merged with this
one). I've now run into the same problem on x86_64.

Is there anything I can do to move this forward?

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#788542: git with https: GNU MP: Cannot allocate memory

[Erik de Castro Lopo]

Package: git
Version: 1:2.1.4+next.20141218-2
Severity: important


Something is very wrong here:

$ git clone https://git.haskell.org/ghc.git
Cloning into 'ghc'...
GNU MP: Cannot allocate memory (size=3067512724234699008)

Tried this on two different amd64 debian machines which very similar
results (different size value though). This works correctly on debian
armhf and powerpc machines.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git depends on:
ii  git-man  1:2.1.4+next.20141218-2
ii  libc62.19-18
ii  libcurl3-gnutls  7.42.1-2
ii  liberror-perl0.17-1.1
ii  libexpat12.1.0-6+b3
ii  libpcre3 2:8.35-5
ii  perl-modules 5.20.2-6
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages git recommends:
ii  less 458-3
ii  openssh-client [ssh-client]  1:6.7p1-6
ii  patch2.7.5-1
ii  rsync3.1.1-3

Versions of packages git suggests:
ii  gettext-base  0.19.4-1
pn  git-arch  none
pn  git-cvs   none
pn  git-daemon-run | git-daemon-sysvinit  none
pn  git-doc   none
pn  git-elnone
ii  git-email 1:2.1.4+next.20141218-2
pn  git-gui   none
pn  git-mediawiki none
ii  git-svn   1:2.1.4+next.20141218-2
pn  gitk  none
pn  gitwebnone

-- no debconf information


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

Bug#786850: gcc-4.9: AddressSanitizer fails with pthread_cond_init

[Erik de Castro Lopo]

Matthias Klose wrote:

 On 05/26/2015 08:32 AM, Erik de Castro Lopo wrote:
  Erik de Castro Lopo wrote:
  
  Package: gcc-4.9
  Version: 4.9.2-16
  Severity: normal
  
  Same problem with gcc-4.9.2-18 from unstable.
 
 please recheck with gcc-5 from unstable.


Works with gcc-5.

Thanks,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#786850: gcc-4.9: AddressSanitizer fails with pthread_cond_init

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Package: gcc-4.9
 Version: 4.9.2-16
 Severity: normal

Same problem with gcc-4.9.2-18 from unstable.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#786853: clang-3.7: Link error with -fsanitize=address

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Possible packaging error?

Very similar error if I try to use -fsanitize=address with
armhf with clang-3.5 and clang-3.6.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#786853: clang-3.7: Link error with -fsanitize=address

[Erik de Castro Lopo]

Package: clang-3.7
Version: 1:3.7~svn230892-1
Severity: normal

Dear Maintainer,

Compiling a simple Hello world style program with -fsanitize=address resukts
in:

$ clang-3.7 -Wall -fsanitize=address program.c -o program
/usr/bin/ld: cannot find /usr/lib/llvm-3.7/bin/../lib/clang/3.7.0/lib/linux/
libclang_rt.asan-arm.a: No such file or directory
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)

It seems that that clang expects /usr/lib/llvm-3.7/lib/clang/3.7.0/linux/ to
exist, but it doesn't. 

Possible packaging error?

Cheers,
Erik

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.10.72+ (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages clang-3.7 depends on:
ii  binutils 2.25-7
ii  libc62.19-18
ii  libc6-dev2.19-18
ii  libclang-common-3.7-dev  1:3.7~svn230892-1
ii  libclang1-3.71:3.7~svn230892-1
ii  libedit2 3.1-20150325-1
ii  libffi6  3.2.1-2
ii  libgcc-4.9-dev   4.9.2-18
ii  libgcc1  1:5.1.1-7
ii  libllvm3.7   1:3.7~svn230892-1
ii  libobjc-4.9-dev  4.9.2-18
ii  libstdc++-4.9-dev4.9.2-18
ii  libstdc++6   5.1.1-7
ii  libtinfo55.9+20140913-1+b1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages clang-3.7 recommends:
ii  llvm-3.7-dev  1:3.7~svn230892-1
ii  python2.7.9-1

Versions of packages clang-3.7 suggests:
pn  clang-3.7-doc  none
pn  gnustepnone
pn  gnustep-devel  none

-- no debconf information


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

Bug#786850: gcc-4.9: AddressSanitizer fails with pthread_cond_init

[Erik de Castro Lopo]

Package: gcc-4.9
Version: 4.9.2-16
Severity: normal

Dear Maintainer,

Trivial C program:

#include stdio.h
#include pthread.h
int main (void)
{   pthread_cond_t cond;
pthread_cond_init(cond, NULL);
return 0;
}

Above works correctly when compiled and run (even under Valgrind) as:

 gcc -Wall cond_init.c -o cond_init  valgrind ./cond_init

on both x86_64/linux and armhf/linux.

However, then compiled with -fsanitize=address as:

 gcc -Wall -fsanitize=address cond_init.c -o cond_init  ./cond_init

it works correctly on x86_64/linux but gets a SIGSEGV on armhf/linux:

ASAN:SIGSEGV
=
==23193==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc 
0x
sp 0xbeffefb0 bp 0x T0)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ??:0 ??
==23193==ABORTING

Apparently this was a problem in gcc-4.8

https://code.google.com/p/address-sanitizer/issues/detail?id=297

but I'm using the Debian gcc-4.9 package.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.10.72+ (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcc-4.9 depends on:
ii  binutils2.25-7
ii  cpp-4.9 4.9.2-16
ii  gcc-4.9-base4.9.2-16
ii  libc6   2.19-18
ii  libcloog-isl4   0.18.3-1
ii  libgcc-4.9-dev  4.9.2-16
ii  libgmp102:6.0.0+dfsg-6
ii  libisl130.14-2
ii  libmpc3 1.0.3-1
ii  libmpfr43.1.2-3
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-18

Versions of packages gcc-4.9 suggests:
pn  gcc-4.9-doc  none
pn  gcc-4.9-locales  none
pn  libasan1-dbg none
pn  libatomic1-dbg   none
pn  libcilkrts5-dbg  none
pn  libgcc1-dbg  none
pn  libgomp1-dbg none
pn  libitm1-dbg  none
pn  liblsan0-dbg none
pn  libquadmath-dbg  none
pn  libtsan0-dbg none
pn  libubsan0-dbgnone

-- no debconf information


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

Bug#782860: FTBFS : use of undeclared identifier '__NR_open'

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 To me it looks like some dependency is missing.

Same problem even after I install linux-headers-amd64.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#782860: FTBFS : use of undeclared identifier '__NR_open'

[Erik de Castro Lopo]

Source: llvm-toolchain-3.5
Version: llvm-toolchain-3.5 (1:3.5-10)
Severity: important

Trying to build from source so I can then raise another bug *and*
provide a patch when I discovered I was not able to build the 
package from the un-modified Debian source package.

I just used `apt-get source llvm-toolchain-3.5` to get the sources
and then changed into the directory and used `dpkg-buildpackage`
to build it. Everything was going ok until I go to the part included
below.

To me it looks like some dependency is missing.

Cheers,
Erik

/tmp/llvm-toolchain-3.5-3.5/build-llvm/Release/bin/clang -std=c++11 
-fno-exceptions -fPIC -funwind-tables 
-I/tmp/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib 
-I/tmp/llvm-toolchain-3.5-3.5/projects/compiler-rt/include -Wall -Werror -O3 
-fomit-frame-pointer -m32 -fPIE -fno-builtin -gline-tables-only -fno-rtti -c -o 
/tmp/llvm-toolchain-3.5-3.5/build-llvm/tools/clang/runtime/compiler-rt/clang_linux/san-i386/i386/SubDir.lib__sanitizer_common/sanitizer_linux.o
 
/tmp/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc
/tmp/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_linux.cc:123:27:
 error: use of
  undeclared identifier '__NR_open'
  return internal_syscall(SYSCALL(open), (uptr)filename, flags);
  ^
/tmp/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_syscall_generic.inc:17:24:
 note: 
  expanded from macro 'SYSCALL'
# define SYSCALL(name) __NR_ ## name
   ^
scratch space:57:1: note: expanded from here
__NR_open
^



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


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

Bug#782868: GHC calling convention incorrect

[Erik de Castro Lopo]

Source: llvm-toolchain-3.5
Version: 1:3.5-10
Severity: normal
Tags: patch

LLVM implements a special calling convention which is used exclusively
by the Glasgow Haskell Compiler (GHC). The llvm-3.5.0 release had a bug
in the GHC calling convention for Arm resulting in Haskell programs
compiled for arm would segfault on being run. See the GHC bug tracker:

https://ghc.haskell.org/trac/ghc/ticket/9920

Release 7.10 of GHC can *only* use the llvm-3.5, but version 3.5.0 has
this bug while 3.5.1 and later do not.

The patch in the above GHC trac ticket applied to the 3.5.0 tree fixes 
this. I have also taken the llvm-toolchain-3.5 debian sources, add the
above patch to the debian/patches/ directory (and updated the series
file) and built it. Unfortunately I can build this package to completion
because of an FTBFS bug (#782860) but the build proceeds far enough for
me to grab the file `build-llvm/Release/bin/llc` to test it and it works
fine.

I will attach the require patch to the ticket.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Origin: https://github.com/llvm-mirror/llvm/commit/f7f88095a32d1ac5bc7778204fd9a37a9fb8082c
Author: Tim Northover tnortho...@apple.com
Date:   Mon Dec 1 17:46:39 2014 +
Subject: ARM: lower tail calls correctly when using GHC calling convention.

 Patch by Ben Gamari.

 This patch was pulled from the LLVM git mirror and tweaked slightly to apply
 cleanly to llvm version 3.5.

---
 lib/Target/ARM/ARMFrameLowering.cpp  | 91 +++-
 lib/Target/ARM/ARMFrameLowering.h|  2 +
 test/CodeGen/ARM/ghc-tcreturn-lowered.ll | 21 
 3 files changed, 76 insertions(+), 38 deletions(-)
 create mode 100644 test/CodeGen/ARM/ghc-tcreturn-lowered.ll

diff --git a/lib/Target/ARM/ARMFrameLowering.cpp b/lib/Target/ARM/ARMFrameLowering.cpp
index a67b360..e55f652 100644
--- a/lib/Target/ARM/ARMFrameLowering.cpp
+++ b/lib/Target/ARM/ARMFrameLowering.cpp
@@ -566,11 +566,59 @@ void ARMFrameLowering::emitPrologue(MachineFunction MF) const {
 AFI-setShouldRestoreSPFromFP(true);
 }
 
+// Resolve TCReturn pseudo-instruction
+void ARMFrameLowering::fixTCReturn(MachineFunction MF,
+   MachineBasicBlock MBB) const {
+  MachineBasicBlock::iterator MBBI = MBB.getLastNonDebugInstr();
+  assert(MBBI-isReturn()  Can only insert epilog into returning blocks);
+  unsigned RetOpcode = MBBI-getOpcode();
+  DebugLoc dl = MBBI-getDebugLoc();
+  const ARMBaseInstrInfo TII =
+  *static_castconst ARMBaseInstrInfo *(MF.getTarget().getInstrInfo());
+
+  if (!(RetOpcode == ARM::TCRETURNdi || RetOpcode == ARM::TCRETURNri))
+return;
+
+  // Tail call return: adjust the stack pointer and jump to callee.
+  MBBI = MBB.getLastNonDebugInstr();
+  MachineOperand JumpTarget = MBBI-getOperand(0);
+
+  // Jump to label or value in register.
+  if (RetOpcode == ARM::TCRETURNdi) {
+unsigned TCOpcode = STI.isThumb() ?
+ (STI.isTargetMachO() ? ARM::tTAILJMPd : ARM::tTAILJMPdND) :
+ ARM::TAILJMPd;
+MachineInstrBuilder MIB = BuildMI(MBB, MBBI, dl, TII.get(TCOpcode));
+if (JumpTarget.isGlobal())
+  MIB.addGlobalAddress(JumpTarget.getGlobal(), JumpTarget.getOffset(),
+   JumpTarget.getTargetFlags());
+else {
+  assert(JumpTarget.isSymbol());
+  MIB.addExternalSymbol(JumpTarget.getSymbolName(),
+JumpTarget.getTargetFlags());
+}
+
+// Add the default predicate in Thumb mode.
+if (STI.isThumb()) MIB.addImm(ARMCC::AL).addReg(0);
+  } else if (RetOpcode == ARM::TCRETURNri) {
+BuildMI(MBB, MBBI, dl,
+TII.get(STI.isThumb() ? ARM::tTAILJMPr : ARM::TAILJMPr)).
+  addReg(JumpTarget.getReg(), RegState::Kill);
+  }
+
+  MachineInstr *NewMI = std::prev(MBBI);
+  for (unsigned i = 1, e = MBBI-getNumOperands(); i != e; ++i)
+NewMI-addOperand(MBBI-getOperand(i));
+
+  // Delete the pseudo instruction TCRETURN.
+  MBB.erase(MBBI);
+  MBBI = NewMI;
+}
+
 void ARMFrameLowering::emitEpilogue(MachineFunction MF,
 MachineBasicBlock MBB) const {
   MachineBasicBlock::iterator MBBI = MBB.getLastNonDebugInstr();
   assert(MBBI-isReturn()  Can only insert epilog into returning blocks);
-  unsigned RetOpcode = MBBI-getOpcode();
   DebugLoc dl = MBBI-getDebugLoc();
   MachineFrameInfo *MFI = MF.getFrameInfo();
   ARMFunctionInfo *AFI = MF.getInfoARMFunctionInfo();
@@ -588,8 +636,10 @@ void ARMFrameLowering::emitEpilogue(MachineFunction MF,
 
   // All calls are tail calls in GHC calling conv, and 

Bug#779012: Anu update on this?

[Erik de Castro Lopo]

Hi,

Any update on this?

I have a Jenkin instance that builds a couple of my packages, including
cross compiling them to 32 and 64 bit Windows and running the test suite
under Wine.

Each time the wine package gets upgraded, I have to manually re-apply
this patch. It I don't, the tests for the 64 bit Windows build will
fail.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#780704: Latest upstream version is 3.2.1

[Erik de Castro Lopo]

Package: cmake
Version: 3.0.2-1
Severity: normal

Would be nice to get this new version in Debian.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cmake depends on:
ii  cmake-data3.0.2-1
ii  dpkg  1.17.24
ii  libarchive13  3.1.2-11
ii  libc6 2.19-15
ii  libcurl3  7.38.0-4
ii  libexpat1 2.1.0-6+b3
ii  libgcc1   1:4.9.2-10
ii  libstdc++64.9.2-10
ii  procps2:3.3.9-9
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages cmake recommends:
ii  gcc   4:4.9.2-2
ii  make  4.0-8.1

Versions of packages cmake suggests:
pn  codeblocks   none
pn  eclipse  none
pn  ninja-build  none

-- no debconf information


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

Bug#779012: Two issues with /usr/bin/wine script

[Erik de Castro Lopo]

Package: wine
Version: 1.6.2-19
Severity: normal
Tags: patch

Hi,

There are currently two issues with the /usr/bin/wine script:

a) On amd64 if fails when there more than one foreign-achitecture installed.
   For instance on my machine where I do a lot of cross-compiling from amd64
   to armhf and arm64:

 dpkg --print-foreign-architectures
i386
armhf
arm64
   which causes the existing foreign architecture test to fail.
   
b) The current script does not seamlessly handle both 32 and 64 bit binaries.
   Fortunately its trivial to add this support using file to detect whether
   the windows binary is 32 or 64 bit and then setting WINEPREFIX to either
   $HOME/.wine for 32 or $HOME/.wine64 for 64 bits.

Patch containing fixes for both these issues attached.

Cheers,
Erik

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), 
(500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, arm64

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wine depends on:
ii  file1:5.20-2
ii  wine32  1.6.2-19
ii  wine64  1.6.2-19

wine recommends no packages.

Versions of packages wine suggests:
pn  avscan | klamav | clamav   none
ii  binfmt-support 2.1.5-1
ii  ttf-mscorefonts-installer  3.6
pn  winbindnone

-- no debconf information
--- /usr/bin/wine	2015-01-11 05:40:21.0 +1100
+++ usr_bin_wine	2015-01-05 21:15:03.311892601 +1100
@@ -6,11 +6,22 @@
 wine32=$bindir/wine32
 wine64=$bindir/wine64
 
+if test -z ${WINEARCH}${WINEPREFIX} ; then
+if test $(file $1 | grep -c 'Intel 80386') -eq 1 ; then
+WINEARCH=win32
+WINEPREFIX=$HOME/.wine
+elif test $(file $1 | grep -c 'x86-64') -eq 1 ; then
+WINEARCH=win64
+WINEPREFIX=$HOME/.wine64
+fi
+fi
+
+
 if test -x $wine32 -a $WINEARCH != win64; then
 wine=$wine32
 elif test -x $wine64; then
 wine=$wine64
-if [ $(dpkg --print-architecture) = amd64 -a $(dpkg --print-foreign-architectures) != i386 ]; then
+if [ $(dpkg --print-architecture) = amd64 -a $(dpkg --print-foreign-architectures | grep -c i386) -ne 1 ]; then
 echo it looks like multiarch needs to be enabled.  as root, please
 echo execute \dpkg --add-architecture i386  apt-get update 
 echo apt-get install $(echo $name | sed s/wine/wine32/)\

Bug#772874: libsndfile1-dev: bugs in some format handlers

[Erik de Castro Lopo]

Frank Heckenbach wrote:

 Package: libsndfile1-dev
 Version: 1.0.25-5
 Severity: normal

Thanks for the bug report.

None of these issues are Debian specific and hence are probably
better addressed in the upstream projects bug tracker:

https://github.com/erikd/libsndfile/

 - Ogg/Vorbis: vorbis_metatypes is lacking:
 
   { SF_STR_TRACKNUMBER, Tracknumber },
   { SF_STR_GENRE, Genre },

I raised this:

https://github.com/erikd/libsndfile/issues/87


 - Wav:
 
 wav.c:308 has:
 
 if (psf-filelength  SF_PLATFORM_S64 (0x))
 psf_log_printf (psf, Warning : filelength  0x. This 
 is bad\n) ;
 
 But for non-seekable files, filelength is set to SF_COUNT_MAX which
 is  0x, so this produces a bogus warning e.g. when doing:
 
 cat somefile.wav | sndfile-info -

https://github.com/erikd/libsndfile/issues/88


 - Voc:

snip

 The first error is clearly bogus because if it could not open the
 file how could it (correctly) determine the length, samplerate etc.?
 OK, that's just a problem with the formulation of the message
 (open != parse).

Open means that libsndfile's sf_open() function returns a non-NULL
pointer as documented here:

http://www.mega-nerd.com/libsndfile/api.html#open

 But the second error is the real problem. It claims there is an
 error in the file. However, this is an original file recorded with
 original recorder software from Creative Labs on a Dos system some
 20 years ago. (I just purged the samples because it was a private
 recording and for compressibility ;), the error was the same before
 and after.)

An error is returned when libsndfile cannot correctly open the file.
Is that not an error?

 Looking at the code (voc.c:256) and also at the strace output, it
 doesn't even check more than one section to determine whether
 they're incompatible (whatever that means -- I guess sections with
 different sample rates might qualify), just gives this message after
 finding there's more than one section!?

A couple of points here:

* VOC is a format that has not been in widespread use for over a decade.
* libsndfile does not handle *any* formats with more than one section.

 I don't really understand what's up here. Either this is unfinished
 code without the appropriate WIP warning,

Err, can you actually name one piece of non-trivial software that is
actually finished? All software is a WIP, and that is especially so
for most Open Source projects.

 or the message is really
 meant to say: Sorry, this library supports VOC files with one
 section only, in which case the accusation Error in VOC file is
 not a good way to put that.

If you look in the code you will find that Error in VOC file is
an error that can occur in a number of situations. Error reporting
is difficult.


Since none of these issues are Debian specific, I suggest you 
close this bug and follow the tickets on github.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#772436: aarch64 optimization bug

[Erik de Castro Lopo]

Package: gcc-4.9
Version: 4.9.1-19
Severity: normal

I have a minimal reproducable test case in a git repo here:

https://github.com/erikd/gcc-aarch64-optimization-bug

which contails a test program which passes when run with
optimization flags -O1 and fails with -O1 -fschedule-insns.

Cloning that repo under aarch64 and doing:

CC=gcc-4.9 make clean check

compiles and runs the program with both sets of optimization
flags and displays success or failure. It does not hwoever
fail on aarch64 with gcc-4.8 or with gcc-snapshot, nor does
it fail with any version of GCC on any other architecture.

There is a usefule comment from Måns Rullgård on G+:

https://plus.google.com/u/0/+ErikdeCastroLopo/posts/F2BPxT7g1Gx

OK, it's a gcc bug. For some unfathomable reason, it chooses to
calculate mask = ~0u  (32 - numBits) in a vector register by
means of left-shifting by -(32 - numBits). It then subtracts 
(bitPos  7) from the negated value and uses this as the shift 
amount of a regular shift instruction in mask = shift which
is obviously nonsense.

This behaviour (and the bug) was introduced in rev 202020 (git
5674183), and reverting this commit makes things work again.

I believe the -fschedule-insns flag is a red herring. It probably 
merely stirs up the code in a way that makes the real bug trigger.

Older discussion about this problem here:

https://plus.google.com/u/0/+ThomasRuecker/posts/e9uxoUyk3Bk

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.90.20141201-1
ii  cpp-4.9 4.9.2-5
ii  gcc-4.9-base4.9.2-5
ii  libc6   2.19-13
ii  libcloog-isl4   0.18.2-1+b2
ii  libgcc-4.9-dev  4.9.2-5
ii  libgmp102:6.0.0+dfsg-6
ii  libisl100.12.2-2+b2
ii  libmpc3 1.0.2-1+b2
ii  libmpfr43.1.2-1+b2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.19-13

Versions of packages gcc-4.9 suggests:
pn  gcc-4.9-doc  none
pn  gcc-4.9-locales  none
pn  libasan1-dbg none
pn  libatomic1-dbg   none
pn  libcilkrts5-dbg  none
pn  libgcc1-dbg  none
pn  libgomp1-dbg none
pn  libitm1-dbg  none
pn  liblsan0-dbg none
pn  libquadmath-dbg  none
pn  libtsan0-dbg none
pn  libubsan0-dbgnone

-- no debconf information


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

Bug#770918: Two CVEs against FLAC

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Package: flac
 Version: 1.3.0-2+b1
 Severity: serious
 Tags: security
 
 From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html
 
  Google Security Team member, Michele Spagnuolo, recently found two potential
  problems in the FLAC code base. They are :
  
  CVE-2014-9028 : Heap buffer write overflow
  CVE-2014-8962 : Heap buffer read overflow
  
  For Linux distributions, the specific fixes for these two CVEs are available
  from Git here:
  
  
  https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85
  
  https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e
  
  and are simple enough that they should apply cleanly to the last official
  release 1.3.0 and possibly even the previous one, 1.2.1.

One more patch to cherry pick:


https://git.xiph.org/?p=flac.git;a=commit;h=5a365996d739bdf4711af51d9c2c71c8a5e14660


  A pre-release (version 1.3.1pre1) for the next version which includes these
  fixes and more is available here:
  
  http://downloads.xiph.org/releases/flac/beta/
  
  A full release (version 1.3.1) will be available in the next couple of days.

The 1.3.1 release is available here:

http://downloads.xiph.org/releases/flac/

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#770918: Two CVEs against FLAC

[Erik de Castro Lopo]

Package: flac
Version: 1.3.0-2+b1
Severity: serious
Tags: security

From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html

 Google Security Team member, Michele Spagnuolo, recently found two potential
 problems in the FLAC code base. They are :
 
 
 CVE-2014-9028 : Heap buffer write overflow
 CVE-2014-8962 : Heap buffer read overflow
 
 For Linux distributions, the specific fixes for these two CVEs are available
 from Git here:
 
 
 https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85
 
 https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e
 
 and are simple enough that they should apply cleanly to the last official
 release 1.3.0 and possibly even the previous one, 1.2.1.
 
 A pre-release (version 1.3.1pre1) for the next version which includes these
 fixes and more is available here:
 
 http://downloads.xiph.org/releases/flac/beta/
 
 A full release (version 1.3.1) will be available in the next couple of days.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages flac depends on:
ii  libc6 2.19-13
ii  libflac8  1.3.0-2+b1

flac recommends no packages.

flac suggests no packages.

-- no debconf information


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

Bug#770813: /usr/bin/wine script insufficiently clever

[Erik de Castro Lopo]

Package: wine
Version: 1.6.2-16
Severity: normal

I have a number of project written in C that I cross compile from Linux
to Windows. These projects often have test programs also written in C
and these I run under Wine.

This all works fine when I'm compiling 32 bit windows binaries but for
64 bit binaries there's a bit of a problem, the /usr/bin/wine script
fails for 64 bit windows binaries although if I set some environment
variables I can run 64 bit binaries, eg:

WINARCH=wine64 WINEPREFIX=~/.wine64 wine hello64.exe

My suggestion is that if $WINEARCH and $WINEPREFIX are both empty
strings, the script could use the file command to figure out whether
the binary is 32 or 64 bits and set those variables appropriately.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages wine depends on:
ii  file1:5.20-2
ii  wine32  1.6.2-16
ii  wine64  1.6.2-16

wine recommends no packages.

Versions of packages wine suggests:
pn  avscan | klamav | clamav   none
ii  binfmt-support 2.1.5-1
ii  ttf-mscorefonts-installer  3.6
pn  winbindnone

-- no debconf information


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

Bug#770813: /usr/bin/wine script insufficiently clever [patch]

[Erik de Castro Lopo]

The following seems to work for me.

--- /usr/bin/wine.orig  2014-11-03 05:33:12.0 +1100
+++ /usr/bin/wine   2014-11-24 20:35:10.081487087 +1100
@@ -6,6 +6,16 @@
 wine32=$bindir/wine32
 wine64=$bindir/wine64
 
+if test -z ${WINEARCH}${WINEPREFIX} ; then
+   if test $(file $1 | grep -c 'Intel 80386') -eq 1 ; then
+   WINEARCH=win32
+   WINEPREFIX=$HOME/.wine
+   elif test $(file $1 | grep -c 'x86-64') -eq 1 ; then
+   WINEARCH=win64
+   WINEPREFIX=$HOME/.wine64
+   fi
+fi
+
 if test -x $wine32 -a $WINEARCH != win64; then
 wine=$wine32
 elif test -x $wine64; then



-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#765449: Two kworder processes takin up 30% CPU each after coming out of suspend

[Erik de Castro Lopo]

Package: src:linux
Version: 3.16.3-2
Severity: normal

I've now seen this a couple of times with this kernel after coming out
of suspend. This is not something I have seen on this now two year old
machine before.

After coming out of suspend top shows this:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  19127 root  20   0   0  0  0 S  31.3  0.0   4:42.20 
kworker/2:2
   5448 root  20   0   0  0  0 S  31.3  0.0   0:25.94 
kworker/0:0
 84 root  20   0   0  0  0 S  18.8  0.0   6:21.82 khubd 
 
  3 root  20   0   0  0  0 S  12.5  0.0   4:51.46 
ksoftirqd/0
 18 root  20   0   0  0  0 S   6.3  0.0   3:43.13 
ksoftirqd/2

The 'iotop -Pa' command shows almost zero I/O going on.

Running perf suggests this is an issue with the xhci_hub_control:

+  8.65%   8.65%swapper  [kernel.kallsyms]  [k] intel_idle  
◆
+  7.92%   7.92%kworker/2:2  [kernel.kallsyms]  [k] xhci_hub_control
▒
+  7.80%   7.80%kworker/0:1  [kernel.kallsyms]  [k] xhci_hub_control
▒
+  1.08%   1.08%kworker/2:2  [kernel.kallsyms]  [k] __switch_to 
▒
+  0.99%   0.99%kworker/0:1  [kernel.kallsyms]  [k] __switch_to 
▒
+  0.84%   0.84%  khubd  [kernel.kallsyms]  [k] _raw_spin_lock_i

I'm going to try linux-image-3.17-rc5-amd64.

-- Package-specific info:
** Version:
Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 
(Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 
root=UUID=5065a2f9-ec31-4a10-8992-ccda124f2d26 ro

** Not tainted

** Kernel log:
[217163.906374] cfg80211: World regulatory domain updated:
[217163.906377] cfg80211:  DFS Master region: unset
[217163.906378] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[217163.906380] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[217163.906382] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[217163.906383] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 
mBm), (N/A)
[217163.906384] cfg80211:   (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[217163.906385] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 
mBm), (N/A)
[217163.906386] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 
0 mBm), (N/A)
[217164.084725] wlan0: send auth to 6c:99:89:99:1a:af (try 2/3)
[217164.086361] wlan0: authenticated
[217164.088728] wlan0: associate with 6c:99:89:99:1a:af (try 1/3)
[217164.091941] wlan0: RX AssocResp from 6c:99:89:99:1a:af (capab=0x11 status=0 
aid=1)
[217164.092041] wlan0: associated
[217164.092113] cfg80211: Calling CRDA for country: AU
[217164.096299] ath: EEPROM regdomain: 0x8024
[217164.096304] ath: EEPROM indicates we should expect a country code
[217164.096307] ath: doing EEPROM country-regdmn map search
[217164.096309] ath: country maps to regdmn code: 0x21
[217164.096311] ath: Country alpha2 being used: AU
[217164.096313] ath: Regpair used: 0x21
[217164.096316] ath: regdomain 0x8024 dynamically updated by country IE
[217164.096352] cfg80211: Regulatory domain changed to country: AU
[217164.096355] cfg80211:  DFS Master region: unset
[217164.096358] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[217164.096362] cfg80211:   (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[217164.096366] cfg80211:   (517 KHz - 525 KHz @ 8 KHz), (N/A, 1700 
mBm), (N/A)
[217164.096369] cfg80211:   (525 KHz - 533 KHz @ 8 KHz), (N/A, 2400 
mBm), (0 s)
[217164.096372] cfg80211:   (549 KHz - 571 KHz @ 8 KHz), (N/A, 2400 
mBm), (0 s)
[217164.096375] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 3000 
mBm), (N/A)
[217387.136173] wlan0: authenticate with 6c:99:89:a7:93:40
[217387.142728] wlan0: send auth to 6c:99:89:a7:93:40 (try 1/3)
[217387.142791] cfg80211: Calling CRDA to update world regulatory domain
[217387.148750] wlan0: authenticated
[217387.152178] wlan0: associate with 6c:99:89:a7:93:40 (try 1/3)
[217387.157918] wlan0: RX AssocResp from 6c:99:89:a7:93:40 (capab=0x431 
status=0 aid=4)
[217387.158006] wlan0: associated
[217387.158160] cfg80211: Calling CRDA to update world regulatory domain
[217387.165481] cfg80211: World regulatory domain updated:
[217387.165484] cfg80211:  DFS Master region: unset
[217387.165485] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[217387.165487] cfg80211:   (2402000 

Bug#755894: systemd does not start postgresql

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Installed postgresql 9.3+157 on a system which already had systemd as its
 init system. When i try to start postgresql:
 
 # systemctl start postgresql
 # systemctl status postgresql
 postgresql.service - LSB: PostgreSQL RDBMS server
Loaded: loaded (/etc/init.d/postgresql)
Active: active (exited) since Tue 2014-07-22 10:40:04 EST; 2 days ago
 
 This looks like : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731862
 
 That bugs asks for an strace output. That should be attached to this report.

Ah this is weird!

It seems systemctl doesn't know how do find the status of the postgresql
daemon. Turns out the systemd service file for postgresql is complete
rubbish:

# systemd service for managing all PostgreSQL clusters on the system. This
# service is actually a systemd target, but we are using a service since
# targets cannot be reloaded.

[Unit]
Description=PostgreSQL RDBMS

[Service]
Type=oneshot
ExecStart=/bin/true
ExecReload=/bin/true
RemainAfterExit=on

[Install]
WantedBy=multi-user.target

This is obviously wrong.


Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#755894: systemd does not start postgresql

[Erik de Castro Lopo]

Christoph Berg wrote:

 Re: Erik de Castro Lopo 2014-08-11 
 20140811205417.510fba1b4dc7f22595328...@mega-nerd.com
  It seems systemctl doesn't know how do find the status of the postgresql
  daemon. Turns out the systemd service file for postgresql is complete
  rubbish:
  
  # systemd service for managing all PostgreSQL clusters on the system. 
  This
  # service is actually a systemd target, but we are using a service since
  # targets cannot be reloaded.
  
  [Unit]
  Description=PostgreSQL RDBMS
  
  [Service]
  Type=oneshot
  ExecStart=/bin/true
  ExecReload=/bin/true
  RemainAfterExit=on
  
  [Install]
  WantedBy=multi-user.target
  
  This is obviously wrong.
 
 You obviously didn't read the comments there.

Oh, I read them but they made close to zero sense to me and were vastly
different from the postgresql.service files I'd found elsewehere on
the 'net, like the one here:

https://bbs.archlinux.org/viewtopic.php?pid=1165363#p1165363

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#750098: libsndfile: Inconsistent use of -funsigned-char

[Erik de Castro Lopo]

Michael Tautschnig wrote:

 Package: libsndfile
 Version: 1.0.25-9
 Severity: minor
 Usertags: goto-cc
 
 During a rebuild of all packages in a clean sid chroot (and 
 cowbuilder+pbuilder)
 the build failed with the following error. Please note that we use our 
 research
 compiler tool-chain (using tools from the cbmc package), which permits 
 extended
 reporting on type inconsistencies at link time.

This has been fixed upstream:


https://github.com/erikd/libsndfile/commit/2b598d2e2322f76a94be0a26405e02b9704e4caf

It will be in the next release.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#578869: #578869 - g-s-d crashes when changing resolutions/adding monitors

[Erik de Castro Lopo]

althaser wrote:

 Hey,
 
 this is an old bug.
 
 Could you please still reproduce this issue with newer
 gnome-settings-daemon version like 3.4.2+git20121218.7c1322-3+deb7u3 or
 3.8.5-2 ?

Sorry, I've long since given up on Gnome. Feel free to close this
bug.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#745105: gcc-4.9: invalid args to -fsanitize should be an error not a warning

[Erik de Castro Lopo]

Package: gcc-4.9
Version: 4.9-20140411-2
Severity: normal

This is a regression from gcc-4.8.

With gcc-4.8 this works because -fsanitize=address works in 4.8:

 gcc-4.8 -fsanitize=address test.c -o /dev/null

and this fails and exits with non-zero because -fsanitize=integer
is not supported in 4.8:

 gcc-4.8 -fsanitize=integer test.c -o /dev/null
gcc-4.8: error: unrecognized command line option ‘-fsanitize=integer’
 echo $?
1

Now for 4.9:

 gcc-4.9 -fsanitize=integer test.c -o /dev/null
gcc-4.9: warning: unrecognized argument to -fsanitize= option: ‘integer’
cc1: warning: unrecognized argument to -fsanitize= option: ‘integer’
 echo $?
0

This should exit with non-zero so that support for this flag can correctly
be detected in things line autoconf generated configure scripts.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gcc-4.9 depends on:
ii  binutils2.24.51.20140411-2
ii  cpp-4.9 4.9-20140411-2
ii  gcc-4.9-base4.9-20140411-2
ii  libc6   2.18-4
ii  libcloog-isl4   0.18.2-1
ii  libgcc-4.9-dev  4.9-20140411-2
ii  libgmp102:6.0.0+dfsg-2
ii  libisl100.12.2-1
ii  libmpc3 1.0.1-1
ii  libmpfr43.1.2-1
ii  zlib1g  1:1.2.8.dfsg-1

Versions of packages gcc-4.9 recommends:
ii  libc6-dev  2.18-4

Versions of packages gcc-4.9 suggests:
ii  binutils [binutils-gold]  2.24.51.20140411-2
pn  gcc-4.9-doc   none
ii  gcc-4.9-locales   4.9-20140411-2
ii  gcc-4.9-multilib  4.9-20140411-2
ii  libasan1-dbg  4.9-20140411-2
ii  libatomic1-dbg4.9-20140411-2
ii  libcilkrts5-dbg   4.9-20140411-2
ii  libgcc1-dbg   1:4.9-20140411-2
ii  libgomp1-dbg  4.9-20140411-2
ii  libitm1-dbg   4.9-20140411-2
ii  liblsan0-dbg  4.9-20140411-2
ii  libquadmath0-dbg  4.9-20140411-2
ii  libtsan0-dbg  4.9-20140411-2
ii  libubsan0-dbg 4.9-20140411-2
ii  libvtv0-dbg   4.9-20140411-2

-- no debconf information


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

Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Yes, I was using systemd on the machine where this is a problem and
 *not* using systemd on the machine where there is no problem.
 
 On the machine that was having the problem I un-installed systemd
 and the problem disappeared. This is definitely systemd related.

Can anyone figure out from what we know so far if this is an schroot
but or a systemd bug?

If someone can give me a gentle nudge in the right direction I'm willing
to invest some time on this because I really do need this bug fixed.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Can anyone figure out from what we know so far if this is an schroot
 but or a systemd bug?
 
 If someone can give me a gentle nudge in the right direction I'm willing
 to invest some time on this because I really do need this bug fixed.

Now I can't even re-produce this bug.

I'm still using schroot 1.6.8-1 with systemd 204-8 but upgrading something
else (no clue what) seems to have fixed.

I have schroot working properly again. I'm very happy. If no one else can
re-produce this then the bug should be closed.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#726872: Lock screen does nothing

[Erik de Castro Lopo]

althaser wrote:

 Could you please still reproduce this issue with newer gnome-shell version
 like 3.8.4-5+b1 ?
 
 I'm running 3.8.4-5+b1 here and lock is working fine here. I don't even
 have gnome-screensaver installed.

I no longer use gnome-shell. Free free to close this if no one else can
reproduce it.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#726872: Lock screen does nothing

[Erik de Castro Lopo]

althaser wrote:

 Could you please still reproduce this issue with newer gnome-shell version
 like 3.8.4-5+b1 ?
 
 I'm running 3.8.4-5+b1 here and lock is working fine here. I don't even
 have gnome-screensaver installed.

I no longer use gnome-shell. Free free to close this if no one else can
reproduce it.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#648940: gnome-shell hangs

[Erik de Castro Lopo]

althaser wrote:

 Hey,
 
 this is an old bug report.
 
 Could you please still reproduce this issue with newer gnome-shell version
 like 3.4.2-7+deb7u1 or 3.8.4-5+b1 ?

Sorry, I ditched gnome-shell some time ago, not just because of this
hang.

Please feel free to close this bug.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Roger Leigh wrote:

  Could this have something to do with the fact that I have /home
  as a separate ext4 partition and that the chroots are kept in
  under /home ?
 
 I'm not sure.  I wouldn't think so, but I haven't tried it myself.
 
 Have you seen the other bug where systemd breaks bind mounting?
 Are you using sytemd?

Yes, I was using systemd on the machine where this is a problem and
*not* using systemd on the machine where there is no problem.

On the machine that was having the problem I un-installed systemd
and the problem disappeared. This is definitely systemd related.

Cheers,
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 I see two mount points for every one mount point I expect. Eg:
 
 
 /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp
 
 and
 /home/chroot/sid64/home/chroot/sid64/tmp
 
 The second one seems wrong.


Could this have something to do with the fact that I have /home
as a separate ext4 partition and that the chroots are kept in
under /home ?

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 On the machine that displays this problem I have a amd64 Sid chroot
 called sid64. If I run it using 'schroot -c sid64' and immediately
 exit I get:

If I just start the chroot and run mount I see:

  /dev/sda4 on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1 type ext4 
(rw,relatime,data=ordered)
  proc on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/proc type 
proc (rw,nosuid,nodev,noexec,relatime)
  proc on /home/chroot/sid64/proc type proc (rw,nosuid,nodev,noexec,relatime)
  sysfs on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/sys type 
sysfs (rw,nosuid,nodev,noexec,relatime)
  sysfs on /home/chroot/sid64/sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  udev on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/dev 
type devtmpfs (rw,relatime,size=10240k,nr_inodes=1006767,mode=755)
  udev on /home/chroot/sid64/dev type devtmpfs 
(rw,relatime,size=10240k,nr_inodes=1006767,mode=755)
  devpts on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/dev/pts type 
devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  devpts on /home/chroot/sid64/dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  /dev/sda4 on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home type 
ext4 (rw,relatime,data=ordered)
  /dev/sda4 on /home/chroot/sid64/home type ext4 (rw,relatime,data=ordered)
  /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/tmp type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
  /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on 
/home/chroot/sid64/tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered)
  /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on 
/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp
 type ext4 (rw,relatime,errors=remount-ro,data=ordered)
  /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on 
/home/chroot/sid64/home/chroot/sid64/tmp type ext4 
(rw,relatime,errors=remount-ro,data=ordered)


I see two mount points for every one mount point I expect. Eg:


/var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp

and
/home/chroot/sid64/home/chroot/sid64/tmp

The second one seems wrong.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#681884: Same problem with schroot 1.6.8-1

[Erik de Castro Lopo]

Hi all,

I'm seeing the same problem with schroot 1.6.8-1 but only on one of
the two machines I regularly use schroot on.

On the machine that displays this problem I have a amd64 Sid chroot
called sid64. If I run it using 'schroot -c sid64' and immediately
exit I get:


E: 10mount: umount: 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/tmp: not 
mounted
E: sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a: Chroot setup failed: 
stage=setup-stop

If I then run 'mount | grep sid64' I get

/dev/sda4 on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a type ext4 
(rw,relatime,data=ordered)
proc on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/proc type 
proc (rw,nosuid,nodev,noexec,relatime)
proc on /home/chroot/sid64/proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/sys type 
sysfs (rw,nosuid,nodev,noexec,relatime)
sysfs on /home/chroot/sid64/sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev type 
devtmpfs (rw,relatime,size=10240k,nr_inodes=1006828,mode=755)
udev on /home/chroot/sid64/dev type devtmpfs 
(rw,relatime,size=10240k,nr_inodes=1006828,mode=755)
devpts on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev/pts type 
devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
devpts on /home/chroot/sid64/dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda4 on 
/var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/home type 
ext4 (rw,relatime,data=ordered)
/dev/sda4 on /home/chroot/sid64/home type ext4 (rw,relatime,data=ordered)

Notice that there are two mount points recorded for say dev:

 /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev
/home/chroot/sid64/dev

I expected to see the first but not the second (which seems completely wrong).

On the machine where schroot is working correctly, I never get the 
/home/chroot/$chroot_name/dev
mount.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#713943: Same problem with linux-image-3.12-1-powerpc64

[Erik de Castro Lopo]

Hi,

I run debian testing on a dual G5 powermac.

Just upgraded from linux-image-3.4-trunk-powerpc64 to
linux-image-3.12-1-powerpc64 and found the same issue. The windfarm
modules are loading but the about 30 seconds to a couple of minutes
after booting to 3.12-1-powerpc64 the fans speed up to full speed.

lsmod says the windfarm modules are being loaded, and its the same
modules being loaded under the 3.4 kernel.

I have however found a difference. On 3.12 I get:

 dmesg | grep windfarm 
[4.358299] windfarm: initializing for dual-core desktop G5

whereas on 3.4 I get:

 dmesg | grep windfarm 
[4.791589] windfarm: initializing for dual-core desktop G5
[9.077416] windfarm: CPUs control loops started.
[   12.440957] windfarm: Backside control loop started.
[   12.491701] windfarm: Slots control loop started.
[   12.592933] windfarm: Drive bay control loop started.

Definitely something wonky there.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#713943: Lack of i2c_powermac module may be the cause

[Erik de Castro Lopo]

Hi,

A previosu message in this big suggested that the i2c_powermac module 
may be involved.

I can confirm that this module is missing completely for the 3.12 kernel
(there is no module of that name in the /lib/modules/3.12-1-powerpc64/
tree) whereas for the 3.4 kernel this module is available and is being
auto-loaded.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#713943: Lack of i2c_powermac module may be the cause

[Erik de Castro Lopo]

Erik de Castro Lopo wrote:

 Hi,
 
 A previosu message in this big suggested that the i2c_powermac module 
 may be involved.
 
 I can confirm that this module is missing completely for the 3.12 kernel
 (there is no module of that name in the /lib/modules/3.12-1-powerpc64/
 tree) whereas for the 3.4 kernel this module is available and is being
 auto-loaded.

It seems that the i2c_powermac module from 3.4 is now called i2c-powermac
(underscore replaced with a minux sign).

Manually loading the i2c-powermac module results in fans that run at the
normal. expected low speed. I will be adding this to /etc/modules as a
workaround for this issue.

A question about kernel modules, can one module (eg windfarm_core) be
made to depend on and auto-load another (eg i2c-powermac)?

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#713943: Lack of i2c_powermac module may be the cause

[Erik de Castro Lopo]

Ben Hutchings wrote:

  Manually loading the i2c-powermac module results in fans that run at the
  normal. expected low speed. I will be adding this to /etc/modules as a
  workaround for this issue.
 
 Does it matter whether you load i2c-powermac before or after the
 windfarm modules?

Loading after is fine. I therefore assume that loading before is also
fine.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#713943: Lack of i2c_powermac module may be the cause

[Erik de Castro Lopo]

David Gosselin wrote:

 Are you testing on a PowerMac G5 7,3?  Should be in /proc/cpuinfo.
 I have a 7,3 model and cannot load the windfarm driver.  It appears
 that the hardware on the 7,3 is not supported.  I’ve been working to
 update the therm_pm72 driver to use the probe interface instead of the
 attach_adapter interface.  Maybe you’re hitting this issue?

Nope, seems to be 11,2:


platform: PowerMac
model   : PowerMac11,2
machine : PowerMac11,2
motherboard : PowerMac11,2 MacRISC4 Power Macintosh 
detected as : 337 (PowerMac G5 Dual Core)


Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#614761: Ping

[Erik de Castro Lopo]

Solveig wrote:

 Hi!
 Do you still encounter this bug with latest versions? If yes, please
 provide up-to-date data, and if not, this bug report might be closed, so
 let us know :)

I haven't seen this in some time. It can be closed.

Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#732346: libsndfile: Update config.{sub,guess} for new architectures

[Erik de Castro Lopo]

Thanks Wookey,

I uploaded a new package two days ago, but the upload queue seems to
be busted. I'm hoping the new package will just magically appear
when the queue gets fixed.

Cheers.
Erik
-- 
--
Erik de Castro Lopo
http://www.mega-nerd.com/


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

Bug#728491: Battery power applet is missing

[Erik de Castro Lopo]

Package: gnome-panel
Version: 3.6.2-2
Severity: normal

For as long as I can remember (and definitely in gnome 3.4), gnome has had a 
battery
power applet but this release it is missing.

When running on a laptop, a battery power applet is sessential.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-panel depends on:
ii  gconf-service  3.2.6-1
ii  gnome-icon-theme-symbolic  3.10.1-1
ii  gnome-menus3.8.0-2
ii  gnome-panel-data   3.6.2-2
ii  libatk1.0-02.10.0-2
ii  libc6  2.17-93
ii  libcairo-gobject2  1.12.16-2
ii  libcairo2  1.12.16-2
ii  libcamel-1.2-433.8.5-2
ii  libdconf1  0.18.0-1
ii  libecal-1.2-15 3.8.5-2
ii  libedataserver-1.2-17  3.8.5-2
ii  libgconf-2-4   3.2.6-1
ii  libgdk-pixbuf2.0-0 2.28.2-1
ii  libglib2.0-0   2.36.4-1
ii  libgnome-desktop-3-7   3.8.4-2
ii  libgnome-menu-3-0  3.8.0-2
ii  libgtk-3-0 3.8.6-1
ii  libgweather-3-33.8.2-3
ii  libical0   0.48-2
ii  libice62:1.0.8-2
ii  libnspr4   2:4.10.1-1
ii  libnspr4-0d2:4.10.1-1
ii  libnss32:3.15.2-1
ii  libnss3-1d 2:3.15.2-1
ii  libpanel-applet-4-03.6.2-2
ii  libpango-1.0-0 1.36.0-1
ii  libpangocairo-1.0-01.36.0-1
ii  librsvg2-2 2.40.0-1
ii  libsecret-1-0  0.15-2
ii  libsm6 2:1.2.1-2
ii  libsoup2.4-1   2.44.1-1
ii  libsqlite3-0   3.8.1-1
ii  libtelepathy-glib0 0.22.0-1
ii  libwnck-3-03.4.7-1
ii  libx11-6   2:1.6.2-1
ii  libxau61:1.0.8-1
ii  libxext6   2:1.3.2-1
ii  libxml22.9.1+dfsg1-3
ii  libxrandr2 2:1.4.1-1

Versions of packages gnome-panel recommends:
ii  alacarte 3.10.0-1
ii  evolution-data-server3.8.5-2
ii  gnome-applets3.4.1-4
ii  gnome-control-center 1:3.8.3-3
ii  gnome-icon-theme 3.10.0-1
ii  gnome-session3.8.4-3
ii  gnome-session-flashback  3.6.2-2
ii  gvfs 1.16.3-1+b2

Versions of packages gnome-panel suggests:
ii  gnome-terminal [x-terminal-emulator]  3.10.1-1
ii  gnome-user-guide  3.8.2-1
ii  nautilus  3.8.2-2
ii  xterm [x-terminal-emulator]   297-1
ii  yelp  3.10.1-1

-- no debconf information


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

Bug#726878: Reportbug crashes

[Erik de Castro Lopo]

Package: reportbug
Version: 6.4.4
Severity: normal

For example.

 reportbug gnome-shell
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Erik de Castro Lopo er...@mega-nerd.com' as your from address.
Getting status for gnome-shell...
Checking for newer versions at madison, incoming.debian.org and 
http://ftp-master.debian.org/new.html
Will send report to Debian (per lsb_release).
Querying Debian BTS for reports on gnome-shell (source)...
Traceback (most recent call last):
  File /usr/bin/reportbug, line 2206, in module
main()
  File /usr/bin/reportbug, line 1080, in main
return iface.user_interface()
  File /usr/bin/reportbug, line 1702, in user_interface
latest_first=self.options.latest_first)
  File /usr/lib/pymodules/python2.7/reportbug/ui/text_ui.py, line 517, in 
handle_bts_query
source=source, http_proxy=http_proxy, archived=archived)
  File /usr/lib/pymodules/python2.7/reportbug/debbugs.py, line 1263, in 
get_reports
stats = debianbts.get_status(bugs)
  File /usr/lib/pymodules/python2.7/debianbts.py, line 161, in get_status
reply = server.get_status(*nr)
  File /usr/lib/pymodules/python2.7/SOAPpy/Client.py, line 470, in __call__
return self.__r_call(*args, **kw)
  File /usr/lib/pymodules/python2.7/SOAPpy/Client.py, line 492, in __r_call
self.__hd, self.__ma)
  File /usr/lib/pymodules/python2.7/SOAPpy/Client.py, line 363, in __call
config = self.config)
  File /usr/lib/pymodules/python2.7/SOAPpy/Client.py, line 252, in call
raise HTTPError(code, msg)
SOAPpy.Errors.HTTPError: HTTPError 500 Internal Server Error




-- Package-specific info:
** Environment settings:
EDITOR=gedit
VISUAL=gedit
DEBEMAIL=er...@mega-nerd.com
EMAIL=er...@mega-nerd.com
DEBFULLNAME=Erik de Castro Lopo

** /home/erikd/.reportbugrc:
mode expert

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages reportbug depends on:
ii  apt   0.9.12.1
ii  python2.7.5-5
ii  python-reportbug  6.4.4

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail   none
pn  debconf-utilsnone
pn  debsums  none
pn  dlocate  none
pn  emacs22-bin-common | emacs23-bin-common  none
ii  file 1:5.14-2
ii  gnupg1.4.15-1.1
ii  postfix [mail-transport-agent]   2.10.2-1
ii  python-gtk2  2.24.0-3+b1
pn  python-gtkspell  none
pn  python-urwid none
ii  python-vte   1:0.28.2-5
ii  xdg-utils1.1.0~rc1+git20111210-7

Versions of packages python-reportbug depends on:
ii  apt   0.9.12.1
ii  python2.7.5-5
ii  python-debian 0.1.21+nmu2
ii  python-debianbts  1.11
ii  python-support1.0.15

python-reportbug suggests no packages.

-- no debconf information


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

Bug#726939: Laptop function keys for LCD backlight not working

[Erik de Castro Lopo]

Package: gnome-shell
Version: 3.8.4-4
Severity: normal

This is a regression from gnome-shell 3.4.

On this laptop I could hold down the funtion key and be pressing f2 or f4 I
could dim or brighten the LCD backlight. These kesy now do nothing.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  evolution-data-server3.8.5-2
ii  gdm3 3.8.4-2
ii  gir1.2-accountsservice-1.0   0.6.34-2
ii  gir1.2-caribou-1.0   0.4.12-1
ii  gir1.2-clutter-1.0   1.14.4-3
ii  gir1.2-freedesktop   1.36.0-2+b1
ii  gir1.2-gcr-3 3.8.2-4
ii  gir1.2-gkbd-3.0  3.6.0-1
ii  gir1.2-glib-2.0  1.36.0-2+b1
ii  gir1.2-gmenu-3.0 3.8.0-2
ii  gir1.2-gnomebluetooth-1.03.8.1-2
ii  gir1.2-gnomedesktop-3.0  3.8.4-2
ii  gir1.2-gtk-3.0   3.8.5-1
ii  gir1.2-ibus-1.0  1.5.4-1
ii  gir1.2-mutter-3.03.8.4-2
ii  gir1.2-networkmanager-1.00.9.8.0-5
ii  gir1.2-nmgtk-1.0 0.9.8.4-1
ii  gir1.2-pango-1.0 1.32.5-5+b1
ii  gir1.2-polkit-1.00.105-4
ii  gir1.2-soup-2.4  2.44.1-1
ii  gir1.2-telepathyglib-0.120.22.0-1
ii  gir1.2-telepathylogger-0.2   0.8.0-2
ii  gir1.2-upowerglib-1.00.9.22-1
ii  gjs  1.36.1-2
ii  gnome-bluetooth  3.8.1-2
ii  gnome-icon-theme-symbolic3.8.2.2-2
ii  gnome-settings-daemon3.8.5-2
ii  gnome-shell-common   3.8.4-4
ii  gnome-themes-standard3.8.4-1
ii  gsettings-desktop-schemas3.8.2-2
ii  libatk-bridge2.0-0   2.10.0-1
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-93
ii  libcairo-gobject21.12.16-2
ii  libcairo21.12.16-2
ii  libcamel-1.2-43  3.8.5-2
ii  libcanberra-gtk3-0   0.30-2
ii  libcanberra0 0.30-2
ii  libclutter-1.0-0 1.14.4-3
ii  libcogl-pango12  1.14.0-3
ii  libcogl121.14.0-3
ii  libcroco30.6.8-2
ii  libdbus-1-3  1.6.16-1
ii  libdbus-glib-1-2 0.100.2-1
ii  libecal-1.2-15   3.8.5-2
ii  libedataserver-1.2-173.8.5-2
ii  libegl1-mesa [libegl1-x11]   9.1.7-1
ii  libgck-1-0   3.8.2-4
ii  libgcr-base-3-1  3.8.2-4
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libgirepository-1.0-11.36.0-2+b1
ii  libgjs0c [libgjs0-libmozjs185-1.0]   1.36.1-2
ii  libglib2.0-0 2.36.4-1
ii  libgnome-menu-3-03.8.0-2
ii  libgstreamer1.0-01.2.0-1
ii  libgtk-3-0   3.8.5-1
ii  libical0 0.48-2
ii  libjson-glib-1.0-0   0.16.2-1
ii  libmozjs185-1.0  1.8.5-1.0.0+dfsg-4+b1
ii  libmutter0b  3.8.4-2
ii  libnm-glib4  0.9.8.0-5
ii  libnm-gtk0   0.9.8.4-1
ii  libnm-util2  0.9.8.0-5
ii  libnspr4 2:4.10-1
ii  libnspr4-0d  2:4.10-1
ii  libnss3  2:3.15.1-1
ii  libnss3-1d   2:3.15.1-1
ii  libp11-kit0  0.18.5-3
ii  libpango-1.0-0   1.32.5-5+b1
ii  libpangocairo-1.0-0  1.32.5-5+b1
ii  libpolkit-agent-1-0  0.105-4
ii  libpolkit-gobject-1-00.105-4
ii  libpulse-mainloop-glib0  4.0-6+b1
ii  libpulse0