Re: systemd requires "plymouth" on server?

[Mart van de Wege]

Steffen Dettmer  writes:

> 2) "Failed at step exec spawning /bin/plymouth: no such file or directory"
> Google suggest this is some graphical whatever, so I think it would be
> a bug if found on a server
>
No, plymouth is not *just* graphical. It is needed for the cases where
you need to provide a password on boot, such as when you have encrypted
volumes or a KDC with no master password stashed.

As I understand it, because systemd starts everything in parallel as
much as possible, it is possible that the password prompt is no longer
available by the time systemd has stopped firing off startup jobs.

A better explanation here:

http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/

And finally, can you please tone down the hostility to systemd a bit?
The flamewars have quietened down, and the tone of your posts is likely
to fire them up again.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Re: kworker eats 45% from first cpu

[deloptes]

deloptes wrote:

> Hi community,
> I moved my system to an SSD two days ago. I applied recommendation to
> use "discard" when I noticed that one kworker is using exactly 45% of the
> first cpu.


perf says


  55.13%  [kernel]   [k] acpi_os_read_port
  26.65%  [kernel]   [k] acpi_os_write_port
   8.33%  [kernel]   [k] __next_timer_interrupt
   5.41%  libglib-2.0.so.0.4200.1[.]
g_io_channel_get_buffer_condition


./perf top -a

so we now know where the cpu power goes - do you have any idea of this?

regards

Info on missing packages (libdancer2-xxx-perl modules)?

[Richard Hector]

Hi,

I'm not really sure how to phrase my question - or search for the
answers I know I've seen here ...

I quite often find myself wanting to know about package that I think
were, or should be, in debian, but for some reason they're not. Since
they're not there, the packages page can't find them.

Sometimes they've been dropped, sometimes they've never made it in - but
it would be nice to know the reasons why.

I know there is at least one page that has some of that kind of info; it
has been mentioned on this list within the last month or two, but on a
thread about something else.

At the moment, I'm particularly interested in why there seem to be many
modules for the perl Dancer framework, but mostly not the corresponding
ones for the more current Dancer2 rewrite. libdancer2-perl itself is
there, but not the corresponding modules for authentication, sessions
etc. Of course, this may not be recorded anywhere, if nobody's even
expressed a wish for these.

Any hints?

Thanks,
Richard



signature.asc
Description: OpenPGP digital signature

How to fix screen resolution ( has been set to 1024 * 768 )

[manashpal]

After installing Debian latest Jessie in my system, I am getting a 1024*768 
screen resolution, but my monitor can render 1366*768. it is unlikely to have 
got such a unexpected screen resolution like 1024*768. on the other hand 
ubuntu, fedora, kali and many more linux distros has never disappoint me such a 
way. how can I fix it ? kindly let me know the steps I will 
follow.thanks.m@n@sh..p@l

Re: Monitor switched off after resume from hibernation

[Joel Rees]

On Mon, Jan 9, 2017 at 10:01 AM, David Wright 
wrote:
> On Sun 08 Jan 2017 at 07:59:39 (+0100), solitone wrote:
>> On Saturday, January 7, 2017 1:35:07 PM CET David Wright wrote:
>> > you could go on to combine it with the
>> > hibernation process to make sure that the monitor was on just before
>> > hibernation started. (There might be some sort of serialisation
>> > required to make sure the two actions occur in the right order. You
>> > don't want a race.)
>>
>> What sort of serialisation are you referring to? I tried with the
following
>> script, but won't work:
>>
>> $cat /usr/lib/systemd/system-sleep/screen_hack_hibernate
>>
>> if [ "$2" = "hibernate" ]; then
>> case "$1" in
>> pre)
>> xset -display :0 dpms force on
>> ;;
>> esac
>> fi
>>
>> I thought it would be run just before hibernate (it's the same technique
I use
>> to unload the driver of my wifi adapter before hibernate, to prevent
some other
>> network issues I had) , but it doesn't.
>
> I can only answer you in the vaguest terms. I thought you might add a
> service that has to run before hibernate, and it would contain a
> Before= (or hibernate an After= ) line to make sure that turning on
> the monitor preceeded the hibernation.
>
> If you manage this, perhaps with others' help, you'll be ahead of me
> on the systemd learning curve.
>
> BTW I haven't bothered to respond to Stefan Monnier's contribution.
> I can imagine scenarios that might cause power consumption when a
> machine is off (like network cards running to watch for magic WoL
> packets, and things like that),

Cheap power supply designs. I think he indicated.

Without load, some power supply designs draw more energy, either in
not-fully-defined operating modes or in modes where the P/S loads itself
down dynamically.

> but a machine in hibernation should
> cope with a power cut. In any case, I support your expectation that
> using sleep/hibernate should not involve compromising monitors'
> power-saving behaviour.
>
> Cheers,
> David.
>



-- 
Joel Rees

I'm imagining I'm a novelist:
http://reiisi.blogspot.jp/p/novels-i-am-writing.html

Re: Monitor switched off after resume from hibernation

[Joel Rees]

On Fri, Jan 6, 2017 at 6:04 AM, solitone  wrote:
>
> I'm on debian stretch, and my computer is a MacBookPro 12,1. I've recently
> noticed an issue that affect my system when it hibernates.
>
> When the screen is already switched off and then the system hibernates, it
> won't resume correctly later on. Specifically, the monitor will be switched 
> off
> again at the end of the resume process.

So, just out of curiosity, what happens if you use ctrl-alt-Fn to
switch between virtual consoles several times after the box gets stuck
thinking the screen is off?

>
> [...]

>   Davide

-- 
Joel Rees

I'm imagining I'm a novelist:
http://reiisi.blogspot.jp/p/novels-i-am-writing.html

log to journal only

[Henning Follmann]

Hello,

right now the default behavior in stable is to log into /var/log and into
journal (located under /run/log/journal).

I wonder if it safe to disable the "old" way of logging. And if so how to
do that.

-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: autofs config

[Harry Putnam]

Reco  writes:

[...]

> And it gone haywire from here.

Hehe... thats a good description...

> Autofs has a concept of master map ( auto.master(5) ) which can contain
> lines referring to either direct or indirect maps ( autofs(5) ).
> 
> /etc/auto.master.d is intended for extending master map, and the files
> inside it should contain master map entries, not indirect ones like you
> did below.

Thanks... and I got that all squared away.

[...]

Harry wrote
>> created /etc/auto.master.d/prj-nfs.autofs like so (as suggested in
>> auto.master):
>> 
>>   d0 --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/d0
>>   dv --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/dv
>

Reco wrote:
> Note that it be simplified to:
>
> * --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/&

I created /etc/auto.nfs and tried that forumulation. Restarted
autofs.  Nothing gets mounted under (now simplified to /projects in
auto.master) /projects when I do ls /projects/d0 or /projects/dv

