Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
Am 16.04.20 um 17:18 schrieb Bernhard Schmidt: Am 16.04.20 um 17:11 schrieb sauro...@gmx.de: Hi, Well at least i thought that this would let me on Squeeze, but i was wrong Could you please rephrase your question? BTW, Squeeze is Debian 6 and out of LTS since 2016. I assume you mean Stretch aka Debian 9? Bernhard Yes Stretch was what i meant, sorry. I don´t have any further questions, at the beginning i was thinking that this bug prevent me from upgrading to Buster, but in fact it has nothing to do with it. Nevertheless i think when you upgrade from 9 to 10 the "sites-available" folder disappears on any machine which causes freeradius to not start. Best regards!
Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
Well at least i thought that this would let me on Squeeze, but i was wrong. I´ve did the upgrade to Buster today now on two machines, both with the following result. After upgrading freeradius wouldn´t start, so i looked into it and found out that somehow the folder: /etc/freeradius/3.0/sites-available was gone after the upgrade. Actually that caused the software to not start. I did a fresh Buster installation then, copied the folder and files to my old machines, changed the owner of the folder to "freerad" and now it´s up and running again. Im not really qualified i think to answer your question and though as you can read im not an Freeradius expert. Thanks for your input!
Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration
On Mon, 14 Jan 2019 08:48:03 -0500 Sam Hartman wrote: > > "Michael" == Michael Stapelberg writes: > I really don't think I'm going to be able to provide more on this prior > to the buster release. I'm struggling trying to get through my own list > of things to fix in my packages. > Is there any news on this? This bug keeps my last important machines i have here on Squeeze, unfortunately.
Bug#622277: Solved
Hi, I solved it by renaming the acpi-cpufreq.ko kernel module. Now the CPU has the full power. So it seems that there is something wrong with this module. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622277: cpufrequtils: CPUs always run on lowest speed
Hi, here ist what lsmod says: #lsmod | grep cpu cpufreq_conservative12987 0 cpufreq_stats 12762 0 cpufreq_userspace 12520 0 cpufreq_powersave 12422 0 acpi_cpufreq 12807 1 mperf 12421 1 acpi_cpufreq processor 27792 1 acpi_cpufreq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622277: cpufrequtils: CPUs always run on lowest speed
Hi, yes I have tried to set it manually, but with no good results. This ist the output from the OpenSuse LiveCD. # cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Bitte melden Sie Fehler an http://bugs.opensuse.org. analysiere CPU 0: Treiber: acpi-cpufreq Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 0 Die Taktfrequenz folgender CPUs werden per Software koordiniert: 0 Maximale Dauer eines Taktfrequenzwechsels: 10.0 us. Hardwarebedingte Grenzen der Taktfrequenz: 2.00 GHz - 3.00 GHz mögliche Taktfrequenzen: 3.00 GHz, 2.00 GHz mögliche Regler: conservative, userspace, powersave, ondemand, performance momentane Taktik: die Frequenz soll innerhalb 2.00 GHz und 2.00 GHz. liegen. Der Regler performance kann frei entscheiden, welche Taktfrequenz innerhalb dieser Grenze verwendet wird. momentane Taktfrequenz ist 3.00 GHz (verifiziert durch Nachfrage bei der Hardware). analysiere CPU 1: Treiber: acpi-cpufreq Folgende CPUs laufen mit der gleichen Hardware-Taktfrequenz: 1 Die Taktfrequenz folgender CPUs werden per Software koordiniert: 1 Maximale Dauer eines Taktfrequenzwechsels: 10.0 us. Hardwarebedingte Grenzen der Taktfrequenz: 2.00 GHz - 3.00 GHz mögliche Taktfrequenzen: 3.00 GHz, 2.00 GHz mögliche Regler: conservative, userspace, powersave, ondemand, performance momentane Taktik: die Frequenz soll innerhalb 2.00 GHz und 3.00 GHz. liegen. Der Regler ondemand kann frei entscheiden, welche Taktfrequenz innerhalb dieser Grenze verwendet wird. momentane Taktfrequenz ist 3.00 GHz (verifiziert durch Nachfrage bei der Hardware). and uname -r 3.1.0-1.2-desktop I found out that Debian has the exact same behaviour when I run 2.6.32-5-686 Kernel. He is not able to speed up both cores. Only if I type in cpufreq-set --max 3.0G he gives the full power to CPU0, as you can see above. Without that command (which does not work in Debian) CPU0 also runs with 2.0G. Greetings -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641114: soundconverter: Soundconverter terminates at
Hi again, I do have this problem in testing and unstable. I have just tested it on a new machine by installing soundcovnerter. Any recommendations about this? -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582368: evolution crashes when sending/forwarding email
Hi, I have opened a report here by myself jsut before I have seen this one here. Sorry for that, but I hope that this backtrace will help you somehow to help us :). gdb evolution GNU gdb (GDB) 7.0.1-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/evolution...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb2818b70 (LWP 6642)] [Thread 0xb2818b70 (LWP 6642) exited] [New Thread 0xb2818b70 (LWP 6643)] [New Thread 0xb2017b70 (LWP 6644)] [New Thread 0xb1816b70 (LWP 6645)] [Thread 0xb1816b70 (LWP 6645) exited] [New Thread 0xb1816b70 (LWP 6646)] [Thread 0xb1816b70 (LWP 6646) exited] [New Thread 0xb1816b70 (LWP 6647)] [New Thread 0xb0f45b70 (LWP 6648)] [New Thread 0xb0744b70 (LWP 6649)] [New Thread 0xafc86b70 (LWP 6650)] [Thread 0xafc86b70 (LWP 6650) exited] [New Thread 0xafc86b70 (LWP 6651)] [New Thread 0xaf3c5b70 (LWP 6652)] [New Thread 0xaebc4b70 (LWP 6653)] [Thread 0xaf3c5b70 (LWP 6652) exited] [Thread 0xafc86b70 (LWP 6651) exited] [New Thread 0xafc86b70 (LWP 6655)] [New Thread 0xaf3c5b70 (LWP 6656)] [New Thread 0xae35db70 (LWP 6657)] [New Thread 0xada5db70 (LWP 6658)] [New Thread 0xad25cb70 (LWP 6659)] [New Thread 0xad21bb70 (LWP 6661)] [New Thread 0xaca1ab70 (LWP 6664)] [New Thread 0xac219b70 (LWP 6665)] [New Thread 0xaba18b70 (LWP )] [Thread 0xaba18b70 (LWP ) exited] [Thread 0xaebc4b70 (LWP 6653) exited] [Thread 0xaca1ab70 (LWP 6664) exited] [Thread 0xad21bb70 (LWP 6661) exited] [New Thread 0xad21bb70 (LWP 6667)] [Thread 0xad21bb70 (LWP 6667) exited] [New Thread 0xad21bb70 (LWP 6668)] [Thread 0xad21bb70 (LWP 6668) exited] [New Thread 0xad21bb70 (LWP 6669)] [Thread 0xad21bb70 (LWP 6669) exited] [Thread 0xada5db70 (LWP 6658) exited] [New Thread 0xada5db70 (LWP 6670)] [Thread 0xae35db70 (LWP 6657) exited] [Thread 0xada5db70 (LWP 6670) exited] [New Thread 0xada5db70 (LWP 6671)] [Thread 0xada5db70 (LWP 6671) exited] [New Thread 0xada5db70 (LWP 6672)] [New Thread 0xae35db70 (LWP 6673)] [Thread 0xae35db70 (LWP 6673) exited] [Thread 0xada5db70 (LWP 6672) exited] [New Thread 0xada5db70 (LWP 6674)] [Thread 0xada5db70 (LWP 6674) exited] [New Thread 0xada5db70 (LWP 6677)] [New Thread 0xae35db70 (LWP 6678)] [Thread 0xae35db70 (LWP 6678) exited] [Thread 0xada5db70 (LWP 6677) exited] [New Thread 0xada5db70 (LWP 6679)] [Thread 0xada5db70 (LWP 6679) exited] [New Thread 0xada5db70 (LWP 6681)] [Thread 0xada5db70 (LWP 6681) exited] [New Thread 0xada5db70 (LWP 6683)] [Thread 0xada5db70 (LWP 6683) exited] [New Thread 0xada5db70 (LWP 6684)] [Thread 0xada5db70 (LWP 6684) exited] [New Thread 0xada5db70 (LWP 6685)] [Thread 0xada5db70 (LWP 6685) exited] [New Thread 0xada5db70 (LWP 6686)] [Thread 0xada5db70 (LWP 6686) exited] [Thread 0xac219b70 (LWP 6665) exited] [New Thread 0xac219b70 (LWP 6691)] [Thread 0xac219b70 (LWP 6691) exited] [New Thread 0xac219b70 (LWP 6692)] [Thread 0xac219b70 (LWP 6692) exited] [New Thread 0xac219b70 (LWP 6693)] [Thread 0xac219b70 (LWP 6693) exited] [New Thread 0xac219b70 (LWP 6694)] [Thread 0xac219b70 (LWP 6694) exited] [New Thread 0xac219b70 (LWP 6695)] [Thread 0xac219b70 (LWP 6695) exited] [New Thread 0xac219b70 (LWP 6696)] [Thread 0xac219b70 (LWP 6696) exited] [New Thread 0xac219b70 (LWP 6697)] [Thread 0xac219b70 (LWP 6697) exited] [New Thread 0xac219b70 (LWP 6698)] (evolution:6639): camel-WARNING **: Camel operation status stack non empty: [Thread 0xac219b70 (LWP 6698) exited] [New Thread 0xac219b70 (LWP 6701)] [Thread 0xac219b70 (LWP 6701) exited] [New Thread 0xac219b70 (LWP 6702)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb0744b70 (LWP 6649)] 0xb0fd9af5 in camel_exchange_utils_send_message (service=0x8876238, from=0xaea38600 priv...@leee.de, recipients=0xaea7cd80, message=0x, ex=0xb07441d0) at camel-exchange-utils.c:3005 3005camel-exchange-utils.c: Datei oder Verzeichnis nicht gefunden. in camel-exchange-utils.c Thank you! -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514703: (no subject)
Hello, the bug is also discribed here and as you can see here https://bugzilla.samba.org/show_bug.cgi?id=6021 it´s fixed in 3.2.8. Unfortunately I can´t install that version in Lenny because of some dependency with libldap2 which is not installable in Lenny. How to solve this now? The Maintainer of smbclient would like to fix or update smbclient or won´t do anything now? -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514703: Additional info
I have just noticed something: Even on shares where it seems to work I get wrong numbers when I change into a subdirecoty. For example: smbclient //myserver/share -U backup du 23231 Bytes cd /share/anotherDirecotry du 23231 Bytes I always get the same results as of the directory one level higher. The number of Bytes in /share do match. -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514703: Working version found
Hello, I have found a working version of smbclient on a Knoppix 5.1.0 from February 2008. The smbclient version of the smbclient is 3.0.23d. All newer Version´s I have tested up to 3.3.X are not working for me. Even the 3.0.24 that comes with Etch don´t give out the right du size´s. The old version has at least one bug remaining in my environment. It won´t show the correct size of files in a subdirecrory by a directly du. Only when Im trying to get the right size with: smbclient //myserver/myShare -U Myuser -c archive 0; recurse; du it works. That´s how Amanda does it. I hope this is a kind of useful information for you and maybe some files out a bug from the integration of smbclient in Debian Etch, Lenny and so on. Greetings -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#63995: Solution ?
Hi there, is there any solution for this bug incoming ? I mean for me personally it´s impossible to report any further, because of this spam I get through this site. Captcahs or Mailform´s would be great to protect us for getting spam. Anyone working on this ? -- Feel free - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
