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
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
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
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
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
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
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
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
> 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
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
Le Mon, 9 Jan 2017 12:15:29 +0100,
Jean-Michel OLTRA a écrit :
> Même noyau chez moi (testing), mais je ne peux lire dmesg en
> utilisateur.
Ça dépend peut-être si l'utilisateur est membre de adm ? une idée comme
ça, vu qu'il y a un groupe staff qui permet
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
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
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
Ce message ne c'est affiché qu'une fois, quand j'étais en wifi et que
j'ai ajouté le cable rj45 puis coupé la wifi.
Depuis, la connexion rj45 semble fonctionner avec quelques une des
manipulations indiquées sur le lien.
[Résolu]
> Salut,
>
> Tu dis
>
> Résolution du problème
>
>
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
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
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
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.
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
Witam.
Od 3 marca, piatek do 5 marca, niedziela odbedzie sie Zimowisko
Linuxowe Trojmiejskiej Grupy Uzytkownikow Linuxa Puck-2017.
Witryna pod http://zimowisko.linux.gda.pl
Miejsce. Powiatowe Centrum Kształcenia Zawodowego i Ustawicznego w Pucku.
ul. Kolejowa 7.
--
Cytuje wybrany
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
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
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
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]
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
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
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
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
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
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
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
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,
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
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
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
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
On lundi 9 janvier 2017 13:20:42 CET Nicolas FRANCOIS wrote:
> Le Mon, 09 Jan 2017 13:14:44 +0100,
>
> Klaus Becker a écrit :
> > Salut,
> >
> > # dpkg -i --force-overwrite /var/cache/apt/archives/vlc-bin_1%3a2.2.4-
> > dmo1~bpo8+5_amd64.deb
> >
> > Klaus
>
> Cool,
Le Mon, 09 Jan 2017 13:14:44 +0100,
Klaus Becker a écrit :
> Salut,
>
> # dpkg -i --force-overwrite /var/cache/apt/archives/vlc-bin_1%3a2.2.4-
> dmo1~bpo8+5_amd64.deb
>
> Klaus
Cool, impeccable, ça a marché.
Merci beaucoup. Et quelle réactivité :-)
Il faut que je lise ce
Isso é algo na interface gráfica.Geralmente há um arquivo .config no home do
seu usuário.Movendo esse .config, sua interface será resetada (e todas as
demais configurações, como thunderbird, por exemplo)O KDE, por exemplo, tem um
diretório a parte chamado .kde ou .kde4. Removendo ele reseta
On lundi 9 janvier 2017 13:09:17 CET Nicolas FRANCOIS wrote:
> Bonjour.
>
> Lors d'une mise à jour de mon système (Debian Jessie avec backports),
> je rencontre l'erreur suivante provenant de la mise à jour de vlc, et
> je ne sais pas comment y remédier. J'ai essayé de désinstaller puis de
>
Bonjour.
Lors d'une mise à jour de mon système (Debian Jessie avec backports),
je rencontre l'erreur suivante provenant de la mise à jour de vlc, et
je ne sais pas comment y remédier. J'ai essayé de désinstaller puis de
réinstaller vlc, mais rien n'y fait (et ça casse tout plein de
Bonjour,
dmesg fonctionne chez moi en user, sous Jessie updaté.
Cependant, je lis ce message concernant ma carte graphique Nvidia :
===
nvidia :04:00.0: irq 45 for MSI/MSI-X
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the
Bonjour,
Le lundi 09 janvier 2017, Klaus Becker a écrit...
> Si, 4.8.0-2-amd64
Même noyau chez moi (testing), mais je ne peux lire dmesg en utilisateur.
--
jm
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
Le 09-01-2017, à 11:16:38 +0100, Klaus Becker a écrit :
Vous ne tournez probablement pas sous un noyau 4.8.
Si, 4.8.0-2-amd64
Bizarre alors. Dans le changelog, on peut lire:
* security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root
users reading the kernel log by default
On lundi 9 janvier 2017 11:07:42 CET steve wrote:
> Le 09-01-2017, à 10:53:35 +0100, Klaus Becker a écrit :
> >> Bonjour,
> >> je viens d'essayer en user : aucun problème...
> >> amicalement
> >> Erwin
> >
> >moi itou
>
> Vous ne tournez probablement pas sous un noyau 4.8.
Si, 4.8.0-2-amd64
Le 09-01-2017, à 10:53:35 +0100, Klaus Becker a écrit :
Bonjour,
je viens d'essayer en user : aucun problème...
amicalement
Erwin
moi itou
Vous ne tournez probablement pas sous un noyau 4.8.
On lundi 9 janvier 2017 10:38:54 CET erwin wrote:
> Le Mon, 9 Jan 2017 10:29:35 +0100
>
> "C. Mourad Jaber" écrivait:
> > Bonjour,
> >
> > Une évolution de debian a changé les droits sur le "tampon du noyau".
> > Maintenant, il me semble que seul de root peut exécuter la
Le Mon, 9 Jan 2017 10:29:35 +0100
"C. Mourad Jaber" écrivait:
> Bonjour,
>
> Une évolution de debian a changé les droits sur le "tampon du noyau".
> Maintenant, il me semble que seul de root peut exécuter la commande dmesg
> avec succès...
> En user, j'ai le message
Salut,
https://lepouf.info/lire-le-dmesg-en-user/ répond à ta question.
Bonjour,
Une évolution de debian a changé les droits sur le "tampon du noyau".
Maintenant, il me semble que seul de root peut exécuter la commande dmesg avec
succès...
En user, j'ai le message suivant :
$ dmesg
dmesg: échec de lecture du tampon de noyau: Opération non permise
Est-il
Enviado desde mi iPhone
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
66 matches
Mail list logo