[Bug 1051447] Re: [regression] Filenames and paths that contain an apostrophe before a space in the name won't open correctly

Doug McMahon 1051447 at bugs.launchpad.net
Sun Sep 16 02:41:12 UTC 2012

The only weird thing  in general is that any word(s) & spaces before the 1st. apostrophe are treated normally (as one), after the 1st occurrence of an apostrophe then spaces & words are separated.
If there is no space after the first occurrence of an apostrophe then all is normal

Anyway, on a live session with an  image that used glib2.0 (2.33.8-1) only updating libglib2.0 & libglib2.0-bin was enough to cause this to start happening.
The update jumped glib up to the current 2.33.12-4, whether it's worth testing the in-betweens don't now, if so ask..

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glib2.0 in Ubuntu.

  [regression] Filenames and paths that contain an apostrophe before a
  space in the name won't open correctly

Status in “glib2.0” package in Ubuntu:

Bug description:
  Test cases:
  Find or rename an audio file so there is an apostrophe before a space in name
  right click on > open with Movie Player (or any media player
  Ex. - I'll be around.flac

  Name any text file in similar fashion,  r. click > open with Text Editor
  Ex. -  don't forget to do

  In addition to context can be seen from cli with xdg-open, gvfs-open &
  gtk-launch <app> <url>

  This wasn't  a problem with glib thru glib2.0 (2.33.8-1), probably became one with glib2.0 (2.33.12-1) or thereabouts
  (can be tracked down if need be

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libglib2.0-0 2.33.12-3
  ProcVersionSignature: Ubuntu 3.5.0-14.17-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 15 19:35:55 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120912)
   PATH=(custom, no user)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list