Ok, removing "dbus" prerequisite from /etc/init.d/mintsystem script seems to fix this issue. I don't see why this script requires dbus in the first place - it's not used in the adjustment script or anywhere else.GeneBenson wrote:I finally narrowed it down to a conflict between dbus and mintsystem at startup time.
Upgrade Warnings: LMDE tracking TESTING [10-11-14]
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Today's upgrade makes system "unloggable". If I try to login to Cinnamon or Gnome classic it stucks on a black screen with mouse arrow. Nothing goes further. As I've found some lib starting on p or o letter causes this (libo*.deb or libp*.deb).
EDIT:
Strange. Only logging in from graphical prompt does the problem. When i log in from text prompt on TTY1 and run startx it runs Cinnamon with no troubles.
EDIT:
Strange. Only logging in from graphical prompt does the problem. When i log in from text prompt on TTY1 and run startx it runs Cinnamon with no troubles.
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
I think I can confirm this. Logging in from mdm gets stuck.Not exactly sure which packaged caused this as I did a really big dist-upgrade today.Cyr4x wrote:Strange. Only logging in from graphical prompt does the problem. When i log in from text prompt on TTY1 and run startx it runs Cinnamon with no troubles.
Think I caught sight of some gdk-pixbuf error similar to http://forums.linuxmint.com/viewtopic.p ... de#p828324 but following the instructions there didn't solve my problem. After some hair pulling, I've installed lightdm for the time being which works too (only how to use startx to log in to root...) in place of mdm. But I noticed all my startup scripts at log in don't run anymore.
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Can't reproduce that in my Debian Testing VM (not LMDE, but has some Mint packages installed) with MATE and MDM 1.6.9.
The login is fine.
Maybe you should try this version of MDM?
The login is fine.
Maybe you should try this version of MDM?
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
It's gnome-keyring 3.12 that breaks the manual login in MDM.Cyr4x wrote:Today's upgrade makes system "unloggable". If I try to login to Cinnamon or Gnome classic it stucks on a black screen with mouse arrow. Nothing goes further
Automatic login still works.
Strange that I couldn't reproduce it earlier... gnome-keyring 3.12 migrated to Testing on 3rd September...
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
That's it. Just edit the file /etc/pam.d/mdm and comment two lines:
That solves the issue and I can login from mdm to my desktop again.
Code: Select all
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Yeah, I use this workaround too. However, it won't be applied in Mint as a solution since the keyring isn't unlocked automatically on login now.
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Finally, fglrx is back in Testing (this version should be compatible with xserver 1.16).
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
Today's kernel update to 3.16 crashes X server with Nvidia graphics (340.32 drivers). If i remove xorg.conf X server starts, but in 1024x768 resolution and no 3d acceleraton of course. I don't know, it's lack of some gfx modules for the new kernel?
EDIT:
Problem solved, that was simple. Just rebuild DMKS module for Nvidia driver:
EDIT:
Problem solved, that was simple. Just rebuild DMKS module for Nvidia driver:
Code: Select all
sudo dpkg-reconfigure nvidia-kernel-dkms
Last edited by Cyr4x on Mon Sep 29, 2014 5:32 pm, edited 1 time in total.
Re: Upgrade Warnings: LMDE tracking TESTING [16-07-14]
This is an amazing hack, just made my day!! Apparently lightdm (which I've been using for about a month now) starts up some programs wayyy slower than mdm But yeah, thinks are back to their nice and snappy state nowCyr4x wrote:That's it. Just edit the file /etc/pam.d/mdm and comment two lines:That solves the issue and I can login from mdm to my desktop again.Code: Select all
auth optional pam_gnome_keyring.so session optional pam_gnome_keyring.so auto_start
Re: Upgrade Warnings: LMDE tracking TESTING [29-09-14]
Skype plugin for libpurple messengers (pidgin-skype) is broken in Testing. Get the fixed version from Sid.
Re: Upgrade Warnings: LMDE tracking TESTING [29-09-14]
Afer upgrading kernel to 3.16 Mintupdate crashes with statement:
Code: Select all
Attempt to unlock mutex that was not locked
Aborted
Re: Upgrade Warnings: LMDE tracking TESTING [29-09-14]
it's not the upgrade to kernel 3.16, (i'm sorry for posting a link to another forum but i saw the same problem yesterday with other applications >> 1)
Re: Upgrade Warnings: LMDE tracking TESTING [29-09-14]
I don't have mintupdate (tracking testing from Sparky now) but mirage and reportbug give the same errors here. They still worked with 3.16 (for a day or two). I suppose at least in my case it was the libglib2.0-packages moving from 2.40.0-5 to 2.42.0-1 that did it. It seems that some gtk-programs also have a slightly different appearance since that change.
Edit: Same problem with pyrenamer.
2nd edit: As mentioned in Debian's bug report #763787 https://bugs.debian.org/cgi-bin/bugrepo ... bug=763787 you can solve the mutex-problem by downgrading all your libglib2.0-packages to your last working version or (in case you have none in /var/cache/apt/archives) to version 2.41.1-2 which you can get from snapshot.debian.org . It worked in my case with the snapshot-versions.
Edit: Same problem with pyrenamer.
2nd edit: As mentioned in Debian's bug report #763787 https://bugs.debian.org/cgi-bin/bugrepo ... bug=763787 you can solve the mutex-problem by downgrading all your libglib2.0-packages to your last working version or (in case you have none in /var/cache/apt/archives) to version 2.41.1-2 which you can get from snapshot.debian.org . It worked in my case with the snapshot-versions.
Re: Upgrade Warnings: LMDE tracking TESTING [29-09-14]
This is due to some recent changes in GLib >= 2.41.Code: Select all
Attempt to unlock mutex that was not locked
See this comment for the complete info.
As GTK+ devs said, they've patched both GTK+ 2 and 3 to introduce a workaround for this issue:
- GTK+2 commit (not yet available in Debian, but you can patch and build gtk+2.0 yourself)
- GTK+3 commit (available in GTK+ 3.14)
So, there are two ways to fix this:
- The "right" way: adjust the code of every application that uses GDK threads to make sure it has threads_enter/threads_leave wrapping around gtk.main() call.
- Get the patched GTK+ 2 and 3 with the aforementioned workaround.
Here's the list:
- mintBackup patch (edit /usr/lib/linuxmint/mintBackup/mintBackup.py)
- mintUpload patch (edit /usr/lib/linuxmint/mintUpload/file-uploader.py)
- mintUpdate (only LMDE version!) patch (edit /usr/lib/linuxmint/mintUpdate/mintUpdate.py)
- mintInstall patch (edit /usr/lib/linuxmint/mintInstall/{frontend.py, mintInstall.py, mintinstall.py, remove.py})
- blueproximity (patch inside)
- geany-plugin-debugger
- gftp (patch inside)
- gnome-do
- keepnote (patch inside)
- mirage (patch inside)
- ntfs-config
- pyrenamer
- radiotray (fixed version is in Sid)
- reportbug
- spacefm (fixed version is already in Testing)
- wordwarvi (patch inside)
Re: Upgrade Warnings: LMDE tracking TESTING [06-10-14]
Upgrading lightdm from 1.10.1-3 to 1.10.2-2 breaks it if you choose to keep the current configuration file (/etc/lightdm/lightdm.conf).
LightDM crashes and you have to run startx manually to get to your desktop.
If you experience this (or simply don't want to replace your config), edit this file and comment/erase these lines:
The "greeter-session" parameter may have any other value on your system, but you need to comment it anyway.
It has something to do with the new /usr/share/lightdm/lightdm.conf.d/01_debian.conf file:
LightDM crashes and you have to run startx manually to get to your desktop.
If you experience this (or simply don't want to replace your config), edit this file and comment/erase these lines:
Code: Select all
greeter-session=lightdm-greeter
session-wrapper=/etc/X11/Xsession
It has something to do with the new /usr/share/lightdm/lightdm.conf.d/01_debian.conf file:
Code: Select all
# Debian specific defaults
#
# - use lightdm-greeter session greeter, points to the etc-alternatives managed
# greeter
# - hide users list by default, we don't want to expose them
# - use Debian specific session wrapper, to gain support for
# /etc/X11/Xsession.d scripts
[SeatDefaults]
greeter-session=lightdm-greeter
greeter-hide-users=true
session-wrapper=/etc/X11/Xsession
Re: Upgrade Warnings: LMDE tracking TESTING [06-10-14]
And as if the mutex issue wasn't enough, some Python apps (mintlocale, mintupload, keepnote, mirage, reportbug) now crash on start with segfault:
This time I really can't figure out who broke it, because there were no updates to python or pygtk...
Code: Select all
[ 2185.028421] mirage[3072]: segfault at 0 ip (null) sp 00007fff36fb4228 error 14 in python2.7[400000+31c000]
Re: Upgrade Warnings: LMDE tracking TESTING [06-10-14]
no change for me (at least with mirage- the only affected app that i have installed here apart from deadbeef)
in today's batch of updates
but that didn't make a difference.
Code: Select all
zerozero@home ~ $ mirage
Attempt to unlock mutex that was not locked
Aborted
zerozero@home ~ $
Code: Select all
Setting up libglib2.0-data (2.42.0-2) ...
Setting up libglib2.0-0:amd64 (2.42.0-2) ...
Setting up libglib2.0-0:i386 (2.42.0-2) ...
Setting up libglib2.0-bin (2.42.0-2) ...
Setting up libglib2.0-dev (2.42.0-2) ...
Re: Upgrade Warnings: LMDE tracking TESTING [06-10-14]
Ok, nevermind, found out who's responsible for that: this hack which I've been testing yesterday and haven't disabled afterwards. Sorry for the false alarm.
Re: Upgrade Warnings: LMDE tracking TESTING [06-10-14]
Something weird happened after an upgrade few days ago. When i try to turn off PC, it runs a job for LSB that counts up to 5 mins. After that, the PC restarts instead of turning off. Look at the screenshot.