Bug#944461: [Pkg-utopia-maintainers] Bug#944461: upower: segfaults when trying to communicate with usbmuxd when iPhone is plugged in

[Lorenz Hübschle-Schneider]

Thanks Michael, I missed that.

#944236 (upower: stack smashing detected) and #941703 (libimobiledevice6: 
Crashes upower with stack smashing when connecting an iPhone) also appear to be 
the same issue, but I see that's been noted already. I guess they can all be 
merged into one.

As far as I can tell the source of the problem is a SONAME tracking issue in 
libusbmuxd: https://github.com/libimobiledevice/libusbmuxd/issues/81 which 
breaks something in libimobiledevice which then causes upower to crash.

Cheers,
Lorenz

On Sun, 10 Nov 2019, at 15:34, Michael Biebl wrote:
> Am 10.11.19 um 13:15 schrieb Lorenz:
> > Package: upower
> > Version: 0.99.11-1
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > when I have my (locked) iPhone plugged into my laptop, upower reproducibly
> > segfaults after five seconds. It is then automatically restarted by systemd,
> > but crashes again five seconds later. gdb was unable to produce a traceback 
> > for
> > the crashing thread, but strace produces:
> > 
> 
> Sounds like a duplicate of #941833
> 
> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 
> 
> Attachments:
> * signature.asc

Bug#872468: bug persists with version 1.184

[Lorenz Hübschle-Schneider]

Hello,

this bug still exists in console-setup version 1.184.

It also makes 'update-initramfs' very noisy, as 'setupcon --save-keyboard 
$destination' prints the same 976 lines for each installed kernel version.

Cheers,
Lorenz

Bug#895224: pdfpc movie playback with gstreamer 1.14.0

[Lorenz Hübschle-Schneider]

Thanks! I'm not very familiar with Debian policy, so I can't really comment on 
what kind of a dependency it should be. But it does seem inconsistent to have a 
"Depends: libgstreamer1.0-0 "but "Recommends: gstreamer1.0-gtk3", given that 
both are required to play video.

Bug#895224: pdfpc movie playback with gstreamer 1.14.0

[Lorenz Hübschle-Schneider]

Do you have the package gstreamer1.0-gtk3 installed? This fixes movie playback 
for me. It seems like pdfpc should at least have a 'Recommends' dependency on 
it.

You can increase the verbosity of gstreamer in pdfpc by setting the GST_DEBUG 
environment variable to, e.g., 4.

Cheers,
Lorenz

Bug#872536: suckless-tools: dmenu fails to capture the keyboard from wayland windows

[Lorenz Hübschle-Schneider]

Thank you Ilias. It does seem like using an alternative implementation
on (X)Wayland is best for now. It's unfortunate that supporting Wayland
seems to be quite a lot of work. Due to a bunch of other
incompatibilities I disabled Wayland on my systems for now. Should I
leave this issue open for others or would you rather close it?

Cheers,
Lorenz

Bug#872536: suckless-tools: dmenu fails to capture the keyboard from wayland windows

[Lorenz Hübschle-Schneider]

Package: suckless-tools
Version: 43-1
Severity: important

Dear Maintainer,

since gnome-session 3.24.1-2 was uploaded to testing, Gnome uses wayland by
default. However, dmenu fails to capture the keyboard when a wayland window
(e.g. gnome-terminal) is in the foreground. It works fine when an X11
(Xwayland) window (e.g. chromium) is active. Are there any plans to support
wayland?

Cheers,
Lorenz



-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages suckless-tools depends on:
ii  libc6   2.24-14
ii  libcap2-bin 1:2.25-1
ii  libfontconfig1  2.12.3-0.2
ii  libpam0g1.1.8-3.6
ii  libx11-62:1.6.4-3
ii  libxft2 2.3.2-1+b2
ii  libxinerama12:1.1.3-1+b3
ii  libxrandr2  2:1.5.1-1
ii  libxss1 1:1.2.2-1+b2

suckless-tools recommends no packages.

Versions of packages suckless-tools suggests:
pn  dwm 
pn  stterm  
pn  surf

-- no debconf information

Bug#858261: gcc-6: "internal compiler error: Segmentation fault" when building webkit2gtk

[Lorenz Hübschle-Schneider]

Package: g++-6
Version: 6.3.0-9
Followup-For: Bug #858261

Dear Maintainer,

I get a similar failure when compiling RaftLib [1]. I'm not entirely sure it's
the same bug but it appeared with the last update (6.3.0-9) so it might well be.

Steps to reproduce:
git clone https://github.com/RaftLib/RaftLib
cd RaftLib
mkdir build
cd build
cmake ..
make

This fails with:

In file included from /tmp/RaftLib/raftinc/ringbufferheap.tcc:25:0,
 from /tmp/RaftLib/raftinc/ringbufferbase.tcc:66,
 from /tmp/RaftLib/raftinc/ringbuffer.tcc:34,
 from /tmp/RaftLib/raftinc/port.hpp:37,
 from /tmp/RaftLib/raftinc/kernel.hpp:29,
 from /tmp/RaftLib/raftinc/allocate.hpp:29,
 from /tmp/RaftLib/src/allocate.cpp:25:
/tmp/RaftLib/raftinc/ringbufferheap_abstract.tcc: In lambda function:
/tmp/RaftLib/raftinc/ringbufferheap_abstract.tcc:371:64: internal compiler 
error: Segmentation fault
 local_insert_helper( *begin, *end, sig );
^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
src/CMakeFiles/raft.dir/build.make:86: recipe for target 
'src/CMakeFiles/raft.dir/allocate.cpp.o' failed

Didn't get a coredump despite them being enabled, but don't have time to figure
out what's going on with that right now, sorry.

Cheers,
Lorenz

[1] https://github.com/RaftLib/RaftLib

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages g++-6 depends on:
ii  gcc-66.3.0-9
ii  gcc-6-base   6.3.0-9
ii  libc62.24-9
ii  libgmp10 2:6.1.2+dfsg-1
ii  libisl15 0.18-1
ii  libmpc3  1.0.3-1+b2
ii  libmpfr4 3.1.5-1
ii  libstdc++-6-dev  6.3.0-9
ii  zlib1g   1:1.2.8.dfsg-5

g++-6 recommends no packages.

Versions of packages g++-6 suggests:
ii  g++-6-multilib6.3.0-9
pn  gcc-6-doc 
ii  libstdc++6-6-dbg  6.3.0-9

-- no debconf information

