Re: How to react on a factually wrong Debian wiki change ?

[Thomas Schmitt]

Hi,

Curt wrote:
> I thought nobody said "should better not be used," but sticking that quoted
> phrase in a search engine produces over 12,000 hits.

12 thousand is not much. Popular germanisms get more. We are busy
spoilers of english language.



After considering all proposals made so far, and the statements in
Steve McIntyre's mail, i inow wrote in the wiki

  wodim should not be used with DVD or BD media.
  [[https://lists.debian.org/debian-user/2018/09/msg01078.html|
This statement is supported by wodim's maintainer.]]

Edit comment is:
  Hopefully final statement on wodim with DVD or BD media.
  Backed by maintainer of wodim.

Steve agreed to my statement with the word "better" in it. That word was
not essential to the advise. So i dropped it.


Have a nice day :)

Thomas

Re: Scribus has stopped importing PDF files - repost - original thread was hijacked

[mick crane]

On 2018-09-26 19:45, Gary Dale wrote:

For the last few days, some Scribus documents I work with have stopped
accepting PDF files within image frames. Prior to this, they would
display a preview. Now new image frames that I create show just the
file name, but some older frames within the document still show the
preview.

When I export the document as a PDF, the frames that just display the
file name export as empty/blank. The older frame that shows a preview
causes the export to stop with an error saying it was unable to load
the image.

I'm not sure if this is related to something in the PDFs or not.
However it is happening on two documents I am working on.



problems with PDFs come up occasionally on the scribus list.
Did you have a look through archives there ?

Scribus Mailing List: scri...@lists.scribus.net
Edit your options or unsubscribe:
http://lists.scribus.net/mailman/listinfo/scribus
See also:
http://wiki.scribus.net
http://forums.scribus.net



mick

--
Key ID4BFEBB31

Re: is it possible to install previous mplayer

[Brian]

On Mon 01 Oct 2018 at 13:08:10 +0800, Li Wei wrote:

> i've installed jessie
> instead of installing jessie's mplayer, can i install wheezy's mplayer?

You could try.

1. Comment out all entries in /etc/apt/sources.list and add a single
   entry for a wheezy archive.

2. Purge mplayer if it is on the system.

3. apt update

4. apt install mplayer

5. Return sources.list to its previous state.

-- 
Brian.

(solved) Re: is it possible to install previous mplayer

[Li Wei]

On 10/1/18, Brian  wrote:
> You could try.
>
> 1. Comment out all entries in /etc/apt/sources.list and add a single
>entry for a wheezy archive.
>
> 2. Purge mplayer if it is on the system.
>
> 3. apt update
>
> 4. apt install mplayer
>
> 5. Return sources.list to its previous state.
>
> --
> Brian.
>
>

Thank Brian!
i've made such attempt a few years ago.
it isn't successful. there may be some conflict with other package

ACPI wrong battery information (kernel 4.18)

[debian]

Hi,

I've made a fresh installation of debian testing on my ASUS eeepc x101.
ACPI reports wrong battery informations. If I type acpi -V:

$ acpi -V
Battery 0: Discharging, 100%, 4200:00:00 remaining
Battery 0: design capacity 4300 mAh, last full capacity 4200 mAh = 97%
Adapter 0: off-line
Thermal 0: ok, 60.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 90.0
degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 88.0
degrees C
Cooling 0: Processor 0 of 10
Cooling 1: LCD 8 of 10
Cooling 2: Processor 0 of 10

$ uname -a
Linux x101 4.18.0-1-amd64 #1 SMP Debian 4.18.6-1 (2018-09-06) x86_64
GNU/Linux

$ cat /etc/debian_version 
buster/sid


But, if I use the 4.14 kernel acpi works fine:

$ acpi -V
Battery 0: Discharging, 30%, 01:32:16 remaining
Battery 0: design capacity 4400 mAh, last full capacity 4323 mAh = 98%
Adapter 0: off-line
Thermal 0: ok, 60.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 90.0
degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 88.0
degrees C
Cooling 0: Processor 0 of 10
Cooling 1: LCD 8 of 10
Cooling 2: Processor 0 of 10

$ uname -a
Linux x101 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64
GNU/Linux


This may be a bug in acpi package? linux-image package...?

Greetings

Re: SVG in SVG.

[peter]

Reco,

Thanks for the reply.

From: Reco 
Date: Mon, 1 Oct 2018 09:48:21 +0300
> 8.5/11 = .7727272...
> 765/990 = .7727272...

OK

> So rsvg-convert seem to preserve aspect ratio.

OK.

> 8.5*90 = 765
> 11*90 = 990

OK.

> You define actual size by specifying (or using default) DPI.

OK.

Also FWIIW (270 mm/25.4 mm/in) x 90 px/in ~= 956.69 px (?)
and (349 mm/25.4 mm/in) x 90 px/in ~= 1236.61 px (?)
and 270/349 = .7736390 ~= .7727272   8~) (aspect ratio again)
and 270/90 = 3 .   8~)

