El 25 de abril de 2018, 09:25, Matias Mucciolo
escribió:
> On Monday, April 23, 2018 1:12:31 PM -03 OddieX wrote:
>> Tengo un host de virtualizacion con Debian 9.4 corriendo Xen 4.8 con
>> kernel 4.15.0-0.bpo.2-amd64 y anda de maravillas, no tengo errores en
>> el syslog
On Monday, April 23, 2018 1:12:31 PM -03 OddieX wrote:
> Tengo un host de virtualizacion con Debian 9.4 corriendo Xen 4.8 con
> kernel 4.15.0-0.bpo.2-amd64 y anda de maravillas, no tengo errores en
> el syslog y otras maquinas virutales dentro anda barbaro...
>
> Ahora bien! Instale otro Debian
2018-04-23 13:12 GMT-03:00 OddieX :
> Tengo un host de virtualizacion con Debian 9.4 corriendo Xen 4.8 con
> kernel 4.15.0-0.bpo.2-amd64 y anda de maravillas, no tengo errores en
> el syslog y otras maquinas virutales dentro anda barbaro...
>
> Ahora bien! Instale otro Debian
Op 24-03-18 om 22:58 schreef Jan Claeys:
> On Sat, 2018-03-24 at 11:50 +0100, Paul van der Vlis wrote:
>> Op 24-03-18 om 04:48 schreef Diederik de Haas:
>>> On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote:
Mijn bug gaat er over, dat de Debian installer de firmware voor
een
On Sat, 2018-03-24 at 11:50 +0100, Paul van der Vlis wrote:
> Op 24-03-18 om 04:48 schreef Diederik de Haas:
> > On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote:
> > > Mijn bug gaat er over, dat de Debian installer de firmware voor
> > > een wifi-stick uit firmware-linux-free niet
Op 24-03-18 om 04:48 schreef Diederik de Haas:
> On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote:
>> Mijn bug gaat er over, dat de Debian installer de firmware voor een
>> wifi-stick uit firmware-linux-free niet laadt.
>
> $ reportbug installation-report --print
Ik denk dat busybox
On vrijdag 23 maart 2018 14:13:11 CET Paul van der Vlis wrote:
> Mijn bug gaat er over, dat de Debian installer de firmware voor een
> wifi-stick uit firmware-linux-free niet laadt.
$ reportbug installation-report --print
Op 23-03-18 om 02:00 schreef Jan Claeys:
> On Thu, 2018-03-22 at 16:25 +0100, Paul van der Vlis wrote:
>> Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de
>> gegevens van mijn systeem erbij vermelden. Echter, ik meld een
>> probleem over een heel ander systeem, deze gegevens
On Thu, 2018-03-22 at 16:25 +0100, Paul van der Vlis wrote:
> Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de
> gegevens van mijn systeem erbij vermelden. Echter, ik meld een
> probleem over een heel ander systeem, deze gegevens zijn dus
> waardeloos en scheppen verwarring.
>
Op 22-03-18 om 16:50 schreef Geert Stappers:
> Wat ik de meeste tijd doe, is een email aan sub...@bugs.debian.org
> schrijven en op de eerste twee regels
>
> Package:
> Version:
>
> Dan verder als gewone email vertellen over de bug.
> Let wel: plain text ( dus geen HTML ruis )
>
>
>
Op 22-03-18 om 16:34 schreef floris:
> Paul van der Vlis schreef op 2018-03-22 16:25:
>> Hoi,
>>
>> Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de
>> gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem
>> over een heel ander systeem, deze gegevens zijn
On Thu, Mar 22, 2018 at 04:34:33PM +0100, floris wrote:
> Paul van der Vlis schreef op 2018-03-22 16:25:
> >Hoi,
> >
> >Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de
> >gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem
> >over een heel ander systeem,
Paul van der Vlis schreef op 2018-03-22 16:25:
Hoi,
Ik heb net een bug gemeld via reportbug, maar reportbug wou perse de
gegevens van mijn systeem erbij vermelden. Echter, ik meld een probleem
over een heel ander systeem, deze gegevens zijn dus waardeloos en
scheppen verwarring.
Eerder kon ik
- Mail original -
> De: "hamster" <hams...@suna.fdn.fr>
> À: debian-user-french@lists.debian.org
> Envoyé: Lundi 12 Mars 2018 17:48:32
> Objet: Re: bug remmina
>
> Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit :
> >
> >
> >
Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit :
- Mail original -
De: "hamster"
À: debian-user-french@lists.debian.org
Envoyé: Lundi 12 Mars 2018 13:01:26
Objet: bug remmina
Hello
J'arrive pas a faire marcher remmina.
Je commence par monter un tunnel ssh,
On Mon, 05 Mar 2018, Gustavo Moitinho Trindade wrote:
> OS: debian 9.3 (x86_64)
> Cinnamon 3.2.7
> Linux kernel: 4.9.0-6-amd64
> Processor: Intel Core i303110M @ 2.40Ghz x 2
> RAM: 3.7 GB
>
>
> After installing textlive with:
> $ sudo apt install texlive
>
> dpkg seems to fail configuring
I submitted this bug to the nvidia-driver package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891960
Étienne Mollier a écrit :
> Bonsoir,
>
> Joël Bertrand, le 2018-02-07 :
>> Étienne Mollier a écrit :
>>> - Pour élargir un peu le spectre, est ce que les autres
>>> journaux d'erreur mentionnent d'autres fichiers que
>>> mod_reqtimeout.so ou liblber-2.4.so.2.10.8, ou bien est ce
>>> que
Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard:
> Michael Biebl:
>
>> If other services depend on dnsmasq, please keep
>> https://www.lucas-nussbaum.net/blog/?p=877 in mind
>>
> Please do not. It is an erroneous conclusion based upon a faulty
> analysis that conflates the readiness
Bonsoir,
Joël Bertrand, le 2018-02-07 :
> Étienne Mollier a écrit :
> > - Pour élargir un peu le spectre, est ce que les autres
> > journaux d'erreur mentionnent d'autres fichiers que
> > mod_reqtimeout.so ou liblber-2.4.so.2.10.8, ou bien est ce
> > que toutes les erreurs tournent autour
Étienne Mollier a écrit :
> Le problème ne viendrait donc pas de la mémoire, c'est toujours
> ça de pris. Quand vous dites « aucun autre symptôme », le
> service est-il toujours rendu par Apache ?
Je ne sais pas, je n'ai pas eu l'idée de tester.
>> Lorsque le système part en vrille
Bonsoir,
Joël Bertrand, le 2018-05-02 :
> Est-ce que je suis le seul à avoir des problèmes avec les
> noyaux de testing ?
J'utilise un noyau compilé maison, mais pas de problème de mon
côté du temps où il était en version 4.14.13. Je n'ai pas
l'usage d'Apache 2 par contre.
> J'ai assez
Le Mon, 5 Feb 2018 23:22:37 +0100,
BERTRAND Joël a écrit :
> Bonjour à tous,
>
> Est-ce que je suis le seul à avoir des problèmes avec les
> noyaux de testing ? J'ai assez souvent la charge de mon serveur de
> test qui monte à plus de 500 (!) avec une
On Tue, 16 Jan 2018, songbird wrote:
David Wright wrote:
...
Un-trimming some evidence:
On Mon 15 Jan 2018 at 23:27:30 (-0500), James Vibber wrote:
[...]
Unpacking libc6:armhf (2.26-2) over (2.19-18+deb8u10) ...
Would it be better to upgrade jessie???stretch before stretch???buster?
David Wright wrote:
...
> Would it be better to upgrade jessie→stretch before stretch→buster?
if that is what OP is doing, then yes, skipping
major versions has never been officially supported.
at that stage it is often much more time efficient
to re install from recent images.
songbird
On Mon 15 Jan 2018 at 23:27:30 (-0500), James Vibber wrote:
> http://ftp.debian.org/debian/ buster/main zsh-common all 5.4.2-3 [3529 kB]
> Fetched 11.7 MB in 13s (846 kB/s)
> Extracting templates from packages: 100%
> Preconfiguring packages ...
> cat: /sys/bus/usb/devices/*:*/bInterfaceClass: No
On 2018-01-14, Richard Owlett wrote:
> On 01/14/2018 10:23 AM, Richard Owlett wrote:
>> If a file is in a folder below a hidden folder, it will *NOT* be found.
>> This happens even when "Show hidden and backup files" is chosen.
>> It does not matter if logged-in as superuser.
On 01/14/2018 10:23 AM, Richard Owlett wrote:
If a file is in a folder below a hidden folder, it will *NOT* be found.
This happens even when "Show hidden and backup files" is chosen.
It does not matter if logged-in as superuser.
I proved it by copying a folder under a hidden folder to a normal
On Mon, 27 Nov 2017 12:37:10 -0500
Cindy-Sue Causey wrote:
> On 11/27/17, Pietro Vischia wrote:
> > Dear All,
> >
> > I apologize in advance if this is not the correct forum: I am
> > following the instructions at
> >
On 11/27/17, Pietro Vischia wrote:
> Dear All,
>
> I apologize in advance if this is not the correct forum: I am
> following the instructions at
> https://www.debian.org/Bugs/Reporting.en.html in the case in which the
> user is not sure of which package is affected.
>
>
On Mon, Nov 27, 2017 at 5:19 PM, Pietro Vischia
wrote:
> I have a Lenovo T460P, and with stretch I enjoyed a reasonable battery
> life (~4 hours). At the beginning of November I switched to buster,
> and things were still OK.
>
> Last week I made an upgrade as usual, and
> El nov 19, 2017, a las 11:51 AM, NIkitushkin Andrey
> escribió:
>
> Hello!
> 1. I have new bug for i965/960M chipset.
> 2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
> . After use new kernel 4.9 from Debian repositories my system not
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Hello!
1. I have new bug for i965/960M chipset.
2. I see: I see https://lists.debian.org/debian-user/2017/02/msg00800.html
. After use new kernel 4.9 from Debian repositories my system not halt. Thanks!
)))
3. Oh! After enables xtables modules for Debian Linux kernel 4.9 my system halt
again
Am Thu, 26 Oct 2017 13:13:57 +0100 schrieb Darac Marjal:
> [Aside: The debian packaging tool is called "synaptic". "Synaptics" are
> a company producing touchpads. The two are not related]
I know, but I always make this mistake. ;-)
> I believe this is a known bug in synaptic: #864640 [1].
It
On Thu, Oct 26, 2017 at 11:50:05AM +, Joerg Desch wrote:
> I'm still running Debian 8 on all of my systems. Since it is time to
> switch to Debian 9, I've tried to have a first look at it. So I've
> installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
> went fine, until
On Thu, Oct 26, 2017 at 11:50:05AM +, Joerg Desch wrote:
I'm still running Debian 8 on all of my systems. Since it is time to
switch to Debian 9, I've tried to have a first look at it. So I've
installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
went fine, until I've tried
On 10/20/17 12:25, Thomas Schmitt wrote:
the weekly testing ISOs for i386 and amd64 are now equipped with the
new MBR:
https://cdimage.debian.org/mirror/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-netinst.iso
...
Testers wanted for booting this ISO from USB stick.
Boots
Hey,
resolvconf[1] would be the package you are looking for.
Regards,
Rhys Williams
[1] https://packages.debian.org/search?keywords=resolvconf
October 21, 2017 5:30 AM, "vandman" wrote:
> Hi,
> I have a bug to report, but I can not find the package responsible for.
>
Jimmy Johnson wrote:
> Hello,
> Here's an update, testing current kernels for Stretch 4.9.0-3, Buster
> 4.12.0-2 and Sid/Testing 4.13.0-1 they are all working swell, as for the
> regression, as long as I don't look there is none. As far as I'm
> concerned we can close this bug.
>
> Thank you,
On 02/10/2017 06:58 PM, Jimmy Johnson wrote:
On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:
"Re: Bug#1 Freeze"
Jimmy Johnson doc
"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to load
On Thu, 05 Oct 2017, Sergey Storm wrote:
> Hello. I have a problem with keyboard input and I don't know what
> package the bug is in. Bugreport gave me this email address for
> assistance. Help me please.
> I use two languages and switch them using ctrl+shift. But combinations
> ctrl+shift+'any
On Monday 07 August 2017 16:12:57 Andrew W wrote:
> /var/log/cups# lpinfo -l -v
> Device: uri = socket
> class = network
> info = AppSocket/HP JetDirect
> make-and-model = Unknown
> device-id =
> location =
> Device: uri = beh
> class =
/var/log/cups# lpinfo -l -v
Device: uri = socket
class = network
info = AppSocket/HP JetDirect
make-and-model = Unknown
device-id =
location =
Device: uri = beh
class = network
info = Backend Error Handler
make-and-model = Unknown
On Sunday 06 August 2017 18:12:49 Brian wrote:
> On Sun 06 Aug 2017 at 16:09:22 -0400, Gene Heskett wrote:
> > On Sunday 06 August 2017 15:32:46 Andrew W wrote:
> > > On 06/08/17 19:33, Gene Heskett wrote:
> > > > That rather sounds as if the cups daemon isn't running. Look
> > > > for
On Sunday 06 August 2017 18:03:31 Brian wrote:
> On Sun 06 Aug 2017 at 15:53:42 -0400, Gene Heskett wrote:
> > On Sunday 06 August 2017 14:45:01 Brian wrote:
> > > On Sun 06 Aug 2017 at 14:21:36 -0400, Gene Heskett wrote:
> > > > On Sunday 06 August 2017 11:28:25 Brian wrote:
> > > > > On Sun 06
On Sun 06 Aug 2017 at 16:09:22 -0400, Gene Heskett wrote:
> On Sunday 06 August 2017 15:32:46 Andrew W wrote:
>
> > On 06/08/17 19:33, Gene Heskett wrote:
> > > That rather sounds as if the cups daemon isn't running. Look
> > > for /var/log/cupsd error files, which might illuminate the real
> >
On Sun 06 Aug 2017 at 15:53:42 -0400, Gene Heskett wrote:
> On Sunday 06 August 2017 14:45:01 Brian wrote:
>
> > On Sun 06 Aug 2017 at 14:21:36 -0400, Gene Heskett wrote:
> > > On Sunday 06 August 2017 11:28:25 Brian wrote:
> > > > On Sun 06 Aug 2017 at 16:18:37 +0100, Andrew W wrote:
> > > > >
On Sunday 06 August 2017 16:02:58 Andrew W wrote:
> On 06/08/17 20:53, Gene Heskett wrote:
> > PPD description, you can read it at localhost:631/printers, click on
> > modify after highliting the printer?
> >
> >
> > Cheers, Gene Heskett
>
> All web browsers give unable to establish a connection
On Sunday 06 August 2017 15:32:46 Andrew W wrote:
> On 06/08/17 19:33, Gene Heskett wrote:
> > That rather sounds as if the cups daemon isn't running. Look
> > for /var/log/cupsd error files, which might illuminate the real
> > error, since no printer is going to work on a modern linux install
>
On 06/08/17 20:53, Gene Heskett wrote:
PPD description, you can read it at localhost:631/printers, click on
modify after highliting the printer?
Cheers, Gene Heskett
All web browsers give unable to establish a connection to localhost:631.
There doesn't appear to be anything on port 631 even
On Sunday 06 August 2017 14:45:01 Brian wrote:
> On Sun 06 Aug 2017 at 14:21:36 -0400, Gene Heskett wrote:
> > On Sunday 06 August 2017 11:28:25 Brian wrote:
> > > On Sun 06 Aug 2017 at 16:18:37 +0100, Andrew W wrote:
> > > > On 06/08/17 15:05, Curt wrote:
> > > > >>The Brother HL404CN does not
On 06/08/17 19:33, Gene Heskett wrote:
That rather sounds as if the cups daemon isn't running. Look
for /var/log/cupsd error files, which might illuminate the real error,
since no printer is going to work on a modern linux install without its
running and waiting for a print request.
Cheers,
On Sun 06 Aug 2017 at 19:43:20 +0200, deloptes wrote:
> Andrew W wrote:
>
> > Can anyone help me determine the location of an annoying bug which seems
> > to persist in the driver(s) for the Brother HL404CN laser printer
> > please? It has existed since Wheezy and is still present in Stretch.
>
On Sun 06 Aug 2017 at 14:21:36 -0400, Gene Heskett wrote:
> On Sunday 06 August 2017 11:28:25 Brian wrote:
>
> > On Sun 06 Aug 2017 at 16:18:37 +0100, Andrew W wrote:
> > > On 06/08/17 15:05, Curt wrote:
> > > >>The Brother HL404CN does not exist.
> > > >
> > > >So this is all a figment of the
On Sunday 06 August 2017 13:43:20 deloptes wrote:
> Andrew W wrote:
> > Can anyone help me determine the location of an annoying bug which
> > seems to persist in the driver(s) for the Brother HL404CN laser
> > printer please? It has existed since Wheezy and is still present in
> > Stretch.
> >
>
On Sunday 06 August 2017 13:43:20 deloptes wrote:
> Andrew W wrote:
> > Can anyone help me determine the location of an annoying bug which
> > seems to persist in the driver(s) for the Brother HL404CN laser
> > printer please? It has existed since Wheezy and is still present in
> > Stretch.
> >
>
On Sunday 06 August 2017 11:28:25 Brian wrote:
> On Sun 06 Aug 2017 at 16:18:37 +0100, Andrew W wrote:
> > On 06/08/17 15:05, Curt wrote:
> > >>The Brother HL404CN does not exist.
> > >
> > >So this is all a figment of the OP's imagination, I take it.
> > >
> > >Maybe he left out a trailing digit
Andrew W wrote:
> Can anyone help me determine the location of an annoying bug which seems
> to persist in the driver(s) for the Brother HL404CN laser printer
> please? It has existed since Wheezy and is still present in Stretch.
>
> Printing from most apps (but interestingly not GIMP) will
On Sun 06 Aug 2017 at 16:18:37 +0100, Andrew W wrote:
>
>
> On 06/08/17 15:05, Curt wrote:
> >
> >>The Brother HL404CN does not exist.
> >>
> >So this is all a figment of the OP's imagination, I take it.
> >
> >Maybe he left out a trailing digit by inadvertence:
> >
>
On 06/08/17 15:05, Curt wrote:
The Brother HL404CN does not exist.
So this is all a figment of the OP's imagination, I take it.
Maybe he left out a trailing digit by inadvertence:
https://www.brother-usa.com/Printer/ModelDetail/1/HL4040CN/Overview
B
Sorry yes 4040CN
On 2017-08-06, Brian wrote:
> On Sat 05 Aug 2017 at 23:16:15 +0100, Andrew W wrote:
>
>> Can anyone help me determine the location of an annoying bug which seems to
>> persist in the driver(s) for the Brother HL404CN laser printer please? It
>> has existed since Wheezy and
On Sat 05 Aug 2017 at 23:16:15 +0100, Andrew W wrote:
> Can anyone help me determine the location of an annoying bug which seems to
> persist in the driver(s) for the Brother HL404CN laser printer please? It
> has existed since Wheezy and is still present in Stretch.
>
> Printing from most apps
Hi,
(sorry, i don't have advise about the mouse problem.)
Josef Atmin wrote:
> Sometimes a bug I want to report has already been reported. Is
> there a way to just indicate "I have the same problem".
You may send your add-on as mail to the bug's mail address
num...@bugs.debian.org, e.g.
Hello Ben,
Thank you for your prompt response to my inquiry, and your kind assistance.
My comments in-line below:
On Sat, 13 May 2017 00:40:47 +0100, Ben Hutchings
wrote:
>On Fri, 2017-05-12 at 21:26 +, Larry Dighera wrote:
>> Dear Mr. Hutchings,
>> Todays update
I suggest, if it is not wanted, to get suricata started at boot by default,
then just leave the package as it is.
However, in that case, you should mention the opportunity by systemctl in the
README.debian (or better let the user decide during install) if he wants it
running at boot or not.
I
On 3 May 2017 at 12:36, Michael Biebl wrote:
> Am 03.05.2017 um 11:11 schrieb Hans:
>> Hello all,
>>
>> I have installed suricata on my system, but it will not start at boot.
>>
>> When I manually start it, it is working well.
>>
>> As the document advises, I copied
On Mon 01 May 2017 at 14:48:13 (-0400), Greg Wooledge wrote:
> On Mon, May 01, 2017 at 01:18:58PM -0500, David Wright wrote:
> > They do. Both expect a command. You can "show" something but you can't
> > "dev" it or, at least, I don't know how to.
>
> The surprise comes from the fact that
On Wed 26 Apr 2017 at 15:26:36 (-0500), Richard Owlett wrote:
> On 04/26/2017 10:02 AM, Lisi Reisz wrote:
> >But did /sbin/ifconfig work?
> >
>
> Had no reason to try.
> Whenever I come across a command that *SHOULD* work, but does not,
> the first diagnostic step is attempt to run the
On Mon, May 01, 2017 at 01:18:58PM -0500, David Wright wrote:
> They do. Both expect a command. You can "show" something but you can't
> "dev" it or, at least, I don't know how to.
The surprise comes from the fact that typically you can add "dev eth0"
to the end of one working ip command, to get
On Wed 26 Apr 2017 at 09:36:36 (-0500), Richard Owlett wrote:
> On 04/26/2017 07:50 AM, Darac Marjal wrote:
> >On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >>On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>>For interface statistics from ip, try "ip -s link
On Wed 26 Apr 2017 at 13:50:15 (+0100), Darac Marjal wrote:
> On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>For interface statistics from ip, try "ip -s link [interface]".
> >
> >On stretch:
> >
> >wooledg:~$ ip
Original Message
Subject: Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet
useage?]
UTC Time: April 26, 2017 8:26 PM
From: rowl...@cloud85.net
In the *MAJORITY* of cases that it runs demonstrates that someone at
sometime decided to restrict some computer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 26, 2017 at 03:26:36PM -0500, Richard Owlett wrote:
[...]
> Whenever I come across a command that *SHOULD* work, but does not,
> the first diagnostic step is attempt to run the *IDENTICAL* command
> as root.
Now you know better: you
On 04/26/2017 10:02 AM, Lisi Reisz wrote:
On Wednesday 26 April 2017 15:36:36 Richard Owlett wrote:
On 04/26/2017 07:50 AM, Darac Marjal wrote:
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface
On 2017-04-26, Greg Wooledge wrote:
> On Wed, Apr 26, 2017 at 10:25:10AM -0400, Ric Moore wrote:
>> On 04/26/2017 10:17 AM, Greg Wooledge wrote:
>> >On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
>> >>"ifconfig" has to be run as root.
>
>> >This is not correct, if
Eduardo M KALINOWSKI wrote on 04/26/17 16:46:
> On Qua, 26 Abr 2017, Richard Owlett wrote:
>> I would go further saying iproute2 is non-functional due to being
>> functionally
>> un-documented.
>>
>> https://manpages.debian.org/jessie/iproute2/ip.8.en.html is useless.
>>
>> Functional commands,
On Qua, 26 Abr 2017, Richard Owlett wrote:
I would go further saying iproute2 is non-functional due to being
functionally un-documented.
https://manpages.debian.org/jessie/iproute2/ip.8.en.html is useless.
Functional commands, for this thread's topic would be
ip -s link
or
ip -s link ls
On Wednesday 26 April 2017 15:36:36 Richard Owlett wrote:
> On 04/26/2017 07:50 AM, Darac Marjal wrote:
> > On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >> On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>> For interface statistics from ip, try "ip -s link
On 04/26/2017 07:50 AM, Darac Marjal wrote:
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is
On Wed, Apr 26, 2017 at 10:25:10AM -0400, Ric Moore wrote:
> On 04/26/2017 10:17 AM, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> >>"ifconfig" has to be run as root.
> >This is not correct, if you are just using it to view an interface rather
> >than to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> On 04/26/2017 08:36 AM, Brian wrote:
> >On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
> >
> >>On 04/25/2017 08:17 AM, Richard Owlett wrote:
> >>>On 04/24/2017 04:12 PM, Ben
On 04/26/2017 10:17 AM, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
"ifconfig" has to be run as root.
ric@iam:~$ sudo ifconfig
[sudo] password for ric:
enp8s0: flags=4163 mtu 1500
This is not correct, if you are just using
On Wed, Apr 26, 2017 at 10:07:01AM -0400, Ric Moore wrote:
> "ifconfig" has to be run as root.
> ric@iam:~$ sudo ifconfig
> [sudo] password for ric:
> enp8s0: flags=4163 mtu 1500
This is not correct, if you are just using it to view an interface rather
than to
On 04/26/2017 08:36 AM, Brian wrote:
On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
On 04/25/2017 08:17 AM, Richard Owlett wrote:
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 26, 2017 at 01:50:15PM +0100, Darac Marjal wrote:
> On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
> >On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> >>For interface statistics from ip, try "ip -s link
On Wed, Apr 26, 2017 at 08:35:44AM -0400, Greg Wooledge wrote:
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is unknown, try "ip link help".
wooledg:~$ ip -s
On Wed 26 Apr 2017 at 07:17:11 -0500, Richard Owlett wrote:
> On 04/25/2017 08:17 AM, Richard Owlett wrote:
> >On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
> >>On 24/04/17 22:58, Richard Owlett wrote:
> >>>If there were user accessible registers with a running total of
>
On Wed, Apr 26, 2017 at 01:25:18PM +0100, Darac Marjal wrote:
> For interface statistics from ip, try "ip -s link [interface]".
On stretch:
wooledg:~$ ip -s link eth0
Command "eth0" is unknown, try "ip link help".
wooledg:~$ ip -s link dev eth0
Command "dev" is unknown, try "ip link help".
Richard Owlett:
>
> I did an install using expert mode, not selecting any GUI.
> At several points during the install I did Alt-F2 to bring up a terminal to
> attempt running ifconfig.
>
> "Command not found" was the uniform response.
> I booted the new install and attempted as root to run
On Wed, Apr 26, 2017 at 07:17:11AM -0500, Richard Owlett wrote:
On 04/25/2017 08:17 AM, Richard Owlett wrote:
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running total of
uploaded/downloaded data
Hi,
It's working fine on windows.
I had also the same problem with another USB3 docking, a cheapest one,
different brand but the chip inside was probably the same one.
Cheers,
Thibault
On 02/22/2017 03:48 PM, Dan Ritter wrote:
> On Tue, Feb 21, 2017 at 09:28:23AM +0100, Thibault Roulet
On Tue, Feb 21, 2017 at 09:28:23AM +0100, Thibault Roulet wrote:
> Hi all,
>
> I have some serious issues with USB 3 HDD docking station, in which
> package should I report this bug ?
>
I don't think it's a bug in Debian. I bet you can get the same
symptoms plugging it into other hardware and
I believe this is meant for the list and was sent to me instead for
responding suggesting more details
Forwarded Message
Subject: Re: bug report
Date: Tue, 21 Feb 2017 13:37:32 +0100
From: Thibault Roulet <t...@omch.ch>
I'm using a USB3 docking station for HDD. (Sh
Thibault Roulet writes:
> I have some serious issues with USB 3 HDD docking station, in which
> package should I report this bug ?
The hardware is not what determines which package to which you should
report the bug.
Instead, you will need to specify what software is behaving
On 02/19/2017 07:53 AM, Jimmy Johnson wrote:
On 02/10/2017 06:58 PM, Jimmy Johnson wrote:
On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:
"Re: Bug#1 Freeze"
Jimmy Johnson doc
"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with
On 02/10/2017 06:58 PM, Jimmy Johnson wrote:
On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:
"Re: Bug#1 Freeze"
Jimmy Johnson doc
"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to load
On 02/10/2017 07:54 AM, debian-...@lists.debian.org wrote:
"Re: Bug#1 Freeze"
Jimmy Johnson doc
"Mine is an Intel Mobile GM965/GL960 Integrated Graphics and
it's now working swell with the Sid 4.8.0-2 kernel but not
as quick to load as the 4.7.0-1 kernel which works with no
prob
On 11/09/2016 12:20 AM, newbee...@nativobject.net wrote:
Le 09/11/2016 à 04:14, Jimmy Johnson a écrit :
On 11/07/2016 04:44 AM, Tim Ruehsen wrote:
With latest updates made today:
From time to time, KDE freezes. Any idea ?
Hi,
If it's an Intel video card and the kernel is 4.8 downgrade the
201 - 300 of 2012 matches
Mail list logo