Upgrade Warnings: LMDE tracking TESTING [10-11-14]

[GeneBenson]

Hi Monsta,

I don't have the logs anymore. I hadn't made the systemd logs permanent yet. But what I saw in the log (journalctl -b) when the problem occurred looked something like this:

Code: Select all

Found ordering cycle on basic.target/start
Walked on cycle path to sockets.target/start
Walked on cycle path to dbus.socket/start
Walked on cycle path to sysinit.target/start
Walked on cycle path to mintsystem.target/start
Breaking ordering cycle by deleting job dbus.socket/start

When I would try to start something from the Menu, like Synaptic, it wouldn't start, and I found messages like this in the log:

Code: Select all

Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory.

I checked and there was no "/var/run/dbus" directory.
From all this I concluded that mintsystem was getting in the way of dbus starting properly. I must admit this was more of a guess then real forensic work on my part, but sometimes I do get lucky. I suppose that at some point, before/with UP9(?), Mint devs will need to provide systemd Service Files for mintsystem to avoide this sort of thing.

Hope this helps. Otherwise, let me know.

[GeneBenson]

Today's update included an update to upower 0.99. For anyone running XFCE this breaks Suspend and Hibernate, which no longer appear as options when you choose to log out. There is a bug report here.

[grizzler]

If I understand this correctly, this is fixed in version 1.2.0-5 of xfce4-power-manager, which should migrate to testing in a couple of days.

[GeneC]

Today's update included an update to upower 0.99. For anyone running XFCE this breaks Suspend and Hibernate, which no longer appear as options when you choose to log out. There is a bug report here.

Confirm that this breaks suspend and hibernate.

--------------------

BUT,

If I understand this correctly, this is fixed in version 1.2.0-5 of xfce4-power-manager, which should migrate to testing in a couple of days.

Upgrade to xfce4-power-manager 1.2.0-5 from SID breaks the desktop.
Appears other packages are needed for a proper fix. Best to wait..

[woodsman]

I created a separate LMDE Mate partition so I could track Debian Testing.

I duplicated an existing fully updated LMDE Mate partition. After the usual nominal edits (fstab, hostname, etc.), the duplicated partition booted fine.

Then I followed the instructions provided here:

* Update sources.list.d.
* Delete the files in preferences.d.
* Run apt-get update.

So far so good.

Running apt-get dist-upgrade failed. There is a conflict with the Debian Mate packages and the Mint Mate packages. The failure leaves more than 700 packages not updated. I don't know how to resolve and get past the conflict.

Help appreciated.

[kurotsugi]

Code: Select all

inxi -r
sudo apt-get update
sudo apt-get -s dist-upgrade
apt-cache policy

[woodsman]

inxi -r:

Code: Select all

Repos:     Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
           deb http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
           deb http://www.deb-multimedia.org testing main non-free

apt-get -s dist-upgrade:

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 atril : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed
 caja : Depends: caja-common (= 1.6.2-3+lmde) but 1.8.1-2 is installed
 caja-gksu : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed
 caja-open-terminal : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed
 caja-share : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed
 engrampa : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed
 mate-user-share : Depends: libcaja-extension1 (>= 1.6.3) but it is not installed

[kurotsugi]

Code: Select all

apt-cache policy caja-common
caja-common:
  Installed: (none)
  Candidate: 1.8.1-2
  Version table:
     1.8.1-2 0
        500 http://ftp.nl.debian.org/debian/ testing/main amd64 Packages
         50 http://ftp.nl.debian.org/debian/ unstable/main amd64 Packages

libcaja-extension1:
  Installed: (none)
  Candidate: 1.8.1-2
  Version table:
     1.8.1-2 0
        500 http://ftp.nl.debian.org/debian/ testing/main amd64 Packages
         50 http://ftp.nl.debian.org/debian/ unstable/main amd64 Packages

something is suspicious in your system :3
the first possibility, you have another pref file and it made LMDE has higher priority. we will need the full result of 'apt-cache policy' to check it
the second possibility, something is broken between LMDE and testing.

I'm on testing and mate is fully installable

Code: Select all

