Re: Bug: updating Debian9 not "allowed".

[Roberto C . Sánchez]

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 to update the APT database.
> 
> Both, apt and Synaptics updates fails. In both cases the error reports, 
> that /etc/apt/trusted.gpg is not accessible by user "_apt". 
> 
> The recommendation I've found was to delete trusted.gpg.
> 
> OK, this was a workaround for using apt. Both update and upgrade works 
> without errors. Trying Synaptics leads to the previous behavior. The file 
> trusted.gpg appears again and with this file, the error returns.
> 
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#apt-unpriv-acquire
> 
> By the way... Why is the VirtualBox Guest Utils package not available in 
> the official repositories?
> 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466

However, there is now a backport:

https://packages.debian.org/source/stretch-backports/virtualbox

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Bug: updating Debian9 not "allowed".

[Darac Marjal]

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 to update the APT database.

Both, apt and Synaptics updates fails. In both cases the error reports,
that /etc/apt/trusted.gpg is not accessible by user "_apt".

The recommendation I've found was to delete trusted.gpg.

OK, this was a workaround for using apt. Both update and upgrade works
without errors. Trying Synaptics leads to the previous behavior. The file
trusted.gpg appears again and with this file, the error returns.


[Aside: The debian packaging tool is called "synaptic". "Synaptics" are 
a company producing touchpads. The two are not related]


I believe this is a known bug in synaptic: #864640 [1].


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864640




By the way... Why is the VirtualBox Guest Utils package not available in
the official repositories?


It is: 
https://packages.debian.org/search?keywords=virtualbox-guest-utils







--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Bug#857597: debian-cd: "isolinux.bin missing or corrupt" when booting USB flash drive in old PC

[David Christensen]

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 correctly on:

Intel D865GBFLK motherboard with Pentium 4 2.8E GHz processor

Intel D945GTP motherboard with Pentium D 945 processor

Intel D945GNT motherboard with Pentium D 945 processor

Intel DQ67SWT motherboard with Core i7-2600S processor

Dell Inspiron 6400 laptop with Core 2 T7400 processor


Thanks everyone for following through.  This will restore Debian (and 
derivatives) as a viable option for many millions of older computers.  :-)



David

p.s.  amd64 version also available for testing:

https://cdimage.debian.org/mirror/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso

Re: Bug with /etc/resolv.conf

[Rhys Williams]

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.
> When I use reportbug, It says it can not find any package and so to
> contact you.
> I have a server on witch I set manually all the conf in
> /etc/network.interfaces.
> As soon as I set up my interfaces with bridge mode and restart the
> server, I get all the time an empty file /etc/resolv.conf and so no dns
> resolution.
> What package sould I use for my report?
> Thanks
> Vandman

Re: Bug#1 Freeze - Re: Intel i965

[deloptes]

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, great job!

I use this opportunity to report on 4.12. I have a server with sas,
precisely
[1.159295] megasas: 07.701.17.00-rc1
[1.159311] mpt3sas version 15.100.00.00 loaded

Before 4.12 I had many issues with raided disks. with 4.12.10 it works
really fine. Upgrading to stretch yesterday, all raid devices assembled
automatically, which before was not the case.

I think I'll stick to 4.12 for a while.

regards

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

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 as the 4.7.0-1 kernel which works with no
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the 
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if 
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. 
Sometimes it will do a first boot without assistance from me but on the 
reboot will lockup without assistance. I'm being forced to use the 
linux-image from Jessie(works swell) in order to get updates. 
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.


If you need testing of assistance let me know.



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, great job!
--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.10.5 - Intel Core 2 Duo T5250 - EXT4 
at sda8

Registered Linux User #380263

Re: bug report - I don't know what package the bug is in

[Don Armstrong]

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 letter' do not correctly work either in the browser,
> or in the konsole. All combinations ctrl+shift+'any letter' run as
> ctrl+'any letter' and language switch. Thank you.

You almost certainly want something like grp:shifts_toggle (both shifts
toggle) or similar, not grp:ctrl_shift (control/shift toggles).

Otherwise you won't be able to type ctrl-shift-key combinations, because
they will shift the layout. man 7 xkeyboard-config; for details about
all of the possible grp: settings for toggling between layouts.

-- 
Don Armstrong  https://www.donarmstrong.com

Some pirates achieved immortality by great deeds of cruelty or
daring-do. Some achieved immortality by amassing great wealth. But
the captain had long ago decided that he would, on the whole, prefer
to achieve immortality by not dying.
 -- Terry Pratchet _The Color of Magic_

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 = network
>  info = Backend Error Handler
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = ipp14
>  class = network
>  info = Internet Printing Protocol (ipp14)
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = http
>  class = network
>  info = Internet Printing Protocol (http)
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = ipp
>  class = network
>  info = Internet Printing Protocol (ipp)
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = ipps
>  class = network
>  info = Internet Printing Protocol (ipps)
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = https
>  class = network
>  info = Internet Printing Protocol (https)
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri = lpd
>  class = network
>  info = LPD/LPR Host or Printer
>  make-and-model = Unknown
>  device-id =
>  location =
> Device: uri =
> dnssd://Brother%20HL-4040CN%20series._pdl-datastream._tcp.local/
>  class = network
>  info = Brother HL-4040CN series
>  make-and-model = Brother HL-4040CN series
>  device-id = MFG:Brother;MDL:HL-4040CN series;CMD:PCL;
>  location =
> Device: uri = lpd://BRNF35C1B/BINARY_P1
>  class = network
>  info = Brother HL-4040CN series
>  make-and-model = Brother HL-4040CN series
>  device-id = MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-4040CN
> series;CLS:PRINTER;
>  location =
> Device: uri =
> dnssd://Brother%20HL-4040CN%20series._printer._tcp.local/ class =
> network
>  info = Brother HL-4040CN series
>  make-and-model = Brother HL-4040CN series
>  device-id = MFG:Brother;MDL:HL-4040CN series;CMD:PCL;
>  location =
>
> systemctl status cups (as per Brians idea) gives
> systemctl status cups
> ● cups.service - CUPS Scheduler
> Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor
> preset: enabled)
> Active: active (running) since Mon 2017-08-07 00:06:46 BST; 21h
> ago Docs: man:cupsd(8)
>   Main PID: 31045 (cupsd)
>  Tasks: 1 (limit: 4915)
> CGroup: /system.slice/cups.service
> └─31045 /usr/sbin/cupsd -l
>
> On 06/08/17 21:09, Gene Heskett wrote:
> > Humm.  Do you have lpinfo? lpinfo -l -v gets me a list of all usable
> > protocols and printers,

So it is running, and I assume the brother printer is attached to that 
machine. Yet you cannot see anything at http://localhost:631/ ? Thats 
why I recommended to take this to the cups mailing list.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Andrew W]

/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
device-id =
location =
Device: uri = ipp14
class = network
info = Internet Printing Protocol (ipp14)
make-and-model = Unknown
device-id =
location =
Device: uri = http
class = network
info = Internet Printing Protocol (http)
make-and-model = Unknown
device-id =
location =
Device: uri = ipp
class = network
info = Internet Printing Protocol (ipp)
make-and-model = Unknown
device-id =
location =
Device: uri = ipps
class = network
info = Internet Printing Protocol (ipps)
make-and-model = Unknown
device-id =
location =
Device: uri = https
class = network
info = Internet Printing Protocol (https)
make-and-model = Unknown
device-id =
location =
Device: uri = lpd
class = network
info = LPD/LPR Host or Printer
make-and-model = Unknown
device-id =
location =
Device: uri = 
dnssd://Brother%20HL-4040CN%20series._pdl-datastream._tcp.local/

class = network
info = Brother HL-4040CN series
make-and-model = Brother HL-4040CN series
device-id = MFG:Brother;MDL:HL-4040CN series;CMD:PCL;
location =
Device: uri = lpd://BRNF35C1B/BINARY_P1
class = network
info = Brother HL-4040CN series
make-and-model = Brother HL-4040CN series
device-id = MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:HL-4040CN 
series;CLS:PRINTER;

location =
Device: uri = dnssd://Brother%20HL-4040CN%20series._printer._tcp.local/
class = network
info = Brother HL-4040CN series
make-and-model = Brother HL-4040CN series
device-id = MFG:Brother;MDL:HL-4040CN series;CMD:PCL;
location =

systemctl status cups (as per Brians idea) gives
systemctl status cups
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor 
preset: enabled)

   Active: active (running) since Mon 2017-08-07 00:06:46 BST; 21h ago
 Docs: man:cupsd(8)
 Main PID: 31045 (cupsd)
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/cups.service
   └─31045 /usr/sbin/cupsd -l


On 06/08/17 21:09, Gene Heskett wrote:


Humm.  Do you have lpinfo? lpinfo -l -v gets me a list of all usable
protocols and printers,

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 /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, Gene Heskett
> > >
> > > Only entries in /var/log/cups/error_log are:
> > >
> > > Duplicate listen address "/var/run/cups/cups.sock" ignored.
> > > E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateAccess
> > > on line 83 of /etc/cups/cupsd.conf.
> > > E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateValues
> > > on line 84 of /etc/cups/cupsd.conf.
> > > E [06/Aug/2017:00:05:22 +0100] Unknown directive
> > > SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
> > > E [06/Aug/2017:00:05:22 +0100] Unknown directive
> > > SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf.
> > >
> > > I've never touched cupsd.conf directly so Im not sure whats messed
> > > it up.
> > >
> > > Ive just printed something sucessfully from GIMP and LibreOffice
> > > and both a JPEG & PDF from Vivaldi and cupsd is listed in the
> > > output from ps yet the web interface is not listening on port 631.
> > >
> > > Printing issue is intermittent, but without being able to get into
> > > the CUPS interface Im not sure which driver it is currently
> > > configured to use.
> >
> > Humm.  Do you have lpinfo? lpinfo -l -v gets me a list of all usable
> > protocols and printers, too long to post though. For my b&w laser:
>
> ~5K is large?
>
> > Device: uri = usb://Brother/HL-2140%20series?serial=L7J156867
> > class = direct
> > info = Brother HL-2140 series
> > make-and-model = Brother HL-2140 series
> > device-id = MFG:Brother;CMD:PJL,HBP;MDL:HL-2140
> > series;CLS:PRINTER;~
> >
> > For my large format inkjet:
> > Device: uri = dnssd://Brother%20MFC-J6920DW._printer._tcp.local/
> > class = network
> > info = Brother MFC-J6920DW
> > make-and-model = Brother MFC-J6920DW
> > device-id = MFG:Brother;MDL:MFC-J6920DW;CMD:HBP,BRPJL,URF;
> >
> > There are several of those because I have them preconfigured for
> > this job or that job.
> >
> > You should get something similar. You might also install htop, and
> > see if cups is running.
>
> What is wrong with 'systemctl status cups'?

Nothing, if the script has a status report ability.  10 years ago it was 
always there and could be trusted.  Now its missing half the time 
because it runs on the authors machine so it must be useless code.

Its one of those things you never need, until you do.  As for the 
systemctl status cups, the only machine I have here new enough for 
systemctl is a jessie install on a raspi thats running 3/4 ton of metal 
lathe, and it says:

pi@picncsheldon:~ $ systemctl status cups
● cups.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
pi@picncsheldon:~ $ systemctl status cupsd
● cupsd.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Despite that, geany can print to either of the two brother printers here 
in this room, anything I want it to print that I have tried so far.  And 
a web page firefox was looking at, printed better on the inkjet here 
than it looked on the raspi's hdmi monitor.

However, htop says cups-browsed is running, so:
pi@picncsheldon:~/linuxcnc/configs/sheldon-lathe $ systemctl status 
cups-browsed

● cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled)
   Active: active (running) since Wed 2017-07-26 22:26:23 EDT; 1 weeks 4 
days ago
 Main PID: 641 (cups-browsed)
   CGroup: /system.slice/cups-browsed.service
   └─641 /usr/sbin/cups-browsed

So that explains that.

And, if I fire up firefox on that raspi and send it to 
localhost:631/printers it lists everything connected to this computer, 
180 feet of cat 5 or 6 away.  And it can print a web page just fine.

But this does not help Brian.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 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:
> > > > > > >
> > > > > > >https://www.brother-usa.com/Printer/ModelDetail/1/HL4040CN/
> > > > > > >Over view
> > > > > > >
> > > > > > >B
> > > > > >
> > > > > > Sorry yes 4040CN
> > > > >
> > > > > Brother doesn't provide a driver for the 4040CN. Perhaps you
> > > > > would explain what you mean by "driver(s) for the Brother
> > > > > HL404CN" and "I've tried several of the drivers listed...".
> > > > > Driver names would be useful.
> > > >
> > > > You will also note that it handles both .pdf's and jpeg's
> > > > natively, so
> > >
> > > Citation for the 4040CN please. As far as I can see its language
> > > emulation is PCL 6 only.
> >
> > From the web link above.
>
> There is nothing on that page which says the 4040CN  will accept a
> PDF or JPEG sent *directly* to it and print it correctly. In other
> words, the printer does not handle both ".pdf's and jpeg's natively".
> Whatever "natively" means.
>
> > > > all the OP needs to do is pick a driver that makes a pdf out of
> > > > whatever knocks on the drivers door?  We have several of those
> > > > critters if the fine print can be believed.
> > >
> > > Which "fine print"?
> >
> > PPD description, you can read it at localhost:631/printers, click on
> > modify after highliting the printer?
>
> I still do not understand what you mean by "makes a pdf out of
> whatever knocks on the drivers door". Sending a PDF to the printer is
> doomed to failure.

