Bug#425120: nvram-wakeup: filename /usr/sbin/time is unfortunate
Subject: nvram-wakeup: filename /usr/sbin/time is unfortunate Package: nvram-wakeup Version: 0.97-12 Severity: wishlist It would be nice if /usr/sbin/time could be renamed. Otherwise this produces unexpected behaviour when the (widely used) package time is also installed. Then calling time as normal user measures cpu resource usage, whereas root acts completely different. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages nvram-wakeup depends on: ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii makedev 2.3.1-83 creates device files in /dev nvram-wakeup recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391952: bug 391952 is fixed upstream
tag 391952 fixed-upstream thank you A workaround for this bug has been included in brand-new Mesa 6.5.3 . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391952: The r300 driver causes a SIGSEV while running nexuiz.
Here are additional infos about the bug: 0. I have not (yet) tried current mesa git. 1. I upgraded my debian mesa to experimental, which has version 6.5.2-3, including libgl1-mesa-dri-dbg 2. I reproduced the bug with the new versions 3. I included info about nexuiz config 4. I included info about how I ran gdb 5. I included the gdb output, including full backtrace I hope it helps (and you do not get lost in the 400-something lines). == about 1. -- $ dpkg -l \*mesa\* libdrm2 \*nexuiz\* xserver-xorg|grep ^ii ii libdrm2 2.3.0-1Userspace interface to kernel ii libgl1-mesa-dev 6.5.2-3A free implementation of the ii libgl1-mesa-dri 6.5.2-3A free implementation of the ii libgl1-mesa-dri-dbg 6.5.2-3A free implementation of the ii libgl1-mesa-glx 6.5.2-3A free implementation of the ii libglu1-mesa 6.5.2-3The OpenGL utility library (G ii libglu1-mesa-dev 6.5.2-3The OpenGL utility library -- ii mesa-common-dev 6.5.2-3Developer documentation for M ii mesa-utils6.5.2-3Miscellaneous Mesa GL utiliti ii nexuiz2.2.1-1A fast-paced 3D Ego-Shooter ii nexuiz-data 2.2.1-1Nexuiz game data files ii xserver-xorg 7.1.0-12 the X.Org X server == about 3. -- https://bugs.freedesktop.org/show_bug.cgi?id=9170 You might want to provide a little more information; what is enabled or disabled with the settings high and low? high: - no .nexuiz directory - alternative: .nexuiz-high as .nexuiz (see below) low: - .nexuiz-low as .nexuiz (see below) -- $ diff -Naur .nexuiz-high/data/config.cfg .nexuiz-low/data/config.cfg --- .nexuiz-high/data/config.cfg2007-02-28 19:23:55.0 +0100 +++ .nexuiz-low/data/config.cfg 2007-02-28 19:22:12.0 +0100 @@ -63,3 +63,15 @@ bind MWHEELDOWN weapprev bind MOUSE4 weaplast bind MOUSE5 +hook +cl_decals 0 +cl_particles_quality 0.10 +seta g_campaign_index 6 +gl_picmip 4 +r_coronas 0 +r_glsl_deluxemapping 0 +r_shadow_realtime_dlight 0 +r_shadow_realtime_world_shadows 0 +showfps 1 +vid_bitsperpixel 16 +vid_height 480 +vid_width 640 -- ..nexuiz-high/data/config.cfg : bind TAB +showscores bind ENTER +jump bind ESCAPE togglemenu bind SPACE +jump bind - sizedown bind 0 impulse 210 bind 1 impulse 1 bind 2 impulse 2 bind 3 impulse 3 bind 4 impulse 4 bind 5 impulse 5 bind 6 impulse 6 bind 7 impulse 7 bind 8 impulse 8 bind 9 impulse 9 bind = sizeup bind ` toggleconsole bind a +moveleft bind d +moveright bind e +hook bind i +show_info bind r messagemode2 bind s +back bind t messagemode bind w +forward bind y messagemode2 bind ~ toggleconsole bind BACKSPACE dropweapon bind UPARROW +forward bind DOWNARROW +back bind LEFTARROW +moveleft bind RIGHTARROW +moveright bind SHIFT +crouch bind F1 vyes bind F2 vno bind F3 spec bind F4 ready bind F5 menu_showteamselect bind F10 quit bind F11 disconnect bind F12 screenshot bind PAUSE pause bind KP_INS messagemode bind KP_END say_team quad soon (h:%h a:%a w:%w l:%l) bind KP_DOWNARROW say_team item free x:%x (h:%h a:%a w:%w l:%l) bind KP_PGDN say_team took item (h:%h a:%a w:%w l:%l) bind KP_LEFTARROW say_team negative (h:%h a:%a w:%w l:%l) bind KP_5 say_team help me (h:%h a:%a w:%w l:%l) bind KP_RIGHTARROW say_team incoming (h:%h a:%a w:%w l:%l) bind KP_HOME say_team defending (h:%h a:%a w:%w l:%l) bind KP_UPARROW say_team roaming (h:%h a:%a w:%w l:%l) bind KP_PGUP say_team attacking (h:%h a:%a w:%w l:%l) bind KP_DEL messagemode2 bind KP_SLASH say_team dropped flag (h:%h a:%a w:%w l:%l) bind KP_MULTIPLY say_team killed flagcarrier (h:%h a:%a w:%w l:%l) bind KP_MINUS say hi / good luck and have fun bind KP_PLUS say good game bind KP_ENTER say :-) / nice one bind MOUSE1 +attack bind MOUSE2 +attack2 bind MOUSE3 +zoom bind MWHEELUP weapnext bind MWHEELDOWN weapprev bind MOUSE4 weaplast bind MOUSE5 +hook -- ..nexuiz-low/data/config.cfg : bind TAB +showscores bind ENTER +jump bind ESCAPE togglemenu bind SPACE +jump bind - sizedown bind 0 impulse 210 bind 1 impulse 1 bind 2 impulse 2 bind 3 impulse 3 bind 4 impulse 4 bind 5 impulse 5 bind 6 impulse 6 bind 7 impulse 7 bind 8 impulse 8 bind 9 impulse 9 bind = sizeup bind ` toggleconsole bind a +moveleft bind d +moveright bind e +hook bind i +show_info bind r messagemode2 bind s +back bind t messagemode bind w +forward bind y messagemode2 bind ~ toggleconsole bind BACKSPACE dropweapon bind UPARROW +forward
Bug#391952: The r300 driver causes a SIGSEV while running nexuiz.
Hi,
I also can reproduce this bug.
The r300 driver causes a SIGSEV while running nexuiz.
This bug is 100% reproduceable by shooting the weapon Mortar
(just before the explosion).
I discovered that this problem is in libgl1-mesa-dri by running
nexuiz-sdl in gdb and getting a backtrace after the crash.
Find the log below.
Then, due to https://bugs.freedesktop.org/show_bug.cgi?id=8348 ,
I upgraded mesa (incl. dri) to current cvs
(similar to http://dri.freedesktop.org/wiki/Building).
This shows the same effect, except that it tells us that the bug is
in r300_state.c:1240 . Find the log below.
The contents of Mesa/src/mesa/drivers/dri/r300/r300_state.c are:
1238 t=r300-state.texture.unit[i].texobj;
1239
1240 if((t-format 0xff00)==0xff00) {
1241 WARN_ONCE(unknown texture format (entry %x)
encountered. Help me !\n, t-format 0xff); 1242}
Maybe t is assigned a NULL pointer ? Then accessing t-format would
segfault. Is mtu wrong ?
However, you can probably interpret this better than me.
Bye,
Wolfgang
-
0. Software Info
-
libgl1-mesa-dri 6.5.1-0.4
libgl1-mesa-glx 6.5.1-0.4
libglu1-mesa6.5.1-0.4
mesa-utils 6.3.2-2.1
nexuiz 2.0-3
nexuiz-data 2.0-hotfix20060616-1
-
1. Hardware info
-
my graphics card is (partial lspci output):
06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60
[Radeon X300 (PCIE)] 06:00.1 Display controller: ATI Technologies Inc
RV370 [Radeon X300SE]
-
2. nexuiz log using libgl1-mesa-dri:
-
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions. Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for
details. This GDB was configured as i486-linux-gnu...(no debugging
symbols found) Using host libthread_db library
/lib/tls/libthread_db.so.1.
(gdb) Starting program: /usr/lib/games/nexuiz/nexuiz-sdl
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
^7Nexuiz Linux 12:39:37 Sep 4 2006
[Thread debugging using libthread_db enabled]
[New Thread -1480988096 (LWP 10445)]
(no debugging symbols found)
^7Trying to load library... libz.so.1 - loaded.
^7Compressed files support enabled
^7Added packfile data/data20060614.pk3 (2849 files)
^7Added packfile data/data20060616_hotfix.pk3 (3 files)
^7Console initialized.
^7Playing registered version.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
^7Trying to load library... libcurl.so.3 - loaded.
^7cURL support enabled
^7Initializing client
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
^7Trying to load library... libvorbis.so.0 - loaded.
(no debugging symbols found)
^7Trying to load library... libvorbisfile.so.3 - loaded.
^7Ogg Vorbis support enabled
^7couldn't exec autoexec.cfg
^7Starting video system
^7Video: fullscreen 800x600x32x60hz
^7Linked against SDL version 1.2.11
^7Using SDL library version 1.2.11
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
^7checking for OpenGL 1.1.0... enabled
^7GL_VENDOR: Tungsten Graphics, Inc.
^7GL_RENDERER: Mesa DRI R300 20060815 TCL
^7GL_VERSION: 1.3 Mesa 6.5.1
^7GL_EXTENSIONS: GL_ARB_fragment_program GL_ARB_imaging
GL_ARB_multisample GL_ARB_multitexture GL_ARB_texture_border_clamp
GL_ARB_texture_compression GL_ARB_texture_cube_map
GL_ARB_texture_env_add GL_ARB_texture_env_combine
Bug#388845: debian-installer: Warn of sarge apt-proxy when selecting mirror
Of course you could display the incompatibility hint when the connection times out (instead of when selecting a mirror). Then it would only be seen by people that have a problem (assuming they have the patience to wait for the timeout). On the other hand it is nice to see a hint before the problem is there. Or you could say that a connection timeout is a good hint that your proxy is broken so that you do not need any further hints. The problem about the apt-proxy bug is that it is a bit hard to detect: - AFAIR some data is successfully retrieved from the apt-proxy before installation fails. - I could switch to the d-i console via Alt-F2 and download the file displayed in the errormessages on Alt-F4. So my apt-proxy mirror seemed to be ok. (Of course it was not.)
Bug#388845: debian-installer: Warn of sarge apt-proxy when selecting mirror
On 24-Sep-2006 Joey Hess wrote: IMHO it would be nice to have a hint / warning about sarge apt-proxy when manually selecting a mirror. Otherwise many people may stumble over this incompatibility. How is a client supposed to get the proxy version? Not at all. I thought of an unconditional line of text. First one selects Choose a mirror of the Debian archive - enter information manually. The next page asks for a mirror hostname. It could include a line of text with s.th. like An apt-proxy from Sarge will not work. Of course this information would also be seen by people that do not need it.. But it would only bother people that have a special proxy. And I think they may rather be happy about that hint than annoyed.
Bug#388845: debian-installer: Warn of sarge apt-proxy when selecting mirror
Package: debian-installer Severity: wishlist I tried to install debian behind an apt-proxy and the installations hangs when fetching packages during installation (Errormsg on ALT-F4). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388769 . It seems that all Debian etch installations behind a sarge apt-proxy fail because of apt-proxy bug 374405: Incompatible with full URL HTTP requests from recent apt versions http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374405 Upgrading the apt-proxy from sarge to backports.org solved the installation-problem. IMHO it would be nice to have a hint / warning about sarge apt-proxy when manually selecting a mirror. Otherwise many people may stumble over this incompatibility. Bye, Wolfgang -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (21, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-3-586tsc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Bug#388769: installer hangs when installing packages; no abort possible
I also tried to install debian behind an apt-proxy and the installations hangs when fetching packages during installation (Errormsg on ALT-F4). It seems that all Debian etch installations behind a sarge apt-proxy fail because of apt-proxy bug 374405: Incompatible with full URL HTTP requests from recent apt versions http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374405 Upgrading the apt-proxy from sarge to backports.org solved the installation-problem. Bye, Wolfgang
Bug#388846: installation: Warn of sarge apt-proxy
Package: installation Severity: wishlist I tried to install debian behind an apt-proxy and the installations hangs when fetching packages during installation (Errormsg on ALT-F4). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388769 . It seems that all Debian etch installations and probably upgrades behind a sarge apt-proxy fail because of apt-proxy bug 374405: Incompatible with full URL HTTP requests from recent apt versions http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374405 Upgrading the apt-proxy from sarge to backports.org solved the installation-problem. IMHO it would be nice to have a hint / warning about sarge apt-proxy in the sarge to etch upgrade instructions. Otherwise many people may stumble over this incompatibility. For installation a hint in d-i mirror selection could be sufficient. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388845 . Bye, Wolfgang -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (21, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-3-586tsc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
