Re: Re: USB wireless keyboard in stretch

[Alle Meije Wink]

Hi Zoltan,

Thanks for all your suggestions

I looked at the .xcfe logs but they did not mention the keyboard or mouse.
Also, xfce4-goodies was already installed

Touching wood it seems the problem is fixed now.
Following

http://tutorialforlinux.com/2017/01/18/how-to-switch-from-gnomegnome3-to-xfce-desktop-on-debian-8-jessie
I set up XFCE with the slim display manager.
That made the keyboard and mouse work again -- I think something had gone
wrong in the lightdm configuration.
After that I removed and re-installed lightdm and can now start that again
with mouse and keyboard as well.

Not sure what was wrong which is a bit of a shame.
Good to have it working again though...

RE: USB wireless keyboard in stretch

[Alle Meije Wink]

Zoltán Herman  wrote:
>> Check the contents of grub conf,
>> what is the difference to the recovery case!?

Hi, thanks for your reply (the first helpful one)

If I go to recovery mode, I can type to go to maintenance.
But even then if I continue booting (using ctrl-d) the XFCE
desktop session that I get has no keyboard/mouse either.

So it does not seem to be a kernel parameter, rather the
wireless keyboard not getting through to lightDM/XFCE?

BTW I mailed bluetooth, but it turns out to be a universal USB receiver
with WiFI

Many thanks

USB wireless keyboard in stretch

[Alle Meije Wink]

After upgrading from Jessie to Stretch, my wireless Logitech keyboard (with
USB bluetooth receiver) has stopped working in a normal login.

First it did not even work in the grub menu, but after a session with a
normal USB keyboard the wireless one is picked up there again.

And then in recovery mode the wireless keyboard works too. First it says

[ sec.microsec]
hidraw: raw HID events driver (C) Jiri Kosina

and finds the usbcore and usbhid drivers. Then it correctly identifies the
the keyboard as Logitech K400, finding various inputs and components.

Then, when I start typing at

Give root password for maintenance
(or type Control-D to continue)

it says

[ sec.microsec] logitech-hidpp-device 0003:0460:4024:0006: HID++ device
connected.

If I type the root password I can keep typing and (after starting dhclient)
do normal command line things.

But if I type Control-D -or if I had not used recovery mode in the first
place- then I go to an X session (xfce4 on lightdm) and have no keyboard
control, neither with the wireless K400 or the old fashioned one (not super
familiar with xfce4 key bindings so the mouse pad on the wireless keyboard
is handy!)

Does anyone understand the cause of this problem & how to fix it? Thanks!

Re: X problems in Stretch with AMD APU?

[Alle Meije Wink]

I'm running 4.11

Got a bit further by removing the MESA libraries for GLX support. That
removed many graphics applications and libraries. Then added
xserver-xorg-core again and now X starts again.

Some work to do because my (wireless USB) keyboard is not recognised in the
x session but that should be doable. So it looks like it's OK again but not
sure what the crucial step was...

On 20 Aug 2017 00:54, "Zoltán Herman"  wrote:

> And what kind of kernel is installed 4.9 or 4.11?
> Check the kernel log to see if the firmware has been loaded.
>
> >>
> I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but
> still plays everything fine. The drivers supplied by the Jessie
> repositories (including fglrx for hardware acceleration) worked fine.
>
> But then I upgraded to Stretch and suddenly started without X. The debian
> supplied drivers don't seem to support the A6 any more?
>
> I got everything working again 3 weeks ago by installing the proprietary
> drivers (catalyst 15.9). But now X has gone again and the same catalyst
> package refuses to install.
>
> The error message that the installer gives is that the X version is too
> low for catalyst?
>
> Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
> now start X it says 'no screens found'..
>
> Is there a way to get the AMD APUs off that generation working in Stretch
> working again?
>
> Or to at least start X again (with a very low resolution, assuming basic
> hardware)?
> <<
> Add non-free to sources.list
> update
> install firmware-amd-graphics
> etc.
> <<.
>

X problems in Stretch with AMD APU?

[Alle Meije Wink]

I have a home theatre PC with an AMD A6-3500 APU. Bit of an oldie but still
plays everything fine. The drivers supplied by the Jessie repositories
(including fglrx for hardware acceleration) worked fine.

But then I upgraded to Stretch and suddenly started without X. The debian
supplied drivers don't seem to support the A6 any more?

I got everything working again 3 weeks ago by installing the proprietary
drivers (catalyst 15.9). But now X has gone again and the same catalyst
package refuses to install.

The error message that the installer gives is that the X version is too low
for catalyst?

Then I removed (--purge) xserver-xorg-core and reinstalled it. But when I
now start X it says 'no screens found'..

Is there a way to get the AMD APUs off that generation working in Stretch
working again?

Or to at least start X again (with a very low resolution, assuming basic
hardware)?

what's with the discussions about non-debian-related issues

[Alle Meije Wink]

In the last month more than half of the messages on this list are crackpot 
theories about WW2. 

Very childish. Can they perhaps be automatically deleted? Surely there are 
better places to discuss them.

Re: X hangs due to 'render ring' issue after suspend/closed lid

[Alle Meije Wink]

>
> Date: Thu, 31 Mar 2016 21:36:31 +0200
> From: Sven Arvidsson <s...@whiz.se>
>
> On Tue, 2016-03-29 at 19:54 +0100, Alle Meije Wink wrote:
> > I am running Jessie on a toshiba laptop with these specs
> > Hardware: i7 5500u
> > Graphics: Intel HD graphics 5500
> > Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
> x86_64 GNU/Linux
> >
> > I had to turn of power saving options (the screen can still be blanked
> > after a few minutes but hibernate etc is out of the question) because
> > after waking up from s suspended session/hibernation, the keyboard and
> > mouse are completely unresponsive. The screen is partly restored (some
> windows
> > are semi-transparent for effect) and I cannot go to single-user mode via
> > key presses either.
>
> The very short answer is that new hardware tends to require new software.
>
That makes sense - although I thought that this card had been around for a
while.
I looked at this question before posting here
http://unix.stackexchange.com/questions/207855 (from June last year)
Followed all the leads there but my drivers were already as recent as that.

