Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, deloptes  wrote:
> Jimmy Johnson wrote:
>
>> Instead of using apt, next time use aptitude -f install, reason is if
>> aptitude can not fix the problem it will give you a clue as what you can
>> do.  Also if you apt install and run 'upgrade-system' upgrade-system
>> will tell what to do, and clean your system too.
>
> I thought aptitude was obsolated - never used it, but I think there was a
> thread on the list about
>

Obsolated: portmanteau of deprecated and obsolete?

I thought it was merely not recommended for upgrades.

PS: Have you ever performed 'apt-get moo'? (You don't need to be root.)
Gives you a cow.
'aptitude moo' (if you persist by increasing the verbosity with ever more
v's) produces a snake eating an elephant. Maybe that's why it may have been 
obsolated (illogical, Captain).

PSS:
Knock knock.
Who's there?
The interruptive cow.
The interruptive c...
Moo!

-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: Secure email server setup

[Jonathan Sélea]

On 01/15/18 22:30, Henning Follmann wrote:
> On Mon, Jan 15, 2018 at 08:56:20PM +0100, Jonathan Sélea wrote:
 I would not recommend having a emailserver on the same server as a
 website, because if the website is compromised the "hacker" can just use
 the mail() function
 to send emails in your name.
>>> so can she/he if the mailserver is on a different host. That doesn't make
>>> any difference.
>> It would, because other mailservers would deny emails from that one
>> because it would fail authentication (SPF, DKIM, DMARC for example).
>>
> Your webserver having a method to use a smarthost, using an external
> mailserver can be abused when compromised. So no win here. Still exploited
> once the attacker is on the system. It will just use the same smarthost
> with the webservers credentials and the mailserver will happily relay the
> spam. 
>
> -H
If configured properly - the hacker can't change how the server do the
transport, except if the hacker
has gained the privileges to do so. But that is not that common if a
LAMP server for example if properly
configured.
But if a hacker has found an exploit where he can change the transport
settings for the MTA.

I am talking about the default mail() function that is used by many
websites. But you are talking about a server
where a hacker has gained root privileges - in that case there is not
much to do.



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 08:16:04 +0100
deloptes  wrote:

> Michael Lange wrote:
> 
> > Oddly, so far as I have followed this thread, no one seems to
> > consider the possibility to try and compile the application from the
> > sources. I wonder if the debian developers should quit shipping the
> > build system when nobody wants to use it anyway ;-)
> 
> well this was going to be my next suggestion as people are not familiar
> with building code, however it is also possible that build fails
> because code must be adapted to newer version of libraries.
> 

Sure, that's true, but if one wants to use such a (somewhat dated) app it
might be worth a try, and at least it would be a quick one.
But iirc the OP was talking about required javascript support which would
rule out amaya anyway.

To the OP: 
a quick web search showed another alternative that (iirc) has not been
mentioned before, see http://bluegriffon.org/ . I don't know anything
about this program, except that it appears to be commercial but open
source and they have a deb package available (which may or may not work
with debian) and it apparently can be used for free with a somewhat
reduced feature set. 

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Madness has no purpose.  Or reason.  But it may have a goal.
-- Spock, "The Alternative Factor", stardate 3088.7

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, Michael Lange  wrote:
>
> To the OP: 
> a quick web search showed another alternative that (iirc) has not been
> mentioned before, see http://bluegriffon.org/ . I don't know anything
> about this program, except that it appears to be commercial but open
> source and they have a deb package available (which may or may not work
> with debian) and it apparently can be used for free with a somewhat
> reduced feature set. 

 Buy User's Manual
 €7.50 (+VAT inside EU).

Software whose user manual is for sale; sign me up, please, that's for
me!

> Regards
>
> Michael
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Madness has no purpose.  Or reason.  But it may have a goal.
>   -- Spock, "The Alternative Factor", stardate 3088.7
>
>


-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: hostname issue

[john doe]

On 1/15/2018 4:10 PM, Adam Weremczuk wrote:

Hi all,

Today when I logged into my Debian 9.2 VM I noticed that the hostname 
has changed to the first block of the IP address I was accessing this VM 
from last:


root@83:~#



The hostname is displayed by the PS* variables.

https://www.cyberciti.biz/tips/howto-linux-unix-bash-shell-setup-prompt.html


"hostname" command was returning the full IP address 83.xxx.xxx.xxx

Cat /etc/hostname was still showing the correct name.

After apt-get update, ap-get upgrade (to 9.3) and reboot things went 
back to normal.


Is it a known bug?

Has anybody seen anything like this before?



For some reasons your hostname was change (dhcp).
This isn't a bug! :)

--
John Doe

Re: Problem using "dpkg -i"

[Jimmy Johnson]

On 01/15/2018 11:17 PM, deloptes wrote:

Jimmy Johnson wrote:


Instead of using apt, next time use aptitude -f install, reason is if
aptitude can not fix the problem it will give you a clue as what you can
do.  Also if you apt install and run 'upgrade-system' upgrade-system
will tell what to do, and clean your system too.


I thought aptitude was obsolated - never used it, but I think there was a
thread on the list about


In my post I should have said: Instead of using apt-get, next time use 
apt -f install or aptitude -f install because the newer apt is also 
verbose like aptitude is. Aptitude is old but still verbose. Personally 
I use all of Debian's tools and when there is a problem, the more 
verbose the better.


Interesting, both aptitude and gdebi got upgrades in the wee hours of my 
morning.  Thank you Debian. :)