Sorry for being dense.  3 is a nice whole number but I still haven't 
found how Document Viewer derives the numbers "270 x 349". 

Regards,   ... Peter E.
-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Not finding openssl during a pkg build (mailsend)

[Harry Putnam]

cat /etc/debian_version
9.4

Summary:

Trying to compile a tool called `mailsend'
 (https://github.com/muquit/mailsend/releases/)

(Which does not appear to be available in the regular repo).

But cannot get it to find openssl.

I do have openssl and libssl-dev installed;

---   ---   ---=---   ---   ---

Details

A check of apt-get search openssl

A quick check of ./configure file suggests using:


 grep [\-]-with.*openssl ./configure
  --with-openssl=PATH where the root of OpenSSL is installed
  --with-openssl-includes where the OpenSSL includes are.
  --with-openssl-libraris where the OpenSSL library is installed.

I tried --with-openssl=/usr/bin/openssl

  and
  --with-openssl=/usr/lib/ssl

  and
  --with-openssl-includes=/usr/include/openssl

using dpkg -L and `grep -v' (to keep down the amount of data) shows:

  dpkg -L openssl |grep -v share
  
  /etc
  /etc/ssl
  /etc/ssl/certs
  /etc/ssl/openssl.cnf
  /etc/ssl/private
  /usr
  /usr/bin
  /usr/bin/c_rehash
  /usr/bin/openssl
  /usr/lib
  /usr/lib/ssl
  /usr/lib/ssl/misc
  /usr/lib/ssl/misc/CA.pl
  /usr/lib/ssl/misc/tsget
  /usr/lib/ssl/certs
  /usr/lib/ssl/openssl.cnf
  /usr/lib/ssl/private

and
  dpkg -L libssl-dev  (95 lines of output omitted)


Are there other parts of openssl I need to install?


I'm not figuring out how to direct this build toward openssl, but the
configure process continues to show:

  [...]

  checking for OpenSSL... no

  [...]

Re: Not finding openssl during a pkg build (mailsend)

[Greg Wooledge]

On Mon, Oct 01, 2018 at 12:47:01PM -0400, Harry Putnam wrote:
> cat /etc/debian_version
> 9.4

> I do have openssl and libssl-dev installed;

In stretch, libssl-dev is the development package for OpenSSL version 1.1.
This is a relatively new version of OpenSSL, and it is not compatible with
version 1.0.

Most programs that use OpenSSL will be expecting to use the version 1.0 API.
I don't know your particular program, but it's a reasonable guess that
it wants the older version.

Try installing libssl1.0-dev (which will remove libssl-dev) and see if that
works.  You can switch back and forth as needed when compiling various
programs, but you can't have both installed at the same time.

Re: SVG in SVG.

[Reco]

