Re: Skype after ia32-libs update?
Doesn't look like a bug to me. More likely a pbkac. The web site's error is clear: 404 page not found. This usually indicates that the looked for page could not be found (what a surprise!). Possibly your apt-get configuration file is wrong, or possibly that the page is actually gone from Skype's website. On 6 Jul, 2009, at 15:27, David wrote: Thank you. I followed your steps, even after deleting /etc/ia32-apt and reinstalling ia32-apt-get (as the former directory did not update its sources.list's). But I am afraid that it does not work yet: # apt-get update [...] W: Failed to fetch http://download.skype.com/linux/repos/debian/dists/stable/non-free/binary-amd64/Packages 404 Not Found E: Some index files failed to download, they have been ignored, or old ones used instead. # apt-get install skype Reading package lists... Done Building dependency tree Reading state information... Done Package skype is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package skype has no installation candidate I am using the latest versions of all the packages. Should I file a bug report? Thank you, David Please Cc to me if replying -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: IPTables allow ping.
I haven't checked your rules, but if you have a modem/router (dsl or other), is configured to allow all icmp ? (just to be sure of course) Ernest On 13 Jun, 2008, at 21:29, Bharath Ramesh wrote: I have a debian amd64 box. I am writing a set of firewall rules. I want to be able to ping my machine from outside. I wrote the following rule. I am still unable to ping my machine from outside. Could someone verify that my rule is correct. # Allow to/be ping(ed). $IPT --append INPUT --in-interface $EXTIF --protocol icmp --icmp- type 0 \ --destination $EXTIP --match state --state NEW,ESTABLISHED,RELATED \ --jump ACCEPT $IPT --append INPUT --in-interface $EXTIF --protocol icmp --icmp- type 8 \ --destination $EXTIP --match state --state NEW,ESTABLISHED,RELATED \ --jump ACCEPT $IPT --append OUTPUT --out-interface $EXTIF --protocol icmp --icmp- type 0 \ --source $EXTIP --match state --state NEW,ESTABLISHED,RELATED \ --jump ACCEPT $IPT --append OUTPUT --out-interface $EXTIF --protocol icmp --icmp- type 8 \ --source $EXTIP --match state --state NEW,ESTABLISHED,RELATED \ --jump ACCEPT I am able to ping other m/c from my m/c but I am not able to ping from outside. Thanks, Bharath --- Bharath Ramesh <[EMAIL PROTECTED]> http://people.cs.vt.edu/~bramesh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot screen
On 25 May, 2008, at 02:20, Alex Samad wrote: silly question did you run update-grub That would not do anything usefull and may harm if you update the menu.lst file by hand. update-grub is used to update that file, and will overwrite anything added by hand. The vga kernel parameter is a bit illogical. vga=ask will give you a list of possible modes. This is done using two numbers, one is the selection number, the other one is the mode as it is known to the VGA BIOS. The one you want is the selection number, not the mode (0F07 was the mode) Then replace the "ask" with that number. Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: libsc7_2.3.1-3_amd64.deb problems
On 6 May, 2008, at 19:04, Francesco Pietra wrote: ___ Well, from present information is it possible to indicate how to remove those files/scripts that generate the error messages, and let lenny do upgrading correctly? Someone has kindly suggested to carry out again a dist-upgrade, though I suspect that with my system the final outcome would be the same. Thanks francesco pietra If you don't need the package anyway, why don't you simply remove it/ them? #> apt-get remove libsc8 libsc7 libsc-dev Might do the trick. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sensors
On 28 Apr, 2008, at 10:51, A J Stiles wrote: Have you tried hacking this Superdoctor to not need GNOME? Presumably it has a bunch of functions at its core that do low-level stuff with the motherboard; if so then all you need to do is chop out everything but them, and create a new main() with just a hard-coded series of calls to set up just the parameters you want the way you want them and/or display statuses on STDOUT. It's ugly, but if it won't be needed often then it might well do the job. The README.txt that comes with superdoctor already mentions a 'sdt' utility which does not require a gui. Ernest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Watchdog
Don't bother. The watchdog only triggers if it is enabled within the kernel (module loaded) and activated by an application. Unless you install such an application and give it the privilege to use the watchdog, nothing will ever happen. As said earlier, if a system is in a difficult to reach place, a watchdog can be _very_ useful. Ernest On 11 Apr, 2008, at 12:28, Francesco Pietra wrote: Hi Giacomo I am going to change the jumper settings in order to disable watchdog. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel: APIC error on CPU0: 40(40)
On 11 Apr, 2008, at 04:12, Karl Schmidt wrote: Apr 10 10:54:02 poland kernel: APIC error on CPU0: 40(40) I see this every once in a while - no problems with the server and others on the web see it only on amd64. Any kernel gurus know exactly what this means? Receive Illegal Vector. From what I understand it means your motherboard's apic is sending invalid io vectors to the cpu Unfortunately it means a crappy motherboard more often than hardware failure. Possibly you could look for and install a bios upgrade (since the apic is set up by the bios). If it bothers you too much, you can run without the apic with kernel parameter noapic at the cost of some speed. Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ISO md5sum signing paranoia
On Friday 30 September 2005 10:08, vitko wrote: > > The idea is that either YOU meet these people, or that somebody you trust > > did it for you, or that somebody you trust knows somebody he trusts who > > knows this trusty gal, who had a relation with a bloke, who met the guy > > at this congress wich he now trusts. > > Yes, that is the idea of signing the keys by CA. It seems gpg supports > this: > > > gpg: WARNING: This key is not certified with a trusted signature! > > > Does it mean that the key is certified, but I miss key of certificator; > then I'd like to know where to get this certificate authority key; OR does > it mean this key is not certified at all? no and no. The key might be certified (trusted) by somebody, however the warning above indicates gpg cannot find a web of trust in _your_ key ring leading to anything that leads to any key that _you_ declared to trust. There is no CA for this. Beside how come you trust any of these supposed CA ? Do you know them ? are they indeed trustworthy ? (sorry I'm a bit paranoid there, but you asked for it ;o) gpg 's web of trust doesn't work with the self appointed Certificate "Authorities" (yes, these literally appeared out of the blue!). gpg expects you to meet people and build a web of trust with them. Of course that is the theory. What I did (and this is the part I'm not supposed to tell you) is over the years declare a few keys marginaly trusted after having seen them coming again and again with emails and packages. After a relatively short time the system started to trust some other keys from new emails and new packages. Cheers, Ernest ter Kuile. > > Vit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ISO md5sum signing paranoia
On Thursday 29 September 2005 18:54, vitko wrote: > I'm reinventing the wheel while learnig abou Debian key signing, so far > I've been able to verify sarge-amd64 DVD iso images via > > $ gpg --verify MD5SUMS.sign MD5SUMS > gpg: Signature made Mon 13 Jun 2005 10:48:17 PM CEST using DSA key ID > F6A32A8E gpg: Good signature from "Santiago Garcia Mantinan (manty) > <[EMAIL PROTECTED]>" gpg: aka "Santiago Garcia Mantinan > (manty) > <[EMAIL PROTECTED]>" gpg: aka "Santiago Garcia Mantinan > (manty) <[EMAIL PROTECTED]>" gpg: WARNING: This key is not certified with a > trusted signature! > gpg: There is no indication that the signature belongs to the > owner. Primary key fingerprint: 3F0A 12FC 0B55 A917 D791 82D3 72FD C205 > F6A3 2A8E > > I'd like to know how to get rid of warning above. So far I've imported the > whole Debian keyring gpg just works this way. Why would you trust these keys until you met those people yourself ? The idea is that either YOU meet these people, or that somebody you trust did it for you, or that somebody you trust knows somebody he trusts who knows this trusty gal, who had a relation with a bloke, who met the guy at this congress wich he now trusts. Thats what the web of trust is about. Of course, if you implicitly and blindly trust those keys to belong to the people they claim to belong to, you could declare them to be trusted or sing them with your own private key. You can either use gpg for that directly (see help, look for edit-key and then trust or sign) or, easier, use kgpg for a friendlier interface. but ... do you really trust those keys ? > > Thanks for any enlightement. hopefully it helped. Ernest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: offtopic "general" help with system clock
I think it's best not to install package adjtimex along ntp as they try to do the same thing (keep the system on time). ntp server will indeed no set the time if it's way off. However, Setting the time to a wild approximation (+/- 1 hour) of the current time is usually enough for ntp to start. Setting the time by hand can be done by running date as root with appropriate params (see date --help) or using ntpdate at startup once system time is set correctly, you can use hwclock to copy system time to Hardware on shutdown, and read it back on boot. Cheers, Ernest. On Friday 29 October 2004 07:07, Stephen Waters wrote: > OK, so if your system clock is way off and NTP doesn't work, try this > before blaming hardware: > > 1) delete /etc/adjtime > 2) run /etc/init.d/hwclock.sh > 3) run adjtimexconfig > 4) run ntpdate > 5) run /etc/init.d/ntp-server start > > Turns out my adjtime was way off due to a bad clock on the previous box > this hard drive was in. > > Cheers, > -s
no more sound after starting KDE
Bafling problem with kde, and probably arts system Before starting kdm I can play any sound (using alsa) without trouble, as can anybody in the audio group . after starting up KDE and logging in there is no more sound and the arts sound server keeps telling me my cpu is in overload. The only way to get any sound after logging in, is to run alsaconfig as root from a terminal, and after that, everything works again, even though I still get every few minutes the sound server cpu overload message. So I expected to find something in the Control server -> Sound & Multimedia -> Sound system, However: - most actions crash Knotify with a sig11 (probably because it tries to play a sound ;o). Most mysteriously, this still happens even after having reset the sound using alsaconf, - attempting to give real time priv. to the sound system tells me artswrapper is missing (it isn't); after alsa reset, this does works - I read someplace I must disable full duplex, however that was never enabled in the first place. In other words ... Running deb for amd64 ; using latest update from : deb http://bach.hpc2n.umu.se/pure64 sid main (half hour ago) User build kernel 2.6.9; but this happen also with deb kernels (as said above, sound works) most of kde is now 3.3.1, but this happend before with 3.3.0 This has never worked since new, clean, amd64 install about a month ago. I've been using debian testing with kde on K7 since about for ever without this problem. I tried comparing the current configuration with my old configuration, but it's hard because of the accumulated cruft from many years KDE upgrades. Beside, there does not seem to be an arts.something.something.conf anywhere underneath ~/.kde, nor does any file in there even contain the word "arts". As sound works again after alsaconfig, I suspect arts startup params. But where can I find those ? where else should I check ? Anybody seen this before ? Ernest ter Kuile.
Re: Newbie question - installation problems
I'm not sure this the best advis, but to solve this, I got rid of package debsig-verify. without this package verification isn't done, so all packages are installed regardless of sig. Don't know why sigs check fail. may be because the amd64 packages aren't signed by the authors. my reasoning was that this was experimental stuff anyway. Ernest. On Wednesday 20 October 2004 23:18, Ray Lanza wrote: > I've just installed debian on an athlon 64 machine using the netinstall > iso. I have my sources.list pointed towards debian-amd64.alioth.org/sarge/ > testing. > > Is this right? > > Many of the things I try to install fail authentication, is that expected? > > thanks, > ray
