19.10 from beta to release

The Ubuntu Budgie team are pleased to announce the beta release of our 19.10 distro.

Please help out testing and lets make this release as polished as we can.

cheers

2 Likes

Just want to say I’m really pleased with initial tests, 19.10 will be an awesome release!

3 Likes

Clean install of 19.10. When trying to install Screen Shot applet I get the error "Failed installation of screenshot applet’ notification.

run a standard update and it will now install successfully.

Strange situation. Clean install 19.10 on Thinkpad 450S. Updated to current.

  1. Get an Incomplete Language Support popup. Run the install app and 5 minutes later get the same popup.

  2. Install gftp, nothing else. Now, if I launch gftp from command line or from budgie menu it takes about 20 seconds for the app gui to come up. However, if I launch from command line with sudo gftp it comes up right away. This is strange.

Obviously never run a gui app with sudo…

At worst run with pkexec

What is its .desktop file exec= value in /usr/share/applications ?

If you run that command in a terminal does it take 20secs?

The language support sounds like a bug where it isnt completing. Not sure what package you should file it under on launchpad

Obviously never run a gui app with sudo…

Understood, just did this for a test.

If you run that command in a terminal does it take 20 secs?

Yes

I know that specific apps are not a UB issue. Since a clean install has problems I have reloaded 19.04 and will wait until 19.10 is released.

hmm … https://launchpad.net/ubuntu/+source/gftp

If looks like gftp hasn’t changed since the 12.04 days - maybe further back. There has been just “lets get it to compile” attempts since then. The last one has failed to build and is stuck in eoan proposed.

I suspect if it continues to fail to build during the 20.04 dev cycle it would be removed from the archive.

further to that I’ve looked at the build logs - lots and lots of deprecated code issues. Probably the issues you are seeing are due to those - the code hasnt kept pace with modern libraries and are now causing real usability issues.

Yea, I looked at that. So, three of my applications are at risk in 19.10, gftp, jpilot, and phpmyadmin. Its funny though, when I first did an upgrade on this machine (19.04 to 19.10) all three apps worked fine. It was only when I did the clean install that they fell over :frowning:

thats a real shame - the fact they worked early is due to the fact the libraries early on were just the 19.04 code-base. I’m aware that phpmyadmin now exists in PPA form under “new management” - so hopefully will make it into 20.04 assuming Debian buys into their efforts.

gftp just looks like a dead project. Not sure of what specifically you look for in a ftp client but I assume you’ve considered well maintained projects like filezilla?

EDIT: yeah - jpilot was removed from the archive - again dead project and no longer works with the current code-base

gftp just looks like a dead project. Not sure of what specifically you look for in a ftp client but I assume you’ve considered well maintained projects like filezilla?

Your going to love this: I installed filezilla on several machines including a 19.10 virtual. Guess what, it takes 35 seconds for the GUI to come up on 19.10 after launching from Budgie menu.

interesting - can also reproduce the slow start of filezilla from a terminal.

Wonder if this is some-sort of apparmor issue or systemd issue.

interesting. dunno really.

also an interesting observation. I purged filezilla and then installed the snap version of filezilla.

This started (second start) almost instantaneously

Both gftp and filezilla halt for the same timeout:

strace -t gftp

09:07:51 write(12, “\1\0\0\0\0\0\0\0”, 8) = 8
09:07:51 write(13, “\1\0\0\0\0\0\0\0”, 8) = 8
09:07:51 poll([{fd=12, events=POLLIN}], 1, 25000) = 1 ([{fd=12, revents=POLLIN}])
09:07:51 read(12, “\1\0\0\0\0\0\0\0”, 16) = 8
09:07:51 poll([{fd=12, events=POLLIN}], 1, 25000) = 0 (Timeout)
09:08:16 write(12, “\1\0\0\0\0\0\0\0”, 8) = 8
09:08:16 futex(0x55cff178e3d0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:08:16 close(12) = 0
09:08:16 write(13, “\1\0\0\0\0\0\0\0”, 8) = 8
09:08:16 futex(0x7ff9b1658f58, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:08:16 futex(0x7ff9b1658f58, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:08:16 statfs("/home/rob", {f_type=EXT2_SUPER_MAGIC, f_bsize=4096, f_blocks=2563397, f_bfree=1131896, f_bavail=996754, f_files=655360, f_ffree=443159, f_fsid={val=[1484858622, 1130548194]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_RELATIME}) = 0
09:08:16 futex(0x7ff9b1658f58, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:08:16 futex(0x7ff9b1658f58, FUTEX_WAKE_PRIVATE, 2147483647) = 0
09:08:16 inotify_init1(IN_CLOEXEC) = 12
09:08:16 fcntl(12, F_GETFL) = 0 (flags O_RDONLY)

doesnt really mean much to me unfortunately. I’ve tried booting with apparmor=0 for the kernel. This had the same issue - so it isnt an apparmor issue. Also installed using btfrs rather than ext4 but had the same issue. So it isnt a linux ext4 file-system issue.

Spun up a Ubuntu Eoan image in Virtualbox and the same problem existed. Installed appmenu-gtk2-module via apt. Now both gftp and filezilla launch right away. Did the same with UB Eoan and the problem still exists.

Today’s apt update seems to have fixed this problem.

1 Like

I have been taking this install.reinstall.re-reinstall cycle this last 30 days to try out other OS then compare/reinstall Ubuntu Budgie. I keep trying elementary OS and it continues to tempt/frustrate me to no end. BUT (I know you all have already figured it out)

— I keep coming back :slight_smile: I can’t quit you I installed the Oct 7th build, works awesomely. No trouble for Firefox/nemo files/wifi driver, although the driver does seem to be present only after the update. I install/update with an ethernet connection everytime, then have to go back in and force the additional drivers to install the wifi driver.

ooops! something’s wrong. I installed the oct 09 build, updated everything (no new programs other than Chrome added form the browser ballot) and I get a white screen with a sad computer face, telling me something has gone wrong and to log back in. Attempted log ins reproduce the same image