Bug#819333: [llvm-3.8-dev] LLVMgold.so is missing, so "clang -flto" is unusable

[Lorenz Hübschle-Schneider]

Awesome - thank you very much! I must confess that I'm not very
proficient in Debian packaging and the package build process. I'll have
to change that some day ;)

Best,
Lorenz

On Mon, 8 Aug 2016, at 18:40, Sylvestre Ledru wrote:
> I think I found the fix. So, don't bother :)
> 
> Le 08/08/2016 à 17:10, Sylvestre Ledru a écrit :
> > I will have a look but don't hesitate to provide a patch to make
> > things moving faster
> >
> > Le 08/08/2016 à 16:41, Lorenz Hübschle-Schneider a écrit :
> >> Dear maintainer,
> >>
> >> this issue is still present in version 1:3.8.1-8. According to
> >> http://llvm.org/docs/GoldPlugin.html the fix should be quite simple. I'd
> >> really appreciate it if you could bring back LLVMgold.so in 3.8.
> >>
> >> Best,
> >> Lorenz
> >>
> >> On Sat, 26 Mar 2016 23:10:18 +0100 Steffen Weinhart
> >> <stw...@blue-cable.de> wrote:
> >>> Package: llvm-3.8-dev
> >>> Version: 1:3.8-2
> >>> Severity: important
> >>>
> >>> In versions prior to 3.8 (final), there was LLVMgold.so, which was used
> >>> e.g. when clang was invoked with "-flto". When using clang-3.8 with
> >>> "-flto" now, the linker cannot find the library and aborts. Why has it
> >>> been removed? Or at least what package should I install then? "apt-file
> >>> search LLVMgold.so" only finds entries in older llvm-3.*-dev packages.
> >>>
> >>> --- System information. ---
> >>> Architecture: amd64
> >>> Kernel: Linux 4.4.6
> >>>
> >>> Debian Release: stretch/sid
> >>> 900 testing security.debian.org
> >>> 900 testing ftp.deb-multimedia.org
> >>> 900 testing ftp.de.debian.org
> >>> 500 testing-updates ftp.de.debian.org
> >>> 500 testing-proposed-updates ftp.de.debian.org
> >>> 500 stable-updates ftp.de.debian.org
> >>> 500 stable security.debian.org
> >>> 500 stable ftp.de.debian.org
> >>> 500 proposed-updates ftp.de.debian.org
> >>> 50 unstable ftp.deb-multimedia.org
> >>> 50 unstable ftp.de.debian.org
> >>> 100 jessie-backports ftp.de.debian.org
> >>> 1 experimental ftp.de.debian.org
> >>>
> >>> --- Package information. ---
> >>> Package's Depends field is empty.
> >>>
> >>> Package's Recommends field is empty.
> >>>
> >>> Package's Suggests field is empty.
> >>>
> >>>
> >>
> >> ___
> >> Pkg-llvm-team mailing list
> >> pkg-llvm-t...@lists.alioth.debian.org
> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-llvm-team
> >>
> >
> > ___
> > Pkg-llvm-team mailing list
> > pkg-llvm-t...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-llvm-team
> 
> 

Bug#819333: [llvm-3.8-dev] LLVMgold.so is missing, so "clang -flto" is unusable

[Lorenz Hübschle-Schneider]

Dear maintainer,

this issue is still present in version 1:3.8.1-8. According to
http://llvm.org/docs/GoldPlugin.html the fix should be quite simple. I'd
really appreciate it if you could bring back LLVMgold.so in 3.8.

Best,
Lorenz

On Sat, 26 Mar 2016 23:10:18 +0100 Steffen Weinhart
 wrote:
> Package: llvm-3.8-dev
> Version: 1:3.8-2
> Severity: important
> 
> In versions prior to 3.8 (final), there was LLVMgold.so, which was used 
> e.g. when clang was invoked with "-flto". When using clang-3.8 with 
> "-flto" now, the linker cannot find the library and aborts. Why has it 
> been removed? Or at least what package should I install then? "apt-file 
> search LLVMgold.so" only finds entries in older llvm-3.*-dev packages.
> 
> --- System information. ---
> Architecture: amd64
> Kernel: Linux 4.4.6
> 
> Debian Release: stretch/sid
> 900 testing security.debian.org
> 900 testing ftp.deb-multimedia.org
> 900 testing ftp.de.debian.org
> 500 testing-updates ftp.de.debian.org
> 500 testing-proposed-updates ftp.de.debian.org
> 500 stable-updates ftp.de.debian.org
> 500 stable security.debian.org
> 500 stable ftp.de.debian.org
> 500 proposed-updates ftp.de.debian.org
> 50 unstable ftp.deb-multimedia.org
> 50 unstable ftp.de.debian.org
> 100 jessie-backports ftp.de.debian.org
> 1 experimental ftp.de.debian.org
> 
> --- Package information. ---
> Package's Depends field is empty.
> 
> Package's Recommends field is empty.
> 
> Package's Suggests field is empty.
> 
> 

Bug#792519: systemd-logind fails to start on system using LDAP

[Lorenz Hübschle-Schneider]

Dear all,

I get similar symptoms (but no boot failures, just unnecessarily slow
boot times) with current unstable (systemd 231-1, dbus 1.10.8-1,
libnss-ldap 265-3+b1) using systemd-networkd instead of NetworkManager.

Loads of
> dbus-daemon[2395]: nss_ldap: could not connect to any LDAP server as (null) - 
> Can't contact LDAP server
in the logs until at some point networkd connects.

I suspect that the network may only be brought up at that point because
of an NFS automount that is triggered:
> systemd[1]: home.automount: Got automount request for /home, triggered by 
> 2458 (mount)
> systemd[1]: Starting Wait for Network to be Configured...

 After that request there are some more failures (this time from nscd
 instead of dbus) until the network is actually connected.

I have nss_initgroups_ignoreusers set up for all system users and
'bind_policy soft' in /etc/ldap.conf

Anything I can do to help fix this?

Best,
Lorenz

