apt-get crashes when trying to update google-chrome 32 bit

[John Conover]

Google no longer supports chrome for 32 bit. Unfortunately, apt-get
crashes and aborts and will not update the rest of the system when it
tries to read the chrome directory at google.

How do you purge google chrome and talk so apt-get will work?

Thanks,

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/

error "sh: 1: exec: ...: File exists" with dash

[Vincent Lefevre]

I've got the following error in a script yesterday on a Debian 8
machine:

  sh: 1: exec: /home/vlefevre/bin/mymaple: File exists

where sh is dash. The command that led to this error is equivalent to:

  sh -c 'exec /home/vlefevre/bin/mymaple -q -s 2>&1'

The "File exists" message corresponds to the EEXIST error:

$ errno --search exists
EEXIST 17 File exists

But what does this error mean here? Which file exists and shouldn't?

I've looked at the dash source, and the error seems to come from
shellexec() in exec.c, and EEXIST is the errno from execve() in
tryexec(). But EEXIST is not among the possible errors listed in
the execve(2) man page.



A bit more details on the context. This comes from a Perl script
that does:

  $pid = IPC::Open2::open2(\*RD, \*WR, "exec @maple 2>&1");

where @maple is ('/home/vlefevre/bin/mymaple', '-q', '-s').
So, what open2 does corresponds to:

  sh -c 'exec /home/vlefevre/bin/mymaple -q -s 2>&1'

My home directory is under NFS.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: apt-get crashes when trying to update google-chrome 32 bit

[Floris]

Op Thu, 03 Mar 2016 09:40:59 +0100 schreef John Conover  
:



Google no longer supports chrome for 32 bit. Unfortunately, apt-get
crashes and aborts and will not update the rest of the system when it
tries to read the chrome directory at google.

How do you purge google chrome and talk so apt-get will work?

Thanks,

John



probably you have a file in /etc/apt/sources.list.d/ called  
google-chrome.list
You can remove that file or open it and place a # in front of deb  
http://dl.google.com/...


or if you can run 64bit programs add after deb [arch=amd64] so the line  
will look like

deb [arch=amd64] http://dl.google.com/...

after you made some changes don't forget to run apt-get update

success,

floris

Re: error "sh: 1: exec: ...: File exists" with dash

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Mar 03, 2016 at 10:18:55AM +0100, Vincent Lefevre wrote:
> I've got the following error in a script yesterday on a Debian 8
> machine:
> 
>   sh: 1: exec: /home/vlefevre/bin/mymaple: File exists
> 
> where sh is dash. The command that led to this error is equivalent to:

Just a cheap shot (I see you've dug up a couple of things which
might make my hunch obsolete). Do you have perhaps the noclobber
option set?

  # -C -- set noclobber
  tomas@rasputin:~$ dash -C
  $ touch moo
  $ echo blah > moo
  dash: 2: cannot create moo: File exists

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

iEYEARECAAYFAlbYDL8ACgkQBcgs9XrR2karkACeOWfg7J9J/qa9JF43EvRcPdeI
tnMAni8M2qxoceb2GVeCwnhYrKzqFa7F
=GL93
-END PGP SIGNATURE-

Re: error "sh: 1: exec: ...: File exists" with dash

[Vincent Lefevre]

On 2016-03-03 11:06:55 +0100, to...@tuxteam.de wrote:
> On Thu, Mar 03, 2016 at 10:18:55AM +0100, Vincent Lefevre wrote:
> > I've got the following error in a script yesterday on a Debian 8
> > machine:
> > 
> >   sh: 1: exec: /home/vlefevre/bin/mymaple: File exists
> > 
> > where sh is dash. The command that led to this error is equivalent to:
> 
> Just a cheap shot (I see you've dug up a couple of things which
> might make my hunch obsolete). Do you have perhaps the noclobber
> option set?

It is in my zsh shell, but here zsh is not involved at all.
For dash, it is not set by default:

francine:~> sh -c 'touch moo; echo blah > moo'
francine:~>

Anyway, I don't see why the noclobber option would have any effect
on the exec command, even when there is a redirection to a file:

francine:~> sh -c 'set -C; touch moo; exec true > moo'
sh: 1: cannot create moo: File exists

As you can see the error message is different. It is at the shell
level (before the "exec" command gets executed).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: error "sh: 1: exec: ...: File exists" with dash

[Vincent Lefevre]

On 2016-03-03 10:18:55 +0100, Vincent Lefevre wrote:
> I've got the following error in a script yesterday on a Debian 8
> machine:
> 
>   sh: 1: exec: /home/vlefevre/bin/mymaple: File exists
> 
> where sh is dash. The command that led to this error is equivalent to:
> 
>   sh -c 'exec /home/vlefevre/bin/mymaple -q -s 2>&1'
> 
> The "File exists" message corresponds to the EEXIST error:
> 
> $ errno --search exists
> EEXIST 17 File exists
> 
> But what does this error mean here? Which file exists and shouldn't?
[...]

Some additional information...

I've looked at the history of my commands, and 5 seconds before this
error, I regenerated my config on another machine, with the same home
directory via NFS. In particular, this has the effect to re-create
the mymaple script with:

  touch /home/vlefevre/bin/mymaple
  mv -v ... /home/vlefevre/bin/mymaple

