Linux Mint 19 “Tara” MATE – BETA Release

Releases and other announcements.
Please don't post support questions here
Forum rules
Section reserved for the team. You can reply to announcements here but not post new topics.Please do not add support questions to threads here,use the appropriate support forum instead
rickNS
Level 3
Level 3
Posts: 155
Joined: Tue Jan 25, 2011 11:59 pm

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by rickNS » Wed Jun 20, 2018 9:18 pm

JosephM wrote:
Wed Jun 20, 2018 12:41 pm
so that said it would seem a lot better for everyone to have a place / blog for just the bugs without the extraneous natter...would it not?
It wouldn't matter where we put it. We would get the same stuff. It wouldn't change anything.
On second though I realize you are right, no matter where it is done you will get that kind of stuff. Like I said though at least as long as you guys can figure it out is all that matters. Furthermore, a lot of the "bugs" reported are knit pickers anyway. Like I said when 19 was first introduced.

Sorry for being a knit picker myself...
Mint 18 mate on 2 identical Thinkpad T420's

JosephM
Level 6
Level 6
Posts: 1045
Joined: Sun May 26, 2013 6:25 pm

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by JosephM » Thu Jun 21, 2018 12:40 am

No need to apologize for nit picking. A lot of the time when we move to a new base users will end up running into things we never did when they try the beta. Cleaning up as many of those little things as we can helps up the overall level of polish a good bit.
When I give opinions, they are my own. Not necessarily those of any other Linux Mint developer or the Linux Mint project as a whole.

User avatar
sdibaja
Level 5
Level 5
Posts: 569
Joined: Sun May 08, 2011 12:57 pm
Location: Baja California, Mexico

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by sdibaja » Thu Jun 21, 2018 8:48 am

JosephM wrote:
Thu Jun 21, 2018 12:40 am
No need to apologize for nit picking. A lot of the time when we move to a new base users will end up running into things we never did when they try the beta. Cleaning up as many of those little things as we can helps up the overall level of polish a good bit.
Maybe I am missing something Sir.
How is one expected to read the Blog? Just start at the top and read all of the comments over again to see if there are new comments? *** I am using a feed reader (Feedbro) and it kinda works for picking out new posts.
If a developer needs a tiny bit more info about a bug, how do you ask that bug reporter?
... or conversely how do I add a tidbit to my previous post after further testing?
The developers... how do we know who you are? I see lots of comments from the peanut gallery, are some of those from developers/maintainers?
... I see comments by "Linux Mint". are those Clem or is it a shared account only used by others? (the writing style suggests the latter)

those of us out here on the fringes do want to help, we do care
thanks, peter

User avatar
thx-1138
Level 6
Level 6
Posts: 1055
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by thx-1138 » Thu Jun 21, 2018 9:07 am

...this thread's evolution so far, almost makes me think that the announcements would probably benefit from being locked down...
so that each & every question, complaint, why this & why that...& why not, would be posted exclusively on the blog.

KBD47
Level 7
Level 7
Posts: 1587
Joined: Fri Jul 29, 2011 12:03 am

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by KBD47 » Thu Jun 21, 2018 9:31 pm

Recent updates to MATE beta and it is looking better. 455mb ram at boot with just terminal open. Themes are looking better as well. Using Mint Y and it looks awesome.

User avatar
Snafu
Level 2
Level 2
Posts: 64
Joined: Tue Mar 13, 2018 7:01 am
Location: Australia

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by Snafu » Fri Jun 22, 2018 12:46 pm

Code: Select all

 systemd-analyze
Startup finished in 13.684s (kernel) + 33.184s (userspace) = 46.869s
graphical.target reached after 33.172s in userspace
For a creaky old Thinkcentre with 2 gb ram I thought this wasn't bad. By comparison my Dell laptop - 4 gb ram and a dual core i5 processor takes around 1:10 to boot Kubuntu
When all else fails follow the instructions

User avatar
all41
Level 13
Level 13
Posts: 4507
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by all41 » Sat Jun 23, 2018 6:47 pm