On Sun, 19 Jul 2015 15:03:53 -0300 Felipe Sateler 
wrote:
> On 17 July 2015 at 18:44, Daniel Schepler  wrote:
> > On Wed, Jul 15, 2015 at 12:30 PM, Felipe Sateler 
> > wrote:
> >>
> >> On 15 July 2015 at 16:09, Daniel Schepler  wrote:
> >> > On Wed, Jul 15, 2015 at 11:48 AM, Felipe Sateler 
> >> > wrote:
> >> >>
> >> >> Hmm. Could you please attach the upgrade logs since some time before
> >> >> the problems occurred?  Might network manager have been updated in the
> >> >> meantime?
> >> >
> >> >
> >> > Attaching /var/log/dpkg.log.  I think the first failed boot was
> >> > 2015-07-08
> >> > or 2015-07-09.  From the previous history, the last upgrade of dbus was:
> >> >
> >> > 2015-05-20 09:46:36 upgrade dbus:amd64 1.8.16-1 1.8.18-1
> >> >
> >> >>
> >> >> Also, how do you manage your connections?
> >> >>
> >> >> I also found this old redhat bug[1]. Could you try adding a conf
> >> >> snippet to order the ldap components before dbus? Use systemctl edit
> >> >>  and add Before=dbus.service.
> >> >>
> >> >>
> >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=502072
> >> >
> >> >
> >> > OK, it will be a while before I can test it because I'm doing work using
> >> > the
> >> > machine right now.
> >> >
> >> > It would appear to me from the logs that NetworkManager can't
> >> > successfully
> >> > start before dbus is available - and I would probably want to make nslcd
> >> > dependent on networking being up.  Would that mean that I'd have to set
> >> > things up so it manually connects eth0 over DHCP, then starts nslcd,
> >> > then
> >> > starts dbus?  And then NetworkManager would be left only managing wlan0?
> >> > And if so, where would I look for documentation on setting up the unit
> >> > to
> >> > connect eth0?  (Sorry for the last very basic question.)
> >>
> >> I think (but I'm not sure) that nm will still connect without dbus
> >> available yet, but it will of course not answer any dbus requests. So
> >> it should only be necessary to order ldap before dbus.
> >>
> >> However, this solution may prove brittle. Reading the linked redhat
> >> bug there are two promsing suggestions:
> >>
> >> 1. Add 'bind_policy soft' to /etc/ldap.conf.
> >> 2. Set nss_initgroups_ignoreusers to at least
> >> 'root,dirsrv,gdm,rtkit,pulse,haldaemon,polkituser,avahi,dbus'
> >>
> >> It seems the problem is that nss_ldap is trying to query ldap for
> >> system users. That seems wrong to me, as the system should be able to
> >> work without network.
> >

Bug#815666: Xwayland crash

[Lorenz Hübschle-Schneider]

Yes, it's fixed. Thanks a lot.

Lorenz

Bug#815666: Duplicate of #814982

[Lorenz Hübschle-Schneider]

Yes, that certainly seems possible as I mentioned in my initial
report. However, I can exclude the possibility of it being a duplicate
of #813687 after the upgrade to mutter 3.18.3.

Bug#815666: xwayland: crashes when turning on screens after waking up from lockscreen

[Lorenz Hübschle-Schneider]

Still reproducible but the log messages changed:

> Mar 01 11:53:03 i10pc82 kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: ELD buf 
> size is 0, force 128
> Mar 01 11:53:03 i10pc82 kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid 
> ELD data byte 0
> Mar 01 11:53:03 i10pc82 /usr/lib/gdm3/gdm-x-session[977]: (II) intel(0): 
> resizing framebuffer to 1920x1080
> Mar 01 11:53:03 i10pc82 gnome-session[830]: (gnome-shell:838): Gdk-ERROR **: 
> The program 'gnome-shell' received an X Window System error.
> Mar 01 11:53:03 i10pc82 gnome-session[830]: This probably reflects a bug in 
> the program.
> Mar 01 11:53:03 i10pc82 gnome-session[830]: The error was 'BadRROutput 
> (invalid Output parameter)'.
> Mar 01 11:53:03 i10pc82 gnome-session[830]:   (Details: serial 583 error_code 
> 147 request_code 140 (RANDR) minor_code 9)
> Mar 01 11:53:03 i10pc82 gnome-session[830]:   (Note to programmers: normally, 
> X errors are reported asynchronously;
> Mar 01 11:53:03 i10pc82 gnome-session[830]:that is, you will receive the 
> error a while after causing it.
> Mar 01 11:53:03 i10pc82 gnome-session[830]:To debug your program, run it 
> with the GDK_SYNCHRONIZE environment
> Mar 01 11:53:03 i10pc82 gnome-session[830]:variable to change this 
> behavior. You can then get a meaningful
> Mar 01 11:53:03 i10pc82 gnome-session[830]:backtrace from your debugger 
> if you break on the gdk_x_error() function.)
> Mar 01 11:53:03 i10pc82 gnome-session[830]: (gnome-settings-daemon:931): 
> Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System 
> error.
> Mar 01 11:53:03 i10pc82 gnome-session[830]: This probably reflects a bug in 
> the program.
> Mar 01 11:53:03 i10pc82 gnome-session[830]: The error was 'BadRROutput 
> (invalid Output parameter)'.
> Mar 01 11:53:03 i10pc82 gnome-session[830]:   (Details: serial 254 error_code 
> 147 request_code 140 (RANDR) minor_code 9)
> Mar 01 11:53:03 i10pc82 gnome-session[830]:   (Note to programmers: normally, 
> X errors are reported asynchronously;
> Mar 01 11:53:03 i10pc82 gnome-session[830]:that is, you will receive the 
> error a while after causing it.
> Mar 01 11:53:03 i10pc82 gnome-session[830]:To debug your program, run it 
> with the GDK_SYNCHRONIZE environment
> Mar 01 11:53:03 i10pc82 gnome-session[830]:variable to change this 
> behavior. You can then get a meaningful
> Mar 01 11:53:03 i10pc82 gnome-session[830]:backtrace from your debugger 
> if you break on the gdk_x_error() function.)
> Mar 01 11:53:03 i10pc82 kernel: traps: gnome-shell[838] trap int3 
> ip:7f147107687b sp:7ffd656e3ba0 error:0
> Mar 01 11:53:03 i10pc82 kernel: traps: gnome-settings-[931] trap int3 
> ip:7fc335ea387b sp:7ffcbdf3bae0 error:0
> Mar 01 11:53:03 i10pc82 gnome-session[830]: gnome-session-binary[830]: 
> WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 5
> Mar 01 11:53:03 i10pc82 gnome-session-binary[830]: WARNING: Application 
> 'gnome-settings-daemon.desktop' killed by signal 5
> Mar 01 11:53:03 i10pc82 kernel: gnome-settings-[8696]: segfault at 10 ip 
> 7fc9a07fc427 sp 7ffc11076a50 error 4 in 
> libgdk-3.so.0.1800.8[7fc9a079c000+c7000]
> Mar 01 11:53:03 i10pc82 gnome-session[830]: gnome-session-binary[830]: 
> WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 11
> Mar 01 11:53:03 i10pc82 gnome-session-binary[830]: WARNING: Application 
> 'gnome-settings-daemon.desktop' killed by signal 11
> Mar 01 11:53:03 i10pc82 gnome-session[989]: (gnome-settings-daemon:1069): 
> color-plugin-WARNING **: failed to connect to device: Failed to connect to 
> missing device 
> /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PL2480H_11183M4502551_Debian_gdm_114
> Mar 01 11:53:03 i10pc82 gnome-session[989]: (gnome-settings-daemon:1069): 
> color-plugin-WARNING **: failed to connect to device: Failed to connect to 
> missing device 
> /org/freedesktop/ColorManager/devices/xrandr_Iiyama_North_America_PL2480H_11183M4502550_Debian_gdm_114
> Mar 01 11:53:03 i10pc82 gnome-session[830]: (EE)
> Mar 01 11:53:03 i10pc82 gnome-session[830]: Fatal server error:
> Mar 01 11:53:03 i10pc82 gnome-session[830]: (EE) failed to dispatch Wayland 
> events: Broken pipe
> Mar 01 11:53:03 i10pc82 gnome-session[830]: (EE)
> Mar 01 11:53:03 i10pc82 polkitd(authority=local)[739]: Unregistered 
> Authentication Agent for unix-session:c1 (system bus name :1.13, object path 
> /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) 
> (disconnected from bus)
> Mar 01 11:53:03 i10pc82 gnome-session-binary[830]: Unrecoverable failure in 
> required component gnome-shell-wayland.desktop
> Mar 01 11:53:03 i10pc82 /usr/lib/gdm3/gdm-wayland-session[827]: Activating 
> service name='ca.desrt.dconf'
> Mar 01 11:53:03 i10pc82 gdm-launch-environment][815]: 
> pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
> Mar 01 11:53:03 i10pc82 /usr/lib/gdm3/gdm-x-session[977]: (II) 
> systemd-logind: 