(the "touch" is a workaround to avoid a kernel bug present in Debian 8)
at about the same time of the error. But this still doesn't explain the
error. Perhaps a race condition in the kernel?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: error "sh: 1: exec: ...: File exists" with dash

[Jean-Baptiste Thomas]

EEXIST does sounds like a strange reason for exec(2) to fail.
Did you strace -f to confirm that EEXIST is indeed set by
execve() ?

I've seen weirdly-named files appear in NFS-exported file
systems. I seem to remember they were related to deleted files
but it might happen in other circumstances. A name collision
could explain EEXIST. I would take a look on the NFS server.

Assuming you've managed to successfully use IPC::Open2::open2
on other executables in the same NFS-mounted file system and
it is only mymaple that fails : if mymaple is a script, what is
it's shebang line ? Is file creation involved somehow ?

Shot in the dark : does the error go away if you remove the
"2>&1" part ?

Re: error "sh: 1: exec: ...: File exists" with dash

[Vincent Lefevre]

On 2016-03-03 12:52:34 +0100, Jean-Baptiste Thomas wrote:
> EEXIST does sounds like a strange reason for exec(2) to fail.
> Did you strace -f to confirm that EEXIST is indeed set by
> execve() ?

I could reproduce the error after regenerating my config (see my
other mail about that). And yes, it comes from execve(). I could
do a simpler test, always reproducible:

francine:~> touch bin/tst
francine:~> cat bin/tst

cassis:~> cat tst.c
int main (void)
{ return 0; }
cassis:~> gcc -O3 tst.c -o tst
cassis:~> mv tst bin/
mv: overwrite ‘bin/tst’? y

At this point, I have to wait for 15 seconds for the "mv" to be
done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799838

After that:

francine:~> strace -f -o tst.out sh -c "exec $HOME/bin/tst"
sh: 1: exec: /home/vlefevre/bin/tst: File exists
zsh: exit 2 strace -f -o tst.out sh -c "exec $HOME/bin/tst"
francine:~[2]> cat tst.out
21573 execve("/bin/sh", ["sh", "-c", "exec /home/vlefevre/bin/tst"], [/* 120 
vars */]) = 0
21573 brk(0)= 0x7f4aded7d000
21573 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
21573 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded46000
21573 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64", 
0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls", 0x7ffec78d5b00) = -1 
ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/x86_64", 0x7ffec78d5b00) = 
-1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib", {st_mode=S_IFDIR|0755, 
st_size=13, ...}) = 0
21573 open("/usr/local/lib/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
21573 stat("/usr/local/lib/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such 
file or directory)
21573 open("/usr/local/lib/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/usr/local/lib/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/usr/local/lib/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
(No such file or directory)
21573 stat("/usr/local/lib/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file 
or directory)
21573 open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/usr/local/lib", {st_mode=S_IFDIR|S_ISGID|0775, st_size=4096, ...}) 
= 0
21573 open("/lib64/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/lib64/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/lib64/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
21573 read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 832) = 832
21573 fstat(3, {st_mode=S_IFREG|0755, st_size=1738176, ...}) = 0
21573 mmap(NULL, 3844640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) 
= 0x7f4ade55f000
21573 mprotect(0x7f4ade701000, 2093056, PROT_NONE) = 0
21573 mmap(0x7f4ade90, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7f4ade90
21573 mmap(0x7f4ade906000, 14880, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f4ade906000
21573 close(3)  = 0
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded45000
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded44000
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded43000
21573 arch_prctl(ARCH_SET_FS, 0x7f4aded44700) = 0
21573 mprotect(0x7f4ade90, 16384, PROT_READ) = 0
21573 mprotect(0x7f4aded48000, 12288, PROT_READ) = 0
21573 mprotect(0x7f4adeb2a000, 4096, PROT_READ) = 0
21573 getpid()  = 21573
21573 rt_sigaction(SIGCHLD, {0x7f4adeb3efd0, ~[RTMIN RT_1], SA_RESTORER, 
0x7f4ade5940e0}, NULL, 8) = 0
21573 geteuid() = 1114
21573 brk(0)

Re: Installing libSSL 0.9.8 in debian jessie

[Dan Ritter]

On Thu, Mar 03, 2016 at 01:06:56PM +0530, venkat wrote:
> I am just exploring the possibilities to install libSSL 0.9.8 in jessie
> 

What are you hoping to accomplish?

-dsr-

Re: Installing libSSL 0.9.8 in debian jessie

[venkat]

I have existing library which is built on 0.9.8 and i will be able to 
use it directly without any issues

.
On 03-03-2016 18:26, Dan Ritter wrote:

What are you hoping to accomplish?



--
Regards
Venkat.S

How to clear notifications?

[Albin Otterhäll]

How can I clear the notifications in Gnome? I still want them, but be
able to clear them. I've tried to restart gnome shell (Alt+F2, input
"r", and press enter), but they are still there. The notifications comes
from the clock app.

Re: which files took the space

[Jochen Spieker]

lina:
> 
> how do I know which files mounted on the /home.

In the future you can install and use 'ncdu'. It is a nice terminal
program that calculates directory sizes and allows you to easily see
what occupies the most disk space.

J.
-- 
I like my Toyota RAV4 because of the commanding view of the traffic
jams.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: XFS on root

[Adam Wilson]

On Wed, 2 Mar 2016 07:09:00 -0300 Renaud (Ron) OLGIATI
 wrote:

> On Wed, 2 Mar 2016 09:52:12 +
> Darac Marjal  wrote:
> 
> > >Why use Ext2 and not Ext 3 or 4 for /boot?  
> > 
> > I believe the reasoning is to keep /boot as simple and as robust as 
> > possible. ext3 and ext4 are, while mostly compatible with ext2, not
> > as well supported. There are third-party drivers, for example, that
> > don't know about the journal of ext3 or the extents of ext4. And
> > besides, these take up unnecessary space on a file system which is
> > only written to, say, once every few months.
> > 
> > Ext2 provides a balance between features (i.e. being sufficiently
> > UNIX-y (which FAT isn't)), and simplicity.
> 
> Not to mention that, given the rarity of changes in /boot, a
> journalling FS may not be really useful... 

Exactly. The reason I don't use ext4 for /boot, but ext2 is that I
simply don't see the need for journalling in a partition that sees only
occasional writes.

I don't really want journalling for /boot, because it's largely
redundant and slower than not having journalling. Debian offers three
non-journalling filesystems in the installer- ext2, fat, and ntfs.
Since I want something UNIX-y, fat and ntfs are out, which leaves ext2.

Faster than ext3 and 4, but still UNIX-compatible.

Re: which files took the space

[Andrew McGlashan]

On 3/03/2016 1:51 PM, lina wrote:
> I figured out, there are so many hidden files.

It also may have been files in the file system, but where another file
system mount hides them

A.

Re: which files took the space

[Adam Wilson]

On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
 wrote:

> 
> 
> On 3/03/2016 1:51 PM, lina wrote:
> > I figured out, there are so many hidden files.
> 
> It also may have been files in the file system, but where another file
> system mount hides them

What does this mean? Mounts overlapping and hiding other mounts?

Explain, please.

Re: which files took the space

[jdd]

Le 03/03/2016 17:03, Andrew McGlashan a écrit :



On 3/03/2016 1:51 PM, lina wrote:

I figured out, there are so many hidden files.


It also may have been files in the file system, but where another file
system mount hides them

A.

or file in use deleted but not released... like virtual machines or 
mounted isos...


jdd

Re: Installing libSSL 0.9.8 in debian jessie

[Dan Ritter]

On Thu, Mar 03, 2016 at 06:47:56PM +0530, venkat wrote:
> I have existing library which is built on 0.9.8 and i will be able to
> use it directly without any issues

Are you aware that 0.9.8 has the following security problems:

https://www.cvedetails.com/vulnerability-list/vendor_id-217/product_id-383/version_id-26306/Openssl-Openssl-0.9.8.html

including remote code execution?

It would be much better if you recompile your application
against a modern version, and make sure you keep it up to date.

-dsr-

Re: XFS on root

[Dan Ritter]

On Thu, Mar 03, 2016 at 06:48:31PM +0300, Adam Wilson wrote:
> 
> Exactly. The reason I don't use ext4 for /boot, but ext2 is that I
> simply don't see the need for journalling in a partition that sees only
> occasional writes.
> 
> I don't really want journalling for /boot, because it's largely
> redundant and slower than not having journalling. Debian offers three
> non-journalling filesystems in the installer- ext2, fat, and ntfs.
> Since I want something UNIX-y, fat and ntfs are out, which leaves ext2.
> 
> Faster than ext3 and 4, but still UNIX-compatible.

On the one hand, you don't use /boot much. And on the other
hand, you are concerned about speed.

These things don't make sense together. The less often you do
something, the less you should care about speed. Conversely, if
you do something often, you should care more about speed... as
long as it is still correct.

A journal on /boot can save you from problems in the part of the system
which is often hardest to debug: booting. Improving reliability at the
cost of speed in something that you do rarely is a win.

-dsr-

Re: which files took the space

[Andrew McGlashan]

On 4/03/2016 3:07 AM, Adam Wilson wrote:
> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
>  wrote:
>> It also may have been files in the file system, but where another file
>> system mount hides them
> 
> What does this mean? Mounts overlapping and hiding other mounts?
> 
> Explain, please.

Yes, this is more likely to happen to the root file system.

Say you have a bunch of files in /boot, but for some reason you have a
/boot partition that wasn't mounted when those files were created 
then you mount the /normal/ boot partition over it and now the other
files are now hidden from view, but still taking up space.

Cheers
A.

Re: Thin Mate window edges

[Liam O'Toole]

On 2016-03-02, Russell Gadd  wrote:
> --001a11383ed40febc2052d18b9b3
> Content-Type: text/plain; charset=UTF-8
>
> I have just installed Jessie with the Mate desktop. My screen is 1920 x
> 1080. I find grabbing the edges or corner of a window with the mouse
> pointer in order to extend it is very fiddly. Is this due to the border
> being very thin? Are there any options to make this easier, such as
> choosing a window style with thicker borders?

This used to work in GNOME 2, so perhaps it does in MATE too. Hit Alt+F8
when the mouse cursor is over the window to be resized, then use the
arrow keys to resize. Hit Enter when done.

-- 

Liam

Re: How to clear notifications?

[Albin Otterhäll]

On 03/03/2016 02:43 PM, Albin Otterhäll wrote:
> How can I clear the notifications in Gnome? I still want them, but be
> able to clear them. I've tried to restart gnome shell (Alt+F2, input
> "r", and press enter), but they are still there. The notifications comes
> from the clock app.

Seems that I only had to move the mouse to the bottom of the screen. It
seemed that it didn't work at first, but it does.

Invisible icon of Iceweasel

[Strelok]

I'm don't know what package is a source of problem. Because this, ask
there. Debian Stretch (current testing) with Mint DE. Applications
menu->Internet->drag Iceweasel icon from menu to somewhere.
What I'm except: Iceweasel icon near mouse cursor, when I'm drag icon somewhere.
What I'm got: little while corner near mouse cursor. Probably, part of
Iceweasel icon. Other parts of icon become invisible.
If I'm drag any other icon, this bug don't appeared.
PS Yes, apt-get update;apt-get upgrade is done.

Re: Invisible icon of Iceweasel

[Sven Arvidsson]

On Thu, 2016-03-03 at 21:33 +0300, Strelok wrote:
> I'm don't know what package is a source of problem. Because this, ask
> there. Debian Stretch (current testing) with Mint DE. Applications
> menu->Internet->drag Iceweasel icon from menu to somewhere.
> What I'm except: Iceweasel icon near mouse cursor, when I'm drag icon
> somewhere.
> What I'm got: little while corner near mouse cursor. Probably, part
> of
> Iceweasel icon. Other parts of icon become invisible.
> If I'm drag any other icon, this bug don't appeared.
> PS Yes, apt-get update;apt-get upgrade is done.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803165
it was fixed once, but the same bug has appeared again :(

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



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

xorg under Mate hogging cpu

[Frank McCormick]

Sorry folks. PEBKAC I think. Marco was listed as
one of the startup programs...totally unnecessary
I think. Mate is back to normal.





I am running Mate as a main desktop on Debian Sid and noticed today xorg
is hogging the cpu. Htop reports 12-15% cpu for xorg, and that
is up quite a bit from the past.
I don't recall the last time xorg or related packages were updated.

Is there a way to figure out what's the problem ?

xorg under Mate hogging cpu

[Frank McCormick]

I am running Mate as a main desktop on Debian Sid and noticed today xorg
is hogging the cpu. Htop reports 12-15% cpu for xorg, and that
is up quite a bit from the past.
I don't recall the last time xorg or related packages were updated.

Is there a way to figure out what's the problem ?

Trend Micro Users

[Alice Williams]

Hi,



Are you interested in* Trend Micro Users* contacts list?



*Information Fields* – Name, Title,  Email, Phone, Company Name, Physical
Address, City, State, Zip Code, Country,  Web Address, Employee Size,
Revenue Size and Industry.



*Other related technology users like:*



Qualys

BigFix

Fortify Software

McAfee

Cigitala

HP

Tenable Network Security

Juniper Security

Imperva

Mercury Interactive

CheckPoint

SonicWall

Fortinet

Symantec

Sophos

FireEye

WatchGuard



If you looking for particular titles from your target geography, do let me
know if you are interested and I would be happy to share our work details
and Prices.



Regards,

*Alice Williams*

Data Specialist Consultant





P.S: This email is not spam, it was manually sent by us, our sole purpose
being to introduce ourselves to you with no obligation on your part. Your
email address was found to be publicly available on your website and it has
not been added to any list. We consider this to be a polite way to contact
you and apologize sincerely if you have been inconvenienced in any way. We
are obliged to offer you an 'OPT-OUT' from future mailings from us; should
you wish to exercise this right, please reply with” OPT-OUT" in the subject
field.

Re: Thin Mate window edges

[Siard]

Russell Gadd wrote:
> I have just installed Jessie with the Mate desktop. [...] I find
> grabbing the edges or corner of a window with the mouse pointer in
> order to extend it is very fiddly. Is this due to the border being
> very thin?

Yes, obviously.

> Are there any options to make this easier, such as choosing a window
> style with thicker borders?

In Mate, you can change window borders as follows:
- Top menu: System > Control Centre > Look and Feel > Appearance
- Under tab 'Theme', choose a theme or keep 'Custom' theme
- Click 'Customize' button
- Under tab 'Window Border', select Spidey (this theme has the widest
  window borders)
- Under tab 'Colors' next to 'Selected items', adjust the window
  border color to your liking.

After restarting Mate, you will see that windows have wider borders,
so that's an improvement at least.
But they can be made even wider if desired.
As root, edit usr/share/themes/Spidey/metacity-1/metacity-theme-1.xml.
You will see these lines near the beginning:


  
  
  

Changing '3' to a higher number, most important for right_width and
bottom_height, will widen those borders.

Bluetooth headphones mistaken for a keyboard!?!

[Mark Fletcher]

I took delivery of a very nice pair of Bang & Olufsen BeoPlay H8
bluetooth headphones yesterday. I've verified they work properly by
connecting them to my iPhone.

When I try to connect them to my PC, I am not having so much luck. PC is
a 7-year-old self-built desktop box running Jessie with Gnome as the DE,
with Intel Core i7-920 CPU and 24GB RAM. Bluetooth capability comes from
a rather younger (bought about 6 months ago) bluetooth USB dongle which
I routinely use to connect my iPhone and Android tablets to the computer
to play audio from them through the computer's speakers. So I know it
works fine too.

Turning on bluetooth from the gnome applet, and putting the headphones
into pairing mode, the computer quickly finds the headphones. When I ask
the computer to connect it quickly does so, apparently successfully, and
I hear the tones in the headphones indicating they too know they are
connected. But, pulseaudio doesn't recognise a new audio sink has been
installed -- and I don't blame it, because of the below.

Looking in the Gnome Log Viewer in messages, at the moment of connecting
the headphones, I see this:

Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) config/udev: Adding input
device 00:09:A7:09:BE:22 (/dev/input/event17)
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22:
Applying InputClass "evdev keyboard catchall"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) Using input driver
'evdev' for '00:09:A7:09:BE:22'
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22: always
reports core events
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) evdev: 00:09:A7:09:BE:22:
Device: "/dev/input/event17"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
Vendor 0 Product 0
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
Found keys
Mar  4 08:07:17 kazuki kernel: [382097.651490] input: 00:09:A7:09:BE:22
as /devices/virtual/input/input30
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) evdev: 00:09:A7:09:BE:22:
Configuring as keyboard
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "config_info"
"udev:/sys/devices/virtual/input/input30/event17"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) XINPUT: Adding extended
input device "00:09:A7:09:BE:22" (type: KEYBOARD, id 13)
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_rules"
"evdev"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_model"
"pc105"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_layout"
"jp,us"
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_variant" ","
Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_options"
"grp:alt_shift_toggle,grp_led:scroll"


That doesn't look healthy. First of all it is detecting an INPUT device,
presumably the headphone controls for volume and so on, and no OUTPUT
device. Second, it seems to think that what it has found is a keyboard.
Pulseaudio can, it seems to me, be excused for thinking a keyboard has
been added and not being accustomed to playing sound through a
keyboard... :-)

