Re: How to install Android Studio on Wheezy?

[David Christensen]

On 11/15/2015 09:35 PM, Marc Shapiro wrote:

I am running Wheezy and I want to install Android Studio.


My notes for installing Android Studio on Wheezy amd64 follow.


David



June 12, 2015

3.  Install Android Studio as dpchrist:

	$ scp 
cd2533:/mnt/i1500/data/dpchrist/Downloads/a/android/android-studio-ide-141.1903250-linux.zip 
.


$ unzip android-studio-ide-141.1903250-linux.zip

OpenJDK 6 is not supported by Android Studio.  Install 7:

$ sudo apt-get install openjdk-7-jdk

'apt-get install ia32-libs' fails on Debian 7 amd64.  Forget it.

$ sudo apt-get install --no-install-recommends lib32ncurses5-dev

$ sudo apt-get install --no-install-recommends lib32stdc++6


$ vi launch-android-studio.sh

#!/bin/sh
PATH=android-studio/bin:$PATH
studio.sh

$ chmod +x launch-android-studio.sh

$ ./launch-android-studio.sh

	Select "I do not have a previous version of Studtio or I do not 
want to import my settings".


Choose Next.

Choose Standard.

In another terminal, install KVM:

$ sudo apt-get --no-install-recommends install kvm

Continue with Android Studio:

Choose Next.

Select Accept.

Wait while components are downloaded and installed.


June 29, 2015

1.  Android Studio pukes when attempting to build default
"hello, world!" application.  Mess begins with:

	AAPT err(2071467357): 
/home/dpchrist/Android/Sdk/build-tools/23.0.0_rc2/aapt: error while 
loading shared libraries: libz.so.1: cannot open shared object file: No 
such file or directory


File exists:

$ locate libz.so.1
/lib/x86_64-linux-gnu/libz.so.1
/lib/x86_64-linux-gnu/libz.so.1.2.7

STFW -- try installing Apt package:

# apt-get install lib32z1

Build -> Make Project now works.


July 3, 2015

1.  Install Git.

2.  As dpchrist, introduce myself to Git:

$ git config --global user.name "David Christensen"

$ git config --global user.email dpchr...@holgerdanske.com

Start Android Studio.  Invoke Build -> Clean Project.  Close
Android Studio.

Put project into Git:

$ cd AndroidStudioProjects/HelloAndroid/

$ git init
	Initialized empty Git repository in 
/home/dpchrist/AndroidStudioProjects/HelloAndroid/.git/


$ git add .

$ git commit

Re: sudo does not respond to settings in /etc/sudoers