There is a bit of a pause with `ls /projects/dv (or d0) but then I
get:
  ls: cannot access /projects/dv: No such file or directory

To clarify my above comments:

  root # grep -v '^#\|^$' /etc/auto.master
  /projects /etc/auto.nfs   --timeout=180
  +dir:/etc/auto.master.d
  +auto.master

  root # grep -v '^#\|^$' /etc/auto.nfs
  *--fstype=nfs4,rw,soft,intr191.168.1.42:/projects/&

I also tried this:

  root # grep -v '^#\|^$' /etc/auto.nfs
  d0   --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/d0
  dv   --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/dv

  A `ls /projects/dv' pauses maybe 10 seconds and returns:
  ls: cannot access /projects/dv: No such file or directory

One question... am I supposed to create the directories
/projects/dv /projects/d0 ?

It appears from the instructions I've seen that .. no I am not to
create those dir... just /projects/.  however, I did try it both ways
and can report that nothing gets mounted in either test.

> Also please note that they give you /etc/auto.net just for your case
> (i.e. mounting nfs).

 Not sure what you mean by `give you'. Do you mean to use as is?
 I tried:
   root # grep -v '^#\|^$' /etc/auto.master
   /projects /etc/auto.net   --timeout=180  (Note: It now says `auto.net')
   +dir:/etc/auto.master.d
   +auto.master

 Made sure auto.net is chmod 755

 Changed (in auto.net)
  opts="-fstype=nfs,hard,intr,nodev,nosuid"
  #opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"
 To:
  #opts="-fstype=nfs,hard,intr,nodev,nosuid"
  opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"

 Restarted autofs
 Again, nothing is mounted under /projects/
 A `ls /projects/dv (or d0)' returns immediately with output:
ls: cannot access /projects/dv: No such file or directory

And once again .. to test nfs:

  mount -t nfs 192.168.1.42:/projects/dv /nfs/dv
  ls /nfs/dv (Yup... lots of files under here)

I'm not able to see what I am doing wrong...

Re: log to journal only

[Mattia Oss]

On Mon, Jan 09, 2017 at 08:15:37AM -0500, Henning Follmann wrote:
> I wonder if it safe to disable the "old" way of logging. And if so how
> to
> do that.
Done that 2 days ago. No problems so far. I just removed rsyslog. Read:
/usr/share/doc/systemd/README.Debian.gz


Mattia

Re: Bash different behaviour of read / strings in jessie versus stretch (regression?)

[Greg Wooledge]

On Sat, Jan 07, 2017 at 09:54:34PM +0100, foo fighter wrote:
> In jessie "version 1" and "version 2" behave identical. In stretch, "version 
> 2" behaves different (only one item in array)

> echo "===Version 2==="
[...]
> _inputstring="$(echo -e "item01\nitem02\nitem03")"

_inputstring=$'item01\nitem02\nitem03'

> read -ra _array <<<$(echo "$_inputstring") # <<< WITH -"- around string

This is just wrong.  You're using $(echo) which is silly and pointless,
and you've failed to quote the result, and you've failed to tell read
not to stop reading at the first newline, and you've failed to set IFS
to use only newlines as delimiters between array elements.

The only way yours "works" at all is because two of your errors are
canceling each other.  The unquoted $(echo) is doing word splitting
and then reassembling the result, effectively replacing each newline
with a space, so that you only have a single line of input, which is
why read sees the entire input  Yikes.

Really, you should be using mapfile (a.k.a. readarray) when reading
a multi-line input where each line is intended to become one array
element.

_inputstring=$'item01\nitem02\nitem03'
mapfile -t _array <<< "$_inputstring"
declare -p _array

Try that in both versions of bash, and I believe that it will work
consistently and correctly.

Now I get to start guessing.  My first guess is that you are doing
something like this:

tmp=$(some program that writes multiple lines)
read -ra array <<< $(echo "tmp")  # wrong

Just do this instead:

mapfile -t array < <(some program that writes multiple lines)

Re: Failure searching forfile known to exist

[Greg Wooledge]

On Mon, Jan 09, 2017 at 12:23:47AM -0600, Richard Owlett wrote:
> I could not remember where "profiles.ini" was stored.

locate profiles.ini
find ~ -name profiles.ini

Re: Failure searching forfile known to exist

[David Wright]

On Mon 09 Jan 2017 at 00:23:47 (-0600), Richard Owlett wrote:
> Environment: Jessie with Mate DE
> Background: Doing an atypical install of SeaMonkey using the generic
> Linux version.
> 
> I could not remember where "profiles.ini" was stored. As my
> reference information was on another system, it appeared easier to
> use the search function of the file manager.

What file manager?

> I chose "file system" as starting point and entered "profiles.ini"
> in the search bar.
> No success whether logged in as a normal user or as root.
> 
> The file DOES exist.
> the complete path is
> /home/richard/.mozilla/seamonkey/profiles.ini
> 
> A little experimentation demonstrated that the apparent trigger was
> that the target file was in a "hidden" folder.
> As the file manager preferences were set to display hidden files and
> folders, I expected search to actually SEARCH!
> 
> Is this a bug or a "feature"?
> Is there a work-around?

Cheers,
David.

Re: Monitor switched off after resume from hibernation

[David Wright]

On Mon 09 Jan 2017 at 21:47:30 (+0900), Joel Rees wrote:
> On Mon, Jan 9, 2017 at 10:01 AM, David Wright  
> wrote:

> > BTW I haven't bothered to respond to Stefan Monnier's contribution.
> > I can imagine scenarios that might cause power consumption when a
> > machine is off (like network cards running to watch for magic WoL
> > packets, and things like that),
> 
> Cheap power supply designs. I think he indicated.

Indicated what?

> Without load, some power supply designs draw more energy, either in
> not-fully-defined operating modes or in modes where the P/S loads itself
> down dynamically.
> 
> > but a machine in hibernation should
> > cope with a power cut. In any case, I support your expectation that
> > using sleep/hibernate should not involve compromising monitors'
> > power-saving behaviour.

Cheers,
David.

Re: Icedove calendar not syncing to google calendar

[Boyan Penkov]

OK, folks, here's the play:

--close icedove
--uninstall calendar-google-provider
--start icedove
--install the provider via icedove's extensions menu
-- restart icedove
--sign back into my accounts

I then watched icedove start syncing, and then throw the same error after a
few minutes.  Does anybody know what "result=item.recurrenceInfo is null"
means?

I would, by and large, prefer to use Debian's version:
http://social.gl-como.it/display/3e3ce0df3657cf0f075f102119218743

Should I file a bug?

Cheers!

On Sun, Jan 8, 2017 at 11:55 AM, didier gaumet 
wrote:

> Le 08/01/2017 à 15:39, Boyan Penkov a écrit :
> > Super, good point — I am on stretch, and the relevant versions are
> >
> > icedove: 1:45.5.1-1
> > calendar-google-provider: 1:45.5.-1-1
> >
> > Would the extension be more up to date?
>
> no, that is the same version as in Jessie, I think that is version 2.6
> of the extension (last stable is 3.1):
>  https://addons.mozilla.org/en-US/thunderbird/addon/provider-
> for-google-calendar/versions/
>
>


-- 
Boyan Penkov

Re: NTP insecure defaults

[Teemu Likonen]

Mart van de Wege [2017-01-09 08:37:48+01] wrote:

> While I like systemd and its related projects, I have not yet switched
> to systemd-timesyncd.

I switched to systemd-timesyncd yesterday and found it great. It just
works and is simpler than alternatives. Recipe:

  - Remove all other ntp server packages (ntp, chrony...).
  - As root, type "systemctl start systemd-timesyncd.service" to start
the service in the current session.
  - As root, type "timedatectl set-ntp true" to make
systemd-timesyncd.service start automatically in the future. That's
actually very close to "systemctl enable --now
systemd-timesyncd.service" which starts and enables the service.

Monitor your computer's time with "timedatectl" or "journalctl -f -u
systemd-timesyncd.service". Settings are in /etc/systemd/timesyncd.conf.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: log to journal only

[Teemu Likonen]

Henning Follmann [2017-01-09 08:15:37-05] wrote:

> right now the default behavior in stable is to log into /var/log and
> into journal (located under /run/log/journal).
>
> I wonder if it safe to disable the "old" way of logging. And if so how
> to do that.

It's safe, it seems. You can remove rsyslog package but there are some
packages that depend on it. I just disabled rsyslog:

systemctl disable rsyslog.service
systemctl stop rsyslog.service

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: Failure searching for file known to exist

[Richard Owlett]

On 1/9/2017 8:08 AM, David Wright wrote:

On Mon 09 Jan 2017 at 00:23:47 (-0600), Richard Owlett wrote:

Environment: Jessie with Mate DE
Background: Doing an atypical install of SeaMonkey using the generic
Linux version.

I could not remember where "profiles.ini" was stored. As my
reference information was on another system, it appeared easier to
use the search function of the file manager.


What file manager?


Whatever the GUI file manager that is installed when using the 
installer on DVD 1 of 13 and specifying Mate as the desktop.


I now have an additional piece of information and a "possible 
solution" if the phrase is interpreted VERY loosely.


I customarily invoke the file manager by clicking on either the 
Computer icon or that of the Home folder for current user.


I *RARELY* use the drop-down menu under "Applications" for 
anything. The four or five icons need to launch the appropriate 
program. Those icons serve >95% of my needs. The most used icon 
is the one to launch a terminal window.


Today,for the first time ever, I clicked on the "Search for files 
menu entry".

It requires that you specify if you wish to search hidden folders.

Thus I would lean towards classing the problem as a "bug" rather 
than a "feature".






I chose "file system" as starting point and entered "profiles.ini"
in the search bar.
No success whether logged in as a normal user or as root.

The file DOES exist.
the complete path is
/home/richard/.mozilla/seamonkey/profiles.ini

A little experimentation demonstrated that the apparent trigger was
that the target file was in a "hidden" folder.
As the file manager preferences were set to display hidden files and
folders, I expected search to actually SEARCH!

Is this a bug or a "feature"?
Is there a work-around?


Cheers,
David.

Re: Failure searching forfile known to exist

[Richard Owlett]

On 1/9/2017 8:13 AM, Greg Wooledge wrote:

On Mon, Jan 09, 2017 at 12:23:47AM -0600, Richard Owlett wrote:

I could not remember where "profiles.ini" was stored.


locate profiles.ini
find ~ -name profiles.ini



Works like a charm. I basically have a command line outlook but 
have been using Windows since ver. 3.1 . There's a reason I'm 
moving to Linux (Debian in particular ;)


Thanks.

Re: Monitor switched off after resume from hibernation

[solitone]

On Monday, January 9, 2017 9:59:45 PM CET Joel Rees wrote: 
> So, just out of curiosity, what happens if you use ctrl-alt-Fn to
> switch between virtual consoles several times after the box gets stuck
> thinking the screen is off?

I don't have virtual consoles. During installation I could switch between 
different consoles with CTRL-ALT-Fn, but since installation has completed this 
key sequence doesn't produce any result. I haven't bothered to investigate 
this thing yet.

Re: autofs config

[Reco]

Hi.

On Mon, 09 Jan 2017 08:14:51 -0500
Harry Putnam  wrote:

> Reco wrote:
> > Note that it be simplified to:
> >
> > * --fstype=nfs4,rw,soft,intr191.168.1.42:/projects/&
> 
> I created /etc/auto.nfs and tried that forumulation. Restarted
> autofs.  Nothing gets mounted under (now simplified to /projects in
> auto.master) /projects when I do ls /projects/d0 or /projects/dv
> 
> There is a bit of a pause with `ls /projects/dv (or d0) but then I
> get:
>   ls: cannot access /projects/dv: No such file or directory

