I'm running Debian Testing on a Kino-945GSE motherboard which has 2 Realtek
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controllers. Only one of
these is in use.
Kernels newer than Linux tuscan3 4.3.0-1-686-pae #1 SMP Debian 4.3.5-1
(2016-02-06) i686 GNU/Linux suffer from Bug#812746 which
I am running up to date KDE Sid with SDDM but I need to start the gnome
keyring at x startup to satisfy Midori dependencies.
The Midori FAQ suggests adding “export `gnome-keyring-daemon –start`” to
the historical .xinitrc but this seems to be ignored as does .xsession as
suggested by the
Teemu Likonen wrote:
>
> If you want to prevent gpg-agent from starting you can do it with this:
>
> $ systemctl --user mask --now gpg-agent.service gpg-agent.socket \
> gpg-agent-ssh.socket gpg-agent-extra.socket \
> gpg-agent-browser.socket
As I was unsure where the
Reco wrote:
> Hi.
>
> On Fri, 27 Jan 2017 15:40:27 +0000
> Bob Brewer <debian-u...@grantura.co.uk> wrote:
>
>> I'm running up-to-date Debian Sid and since gnupg-agent was upgraded from
>> gnupg-agent:amd64 (2.1.17-3), I have been seeing the following error in
Reco wrote:
> Hi.
>
> On Fri, 27 Jan 2017 15:40:27 +0000
> Bob Brewer <debian-u...@grantura.co.uk> wrote:
>
>> I'm running up-to-date Debian Sid and since gnupg-agent was upgraded from
>> gnupg-agent:amd64 (2.1.17-3), I have been seeing the following error in
I'm running up-to-date Debian Sid and since gnupg-agent was upgraded from
gnupg-agent:amd64 (2.1.17-3), I have been seeing the following error in
syslog:
gpg-agent[7545]: can't connect to the SCdaemon: IPC connect call failed
this is repeated every 2 seconds.
I have tried killing gpg-agent
I am running up-to-date debian sid amd64 and have found that fancontol
sometimes fails to start after a reboot reporting that:
Device path of hwmon0 has changed
Device name of hwmon0 has changed
Configuration appears to be outdated, please run pwmconfig again
On inspecting /etc/fancontrol it
Hi
Some packages failed to upgrade in my lenny to squeeze update because
updare-alternatives encountered a file rather than a symbolic link. An
example of this was fakeroot which produced the error:
update-alternatives: error: readlink(/etc/alternatives/fakeroot)
failed: Invalid argument
The
Tony van der Hoff wrote:
My ISP blocks NNTP traffic. To get round this, I propose to use my
Squeze VPS, which has direct access to the Internet, to collect news
articles from a few selected groups, and access these over SSH (or
something like that).
Can anyone advise me on which package(s)
Camaleón wrote:
Yes, and that sounds even weirder, I mean, that can be launched on a
running system but fails when loading. I've also found another bug
report (which is older than the one you pointed before) that basically
comes to say the same as you:
Calamine wrote:
On Mon, 31 Oct 2011 10:46:55 +, Bob Brewer wrote:
Calamine wrote:
Yes, and that sounds even weirder, I mean, that can be launched on a
running system but fails when loading. I've also found another bug
report (which is older than the one you pointed before
Camaleón wrote:
Nothing has been written to my 'boot' file since last April so I
guess something was changed during a software update since then, I
haven't knowingly turned of boot logging.
(...)
Mmm... are the kernel logs being written okay? Have you a separated /
var partition?
No
Camaleón wrote:
Mmm... then try to direct bootlogd logs to the root partition and see
what happens. This could be done by passing -l argument and I
suppose you will have to tweak the /etc/init.d/bootlogd script file
:-?
I tried adding -l /bootlog to the DAEMON=/sbin/bootlogd line but
Camaleón wrote:
It works here but I edited this line:
BOOTLOGD_OPTS=-r -c -l /bootlog
I've now changed mine to be the same as yours
After restarting the system the file is indeed placed at the /
instead /var/log/boot.
If I now run /etc/init.d/bootlogd start It does indeed write an
On my up-to-date sid distro, my /var/log/boot hasn't been updated since
13 April 2011 (BOOTLOGD_ENABLE is set to Yes in /etc/default/bootlogd).
This looks to be the same as Bug 624289 which was raised against the
sysvinit-utils package but perhaps should have been raised against the
Camaleón wrote:
On my up-to-date sid distro, my /var/log/boot hasn't been updated
since 13 April 2011 (BOOTLOGD_ENABLE is set to Yes in
/etc/default/bootlogd).
This looks to be the same as Bug 624289 which was raised against the
sysvinit-utils package but perhaps should have been raised
Marc Shapiro wrote:
Marc Shapiro mshapiro...@yahoo.com wrote:
Now, my problem is with connecting and that is probably a
configuration problem, but...
My wireless network shows up in wicd and I
select it and click on Connect. Wicd connects and authenticates,
then it
tries to
Paul Scott wrote:
How you create a Preshared Key?
I used https://www.grc.com/passwords.htm
Bob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi
Is there a reason why the 'Scroll Lock' key on my up to date SID / KDE4 box
is inoperative.
If I run xmodmap -e 'add mod3 = Scroll_Lock' I can re-enable it, but I
don't want to compromise any functions that may need 'Scroll Lock' disabled.
Bob
--
To UNSUBSCRIBE, email to
19 matches
Mail list logo
