Matrox Meteor frame grabber.

[peter]

There is an old Matrox Meteor PCI card here.
http://easthope.ca/MatroxMeteor.jpg 
As I understand, a frame grabber or video tuner.  

The connector on the lower left in the photo accepts an RCA plug.  The 
connector immediately above that is S video.  The next above is a 3.5 
mm TRS socket.  Audio? The connector on the shielding box is similar 
to RCA but smaller.  Any ideas about that?  

Which of these is input and which is output?

The closest document I've found on the Matrox Web site lacks the 
shielding box and has a DE-9 subminiature connector on the upper end of 
the bracket. 

Can Debian display composite video using this card?  Which packages are 
needed?

Thanks,... Peter E. 
-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Whats the alternative to .xinitrc

[Rob Brewer]

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 startx man page.

As .xinitrc has worked OK in the past, how do I now set the user environment 
when X starts?

Rob

Re: customizing debian-installer

[Brian]

On Sat 18 Feb 2017 at 14:24:56 +0100, jurek wrote:

> Hi,
> 
> I'd like to have several debian-installers on one pendrive (luks
> encrypted) and
> keep them in subdirectories.
> 
> I've set up grub.cfg in mbr to choose between them.
> 
> At the moment it works, but I need to run several commands manually:
> 
> For example:
> 
> anna-install cryptsetup-udeb
> anna-install crypto-dm-modules
> anna-install crypto-modules
> depmod -a
> modprobe dm-mod
> cryptsetup luksOpen /dev/sda3 sda3
> mkdir cdr
> mount -t ext4 /dev/mapper/sda3 /cdr
> umount /cdrom
> mount --bind /cdr/i386 /cdrom
> 
> How can I automate those commands?

Take a look at early_command and late_command to begin with. The
Installation Manual should help.

-- 
Brian.

Re: Printing from feh

[Brian]

On Sat 18 Feb 2017 at 21:02:30 +, Darac Marjal wrote:

> It looks like it should be possible, using the --action options. Try
> setting Action 1 to something like lpr, then press 1 while viewing an image.
> 
> On 17/02/17 19:54, Brian wrote:
> > On Fri 17 Feb 2017 at 19:11:29 +, Andre Müller wrote:
> >
> >> It's ok :-)
> >> The topic is very dry and hard to understand because you have to make
> >> a step to the side and to call everything to into question.
> > That is what is on my mind too. Feh is a nice image viewer but it
> > appears to have no printing facility. Is there a way of printing
> > a displayed image from within the program?

A spot-on suggestion. I ended up with /usr/local/bin/feh with
the contents

  /usr/bin/feh --action "xpp %f" "$1"

Then took it a step further and rebound action_0 to ctrl-P to fit with
other applications. In .config/feh/keys:

  action_0
  action_0 C-p

"xpp %f" can be replaced with a printing command of your choice. It's
not so hard to print from an image viewer without its own printing
dialog after all.

Thanks.

-- 
Brian.

Re: Printing from feh

[Darac Marjal]

It looks like it should be possible, using the --action options. Try
setting Action 1 to something like lpr, then press 1 while viewing an image.


On 17/02/17 19:54, Brian wrote:
> On Fri 17 Feb 2017 at 19:11:29 +, Andre Müller wrote:
>
>> It's ok :-)
>> The topic is very dry and hard to understand because you have to make
>> a step to the side and to call everything to into question.
> That is what is on my mind too. Feh is a nice image viewer but it
> appears to have no printing facility. Is there a way of printing
> a displayed image from within the program?
>

Re: Whats the alternative to .xinitrc

[Brian]

On Sat 18 Feb 2017 at 12:56:54 +, Bob Brewer wrote:

> 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 startx man page.

The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
DM ignores it.

-- 
Brian.

Re: Whats the alternative to .xinitrc

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Feb 18, 2017 at 12:56:54PM +, Bob Brewer wrote:
> 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 startx man page.
> 
> As .xinitrc has worked OK in the past, how do I now set the user environment 
> when X starts?

My .xsessionrc is functional. The magic happens in
   /etc/X11/Xsession.d/40x11-common_xsessionrc

 +---
 | # This file is sourced by Xsession(5), not executed.
 | 
 | #Source user defined xsessionrc (locales and other environment variables)
 | if [ -r "$USERXSESSIONRC" ]; then
 |   . "$USERXSESSIONRC"
 | fi
 +---