Won't it be fun otherwise?

The good thing is - autofs is working as intended.
The bad thing is - mount is failing.

Which brings me to this:

1) What security option are you using (i.e. none, sys, krb5, etc)?
If unsure, please mount a share by hand and obtain mount options
from /proc/mounts.

2) If you're using kerberos, can autofs access krb5.conf and
krb5.keytab?

3) Stop autofs, start it like this:

/usr/sbin/automount -fd

Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C.

 
> One question... am I supposed to create the directories
> /projects/dv /projects/d0 ?
> 
> It appears from the instructions I've seen that .. no I am not to
> create those dir... just /projects/.  however, I did try it both ways
> and can report that nothing gets mounted in either test.

No, you definitely do not. Either autofs creates a directory for you, or
you're unable to mount it. Top-level directory *must* be created, but
you did it.

 
> > Also please note that they give you /etc/auto.net just for your case
> > (i.e. mounting nfs).
> 
>  Not sure what you mean by `give you'. Do you mean to use as is?
>  I tried:
>root # grep -v '^#\|^$' /etc/auto.master
>/projects /etc/auto.net   --timeout=180  (Note: It now says `auto.net')
>+dir:/etc/auto.master.d
>+auto.master

Should be something like this:

/projects program:/etc/auto.net --timeout=180


>  Made sure auto.net is chmod 755

Yep, it's importanet.


>  Changed (in auto.net)
>   opts="-fstype=nfs,hard,intr,nodev,nosuid"
>   #opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"
>  To:
>   #opts="-fstype=nfs,hard,intr,nodev,nosuid"
>   opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"

A small nit. Do not use 'hard' mount option unless you absolutely need
it. It is painful, and it's by design. It has nothing to do with your
current problem, though. What you probably need is:

-fstype=nfs4,soft,intr,nodev,nosuid,async

Reco

[SOLVED] Re: kworker eats 45% from first cpu

[deloptes]

deloptes wrote:

> deloptes wrote:
> 
>> Hi community,
>> I moved my system to an SSD two days ago. I applied recommendation to
>> use "discard" when I noticed that one kworker is using exactly 45% of the
>> first cpu.
> 
> 
> perf says
> 
> 
>   55.13%  [kernel]   [k] acpi_os_read_port
>   26.65%  [kernel]   [k] acpi_os_write_port
>8.33%  [kernel]   [k] __next_timer_interrupt
>5.41%  libglib-2.0.so.0.4200.1[.]
> g_io_channel_get_buffer_condition
> 
> 
> ./perf top -a
> 
> so we now know where the cpu power goes - do you have any idea of this?
> 
> regards

Based on these posts

https://bugs.freedesktop.org/show_bug.cgi?id=90014
http://askubuntu.com/questions/176565/why-does-kworker-cpu-usage-get-so-high

I found out gpe4D is causing the problem on my system

# echo disable > /sys/firmware/acpi/interrupts/gpe4D 2>/dev/null

solved the problem

regards

PS: to find out use

# grep . /sys/firmware/acpi/interrupts/gpe*

New version of lcdproc in experimental

[Dominique Dumont]

Hello

After a pause of 2 years, lcdproc [1] project is restarting. lcdproc is a LCD 
display driver useful for Pc based home cinema. It supports quite a lot of LCD 
displays.

Upstream has prepared a release candidate that is now available as a Debian 
package [2] on experimental [3].

Please test this new RC release if you have a LCD display on your system. 

Please report any upstream issue on upstream bug tracker [4]. Packaging issues 
can be reported with Debian BTS as usual.

All the best

[1] http://www.lcdproc.org/
[2] https://packages.qa.debian.org/l/lcdproc.html
[3] https://wiki.debian.org/DebianExperimental
[4] https://github.com/lcdproc/lcdproc/issues

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

Re: Icedove calendar not syncing to google calendar

[didier gaumet]

Le 09/01/2017 à 15:28, Boyan Penkov a écrit :
> OK, folks, here's the play:
> 
> --close icedove
> --uninstall calendar-google-provider
> --start icedove
> --install the provider via icedove's extensions menu
> -- restart icedove
> --sign back into my accounts
> 
> I then watched icedove start syncing, and then throw the same error
> after a few minutes.  Does anybody know what "result=item.recurrenceInfo
> is null" means?
> 
> I would, by and large, prefer to use Debian's version:
> http://social.gl-como.it/display/3e3ce0df3657cf0f075f102119218743
> 
> Should I file a bug?

there are several Mozilla bugs that have been open and marked solved
regarding this error message: I suppose it is in relation to Google
calendars not syncing due to events marked as reccurring but with no
valid information about the reccurrence...
You could probably file a bug report...

Re: New version of lcdproc in experimental

[Brian]

On Mon 09 Jan 2017 at 21:00:17 +0100, Dominique Dumont wrote:

[Snip]

> Please report any upstream issue on upstream bug tracker [4]. Packaging 
> issues 
> can be reported with Debian BTS as usual.

What will happen to a bug report which is clearly an upstream issue and
tagged as such which is sent to the BTS?  Does the BTS deal only with
packaging issues now?

-- 
Brian.

Re: Fresh install gives no graphical login

[Floris]

Op Mon, 09 Jan 2017 05:10:11 +0100 schreef Tama McGlinn  
:



Dear Debian volunteers,

I hope you can help me with a problem I've been experiencing since  
Debian Jessie; After doing a new installation, debian >boots, but only  
presents me with a tty1 login screen, and no graphical session started.  
Here's what I've tried so far:


-Different versions of debian: netinstall vs full CD, with and without  
live, with and without nonfree, amd64 or i386 (it's >an i7 I'm trying to  
install to; I've done lots of googling and found many people asking how  
to tell architecture type, but >no real answers, so I'm going to stick  
with my guess that amd64 is for 64 bit computers, and i386 is for 32 bit  
computers, >and all the rest are for uncommon architectures that I will  
never need.) - that gives 16 possibilities, of which I have >tried about  
half but every option gives the same result.


-Different Methods of putting the iso on the usb stick: using `dd  
if=isofile.iso of=/dev/sdc; sync` (after checking that's >the one with  
gparted or fdisk -l) ; right clicking the isofile and choosing "open  
with disk image writer" and "restoring" to >the usb stick ; using  
mkusb(-dus). I'm doing this because my previous way, using unetbootin,  
is said to be obsolete for the >latest version of debian, and because it  
wasn't working. (the error message led me to the article or question  
where I found >it was obsolete)