Try upgrading to new kernel/Xorg driver/mesa. (You might want to try out
> using a live cd/usb first).
>
I did try kernel 4 (via backports) but that broke other things, and it did
not fix the problem.


> You might also need new microcode updates, I'm not sure if they are pushed
> for the updates for jessie.
>
Don that now, by using apt-get install intel-microcode


> The same thing goes for bug reports, if you can't reproduce the problem
> with the latest software they tend to not be very interested.
>
What same thing? I'm just trying to figure out what causes this hanging /
if anyone knows a solution.
It may not be a bug -- if I can solve it by using backports, switching to
testing or installing proprietary drivers then I'm more than happy to give
it a go :)

bw Alle Meije

X hangs due to 'render ring' issue after suspend/closed lid

[Alle Meije Wink]

I am running Jessie on a toshiba laptop with these specs

Hardware: i7 5500u
Graphics: Intel HD graphics 5500
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29)
x86_64 GNU/Linux

I had to turn of power saving options (the screen can still be blanked
after a few minutes but hibernate etc is out of the question) because after
waking up from s suspended session/hibernation, the keyboard and mouse are
completely unresponsive. The screen is partly restored (some windows are
semi-transparent for effect) and I cannot go to single-user mode via key
presses either.

Posted this on debian-laptop a while ago
https://lists.debian.org/debian-laptop/2016/01/msg00027.html but that does
not appear to be a very active list. Besides, The one suggestion that was
very kindly offered involved using the keyboard, so I'm still stuck.

The problem seems to be with the Intel graphics driver. I filed a bug
report about what happens when I suspend - resume at bugzilla.org
https://bugs.freedesktop.org/show_bug.cgi?id=93868 but not sure whether
this bug is now considered solved, active or left to its own devices?

After a reboot there is nothing for me to do but hold down the power button
for 3s. After that I check the old log file (Xorg.0.log.old) and this seems
to be the offending section:

[drm] stuck on render ring
[drm] GPU HANG: ecode 0:0x00dff888, in Xorg [751], reason: Ring hung,
action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against
DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please
always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

The post to BugZilla also includes a -GZipped- file
/sys/class/drm/card0/error from right after the fact whose first 13 lines
are:

GPU HANG: ecode 0:0x00dff888, in Xorg [751], reason: Ring hung, action:
reset
Time: 1453805023 s 872139 us
Kernel: 3.16.0-4-amd64
Active process (on ring render): Xorg [751]
Reset count: 0
Suspend count: 1
PCI ID: 0x1616
EIR: 0x
IER: 0x
PGTBL_ER: 0x
FORCEWAKE: 0x00010001
DERRMR: 0x2070ef2f
CCID: 0x028f510d

... and the total no. of lines is 151,075. None of which make sense to me...