[Ken Heard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2015-11-15 23:26, Teemu Likonen wrote:

> Maybe you added the user to the "undo" group

Surely you mean the "sudo" group?

> but forgot to test it with a new login session. Group changes
> don't affect the current login session (unless newgrp is used).

My eureka moment! I forgot to logout and in again as my user before
testing the various options. I tested the two options to do what I
wanted to do as described in my original post, but not both on, or
open at the same time. I found that adding to the "user privilege
specification" section in the sudoers file the following line DOES work:

ken ALL=NOPASSWD: ALL

However, removing that line, and in the TDE User Manager (Kuser)
simply adding my user to the "sudo" group does NOT work. That option
DOES nevertheless work in my Jessie box. Strange.

Thanks guys for collectively putting me on the right track.

Ken




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

iEYEARECAAYFAlZJfKEACgkQlNlJzOkJmTfY6ACeOijk3QTayP+2rIpUJ0N9Zj2x
sSYAn01UPKZyBd6QAa1t0GbcT+9d7hF3
=hCiX
-END PGP SIGNATURE-

jira integration

[Louis Lu]

Hi,

I am currently working on a project for my company and search for a suitable 
help desk software.

Debian bug tracking system is one of the products on the list.

However, I have some technical issues and wonder if you guys can give me a hand.

One of the key features of the product we need is that it must have 2-way 
integration between Jira and Debian bug tracking system.

What I mean 2-way integration:
I can create a ticket (eg a bug/support contact etc) from Debian bug tracking 
system in Jira.

If I update (eg, adding a comment or changing the status etc) that ticket in 
Jira, Debian bug tracking system will get automatically updated with the 
changes.
If I update in Debian bug tracking system, Jira will get automatically updated.

Is this possible to be done in Debian bug tracking system? Do you have an 
already built Plug-in for this functionality?



Kind regards,

Louis Lu
Graduate Support Analyst

Re: how execute a script

[Chris Bannister]

On Mon, Nov 16, 2015 at 06:54:40AM +0100, Martin Str|mberg wrote:
> In article  David Wright 
>  wrote:
> > As for script-file extensions in DOS, there was really only .BAT
> > wasn't there?, so the idea of distinguishing .bash, .csh, .py, .pl,
> > .sh, .zsh etc as being inherited from DOS is difficult for me to
> > understand.
> 
> Perhaps it's because (MS)DOS begat WINDOWS that only knew how to run
> something based on the extension?

That's what I understood the comment to mean.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

Re: Charsets v grep

[Martin Str|mberg]

In article  R. Clayton  
wrote:
> and I've been getting a lot of this lately:

>   $ grep ^Subject: cbtm 
>   Binary file cbtm matches

> whereas before (a month or so ago) I used to get actual matches on std-out.
> It's easy enough to work around like so

>   $ sed -n -e '/^Subject:/p' < cbtm 
>   Subject: Re: PTFACULTY: FTFACULTY: When saying "Nous sommes Paris" is not
>   Subject: FTFACULTY: When saying "Nous sommes Paris" is not enough
>   Subject: Lowered Reserve Prices

> but I'd like to grep working like it used to.  What is the way for me to get
> grep back?  Some other points that may be useful:

>   $ file cbtm 
>   cbtm: ISO-8859 text, with very long lines

>   $ ba env | grep -i utf
>   LANG=en_US.UTF-8
>   XTERM_LOCALE=en_US.UTF-8

Trying "grep -a ..." might work. Or "LANG=C grep ...".


-- 
MartinS

Re: how execute a script

[Martin Str|mberg]

In article  David Wright 
 wrote:
> As for script-file extensions in DOS, there was really only .BAT
> wasn't there?, so the idea of distinguishing .bash, .csh, .py, .pl,
> .sh, .zsh etc as being inherited from DOS is difficult for me to
> understand.

Perhaps it's because (MS)DOS begat WINDOWS that only knew how to run
something based on the extension?

And that is why we shudder on the sight of a (unnecessary?) extension?


-- 
MartinS

How to install Android Studio on Wheezy?

[Marc Shapiro]

I am running Wheezy and I want to install Android Studio.  I am looking 
at the following post:


http://techieventures.blogspot.com/2014/11/install-android-studiosdk-on-debian.html

I already have multi-arch set up, as well as the required libraries.

Apparently, Android Studio requires Oracle's JDK and will not work with 
OpenJDK, so installing java-package and creating  a .deb package of 
Oracle's JDK 8 is my next step.   That doesn't look too bad.


My real questions are:

1)  The requirements for Android studio, posted at:

http://developer.android.com/sdk/index.html#Requirements

say:

 * GNOME or KDE desktop
 * GNU C Library (glibc) 2.15 or later
 * 2 GB RAM minimum, 4 GB RAM recommended
 * 400 MB hard disk space
 * At least 1 GB for Android SDK, emulator system images, and caches
 * 1280 x 800 minimum screen resolution
 * Oracle® Java Development Kit (JDK) 7


Wheezy has glibc 2.13.  The instructions that I linked to above are a 
year old and make no mention of upgrading from 2.13 to 2.15. Since so 
much is dependent on glibc, changing from 2.13 to 2.15 seems potentially 
hazardous.  Is there a reasonable way to upgrade to 2.15, or otherwise 
satisfy this requirement while staying with Wheezy, or am I going to be 
forced to update to Jessie?  I have not switched to Jessie, yet, as I am 
not convinced that systemd is a good idea.  (This post is NOT about 
systemd and I do NOT want the discussion to take up that arguement!  
Please!)


2) The Android Studio requirements say "GNOME or KDE desktop".  Do they 
really mean that?  Can you not use Android Studio unless you are willing 
to use one of those two DTEs?  I am running Mate.  Is that close enough?


Marc

Re: no SMART support for western digital drive

[David Christensen]

On 11/15/2015 09:10 PM, kamaraju kusumanchi wrote:

I do not think it is a problem with CMOS setup since SMART is working
fine on my internal hard drive. But I can check for it next time when
I reboot the computer.


So, the drive is not internal?  How is it connected to your computer?


David

Re: no SMART support for western digital drive

[kamaraju kusumanchi]

On Mon, Nov 16, 2015 at 12:01 AM, Andrew McGlashan
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 16/11/2015 3:32 PM, kamaraju kusumanchi wrote:
>> Running gsmartcontrol on a brand new Western Digital hard drive
>> says that SMART support is unavailable. I was under the impression
>> that most hard drives have SMART support these days. Given that
>> Western Digital is a popular company I am a bit shocked that they
>> are manufacturing hard drives without SMART support.
>>
>> Does anyone know of a work around to check the health of this
>> drive?
>
> It's likely that the drive isn't directly connected to the SATA bus;
> if it is going through a "bridge" device, be that a USB, Firewire or
> something else... then there is every chance that your are being
> denied access as it isn't passing through.
>
> Kind Regards
> AndrewM