-Searching for other people with this problem; just a few results: Tried  
`startx` and `xstart` - programs don't exist. `grep >EE  
/var/log/Xorg.0.log` that file does not exist on the fresh install, it  
does on all my other debian jessie installs which >do work.


-Tried with 2 usb sticks, these have been used in the past to install  
debian jessie to the same computer, (both of them - I >install often) so  
I don't know what is different but it's very unlikely both usb sticks  
have become faulty.


I have a current workaround, which is to dd my current installation onto  
the new harddisk, but I really want to have a clean >install, which  
should go through the installer.


I hope someone here can help me; the documentation is not very clear on  
how to "write the iso to usb" and I suspect that is >what I have done  
incorrectly in this case.


Kind regards,
Tama


If you have an internet connection available in tty1 you can install a  
desktop with:

(as root)
apt-get install tasksel
tasksel --list-tasks
choose your favorite desktop from the list and install it with:
tasksel install -desktop

Floris

Re: How to fix screen resolution ( has been set to 1024 * 768 )

[Floris]

Op Mon, 09 Jan 2017 11:34:23 +0100 schreef manashpal  
:


After installing Debian latest Jessie in my system, I am getting a  
1024*768 screen resolution, but my monitor can render >1366*768. it is  
unlikely to have got such a unexpected screen resolution like 1024*768.  
on the other hand ubuntu, fedora, >kali and many more linux distros has  
never disappoint me such a way. how can I fix it ? kindly let me know  
the steps I will >follow.


thanks.

m@n@sh..p@l


Is it possible to give us some more information? What is your system?
Can you post the output of:
lspci | grep VGA
and
xrandr

Floris

Re: New version of lcdproc in experimental

[Don Armstrong]

On Mon, 09 Jan 2017, Brian wrote:
> On Mon 09 Jan 2017 at 21:00:17 +0100, Dominique Dumont wrote:
> > Please report any upstream issue on upstream bug tracker [4]. Packaging 
> > issues 
> > can be reported with Debian BTS as usual.
> 
> What will happen to a bug report which is clearly an upstream issue and
> tagged as such which is sent to the BTS?  Does the BTS deal only with
> packaging issues now?

The BTS can handle both, but there's no automated process which sends
bugs upstream. So, if you can, file upstream bugs upstream. If not, in
theory someone will take care of filing them upstream for you.

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

unbeingdead isn't beingalive
 -- e.e. cummings "31" _73 Poems_

Re: Failure searching for file known to exist

[David Wright]

On Mon 09 Jan 2017 at 09:29:12 (-0600), Richard Owlett wrote:
> On 1/9/2017 8:08 AM, David Wright wrote:
> >On Mon 09 Jan 2017 at 00:23:47 (-0600), Richard Owlett wrote:
> >>Environment: Jessie with Mate DE
> >>Background: Doing an atypical install of SeaMonkey using the generic
> >>Linux version.
> >>
> >>I could not remember where "profiles.ini" was stored. As my
> >>reference information was on another system, it appeared easier to
> >>use the search function of the file manager.
> >
> >What file manager?
> 
> Whatever the GUI file manager that is installed when using the
> installer on DVD 1 of 13 and specifying Mate as the desktop.

Oh, that one. You should have used the other.

Cheers,
David.

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

[Steffen Dettmer]

Hi,

thank you for your quick reply.

On Mon, Jan 9, 2017 at 1:38 AM, David Wright  wrote:
> On Sun 08 Jan 2017 at 15:56:36 (+0100), Steffen Dettmer wrote:
>> apparently is ignored and "1" is assumed instead, BUT systemd does not
>> call fsck! fsck parsed the line as intended (pass=0 -> no check), so
>> is all fine.
>
> Why would fsck parse /etc/fstab?

Because man page says so? Because fsck's job is to check fs?
Don't know what systemd interferes at all.

> man fstab   in jessie is pretty long in the tooth (from the days of
> lenny) and might have some clarification of how systemd scans it,
> which does seem to differ from sysvinit's approach.

I'm looking at Jessie (Debian 8) man fsck. I found no refernce
to systemd. I think this is some compatiblity feature of systemd.

> How essential it was to read §5.6.1 in jessie's release notes!

Thanks for pointing this. Indeed. So no need to write a bug
report, already documented :)

I remember similar issues long time ago with messages like
"failed to mount the root file system, dropping an emergency
shell" or alike.

> I think they might usefully have added here a recommendation to
> check /etc/fstab thoroughly for non-compliance with the stricter
> behaviour of systemd. I got caught out by systemd's acting upon
> cruft that sysv happily ignored as redundant.

You cannot check everything everytime. Next time systemd
includes a kernel and you need to migrate boot options... SCNR :)

> A bug report would involve an explanation of exactly what you
> think the bug is, without the words "apparently", "probably",
> "assumed", "intended", "do things itself", etc.

I can explain what I see and wait I expect, but not be sure about
the cause. There are so many possible reasons why an error
message could be missing.
Or it is not a bug at all but a feature, to avoid irritating the emergency
shell users with too much technical details. I'm not familiar with
systemd, surely a source of problems. I just used it because I was
told using sysv on Debian 8 or other recent Linuxes caused more
difficulties. I'd rather keep it as simple as possible.

Steffen

Re: Failure searching forfile known to exist

[Lisi Reisz]

On Monday 09 January 2017 15:34:44 Richard Owlett wrote:
> On 1/9/2017 8:13 AM, Greg Wooledge wrote:
> > On Mon, Jan 09, 2017 at 12:23:47AM -0600, Richard Owlett wrote:
> >> I could not remember where "profiles.ini" was stored.
> >
> > locate profiles.ini
> > find ~ -name profiles.ini
>
> Works like a charm. I basically have a command line outlook

But you were using a GUI for a command line function . :-/ 

Lisi

> but 
> have been using Windows since ver. 3.1 . There's a reason I'm
> moving to Linux (Debian in particular ;)
>
> Thanks.

Re: autofs config

[Harry Putnam]

Reco  writes:

[...]

> Won't it be fun otherwise?
>
> The good thing is - autofs is working as intended.
> The bad thing is - mount is failing.

,
| NOTE: I've rearranged your post to put the next question and answer at
| the bottom of this reply
`
  [...] missing q and a
  
>> One question... am I supposed to create the directories
>> /projects/dv /projects/d0 ?
>> 
>> It appears from the instructions I've seen that .. no I am not to
>> create those dir... just /projects/.  however, I did try it both ways
>> and can report that nothing gets mounted in either test.
>
> No, you definitely do not. Either autofs creates a directory for you, or
> you're unable to mount it. Top-level directory *must* be created, but
> you did it.

Well at least I got that part right.

[...]

>>/projects /etc/auto.net   --timeout=180  (Note: It now says 
>> `auto.net')
>>+dir:/etc/auto.master.d
>>+auto.master
>

Reco wrote
> Should be something like this:
>
> /projects program:/etc/auto.net --timeout=180

Ok, commented out the 2 lines that were uncommented by default

[...]

> A small nit. Do not use 'hard' mount option unless you absolutely need
> it. It is painful, and it's by design. It has nothing to do with your
> current problem, though. What you probably need is:
>
> -fstype=nfs4,soft,intr,nodev,nosuid,async
All right, good to know.

---   ---   ---=---   ---   ---

And now the question answer I moved:

Reco Wrote:
> Which brings me to this:
>
> 1) What security option are you using (i.e. none, sys, krb5, etc)?
> If unsure, please mount a share by hand and obtain mount options
> from /proc/mounts.

It appears to be sys (sec=sys)

192.168.1.42:/projects/dv /projects/dv nfs4 rw,relatime,vers=4.0,\
rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,\
timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.29,local_lock=none,\
^^^   
addr=192.168.1.42 0 0

[...]

> 3) Stop autofs, start it like this:
>
> /usr/sbin/automount -fd
>
> Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C.

  (below I marked with *** what might be a clue)
---   ---   ---=---   ---   --- 
parse_init: parse(sun): init gathered global options: (null)
spawn_mount: mtab link detected, passing -n to mount
spawn_umount: mtab link detected, passing -n to mount
mounted indirect on /test with timeout 90, freq 23 seconds
st_ready: st_ready(): state = 0 path /test
handle_packet: type = 3
handle_packet_missing_indirect: token 47, name dv, request pid 11696
attempting to mount entry /test/dv
lookup_mount: lookup(file): looking up dv
lookup_mount: lookup(file): dv -> --fstype=nfs4,rw,soft,intr
191.168.1.42:/test
parse_mount: parse(sun): expanded entry: --fstype=nfs4,rw,soft,intr
191.168.1.42:/test
parse_mount: parse(sun): gathered options: -fstype=nfs4,rw,soft,intr
parse_mount: parse(sun): dequote("191.168.1.42:/test") -> 191.168.1.42:/test
parse_mount: parse(sun): core of entry: options=-fstype=nfs4,rw,soft,intr, 
loc=191.168.1.42:/test
sun_mount: parse(sun): mounting root /test, mountpoint dv, what 
191.168.1.42:/test, fstype nfs, options -fstype=nfs4,rw,soft,intr
mount_mount: mount(nfs): root=/test name=dv what=191.168.1.42:/test, 
fstype=nfs, options=-fstype=nfs4,rw,soft,intr
mount_mount: mount(nfs): nfs options="-fstype=nfs4,rw,soft,intr", nobind=0, 
nosymlink=0, ro=0
get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 6 version 0x30
get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 17 version 0x30

*** mount(nfs): no hosts available

dev_ioctl_send_fail: token = 47
failed to mount /test/dv
handle_packet: type = 3
handle_packet_missing_indirect: token 48, name dv, request pid 11696
dev_ioctl_send_fail: token = 48
st_expire: state 1 path /test
expire_proc: exp_proc = 140662262839040 path /test
expire_cleanup: got thid 140662262839040 path /test stat 0
expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /test
st_expire: state 1 path /test
expire_proc: exp_proc = 140662262839040 path /test
expire_cleanup: got thid 140662262839040 path /test stat 0
expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /test
[...]  
---   ---   ---=---   ---   ---

As I mentioned in the OP:
The host involved is a solaris x86 host.  The file systems set for
nfs availability are not put into an /etc/exports type setup.

The way it is done on solaris with the zfs file system... is during
the creation of a file system with `zfs create'

One usees an option (-o) that looks like:

  zfs create -o sharenfs=on -o sharesmb=on  somezpool/some/path

So in the case above nfs (and smb access) will be turned on.

So maybe that has something to do with the problem...

But then again, maybe not. Because as I have demonstrated, the share
is readily recognized by this Debian host in

no tty active after system migration to second disk

[deloptes]

Hi community,
I recently added a ssd and moved the debian system to it. It might be not
related to this fact but I now do not see the tty login prompt
(CTRL+ALT+F1..F6). I however see it if I boot with sysvinit, so I think it
is something in systemd, but I have no idea how I can debug and fix it. 

Can someone help?

:~# systemctl status console-getty.service
● console-getty.service - Console Getty
   Loaded: loaded (/lib/systemd/system/console-getty.service; disabled)
   Active: inactive (dead)
 Docs: man:agetty(8)


:~# systemctl status getty.target
● getty.target - Login Prompts
   Loaded: loaded (/lib/systemd/system/getty.target; static)
   Active: inactive (dead)
 Docs: man:systemd.special(7)
   man:systemd-getty-generator(8)
   http://0pointer.de/blog/projects/serial-console.html



systemctl restart console-getty

hangs forever

thanks in advance

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

[deloptes]

Steffen Dettmer wrote:

> I'd rather keep it as simple as possible

you can still use sysvinit as init

or follow without-systemd.org

regards

Aw: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?)