I'm thinking this could be a udev problem of some kind -- perhaps I am
missing appropriate udev rules? I am not sure how to diagnose the
problem from here, far less fix it, so any advice would be appreciated.
Google has, unusually, turned up zilch.

Thanks in advance

Mark

Re: Bluetooth headphones mistaken for a keyboard!?!

[deloptes]

Mark Fletcher wrote:

> I took delivery of a very nice pair of Bang & Olufsen BeoPlay H8
> bluetooth headphones yesterday. I've verified they work properly by
> connecting them to my iPhone.
> 
> When I try to connect them to my PC, I am not having so much luck. PC is
> a 7-year-old self-built desktop box running Jessie with Gnome as the DE,
> with Intel Core i7-920 CPU and 24GB RAM. Bluetooth capability comes from
> a rather younger (bought about 6 months ago) bluetooth USB dongle which
> I routinely use to connect my iPhone and Android tablets to the computer
> to play audio from them through the computer's speakers. So I know it
> works fine too.
> 
> Turning on bluetooth from the gnome applet, and putting the headphones
> into pairing mode, the computer quickly finds the headphones. When I ask
> the computer to connect it quickly does so, apparently successfully, and
> I hear the tones in the headphones indicating they too know they are
> connected. But, pulseaudio doesn't recognise a new audio sink has been
> installed -- and I don't blame it, because of the below.
> 
> Looking in the Gnome Log Viewer in messages, at the moment of connecting
> the headphones, I see this:
> 
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) config/udev: Adding input
> device 00:09:A7:09:BE:22 (/dev/input/event17)
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22:
> Applying InputClass "evdev keyboard catchall"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) Using input driver
> 'evdev' for '00:09:A7:09:BE:22'
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) 00:09:A7:09:BE:22: always
> reports core events
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) evdev: 00:09:A7:09:BE:22:
> Device: "/dev/input/event17"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
> Vendor 0 Product 0
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (--) evdev: 00:09:A7:09:BE:22:
> Found keys
> Mar  4 08:07:17 kazuki kernel: [382097.651490] input: 00:09:A7:09:BE:22
> as /devices/virtual/input/input30
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) evdev: 00:09:A7:09:BE:22:
> Configuring as keyboard
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "config_info"
> "udev:/sys/devices/virtual/input/input30/event17"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (II) XINPUT: Adding extended
> input device "00:09:A7:09:BE:22" (type: KEYBOARD, id 13)
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_rules"
> "evdev"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_model"
> "pc105"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_layout"
> "jp,us"
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_variant" ","
> Mar  4 08:07:17 kazuki gdm-Xorg-:0[1040]: (**) Option "xkb_options"
> "grp:alt_shift_toggle,grp_led:scroll"
> 
> 
> That doesn't look healthy. First of all it is detecting an INPUT device,
> presumably the headphone controls for volume and so on, and no OUTPUT
> device. Second, it seems to think that what it has found is a keyboard.
> Pulseaudio can, it seems to me, be excused for thinking a keyboard has
> been added and not being accustomed to playing sound through a
> keyboard... :-)
> 
> I'm thinking this could be a udev problem of some kind -- perhaps I am
> missing appropriate udev rules? I am not sure how to diagnose the
> problem from here, far less fix it, so any advice would be appreciated.
> Google has, unusually, turned up zilch.
> 
> Thanks in advance
> 
> Mark