Bug#816080: [wajig] Segfault on wajig show command for some packages.

[Lorenz Hübschle-Schneider]

Sounds like a duplicate of #815581 (fixed / pending) to me

Cheers
Lorenz

Bug#815666: xwayland: crashes when turning on screens after waking up from lockscreen

[Lorenz Hübschle-Schneider]

Attached is the output of gdb "thread apply all bt full" for
gnome-shell, both the grandchild process of gdm-x-session and
gdm-wayland-session. The parent in both cases is gnome-session-binary,
and gnome-session is invoked without flags/parameters (X) or
"--mode=gdm --wayland --display-server" (wayland). Maybe these can be
of help?

Cheers
Lorenz

On Tue, Feb 23, 2016 at 2:35 PM, Lorenz Hübschle-Schneider
<lorenz-...@lgh-alumni.de> wrote:
> Package: xwayland
> Version: 2:1.18.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> since today my machine is no longer lockable, as Xwayland segfaults upon 
> waking
> up whenever I lock the screen for more than a few seconds.  The precise
> criterion for the crash happening or not is the monitors powering down. The
> segfault occurs when the monitors power up again.  This renders my system
> unlockable as gnome-session now uses Xwayland by default.
>
> >From the journal:
>
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Backtrace:
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 0: /usr/bin/Xwayland 
> (xorg_backtrace+0x4e) [0x55e3df37cb0e]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 1: /usr/bin/Xwayland 
> (0x55e3df1e2000+0x19ee99) [0x55e3df380e99]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 2: 
> /lib/x86_64-linux-gnu/libc.so.6 (0x7ff802838000+0x33590) [0x7ff80286b590]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 3: /usr/bin/Xwayland 
> (MakeAtom+0x30) [0x55e3df3352f0]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 4: /usr/bin/Xwayland 
> (0x55e3df1e2000+0xe7cd8) [0x55e3df2c9cd8]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 5: /usr/bin/Xwayland 
> (0x55e3df1e2000+0xe8739) [0x55e3df2ca739]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 6: /usr/bin/Xwayland 
> (0x55e3df1e2000+0xe8d5b) [0x55e3df2cad5b]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 7: /usr/bin/Xwayland 
> (0x55e3df1e2000+0x164dcf) [0x55e3df346dcf]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 8: /usr/bin/Xwayland 
> (0x55e3df1e2000+0x168de3) [0x55e3df34ade3]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 9: 
> /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7ff802858870]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 10: /usr/bin/Xwayland 
> (_start+0x29) [0x55e3df21b019]
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Segmentation fault at 
> address 0x0
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
> Feb 23 13:47:45 i10pc82 gnome-session[836]: Fatal server error:
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Caught signal 11 
> (Segmentation fault). Server aborting
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (gnome-settings-daemon:920): 
> Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource 
> temporarily unavailable) on X server :1024.
> Feb 23 13:47:45 i10pc82 org.a11y.atspi.Registry[889]: XIO:  fatal IO error 11 
> (Resource temporarily unavailable) on X server ":1024"
> Feb 23 13:47:45 i10pc82 org.a11y.atspi.Registry[889]:   after 21 requests 
> (21 known processed) with 0 events remaining.
> Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: WARNING: App 
> 'gnome-settings-daemon.desktop' exited with code 1
> Feb 23 13:47:45 i10pc82 gnome-session[836]: gnome-session-binary[836]: 
> WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
> Feb 23 13:47:45 i10pc82 gnome-session[836]: (gnome-shell:844): mutter-ERROR 
> **: Connection to xwayland lost
> Feb 23 13:47:45 i10pc82 kernel: traps: gnome-shell[844] trap int3 
> ip:7fc30b86287b sp:7ffc0fa3af30 error:0
> Feb 23 13:47:45 i10pc82 gnome-session[836]: ** (gnome-settings-daemon:995): 
> WARNING **: Unable to initialize GTK+
> Feb 23 13:47:45 i10pc82 gnome-session[836]: gnome-session-binary[836]: 
> WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
> Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: WARNING: App 
> 'gnome-settings-daemon.desktop' exited with code 1
> Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: Unrecoverable failure in 
> required component gnome-shell-wayland.desktop
>
> I'm not sure if this should be filed against gnome-session, gnome-shell or 
> some
> other package but since the segmentation fault is occurring in Xwayland I
> decided to file the issue here.
>
> The issue also looks very similar to #814982, but seems to be triggered by
> some other update since it never occurred before today, and now it is 100%
> reproducible.  Package changes since last confirmed working state, from
> /var/log/aptitude, are listed below.
>

