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
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
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.
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
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 othe
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
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/Raft
t;
> 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,
> >>
> &
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:
> Pac
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
Yes, it's fixed. Thanks a lot.
Lorenz
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.
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-
Sounds like a duplicate of #815581 (fixed / pending) to me
Cheers
Lorenz
-display-server" (wayland). Maybe these can be
of help?
Cheers
Lorenz
On Tue, Feb 23, 2016 at 2:35 PM, Lorenz Hübschle-Schneider
wrote:
> Package: xwayland
> Version: 2:1.18.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> sinc
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
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
wrote:
> Hello,
>
> On Thu, Nov 19, 2015 at 4:07 PM, Michael Biebl wrote:
>> I just realized, that you
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 (per
twork 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 wrote:
> Am 19.11.2015 um 14:29 schrieb Felipe Sateler:
> > Control: tags -1 moreinfo
> >
> > On 19 November 2015 at 09:59, Lore
ut 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
wrote:
> Le 03/08/2015 15:11, Lore
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
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:
Synch
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 mo
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 Opti
24 matches
Mail list logo
