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 multib
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
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
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 whate
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
> 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?
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
F
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@
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.
A
> 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.
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
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 s
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
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 int
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 w
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
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.
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 questio
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 lik
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),
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.
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
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
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 starte
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 se
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 sync
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
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_
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
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 b
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 Wind
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 infor
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 rsy
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
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 anyb
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 r
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
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
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 "ite
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
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
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
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 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
>>
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
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.
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]
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
48 matches
Mail list logo