I came across another niggle with Tara Mate.
The out of the box video driver worked fine in every respect (if it ain't broke fix it till it is)---I went into driver manager and selected the recommended nvidia 340.106 Oubuntu3 drivers and this system crashes everytime I open Synaptics Package Manager. If not instantly then as soon as I search for a package--leaving a crazy pixelated screen, locked up system, with no option other than reisub.
Definitely repeatable.
I was getting crashes other times as well, but not pinned down.
I reverted back to the Driver Manager's offering of Xorg 1:1.0.15.2 and the screen is too small and Displays do not recognize the LG monitor and use an ugly 1600x900 unchangeable resolution.
When I try to go back to the nvidia drivers I get an error box:

Code: Select all

installArchives() failed: Selecting previously unselected package nvidia-340.
(Reading database ... 
(Reading database ... 5%%
(Reading database ... 10%%
(Reading database ... 15%%
(Reading database ... 20%%
(Reading database ... 25%%
(Reading database ... 30%%
(Reading database ... 35%%
(Reading database ... 40%%
(Reading database ... 45%%
(Reading database ... 50%%
(Reading database ... 55%%
(Reading database ... 60%%
(Reading database ... 65%%
(Reading database ... 70%%
(Reading database ... 75%%
(Reading database ... 80%%
(Reading database ... 85%%
(Reading database ... 90%%
(Reading database ... 95%%
(Reading database ... 100%%
(Reading database ... 299498 files and directories currently installed.)
Preparing to unpack .../nvidia-340_340.106-0ubuntu3_amd64.deb ...
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so to /usr/lib/x86_64-linux-gnu/libGL.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGL.so to /usr/lib/i386-linux-gnu/libGL.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libEGL.so.1 to /usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libEGL.so.1 to /usr/lib/i386-linux-gnu/libEGL.so.1.distrib by nvidia-340'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libEGL.so to /usr/lib/x86_64-linux-gnu/libEGL.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libEGL.so to /usr/lib/i386-linux-gnu/libEGL.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so to /usr/lib/x86_64-linux-gnu/libGLESv2.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to /usr/lib/i386-linux-gnu/libGLESv2.so.distrib by nvidia-340'
Adding 'diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to /usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib by nvidia-340'
Adding 'diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to /usr/lib/i386-linux-gnu/libGLESv2.so.2.distrib by nvidia-340'
Unpacking nvidia-340 (340.106-0ubuntu3) ...
Processing triggers for ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
Setting up initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Setting up nvidia-340 (340.106-0ubuntu3) ...
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Adding system user `nvidia-persistenced' (UID 122) ...
Adding new group `nvidia-persistenced' (GID 129) ...
Adding new user `nvidia-persistenced' (UID 122) with group `nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-340-340.106 DKMS files...
Building for 4.15.0-23-generic
Building for architecture x86_64
Building initial module for 4.15.0-23-generic
Done.

nvidia:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-23-generic/kernel/drivers/char/drm/

nvidia_uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-23-generic/kernel/drivers/video/

depmod.....

DKMS: install completed.
Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
cp: -r not specified; omitting directory '/etc/udev/rules.d/'
cp: cannot stat '50-bluetooth-hci-auto-poweron.rules': No such file or directory
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-23-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 initramfs-tools
Setting up initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.130ubuntu3.1) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
cp: -r not specified; omitting directory '/etc/udev/rules.d/'
cp: cannot stat '50-bluetooth-hci-auto-poweron.rules': No such file or directory
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.15.0-23-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
So I am stuck with either a crashing driver, or a wrong driver--neither is acceptable.
What is different about the .iso installed driver?
My inxi is here:
viewtopic.php?f=157&t=271537
I am understanding why elephants are boring
Proud to be a supporter and monthly contributor to Mint.

User avatar
all41
Level 13
Level 13
Posts: 4507
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by all41 » Sat Jun 23, 2018 9:47 pm

Just now found that suspend recovery is also affected and not possible, have to resisub after suspend when using the (updated?) xorg drivers
Proud to be a supporter and monthly contributor to Mint.

Mattyboy
Level 6
Level 6
Posts: 1196
Joined: Thu Mar 26, 2015 2:17 pm

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by Mattyboy » Sun Jun 24, 2018 4:24 pm

all41 wrote:
Sat Jun 23, 2018 9:47 pm
Just now found that suspend recovery is also affected and not possible, have to resisub after suspend when using the (updated?) xorg drivers
Not sure if its still a problem, ie fixed, but swap was getting encrypted on some installs.. its legacy from Ubuntu 18.04... hashing it out fixed slow boot issues but killed suspend.

User avatar
all41
Level 13
Level 13
Posts: 4507
Joined: Tue Dec 31, 2013 9:12 am
Location: Computer, Car, Cage

Re: Linux Mint 19 “Tara” MATE – BETA Release

Post by all41 » Sun Jun 24, 2018 6:52 pm

@Mattyboy
Thank you for that information, and for supporting Mint 8)
I did not find an actual solution.
I reinstalled and left the default .iso's graphic driver as is--and it is now running great, looks good, and suspend works without a hitch.
It was a fairly fresh install with few customizations so not a lot of time was needed to get back to
the point previous to the driver fiasco. I had backup of the apt cache and copied those files into the
fresh install, and with all the updates present locally they did not need to download again, so the reinstall completed quickly.
This time I made a Timeshift restore file just in case, but most likely will reinstall yet again using the final release .iso.
Cheers
Proud to be a supporter and monthly contributor to Mint.

Post Reply

Return to “Releases & Announcements”