Re: Re: Re: debian and wol on Buffalo Linkstation WXL

2017-12-27 Thread Paul Wise
On Thu, Dec 28, 2017 at 11:52 AM, Adam Borowski wrote: > glibc in stretch requires kernel 3.2, systemd kernel 3.13. Most kernels you > get on vendor images are 3.4, 3.8 or 3.10 -- all of them good for stretch in > general but not for systemd; other packages with kernel requirements are >

Re: Re: Re: debian and wol on Buffalo Linkstation WXL

2017-12-27 Thread Adam Borowski
On Thu, Dec 28, 2017 at 07:31:03AM +0800, Paul Wise wrote: > On Thu, Dec 28, 2017 at 3:25 AM, rosanna wrote: > > > ... but, at reboot, ssh and telnet access are no more available > ... > > any idea on what can be the cause? > > It is possible that Debian is not compatible with the version of the

Re: Plasma-mobile on cubox-i

2017-12-27 Thread Paul Wise
On Thu, Dec 28, 2017 at 5:27 AM, Rainer Dorsch wrote: > Do you have any idea what I might have done wrong? Are there any logs > available (first time I am running wayland and not an xserver)? Sounds like a bug in kwin, please install debug symbols (run find-dbgsym-packages from debian-goodies on

Re: Re: Re: debian and wol on Buffalo Linkstation WXL

2017-12-27 Thread Paul Wise
On Thu, Dec 28, 2017 at 3:25 AM, rosanna wrote: > ... but, at reboot, ssh and telnet access are no more available ... > any idea on what can be the cause? It is possible that Debian is not compatible with the version of the Linux kernel available in the original rootfs, it might be too old for

Plasma-mobile on cubox-i

2017-12-27 Thread Rainer Dorsch
Hi Bhushan and Matthias, I closely followed https://puri.sm/posts/running-plasma-mobile-on-an-imx6-test-board/ but after starting kwin_wayland --drm --xwayland plasma-phone all I got was a segmentation fault. I also tried kwin_wayland --drm --xwayland plasma-phone but same result. Do you

Re: Re: Re: debian and wol on Buffalo Linkstation WXL

2017-12-27 Thread rosanna
I think I've understood and followed correctly your suggested process, substituting the bootloader files by making a symbolik link to the original ones ... but, at reboot, ssh and telnet access are no more available nmap says that all ports are closed, the only way to access the unit is

Re: Reschedule Thunderbird 52.5.2-2 for armel

2017-12-27 Thread Carsten Schoenert
Hello Adrian, Am 27.12.2017 um 14:24 schrieb John Paul Adrian Glaubitz: > Hi Carsten! > > On 12/27/2017 01:18 PM, Carsten Schoenert wrote: >> /tmp/ccEJuOJM.s: Assembler messages: >> /tmp/ccEJuOJM.s:5366: Error: bad instruction `ocfi_def_cfa_offset 0' >> Please submit a full bug report, >> with

Re: Reschedule Thunderbird 52.5.2-2 for armel

2017-12-27 Thread John Paul Adrian Glaubitz
Hi Carsten! On 12/27/2017 01:18 PM, Carsten Schoenert wrote: > /tmp/ccEJuOJM.s: Assembler messages: > /tmp/ccEJuOJM.s:5366: Error: bad instruction `ocfi_def_cfa_offset 0' > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. That's not a segfault

Reschedule Thunderbird 52.5.2-2 for armel

2017-12-27 Thread Carsten Schoenert
Dear buildd admins, could you please reschedule a build of thunderbird 1:52.5.2-2 for armel? The last build attempt was ending with a segfault of the compiler. https://buildd.debian.org/status/fetch.php?pkg=thunderbird=armel=1%3A52.5.2-2=1514304906=0 > g++-6