On Mon, Oct 01, 2018 at 08:54:43AM -0700, pe...@easthope.ca wrote:
> Reco,
> 
> Thanks for the reply.
> 
> From: Reco 
> Date: Mon, 1 Oct 2018 09:48:21 +0300
> > 8.5/11 = .7727272...
> > 765/990 = .7727272...
> 
> OK
> 
> > So rsvg-convert seem to preserve aspect ratio.
> 
> OK.
> 
> > 8.5*90 = 765
> > 11*90 = 990
> 
> OK.
> 
> > You define actual size by specifying (or using default) DPI.
> 
> OK.
> 
> Also FWIIW (270 mm/25.4 mm/in) x 90 px/in ~= 956.69 px (?)
> and (349 mm/25.4 mm/in) x 90 px/in ~= 1236.61 px (?)

Here's your mistake. rsvg-convert assumes 90 DPI by default, and it can
be changed by the user if needed.

In the case of Evince ("Document Viewer" in GNOME-speak), 72 DPI is
assumed and hardcoded (see shell/ev-window.c and libview/ev-view.c for
some examples) without any possibility of user changes.
Note that libpoppler - the library that evince uses to render PDF - does
not make such assumptions, it's all pixels for them.

Therefore, 765 pixels equals 269.88 GNOME millimeters and 10.63 GNOME
inches.
Likewise, 990 pixels equals 349.25 GNOME millimeters and exactly 13.75
GNOME inches.

Note that all those mm and inches are not the units of measurement we
common people are accustomed for. They are special GNOME units of
measurement, hence your confusion.


> Sorry for being dense.

I see nothing to be sorry for. They say that mathematics is the
universal language for a reason :)

Reco

Re: (solved) Re: is it possible to install previous mplayer

[deloptes]

Li Wei wrote:

> Thank Brian!
> i've made such attempt a few years ago.
> it isn't successful. there may be some conflict with other package

sure there will be, why would you need mplayer for wheezy?

Re: (solved) Re: is it possible to install previous mplayer

[Li Wei]

On 10/2/18, deloptes  wrote:
>
> sure there will be, why would you need mplayer for wheezy?
>

mencoder of jessie doesn't have some feature I need
I can't use option vcodec=mpeg4
both wheezy and stretch have such option.

Re: (solved) Re: is it possible to install previous mplayer

[Brian]

On Mon 01 Oct 2018 at 20:08:26 +0200, deloptes wrote:

> Li Wei wrote:
> 
> > Thank Brian!
> > i've made such attempt a few years ago.
> > it isn't successful. there may be some conflict with other package
> 
> sure there will be, why would you need mplayer for wheezy?

You've been around long enough to know that users want all sort of
things; warranted or not.

More to the point is that I have installed mplayer from wheezy on
unstable after following my own excellent advice. Took all of five
minutes. So why not jessie --> wheezy is the question in my mind?

-- 
Brian.

Re: (solved) Re: is it possible to install previous mplayer

[Teemu Likonen]

Li Wei [2018-10-02 02:40:39+08] wrote:

> mencoder of jessie doesn't have some feature I need
> I can't use option vcodec=mpeg4
> both wheezy and stretch have such option.

Obviously I don't know all your needs but how about this?

mencoder -ovc lavc -lavcopts vcodec=mpeg4

"mpeg4" is actually the default value for "-lavcopts vcodec". I'm
talking of mplayer package version 2:1.3.0-6 in Debian 9.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: (solved) Re: is it possible to install previous mplayer

[deloptes]

Li Wei wrote:

> mencoder of jessie doesn't have some feature I need
> I can't use option vcodec=mpeg4
> both wheezy and stretch have such option.

why not try backport from stretch if available?

Re: (solved) Re: is it possible to install previous mplayer

[Teemu Likonen]

Teemu Likonen [2018-10-01 21:56:53+03] wrote:

> Li Wei [2018-10-02 02:40:39+08] wrote:
>> mencoder of jessie doesn't have some feature I need
>> I can't use option vcodec=mpeg4
>> both wheezy and stretch have such option.
>
> Obviously I don't know all your needs but how about this?
>
> mencoder -ovc lavc -lavcopts vcodec=mpeg4

It seems that I got confused about those Debian codenames and my advice
is useless. Sorry.