One solution offered in BugZilla (
https://bugs.freedesktop.org/show_bug.cgi?id=91152) that lies within my
linux knowledge I tried: adding the option
 intel_iommu=igfx_off
to the boot parameters in grub.cfg.

Unfortunately that makes no difference in my case. If I close the lid and
open it again after everything's gone quiet - nothing

Does anyone in this group know of a working and
understandable-by-limited-time-enthusiast solution?
As said I have all the power-saving options off, but if the lid is closed
it still continues to hang.

Many thanks, happy to send more details.

belkin wireless PCI card

[Alle Meije Wink]

Hi,

Since my computer moved inside my house, I rely on a Belkin G+ 802.11g 
Network card (that's all it says on the box).


Used as I am to debian just starting DHCP without a problem, I didn't 
know what to do when the network did not appear.


Is this easy to add to my existing configuration? I'm hopeful because 
when I installed Ubuntu (sort-of Debian) on an old 486-based laptop the 
other day, wireless worked out of the box.


No idea where to start though?

Does anyone know a how-to, or just a program/script to make this work?

MAny thanks
Alle Meije Wink


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

apt-get update on ftp.uk.debian.org

[Alle Meije Wink]

/contrib Packages
  Could not connect data socket, connection timed out
Get: 20 ftp://ftp.uk.debian.org stable/main Sources [1977kB]
Err ftp://ftp.uk.debian.org stable/main Sources
  Could not connect data socket, connection timed out
Get: 21 ftp://ftp.uk.debian.org stable/non-free Sources [39.3kB]
Err ftp://ftp.uk.debian.org stable/non-free Sources
  Could not connect data socket, connection timed out
Get: 22 ftp://ftp.uk.debian.org stable/contrib Sources [34.0kB]
Err ftp://ftp.uk.debian.org stable/contrib Sources
  Could not connect data socket, connection timed out
Fetched 1302B in 34m0s (1B/s)
Failed to fetch ftp://ftp.uk.debian.org/debian/dists/stable/Release.gpg 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/main/i18n/Translation-en_GB.bz2 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/non-free/i18n/Translation-en_GB.bz2 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/contrib/i18n/Translation-en_GB.bz2 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/main/binary-i386/Packages.gz 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/non-free/binary-i386/Packages.gz 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/contrib/binary-i386/Packages.gz 
 Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/main/source/Sources.gz 
Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/non-free/source/Sources.gz 
Could not connect data socket, connection timed out
Failed to fetch 
ftp://ftp.uk.debian.org/debian/dists/stable/contrib/source/Sources.gz 
Could not connect data socket, connection timed out

Reading package lists... Done
E: Some index files failed to download, they have been ignored, or old 
ones used instead.


This seems to be a problemwith the uk mirror: when I use ftp.debian.org 
or ftp.nl.debian.org, everything goes fine.


I tried all the suggestions in the mails about this:
 o installing install
 o installing gpgv
 o rm /var/lib/apt/lists/partial/*
but with the uk mirror it just doesn't seem to work...

I'm not sure why it would have anything to do with Translation-en_GB 
(that is not even installed!!!) but this package keeps popping up...


Anyone got a clue? Is it a partial install still sitting around somewhere?

Thanks
Alle Meije Wink



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: when will nvidai-glx and nvidia-kernel-source hit etch?

[Alle Meije Wink]

Apologies if this question has already been answered, but I have not 
been able yet to get ANY version of nvidia-glx back on my system!


I run a mix of testing and experimental (?), see my sources.list below. 
The nvidia driver files should come straight from their Maker..


My kernel is 2.6.18, and my X server is Xorg.

I have read some hints of changing to unstable to get nvidia-glx, but 
have never been able to replicate any one of those excercises...


When I run
apt-get install nvidia-glx
it keeps giving messages like
nvidia-glx depends on xserver-common

so I guess that is still a problem XFree86/Xorg?

The rest of the nvidia packages install well, by the way. It is just 
nvidia-glx whose access is completely denied by apt/xorg or a 
combination of the two...


There are loads of web pages on this, but none of the solutions there 
seems to work for everyone?


Thanks
Alle Meije

sources.list:

# general # TESTING
# UK
deb ftp://ftp.uk.debian.org/debian/ testing main contrib non-free
# if UK is down - NL?
# deb ftp://ftp.nl.debian.org/debian/ unstable main contrib non-free

# nvidia driver: see http://people.debian.org/~rdonald/index.php
# use this source line for unstable drivers
deb http://people.debian.org/~rdonald/nvidia unstable
 nvidia-graphics-drivers
deb http://people.debian.org/~rdonald/nvidia unstable
 nvidia-kernel-common
deb http://people.debian.org/~rdonald/nvidia unstable nvidia-settings 
deb http://people.debian.org/~rdonald/nvidia unstable nvidia-xconfig

deb http://people.debian.org/~rdonald/nvidia unstable modules

# mplayer # see http://www.debian-multimedia.org/
deb http://www.debian-multimedia.org etch main

# root dirs that may contain packages
# deb file:/root/ debs/


Subject: Re: when will nvidai-glx and nvidia-kernel-source hit etch? 
From: Florian Kulzer [EMAIL PROTECTED] Date: Thu, 9 Nov

2006 12:26:22 +0100 To: debian-user@lists.debian.org
To: debian-user@lists.debian.org

On Thu, Nov 09, 2006 at 10:38:23 +0100, Lubos Vrbka wrote:

Florian Kulzer wrote:

Now I am confused:

me too...


$ apt-file search nvidia_drv nvidia-glx:
usr/X11R6/lib/modules/drivers/nvidia_drv.o nvidia-glx:
usr/lib/xorg/modules/drivers/nvidia_drv.o nvidia-glx-legacy:
usr/lib/xorg/modules/drivers/nvidia_drv.o

i get empty output from apt-file.


Maybe the .so file comes from an older version of nvidia-glx.
What is the result of dpkg -S nvidia_drv?

nvidia-glx: /usr/lib/xorg/modules/drivers/nvidia_drv.so

btw, dpkg -l nvidia-glx gives me 1.0.9625-2 NVIDIA binary XFree86
4.x driver


That is the driver from Experimental. (Maybe you mentioned that
before and I did not notice.) I have never tried that one myself so
there might be some 9xxx-specific issue that I don't know anything
about.

OK, indeed the name is .so:

$ aptitude download nvidia-glx/experimental $ dpkg-deb --contents
nvidia-glx_1.0.9625-2_i386.deb | grep nvidia_drv -rw-r--r-- root/root
1064588 2006-10-20 19:55 ./usr/lib/xorg/modules/drivers/nvidia_drv.so


The only thing I know for sure from when I switched from the
nvidia installer to the Debian packages is that the .so and the
.o module do not play nicely together (at least if the .so file
comes from the nvidia installer).

strange... there is really no .o file in xorg/modules/drivers/


It seems that there is a bug in apt-file: I have Experimental in my 
sources.list and yet apt-file search did not tell me about the 
nvidia_drv.so file, and in your case it comes up empty. Anyway, that 
means my previous statements do not apply to your situation at all. I

 am sorry for adding to the confusion.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nividia-glx working in etch???

[Alle Meije Wink]

Hi all,

I read this in an earlier post about etch


Here's what I do.

~apt-get install module-assistant nvidia-kernel-source
~m-a prepare (sudo or root)
~m-a a-i nvidia (sudo or root)
~dpkg -i /usr/src/nvidia-kernel-moduleX.deb (sudo or root)
~apt-get install nvidia-glx (sudo or root)

Restart X.



I think this is exactly what I do on Etch, and it works fine.


I can confirm only the first 4 lines... I have been running the nv 
driver in etch no for so long that my eyes are sore even when I think 
about running debian...


I try every now and then if I can install nvidia-glx (trusting the 
nvidia-kernel package not to be te problem) and what I get is still this:


The following packages have unmet dependencies:
  nvidia-glx: Depends: xserver-common (= 4.0.3) but it is not installable
E: Broken packages

I have all of Randall Donalds' package directories in my sources.list, 
so the material comes hot off the press...


I guess this has to do with using Xorg instead of Xfree86, but surely 
there must be a way around this?


I tried some archive/web searches but there does not yet seem to be a 
solution for the etch drivers?


bw,
Alle Meije






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nividia-glx working in etch???

[Alle Meije Wink]

From: Sridhar M.A. [EMAIL PROTECTED]
Date: Wed, 25 Oct 2006 18:24:02 +0530
To: debian-user@lists.debian.org

On Wed, Oct 25, 2006 at 10:35:55AM +0200, Florian Kulzer wrote:
 
I think that people on Etch either install the nvidia-* packages from

Unstable or they use the installer script from the nvidia homepage. (I
can only confirm that both these methods work fine on Sid since I am not
an Etch user myself.)


Hang on, does this only hold for testing? The lines in my 
/etc/apt/sources.list are all for unstable:


..
# nvidia driver: see http://people.debian.org/~rdonald/index.php
# use this source line for unstable drivers
deb http://people.debian.org/~rdonald/nvidia unstable 
nvidia-graphics-drivers

deb http://people.debian.org/~rdonald/nvidia unstable nvidia-kernel-common
deb http://people.debian.org/~rdonald/nvidia unstable nvidia-settings
deb http://people.debian.org/~rdonald/nvidia unstable nvidia-xconfig
deb http://people.debian.org/~rdonald/nvidia unstable modules
..

In that case all should work well?? Or is there something with my X 
server not in order? The KDE control centre says: version 70,000,000??


However it *is* nvidia-glx demanding xserver-common (= 4.0.3).

..does not compute..


Just want to mention that I was using sarge till 10 days back and was
using nvidia drivers obtained directly. They were working well with
both X and Xorg from backports. I have now upgraded to etch, and
everything still works well. 


Generally, I have found it easier to install the driver directly rather
than the deb packages.


Yeah, I think I might just start using that again. Too bad, I kind of 
liked the debian packages (with A.Schulman's installation recipe).


I started using Xorg in sarge/sid. Never a problem. Etch is definitely 
trickier (though I don't know unstable [see above] qualifies as etch)


Thanks,
Alle Meije


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Still fontconfig (and Xorg and Defoma, ...)?

[Alle Meije Wink]

On Mon, Oct 16, 2006 at 22:36:42 +0100, Alle Meije Wink wrote:
I am running etch at the moment, with Xorg as my X server. During an 
apt-get update last week or so, openoffice-org and ttf-opensymbol were 
upgraded. Things started going wrong when it came to installing 
openoffice-org, which was unconfigured and that was a problem. Not that 
I had had a chance to run it... Could not really figure out what the 
problem was. After that, during the configuration of ttf-opensymbol, 
these error messages showed up:

 Setting up ttf-opensymbol (2.0.4~rc3-1) ...
Updating fontconfig cache...
/usr/share/fonts: failed to write cache
/usr/share/fonts/X11: failed to write cache
   

[...]

In other words: either 0 fonts, n dirs; or m fonts, 0 dirs for all fonts 
that fc-cache tries.


I get the same type of message for all my font directories when I run
fc-cache -v, but don't get the failed to write cache error.


What are the permissions of /var/cache/fontconfig?


They are fine (although the dir is empty). I'm not sure where fontconfig 
wants to write the cache?



$ ls -ld /var/cache/fontconfig/
drwxr-xr-x 2 root root 4096 2006-10-16 09:43 /var/cache/fontconfig/
$ lsattr -d /var/cache/fontconfig/
-- /var/cache/fontconfig/

Does this directory contain any files with names like
long hex string-x86.cache-2? If yes, do these files have reasonable
timestamps (i.e. not in the future)?

Can you do things like touch /var/cache/fontconfig/testfile as root?


no problem...

[EMAIL PROTECTED]:~$ ls -ld /var/cache/fontconfig/
drwxr-xr-x 2 root root 4096 Oct 18 01:51 /var/cache/fontconfig//
[EMAIL PROTECTED]:~$ lsattr -d /var/cache/fontconfig/
- /var/cache/fontconfig/

... exactly the same
(except that it is empty)

A long string of errors seem to come from defoma. I tried 
dpkg-reconfigure defoma (as well as fontconfig) but that gives me the 
same list of errors.


When I remove defoma and/or fontconfig, most of my X programs will be 
removed (KDE, firefox, etc). If it removes the problem though, would 
that be worth a try?


Many thanks for any suggestions.

Is nobody else having these problems? I cannot remember ever installing 
weird font things (except upgrading OpenOffice)


Alle Meije




Send instant messages to your online friends http://uk.messenger.yahoo.com 



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: debian-user-digest Digest V2006 #2204

[Alle Meije Wink]

Hi Florian and others,

Thanks for you suggestions!

On Thu, Oct 12, 2006 at 07:55:48 +0100, Alle Meije Wink wrote:
  

These three, and maybe Xorg, seem to not like each other...

I am running etch at the moment, with Xorg as my X server. During an 
apt-get update last week or so, openoffice-org and ttf-opensymbol were 
upgraded. Things started going wrong when it came to installing 
openoffice-org, which was unconfigured and that was a problem. Not that 
I had had a chance to run it... Could not really figure out what the 
problem was. After that, during the configuration of ttf-opensymbol, 
these error messages showed up:


Setting up ttf-opensymbol (2.0.4~rc3-1) ...
Updating fontconfig cache...
/usr/share/fonts: failed to write cache
/usr/share/fonts/X11: failed to write cache



[ snip: the same message for the other font directories ]
  
I could reproduce these messages by running fc-cache. No idea where the 
cache is that needs to be written but can't. I tried to change 
permissions in /var and /etch but that didn't help. The final message of 
apt-get was:


Errors were encountered while processing:
ttf-opensymbol
openoffice.org-core
python-uno
openoffice.org-writer
openoffice.org-help-en-gb

and every time I run apt-get update, it tries again to configure 
ttf-opensymbols/fontconfig (and fails)



Try to run

fc-cache -v

as root. That way it should list which directories it is trying to
access. That might give us a clue what is wrong.
  

This is what `sudo fc-cache -v  fccache.txt` gives me:

/usr/share/fonts: /usr/share/fonts: failed to write cache
caching, 0 fonts, 4 dirs
/usr/share/fonts/X11: /usr/share/fonts/X11: failed to write cache
caching, 0 fonts, 6 dirs
/usr/share/fonts/X11/100dpi: /usr/share/fonts/X11/100dpi: failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/X11/75dpi: /usr/share/fonts/X11/75dpi: failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/X11/Type1: /usr/share/fonts/X11/Type1: failed to write cache
caching, 43 fonts, 0 dirs
/usr/share/fonts/X11/encodings: /usr/share/fonts/X11/encodings: failed to write 
cache
caching, 0 fonts, 1 dirs
/usr/share/fonts/X11/encodings/large: /usr/share/fonts/X11/encodings/large: 
failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/X11/misc: /usr/share/fonts/X11/misc: failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/X11/util: /usr/share/fonts/X11/util: failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/afms: /usr/share/fonts/afms: failed to write cache
caching, 0 fonts, 1 dirs
/usr/share/fonts/afms/adobe: /usr/share/fonts/afms/adobe: failed to write cache
caching, 0 fonts, 0 dirs
/usr/share/fonts/truetype: /usr/share/fonts/truetype: failed to write cache
caching, 45 fonts, 4 dirs
/usr/share/fonts/truetype/freefont: /usr/share/fonts/truetype/freefont: failed 
to write cache
caching, 12 fonts, 0 dirs
/usr/share/fonts/truetype/latex-xft-fonts: 
/usr/share/fonts/truetype/latex-xft-fonts: failed to write cache
caching, 7 fonts, 0 dirs
/usr/share/fonts/truetype/msttcorefonts: 
/usr/share/fonts/truetype/msttcorefonts: failed to write cache
caching, 60 fonts, 0 dirs
/usr/share/fonts/truetype/ttf-bitstream-vera: 
/usr/share/fonts/truetype/ttf-bitstream-vera: failed to write cache
caching, 10 fonts, 0 dirs
/usr/share/fonts/type1: /usr/share/fonts/type1: failed to write cache
caching, 0 fonts, 1 dirs
/usr/share/fonts/type1/gsfonts: /usr/share/fonts/type1/gsfonts: failed to write 
cache
caching, 35 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts: /usr/X11R6/lib/X11/fonts: failed to write cache
caching, 0 fonts, 6 dirs
/usr/X11R6/lib/X11/fonts/100dpi: /usr/X11R6/lib/X11/fonts/100dpi: failed to 
write cache
caching, 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/75dpi: /usr/X11R6/lib/X11/fonts/75dpi: failed to write 
cache
caching, 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/Speedo: /usr/X11R6/lib/X11/fonts/Speedo: failed to 
write cache
caching, 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/Type1: /usr/X11R6/lib/X11/fonts/Type1: failed to write 
cache
caching, 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/encodings: /usr/X11R6/lib/X11/fonts/encodings: failed 
to write cache
caching, 0 fonts, 1 dirs
/usr/X11R6/lib/X11/fonts/encodings/large: 
/usr/X11R6/lib/X11/fonts/encodings/large: failed to write cache
caching, 0 fonts, 0 dirs
/usr/X11R6/lib/X11/fonts/misc: /usr/X11R6/lib/X11/fonts/misc: failed to write 
cache
caching, 0 fonts, 0 dirs
/usr/local/share/fonts: /usr/local/share/fonts: failed to write cache
caching, 0 fonts, 0 dirs
/home/wink/.fonts: /home/wink/.fonts: failed to write cache
caching, 0 fonts, 0 dirs
/var/lib/defoma/fontconfig.d: /var/lib/defoma/fontconfig.d: failed to write 
cache
caching, 0 fonts, 16 dirs
/var/lib/defoma/fontconfig.d/A: /var/lib/defoma/fontconfig.d/A: failed to write 
cache
caching, 6 fonts, 0 dirs
/var/lib/defoma/fontconfig.d/B: /var/lib/defoma/fontconfig.d/B: failed to write 
cache
caching, 10 fonts, 0 dirs
/var/lib/defoma/fontconfig.d/C: /var/lib/defoma/fontconfig.d/C: failed

Font Config, TTF-OpenSymbol and OpenOffice?

[Alle Meije Wink]

These three, and maybe Xorg, seem to not like each other...

I am running etch at the moment, with Xorg as my X server. During an 
apt-get update last week or so, openoffice-org and ttf-opensymbol were 
upgraded. Things started going wrong when it came to installing 
openoffice-org, which was unconfigured and that was a problem. Not that 
I had had a chance to run it... Could not really figure out what the 
problem was. After that, during the configuration of ttf-opensymbol, 
these error messages showed up:


Setting up ttf-opensymbol (2.0.4~rc3-1) ...
Updating fontconfig cache...
/usr/share/fonts: failed to write cache
/usr/share/fonts/X11: failed to write cache
/usr/share/fonts/X11/100dpi: failed to write cache
/usr/share/fonts/X11/75dpi: failed to write cache
/usr/share/fonts/X11/Type1: failed to write cache
/usr/share/fonts/X11/encodings: failed to write cache
/usr/share/fonts/X11/encodings/large: failed to write cache
/usr/share/fonts/X11/misc: failed to write cache
/usr/share/fonts/X11/util: failed to write cache
/usr/share/fonts/afms: failed to write cache
/usr/share/fonts/afms/adobe: failed to write cache
/usr/share/fonts/truetype: failed to write cache
/usr/share/fonts/truetype/freefont: failed to write cache
/usr/share/fonts/truetype/latex-xft-fonts: failed to write cache
/usr/share/fonts/truetype/msttcorefonts: failed to write cache
/usr/share/fonts/truetype/openoffice: failed to write cache
/usr/share/fonts/truetype/ttf-bitstream-vera: failed to write cache
/usr/share/fonts/type1: failed to write cache
/usr/share/fonts/type1/gsfonts: failed to write cache
/usr/X11R6/lib/X11/fonts: failed to write cache
/usr/X11R6/lib/X11/fonts/100dpi: failed to write cache
/usr/X11R6/lib/X11/fonts/75dpi: failed to write cache
/usr/X11R6/lib/X11/fonts/Speedo: failed to write cache
/usr/X11R6/lib/X11/fonts/Type1: failed to write cache
/usr/X11R6/lib/X11/fonts/encodings: failed to write cache
/usr/X11R6/lib/X11/fonts/encodings/large: failed to write cache
/usr/X11R6/lib/X11/fonts/misc: failed to write cache
/usr/local/share/fonts: failed to write cache
/var/lib/defoma/fontconfig.d: failed to write cache
/var/lib/defoma/fontconfig.d/A: failed to write cache
/var/lib/defoma/fontconfig.d/B: failed to write cache
/var/lib/defoma/fontconfig.d/C: failed to write cache
/var/lib/defoma/fontconfig.d/D: failed to write cache
/var/lib/defoma/fontconfig.d/F: failed to write cache
/var/lib/defoma/fontconfig.d/G: failed to write cache
/var/lib/defoma/fontconfig.d/I: failed to write cache
/var/lib/defoma/fontconfig.d/N: failed to write cache
/var/lib/defoma/fontconfig.d/S: failed to write cache
/var/lib/defoma/fontconfig.d/T: failed to write cache
/var/lib/defoma/fontconfig.d/U: failed to write cache
/var/lib/defoma/fontconfig.d/V: failed to write cache
/var/lib/defoma/fontconfig.d/W: failed to write cache
/var/lib/defoma/fontconfig.d/c: failed to write cache
/var/lib/defoma/fontconfig.d/m: failed to write cache
/var/lib/defoma/fontconfig.d/w: failed to write cache
/usr/lib/X11/fonts/misc: failed to write cache
/usr/lib/X11/fonts/100dpi: failed to write cache
/usr/lib/X11/fonts/75dpi: failed to write cache
/usr/lib/X11/fonts/Type1: failed to write cache
/usr/lib/X11/fonts/Speedo: failed to write cache

I could reproduce these messages by running fc-cache. No idea where the 
cache is that needs to be written but can't. I tried to change 
permissions in /var and /etch but that didn't help. The final message of 
apt-get was:


Errors were encountered while processing:
ttf-opensymbol
openoffice.org-core
python-uno
openoffice.org-writer
openoffice.org-help-en-gb

and every time I run apt-get update, it tries again to configure 
ttf-opensymbols/fontconfig (and fails)


Does anyone know what this problem is? Can it be solved by manually 
deleting files? Someone here describes a solution
http://forums.debian.net/viewtopic.php?p=35155sid=90c8663cce0078cb81209c36e33e519e 

by moving libraries from /usr/lib/ to /usr/X11R6/lib/, but those are not 
the same as I have...


Any help on this would be very much appreciated!
best wishes, Alle Meije



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Font Config, TTF-OpenSymbol and OpenOffice?

[Alle Meije Wink]

These three, and maybe Xorg, seem to not like each other...

I am running etch at the moment, with Xorg as my X server. During an 
apt-get update last week or so, openoffice-org and ttf-opensymbol were 
upgraded. Things started going wrong when it came to installing 
openoffice-org, which was unconfigured and that was a problem. Not that 
I had had a chance to run it... Could not really figure out what the 
problem was. After that, during the configuration of ttf-opensymbol, 
these error messages showed up:


Setting up ttf-opensymbol (2.0.4~rc3-1) ...
Updating fontconfig cache...
/usr/share/fonts: failed to write cache
/usr/share/fonts/X11: failed to write cache
/usr/share/fonts/X11/100dpi: failed to write cache
/usr/share/fonts/X11/75dpi: failed to write cache
/usr/share/fonts/X11/Type1: failed to write cache
/usr/share/fonts/X11/encodings: failed to write cache
/usr/share/fonts/X11/encodings/large: failed to write cache
/usr/share/fonts/X11/misc: failed to write cache
/usr/share/fonts/X11/util: failed to write cache
/usr/share/fonts/afms: failed to write cache
/usr/share/fonts/afms/adobe: failed to write cache
/usr/share/fonts/truetype: failed to write cache
/usr/share/fonts/truetype/freefont: failed to write cache
/usr/share/fonts/truetype/latex-xft-fonts: failed to write cache
/usr/share/fonts/truetype/msttcorefonts: failed to write cache
/usr/share/fonts/truetype/openoffice: failed to write cache
/usr/share/fonts/truetype/ttf-bitstream-vera: failed to write cache
/usr/share/fonts/type1: failed to write cache
/usr/share/fonts/type1/gsfonts: failed to write cache
/usr/X11R6/lib/X11/fonts: failed to write cache
/usr/X11R6/lib/X11/fonts/100dpi: failed to write cache
/usr/X11R6/lib/X11/fonts/75dpi: failed to write cache
/usr/X11R6/lib/X11/fonts/Speedo: failed to write cache
/usr/X11R6/lib/X11/fonts/Type1: failed to write cache
/usr/X11R6/lib/X11/fonts/encodings: failed to write cache
/usr/X11R6/lib/X11/fonts/encodings/large: failed to write cache
/usr/X11R6/lib/X11/fonts/misc: failed to write cache
/usr/local/share/fonts: failed to write cache
/var/lib/defoma/fontconfig.d: failed to write cache
/var/lib/defoma/fontconfig.d/A: failed to write cache
/var/lib/defoma/fontconfig.d/B: failed to write cache
/var/lib/defoma/fontconfig.d/C: failed to write cache
/var/lib/defoma/fontconfig.d/D: failed to write cache
/var/lib/defoma/fontconfig.d/F: failed to write cache
/var/lib/defoma/fontconfig.d/G: failed to write cache
/var/lib/defoma/fontconfig.d/I: failed to write cache
/var/lib/defoma/fontconfig.d/N: failed to write cache
/var/lib/defoma/fontconfig.d/S: failed to write cache
/var/lib/defoma/fontconfig.d/T: failed to write cache
/var/lib/defoma/fontconfig.d/U: failed to write cache
/var/lib/defoma/fontconfig.d/V: failed to write cache
/var/lib/defoma/fontconfig.d/W: failed to write cache
/var/lib/defoma/fontconfig.d/c: failed to write cache
/var/lib/defoma/fontconfig.d/m: failed to write cache
/var/lib/defoma/fontconfig.d/w: failed to write cache
/usr/lib/X11/fonts/misc: failed to write cache
/usr/lib/X11/fonts/100dpi: failed to write cache
/usr/lib/X11/fonts/75dpi: failed to write cache
/usr/lib/X11/fonts/Type1: failed to write cache
/usr/lib/X11/fonts/Speedo: failed to write cache

I could reproduce these messages by running fc-cache. No idea where the 
cache is that needs to be written but can't. I tried to change 
permissions in /var and /etch but that didn't help. The final message of 
apt-get was:


Errors were encountered while processing:
ttf-opensymbol
openoffice.org-core
python-uno
openoffice.org-writer
openoffice.org-help-en-gb

and every time I run apt-get update, it tries again to configure 
ttf-opensymbols/fontconfig (and fails)


Does anyone know what this problem is? Can it be solved by manually 
deleting files? Someone here describes a solution

http://forums.debian.net/viewtopic.php?p=35155sid=90c8663cce0078cb81209c36e33e519e
by moving libraries from /usr/lib/ to /usr/X11R6/lib/, but those are not 
the same as I have...


Any help on this would be very much appreciated!
best wishes, Alle Meije



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

trying to rescue disk

[Alle Meije Wink]

Hi,

I wrote some time ago about a my linux disk that had crashed. The 
contents could be saved and were put on another disk (same size 
different brand). The new disk was not accessable from Windows anymore 
(explore2fs), as the old one was. I also could not boot from it anymore, 
tried that and the screen was filled with an endless string of GRUB 
GRUB GRUB... which *was* my boot manager.


I tried the Live CD rescue option:


From:  Mumia W. [EMAIL PROTECTED]
Date: Sun, 13 Aug 2006 11:04:52 -0500
To: Debian User debian-user@lists.debian.org

On 08/13/2006 08:32 AM, Alle Meije Wink wrote:
[...] It gives messages like ``Error: Access violation at address 
00097BD1 in module `explore2fs.exe'. Read of address 00921268''.


My guess is that the addressing on the Seagate is somehow different 
than on the Maxtor, which makes it less straightforward to transfer a 
whole disc image between the two. Is there a way to access the 
contents of the old disc on the new disc (e.g. by running a liveCD and 
then mounting the disc and re-installing Grub)?


Does anyone who's been in a similar situation know how to deal with this?

See if you can use a Knoppix disk or another Linux live CD to look at 
that partition.


The Live CD was Ubuntu in this case (as Knoppix, it's Debian-based). In 
the Live CD session, though, you're logged in as non-root, and the root 
pwd is not given. Does that mean exit Live CD?


I also tried Ubuntu alternate install, which contains text-based 
installation and rescue disk. These options all seem to want to interact 
with/write to the disk before you can log in, which is not something 
that makes me feel safe (without knowing what is actually written).


Does anyone know of a Live CD that permits you to do things in a 
terminal and interact with your old linux system?


Many thanks
Alle Meije


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

tranfer of linux image

[Alle Meije Wink]

I had a linux system on a 120 Gb hard disc (Maxtor DiamondMax plus 9). 
At some point is stopped working, and I thought the head had crashed.


It appeared that it was only a controller failure, and it was possible 
to transfer the contents to another 120 Gb disc (a Seagate ST3120026A). 
I put the disc in the drive, and tried to boot it. Would have been 
surprised if it had worked at once...


After booting from the disc, the screen was filled with `GRUB GRUB 
GRUB'... which does make sense in the way that GRUB was my boot manager 
on the old disc, but does not really help for booting.


I booted then from the other disc again (WinXP), wher I can run 
explore2fs (a program to access my Linux disc from outside). That always 
worked very well with the old Maxtor, but returns an error with the new 
Seagate. It gives messages like ``Error: Access violation at address 
00097BD1 in module `explore2fs.exe'. Read of address 00921268''.


My guess is that the addressing on the Seagate is somehow different than 
on the Maxtor, which makes it less straightforward to transfer a whole 
disc image between the two. Is there a way to access the contents of the 
old disc on the new disc (e.g. by running a liveCD and then mounting the 
disc and re-installing Grub)?


Does anyone who's been in a similar situation know how to deal with this?

Many thanks
Alle Meije Wink


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: dhcp, router and debian

[Alle Meije Wink]

Chris Lale wrote:

The thing is, after my computer halts (and no wireless connections
are in use), I usually switch off the whole box by switching off
the power socket. So when I fire up the system, the modem + router
are usually just starting as well.


This is the cause of your problem. This is how booting seems to work.
During boot, Debian starts running the MTA (Mail Transport Agent)
which is Exim4 in a default installation. It is looking for the
network connection - this will be the internet. If your ethernet card
connects immediately to the internet, Exim4 will start seamlessly.
Otherwise, you will have to wait a minute or two until Debian gives
up trying the connection and starts Exim4 anyway.
It seems that if my router is running without problems already (after 
having started the computer with windows :( ), exim connects fine 
through the router (not immediate connection) as well. The problem 
really seems to be that after a cold start (both modem and router are 
switched on and the computer is booting), the router does not find the 
connection itself. It needs something from windows to start it. If that 
is true it is bad...


I usually switch off the whole box by switching off the power 
socket.


This is not a good idea with any system - you could easily get disc
corruption. Always shutdown normally using the display manager
command button (in gdm, kdm, xdm) in X, shutdown command or
ctrl-alt-del in a console.
Well, this is what I do. I shutdown from within KDE (since 2.6 even the 
computer turns itself off) and then I switch of the main socket on the 
wall. This works perfectly, even with the cable modem starting up. It's 
since I got the router that the problems have started. Nobody else has 
similar experiences with a D-link DI425?


George Borisov wrote:

This is the cause of your problem. This is how booting seems to work.
During boot, Debian starts running the MTA (Mail Transport Agent) which
is Exim4 in a default installation. It is looking for the network
connection - this will be the internet. If your ethernet card connects
immediately to the internet, Exim4 will start seamlessly. Otherwise, you
will have to wait a minute or two until Debian gives up trying the
connection and starts Exim4 anyway.

Alternatively, if you don't have a reliable internet connection on
start-up you can do dpkg-reconfigure exim4-config and select yes for
the Use Minimal DNS question at the very end. This will stop it
hanging on start-up, if the internet connection is down.
This may be an idea to use anyway, thanks. Nevertheless I still think my 
connection is quite reliable. It's the router in between. When it works 
(once it works) it's very reliable too...


I'm now leaving the modem and the router on (using a different socket), 
and this seems to work. Thanks for all the advice. I still consider it a 
low-tech solution though (feel a bit beaten by D-link and M$).


Cheers
Alle Meije


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: dhcp, router and debian

[Alle Meije Wink]

Hi,

I have installed a D-Link DI-524 wireless/ethernet router between my
cable modem and my PC. It worked fine on the first 5 (or so) sessions,
but now when I start up debian, the startup item `ATM' takes ages to
finish (it says `exim4' in the end) and I have no internet connection 
 
 Are you sure you aren't seeing MTA?

 If you are, that is probably exim starting, which on a few of my
 systems caused boot delays. This caused no problem however, in my case
 at least.
 
 exim is the systems mailer, delevering mail between users, on certain

 events, etc.
 
 Have you tried ifconfig after you are logged in? You will have to

 either use sudo, or su from a non-privelaged account.


I'm sorry, yes it was MTA.

The thing is, after my computer halts (and no wireless connections are
in use), I usually switch off the whole box by switching off the power
socket. So when I fire up the system, the modem + router are usually
just starting as well.
In some way, this works for windows and not for linux. After I boot in
windows and restart in linux (without switching off the power socket),
the connection is just fine.

When the connection works I get something like this:
$ sudo /sbin/ifconfig eth0
eth0   Link encap:Ethernet  HWaddr ##:##:##:##:##:##
   inet addr:192.168.0.152  Bcast:192.168.0.255  Mask:255.255.255.0
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:804 errors:0 dropped:0 overruns:0 frame:0
   TX packets:696 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:171908 (167.8 KiB)  TX bytes:54151 (52.8 KiB)
   Interrupt:11 Base address:0x2000
I can ifdown and ifup my network card as often as I like.

ah...
When the connection doesn't work it does exactly the same thing. This is 
only for the connection Linux PC - router...


The only thing I can think of is that it is the router that cannot get a 
connection to the internet/my ISP. Although that does not make sense, 
does it? I mean, the router is a standalone device, that does not need a 
windows or linux PC to run (maybe for setting it up via its html page, 
but that's it).


The setup html page for the router (the dhcp part) has got fields to 
fill in (like DNSes, masks, etc) but usually it runs without those. 
Would it be necessary to fill in these values to guarantee it working 
with linux? Can't remember ever being told my ISP's DNS.


Thanks for your help,
Alle Meije


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

dhcp, router and debian

[Alle Meije Wink]

Hi,

I have installed a D-Link DI-524 wireless/ethernet router between my 
cable modem and my PC. It worked fine on the first 5 (or so) sessions, 
but now when I start up debian, the startup item `ATM' takes ages to 
finish (it says `exim4' in the end) and I have no internet connection in 
Linnux. The setup software for the router was of course all M$ software, 
and when I start my PC in Windows the internet connection seems to work.


I don't know what ATM does (it does not show up in the /var/boot file) 
but that seems to be the difference between it working and not working. 
On startup, dhcpclient does not seem to have any sort of problem, but as 
soon as I have logged in, all internet access (ping, thunderbird, 
apt-get) fails.


I have protected the wireless network with WPA. Don't know if that is 
part of the problem.


Is this a problem that people have come across before?

Thanks
Alle Meije Wink



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

new packages

[Alle Meije Wink]

Hello,

My apt-get, although it appears to be working fine, has not found
updated packages for the the last week. Is this because actually no
packages have been updated or is there another reason?

Best wishes
Alle Meije



___ 
How much free photo storage do you get? Store your holiday 
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]