Control: tag + patch
Hi,
I compared the source code on sources.debian.org and upstream and I
think this exact build error was fixed upstream by adding a cast:
https://gitea.wildfiregames.com/0ad/0ad/commit/7c07083724980af73f299c079f9040166120b1e4
Cheers,
Uli
tags 1064307 patch
thanks
Hi,
for $REASONS I need to use awscli on Ubuntu, but the package was removed
from Ubuntu Noble (supposedly due to this bug). Here is how I managed to
get things to work on Noble.
The problem that is reported in this bug comes from an old version of
"six" that is bundle
Hi,
this issue was now fixed upstream and thus should be solved in an
upcoming release:
http://cvs.schmorp.de/rxvt-unicode/src/command.C?r1=1.603&r2=1.604&sortby=date
Cheers,
Uli
Package: rxvt-unicode
Version: 9.31-1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: tobespam...@web.de
Hi,
I was recently experimenting with a terminal UI library and had some contact
with terminal mouse reporting [0]. Specifically, SGR pixel mode (enabled via
ESC[?1006h) and the any mouse
Package: libxcb-cursor0
Version: 0.1.1-4
Severity: normal
X-Debbugs-Cc: tobespam...@web.de
Hi,
for $REASONS [0] I tested today what happens when loading a non-existing
cursor through libxcb-cursor. To my surprise, I got X11 errors instead
of the existing "cannot load cursor"-message. After some
Package: cargo
Version: 0.57.0-7+b1
Severity: important
Tags: upstream
X-Debbugs-Cc: psyc...@znc.in
Hi,
recently I tried to update some dependencies of a crate and cargo e.g.
claimed that libc 0.2.126 is the newest version, even though 0.2.127 was
released on August 3rd. I reported [#11009] ab
Hi,
can anyone tell me what the actual error here is?
I took a look at run.sh (the script that integration.sh actually runs)
and as far as I can tell, this script exited successfully.
The end of [0] is:
autopkgtest [19:16:07]: summary
integration.sh FAIL stderr: The X
Hi,
On 22.03.19 00:53, T. Joseph Carter wrote:
> <-- nick (~u@h) has quit (Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in)
> <-- nick (~u@h) has quit (Quit: ZNC 1.6.6+deb1ubuntu0.1 - http://znc.in)
> <-- nick (~u@h) has quit (Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in)
>
> And one counter-example o
Hi,
On 02.12.18 02:30, Roland Hieber wrote:
> since a recent apt-get upgrade, followed by a restart of X, the systray
> icons in my awesome with default configuration look strange and it seems
> like the transparent parts are no longer redrawn with the background
> color, but previously drawn item
Hi,
On 15.03.2018 22:58, Hans van den Bogert wrote:
> It is arguable if this patch truly fixes a bug, [...]
Since the gist of the patch seemed to have been lost in the noise, I'll
repeat it here explicitly:
> +diff --git a/lib/menubar/menu_gen.lua b/lib/menubar/menu_gen.lua
> +index 519629c7d4..
Hi,
On 05.01.2018 11:45, Wouter Verhelst wrote:
> If you need further information, do ask.
How would you fix this?
Awesome uses glib. Your favorite search engine can provide you with lots
of information on the problems here (e.g. [1,2]), but it boils down to:
This is not possible with glib. GLib
experience is one of those things that say,
'You know that thing you just did? Don't do that.'
-- Douglas Adams
>From f8350780e77ed68922493c8397615abbd6908cb8 Mon Sep 17 00:00:00 2001
From: Uli Schlachter
Date: Mon, 30 Oct 2017 21:14:11 +0100
Subject: [PATCH] callabl
Hi,
FYI, the bug was already reported upstream:
https://github.com/pavouk/lgi/issues/167
The reason seems to be a (GObject-introspection) API break in GLib.
Previously g_object_newv was [rename-to g_object_new], but now this
annotation is on g_object_new_with_properties().
If you ask me, this i
Hi,
could you try if starting awesome with the --no-argb flag fixes this?
First: "Why I think that this is not a bug in awesome"
The systray is implemented as windows. The systray provider (awesome in
this case) only places these windows, but it does not draw them. Since
in X11 a window cannot be
On 28.01.2017 16:37, Goedson Teixeira Paixao wrote:
> Package: awesome
> Version: 4.0-1
>
> When trying to show the menubar (shortcut is Super+p in the default
> configuration) I get the following error message:
>
> /usr/share/awesome/menubar/utils.lua:289: attempt to index field
> 'Async' (a nil
On 19.12.2016 00:04, Christian Hofstaedtler wrote:
> Control: tags -1 + moreinfo
>
> Dear Submitter,
>
> I've quickly tried to reproduce your bug report, but failed to do
> so. Please provide more info.
I'm happy to do so, I just didn't have any good ideas on which
information. :-)
> Were you u
On 09.12.2016 08:59, Philipp Ittershagen wrote:
[...]
> On Sun, Dec 04 2016, Uli Schlachter wrote:
>> I had the same problem and I can confirm that creating the following
>> file fixed this issue for me:
>>
>> $ cat /etc/systemd/system/apt-daily.timer.d/10-depend-on-netw
Package: dma
Version: 0.11-1+b1
Severity: serious
--- Please enter the report below this line. ---
Hi,
I don't know really what is going on, but the symptom is:
dpkg: Fehler beim Bearbeiten des Paketes dma (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert
12
Hi,
I had the same problem and I can confirm that creating the following
file fixed this issue for me:
$ cat /etc/systemd/system/apt-daily.timer.d/10-depend-on-network.conf
[Unit]
After=network-online.target
(However, I wonder if the timer or the service should depend on
network-online.target, b
On 29.10.2016 17:53, Santiago Vila wrote:
> On Sat, Oct 29, 2016 at 05:03:55PM +0200, Uli Schlachter wrote:
[...]
>> while investigating [1], I noticed that this package contains a copy of
>> parts of glib and exports its symbols.
[...]
> As you have rightly pointed ou
Package: gettext
Version: 0.19.8.1-1
Severity: serious
Justification: Policy 4.13
--- Please enter the report below this line. ---
Hi,
while investigating [1], I noticed that this package contains a copy of
parts of glib and exports its symbols. For example, the following says
that libgettextlib
Hi,
the arch issues seemed to be GCC6, -O2 (and x86?) specific [1,2] and was fixed
in Arch by compiling libxcb with -O1 [3]. Also, the code where this crash
occurred was not changed since the last release.
I would suggest to just ignore that one report.
Cheers,
Uli
[1]: https://lists.freedeskto
tags 826197 + fixed-upstream patch
thanks
This issue was fixed upstream (and the bug is actually on those arches
where the tests did NOT fail...):
https://github.com/Orc/discount/commit/0d71ce77859c44aad7379d70c9024d5047577100
https://github.com/Orc/discount/commit/aa9a54bddb3211204625c1eb6a26
Hi,
this issue was fixed upstream 26 days ago and a new release with this
fix was published. Are you planning to backport this fix or to upload
the new version? What is blocking this from being fixed in Debian? How
can I help?
Two weeks left until auto-removal and lua-lgi seems to have ended
Package: rsnapshot
Version: 1.4.1-1
Severity: grave
Tags: upstream patch
Hi,
I just noticed that my backups are broken since a while. rsnapshot happily makes
backups of an old state of its .sync directory. Symptoms on stderr are:
[snip]
---
Hi,
just wanted to mention: The following bugs sound like previous reports of this
problem which were fixed by depending on shared-mime-info, however the
dependency was added to the wrong package each time (libgdk-pixbuf2.0-dev,
libgtk2.0-0):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7588
reassign 801170 libgdk-pixbuf2.0-0
thanks
Hi,
I tried a slight variation of your instruction:
host$ fallocate -l 10G testimg
host$ /sbin/mkfs.ext4 testimg
host$ mkdir /tmp/mount
host$ mount testimg /tmp/mount
host$ sudo /usr/sbin/debootstrap --variant=minbase unstable /tmp/mount
host$ echo 'APT:
reassign 802248 lua-ldoc 1.4.3-4
retitle 802248 lua-ldoc does not work with lua5.1
tag 802248 patch
thanks
Hi,
lua-ldoc clearly uses lua-any, but claims to only work with lua5.2:
$ grep Lua-Versions /usr/bin/ldoc
-- Lua-Versions: 5.2
After uninstalling lua5.2 I thus get:
$ ldoc
Error: no suita
Hi everyone,
isn't this a bug in ldoc?
If I understand the dependencies correctly, awesome depends on lua 5.1 and
lua-ldoc depends on lua5.1 | lua5.2, so only lua 5.1 is installed.
However, looking at [0], ldoc contains "Lua-Versions: 5.2", so lua-any doesn't
consider lua 5.1 a valid option.
Th
Hi,
the bug was introduced in the following commit:
https://github.com/znc/znc/commit/997023ea9de8fcc4ab68f0139015e1b7dba3b8a9
This is from 2005. Or put differently, everything this release is affected:
$ git describe --contains 997023ea9de8fcc4ab68f0139015e1b7dba3b8a9
znc-0.043~72
Yay,
Uli
--
Hi,
On 02.02.2014 17:41, Julien Cristau wrote:
[...]
>> On 2014-02-01 23:18, Alexander V. Kudrevatykh wrote:
>>> В Чтв, 30/01/2014 в 01:05 +0100, Andreas Beckmann пишет:
First step of debugging would be to run glxinfo inside gdb and get a
backtrace
after the crash. And maybe runn
Package: rxvt-unicode-256color
Version: 9.19-1
Severity: minor
Hi,
I got git builds of various libraries laying around (xcb, Xlib, cairo, ...) and
want all my program to use these versions of the libraries so that I notice new
problems early. To do this, I set LD_LIBRARY_PATH in ~/.xsession which
Package: libxcb-cursor-dev
Version: 0.1.0-1
Severity: normal
After installing libxcb-cursor-dev, I tried to use it through its pkg-config
file, but cmake/pkg-config was not happy:
$ cat CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
include(FindPkgConfig)
pkg_check_modules(FOO REQUIRED xc
Hi,
turns out that this is ultimately a bug in Pango. However, a work-around was
just committed to lua-lgi upstream:
https://github.com/pavouk/lgi/commit/ec3dfe88ce013e78246b22adce88a2c97a934005
Uli
--
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, w
Hi,
On 14.06.2013 17:26, Scott Kitterman wrote:
[...]
> dpkg-source: warning: ignoring deletion of file modules/modpython/swigpyrun.h
> dpkg-source: warning: ignoring deletion of file modules/modpython/znc_core.py
> dpkg-source: warning: ignoring deletion of file
> modules/modpython/_znc_core.cpp
Hi,
I just ran into this issue and Google led me to debian bug #708252. The problem
likely was with a video file whose file name contained an Umlaut (ö).
I sudoedit-ed the patch[0] into my iotop installation to test it. The result
didn't look pretty:
UnicodeEncodeError: 'ascii' codec can't encod
tags 703716 + upstream patch
thanks
Hi,
I just fixed this bug in DCMTK's git repository. The commit will soon be
publicly available[0]. The patch is also attached to this mail.
The problem was that with --disable-get some code was executed which used a
wrong value for the number of supported
Hi,
You write that this happens 'usually'. So it only happens sometimes? How often
does moving a window around have this effect? (Always / every second times /
only on full moon)
When did this behavior start? Or did awesome always do this? Do you have some
kind of roxterm or gnome-terminal c
Package: libpoppler13
Version: 0.16.7-3
Severity: important
Tags: upstream patch
This problem was already reported upstream[0] and fixed[1].
Basically, cairo 1.12 started clipping user fonts to the text extents while
cairo 1.10 didn't do any clipping. This results in only one pixel of each text
l
inning the Universe was created. This has made a lot of
people very angry and has been widely regarded as a bad move."
>From d6c087dcf9557ecb16bc4741b2e47de0bb90c14b Mon Sep 17 00:00:00 2001
From: Uli Schlachter
Date: Fri, 10 Feb 2012 18:09:23 +0100
Subject: [PATCH] Tests: Fix for c
On 19.02.2012 13:10, folkert wrote:
>> Could you also try /znc clearbindhost?
>
> Tried that but it did not help.
Could you try "/znc setbindhost 0.0.0.0"? That should force znc to use ipv4.
--
- Buck, when, exactly, did you lose your mind?
- Three months ago. I woke up one morning married to a
On 03.02.2012 20:42, folkert wrote:
>>> Suddenly after a restart znc won't connect to irc.oftc.net 6667 and
>>> irc.eu.rizon.net.
>>> So I did an strace on the process to see what was going on and saw this:
>>
>> what's the error message from ZNC?
> 20:23:20] *status: Cannot connect to IRC (Can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11.09.2011 18:19, Robert Kawecki wrote:
> ZNC uses an exclusive lock on a file handle that is open read-only. This
> operation is not supported on NFSv4, as described here:
> http://www.spinics.net/lists/linux-nfs/msg18594.html
> This problem make
Easy way to reproduce:
nc -l -p 1230
Then add 127.0.0.1 +6667 as an IRC server (important: ssl!) and see it eat all
the CPU time. I'm not yet 100% sure what exactly happens, but it's definitely
waiting for the SSL handshake to finish.
@Michael: Why are you connecting to a broken SSL server with t
Hi,
this issue was already reported to me by someone who built oocairo on ubuntu
natty. These problems started happening with cairo 1.10.
Fixes are in git:
http://git.naquadah.org/?p=oocairo.git;a=commitdiff;h=420b9ed240db4be6f6472b6a8092690867caa2ce
http://git.naquadah.org/?p=oocairo.git;a=c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
attached is a patch which in theory might fix this. However, I don't have an
openssl version with SSLv2 disabled and thus can't properly verify this.
Could someone test this patch, please?
Cheers,
Uli
- --
The Angels have the phone box!
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 10.10.2010 13:19, Moritz Muehlenhoff wrote:
> Package: znc
> Severity: grave
> Tags: security
>
> CVE-2010-2812 and CVE-2010-2934 are currently only
> fixed in experimental, but not sid and Squeeze. The
> Red Hat bug contains references to the pa
Hi,
I just found out that someone at redhat cares. This was assigned CVE-2010-3071.
http://seclists.org/oss-sec/2010/q3/276
http://seclists.org/oss-sec/2010/q3/289
Cheers,
Uli
--
- Buck, when, exactly, did you lose your mind?
- Three months ago. I woke up one morning married to a pineapple.
Package: bip
Version: 0.8.2-1
Severity: grave
Tags: security
Unauthenticated users can easily cause a NULL pointer dereference in bip (bip is
listening at localhost:7778):
$ echo USER | telnet localhost 7778
==25787== Process terminating with default action of signal 11 (SIGSEGV)
==25787== Ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> I liked the default layout implicitly being the first one in the list,
> since it is logical and doesn't require any additional code to
> express.
FYI:
The default config was modified so that the first entry in the layouts table is
the defaul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
just FYI, this bug might be fixed in version 3.4.6. I'm 90% sure it was fixed by
this commit:
http://git.naquadah.org/?p=awesome.git;a=commitdiff;h=4ed587206e6f34a7f367653b50e13316a82b3928
That bug was introduced here:
http://git.naquadah.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 16.05.2010 22:58, Jonathan Nieder wrote:
> found 542709 git-core/1:1.6.5-1
> quit
>
> Uli Schlachter wrote:
>
>> this happened to me the day I wrote the mail to this bug (google found this
>> bug
>> report w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 15.05.2010 21:36, Jonathan Nieder wrote:
> Uli, do you know whether you were using a release candidate when you
> experienced this problem? If you remember when that was,
> /var/log/dpkg.log would tell. I am asking because this would confirm
> w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
bug is kind of reproducible here. When I start an "audio/video call", my local
pidgin crashes. From the valgrind output I concluded that this is a NULL pointer
dereference (EIP points to "mov 0x38(%rbp),%rbp" and valrgind talks about
invalid acc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: libev3
Version: 1:3.9-1
Hi,
libev 3.8 had the following definition in ev.h:
#define EVFLAG_NOSIGFD0x0020U /* do not attempt to
use signalfd */
libev 3.9 now contains:
#define EVFLAG_NOSIGFD 0 /* compatibility to pre-3.9 */
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
maximilian attems wrote:
> On Wed, Feb 24, 2010 at 03:29:04PM +0100, Uli Schlachter wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> maximilian attems wrote:
>>> On Wed, Feb 24, 2010 at 12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
maximilian attems wrote:
> On Wed, Feb 24, 2010 at 12:58:54PM +0100, Uli Schlachter wrote:
>> This morning when I booted my laptop, right after grub was done, the
>> backlight
>> turned off. I collected the attached in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I just saw something like this, too.
After git rebase I got tons of conflicts, I fixed them up and "git add"'ed each
file, but git rebase --continue just showed me the message the message above.
(git status didn't report any unmerged files)
Wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: znc
Version: 0.045-3+etch1
Tags: Security
Severity: critical
All ZNC versions which have webadmin contain a privilege escalation bug in
webadmin. This bug was fixed with znc 0.066.
A quote from the changelog[1]:
Webadmin doesn't properly va
59 matches
Mail list logo
