Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubuntu Desktop 24.04 hangs forever after waking up from sleep #1933

Open
GinoMalatesta opened this issue Feb 1, 2025 · 5 comments
Open

Ubuntu Desktop 24.04 hangs forever after waking up from sleep #1933

GinoMalatesta opened this issue Feb 1, 2025 · 5 comments

Comments

@GinoMalatesta
Copy link

GinoMalatesta commented Feb 1, 2025

I discovered the following:

If I have a share mounted and put my notebook to sleep, it'll hang forever after waking up, if the share isn't available anymore.
Keyboard hangs as well, can't switch to another tty or kill gnome, needs a full hard shutdown then.
It comes back to life, if I make the share available again.

Can't say if it's caused by Netatalk, Gnome or Nautilus though ...

@rdmark
Copy link
Member

rdmark commented Feb 2, 2025

Can you please provide a bit more context here. Where is netatalk running? What is the client that is mounting the netatalk volume? What version of netatalk, and how is it configured?

It's helpful if you break down the exact steps to reproduce in a bulleted format, to avoid ambiguity.

@GinoMalatesta
Copy link
Author

  • Client and server both Ubuntu 24.04 Desktop - Gnome
  • netatalk/noble 3.1.18~ds-1build4 amd64 running as systemd service
  • configured in /etc/netatalk/afp.conf (2 shares/paths)

To reproduce:

  • Mount a share in Nautilus
  • Suspend notebook
  • Suspend/shutdown server
  • Wake up notebook and authenticate
  • Hangs until the server is brought up again.

Could it be the
<limit name="auth_timeout">240000</limit>
in /etc/netatalk/dbus-session.conf ? I never waited an hour ...

@rdmark
Copy link
Member

rdmark commented Feb 2, 2025

netatalk/noble 3.1.18~ds-1build4 amd64 running as systemd service

Netatalk 3.1.18 is long outdated and won't get any bugfixes. It would be great if you could upgrade to the latest v4.1 and test with that.

Client and server both Ubuntu 24.04 Desktop - Gnome

Interesting! But if the host and client are the same machine, why don't you access the file system directly? You can even use the ad toolsuite to move files to and from while keeping the CNID database up to date.

BTW, thanks to this discussion, I learned (or was reminded that) Nautilus and Gvfs support AFP natively. My immediate thought is that there's a bug in Nautilus and/or Gvfs. Looking at the Gvfs repo, the AFP compatibility code hasn't been updated for many years.

@GinoMalatesta
Copy link
Author

Netatalk 3.1.18 is long outdated and won't get any bugfixes. It would be great if you could upgrade to the latest v4.1 and test with that.

It's the actual Version in the Ubuntu noble repo. I didn't find a package for the actual version. Don't want to make it ...

It's running on two machines, a desktop and a notebook, home lab.
I also run qemu VMs with macOS and chose to use afp for sharing with the host, for convenience, haven't configured smb ...

Now that i know it, it's not a big issue, but took me a while to figure why my notebook randomly freezes. Cheers.

@rdmark
Copy link
Member

rdmark commented Feb 2, 2025

You would probably have to build netatalk 4.1 from source. Which is not that hard, frankly. But with the caveat that you should take a backup of your shared volumes before attempting a manual upgrade.

The INSTALL readme is a good starting point. https://github.com/Netatalk/netatalk/blob/main/INSTALL.md

If you get around to filing this with the GNOME team, I'm curious to hear what they say. I definitely am motivated to do what I can to improve the AFP ecosystem.

As a side note, I'm maintaining a fork of afpfs-ng, an alternative AFP client. It's kind of unstable though.

https://github.com/rdmark/afpfs-ng

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants