← prev | next →
CrunkLord420 2022-09-15 03:28:49
Glats 2022-09-15 02:22:04
I’m getting a super weird issue. I’m using vnc to connect to the macosx from linux. after awhile the osx lock up and you need to relogin. after a couple of hours the whole network gets super slow…
my first clue could be multiples vnc clients remain opens and that could be the reason the slowness
probably a memleak
yabadaba doo 2022-09-15 07:51:34
why is memmove fine with s[] but alergic to *s?
CrunkLord420 2022-09-15 08:00:52
yabadaba doo 2022-09-15 07:51:34
why is memmove fine with s[] but alergic to *s?
are you writing C++
CrunkLord420 2022-09-15 08:00:58
or C
yabadaba doo 2022-09-15 08:01:04
C99
CrunkLord420 2022-09-15 08:01:34
weird lol, works fine for me
CrunkLord420 2022-09-15 08:01:38
maybe just cast it
yabadaba doo 2022-09-15 08:05:05
:/
qontinuum 2022-09-15 08:08:39
yabadaba doo 2022-09-15 07:51:34
why is memmove fine with s[] but alergic to *s?
What is the error with the pointer version?
qontinuum 2022-09-15 08:16:22
wardenunit 2022-09-15 00:55:30
This is what /usr/lib64 looked like before I backed it up as lib64bak:
ls -lA /usr/lib64bak
total 8.0M
drwxr-xr-x 3 root root 4.0K Sep 15 00:23 cmake
drwxr-xr-x 2 root root 4.0K Sep 15 00:23 pkgconfig
lrwxrwxrwx 1 root root 14 Sep 14 01:57 libassimp.so -> libassimp.so.5
lrwxrwxrwx 1 root root 18 Sep 14 01:57 libassimp.so.5 -> libassimp.so.5.2.4
-rwxr-xr-x 1 root root 8.0M Sep 14 01:57 libassimp.so.5.2.4
The file is owned by the filesystem package that hasn’t moved in months so I really don’t get what happened
AndrewBenn 2022-09-15 08:23:01
I’m also suspect, as /usr/lib64 should have at least hundreds, if not thousands of files. Depending on number of packages.
qontinuum 2022-09-15 08:23:52
AndrewBenn 2022-09-15 08:23:01
I’m also suspect, as /usr/lib64 should have at least hundreds, if not thousands of files. Depending on number of packages.
It is a link to /usr/lib but yeah
CrunkLord420 2022-09-15 08:24:10
wardenunit 2022-09-15 00:52:43
1) for some reason lib64 transformed from “being a link to lib” to the thing I’ll send just below. But changing it back didn’t fix anything (maybe I forgot to mkinitcpio? idk if that was necessary)
2) Reinstalled several packages mentioned in that thread. That worked, but according to (1), I hadn’t got any luck deducing the sole fix|reason of the issue
lol just copy lib64 into usr lib64 and relink it
CrunkLord420 2022-09-15 08:24:23
that’s what I did
qontinuum 2022-09-15 08:25:31
Another weird thing is that the other guy reporting the issue isn’t describing the same naming
lanciagreggori 2022-09-15 08:41:53
Wolandarkside 2022-09-14 23:29:49
hmm, like with dd?
If you have an SSD, you can do a full flash erase
wardenunit 2022-09-15 08:57:03
CrunkLord420 2022-09-15 08:24:10
lol just copy lib64 into usr lib64 and relink it
Are you blind or what? I’ve already mentioned that this did not work
CrunkLord420 2022-09-15 09:04:41
wardenunit 2022-09-15 08:57:03
Are you blind or what? I’ve already mentioned that this did not work
sounds like a (You) problem
qontinuum 2022-09-15 09:05:00
It isn’t
CrunkLord420 2022-09-15 09:05:22
worx on my masheen
qontinuum 2022-09-15 09:05:34
CrunkLord420 2022-09-15 09:05:22
worx on my masheen
But no one cares about you
qontinuum 2022-09-15 09:08:17
@wardenunit have you got a chance to get the list of the latest packages you upgraded when it broke?
wardenunit 2022-09-15 09:11:43
qontinuum 2022-09-15 09:08:17
@wardenunit have you got a chance to get the list of the latest packages you upgraded when it broke?
I know the files that are related to those packages
wardenunit 2022-09-15 09:11:57
I sent the names up there
wardenunit 2022-09-15 09:12:06
This is what /usr/lib64 looked like before I backed it up as lib64bak:
ls -lA /usr/lib64bak
total 8.0M
drwxr-xr-x 3 root root 4.0K Sep 15 00:23 cmake
drwxr-xr-x 2 root root 4.0K Sep 15 00:23 pkgconfig
lrwxrwxrwx 1 root root 14 Sep 14 01:57 libassimp.so -> libassimp.so.5
lrwxrwxrwx 1 root root 18 Sep 14 01:57 libassimp.so.5 -> libassimp.so.5.2.4
-rwxr-xr-x 1 root root 8.0M Sep 14 01:57 libassimp.so.5.2.4
qontinuum 2022-09-15 09:14:15
wardenunit 2022-09-15 09:12:06
This is what /usr/lib64 looked like before I backed it up as lib64bak:
ls -lA /usr/lib64bak
total 8.0M
drwxr-xr-x 3 root root 4.0K Sep 15 00:23 cmake
drwxr-xr-x 2 root root 4.0K Sep 15 00:23 pkgconfig
lrwxrwxrwx 1 root root 14 Sep 14 01:57 libassimp.so -> libassimp.so.5
lrwxrwxrwx 1 root root 18 Sep 14 01:57 libassimp.so.5 -> libassimp.so.5.2.4
-rwxr-xr-x 1 root root 8.0M Sep 14 01:57 libassimp.so.5.2.4
Yeah but I think this is just a symptom, you should have got a file conflict
wardenunit 2022-09-15 09:14:25
qontinuum 2022-09-15 09:14:15
Yeah but I think this is just a symptom, you should have got a file conflict
Yes I had
qontinuum 2022-09-15 09:14:35
And you overwrote?
wardenunit 2022-09-15 09:14:38
And it were them
wardenunit 2022-09-15 09:14:39
qontinuum 2022-09-15 09:14:35
And you overwrote?
Yes
qontinuum 2022-09-15 09:14:53
CrunkLord420 2022-09-15 09:04:41
sounds like a (You) problem
Okay you were right
qontinuum 2022-09-15 09:14:57
wardenunit 2022-09-15 09:14:39
Yes
Why the fuck?
qontinuum 2022-09-15 09:15:25
You shouldn’t overwrite unless asked by a dev
qontinuum 2022-09-15 09:16:18
Also it seems it is fixed
wardenunit 2022-09-15 09:16:54
qontinuum 2022-09-15 09:14:57
Why the fuck?
Because I’ve got broken python directories and it is the way I handle it
← prev | next →