It has become obvious to me that you have an unusual situation, that I 
have attempted to ask questions that might lead to discovering the 
problem.  I have failed, and since it seems Mikes cups software is in 
the middle of it, that is why I recommended you take your .conf file, 
and the logs to Mike on his list. You will probably get an answer from 
Mike or one of his staff at Apple.  I've known Mike since the Delphi 
days when we were working on TRS-80 Color Computers, running os9, a unix 
like os for a 64k computer, 30 years ago.  He is ok IMNSHO, and he wrote 
cups.

You likely will not solve it by chasing every bit of the advice offered 
here, so take it to the source, Michael Sweet.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Brian]

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
> > > error, since no printer is going to work on a modern linux install
> > > without its running and waiting for a print request.
> > >
> > > Cheers, Gene Heskett
> >
> > Only entries in /var/log/cups/error_log are:
> >
> > Duplicate listen address "/var/run/cups/cups.sock" ignored.
> > E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateAccess on
> > line 83 of /etc/cups/cupsd.conf.
> > E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateValues on
> > line 84 of /etc/cups/cupsd.conf.
> > E [06/Aug/2017:00:05:22 +0100] Unknown directive
> > SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
> > E [06/Aug/2017:00:05:22 +0100] Unknown directive
> > SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf.
> >
> > I've never touched cupsd.conf directly so Im not sure whats messed it
> > up.
> >
> > Ive just printed something sucessfully from GIMP and LibreOffice and
> > both a JPEG & PDF from Vivaldi and cupsd is listed in the output from
> > ps yet the web interface is not listening on port 631.
> >
> > Printing issue is intermittent, but without being able to get into the
> > CUPS interface Im not sure which driver it is currently configured to
> > use.
> Humm.  Do you have lpinfo? lpinfo -l -v gets me a list of all usable 
> protocols and printers, too long to post though. For my b&w laser:

~5K is large?

> Device: uri = usb://Brother/HL-2140%20series?serial=L7J156867
> class = direct
> info = Brother HL-2140 series
> make-and-model = Brother HL-2140 series
> device-id = MFG:Brother;CMD:PJL,HBP;MDL:HL-2140 
> series;CLS:PRINTER;~
> 
> For my large format inkjet:
> Device: uri = dnssd://Brother%20MFC-J6920DW._printer._tcp.local/
> class = network
> info = Brother MFC-J6920DW
> make-and-model = Brother MFC-J6920DW
> device-id = MFG:Brother;MDL:MFC-J6920DW;CMD:HBP,BRPJL,URF;
> 
> There are several of those because I have them preconfigured for this job 
> or that job.
> 
> You should get something similar. You might also install htop, and see if 
> cups is running.

What is wrong with 'systemctl status cups'?

-- 
Brian.

Re: Bug in Brother HL4040 driver?

[Brian]

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 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/Over
> > > > > >view
> > > > > >
> > > > > >B
> > > > >
> > > > > Sorry yes 4040CN
> > > >
> > > > Brother doesn't provide a driver for the 4040CN. Perhaps you would
> > > > explain what you mean by "driver(s) for the Brother HL404CN" and
> > > > "I've tried several of the drivers listed...". Driver names would
> > > > be useful.
> > >
> > > You will also note that it handles both .pdf's and jpeg's natively,
> > > so
> >
> > Citation for the 4040CN please. As far as I can see its language
> > emulation is PCL 6 only.
> >
> From the web link above.

There is nothing on that page which says the 4040CN  will accept a
PDF or JPEG sent *directly* to it and print it correctly. In other
words, the printer does not handle both ".pdf's and jpeg's natively".
Whatever "natively" means.

> > > all the OP needs to do is pick a driver that makes a pdf out of
> > > whatever knocks on the drivers door?  We have several of those
> > > critters if the fine print can be believed.
> >
> > Which "fine print"?
> PPD description, you can read it at localhost:631/printers, click on 
> modify after highliting the printer?

I still do not understand what you mean by "makes a pdf out of whatever
knocks on the drivers door". Sending a PDF to the printer is doomed to
failure.

-- 
Brian

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 to
> localhost:631. There doesn't appear to be anything on port 631 even
> though cupsd is running.

Post your /etc/cups/cupsd.conf please, but do it on the cups mailing list 
where Michael Sweet will see it.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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
> > without its running and waiting for a print request.
> >
> > Cheers, Gene Heskett
>
> Only entries in /var/log/cups/error_log are:
>
> Duplicate listen address "/var/run/cups/cups.sock" ignored.
> E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateAccess on
> line 83 of /etc/cups/cupsd.conf.
> E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateValues on
> line 84 of /etc/cups/cupsd.conf.
> E [06/Aug/2017:00:05:22 +0100] Unknown directive
> SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
> E [06/Aug/2017:00:05:22 +0100] Unknown directive
> SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf.
>
> I've never touched cupsd.conf directly so Im not sure whats messed it
> up.
>
> Ive just printed something sucessfully from GIMP and LibreOffice and
> both a JPEG & PDF from Vivaldi and cupsd is listed in the output from
> ps yet the web interface is not listening on port 631.
>
> Printing issue is intermittent, but without being able to get into the
> CUPS interface Im not sure which driver it is currently configured to
> use.
Humm.  Do you have lpinfo? lpinfo -l -v gets me a list of all usable 
protocols and printers, too long to post though. For my b&w laser:

Device: uri = usb://Brother/HL-2140%20series?serial=L7J156867
class = direct
info = Brother HL-2140 series
make-and-model = Brother HL-2140 series
device-id = MFG:Brother;CMD:PJL,HBP;MDL:HL-2140 
series;CLS:PRINTER;~

For my large format inkjet:
Device: uri = dnssd://Brother%20MFC-J6920DW._printer._tcp.local/
class = network
info = Brother MFC-J6920DW
make-and-model = Brother MFC-J6920DW
device-id = MFG:Brother;MDL:MFC-J6920DW;CMD:HBP,BRPJL,URF;

There are several of those because I have them preconfigured for this job 
or that job.

You should get something similar. You might also install htop, and see if 
cups is running.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Andrew W]

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 though cupsd is 
running.

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 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/Over
> > > > >view
> > > > >
> > > > >B
> > > >
> > > > Sorry yes 4040CN
> > >
> > > Brother doesn't provide a driver for the 4040CN. Perhaps you would
> > > explain what you mean by "driver(s) for the Brother HL404CN" and
> > > "I've tried several of the drivers listed...". Driver names would
> > > be useful.
> >
> > You will also note that it handles both .pdf's and jpeg's natively,
> > so
>
> Citation for the 4040CN please. As far as I can see its language
> emulation is PCL 6 only.
>
From the web link above.

> > all the OP needs to do is pick a driver that makes a pdf out of
> > whatever knocks on the drivers door?  We have several of those
> > critters if the fine print can be believed.
>
> Which "fine print"?
PPD description, you can read it at localhost:631/printers, click on 
modify after highliting the printer?


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Andrew W]

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, Gene Heskett

Only entries in /var/log/cups/error_log are:

Duplicate listen address "/var/run/cups/cups.sock" ignored.
E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateAccess on 
line 83 of /etc/cups/cupsd.conf.
E [06/Aug/2017:00:05:22 +0100] Unknown directive JobPrivateValues on 
line 84 of /etc/cups/cupsd.conf.
E [06/Aug/2017:00:05:22 +0100] Unknown directive 
SubscriptionPrivateAccess on line 85 of /etc/cups/cupsd.conf.
E [06/Aug/2017:00:05:22 +0100] Unknown directive 
SubscriptionPrivateValues on line 86 of /etc/cups/cupsd.conf.


I've never touched cupsd.conf directly so Im not sure whats messed it up.

Ive just printed something sucessfully from GIMP and LibreOffice and 
both a JPEG & PDF from Vivaldi and cupsd is listed in the output from ps 
yet the web interface is not listening on port 631.


Printing issue is intermittent, but without being able to get into the 
CUPS interface Im not sure which driver it is currently configured to use.

Re: Bug in Brother HL4040 driver?

[Brian]

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.
> > 
> > Printing from most apps (but interestingly not GIMP) will often fail
> > with the printers firmware locking up and showing Error E1 on its
> > display - the only way out of this is to turn the printer off and back on.
> > 
> > I've tried several of the drivers listed and all seem to have the same
> > issue. Further more in Stretch the web interface for CUPS doesnt seem to
> > work on localhost:631 and the Gnome system settings GUI for print queue
> > management doesnt do anything. Its as if the buttons have no event
> > handlers behind them to actually do anything!
> > 
> > 
> > Thanks
> 
> Have you done firmware upgrade?
> https://help.brother-usa.com/app/answers/detail/a_id/80507/~/print-unable-e1-or-machine-error-e1-message

You'll have read the recent thread (a couple of days ago) about doing
printer firmware updates on Debian. No? We will let you find it and then
come back with a revised opinion or sound advice.
 
> also here it suggests that it might be the poppler lib causing issues
> 
> https://bugs.chromium.org/p/chromium/issues/detail?id=89122
> 
> the printer uses PCL6 so make sure you get the proper conversion from any
> type to PCL in cups. Look there for solution.

Thanks. Looks interesting and bears examination when time permits.

-- 
Brian.

Re: Bug in Brother HL4040 driver?

[Brian]

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 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
> >
> > Brother doesn't provide a driver for the 4040CN. Perhaps you would
> > explain what you mean by "driver(s) for the Brother HL404CN" and
> > "I've tried several of the drivers listed...". Driver names would
> > be useful.
> 
> You will also note that it handles both .pdf's and jpeg's natively, so

Citation for the 4040CN please. As far as I can see its language
emulation is PCL 6 only.

> all the OP needs to do is pick a driver that makes a pdf out of whatever 
> knocks on the drivers door?  We have several of those critters if the 
> fine print can be believed.

Which "fine print"?

-- 
Brian.

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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.
> >
> > Printing from most apps (but interestingly not GIMP) will often fail
> > with the printers firmware locking up and showing Error E1 on its
> > display - the only way out of this is to turn the printer off and
> > back on.
> >
> > I've tried several of the drivers listed and all seem to have the
> > same issue. Further more in Stretch the web interface for CUPS
> > doesnt seem to work on localhost:631 and the Gnome system settings
> > GUI for print queue management doesnt do anything. Its as if the
> > buttons have no event handlers behind them to actually do anything!

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.
> >
> > Thanks
>
> Have you done firmware upgrade?
> https://help.brother-usa.com/app/answers/detail/a_id/80507/~/print-una
>ble-e1-or-machine-error-e1-message
>
> also here it suggests that it might be the poppler lib causing issues
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=89122
>
> the printer uses PCL6 so make sure you get the proper conversion from
> any type to PCL in cups. Look there for solution.
>
> regards


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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.
> >
> > Printing from most apps (but interestingly not GIMP) will often fail
> > with the printers firmware locking up and showing Error E1 on its
> > display - the only way out of this is to turn the printer off and
> > back on.
> >
> > I've tried several of the drivers listed and all seem to have the
> > same issue. Further more in Stretch the web interface for CUPS
> > doesnt seem to work on localhost:631 and the Gnome system settings
> > GUI for print queue management doesnt do anything. Its as if the
> > buttons have no event handlers behind them to actually do anything!
> >
> >
> > Thanks
>
> Have you done firmware upgrade?
> https://help.brother-usa.com/app/answers/detail/a_id/80507/~/print-una
>ble-e1-or-machine-error-e1-message

This is a wild goose chase, and the goose is winning.  At the bottom of 
that faq, is a link to a list of the models that proceedure applies to.  
His printer is not in that list, as its only for:
   Color Laser LED Printer
   HL3140CW
   HL4150CDN
   HL4570CDW
   HL4570CDWT
[...]

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[Gene Heskett]

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 by inadvertence:
> > >
> > >https://www.brother-usa.com/Printer/ModelDetail/1/HL4040CN/Overview
> > >
> > >B
> >
> > Sorry yes 4040CN
>
> Brother doesn't provide a driver for the 4040CN. Perhaps you would
> explain what you mean by "driver(s) for the Brother HL404CN" and
> "I've tried several of the drivers listed...". Driver names would
> be useful.

You will also note that it handles both .pdf's and jpeg's natively, so 
all the OP needs to do is pick a driver that makes a pdf out of whatever 
knocks on the drivers door?  We have several of those critters if the 
fine print can be believed.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug in Brother HL4040 driver?