[foo fighter]

Hi Greg,
 
thanks for your answer. I used "read" because it offered different delimiter 
(IFS) at the same time as far as my elements are seperateed by LF or (one) 
space (per element). You are right it is stdout of other programs. Furthermore 
globbing was not intended in this area but I did not want to toggle globbing 
off/on  with "set" within the script. As far as mapfile needs LF as delimiter 
(as far as I see) I do now a search and replace (space to LF)

 
mapfile -t _array <<<"${_inputstring// /$'\n'}"
 
This works in both bash versions.
 
Thanks !!
 
Yours
 
Lopiuh

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

[Michael Biebl]

Am 10.01.2017 um 00:43 schrieb deloptes:
> Steffen Dettmer wrote:
> 
>> I'd rather keep it as simple as possible
> 
> you can still use sysvinit as init

The shell scripts used by sysvinit are not simpler. More familiar maybe,
but not simpler.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

netinstall amd64 was unable to find a usable jessie mirror

[Paul Dufresne]

I downloaded netinst AMD 64 bits and made an installation on a laptop today.
I believe it was
http://cdimage.debian.org/debian-cd/8.6.0/amd64/iso-cd/debian-8.6.0-amd64-netinst.iso
I choose 64 bit install (that's for a uefi laptop  [with no more csm]
and that's was about the sixth distro iso I tried)
and that's was the first one to work (except for erfind and gparted).

Anyway, when it came time to choose a mirror, I tried 6 or 7 in Canada
(where I am) and 6 or 7 in
USA, none was working. Ctrl-Alt-F4, did show, a wget ... | grep
^something, then a message that
no valid jessie image was found on the server. I am sorry, it is not very clear.

I finished installation, then added a /etc/source.list for stable with
main contrib non-free, and then was able
after apt-get select, to do a sudo tasksel.

So I got around but still, wanted to share that something seems to go wrong.

Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

[Paul Dufresne]

That's on a laptop I installed Jessie on today.
In XFCE 4 (no reason to believe it is specific to that desktop
interface), when I pressed mute key (F7), indeed the sound
goes off. But afer that, pressing again F7 did not unmute, nor Volume
up or down key.

When I have gone in Mixer application, I saw that Mute was muting Main
and Speaker Channel.
Unmute was unmuting Main channel, but leaving Speaker channel muted.
Manually unmuting Speaker works, giving back the sound.

I looked in Parameters/Keyboard, then look at keyboard settings, but
there was no F7 key (or F8 key for up or down volume).

I have seen that list-acpi, was showing the event... but I don't
really understand where the actions are taken.

I even do have visual feedback when doing volume up or down on the screen.

But somehow would like to fix the unmute, not unmuting speaker channel
and don't know where to look.

Re: netinstall amd64 was unable to find a usable jessie mirror

[Paul Dufresne]

I just checked on the USB key, what disk it really is:
Debian GNU/Linux 8.6.0 "Jessie" - Official Multi-architecture
amd64/i386 NETINST #1 20160917-18:46

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

[Stefan Monnier]

> But somehow would like to fix the unmute, not unmuting speaker channel
> and don't know where to look.

If/when you do find out, please report here: I've had similar problems
on my laptops but could never figure out how those things are expected
to work nor how to change their behavior.


Stefan

Re: Fresh install gives no graphical login

[kamaraju kusumanchi]

On Sun, Jan 8, 2017 at 11:10 PM, Tama McGlinn  wrote:
> Dear Debian volunteers,
>
> I hope you can help me with a problem I've been experiencing since Debian
> Jessie; After doing a new installation, debian boots, but only presents me
> with a tty1 login screen, and no graphical session started.

As root, do the following
apt-get update
apt-get install task-kde-desktop lightdm

This will install the KDE desktop environment. There are many other
desktop environments available in Debian. But for new users, I always
recommend KDE as it has all the bells and whistles that one can think
of. The only downside with KDE is that it will occupy more space and
requires memory to run.

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

breaks unrelated software

[recipe . sim]

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Torquato de Rezende 
To: Debian Bug Tracking System 
Subject: debian-i18n: I'm having problem to correctly apply password w
usb-card
reader blocking
Message-ID: <20170110045120.1415.89103.reportbug@Tasked.localhost>
X-Mailer: reportbug 6.6.3
Date: Tue, 10 Jan 2017 02:51:20 -0200
X-Debbugs-Cc: torquato@Tasked.localhost 

Package: debian-i18n
Severity: critical
Justification: breaks unrelated software 

Dear Maintainer, 

*** Reporter, please consider answering these questions, where
appropriate *** 

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead? 

*** End of the template - remove these template lines ***
1. Debian Lead me to setup cryptographicaly the system with LVM.
2. The password has not entered a clearyfied situation whether 
criptographically has entered the unlock to enter the script.
3. The USB-Card Reader (PCI Internal HUB) Has presented the same
situation in the bios to lock usb peripherals in any port of the
motherboard.
But now it are locking on Debian lucky.
4. I spect only for my life, which considers, what work to understand in
having it working. Debian is functioning outgraded without the device. 

-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686) 

Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