aptitude -s install mate-desktop-environment
The following NEW packages will be installed:
  caja{a} caja-common{a} gvfs-bin{a} libcaja-extension1{a} 
  libcanberra-gtk0{a} libelfg0{a} libgail18{a} libglib2.0-bin{a} 
  libmarco-private0{a} libmate-desktop-2-17{a} libmate-menu2{a} 
  libmate-panel-applet-4-1{a} libmate-slab0{a} libmate-window-settings1{a} 
  libmatekbd-common{a} libmatekbd4{a} libmateweather-common{a} 
  libmateweather1{a} libwebkitgtk-3.0-0{a} libwebkitgtk-3.0-common{a} 
  marco{a} marco-common{a} mate-backgrounds{a} mate-control-center{a} 
  mate-control-center-common{a} mate-desktop{a} mate-desktop-common{a} 
  mate-desktop-environment mate-desktop-environment-core{a} 
  mate-icon-theme{a} mate-menus{a} mate-panel{a} mate-panel-common{a} 
  mate-polkit{a} mate-polkit-common{a} mate-session-manager{a} 
  mate-settings-daemon{a} mate-settings-daemon-common{a} 
  mate-settings-daemon-gstreamer{a} mate-terminal{a} 
  mate-terminal-common{a} menu-xdg{a} zenity{a} zenity-common{a} 
The following packages are RECOMMENDED but will NOT be installed:
  atril engrampa eom ffmpegthumbnailer galculator geoclue-2.0 
  libcanberra-gtk-module mate-applets mate-icon-theme-faenza mate-media 
  mate-notification-daemon mate-power-manager mate-screensaver 
  mate-system-monitor mate-themes mate-utils menu menu:i386 pluma 
0 packages upgraded, 44 newly installed, 0 to remove and 0 not upgraded.
Need to get 57.0 MB/58.4 MB of archives. After unpacking 154 MB will be used.

it means the first possibility might the true reason why you can't upgrade mate. nevertheless, regardless the possibility you'd better remove mintsystem and debian-system-adjustment before move to testing. these package tends to break your system. the closer your system to debian testing is better.

[GeneC]

inxi -r:

Code: Select all

Repos:     Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
           deb http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
           deb http://www.deb-multimedia.org testing main non-free

.............

Woodsman, I see you don't have Mint repo in your sources...?
1st line...

(From "Jumping to Testing or Sid" thread)

B- moving to testing

1- check in the testing breakage topic if there's no problem listed

2- replace all the content of /etc/apt/sources.list with

Code: Select all

deb http://packages.linuxmint.com/ debian main upstream import backport
deb http://ftp.debian.org/debian testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://www.deb-multimedia.org testing main non-free

LMDE has its own Mate packages (import). http://packages.linuxmint.com/list.php?release=Debian
Debian also its own. https://packages.debian.org/search?suit ... words=mate
You have the Mint mate pkgs installed. Try adding the Mint repo and see if you still have conflicts. If so you MAY have to make some sort of preference file. (OR apt-pinning)..

[woodsman]

apt-cache policy:

Code: Select all

Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://www.deb-multimedia.org/ testing/non-free i386 Packages
     release v=None,o=Unofficial Multimedia Packages,a=testing,n=jessie,l=Unofficial Multimedia Packages,c=non-free
     origin www.deb-multimedia.org
 500 http://www.deb-multimedia.org/ testing/main i386 Packages
     release v=None,o=Unofficial Multimedia Packages,a=testing,n=jessie,l=Unofficial Multimedia Packages,c=main
     origin www.deb-multimedia.org
 500 http://security.debian.org/ testing/updates/non-free Translation-en
 500 http://security.debian.org/ testing/updates/main Translation-en
 500 http://security.debian.org/ testing/updates/contrib Translation-en
 500 http://security.debian.org/ testing/updates/non-free i386 Packages
     release o=Debian,a=testing,n=jessie,l=Debian-Security,c=non-free
     origin security.debian.org
 500 http://security.debian.org/ testing/updates/contrib i386 Packages
     release o=Debian,a=testing,n=jessie,l=Debian-Security,c=contrib
     origin security.debian.org
 500 http://security.debian.org/ testing/updates/main i386 Packages
     release o=Debian,a=testing,n=jessie,l=Debian-Security,c=main
     origin security.debian.org
 500 http://ftp.debian.org/debian/ testing/contrib Translation-en
 500 http://packages.linuxmint.com/ debian/backport i386 Packages
     release v=1,o=linuxmint,a=debian,n=debian,l=linuxmint,c=backport
     origin packages.linuxmint.com
 500 http://packages.linuxmint.com/ debian/import i386 Packages
     release v=1,o=linuxmint,a=debian,n=debian,l=linuxmint,c=import
     origin packages.linuxmint.com
 500 http://packages.linuxmint.com/ debian/upstream i386 Packages
     release v=1,o=linuxmint,a=debian,n=debian,l=linuxmint,c=upstream
     origin packages.linuxmint.com
 500 http://packages.linuxmint.com/ debian/main i386 Packages
     release v=1,o=linuxmint,a=debian,n=debian,l=linuxmint,c=main
     origin packages.linuxmint.com
 500 http://dl.google.com/linux/chrome/deb/ stable/main i386 Packages
     release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main
     origin dl.google.com
Pinned packages:

inxi -r:

Code: Select all

Repos:     Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
           deb http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com/ debian main upstream import backport
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
           deb http://www.deb-multimedia.org testing main non-free

My previous inxi output was incorrectly done after I disabled the linuxmint repo. I was madly trying to find a way around the problem.

Here is the failure of apt-get dist-upgrade:

Code: Select all

Preparing to unpack .../caja-common_1.8.1-2_all.deb ...
Unpacking caja-common (1.8.1-2) over (1.6.2-3+lmde) ...
Preparing to unpack .../archives/caja_1.8.1-2_i386.deb ...
Unpacking caja (1.8.1-2) over (1.6.2-3+lmde) ...
dpkg: error processing archive /var/cache/apt/archives/caja_1.8.1-2_i386.deb (--unpack):
 trying to overwrite '/usr/lib/caja/caja-convert-metadata', which is also in package libcaja-extension 1.6.2-3+lmde
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package caja-extensions-common.
Preparing to unpack .../caja-extensions-common_1.8.0-1_all.deb ...

[woodsman]

If so you MAY have to make some sort of preference file. (OR apt-pinning)..

I need coaching on that --- I am not going to bother tracking Testing unless I run the latest Mate.

nevertheless, regardless the possibility you'd better remove mintsystem and debian-system-adjustment before move to testing. these package tends to break your system. the closer your system to debian testing is better.

Perhaps then somebody knowledgeable should update the thread for tracking Testing or tag the thread obsolete and write new instructions?

[Monsta]

I don't have the logs anymore. I hadn't made the systemd logs permanent yet. But what I saw in the log (journalctl -b) when the problem occurred looked something like this:

Code: Select all

Found ordering cycle on basic.target/start
Walked on cycle path to sockets.target/start
Walked on cycle path to dbus.socket/start
Walked on cycle path to sysinit.target/start
Walked on cycle path to mintsystem.target/start
Breaking ordering cycle by deleting job dbus.socket/start

I've tried to reproduce it from the other end - by installing mintsystem in a Debian Testing VM (not LMDE, it just has Mint repo enabled).
I've got a different result:

Code: Select all

июл 21 11:10:41 jessica systemd[1]: Found ordering cycle on basic.target/start
июл 21 11:10:41 jessica systemd[1]: Found dependency on sysinit.target/start
июл 21 11:10:41 jessica systemd[1]: Found dependency on mintsystem.service/start
июл 21 11:10:41 jessica systemd[1]: Found dependency on dbus.service/start
июл 21 11:10:41 jessica systemd[1]: Found dependency on basic.target/start
июл 21 11:10:41 jessica systemd[1]: Breaking ordering cycle by deleting job mintsystem.service/start
июл 21 11:10:41 jessica systemd[1]: Job mintsystem.service/start deleted to break ordering cycle starting with basic.target/start

So systemd removed mintsystem service itself instead of dbus or some other service.
Nevertheless, it means that mintsystem needs to be corrected anyway. Thanks for spotting this issue.

