New LMDE isos (Pos-UP4) in testing

[zerozero]

ok, installing as i type the 64bit mate/cin rc.
first impressions:
- the default DE is mate;
- and it looks like the good'old gnome2
- one issue i just found out in the installer (never realised if it was there before or not): it stalls if you try to install in a partition that you have mounted before (so basically it fails to unmount it > as soon as i did it manually it went smooth)

[zerozero]

at least the 64bit mate/cinnamon the one we are testing have an issue, so please use them only for testing, wait for the final isos if you want to install/reinstall the system.

[Monsta]

I hope a general "UP4/new ISOs problems" thread will be created when these RC's are officially out. I'm fine with all these sudden threads with the same questions about new breakages, but we really need a place to put a little summary and maybe a little FAQ

Or does this very thread suit as such a place?

[zerozero]

Or does this very thread suit as such a place?

i hope people report the new RC issues and wonders here (makes the forum lot easier to follow for everybody)

[kmb42vt]

at least the 64bit mate/cinnamon the one we are testing have an issue, so please use them only for testing, wait for the final isos if you want to install/reinstall the system.

Yup, and the ISOs aren't even officially released yet which is why I installed thing. Catch the "pre-official-release" bugs early and all that. Found a couple other issues as well.

1. No "Open as administrator" for Nautilus (Gnome3/Cinnamon--known problem).

2. Mint-X/Mint-X-Metal theme fonts (for menus mostly) for MATE still fixed at 9px so it doesn't follow system font settings (old problem). Comment out line 53 in "/usr/share/themes/Mint-X/gtk-2.0/gtkrc" and "/usr/share/themes/Mint-X-Metal/gtk-2.0" to fix this problem. Line 53 looks like this:

Code: Select all

#font_name                = "9"

I'm sure I saw a few more last night but it was late and my health isn't so grand lately. I'll report back as soon as I get the chance to go through things more thoroughly.

[Monsta]

Okay, it's official.

[Graes]

tried the 64bit MATE version yesterday.

the only problem i've found is that VLC won't start!

[äxl]

And they upgraded to ... semi-rolling ... ?!?

Hm, I came for rolling, I'm staying for mate ...

[zerozero]

And they upgraded to ... semi-rolling ... ?!?

Hm, I came for rolling, I'm staying for mate ...

testing (debian proper) was/is always a semi-rolling release, lmde with the UP's follows the same pattern but with a buffer for stability.

[äxl]

Pseude, opt, truly, fully ...
All I know that it wasn't called semi here http://blog.linuxmint.com/?p=1818

[zerozero]

ahh, and lmde repos are not compatible with squeeze not anymore

[jjaythomas]

