Re: Teeny tiny console font after firmware-linux

2015-05-20 Thread Umarzuki Mochlis
2015-05-21 11:10 GMT+08:00 Bob Bernstein : > I always cleave to my number one fundamental rule: if it ain't > broke don't fix it. Unless of course curiosity comes into the > picture and momentarily releases the crazy person who lives in > my head. > > It wasn't pure unalloyed curiosity. I did see a

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alexis
Ansgar Burchardt writes: Or just look in /usr/local/lib. Looking in that directory, i saw various libpoppler libraries installed; removing them fixed the issue. :-) My thanks to you and everyone else who helped me on this! Alexis. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alexis
Ansgar Burchardt writes: Usually the problematic (locally-installed) libraries should be in /usr/local. So you could try looking at the output of "ldd" for libraries located there. Running: $ ldd /usr/bin/evince | grep /usr/local/ returned no results, nor did: $ ldd /usr/bin/okular

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alexis
Martin Read writes: On 20/05/15 13:47, Alexis wrote: i do[1]; but how can i find out which library is the one calling libtiff4? E.g. do i need to make use of something like strace(1), or to methodically work through the output of ldd(1)? The following *should* do the trick: find /usr/lib

Teeny tiny console font after firmware-linux

2015-05-20 Thread Bob Bernstein
I always cleave to my number one fundamental rule: if it ain't broke don't fix it. Unless of course curiosity comes into the picture and momentarily releases the crazy person who lives in my head. It wasn't pure unalloyed curiosity. I did see a line in dmesg telling me I should install the pac

Re: Issues with openvpn and virtualbox as the sole networking provider

2015-05-20 Thread John T. Haggerty
Also this workaround fails to work http://www.blackmoreops.com/2015/03/01/setup-vpn-on-kali-linux/ Again provider agnostic On Wed, May 20, 2015 at 6:28 PM, John T. Haggerty wrote: > For example here > http://www.ibvpn.com/billing/knowledgebase/50/Set-up-the-PPTP-VPN-connection-on-Linux-Network-

Re: Issues with openvpn and virtualbox as the sole networking provider

2015-05-20 Thread John T. Haggerty
For example here http://www.ibvpn.com/billing/knowledgebase/50/Set-up-the-PPTP-VPN-connection-on-Linux-Network-Manager-GUI.html fails to work for me on Debian gnome. This is not the provider in question however. On Tue, May 19, 2015 at 2:31 PM, John T. Haggerty wrote: > I don't know if I am able

RE: strange booting behavior

2015-05-20 Thread Arno Schuring
Hi, > On 5/19/15, Arno Schuring wrote: > > > > Note that you can add break=premount to the kernel cmdline > > to force an initramfs shell, then use sh -x /scripts/$phase/$script > > to manually step through the initramfs procedure. > > > > You can use "grep maybe_break /usr/share/initramfs-tools

Re: Colorized Prompts Problem - Thanks for the Deconstruction

2015-05-20 Thread Chris Bannister
On Fri, May 15, 2015 at 09:49:12PM -0500, David Wright wrote: > Quoting Thomas H. George (li...@tomgeorge.info): > > > > > Your explanation is very helpful, converts the jumble I copied from a > > website into a logical sequence of instructions. I really appreciate > > being able to understand the

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Ansgar Burchardt
On 05/20/2015 02:47 PM, Alexis wrote: > Sven Arvidsson writes: >> Do you have old versions of libraries lying around? Maybe things you >> compiled and installed yourself? > > i do[1]; but how can i find out which library is the one calling > libtiff4? E.g. do i need to make use of something like

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Martin Read
On 20/05/15 13:47, Alexis wrote: i do[1]; but how can i find out which library is the one calling libtiff4? E.g. do i need to make use of something like strace(1), or to methodically work through the output of ldd(1)? The following *should* do the trick: find /usr/lib -type f -name '*.so*' -pr

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alexis
Hi Sven, Thanks for your response! Sven Arvidsson writes: On Wed, 2015-05-20 at 18:54 +1000, Alexis wrote: They don't. I think something is broken on your system. i agree. :-) (i'm pretty sure that if the problem extended beyond my system, there would be no shortage of people noting

Re: aufs support in linux-image-4.0.0-1-686-pae

2015-05-20 Thread Sven Arvidsson
On Wed, 2015-05-20 at 10:03 +0530, rajiv chavan wrote: > Aufs support dropped in linux-image-4.0.0-1-686-pae? Or in all 4.0 > debian-kernels > Any way to add module? Hi, It was dropped in 3.18 in favour of overlayfs: https://lists.debian.org/debian-live/2014/12/msg00041.html There doesn't seem t

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Sven Arvidsson
On Wed, 2015-05-20 at 18:54 +1000, Alexis wrote: > > libtiff4 is not available in jessie. > > Indeed, which is why i find it odd that such significant packages > as `evince` (version 3.14.1-2) and `okular` (version 4:4.14.2-2) > are apparently requiring it. They don't. I think something is br

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Martin Read
On 20/05/15 09:54, Alexis wrote: Indeed, which is why i find it odd that such significant packages as `evince` (version 3.14.1-2) and `okular` (version 4:4.14.2-2) are apparently requiring it. A bit of tooling around with grep and ldd suggests that it's not evince and okular that are demanding

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alexis
Hi Alex, Thanks for your response! Alex Mestiashvili writes: On 05/20/2015 08:44 AM, Alexis wrote: Hi all, Context: jessie x86_64 [+updates], recently upgraded from wheezy. i've started having a strange issue where none of `evince`, `atril` or `okular` can open PDFs. All produce the

Re: jessie: `evince`, `atril`, `okular` unable to open PDFs; "libtiff.so.4: cannot open shared object file: No such file or directory"

2015-05-20 Thread Alex Mestiashvili
On 05/20/2015 08:44 AM, Alexis wrote: Hi all, Context: jessie x86_64 [+updates], recently upgraded from wheezy. i've started having a strange issue where none of `evince`, `atril` or `okular` can open PDFs. All produce the error: libtiff.so.4: cannot open shared object file: No such fil