--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

Re: Fwd: Bug Report

[Darac Marjal]

On Mon, Jan 15, 2018 at 11:31:02PM -0500, James Vibber wrote:

  -- Forwarded message --
  From: "James Vibber" <[1]jvibbe...@gmail.com>
  Date: Jan 15, 2018 10:54 PM
  Subject: Bug Report
  To: <[2]deb...@gmail.com>
  Cc:

  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
    apt libapt-pkg4.12 (due to apt) libc6 (due to apt) libgcc1 (due to apt) 
libstdc++6 (due to apt) gnupg (due to apt)
  base-passwd libdebconfclient0 (due to base-passwd) bash debianutils (due to 
bash) dash (due to
    bash) libncurses5 (due to bash) libtinfo5 (due to bash) bsdutils 
libsystemd0 (due to bsdutils) coreutils libacl1 (due to
  coreutils) libattr1 (due to coreutils) libselinux1 (due to coreutils) dpkg 
(due to dash)
    diffutils libbz2-1.0 (due to dpkg) liblzma5 (due to dpkg) zlib1g (due to 
dpkg) tar (due to dpkg) e2fsprogs e2fslibs (due
  to e2fsprogs) libblkid1 (due to e2fsprogs) libcomerr2 (due to e2fsprogs) 
libss2 (due to
    e2fsprogs) libuuid1 (due to e2fsprogs) util-linux (due to e2fsprogs) 
findutils grep libpcre3 (due to grep) gzip hostname
  init systemd-sysv (due to init) init-system-helpers perl-base (due to
    init-system-helpers) libc-bin login libaudit1 (due to login) libpam0g (due 
to login) libpam-runtime (due to login)
  libpam-modules (due to login) mount libmount1 (due to mount) libsmartcols1 
(due to mount)
    ncurses-bin sed sysvinit-utils startpar (due to sysvinit-utils) initscripts 
(due to util-linux) tzdata (due to util-linux)
  libslang2 (due to util-linux)
  43 upgraded, 33 newly installed, 1458 to remove and 172 not upgraded.
  4 not fully installed or removed.
  Need to get 29.6 MB/41.1 MB of archives.
  After this operation, 2407 MB disk space will be freed.
  You are about to do something potentially harmful.
  To continue type in the phrase 'Yes, do as I say!'
  ?] yes,do as I say!
  Abort.
  root@loc


Firstly, it's normal to accompany a bug report with some narrative. An 
isolated error message is not always useful to a developer. Adding "I 
was trying to install firefox and apt wanted to delete every other 
package' gives the developer some context. The above is akin to taking 
your car into a garage and pointed at the "Check Engine" light


Secondly, I presume you're sending the message to debian-user@l.d.o 
because you don't know which package to report the bug against. In my 
opinion, that depends on what, exactly, you're complaining about. Are 
you complaining that making some change to packages caused apt to try to 
remove essential packages (but if it was that, you'd have told us what 
changes you were trying to make, any why you were willing to remove 
them)?