Bug#815666: xwayland: crashes when turning on screens after waking up from lockscreen

[Lorenz Hübschle-Schneider]

Package: xwayland
Version: 2:1.18.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

since today my machine is no longer lockable, as Xwayland segfaults upon waking
up whenever I lock the screen for more than a few seconds.  The precise
criterion for the crash happening or not is the monitors powering down. The
segfault occurs when the monitors power up again.  This renders my system
unlockable as gnome-session now uses Xwayland by default.

>From the journal:

Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Backtrace:
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 0: /usr/bin/Xwayland 
(xorg_backtrace+0x4e) [0x55e3df37cb0e]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 1: /usr/bin/Xwayland 
(0x55e3df1e2000+0x19ee99) [0x55e3df380e99]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 2: 
/lib/x86_64-linux-gnu/libc.so.6 (0x7ff802838000+0x33590) [0x7ff80286b590]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 3: /usr/bin/Xwayland 
(MakeAtom+0x30) [0x55e3df3352f0]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 4: /usr/bin/Xwayland 
(0x55e3df1e2000+0xe7cd8) [0x55e3df2c9cd8]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 5: /usr/bin/Xwayland 
(0x55e3df1e2000+0xe8739) [0x55e3df2ca739]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 6: /usr/bin/Xwayland 
(0x55e3df1e2000+0xe8d5b) [0x55e3df2cad5b]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 7: /usr/bin/Xwayland 
(0x55e3df1e2000+0x164dcf) [0x55e3df346dcf]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 8: /usr/bin/Xwayland 
(0x55e3df1e2000+0x168de3) [0x55e3df34ade3]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 9: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7ff802858870]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) 10: /usr/bin/Xwayland 
(_start+0x29) [0x55e3df21b019]
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Segmentation fault at address 
0x0
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
Feb 23 13:47:45 i10pc82 gnome-session[836]: Fatal server error:
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE) Caught signal 11 (Segmentation 
fault). Server aborting
Feb 23 13:47:45 i10pc82 gnome-session[836]: (EE)
Feb 23 13:47:45 i10pc82 gnome-session[836]: (gnome-settings-daemon:920): 
Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :1024.
Feb 23 13:47:45 i10pc82 org.a11y.atspi.Registry[889]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
Feb 23 13:47:45 i10pc82 org.a11y.atspi.Registry[889]:   after 21 requests 
(21 known processed) with 0 events remaining.
Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: WARNING: App 
'gnome-settings-daemon.desktop' exited with code 1
Feb 23 13:47:45 i10pc82 gnome-session[836]: gnome-session-binary[836]: WARNING: 
App 'gnome-settings-daemon.desktop' exited with code 1
Feb 23 13:47:45 i10pc82 gnome-session[836]: (gnome-shell:844): mutter-ERROR **: 
Connection to xwayland lost
Feb 23 13:47:45 i10pc82 kernel: traps: gnome-shell[844] trap int3 
ip:7fc30b86287b sp:7ffc0fa3af30 error:0
Feb 23 13:47:45 i10pc82 gnome-session[836]: ** (gnome-settings-daemon:995): 
WARNING **: Unable to initialize GTK+
Feb 23 13:47:45 i10pc82 gnome-session[836]: gnome-session-binary[836]: WARNING: 
App 'gnome-settings-daemon.desktop' exited with code 1
Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: WARNING: App 
'gnome-settings-daemon.desktop' exited with code 1
Feb 23 13:47:45 i10pc82 gnome-session-binary[836]: Unrecoverable failure in 
required component gnome-shell-wayland.desktop

I'm not sure if this should be filed against gnome-session, gnome-shell or some
other package but since the segmentation fault is occurring in Xwayland I
decided to file the issue here.

The issue also looks very similar to #814982, but seems to be triggered by
some other update since it never occurred before today, and now it is 100%
reproducible.  Package changes since last confirmed working state, from
/var/log/aptitude, are listed below.

Thanks a lot in advance

Cheers
Lorenz

Aptitude 0.7.5: log report
Mon, Feb 22 2016 17:41:48 +0100

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 263 packages, and remove 3 packages.
220 MB of disk space will be used

[REMOVE, NOT USED] libquvi-scripts:amd64 0.4.21-2
[REMOVE, NOT USED] libquvi7:amd64 0.4.1-3
[REMOVE, NOT USED] linux-perf-4.3:amd64 4.3.1-2
[INSTALL, DEPENDENCIES] linux-headers-4.4.0-1-amd64:amd64 4.4.2-3
[INSTALL, DEPENDENCIES] linux-headers-4.4.0-1-common:amd64 4.4.2-3
[INSTALL, DEPENDENCIES] linux-image-4.4.0-1-amd64:amd64 4.4.2-3
[INSTALL, DEPENDENCIES] linux-kbuild-4.4:i386 4.4-4
[INSTALL, DEPENDENCIES] linux-perf-4.4:amd64 4.4-4
[UPGRADE] afl:amd64 1.96b-1 -> 1.96b-2
[UPGRADE] afl-clang:amd64 1.96b-1 -> 1.96b-2
[UPGRADE] aptitude:amd64 

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

[Lorenz Hübschle-Schneider]

Well... using a regular mount doesn't work after all, as that results
in an ordering cycle:

Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found ordering
cycle on remote-fs.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on home.mount/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on network-online.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on systemd-networkd-wait-online.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on systemd-networkd.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on dbus.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on sysinit.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on console-setup.service/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Found dependency
on remote-fs.target/start
Nov 20 09:35:48 i10pc82 systemd[1]: remote-fs.target: Breaking
ordering cycle by deleting job home.mount/start
Nov 20 09:35:48 i10pc82 systemd[1]: home.mount: Job home.mount/start
deleted to break ordering cycle starting with remote-fs.target/start


...maybe that was the reason I was using the automount?

Lorenz

