Re: MTP devices leave multiple copies under Devices in file managers

2018-01-07 Thread Ben Caradoc-Davies

On 08/01/18 02:28, Carl Fink wrote:

On 01/06/2018 03:06 PM, Ben Caradoc-Davies wrote:

What kernel version? Do the entries disappear on reboot?

This morning I had time to reboot, and I can now confirm that
rebooting cleared the dead entries. It sure looks like the
already-reported bug.
Thanks for the pointer--it never occurred to me to look for a kernel
bug because I don't know the underpinnings of the process (MTP
mountpoints?) and wasn't aware that a kernel process (module?) was
involved. Much appreciated.


It is not certain that it is a kernel bug, but when I booted into a 4.13 
kernel, it was not present. There are a few other things in the initrd 
that might cause the problem, and it might be that a kernel change has 
revealed a bug elsewhere, such as a library. I am sure that kernel 
experts can figure it out.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand



Black screen on boot after upgrade to 4.9.0-4 & 4.9.0-5 kernels

2018-01-07 Thread Michael Yartsev
Hello,

I have been using the 4.9.0-3 kernel just fine on my Asus UX306U laptop,
but when I attempt to boot with 4.9.0-34 or 4.9.0-35, they both boot to a
black screen.
Here's a sample of the errors in the kernel log files.

Appreciate any help! And let me know if further information is useful.