[Jude DaShiell]

Once a speaker is unmuted it may help to check the volume levels on all 
sound devices.  I suspect when mute speaker is done, all volume levels 
also get set to 0, and sink for that speaker has its default value 
erased.


On Mon, 9 Jan 2017, Stefan Monnier wrote:


Date: Mon, 9 Jan 2017 22:42:39
From: Stefan Monnier 
To: debian-user@lists.debian.org
Subject: Re: Mute mutes speaker,
but Unmute does not unmute speaker channel (XFCE4)
Resent-Date: Tue, 10 Jan 2017 03:43:32 + (UTC)
Resent-From: debian-user@lists.debian.org


But somehow would like to fix the unmute, not unmuting speaker channel
and don't know where to look.


If/when you do find out, please report here: I've had similar problems
on my laptops but could never figure out how those things are expected
to work nor how to change their behavior.


   Stefan




--

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

[Stefan Monnier]

> Once a speaker is unmuted it may help to check the volume levels on all
> sound devices.  I suspect when mute speaker is done, all volume levels also
> get set to 0, and sink for that speaker has its default value erased.

You mean, we can/should use alsamixer and friends to fix the mess by hand?
Yes, that's what I do, but I'd really like to better understand who
makes this mess, why, and how I can tell it to stop doing that.

I.e. when I press that mute/unmute button, what is the path followed by
this event through the various layers of event handling, and along this
path, where (in which tool) is it decided which channel to mute or to
unmute (or to change the volume level), based on what configuration
data, and which tool does actually perform this action (in case it's
not the same as the tool which made the decision)?  I suspect there
might also be several tools making and applying those decisions and that
might be part of the problem (at least that has been the case for the
LCD brightness management which has historically been handled at all
kinds of places with various successes at avoiding conflicts between
them).


Stefan


> On Mon, 9 Jan 2017, Stefan Monnier wrote:

>> Date: Mon, 9 Jan 2017 22:42:39
>> From: Stefan Monnier 
>> To: debian-user@lists.debian.org
>> Subject: Re: Mute mutes speaker,
>> but Unmute does not unmute speaker channel (XFCE4)
>> Resent-Date: Tue, 10 Jan 2017 03:43:32 + (UTC)
>> Resent-From: debian-user@lists.debian.org
>> 
>>> But somehow would like to fix the unmute, not unmuting speaker channel
>>> and don't know where to look.
>> 
>> If/when you do find out, please report here: I've had similar problems
>> on my laptops but could never figure out how those things are expected
>> to work nor how to change their behavior.
>> 
>> 
>> Stefan
>> 
>> 

Re: Fresh install gives no graphical login

[Jude DaShiell]

One of the bells and whistles kde hasn't got is anything approaching a 
screen reader that works as well as orca does in gnome/mate.  So for the 
new users out there who have never seen anything in this life kde is a 
no go unless I'm quite wrong about this and in that case I really would 
like to know how to get screen reading up and running on kde and where 
the documentation for it is on the internet.  By screen reading, I do 
not mean the ability to read files exclusively screen reading has speech 
or other accessible output happening all during the interactive session 
in which commands get entered and results from commands get spoken too. 
If anyone with vision could figure out how to get this working and 
document it somewhere on the internet this would close a huge 
accessibility hole for kde.  Best of all would be a kde-accessible 
debian install iso preferably of the firmware variety since that would 
have best chances for actually getting to the internet and completing an 
installation.  With such an iso, kde would get more use in the community 
needing screen readers and accessibility bugs remaining could then get 
reported specific to kde and perhaps squashed in time.


On Mon, 9 Jan 2017, kamaraju kusumanchi wrote:


Date: Mon, 9 Jan 2017 23:58:43
From: kamaraju kusumanchi 
To: "debian-user@lists.debian.org" 
Subject: Re: Fresh install gives no graphical login
Resent-Date: Tue, 10 Jan 2017 04:59:19 + (UTC)
Resent-From: debian-user@lists.debian.org

On Sun, Jan 8, 2017 at 11:10 PM, Tama McGlinn  wrote:

Dear Debian volunteers,

I hope you can help me with a problem I've been experiencing since Debian
Jessie; After doing a new installation, debian boots, but only presents me
with a tty1 login screen, and no graphical session started.


As root, do the following
apt-get update
apt-get install task-kde-desktop lightdm

This will install the KDE desktop environment. There are many other
desktop environments available in Debian. But for new users, I always
recommend KDE as it has all the bells and whistles that one can think
of. The only downside with KDE is that it will occupy more space and
requires memory to run.

hope that helps
raju



--

Re: Mute mutes speaker, but Unmute does not unmute speaker channel (XFCE4)

[Jude DaShiell]

Perhaps you've heard of the freedesktop project?  The only thing that's 
above alsa is pulseaudio.  I had a situation with pulseaudio and 
alsamixer recently I got resolved through some hacking it may be 
instructive to describe here.  I had moved my computer from one room to 
another and for whatever reason the speaker output arbitrarily got moved 
back to the 3.5MM jack rather than a usb port and the usb port had my 
best speakers playing on it.  Adjusting pulseaudio did nothing to 
correct the speaker output.  I had to adjust alsamixer and pulseaudio to 
fix the issue.


On Tue, 10 Jan 2017, Stefan Monnier wrote:


Date: Tue, 10 Jan 2017 00:55:40
From: Stefan Monnier 
To: debian-user@lists.debian.org
Subject: Re: Mute mutes speaker,
but Unmute does not unmute speaker channel (XFCE4)
Resent-Date: Tue, 10 Jan 2017 05:56:09 + (UTC)
Resent-From: debian-user@lists.debian.org


Once a speaker is unmuted it may help to check the volume levels on all
sound devices.  I suspect when mute speaker is done, all volume levels also
get set to 0, and sink for that speaker has its default value erased.


You mean, we can/should use alsamixer and friends to fix the mess by hand?
Yes, that's what I do, but I'd really like to better understand who
makes this mess, why, and how I can tell it to stop doing that.

I.e. when I press that mute/unmute button, what is the path followed by
this event through the various layers of event handling, and along this
path, where (in which tool) is it decided which channel to mute or to
unmute (or to change the volume level), based on what configuration
data, and which tool does actually perform this action (in case it's
not the same as the tool which made the decision)?  I suspect there
might also be several tools making and applying those decisions and that
might be part of the problem (at least that has been the case for the
LCD brightness management which has historically been handled at all
kinds of places with various successes at avoiding conflicts between
them).


   Stefan