[deloptes]

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 often fail
> with the printers firmware locking up and showing Error E1 on its
> display - the only way out of this is to turn the printer off and back on.
> 
> I've tried several of the drivers listed and all seem to have the same
> issue. Further more in Stretch the web interface for CUPS doesnt seem to
> work on localhost:631 and the Gnome system settings GUI for print queue
> management doesnt do anything. Its as if the buttons have no event
> handlers behind them to actually do anything!
> 
> 
> Thanks

Have you done firmware upgrade?
https://help.brother-usa.com/app/answers/detail/a_id/80507/~/print-unable-e1-or-machine-error-e1-message

also here it suggests that it might be the poppler lib causing issues

https://bugs.chromium.org/p/chromium/issues/detail?id=89122

the printer uses PCL6 so make sure you get the proper conversion from any
type to PCL in cups. Look there for solution.

regards

Re: Bug in Brother HL4040 driver?

[Brian]

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:
> >
> >https://www.brother-usa.com/Printer/ModelDetail/1/HL4040CN/Overview
> >
> >B
> Sorry yes 4040CN

Brother doesn't provide a driver for the 4040CN. Perhaps you would
explain what you mean by "driver(s) for the Brother HL404CN" and
"I've tried several of the drivers listed...". Driver names would
be useful.

-- 
Brian.

Re: Bug in Brother HL4040 driver?

[Andrew W]

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

Re: Bug in Brother HL4040 driver?

[Curt]

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 is still present in Stretch.
>> 
>> Printing from most apps (but interestingly not GIMP) will often fail with
>> the printers firmware locking up and showing Error E1 on its display - the
>> only way out of this is to turn the printer off and back on.
>> 
>> I've tried several of the drivers listed and all seem to have the same
>> issue. Further more in Stretch the web interface for CUPS doesnt seem to
>> work on localhost:631 and the Gnome system settings GUI for print queue
>> management doesnt do anything. Its as if the buttons have no event handlers
>> behind them to actually do anything!
>
> 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

But, as Olivier Vandal Homes III said the other day at lunch: "Guessing
is the curse of the presumptive class." He paused, gazing at me over our
third *digestif* of the afternoon. "And it's all so tiresome in the end,
isn't it old man, when people can't say what they mean and vice versa?"
he added in his typically jaded tone.

-- 
“Certitude is not the test of certainty.”
--Oliver Wendell Holmes, Jr.

Re: Bug in Brother HL4040 driver?

[Brian]

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 (but interestingly not GIMP) will often fail with
> the printers firmware locking up and showing Error E1 on its display - the
> only way out of this is to turn the printer off and back on.
> 
> I've tried several of the drivers listed and all seem to have the same
> issue. Further more in Stretch the web interface for CUPS doesnt seem to
> work on localhost:631 and the Gnome system settings GUI for print queue
> management doesnt do anything. Its as if the buttons have no event handlers
> behind them to actually do anything!

The Brother HL404CN does not exist.

-- 
Brian.

Re: bug report mouse

[Thomas Schmitt]

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.  864...@bugs.debian.org .

If you participate in a bug report, you should also subscribe to
the bug: number-subscr...@bugs.debian.org (e.g.
864701-subscr...@bugs.debian.org) so you get other people's add-ons
as mail.

It depends on the situation, whether a simple "me too" report is
of help. Often it is appropriate only if you can contribute yet
unknown information how to reproduce or how to avoid the bug.
Hardware related bugs on the other side, can well take profit from
add-on reports which simply tell affected or non-affected hardware.

Always welcome is a good theory why the bug happens.
(Read The Source, Luke !)


Have a nice day :)

Thomas

Re: Bug#860543: 'Gave up waiting for suspend/resume device'

[Larry Dighera]

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 appears to have caused my Debian Stretch Linux system
>> to fail to boot with this error message: 
>> 
>>     "Gave up waiting for suspend/resume device..."
>
>That (by itself) does not indicate a boot failure; it only means that
>resume from disk (hibernation) won't work.  
>

Previous to the update, hibernation worked.  

>
>Do any messages appear afterward?
>

Yes.  There is a bit after that.

"Gave up waiting for root file system device"
or

"Gave up waiting for suspend/resume device"

Then some suggestions presumably about how to address the issue:

"Boot Args. Cat /proc/cmdline"
something about "check root delay" perhaps not long enough... 
missing modules..."
"UUID 2d182fb2... doesn't exist."

>
>> The Grub menu is still accessible, but I'm clueless how to return the
>> system to operational status.
>> Please provide complete step-by-step instructions to restore
>> successful system booting through the Grub menu.  
>
>One of the 'recovery mode' item under Advanced Options will enable
>verbose logging to the screen and will perhaps get you to a shell.
>

Unfortunately, selecting the 'recovery mode' grub menu option is useless.
There is something about 'busybox' and a '(initramfs)' prompt(?), but the
system fails to respond to keyboard or mouse input at that point.  So
'recovery mode' appears to be useless.

However, by entering 'e' at the grub menu, I can edit the 'command line.  At
your suggestion above, I changed 'quite' to 'verbose', but nothing seems to
have changed when rebooting.

By entering 'c' at the grub menu, I can get a 'Grub>' prompt from which I am
able to 'ls' and 'cat' and probably a hundred or more other commands that
can be displayed with the 'help' command.  It is necessary to enter 'set
pager=1' to see them before they scroll off screen.  Entering 'help
' provides some additional terse (cryptic) information about the
command.

I don't find any sort of editing command, and redirection '>>' attempts
fail.  

Can you give me a clue to necessary commands to go about returning my system
to operational status from this 'Grub>' prompt?  

>
>In any case, you should open a *new* bug report rather than appending
>to this one.
>
>Ben.

It was not my intent to open a bug report at all.  I apologize for any issue
I may have caused.

In the information at this link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860543 you stated:

"Is there a resume device specified in
/etc/initramfs-tools/conf.d/resume and does it exist?"

I found /etc/initramfs-tools/conf.d/resume.  It contains the single entry:

"RESUME=UUID=f5aa19f3-7707-4bab-bd18-15d6124a0147"

I have no idea where to find that file/device/?.

I just want my system to boot again.  Please assist me in reaching that
goal.

Best regards,
Larry

PS:
On that page, you also stated: 

> ...
> /etc/initramfs-tools/conf.d/resume exists and did not contain a valid
> device. The problem still persists, if I enter a valid UUID, or remove
> the file.

This issue should only affect systems that have a nonexistent device
specified in the configuration, or that have a swap device that isn't
suitable as a resume device because it's not set up early enough.
Previously we would only look for the resume device once, so this
didn't hurt, but it also meant that resume was broken on some systems.

Unfortunately, as you've seen, there isn't currently a way to
completely disable use of a resume device when building the initramfs. 
It *is* possible to do so at boot time (kernel parameter 'noresume' or
'resume=').

I think I need to add:

- The option to disable use of a resume device in the configuration
  (e.g. RESUME=none)
- A warning on upgrade if the configured resume device doesn't exist or
  is unlikely to be available

Ben.

Is that what I need to do?  If so, please provide step-by-step keystrokes I
need to enter at the "Grub>" prompt. 

Re: Bug#861732: systemd: How to get suricata started at boot?

[Hans]

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 personally found the solution with systemctl, so this regardless what you 
decide, IMO this bugreport can be closed. 

To discuss this is a welcome decision and real open-source-thinking!

Best 

Hans 

Re: Bug#861732: systemd: How to get suricata started at boot?

[Arturo Borrero Gonzalez]

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  /lib/systemd/system/suricata.service to
>> /etc/systemd/system/suricata.service and tested with
>
> You only need to copy suricata.service to /etc if you want to change its
> contents. Even then, often drop-in snippets are preferrable, which only
> override/extend the parts you need
>
>> systemctl start suricata.service
>>
>> "ps -aux | grep suricata" showed me the running process. But after reboot, 
>> the
>> process is not started automatically. As init is no more supported by
>> suricata, but systemd,
>
> The suricata package still ships a SysV init script, but if a systemd
> service file exists, it takes precedence.
>
>  how can I add this service into systemd, so that it is
>> started automatically at boot? I am still not quite experienced with systemd.
>
> systemctl enable suricata.service
>
> will do the trick. That should be done by the package though.

This conflicts with what was reported in #850889 [0].

I think both arguments are valid:

1) any suricata deployment is likely to require manual configuration
before proper service. Auto-start makes no sense.
2) yes, we are debian, we like things running out of the box

So, I'm unsure what path to follow.

In any case, a fix is not landing in stretch at this point. We should
wait for the stretch stable release.

Comments/discussion welcome.

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861732

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

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 typically you can add "dev eth0"
> to the end of one working ip command, to get another working ip command
> which is restricted to that one interface -- but not always.
> 
> ip addr show (working)
> ip addr show dev eth0 (working)
> 
> But
> 
> ip addr (working)
> ip addr dev eth0 (NOT working)
> 
> And
> 
> ip -s link show (working)
> ip -s link show dev eth0 (working)
> 
> But
> 
> ip -s link (working)
> ip -s link dev eth0 (NOT working)
> 
> Apparently, in order to understand why half of the commands work and
> half do not, you have to somehow figure out that you're currently using
> a command with an assumed verb, and that this makes a difference, in
> some way, if you try to add words that follow the assumed verb.  Like,
> "the verb is only added if the parser runs out of words" or something.

I'd assumed that the presumption of "show [everything]" was there
because non-root users can do little else, and I don't think you can
omit/assume any other verb. cf mount.

> The inconsistency is quite confusing, especially if you haven't
> scientifically attempted EVERY combination of words yet, to see which
> combinations work and which do not, in order to analyze it for patterns
> and infer the actual grammar rules.

Sure, but who would prefer "ip link" to give you a load of its BNF
rather than assuming you meant show. "ip" does give you BNF, it's
true, but with such a flexible command, where to start. "ip nt"
already fills the screen; only 16 more object types to go.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

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 *IDENTICAL* command
> as root.
> In the *MAJORITY* of cases that it runs demonstrates that someone at
> sometime decided to restrict some computer owners from using their
> own computer in a reasonable manner.

Which merely begs the question. The meaning of "*should* work
as non-root" is defined by your workaround.

> Remember Linux borrows heavily from an OS designed in another era
> for a another audience. I have yet to run across a case where any
> distinction should be made between "user richard" and "user root". I
> do not take that as necessary and sufficient conditions to abolish
> questionable conventions. They might be occasionally valuable.

That's a nice explanation of why I wrote last year a sentence that
you didn't understand:

  The usefulness of many suggestions is limited, of course, by the OPs
  insistence that a horse and cart is driven through the unix security
  model merely because the OP never connects anything to the internet
  (which is insane).

https://lists.debian.org/debian-user/2016/11/msg00903.html

I guess you were happier with DOS.

> In the age of laptops, tablets, and so-called "smart phones" I think
> the more relevant basic distinction would be between "physically
> local user" and "physically external user".

So how is anyone able to configure a computer for their naive family,
say, to use.

> Haven't yet figured out what to propose that wouldn't "throw baby
> out with the bath water".

The same answer, then, as I gave you for your proposed vague changes
to the man pages.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Greg Wooledge]

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 another working ip command
which is restricted to that one interface -- but not always.

ip addr show (working)
ip addr show dev eth0 (working)

But

ip addr (working)
ip addr dev eth0 (NOT working)

And

ip -s link show (working)
ip -s link show dev eth0 (working)

But

ip -s link (working)
ip -s link dev eth0 (NOT working)

Apparently, in order to understand why half of the commands work and
half do not, you have to somehow figure out that you're currently using
a command with an assumed verb, and that this makes a difference, in
some way, if you try to add words that follow the assumed verb.  Like,
"the verb is only added if the parser runs out of words" or something.

