Re: Issue -Debian 10 upload speed over LAN and Wlan
On Sat, Mar 21, 2020 at 03:39:26AM +, Pedro Gumucio wrote: > Hello, I have been researching the past week an issue that I have with the > upload speed using the last version of Debian 10/Raspbian GNU/Linux 10. > My internet provider gives me 100/100 Mb/s. but my speed test upload speed is > only 3.8Mb/s > > Retrieving speedtest.net configuration... > Testing from Verizon Fios (100.36.172.81)... > Retrieving speedtest.net server list... > Selecting best server based on ping... > Hosted by PBW Communications, LLC (Herndon, VA) [21.83 km]: 115.366 ms > Testing download > speed > Download: 84.38 Mbit/s > Testing upload > speed.. > Upload: 3.85 Mbit/s > > I tried fresh installations and ran it in raspberry pi 3+ and 4 having the > same results. So you learned that transfer speed is totally independent from installation. > Please help :/ You are asking at the wrong place. Regards Geert Stappers P.S. I could have totally ignore the original message. -- Silence is hard to parse
Processed: Re: Bug#954134: [d-i bullseye alpha2] installing grub fails
Processing control commands: > severity -1 normal Bug #954134 [debian-installer] [d-i bullseye alpha2] installing grub fails Severity set to 'normal' from 'grave' > retitle -1 [d-i bullseye alpha2 i386] Configuring 'grub-installer' failed > with error code 134 Bug #954134 [debian-installer] [d-i bullseye alpha2] installing grub fails Changed Bug title to '[d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134' from '[d-i bullseye alpha2] installing grub fails'. > tags -1 + unreproducible Bug #954134 [debian-installer] [d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134 Added tag(s) unreproducible. -- 954134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#954134: [d-i bullseye alpha2] installing grub fails
Control: severity -1 normal Control: retitle -1 [d-i bullseye alpha2 i386] Configuring 'grub-installer' failed with error code 134 Control: tags -1 + unreproducible Steve McIntyre wrote: > Hey Holger! > > On Fri, Mar 20, 2020 at 01:35:24PM +0100, Holger Wansing wrote: > >Steve McIntyre wrote: > >> > >> Hmmm. Can you try wiping the partition table in between tests? > > > >I already tried that on wednesday, with no success. > > > >However, today it does the trick! Success! > >Curious, but installation completed fine. > > > >Will see, if I can reproduce it again... > > ACK. I'm struggling to understand this otherwise. Hmm, this is getting annoying: while doing several test installs, I thought I had a path how to reproduce the issue, but then suddenly it looked completely different than before. So, that's something between "some portion of coincidence involved" and "wow, not it looks like a hardware failure". And since I was never able to reproduce the issue on amd64, it seems at least to be a i386-only issue, and thus could be considered as a corner case... Therefore reducing severity to normal and tagging as unreproducible + renaming to include the exact error message: "Configuring 'grub-installer' failed with error code 134" (leaving this bug open for a while, other people with the same problem may find it, and probably shade some light on it.) Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#954134: [d-i bullseye alpha2] installing grub fails
On Sat, Mar 21, 2020 at 05:46:03PM +0100, Holger Wansing wrote: >Control: severity -1 normal >Control: retitle -1 [d-i bullseye alpha2 i386] Configuring 'grub-installer' >failed with error code 134 >Control: tags -1 + unreproducible > >Steve McIntyre wrote: >> Hey Holger! >> >> On Fri, Mar 20, 2020 at 01:35:24PM +0100, Holger Wansing wrote: >> >Steve McIntyre wrote: >> >> >> >> Hmmm. Can you try wiping the partition table in between tests? >> > >> >I already tried that on wednesday, with no success. >> > >> >However, today it does the trick! Success! >> >Curious, but installation completed fine. >> > >> >Will see, if I can reproduce it again... >> >> ACK. I'm struggling to understand this otherwise. > >Hmm, this is getting annoying: >while doing several test installs, I thought I had a path how to reproduce >the issue, but then suddenly it looked completely different than before. >So, that's something between "some portion of coincidence involved" and >"wow, not it looks like a hardware failure". > >And since I was never able to reproduce the issue on amd64, it seems at >least to be a i386-only issue, and thus could be considered as a corner >case... > >Therefore reducing severity to normal and tagging as unreproducible >+ renaming to include the exact error message: >"Configuring 'grub-installer' failed with error code 134" >(leaving this bug open for a while, other people with the same problem may >find it, and probably shade some light on it.) ACK. Thanks for continuing on with this - unreproducible bugs are the worst... :-/ -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross
Bug#949694: tasksel: Please drop all kde-l10n packages
Hi! On Sun, 15 Mar 2020 at 03:57, Holger Wansing wrote: > > Hi, > > Wolfgang Schweer wrote: > > Package: tasksel > > Version: 3.58 > > Severity: normal > > > > Hi, > > > > all kde-l10n packages are no longer available. They have been removed > > from unstable and testing some time ago, see: > > https://tracker.debian.org/pkg/kde-l10n > > > > See also the related bug: > > https://bugs.debian.org/935665 > > > > (As far as I can tell, translations are now contained in the > > libkf5i18n-data package, which is installed as a kde dependency.) > > Hmm, libkf5i18n-data was already existing in buster, and it has nearly the > same filesize in sid compared to buster, so it seems that it does not contain > additional translations which have been dropped from kde-l10n-* > > kde-l10n-* packages contain masses of .mo files, which I cannot find > anymore in unstable. Where have all those translations gone? > > CC'ing kde people for advise. If I remember correctly (I'm more with the Qt side of things) most of the translations are part of the applications themselves since Plasma/KF 5. libkf5i18n-data should clearly stay. --- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#954460: remove mentions of "volatile" repo from sources.list
Package: apt-setup Severity: wishlist Tags: patch Forwarding MR from salsa here: I just found out that volatile is still mentioned in sources.list, which I consider outdated and confusing for the end user. This MR changes the wording of the comment in the sources.list to address that. Please feel free to change the wording as you find appropriate. https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/3 patch: https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/3/diffs?commit_id=8de2bfd444c383867f31680de2b9dadbf61e601b -- Samuel Henrique
Bug#954463: override: gir1.2-nemo-3.0:introspection/optional
Package: ftp.debian.org Severity: normal Please change the section from libdevel to introspection