Fresh installed from new ISO RC (yay got before official post and server avalanche)
Installed without problem (for me )
and found no major problems (of coarse I don't use much besides browser, E-Mail, DVD playing, and stream-tuner

J.Jay

[water spirit]

edit

[Monsta]

i hope people report the new RC issues and wonders here (makes the forum lot easier to follow for everybody)

Here, in "open discussion"? Well... okay
For a start, here are the warnings right from the live cd boot:

Code: Select all

creating compatibility symlink from /etc/mtab to /proc/mounts. ... (warning)

Code: Select all

mount: according to mtab, tmpfs is already mounted on /run/lock

mount: according to mtab, tmpfs is already mounted on /run/shm

Mount point '/filesystem.squashfs' does not exist. Skipping mount. ... (warning)

The first two probably have something to do with upstream changes in /etc/default/rcS, but I can't figure out what to edit to fix it AND not to break something else at the same time

Code: Select all

Fast boot enabled, so skipping file system check. ... (warning)

Code: Select all

startpar: service(s) returned failure: udev console-setup live-boot ... failed!

Actually, console-setup apparently succeeded - the font has changed halfway through the process (as usual)... well, maybe it failed in doing something else

Code: Select all

No such key `show-actions' in schema `org.gnome.power-manager' as specified in override file `/tmp/gdm-gD435b/xx_upstream.gschema.override'; ignoring override for this key.
No such key `icon-policy' in schema `org.gnome.power-manager' as specified in override file `/tmp/gdm-gD435b/yy_debian.gschema.override'; ignoring override for this key.

Most of them are also present when you update your common UP3 installation to UP4.

[äxl]

I think it would be a good idea to also arrange an "UP testing" with all the dist-upgrade breakages here ...

With a SEMI-rolling release maybe even a better idea since I hope most people don't re/install.

On Ubuntu I only made one dist-upgrade and I can't remember having any trouble.

[Monsta]

Okay... now there are also some warnings on poweroff:

Code: Select all

umount: /var/run: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
umount: /live: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

Code: Select all

loop: can't delete device /dev/loop1: No such device or address

Code: Select all

/etc/init.d/live-boot: 203: [: =: unexpected operator

Now let's boot our shiny new system and see if the warnings are still here.
compatibility symlink warning: check (but gone on the next boot - obviously the symlink is created only once)
two tmpfs warnings: check
third mount warning: gone (apparently something livecd-specific)
fast boot warning: gone (fsck is turned on as it should)
startpar failure notice: gone (okay...)
org.gnome.power-manager schema errors: check

And let's also reboot it.
two umount errors: check
loop error: gone (apparently something livecd-specific)
live-boot error: gone (same here, the name tells it)


And now for a new error. Console localization horribly failed and made me remember the good old days when I've struggled with the localization in Red Hat 7.2.
It starts with these schema error messages mentioned above. They are now localized (in Russian in my case) - but half of the letters is replaced with some weird symbols. Then it's all the same with the usual programs, for example, apt-get. Or maybe it's just my VirtualBox 4.1.0 in which I'm testing this LMDE edition right now...


Fortunately, this nuisance is removed by the most vulgar and brutal solution (run this as root of course):

Code: Select all

apt-get purge console-setup && apt-get install console-setup

and the things are fine on the next boot.

[cpatrick08]

when I check update manager and update pack info it says
Current update pack available 4
Latest update pack used by this system is 2
i installed from the 64 bit cinnamon/mate rc iso
no updates are available i am using the default incoming not latest

[äxl]

Code: Select all

apt-get purge console-setup && apt-get install console-setup

You can manage that in one step I suppose

Code: Select all

sudo apt-get -o dpkg::options::="--force-confnew" -o dpkg::options::="--force-confmiss" --reinstall install console-setup

[zerozero]

when I check update manager and update pack info it says
Current update pack available 4
Latest update pack used by this system is 2
i installed from the 64 bit cinnamon/mate rc iso
no updates are available i am using the default incoming not latest

i remember having the same "issue" with MU right after installing; no matter what i did it refused to show UP4 as installed (i hit refresh several times, opened it and closed, opened the update pack info button, nothing ) then i pressed install updates even knowing that there was none) and voila it accepted that the last UP used in the system was 4.
yeahh, i know, this sounds terribly scientific

[kmb42vt]

when I check update manager and update pack info it says
Current update pack available 4
Latest update pack used by this system is 2
i installed from the 64 bit cinnamon/mate rc iso
no updates are available i am using the default incoming not latest

i remember having the same "issue" with MU right after installing; no matter what i did it refused to show UP4 as installed (i hit refresh several times, opened it and closed, opened the update pack info button, nothing ) then i pressed install updates even knowing that there was none) and voila it accepted that the last UP used in the system was 4.
yeahh, i know, this sounds terribly scientific

Quite a lot of problems with this RC?

Yup, I see this as well and I first changed my sources to point to "latest" which is, I believe, what they should have been pointed to? Either way, I did all the above (as per your most scientific post) with the exception of installing updates that weren't there--no go. Still says my system has UP2 installed which is very funny since this is a clean install of LMDE UP4. I'll have to try that phantom update-update. It may take a bit as the update server still chokes more times than not. That's the problem with being popular?

Update: All hail the great zerozero for his very scientific fix of the Update Pack 2 conundrum! Worked like a charm. And of course, the update server data downloaded just fine this time around. Must have heard me bad mouthing it.