[dumas777]

Today's update included an update to upower 0.99. For anyone running XFCE this breaks Suspend and Hibernate, which no longer appear as options when you choose to log out. There is a bug report here.

This breaks suspend and hibernate for many other WM/DE as well because upower no longer supports suspend (see command below for example that used to work from the command line) which as far as I know means regular users (without sudo) can no longer suspend the system even if you want them to be able to (now have to do a sudo or gksu pm-suspend). Also with the new upower, the calendar applet in Cinnamon 2.2 (built cinnamon debs myself) no longer was displaying right for me in the bottom panel (think this will be true of all recent cinnamon versions with new upower). The fix is to download the new applet.js (or add few line diff yourself to existing file) file at https://github.com/linuxmint/Cinnamon/t ... nnamon.org
and move it (as root or sudo) to /usr/share/cinnamon/applets/calendar@cinnamon.org/ (be sure to change owner and permission to match what is there).

Rant Alert: Friggin systemd (upower now part of, yet more functionality gobbled up by this hungry cancer, so much for doing one thing and doing it well I guess) is the Pulse Audio of init scripts (same original author and wish it would stay just an init script). They seem to just love breaking other userland stuff without giving a flying f__k. The more I use OpenBSD the more I realize how systemd is ruining many major linux distros. Soon to be Debian.

Old regular user suspend command: (used to be useful to put on a keybinding so you can add suspend to virtually any WM).

dbus-send --system --print-reply \
--dest="org.freedesktop.UPower" \
/org/freedesktop/UPower \
org.freedesktop.UPower.Suspend

[bithir]

I've not switched over to systemd yet and today I notice the following:

Code: Select all

The following packages will be REMOVED:
  sysvinit-core

I assume I somehow now is supposed to make the transition to systemd urgently. Is there any way to do this automatically or do I need to manually hack grub configurations to make it happen?

[kurotsugi]

simply install systemd-sysv and you'll officially use systemd in your system.

[Cyr4x]

Today's Cinnamon components update to 2.2.x version totally crashes whole IDE for me. When I log into system it displays a popup that Cinnamon couldn't load (and the only I can click is logout). I can log into Gnome-classic and then run cinnamon --replace from terminal. Cinnamon runs, nemo desktop appears, but if i click on the bottom panel, everything hangs. Deleting all hidden cinnamon directories from my home doesn't help. I've had to revert system partition from partimage backup and apt-mark hold cinnamon packages before upgrading again.

[kurotsugi]

cinnamon is expected to be broken in testing. it's not even available on testing yet. there might be some conflict between LMDE's cinnamon and debian's cinnamon too. no one can guarantee using LMDE+testing with cinnamon.

[zerozero]

Today's Cinnamon components update to 2.2.x version totally crashes whole IDE for me. When I log into system it displays a popup that Cinnamon couldn't load (and the only I can click is logout). I can log into Gnome-classic and then run cinnamon --replace from terminal. Cinnamon runs, nemo desktop appears, but if i click on the bottom panel, everything hangs. Deleting all hidden cinnamon directories from my home doesn't help. I've had to revert system partition from partimage backup and apt-mark hold cinnamon packages before upgrading again.

cinnamon 2.2 is only available in Sid.
https://packages.debian.org/sid/cinnamon
are you sure you don't have sid repos in your sources.list somewhere?
what is the output of

Code: Select all

inxi -r; apt policy cinnamon

[kurotsugi]

cinnamon is begin moving to testing https://lists.debian.org/debian-testing ... 00042.html
but apparently the migration isn't over yet. some of cinnamon packages haven't migrated to testing. if everything good we'll have complete cinnamon on testing tomorrow but I'm not sure what happened if we upgrade cinnamon from LMDE's cinnamon.

[Chris M]

If I understand this correctly, this is fixed in version 1.2.0-5 of xfce4-power-manager, which should migrate to testing in a couple of days.

Upgrade to xfce4-power-manager 1.2.0-5 from SID breaks the desktop.
Appears other packages are needed for a proper fix. Best to wait..

Gene, xfce4-power-manager 1.2.0-5 is coming in today. Has this been fixed in SID?