Thirdly, (and I GUESS that this is why you're trying to report a bug), 
do YOU see a differenve between:


Yes, do as I say!

and

yes,do as I say!

?



References

  Visible links
  1. mailto:jvibbe...@gmail.com
  2. mailto:deb...@gmail.com


--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Fwd: Bug Report

[Greg Wooledge]

> >   WARNING: The following essential packages will be removed.
> >   This should NOT be done unless you know exactly what you are doing!
> >     apt libapt-pkg4.12 (due to apt) libc6 (due to apt) libgcc1 (due to apt) 
> > libstdc++6 (due to apt) gnupg (due to apt)
[...]

On Tue, Jan 16, 2018 at 01:31:39PM +, Darac Marjal wrote:
> Thirdly, (and I GUESS that this is why you're trying to report a bug), do
> YOU see a differenve between:
> 
>   Yes, do as I say!
> 
> and
> 
>   yes,do as I say!
> 
> ?

It's good that he failed to type it correctly.  His system would NOT
have survived had he confirmed this removal.

Re: Bug Report

[songbird]

David Wright wrote:
...
> Would it be better to upgrade jessie→stretch before stretch→buster?

  if that is what OP is doing, then yes, skipping
major versions has never been officially supported.

  at that stage it is often much more time efficient 
to re install from recent images.


  songbird

Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

[Pieter Van Isacker]

Hi all,

While testing change a Debian Wheezy from 32bit to 64bit I ran into an issue. 
Following the guide on https://wiki.debian.org/CrossGrading 

Once we've change to 64bit we plan to update to Debian 8 and then possibly to 
Debian 9

Changing the kernel to 64bit works fine, installing a 64bit version of dpkg, 
tar & apt also works fine.

But then when having to change the installed packages from 32bit to 64bit I ran 
into trouble.
When trying to run install vim for example:

# apt-get install vim
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 acpi-support-base : Depends: acpid (>= 1.0.4) but it is not going to be 
installed
 Recommends: consolekit but it is not going to be installed
 acpid:i386 : Depends: module-init-tools:i386 (> 3.1-rel-2) but it is not 
installable
  Recommends: acpi-support-base:i386 (>= 0.114-1) but it is not 
installable
 adduser : Depends: perl-base (>= 5.6.0) but it is not going to be installed
 ca-certificates : Depends: openssl (>= 1.0.0) but it is not going to be 
installed
 ca-certificates-java : Depends: openjdk-6-jre-headless (>= 6b16-1.6.1-2) but 
it is not going to be installed or
 java6-runtime-headless
Depends: libnss3 (>= 3.12.10-2~) but it is not going to 
be installed
 console-setup-linux : Depends: kbd (>= 0.99-12) or
console-tools (>= 1:0.2.3-16) but it is not 
going to be installed
 debconf : PreDepends: perl-base (>= 5.6.1-4) but it is not going to be 
installed
   Recommends: apt-utils (>= 0.5.1) but it is not going to be installed
 debconf-i18n : Depends: liblocale-gettext-perl but it is not going to be 
installed
Depends: libtext-iconv-perl but it is not going to be installed
Depends: libtext-charwidth-perl but it is not going to be 
installed
 facter : Depends: virt-what but it is not going to be installed
  Recommends: dmidecode but it is not going to be installed
 fai-client : Depends: perl but it is not going to be installed
  Depends: libapt-pkg-perl but it is not going to be installed
  Recommends: libgraph-perl but it is not going to be installed
 grub-pc:i386 : Depends: ucf:i386 but it is not installable
 initramfs-tools : Depends: klibc-utils (>= 2.0-1~) but it is not going to be 
installed
   Depends: cpio but it is not going to be installed
   Recommends: busybox (>= 1:1.01-3) but it is not going to be 
installed or
   busybox-initramfs but it is not installable or
   busybox-static but it is not going to be 
installed
 initscripts:i386 : Depends: sysv-rc:i386 but it is not installable or
 file-rc:i386 but it is not installable
 keyboard-configuration : Depends: liblocale-gettext-perl but it is not going 
to be installed
  Depends: initscripts but it is not going to be 
installed
 libaugeas-ruby : Depends: libaugeas-ruby1.9.1 but it is not going to be 
installed
 libaugeas0:i386 : Depends: augeas-lenses:i386 but it is not installable
 libjson-ruby : Depends: ruby-json but it is not going to be installed
 libpam-runtime : Depends: libpam-modules (>= 1.0.1-6) but it is not going to 
be installed
 libswitch-perl : Depends: perl but it is not going to be installed
 libtext-wrapi18n-perl : Depends: libtext-charwidth-perl but it is not going to 
be installed
 linux-base : Depends: libuuid-perl but it is not going to be installed
 module-init-tools : Depends: libkmod2 but it is not going to be installed
 nfs-common:i386 : Depends: ucf:i386 but it is not installable
   Recommends: python:i386 but it is not installable
 ntp:i386 : Depends: netbase:i386 but it is not installable
 perl:i386 : Depends: perl-modules:i386 (>= 5.14.2-21+deb7u5) but it is not 
installable
 Recommends: netbase:i386 but it is not installable
 perl-modules : Depends: perl (>= 5.14.2-1) but it is not going to be installed
 puppet-common : Depends: libopenssl-ruby or
  libopenssl-ruby1.9.1 or
  libruby (>= 1:1.9.3.4) but it is not going to be 
installed
 Depends: ruby-shadow but it is not going to be installed or
  libshadow-ruby1.8
 python : Depends: python2.7 (>= 2.7.3-1~) but it is not going to be installed
 python-minimal : Depends: python2.7-minimal (>= 2.7.3-1~) but it is not going 
to be installed
 python2.7:i386 : Depends: mime-support:i386 but it is not installable
 ruby : Depends: ruby1.9.1 (>= 1.9.3.194-1) but it is not going to be installed
 sysv-rc : Depends: sysvinit-utils (>= 2.86.ds1-62) but it is not going to be 
installed
   Depends

Re: Bug Report

[davidson]

On Tue, 16 Jan 2018, songbird wrote:


David Wright wrote:
...


Un-trimming some evidence:


On Mon 15 Jan 2018 at 23:27:30 (-0500), James Vibber wrote:

[...]

Unpacking libc6:armhf (2.26-2) over (2.19-18+deb8u10) ...


Would it be better to upgrade jessie???stretch before stretch???buster?


 if that is what OP is doing,


Judging by the libc6 versions, that is exactly what it looks like.


then yes, skipping major versions has never been officially
supported.

 at that stage it is often much more time efficient
to re install from recent images.


 songbird

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

[Sven Hartge]

Pieter Van Isacker  wrote:

> While testing change a Debian Wheezy from 32bit to 64bit I ran into an
> issue. Following the guide on https://wiki.debian.org/CrossGrading
>  Once we've change to 64bit we
> plan to update to Debian 8 and then possibly to Debian 9

You are better off first upgrading to Debian 9 and *then* trying to
crossgrade. The packages in Debian 9 are more prepared for multi-arch
than the one in Debian 7.

Still, there is no guarantee it will work and for production systems I
strongly advise you to just backup the data and reinstall from scratch
as 64bit system.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: To many repos??? No Public Key's!!

[davidson]

On Mon, 15 Jan 2018, Josh W. wrote:


So I posted about either having a faulty .iso and non-public keys.


In your previous thread,...

 
https://lists.debian.org/msgid-search/CAG9XMTsz4Ak+4=xvy_ogyufe61eeygf5k3jdb4rhp6nwsd6...@mail.gmail.com

... it looks like you included possibly important details in an
attached file that was not plain text. If you want people here to
examine what you post, post it in plain text format.

If cutting/pasting copious output is cumbersome or not possible, you
can write it to a file like so:

If, let's say, someone asked you to post the output of

 $ apt policy debian-archive keyring

then you could run this:

 $ apt policy debian-archive-keyring |& tee d-a-k_policy_for_jonathan

Any output would then be displayed as usual, and would also be written
to a file named "d-a-k_policy_for_jonathan", located in the current
directory. You could then include the contents of that file in your
message to debian-user (or attach it to your message).

Before running the command, do check the contents of the current
directory first, to make sure that you have chosen a destination
filename that does not already exist there (in the above example,
"d-a-k_policy_for_jonathan"). Otherwise the "tee" command will
overwrite it with the apt command's output and you will lose whatever
used to be there.

Likewise, if you cared to post any troubling messages that you see
when you run...

 $ sudo apt-get install wine

...then you could run something like the following instead, to save
the output to a file, by adding "|& tee FILENAME" to the end of your
command:

 $ sudo apt-get install wine |& tee install-wine.log

Speaking of output, I have yet to see posted in plain text:

 * precisely what commands produced error messages about public keys.

 * the output from those commands.

There is a lot of expertise on this list, but even experts need some
material to work with: materials like precisely what commands you
issued, and their output.

Messages that appear to be full of redundant pointless noise to you
might be very informative to others.


I've looked around in my /etc/apt/sources.list file. Maybe i have to
many repos or just not the right ones... I have tried netselect on a
bunch but not really getting any where. Here is the output of my
sources.list file as of now. I commented out the Oracle VM repo, the
"Also a Secondary" repo, and also the first repo under the cdrom
repo... When i tried the netselect it gave me ip address's that
didn't go anywhere. Not sure on what to do next... Can somebody
point me in the right direction.


You could begin by replying, in full, to this attempt to help you:

 https://lists.debian.org/msgid-search/1515499451.12102.2.ca...@debian.org

It is helpful, by the way, that you posted the contents of your
sources.list.

Good luck with your project.

--

P: C'est Darth Vader qui rentre dans une boulangerie. Il demande quoi
   à ton avis?
Q: ...
P: 3 pains et deux tartes tatins! Tu sais pourquoi?
Q: ...?
P: PAIN PAIN PAIN TARTE TATIN TARTE TATIN

Re: history issue - bug?

[Felipe Salvador]

On Sun, Jan 14, 2018 at 06:24:27PM +0100, Felipe Salvador wrote:
> On Sun, Jan 14, 2018 at 02:07:01PM +0100, Hans wrote:
> > Hi folks, 
> > 
> > try this:
> > 
> > 1. login as normal user
> > 
> > 2. become root with "su -"
> > 
> > 3. delete history with "history -c"
> 
> Then run "history -w" to "write the current history to the history
> file"

Maybe you could fill a bug report in order to ask if it is possible
change the history behaviour about -c and -w switches, actually it
doesn't accept this combination, you cannot use

$history -c -w  
or
$history -cw

You have to run separately

$history -c
AND
$history -w

Though I don't think this is a bug.


Regards
-- 
Felipe Salvador

Re: How to disable V6 DHCP ?

[Pierre Couderc]

On 01/15/2018 05:48 PM, Darac Marjal wrote:

On Mon, Jan 15, 2018 at 05:40:54PM +0100, Pierre Couderc wrote:

I have tried to comment INTERFACESv6 in /etc/default/isc-dhcp-server
but systemd  tries to start dhcp server ipV6, fails as it is not 
initiliased and remains in failed status, even if DSCP ipv4 is welle 
started.

But it refuses to start at next power on.


Have you tried setting INTERFACESv6=""?

Yes, thank you, it was the default after installation :
INTERFACESv4=""
INTERFACESv6=""





So how should I start DHCP v4 only... ?

Thanks in advance
PC

Re: Problem using "dpkg -i"

[deloptes]

Curt wrote:

> Obsolated: portmanteau of deprecated and obsolete?
> 
> I thought it was merely not recommended for upgrades.
> 

might be we check to see what is official statement on that

> PS: Have you ever performed 'apt-get moo'? (You don't need to be root.)
> Gives you a cow.
> 'aptitude moo' (if you persist by increasing the verbosity with ever more
> v's) produces a snake eating an elephant. Maybe that's why it may have
> been obsolated (illogical, Captain).
> 

that's really funny I never had time or desire to ask apt-get to make moo :D

> PSS:
> Knock knock.
> Who's there?
> The interruptive cow.
> The interruptive c...
> Moo!

$ apt-get moo
 (__)
 (oo)
   /--\/
  / |||
 *  /\---/\
~~   ~~
..."Have you mooed today?"...

:D :D :D :D :D :D :D :D :D :D :D :D

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

[deloptes]

Sven Hartge wrote:

> Still, there is no guarantee it will work and for production systems I
> strongly advise you to just backup the data and reinstall from scratch
> as 64bit system.

+1

copy data (backup)
dpkg --get-selections
install 64
dpkg --set-selections
migrate configurations

90% is planning

Re: Problem using "dpkg -i"

[Brian]

On Tue 16 Jan 2018 at 18:52:51 +0100, deloptes wrote:

> Curt wrote:
> 
> > Obsolated: portmanteau of deprecated and obsolete?
> > 
> > I thought it was merely not recommended for upgrades.
> > 
> 
> might be we check to see what is official statement on that

Section 4.4 of the Release Notes is probably as official as it gets:

https://www.debian.org/releases/stable/amd64/release-notes.en.txt

Should aptitude users really be bothered?

-- 
Brian.

Re: Secure email server setup

[Brian]

On Mon 15 Jan 2018 at 16:22:26 -0500, Henning Follmann wrote:

> On Mon, Jan 15, 2018 at 08:42:34PM +, Brian wrote:
> > On Mon 15 Jan 2018 at 14:51:56 -0500, Henning Follmann wrote:
> > 
> > > On Mon, Jan 15, 2018 at 08:34:33PM +0100, Jonathan Sélea wrote:
> > > > 
> > > > As other people already have said - do you really need emailserver of
> > > > this kind?
> > > 
> > > This however is a valid question. A full functional mailserver requires
> > > effort and administrative knowledge to setup properly. And your question
> > > already hints that the latter is no there yet.
> > 
> > All things computer-related require effort and administrative knowledge
> > to setup properly if anything out of the ordinary is being done. "do you
> > really need emailserver of this kind" is an indication of something bad
> > in the state of email.
> > 
> > Don't do it your way or take advantage of what the net provides appears
> > to be the message. Your intentions are verging on the incompetent, or,
> > maybe, you are bucking the trend, just use Google like everyone else
> > is the message.
> > 
> 
> Well,
> honestly I always thought it is very beneficial to run your own mailserver.
> But it is also one of the most difficult tasks to master. We have come a

Agreed. Although the Debian exim documentation makes an excellent
contribution to getting users off the ground.

> long way from setting up a sendmail server with its unique M4 syntax, but
> still you have to understand more than just setting up a smtp server. You
> need to understand DNS, SSL, TLS. You have to master at least one form of
> authentication method and avoid any possible relay desasters. 
> Because all this is potentially hard to understand. This was my thought

Agreed. There are many pitfalls to avoid.

> behind my comment. I would like to encourage anybody to try and set this
> up. However this will take some time before this should be practiced on an
> openly connected server.

Having a fully operating mail server is very satisfying but your point
is well-taken. The risk of mucking up a server for an important task is
not to be taken lightly.

-- 
Brian.

Re: scriptable way to list packages that are not installed

[davidson]

On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote:


Hi, John,

On Sun, Jan 14, 2018 at 8:48 AM, john doe  wrote:

On 1/14/2018 7:28 AM, john doe wrote:

$ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk
cmake 2>&1 | awk '!/^ii/ || !/^un/{print $6}'
git
gawk
cmake


I also tried to parse stderr, but then I realized that relying on the output

  dpkg-query: no packages found matching

is not correct since it might be localized and is not suitable for scripting.


You could just discard the stderr, and take the complement of the hits
from dpkg-query, relative to the supplied arguments:

show-installed () {
dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' "$@" |
awk '/^ii/ {print $2}'
}

show-absent () {
universe=("$@")
diff <( IFS=$'\n' ; sort <<<"${universe[*]}" ) \
<( show-installed "${universe[@]}" 2>/dev/null ) |
sed -n 's/^< //p'
}

$ dpkg-query -l not-a-real-package exim4 mksh xorg bash xterm chromium
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  bash   4.4-5amd64GNU Bourne Again 
SHell
un  exim4(no description 
available)
ii  mksh   54-2+b4  amd64MirBSD Korn Shell
ii  xorg   1:7.7+19 amd64X.Org X Window 
System
ii  xterm  327-2amd64X terminal emulator
dpkg-query: no packages found matching not-a-real-package
dpkg-query: no packages found matching chromium

$ show-installed !*
show-installed not-a-real-package exim4 mksh xorg bash xterm chromium
dpkg-query: no packages found matching not-a-real-package
dpkg-query: no packages found matching chromium
bash
mksh
xorg
xterm

$ show-absent !*
show-absent not-a-real-package exim4 mksh xorg bash xterm chromium
chromium
exim4
not-a-real-package

(It is above my pay grade to tell whether "sort" needs its flags
tweaked to sort identically to dpkg on arbitary package names.)

Re: scriptable way to list packages that are not installed

[davidson]

On Tue, 16 Jan 2018, davidson wrote:


On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote:


Hi, John,

On Sun, Jan 14, 2018 at 8:48 AM, john doe  wrote:

On 1/14/2018 7:28 AM, john doe wrote:

$ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk
cmake 2>&1 | awk '!/^ii/ || !/^un/{print $6}'
git
gawk
cmake


I also tried to parse stderr, but then I realized that relying on the 
output


  dpkg-query: no packages found matching

is not correct since it might be localized and is not suitable for 
scripting.


You could just discard the stderr, and take the complement of the hits
from dpkg-query, relative to the supplied arguments:

show-installed () {
   dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' "$@" |
   awk '/^ii/ {print $2}'
}

show-absent () {
   universe=("$@")
   diff <( IFS=$'\n' ; sort <<<"${universe[*]}" ) \
<( show-installed "${universe[@]}" 2>/dev/null ) |
   sed -n 's/^< //p'
}

$ dpkg-query -l not-a-real-package exim4 mksh xorg bash xterm chromium


Er, the history expansions entered at the two prompts below don't work
as shown, with the command line at the prompt immediately above.

If you must know, (and you don't, but I'll tell you anyway!) in
actuality I used a one-word alias defined as "dpkg-query -l", which
prevented the "-l" flag from getting included in the "!*" expansions.

Is there a natural law or something, that every email message sent
must contain at least one distracting error that is totally beside the
point?

Anyways, over and out.


Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  bash   4.4-5amd64GNU Bourne Again 
SHell
un  exim4(no description 
available)
ii  mksh   54-2+b4  amd64MirBSD Korn 
Shell
ii  xorg   1:7.7+19 amd64X.Org X Window 
System
ii  xterm  327-2amd64X terminal 
emulator

dpkg-query: no packages found matching not-a-real-package
dpkg-query: no packages found matching chromium

$ show-installed !*
show-installed not-a-real-package exim4 mksh xorg bash xterm chromium
dpkg-query: no packages found matching not-a-real-package
dpkg-query: no packages found matching chromium
bash
mksh
xorg
xterm

$ show-absent !*
show-absent not-a-real-package exim4 mksh xorg bash xterm chromium
chromium
exim4
not-a-real-package

(It is above my pay grade to tell whether "sort" needs its flags
tweaked to sort identically to dpkg on arbitary package names.)

Making a driver for the Matrox P650 card.

[peter]

An attempt to make the driver fails with the following log.
Is a solution feasible?  Debian has evolved too far for the P650?

Thanks,  ... Peter E.
=
Using kernel headers in /lib/modules/4.9.0-5-686-pae/build/include for kernel 
version 4.9.x
making all in /parhelia...
make[1]: Entering directory 
'/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory 
'/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia'
making all in /mtxvxd...
make[1]: Entering directory 
'/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/mtxvxd'
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxCpu.c -o MtxCpu.o
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxCs.c -o MtxCs.o
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxIo.c -o MtxIo.o
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxMem.c -o MtxMem.o
MtxMem.c: In function âĘmemFileAllocâę:
MtxMem.c:79:55: warning: passing argument 2 of âĘClientMemAllocâę makes 
integer from pointer without a cast [-Wint-conversion]
 pvChunk = ClientMemAlloc(dwSize + sizeof(UINT32), NULL);
   ^~~~
In file included from precomp.h:33:0,
 from MtxMem.c:19:
/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/mtx_client.h:41:30: note: 
expected âĘHREGION {aka long unsigned int}âę but argument is of type âĘvoid 
*âę
 EXTERN_C STACK_LINKAGE void* ClientMemAlloc(size_t size, HREGION region);
  ^~
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxPci.c -o MtxPci.o
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/parhelia/Main 
-I/lib/modules/4.9.0-5-686-pae/build/include 
-I/lib/modules/4.9.0-5-686-pae/build/include/asm/mach-default  -D__NO_VERSION__ 
-c MtxMap.c -o MtxMap.o
gcc   -DMEMORY_STATS=0  -DOS_LINUX -D__KERNEL__  -O2 -fomit-frame-pointer 
-finline-functions  -DMODULE 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include 
-I/home/guest/y/matroxdriver-x86_32-1.4.6/kernel/src/../include/mtxvxd 
-I

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 11:13:05 + (UTC)
Curt  wrote:

> On 2018-01-16, Michael Lange  wrote:
> >
> > To the OP: 
> > a quick web search showed another alternative that (iirc) has not been
> > mentioned before, see http://bluegriffon.org/ . I don't know anything
> > about this program, except that it appears to be commercial but open
> > source and they have a deb package available (which may or may not
> > work with debian) and it apparently can be used for free with a
> > somewhat reduced feature set. 
> 
>  Buy User's Manual
>  €7.50 (+VAT inside EU).
> 
> Software whose user manual is for sale; sign me up, please, that's for
> me!

Yes sure, I did not intend to advertise that app. 
But then, if you buy the "basic" license (for just 75.00 €) you get the
manual for free!! :-)

Still, if one is looking for such a tool there are not too many
competitors out there. If the free version is usable without buying the
manual I cannot tell (and I do not feel much inclination to find out).
And besides, I don't think we should condemn the developers because they
try to earn money with the work they are doing. Some way or other all of
us have to earn their living. At least they give away a free and open
source version of their app and sell the manual, I think that is better
than the other way around.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Without followers, evil cannot spread.
-- Spock, "And The Children Shall Lead", stardate 5029.5

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 18:52:51 +0100
deloptes  wrote:

> Curt wrote:
> > 
> > I thought it was merely not recommended for upgrades.
> > 
> 
> might be we check to see what is official statement on that

Maybe Curt refers to the following from
https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.en.html#upgradingpackages

"The recommended way to upgrade from previous Debian releases is to use
the package management tool apt-get. In previous releases, aptitude was
recommended for this purpose, but recent versions of apt-get provide
equivalent functionality and also have proven to more consistently give
the desired upgrade results. "

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4

Re: Making a driver for the Matrox P650 card.

[Dan Ritter]

On Tue, Jan 16, 2018 at 12:15:52PM -0800, pe...@easthope.ca wrote:
> An attempt to make the driver fails with the following log.
> Is a solution feasible?  Debian has evolved too far for the P650?
> 

I'm assuming you're trying to compile a driver from
http://www.matrox.com/graphics/en/support/drivers/download/certified/

because Debian only has support up through the 550 series.

Have you tried asking Matrox? They might have someone who 
can tell you definitively.

-dsr-

Re: Crossgrading Wheezy from 32bit to 64bit: Solving package dependency problems after kernel change.

[Michael Lange]

Hi,

On Tue, 16 Jan 2018 14:58:48 +0100
Pieter Van Isacker  wrote:

> Hi all,
> 
> While testing change a Debian Wheezy from 32bit to 64bit I ran into an
> issue. Following the guide on https://wiki.debian.org/CrossGrading
>  Once we've change to 64bit we
> plan to update to Debian 8 and then possibly to Debian 9

About two years ago, before upgrading from wheezy to jessie, I
successfully switched my system from 32 to 64 bit (after two failed
trials :)
When I had first started with the tips from the above link, the results
were desastrous :)
The advice from the following page:
http://blog.zugschlus.de/archives/972-How-to-amd64-an-i386-Debian-installation-with-multiarch.html
worked for me, although of course I cannot guarantee that they will work
for you either. And I'll have to add that I began to do as above page
instructed me only halfway into the process (when I had almost manoeuvered
myself into disaster again), so I cannot tell about the first half of that
page's instructions; the second half though surely saved my day back then.

Good luck (and don't forget to backup first!! :)

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3

Re: scriptable way to list packages that are not installed

[davidson]

On Tue, 16 Jan 2018, davidson wrote:


On Sun, 14 Jan 2018, Vasyl Vavrychuk wrote:


Hi, John,

On Sun, Jan 14, 2018 at 8:48 AM, john doe  wrote:

On 1/14/2018 7:28 AM, john doe wrote:

$ dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' awk git gawk
cmake 2>&1 | awk '!/^ii/ || !/^un/{print $6}'
git
gawk
cmake


I also tried to parse stderr, but then I realized that relying on the 
output


  dpkg-query: no packages found matching

is not correct since it might be localized and is not suitable for 
scripting.


You could just discard the stderr, and take the complement of the hits
from dpkg-query, relative to the supplied arguments:

show-installed () {
   dpkg-query -W -f='${db:Status-Abbrev}${binary:Package}\n' "$@" |
   awk '/^ii/ {print $2}'
}

show-absent () {
   universe=("$@")
   diff <( IFS=$'\n' ; sort <<<"${universe[*]}" ) \
<( show-installed "${universe[@]}" 2>/dev/null ) |
   sed -n 's/^< //p'
}


Further testing shows that the above has a lot of problems.

Would not recommend.

Sorry for the noise.

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/16/2018 04:17 AM, Michael Lange wrote:

[snip]

To the OP:
a quick web search showed another alternative that (iirc) has not been
mentioned before, see http://bluegriffon.org/ . I don't know anything
about this program, except that it appears to be commercial but open
source and they have a deb package available (which may or may not work
with debian) and it apparently can be used for free with a somewhat
reduced feature set.



That looks interesting. The only problem is I'm still using i386 flavor.

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 15:29:57 -0600
Richard Owlett  wrote:

> On 01/16/2018 04:17 AM, Michael Lange wrote:
> > [snip]
> > 
> > To the OP:
> > a quick web search showed another alternative that (iirc) has not been
> > mentioned before, see http://bluegriffon.org/ . I don't know anything
> > about this program, except that it appears to be commercial but open
> > source and they have a deb package available (which may or may not
> > work with debian) and it apparently can be used for free with a
> > somewhat reduced feature set.
> > 
> 
> That looks interesting. The only problem is I'm still using i386 flavor.

Maybe you could try to build from source? The instructions at 
https://github.com/therealglazou/bluegriffon
at a quick glance look quite detailed, and I assume you are not
interested in the expensive extra-features from the binary packages
anyway?

Or, the (maybe) easier way, try to pick one of the older releases from 
http://bluegriffon.org/freshmeat/ and see if one of these can be installed
and run on your system (2.3.1 appears to be the latest that comes with a
386 deb).

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, "Wolf in the Fold", stardate 3615.4

NFS4 file transfers fail or are very slow

[Michael]

Hello guys,

I have recently installed Debian Stretch 9.3 on a new PC and I'd just 
like to provide some NFS shares for other Linux machines in the LAN 
(1GBit). With small files everything works fine, but if I try to copy, 
e.g., a 7GB file with rsync it starts with a high transmission rate 
above 160MB/s and then goes down to around 70-90MB/s. After a random but 
short time there's no more progress going on for about 10-15 seconds. 
When the process then continues, the speed goes down to around 20MB/s 
and then up to about 200MB/s. It seems to continue transferring data, 
but rsync gives me an error message in the end.


On another client I experience the same, but there the last rate lies 
around 85MB/s instead of the 200MB/s from above. I guess this comes 
because the first PC has a SSD and the latter only a HDD. On the first 
client runs Arch Linux, on the latter ubuntu mate 16.04.
Exactly the same share is able to write more than 105MB/s via SMB/CIFS, 
so I would expect an NFS speed in a similar range.


My configurations files look as follows.

/etc/fstab on server:
/dev/disk/by-label/vol1  /vol1  ext4 
defaults,nofail,user_xattr,noexec,usrjquota=aquota.usr,grpjquota=aquota.grp,jqfmt=vfsv0,acl 
0 2

/vol1/temp  /export/temp  none  bind,nofail  0 0

/etc/exports on server:
/export/temp  192.168.192.0/24(fsid=1,rw,subtree_check,secure)
# NFSv4 pseudo filesystem root
/export 192.168.192.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)

/etc/default/nfs-kernel-server on server:
RPCNFSDCOUNT=64
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids"
NEED_SVCGSSD=
RPCSVCGSSDOPTS=

/etc/fstab on clients:
192.168.192.10:/temp  /mnt/temp  nfs 
rw,bg,intr,soft,users,noauto,_netdev,proto=tcp,retry=3,timeo=10  0 0


I tried different export and mount options, but nothing helped to get 
stable transfer. Sometimes the transmission finishes successfully, but 
with a low rate (<60MB/s).


What can cause this problem?

Best regards,
Michael

Re: Bluetooth devices get disconnected.

[Jiri Kanicky]

Hi,

So the issue was most likely related to iwlwifi modue (Network 
controller: Intel Corporation Wireless 8260 (rev 3a)). After adding the 
following options for iwlwifi the issue disappeared and the mouse is 
working fine.


$ cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8 led_mode=3

-Jiri


On 12/12/17 23:44, Jiri Kanicky wrote:

Hi.

I am running Debian Sid with KDE. I have Logitech MX 2 and Bose 
Bluetooth headphones. I experience disconnects very often.


I tried to use different configuration, but nothing seems to work.

After running the following the mouse gets connected again, and I can 
reconnect BT headphones also. However the devices get disconnected 
again in 1, 5 or 10 minutes again:

hciconfig hci0 sspmode 1
hciconfig hci0 down
hciconfig hci0 up

I also noticed that when the mouse is working I see the following:

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
    BD Address: 28:16:AD:B6:2A:0A  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING
    RX bytes:21923293 acl:792631 sco:0 events:111597 errors:0
    TX bytes:10619740 acl:18458 sco:0 commands:1832 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: SLAVE ACCEPT
    Name: 'supermanbt'
    Class: 0x1c010c
    Service Classes: Rendering, Capturing, Object Transfer
    Device Class: Computer, Laptop
    HCI Version: 4.2 (0x8)  Revision: 0x100
    LMP Version: 4.2 (0x8)  Subversion: 0x100
    Manufacturer: Intel Corp. (2)


After disconnect I can see the following:

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
    BD Address: 28:16:AD:B6:2A:0A  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:22096318 acl:800070 sco:0 events:113012 errors:0
    TX bytes:11042199 acl:19322 sco:0 commands:2053 errors:0
    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH SNIFF
    Link mode: SLAVE ACCEPT
    Name: 'Bluemoon Universal Bluetooth Host Controller'
    Class: 0x00
    Service Classes: Unspecified
    Device Class: Miscellaneous,
    HCI Version: 4.2 (0x8)  Revision: 0x100
    LMP Version: 4.2 (0x8)  Subversion: 0x100
    Manufacturer: Intel Corp. (2)

I also configured blutoothd with -d option, but I don't see any 
specific messages when the devices disconnect.


Any thoughts how to fix it or debug it? Is this general bluetooth 
issue or KDE bluedevil problem?


Thanks Jiri

Re: Making a driver for the Matrox P650 card.

[peter]

*   From: Dan Ritter d...@randomstring.org
*   Date: Tue, 16 Jan 2018 16:11:29 -0500
> I'm assuming you're trying to compile a driver from
> http://www.matrox.com/graphics/en/support/drivers/download/certified/

Yes, from that Web site, but the page notifies 
"There is no software available for download. 
Can't find what you're looing for?  Simply contact us."

To get an installer, I registered, logged in, traced through a 
hierarchy of menues to identify the requirement and ultimately got 
these files. 
mtxdriver-installer-x86_32-cvs-1.4.7.run
mtxdriver-installer-x86_32-cvs-1.4.6.run

Each of them contains an elaborate shell script followed by a binary 
archive.  "sh <...>.run" extracts the archive and proceeds to attempt 
making the driver.  The log in my previous message is from 1.4.6 
whereas 1.4.7 fails earlier in the script.

> Have you tried asking Matrox? They might have someone who 
> can tell you definitively.

Just submitted a request.  Will report later.

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

Re: scriptable way to list packages that are not installed

[Charlie Gibbs]

On 16/01/18 12:15 PM, david...@freevolt.org wrote:


Is there a natural law or something, that every email message sent
must contain at least one distracting error that is totally beside the
point?

Anyways, over and out.


"Over" means "My transmission is finished; I expect a reply."
"Out" means "My transmission is finished; I do not expect a reply."

One more distracting error... :-)

--
cgi...@surfnaked.ca (Charlie Gibbs)

Re: scriptable way to list packages that are not installed

[The Wanderer]

On 2018-01-16 at 21:17, Charlie Gibbs wrote:

> On 16/01/18 12:15 PM, david...@freevolt.org wrote:
> 
>> Is there a natural law or something, that every email message sent
>> must contain at least one distracting error that is totally beside the
>> point?
>>
>> Anyways, over and out.
> 
> "Over" means "My transmission is finished; I expect a reply."
> "Out" means "My transmission is finished; I do not expect a reply."
> 
> One more distracting error... :-)

I usually think of "Over and out" as being effectively equivalent to
"You can respond if you want to, but I'm not going to be listening".

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: scriptable way to list packages that are not installed

[John Hasler]

The Wanderer writes:
> I usually think of "Over and out" as being effectively equivalent to
> "You can respond if you want to, but I'm not going to be listening".

If I say that I mean "I am done transmitting.  I will listen for your
final transmission."  If you have nothing more to say you should respond
with "Roger  Out" or possibly just "Out."

If I was done transmitting and did not expect a reply I would simply end
my transmission with "Out." You would then not respond at all.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

[no subject]

[josh cha]

Hello again. Too all the debain users.
I realised linksys AE6000 wifi usb SUPPORT IS DEAD LOL or maybe im not
checking the right places. Other wise is there a usb wifi that i can buy
That is compatible to debian.