On Thu, Nov 19, 2015 at 4:33 PM, Lorenz Hübschle-Schneider
<lorenz-...@lgh-alumni.de> wrote:
> Hello,
>
> On Thu, Nov 19, 2015 at 4:07 PM, Michael Biebl <bi...@debian.org> wrote:
>> I just realized, that you use systemd-networkd and
>> systemd-networkd-wait-online. With that setup I do indeed run into a
>> real dead-lock.
>
> Yes, I use systemd-networkd because it's perfectly adequate for my use
> case and I have a (perhaps unfounded) dislike for network manager.
> This is a desktop machine sitting in an office.
>
> I think I activated systemd-networkd-wait-online because otherwise
> LDAP authentication got very confused.
>
> After trying out the options I mentioned earlier, I observed the following:
> - Changing Q/q to v in tmpfiles.d/home.conf fixes the issue completely
> - Using a regular mount instead of an automount for /home fixes the
> issue completely
> - Without any configuration changes, the request does not time out (as
> Michael mentioned above). I waited for 11 minutes, after which I had
> caught up with my twitter stream and aborted the experiment ;)
>
> I ended up using a regular mount for /home now since the automount
> doesn't make any sense any more anyway (it was part of a semi-working
> hack to bind-mount a local dir into the remote mount, which was
> dependent on the right unit being killed when resolving the resulting
> ordering cycle, i.e., the machine booted 9/10 times and I had to
> manually fix mounts the other 10% of the time). Since that's now
> successfully worked around with /etc/rc.local, I don't need the
> automount any more.
>
> Thank you for your help!
>
> Lorenz

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

[Lorenz Hübschle-Schneider]

Hello,

On Thu, Nov 19, 2015 at 4:07 PM, Michael Biebl  wrote:
> I just realized, that you use systemd-networkd and
> systemd-networkd-wait-online. With that setup I do indeed run into a
> real dead-lock.

Yes, I use systemd-networkd because it's perfectly adequate for my use
case and I have a (perhaps unfounded) dislike for network manager.
This is a desktop machine sitting in an office.

I think I activated systemd-networkd-wait-online because otherwise
LDAP authentication got very confused.

After trying out the options I mentioned earlier, I observed the following:
- Changing Q/q to v in tmpfiles.d/home.conf fixes the issue completely
- Using a regular mount instead of an automount for /home fixes the
issue completely
- Without any configuration changes, the request does not time out (as
Michael mentioned above). I waited for 11 minutes, after which I had
caught up with my twitter stream and aborted the experiment ;)

I ended up using a regular mount for /home now since the automount
doesn't make any sense any more anyway (it was part of a semi-working
hack to bind-mount a local dir into the remote mount, which was
dependent on the right unit being killed when resolving the resulting
ordering cycle, i.e., the machine booted 9/10 times and I had to
manually fix mounts the other 10% of the time). Since that's now
successfully worked around with /etc/rc.local, I don't need the
automount any more.

Thank you for your help!

Lorenz

Bug#805553: systemd 228-1 fails to boot: hangs in Create Volatile Files and Directories

[Lorenz Hübschle-Schneider]

I will try re-upgrading later this afternoon and let it run for a longer
time, but the message was "$x sec / no limit".

Felipe, are you referring to /usr/lib/tmpfiles.d/home.conf? I will try that
out as well.

With a normal mount I previously had cyclic dependency issues, as I want to
bind-mount a local directory into that. It seems that this is wholly
unsupported by systemd and I couldn't get it to work reliably, so now the
bind mount is in /etc/rc.local as an ugly workaround. I can try making
/home a normal mount again, but given that the issue seems to be a lack of
network access, I don't see how that would succeed. I'll try to be sure
though.

Cheers,
Lorenz

On Thu, Nov 19, 2015 at 2:40 PM, Michael Biebl <bi...@debian.org> wrote:

> Am 19.11.2015 um 14:29 schrieb Felipe Sateler:
> > Control: tags -1 moreinfo
> >
> > On 19 November 2015 at 09:59, Lorenz Hübschle-Schneider
> > <lorenz-...@lgh-alumni.de> wrote:
> >> Package: systemd
> >> Version: 228-1
> >> Severity: critical
> >> Justification: breaks the whole system
> >>
> >> Dear Maintainer,
> >>
> >> after the upgrade to systemd 228-1, my system failed to boot. It got
> stuck in "Create Volatile Files and Directories...", which I cancelled
> after a good minute. I had to downgrade systemd and related packages (udev,
> etc) to be able to boot again.
> >>
>
> >> I set the severity to critical as this seems to render systems
> unbootable if /home is a network filesystem. I hope that's not too drastic.
> >
> > My guess is that the automount part is part of the problem here. If
> > so, we should lower severity.
>
> It would also be interesting to at least let systemd-tmpfiles run for 90
> secs.
> It might eventually time out and the boot continues.
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#794475: clang-3.6: clang segfaults on invalid use of non-static data member

[Lorenz Hübschle-Schneider]

Package: clang-3.6
Version: 1:3.6.2~+rc1-1~exp1
Severity: normal

Dear Maintainer,

I managed to make clang-3.6 segfault on a piece of code that should not compile,
as it comprises the invalid use of a non-static data member.

This also applies to clang-3.5.

The crash is 100% reproducible and also affects clang-3.5 (1:3.5.2-1) but 
appears
to be fixed in clang-3.7 (1:3.7~svn239806-1+b1). It affects clang-3.6 both from
unstable (1:3.6.1-1) and experimental (1:3.6.2~+rc1-1~exp1).

Unfortunately I have not been able to isolate what causes the crash or to
produce a minimal example, and I can't share the original code (yet -- it's
unpublished research).

crash backtrace:


OMPI_CXX=clang++-3.6 mpic++ -std=c++11 -Wall -Wextra -Werror 
-I/opt/intel/composer_xe_2015.2.164/mkl/include  -Ofast -g -flto -DNDEBUG -o 
mostfreq mostfreq.cpp /usr/lib/x86_64-linux-gnu/libgsl.a libboost_mpi.a 
libboost_serialization.a 
/opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_intel_lp64.a 
/opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_core.a 
/opt/intel/composer_xe_2015.2.164/mkl/lib/intel64/libmkl_sequential.a -ldl
In file included from mostfreq.cpp:13:
../worker_ec.h:178:48: error: invalid use of non-static data member 'k'
std::vectorelement select_dht(int rank = k) {
   ^
../worker_ec.h:178:41: error: unused parameter 'rank' 
[-Werror,-Wunused-parameter]
std::vectorelement select_dht(int rank = k) {
^
#0 0x7f991806d3a2 llvm::sys::PrintStackTrace(_IO_FILE*) 
(/usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1+0xf943a2)
#1 0x7f991806baf1 (/usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1+0xf92af1)
#2 0x7f9916cb08d0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0xf8d0)
#3 0xb62721 (/usr/lib/llvm-3.6/bin/clang+0xb62721)
#4 0xb62b35 (/usr/lib/llvm-3.6/bin/clang+0xb62b35)
#5 0xb630f2 clang::Sema::CheckCompletedExpr(clang::Expr*, 
clang::SourceLocation, bool) (/usr/lib/llvm-3.6/bin/clang+0xb630f2)
#6 0xc96118 clang::Sema::BuildCXXDefaultArgExpr(clang::SourceLocation, 
clang::FunctionDecl*, clang::ParmVarDecl*) 
(/usr/lib/llvm-3.6/bin/clang+0xc96118)
#7 0xc9646c clang::Sema::GatherArgumentsForCall(clang::SourceLocation, 
clang::FunctionDecl*, clang::FunctionProtoType const*, unsigned int, 
llvm::ArrayRefclang::Expr*, llvm::SmallVectorImplclang::Expr*, 
clang::Sema::VariadicCallType, bool, bool) 
(/usr/lib/llvm-3.6/bin/clang+0xc9646c)
#8 0xc97302 clang::Sema::ConvertArgumentsForCall(clang::CallExpr*, 
clang::Expr*, clang::FunctionDecl*, clang::FunctionProtoType const*, 
llvm::ArrayRefclang::Expr*, clang::SourceLocation, bool) 
(/usr/lib/llvm-3.6/bin/clang+0xc97302)
#9 0xd852d9 clang::Sema::BuildCallToMemberFunction(clang::Scope*, clang::Expr*, 
clang::SourceLocation, llvm::MutableArrayRefclang::Expr*, 
clang::SourceLocation) (/usr/lib/llvm-3.6/bin/clang+0xd852d9)
#10 0xc98c79 clang::Sema::ActOnCallExpr(clang::Scope*, clang::Expr*, 
clang::SourceLocation, llvm::MutableArrayRefclang::Expr*, 
clang::SourceLocation, clang::Expr*, bool) 
(/usr/lib/llvm-3.6/bin/clang+0xc98c79)
#11 0xe36a18 (/usr/lib/llvm-3.6/bin/clang+0xe36a18)
#12 0xe32645 (/usr/lib/llvm-3.6/bin/clang+0xe32645)
#13 0xe335d1 (/usr/lib/llvm-3.6/bin/clang+0xe335d1)
#14 0xe33801 (/usr/lib/llvm-3.6/bin/clang+0xe33801)
#15 0xe3fcc5 (/usr/lib/llvm-3.6/bin/clang+0xe3fcc5)
#16 0xe40c63 (/usr/lib/llvm-3.6/bin/clang+0xe40c63)
#17 0xe40d7b (/usr/lib/llvm-3.6/bin/clang+0xe40d7b)
#18 0xe3ff35 (/usr/lib/llvm-3.6/bin/clang+0xe3ff35)
#19 0xe42ddf clang::Sema::SubstStmt(clang::Stmt*, 
clang::MultiLevelTemplateArgumentList const) 
(/usr/lib/llvm-3.6/bin/clang+0xe42ddf)
#20 0xe65280 clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, 
clang::FunctionDecl*, bool, bool) (/usr/lib/llvm-3.6/bin/clang+0xe65280)
#21 0xe63efb clang::Sema::PerformPendingInstantiations(bool) 
(/usr/lib/llvm-3.6/bin/clang+0xe63efb)
#22 0xe65365 clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation, 
clang::FunctionDecl*, bool, bool) (/usr/lib/llvm-3.6/bin/clang+0xe65365)
#23 0xe63efb clang::Sema::PerformPendingInstantiations(bool) 
(/usr/lib/llvm-3.6/bin/clang+0xe63efb)
#24 0xb157df clang::Sema::ActOnEndOfTranslationUnit() 
(/usr/lib/llvm-3.6/bin/clang+0xb157df)
#25 0xa68fa0 
clang::Parser::ParseTopLevelDecl(clang::OpaquePtrclang::DeclGroupRef) 
(/usr/lib/llvm-3.6/bin/clang+0xa68fa0)
#26 0xa5ecc3 clang::ParseAST(clang::Sema, bool, bool) 
(/usr/lib/llvm-3.6/bin/clang+0xa5ecc3)
#27 0x6efdc6 clang::FrontendAction::Execute() 
(/usr/lib/llvm-3.6/bin/clang+0x6efdc6)
#28 0x6cc2f9 clang::CompilerInstance::ExecuteAction(clang::FrontendAction) 
(/usr/lib/llvm-3.6/bin/clang+0x6cc2f9)
#29 0x6b4c43 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) 
(/usr/lib/llvm-3.6/bin/clang+0x6b4c43)
#30 0x6af278 cc1_main(llvm::ArrayRefchar const*, char const*, void*) 
(/usr/lib/llvm-3.6/bin/clang+0x6af278)
#31 0x6ae8a3 main (/usr/lib/llvm-3.6/bin/clang+0x6ae8a3)
#32 0x7f9915884b45 __libc_start_main 

Bug#794475: clang-3.6: clang segfaults on invalid use of non-static data member

[Lorenz Hübschle-Schneider]

reopen 794475 =
retitle 794475 clang segfaults on failed parameter substitution in
templated class or struct

Hi,

I've managed to come up with a small test case now and it's really quite
small:

-
template typename T
struct test {
test() { foo(); }
void foo(int x = k) {}
};

int main() {
testint w;
}
-

the simplest possible invocation is enough to trigger the bug (clang++-3.6
foo.cpp)

The test case demonstrates that it's not the invalid use of a non-static
data member that causes this (there is no member k in test), but a failure
to substitute arguments. Since the crash does not occur if test isn't
templated, that probably has something to do with the issue as well.

I hope my usage of the BTS was correct.

Cheers,
Lorenz

