bug#58219: ubuntu 22.04.1 LTS

bug#58219: ubuntu 22.04.1 LTS

[Gwang-Jin Kim]

[-- Attachment #1: Type: text/plain, Size: 256 bytes --]

I did

```
conda create --name emacs
conda activate emacs
conda install -c conda-forge emacs  # downloaded v28
emacs &
## output: emacs: symbol lookup error: emacs: undefined symbol:
malloc_get_state, version GLIBC_2.2.5
```
The apt-installed emacs works.

[-- Attachment #2: Type: text/html, Size: 400 bytes --]

bug#58219: ubuntu 22.04.1 LTS

[Lars Ingebrigtsen]

Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com> writes:

> I did
>
> ```
> conda create --name emacs
> conda activate emacs
> conda install -c conda-forge emacs  # downloaded v28
> emacs &
> ## output: emacs: symbol lookup error: emacs: undefined symbol: malloc_get_state,
> version GLIBC_2.2.5
> ```
> The apt-installed emacs works.

This seems like a problem with "conda" (which I know nothing about) or
Ubuntu, so you should report this problem to them.

Closing.

bug#58219: ubuntu 22.04.1 LTS

[Gwang-Jin Kim]

[-- Attachment #1: Type: text/plain, Size: 745 bytes --]

Yes, later, it came to my mind that the conda package has to be re-flashed
probably
I have to learn building conda packages to be able to fix it myself.
Thank you a lot!

On Sat, Oct 1, 2022 at 2:18 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com> writes:
>
> > I did
> >
> > ```
> > conda create --name emacs
> > conda activate emacs
> > conda install -c conda-forge emacs  # downloaded v28
> > emacs &
> > ## output: emacs: symbol lookup error: emacs: undefined symbol:
> malloc_get_state,
> > version GLIBC_2.2.5
> > ```
> > The apt-installed emacs works.
>
> This seems like a problem with "conda" (which I know nothing about) or
> Ubuntu, so you should report this problem to them.
>
> Closing.
>

[-- Attachment #2: Type: text/html, Size: 1230 bytes --]

bug#58219: resolved the "but"

[Gwang-Jin Kim]

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

The bug was a self-created one!
I once long time ago softlinked /var/log to some home directory folder
because I ran out of memory space.

Somehow the link was persisting.

Meanwhile I enlarged the partition using gparted - so I had no space
problems any more.

My solution was to remove the softlink and replace file folder instead:

sudo rm /var/log
sudo mkdir -p /var/log

probably such kind of softlinks underlie mount errors freuquently related
to snap.

You can close this case then now, since it is resolved.
Thank you for your time!

Best,
GWang Jin

[-- Attachment #2: Type: text/html, Size: 804 bytes --]

bug#58219: resolved the "but"

[Gwang-Jin Kim]

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

Oh no - sorry - this is for emacs - and not my ubuntu bug which I reported.
Sorry - but thank you for the answer!!!
Glad to know that it is there. How to tell the package owners to change it?
...

On Tue, Oct 4, 2022 at 11:00 AM Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com>
wrote:

> The bug was a self-created one!
> I once long time ago softlinked /var/log to some home directory folder
> because I ran out of memory space.
>
> Somehow the link was persisting.
>
> Meanwhile I enlarged the partition using gparted - so I had no space
> problems any more.
>
> My solution was to remove the softlink and replace file folder instead:
>
> sudo rm /var/log
> sudo mkdir -p /var/log
>
> probably such kind of softlinks underlie mount errors freuquently related
> to snap.
>
> You can close this case then now, since it is resolved.
> Thank you for your time!
>
> Best,
> GWang Jin
>

[-- Attachment #2: Type: text/html, Size: 1397 bytes --]