Re: nvidia-glx not updating
Hi Seb For the last several days, nvidia-glx fails to upgrade with apt-get install nvidia-glx (or apt-get update): You must build the new nvidia-kernel-169.07 version of this package. Due a bug, already reported, you must have a link to fix a renaming problem: ln -s /usr/src/nvidia-kernel.tar.bz2 /usr/src/nvidia-kernel-source.tar.bz2 Now you can build the package. :-) Greetings from Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel module eeprom causing system freeze
Hi Dean, Dean Hamstead wrote: after a circuit breaker caused a power outage, which reset the bios. debian is now freezing (solid) at 'Loading kernel module eeprom'. The package lm-sensors uses the eeprom module to get temperature readings from motherboard sensors. I have seen Dell servers freeze when this module is being loaded. Maybe the module got updated but was never reloaded until the power outage now? Boot from a live CD and comment out eeprom from /etc/modules and then boot again. As far as I know, this module isn't used for anything else. Koen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia-glx not updating
On Mon, 14 Jan 2008 10:12:23 +0100, Thomas Rösch [EMAIL PROTECTED] wrote: [...] ln -s /usr/src/nvidia-kernel.tar.bz2 /usr/src/nvidia-kernel-source.tar.bz2 Now you can build the package. :-) Thanks everybody, this indeed allowed 'm-a a-i nvidia' to finish the job and work around the bug. Hopefully this will be fixed when the next version comes up. -- Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Corrupted Gnome terminal
Hi, all I screwed up my Gnome Terminal setup some how... on my workstation desktop. My system: Debian Lenny Kernel: 2.6.22-3-amd64 Video: Nvidia 8600 GT Video Drv. NVIDIA 169.07 My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. Thanks, in advance.. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia-glx not updating
On Mon, Jan 14, 2008 at 10:13:24AM +1100, Dean Hamstead wrote: you need to make the kernel module. its easy, if module-assistant (m-a) isnt installed, just go apt-get install module-assistant (may not be with a -) then do this... m-a prepare nvidia m-a a-i nvidia Unfortunately it seems m-a doesn't understand the current version of the nvidia driver. It claims it can't find the source archive (it is /usr/src/nvidia-kernel-source.tar.bz2). Doing this worked for me: cd /usr/src rm -rf modules/nvidia* tar xjf nvidia-kernel-source.tar.bz2 m-a a-i -t nvidia m-a still can't find the source, but since I already extracted it for it, it now builds an up to date module rather than continuing to reuse the extracted source from version 100 or so. After that nvidia-glx has no problem upgrading since there is now a matching kernel module package installed. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, Jan 14, 2008 at 08:38:59AM -0600, Don Montgomery wrote:
Here is what I found:
[EMAIL PROTECTED]:~$ less /etc/apt/apt.conf
/etc/apt/apt.conf: No such file or directory
[EMAIL PROTECTED]:~$ ll /etc/apt
total 40
drwxr-xr-x 2 root root 4096 2007-11-25 14:28 apt.conf.d
-rw-r--r-- 1 root root 2524 2006-11-14 08:43 apt-file.conf
-rw--- 1 root root0 2007-04-26 17:06 secring.gpg
-rw-r--r-- 1 root root 952 2008-01-13 19:35 sources.list
-rw-r--r-- 1 root root0 2007-04-26 17:06 sources.list~
drwxr-xr-x 2 root root 4096 2007-02-26 15:53
sources.list.d
-rw-r--r-- 1 root root 506 2007-04-30 19:32
sources.list.save
-rw--- 1 root root 1200 2007-08-13 19:50 trustdb.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg~
[EMAIL PROTECTED]:~$ cd /etc/apt/apt.conf.d/
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ ll
total 16
-rw-r--r-- 1 root root 40 2007-04-26 17:06 00trustcdrom
-rw-r--r-- 1 root root 92 2007-07-02 07:07 01autoremove
-rw-r--r-- 1 root root 91 2007-04-30 19:32 10periodic
-rw-r--r-- 1 root root 182 2006-12-20 13:31 70debconf
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 00trustcdrom
APT::Authentication::TrustCDROM true;
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 01autoremove
APT
{
NeverAutoRemove
{
^linux-image.*;
^linux-restricted-modules.*;
};
};
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 10periodic
APT::Periodic::Update-Package-Lists 1;
APT::Periodic::Download-Upgradeable-Packages 0;
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 70debconf
// Pre-configure all packages with debconf before they are installed.
// If you don't like it, comment it out.
DPkg::Pre-Install-Pkgs {/usr/sbin/dpkg-preconfigure --apt || true;};
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$
Thanks, Don
Perhaps try:
grep 4001 -r /etc/
or
env|grep 4001
My guess is you have a proxy setting somewhere in /etc, or you somehow
set a proxy environment variable that it is trying to use.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
Here is what I found:
[EMAIL PROTECTED]:~$ less /etc/apt/apt.conf
/etc/apt/apt.conf: No such file or directory
[EMAIL PROTECTED]:~$ ll /etc/apt
total 40
drwxr-xr-x 2 root root 4096 2007-11-25 14:28 apt.conf.d
-rw-r--r-- 1 root root 2524 2006-11-14 08:43 apt-file.conf
-rw--- 1 root root0 2007-04-26 17:06 secring.gpg
-rw-r--r-- 1 root root 952 2008-01-13 19:35 sources.list
-rw-r--r-- 1 root root0 2007-04-26 17:06 sources.list~
drwxr-xr-x 2 root root 4096 2007-02-26 15:53
sources.list.d
-rw-r--r-- 1 root root 506 2007-04-30 19:32
sources.list.save
-rw--- 1 root root 1200 2007-08-13 19:50 trustdb.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg~
[EMAIL PROTECTED]:~$ cd /etc/apt/apt.conf.d/
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ ll
total 16
-rw-r--r-- 1 root root 40 2007-04-26 17:06 00trustcdrom
-rw-r--r-- 1 root root 92 2007-07-02 07:07 01autoremove
-rw-r--r-- 1 root root 91 2007-04-30 19:32 10periodic
-rw-r--r-- 1 root root 182 2006-12-20 13:31 70debconf
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 00trustcdrom
APT::Authentication::TrustCDROM true;
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 01autoremove
APT
{
NeverAutoRemove
{
^linux-image.*;
^linux-restricted-modules.*;
};
};
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 10periodic
APT::Periodic::Update-Package-Lists 1;
APT::Periodic::Download-Upgradeable-Packages 0;
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat 70debconf
// Pre-configure all packages with debconf before they are installed.
// If you don't like it, comment it out.
DPkg::Pre-Install-Pkgs {/usr/sbin/dpkg-preconfigure --apt || true;};
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$
Thanks, Don
On Sun, 13 Jan 2008, Douglas A. Tutty wrote:
Date: Sun, 13 Jan 2008 23:13:25 -0500
From: Douglas A. Tutty [EMAIL PROTECTED]
To: debian-amd64@lists.debian.org
Subject: Re: apt-get problem
Resent-Date: Mon, 14 Jan 2008 04:13:47 + (UTC)
Resent-From: debian-amd64@lists.debian.org
On Sun, Jan 13, 2008 at 07:43:22PM -0600, Don Montgomery wrote:
I looked at the apt-get howto located at
http://www.debian.org/doc/manuals/apt-howto/ch-basico.en.html#s-sources.list
and grabbed some additional lines for my
/etc/apt/sources.list file, which now reads:
---
however, when I run apt-get update, I still get no joy,
and a lot of lines like:
Failed to fetch
http://debian.uchicago.edu/debian/dists/testing/Release.gpg
Could not connect to localhost:4001 (127.0.0.1). - connect
(111 Connection refused)
Any ideas what is happening?
Still looks like its trying to connect to a proxy at localhost port
4001. Give us your /etc/apt/apt.conf and any files under
/etc/apt/apt.conf.d
Doug.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel module eeprom causing system freeze
On Mon, Jan 14, 2008 at 08:58:25AM +1100, Dean Hamstead wrote: after a circuit breaker caused a power outage, which reset the bios. debian is now freezing (solid) at 'Loading kernel module eeprom'. Power loss should never reset the BIOS. A power surge perhaps, or a defective motherboard could. I have tended to the bios and reset to optimized, fail safe etc. Prior to the power outage there wasnt anything fancy in the bios settings regardless. I have tried booting the current and the two prior kernels with the same results. Any thoughts? Well eeprom is the I2C eeprom driver, so I would guess one of your I2C controllers is broken. Often found on the motherboard and the video card among others. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, Jan 14, 2008 at 10:02:33AM -0600, Don Montgomery wrote: Wow, a lot of output, but I suspect the first few lines tell the tale: [EMAIL PROTECTED]:/etc/apt/apt.conf.d# env|grep 4001 http_proxy=http://localhost:4001 HTTP_PROXY=http://localhost:4001 [EMAIL PROTECTED]:/etc/apt/apt.conf.d# grep 4001 -r /etc/ grep: /etc/alternatives/javac: No such file or directory /etc/rc1.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc5.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc4.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/popularity-contest.conf:MY_HOSTID=f763d78f15bb4001b5315c9e2423a993 /etc/rc3.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc0.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc6.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/environment:HTTP_PROXY=http://localhost:4001 # +ANON_MARK+ /etc/environment:http_proxy=http://localhost:4001 # +ANON_MARK+ So that there just set an entironment variable making most programs that are properly written try to use it as a proxy. apt is properly written so it does as it is told and tries to use your proxy. Now the question is why does your proxy not work. I also see the anon-proxy script in rc#.d and init.d apparently providing a proxy on that port. Maybe it's misconfigured or it simply doesn't work. So either fix the proxy so it works, or stop using it as a global proxy setting and only enable it for those programs where it actually works. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
weired message
Hi all, after the last update I get some strange messages in stdout during boot: no file /var/lib/misc/service.db or no file /var/lib/misc/protocol.db I guess, this belongs to libnss-db (please correct me, if I am wrong!) and I suppose, these are databases. Can I generate these databases manually ? and how do I have to do it ? I suppose it is makedb , but I am not sure. regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
Wow, a lot of output, but I suspect the first few lines
tell the tale:
[EMAIL PROTECTED]:/etc/apt/apt.conf.d# env|grep 4001
http_proxy=http://localhost:4001
HTTP_PROXY=http://localhost:4001
[EMAIL PROTECTED]:/etc/apt/apt.conf.d# grep 4001 -r /etc/
grep: /etc/alternatives/javac: No such file or directory
/etc/rc1.d/K20anon-proxy:[ -z $PORT ] PORT=4001
/etc/rc5.d/S20anon-proxy:[ -z $PORT ] PORT=4001
/etc/rc4.d/S20anon-proxy:[ -z $PORT ] PORT=4001
/etc/popularity-contest.conf:MY_HOSTID=f763d78f15bb4001b5315c9e2423a993
/etc/rc3.d/S20anon-proxy:[ -z $PORT ] PORT=4001
/etc/rc0.d/K20anon-proxy:[ -z $PORT ] PORT=4001
/etc/rc6.d/K20anon-proxy:[ -z $PORT ] PORT=4001
/etc/environment:HTTP_PROXY=http://localhost:4001 # +ANON_MARK+
/etc/environment:http_proxy=http://localhost:4001 # +ANON_MARK+
/etc/udev/libsane.rules:SYSFS{idVendor}==04b0, SYSFS{idProduct}==4001, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
/etc/udev/libsane.rules:# Artec/Ultima 1236 USB | Artec/Ultima Ultima 2000
(0x4001)
/etc/udev/libsane.rules:SYSFS{idVendor}==05d8, SYSFS{idProduct}==4001, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
/etc/udev/rules.d/025_libsane.rules:SYSFS{idVendor}==04b0, SYSFS{idProduct}==4001, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
/etc/udev/rules.d/025_libsane.rules:# Artec/Ultima 1236 USB | Artec/Ultima
Ultima 2000 (0x4001)
/etc/udev/rules.d/025_libsane.rules:SYSFS{idVendor}==05d8, SYSFS{idProduct}==4001, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
/etc/mime-magic:0 beshort 054001 370 sysV pure executable
/etc/mime-magic:0 beshort 0x4001 MIPSEB-LE MIPS-III COFF
executable
/etc/default/anon-proxy:PORT=4001
/etc/default/nfs-common:# this variable to a statd argument like: --port 4000
--outgoing-port 4001.
/etc/selinux/refpolicy-targeted/contexts/netfilter_contexts:-A
selinux_new_input -p udp --dport 64001 -j SECMARK --selctx
system_u:object_r:traceroute_server_packet_t:s0
/etc/selinux/refpolicy-targeted/contexts/netfilter_contexts:-A selinux_new_output -p udp --dport 64001 -j SECMARK --selctx system_u:object_r:traceroute_client_packet_t:s0 Binary file
/etc/selinux/refpolicy-targeted/modules/previous/base.linked matches
/etc/selinux/refpolicy-targeted/modules/previous/netfilter_contexts:-A
selinux_new_input -p udp --dport 64001 -j SECMARK --selctx
system_u:object_r:traceroute_server_packet_t:s0
/etc/selinux/refpolicy-targeted/modules/previous/netfilter_contexts:-A selinux_new_output -p udp --dport 64001 -j SECMARK --selctx system_u:object_r:traceroute_client_packet_t:s0 Binary file
/etc/selinux/refpolicy-targeted/modules/previous/base.pp matches Binary file
/etc/selinux/refpolicy-targeted/modules/active/base.linked matches
/etc/selinux/refpolicy-targeted/modules/active/netfilter_contexts:-A
selinux_new_input -p udp --dport 64001 -j SECMARK --selctx
system_u:object_r:traceroute_server_packet_t:s0
/etc/selinux/refpolicy-targeted/modules/active/netfilter_contexts:-A selinux_new_output -p udp --dport 64001 -j SECMARK --selctx system_u:object_r:traceroute_client_packet_t:s0 Binary file
/etc/selinux/refpolicy-targeted/modules/active/base.pp matches
/etc/kde3/kdebug.areas:24001 Quanta (parser)
/etc/kde3/kdebug.areas:34001klyx
/etc/kde3/kdebug.areas:44001KexiDB (driver impl)
/etc/init.d/anon-proxy:[ -z $PORT ] PORT=4001
/etc/rc2.d/S20anon-proxy:[ -z $PORT ] PORT=4001
[EMAIL PROTECTED]:/etc/apt/apt.conf.d#
--Don
On Mon, 14 Jan 2008, Lennart Sorensen wrote:
Date: Mon, 14 Jan 2008 09:54:41 -0500
From: Lennart Sorensen [EMAIL PROTECTED]
To: Don Montgomery [EMAIL PROTECTED]
Cc: Douglas A. Tutty [EMAIL PROTECTED], debian-amd64@lists.debian.org
Subject: Re: apt-get problem
Resent-Date: Mon, 14 Jan 2008 14:54:56 + (UTC)
Resent-From: debian-amd64@lists.debian.org
On Mon, Jan 14, 2008 at 08:38:59AM -0600, Don Montgomery wrote:
Here is what I found:
[EMAIL PROTECTED]:~$ less /etc/apt/apt.conf
/etc/apt/apt.conf: No such file or directory
[EMAIL PROTECTED]:~$ ll /etc/apt
total 40
drwxr-xr-x 2 root root 4096 2007-11-25 14:28 apt.conf.d
-rw-r--r-- 1 root root 2524 2006-11-14 08:43 apt-file.conf
-rw--- 1 root root0 2007-04-26 17:06 secring.gpg
-rw-r--r-- 1 root root 952 2008-01-13 19:35 sources.list
-rw-r--r-- 1 root root0 2007-04-26 17:06 sources.list~
drwxr-xr-x 2 root root 4096 2007-02-26 15:53
sources.list.d
-rw-r--r-- 1 root root 506 2007-04-30 19:32
sources.list.save
-rw--- 1 root root 1200 2007-08-13 19:50 trustdb.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg
-rw--- 1 root root 4148 2007-08-13 19:50 trusted.gpg~
[EMAIL PROTECTED]:~$ cd /etc/apt/apt.conf.d/
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ ll
total 16
-rw-r--r-- 1 root root 40 2007-04-26 17:06 00trustcdrom
-rw-r--r-- 1 root root 92 2007-07-02 07:07 01autoremove
-rw-r--r-- 1 root root 91 2007-04-30 19:32 10periodic
-rw-r--r-- 1 root root 182 2006-12-20 13:31 70debconf
[EMAIL PROTECTED]:/etc/apt/apt.conf.d$ cat
Re: kernel module eeprom causing system freeze
On Monday 14 Jan 2008, Lennart Sorensen wrote: On Mon, Jan 14, 2008 at 08:58:25AM +1100, Dean Hamstead wrote: after a circuit breaker caused a power outage, which reset the bios. debian is now freezing (solid) at 'Loading kernel module eeprom'. Power loss should never reset the BIOS. A power surge perhaps, or a defective motherboard could. If the lithium battery on the motherboard is defective, then CMOS settings can be lost with a power failure. However, modern motherboards will be able to determine that the CMOS memory has become corrupt and will automatically adopt working (though probably sub-optimal) settings if this happens. Note that a duff motherboard battery sometimes fails to manifests itself, because most people leave their PC plugged into the wall all the time. As long as the PC is plugged into the mains, the switch on the wall socket is on and the electricity meter is in credit, the PSU will supply standby power to the motherboard and the lithium battery will not be used. Most PCs are plugged into extension leads which do not have separate switches for each socket; which are then plugged into inconveniently-located wall sockets whose switches stay ON all the time. -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mute key not working anymore on T61
Hi all, Since a few days (weeks?), my mute key does not work anymore. Volume up and down work as expected. xev just says nothing while pressing this key. I reported this here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460564 However, I can't remember if the mute key used to generate an ACPI event or was monitored by thinkpad-keys!? Dear Lenovo T61 users, do you have a working mute key under unstable? Thanks, Cyril Jaquier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? Thanks, Don On Mon, 14 Jan 2008, Lennart Sorensen wrote: Date: Mon, 14 Jan 2008 11:25:10 -0500 From: Lennart Sorensen [EMAIL PROTECTED] To: Don Montgomery [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org Subject: Re: apt-get problem On Mon, Jan 14, 2008 at 10:02:33AM -0600, Don Montgomery wrote: Wow, a lot of output, but I suspect the first few lines tell the tale: [EMAIL PROTECTED]:/etc/apt/apt.conf.d# env|grep 4001 http_proxy=http://localhost:4001 HTTP_PROXY=http://localhost:4001 [EMAIL PROTECTED]:/etc/apt/apt.conf.d# grep 4001 -r /etc/ grep: /etc/alternatives/javac: No such file or directory /etc/rc1.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc5.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc4.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/popularity-contest.conf:MY_HOSTID=f763d78f15bb4001b5315c9e2423a993 /etc/rc3.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc0.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc6.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/environment:HTTP_PROXY=http://localhost:4001 # +ANON_MARK+ /etc/environment:http_proxy=http://localhost:4001 # +ANON_MARK+ So that there just set an entironment variable making most programs that are properly written try to use it as a proxy. apt is properly written so it does as it is told and tries to use your proxy. Now the question is why does your proxy not work. I also see the anon-proxy script in rc#.d and init.d apparently providing a proxy on that port. Maybe it's misconfigured or it simply doesn't work. So either fix the proxy so it works, or stop using it as a global proxy setting and only enable it for those programs where it actually works. -- Len Sorensen -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Corrupted Gnome terminal
From: Jack Schneider [EMAIL PROTECTED] Date: Mon, Jan 14, 2008 at 08:02:28AM -0600 Hi, all I screwed up my Gnome Terminal setup some how... on my workstation desktop. My system: Debian Lenny Kernel: 2.6.22-3-amd64 Video: Nvidia 8600 GT Video Drv. NVIDIA 169.07 My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. Thanks, in advance.. Jack If you remove the package (apt-get remove --purge) and then reinstall it, does it disappear? If not, what I'd do is compare strace logs of Gnome terminal for the user where it isn't OK and the strace logs of Gnome terminal for the user where it is OK, or find all files including hidden files changed in the last week or so starting from ~ and guessing which one interacts with Gnome terminal. Good luck, Jurriaan -- Morwatz said fretfully, Why are you so interested in the mannerisms of the race? Tonight, they intend to eat us . . . Jack Vance - Big Planet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Corrupted Gnome terminal
On Mon, 2008-01-14 at 08:02 -0600, Jack Schneider wrote: --snip-- My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. A good place to start would be to take a look at the gconf settings for gnome-terminal, specifically /apps/gnome-terminal. If you don't mind losing any settings for it, you can do: gconftool-2 --recursive-unset /apps/gnome-terminal However, as you've mentioned you're having difficulties closing the program, I'd be inclined to think that the problem might lie with another application in your session. Try logging into a failsafe xterm session and starting up just your WM and gnome-terminal. Something along the lines of: [EMAIL PROTECTED]:~$ metacity [EMAIL PROTECTED]:~$ gnome-terminal And then see what happens. Doing it this way will allow you to determine if the fault lies with another program that's running in your session. Hope that helps. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: Corrupted Gnome terminal
On Mon, 2008-01-14 at 13:41 -0800, Alex Malinovich wrote: On Mon, 2008-01-14 at 08:02 -0600, Jack Schneider wrote: --snip-- My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. A good place to start would be to take a look at the gconf settings for gnome-terminal, specifically /apps/gnome-terminal. If you don't mind losing any settings for it, you can do: gconftool-2 --recursive-unset /apps/gnome-terminal However, as you've mentioned you're having difficulties closing the program, I'd be inclined to think that the problem might lie with another application in your session. Try logging into a failsafe xterm session and starting up just your WM and gnome-terminal. Something along the lines of: [EMAIL PROTECTED]:~$ metacity [EMAIL PROTECTED]:~$ gnome-terminal And then see what happens. Doing it this way will allow you to determine if the fault lies with another program that's running in your session. Hope that helps. Thanks for the reply, Below is the output of the metacity command: [EMAIL PROTECTED]:~$ metacity [1] 5844 [EMAIL PROTECTED]:~$ Window manager warning: AltButton3 found in configuration d atabase is not a valid value for keybinding activate_window_menu Window manager warning: AltButton1 found in configuration database is not a valid value for keybinding begin_move Window manager warning: AltButton2 found in configuration database is not a valid value for keybinding begin_resize Also when I started gnome-terminal from that point it gave me a completely working terminal... I tried to capture the profile as the default and restarted my normal login... No Improvemnt The above looks like somthing to work on..??? What next Coach??? Thanks, Alex.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Corrupted Gnome terminal
On Mon, 2008-01-14 at 13:41 -0800, Alex Malinovich wrote: On Mon, 2008-01-14 at 08:02 -0600, Jack Schneider wrote: --snip-- My Problems: Gnome terminal has unreadable fonts..TOO small. The terminal will not close, when clicking on X, and cntrl++ will not work. Xterm seems to work. OK /var/log/Xorg.0.log has one failure: (EE) Failed to load module type1 (module does not exist, 0) I created a new user, and the Gnome terminal on that Desktop works normally..OK So it seems I have a hidden file screwed up on my desktop... Anyone have a idea what folder i should replace??? or what/where I should look or go from here??? I have been struggling for several days and come up blank from Archive and Google. A good place to start would be to take a look at the gconf settings for gnome-terminal, specifically /apps/gnome-terminal. If you don't mind losing any settings for it, you can do: gconftool-2 --recursive-unset /apps/gnome-terminal However, as you've mentioned you're having difficulties closing the program, I'd be inclined to think that the problem might lie with another application in your session. Try logging into a failsafe xterm session and starting up just your WM and gnome-terminal. Something along the lines of: [EMAIL PROTECTED]:~$ metacity [EMAIL PROTECTED]:~$ gnome-terminal And then see what happens. Doing it this way will allow you to determine if the fault lies with another program that's running in your session. Hope that helps. Thanks, Alex I'll try that in a few hours... Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Corrupted Gnome terminal
On Mon, 2008-01-14 at 17:01 -0600, Jack Schneider wrote: --snip-- Below is the output of the metacity command: [EMAIL PROTECTED]:~$ metacity [1] 5844 [EMAIL PROTECTED]:~$ Window manager warning: AltButton3 found in configuration d atabase is not a valid value for keybinding activate_window_menu Window manager warning: AltButton1 found in configuration database is not a valid value for keybinding begin_move Window manager warning: AltButton2 found in configuration database is not a valid value for keybinding begin_resize These are just warnings. If you're so inclined you can try fixing them up later, but they shouldn't matter for the current problem at least. Also when I started gnome-terminal from that point it gave me a completely working terminal... I tried to capture the profile as the default and restarted my normal login... No Improvemnt Well, this tells us that, most likely, the problem doesn't lie with gnome-terminal itself, but rather with some other application that's running in your session. The next step would be to try to log into a failsafe gnome session and see if it works there. That'll just start up gnome with none of your personal settings applied. If it works fine there, then it's time to start really digging. At that point, you can try the strace approach that Jurriaan mentioned and see if it helps. If you have a conflict with another program the strace should show you where the problem lies (if you can read the output that is. It's a bit of an acquired skill...) p.s. I'm subscribed to the list so you don't have to do a Reply To All when responding. As it looks like you're using Evolution you can just do Reply to List (Ctrl+L is the default, I believe), and it will take care of the rest for you. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: apt-get problem
On Mon, 14 Jan 2008, Douglas A. Tutty wrote: Date: Mon, 14 Jan 2008 13:47:51 -0500 From: Douglas A. Tutty [EMAIL PROTECTED] To: debian-amd64@lists.debian.org Subject: Re: apt-get problem Resent-Date: Mon, 14 Jan 2008 18:58:30 + (UTC) Resent-From: debian-amd64@lists.debian.org On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. my apologies Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Don Doug. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: Date: Mon, 14 Jan 2008 13:47:51 -0500 From: Douglas A. Tutty [EMAIL PROTECTED] To: debian-amd64@lists.debian.org Subject: Re: apt-get problem Resent-Date: Mon, 14 Jan 2008 18:58:30 + (UTC) Resent-From: debian-amd64@lists.debian.org On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. my apologies Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Don Is that supposed to be funny? Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. my apologies Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Don Is that supposed to be funny? no Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? Thanks, Don Doug. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On 1/14/08, Don Montgomery [EMAIL PROTECTED] wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. my apologies Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Don Is that supposed to be funny? no Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? 1.- did you install this machine by yourself? let me explain, the proxy configuration and app (just a guess anon-proxy see http://packages.debian.org/anon-proxy) don't appear by himself in your machine... but if you don't install it then you mustn't remove the package beacuse could be really well configured... 2.- did you could be able to use any other net tool (e.j. iceweasel) 3.- could you simply reinstall to avoid the problem? good luck... Thanks, Don Doug. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
Re: apt-get problem
Don Montgomery([EMAIL PROTECTED]) is reported to have said: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: --snip-- Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? dpkg -l *proxy* |grep ^i should get you what you need. WT -- Adding manpower to a late software project makes it later. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On 1/14/08, Wayne Topa [EMAIL PROTECTED] wrote: Don Montgomery([EMAIL PROTECTED]) is reported to have said: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: --snip-- Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? dpkg -l *proxy* |grep ^i should get you what you need. /etc/rc1.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc5.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc4.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/popularity-contest.conf:MY_HOSTID=f763d78f15bb4001b5315c9e2423a993 /etc/rc3.d/S20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc0.d/K20anon-proxy:[ -z $PORT ] PORT=4001 /etc/rc6.d/K20anon-proxy:[ -z $PORT ] PORT=4001 If you are shure to remove the proxy just type dpkg --purge anon-proxy WT -- Adding manpower to a late software project makes it later. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
Re: apt-get problem
On Mon, Jan 14, 2008 at 06:49:26PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? stop top posting. my apologies Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? This isn't a KDE thing. What package manager do you use? E.g. aptitude, apt-get, dselect... Then use its search function and look for installed packages with the word proxy in the description. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On Mon, Jan 14, 2008 at 07:02:45PM -0600, Jaime Ochoa Malag?n wrote: On 1/14/08, Don Montgomery [EMAIL PROTECTED] wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? 1.- did you install this machine by yourself? let me explain, the proxy configuration and app (just a guess anon-proxy see http://packages.debian.org/anon-proxy) don't appear by himself in your machine... but if you don't install it then you mustn't remove the package beacuse could be really well configured... 2.- did you could be able to use any other net tool (e.j. iceweasel) 3.- could you simply reinstall to avoid the problem? If he is the system admin, he should know if he installed or set up the machine. If he isn't, then he shouldn't reinstall or install packages. If he didn't install the system but is now the sysadmin, then he needs to learn to use a package manager sooner or later. Reinstalling to avoid removing a proxy seems overkill. This is debian. You should only need to reinstall for a failed disk in a non-raid system. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-get problem
On 1/14/08, Douglas A. Tutty [EMAIL PROTECTED] wrote: On Mon, Jan 14, 2008 at 07:02:45PM -0600, Jaime Ochoa Malag?n wrote: On 1/14/08, Don Montgomery [EMAIL PROTECTED] wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: For discontinuing the proxy, I guess I can go into /etc/rc*.d/* and comment out all the lines mentioning port 4001; would reboot be necessary after that? Otherwise, how would one go about fixing the proxy so that it does work? Debian doesn't proxy by default so you must have a proxy package installed. If you don't want it, remove it. that sounds like a good idea; perhaps I could google up proxy package and find out what might be there? Use whatever package management tools you usually use and see what proxy packages you have installed. Then delete it. KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? 1.- did you install this machine by yourself? let me explain, the proxy configuration and app (just a guess anon-proxy see http://packages.debian.org/anon-proxy) don't appear by himself in your machine... but if you don't install it then you mustn't remove the package beacuse could be really well configured... 2.- did you could be able to use any other net tool (e.j. iceweasel) 3.- could you simply reinstall to avoid the problem? If he is the system admin, he should know if he installed or set up the machine. If he isn't, then he shouldn't reinstall or install packages. Thats the point... If he didn't install the system but is now the sysadmin, then he needs to learn to use a package manager sooner or later. I hope sooner... Reinstalling to avoid removing a proxy seems overkill. This is debian. I agree, but he should learn to use it, or perhaps all the configuration need to be ajusted to the new sysadmin (in a laptop scenario primarily) You should only need to reinstall for a failed disk in a non-raid system. Isn't it beautifull? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Perhaps the depth of love can be calibrated by the number of different selves that are actively involved in a given relationship. Carl Sagan (Contact) Jaime Ochoa Malagón Integrated Technology Tel: (55) 52 54 26 10
Re: apt-get problem
On Mon, 14 Jan 2008, Jaime Ochoa Malagón wrote: On 1/14/08, Don Montgomery [EMAIL PROTECTED] wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 05:39:04PM -0600, Don Montgomery wrote: On Mon, 14 Jan 2008, Douglas A. Tutty wrote: On Mon, Jan 14, 2008 at 11:50:58AM -0600, Don Montgomery wrote: KDE Control Center lists Proxy as connect to the Internet directly Is there another way to find out what I need to know? 1.- did you install this machine by yourself? let me explain, the proxy configuration and app (just a guess anon-proxy see http://packages.debian.org/anon-proxy) don't appear by himself in your machine... but if you don't install it then you mustn't remove the package beacuse could be really well configured... I did a netinstall a while back. About a month ago, I dist-upgraded to lenny---I guess that was about the time this started. 2.- did you could be able to use any other net tool (e.j. iceweasel) Yes, iceweasel, konqueror, and galeon all work fine, even now. apt-get worked fine too, until the dist-upgrade. 3.- could you simply reinstall to avoid the problem? I certainly will, if I cannot find another way to deal with it. good luck... Thanks. I really appreciate all the great work that the folks on this list have done for this port. Don Thanks, Don Doug. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] --
