cropping an image in shotwell crashes unity

Bug #641554 reported by Omer Akram
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Shotwell
Won't Fix
Unknown
Unity
Fix Released
Critical
Neil J. Patel
shotwell (Ubuntu)
Invalid
Undecided
Unassigned
unity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: shotwell

if I open an image in shotwell (in unity session) and click crop then select the area I want to crop and then click again on crop to cut that area. unity crashes and reloads.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Fri Sep 17 23:56:28 2010
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: shotwell

Related branches

Revision history for this message
Omer Akram (om26er) wrote :
Revision history for this message
Jim Nelson (yorba-jim) wrote :

I'm unable to reproduce this. Does this happen with any photo in your library, or is it specific to one (or a few)?

Revision history for this message
Omer Akram (om26er) wrote :

hm I am able to reproduce this with a any image here. It seems.

Revision history for this message
Hernando Torque (htorque) wrote :

I too cannot reproduce this.

Revision history for this message
Omer Akram (om26er) wrote :

cant reproduce this on nvidia but is easiliy reproducable on my netbook (Intel Corporation Mobile 945GME Express Integrated Graphics Controller)

Changed in shotwell:
status: Unknown → New
Revision history for this message
Hernando Torque (htorque) wrote :

Good to know, I tried it with a Nvidia system.

Revision history for this message
Jim Nelson (yorba-jim) wrote :

I'm not sure from your description if Shotwell is segfaulting or it's entirely Unity. One thing that might help: Run Shotwell from a terminal window like this:

$ SHOTWELL_LOG=1 gdb shotwell 2>&1 | tee shotwell.gdb

At the gdb prompt type this:

(gdb) run

When Shotwell crashes, you should be at the gdb prompt. Type this:

(gdb) backtrace full

Then exit. If you could attach the shotwell.gdb file to this ticket that would be helpful.

If the crash is so hard it kills the terminal window and/or gdb (I've seen both in earlier revisions of Unity), then it's a larger problem than Shotwell.

Revision history for this message
Jim Nelson (yorba-jim) wrote :

For the record, my machine is running Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) (not a Netbook, however).

summary: - croping an image in shotwell crashes unity
+ cropping an image in shotwell crashes unity
Revision history for this message
Omer Akram (om26er) wrote :

cant get the backtrace because as unity crashes gnome-terminal crashes too due to bug 633303

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

@Omer: can you try with terminator? I'll set bug 633303 in a higher importance.

Revision history for this message
Omer Akram (om26er) wrote :

shotwell log is not showing anything as shotwell does not crash, unity crashes. how do I get a mutter backtrace?

Revision history for this message
Omer Akram (om26er) wrote :

oh and I can reproduce this on both nvidia and intel ;)

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Omer: you can run unity from a terminal with mutter --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so under gdb. Think to install debug symbol of course :)

Neil J. Patel (njpatel)
Changed in unity:
assignee: nobody → Neil J. Patel (njpatel)
importance: Undecided → Critical
milestone: none → 2010-09-22
Revision history for this message
Hernando Torque (htorque) wrote :

I managed to trigger such a crash (by removing missing images from the library), but it only worked once. Cropping still doesn't do anything else than cropping the image. Will keep trying with gdb attached.

Revision history for this message
Omer Akram (om26er) wrote :
Download full text (19.6 KiB)

om26er@om26er-laptop:~$ mutter --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so
(mutter:2921): libunity-private-DEBUG: gdk_window_set_mwm_hints: 44040639 0

Window manager warning: Log level 8: mutter_window_mapped: assertion `!priv->mapped' failed
Window manager warning: Log level 16: Unable to find the file menu stock item
Window manager warning: Log level 128: New Desktop Window: 1E00028
(mutter:2921): Indicator-Sound-DEBUG: At start-up attempting to set the image to audio-volume-muted-panel
Window manager warning: Log level 128: Evaluating bitmask for '%l:%M %p'
Window manager warning: Log level 128: Checking against 2 posible times
Window manager warning: Log level 128: Guessing max time width: 59
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(mutter:2921): libunity-private-DEBUG: unity_gesture_xcb_dispatcher_glue_init
Window manager warning: Log level 16: invalid cast from `BamfApplication' to `BamfWindow'
Window manager warning: Log level 8: bamf_window_get_window_type: assertion `BAMF_IS_WINDOW (self)' failed
Window manager warning: Log level 16: invalid cast from `BamfApplication' to `BamfWindow'
Window manager warning: Log level 8: bamf_window_get_window_type: assertion `BAMF_IS_WINDOW (self)' failed
Window manager warning: Log level 128: New Desktop Window: 1E00028
Window manager warning: Log level 16: Failed to fetch view type: Method "ViewType" with signature "" on interface "org.ayatana.bamf.view" doesn't exist

Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Window manager warning: Log level 128: Looking for parent window on XID 48234500
Window manager warning: Log level 128: Switching to menus from XID 48234500
Window manager warning: Log level 128: Unable to get MWM functions for: 48234500
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_...

Revision history for this message
Omer Akram (om26er) wrote :

bug 642669 and this might turn out to be the same. (I can reproduce both) in both cases clicking on a dialog from the main window crashes unity.

Revision history for this message
Vish (vish) wrote :

@Omer , didrocks mentioned getting a *gdb* and running that command under gdb.

have a look at: <https://wiki.ubuntu.com/Backtrace#Generation> ,
From a desktop session, you have to start gdb with:

 gdb mutter 2>&1 | tee ~/gdb-unity.txt

 and then in the arguments is :
(gdb) run --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so.0

and as didrocks mentioned , we need to install the debugging symbols

Revision history for this message
Neil J. Patel (njpatel) wrote :

Omer, would it be possible for you to test the indicator-appmenu branch that is linked from https://bugs.edge.launchpad.net/unity/+bug/642669 ? I think it solves this bug too.

Revision history for this message
Omer Akram (om26er) wrote :

Just build appmenu with that branch and the problem is still there.

Revision history for this message
Omer Akram (om26er) wrote :
Download full text (24.5 KiB)

got a backtrace with libunity0-dbgsym installed

GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/mutter...(no debugging symbols found)...done.
(gdb) run --replace --mutter -plugins=/usr/lib/mutter/pllugins/linbunity-mutter-.so.0
(gdb) run --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so.0
Starting program: /usr/bin/mutter --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so.0
[Thread debugging using libthread_db enabled]
[New Thread 0xb7952b70 (LWP 5925)]
[New Thread 0xb6e3db70 (LWP 5927)]
Window manager warning: Log level 16: Unable to find the file menu stock item
Window manager warning: Log level 128: New Desktop Window: 1800028
(mutter:5922): Indicator-Sound-DEBUG: At start-up attempting to set the image to audio-volume-muted-panel
Window manager warning: Log level 128: Evaluating bitmask for '%l:%M %p'
Window manager warning: Log level 128: Checking against 2 posible times
Window manager warning: Log level 128: Guessing max time width: 59
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(mutter:5922): libunity-private-DEBUG: unity_gesture_xcb_dispatcher_glue_init
Window manager warning: Log level 128: connecting to network service signals
Window manager warning: Log level 16: The dbus name we want is already taken
(mutter:5922): Indicator-Application-DEBUG: Connected to Application Indicator Service.
(mutter:5922): Indicator-Application-DEBUG: Setup proxy signals
(mutter:5922): Indicator-Application-DEBUG: Connect to them.
(mutter:5922): Indicator-Application-DEBUG: Request current apps
(mutter:5922): Indicator-Sound-DEBUG: about to connect to the signals
Window manager warning: Log level 128: set_icon_name(nm-signal-100)
Window manager warning: Log level 128: Username width 49px
Window manager warning: Log level 128: Font size 10.000000 pt
Window manager warning: Log level 128: Screen DPI 96.000000
Window manager warning: Log level 128: Username width 3.675000em
(mutter:5922): Indicator-Sound-DEBUG: indicator-sound: new_volume_slider_widget
(mutter:5922): Indicator-Sound-DEBUG: VolumeWidget::volume_widget_init
(mutter:5922): Indicator-Sound-DEBUG: volume_widget_set_twin_item initial level = 52.001953
(mutter:5922): Indicator-Sound-DEBUG: volume_widget_pa...

Revision history for this message
Neil J. Patel (njpatel) wrote :

Hmm, that's the exact bug this branch should fix, did you install into /usr ? It needs to overwrite the appmenu.so installed in /usr/lib/indicators/3/libappmenu.so and then restart Unity.

Revision history for this message
Neil J. Patel (njpatel) wrote :
Revision history for this message
Omer Akram (om26er) wrote :
Revision history for this message
Neil J. Patel (njpatel) wrote :

You know what? I just realised how this bug report is different, sorry!

Can you please do the gdb thing again, but this time, when it stops and you are at the gdb prompt "(gdb)", type in "bt" and press enter, and paste the output here please so I can see the stack and figure out where it crashed. If we can get that I think I can fix it pretty quickly, thanks!

Revision history for this message
Omer Akram (om26er) wrote :

the problem is when unity crashes in gnome-session (if started through gdb) system dies i.e. nothing can be clicked just the cursor moves so I have to kill X thats why previous logs were incomplete.

Revision history for this message
Vish (vish) wrote :

@Omer , pls read : <https://wiki.ubuntu.com/Backtrace#Generation> and all the steps..

the backtrace will be generated as a file, you can just attach it to the bug report. the comments can get way too long ;)

Changed in unity:
status: New → Incomplete
Revision history for this message
Vish (vish) wrote :

@Omer, you can try to ssh into the session too.

Revision history for this message
Vish (vish) wrote :

@Omer , If ssh is not possible, you can try what i did for similar problem > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/616997/comments/34

While running gdb, i noticed same problems, of no cursor.. so try copy-pasting.. its crude but worked ;p

Revision history for this message
Omer Akram (om26er) wrote :

the logs that I attached previously were copied from the text file generated by gdb.

if I was not clear: if I run unity from gdb with 'run --replace --mutter-plugins=/usr/lib/mutter/plugins/libunity-mutter.so.0' on a second or third attempt to crop an image in shotwell. system freezes i.e. no clicks are taken into account everything is like a still image just the cursor moves so I have to kill X. thats why I am not able to get a backtrace. I am googling for other methods to get a backtrace. I might find one ;-)

Revision history for this message
Neil J. Patel (njpatel) wrote :

Ah, okay sorry, this is the way you can get a backtrace for Unity without ssh etc:

- Use your Intel system
- Switch to VT1
- login
- export DISPLAY=:0
- export UBUNTU_MENUPROXY=libappmenu.so
- gdb --args mutter --replace --mutter-plugins=libunity-mutter
- At gdb prompt, type 'r' and then <enter>
- Switch to VT7
*** Cause the crash, system will stop responding but mouse will keep moving ***
- Switch back to VT1
- At the gdb prompt, type "bt" and <enter>

That should give you a full backtrace. Instead of copying it over, you can just take a picture of the trace with a camera and attach it to this bug, i just need to see the exact point of failure.

I hope that helps!

Revision history for this message
Omer Akram (om26er) wrote :

Window manager warning: Log level 128: Looking for parent window on XID 37749492
Window manager warning: Log level 128: Switching to menus from XID 37748739
[Thread 0xb6f5bb70 (LWP 7643) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0288a633 in egg_xid_get_functions () from /usr/lib/indicators/3/libappmenu.so
(gdb) bt
#0 0x0288a633 in egg_xid_get_functions () from /usr/lib/indicators/3/libappmenu.so
#1 0x0288b757 in ?? () from /usr/lib/indicators/3/libappmenu.so
#2 0x0288b91a in ?? () from /usr/lib/indicators/3/libappmenu.so
#3 0x0175408f in bamf_marshal_VOID__OBJECT_OBJECT () from /usr/lib/libbamf.so.0
#4 0x00a614b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#5 0x00a7a0e5 in ?? () from /usr/lib/libgobject-2.0.so.0
#6 0x00a7b75c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#7 0x00a7bec2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#8 0x0174f87b in ?? () from /usr/lib/libbamf.so.0
#9 0x0175420f in bamf_marshal_VOID__STRING_STRING () from /usr/lib/libbamf.so.0
#10 0x016905d4 in ?? () from /usr/lib/libdbus-glib-1.so.2
#11 0x00a614b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#12 0x00a7a0e5 in ?? () from /usr/lib/libgobject-2.0.so.0
#13 0x00a7b75c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#14 0x00a7bec2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#15 0x016918a3 in ?? () from /usr/lib/libdbus-glib-1.so.2
#16 0x016ae358 in dbus_connection_dispatch () from /lib/libdbus-1.so.3
#17 0x0168739d in ?? () from /usr/lib/libdbus-glib-1.so.2
#18 0x00af1015 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00af4e28 in ?? () from /lib/libglib-2.0.so.0
#20 0x00af5367 in g_main_loop_run () from /lib/libglib-2.0.so.0
#21 0x08082e13 in main ()
(gdb)

Revision history for this message
Omer Akram (om26er) wrote :
Download full text (3.3 KiB)

These logs would be better as they are generated after installing indicator-appmenu-dbgsym also attaching the complete file.

Window manager warning: Log level 16: invalid (NULL) pointer instance
Window manager warning: Log level 8: g_signal_connect_object: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Window manager warning: Log level 128: Active window is: NULL
Window manager warning: Log level 128: Switching to menus from XID 0
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 16: gtk_menu_detach(): menu is not attached
Window manager warning: Log level 8: bamf_window_get_xid: assertion `BAMF_IS_WINDOW (self)' failed
Window manager warning: Log level 128: Looking for parent window on XID 23070601
Window manager warning: Log level 128: Switching to menus from XID 23068675
Bug in window manager: Unexpected X error: BadWindow (invalid Window parameter) serial 6819 error_code 3 request_code 20 minor_code 0)
[Thread 0xb6fbbb70 (LWP 9223) exited]

Program received signal SIGABRT, Aborted.
0x0012e416 in __kernel_vsyscall ()
(gdb) bt
#0 0x0012e416 in __kernel_vsyscall ()
#1 0x00d50941 in raise () from /lib/libc.so.6
#2 0x00d53e42 in abort () from /lib/libc.so.6
#3 0x080920cc in meta_bug ()
#4 0x0807a57f in ?? ()
#5 0x00bf02c9 in _XError () from /usr/lib/libX11.so.6
#6 0x00bf70de in _XReply () from /usr/lib/libX11.so.6
#7 0x00bd4316 in XGetWindowProperty () from /usr/lib/libX11.so.6
#8 0x0288a5e4 in gdk_xid_get_mwm_hints (window=23070601, functions=0xbfffe89c) at gdk-get-func.c:97
#9 egg_xid_get_functions (window=23070601, functions=0xbfffe89c) at gdk-get-func.c:123
#10 0x0288b717 in switch_active_window (iapp=0x810f9d0, active_window=<value optimized out>) at indicator-appmenu.c:766
#11 0x0288b8da in switch_default_app (iapp=0x810f9d0, newdef=<value optimized out>, active_window=0xb6614090)
    at indicator-appmenu.c:838
#12 0x0175408f in bamf_marshal_VOID__OBJECT_OBJECT () from /usr/lib/libbamf.so.0
#13 0x00a614b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#14 0x00a7a0e5 in ?? () from /usr/lib/libgobject-2.0.so.0
#15 0x00a7b75c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#16 0x00a7bec2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#17 0x0174f87b in ?? () from /usr/lib/libbamf.so.0
#18 0x0175420f in bamf_marshal_VOID__STRING_STRING () from /usr/lib/libbamf.so.0
#19 0x016905d4 in ?? () from /usr/lib/libdbus-glib-1.so.2
#20 0x00a614b2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#21 0x00a7a0e5 in ?? () from /usr/lib/libgobject-2.0.so.0
#22 0x00a7b75c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#23 0x00a7bec2 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#24 0x016918a3 in ?? () from /usr/lib/libdbus-glib-1.so.2
#25 0x016ae358 in dbus_connection_dispatch () from /lib/libdbus-1.so.3
#26 0x0168739d in ?? () from /usr/lib/libdbus-glib-1.so.2
#27 0x00af1015 in g_main_context...

Read more...

Revision history for this message
Neil J. Patel (njpatel) wrote :

Excellent, thanks! It seems that it is in the same place, but we might be hitting different things, could you please try

lp:~indicator-applet-developers/indicator-appmenu/one-more-xerror-fix

As I fixes a crash I have with Shotwell and repeatedly pressing the crop button very quickly (causing unity to crash), but this happens on a XFree. Once again, thanks for this, it *really* helps Unity development!

Revision history for this message
Omer Akram (om26er) wrote :

Yep fixed.

Revision history for this message
Omer Akram (om26er) wrote :

invalidating shotwell as upstream bug was also closed.

Changed in shotwell (Ubuntu):
status: New → Invalid
Revision history for this message
Neil J. Patel (njpatel) wrote :

Woohoo!

Changed in unity:
status: Incomplete → Fix Committed
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 641554] Re: cropping an image in shotwell crashes unity

Knock another one off the fence :-)

Revision history for this message
Vish (vish) wrote :

> On Tue, 2010-09-21 at 17:11 +0000, Neil J. Patel wrote:
> Woohoo!
>

:-)

Changed in shotwell:
status: New → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.7 KiB)

This bug was fixed in the package unity - 0.2.42-0ubuntu1

---------------
unity (0.2.42-0ubuntu1) maverick; urgency=low

  * New upstream release:
    - "Applications" and "Files & Folders" tooltips are not translatable
      (LP: #644215)
    - Fix inactive menus are accessible on switching to a window (LP: #604505)
    - Fix wrong launcher tile label/quicklist x position (LP: #631446)
    - Fix highlighted items in quicklist have different widths (LP: #643315)
    - In migration tool, being safe when people are using crazy caracters in
      desktop file (LP: #644114, #635156)
    - Detect if 3D acceleration support is provided. Otherwise, prompt for
      logout and change default session (LP: #614088)
    - Fix quicklist shows hidden menu items (LP: #641543)
    - Fix removing launchers via dnd fails (LP: #643434)
    - Better launcher auto-scroll performances (LP: #640560)
    - Make the insensitive state of the forward- and back-button more obvious by
      decreasing their opacity, thus users don't assume they are actually
      clickable. (LP: #638285)
    - Fix some dialogs aren't maximized but are undecorated (LP: #628822)
    - Fix some menus don't go away when window closes (LP: #640557)
    - Fixes bug where the wrong icon where at times associated with a tile in
      the places view. (LP: #642935)
    - Speedup icon loading (LP: #641246)
    - Make trash menu items in Unity are either not translatable or translations
      are not loaded (LP: #645038)
    - Fix using dnd on launcher makes focus not work out of the unity ui
      (LP: #637123)
    - Multi-monitor support (LP: #637123)
    - Enable/disable super key by a gconf key (LP: #632581)
    - Remove glow on fold (LP: #619344)
    - Ensure we dont map windows when expose is active (LP: #599766)
    - take new indicator API for action for top-level dropdown menu item not
      activated (LP: #637692)
    - Make the home buttons reactive (LP: #638857)
    - Add red tint when search fails (LP: #607821)
    - New (and final!) UI adjustement, but UNE isn't in the doc as seen with
      the doc team (LP: #627009)
    - Single-touches on the launcher are usually interpreted as a drag
      (LP: #641328)
    - URI activation in global view (LP: #612562)
    - Clicking a Place icon while viewing the same place in the Dash should
      return to the Home screen of that place and clear the search (LP: #607829)
    - Fix mutter crashed with SIGSEGV in g_type_check_instance() (LP: #641561)
    - Fix panel and menu item font colors don't match (LP: #637480)
    - Fix indicators have orange color (LP: #632975)
    - Fix inactive menus are accessible on switching to a window (LP: #604505)
    - Use semi-transparent rectangle around launcher-icon (LP: #643388)
    - Fix mutter crashes when closing pop-up dialog (LP: #642669)
    - Change launcher icon reference size loading (LP: #641669)
    - Fix mutter crashing in mumble start (LP: #641335)
    - Fix clicking on a category from CoFs does not directly take you to the
      desired category (LP: #638402)
    - Fix some menus don't go away when window closes (LP: #640557)
    - Launchers should act like if the application was not focussed ...

Read more...

Changed in unity (Ubuntu):
status: New → Fix Released
Omer Akram (om26er)
Changed in unity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.