Jan  7 17:31:12 phoenix kernel: [1.812973]  [] ?
fbcon_init+0x570/0x600
Jan  7 17:31:12 phoenix kernel: [1.812975]  [] ?
visual_init+0xcf/0x130
Jan  7 17:31:12 phoenix kernel: [1.812976]  [] ?
do_bind_con_driver+0x1cf/0x3b0
Jan  7 17:31:12 phoenix kernel: [1.812977]  [] ?
do_take_over_console+0x10e/0x170
Jan  7 17:31:12 phoenix kernel: [1.812979]  [] ?
do_fbcon_takeover+0x58/0xb0
Jan  7 17:31:12 phoenix kernel: [1.812981]  [] ?
notifier_call_chain+0x45/0x70
Jan  7 17:31:12 phoenix kernel: [1.812983]  [] ?
__blocking_notifier_call_chain+0x41/0x60
Jan  7 17:31:12 phoenix kernel: [1.812984]  [] ?
register_framebuffer+0x212/0x360
Jan  7 17:31:12 phoenix kernel: [1.812986]  [] ?
vga_switcheroo_client_fb_set+0x19/0x70
Jan  7 17:31:12 phoenix kernel: [1.812990]  [] ?
drm_fb_helper_initial_config+0x29e/0x440 [drm_kms_helper]
Jan  7 17:31:12 phoenix kernel: [1.813015]  [] ?
intel_fbdev_initial_config+0x14/0x30 [i915]
Jan  7 17:31:12 phoenix kernel: [1.813017]  [] ?
async_run_entry_fn+0x34/0x140
Jan  7 17:31:12 phoenix kernel: [1.813018]  [] ?
process_one_work+0x184/0x410
Jan  7 17:31:12 phoenix kernel: [1.813019]  [] ?
worker_thread+0x4d/0x490
Jan  7 17:31:12 phoenix kernel: [1.813021]  [] ?
process_one_work+0x410/0x410
Jan  7 17:31:12 phoenix kernel: [1.813022]  [] ?
kthread+0xd7/0xf0
Jan  7 17:31:12 phoenix kernel: [1.813024]  [] ?
kthread_park+0x60/0x60
Jan  7 17:31:12 phoenix kernel: [1.813026]  [] ?
ret_from_fork+0x41/0x50
Jan  7 17:31:12 phoenix kernel: [1.813027] ---[ end trace
d2b9d5cf9a51e9b6 ]---
Jan  7 17:31:12 phoenix kernel: [1.813028] [ cut here
]
Jan  7 17:31:12 phoenix kernel: [1.813051] WARNING: CPU: 3 PID: 106 at
/build/linux-4.9.65/drivers/gpu/drm/i915/intel_pm.c:3720 skl_compute_w$
Jan  7 17:31:12 phoenix kernel: [1.813052]
WARN_ON(!intel_pstate->base.fb)
Jan  7 17:31:12 phoenix kernel: [1.813068] Modules linked in:
i2c_designware_platform(+) i2c_designware_core asus_nb_wmi(+) asus_wmi
sparse_k$
Jan  7 17:31:12 phoenix kernel: [1.813082]  mei intel_pch_thermal
intel_soc_dts_iosf btintel intel_lpss_pci bluetooth wmi int3403_thermal rfk$
Jan  7 17:31:12 phoenix kernel: [1.813084] CPU: 3 PID: 106 Comm:
kworker/u8:2 Tainted: GW   4.9.0-5-amd64 #1 Debian
4.9.65-3+deb9$
Jan  7 17:31:12 phoenix kernel: [1.813084] Hardware name: ASUSTeK
COMPUTER INC. UX305UAB/UX305UAB, BIOS UX305UAB.201 04/14/2016
Jan  7 17:31:12 phoenix kernel: [1.813086] Workqueue: events_unbound
async_run_entry_fn
Jan  7 17:31:12 phoenix kernel: [1.813087]  
94529964 a4d0c105b910 
Jan  7 17:31:12 phoenix kernel: [1.813089]  9427662e
8bb36738b400 a4d0c105b968 8bb36934daa8
Jan  7 17:31:12 phoenix kernel: [1.813090]  8bb3680603c8
8bb368460800 0001 942766af
Jan  7 17:31:12 phoenix kernel: [1.813090] Call Trace:
Jan  7 17:31:12 phoenix kernel: [1.813092]  [] ?
dump_stack+0x5c/0x78
Jan  7 17:31:12 phoenix kernel: [1.813094]  [] ?
__warn+0xbe/0xe0
Jan  7 17:31:12 phoenix kernel: [1.813095]  [] ?
warn_slowpath_fmt+0x5f/0x80
Jan  7 17:31:12 phoenix kernel: [1.813115]  [] ?
skl_compute_wm+0xb16/0x1440 [i915]
Jan  7 17:31:12 phoenix kernel: [1.813126]  [] ?
drm_atomic_check_only+0x304/0x5a0 [drm]
Jan  7 17:31:12 phoenix kernel: [1.813136]  [] ?
drm_atomic_add_affected_connectors+0x57/0xf0 [drm]
Jan  7 17:31:12 phoenix kernel: [1.813145]  [] ?
drm_atomic_commit+0x12/0x50 [drm]
Jan  7 17:31:12 phoenix kernel: [1.813150]  [] ?
restore_fbdev_mode+0x14c/0x270 [drm_kms_helper]
Jan  7 17:31:12 phoenix kernel: [1.813158]  [] ?
drm_modeset_lock_all_ctx+0xa0/0xb0 [drm]
Jan  7 17:31:12 phoenix kernel: [1.813162]  [] ?
drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x70 [drm_kms_helper]
Jan  7 17:31:12 phoenix kernel: [1.813166]  [] ?
drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper]
Jan  7 17:31:12 phoenix kernel: [1.813191]  [] ?
intel_fbdev_set_par+0x13/0x60 [i915]
Jan  7 17:31:12 phoenix kernel: [1.813192]  [] ?
fbcon_init+0x570/0x600
Jan  7 17:31:12 phoenix kernel: [1.813194]  [] ?
visual_init+0xcf/0x130
Jan  7 17:31:12 phoenix kernel: [1.813195]  [] ?
do_bind_con_driver+0x1cf/0x3b0
Jan  7 17:31:12 phoenix kernel: [1.813196]  [] ?
do_take_over_console+0x10e/0x170
Jan  7 17:31:12 phoenix kernel: [1.813198]  [] ?
do_fbcon_takeover+0x58/0xb0
Jan  7 17:31:12 phoenix kernel: [1.813199]  [] ?
notifier_call_chain+0x45/0x70
Jan  7 17:31:12 phoenix kernel: [1.813201]  [] ?
__blocking_notifier_call_chain+0x41/0x60
Jan  7 17:31:12 phoenix kernel: [ 

Re: vbox cannot find headers, although they are installed

2018-01-07 Thread Eike Lantzsch
On Saturday, January 6, 2018 8:36:38 PM -03 Harry Putnam wrote:
> Having a problem getting the vbox guest additions on a `testing'
> install to allow for larger monitor resolution.
> 
> When I attempt to install the additions the ouput says it cannot find
> the headers for the running kernel.
> 
> I have checked, rechecked and reinstalled the headers but still get
> the message that they cannot be found and the kernel module build then
> fails.
> 
> (Note: All debian systems mentioned below are running as guests on an
> `openindiana' (a solaris offshoot) host)
> 
> (Full output of attempted guest additions install are at the end)
> 
> But briefly . . . .
> 
> >From the host with the failure:
>   uname -r 4.14.0-2-amd64
This is not Stretch? Stretch is still with 4.9.0-5-amd64.
> 
>   aptitude search headers |grep ^i
> 
>   i  linux-headers-4.14.0-2-amd64 - Header files for Linux 4.14.0-2-amd64
>   i A linux-headers-4.14.0-2-common - Common header files for Linux 4.14.0-2
> 
> ,
> 
> | On two other debian systems (both running stretch, not `testing')
> | everything works as expected and the kernel module build succeeds...
> | monitor settings then act accordingly.
> | 
> | From 2 stretch hosts:
> | Of course, it is a different kernel and headers (4.9.0-5-amd64) on the
> | `stretch' systems and with like named header files.
> | 
> |   i A linux-headers-4.9.0-5-common
> |   i A linux-headers-4.9.0-5-amd64
> | 
> | With those in place on the stretch systems the guest additions build
> | just like they should.
> 
> `
> 
> What am I missing?

Did you by any chance install a kernel higher than 4.14.0-2 to check it out, 
then went back to 4.14.0-2 or installed 4.14.0 and then went back to 4.9.0?
In that case VBox is most probably still looking for the headers of the higher 
kernel version and cannot find them. I ran into that problem before.
In that case you will have to deinstall VBox completely and install it again. 
You can retain the virtual installations and later incorporate them into VBox 
again.
Cheers
Eike

> 
> =
> 
> Terminal output from attempting install of guest additions
> =
> 
> [Did not post the full log referred to in the output below... it is
> very long... but I can post it if necessary]
> 
> root # bash ./VBoxLinuxAdditions.run
> Verifying archive integrity... All good.
> Uncompressing VirtualBox 5.0.40 Guest Additions for Linux
> VirtualBox Guest Additions installer
> Removing installed version 5.0.40 of VirtualBox Guest Additions...
> Removing existing VirtualBox non-DKMS kernel modules ...done.
> update-initramfs: Generating /boot/initrd.img-4.14.0-2-amd64
> Copying additional installer modules ...
> Installing additional modules ...
> Removing existing VirtualBox non-DKMS kernel modules ...done.
> Building the VirtualBox Guest Additions kernel modules
> The headers for the current running kernel were not found. If the following
> module compilation fails then this could be the reason.
> 
> Building the main Guest Additions module ...fail!
> (Look at /var/log/vboxadd-install.log to find out what went wrong)
> Doing non-kernel setup of the Guest Additions ...done.



Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Yao Wei
It is caused by a missing dependency libelf-dev.
It is already reported against linux-headers-4.14.0-3-amd64:
https://bugs.debian.org/886474

I have the same symptom of broadcom-sta-dkms

On Mon, 8 Jan 2018 at 02:47 Boyan Penkov  wrote:

> Hello,
>
> After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
> light of meltdown -- my nvidia drivers failed to load.
>
> Rebulding the modules manually --
>
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
> -- did fix it.
>
> Did I miss something?
>
> Cheers!
>
> --
> Boyan Penkov
>
>


Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Daniel Reichelt
On 01/07/2018 07:47 PM, Boyan Penkov wrote:
> and a backport (4.14.0-bpo2) -- in light of meltdown --

To avoid a false sense of security: according to [1], [2], [3], the
current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
yet include any mitigations against meltdown.

Daniel



[1] https://security-tracker.debian.org/tracker/CVE-2017-5753
[2] https://security-tracker.debian.org/tracker/CVE-2017-5754
[3] https://security-tracker.debian.org/tracker/CVE-2017-5715



signature.asc
Description: OpenPGP digital signature


Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Thanks, Yao —  in messing around with this, I did end up finding a thread that 
suggested installing libelf-dev — I did so, but I guess the order in which I 
did it make me recompile my dkms modules manually.

Thanks for the note!
--
Boyan Penkov
www.boyanpenkov.com

> On Jan 7, 2018, at 18:31, Yao Wei  wrote:
> 
> It is caused by a missing dependency libelf-dev.
> It is already reported against linux-headers-4.14.0-3-amd64:
> https://bugs.debian.org/886474 
> 
> I have the same symptom of broadcom-sta-dkms
> 
> On Mon, 8 Jan 2018 at 02:47 Boyan Penkov  > wrote:
> Hello,
> 
> After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
> light of meltdown -- my nvidia drivers failed to load.
> 
> Rebulding the modules manually --
> https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
>  
> 
> -- did fix it.
> 
> Did I miss something?
> 
> Cheers!
> 
> --
> Boyan Penkov
> 



Re: Weired package policy

2018-01-07 Thread Mark Fletcher
On Sun, Jan 07, 2018 at 04:37:49PM +0100, Hans wrote:
> Am Sonntag, 7. Januar 2018, 16:26:55 CET schrieb Floris:
> Hi Floris and all,
> 
> maybe my question was not clearly expressed, due to my English. It was not 
> aimed to that special package. I would like to know, why packages completely 
> disappear, instead of just leaving the last well running version available in 
> testing. IMO to fully remove a running version completely in opposite of 
> keeping the last good version is in my eyes the worse idea.
> 

One point that has been skirted around in a couple of answers but not 
directly expressed is that putting the old, working version in testing 
is not the right thing to do in some situations if that old version 
cannot be a candidate for inclusion in buster when it is released (that 
is, when it becomes the stable distribution).

Using this package you took as an example, it is not at the moment a 
candidate for inclusion in buster as a release because it depends on a 
version of the SSL libraries that will not be there when buster is 
released (unless something changes). Putting it in testing now would be 
lying, in a way, because that package will not be there when the testing 
distribution becomes the stable distribution. The version already in 
stable is fine because the version of the SSL library it needs is in 
stable.

Why then, you might ask, is the package in sid? Two reasons, I guess : 
one, the package maintainer is clearly engaged in an argument with 
_someone_ about what the right resolution is, but the package isn't 
regarded as evil and isn't being dropped from Debian altogether, on the 
assumption a resolution will eventually be found. Two, the required SSL 
library is in sid but blocked from making the transition to buster, and 
therefore this package cannot make the transition because not all its 
dependencies have.

So in summary this comes about because the package is not _currently_ in 
a state that could be released in a stable buster release, but an 
optimistic assumption that the problem will get solved eventually is 
being made. In the meantime, no claims are being made that buster is 
anywhere near ready for release, so things like this are to be expected.

HTH

Mark



Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Hello Dan — thanks kindly, I had indeed not noticed….

I guess I’ll have a chance to test if the libelf-dev issue is really the fix 
when the patches do roll out.

In that vein, I would like to note that 
https://security-tracker.debian.org/tracker/CVE-2017-5754 
  makes no mention 
of bpo kernels in backports.  Is this by design?

Cheers!
--
Boyan Penkov
www.boyanpenkov.com

> On Jan 7, 2018, at 18:44, Daniel Reichelt  wrote:
> 
> On 01/07/2018 07:47 PM, Boyan Penkov wrote:
>> and a backport (4.14.0-bpo2) -- in light of meltdown --
> 
> To avoid a false sense of security: according to [1], [2], [3], the
> current stretch-bpo kernel (linux-image-4.14.0-0.bpo.2-$arch) does *NOT*
> yet include any mitigations against meltdown.
> 
> Daniel
> 
> 
> 
> [1] https://security-tracker.debian.org/tracker/CVE-2017-5753
> [2] https://security-tracker.debian.org/tracker/CVE-2017-5754
> [3] https://security-tracker.debian.org/tracker/CVE-2017-5715
> 



Re: kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Mark Fletcher
On Sun, Jan 07, 2018 at 11:31:58PM +, Yao Wei wrote:
> It is caused by a missing dependency libelf-dev.
> It is already reported against linux-headers-4.14.0-3-amd64:
> https://bugs.debian.org/886474
> 
> I have the same symptom of broadcom-sta-dkms
> 
Interesting. I noticed the libelf dependency when building 4.15-rc6 on 
an LFS machine the other day, also driven by Meltdown, and had to 
install elfutils to get the kernel to build without errors. Looks like 
the new kernel has a dependency on that -- one reason is to use the ORC 
kernel unwinder which is the default in that version I believe. Using 
the alternative, the Frame Pointer unwinder, allows the build to happen 
but then you get complaints at modules_install time for something else 
that wants libelf too, I forget what. Installing elfutils solved all 
issues.

I hadn't seen the problem in Debian but where I run Debian I run stretch 
so just installed the stable update from stretch to fix Meltdown. Since 
my stretch machines are behind my firewall anyway my priority was to get 
my firewall patched, so if there is more to come in terms of patching 
stock Debian kernels, I am disinclined to panic.

Mark



Re: Android Debian - Lets start Debian for Android hw phones

2018-01-07 Thread SDA
On Wed, Jan 03, 2018 at 12:25:50AM +0100, Anders Andersson wrote:
> On Tue, Jan 2, 2018 at 5:50 PM, Samuel  wrote:
> > could you add a support for wiko
> > I have a wiko lenny 4 plus
> 
> Sure! Probably a small job. I'll submit a patch tomorrow to port
> debian to android.
>

Well, Debian does call itself the 'Universal Operating System'. Maybe that 
phrase should be rethought since it doesn't run on all devices. Worthy 
thought, but not reality. 



Re: [OFFTOPIC] Re: "Meltdown" and "Spectre": Every modern processor has unfixable security flaws

2018-01-07 Thread SDA
Show who you're quoting with an attribution line, please!



Re: Android Debian - Lets start Debian for Android hw phones

2018-01-07 Thread arne
On Sun, 7 Jan 2018 19:32:25 -0500
SDA  wrote:

> On Wed, Jan 03, 2018 at 12:25:50AM +0100, Anders Andersson wrote:
> > On Tue, Jan 2, 2018 at 5:50 PM, Samuel  wrote:  
> > > could you add a support for wiko
> > > I have a wiko lenny 4 plus  
> > 
> > Sure! Probably a small job. I'll submit a patch tomorrow to port
> > debian to android.
> >  
> 
> Well, Debian does call itself the 'Universal Operating System'. Maybe
> that phrase should be rethought since it doesn't run on all devices.
> Worthy thought, but not reality. 
> 

Debian should run on the Gemini PDA, an Android handhold device.
In dual boot.
It is not ready yet though.
Should be ready this month.



Re: Kernel problem?

2018-01-07 Thread tv.deb...@googlemail.com

On 07/01/2018 21:27, Marc Auslander wrote:

The new kernel implements the "fix" for meltdown.  You could try booting
with the fix turned off - I believe the kernel parameter is pti=off
Rob Hurle  writes:


Hi All,

I'm running Stretch and yesterday I did my normal:

sudo apt-get update
sudo apt-get upgrade

It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config
and image files, etc) in place of 4.9.0-4-686-pae versions. Now the
system won't boot at all. I have reverted to 4.9.0-4-686-pae and all
is well. My questions are:

1. Does anyone else see this?

2. How can I revert without losing my working 4.9.0-4-686-pae system?
Can I just change the soft links for initrd.img and vmlinuz at / to
point to the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae
ones? Will this break something else for a future upgrade?

Any help much appreciated. Thank you.

Cheers, Rob Hurle

-
Rob Hurle
e-mail: rob1...@gmail.com
Mobile: +61 417 293 603 (Australia)
Telephone: (02) 6236 3895
28 Mirrormere Rd, Burra, NSW 2620, Australia




Hi, if the hang is due to memory isolation option, then "nopti" added as 
a kernel boot parameter will cancel it. If you are on an Intel machine 
this will leave you exposed to the new class of "Meltdown" attacks.
This kind of boot problem seems to happen to a very small number of 
systems, patches are already queued in the kernel to (hopefully) correct 
this, but you will have to wait for them to be merged.


Hope it helps.



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread David Wright
On Sun 07 Jan 2018 at 18:15:06 (+), Brian wrote:
> On Sun 07 Jan 2018 at 07:46:30 -0500, rhkra...@gmail.com wrote:
> 
> > I know this is not directly on point to the OP's question as subsequently 
> 
> But it does treat conversion of files to PDFs, so you are not way off
> base. Look at the variety of techniques people use: paps, a2ps,
> enscript, cupsfilter, ps2pdf, unoconv etc. There probably isn't one
> tried and trusted method which suits everyone; and we haven't exhausted
> discussion of them all and how they could fit into a printing system.
> 
> > clarified, but I would point out that a variety of programs like txt2pdf 
> > exist 
> > (and work)--I assume, but don't know that they are available in the various 
> > Debian distros.
> 
> Which txt2pdf? I tried the DFSG free one at
> 
> https://github.com/baruchel/txt2pdf
> 
> Not in Debian, AFAICT, but download, put in /usr/local/bin and install
> python-reportlab. Gives searchable PDFs, fonts can be selected more
> easily than with cupsfilter or cups-pdf and it has UTF-8 support. Looks
> useful.

Indeed. It seems a lot faster than paps+ps2pdf too. I can see myself
using this, though I'll keep my paps function as well, as it appears
to be able to make substitutions for missing glyphs. It's handy to
have a function that prints *something* at every position (except
the strip at 0x80), with those little blobs containing 4 hex chars
where there's no glyph. paps also does columns.

The default fault in txt2pdf is Courier→Nimbus Mono AFAICT, which is
very limited. The unifont TTF font has far more characters, but
the quality is very poor (deliberately, but looks like a bitmapped font).
I also haven't figured out line-numbering: I'll have to study the script.
Searchability is a useful extra (I'm used to just searching the original
text source file).

BTW a2ps, suggested earlier, is another that failed to move to Unicode
AIUI. A shame as it had lots of useful column/custom heading stuff.

Cheers,
David.



Re: Weired package policy

2018-01-07 Thread Joe Pfeiffer
Hans  writes:

> I searched the manuals for this point, but this was nowhere mentioned. Of 
> course, you may say, that this is self-evident, but people might want to have 
> the repo small and may think, "hey, if I get testing, then all packages of 
> stable will be available as well."

As I understand the repository structure, packages in stable are not
necessarily also in testing.  Stable is, as the name implies, packages
that are regarded as good and solid; testing is packages that are
candidates to be upgrades to those in stable.

So, unless you are really running a machine strictly for the purpose of
testing packages, you should have your apt preferences set so that
you'll find packages in stable as that's the standard set of packages,
plus packages in testing so you can stay more current.  In my case, part
of my /etc/apt/preferences is

Package: *
Pin: release a=testing
Pin-Priority: 700

Package: *
Pin: release a=stable
Pin-Priority: 650

in order to capture this intent.



Re: Kernel problem?

2018-01-07 Thread Rob Hurle
Thanks to everyone who provided help with this failure of the
4.9.0-5-686-pae kernel.  I have tried both "nopti" and "pti=off" kernel
parameters to see if it is the fix for "Meltdown" which is causing the
problem, but neither parameter changes anything. Since the system doesn't
even get to the kernel fsck stage, I don't have any logs to be able to
either report a bug or analyse the problem.  I also realise now that
auto-update is turned on by default in Stretch, so that is how the new
kernel became installed.  I have temporarily turned auto-update off because
I don't want any automatic update to clobber my only working kernel - the
4.9.0-4-686-pae.  The updating system only seems to keep 2 generations of
kernel?

Any further ideas would be very welcome.

Cheers, Rob Hurle

-
Rob Hurle
e-mail:rob1...@gmail.com
Mobile:   +61 417 293 603 (Australia)
Telephone:  (02) 6236 3895
28 Mirrormere Rd, Burra, NSW 2620, Australia

On 8 January 2018 at 13:11, tv.deb...@googlemail.com <
tv.deb...@googlemail.com> wrote:

> On 07/01/2018 21:27, Marc Auslander wrote:
>
>> The new kernel implements the "fix" for meltdown.  You could try booting
>> with the fix turned off - I believe the kernel parameter is pti=off
>> Rob Hurle  writes:
>>
>> Hi All,
>>>
>>> I'm running Stretch and yesterday I did my normal:
>>>
>>> sudo apt-get update
>>> sudo apt-get upgrade
>>>
>>> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config
>>> and image files, etc) in place of 4.9.0-4-686-pae versions. Now the
>>> system won't boot at all. I have reverted to 4.9.0-4-686-pae and all
>>> is well. My questions are:
>>>
>>> 1. Does anyone else see this?
>>>
>>> 2. How can I revert without losing my working 4.9.0-4-686-pae system?
>>> Can I just change the soft links for initrd.img and vmlinuz at / to
>>> point to the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae
>>> ones? Will this break something else for a future upgrade?
>>>
>>> Any help much appreciated. Thank you.
>>>
>>> Cheers, Rob Hurle
>>>
>>> -
>>> Rob Hurle
>>> e-mail: rob1...@gmail.com
>>> Mobile: +61 417 293 603 (Australia)
>>> Telephone: (02) 6236 3895
>>> 28 Mirrormere Rd, Burra, NSW 2620, Australia
>>>
>>
>>
> Hi, if the hang is due to memory isolation option, then "nopti" added as a
> kernel boot parameter will cancel it. If you are on an Intel machine this
> will leave you exposed to the new class of "Meltdown" attacks.
> This kind of boot problem seems to happen to a very small number of
> systems, patches are already queued in the kernel to (hopefully) correct
> this, but you will have to wait for them to be merged.
>
> Hope it helps.
>
>


Re: Android Debian - Lets start Debian for Android hw phones

2018-01-07 Thread Ben Oliver

On 18-01-08 02:35:02, arne wrote:

On Sun, 7 Jan 2018 19:32:25 -0500
SDA  wrote:


On Wed, Jan 03, 2018 at 12:25:50AM +0100, Anders Andersson wrote:
> On Tue, Jan 2, 2018 at 5:50 PM, Samuel  wrote:
> > could you add a support for wiko
> > I have a wiko lenny 4 plus
>
> Sure! Probably a small job. I'll submit a patch tomorrow to port
> debian to android.
>

Well, Debian does call itself the 'Universal Operating System'. Maybe
that phrase should be rethought since it doesn't run on all devices.
Worthy thought, but not reality.



Debian should run on the Gemini PDA, an Android handhold device.
In dual boot.
It is not ready yet though.
Should be ready this month.



I am currently working on getting a wifi kettle port of Debian up and 
running. Should be done by Thursday, just need to finish soldering a 
serial port to it.




[SOLVED] (was: [Stable/AMD64] Changing gdm background)

2018-01-07 Thread Leandro Noferini
Floris  writes:

>>> I would like to change the default background of gdm login screen on my

[...]

> There is no easy way to change the gdm3 theme, but you can. The Arch
> Wiki has a small how-to:
> https://wiki.archlinux.org/index.php/GDM

Thanks a lot, I managed to change the background using the script found
in https://bbs.archlinux.org/viewtopic.php?id=197036 linked in the page
you pointed out.

-- 
Ciao
leandro
http://6xukrlqedfabdjrb.onion/blog/
Alla bellezza preferisco la verità.
E il dubbio è l'unità di misura.


signature.asc
Description: PGP signature


Re: Kernel problem?

2018-01-07 Thread Sven Joachim
On 2018-01-07 13:58 +1100, Rob Hurle wrote:

>   I'm running Stretch and yesterday I did my normal:
>
> sudo apt-get update
> sudo apt-get upgrade
>
> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
> image files, etc) in place of 4.9.0-4-686-pae versions.  Now the system
> won't boot at all.  I have reverted to 4.9.0-4-686-pae and all is well.  My
> questions are:
>
> 1.  Does anyone else see this?

Bug #886485[1] talks about a hang at boot which may be the same what you
are seeing.

> 2.  How can I revert without losing my working 4.9.0-4-686-pae system?  Can
> I just change the soft links for initrd.img and vmlinuz at / to point to
> the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae ones?

Most bootloaders, including the default bootloader on PCs (grub), do not
use these symlinks at all.  To boot with the 4.9.0-4-686-pae kernel by
default, you can fiddle around with the grub configuration or uninstall
the 4.9.0-5-686-pae kernel.  In the latter case you would have to
downgrade or uninstall the linux-image-686-pae metapackage as well.

Cheers,
   Sven


1. https://bugs.debian.org/886485



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Brian
On Sat 06 Jan 2018 at 20:45:01 -0600, Jason wrote:

> > lpadmin. The wiki should help.
> 
> I had looked into lpadmin and thought that might be what I need but
> couldn't find in the man page how to add a printer. I don't have web
> access so am asking here rather than looking on the wiki.

For a PDF printer: install (or reinstall) printer-driver-cups-pdf.
lpadmin automatically sets up a print queue.
 
> So basically what I'm asking is how to add a printer (this could apply
> to any printer, not just PDF) without needing to install a printer
> configuration GUI.

In general: lpadmin -p queue_name -v device_uri -E -m PPD.

Obtain device_uri from 'lpinfo -v' and PPD from 'lpinfo -m'.

-- 
Brian.



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Curt
On 2018-01-07, Brian  wrote:
>> >
>> > How does one convert a text file to a PDF using the command line?
>> >
>> 
>>  unoconv -f pdf text.txt
>
> 50+ megabytes of the libreoffice stack to install, But yes, that will
> do it. A sledgehammer to crack a nut.

Depends on the nut, doesn't it?

Anyhoo, I don't understand where you get the 50+ megabytes. I see two
dependencies in stable (python3 and python3-uno), a package size of 48.8
kB, and an installed size of 327.0 kB. So I'm understanding the package
does not depend upon the installation of LibreOffice proper (the
redoubtable "stack"?).

Perhaps my comprehension is faulty.

-- 
"An autobiography is only to be trusted when it reveals something disgraceful.
A man who gives a good account of himself is probably lying, since any life
when viewed from the inside is simply a series of defeats."
— George Orwell



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Brian
On Sun 07 Jan 2018 at 11:06:01 +, Curt wrote:

> On 2018-01-07, Brian  wrote:
> >> >
> >> > How does one convert a text file to a PDF using the command line?
> >> >
> >> 
> >>  unoconv -f pdf text.txt
> >
> > 50+ megabytes of the libreoffice stack to install, But yes, that will
> > do it. A sledgehammer to crack a nut.
> 
> Depends on the nut, doesn't it?
> 
> Anyhoo, I don't understand where you get the 50+ megabytes. I see two
> dependencies in stable (python3 and python3-uno), a package size of 48.8

Look at the dependencies of python3-uno and then at those of
libreoffice-core.

> kB, and an installed size of 327.0 kB. So I'm understanding the package
> does not depend upon the installation of LibreOffice proper (the
> redoubtable "stack"?).

Indeed not. Those packages are recommended only. (But many people wisely
stick with the default of installing Recommends:).
 
> Perhaps my comprehension is faulty.

"Room for improvement" is how I would put it. :)


root@desktop3:~# apt-get install unoconv
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  fonts-opensymbol libboost-date-time1.62.0 libboost-filesystem1.62.0 
libboost-iostreams1.62.0 libboost-system1.62.0
  libclucene-contribs1v5 libclucene-core1v5 libcmis-0.5-5v5 libeot0 
libexttextcat-2.0-0 libexttextcat-data libgltf-0.  1-1 libgpgmepp6 libhyphen0 
liblangtag-common liblangtag1 libmhash2 libmythes-1.2-0 libneon27-gnutls 
libodfgen-0.1-1
  liborcus-0.12-0 libpython3.6 libraptor2-0 librasqal3 librdf0 
libreoffice-common libreoffice-core libreoffice-style-  galaxy 
libreoffice-style-tango librevenge-0.0-0 libxmlsec1 libxmlsec1-nss libyajl2 
python3-uno uno-libs3 ure
Suggested packages:
  raptor2-utils rasqal-utils librdf-storage-postgresql librdf-storage-mysql 
librdf-storage-sqlite librdf-storage-virt  uoso redland-utils tango-icon-theme 
java5-runtime
Recommended packages:
  libreoffice-writer libreoffice-draw libreoffice-calc libreoffice-impress
The following NEW packages will be installed:
  fonts-opensymbol libboost-date-time1.62.0 libboost-filesystem1.62.0 
libboost-iostreams1.62.0 libboost-system1.62.0
  libclucene-contribs1v5 libclucene-core1v5 libcmis-0.5-5v5 libeot0 
libexttextcat-2.0-0 libexttextcat-data libgltf-0.  1-1 libgpgmepp6 libhyphen0 
liblangtag-common liblangtag1 libmhash2 libmythes-1.2-0 libneon27-gnutls 
libodfgen-0.1-1
  liborcus-0.12-0 libpython3.6 libraptor2-0 librasqal3 librdf0 
libreoffice-common libreoffice-core libreoffice-style-  galaxy 
libreoffice-style-tango librevenge-0.0-0 libxmlsec1 libxmlsec1-nss libyajl2 
python3-uno uno-libs3 unoconv ur  e
0 upgraded, 37 newly installed, 0 to remove and 0 not upgraded.
Need to get 67.0 MB of archives.
After this operation, 240 MB of additional disk space will be used.
Do you want to continue? [Y/n]


Note that recommended packages are not being installed. Adding them
with "--install-recommends" raises the bar to 207 MB. My estimate was
conservative.

OTOH, cupsfilter is already on the system. It handles text, image and
Postscript files and, run with "-m application/vnd.cups-pdf", produces
a PDF which is autorotated to make it suitable for normal printing.
Lack of searchable text in a PDF is of no consequence for printing.

-- 
Brian.



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread rhkramer
I know this is not directly on point to the OP's question as subsequently 
clarified, but I would point out that a variety of programs like txt2pdf exist 
(and work)--I assume, but don't know that they are available in the various 
Debian distros.

On Sunday, January 07, 2018 05:10:50 AM Brian wrote:
> On Sat 06 Jan 2018 at 20:45:01 -0600, Jason wrote:
> > > lpadmin. The wiki should help.
> > 
> > I had looked into lpadmin and thought that might be what I need but
> > couldn't find in the man page how to add a printer. I don't have web
> > access so am asking here rather than looking on the wiki.
> 
> For a PDF printer: install (or reinstall) printer-driver-cups-pdf.
> lpadmin automatically sets up a print queue.
> 
> > So basically what I'm asking is how to add a printer (this could apply
> > to any printer, not just PDF) without needing to install a printer
> > configuration GUI.
> 
> In general: lpadmin -p queue_name -v device_uri -E -m PPD.
> 
> Obtain device_uri from 'lpinfo -v' and PPD from 'lpinfo -m'.



Re: MTP devices leave multiple copies under Devices in file managers

2018-01-07 Thread Carl Fink

On 01/06/2018 03:06 PM, Ben Caradoc-Davies wrote:

What kernel version? Do the entries disappear on reboot?


This morning I had time to reboot, and I can now confirm that
rebooting cleared the dead entries. It sure looks like the
already-reported bug.

Thanks for the pointer--it never occurred to me to look for a kernel
bug because I don't know the underpinnings of the process (MTP
mountpoints?) and wasn't aware that a kernel process (module?) was
involved. Much appreciated.

--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com



Re: Is there a way to know the ISP with the default installation of Stretch?

2018-01-07 Thread Pascal Hambourg

Le 04/01/2018 à 05:32, Michael Stone a écrit :


No, it's a pretty common shorthand to say "routable" to mean "routable 
on the public internet", especially where there's no real possibility of 
confusing it with specifically non-routable blocks like 127.0.0.0/8. 


This is still a mistake. In technical fields such as this one, words 
have a well defined meaning.


Honestly, I considered it less likely to be confusing than calling them 
RFC1918 addresses in this context.


What about "private", as defined in RFC1918 ?

As far as 169.254.0.0/16, it's defined as a link local range for address 
autoconfiguration, but it can still be routed internally just as much as 
the RFC1918 space can be.


No, unless you're ready to violate the standards. RFC3927 (Dynamic 
Configuration of IPv4 Link-Local Addresses) explicitly states in chapter 
7 "Router Considerations" :


   A router MUST NOT forward a packet with an IPv4 Link-Local source or
   destination address, irrespective of the router's default route
   configuration or routes obtained from dynamic routing protocols.

   A router which receives a packet with an IPv4 Link-Local source or
   destination address MUST NOT forward the packet.  This prevents
   forwarding of packets back onto the network segment from which they
   originated, or to any other segment.

Note that it says "MUST", not "SHOULD".

(Doing so just might not be a good idea, 


Yes, violating the standards is often a bad idea.


because some devices might code in some assumptions


What you call "assumptions" is just compliance with the standards.



Re: T570 Powerkey doesn't work

2018-01-07 Thread Floris
Op Thu, 04 Jan 2018 22:42:34 +0100 schreef Markus Grunwald  
:



Hello,

as far as I understand, pressing the power key on my Lenovo T570 should
produce some output in the journal like this:

Mär 31 18:04:47 my_computer systemd-logind[1402]: Power key pressed.

On my laptop, this doesn't work - I see nothing in the journal.
Hibernating doesn't work, neither but that's the reason, I think...

Is there something special that I have to do?

cu


Can you find the Powerkey with evtest?

[NumLock example]

sudo evtest /dev/input/event12
...
Event: time 1434666536.001123, type 4 (EV_MSC), code 4 (MSC_SCAN), value  
70053
Event: time 1434666536.001123, type 1 (EV_KEY), code 69 (KEY_NUMLOCK),  
value 0

Event: time 1434666536.001123, -- EV_SYN 



Re: vbox cannot find headers, although they are installed

2018-01-07 Thread x9p

On Sat, January 6, 2018 11:36 pm, Harry Putnam wrote:
...
> (Look at /var/log/vboxadd-install.log to find out what went wrong)
...

the line above can explain a lot.

cheers.

--
x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 
E7EE

"I don't know where I'm going from here, but I promise it won't be boring." - 
David Bowie




Weired package policy

2018-01-07 Thread Hans
Hi folks, 

there is a thing, I cannot understand. 

>From time to time, there appear packages, which are in stable for a long time, 
and then suddenly they are in unstable and stable, but NOT in testing.

This is a policy, I do not understand! An actual example is "cqrlog" which 
appears in stable and sid, but not in testing.

For my feeling, I would expect "cqrlog" in testing, too, maybe in the same 
version as in stable, but not fully disappeared. 

Debian's way is not quite clear for me, and IMO I think it not a good idea, to 
let packages silently disappear. At this point, I may be wrong.

Thinking of this let me think of another point, which has never been clear for 
me since years: When I install a new system, and I want to run testing, then 
you MUST also add the repo for stable in the sources.list, otherwise packages 
you might want to use, are missing (due to the policy above).

I searched the manuals for this point, but this was nowhere mentioned. Of 
course, you may say, that this is self-evident, but people might want to have 
the repo small and may think, "hey, if I get testing, then all packages of 
stable will be available as well."

Anyway, maybe someone might enlighten me (and maybe others, too as well) of 
that.

Thank you for all your answers and the great work.

Best

Hans 

 



Re: Weired package policy

2018-01-07 Thread Floris

Op Sun, 07 Jan 2018 15:58:57 +0100 schreef Hans :


Hi folks,

there is a thing, I cannot understand.

From time to time, there appear packages, which are in stable for a  
long time,

and then suddenly they are in unstable and stable, but NOT in testing.

This is a policy, I do not understand! An actual example is "cqrlog"  
which

appears in stable and sid, but not in testing.

For my feeling, I would expect "cqrlog" in testing, too, maybe in the  
same

version as in stable, but not fully disappeared.



from: https://tracker.debian.org/pkg/cqrlog

testing migrations
excuses:
Migration status: BLOCKED: Rejected/introduces a regression (please see  
below)

164 days old (needed 5 days)
Updating cqrlog introduces new bugs: #867140

There is difference of opinion about the libssl version. Buster will have  
1.1. Cqrlog depends on 1.0




Re: Weired package policy

2018-01-07 Thread Hans
Am Sonntag, 7. Januar 2018, 16:26:55 CET schrieb Floris:
Hi Floris and all,

maybe my question was not clearly expressed, due to my English. It was not 
aimed to that special package. I would like to know, why packages completely 
disappear, instead of just leaving the last well running version available in 
testing. IMO to fully remove a running version completely in opposite of 
keeping the last good version is in my eyes the worse idea.




> from: https://tracker.debian.org/pkg/cqrlog
> 
> testing migrations
> excuses:
> Migration status: BLOCKED: Rejected/introduces a regression (please see
> below)
> 164 days old (needed 5 days)
> Updating cqrlog introduces new bugs: #867140
> 
> There is difference of opinion about the libssl version. Buster will have
> 1.1. Cqrlog depends on 1.0




Re: Weired package policy

2018-01-07 Thread The Wanderer
On 2018-01-07 at 10:26, Floris wrote:

> Op Sun, 07 Jan 2018 15:58:57 +0100 schreef Hans
> :
> 
>> Hi folks,
>> 
>> there is a thing, I cannot understand.
>> 
>>> From time to time, there appear packages, which are in stable
>>> for a long time, and then suddenly they are in unstable and
>>> stable, but NOT in testing.
>> 
>> This is a policy, I do not understand! An actual example is
>> "cqrlog" which appears in stable and sid, but not in testing.
>> 
>> For my feeling, I would expect "cqrlog" in testing, too, maybe in
>> the same version as in stable, but not fully disappeared.
> 
> from: https://tracker.debian.org/pkg/cqrlog
> 
> testing migrations
> excuses:
> Migration status: BLOCKED: Rejected/introduces a regression (please see  
> below)
> 164 days old (needed 5 days)
> Updating cqrlog introduces new bugs: #867140
> 
> There is difference of opinion about the libssl version. Buster will have  
> 1.1. Cqrlog depends on 1.0

I read his objection as being to the policy about what should be done
when a bug bad enough to warrant removing that package version from
testing is identified.

Currently, the policy is that when that happens, the package is removed
from testing.

I read him as saying that the policy *should* be that when such a bug is
identified, the version from stable (or maybe the previous
non-buggy version, from before the upload which introduced the bug)
should be reintroduced into testing.

Unfortunately, this would not work well with the way package version
numbers are handled, and I'm not sure it wouldn't be impractically
unwieldy to implement on the backend in any case.

(Plus the difficulties with dependencies; what happens when the version
which would be reintroduced depends on an older version of another
package, and the newer version is already in testing and does not itself
have such a bug?)

-- 
   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: Kernel problem?

2018-01-07 Thread Marc Auslander
The new kernel implements the "fix" for meltdown.  You could try booting
with the fix turned off - I believe the kernel parameter is pti=off
Rob Hurle  writes:

>Hi All,
>
>I'm running Stretch and yesterday I did my normal:
>
>sudo apt-get update
>sudo apt-get upgrade
>
>It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config
>and image files, etc) in place of 4.9.0-4-686-pae versions. Now the
>system won't boot at all. I have reverted to 4.9.0-4-686-pae and all
>is well. My questions are:
>
>1. Does anyone else see this?
>
>2. How can I revert without losing my working 4.9.0-4-686-pae system?
>Can I just change the soft links for initrd.img and vmlinuz at / to
>point to the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae
>ones? Will this break something else for a future upgrade?
>
>Any help much appreciated. Thank you.
>
>Cheers, Rob Hurle
>
>-
>Rob Hurle
>e-mail: rob1...@gmail.com
>Mobile: +61 417 293 603 (Australia)
>Telephone: (02) 6236 3895
>28 Mirrormere Rd, Burra, NSW 2620, Australia



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread David Wright
On Sun 07 Jan 2018 at 11:06:01 (+), Curt wrote:
> On 2018-01-07, Brian  wrote:
> >> >
> >> > How does one convert a text file to a PDF using the command line?
> >> >
> >> 
> >>  unoconv -f pdf text.txt
> >
> > 50+ megabytes of the libreoffice stack to install, But yes, that will
> > do it. A sledgehammer to crack a nut.
> 
> Depends on the nut, doesn't it?
> 
> Anyhoo, I don't understand where you get the 50+ megabytes. I see two
> dependencies in stable (python3 and python3-uno), a package size of 48.8
> kB, and an installed size of 327.0 kB. So I'm understanding the package
> does not depend upon the installation of LibreOffice proper (the
> redoubtable "stack"?).
> 
> Perhaps my comprehension is faulty.

I guess you forgot to readman unoconv:

   "unoconv uses the LibreOffice’s UNO bindings for non-interactive
   conversion of documents and therefore needs an LibreOffice
   instance to communicate with. Therefore if it cannot find one,
   it will start its own instance for temporary usage."

Myself, I use paps and ps2pdf. paps has a few options that I use,
like margins and columns, and I get a few more obscure Unicode
characters rendered successfully using the Freemono fonts than
I get with cupsfilter, but that's probably because I haven't
studied how I could modify the latter's behaviour.

Cheers,
David.



Problem formatting a column to justify (i.e. line wrap)

2018-01-07 Thread Richard Owlett

I'm new to gnumeric and have not used any spreadsheet since mid 70's.
I'm running Debian 9.1 with MATE desktop and gnumeric 1.12.32 .

I have 2 columns with potentially long lines.
I had no problem selecting a preferred font size.
I created a spreadsheet allowing cells with with long lines to truncate 
when displayed.


I then chose to justify. An inappropriate column with had been set 
initially resulting in row height of 3 lines of text. I manually dragged 
the column separator to an appropriate width resulting in a desired 
height of 2 lines of text.


That row is stuck at a height of 3 lines of text.

How can I force each row height to be *NO* taller than necessary to for 
the currently longest line?


TIA




Re: Different language per user in MATE and change default lang of greeter

2018-01-07 Thread john doe

On 1/4/2018 10:50 AM, Alex ARNAUD wrote:

Hello John,

I've configured a multilingual system based on Debian Jessie last month.

The steps I've followed are:
1) Install the language pack of your targeted languages like 
"task-english", don't miss to install the language pack for Firefox, 
Thunderbird and LibreOffice if needed.


2) Enable the locales of your users and move the default locale to 
"None" with :

sudo dpkg-reconfigure locales

3) Log in with one account

4) Edit the file "~/.dmrc", replace the locale with the locale you want.

5) Do the strep "4" for all the users

You have to reboot your computer after applying the configuration to 
avoid cache. IMO, you should login into all your users to ensure that it 
works or test the procedure on a VM first.


Could you let me know if it works correctly for you and what issues do 
you have to be sure that my Jessie procedure continues to work on Stretch ?




Hi Alex and sorry for my late answer :)

Your procedure doesn't seem to work anymore on Debian Stretch.

--
John Doe



Unable to get the temp for one disk in Stretch

2018-01-07 Thread Daniel Bareiro
Hi all!

I recently updated my firewall from Jessie to Stretch and I realized
that the check_lm_sensors plugin was apparently not working because it
was not possible to get the temperature of one of the disks:

# /usr/lib/nagios/plugins/check_lm_sensors --list
LM_SENSORS UNKNOWN - Error while executing /usr/sbin/hddtemp -n /dev/sdb

These are two disks which form several MD arrays.

# /usr/sbin/hddtemp -n /dev/sda
44

# /usr/sbin/hddtemp -n /dev/sdb
WARNING: Drive /dev/sdb doesn't seem to have a temperature sensor.
WARNING: This doesn't mean it hasn't got one.
WARNING: If you are sure it has one, please contact me (hddt...@guzu.net).
WARNING: See --help, --debug and --drivebase options.
/dev/sdb: WDC WD5000AAKX-60U6AA0:  no sensor

In fact, not even smartctl is able to see the temperature:

# smartctl -a /dev/sda | grep Temperature_Celsius
194 Temperature_Celsius 0x0022   099   090   000Old_age   Always
  -   44

# smartctl -a /dev/sdb | grep Temperature_Celsius
#

It's weird because in Jessie I do not remember having this problem. I
can even find smartd entries in the syslog before doing the update:

# grep smart syslog
Jan  7 06:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 61
Jan  7 10:52:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 61 to 60
Jan  7 11:22:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 102 to 101
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 101 to 100
Jan  7 12:22:28 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 59
Jan  7 13:52:27 alderamin smartd[438]: Device: /dev/sda [SAT], SMART
Usage Attribute: 194 Temperature_Celsius changed from 100 to 99
Jan  7 14:22:27 alderamin smartd[438]: Device: /dev/sdb [SAT], SMART
Usage Attribute: 190 Airflow_Temperature_Cel changed from 59 to 58

So I'm not sure where the problem may be. If it is in smartd (and
hddtemp is based on smartd) or maybe in some kernel module.

Any thoughts will be greatly appreciated.

Thanks in advance.


Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature


Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Brian
On Sun 07 Jan 2018 at 07:46:30 -0500, rhkra...@gmail.com wrote:

> I know this is not directly on point to the OP's question as subsequently 

But it does treat conversion of files to PDFs, so you are not way off
base. Look at the variety of techniques people use: paps, a2ps,
enscript, cupsfilter, ps2pdf, unoconv etc. There probably isn't one
tried and trusted method which suits everyone; and we haven't exhausted
discussion of them all and how they could fit into a printing system.

> clarified, but I would point out that a variety of programs like txt2pdf 
> exist 
> (and work)--I assume, but don't know that they are available in the various 
> Debian distros.

Which txt2pdf? I tried the DFSG free one at

https://github.com/baruchel/txt2pdf

Not in Debian, AFAICT, but download, put in /usr/local/bin and install
python-reportlab. Gives searchable PDFs, fonts can be selected more
easily than with cupsfilter or cups-pdf and it has UTF-8 support. Looks
useful.

-- 
Brian.



kernel nvidia dkms rebuild after upgrade?

2018-01-07 Thread Boyan Penkov
Hello,

After the latest update to 4.9.0-5, and a backport (4.14.0-bpo2) -- in
light of meltdown -- my nvidia drivers failed to load.

Rebulding the modules manually --
https://askubuntu.com/questions/53364/command-to-rebuild-all-dkms-modules-for-all-installed-kernels/174017
-- did fix it.

Did I miss something?

Cheers!

-- 
Boyan Penkov



Re: Problem formatting a column to justify (i.e. line wrap)

2018-01-07 Thread David Wright
On Sun 07 Jan 2018 at 11:34:43 (-0600), Richard Owlett wrote:
> I'm new to gnumeric and have not used any spreadsheet since mid 70's.
> I'm running Debian 9.1 with MATE desktop and gnumeric 1.12.32 .
> 
> I have 2 columns with potentially long lines.
> I had no problem selecting a preferred font size.
> I created a spreadsheet allowing cells with with long lines to
> truncate when displayed.
> 
> I then chose to justify. An inappropriate column with had been set
> initially resulting in row height of 3 lines of text. I manually
> dragged the column separator to an appropriate width resulting in a
> desired height of 2 lines of text.
> 
> That row is stuck at a height of 3 lines of text.
> 
> How can I force each row height to be *NO* taller than necessary to
> for the currently longest line?

To correct one row, double-click on the line underneath the row number
in the left hand margin.

To correct all the rows, click on the area just above the row number
for the first row (selects the entire sheet) and then double-click on
any of the lines like the one I described in the previous paragraph.

Cheers,
David.



Re: Different language per user in MATE and change default lang of greeter

2018-01-07 Thread john doe

On 1/7/2018 6:52 PM, john doe wrote:

On 1/4/2018 10:50 AM, Alex ARNAUD wrote:

Hello John,

I've configured a multilingual system based on Debian Jessie last month.

The steps I've followed are:
1) Install the language pack of your targeted languages like 
"task-english", don't miss to install the language pack for Firefox, 
Thunderbird and LibreOffice if needed.


2) Enable the locales of your users and move the default locale to 
"None" with :

sudo dpkg-reconfigure locales

3) Log in with one account

4) Edit the file "~/.dmrc", replace the locale with the locale you want.

5) Do the strep "4" for all the users

You have to reboot your computer after applying the configuration to 
avoid cache. IMO, you should login into all your users to ensure that 
it works or test the procedure on a VM first.


Could you let me know if it works correctly for you and what issues do 
you have to be sure that my Jessie procedure continues to work on 
Stretch ?




Hi Alex and sorry for my late answer :)

Your procedure doesn't seem to work anymore on Debian Stretch.



I got it working:

You also need to set the desired locale in 
'/var/lib/AccountsService/users/'.


https://www.freedesktop.org/wiki/Software/AccountsService/
https://afrantzis.wordpress.com/2012/06/11/changing-gdmlightdm-user-login-settings-programmatically/

--
John Doe



Re: Weired package policy

2018-01-07 Thread Roberto C . Sánchez
On Sun, Jan 07, 2018 at 04:37:49PM +0100, Hans wrote:
> Am Sonntag, 7. Januar 2018, 16:26:55 CET schrieb Floris:
> Hi Floris and all,
> 
> maybe my question was not clearly expressed, due to my English. It was not 
> aimed to that special package. I would like to know, why packages completely 
> disappear, instead of just leaving the last well running version available in 
> testing. IMO to fully remove a running version completely in opposite of 
> keeping the last good version is in my eyes the worse idea.
> 
The package disappears when the version in testing is affected by a
release critical bug which does not get fixed.  If a bug only affects
the unstable/sid version of a package and the package in testing is of a
different version, the package in testing will remain.

Regards,

-Roberto

-- 
Roberto C. Sánchez



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Brian
On Sat 06 Jan 2018 at 21:51:18 +0100, john doe wrote:

> On 1/6/2018 9:15 PM, Brian wrote:
> > On Sat 06 Jan 2018 at 05:54:00 +0100, john doe wrote:
> > 
> > > On 1/6/2018 4:06 AM, Jason wrote:
> > > > On a RasperryPi with Raspbian, I would like to create a PDF Printer to
> > > > print files to. I only know how to do this with the GUI program
> > > > system-config-printer but I don't want to install that on this
> > > > Pi. What shell command do I need to create a PDF printer on the Pi (or
> > > > on any Debian, for that matter)?
> > > > 
> > > 
> > > Why do you want to"print" if you can convert to pdf using the command 
> > > line?
> > > Based on the original file extension you simply search for a utility that
> > > will convert your original file to pdf.
> > 
> > How does one convert a text file to a PDF using the command line?
> > 
> 
> Using enscript and ps2pdf (goastscript) for example.
> 
> https://www.gnu.org/software/enscript/
> https://www.ghostscript.com/doc/current/Ps2pdf.htm
> https://askubuntu.com/questions/27097/how-to-print-a-regular-file-to-pdf-from-command-line
> https://unix.stackexchange.com/questions/17406/how-to-convert-txt-to-pdf

Thanks, but I should have been clearer and more precise. I was after a
"one-step" utility which went directly from text to PDF. (cups-pdf gives
the appearence of doing that but it doesn't). You question its utility;
if pressed, I could agree with you.

I don't want to do through the intermediate Postscript production step.
But, perhaps, it is unavoidable.

-- 
Brian.



Re: Problem formatting a column to justify (i.e. line wrap)

2018-01-07 Thread Richard Owlett

On 01/07/2018 12:48 PM, David Wright wrote:

On Sun 07 Jan 2018 at 11:34:43 (-0600), Richard Owlett wrote:

I'm new to gnumeric and have not used any spreadsheet since mid 70's.
I'm running Debian 9.1 with MATE desktop and gnumeric 1.12.32 .

I have 2 columns with potentially long lines.
I had no problem selecting a preferred font size.
I created a spreadsheet allowing cells with with long lines to
truncate when displayed.

I then chose to justify. An inappropriate column with had been set
initially resulting in row height of 3 lines of text. I manually
dragged the column separator to an appropriate width resulting in a
desired height of 2 lines of text.

That row is stuck at a height of 3 lines of text.

How can I force each row height to be *NO* taller than necessary to
for the currently longest line?


To correct one row, double-click on the line underneath the row number
in the left hand margin.

To correct all the rows, click on the area just above the row number
for the first row (selects the entire sheet) and then double-click on
any of the lines like the one I described in the previous paragraph.

Cheers,
David.



Thank you.



Re: root privilege

2018-01-07 Thread Andrew M.A. Cater
On Sun, Jan 07, 2018 at 08:16:58AM -0700, Gary Sylvester wrote:
> How do I get root privilege in Debian 9?
> 
> Thank you,
> Gary

This is a debian-user question. By default, if you step through the
installer and _don't_ give a root password, then sudo is set up such
that the first created user is set up to use sudo.

Login as that user and type sudo [command]

At least that's what I'm assuming you're asking. If you want to 
get a root shell on any random Debian machine - no, sorry, won't help
- you have to do your own homework and (potentially) break your own
  laws.

  All the best,

  Andy C.




Re: How to create a PDF-Printer from the command line

2018-01-07 Thread rhkramer
On Sunday, January 07, 2018 01:15:06 PM Brian wrote:
> On Sun 07 Jan 2018 at 07:46:30 -0500, rhkra...@gmail.com wrote:

> > clarified, but I would point out that a variety of programs like txt2pdf
> > exist (and work)--I assume, but don't know that they are available in
> > the various Debian distros.
> 
> Which txt2pdf? 

Sorry, I don't remember--it must have been on a machine prior to my current 
one (with Wheezy) as I don't see it--the prior machine was Lenny, iirc (Debain 
5.n).

But my statement about variety of programs was more intended to say that there 
are programs like txt2pdf, pdf2txt, html2txt (iirce)--in other words, such 
programs to convert between a variety of formats.

> I tried the DFSG free one at
> 
> https://github.com/baruchel/txt2pdf
> 
> Not in Debian, AFAICT, but download, put in /usr/local/bin and install
> python-reportlab. Gives searchable PDFs, fonts can be selected more
> easily than with cupsfilter or cups-pdf and it has UTF-8 support. Looks
> useful.



Re: root privilege

2018-01-07 Thread john doe

On 1/7/2018 9:14 PM, Andrew M.A. Cater wrote:

On Sun, Jan 07, 2018 at 08:16:58AM -0700, Gary Sylvester wrote:

How do I get root privilege in Debian 9?

Thank you,
Gary


This is a debian-user question. By default, if you step through the
installer and _don't_ give a root password, then sudo is set up such
that the first created user is set up to use sudo.

Login as that user and type sudo [command]

At least that's what I'm assuming you're asking. 



If you did enter a root password:

$ su --login

--
John Doe



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread john doe

On 1/7/2018 9:01 PM, Brian wrote:

On Sat 06 Jan 2018 at 21:51:18 +0100, john doe wrote:


On 1/6/2018 9:15 PM, Brian wrote:

On Sat 06 Jan 2018 at 05:54:00 +0100, john doe wrote:


On 1/6/2018 4:06 AM, Jason wrote:

On a RasperryPi with Raspbian, I would like to create a PDF Printer to
print files to. I only know how to do this with the GUI program
system-config-printer but I don't want to install that on this
Pi. What shell command do I need to create a PDF printer on the Pi (or
on any Debian, for that matter)?



Why do you want to"print" if you can convert to pdf using the command line?
Based on the original file extension you simply search for a utility that
will convert your original file to pdf.


How does one convert a text file to a PDF using the command line?



Using enscript and ps2pdf (goastscript) for example.

https://www.gnu.org/software/enscript/
https://www.ghostscript.com/doc/current/Ps2pdf.htm
https://askubuntu.com/questions/27097/how-to-print-a-regular-file-to-pdf-from-command-line
https://unix.stackexchange.com/questions/17406/how-to-convert-txt-to-pdf


Thanks, but I should have been clearer and more precise. I was after a
"one-step" utility which went directly from text to PDF. (cups-pdf gives
the appearence of doing that but it doesn't). You question its utility;
if pressed, I could agree with you.

I don't want to do through the intermediate Postscript production step.


Why not (you can run both utilities in one go)?

--
John Doe



Re: How to create a PDF-Printer from the command line

2018-01-07 Thread Brian
On Sun 07 Jan 2018 at 21:41:16 +0100, john doe wrote:

> On 1/7/2018 9:01 PM, Brian wrote:
> > On Sat 06 Jan 2018 at 21:51:18 +0100, john doe wrote:
> > 
> > > On 1/6/2018 9:15 PM, Brian wrote:
> > > > On Sat 06 Jan 2018 at 05:54:00 +0100, john doe wrote:
> > > > 
> > > > > On 1/6/2018 4:06 AM, Jason wrote:
> > > > > > On a RasperryPi with Raspbian, I would like to create a PDF Printer 
> > > > > > to
> > > > > > print files to. I only know how to do this with the GUI program
> > > > > > system-config-printer but I don't want to install that on this
> > > > > > Pi. What shell command do I need to create a PDF printer on the Pi 
> > > > > > (or
> > > > > > on any Debian, for that matter)?
> > > > > > 
> > > > > 
> > > > > Why do you want to"print" if you can convert to pdf using the command 
> > > > > line?
> > > > > Based on the original file extension you simply search for a utility 
> > > > > that
> > > > > will convert your original file to pdf.
> > > > 
> > > > How does one convert a text file to a PDF using the command line?
> > > > 
> > > 
> > > Using enscript and ps2pdf (goastscript) for example.
> > > 
> > > https://www.gnu.org/software/enscript/
> > > https://www.ghostscript.com/doc/current/Ps2pdf.htm
> > > https://askubuntu.com/questions/27097/how-to-print-a-regular-file-to-pdf-from-command-line
> > > https://unix.stackexchange.com/questions/17406/how-to-convert-txt-to-pdf
> > 
> > Thanks, but I should have been clearer and more precise. I was after a
> > "one-step" utility which went directly from text to PDF. (cups-pdf gives
> > the appearence of doing that but it doesn't). You question its utility;
> > if pressed, I could agree with you.
> > 
> > I don't want to do through the intermediate Postscript production step.
> 
> Why not (you can run both utilities in one go)?

You have completely missed the point. "one-step" and "directly" were
the clues.

-- 

Brian



Re: vbox cannot find headers, although they are installed

2018-01-07 Thread Harry Putnam
"x9p"  writes:

> On Sat, January 6, 2018 11:36 pm, Harry Putnam wrote:
> ...
>> (Look at /var/log/vboxadd-install.log to find out what went wrong)
> ...
>
> the line above can explain a lot.

Looked at that for some length before posting... it didn't explain
dodo to me... didn't understand what I was reading,  maybe it will to you:

grep: /lib/modules/4.14.0-2-amd64/build/include/linux/version.h: No such file 
or directory
make KBUILD_VERBOSE=1 CONFIG_MODULE_SIG= -C /lib/modules/4.14.0-2-amd64/build 
SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
make -C /usr/src/linux-headers-4.14.0-2-amd64 
KBUILD_SRC=/usr/src/linux-headers-4.14.0-2-common \
-f /usr/src/linux-headers-4.14.0-2-common/Makefile modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f /usr/src/linux-headers-4.14.0-2-common/scripts/Makefile.build 
obj=/tmp/vbox.0
   gcc-7 -Wp,-MD,/tmp/vbox.0/.VBoxGuest-linux.o.d  -nostdinc -isystem 
/usr/lib/gcc/x86_64-linux-gnu/7/include 
-I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include 
-I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.14.0-2-common/include -I./include 
-I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-4.14.0-2-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-4.14.0-2-common/include/linux/kconfig.h  -I/tmp/vbox.0 
-I/tmp/vbox.0 -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar 
-Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE 
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 
-mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time 
-DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 
-DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 
-DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare 
-fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks 
-Wno-frame-address -Wno-format-truncation -Wno-format-overflow 
-Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 
-DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 -fstack-protector-strong 
-Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer 
-fno-optimize-sibling-calls -fno-var-tracking-assignments -g -pg -mfentry 
-DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign 
-fno-strict-overflow -fconserve-stack -Werror=implicit-int 
-Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types 
-Werror=designated-init -Wno-declaration-after-statement -include 
/tmp/vbox.0/include/VBox/VBoxGuestMangling.h -fno-pie  
-I/lib/modules/4.14.0-2-amd64/build/include  -I/tmp/vbox.0/  
-I/tmp/vbox.0/include  -I/tmp/vbox.0/r0drv/linux  -I/tmp/vbox.0/vboxguest/  
-I/tmp/vbox.0/vboxguest/include  -I/tmp/vbox.0/vboxguest/r0drv/linux 
-D__KERNEL__ -DMODULE -DVBOX -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_GUEST 
-DIN_GUEST_R0 -DIN_MODULE -DRT_WITH_VBOX -DVBGL_VBOXGUEST -DVBOX_WITH_HGCM 
-DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS  -DMODULE  
-DKBUILD_BASENAME='"VBoxGuest_linux"'  -DKBUILD_MODNAME='"vboxguest"' -c -o 
/tmp/vbox.0/.tmp_VBoxGuest-linux.o /tmp/vbox.0/VBoxGuest-linux.c
  if [ "-pg" = "-pg" ]; then if [ /tmp/vbox.0/VBoxGuest-linux.o != 
"scripts/mod/empty.o" ]; then ./scripts/recordmcount  
"/tmp/vbox.0/VBoxGuest-linux.o"; fi; fi;
   gcc-7 -Wp,-MD,/tmp/vbox.0/.VBoxGuest.o.d  -nostdinc -isystem 
/usr/lib/gcc/x86_64-linux-gnu/7/include 
-I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include 
-I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.14.0-2-common/include -I./include 
-I/usr/src/linux-headers-4.14.0-2-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-4.14.0-2-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-4.14.0-2-common/include/linux/kconfig.h  -I/tmp/vbox.0 
-I/tmp/vbox.0 -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -fshort-wchar 
-Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE 
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 
-falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 
-mskip-rax-setup -mtune=gener