On Fri, Apr 05, 2024 at 05:04:37AM +, Thorsten Glaser wrote:
> Markus Wichmann dixit:
>
> >can check with readelf -r what the relocation types are. If they are not
> >relative, they will not be processed.
>
> Gotcha! They are all R_390_RELATIVE except for:
>
> 00045ff0 00110016
On Thu, Apr 04, 2024 at 07:50:40PM +, Thorsten Glaser wrote:
> Szabolcs Nagy dixit:
>
> >the next culprit is gcc (each target can have their own
>
> gcc-13_13.2.0-23
>
> >static pie specs) or the way you invoked gcc (not visible
>
> As I wrote earlier, though with more flags. Dropping all
On Sat, Feb 03, 2024 at 08:20:28AM +, Thorsten Glaser wrote:
> Hi musl maintainers,
>
> waldi indeed provided a fix for this bug forgot to Cc me, so I missed
> it until now. I tested this:
>
>
>
> (sid_mips64el-dchroot)tg@eberlin:~$ sh -x $(which musl-gcc) hello.c
> + exec
On Fri, Jun 11, 2021 at 08:35:08PM +0200, Helmut Grohne wrote:
> Dear musl developers,
>
> As I proceeded to building libselinux, I ran into the well-known issue
> that musl does not include a fts.h header. This is documented in the
> musl faq at:
>
In support of this not being a bug, I have code which uses the
correct, standards-compliant behavior of fgets. Contrary to Andrew's
report, it's very easy to know how much is read by fgets and use it
with data containing '\0'. Simply ensure the buffer does not contain
any occurrances of '\n' (for
On Sun, Oct 26, 2008 at 05:22:57PM -0400, Eric Dorland wrote:
* Rich Felker ([EMAIL PROTECTED]) wrote:
Package: iceweasel
Version: 2.0.0.6-1
Severity: normal
Tags: l10n
*** Please type your report below this line ***
When using the Tibetan Machine Uni font (which is packaged
Package: ttf-tmuni
Version: 0.0.20040806-1
Severity: normal
tmuni 'recommends' mknfonts.tool rather than merely suggesting it,
which causes unnecessary software only of interest to font hackers to
be installed in the default configuration. This is almost surely not
the intended behavior. Please
Package: autofs
Version: 4.1.4+debian-2.1
Severity: normal
These days autofs is at least as useful, if not moreso, for managing
removable media than for nfs, which has become something of a niche
application. Installing autofs should not cause nfs stuff to be
installed, since anyone needing nfs
If this bug is going to be marked wontfix, I think a justification is
in order. Enabling eightBitInput (which Henning has correctly noted
is a misnomer) by default clashes with non-7bit characters, making it
unreasonable for any application using a terminal to attempt to treat
octets with the 8th
I RTFS'd mg a while back looking to add UTF-8 support, and the biggest
problem for bloating and complexity seemed to be the layer that
manages the screen contents for refresh optimization. Basic UTF-8
support would require enlarging it quite a bit, and full support
(including nonspacing marks)
Package: xbase-clients
Version: 1:7.3+2
Severity: normal
The program 'bitmap' from the standard X clients seems to have
disappeared with the split of the xbase-clients package. As far I can
can tell it is gone, not moved to another package. I use this program
frequently and consider its
On Wed, Oct 03, 2007 at 11:50:53AM +0300, Timo Aaltonen wrote:
Yes, I did the original split, but didn't think that anyone actually used
bitmap :) (it isn't included in Fedora, for instance)
Anyway, it will be added to x11-apps.
Thanks! For what it's worth, this program, simple as it is, is
I’m against making default aliases for these fonts, for two reasons:
1. The proposed fonts to replace the MS fonts are not clones of the MS
fonts. They do not look similar and do not have similar metrics.
Aliases should be used only as a means of providing actual font
clones or generic
Package: fontconfig-config
Version: 2.4.2-1.2
Severity: normal
The URW Nimbus fonts, in their original Postscript form, have major
kerning issues which cause many letters to run together when hinting
is enabled. I’m uncertain whether this is a bug in the fonts
themselves or a problem in
Package: xorg
Version: 1:7.3+2
Severity: normal
Since upgrading to the latest xorg package, the keyboard led
indicators showing the XKB group toggle no longer work on my system.
I have grp_led:caps in my configuration but the caps lock light
remains unlit, while the group toggle key itself works.
On Fri, Sep 14, 2007 at 10:58:32AM +0200, Eugeniy Meshcheryakov wrote:
13 вересня 2007 о 23:37 -0400 Rich Felker написав(-ла):
While other Latin glyphs are equipped with proper hinting in the
DejaVu family of fonts, the ligatures for fi, fl, ffi, and ffl are
very poorly hinted (perhaps auto
Package: ttf-dejavu
Version: 2.19-1
Severity: normal
While other Latin glyphs are equipped with proper hinting in the
DejaVu family of fonts, the ligatures for fi, fl, ffi, and ffl are
very poorly hinted (perhaps auto-generated hints?). This causes the
auto-ligated letters to become blurry or
I just experienced the same problem and was about to report a bug for
it, but it seems I wasn't the first. The issue is that fontconfig has
standard aliases sans, serif, and monospace which applications
should use to get the user's preferred font in each of these 3
families. A good fontconfig
Package: ttf-tamil-fonts
Version: 1:0.5.0
Severity: normal
The TAMu family of fonts in the ttf-tamil-fonts package simply contain
Tamil glyphs placed over top of Latin codepoints. This constitutes
incorrect encoding.
If fonts like this are needed by users of the language, perhaps for
reading
Package: ttf-alee
Version: 11.4
Severity: normal
The [HaN-mfs] font in the ttf-alee package simply contain Hangul
glyphs placed over top of Latin codepoints. This constitutes incorrect
encoding.
If there is a real need for this font by users, could it be moved to a
separate package such as
Waiting for upstream to take their merry time to release 3.0 hardly
seems like a good way to deal with the problem to me. If fixing it
independently is too much work, how about just disabling justified
text completely when using Pango? I find it slows down the browser to
an almost unusable crawl
Package: ttf-bengali-fonts
Version: 1:0.5.0
Severity: normal
running fc-list shows:
Ani,অনি Dvf:style=Regular
Mukti Narrow,মà§U+0081কà§U+008Dতি:style=Regular
Mukti Narrow,মুক্তি পাতনা,Mukti Narrow Bold:style=Regular,Bold
[The U+ escaping was done by less; these are control
Mitra Mono also has a similar problem
Mitra Mono,\\u09ae\\u09bf\\u09a4\\u09cd\\u09b0:style=Regular
Here, \u escapes have been used for the characters. If this is valid
but just not supported by fontconfig, maybe the issue should be
reported as a bug with fontconfig, but nonetheless putting
On Sat, Sep 08, 2007 at 08:06:15PM +0200, Sven Arvidsson wrote:
Hi again,
I forwarded this bug to the upstream developers,
http://bugzilla.gnome.org/show_bug.cgi?id=472657
They are asking if you also see this in gedit?
Yes, see screenshot attached. Typing any Latin character between the
Package: xterm
Version: 229-1
Severity: normal
When using GNU Unifont with xterm, certain Unicode characters
(0100-011F, 017F-019F, 0200-021F, ...) are displayed in the wrong
position, roughly half a cell-width to the left of where they belong.
Using urxvt works fine so the issue seems to be a
Package: libc6
Version: 2.6.1-2
Severity: important
glibc's regular expression engine crashes with sig11 whenever trying
to compile a regular expression with non-ASCII range expressions if
LC_CTYPE is a UTF-8 locale but LC_COLLATE is set to C or POSIX. This
is a common setup among users who want
Package: unifont
Version: 1:1.0-4
Severity: wishlist
Unifont contains an incomplete set of Tibetan glyphs covering most of
the range U+0F40 to U+0F68, but these are insufficient for even
minimal use of the language. Proper rendering of Tibetan requires
contextual substitutions ala OpenType, but
Package: iceweasel
Version: 2.0.0.6-1
Severity: normal
Tags: l10n
*** Please type your report below this line ***
When using the Tibetan Machine Uni font (which is packaged with
Debian and intended as the default font for Tibetan script), Iceweasel
is displaying every combining character
Package: libpango1.0-0
Version: 1.16.5-1
Severity: normal
After upgrading my system, the latest Pango renders U+200B (zero-width
space) visibly under certain conditions, as a missing glyph box
containing the hex value. Particularly, Pango seems to be a looking
for a glyph for this character
Subject: uim-common: postinst script fails (in init.scm?)
Package: uim-common
Version: 1.4.1-2
Severity: grave
Justification: renders package unusable
File: uim-common
*** Please type your report below this line ***
apt-get install results in the following:
30 matches
Mail list logo
