Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[SOLVED]An update seems to have messed a Mepis instalationup

For help or questions about 64-bit version of MEPIS, this is the forum to use.
Message
Author
User avatar
radissthor
Forum Regular
Forum Regular
Posts: 339
Joined: Mon Sep 13, 2010 11:18 am

[SOLVED]An update seems to have messed a Mepis instalationup

#1 Post by radissthor » Thu Mar 20, 2014 9:32 am

Hi everyone,

I am writing on behalf on a less experienced Mepis user, who went on and installed some updates from a Mepis 12 system. She told me that at some point she got a blue screen asking whether she wanted the computer to be restarted right away, or later. Judging from this account, it seems like the xserver or something like that was being updated.

Well, the problem started after the update. First, the system booted to the terminal, not starting KDE. After login in through the black screen, and prompting the startx command, KDE starts, but there are several things that are wrong.

1. When the Shut Down button is pressed, amazingly, only the Logout option is displayed. And when going to Start Menu > Leave, the only options are Sleep and Hibernate, so no restart and no shut down.

2. Internet is not working. Network manager used to be configured to automatically connect to a wireless netowork. Now it doesn't connect, and when I entered the password manually, it have me the message:
Error adding connection: No session found for uid 1000 (Error stating file var/run/ConsoleKit/database: No such file or directory)

3. External hardrives and pendrives cannot be accessed anymore. When plugged in, I get the pop-out saying a device has been recognized, and offering a series of available courses of action, but when clicked, it says the device cannot be mounted.

So... it seems something went terribly wrong with that update. Now sadly the user wasn't really reading, and just clicked yes when prompted by synaptic, so I cannot say what update it was. Still, any idea or suggestions to start fixing this computer are greatly appreciated.
Last edited by radissthor on Thu Mar 20, 2014 2:04 pm, edited 1 time in total.
Image

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 5896
Joined: Wed Jul 12, 2006 2:10 am

Re: An update seems to have messed a Mepis instalation up

#2 Post by Eadwine Rose » Thu Mar 20, 2014 9:37 am

You should be able to see in the history of synaptic which update went through last, maybe see what that gives?
MX-17.1_x64 Horizon 14-3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP F2280

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9290
Joined: Wed Jul 12, 2006 2:26 pm

Re: An update seems to have messed a Mepis instalation up

#3 Post by kmathern » Thu Mar 20, 2014 9:54 am

This a repost of a post that Stevo sent to the MX development team, I'm posting it here so everybody can read it.
Stevo wrote: Re: Watch out for this update in wheezy-backports--hold off!

Apparently the udev update breaks the existing (and only) version of policykit-1 in Wheezy for MX and M12:

# aptitude dist-upgrade
The following NEW packages will be installed:
gir1.2-gudev-1.0{a} libudev1{a}
The following packages will be upgraded:
libgudev-1.0-0 libgudev-1.0-dev libudev-dev udev{b}
4 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,225 kB of archives. After unpacking 4,153 kB will be used.
The following packages have unmet dependencies:
udev : Breaks: consolekit (< 0.4.6-1) but 0.4.5-3.1 is installed.
open: 22; closed: 380; defer: 17; conflict: 38 .The following actions will resolve these dependencies:

Remove the following packages:
1) checkaptgpg
2) consolekit
3) ddrescue-gui
4) kdm
6) lightdm
19) policykit-1
20) polkit-kde-1



Accept this solution? [Y/n/q/?]
@radissthor, I'm pretty sure this is the cause of your problem.

User avatar
radissthor
Forum Regular
Forum Regular
Posts: 339
Joined: Mon Sep 13, 2010 11:18 am

Re: An update seems to have messed a Mepis instalation up

#4 Post by radissthor » Thu Mar 20, 2014 10:29 am

@Eadwine Rose : thx, I looked at the history, but the last log is from March 15, so apparently the update that caused the problem (which was done today, March 20th) was not recorded.

@Kmathern : That seems plausible. I don't know those packages and what the causes would be if they break down. Is there any clue on how to fix the problems caused by that update?

Thx
Image

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9290
Joined: Wed Jul 12, 2006 2:26 pm

Re: An update seems to have messed a Mepis instalation up

#5 Post by kmathern » Thu Mar 20, 2014 10:35 am

Could you try this command (and post the results)

Code: Select all

zgrep -EH ' install | upgrade | remove | purge ' /var/log/dpkg* | cut -f 2- -d : | sort -r | sed 's/remove/remove / ; s/purge/purge  /'| grep 2014-03-20
It greps today's package management activity from the /var/log/dpkg.log

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 5896
Joined: Wed Jul 12, 2006 2:10 am

Re: An update seems to have messed a Mepis instalation up

#6 Post by Eadwine Rose » Thu Mar 20, 2014 10:51 am

What do we do now Kmathern? Wait till it gets fixed?


I saw them appear today, they were not there this morning for me.
MX-17.1_x64 Horizon 14-3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP F2280

User avatar
Jerry3904
Forum Veteran
Forum Veteran
Posts: 21921
Joined: Wed Jul 19, 2006 6:13 am

Re: An update seems to have messed a Mepis instalation up

#7 Post by Jerry3904 » Thu Mar 20, 2014 11:01 am

A fix is in the works, just wait and watch the Site Announcements on the Forum home page (where I posted a big red warning).
Production: 4.15.0-1-amd64, MX-17.1, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 8 GB, Kingston SSD 120 GB and WesternDigital 1TB
Testing: AAO 722: 4.15.0-1-386. MX-17.1, AMD C-60 APU, 4 GB

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9290
Joined: Wed Jul 12, 2006 2:26 pm

Re: An update seems to have messed a Mepis instalation up

#8 Post by kmathern » Thu Mar 20, 2014 11:03 am

Eadwine Rose wrote:What do we do now Kmathern? Wait till it gets fixed?


I saw them appear today, they were not there this morning for me.
If you haven't upgraded udev yet (or canceled it because you saw what it was going to do), I would just wait.

From my PMs it looks like Tim & Stevo are in the process of putting a backported consolekit into the CR that should fix the problem.


If you did let it do the udev upgrade you'll need to install the backported consolekit, and you'll also need to reinstall packages that were removed during the dist-upgrade, getting them from either the Synaptic history or the command I posted.

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4264
Joined: Wed Jul 12, 2006 4:05 pm

Re: An update seems to have messed a Mepis instalation up

#9 Post by timkb4cq » Thu Mar 20, 2014 11:26 am

The backported consolekit packge is now in the main MEPIS 12 Community Repository. When wheezy-backports updated udev they should have updated consolekit as well, but they didn't and that caused the breakage.

The problem is that a number of other packages get removed. The critical ones in MEPIS12 are kdm and policykit1, but packages dependent on policykit1 such as synaptic, hplip, network-manager & checkaptgpg are also removed. I don't have a full list right now...
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
richb
Administrator
Posts: 16915
Joined: Wed Jul 12, 2006 2:17 pm

Re: An update seems to have messed a Mepis instalation up

#10 Post by richb » Thu Mar 20, 2014 11:29 am

Adrian's Question, "should backports be enabled by default". We changed priority of backports to be equal to other repos, it was 100, now 500, to avoid issues that were arising when installing packages causing broken packages. Samba was one of them. As that is likely to occur more often than backports foul ups due to their upgrades, I think, it seems we should leave things as is.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

Post Reply

Return to “64-bit Newbies”