Which version of debian are you on and which kernel?

You may need to tell udev what kind of device it is, but we don't know if
your system is configured properly

check following articles - the second one is more practical, where you can
test pulse against the headset - I couldn't find any information on that
head set and linux except that head set is pretty expensive

https://lwn.net/Articles/531133/
http://jfcarter.net/~jimc/documents/blue-music-1504.html

I hope this helps 

regards

Re: How to tell the system to load right name for wireless card?

[Jude DaShiell]

I've had two kinds of instances over here when a wireless wifi adapter 
wasn't picked up correctly.  One of them happened when I accidentally 
changed the usb port the adapter was in and the network profile no 
longer matched.  The second happened as a result of a brown out 
preparatory to a black out of power.  A third instance happened and 
maybe this effects you too.  I run different operating systems on the 
same hardware by swapping out hard drives.  I had run KaliLinux on the 
machine for a little while and returning to talkingarchlinux, on the 
first boot of the machine the wireless wifi adapter wasn't picked up 
correctly.  A subsequent reboot of the machine got a correct connection 
though.  Had this been windows I would have had to reboot more often and 
perhaps would have found this stuff out sooner but we're dealing with 
Linux which is loads more stable especially for those of us who use 
screen readers and accessibility environments like emacspeak.


On Wed, 17 Feb 2016, German wrote:


Date: Wed, 17 Feb 2016 02:31:45
From: German 
To: debian-user@lists.debian.org
Subject: How to tell the system to load right name for wireless card?
Resent-Date: Wed, 17 Feb 2016 07:32:00 + (UTC)
Resent-From: debian-user@lists.debian.org

Hi list,

A couple of days ago I asked why my pc changes the wireless card name.
It switches between AR9285 ( right) and AR5008 ( wrong). Someone
suggested  that this is because another kernel module is loaded by
mistake. Well, it is not the case. When system identified with AR9285,
it loads ath9k and I can connect to the router. When system identifies
my card as AR5008, no kernel module is present at all ( lspci -k). The
wrong card name occurs only when system rebooted. If I gracefully shut
down the system, it always comes up with a right name for the card
( AR9285). So, how to force the system identify my card right no matter
if I reboot or shut down? Thank you.




--

Re: Using an SSD with strictatime mount option

[Joel Roth]

On Tue, Mar 01, 2016 at 01:53:11PM +0100, Jochen Spieker wrote:
> Joel Roth:
> > 
> > mount -o remount,strictatime /
> > 
> > Fixes it.
> 
> Great! But wouldn't that still be a good idea to switch to Maildir? :)

Yes, it just takes a little work to change over :)

> J.
> -- 
> I can tell a Whopper™ from a BigMac™ and Coke™ from Pepsi™.
> [Agree]   [Disagree]
>  



-- 
Joel Roth
  

Re: which files took the space

[Cindy-Sue Causey]

On 3/3/16, Andrew McGlashan  wrote:
>
> On 4/03/2016 3:07 AM, Adam Wilson wrote:
>> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
>>  wrote:
>>> It also may have been files in the file system, but where another file
>>> system mount hides them
>>
>> What does this mean? Mounts overlapping and hiding other mounts?
>>
>> Explain, please.
>
> Yes, this is more likely to happen to the root file system.
>
> Say you have a bunch of files in /boot, but for some reason you have a
> /boot partition that wasn't mounted when those files were created 
> then you mount the /normal/ boot partition over it and now the other
> files are now hidden from view, but still taking up space.


Is that behavior as designed and thus expected, or is it a glitch?

My brain's thinking it should either complain and refuse to continue
else obliterate and replace.

To me it would be... safer that it halt and complain rather than
destroy, but all that shows is that I most likely just don't
understand the function.

Do (and/or should) the original files "reappear" later?

Guess I'm just thinking out loud again mostly because I actually
understand the circumstance as presented. :)

Cindy :)

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

* runs with duct tape *

Re: which files took the space

[Adam Wilson]

On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan
 wrote:

> 
> 
> On 4/03/2016 3:07 AM, Adam Wilson wrote:
> > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> >  wrote:
> >> It also may have been files in the file system, but where another
> >> file system mount hides them
> > 
> > What does this mean? Mounts overlapping and hiding other mounts?
> > 
> > Explain, please.
> 
> Yes, this is more likely to happen to the root file system.
> 
> Say you have a bunch of files in /boot, but for some reason you have a
> /boot partition that wasn't mounted when those files were created 
> then you mount the /normal/ boot partition over it and now the other
> files are now hidden from view, but still taking up space.