The inconsistency is quite confusing, especially if you haven't
scientifically attempted EVERY combination of words yet, to see which
combinations work and which do not, in order to analyze it for patterns
and infer the actual grammar rules.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

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 [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".
> >>
> >>wooledg:~$ ip link help
> >>[... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >>to the fact that you can stick options between "ip" and "link" ...]
> >>
> >>wooledg:~$ ip -s link show eth0
> >>2: eth0:  mtu 1500 qdisc pfifo_fast
> >>state UP mode DEFAULT group default qlen 1000
> >>   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >>   RX: bytes  packets  errors  dropped overrun mcast
> >>   380719013  1442490  0   0   0   4731
> >>   TX: bytes  packets  errors  dropped carrier collsns
> >>   57971257   614586   0   0   0   0
> >>
> >>Aha!
> >
> >My bad. I actually only got as far as discovering "ip -s link" on my own
> >system. As I was typing up the email I remembered that Richard was after
> >statistics for a specific interface. I should have been more diligent in
> >working out the correct format.
> >
> >>
> >>(Sadly, this is my *typical* experience with the ip command -- trying
> >>random things until one of them works, because the documentation
> >>is impenetrable, and the syntax barely guessable, and certainly not
> >>predictable.)
> >
> >ip *could* do a lot better, it's true. As a monolithic tool, there's not
> >really much excuse for the different sub-tools to parse the commands
> >differently. As you say, "ip address" expects the device to be expressed
> >as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
> >know.
> 
> 
> 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.

It is if you want to know exactly what you can do with one of
the seventeen different objects it can handle. If you want to
know what those objects are, or what options are available, it's
not useless.

> Functional commands, for this thread's topic would be
>   ip -s link
> or
>   ip -s link ls usb0
> 
> No hint of either in so-called man page.
> 
> I accidentally discovered it by following up links when doing
> DuckDuckGo search for "documentation iproute2" (w/o quotes).
> 
> I then did another netinst of testing. There is some subset of the
> "ip" command available after the network has been configured. The
> help is too abbreviated to be useful.

Not at all. The abbreviated help shows you what's available
during the installation process which, as you have noticed,
is often a subset.

Having ascertained that subset, you now know which parts of the
main documentation, available in various locations, still apply.

You seem to want the cut-down man pages to be included in the
installation, which is a surprise coming from someone who seems
concerned about bandwidth almost to the point of obsession.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[David Wright]

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 -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".
> >
> >wooledg:~$ ip link help
> >[... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >to the fact that you can stick options between "ip" and "link" ...]

Presumably you realisd that the options to ip are documented in
man ip   and summarised in   ip help. Otherwise, this has to be
duplicated and maintained seventeen times.

> >wooledg:~$ ip -s link show eth0
> >2: eth0:  mtu 1500 qdisc pfifo_fast state 
> >UP mode DEFAULT group default qlen 1000
> >   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >   RX: bytes  packets  errors  dropped overrun mcast
> >   380719013  1442490  0   0   0   4731
> >   TX: bytes  packets  errors  dropped carrier collsns
> >   57971257   614586   0   0   0   0
> >
> >Aha!
> 
> My bad. I actually only got as far as discovering "ip -s link" on my own
> system. As I was typing up the email I remembered that Richard was after
> statistics for a specific interface. I should have been more diligent in
> working out the correct format.
> 
> >
> >(Sadly, this is my *typical* experience with the ip command -- trying
> >random things until one of them works, because the documentation
> >is impenetrable, and the syntax barely guessable, and certainly not
> >predictable.)
> 
> ip *could* do a lot better, it's true. As a monolithic tool, there's not
> really much excuse for the different sub-tools to parse the commands
> differently. As you say, "ip address" expects the device to be expressed
> as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
> know.

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.

Cheers,
David.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Fungi4All]

 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 owners from using their own
computer in a reasonable manner.

Are you saying debian is not designed for users but for sys-admins as owners?
I assume if you are a confident sys-adm and single user then you can run it as 
root and have no users or create a user with identical rights to root. But for 
debian and most linux/unix derivatives to have it plastered all over the place 
to rarely if ever use root, I assume and can think of reasons. If your 
significant other uses it and you get into a fight he/she might destroy your 
system, or your kid, or your neighbor who uses it as a server for his 
connection to the world.

Remember Linux borrows heavily from an OS designed in another era for a
another audience.

Can you explain what era and audience was this and how has it changed?

I have yet to run across a case where any distinction
should be made between "user richard" and "user root".

That is because those who run 6 servers and 300,000 users based on the same 
installation you had would have a stroke hearing something like this. Can you 
run a webmail server and administer it off of your system?
What it sounds like you are asking for is a Debian-workstation and a 
Debian-enterprise as separate systems in a way the 1st would never be able to 
be transformed into the 2nd.

I do not take
that as necessary and sufficient conditions to abolish questionable
conventions. They might be occasionally valuable.

In the age of laptops, tablets, and so-called "smart phones" I think the
more relevant basic distinction would be between "physically local user"
and "physically external user".

How about a coffee shop with dummy terminals all connected to a pc-server?
You would be the coffee-shop owner and use the pc as your workstation as well. 
The rest would be ?external? users?

Haven't yet figured out what to propose that wouldn't "throw baby out
with the bath water".

So you are wasting bandwidth without a proposal.
You want something to change but don't know what yet.

-freak

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[tomas]

-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 were holding it wrong.

cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkBkrIACgkQBcgs9XrR2kZUIACffBPd+HfOSjcIDSsxuYdvcwL0
4iIAnitbWWZOm47UI5L79ditgZ/OEiU4
=uXWx
-END PGP SIGNATURE-

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Richard Owlett]

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 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".

wooledg:~$ ip link help
[... enormous BNF dump, entirely missing -s, or any reference whatsoever
to the fact that you can stick options between "ip" and "link" ...]

wooledg:~$ ip -s link show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
   RX: bytes  packets  errors  dropped overrun mcast
   380719013  1442490  0   0   0   4731
   TX: bytes  packets  errors  dropped carrier collsns
   57971257   614586   0   0   0   0

Aha!


My bad. I actually only got as far as discovering "ip -s link" on my own
system. As I was typing up the email I remembered that Richard was after
statistics for a specific interface. I should have been more diligent in
working out the correct format.


(Sadly, this is my *typical* experience with the ip command -- trying
random things until one of them works, because the documentation
is impenetrable, and the syntax barely guessable, and certainly not
predictable.)


ip *could* do a lot better, it's true. As a monolithic tool, there's not
really much excuse for the different sub-tools to parse the commands
differently. As you say, "ip address" expects the device to be expressed
as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
know.


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 usb0

No hint of either in so-called man page.

I accidentally discovered it by following up links when doing DuckDuckGo
search for "documentation iproute2" (w/o quotes).

I then did another netinst of testing. There is some subset of the "ip"
command available after the network has been configured. The help is too
abbreviated to be useful.


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 *IDENTICAL* command as root.
In the *MAJORITY* of cases that it runs demonstrates that someone at 
sometime decided to restrict some computer owners from using their own 
computer in a reasonable manner.


Remember Linux borrows heavily from an OS designed in another era for a 
another audience. I have yet to run across a case where any distinction 
should be made between "user richard" and "user root". I do not take 
that as necessary and sufficient conditions to abolish questionable 
conventions. They might be occasionally valuable.


In the age of laptops, tablets, and so-called "smart phones" I think the 
more relevant basic distinction would be between "physically local user" 
and "physically external user".


Haven't yet figured out what to propose that wouldn't "throw baby out 
with the bath water".

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Curt]

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 you are just using it to view an interface rather
>> >than to change the interface.
>
>> And that makes me incorrect how??
>
> Because your statement is literally untrue.  You said a thing which does
> not match reality.
>

It's an alternative fact, I think. I've always run ifconfig as a user using the
full path--/sbin/ifconfig (to get my ip address). 

But then there's ip, which *is* in my path

ip addr

I've seen people recommending ip as a superior alternative to ifconfig.

Anyway, I'm adding nothing of extra value to the thread, as usual.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Jörg-Volker Peetz]

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, for this thread's topic would be
>>   ip -s link
>> or
>>   ip -s link ls usb0
>>
>> No hint of either in so-called man page.
> 
> There are man pages for each command, such as
> https://manpages.debian.org/jessie/iproute2/ip-link.8.en.html . They're listed
> in the SEE ALSO section, but there could be a mention higher up in the text
> advising the user to consult the specific pages.
> 
> Also, typing 'man ip link' should work on the command line.
> 

I'll second this. The ip command is nearly as complex as git. The CLI help
is also usefull, like

$ ip help

and then

$ ip addr help

In the end, may be, you're satisfied with the output of

$ ip -s -h addr s eth0

-- 
Regards,
jvp.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Eduardo M KALINOWSKI]

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 usb0

No hint of either in so-called man page.


There are man pages for each command, such as  
https://manpages.debian.org/jessie/iproute2/ip-link.8.en.html .  
They're listed in the SEE ALSO section, but there could be a mention  
higher up in the text advising the user to consult the specific pages.


Also, typing 'man ip link' should work on the command line.


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Lisi Reisz]

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 [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".
> >>
> >> wooledg:~$ ip link help
> >> [... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >> to the fact that you can stick options between "ip" and "link" ...]
> >>
> >> wooledg:~$ ip -s link show eth0
> >> 2: eth0:  mtu 1500 qdisc pfifo_fast
> >> state UP mode DEFAULT group default qlen 1000
> >>link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >>RX: bytes  packets  errors  dropped overrun mcast
> >>380719013  1442490  0   0   0   4731
> >>TX: bytes  packets  errors  dropped carrier collsns
> >>57971257   614586   0   0   0   0
> >>
> >> Aha!
> >
> > My bad. I actually only got as far as discovering "ip -s link" on my own
> > system. As I was typing up the email I remembered that Richard was after
> > statistics for a specific interface. I should have been more diligent in
> > working out the correct format.
> >
> >> (Sadly, this is my *typical* experience with the ip command -- trying
> >> random things until one of them works, because the documentation
> >> is impenetrable, and the syntax barely guessable, and certainly not
> >> predictable.)
> >
> > ip *could* do a lot better, it's true. As a monolithic tool, there's not
> > really much excuse for the different sub-tools to parse the commands
> > differently. As you say, "ip address" expects the device to be expressed
> > as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
> > know.
>
> 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 usb0
>
> No hint of either in so-called man page.
>
> I accidentally discovered it by following up links when doing DuckDuckGo
> search for "documentation iproute2" (w/o quotes).
>
> I then did another netinst of testing. There is some subset of the "ip"
> command available after the network has been configured. The help is too
> abbreviated to be useful.

But did /sbin/ifconfig work?

Lisi

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Richard Owlett]

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 unknown, try "ip link help".

wooledg:~$ ip -s link dev eth0
Command "dev" is unknown, try "ip link help".

wooledg:~$ ip link help
[... enormous BNF dump, entirely missing -s, or any reference whatsoever
to the fact that you can stick options between "ip" and "link" ...]

wooledg:~$ ip -s link show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
   RX: bytes  packets  errors  dropped overrun mcast
   380719013  1442490  0   0   0   4731
   TX: bytes  packets  errors  dropped carrier collsns
   57971257   614586   0   0   0   0

Aha!


My bad. I actually only got as far as discovering "ip -s link" on my own
system. As I was typing up the email I remembered that Richard was after
statistics for a specific interface. I should have been more diligent in
working out the correct format.



(Sadly, this is my *typical* experience with the ip command -- trying
random things until one of them works, because the documentation
is impenetrable, and the syntax barely guessable, and certainly not
predictable.)


ip *could* do a lot better, it's true. As a monolithic tool, there's not
really much excuse for the different sub-tools to parse the commands
differently. As you say, "ip address" expects the device to be expressed
as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
know.



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 usb0

No hint of either in so-called man page.

I accidentally discovered it by following up links when doing DuckDuckGo 
search for "documentation iproute2" (w/o quotes).


I then did another netinst of testing. There is some subset of the "ip" 
command available after the network has been configured. The help is too 
abbreviated to be useful.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Greg Wooledge]

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 change the interface.

> And that makes me incorrect how??

Because your statement is literally untrue.  You said a thing which does
not match reality.

wooledg:~$ id
uid=1000(wooledg) gid=1000(wooledg) 
groups=1000(wooledg),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev)
wooledg:~$ /sbin/ifconfig
eth0: flags=4163  mtu 1500
inet 10.76.172.97  netmask 255.255.254.0  broadcast 10.76.173.255
inet6 fe80::a28c:fdff:fec3:89e0  prefixlen 64  scopeid 0x20
ether a0:8c:fd:c3:89:e0  txqueuelen 1000  (Ethernet)
RX packets 1575652  bytes 408905635 (389.9 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 708994  bytes 65901838 (62.8 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 16  memory 0xd100-d102  

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 1270503  bytes 260699031 (248.6 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1270503  bytes 260699031 (248.6 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[tomas]

-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 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 since device power on would be almost ideal
> >granularity.
> 
> Is ifconfig available on a console during installation?
> >>>
> >>>I can not check at the moment.
> >>
> >>I attempted to check this morning using
> >>  debian-stretch-DI-rc3-i386-netinst.iso
> >>
> >>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 ifconfig.
> >>I again got "Command not found".
> >>That seemed odd.
> >>
> >>Having previously done an install using the same ISO and having selected the
> >>MATE desktop, I repeated the above with the same error.
> >>
> >>I have no problem running ifconfig under Squeeze (8.6.0).
> >>
> >>Is it "bug" or "operator error"?
> >
> >Let us see how a reasonably experienced user could have investigated the
> >cause. The package which provides ifconfig can be found from 'dpkg -S'
> >on a machine which has it. Or from the packages page on the Debian web
> >site,
> >
> >The ISO can be opened up (I use mc) and the /pool/main directory entered.
> >Go to "n". See it? No? Not a bug, then.
> 
> 
> "ifconfig" has to be run as root.

If you want to change something, yes. If not -- no.

Perhaps you're being misled by the fact that ifconfig usually lives in
/usr/bin, which usually isn't in a regular user's path, Therefore, just
invoking "ifconfig" as a regular user ends (usually) like so:

  tomas@rasputin:~$ ifconfig
  bash: ifconfig: command not found

That means your shell isn't finding the command. That *doesn't mean" you
are not allowed to invoke it (nor is that the message on the wrapping :)

Try with full path:

  tomas@rasputin:~$ /sbin/ifconfig
  eth0  Link encap:Ethernet  HWaddr f0:de:f1:71:84:41  
inet addr:10.10.69.65  Bcast:10.10.69.127  Mask:255.255.255.128
[blah blah blah]

Now if you tried to change the IP address as a regular user...

  tomas@rasputin:~$ /sbin/ifconfig eth0 10.10.69.66
  SIOCSIFADDR: Operation not permitted
  SIOCSIFFLAGS: Operation not permitted

Ouch. My operating system scolded me. *That* was an authorization failure
(and not a "command not found"). "Read the message" [1]


Cheers

[1] Ed Krol "The Whole Internet User's Guide and Catalog"
https://en.wikipedia.org/wiki/Whole_Internet_User%27s_Guide_and_Catalog

- - tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkArvkACgkQBcgs9XrR2kaP0ACeKzkAIB7kffOm19P9FhmDW+PY
CI0An2cd8dqSc09os2XdGZ/0cgbLN6eL
=DgK8
-END PGP SIGNATURE-

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Ric Moore]

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 it to view an interface rather
than to change the interface.

ifconfig lives in the /sbin directory, which is not in the default PATH
that user accounts get when they login.  It *is* in the PATH that you
get when you run su, or sudo.  That's why it works when you slap sudo
in front of it.

You could also simply run /sbin/ifconfig directly.  Or, you could change
your PATH variable to include the /sbin directory.  Either of these will
let you run ifconfig without root privileges.


And that makes me incorrect how?? For a new user, who doesn't want to 
dink with $PATH, su or sudo will run ifconfig. It doesn't run, out of 
the box, as USER, which was the OP's original issue. Ric

.


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Greg Wooledge]

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 change the interface.

ifconfig lives in the /sbin directory, which is not in the default PATH
that user accounts get when they login.  It *is* in the PATH that you
get when you run su, or sudo.  That's why it works when you slap sudo
in front of it.

You could also simply run /sbin/ifconfig directly.  Or, you could change
your PATH variable to include the /sbin directory.  Either of these will
let you run ifconfig without root privileges.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Ric Moore]

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 total of
uploaded/downloaded data since device power on would be almost ideal
granularity.


Is ifconfig available on a console during installation?


I can not check at the moment.


I attempted to check this morning using
  debian-stretch-DI-rc3-i386-netinst.iso

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 ifconfig.
I again got "Command not found".
That seemed odd.

Having previously done an install using the same ISO and having selected the
MATE desktop, I repeated the above with the same error.

I have no problem running ifconfig under Squeeze (8.6.0).

Is it "bug" or "operator error"?


Let us see how a reasonably experienced user could have investigated the
cause. The package which provides ifconfig can be found from 'dpkg -S'
on a machine which has it. Or from the packages page on the Debian web
site,

The ISO can be opened up (I use mc) and the /pool/main directory entered.
Go to "n". See it? No? Not a bug, then.



"ifconfig" has to be run as root.
ric@iam:~$ sudo ifconfig
[sudo] password for ric:
enp8s0: flags=4163  mtu 1500
inet 192.168.0.3  netmask 255.255.255.0  broadcast 192.168.0.255
inet6 fe80::16da:e9ff:fe09:4706  prefixlen 64  scopeid 0x20
ether 14:da:e9:09:47:06  txqueuelen 1000  (Ethernet)
RX packets 6879  bytes 3709031 (3.7 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 6276  bytes 596404 (596.4 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 35  base 0x9000

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 88693  bytes 15355517 (15.3 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 88693  bytes 15355517 (15.3 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ric@iam:~$




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[tomas]

-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 [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".
> >
> >wooledg:~$ ip link help
> >[... enormous BNF dump, entirely missing -s, or any reference whatsoever
> >to the fact that you can stick options between "ip" and "link" ...]
> >
> >wooledg:~$ ip -s link show eth0
> >2: eth0:  mtu 1500 qdisc pfifo_fast state 
> >UP mode DEFAULT group default qlen 1000
> >   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
> >   RX: bytes  packets  errors  dropped overrun mcast
> >   380719013  1442490  0   0   0   4731
> >   TX: bytes  packets  errors  dropped carrier collsns
> >   57971257   614586   0   0   0   0
> >
> >Aha!
> 
> My bad [...]

I'd say "ip's bad"

> ip *could* do a lot better [...]

That's why I end up (after re-trying ip for a short while) installing
net-tools. Every single time.

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkAohkACgkQBcgs9XrR2kYaPwCfZXHlL7f7pCcRZjLYHPHumCmu
0aMAnRjNW482CD5j5LKehIaR8VgM6N46
=1vqx
-END PGP SIGNATURE-

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Darac Marjal]

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 link dev eth0
Command "dev" is unknown, try "ip link help".

wooledg:~$ ip link help
[... enormous BNF dump, entirely missing -s, or any reference whatsoever
to the fact that you can stick options between "ip" and "link" ...]

wooledg:~$ ip -s link show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
   link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
   RX: bytes  packets  errors  dropped overrun mcast
   380719013  1442490  0   0   0   4731
   TX: bytes  packets  errors  dropped carrier collsns
   57971257   614586   0   0   0   0

Aha!


My bad. I actually only got as far as discovering "ip -s link" on my own
system. As I was typing up the email I remembered that Richard was after
statistics for a specific interface. I should have been more diligent in
working out the correct format.



(Sadly, this is my *typical* experience with the ip command -- trying
random things until one of them works, because the documentation
is impenetrable, and the syntax barely guessable, and certainly not
predictable.)


ip *could* do a lot better, it's true. As a monolithic tool, there's not
really much excuse for the different sub-tools to parse the commands
differently. As you say, "ip address" expects the device to be expressed
as "dev eth0", so why doesn't "ip link" handle it the same way? I don't
know.

--
For more information, please reread.


signature.asc
Description: PGP signature

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Brian]

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
> >>>uploaded/downloaded data since device power on would be almost ideal
> >>>granularity.
> >>
> >>Is ifconfig available on a console during installation?
> >
> >I can not check at the moment.
> 
> I attempted to check this morning using
>   debian-stretch-DI-rc3-i386-netinst.iso
> 
> 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 ifconfig.
> I again got "Command not found".
> That seemed odd.
> 
> Having previously done an install using the same ISO and having selected the
> MATE desktop, I repeated the above with the same error.
> 
> I have no problem running ifconfig under Squeeze (8.6.0).
> 
> Is it "bug" or "operator error"?

Let us see how a reasonably experienced user could have investigated the
cause. The package which provides ifconfig can be found from 'dpkg -S'
on a machine which has it. Or from the packages page on the Debian web
site,

The ISO can be opened up (I use mc) and the /pool/main directory entered.
Go to "n". See it? No? Not a bug, then.

-- 
Brian.

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Greg Wooledge]

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".

wooledg:~$ ip link help
[... enormous BNF dump, entirely missing -s, or any reference whatsoever
 to the fact that you can stick options between "ip" and "link" ...]

wooledg:~$ ip -s link show eth0
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
link/ether a0:8c:fd:c3:89:e0 brd ff:ff:ff:ff:ff:ff
RX: bytes  packets  errors  dropped overrun mcast   
380719013  1442490  0   0   0   4731
TX: bytes  packets  errors  dropped carrier collsns 
57971257   614586   0   0   0   0   

Aha!

(Sadly, this is my *typical* experience with the ip command -- trying
random things until one of them works, because the documentation
is impenetrable, and the syntax barely guessable, and certainly not
predictable.)

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Jochen Spieker]

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 ifconfig.
> I again got "Command not found".
> That seemed odd.

Did you check whether /sbin/ was in your $PATH at that time or did you
try to run it as /sbin/ifconfig? The problem may simply be that the
executable was not found in your $PATH although the executable was where
it should be.

(Apart from that I thought that ifconfig and friends were not really
necessary anymore since they were replaced by the "ip" tool. I think the
priority of this package was demoted from important to optional but I
cannot check at the moment. Maybe net-tools just isn't part of a
standard install anymore. If you want ifconfig, you need to install
net-tools.)

J.
-- 
Whenever I hear the word 'art' I reach for my visa card.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: BUG or OPERATOR error? - was [Re: Measuring aggregate internet useage?]

[Darac Marjal]

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 since device power on would be almost ideal
granularity.


Is ifconfig available on a console during installation?


I can not check at the moment.


I attempted to check this morning using
 debian-stretch-DI-rc3-i386-netinst.iso

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 ifconfig.
I again got "Command not found".
That seemed odd.

Having previously done an install using the same ISO and having 
selected the MATE desktop, I repeated the above with the same error.


I have no problem running ifconfig under Squeeze (8.6.0).

Is it "bug" or "operator error"?


"ifconfig" was part of the "net-tools" package. Recently, though, this
has been deprecated in favour of the "iproute2" package. The main
difference is that "ifconfig", "route" and a few other tools are now
replaced by a single "ip" command. The interface to "ip", however, is
completely different.

For interface statistics from ip, try "ip -s link [interface]".


--
For more information, please reread.


signature.asc
Description: PGP signature

Re: bug report

[Thibault Roulet]

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 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 operating systems.
>
> Have you checked?
>
> -dsr-

Re: bug report

[Dan Ritter]

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 operating systems.

Have you checked?

-dsr-

Fwd: Re: bug report

[GiaThnYgeia]

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 

I'm using a USB3 docking station for HDD. (Sharkoon QuickPort USB 3)

During copies from a plugged disk, the speed falls to zero after a few
seconds and the system is like reseting the link with the USB device.
Everything works fine when plugged on a USB2 port.
I have a bunch of errors in /var/log/messages (see attached file) but
then no idea of what is causing this problem.

Don't hesitate to ask if you need more logs or tests.

Cheers,

Thibault

> Thibault Roulet:
>> Hi all,
>>
>> I have some serious issues with USB 3 HDD docking station, in which
>> package should I report this bug ?
>>
>> Thanks
>>
>> Thibault Roulet

Feb 21 09:10:43 sbitpc23 kernel: [597463.015702] usb 4-6: new SuperSpeed USB 
device number 6 using xhci_hcd
Feb 21 09:10:43 sbitpc23 kernel: [597463.040260] usb 4-6: New USB device found, 
idVendor=1759, idProduct=5002
Feb 21 09:10:43 sbitpc23 kernel: [597463.040265] usb 4-6: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Feb 21 09:10:43 sbitpc23 kernel: [597463.040267] usb 4-6: Product: MassStorage 
Device
Feb 21 09:10:43 sbitpc23 kernel: [597463.040269] usb 4-6: Manufacturer: USB 3.0
Feb 21 09:10:43 sbitpc23 kernel: [597463.040270] usb 4-6: SerialNumber:  
WD-WCC1S5731799
Feb 21 09:10:43 sbitpc23 kernel: [597463.056490] scsi host6: uas
Feb 21 09:10:43 sbitpc23 kernel: [597463.057299] scsi 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.057369] scsi 6:0:0:0: Direct-Access
 USB 3.0  LucidPort UAS0100 PQ: 0 ANSI: 4
Feb 21 09:10:43 sbitpc23 kernel: [597463.057906] scsi 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.058458] scsi 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.058970] scsi 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.059153] sd 6:0:0:0: Attached scsi 
generic sg2 type 0
Feb 21 09:10:43 sbitpc23 kernel: [597463.059395] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.059899] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 mtp-probe: checking bus 4, device 6: 
"/sys/devices/pci:00/:00:14.0/usb4/4-6"
Feb 21 09:10:43 sbitpc23 mtp-probe: bus: 4, device: 6 was not an MTP device
Feb 21 09:10:43 sbitpc23 kernel: [597463.059924] sd 6:0:0:0: [sdc] 1953525168 
512-byte logical blocks: (1.00 TB/932 GiB)
Feb 21 09:10:43 sbitpc23 kernel: [597463.060425] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.060951] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.061470] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.061989] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.062448] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.062455] sd 6:0:0:0: [sdc] Write 
Protect is off
Feb 21 09:10:43 sbitpc23 kernel: [597463.062917] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.063436] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.063956] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.064318] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.064838] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.065367] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 21 09:10:43 sbitpc23 kernel: [597463.065880] sd 6:0:0:0: uas_sense: urb 
length 26 disagrees with IU sense data length 0, using 0 bytes of sense data
Feb 

Re: bug report

[Ben Finney]

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 incorrectly.
That's what determines which package should receive the bug report.