On Mon, 9 Jan 2017, Stefan Monnier wrote:



Date: Mon, 9 Jan 2017 22:42:39
From: Stefan Monnier 
To: debian-user@lists.debian.org
Subject: Re: Mute mutes speaker,
but Unmute does not unmute speaker channel (XFCE4)
Resent-Date: Tue, 10 Jan 2017 03:43:32 + (UTC)
Resent-From: debian-user@lists.debian.org


But somehow would like to fix the unmute, not unmuting speaker channel
and don't know where to look.


If/when you do find out, please report here: I've had similar problems
on my laptops but could never figure out how those things are expected
to work nor how to change their behavior.


Stefan








--

kde install accessibility experience

[Jude DaShiell]

Earlier I wrote the kde-accessibility list and asked how to get kde 
accessibility working with kde installed on a system specifically screen 
reading accessibility.  I was advised I would need to install the whole 
orca dependency stack and get orca up and running and from orca then get 
kdespeech started.  I was also told kdespeech would read qt stuff orca 
cannot read but wouldn't do much more beyond that.

I tried it and had an interesting install failure experience.
First going into console and installing orca dependency stack on the kde 
installation that had already got done was no problem.
The problem started on rebootand I got the graphical environment running 
and I know that because espeakup stopped working like it does in the 
console.  So next I start orca up and that worked too and I was thinking 
I'm just about home free here.  Wrong!  What came up talking on the screen 
was I suppose you could call it a dialog to set the system date.  I tried 
several times to set the system date in that calendar dialog and though I 
was able to set the date, I found no control or way to close the calendar 
dialog and go beyond the calendar dialog to get any of kde's accessibility 
up and working.  Since then I have read about some variables that may be 
helpful exporting before I start up the graphical environment on next 
installation try.
Understand, I do my own stuff with computers and do not have sighted 
assistance to help out when I do it let alone someone experienced with kde 
who can see so that's the explanation for this failed kde accessibility 
install experience.




--

Re: Fresh install gives no graphical login

[Felix Miata]

Tama McGlinn composed on 2017-01-09 17:10 (UTC+1300):


I hope you can help me with a problem I've been experiencing since Debian
Jessie; After doing a new installation, debian boots, but only presents me
with a tty1 login screen, and no graphical session started.
That you reached this point means you have a successful installation that is 
simply incomplete for your needs, which means specifically how you are creating 
your installation media hasn't been a material issue.


Depending on which desktop environment you are used to using, you might wish to 
try TDE, which is a mature fork of KDE3, reliable and far less demanding of the 
hardware when KDE5 or other newer DEs like Gnome. Once you can login on any tty 
and have network working you can add whatever is missing, including any of the 
standard Debian DEs/WMs, only of which I ever install, and only rarely use 
(IceWM). My standard Debian installation produces what you see, after which I 
install TDE.


https://wiki.trinitydesktop.org/DebianInstall
 > Here's what I've tried so far:


-Different versions of debian: netinstall vs full CD, with and without
live, with and without nonfree, amd64 or i386 (it's an i7 I'm trying to

> install to;

How old is this target PC? Could it be new enough that a standard Jessie is too 
old to support it? If so, give Stretch a try It's fairly well along the path to 
release.



I've done lots of googling and found many people asking how to
tell architecture type, but no real answers, so I'm going to stick with my
guess that amd64 is for 64 bit computers, and i386 is for 32 bit computers,


As far as you went, correct. More specifically, i386 is for any 32-bit Intel 
"386"-compatible CPU (e.g. Pentium III, Pentium IV, Athlon XP, etc.) while amd64 
is for any 64-bit AMD64-compatible CPU, which includes late Intel Pentium IV, 
Intel Core series, and i3/i5/i7 series like you have.



-Searching for other people with this problem; just a few results: Tried
`startx` and `xstart` - programs don't exist. `grep EE /var/log/Xorg.0.log`
that file does not exist on the fresh install, it does on all my other
debian jessie installs which do work.


Which DE(s) are those other installs running? Mate? Plasma? Gnome? XFCE? Which 
processors are those machines using? Do you know which DE you do want?



I hope someone here can help me; the documentation is not very clear on how
to "write the iso to usb" and I suspect that is what I have done
incorrectly in this case.


Again, I think how you've gone about creating installation media has nothing to 
do with the incomplete installation result you've experienced. More likely this 
is either a case of hardware newer than the Jessie version of Debian supports, 
or a successful minimal installation that simply needs more work to complete, 
either as I suggested above, or as Floris suggested hours ago in thread, by 
using tasksel.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: kde install accessibility experience

[Felix Miata]

What follows is likely no more than tangentially related to the subject line or 
the OP, but might be of use to anyone seriously challenged visually.


I spent about 6 hours today at the home of a previously sighted long-time Linux 
user whose macular degeneration is nearly complete. We have multiboot on his 
machine, primarily openSUSE, which he started using long before I started using 
Linux at all, at least 15 years ago. Right now he has openSUSE 13.1, 13.2 and 
42.1, plus Stretch, all bootable from one Grub menu that I configure manually.


In 13.1 he has KDE3. In 13.2 he has KDE3 and KDE4. In 42.1 and Stretch he has 
TDE, a very mature fork of KDE3. We've never been able to get everything he 
needs to work from any single DE, which is why we have the four installations. 
Up until today, he hasn't put Stretch to use. 13.1 has gone out of support, and 
13.2 is on the out of support doorstep, so 42.1 and/or Stretch need to be doing 
at least as well as the older openSUSE versions did.


Today we got over one big hump. KDE3 and TDE have KTTS (which provides speech in 
conjunction with Festival voices), but it stopped working with the upgrade from 
13.1 to 13.2, and still would not work in 42.1, because Festival got upgraded 
from 2.1.something to 2.4.something[1]. Before today we had KTTS working in 
Stretch, but he wasn't using it because of other things I never got finished 
getting to work in Stretch. Today I got all but one of those other things to 
work in Stretch, so that's what was running when I wore out and came home. The 
hump was proper migration of KMail, which resulted from using TDE's migration 
utility that I hadn't previously known existed, migratekde3.


So, what still does not work is Audible.com. It works fine in Firefox ESR 38 in 
13.1 and 13.2, will not play what matters in 42.1 or Stretch. Its sample media, 
which are tiny sound files embedded in the logged in home page, play just fine 
in both Firefox ESR 45 and Chromium in 42.1 and Stretch, but the books he has 
subscribed and paid for, which live in "the cloud", error in trying to play 
("problem connecting to server. Please click to try again."). Audible tech 
support does not support Linux, even though it previously worked, and works in 
older versions, in Linux. NAICT, the problem is CORS related, but I had to quit 
before making any significant progress trying to figure out if a solution exists.


[1] https://bugzilla.opensuse.org/show_bug.cgi?id=981271
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/