I have this issue too but not only when logged in under tigervnc on my server (supermicro amd-epyc platform).
KDE6 is definitely no improvement - I had this nice little feature already for at least 2 or 3 years also under KDE5.
My dirty workaround is to kill this process periodically via cron ...

ran into the same problem today.

moving away my binpkgs solved it.

After 13 years of daily Gentoo use, I finally got around to making a forum account just to say - How can I help?

I recently purged my system of *kit, dbus, avahi, pulseaudio, zeroconf, udev->eudev and anything else belonging to that cult.

Everything still seems to work fine, which leaves me ...

I installed x2go but the session lasts for a second then terminates automatically without any obvious reason in the logs. Any ideas?

same for me - also with a removed /etc/x2go/Xsessions file (always with the very obvious reason "Error: blabla in stage 7")

If I select Terminal instead of KDE ...

my layman -L prints now....


...
* verlihub [Git ] (git://verlihub.git.sourceforge.net/gitroot/verlihub...)
* vincent [Git ] (git://git.o.g.o/dev/vincent.git, http://git.o.g.o/g...)
* viprea-overlay [Git ] (git://github.com/viprea/viprea-overlay.git, https:/...)
* virtualization [Git ] (git ...

I ended up in adding nearly all kde apps/libs (">=kde-base/xxxx-4.11.0") in /etc/portage/package.mask

Hi,

I'm no longer able to update my portage tree (squash_dir, unionfs_fuse [everything from mv-overlay])
sys-fs/fuse-2.8.7, kernel 3.2.11-gentoo or 3.3-gentoo, net-misc/rsync-3.0.9-r1


emerge --sync produces the following error:
And it worked before (i.e. with other kernels)? Then it looks to ...

Hi,

I'm no longer able to update my portage tree (squash_dir, unionfs_fuse [everything from mv-overlay])
sys-fs/fuse-2.8.7, kernel 3.2.11-gentoo or 3.3-gentoo, net-misc/rsync-3.0.9-r1


emerge --sync produces the following error:


app-backup/backup-manager/files/
app-backup/backupninja/
app ...

Jaglover wrote:Yes, three of my boxes were running overnight and were screwed. There is no need to unmerge prelink, though, just make sure you have

Code: Select all

PRELINKING=""

in your /etc/conf.d/prelink.

I assume most of us want to keep prelink despite this little @#$%.

thanx this helped.

Hi

On my AMD64 (no multilib) I start only when I really need it my chroot32 environment (more or less identical with the description in the gentoo documentation http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 )
When I stop it I get sometimes problems (device busy...) and ...

as assumed it's the compiler which is buggy or trigger this bug (Portage 2.1.9.26 (default/linux/amd64/10.0/no-multilib, gcc-4.5.2, glibc-2.12.1-r3, 2.6.37-rc5 x86_64))

gcc-4.5.2 -> sys-boot/grub-1.97.2-r2 -> out of range pointer 0x7fe80
gcc-4.5.2 -> sys-boot/grub-1.98-r8 -> same out of range ...

I've been using grub-1.97.2-r2 (sabayon-overlay) for more than a half year now and it worked fine, survived several system/world rebuilds up to yesterday on my laptop (AMD64, /boot belongs to / and is ext4). Yesterday I did a world rebuild after switching to gcc-4.5.2 and now the system is no longer ...

I have two absolutely identical machines that have absolutely the same set of software installed (basically just system and system tools: cron, slocate, syslog, logrotate etc.). Both machines run OpenRC 0.6.2. However, after boot on one machine set of started services looks like that:


Runlevel ...

... also so schaut's auch bei mir die meiste zeit aus. aber irgendwann geht's los. das ist ja eines der probleme.
definitiv reproduzieren, kann ich's mit revdep-rebuild auf 2 gentoo 64bit maschinen (aktuellster stand, 2.6.35-gentoo-r5 kernel,
ausser iproute2-2.6.35-r1, damit geht nämlich kein ...

also ich kann's jetzt zumindest bei mir daheim an mehreren gentoo-kisten reproduzieren.

1) normaler user (normales xterm/konsole oder per ssh -Y)
2) su
3) revdep-rebuild

danach geht's rund... im sekundentakt je nach prozessorleistung ca 10 dbus-daemon mehr...

- vor allem bleiben sie auch ...

seit einigen tagen gibts auf meinem laptop immer wieder probleme mit dem dbus-daemon.
wie von geisterhand starten sich die burschen x-fach und müllen mir den rechner zu bis nix mehr geht (zigtausende von dbus-daemons)

hier ein auszug aus der processliste...
bisheriger vermutungs/erkenntnisstand ...

works fine.

aakef wrote:Thanks for the logs, I think you used Martins previously compiled version, right?

exactly !

Is it possible to upload/send you the output of ddd/gdb and the concerning console output?

I have created at least one which ends in an empty /usr/portage directory.

EDIT:
Since I didn't find an upload page here or on radek's website I uploaded the tar-file to uploaded.to

http://ul.to/7j52bl ...

Hmm, can't reproduce it :(

I think I need to update libfuse and to check what then happens.

strange.
- with unionfs-fuse versions >0.23 it is so reproducable that I'm not able update the portage tree - every rync fails.
- I tried also the next older version in the portage tree libfuse 2.7.4 ...

Are you sure 0.23 vs. 0.24/0.25 are linked against the very same libfuse?
fuse is not slotted in gentoo, so the answer will almost surely be "yes". Moreover, libfuse has not been upgraded for a while in gentoo: The latest stable (and simultaneously latest unstable) version of fuse in the portage ...

Are you sure 0.23 vs. 0.24/0.25 are linked against the very same libfuse? I assume the kernel is definitely the same? Are you able to create a test case for me? So I already know the unionfs-fuse command and now I know that ?it is not only the umount issue. But I still do not have the slightest ...

If umount fails, squash_dir-10.6 will now sleep for 1s and retry (and repeat this procedure). Moreover, it attempts now to check whether the directory is already umounted and skip the umount if this is the case. I guess, in most cases this is the desired behavior although perhaps some strange error ...

Are you sure its 0.24 and not 0.25alpha? 0.24 is mostly a bugfix release to 0.23. But 0.25 simplifies path building (unionfs internal) and handles MAX_PATH_LEN better. But this change might have introduced bugs.
However, I'm a Debian user and only found that thread here, as I had been curious what ...

Upstream is just reading here ;) and would like to see a detailed problem discription.

ok the unionfs-fuse issue: (happens with mv's overlay version and the new 0.24 version, so I switched back to 0.23)
a simple eix-sync/emerge -sync which executes rsync ends with an empty /usr/portage. According ...