Running Linux Mint 12 x64, Cinnamon from a nightly build (1.2.0-20120211030001-oneiric), NVidia Driver V 280.13 running in Dual Monitor mode with main desktop in right hand screen. Using it as OS for proper work have found the following issues that appear to relate to the fact that it's a 2 monitor set up, i.e. they don't appear on my laptop, hence grouping them together:-
1) Top left dash trigger can't be switched off. GitHub issue 325 raised (12/02/12)
2) Windows pop up and change screens on dual monitor set up, i.e. Nautilus when changing directories.
3) Bottom Panel applet minimised window mouseover titles appear on left screen when applet is in right screen and is primary screen.
4) Notifications appear at the right hand side of the left hand screen when the right hand screen is the primary screen.
5) Desktop icons don't stay where they're put on reboot.
6) No indication an app is starting once clicked.
7) The "Mute" icon that pops up when you mute/unmute is VERY low res and looks badly out of focus on a desktop.
8) Second monitor not part of workspace by default.
With the release of Cinnamon 1.4, items 5, 7 and 8 appear to have been solved. All others remain outstanding though.
using 1.4 on Ubuntu 11.10
main ones I noticed are:
#4 - I would like this to be customised somehow (active monitor?)
#7 is still an issue for me.
#8 not sure if the OP is talking about expo mode or not but expo mode only shows monitor 1 (not a huge deal but its still there)
It also fails to me: #242
Cinnamon 1.4.0-UP3 + NVidia 295.53 (x86) + Dual Display with TwinView (Primary on the right one)
If the primary is the left it doesn't happen.
(cinnamon:11841): St-WARNING **: percentage lengths not currently supported
Window manager warning: Log level 16: The program 'cinnamon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 561 error_code 2 request_code 151 minor_code 31)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)