So you're talking about creating files in an unmounted partition, and
then mounting it, but since file addition happened when the FS was
still in an unmounted state, the new files weren't written to the
journal?

Surely in that case the new files would simply not be registered and
act as free space (as if they had been deleted)?

Re: which files took the space

[David Wright]

On Thu 03 Mar 2016 at 23:17:19 (-0500), Cindy-Sue Causey wrote:
> On 3/3/16, Andrew McGlashan  wrote:
> >
> > On 4/03/2016 3:07 AM, Adam Wilson wrote:
> >> On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> >>  wrote:
> >>> It also may have been files in the file system, but where another file
> >>> system mount hides them
> >>
> >> What does this mean? Mounts overlapping and hiding other mounts?
> >>
> >> Explain, please.
> >
> > Yes, this is more likely to happen to the root file system.
> >
> > Say you have a bunch of files in /boot, but for some reason you have a
> > /boot partition that wasn't mounted when those files were created 
> > then you mount the /normal/ boot partition over it and now the other
> > files are now hidden from view, but still taking up space.
> 
> 
> Is that behavior as designed and thus expected, or is it a glitch?

It is as defined by mount's man page.

> My brain's thinking it should either complain and refuse to continue
> else obliterate and replace.

Typically a mount point is an empty directory. However, this does not
_have to be_ the case.

> To me it would be... safer that it halt and complain rather than
> destroy, but all that shows is that I most likely just don't
> understand the function.

Nothing is destroyed, but just inaccessible or "hidden".

> Do (and/or should) the original files "reappear" later?

As soon as you unmount the device that you mounted on that directory.

Cheers,
David.

Re: which files took the space

[David Wright]

On Fri 04 Mar 2016 at 07:18:59 (+0300), Adam Wilson wrote:
> On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan
>  wrote:
> 
> > On 4/03/2016 3:07 AM, Adam Wilson wrote:
> > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> > >  wrote:
> > >> It also may have been files in the file system, but where another
> > >> file system mount hides them
> > > 
> > > What does this mean? Mounts overlapping and hiding other mounts?
> > > 
> > > Explain, please.
> > 
> > Yes, this is more likely to happen to the root file system.
> > 
> > Say you have a bunch of files in /boot, but for some reason you have a
> > /boot partition that wasn't mounted when those files were created 
> > then you mount the /normal/ boot partition over it and now the other
> > files are now hidden from view, but still taking up space.
> 
> So you're talking about creating files in an unmounted partition, and
> then mounting it, but since file addition happened when the FS was
> still in an unmounted state, the new files weren't written to the
> journal?
> 
> Surely in that case the new files would simply not be registered and
> act as free space (as if they had been deleted)?

