On 11/26/24 12:59, Mario Marietto wrote:
2)
# apt install nvidia-detect nvidia-driver
You first did an `update`.
Also the wiki at [1] suggest to install other PKGs.
[1]
https://www.reddit.com/r/debian/comments/1h08w9v/ssl_error8002system_libraryno_such/?rdt=41730
--
John Doe
/sign-file sha512
/var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der
/lib/modules/5.19.0-23-generic/updates/dkms/nvidia.ko
At main.c:298:
- SSL error:8002:system library::No such file or directory:
../crypto/bio/bss_file.c:67
- SSL error:1080:BIO routines::no suc
o chroot within it :
>
> root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
> chroot ./jessie-armhf /bin/bash
>
> it gives the following error :
>
> chroot: can't execute command "/bin/bash": No such file or directory
Omit the interpreter:
#
On Sun, 18 Jun 2023, Mario Marietto wrote:
Hello.
with qemu works,but I thought that it was better to avoid the usage of
qemu.
I'm a bit puzzled what you're trying to do.
if you want to chroot on an amd64 machine then you have to use something
like qemu to emulate the armhf processor.
If yo
I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the d
debian.org/debian <http://archive.debian.org/debian>
>> >
>> > and it worked ok,but when I try to chroot within it :
>> >
>> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>>
>> > chroot ./jessie-armhf /bin/bash
&
http://archive.debian.org/debian <http://archive.debian.org/debian>
> >
> > and it worked ok,but when I try to chroot within it :
> >
> > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
>
> > chroot ./jessie-armhf /bin/bash
&g
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
bian.org/debian>
and it worked ok,but when I try to chroot within it :
root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
7-HD3:/home/marietto/Scrivania/Chromebook/linux-distros#
chroot ./jessie-armhf /bin/bash
it gives the following error :
chroot: can't execute command "/bin/bash": No such file or directory
but I see the file bash within the directory /bin of the debootstrapped
directory called
Thanks Reco,
I don't know how you keep up after all these years seen you here on the
debian list.
Congrats.
Beco.
On Tue, 15 Sep 2020 at 11:36, Reco wrote:
> Hi.
>
> On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> > Is this pam module deprecated?
>
> Yes, it was removed fr
Hi.
On Tue, Sep 15, 2020 at 11:19:39AM -0300, Beco wrote:
> Is this pam module deprecated?
Yes, it was removed from main archive back in 2018 - [1].
> I can't find the package that provides it on
> debian buster.
There's no package in buster that provides the PAM module or ConsoleKit
it
urity/pam_ck_connector.so:
cannot open shared object file: No such file or directory
What is the correct secure approach? Should I just remove the optional
session line from PAM config?
I can't even find consolekit for buster.
Maybe this is old news (gentoo reports no activity on this since 2017
I'm getting the error
avahi-daemon: Failed to open /etc/resolv.conf: Invalid argument
chroot.c: open() failed: No such file or directory
at boot.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800643
Is the workaround mentioned above (and below) still valid (bug date Oct
Foundation 2.0 root hub
root@kali:~# airmon-ng
ls: cannot access '/sys/class/ieee80211/': No such file or directory
PHY Interface Driver Chipset
root@kali:~# airmon-ng check kill
ls: cannot access '/sys/class/ieee80211/': No such file or directory
Killing these pr
On Tue 27 Sep 2016 at 12:05:37 -0400, Greg Wooledge wrote:
> On Tue, Sep 27, 2016 at 04:52:34PM +0100, Brian wrote:
> > You need a ~/.xsession file when you need a ~/.xsession file. Isn't it
> > one purpose of the wiki to explain how it fits into the traditional X
> > configuration and why one mig
On Tue, Sep 27, 2016 at 04:52:34PM +0100, Brian wrote:
> You need a ~/.xsession file when you need a ~/.xsession file. Isn't it
> one purpose of the wiki to explain how it fits into the traditional X
> configuration and why one might be useful. Instead, we appear to have
> ~/.xsessionrc promoted as
On Tue 27 Sep 2016 at 10:29:44 -0400, Greg Wooledge wrote:
> On Tue, Sep 27, 2016 at 03:15:54PM +0100, Brian wrote:
> > Ok, let's go along with ~/.xsessionrc being the simplest way for a user
> > to configure his X session. I'll follow the advice on the wiki and have
> >
> > PATH=~/bin:$PATH
>
On Tue, Sep 27, 2016 at 03:15:54PM +0100, Brian wrote:
> Ok, let's go along with ~/.xsessionrc being the simplest way for a user
> to configure his X session. I'll follow the advice on the wiki and have
>
> PATH=~/bin:$PATH
> xterm &
> iceweasel &
> exec fvwm
No, this is not what I advise
On Mon 26 Sep 2016 at 17:44:17 -0400, Greg Wooledge wrote:
> On Mon, Sep 26, 2016 at 10:19:27PM +0100, Brian wrote:
> > But now we have
> >
> > > User configuration may be done in a few different ways. The simplest
> > > way is to create a ~/.xsessionrc file,.
> >
> > The pedantic side of
On Mon, Sep 26, 2016 at 05:58:59PM -0400, Neal P. Murphy wrote:
> A semantic observation (probably unrelated to the aforementioned editing):
> "... dot in ..." might be more clearly stated as "... source ( or '.') in
> ..." because the action is to source the script into the current shell (thus
> r
On Mon, Sep 26, 2016 at 10:46:07PM -0700, Seeker wrote:
> It's possible that something changed with gdm3 after I stopped using it,
> or that it's been long enough I just don't remember, but I don't
> remember any of these in recent years using the .xsession file if you
> use a session other than
On 9/26/2016 2:44 PM, Greg Wooledge wrote:
On Mon, Sep 26, 2016 at 10:19:27PM +0100, Brian wrote:
But now we have
> User configuration may be done in a few different ways. The simplest
> way is to create a ~/.xsessionrc file,.
The pedantic side of me asks - why is it the simplest way? An
On Mon, 26 Sep 2016 22:19:27 +0100
Brian wrote:
> On Sun 25 Sep 2016 at 18:55:03 +0100, Brian wrote:
>
> > The existence of ~/.xessionrc appears to cause more problems than it
> > purportedly solves.
>
> And it still won't lie down and die. It is determined to take over the
> traditional role o
On Mon, Sep 26, 2016 at 10:19:27PM +0100, Brian wrote:
> But now we have
>
> > User configuration may be done in a few different ways. The simplest
> > way is to create a ~/.xsessionrc file,.
>
> The pedantic side of me asks - why is it the simplest way? And in what
> cirumstances?
Because
On Sun 25 Sep 2016 at 18:55:03 +0100, Brian wrote:
> The existence of ~/.xessionrc appears to cause more problems than it
> purportedly solves.
And it still won't lie down and die. It is determined to take over the
traditional role of ~/.xsession and prove its worth. However, kudos for
the editin
On Sat 24 Sep 2016 at 20:38:50 +0100, Brian wrote:
> On Fri 23 Sep 2016 at 17:36:11 +0100, Brian wrote:
>
> I don't think I shall be pointing a user to this wiki page in its
> present state.
~/.xessionrc as the primary file for configuring startup of X is not
only not necessary but has a disadva
On Fri 23 Sep 2016 at 17:36:11 +0100, Brian wrote:
> ~/.xsessionrc was introduced in 2007 in response to a perceived problem.
> If the choice of DE (or WM) and terminal is left in the care of the
> system's x-session-manager, x-window-manager and x-terminal-emulator
> nothing need be put in ~/.xse
On 9/23/2016 10:28 AM, Brian wrote:
On Fri 23 Sep 2016 at 10:07:43 -0700, Seeker wrote:
On 9/22/2016 6:18 PM, Seeker wrote:
In spite of the existence of 60xprofile and the fact that '~/.xprofile' did
get sourced in the ast, I'm not finding any information on when you
might expect xprofile
On Fri 23 Sep 2016 at 10:07:43 -0700, Seeker wrote:
> On 9/22/2016 6:18 PM, Seeker wrote:
> >On 9/22/2016 10:45 AM, Brian wrote:
> >>On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote:
> >>
> >>>On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
> A little late, but personally I wo
On 9/22/2016 6:18 PM, Seeker wrote:
On 9/22/2016 10:45 AM, Brian wrote:
On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote:
On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
A little late, but personally I would have tried using '~/.xprofile'
first.
I believe the information abo
On Thu 22 Sep 2016 at 16:19:26 -0400, Greg Wooledge wrote:
> I've edited https://wiki.debian.org/LightDM and written
> https://wiki.debian.org/Xsession from scratch. I hope this helps other
> people who were as lost and confused as I was.
>
> If you're still wondering what kind of documentation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 23, 2016 at 11:31:20AM +0200, to...@tuxteam.de wrote:
[...]
> > It makes a big difference for remote applications, since they will see the
> > .Xresources from the server but the .Xdefaults from the client.
Forgot to say that typically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Sep 23, 2016 at 08:57:18AM +, Curt wrote:
[...]
> Nicolas Georges gave some interesting information once when I said that
> .Xdefaults was "deprecated" concerning what is read by what where and
> why (went over my head, of course).
>
> H
On 2016-09-22, Dominic Knight wrote:
> On Thu, 2016-09-22 at 16:19 -0400, Greg Wooledge wrote:
>> I've edited https://wiki.debian.org/LightDM and written
>> https://wiki.debian.org/Xsession from scratch. I hope this helps
>> other
>> people who were as lost and confused as I was.
>>
>> If you're
On 9/22/2016 10:45 AM, Brian wrote:
On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote:
On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
A little late, but personally I would have tried using '~/.xprofile'
first.
I believe the information about this from the Arch Wiki applies eq
On Thu, 2016-09-22 at 16:19 -0400, Greg Wooledge wrote:
> I've edited https://wiki.debian.org/LightDM and written
> https://wiki.debian.org/Xsession from scratch. I hope this helps
> other
> people who were as lost and confused as I was.
>
> If you're still wondering what kind of documentation I
I've edited https://wiki.debian.org/LightDM and written
https://wiki.debian.org/Xsession from scratch. I hope this helps other
people who were as lost and confused as I was.
If you're still wondering what kind of documentation I was looking for,
you may use https://wiki.debian.org/Xsession as the
On Thu 22 Sep 2016 at 09:11:53 -0400, Greg Wooledge wrote:
> On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
> > But I don't understand the concept of "user configuration" for a DM.
> > Wouldn't that be like a user configuring /etc/issue, the login prompt
> > or /etc/motd ?
>
> By u
On Thu 22 Sep 2016 at 09:11:53 -0400, Greg Wooledge wrote:
> On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
>
> > I'm not a DE or DM user, so I'm know very little about them.
>
> Yes, THIS is the problem! You, and I, and everyone else on the guru side
> are just completely stumpe
On Thu, 2016-09-22 at 10:56 -0400, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
> > I edit ~/.xsessionrc to have a single line:
> >
> > . /home/tixy/.profile
>
> [...] how did you learn about it?
Reading the debian-user list for many years :-)
--
Tixy
On Thu 22 Sep 2016 at 12:10:35 -0400, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
> > A little late, but personally I would have tried using '~/.xprofile'
> > first.
> >
> > I believe the information about this from the Arch Wiki applies equally
> > to Debian.
>
On Thu 22 Sep 2016 at 16:10:01 +0100, Darac Marjal wrote:
> On Thu, Sep 22, 2016 at 10:56:49AM -0400, Greg Wooledge wrote:
> >On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
> >>I edit ~/.xsessionrc to have a single line:
> >>
> >>. /home/tixy/.profile
> >
> >Which program reads ~/.x
On 9/21/2016 12:07 PM, Anthony Baldwin wrote:
On 09/21/2016 11:05 AM, Greg Wooledge wrote:
On Wed, Sep 21, 2016 at 10:49:13AM -0400, Tony Baldwin wrote:
it seems that I am using lightdm.
I know of absolutely no documentation for configuring lightdm as a
user. I suspect that the software *has
On 09/22/2016 09:59 AM, Greg Wooledge wrote:
On Thu, Sep 22, 2016 at 02:50:30PM +0100, Brian wrote:
To read the manual
apt-get download lightdm
works every time.
Hmm, well.
$ cd /tmp
$ apt-get download lightdm
$ ls, man dpkg, ...
$ dpkg -x lightdm_1.10.3-3_amd64.deb ldm
$ gzip -dc ldm/usr
On Thu, Sep 22, 2016 at 09:00:11AM -0700, Seeker wrote:
> A little late, but personally I would have tried using '~/.xprofile'
> first.
>
> I believe the information about this from the Arch Wiki applies equally
> to Debian.
>
> https://wiki.archlinux.org/index.php/xprofile
wooledg@wooledg:~$ gr
On 9/22/2016 8:25 AM, Tony Baldwin wrote:
On 09/22/2016 10:15 AM, Tixy wrote:
On Thu, 2016-09-22 at 09:11 -0400, Greg Wooledge wrote:
On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
But I don't understand the concept of "user configuration" for a DM.
Wouldn't that be like a user
On Thu 22 Sep 2016 at 10:56:49 -0400, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
> > I edit ~/.xsessionrc to have a single line:
> >
> > . /home/tixy/.profile
>
> Which program reads ~/.xsessionrc
X.
> and how did you
On 09/22/2016 10:15 AM, Tixy wrote:
On Thu, 2016-09-22 at 09:11 -0400, Greg Wooledge wrote:
On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
But I don't understand the concept of "user configuration" for a DM.
Wouldn't that be like a user configuring /etc/issue, the login
prompt
On Thu, Sep 22, 2016 at 10:56:49AM -0400, Greg Wooledge wrote:
On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
I edit ~/.xsessionrc to have a single line:
. /home/tixy/.profile
Which program reads ~/.xsessionrc and how did you learn about it?
Which man page describes it? Does i
On Thu, Sep 22, 2016 at 03:15:40PM +0100, Tixy wrote:
> I edit ~/.xsessionrc to have a single line:
>
> . /home/tixy/.profile
Which program reads ~/.xsessionrc and how did you learn about it?
Which man page describes it? Does its existence merely "add on" to some
system-wide default scri
On Thu 22 Sep 2016 at 09:59:07 -0400, Greg Wooledge wrote:
> On Thu, Sep 22, 2016 at 02:50:30PM +0100, Brian wrote:
> > To read the manual
> >
> > apt-get download lightdm
> >
> > works every time.
>
> Hmm, well.
Worked, didn't it? A two second operation.
> $ cd /tmp
> $ apt-get download li
On Thu, 2016-09-22 at 09:11 -0400, Greg Wooledge wrote:
> On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
> > But I don't understand the concept of "user configuration" for a DM.
> > Wouldn't that be like a user configuring /etc/issue, the login
> prompt
> > or /etc/motd ?
>
> By use
On Thu, Sep 22, 2016 at 02:50:30PM +0100, Brian wrote:
> To read the manual
>
> apt-get download lightdm
>
> works every time.
Hmm, well.
$ cd /tmp
$ apt-get download lightdm
$ ls, man dpkg, ...
$ dpkg -x lightdm_1.10.3-3_amd64.deb ldm
$ gzip -dc ldm/usr/share/man/man1/lightdm.1.gz | nroff -m
On Thu 22 Sep 2016 at 09:11:53 -0400, Greg Wooledge wrote:
> Don't believe me? I know none of us has lightdm installed, so here is
> a man page, allegedly from Debian wheezy:
>
> http://www.unix.com/man-page/debian/1/lightdm/
>
> It takes several tries for me even to find *that*, probably becau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Sep 22, 2016 at 09:11:53AM -0400, Greg Wooledge wrote:
[...]
> Don't believe me? I know none of us has lightdm installed, so here is
> a man page, allegedly from Debian wheezy:
>
> http://www.unix.com/man-page/debian/1/lightdm/
>
> It take
On Wed, Sep 21, 2016 at 09:19:11PM -0500, David Wright wrote:
> But I don't understand the concept of "user configuration" for a DM.
> Wouldn't that be like a user configuring /etc/issue, the login prompt
> or /etc/motd ?
By user configuration, I mean "which files can the user edit, without
superu
On Wed 21 Sep 2016 at 15:07:09 (-0400), Anthony Baldwin wrote:
> On 09/21/2016 11:05 AM, Greg Wooledge wrote:
> >On Wed, Sep 21, 2016 at 10:49:13AM -0400, Tony Baldwin wrote:
> >>it seems that I am using lightdm.
> >
> >I know of absolutely no documentation for configuring lightdm as a
> >user. I
On 09/21/2016 11:05 AM, Greg Wooledge wrote:
On Wed, Sep 21, 2016 at 10:49:13AM -0400, Tony Baldwin wrote:
it seems that I am using lightdm.
I know of absolutely no documentation for configuring lightdm as a
user. I suspect that the software *has* no user configuration at all,
because every s
On 09/21/2016 11:20 AM, Thomas Schmitt wrote:
Hi,
Anthony Baldwin wrote:
giving the full path in the rc.xml doesn't seem to make
any difference.
Are you sure openbox is aware of the change ?
(Did you restart it ? Does it react immediately on newly added
key combinations ?)
Normally, yes, O
On Wed, Sep 21, 2016 at 05:20:31PM +0200, Thomas Schmitt wrote:
> You could put a script into /usr/bin (where it will be found, i hope),
> let it print the PATH to a file, bind it to a key combination, and
> look what it writes into the file:
> #!/bin/sh
> echo "$PATH" >/tmp/my_openbox_test_for
Hi,
Anthony Baldwin wrote:
> giving the full path in the rc.xml doesn't seem to make
> any difference.
Are you sure openbox is aware of the change ?
(Did you restart it ? Does it react immediately on newly added
key combinations ?)
> Yes, the $PATH is set in my .bashrc...
> Wait.. Is this why
Sorry that you're getting this twice again, Thomas,
but I keep flummoxing the list-reply function (old age + brain tumor).
Tony
On 09/21/2016 09:54 AM, Thomas Schmitt wrote:
Hi,
Tony Baldwin wrote:
.config/openbox/rc.xml
bid
Well, a short while ago with cron it helped to tell the c
On Wed, Sep 21, 2016 at 10:49:13AM -0400, Tony Baldwin wrote:
> it seems that I am using lightdm.
I know of absolutely no documentation for configuring lightdm as a
user. I suspect that the software *has* no user configuration at all,
because every search I've ever done has come up with nothing.
? Which one?
it seems that I am using lightdm.
when I press W-b, and some others I get this:
Failed to execute child process (no such file or directory)
And you believe it's because of a PATH mismatch. OK. I don't have
experience with whichever desktop or window manager this is.
T
and some others I get this:
> Failed to execute child process (no such file or directory)
And you believe it's because of a PATH mismatch. OK. I don't have
experience with whichever desktop or window manager this is.
> But the script IS in ~/bin/
> $ which bid
> /home/tony/
, and some others I get this:
Failed to execute child process (no such file or directory)
But the script IS in ~/bin/
$ which bid
/home/tony/bin/bid
and that dir IS in my $PATH:
$ echo $PATH
/home/tony/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
and it IS executable:
$ ls -la bin/ |
Hi,
Tony Baldwin wrote:
> .config/openbox/rc.xml
> bid
Well, a short while ago with cron it helped to tell the clueless
software where the script is by an absolute path.
Probably:
/home/tony/bin/bid
> Shortuts for stuff in /bin/ or /usr/bin/ [...] seem to work fine
What user st
ocess (no such file or directory)
But the script IS in ~/bin/
$ which bid
/home/tony/bin/bid
and that dir IS in my $PATH:
$ echo $PATH
/home/tony/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
and it IS executable:
$ ls -la bin/ | grep bid
-rwxr-xr-x 1 tony tony 142 Oct 4 2012
/passenger-config
App 670 stderr: : No such file or directory
App 670 stderr:
Cheers Bram
apache redmine site configuration:
NameVirtualhost *:443
ServerName redmine
PassengerDefaultUser www-data
# FcgidInitialEnv for module mod_fcgid
FcgidInitialEnv
Martin Read writes:
xargs would receive that list, separate it at the NULs, and pass
the resulting strings as command line arguments to grep (across
multiple executions if the list is long enough to blow out the
limit on command line size)
grep would then search each of the files identi
On 21/05/15 06:24, Alexis wrote:
Martin Read writes:
The following *should* do the trick:
find /usr/lib -type f -name '*.so*' -print0 | xargs -0 grep libtiff.so.4
(It comes up empty on my jessie system, whereas putting libtiff.so.5
in the arguments to grep gives me a nice long list.)
That
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.
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
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
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
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
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
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
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
e the error:
libtiff.so.4: cannot open shared object file: No such file
or
directory
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 requiri
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
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 file or
directory
Indeed, `l
On Mon, May 05, 2014 at 08:50:58AM +0900, Joel Rees wrote:
> Although, if we wanted to get really crazy, we could say this is a bug in
> the spec of ld. But if we go there, we have to acknowledge that the spec of
> ld matches the general C/*nix run-time spec, so the bug is in ... (chasing
> our se
On Mon, May 5, 2014 at 8:34 AM, Tom Furie wrote:
> On Mon, May 05, 2014 at 06:44:30AM +0900, Joel Rees wrote:
>
> > Well, okay, we need to start somewhere, and, while we suspect ld, we
> don't
> > really know for sure. And we suspect that the actual fix may not end up
> > being in ld.
> >
> > So,
On Mon, May 05, 2014 at 06:44:30AM +0900, Joel Rees wrote:
> Well, okay, we need to start somewhere, and, while we suspect ld, we don't
> really know for sure. And we suspect that the actual fix may not end up
> being in ld.
>
> So, what is the name of the package that is trying to load libc6:i38
On Mon, May 5, 2014 at 6:44 AM, Joel Rees wrote:
>
> On Mon, May 5, 2014 at 5:07 AM, Tom Furie wrote:
>
>> On Sun, May 04, 2014 at 12:03:17PM -0400, Tom H wrote:
>>
>> > But installing libc6:i386 and a few others allows firefox to work:
>>
>> Meaning installing the :i386 versions of the librarie
On Mon, May 5, 2014 at 5:07 AM, Tom Furie wrote:
> On Sun, May 04, 2014 at 12:03:17PM -0400, Tom H wrote:
>
> > But installing libc6:i386 and a few others allows firefox to work:
>
> Meaning installing the :i386 versions of the libraries was (part of) the
> solution, not the problem. Any bug repo
On Sun, May 04, 2014 at 12:03:17PM -0400, Tom H wrote:
> But installing libc6:i386 and a few others allows firefox to work:
Meaning installing the :i386 versions of the libraries was (part of) the
solution, not the problem. Any bug report would have to go against a
part of the system that was par
On Sun, May 4, 2014 at 5:35 AM, Tom Furie wrote:
> On Sun, May 04, 2014 at 06:23:05PM +0900, Joel Rees wrote:
>> On Sun, May 4, 2014 at 8:05 AM, Tom Roche wrote:
>>>
>>> summary: solution: install jessie package=libc6:i386 et al
>>>
>>
>> Well, you've actually pinned the problem pretty well. Who,
On Sun, May 04, 2014 at 06:23:05PM +0900, Joel Rees wrote:
> On Sun, May 4, 2014 at 8:05 AM, Tom Roche wrote:
>
> >
> > summary: solution: install jessie package=libc6:i386 et al
> >
>
> Well, you've actually pinned the problem pretty well. Who, or, rather,
> which tool should be responsible for
On Sun, May 4, 2014 at 8:05 AM, Tom Roche wrote:
>
> summary: solution: install jessie package=libc6:i386 et al
>
Well, my understanding is that it's likely a temporary solution. And not a
recommended one. (Think carefully about the about the recent fuss about the
openssl vulnerability.)
You ne
Well, at least, if you have a dangling hard link, the file system itself is
broken. And it would not be the normal kind of breakage, at all.
rm will not actually de-allocate a file until all hard links have been
rm-ed, in file systems where multiple hard links are allowed. That is, when
you first
essence of the problem appears to be
>
> me@it ~ $ /usr/local/share/firefox-3.6.28/firefox-bin
> bash: /usr/local/share/firefox-3.6.28/firefox-bin: No such file or
> directory
> [127]me@it ~ $ lsalh /usr/local/share/firefox-3.6.28/firefox-bin
> -rwxr-xr-x 1 root staff 44K Mar 6
Ralf Mardorf wrote, on 05/04/2014 01:55:
> On Sun, 2014-05-04 at 01:53 +0200, Ralf Mardorf wrote:
>> On Sun, 2014-05-04 at 01:05 +0200, Jörg-Volker Peetz wrote:
> $ touch x
> $ ln -s x firefox-bin
>>
>> JFTR
>>
>> I guess your intention was
>>
>> ln -s firefox-bin x
>>
>> ;).
>
> Mumpitz (
On 05/03/2014 09:15 PM, Paul E Condon wrote:
On 20140502_1600-0700, David Christensen wrote:
But, it looks like Debian Wheezy packages are now (were then?) available:
2014-05-02 15:51:20 dpchrist@desktop ~
$ apt-cache search mate | egrep '^mate' | head
mate-applets - Various apple
On Sat, 3 May 2014 22:15:27 -0600
Paul E Condon wrote:
>
> I'm running Wheezy and using xfce4. Aptitude shows no sign of 'mate-*'
> packages mentioned above. I wonder how this could be ..., probably
> an error on my part... but what?
>
Wheezy is the stable release, so the Mate packages will
On 20140502_1600-0700, David Christensen wrote:
> On 05/02/2014 03:33 PM, John Hasler wrote:
> >The MATE Packaging Team will be
> >amazed to learn that.
>
> That's news to me. I used the following information:
>
> http://mate-desktop.org/
>
> MATE is available via unofficial repositori
On Sun, 2014-05-04 at 01:53 +0200, Ralf Mardorf wrote:
> On Sun, 2014-05-04 at 01:05 +0200, Jörg-Volker Peetz wrote:
> > >> $ touch x
> > >> $ ln -s x firefox-bin
>
> JFTR
>
> I guess your intention was
>
> ln -s firefox-bin x
>
> ;).
Mumpitz (humbug), now I'm mistaken :D.
--
To UNSUBSCRIB
On Sun, 2014-05-04 at 01:05 +0200, Jörg-Volker Peetz wrote:
> >> $ touch x
> >> $ ln -s x firefox-bin
JFTR
I guess your intention was
ln -s firefox-bin x
;).
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
1 - 100 of 324 matches
Mail list logo