The hard drive is placed in a Dual Bay external hard drive docking
station which is connected via USB to my computer. Is that a problem?

Docking station info:
Sabrent USB 3.0 to SATA Dual Bay External Hard Drive Docking Station
for 2.5 or 3.5in HDD, SSD with Hard Drive Duplicator/Cloner Function
[4TB Support] (EC-HDD2)
http://www.amazon.com/gp/product/B00IKC14OG

Is my only option to connect this hard drive internally? How does one
check the health of a drive connected via USB?

thanks
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: no SMART support for western digital drive

[kamaraju kusumanchi]

On Sun, Nov 15, 2015 at 11:54 PM, David Christensen
 wrote:
> On 11/15/2015 08:32 PM, kamaraju kusumanchi wrote:
>>
>> Does anyone know of a work around to check the health of this drive?
>
>
> Check your CMOS setup for a SMART enable/ disable setting.
>

I do not think it is a problem with CMOS setup since SMART is working
fine on my internal hard drive. But I can check for it next time when
I reboot the computer.

thanks
-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: no SMART support for western digital drive

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 16/11/2015 3:32 PM, kamaraju kusumanchi wrote:
> Running gsmartcontrol on a brand new Western Digital hard drive
> says that SMART support is unavailable. I was under the impression
> that most hard drives have SMART support these days. Given that
> Western Digital is a popular company I am a bit shocked that they
> are manufacturing hard drives without SMART support.
> 
> Does anyone know of a work around to check the health of this
> drive?

It's likely that the drive isn't directly connected to the SATA bus;
if it is going through a "bridge" device, be that a USB, Firewire or
something else... then there is every chance that your are being
denied access as it isn't passing through.

Kind Regards
AndrewM
-BEGIN PGP SIGNATURE-

iF4EAREIAAYFAlZJYygACgkQqBZry7fv4vtUfgD/eCMtCP/oZ25+pG7fQnhH33/Y
tZ6eM4+0iZDUdcKmbHgA/3CJBX7Qqip3ZcujjHV4JN2xRfleEy59az8J4z5+LmxF
=qN70
-END PGP SIGNATURE-

Re: no SMART support for western digital drive

[David Christensen]

On 11/15/2015 08:32 PM, kamaraju kusumanchi wrote:

Does anyone know of a work around to check the health of this drive?


Check your CMOS setup for a SMART enable/ disable setting.


David

Re: how execute a script

[David Wright]

On Sat 14 Nov 2015 at 08:00:20 (+0100), to...@tuxteam.de wrote:
> On Fri, Nov 13, 2015 at 09:11:34AM -0600, David Wright wrote:
> > On Fri 13 Nov 2015 at 14:43:39 (+0100), to...@tuxteam.de wrote:
> > 
> > > (as an aside: it's bad custom inherited from DOS to name shell scripts
> > > with an .sh ending. No ending is the right thing here).
> > 
> > So these were all DOS scripts once, were they?
> > 
> > -rwxr-xr-x 1 root root 1248 Apr 21  2014 /etc/init.d/bootmisc.sh*
> > -rwxr-xr-x 1 root root 3807 Apr 21  2014 /etc/init.d/checkfs.sh*
> 
> [...]
> 
> Very smart. I didn't say the scripts are inherited from DOS. That bad
> habit is, definitely.

Well file extensions in general are of course much older than DOS
(assuming you mean MSDOS-compatible rather than the old meaning as in,
say, DOS/360 etc), going back to the origins of unix and further.

As for script-file extensions in DOS, there was really only .BAT
wasn't there?, so the idea of distinguishing .bash, .csh, .py, .pl,
.sh, .zsh etc as being inherited from DOS is difficult for me to
understand. I have no idea what was going through the head of whoever
christened /etc/init.d/hostname.sh originally.

> > I name my scripts in ~/bin with an extension corresponding to their
> > contents: .pl .py .sh etc. Where I'm working on alternative versions,
> > I might have more than one language. Extensionless filenames are
> > either links or binaries. What's bad about this? Or is it just
> > snobbery: Look, we don't need extensions.
> 
> No. If you call your scripts from other places, and -- say -- change
> the implementation from shell to ruby: do you have to run around and
> fix all the call sites? Have fun.

Of course I don't. Just write a foo.rb script, and when happy with it,
move the link to point at it. Above, you just quoted my saying
"Extensionless filenames are either links or binaries."

> The one case where an "extension" (as you call it: DOS, see?)