No, the other way around. (You can't create files on an unmounted filesystem.)

1. A directory contains some files.
2. You mount a filesystem onto that directory. (You obviously don't
   realise that this, while unusual, is a perfectly well-defined
   operation. †)
3. The directory now contains the top-level files in the filesystem.
   The files that were in the directory before are inaccessible,
   hidden under the mounted filesystem.
4. You unmount the filesystem. Now you can see the original files again.

While the files are hidden, they still occupy the space.

† Take a look at the first three paragraphs of   man mount.

Cheers,
David.

Re: which files took the space

[Gene Heskett]

On Thursday 03 March 2016 23:18:59 Adam Wilson wrote:

> On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan
>
>  wrote:
> > On 4/03/2016 3:07 AM, Adam Wilson wrote:
> > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> > >
> > >  wrote:
> > >> It also may have been files in the file system, but where another
> > >> file system mount hides them
> > >
> > > What does this mean? Mounts overlapping and hiding other mounts?
> > >
> > > Explain, please.
> >
> > Yes, this is more likely to happen to the root file system.
> >
> > Say you have a bunch of files in /boot, but for some reason you have
> > a /boot partition that wasn't mounted when those files were created
> >  then you mount the /normal/ boot partition over it and now the
> > other files are now hidden from view, but still taking up space.
>
> So you're talking about creating files in an unmounted partition, and
> then mounting it, but since file addition happened when the FS was
> still in an unmounted state, the new files weren't written to the
> journal?
>
> Surely in that case the new files would simply not be registered and
> act as free space (as if they had been deleted)?

No, the mount point, by whatever name exists as a directory on the hard 
drive, and creating files in that mount point actually creates the files 
and they take up normal space on the drive in that directory.  You can 
then mount another drive or partition on top of that mount point, which 
hides the files, but they are still there, taking up space.

If you need those files to be accessable at that mount point in normal 
operation, you must create a different mount point, umount that storage 
from that mount point and mount it to the new different point.  You will 
now see that the files are there, and you can use some file utility (I'm 
old old school, so mc is the obvious choice) to move them to the storage 
mounted elsewhere temporarily. When that directory is empty, you umount 
that storage from its temporary location and remount it back where it 
will normally live. Now those files really are there.  Problem solved 
and you have your drive space back too.

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 

Netinstall senza rete

[Fabrizio Carrai]

Ciao a tutti,
Ho fatto una installazione Debian usando la Netinstall. Purtroppo al
momento dell'installazione la rete non era disponibile e quindi potuto fare
solo una installazione minimale. Tutto ok. Ora la connessione di rete è
funzionante.

Che cosa devo fare per completare l'installazione e scegliere gli altri
pacchetti ?

Grazie
-- 
*Fabrizio*

Re: Bluetooth headphones mistaken for a keyboard!?!

[Mark Fletcher]

deloptes  gmail.com> writes:

> 
> Mark Fletcher wrote:
> 

> > PC is
> > a 7-year-old self-built desktop box running Jessie with Gnome as the DE,
> 
> Which version of debian are you on and which kernel?
> 

Thanks for your time and attention. As I mentioned in my original post, I 
am running Jessie. The kernel is the stock x86_64 kernel currently in 
Jessie. I'm sorry but I'm not in front of the computer right now and am not 
sure exactly what version. I last updated last Sunday.

> You may need to tell udev what kind of device it is, but we don't know if
> your system is configured properly
> 

I'm fairly confident in my system configuration since I have been able to 
get my system to work as s Pulse SINK for an iPhone and Android SOURCE, 
which is reputed to be harder than what I am trying to do here. But I take 
your point, no proof there isn't some misconfiguration lurking somewhere. 
And I suppose it's possible that I jiggered something up, if you'll pardon 
the technical term, when I was getting the iPhone / Android thing working. 
I'm not sure HOW to educate udev on a device it doesn't just know -- and 
the few google queries on that I have tried so far have left me cross-
eyed...

> I couldn't find any information on that
> head set and linux except that head set is pretty expensive
> 

Yes it's a very nice pair of headphones -- the sound quality is amazing, 
and the noise cancellation isn't bad either. And comfortable for spectacle 
wearers which not all makers can claim.

> https://lwn.net/Articles/531133/
> http://jfcarter.net/~jimc/documents/blue-music-1504.html
> 

Thanks for these -- I have only been able to review the second of these as 
the first is being blocked by my company firewall for some reason. I'll 
look at it when I get home tonight. Unfortunately, the second, like 
everything I've read on the internet about this problem in the last 24 
hours or so, skips over the problem I'm having -- from pairing (no problem) 
to connecting (no ERRORS, _probably_ no problem) to configuring / setting 
up Pulse (which I don't get to because my system thinks a keyboard just 
connected to it, not a pair of headphones). 

Mark

Re: which files took the space

[Frédéric Marchal]

On Friday 04 March 2016 07:18:59 Adam Wilson wrote:
> On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan
> 
>  wrote:
> > On 4/03/2016 3:07 AM, Adam Wilson wrote:
> > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> > > 
> > >  wrote:
> > >> It also may have been files in the file system, but where another
> > >> file system mount hides them
> > > 
> > > What does this mean? Mounts overlapping and hiding other mounts?
> > > 
> > > Explain, please.
> > 
> > Yes, this is more likely to happen to the root file system.
> > 
> > Say you have a bunch of files in /boot, but for some reason you have a
> > /boot partition that wasn't mounted when those files were created 
> > then you mount the /normal/ boot partition over it and now the other
> > files are now hidden from view, but still taking up space.
> 
> So you're talking about creating files in an unmounted partition, and
> then mounting it, but since file addition happened when the FS was
> still in an unmounted state, the new files weren't written to the
> journal?
> 
> Surely in that case the new files would simply not be registered and
> act as free space (as if they had been deleted)?

This is not about a caching service. It is about the way the content of a 
mounted disk is made visible to you.

Have you ever wondered how a path name, on your main hard disk, such as 
/mnt/usb becomes a link to a USB disk known to the system as /dev/sdd1?

When you type

mount /dev/sdd1 /mnt/usb

It tells the system that, from now on, the directory named "/mnt/usb" becomes 
the entry point to the file system that sit at "/dev/sdd1".

Any call such as "ls /mnt/usb" will list the content of the USB disk instead 
of the usual content of /mnt/usb.

When the device is unmounted, the directory that serves as its mount point is 
restored as a regular directory.

Now, imagine /mnt/usb is not mounted. It is a directory just like any other. 
If you copy files to /mnt/usb, they will be copied to that directory and you 
have access to them as long as no device is mounted under /mnt/usb.

Then, you mount the USB disk to /mnt/usb. Now, the files are still on the hard 
disk (let's say /dev/sda1) but the path /mnt/usb now lists the content of the 
USB disk on /dev/sdd1.

It can happen with /boot or /home. Mistakenly copying files to an unmounted 
drive copies the files to the underlying file system, in the directory that 
usually serves as the mount point for the external file system. Once /boot or 
/home is mounted, you don't see the files but they are still taking space on 
the disk.

Hope it helps,

Frederic

Re: which files took the space

[jdd]

Le 04/03/2016 08:11, Frédéric Marchal a écrit :


It can happen with /boot or /home. Mistakenly copying files to an unmounted
drive copies the files to the underlying file system, in the directory that
usually serves as the mount point for the external file system. Once /boot or
/home is mounted, you don't see the files but they are still taking space on
the disk.



I have recently seen such thing happening, due to faulty script 
expecting a usb mounted disk that was not always there. A rsync in such 
situation can fill a disk


jdd