Attention: I'm running SysV init -- perhaps things are different in other
settings.

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliormQACgkQBcgs9XrR2ka3sACfYUICUKHA955wfYf3tfBhSC3M
T7AAnAy8UvS5CQnSVLzOptexKu3zNrn2
=Xlbl
-END PGP SIGNATURE-

Re: Don't taint kernel when using the forcepae kernel boot parameter

[Stephen Powell]

On Sat, Feb 18, 2017, at 13:36, Nicholas Geovanis wrote:
> 
> Wow. This is some of the best Debian doc I've seen. Really thanks.
> And z/VM stuff. What's not to like?
> 
> Nick-former-VM/SP-current-Debian-system-administrator-:-)-G

Thanks for the compliment.  I hope you find at least some of it useful.
I have received much benefit over the years as a user of open source
software.  The docs are my attempt at giving something back.

Regards,

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Don't taint kernel when using the forcepae kernel boot parameter

[Nicholas Geovanis]

Wow. This is some of the best Debian doc I've seen. Really thanks.
And z/VM stuff. What's not to like?

Nick-former-VM/SP-current-Debian-system-administrator-:-)-G

On Sat, Feb 18, 2017 at 8:07 AM, Stephen Powell 
wrote:

> For those of you who have an old laptop/notebook with a Banias-class
> Pentium M or
> Celeron M 32-bit Intel processor, use the forcepae option, and run a
> custom kernel
> (admitedly a limited audience), I have just developed a patch which you
> may find
> useful.  By default, the kernel will taint itself (for the reason "CPU out
> of spec")
> when the forcepae kernel boot parameter is used.  I disagree with this
> course of
> action.  First of all, the CPU is not really out of spec.  The CPU has all
> the
> capabilities that the kernel requires of it.  It just fails to report one
> of them.
> Second, there is no binary-only blob mixed in with the source code.  It
> makes sense
> to disable lock debugging when all the source code is not available, but
> there is
> no missing source code in this case.  My patch leaves the kernel untainted:
>
>wget http://www.stevesdebianstuff.org/dont_taint_forcepae.patch
>
> For more information about building a custom kernel, see
>
>http://www.stevesdebianstuff.org/Kernel.htm
>
> --
>   .''`. Stephen Powell
>  : :'  :
>  `. `'`
>`-
>
>

Whats the alternative to .xinitrc

[Bob Brewer]

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 startx man page.

As .xinitrc has worked OK in the past, how do I now set the user environment 
when X starts?

Rob

Re: Last spam: Let me know Munich Mayor's email address, please..

[deloptes]

Andre Müller wrote:

> can't make a constitution.
you don't have constitution but Grundgesetz, which is meant to function as a
constitution. I tried to find out for couple of months , but there is only
the 2+4 Vertrag and it is not conclusive. So it is not clear to me ... and
not only to me.

It doesn't help to argue here anyway.

regards

Re: Last spam: Let me know Munich Mayor's email address, please..

[deloptes]

to...@tuxteam.de wrote:

> I don't think you want to go there (especially when the above mentioned
> Reichsbürger have been caught hoarding weapons and when one of them has
> already shot a cop dead.

A common mistake is to deduce from one event or single person, which does
not mean I agree with the Reichsbürgers ideas, however one should respect
each other. The growing number of the s.c. Reichsbürger in the past years
in Germany and Austria means there is a problem in those countries.
Laughing at those people is pointless, but understanding the reasons
behind, would be wise IMO.

regards

Don't taint kernel when using the forcepae kernel boot parameter

[Stephen Powell]

For those of you who have an old laptop/notebook with a Banias-class Pentium M 
or
Celeron M 32-bit Intel processor, use the forcepae option, and run a custom 
kernel
(admitedly a limited audience), I have just developed a patch which you may find
useful.  By default, the kernel will taint itself (for the reason "CPU out of 
spec")
when the forcepae kernel boot parameter is used.  I disagree with this course of
action.  First of all, the CPU is not really out of spec.  The CPU has all the
capabilities that the kernel requires of it.  It just fails to report one of 
them.
Second, there is no binary-only blob mixed in with the source code.  It makes 
sense
to disable lock debugging when all the source code is not available, but there 
is
no missing source code in this case.  My patch leaves the kernel untainted:

   wget http://www.stevesdebianstuff.org/dont_taint_forcepae.patch

For more information about building a custom kernel, see

   http://www.stevesdebianstuff.org/Kernel.htm

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

customizing debian-installer

[jurek]

Hi,

I'd like to have several debian-installers on one pendrive (luks
encrypted) and
keep them in subdirectories.

I've set up grub.cfg in mbr to choose between them.

At the moment it works, but I need to run several commands manually:

For example:

anna-install cryptsetup-udeb
anna-install crypto-dm-modules
anna-install crypto-modules
depmod -a
modprobe dm-mod
cryptsetup luksOpen /dev/sda3 sda3
mkdir cdr
mount -t ext4 /dev/mapper/sda3 /cdr
umount /cdrom
mount --bind /cdr/i386 /cdrom

How can I automate those commands?

Thanks!
Jurek

Re: Last spam: Let me know Munich Mayor's email address, please..

[GiaThnYgeia]

I apologize for feeding the trolls, you may say I have a soft spot for
strays.

to...@tuxteam.de:
> No. You don't define truth as "arithmetic means between realities", unless
> you've convinced yourself the deviations follow a normal distribution.

I liked this part better than any practical advise on deb.sys,admin ever.

> I don't think you want to go there (especially when the above mentioned
> Reichsbürger have been caught hoarding weapons and when one of them has
> already shot a cop dead.

Not all people who shot cops are good people, is this what you are
saying?  But let's make a mini sublist somewhere else and discuss this.

> I bow out.

Eject, eject

-- 
 "The most violent element in society is ignorance" rEG

Re: stretch apt-get -u dist-upgrade does not result in sid

[Felix Miata]

Gene Heskett composed on 2017-02-18 06:09 (UTC-0500):


Felix Miata wrote:



Gene Heskett composed on 2017-02-18 00:25 (UTC-0500):



> Felix Miata wrote:



>> I changed sources.list to point only to sid, then apt-get clean,
>> then apt-get update, apt-get -u dist-upgrade. /etc/debian_version
>> and /etc/issue still say I have 9.0. Can held back non-essential
>> packages stonewall a dist-upgrade? mc and mc-lang 4.8.17 have been
>> held back by me manually because 4.8.18 is broken. Is this why I
>> don't seem to have sid?



> File the bug. Its pretty likely.



File which bug? mc-4.8.19 is fixed.



But is it in a repo you can access?


Probably not. It hasn't been released yet.
--
"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: stretch apt-get -u dist-upgrade does not result in sid

[Gene Heskett]

On Saturday 18 February 2017 00:33:32 Felix Miata wrote:

> Gene Heskett composed on 2017-02-18 00:25 (UTC-0500):
> > Felix Miata wrote:
> >> I changed sources.list to point only to sid, then apt-get clean,
> >> then apt-get update, apt-get -u dist-upgrade. /etc/debian_version
> >> and /etc/issue still say I have 9.0. Can held back non-essential
> >> packages stonewall a dist-upgrade? mc and mc-lang 4.8.17 have been
> >> held back by me manually because 4.8.18 is broken. Is this why I
> >> don't seem to have sid?
> >
> > File the bug. Its pretty likely.
>
> File which bug? mc-4.8.19 is fixed.

But is it in a repo you can access?


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Library Install Problem.

[S. P. Molnar]

On 02/18/2017 04:40 AM, Floris wrote:


Op Fri, 17 Feb 2017 19:09:37 +0100 schreef S. P. Molnar 
:


I am running an up-to-date Debian v-8.7.1 and have encountered a 
problem installing some libraries.


Here are the error messages:

comp@AbNormal ~> sudo dpkg --configure -a
Setting up libcuda1:amd64 (340.101-1) ...
Killed
dpkg: error processing package libcuda1:amd64 (--configure):
  subprocess installed post-installation script returned error exit 
status 137

dpkg: dependency problems prevent configuration of libnvcuvid1:amd64:
  libnvcuvid1:amd64 depends on libcuda1 (= 340.101-1); however:
   Package libcuda1:amd64 is not configured yet.

dpkg: error processing package libnvcuvid1:amd64 (--configure):
  dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libcuinj64-6.0:amd64:
  libcuinj64-6.0:amd64 depends on libcuda1 (>= 169); however:
   Package libcuda1:amd64 is not configured yet.

dpkg: error processing package libcuinj64-6.0:amd64 (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  libcuda1:amd64
  libnvcuvid1:amd64
  libcuinj64-6.0:amd64

This is very annoying as it stops Synaptic.

How do i solve the problem?

Thanks in advance.



sudo apt-get purge libcuda1

if you need this package and your GPU is supported by the latest version
enable backports and install version 375.26-2

https://backports.debian.org/Instructions/

Floris



Thanks for the apt-get command.  It solved the problem.

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.Molecular-Modeling.net  Stochastic and multivariate
(614)312-7528 (c)
Skype:  smolnar1

Re: stretch apt-get -u dist-upgrade does not result in sid

[Joe]

On Sat, 18 Feb 2017 00:10:00 -0500
Felix Miata  wrote:

> I changed sources.list to point only to sid, then apt-get clean, then
> apt-get update, apt-get -u dist-upgrade. /etc/debian_version
> and /etc/issue still say I have 9.0. Can held back non-essential
> packages stonewall a dist-upgrade? mc and mc-lang 4.8.17 have been
> held back by me manually because 4.8.18 is broken. Is this why I
> don't seem to have sid?

What is the boot console banner?

Unstable is always named as "/sid", even with a minimal
stable installation followed by immediate upgrade to unstable. The
version number will always be that of testing, unstable doesn't have
its own number.

Also try a grep for distro in /var/log/messages. There should be a
90linux-distro: result: line. But if the sources.list contains only
unstable or sid, that's what you will get. Once you've done an update,
apt doesn't know about the testing repositories any more.

Until the freeze, most packages will be the same in sid as in testing,
generally anything that survives without major breakage in sid for
about ten days gets moved on. Did you get a larger than normal upgrade
when you did the dist-upgrade? Make an upgrade now and note any changed
version: check with the Debian packages search to see which
distribution the new one comes from.

-- 
Joe

Re: stretch apt-get -u dist-upgrade does not result in sid

[Jörg-Volker Peetz]

Felix Miata wrote on 02/18/17 06:10:
> I changed sources.list to point only to sid, then apt-get clean, then apt-get
> update, apt-get -u dist-upgrade. /etc/debian_version and /etc/issue still say 
> I
> have 9.0. Can held back non-essential packages stonewall a dist-upgrade? mc 
> and
> mc-lang 4.8.17 have been held back by me manually because 4.8.18 is broken. Is
> this why I don't seem to have sid?

The file /etc/issue belongs to package base-files (dpkg -S /etc/issue)
There is no newer version of this package in sid than that of testing which is
version 9.8. Therefore, you see "9.0" in /etc/issue.

More helpful is apt-show-versions (from the package with the same name):

$ apt-show-versions | grep unstable

To find out if some packages are still upgradeable, order

$ apt-show-versions -u

Regards,
jvp.

Re: Library Install Problem.

[Floris]

Op Fri, 17 Feb 2017 19:09:37 +0100 schreef S. P. Molnar  
:


I am running an up-to-date Debian v-8.7.1 and have encountered a problem  
installing some libraries.


Here are the error messages:

comp@AbNormal ~> sudo dpkg --configure -a
Setting up libcuda1:amd64 (340.101-1) ...
Killed
dpkg: error processing package libcuda1:amd64 (--configure):
  subprocess installed post-installation script returned error exit  
status 137

dpkg: dependency problems prevent configuration of libnvcuvid1:amd64:
  libnvcuvid1:amd64 depends on libcuda1 (= 340.101-1); however:
   Package libcuda1:amd64 is not configured yet.

dpkg: error processing package libnvcuvid1:amd64 (--configure):
  dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libcuinj64-6.0:amd64:
  libcuinj64-6.0:amd64 depends on libcuda1 (>= 169); however:
   Package libcuda1:amd64 is not configured yet.

dpkg: error processing package libcuinj64-6.0:amd64 (--configure):
  dependency problems - leaving unconfigured
Errors were encountered while processing:
  libcuda1:amd64
  libnvcuvid1:amd64
  libcuinj64-6.0:amd64

This is very annoying as it stops Synaptic.

How do i solve the problem?

Thanks in advance.



sudo apt-get purge libcuda1

if you need this package and your GPU is supported by the latest version
enable backports and install version 375.26-2

https://backports.debian.org/Instructions/

Floris

Re: Crashes in Icedove on Stretch

[Jörg-Volker Peetz]

Daniel Bareiro wrote on 02/16/17 15:14:

> Thanks for sharing your experience. It would be good to know if it
> remains stable after several days. I just applied the change suggested
> by Benjamin in another message in this thread.
> 
> Kind regards,
> Daniel
> 
Meanwhile I had the first crash of thunderbird. After updating some gtk- and
glib related stuff I'm trying it again. If thunderbird still crashes, I surely
apply the setting of the config variable
"layers.offmainthreadcomposition.enabled" (OMTC) which is enabled for faster and
smoother composition.

Regards,
jvp.

Re: stretch apt-get -u dist-upgrade does not result in sid

[Floris]

Op Sat, 18 Feb 2017 06:10:00 +0100 schreef Felix Miata  
:


I changed sources.list to point only to sid, then apt-get clean, then  
apt-get update, apt-get -u dist-upgrade. /etc/debian_version and  
/etc/issue still say I have 9.0. Can held back non-essential packages  
stonewall a dist-upgrade? mc and mc-lang 4.8.17 have been held back by  
me manually because 4.8.18 is broken. Is this why I don't seem to have  
sid?


sid doesn't have a version number

stretch and sid both use the same base-file package, so  
/etc/debian_version is the same

http://sources.debian.net/src/base-files/

Floris

Re: Last spam: Let me know Munich Mayor's email address, please..

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sat, Feb 18, 2017 at 09:26:47AM +0100, deloptes wrote:
> Michael Lange wrote:
> 
> > Oops, I guess I picked the wrong English word, I guess it should rather
> > read "deny the legal existence..."
> 
> You know Germany is still occupied by the USA [...]
> IMO the truth is somewhere in the middle.

No. You don't define truth as "arithmetic means between realities", unless
you've convinced yourself the deviations follow a normal distribution.

> In return you may check https://en.wikipedia.org/wiki/Allegory_of_the_Cave
> and be more polite and show some more respect towards different opinions.

Or alternate realities.

I don't think you want to go there (especially when the above mentioned
Reichsbürger have been caught hoarding weapons and when one of them has
already shot a cop dead.

I bow out.
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlioD40ACgkQBcgs9XrR2kY9TgCfY+RsktG/DJWW2OgoCJwIXJod
6PcAn20H4aXizqFeGpmkgj5Q0DFUZ+Y2
=EV8k
-END PGP SIGNATURE-

Re: Last spam: Let me know Munich Mayor's email address, please..

[Andre Müller]

Good morning,

I do not want to fire up a new discussion in a mailing list for a operating
system. I want to clarify some things.
So if you're not interested, then don't answer, don't read it.

@deloptes, this is a good point. To have only on view, you never can say
what is behind you.

Germany is free and not Occupied.
What you have to know Germany != Federal Republic of Germany.
If someone is talking about Germany, he should know that Germany is mix of
different german cultures.
Based on history, Germany has 26 States. The currently 13 federal states
are constructs of the allied.
The federal republic of Germany have made contracts with the NATO.
Nothing more, just contracts between two companies. If we're occupied, then
we can't make a constitution.
We're not Reichsbürger, this is coming from people without much knowledge
about history and the current situation.
But it's normal, that this came from a German guy. I get this message every
day.
So maybe you stop repeating others and start with thinking.
Take a step back from the system where we all live in.
This is always a problem.

The most people are just repeating the media and don't have a own opinion
and no knowledge.

It is also very easy to describe the all actions of the government,
if you know that the federal Republic of Germany is just an operative
US-Holding.

But this is not the point. It doesn't matter what the federal Repuplic of
Germany is, when the people make a constitution.
Even when this is a real State, Constitution Law is one Level above State
Law. Constitution Law yields a new state.

Greetings
Andre

Michael Lange  schrieb am Sa., 18. Feb. 2017 um
01:21 Uhr:

> On Sat, 18 Feb 2017 00:42:34 +0100
> Michael Lange  wrote:
>
> > referred to as "Reichsbürger", who, as a common base, neglect the legal
> > existence of the Federal Republic of Germany and declare their own
>
> Oops, I guess I picked the wrong English word, I guess it should rather
> read "deny the legal existence..." :-)
>
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Genius doesn't work on an assembly line basis.  You can't simply say,
> "Today I will be brilliant."
> -- Kirk, "The Ultimate Computer", stardate 4731.3
>
>

Re: Last spam: Let me know Munich Mayor's email address, please..

[deloptes]

Michael Lange wrote:

> Oops, I guess I picked the wrong English word, I guess it should rather
> read "deny the legal existence..."

You know Germany is still occupied by the USA as there is no legal document
for the opposite. I am not sure who is living in the real world - you or
they. IMO the truth is somewhere in the middle.
In return you may check https://en.wikipedia.org/wiki/Allegory_of_the_Cave
and be more polite and show some more respect towards different opinions.

regards