(Release codenames stopped making sense to me around Debian 5 (Lenny). I
have not been able to sort the later releases in my mind.)

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: (solved) Re: is it possible to install previous mplayer

[Brian]

On Mon 01 Oct 2018 at 21:04:15 +0200, deloptes wrote:

> Li Wei wrote:
> 
> > mencoder of jessie doesn't have some feature I need
> > I can't use option vcodec=mpeg4
> > both wheezy and stretch have such option.
> 
> why not try backport from stretch if available?

In a previous message:

 > Thank Brian!
 > i've made such attempt a few years ago.

Notice that Li Wei didn't say that he had followed the advice given. He
was relying on memory and did not test. Never a good thing.

Wheezy's mplayer will install on unstable. Conclusion?

-- 
Brian.

Re: (solved) Re: is it possible to install previous mplayer

[deloptes]

Brian wrote:

> More to the point is that I have installed mplayer from wheezy on
> unstable after following my own excellent advice. Took all of five
> minutes. So why not jessie --> wheezy is the question in my mind?

I am just curious - that is all - and it brings fruits - it is long time
since I played with encoding or recoding files with mencoder, so it looks
like we missed something that Li Wei found out. I use recently ffmpeg for
re-encoding.

regards

No sound after installing debian

[ilovecountrymusic483]

Hi all,  I am a blind user of Debian and have made several attempts to
install Debian both stretch and testing with the same strange problem.  I
have speech during the install prosses and the system installs with no
problem.  How ever after booting into the new system the speech is not
there.  I tried going to alsamixer with root access and razing the sound
valume with no luck.  This happens both with the alfa and stable installs.
I tried with both isos installing with a gnome install as well as a mate
install.  I don't recall ever having this problems with this.  I do not have
any bare bones system to try with so using a virtual machine.  Any one here
have any ideas on how to rectify getting speech back aftr installing.  

 

Thanks again.

 

Matthew

 

 

beep.c race condition

[Stefan Helmert]

Hello,

I hope this may be helpfull:

https://github.com/TheTesla/beep/commit/3ac3c7e8d38e6ac6b1427aed74a579f5b7485cb2

Re: all files moved to lost+found

[Beco]

On Sun, 30 Sep 2018 at 15:25, David Christensen 
wrote:

>
> Download and run Seagate's diagnostic tool on the 2 TB drive:
>
> https://www.seagate.com/support/downloads/seatools/
>
> (I have been using the bootable CD image for years ("legacy"), but it
> looks like they finally have a bootable USB image.)
>
> Use a camera and take pictures of the various screens.  Transcribe them
> into a reply to this list.
>
>
>
>
Dear David, hi guys/girls that are following this problem.

First, the delay in my response is due to the fact that I'm fighting a lot
of parallel battles here, but I'm still trying to solve this problem.
In the next days I'll always try to reply.

I've done the bootable seagate HD test. It came up 100% ok, all tests. The
HD is new, I wouldn't expect different, but it is always reassuring to do
the real test and see the results.

To recap, I used the computer all day, since morning until late night. From
time to time, say, about 3 times that day, I noticed a small 5 seconds long
freeze. Sometimes, in other days, KDE wouldn't open plasmashell, but I did
not need to reboot; just open tty1, and run systemctl restart sddm, and it
would run ok. Not sure if this is related.

That night, I turned off the computer, no errors, nothing.

Next morning, first boot, it booted fast and I was faced with an empty
desktop. Also empty /home. After e2fsck, all my files reappeared as inode
numbers in lost+found. I was able to recover some of them, and I have
backup for others. But I'm not still putting them on the hard disk.

I'm still waiting for possible causes or solutions, or just to know what
have happened in the first place.

Is the "swap" partition something that could cause that if turned off by
"swapoff"? Because I remember turning it off during that afternoon. But I
used the computer a LOT until night, so, I don't think there was any link
to the disappearance of ALL files. Also, when I used swapoff, it was almost
without use anyway.