On Mon, Aug 3, 2015 at 3:27 PM, Sylvestre Ledru sylves...@debian.org
wrote:

 Le 03/08/2015 15:11, Lorenz Hübschle-Schneider a écrit :
  Package: clang-3.6
  Version: 1:3.6.2~+rc1-1~exp1
  Severity: normal
 
 
  Unfortunately I have not been able to isolate what causes the crash or to
  produce a minimal example, and I can't share the original code (yet --
 it's
  unpublished research).
 
 Without a test case, I won't be able to do anything.

 Please reopen with a way to reproduce it... Sorry about that :(
 Maybe creduce (https://packages.debian.org/sid/creduce) could help you.

 Sylvestre

Bug#785687: systemd: systemctl double free or corruption when enabling/disabling sysv units if pwd non-readable

[Lorenz Hübschle-Schneider]

Package: systemd
Version: 215-17
Severity: normal

Dear Maintainer,

systemctl fails to enable/disable sysv units if the current working directory is
not readable to the user systemctl is running at (root). In my case, the home
directory is mounted via nfs and unreadable to root.

gdb output:
Synchronizing state for docker.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d docker defaults
insserv: popd() can not change directory /home/lorenzhs: Permission denied
update-rc.d: error: insserv rejected the script header
*** Error in `/bin/systemctl': double free or corruption (fasttop): 
0x557da900 ***

Program received signal SIGABRT, Aborted.
0x7784b107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: Permission denied.
(gdb) bt
#0  0x7784b107 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x7784c4e8 in __GI_abort () at abort.c:89
#2  0x77889204 in __libc_message (do_abort=do_abort@entry=1, 
fmt=fmt@entry=0x7797bfe0 *** Error in `%s': %s: 0x%s ***\n) at 
../sysdeps/posix/libc_fatal.c:175
#3  0x7788e9de in malloc_printerr (action=1, str=0x7797c1c8 double 
free or corruption (fasttop), ptr=optimized out) at malloc.c:4996
#4  0x7788f6e6 in _int_free (av=optimized out, p=optimized out, 
have_lock=0) at malloc.c:3840
#5  0x5556ef93 in freep () at ../src/shared/util.h:641
#6  enable_sysv_units (verb=optimized out, args=0x557da860) at 
../src/systemctl/systemctl.c:5016
#7  0x5556f5fd in enable_unit.lto_priv.331 (bus=0x557d9f70, 
args=0x7fffeb80) at ../src/systemctl/systemctl.c:5235
#8  0x55561bd2 in systemctl_main (bus_error=0, argv=0x7fffeb78, 
argc=optimized out, bus=0x557d9f70) at ../src/systemctl/systemctl.c:6730
#9  main (argc=optimized out, argv=0x7fffeb78) at 
../src/systemctl/systemctl.c:6985

Best,
Lorenz

-- Package-specific info:

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

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

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

Versions of packages systemd recommends:
ii  dbus1.8.18-1
ii  libpam-systemd  215-17

Versions of packages systemd suggests:
pn  systemd-ui  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#752748: chromium crash on save-as

[Lorenz Hübschle-Schneider]

Dear maintainers,

please note comments #10 and #12 on this upstream bug report:

https://code.google.com/p/chromium/issues/detail?id=395982#c10

The crash is caused by OFFICIAL_BUILD not being defined. Upstream
recommends to patch out the part that causes the fatal assertion, at least
for the moment.

Cheers
Lorenz

On Fri, 27 Jun 2014 13:54:51 +0200 Morten Garkier Hendriksen 
gark...@etep.dk wrote:
 Hello maintainers

 Got hit by the same symptom.

 Moderate use of a major search machine brought me to this page:
 https://code.google.com/p/chromium/issues/detail?id=334125

 With this in one of the last comments on a patch:
  Don't try to guess the referrer policy, but use the one associated
  with the request

 Thought it might help.

 Thanks

 Morten

Bug#626604: xorg: X server disables mouse and keyboard upon starting (Thinkpad T420 4180W1H)

[Lorenz Hübschle-Schneider]

Package: xorg
Version: 1:7.6+6
Severity: important

On a clean install of Debian testing (completely up-to-date as of 10 minutes 
ago) on a Thinkpad T420 4180W1H, upon starting an X server, it seems to disable 
mouse and keyboard.
The laptop comes with a dual-graphics-card-setup using NVidia's Optimus 
technique, which I disabled in the BIOS before installing (I selected the 
integrated Intel Graphics of the Sandy Bridge CPU).
When starting X, either via service gdm3 start or startx, everything will 
work as expected, except I cannot use mouse, trackpoint and/or keyboard. 
Ctrl+Alt+F1 etc do not work either; Magic SysRQ remains functional.
I can reproduce this behaviour every time.
I tested Ubuntu 11.04 and it does not have this issue.

Somehow I suspect it might have something to do with the whole graphics setup, 
but nothing I tried proved successfully so far.
Also, /var/log/gdm/:0.log ends like this:

(WW) Falling back to old probe method for vesa
(EE) No devices detected.

Fatal server error:
no screens found


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Apr 20 23:40 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1926464 Mar 26 04:49 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

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

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

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 20150 May 13 18:12 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  1507.539] 
X.Org X Server 1.9.5
Release Date: 2011-03-17
[  1507.539] X Protocol Version 11, Revision 0
[  1507.539] Build Operating System: Linux 2.6.38-1-amd64 x86_64 Debian
[  1507.539] Current Operating System: Linux znetroll 2.6.38-2-amd64 #1 SMP Thu 
Apr 7 04:28:07 UTC 2011 x86_64
[  1507.540] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 
root=UUID=d6428355-9946-41db-9078-5d7ec4927fdf ro quiet
[  1507.540] Build Date: 26 March 2011  03:32:34AM
[  1507.540] xorg-server 2:1.9.5-1 (Cyril Brulebois k...@debian.org) 
[  1507.540] Current version of pixman: 0.21.8
[  1507.540]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1507.541] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1507.542] (==) Log file: /var/log/Xorg.0.log, Time: Fri May 13 18:12:31 
2011
[  1507.543] (==) Using system config directory /usr/share/X11/xorg.conf.d
[  1507.566] (==) No Layout section.  Using the first Screen section.
[  1507.566] (==) No screen section available. Using defaults.
[  1507.567] (**) |--Screen Default Screen Section (0)
[  1507.567] (**) |   |--Monitor default monitor
[  1507.567] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[  1507.567] (==) Automatically adding devices
[  1507.567] (==) Automatically enabling devices
[  1507.567] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[  1507.567]Entry deleted from font path.
[  1507.567] (WW) `fonts.dir' not found (or not valid) in 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType.
[  1507.567]Entry deleted from font path.
[  1507.567](Run 'mkfontdir' on 
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType).
[  1507.567] (==) 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
[  1507.567] (==) ModulePath set to /usr/lib/xorg/modules
[  1507.567] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  1507.567] (II) Loader magic: 0x7d1be0
[  1507.567] (II) Module ABI versions:
[  1507.567]X.Org ANSI C Emulation: 0.4
[  1507.567]X.Org Video Driver: 8.0
[  1507.567]X.Org XInput driver : 11.0
[  1507.567]X.Org Server Extension : 4.0
[  1507.569] (--) PCI:*(0:0:2:0) 8086:0126:17aa:21d0 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x5000/64
[  1507.569] (II)