$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1958288 0 1958288 0% /dev
tmpfs 393692 6296 387396 2% /run
/dev/sda8 20025212 14023532 4961400 74% /
tmpfs 1968448 84 1968364 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1968448 0 1968448 0% /sys/fs/cgroup
/dev/sda7 242570920 229840596 385328 100% /home
tmpfs 393688 4 393684 1% /run/user/116
tmpfs 393688 12 393676 1% /run/user/1000
$ free total used free shared buff/cache
available
Mem: 3936896 298520 2595240 86544 1043136 3271988
Swap: 7811068 0 7811068
$ xsane
^C
$ free
total used free shared buff/cache available
Mem: 3936896 296272 2620584 85932 1020040 3267724
Swap: 7811068 0 7811068
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1958288 0 1958288 0% /dev
tmpfs 393692 6292 387400 2% /run
/dev/sda8 20025212 13972704 5012228 74% /
tmpfs 1968448 84 1968364 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1968448 0 1968448 0% /sys/fs/cgroup
/dev/sda7 242570920 229840596 385328 100% /home
tmpfs 393688 4 393684 1% /run/user/116
tmpfs 393688 12 393676 1% /run/user/1000
I leave out the ecryptfs drive mounted inside /home/<username> and a mounted
external hdd.
I pressed ctrl+c after 2 or 3 minutes, just before I did I grabbed these stats:
$ free
total used free shared buff/cache available
Mem: 3936896 302712 2613096 86984 1021088 3260232
Swap: 7811068 0 7811068
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1958288 0 1958288 0% /dev
tmpfs 393692 6292 387400 2% /run
/dev/sda8 20025212 13972704 5012228 74% /
tmpfs 1968448 84 1968364 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 1968448 0 1968448 0% /sys/fs/cgroup
/dev/sda7 242570920 229840596 385328 100% /home
tmpfs 393688 4 393684 1% /run/user/116
tmpfs 393688 12 393676 1% /run/user/1000
Additional from what I left out before, after this I run:
$ scanimage -T
scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
scanimage: acquiring RGB frame, 8 bits/sample
scanimage: reading one scanline, 1914 bytes... ^Cscanimage: received signal 2
scanimage: trying to stop scanner
^Cscanimage: received signal 2
scanimage: aborting
$ scanimage > foo
$ xsane
and then xsane works fine as well as the scanimage > foo... next time I scan I
shall try
skipping out the scanimage -T step. IIRC from before, I had to run "scanimage
> foo" twice
with the scanner working on the 2nd attempt of scanimage. xsane by itself
never seems to work :(.
I hope that helps,
Jack
________________________________
From: Jörg Frings-Fürst <[email protected]>
To: Jack Underwood <[email protected]>
Cc: [email protected]
Sent: Thursday, 3 November 2016, 17:18
Subject: Re: Bug#842999: xsane: XSane takes ages to start and do anything
Hello Jack,
thank you for spending your time helping to make Debian better with
this bug report.
Please can you open a console and run
- df
- free
- xsane
- free
- df
and attach the output here.
Many thanks.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
Threema: SYR8SJXB
IRC: [email protected]
[email protected]
My wish list:
- Please send me a picture from the nature at your home.