I read above from Abdullah, that it is very unlike to have such major FS
fail, and it looks like it didn't "flush" the night I turned off. This is
also my guess, it is the only thing that make sense. Maybe the inode table
was in the memory and got corrupted. But it is strange to figure that,
since the filesystem is EXT4, and it is very stable nowadays.

Someonelse asked if 2TB is ok for this laptop, Causey I believe, my inbox
got deleted, but yes, this configuration accepts a 2TB; also, this would be
a problem during the installation 3 months ago, and the consequences would
be far different from the reported problem here.

Thanks all for inputs and lets reason what else. I may be able to create a
virtualbox to test some theories in the future, to get to the bottom of it.
The laptop is still in guarantee period, I need to know if there is
something really wrong or if it was just an occasional, yet rare, event.

My best,

Beco


PS. Sorry for not copying Abdullah and Causey on the reply, my inbox got
cleaned here.

-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Re: all files moved to lost+found

[David Christensen]

On 10/1/18 5:31 PM, Beco wrote:

On Sun, 30 Sep 2018 at 15:25, David Christensen 
wrote:



Download and run Seagate's diagnostic tool on the 2 TB drive:

https://www.seagate.com/support/downloads/seatools/

(I have been using the bootable CD image for years ("legacy"), but it
looks like they finally have a bootable USB image.)

Use a camera and take pictures of the various screens.  Transcribe them
into a reply to this list.





Dear David, hi guys/girls that are following this problem.

First, the delay in my response is due to the fact that I'm fighting a lot
of parallel battles here, but I'm still trying to solve this problem.
In the next days I'll always try to reply.

I've done the bootable seagate HD test. It came up 100% ok, all tests. The
HD is new, I wouldn't expect different, but it is always reassuring to do
the real test and see the results.

To recap, I used the computer all day, since morning until late night. From
time to time, say, about 3 times that day, I noticed a small 5 seconds long
freeze. Sometimes, in other days, KDE wouldn't open plasmashell, but I did
not need to reboot; just open tty1, and run systemctl restart sddm, and it
would run ok. Not sure if this is related.

That night, I turned off the computer, no errors, nothing.

Next morning, first boot, it booted fast and I was faced with an empty
desktop. Also empty /home. After e2fsck, all my files reappeared as inode
numbers in lost+found. I was able to recover some of them, and I have
backup for others. But I'm not still putting them on the hard disk.

I'm still waiting for possible causes or solutions, or just to know what
have happened in the first place.

Is the "swap" partition something that could cause that if turned off by
"swapoff"? Because I remember turning it off during that afternoon. But I
used the computer a LOT until night, so, I don't think there was any link
to the disappearance of ALL files. Also, when I used swapoff, it was almost
without use anyway.

I read above from Abdullah, that it is very unlike to have such major FS
fail, and it looks like it didn't "flush" the night I turned off. This is
also my guess, it is the only thing that make sense. Maybe the inode table
was in the memory and got corrupted. But it is strange to figure that,
since the filesystem is EXT4, and it is very stable nowadays.

Someonelse asked if 2TB is ok for this laptop, Causey I believe, my inbox
got deleted, but yes, this configuration accepts a 2TB; also, this would be
a problem during the installation 3 months ago, and the consequences would
be far different from the reported problem here.

Thanks all for inputs and lets reason what else. I may be able to create a
virtualbox to test some theories in the future, to get to the bottom of it.
The laptop is still in guarantee period, I need to know if there is
something really wrong or if it was just an occasional, yet rare, event.

My best,

Beco


PS. Sorry for not copying Abdullah and Causey on the reply, my inbox got
cleaned here.


If Seagate Seatools is happy with the 2 TB drive, that should eliminate 
the 2 TB drive, the cable, and the motherboard port as sources of the 
problem.



Just to be thorough, you should also check memory.  I've been using 
memtest86+ for years, but other people say there a better choices. 
STFW, pick one you like, download it, and run it.



STFW "lenovo ideapad 320", I see that there are many variants of that 
model.  However, I am unable to find technical specifications or a 
service manual.  Please post a description of the machine, the specific 
Lenovo part number/ whatever, and a URL to the exact same computer (if 
available).  If you have a URL for technical specifications and/or 
service manual, please post those.