-- 
 \   “We must respect the other fellow's religion, but only in the |
  `\   sense and to the extent that we respect his theory that his |
_o__) wife is beautiful and his children smart.” —Henry L. Mencken |
Ben Finney

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

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 the Sid 4.8.0-2 kernel but not
as quick to load as the 4.7.0-1 kernel which works with no
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression.
Sometimes it will do a first boot without assistance from me but on the
reboot will lockup without assistance. I'm being forced to use the
linux-image from Jessie(works swell) in order to get updates.
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.

If you need testing of assistance let me know.


Hello,
Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965.
regards,


So..
I installed linux-image-4.9.0-2-amd64 to Stretch and it did not work, 
never got to sddm, just loads a black screen and then 
freeze/lockup/quits/dies/kaput.


Also I worth mentioning, the regression while booting Sid makes it 
painful to watch it boot, but it will get to the plasma desktop.

4.7.0-1-amd64 is still installed and quick too, works swell.

regards,
--
Jimmy Johnson

Debian St etch - Plasma 5.8.2 - Intel Mobile 965 - EXT4 at sda6
Registered Linux User #380263

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

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 as the 4.7.0-1 kernel which works with no
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression.
Sometimes it will do a first boot without assistance from me but on the
reboot will lockup without assistance. I'm being forced to use the
linux-image from Jessie(works swell) in order to get updates.
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.

If you need testing of assistance let me know.


Hello,
Update, linux-image-4.9.0-2-amd64 now in Sid is working with i965.
regards,
--
Jimmy Johnson

Debian Sid/Testing - Plasma 5.8.4 - AMD64 - EXT4 at sda9
Registered Linux User #380263

Re: Bug#1 Freeze - Re: Intel i965

[Jimmy Johnson]

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
problem. In Stretch the 4.8.0-2 kernel is freezing the system,
4.7.0-1 kernel works swell - Intel Mobile GM965/GL960 Integrated
Graphics. Plasma and SDDM."

Here's an update for the i965, the linux-image-4.7 is no longer in the 
reposes, but is still on my laptop. linux-image-4.8 and 4.9 work only if 
I keep pressing ctrl+alt+F1, F2, F7, etc., way to much regression. 
Sometimes it will do a first boot without assistance from me but on the 
reboot will lockup without assistance. I'm being forced to use the 
linux-image from Jessie(works swell) in order to get updates. 
jessie-backports 4.8 and 4.9 do not work with plasma on the i965.


If you need testing of assistance let me know.
--
Jimmy Johnson

Debian Stretch - Plasma 5.8.4 - EXT4 at sda11
Registered Linux User #380263

Re: Bug#1 Freeze

[Jimmy Johnson]

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 kernel
to 4.7 and it will take care of the problem.

Same here !

Regards

Mourad



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 problem.  In Stretch the 4.8.0-2 
kernel is freezing the system, 4.7.0-1 kernel works swell - Intel Mobile 
GM965/GL960 Integrated Graphics. Plasma and SDDM.

--
Jimmy Johnson

Ubuntu 16.04 LTS - Plasma 5.8.4 - AMD64 - EXT4 at sda22
Registered Linux User #380263

Re: bug - nvidia related

[Alberto Luaces]

"Janusz S. Kulpa" writes:

> Hello. I am unsure which package is it related to and how to properly
> summit a bug report. I think it may be nvidia-drivers,
> xserver-xorg-video-nvidia or nvidia-kernel-dkms.
>
> I am running stretch. Yesterday I was updating the packages (900+),
> including xserver, kernel (4.3 -> 4.6) and nvidia-drivers
> After reboot, the screen was black. After some time I realized that
> this is a problem with nvidia modules - they name changed so there is
> a -current- in the middle of the name. 
>
> The solution was available in /etc/nvidia/nvidia-modprobe.conf,
> however it was not linked/copied to /etc/modprobe.d/ and no
> information about need to link it by hand was provided

Hi, Janusz:

% dpkg -S nvidia-modprobe.conf
nvidia-kernel-support: /etc/nvidia/current/nvidia-modprobe.conf

so since the file is owned by "nvidia-kernel-support", I would submit
the bug against it.

-- 
Alberto

Re: Bug with lib ssl

[Sven Joachim]

On 2016-06-18 01:45 -0400, Fabrice Vaillant wrote:

> I'm running debian testing and I have encountered a weird bug. Wanted
> to check if that was a real bug or an issue on my end.

It's an issue on the other end (media.w3.org).

> The site https://www.w3.org/2010/05/video/mediaevents.html fails on my
> computer with both iceweasel on chromium whereas it succeds on other
> computer (not debian) I have tried it with. The reason is that media
> content downloaded  from media.w3.org over https fail due too :
>
> ```
> An error occurred during a connection to media.w3.org.
>
> SSL received a record that exceeded the maximum permissible length.
>
> (Error code: ssl_error_rx_record_too_long)

This means that the web server on media.w3.org listens on port 443, but
it speaks plain HTTP there.  Visit http://media.w3.org:443 to convince
yourself.

Cheers,
   Sven

Re: Bug with lib ssl

[Steve Witt]

On Sat, 18 Jun 2016, Fabrice Vaillant wrote:


Hey

I'm running debian testing and I have encountered a weird bug. Wanted to 
check if that was a real bug or an issue on my end.


The site https://www.w3.org/2010/05/video/mediaevents.html fails on my 
computer with both iceweasel on chromium whereas it succeds on other computer 
(not debian) I have tried it with. The reason is that media content 
downloaded  from media.w3.org over https fail due too :


```
An error occurred during a connection to media.w3.org.

SSL received a record that exceeded the maximum permissible length.

(Error code: ssl_error_rx_record_too_long)
```
Similar error message show up when I try to directly download the content 
from the site using curl. I suspect an issue in the ssl implementation but I 
have not been able to reporduce on other site.


Does anybody have a similar problem?


Works for me using Firefox and Google Chrome on unstable. Also works using 
Firefox on Jessie.  I don't have a testing system to try.

Re: bug reporting and packages

[Cindy-Sue Causey]

On 4/4/16, Alan Fujinami  wrote:
> Hi,
> I was going to use the bugreport feature of my Debian 8.3 install... it say
> if I don't know the package then I should contact you...
> my bug is that I have a ps2mouse. Whenever the computer goes into
> screensaver mode, the mouse icon disappears. I have to reboot to bring it
> back. I tried modprobe and a few other things to no avail.
> So what package is affected?
> alan


While you're waiting for others to respond, how many PS/2 ports do you
have? If there's more than one, can you take a quick peek and make
sure you're actually plugged into the mouse port and not the keyboard
one?

That option came up as a fix on a recent Debian-User thread.
Additionally, I also experienced that a few years ago. In those
instances, the mouse would function seemingly normal for a while and
then would eventually glitch to where nothing short of a reboot would
fix things.

Just out of curiosity, too, how much memory do you have? Occasionally
memory (or the lack of it) plays a part in glitches related to paths
that head towards hibernate, suspend, etc.

A PS to it is this is a good trigger for learning the keyboard
shortcuts necessary for at least getting to "Log Out" and/or "Settings
> Mouse and Touchpad" under the Applications menu. ALT+F1 works for
me, grin.

Just thinking out loud.. :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *

Re: Bug report (ASUS M2NPV/VM: Garbled screen instead of GUI)

[Cindy-Sue Causey]

On 4/4/16, Gene Heskett  wrote:
> On Monday 04 April 2016 05:01:57 Manfred wrote:
>
>> >If you are unable to determine which package your bug report should
>> > be filed against, please send e-mail to the Debian user mailing list
>> > asking for advice.
>>
>> Ok, so I'm asking for advice, since Debian doesn't even boot
>> correctly.
>>
>> Besides that, my bug report would be as follows:
>>
>> Package: ???
>> Version: 8.3.0-live ?
>>
>> No GUI when booting debian-live-8.3.0-i386-gnome-desktop.iso as well
>> as debian-live-8.3.0-amd64-gnome-desktop.iso.
>>
>> Instead of the GUI (desktop etc.) only a garbled screen: Sometimes
>> black with only a mouse pointer, sometimes yellow and green horizontal
>> blocks or other weird patterns. The system mostly hangs after a couple
>> of mouse clicks.
>>
>> ASUS motherboard M2NPV/VM with on-board NVIDIA GeForce 6150 graphics,
>> 3GB RAM, Athlon X2 240e.
>
> Do you know what "family" that Athlon is?  It should be listed as the
> machine is booting if you get rid of the quiet and splash keywords in
> the grub command line by using the grub editor.
>
> Family 15 and earlier have no microcode update capability, and family 15
> in particular has an unfixable halt bug.


What about something like video driver and/or screen resolution? I
have had a similar problem with an older Debian based distro when all
other distros work (are viewable). It was always just kneejerk
reaction that it "felt like" driver or resolution issue. It occurred
across multiple laptops, too.

It SEEMS LIKE I was able to get the distro to at least half function
if I could navigate through the garble and into the settings manager.
The visuals would be duplicated anywhere from 3 to 7 times across the
screen. I just reread the issue description above. It sure sounds VERY
familiar although it has been a long time since I've experienced it.
:)

Just thinking out loud... :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *

Re: Bug report (ASUS M2NPV/VM: Garbled screen instead of GUI)

[Gene Heskett]

On Monday 04 April 2016 05:01:57 Manfred wrote:

> >If you are unable to determine which package your bug report should
> > be filed against, please send e-mail to the Debian user mailing list
> > asking for advice.
>
> Ok, so I'm asking for advice, since Debian doesn't even boot
> correctly.
>
> Besides that, my bug report would be as follows:
>
>
> Package: ???
> Version: 8.3.0-live ?
>
>
> No GUI when booting debian-live-8.3.0-i386-gnome-desktop.iso as well
> as debian-live-8.3.0-amd64-gnome-desktop.iso.
>
> Instead of the GUI (desktop etc.) only a garbled screen: Sometimes
> black with only a mouse pointer, sometimes yellow and green horizontal
> blocks or other weird patterns. The system mostly hangs after a couple
> of mouse clicks.
>
> ASUS motherboard M2NPV/VM with on-board NVIDIA GeForce 6150 graphics,
> 3GB RAM, Athlon X2 240e.

Do you know what "family" that Athlon is?  It should be listed as the 
machine is booting if you get rid of the quiet and splash keywords in 
the grub command line by using the grub editor.

Family 15 and earlier have no microcode update capability, and family 15 
in particular has an unfixable halt bug.

I just recycled just such a quite well built and performing machine 
because it froze at random times while running potentially dangerous 
machinery via a CNC program.  An off-lease, no HD Dell 745 took that 
machines hard drive, booted from it, and except for what I consider to 
be a huge bug in udev that destroys networking, fired right up and ran 
the machine and gives me power fail to power fail uptimes.

Family 16, "hex" 10 and up can be patched on the bootup with microcode.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Bug ?

[Adam Wilson]

On Sat, 12 Mar 2016 18:53:22 +0100 Aymeric Do 
wrote:

> Hello,
> This is message in english (LANG=C) and example with reportbug :
> 
> (reportbug:2211): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "adwaita",
> 
> (reportbug:2211): Gtk-WARNING **: Unable to locate theme engine in
> module_path: "adwaita",
> 
> But this warning come with a lot of command, like reportbug, keepassx
> etc...

A question:

Is the Adwaita theme installed on your system?

a) If not, but the program runs after the warning anyway, then
this is not a bug.

b) If not, and the program fails to start because of this, then
this is a bug. Programs should not require specific GTK+ themes.

c) If Adwaita is installed, but this warning is displayed
anyway, then this is a bug.

a) is not a bug. b) and c) are. Which is your case?

Re: Bug ?

[Sven Arvidsson]

On Sat, 2016-03-12 at 18:49 +0100, Aymeric Do wrote:
> Hello,
> I have several warning in my terminal when I launch program as
> reportbug,
> keepassx etc.
> 
> Warning :
> Gtk-WARNING **: Impossible de trouver le moteur de thème dans
> module_path :
> « adwaita »
> 
> I think that is a bug on

I wouldn't exactly call it a bug. Adwaita is the default GTK+ theme in
GNOME and it doesn't seem to be found on your system, 

You could try to install gnome-themes-standard and see if that changes
it, or try another theme.
 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5



signature.asc
Description: This is a digitally signed message part

Re: Bug ?

[Aymeric Do]

Sorry my email was sent by error :

This is detail of my debian OS :
No LSB modules are available.
Distributor ID:Debian
Description:Debian GNU/Linux testing-proposed-updates (sid)
Release:testing-proposed-updates
Codename:sid

What packet is concerning by this bug if this is a bug ?


Thank you

Regards,
gnutux95

2016-03-12 18:49 GMT+01:00 Aymeric Do :

> Hello,
> I have several warning in my terminal when I launch program as reportbug,
> keepassx etc.
>
> Warning :
> Gtk-WARNING **: Impossible de trouver le moteur de thème dans
> module_path : « adwaita »
>
> I think that is a bug on
>
>

Re: Bug ?

[Aymeric Do]

Hello,
This is message in english (LANG=C) and example with reportbug :

(reportbug:2211): Gtk-WARNING **: Unable to locate theme engine in
module_path: "adwaita",

(reportbug:2211): Gtk-WARNING **: Unable to locate theme engine in
module_path: "adwaita",

But this warning come with a lot of command, like reportbug, keepassx
etc...

Regards,
gnutux95

2016-03-12 18:51 GMT+01:00 Aymeric Do :

> Sorry my email was sent by error :
>
> This is detail of my debian OS :
> No LSB modules are available.
> Distributor ID:Debian
> Description:Debian GNU/Linux testing-proposed-updates (sid)
> Release:testing-proposed-updates
> Codename:sid
>
> What packet is concerning by this bug if this is a bug ?
>
>
> Thank you
>
> Regards,
> gnutux95
>
> 2016-03-12 18:49 GMT+01:00 Aymeric Do :
>
>> Hello,
>> I have several warning in my terminal when I launch program as reportbug,
>> keepassx etc.
>>
>> Warning :
>> Gtk-WARNING **: Impossible de trouver le moteur de thème dans
>> module_path : « adwaita »
>>
>> I think that is a bug on
>>
>>
>

Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)