"Extension" is a generally understood shorthand that's been around for
years. Should we go through man pages such as gzip and change the word
to "suffix"? Or we could go back to using the language of dmr, as in:
'Arguments whose names end with ".c" are assumed to be C source
programs; they are compiled, and the object program is left on the
file sfile.o (i.e. the file whose name is that of the source with ".o"
substituted for ".c").'

> might
> make sense (I'd say a hint in the filename) is when your script isn't
> an executable in itself but a collection of functions you *source*
> from another shell: this so-called "shell library" has to be shell
> code (i.e. you can't change implementation).

Well, yes, that's frequently recommended in such cases.

> And snobbery? Pthttht.

Well, I'm just trying to find a motive for your condemnation, the use
of words like "right thing" and "bad", and your conviction that it's
all down to DOS (not just the phenomenon but even the word I used to
describe it).

I've never distributed a library, but have read about distributions
being packaged with file extensions, these then being stripped off at
installation time. As already explained in this thread, I achieve
the same effect with a link. I don't have enough scripts to have a
separate archive all packaged up and with an installation script, but
I want to be able to see the various scripting languages without
having to open the files themselves.

Say I want to see how many python scripts are still using a module
that I'm eliminating. I type grep ... ~/bin/*py just as I would if
python was a compiled language, rather than testing every file in
~/bin/* with file to discover its source language.

Cheers,
David.

no SMART support for western digital drive

[kamaraju kusumanchi]

Running gsmartcontrol on a brand new Western Digital hard drive says
that SMART support is unavailable. I was under the impression that
most hard drives have SMART support these days. Given that Western
Digital is a popular company I am a bit shocked that they are
manufacturing hard drives without SMART support.

Does anyone know of a work around to check the health of this drive?

Hard disk Info:
"WD Blue 1TB Desktop Hard Disk Drive - 7200 RPM SATA 6 Gb/s 64MB Cache
3.5 Inch - WD10EZEX" bought from Amazon
http://www.amazon.com/Blue-Desktop-Hard-Disk-Drive/dp/B0088PUEPK.


gsmartcontrol output:

smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:   WDC WD10
Product:  EZEX-00BN5A0
Revision: 0106
Compliance:   SPC-4
User Capacity:1,000,204,886,016 bytes [1.00 TB]
Logical block size:   512 bytes
LB provisioning type: unreported, LBPME=-1, LBPRZ=0
Form Factor:  3.5 inches
Logical Unit id:  0x50323039383638bd
Serial number:DB98765432117
Device type:  disk
Local Time is:Sun Nov 15 23:17:54 2015 EST
SMART support is: Unavailable - device lacks SMART capability.

=== START OF READ SMART DATA SECTION ===

Error Counter logging not supported

Device does not support Self Test logging

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

very naive question iPad as extra monitor

[Jerome BENOIT]

Hello Forum:

Does anyone know a working way to use an iPad as extra monitor with Debian ?

Thanks in advance,
Jerome

Charsets v grep

[R. Clayton]

I'm running this

  $ bash --version
  GNU bash, version 4.3.42(1)-release (i586-pc-linux-gnu)
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  $

on this

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Debian
  Description:  Debian GNU/Linux testing-updates (sid)
  Release:  testing-updates
  Codename: sid

  $

and I've been getting a lot of this lately:

  $ grep ^Subject: cbtm 
  Binary file cbtm matches

  $

whereas before (a month or so ago) I used to get actual matches on std-out.
It's easy enough to work around like so

  $ sed -n -e '/^Subject:/p' < cbtm 
  Subject: Re: PTFACULTY: FTFACULTY: When saying "Nous sommes Paris" is not
  Subject: FTFACULTY: When saying "Nous sommes Paris" is not enough
  Subject: Lowered Reserve Prices

  $

but I'd like to grep working like it used to.  What is the way for me to get
grep back?  Some other points that may be useful:

  $ file cbtm 
  cbtm: ISO-8859 text, with very long lines

  $ ba env | grep -i utf
  LANG=en_US.UTF-8
  XTERM_LOCALE=en_US.UTF-8

  $ 

Re: default English (US) QWERTY layout

[Patrick Bartek]

On Sun, 15 Nov 2015, rlhar...@oplink.net wrote:

> On Sun, November 15, 2015 12:00 pm, Patrick Bartek wrote:
> > As I don't run a desktop (window manager only -- Openbox) on my very
> > custom installed Wheezy 64-bit system, I can't follow your menu
> > request, but 'debconf-show keyboard-configuration' reports:
> 
> Thanks for introducing me to debconf-show.  One of the best parts
> about the list is that it calls attention to such useful but
> generally-unknown tools.

A wealth of information awaits by following-up on the "SEE
ALSO" section of every man page.

B

any way to setup a nevo c2 remote control ?

[Bernard]

Hi,

This remote is said to be compatible with linux. I have both Debian 
Lenny and Ubuntu 14.04 on 2 different computers, trials were carried on 
both.


Has anyone ever succeeded to connect to the setup database ?

www.ez-rc.com is the url that is written on the remote cover, the device 
comes with no paper notice.. Once this url reached, you are being 
requested to either create a new account or connect to an existing one. 
Problem is, whichever email address you enter as a new user, the reply 
is 'This e-mail address is already registered with us'. On the other 
hand, if you try to connect as a know user using same adress, and then 
click upon 'lost pasword ?', you get asked to enter again your e-mail 
adress, and then get the reply that the address in their base is not 
matching. Something must be wrong, maybe the service is being 
discontinued. True enough, in the bottom of login page, appears in red 
"this site is designed for Internet Explorer version 7 and 8". So, I 
tried to connect using an old XP partition with IE7, but then, whenever 
I enter an e-mail address on the ez-rc application, it says "this format 
is not reckognized".


I hope that there is a way to get connected to this setup site, or maybe 
a way around.


Thanks in advance for any input

Bernard

sound for multiple users in Debian Jessie

[Staszek]

Hi

How do I enable sound for multiple users in Debian Jessie?

I have tried adding those other users to the audio group but it doesn't
help.

-- 
http://people.eisenbits.com/~stf/
http://www.eisenbits.com/

OpenPGP: 9EC2 5620 2355 B1DC 4A8F  8C79 0EC7 C214 E5AE 3B4E

Re: default English (US) QWERTY layout

[Lisi Reisz]

On Sunday 15 November 2015 21:46:23 Ric Moore wrote:
> On 11/15/2015 04:34 PM, rlhar...@oplink.net wrote:
> > On Sun, November 15, 2015 2:10 pm, David Christensen wrote:
> >> I just did a fresh install of debian-8.2.0-amd64-xfce yesterday:
> >>
> >> Keyboard model Generic 105-key (Intl) PC
> >
> > Obviously, the keyboard settings menu (reached from xfce by
> >
> > applications -> setting -> keyboard -> layout
> >
> > has its own layout nomenclature.  The only "English (US, ...)" selections
> > which the menu on my system (i386, Jessie, Xfce) offers are:
> >

> > English (US, international with dead keys)

This one appears to be the "normal" "standard" US international.


Dead keys on various keyboard layouts[edit]
Main article: Keyboard layout
A key may function as a dead key by default, and many non-English keyboard 
layouts in particular have dead keys directly on the keyboard. The basic US 
keyboard does not have any dead keys, but the US-International keyboard 
layout, available on Windows and the X Window System, places some dead keys 
directly on similar-looking punctuation marks. Old computer systems, such as 
the MSX, often had a special key labeled dead key, which in combination with 
the Ctrl and Shift keys could be used to add some of the diacritics commonly 
needed in the Western European languages (´, `, ˆ and ¨) to vowels that were 
typed subsequently.

https://en.wikipedia.org/wiki/Dead_key

https://www.google.co.uk/search?q=English+(US,+international+with+dead+keys),
+layout&es_sm=93&biw=1156&bih=835&tbm=isch&imgil=0nPw4DKeEA8BAM%253A%253BKCWVRBoNfdDbvM%253Bhttp%25253A%25252F%25252Fapple.stackexchange.com%25252Fquestions%25252F30262%25252Fus-international-altgr-dead-keys-layout-on-mac-os-x&source=iu&pf=m&fir=0nPw4DKeEA8BAM%253A%252CKCWVRBoNfdDbvM%252C_&usg=__7-YA249zdN0UqeYtD4catm2jDSU%3D&ved=0CCgQyjdqFQoTCIesnKS4k8kCFcRaGgodWzEJMA&ei=HQJJVsepIMS1advipIAD#imgrc=VPY-rIKk-acQWM%3A&usg=__7-YA249zdN0UqeYtD4catm2jDSU%3D

Lisi

> > English (US, with euro on 5)
> >
> > none of which look familiar to me.  So I wondered whether I had managed
> > to delete whatever is the default English US layout.
> >
> > What I would like to know is the "English (US...)" options which the
> > keyboard settings menu offers if the menu has not been used to switch
> > from the default English US layout to some other layout.
>
> Mine says "Generic 105 (intl) PC" for keyboard model and "English (US)"
> for layout. Hope that helps. That is the "system default" setting used
> at install time. Ric

Re: default English (US) QWERTY layout

[rlharris]

On Sun, November 15, 2015 3:46 pm, Ric Moore wrote:
> Mine says "Generic 105 (intl) PC" for keyboard model and "English (US)"
> for layout. Hope that helps. That is the "system default" setting used at
> install time. Ric

In my previous posting, I neglected to tack on " -> +add" at the tail.

But guess what?  In response to:

  applications -> setting -> keyboard -> layout -> +add

I was not simply selecting English (US); rather, I clicked on the EXPAND
symbol (">") and that displayed a list of variants, none of which is
simply "English (US)".

Mystery solved (at least in part).  Thanks, Ric.

Russ

Re: default English (US) QWERTY layout

[Ric Moore]

On 11/15/2015 04:34 PM, rlhar...@oplink.net wrote:

On Sun, November 15, 2015 2:10 pm, David Christensen wrote:

I just did a fresh install of debian-8.2.0-amd64-xfce yesterday:

Keyboard model  Generic 105-key (Intl) PC



Obviously, the keyboard settings menu (reached from xfce by

applications -> setting -> keyboard -> layout

has its own layout nomenclature.  The only "English (US, ...)" selections
which the menu on my system (i386, Jessie, Xfce) offers are:

English (US, alternative international)
English (US, international with dead keys)
English (US, with euro on 5)

none of which look familiar to me.  So I wondered whether I had managed to
delete whatever is the default English US layout.

What I would like to know is the "English (US...)" options which the
keyboard settings menu offers if the menu has not been used to switch from
the default English US layout to some other layout.



Mine says "Generic 105 (intl) PC" for keyboard model and "English (US)" 
for layout. Hope that helps. That is the "system default" setting used 
at install time. 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: debian/sid: yubi key USB error: Access denied (insufficient permissions)

[Sven Hartge]

Bruno Voigt  wrote:

> I'm using debian/sid.
> Where do I configure the USB permissions
> so that I can run commands as a regular user:

> $ ykinfo -s
> USB error: Access denied (insufficient permissions)

> $ ykpamcfg -v -2
> USB error: Access denied (insufficient permissions)

> ykinfo run as root works as expected ..

I am using a Yubikey myself, for KeePass and other things and I never
had to do anything special to do so. ykinfo works for me as a normal
user.

Maybe this has something to do with the groups you user is in. Please
provide the output of "id" from your user.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: default English (US) QWERTY layout

[rlharris]

On Sun, November 15, 2015 2:10 pm, David Christensen wrote:
> I just did a fresh install of debian-8.2.0-amd64-xfce yesterday:
>
> Keyboard modelGeneric 105-key (Intl) PC


Obviously, the keyboard settings menu (reached from xfce by

   applications -> setting -> keyboard -> layout

has its own layout nomenclature.  The only "English (US, ...)" selections
which the menu on my system (i386, Jessie, Xfce) offers are:

   English (US, alternative international)
   English (US, international with dead keys)
   English (US, with euro on 5)

none of which look familiar to me.  So I wondered whether I had managed to
delete whatever is the default English US layout.

What I would like to know is the "English (US...)" options which the
keyboard settings menu offers if the menu has not been used to switch from
the default English US layout to some other layout.

Russ

Re: assistance for determining package for bugreport

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Nov 15, 2015 at 05:40:00PM +0100, wandang wrote:
> Hello there,
> 
> I wanted to report a bug but I failed to determine the packagename.
> 
> The bug occurs in the default mouse&trackpad settings menu (gui).
> 
> My os: Debian stretch
> 
> Thank you for your guidance!

First we have to find out which settings program is making difficulties.
As Brian has aleady hinted, it's probably part of your desktop environment.
Are you using Gnome?

Can you describe the bug a bit more?

> PS: Sorry if I failed procedures already!

No worries. We try to help as good as we can, and everyone understands
that it takes a while to find out what's happening.

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

iEYEARECAAYFAlZI69MACgkQBcgs9XrR2kYB/ACfZBfm1SJ1C7CYqFJzryBNtG5v
7IQAn3vZQPQJicrn7FqRWN5QQuJnVkiD
=BtK6
-END PGP SIGNATURE-

Re: assistance for determining package for bugreport

[Sven Arvidsson]

On Sun, 2015-11-15 at 17:40 +0100, wandang wrote:
> Hello there,
> 
> I wanted to report a bug but I failed to determine the packagename.
> 
> The bug occurs in the default mouse&trackpad settings menu (gui).
> 
> My os: Debian stretch
> 
> Thank you for your guidance!
> 
> PS: Sorry if I failed procedures already!

It is most likely gnome-control-center

But unless it's something that's specific to Debian it's usually a bett
er idea to file the bug directly upstream. 

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





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

Re: default English (US) QWERTY layout

[Ric Moore]

On 11/15/2015 03:10 PM, David Christensen wrote:

On 11/14/2015 09:01 PM, rlhar...@oplink.net wrote:

Would some kindly soul who is a English (US) QWERTY user and who is
running Jessie on an i386 system follow the path:

applications -> setting -> keyboard -> layout

and tell me which is the default English (US) layout which is selected by
the installer?


I get "English US" using AMD64 - Stretch. Dunno if that is different on 
i386.


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

debian/sid: yubi key USB error: Access denied (insufficient permissions)

[Bruno Voigt]

Hi,

I'm using debian/sid.
Where do I configure the USB permissions
so that I can run commands as a regular user:

$ ykinfo -s
USB error: Access denied (insufficient permissions)

$ ykpamcfg -v -2
USB error: Access denied (insufficient permissions)

ykinfo run as root works as expected ..

Thanks in advance for any hints.
Bruno

Re: default English (US) QWERTY layout

[David Christensen]

On 11/14/2015 09:01 PM, rlhar...@oplink.net wrote:

Would some kindly soul who is a English (US) QWERTY user and who is
running Jessie on an i386 system follow the path:

applications -> setting -> keyboard -> layout

and tell me which is the default English (US) layout which is selected by
the installer?


I just did a fresh install of debian-8.2.0-amd64-xfce yesterday:

Keyboard model  Generic 105-key (Intl) PC


David

Re: assistance for determining package for bugreport

[Brian]

On Sun 15 Nov 2015 at 17:40:00 +0100, wandang wrote:

> Hello there,
> 
> I wanted to report a bug but I failed to determine the packagename.
> 
> The bug occurs in the default mouse&trackpad settings menu (gui).
> 
> My os: Debian stretch
> 
> Thank you for your guidance!
> 
> PS: Sorry if I failed procedures already!

You might want to discuss a problem? You are in the right place but will
have to be more specific about what the problem is.

A bug report is not for reporting problems. If it contained the level of
detail you have provided here it would probably be of little use. 

Re: default English (US) QWERTY layout

[rlharris]

On Sun, November 15, 2015 12:00 pm, Patrick Bartek wrote:
> As I don't run a desktop (window manager only -- Openbox) on my very
> custom installed Wheezy 64-bit system, I can't follow your menu request,
> but 'debconf-show keyboard-configuration' reports:

Thanks for introducing me to debconf-show.  One of the best parts about
the list is that it calls attention to such useful but generally-unknown
tools.

Russ

Re: default English (US) QWERTY layout

[Patrick Bartek]

On Sat, 14 Nov 2015, rlhar...@oplink.net wrote:

> Would some kindly soul who is a English (US) QWERTY user and who is
> running Jessie on an i386 system follow the path:
> 
> applications -> setting -> keyboard -> layout
> 
> and tell me which is the default English (US) layout which is
> selected by the installer?
> 
> I routinely switch to "classic Dvorak" immediately after installing
> and delete the default layout.
> 
> But now I need to switch over a machine for a friend who knows only
> QWERTY.

As I don't run a desktop (window manager only -- Openbox) on my very
custom installed Wheezy 64-bit system, I can't follow your menu
request, but 'debconf-show keyboard-configuration' reports:

* keyboard-configuration/modelcode: pc105
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/unsupported_config_layout: true
* keyboard-configuration/toggle: No toggling
* keyboard-configuration/compose: No compose key
* keyboard-configuration/layout:
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/variant: English (US)
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/switch: No temporary switch
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/variantcode:
* keyboard-configuration/model: Generic 105-key (Intl) PC
* keyboard-configuration/layoutcode: us
* keyboard-configuration/other:
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/optionscode:

This was the keyboard type the installer picked when I installed Wheezy.  I saw 
reason to change it.

The keyboard itself is a Kensington Keyboard for Life that has to be at least 6 
years old, and I've been using it on this system I build about 9 years ago 
which has gone through numerous hardware upgrades and OSes in those 9 years.

B
 

TLP vs laptop-mode-tools?

[Himanshu Shekhar]

Am bit confused between choosing laptop-mode-tools and tlp for power-saving
on my Dell laptop?
Can anyone suggest the better one? All I need is the maximum possible
battery life out of my laptop.
Are there any additional tweaks needed for them?

Regards
Himanshu Shekhar

assistance for determining package for bugreport

[wandang]

Hello there,

I wanted to report a bug but I failed to determine the packagename.

The bug occurs in the default mouse&trackpad settings menu (gui).

My os: Debian stretch

Thank you for your guidance!

PS: Sorry if I failed procedures already!

Re: sudo does not respond to settings in /etc/sudoers

[Johan DS]

Did you check the permissions?

-r--r- 1 root root 1011 Oct  4 21:58 /etc/sudoers





On Sun, Nov 15, 2015 at 5:27 PM, Ric Moore  wrote:

> On 11/15/2015 11:18 AM, Joe wrote:
>
>> On Sun, 15 Nov 2015 10:44:10 -0500
>> Ric Moore  wrote:
>>
>> On 11/14/2015 03:01 PM, Joe wrote:
>>> Your example will
>>>
 still ask for a password, and anyway it's either/or: you can either
 add yourself to the sudo group or add your name to sudoers, you
 don't need both.

>>>
>>> I had to, before it would work. YMMV, Ric
>>>
>>>
>>>
>> You must have an unusually paranoid computer. I have a sid workstation
>> and wheezy server running at the moment, neither of which has any
>> members of the sudo group, which I think is a relatively recent
>> innovation in Debian.
>>
>> It might be one of those situations where 'I did A and it didn't work,
>> I did B and it didn't work, I did C and it finally did work, and I was
>> so relieved that I could get on with the job that was being held up that
>> I didn't take the time to go back and undo A and B'. We've all been
>> there, and have bits of mostly harmless cruft here and there to prove
>> it...
>>
>
> I just installed fresh, after a stinkin' seagate drive failed miserably,
> and had to do both steps before sudo would work. It's become automatic to
> do A and B to get C. But then again, I've never reversed the process to see
> if A or B could be omitted. Maybe I'm scared.   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: sudo does not respond to settings in /etc/sudoers

[Ric Moore]

On 11/15/2015 11:18 AM, Joe wrote:

On Sun, 15 Nov 2015 10:44:10 -0500
Ric Moore  wrote:


On 11/14/2015 03:01 PM, Joe wrote:
Your example will

still ask for a password, and anyway it's either/or: you can either
add yourself to the sudo group or add your name to sudoers, you
don't need both.


I had to, before it would work. YMMV, Ric




You must have an unusually paranoid computer. I have a sid workstation
and wheezy server running at the moment, neither of which has any
members of the sudo group, which I think is a relatively recent
innovation in Debian.

It might be one of those situations where 'I did A and it didn't work,
I did B and it didn't work, I did C and it finally did work, and I was
so relieved that I could get on with the job that was being held up that
I didn't take the time to go back and undo A and B'. We've all been
there, and have bits of mostly harmless cruft here and there to prove
it...


I just installed fresh, after a stinkin' seagate drive failed miserably, 
and had to do both steps before sudo would work. It's become automatic 
to do A and B to get C. But then again, I've never reversed the process 
to see if A or B could be omitted. Maybe I'm scared.   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: sudo does not respond to settings in /etc/sudoers

[Teemu Likonen]

Ric Moore [2015-11-15 10:44:10-05] wrote:

> On 11/14/2015 03:01 PM, Joe wrote:
>> it's either/or: you can either add yourself to the sudo group or add
>> your name to sudoers, you don't need both.
>
> I had to, before it would work. YMMV, Ric

Maybe you added the user to the "undo" group but forgot to test it with
a new login session. Group changes don't affect the current login
session (unless newgrp is used).


signature.asc
Description: PGP signature

Re: sudo does not respond to settings in /etc/sudoers

[Joe]

On Sun, 15 Nov 2015 10:44:10 -0500
Ric Moore  wrote:

> On 11/14/2015 03:01 PM, Joe wrote:
> Your example will
> > still ask for a password, and anyway it's either/or: you can either
> > add yourself to the sudo group or add your name to sudoers, you
> > don't need both.  
> 
> I had to, before it would work. YMMV, Ric
> 
> 

You must have an unusually paranoid computer. I have a sid workstation
and wheezy server running at the moment, neither of which has any
members of the sudo group, which I think is a relatively recent
innovation in Debian.

It might be one of those situations where 'I did A and it didn't work,
I did B and it didn't work, I did C and it finally did work, and I was
so relieved that I could get on with the job that was being held up that
I didn't take the time to go back and undo A and B'. We've all been
there, and have bits of mostly harmless cruft here and there to prove
it...

-- 
Joe

Re: sudo does not respond to settings in /etc/sudoers

[Ric Moore]

On 11/14/2015 03:01 PM, Joe wrote:
Your example will

still ask for a password, and anyway it's either/or: you can either add
yourself to the sudo group or add your name to sudoers, you don't need
both.


I had to, before it would work. YMMV, 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: how execute a script

[shawn wilson]

You can call a function from within a sourced file and it'll run (no matter
x bit).

So:

# ~/bin/runner.sh
runner () {
echo foo
}

runner

# ~/.bashrc
PATH="$PATH:~/bin"
source runner.sh
On Nov 14, 2015 4:51 AM, "Pol Hallen"  wrote:

> Put the command at the end of /home/user/.profile
>> It works for me.
>>
>
> thanks for help but does not work :-/
>
> Pol
>
>