Please run the following commands as root and post your complete console 
session (prompts, commands, and output):


# cat /etc/debian_version

# uname -a

# parted --list

# mount

# swapon

# df

# cat /etc/apt/sources.list

# ls /etc/apt/sources.list.d/

# cat /etc/apt/sources.list.d/*


Have you installed any software using means other than the Debian 
built-in package management tools?  E.g. download a source tarball, 
build it, install it; download a *.deb package and install it; etc.?



Have you changed, recompiled, or otherwise messed with the kernel?


David

Re: all files moved to lost+found

[David Christensen]

On 10/1/18 8:40 PM, Abdullah Ramazanoğlu wrote:

On Mon, 1 Oct 2018 19:06:20 -0700 David Christensen said:
  

If Seagate Seatools is happy with the 2 TB drive, that should eliminate
the 2 TB drive, the cable, and the motherboard port as sources of the
problem.


I'm not sure how an on-disk cache problem could definitively be caught without
power cycling. What if on-disk controller is ignoring all cache related
commands? (cache bypass, cache invalidate, cache flush)


I must depend upon Seagate to get their firmware and their diagnostics 
right.  If their firmware were so bad as to ignore all cache related 
commands, we'd probably hear about it.



Every disk that I have seen fail the manufacturer's diagnostic has also 
exhibited bad behavior in whatever computer it occupied.



But, the contrary is not true.  When it is false (e.g. bad behavior, 
passes diagnostic), either I'm confused, some other part of the computer 
is having issues, or both.  (PEBKAC is a common root cause.)



Then again, as the OP's computer seems to be a newer model, some 
hardware could be unsupported and/or the supporting device drivers could 
be incomplete and/or buggy.  I know Intel provides reference FOSS 
drivers for their stuff; does AMD?  Without a shopping list of the key 
chips in the OP's computer, there is no way to check support status.



David

Re: all files moved to lost+found

[David Christensen]

On 10/1/18 9:07 PM, Abdullah Ramazanoğlu wrote:

On Mon, 1 Oct 2018 21:31:27 -0300 Beco said:


I've done the bootable seagate HD test. It came up 100% ok, all tests. The
HD is new, I wouldn't expect different, but it is always reassuring to do
the real test and see the results.


I am not familiar with seatools, but there are usually destructive and
non-destructive test suites in such tools. I hope you have run a destructive
one (which destroys data on disk) as some marginal errors can only be caught by
destructive tests.


The only destructive test I recall from SeaTools is writing zeros to the 
disk.  Of course, you don't want to do that until the data recovery 
effort is complete. And, the OP seems to be ignoring recovery and still 
trying to use the drive (!).




Is the "swap" partition something that could cause that if turned off by
"swapoff"?


I don't think so.


+1



I read above from Abdullah, that it is very unlike to have such major FS
fail, and it looks like it didn't "flush" the night I turned off. This is
also my guess, it is the only thing that make sense. Maybe the inode table
was in the memory and got corrupted. But it is strange to figure that,
since the filesystem is EXT4, and it is very stable nowadays.


I'm not sure how much isolation the various parts of the Linux kernel 
now have from each other.  In the bad old days of monolithic kernels, 
everything inside the kernel could touch everything else in the kernel. 
A buggy driver in one subsystem could wreak havoc in any other subsystem.




But the journal is passing through on-disk controller, too. If the drive is
mishandling its on-drive cache, then an FS corruption is still possible. Even
if journal writes are "direct", the drive could be ignoring that (i.e. caches
it nevertheless) without flushing it prior to power-off, corrupting the journal
as well.

If the FS survives through reboots, but falters when the laptop is power
cycled, then a cache flush issue is still probable.

Another test method might be hibernation. If resume from hibernation works,
then that rules out on-disk caching problem.

Regards


Hypotheses require experiments to confirm or refute them.


The chicken-and-egg problem is to get some solid data to start with. 
We'll see if the OP responds to my shopping list of requested commands.



David