Bug#148762: breaks lxdoom build
On Sat, 01 Jun 2002, Robert Millan wrote: Hi, > Package: svgalib > Version: 1:1.4.3-9 > Severity: serious > > When Svgalib is enabled, lxdoom fails to build due to a linker > problem with lsdoom. It looks like a bug in svgalib to me: > I can't reproduce the bug. lxdoom 1.4.4-7 compiles fine for me both with svgalib 1:1.4.3-9 and -10. Best Regards, Robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#148762: breaks lxdoom build
Processing commands for [EMAIL PROTECTED]: > severity 148762 important Bug#148762: breaks lxdoom build Severity set to `important'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#148762: breaks lxdoom build
severity 148762 important thanks On Tue, Jun 04, 2002 at 10:33:29AM +, Robert Luberda wrote: > On Sat, 01 Jun 2002, Robert Millan wrote: > > Hi, > > > Package: svgalib > > Version: 1:1.4.3-9 > > Severity: serious > > > > When Svgalib is enabled, lxdoom fails to build due to a linker > > problem with lsdoom. It looks like a bug in svgalib to me: > > > > I can't reproduce the bug. lxdoom 1.4.4-7 compiles fine for me both with > svgalib 1:1.4.3-9 and -10. curious, it stopped happening for me too. maybe just after glibc upgrade? I'm reducing severity to important, it could be a bug somewhere else that still needs fixing. -- Robert Millan "5 years from now everyone will be running free GNU on their 200 MIPS, 64M SPARCstation-5" Andrew S. Tanenbaum, 30 Jan 1992 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#126154: Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126154
Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126154&repeatmerged=yes | [ Charset ISO-8859-1 unsupported, converting... ] | [ You can also use 'v' to view or save this part. ] | | ... | | -- System Information | Debian Release: 3.0 | Architecture: i386 | Kernel: Linux meiner 2.2.20 #2 Sun Nov 4 23:47:51 CET 2001 i686 | Locale: LANG=C, LC_CTYPE=C == I of course do not know about Debian, but usually C locale implies US-ASCII charset. US-ASCII does not handle characters from ISO-8859-1. ( Another story is that you can ask Elm ME+ switch charsets of terminal and tell to Elm ME+ what charsets your particular terminal support. ) / Kari Hurtta -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#134742: Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134742
Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134742&repeatmerged=yes | Elm appears to search dirents under every component of the $MAIL path | with stat64. When some of these components have softlinks pointing into | an autofs-controlled areas (e.g. cdrom, or NFS mounts), the stat64 I of course do not know about Debian, but are you tried elmrc option: local-fast-lookup = yes That option have following description: # If set indicates that directory listing not needed for lookup # Need to be unset, if same character on local-fs-charset is several # repesentations (or encodings) # # See also: local-fs-charset, imap-fast-lookup ### local-fast-lookup = OFF / Kari Hurtta -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#134742: Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134742
Hi! "A month of sundays ago Kari Hurtta wrote:" > Spying at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134742&repeatmerged=yes > > | Elm appears to search dirents under every component of the $MAIL path > | with stat64. When some of these components have softlinks pointing into > | an autofs-controlled areas (e.g. cdrom, or NFS mounts), the stat64 > > I of course do not know about Debian, > but are you tried elmrc option: > > local-fast-lookup = yes Thanks for the suggestion. No I haven't. Because the bug manifested itself only recently in 2.4pl25ME+89-2, after being absent in 2.4pl25ME+66-1. So I presumed it was unintentional. And the strace clearly shows a search that one can easily interpret as a coding mistake. So I haven't been looking for exotic explanations where a simple one suffices! > That option have following description: > > # If set indicates that directory listing not needed for lookup ?? Double dutch! Lookup of what? What directory listing? > # Need to be unset, if same character on local-fs-charset is several > # repesentations (or encodings) Again, this is not english. What? "is several representations"? Do they mean "HAS several representations"? > # > # See also: local-fs-charset, imap-fast-lookup > ### local-fast-lookup = OFF The comments are incomprehensible, I am afraid, which is a bug in itself. However, I'll try it ... with elm ... 66-1 .. nbd:/tmp% elm I can't understand keyword "local-fast-lookup" in line 18 in ".elm/elmrc" file I can't understand keyword "gpg" in line 166 in ".elm/elmrc" file Fix .elm/elmrc or let elm rebuild elmrc with option '-w' nbd:/tmp% with elm .. 95-3 .. grrr .. doesn't work at all with nfs mounts. Wait while I recompile with appropriate locking options. Yes. I would say that local-fast-lookup = yes works! The difference is profoundly noticable with the option set and unset. One hangs for a minute, the other goes through like lightning. However, I think that's just a workaround. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#148762: breaks lxdoom build
Robert Millan <[EMAIL PROTECTED]> immo vero scripsit: > > I can't reproduce the bug. lxdoom 1.4.4-7 compiles fine for me both with > > svgalib 1:1.4.3-9 and -10. > > curious, it stopped happening for me too. maybe just after glibc upgrade? > > I'm reducing severity to important, it could be a bug somewhere else > that still needs fixing. You could have set LD_LIBRARY_PATH to a weird value, etc. Sounds more like a user error to me. -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#134742: Spying at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134742
"A month of sundays ago Kari Hurtta wrote:" > local-fast-lookup = yes Just to confirm, yes that option disables the undesirable directory searching that triggers autofs, at least in elm-me+-2.4pl25ME+95 HOWEVER .. it's not satisfactory. Putting it in elmrc makes earlier elms barf, complaining about oboe:/usr/oboe/ptb% elm I can't understand keyword "local-fast-lookup" in line 18 in ".elm/elmrc" file Fix .elm/elmrc or let elm rebuild elmrc with option '-w' followed by bailout. So the workaround is untenable on a system with NFS shared home directories, which people may be accessing from different computers, with different versions of elm. Come to that, I can't find where to turn on only dotlocking for NFS mounted maildirs ... all in all, I would suggest that moving above elm-me+-2.4pl66 continues to be highly unadvisable. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#142355: freeamp: freeze with watch directory.
Package: freeamp Version: 1:2.1.1.0-4 Followup-For: Bug #142355 I'm seeing this too; I'm willing to help debug if anyone has any ideas. freeamp doesn't respond to any user input with the watch directory timeout set to 10 minutes; manually editing the line: WatchThisDirectoryTimeout: 600 to WatchThisDirectoryTimeout: 0 in ~/.freeamp/preferences fixed the problem (or rather, worked around it). --scott -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux skiffserv 2.4.17 #1 Fri Feb 8 14:08:32 EST 2002 i686 Locale: LANG=C, LC_CTYPE= Versions of packages freeamp depends on: ii libc6 2.2.5-6 GNU C Library: Shared libraries an ii libgdk-pixbuf2 0.17.0-2 The GdkPixBuf library. ii libglib1.2 1.2.10-ximian.2 The GLib library of C routines ii libgtk1.2 1.2.10-ximian.21 The GIMP Toolkit set of widgets fo ii libmusicbrainz11.0.1.final-2 Second generation incarnation of t ii libstdc++2.10-glibc2.2 1:2.95.4-9The GNU stdc++ library ii libttf21.4pre.20011029-1 FreeType 1, The FREE TrueType Font ii libvorbis0 1.0rc3-ximian.2 The Vorbis General Audio Compressi ii xlibs 4.1.0-17 X Window System client libraries ii zlib1g 1:1.1.4-1 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#110295: freeamp: can't reproduce.
Package: freeamp
Version: 1:2.1.1.0-4
Followup-For: Bug #110295
I don't see this on my system -- with the Ximian rc3 version of libvorbis,
if that helps. The second follow-up to this bug ("GUI stops responding")
sounds more like the symptoms of the watch directory bug described in
Debian Bug #142355. Hopefully my library versions listed below will further
help track down what's causing this not to work for some people.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux skiffserv 2.4.17 #1 Fri Feb 8 14:08:32 EST 2002 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages freeamp depends on:
ii libc6 2.2.5-6 GNU C Library: Shared libraries an
ii libgdk-pixbuf2 0.17.0-2 The GdkPixBuf library.
ii libglib1.2 1.2.10-ximian.2 The GLib library of C routines
ii libgtk1.2 1.2.10-ximian.21 The GIMP Toolkit set of widgets fo
ii libmusicbrainz11.0.1.final-2 Second generation incarnation of t
ii libstdc++2.10-glibc2.2 1:2.95.4-9The GNU stdc++ library
ii libttf21.4pre.20011029-1 FreeType 1, The FREE TrueType Font
ii libvorbis0 1.0rc3-ximian.2 The Vorbis General Audio Compressi
ii xlibs 4.1.0-17 X Window System client libraries
ii zlib1g 1:1.1.4-1 compression library - runtime
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
