Yes, you are right these things shouldn't happen in a stable LTS, and your anger is justified. But you know have a solution for it, hope you can get it working back again and unboil yourself down...
Computers have no brains, so they are as fallible as the ones that program them, and I know they work a lot
for my great OS free as in free beer! So the Mint and Mate devs still have all my patience, respect and gratitude.
The same thing happened to me while I was doing serious work, but there again, even knowing chances things break are low, I shouldn't update while working, mea culpa
here on my behalf.
Since I'm no expert, it took me an hour of trial and error until I find the solution, but I made it work back again on my own so I'm happy, I've learned a couple of new tricks. Came here to see if there were people needed help but someone helped first, so it's always nice to see the community working fast! Kudos!
Ok, so I can boot my system now but I've got my notifications changed and I cannot see where to configure it. Shouldn't it be in the Control Center?
Meanwhile, I've been digging around and I've checked that mate-notification-daemon
is not installed. I tried to, but it depends on libmatewnck (>= 1.5.1)
and apt says I have hold packages. libmatewnck depends on libmatewnck
, in turn depending on libmatewnck-common (= 1.6.0-1+precise) but 1.6.1-1+maya is to be installed
So it's my turn to ask for help and suggestions...
Any hints, or, since this is not critical at all, should I just wait for a couple of days and hope the solution is inserted into the repos?
Please note that I upgraded from mate 1.6 (.1, I guess). I've done a dist-upgrade on the terminal.
Should I also run