[Ian Campbell]

On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote:
> [...]
> Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 GNU/Linux
> 
> [...]
> Any idea what is the problem? 

Your local vmlinux and initrd binaries are out of sync with the kernel
modules in the mirror network, due to the kernel update in the latest point
release. i.e. you need to update the binaries on your PXE server to deb8u2.

The current Jessie kernel is now 3.16.7-ckt20-1+deb8u2.

Ian.

Re: Bug report - ext4: Unknown symbol __getblk_gfp (err 0)

[Ben Hutchings]

On Thu, 2016-02-18 at 13:18 +0100, Miroslav Svoboda wrote:
> Dear Debian team, 
> 
> I have problem with debian Jessie PXE installation with preseed. I'm
> trying to install Debian Jessie on amd64 server. The installation goes
> fine until partitionning and fails right after when trying to mount the
> newly created partitions with ext4 filesystem. Dmesg give us an idea
> about the error that seems related to filesystem module:
> 
> ext4: Unknown symbol __bread_gfp (err 0)
> ext4: Unknown symbol __getblk_gfp (err 0)
>
> uname -a:
> Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64
> GNU/Linux
[...]

This is the original kernel image for jessie (from 8.0).  Not all the kernel 
modules from current jessie (8.3) will work with it.
You must update your netboot images after each point release.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

signature.asc
Description: This is a digitally signed message part

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

[Steffen Nurpmeso]

Rick Thomas  wrote:
 |On Dec 30, 2015, at 3:36 AM, Steffen Nurpmeso  wrote:
 |> Rick Thomas  wrote:
 |>|Hi Steffan,
 |> 
 |> (My name is Steffen)
 |
 |Ooops!  Sorry!

Don't worry, i had so many typos myself in what followed..

 ..
 |> It must be SETUID to a super-user that can impersonate as all

 |So the fix posted by Hilko Bengen is correct.  Thanks for the confirmation!

The Debian package system is quite complicated, but if chmod(1)
must be called explicitly then it is, yes.  Normally the
`doinstall' / `packager-install' make(1) rules (`install' in
v14.9) should do the right thing (tm) by themselves.
The current v14.8.6 has already learned and explicitly sorts
sources for reproducible-builds.org and alos should also work on
Debian/kFreeBSD out of the box, for example.  More in v14.9 (e.g.,
truly parallelizable build phase).

 |>|Thanks for all your help!
 |> 
 |> Hm.  Thanks to you.  Just complain loudly if something isn't what
 |> you’d expected!
 |
 |Don’t worry, I will!

Yes, please!

And a happy new year..

--steffen

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

[Rick Thomas]

On Dec 30, 2015, at 9:51 AM, Jörg-Volker Peetz  wrote:

> Steffen Nurpmeso wrote on 12/30/15 12:36:
>> Hello!
>> 
>> Rick Thomas  wrote:
> 
> 
>> |-rwxr-sr-x 1 root mail 10104 Dec  4 14:52 /usr/lib/s-nail/s-nail-privsep
> 
> Wouldn't these be enough rights for mailx to do it's work?
> I.e., owner: root, group: mail, sticky bit for the group?
> This works on my system (and on Rick's).
> 
> Regards,
> jvp.

Set-gid alone works for all my use cases, but I have never needed to use the 
“-u user” option to masquerade as someone different from myself.  If you need 
to do that, I’m guessing that nothing less than set-uid will do the job.  
Though I haven’t tried it so I don’t know for sure…

Enjoy!
Rick

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

[Rick Thomas]

On Dec 30, 2015, at 3:36 AM, Steffen Nurpmeso  wrote:

> Hello!
> 
> Rick Thomas  wrote:
> |Hi Steffan,
> 
> (My name is Steffen)

Ooops!  Sorry!

> Well, just as already shown in this thread, on my local box it is
> 
>  ?0[sdaoden@wales nail.git]$ ll /usr/local/libexec/s-nail-privsep
>  -r-sr-xr-x 1 root root 9860 Dec  2 14:45 /usr/local/libexec/s-nail-privsep*
> 
> It must be SETUID to a super-user that can impersonate as all
> users and groups that mailx(1) may potentially open system
> mailboxes for in order to give mailbox locks the UID and GID of
> the mailbox they are ment for.  Usually only root satisfies this.
> I thing i need to improve the wording (not examples) in make.rc
> and INSTALL.

So the fix posted by Hilko Bengen is correct.  Thanks for the confirmation!

> 
> |Thanks for all your help!
> 
> Hm.  Thanks to you.  Just complain loudly if something isn't what
> you’d expected!

Don’t worry, I will!

> Ciao,
> 
> |Rick
> 
> --steffen
> 

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

[Jörg-Volker Peetz]

Steffen Nurpmeso wrote on 12/30/15 12:36:
> Hello!
> 
> Rick Thomas  wrote:


>  |-rwxr-sr-x 1 root mail 10104 Dec  4 14:52 /usr/lib/s-nail/s-nail-privsep

Wouldn't these be enough rights for mailx to do it's work?
I.e., owner: root, group: mail, sticky bit for the group?
This works on my system (and on Rick's).

Regards,
jvp.

Re: Bug#806858 Re: s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied

[Steffen Nurpmeso]

Hello!

Rick Thomas  wrote:
 |Hi Steffan,

(My name is Steffen)

 |So what, exactly, are the correct permissions for s-nail-privsep?
 |
 |Should it be:
 |-rwxr-sr-x 1 root mail 10104 Dec  4 14:52 /usr/lib/s-nail/s-nail-privsep
 |or:
 |-rwsr-xr-x 1 root mail 10104 Dec  4 14:52 /usr/lib/s-nail/s-nail-privsep
 |or:
 |-rwsr-sr-x 1 root mail 10104 Dec  4 14:52 /usr/lib/s-nail/s-nail-privsep
 |
 |Or something else?

Well, just as already shown in this thread, on my local box it is

  ?0[sdaoden@wales nail.git]$ ll /usr/local/libexec/s-nail-privsep
  -r-sr-xr-x 1 root root 9860 Dec  2 14:45 /usr/local/libexec/s-nail-privsep*

It must be SETUID to a super-user that can impersonate as all
users and groups that mailx(1) may potentially open system
mailboxes for in order to give mailbox locks the UID and GID of
the mailbox they are ment for.  Usually only root satisfies this.
I thing i need to improve the wording (not examples) in make.rc
and INSTALL.

 |Thanks for all your help!

Hm.  Thanks to you.  Just complain loudly if something isn't what
you'd expected!
Ciao,

 |Rick

--steffen

Re: bug in single-user fsck mode

[Pete Greening]

Additionally, I can not (easily) unmount /var. rpm.statd is running and 
has a cwd of /var/lib/nfs, preventing normal system recovery. This seems 
very wrong.



On 10/09/2015 11:09 AM, Pete Greening wrote:

All,
I would like to report a bug, but I am not sure what package it 
belongs to. Probably systemd...


Here's what happens. I have a LVM LV formated ext4 for /var partition. 
At boot, there was a minor error and fsck failed due to a hard 
shutdown.   I received the well known error "UNEXPECTED INCONSISTENCY; 
RUN fsck MANUALLY." and was presented with an emergency mode login.
I proceed to login and run fsck against /var, however /var is already 
mounted. Apparently systemd somehow mounted the filesystem despite the 
errors. I really don't know what's going on here..


Additionally, networking has been brought up. The machine is not even 
booted to multi-user mode, should it really initialize the networking 
stack before completing the local file systems?


How do I submit this bug? any advice would be greatly appreciated.

Thank you



--
Pete Greening
pgreen...@bofanez.org
(505) 363-2406

Re: Bug? - Debian does not assign IP address after reboot?

[Sven Hartge]

linuxthefish  wrote:

> I removed allow-hotplug eth0 and it still does not auto configure :(

> Where would i find log files to diagnose this?

Please run

  ifup -v eth0

after a reboot if the error persists and paste the output verbatim to
the list.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: Bug? - Debian does not assign IP address after reboot?

[linuxthefish]

Hi,

I removed allow-hotplug eth0 and it still does not auto configure :(

Where would i find log files to diagnose this?

Thanks

On 16 September 2015 at 20:55, Sven Hartge  wrote:

> linuxthefish  wrote:
>
> > After I reboot my Debian machine it does not assign an IP to eth0. It
> > brings the interface up after a reboot, but does not set the IP on it!
> > Running a cronjob every min to set the IP address is the only way to
> > fix this, but why does it happen? Is this some sort of bug?
>
> > My interfaces file is as follows:
>
> > auto eth0
> > allow-hotplug eth0
> > iface eth0 inet static
> >   address 172.16.0.30
> >   netmask 255.255.0.0
>
> You cannot have both "auto eth0" _and_ "allow-hotplug eth0". Choose one.
>
> S°
>
> --
> Sigmentation fault. Core dumped.
>
>

Re: Bug? - Debian does not assign IP address after reboot?

[Seeker]

On 9/16/2015 12:38 PM, linuxthefish wrote:

Hi,

After I reboot my Debian machine it does not assign an IP to eth0. It
brings the interface up after a reboot, but does not set the IP on it!
Running a cronjob every min to set the IP address is the only way to
fix this, but why does it happen? Is this some sort of bug?

My interfaces file is as follows:

auto lo
iface lo inet loopback

auto eth0
allow-hotplug eth0
iface eth0 inet static
   address 172.16.0.30
   netmask 255.255.0.0

allow-hotplug wlan1
iface wlan1 inet static
 wpa-ap-scan 1
 wpa-scan-ssid 1
   wpa-ssid connect
   wpa-psk linuxthefish
address 192.168.43.200
netmask 255.255.255.0

Please can someone tell me why this happens? :(

Thanks!


I hope that is not your real wireless key.

If it is you might want to change it now that it has been shared in a 
public forum. ;-)


Later, Seeker

Re: Bug? - Debian does not assign IP address after reboot?

[Sven Hartge]

linuxthefish  wrote:

> After I reboot my Debian machine it does not assign an IP to eth0. It
> brings the interface up after a reboot, but does not set the IP on it!
> Running a cronjob every min to set the IP address is the only way to
> fix this, but why does it happen? Is this some sort of bug?

> My interfaces file is as follows:

> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
>   address 172.16.0.30
>   netmask 255.255.0.0

You cannot have both "auto eth0" _and_ "allow-hotplug eth0". Choose one.

S°

-- 
Sigmentation fault. Core dumped.

Re: Bug report

[Dominique Dumont]

On Sunday 13 September 2015 19:53:52 Peter Gonsalves wrote:
> I'm guessing my bug may have already been reported but have no idea what
> categories to use for reporting so I can't check. The bug is brightness on
> an HP EliteBook 8560w. The buttons adjust the app but this has no effect on
> the screen

I guess this bug is related to nvidia graphic drivers.

You can try to build a driver to restore backlight control:
https://github.com/guillaumezin/nvidiabl

HTH

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Re: Bug Reporting

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Aug 16, 2015 at 04:16:33AM +0800, Nafiez wrote:
> Hi,
> 
> I wanted to ask on what is the process to submit bug via e-mail. Can you
> help?

I assume you are talking about reporting a bug against a Debian package:
there's a comand for that called "reportbug". As argument you give it
the package name -- alternatively a complete file path belonging to the
package.

It goes then to gather information from the system to help package
maintainers pin-point the relevant software versions, asks you for
whatever information it "thinks" relevant and formats a mail with all
the necessary parts for a proper bug report.

Read the manual page of report-bug (type "man reportbug" at the command
line) and come back if you stumble upon any difficulties.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlXPpx8ACgkQBcgs9XrR2kaXKQCfQ25KxCQwurk4hzVl23GLu3Ry
Ns0An2OWK5CpgrgfR5x4XgpSnG2UpxBJ
=oAOh
-END PGP SIGNATURE-

Re: Bug Reporting

[Francesco Ariis]

On Sun, Aug 16, 2015 at 04:16:33AM +0800, Nafiez wrote:
> Hi,
> 
> I wanted to ask on what is the process to submit bug via e-mail. Can you
> help?
> 
> Thank you,
> Nafiez
> 

Hello Nafiez,
you usually report bugs via reportbug (open a terminal, type
`reportbug ` and follow the instructions).

There is a way to report directly using the mail, more info on
http://www.debian.org/Bugs/Reporting

Hope this helps

[SOLVED] Re: bug? laptop-mode-tools - mouse turns off after 3s of inactivity after last update

[Hans]

>Sounds like usb-autosuspend, at a glance.

>I noticed that the commented line listing usb-autosuspend as a valid
>option for one of the settings in /etc/laptop-mode/laptop-mode.conf
>disappeared with the most recent update to that package, but I didn't
>notice anything in the changelogs that would seem to explain that. (I'm
>not on that laptop now, so I can't check easily.)

>I really hope the option to disable USB auto-suspending hasn't
>disappeared; last I checked, allowing USB autosuspend would deactivate
>my mouse in exactly this way.

>-- 
>  The Wanderer
I found a solution myself.
Edit /etc/laptop-mode/conf.d/runtime-pm.conf
Search this:
# The list of Device IDs that should not use autosuspend. Use system 
commands or
# look into sysfs to find out the IDs of your devices.
# Example: AUTOSUSPEND_DEVID_BLACKLIST="046d:c025 0123:abcd"
AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST=""

Then do lsusb and find the mouse:
lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 5986:0102 Acer, Inc Crystal Eye Webcam
Bus 003 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

You find the mouse ->  093a:2510

Now edit AUTOSUSPEND_RUNTIME_DEVID_BLACKLIST="093a:2510"

After next boot, your mouse will not suspended any more.

However, if you wish the mouse to be suspended, but want increase the 
delay (which is 2s by default and rather short), edit the last line:

# Auto-Suspend timeout in seconds
# Number of seconds after which the USB devices should suspend
AUTOSUSPEND_TIMEOUT=2

Good luck and thanks for the answers.

Best 

Hans

Re: bug? laptop-mode-tools - mouse turns off after 3s of inactivity after last update

[The Wanderer]

On 07/11/2015 at 09:04 AM, Hans wrote:

> Dear list,
> 
> I accidently had to reinstall laptop-mode-tools. I had to purge and
> reinstall the package.
> 
> After this, I noticed, that my usb-mouse (cable), turns off after 3s
> of inactivity. This behaviour was already deccribed here in older
> forums:
> 
> http://askubuntu.com/questions/130915/optical-mouse-temporarily-turns-off-when-system-is-idle
>
> and more special here
> 
> https://fitzcarraldoblog.wordpress.com/2013/02/26/how-to-prevent-a-usb-mouse-auto-suspending-in-linux-when-a-laptops-power-supply-is-disconnected/
>
> However, I could not find a configuration file in laptop-mode-tools
> to prevent this behaviour.
> 
> This happens only, when I am on battery, or when I am connected to
> power supply, but got no battery inserted.

Sounds like usb-autosuspend, at a glance.

I noticed that the commented line listing usb-autosuspend as a valid
option for one of the settings in /etc/laptop-mode/laptop-mode.conf
disappeared with the most recent update to that package, but I didn't
notice anything in the changelogs that would seem to explain that. (I'm
not on that laptop now, so I can't check easily.)

I really hope the option to disable USB auto-suspending hasn't
disappeared; last I checked, allowing USB autosuspend would deactivate
my mouse in exactly this way.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Bug with xdg-utils / xdg-open / gvfs-open

[Sven Arvidsson]

On Fri, 2015-06-19 at 20:43 +0200, Christoph Martens wrote:
> Hey guys,
> 
> I wanted to report a bug, but reportbug is completely broken on 
> Ubuntu.
> 
> So, I have the following issue with xdg-open, which is not the fault 
> of 
> xdg-utils, but an issue with gvfs: 
> https://bugs.freedesktop.org/show_bug.cgi?id=91027
> 
> 
> Can somebody please file a bug accordingly? Everything that you need 
> to 
> know is inside the already reported bug. For end users that are not 
> core-debian developers, filing a bug is close to impossible.

Unlikely to be specific to Debian or Ubuntu, so best to file it
upstream (product gvfs):
https://bugzilla.gnome.org

There where quite a few (closed) bugs about slashes so maybe check them
first.

Anyway, you can use reportbug to fill out a bug report and then send it
manually, or compose the bug report yourself and send it to 
sub...@bugs.debian.org 


-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5




signature.asc
Description: This is a digitally signed message part

Re: Bug Report: QMMP issue - [Jessie with MATE] when caja opened, qmmp launches instead

[Sven Arvidsson]

On Fri, 2015-05-22 at 18:16 +0200, jake.pers...@riseup.net wrote:
> Hi Guys
> 
> Very odd bug this. Caja opens fine without qmmp installed. But when qmmp 
> is installed and you want to browse with caja, the qmmp player launches 
> instead.
> 
> Where do I post this?

Hi,

I poked around the qmmp package, and it has a suspicious
qmmp_dir.desktop file which registers qmmp has a handler for
MimeType=inode/directory;

So I'm guessing that's why you get qmmp instead of the file manager. Not
sure if this is a bug in qmmp or a problem with your desktop environment
in general. 

Try filing a bug with qmmp, if it's a more serious problem the bug can
always be reassigned.

HTH,

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5




signature.asc
Description: This is a digitally signed message part

Re: bug report

[Bob Proulx]

Nader wrote:
> hi, I need to report a bug in the debian installation system. I do not
> know the name of the package that reportbug needs. Please let me know
> how to proceed.

Browse the bugs in installation-reports and see if it has been
reported already.

  https://bugs.debian.org/installation-reports

If not then make your report there.

Since you are talking with us here at debian-user mailing list it is
also useful to describe your problem here.  Perhaps one of us can
help.  Won't know until you describe the problem.

Bob

P.S. The list of pseudo packages for things like this is documented here:

  https://www.debian.org/Bugs/pseudo-packages


signature.asc
Description: Digital signature

Re: bug report

[Umarzuki Mochlis]

could be debian-installer package?

2015-05-06 11:13 GMT+08:00 Nader :
> hi, I need to report a bug in the debian installation system. I do not
> know the name of the package that reportbug needs. Please let me know
> how to proceed.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> https://lists.debian.org/caj19urtnz2l94d2jukdruoubeqnqjxweinnti-26bykzkfl...@mail.gmail.com
>


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAHW9mbxiiLyz85D5vLBLkt-a8XOFbNqHnaw=_purgxgfhbp...@mail.gmail.com

Re: Bug#780201: new codename needed for oldstable (due to squeeze-lts) when stable becomes oldstable

[Cindy-Sue Causey]

On 3/10/15, Bret Busby  wrote:
> -- Forwarded message --
> From: Bret Busby 
> Date: Tue, 10 Mar 2015 22:54:42 +0800
> Subject: Re: Bug#780201: new codename needed for oldstable (due to
> squeeze-lts) when stable becomes oldstable
> To: debian-...@lists.debian.org
>
> On 10/03/2015, Andreas Glaeser  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Tue, 10 Mar 2015 12:38:29 +0100
>> Holger Levsen  wrote:
>>
>>> Hi,
>>>
>>> when jessie will be released, wheezy will become oldstable and we'll
>>> need
>>> a
>>> new alias for squeeze, as various tools internally work with aliases.
>>> (The
>>>
>>> security tracker comes to my mind, but also the Release files it seems.
>>> And
>>> probably more.)
>>>
< snipped for brevity>
>>>
>>> Current suggestions I've heard (and liked) are "oldoldstable" and
>>> "veryoldstable".
>>>
>>> I *dislike* "obsoletestable" and "stalestable" as they are either wrong
>>> (squeeze is not obsolete) or carry a bad connotation.
>>
>> What about 'extremely-stable' ??
>>
>
> Why not simply use the states
> experimental
> unstable
> testing
>
> and for the stable version
> stable and version number (eg Debian7)
>
> and all preceding versions,
> version number
> eg
> Debian6 LTS
> Debian 5
> Debian4
> etc


Coming into this just now and immediate response was... HEY, I
*like* that... maybe with no capital letters where possible unless
that's a longstanding "head nod", name *RESPECT* thing toward Debian.
That would certainly be understandable.

Its concept is obviously that, when any stable becomes an old stable,
all that's needed for identification purposes forever after that is
the referenced prior release's original/primary defining "6" or "7" or
"8", etc...

NOTE: While proofreading this email before sending, comes to mind that
yes, codenames would do similar BUT... With a numerical based method,
a new user could walk in not knowing code names and yet still be able
to reasonably maneuver around. Example there would be where we can
currently replace "stable" with "testing" or "unstable" in
Debian.org's website hierarchy structure to successfully navigate
within the packages subdomain.

The way I'm grasping via the Bug's commentary, specifically Bret's
suggestion, is that the addition into wherever is
appropriate/necessary, could be similar to, say, like where we add in
a "free floating" "jessie" or "sid" to debootstrap's command.. Or like
where we see similar looking "free floating" personalizations in a
string within grub.cfg, maybe. Yeah, I know, probably apples and
oranges comparison to bug originator's intent, but it's what my mind
is visualizing for potential usage as you all chat this up.

Oh, and that _already_ "free floating" LTS notation might then need
addressed within a "free floating" usage situation, I think.. I
think. Otherwise additional keystrokes (ack!) with respect to
parentheses then become necessary? Maybe? Ok, I'll stop now. *grin*

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Georgia USA

* User Tip: Wondering what packages are available in stable? Check this out:
https://packages.debian.org/stable/
Simply replace "stable" with "testing" or "unstable" if you use either
instead. *


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAO1P-kAfmgM=sufjecu0nqb+e-3wnc9a-5mlxfrbwbmkfhy...@mail.gmail.com

Re: BUG REPORT (CRITICAL) - JESSIE: System Barely Running ... right after lightdm starts

[Khurram Mahmood]

*Hello*

*Kindly acknowledge that the problem is partially resolved.*

*I managed to run top for a while and found that mount and systemd were
consuming the cpu, so tried to delete some packages like lightdm and
schroot.*

*After removal of schroot the system has now become usable.*

*I have not installed schroot again until the jessie is declared stable,
but kindly inform of any log report required by bug-tracking.*


*Thank you and oblige.*

*Kind Regards,*

*(Khurram Mahmood)*

On 18 February 2015 at 02:34, Khurram Mahmood  wrote:

> *Hello*
>
> *Kindly see the attached /var/log/message*
> *s*
>
>
>
> *Also noted:*
>
>
> *1. systemd is consuming 100% CPU*
>
> *2. and RAM is used by more than the usual of 240MB, ie upto around 3GB*
>
>
> *3. This is not a problem in the root repair mode.*
>
>
>
> *4. There is no application found to be consuming RAM.*
>
> *5. The system runs A-OKAY under Arch Linux.*
>
>
>
> *6. After an update, this fault has surfaced. Before it the Jessie was
> running fine.*
>
> *My System is:*
>
> *a. HP Probook 440 G2, i3-4030U, 4GB Ram *
>
> *b. Jessie 64-Bit*
>
>
>
> *Please inform if any other information is required.*
>
> *Thank you and oblige.*
>
> *Kind Regards,*
>
> *خرم محمود*
> *(Khurram M.)*
>

Re: Bug or problem with ssd disk

[Alex Mestiashvili]

On 02/03/2015 06:32 AM, Ian Scheehan wrote:

Sometimes (random moment), my debian freeze, stop working.
I don't know which package or kernel part cause that debian jessie freeze.

How can get data/info of my computer and error which happen and send 
report bug to you?


Can you help?

best regards,
Bogdan


OK, the first answer probably doesn't address the issue,
Try to check the memory with memtest.
Also graphics drivers can cause problems like that.
It would be more helpful if you would provide more details about hardware.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54d0864b.8080...@biotec.tu-dresden.de

Re: Bug or problem with ssd disk

[Alex Mestiashvili]

On 02/03/2015 06:32 AM, Ian Scheehan wrote:

Sometimes (random moment), my debian freeze, stop working.
I don't know which package or kernel part cause that debian jessie freeze.

How can get data/info of my computer and error which happen and send 
report bug to you?


Can you help?

best regards,
Bogdan


There are a lot of tools you can try,
the first thing I would do is to look on dmesg output.
iotop - shows you disk activity,
top or atop to see process activity.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/54d08532.2020...@biotec.tu-dresden.de

Re: bug report

[Jonathan Dowland]

Hi Georges,

On Thu, Nov 13, 2014 at 08:53:19PM -0600, Georges Jamieson wrote:
> I was trying to install jasper on a Raspbery Pi.
> The installation failed and requested that I send in a bug report thus my 
> email.
> I can not understand the instructions for doing so but I did see this email 
> address as a place to ask for instructions on bug reporting.

Jasper is not part of Debian, so I'm afraid there's no value in filing a bug
report on Jasper with Debian. (Even if you were to do so, you would not do so
by posting to debian-user).

You haven't made clear what operating system you are using on the raspberry pi.
Perhaps it's Raspbian, in which case it might be necessary to file a bug with 
them. Raspbian is not a part of the Debian project.

> Here is the message I received from make install. I was simply following the
> instructions on the jasper website (3ed method).

Looking at the instructions for Jasper[1], it would seem that they provide
pre-built images of Raspbian + Jasper. Why not use those? (i.e. method 1)

Looking briefly at the log of compiling for openfst you have provided:

> g++: internal compiler error: Killed (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.

The build has triggered a bug in the compiler. If you want to report the
compiler bug, please read that above file for instructions. However that
is quite an old version of the compiler, so it's quite possible the bug
has already been fixed in a more recent version.

[1] http://jasperproject.github.io/documentation/software/

-- 
Jonathan Dowland


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141114094348.gb3...@chew.redmars.org