[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Allison Ryan Lortie]

The latest patch looks good to me, but with a couple of notes (no need
to fix these):

 - using the _full() version of the timeout call is not necessary here

 - now that this patch is simplified it becomes easy to see how all of
this is just putting values into one structure and then later moving
them into another structure.  It seems like we could have just used the
first structure type, or even just fixed the other queue mechanism to
add the delay.  Oh well.  No real gain from making that change at this
point.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1506744

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  In Progress
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Allison Ryan Lortie]

To elaborate on the previous remark: why didn't we just replace:

  menu_monitor_queue_event (event_info);

with:

  g_timeout_add_seconds (2, menu_monitor_queue_event, event_info);


(and make sure menu_monitor_queue_event() returns FALSE)?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1506744

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  In Progress
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Allison Ryan Lortie]

The patch in comment 42 is not acceptable, for two big reasons.

First: you need to hold a ref on the GFile object when you put it into
the info struct.  This means that you cannot simply use g_free for the
struct: you need to write a custom free func that handles the unref as
well.  Also: you can't cast g_source_remove() to a GDestroyNotify and
expect that to work... one takes a pointer, and the other an int.  This
may randomly work on some architectures, sometimes, but you cannot rely
on this.

The entire act of keeping the list is slightly suspect.  At the sprint I
think I mentioned that it would be better to have one global timeout
that is set (and reset) when any activity happens.  The timeout would
run after the activity died down, and it would handle all things
together in one go.  In that case, you'd still need a list, except for
the info objects themselves.  It's also fine to keep the list of the
timeout IDs, but you can't free it in the way that you're doing in the
current patch.

Another nice approach, if you want to avoid running the callbacks after
teardown: store a weak pointer to the main object in each of the info
structs (g_object_add_weak_pointer).  The info structs are then used as
the user_data to the timeout (this assumes you keep the multiple
timeouts).  If you find the weak pointer to be empty, then just return
without doing anything.  That also means that you don't need to handle
the "cleanup" -- it will happen automatically.  It also means that you
can avoid the custom free function if you are clever: the timeout will
always run once, and you can do the cleanup from the normal handler
(taking care regarding the early exit discussed above).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-menus in Ubuntu.
https://bugs.launchpad.net/bugs/1506744

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  In Progress
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

[Allison Ryan Lortie]

Although I agree that it makes sense to allow the user to modify their
own data even if not "actively logged in", I think it would also be
interesting to track down the program that is the real source of this
problem.  ie: let's figure out which part of the session is writing to
accountsservice at random times...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1512002

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in policykit-1-gnome package in Ubuntu:
  Confirmed

Bug description:
  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/1512002/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 867424]

[Ryan Lortie]

There is really no good reason for this code to exist anymore.  I ended
up with libgnome installed as a dependency for another old program and
my Firefox install started misbehaving as a (nearly untracable)
sideeffect of that.  It took me quite a while to figure out that a
Firefox bug could be triggered as a result of installing an unrelated
program.

The fact that I didn't have libgnome installed before, and everything
was working just fine, is as much of an indication as any that this code
needs to die.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/867424

Title:
  Oneric: On boot up Firefox always displays the “Well, This Is
  Embarrassing” screen.

Status in The Mozilla Firefox Browser:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged
Status in firefox source package in Precise:
  Triaged
Status in thunderbird source package in Precise:
  Triaged

Bug description:
  This happens on every restart or boot. Firefox fails to load previous
  tabs.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 7.0.1+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:240: no soundcards found...
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20110929022028
  CRDA: Error: [Errno 2] No such file or directory
  Channel: release
  Date: Tue Oct  4 13:15:01 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: NoScript - ID={73a6fe31-595d-460b-a920-fcc0f8843232}, 
Version=2.1.4rc2, minVersion=1.9a2, maxVersion=1.9.6, Location=app-profile, 
Type=extension, Active=Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110910)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.4  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929022028 (Running)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserJS: general.useragent.vendor - Firefox
  dmi.bios.date: 01/23/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0304
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EH
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0304:bd01/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/867424/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

[Ryan Lortie]

I'm not sure it would be very helpful for me to review this either --
I'm very unfamiliar with the codebase and even with how locking works in
libdbus-1.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1384776

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1383486] Re: menu to select zoom doesn't drop down

[Ryan Lortie]

This was fixed upstream here:
https://git.gnome.org/browse/gtk+/commit/?id=a1af365566161067c4eb246a1c66e7914f119537

Unfortunately this doesn't backport cleanly.  I'll try to rebase the
patch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1383486

Title:
  menu to select zoom doesn't drop down

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce open a pdf file in evince from pcmanfm or another file
  manager. Then move the mouse to the upper right corner of the window
  along the top bar. Then try to click on the arrow pointing down to
  drop down the menu. The mouse pointer will click but no menu will drop
  down. I can still edit the zoom by clickin in this bar but I cannoy
  select fit page or fit width like I used to be able to in 14.04. I am
  using lxde as my desktop environment with openbox as my window
  manager.

  evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu 14.10
  Release:  14.10
  I expected a menu to be able to choose zoom instead I can only change zoom by 
typing in the box. 

  Work around is to manually set a zoom by typing it in. This could lead
  to some accessibility problems for people with low vision if they need
  to zoom in on a pdf and don't know the workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Oct 20 14:08:31 2014
  InstallationDate: Installed on 2014-09-30 (19 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1383486] Re: menu to select zoom doesn't drop down

[Ryan Lortie]

It will work if we also take 0dcffe3cd421555926e74002d5297d6dac0886e7,
which is another bugfix that may be worth having.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1383486

Title:
  menu to select zoom doesn't drop down

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce open a pdf file in evince from pcmanfm or another file
  manager. Then move the mouse to the upper right corner of the window
  along the top bar. Then try to click on the arrow pointing down to
  drop down the menu. The mouse pointer will click but no menu will drop
  down. I can still edit the zoom by clickin in this bar but I cannoy
  select fit page or fit width like I used to be able to in 14.04. I am
  using lxde as my desktop environment with openbox as my window
  manager.

  evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu 14.10
  Release:  14.10
  I expected a menu to be able to choose zoom instead I can only change zoom by 
typing in the box. 

  Work around is to manually set a zoom by typing it in. This could lead
  to some accessibility problems for people with low vision if they need
  to zoom in on a pdf and don't know the workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Oct 20 14:08:31 2014
  InstallationDate: Installed on 2014-09-30 (19 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1383486] Re: menu to select zoom doesn't drop down

[Ryan Lortie]

Both have been pushed upstream on gtk-3-12 branch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1383486

Title:
  menu to select zoom doesn't drop down

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  To reproduce open a pdf file in evince from pcmanfm or another file
  manager. Then move the mouse to the upper right corner of the window
  along the top bar. Then try to click on the arrow pointing down to
  drop down the menu. The mouse pointer will click but no menu will drop
  down. I can still edit the zoom by clickin in this bar but I cannoy
  select fit page or fit width like I used to be able to in 14.04. I am
  using lxde as my desktop environment with openbox as my window
  manager.

  evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
   *** 3.14.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu 14.10
  Release:  14.10
  I expected a menu to be able to choose zoom instead I can only change zoom by 
typing in the box. 

  Work around is to manually set a zoom by typing it in. This could lead
  to some accessibility problems for people with low vision if they need
  to zoom in on a pdf and don't know the workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Oct 20 14:08:31 2014
  InstallationDate: Installed on 2014-09-30 (19 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140930)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1383486/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

[Ryan Lortie]

The patch already went upstream in NetworkManager and now we have an
Ubuntu package landing soon.

The upshot is that we now have a simple DBus property:

  system
  org.freedesktop.NetworkManager
  /org/freedesktop/NetworkManager
  org.freedesktop.NetworkManager.PrimaryConnectionType

which is a string like '802-11-wireless' or 'bluetooth'.  If there is no
connection then it is an empty string.

We don't have normal D-Bus property change notification here but rather
a custom-rolled signal from NetworkManager itself (PropertiesChanged).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1384776

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()

[Ryan Lortie]

GLib completely changed the implementation of GMutex from being based on
POSIX primatives to being based on a home-grown solution that is
substantially faster (and with room for further improvements).

This caused deadlocks/crashes in some Vala programs, and I wonder if the
same thing is going on with Mono.  See this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=733500

** Bug watch added: GNOME Bug Tracker #733500
   https://bugzilla.gnome.org/show_bug.cgi?id=733500

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1344386

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in “glib2.0” package in Ubuntu:
  New
Status in “gnome-do” package in Ubuntu:
  Confirmed

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()

[Ryan Lortie]

Invalid for glib since the bug is confirmed as being in gnome-do (not
acquiring the lock before gtk_main).

** Changed in: glib2.0 (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1344386

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “gnome-do” package in Ubuntu:
  Confirmed

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()

[Ryan Lortie]

The new mutex implementation detects the (error) case when you try to
unlock a mutex that is not locked.

Callers are supposed to acquire the Gtk lock before calling gtk_main()
and I guess gnome-do isn't doing that...

POSIX silently ignores this...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1344386

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “gnome-do” package in Ubuntu:
  Confirmed

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()

[Ryan Lortie]

** Also affects: do
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1344386

Title:
  Do.exe crashed with SIGABRT in __GI_raise()

Status in Do:
  New
Status in “glib2.0” package in Ubuntu:
  Invalid
Status in “gnome-do” package in Ubuntu:
  Fix Released

Bug description:
  Do.exe crashed with SIGABRT in __GI_raise()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-do 0.9-1build1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 18 17:47:01 2014
  ExecutablePath: /usr/lib/gnome-do/Do.exe
  InstallationDate: Installed on 2014-05-16 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/mono-sgen
  ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
  Signal: 6
  SourcePackage: gnome-do
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
   __GI_abort () at abort.c:89
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? ()
  Title: Do.exe crashed with SIGABRT in __GI_raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/do/+bug/1344386/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1296233] Re: increase in number of wakeups in recent release in indicator-datetime

[Ryan Lortie]

This is my fault indeed.  I introduced the code that added this watch
without remembering that it does the wrong thing in the case of missing
directories.  I think the correct fix here is to reevaluate our approach
to dealing with missing files in the inotify monitor...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1296233

Title:
  increase in number of wakeups in recent release in indicator-datetime

Status in The Date and Time Indicator:
  Confirmed
Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  The number of wakeup events has quadrupled in a recent release of
  indicator datetime on Trusty 14.04, so this looks like a minor
  regression.

  http://ci.ubuntu.com/power/eventstat/image/3101/machine/1/task
  /indicator-datetime-service/details

  In the previous set of runs it was down to ~2 wakeups a minute, now
  it's up to 8 again.

  Attached is the output of a heath-check analysis of indicator-
  datetime-service showing the activity over 5 minutes. It seems that
  there is a poll occurring every 4 seconds which may be the root cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1296233/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1284647] Re: gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal()

[Ryan Lortie]

Confirmed GLib bug: https://bugzilla.gnome.org/show_bug.cgi?id=710367

** Bug watch added: GNOME Bug Tracker #710367
   https://bugzilla.gnome.org/show_bug.cgi?id=710367

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1284647

Title:
  gsettings crashed with SIGSEGV in g_settings_backend_dispatch_signal()

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  Crash collected during automated installer tests of ubuntu and ubuntu-
  gnome [1]

  https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Ubuntu-Gnome/job
  /ubiquity_ap-ubuntu-gnome_devel_daily-
  test_custom_install/ARCH=amd64,label=rabisu/92/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.90-0ubuntu1
  Uname: Linux 3.13.0-12-generic x86_64
  Architecture: amd64
  Date: Tue Feb 25 03:27:46 2014
  ExecutablePath: /usr/bin/gsettings
  ExecutableTimestamp: 1392811897
  ProcCmdline: gsettings set org.gnome.settings-daemon.plugins.power active 
false
  ProcCwd: /home/ubuntu-gnome/ubiquity-autopilot/autopilot
  ProcEnviron:
   TERM=unknown
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: glib2.0
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_backend_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1284647/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1246516] Re: Memory from slice allocator passed to PyObject_Free

[Ryan Lortie]

This is not the same as the error we were seeing before: that error was
an invalid read on memory that was just before a piece of memory that
was allocated through the slice allocator.  There is no gslice in this
trace...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1246516

Title:
  Memory from slice allocator passed to PyObject_Free

Status in “pygobject” package in Ubuntu:
  New

Bug description:
  This issue is causing segfaults in Trusty. Here is the valgrind
  output:

  ==8100== Invalid read of size 4
  ==8100==at 0x5A479E: PyObject_Free (obmalloc.c:987)
  ==8100==by 0x443D7A: xmlparse_ParseFile.45364 (pyexpat.c:865)
  ==8100==by 0x4B410B: PyEval_EvalFrameEx (ceval.c:4057)
  ==8100==by 0x5A1969: function_call.70433 (ceval.c:3439)
  ==8100==by 0x4DCF0B: method_call.65011 (abstract.c:2064)
  ==8100==by 0x56BA13: slot_tp_init.6802 (abstract.c:2064)
  ==8100==by 0x4C9856: type_call.6601 (typeobject.c:754)
  ==8100==by 0x4B42E5: PyEval_EvalFrameEx (abstract.c:2064)
  ==8100==by 0x4B3CA4: PyEval_EvalFrameEx (ceval.c:4157)
  ==8100==by 0x5A1969: function_call.70433 (ceval.c:3439)
  ==8100==by 0x4DCF0B: method_call.65011 (abstract.c:2064)
  ==8100==by 0x56BA13: slot_tp_init.6802 (abstract.c:2064)
  ==8100==by 0x4C9856: type_call.6601 (typeobject.c:754)
  ==8100==by 0x581889: PyObject_Call (abstract.c:2064)
  ==8100==by 0x4B19F3: PyEval_EvalFrameEx (ceval.c:4384)
  ==8100==by 0x5A1046: PyEval_EvalCodeEx (ceval.c:3439)
  ==8100==by 0x4B4401: PyEval_EvalFrameEx (ceval.c:4167)
  ==8100==by 0x5A1969: function_call.70433 (ceval.c:3439)
  ==8100==by 0x581889: PyObject_Call (abstract.c:2064)
  ==8100==by 0x4B19F3: PyEval_EvalFrameEx (ceval.c:4384)
  ==8100==by 0x5A1969: function_call.70433 (ceval.c:3439)
  ==8100==by 0x4DCF0B: method_call.65011 (abstract.c:2064)
  ==8100==by 0x56B5D6: slot_tp_call.6815 (abstract.c:2064)
  ==8100==by 0x4B42E5: PyEval_EvalFrameEx (abstract.c:2064)
  ==8100==by 0x4B3CA4: PyEval_EvalFrameEx (ceval.c:4157)
  ==8100==  Address 0x19df7020 is 64 bytes inside a block of size 72 free'd
  ==8100==at 0x4C2B60C: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==8100==by 0x7037AB2: _pygi_argument_to_object (in 
/usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so)
  ==8100==by 0x7037D7F: _pygi_argument_to_object (in 
/usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so)
  ==8100==by 0x703A43D: _pygi_closure_handle (in 
/usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so)
  ==8100==by 0x816C8CA: ffi_closure_unix64_inner (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x816CC43: ffi_closure_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x816CADB: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x816C40B: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x74BAE24: g_cclosure_marshal_generic_va (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3800.1)
  ==8100==by 0x74BA3B6: ??? (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3800.1)
  ==8100==by 0x74D2E81: g_signal_emit_valist (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3800.1)
  ==8100==by 0x74D4011: g_signal_emit_by_name (in 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3800.1)
  ==8100==by 0x7E9EE46: ??? (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3800.1)
  ==8100==by 0x7EC0B10: ??? (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3800.1)
  ==8100==by 0x77433B5: g_main_context_dispatch (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1)
  ==8100==by 0x7743707: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1)
  ==8100==by 0x77437AB: g_main_context_iteration (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3800.1)
  ==8100==by 0x7E9DA8B: g_application_run (in 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3800.1)
  ==8100==by 0x816CADB: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x816C40B: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.1)
  ==8100==by 0x7280CC8: g_callable_info_invoke (in 
/usr/lib/libgirepository-1.0.so.1.0.0)
  ==8100==by 0x7282006: g_function_info_invoke (in 
/usr/lib/libgirepository-1.0.so.1.0.0)
  ==8100==by 0x703D546: pygi_callable_info_invoke (in 
/usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so)
  ==8100==by 0x703352D: _callable_info_call (in 
/usr/lib/python3/dist-packages/gi/_gi.cpython-33m-x86_64-linux-gnu.so)
  ==8100==by 0x4B42E5: PyEval_EvalFrameEx (abstract.c:2064)
  ==8100== 
  ==8100== Conditional jump or move depends on uninitialised value(s)
  ==8100==at 0x5A47A7: PyObject_Free (obmalloc.c:987)
  ==8100==by 0x443D7A: xmlparse_ParseFile.45364 (pyexpat.c:865)
  ==8100==   

[Desktop-packages] [Bug 1222053] Re: per-session gsettings overrides

[Ryan Lortie]

Worth noting that it's already possible to add new directories to the
schema search path via GSETTINGS_SCHEMA_DIR.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1222053

Title:
  per-session gsettings overrides

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  There have been several occasions now where Ubuntu GNOME has had to
  patch code, that could in theory instead be handled by per-session
  gsettings overrides. A recent example is the background plugin in
  gnome-settings-daemon (LP: #1219148), this should be loaded under
  unity, gnome-flashback sessions but not gnome-shell session. A per-
  session override would make this possible without any patches to the
  codebase.

  As I understand it the overrides are processed by glib-compile-schemas
  so perhaps we would have to recompile schemas on each login to achieve
  this? Any thoughts on how we can achieve this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1222053/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1196752] Re: Suspend only works once when using upower with logind -- s-shim needs to call /lib/systemd/system-sleep/*

[Ryan Lortie]

No.  I talked about this with Martin today and we both agree that it's
not really worth it for supporting a deprecated API that we will remove
soon anyway.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1196752

Title:
  Suspend only works once when using upower with logind -- s-shim needs
  to call /lib/systemd/system-sleep/*

Status in “systemd” package in Ubuntu:
  Invalid
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “upower” package in Ubuntu:
  Fix Released
Status in “upower” package in Debian:
  Fix Released

Bug description:
  On saucy with upower 0.9.20-1ubuntu2, suspending via UPower (or the KDE 
suspend menu) only works once:
  dbus-send --print-reply --system --dest=org.freedesktop.UPower 
/org/freedesktop/UPower org.freedesktop.UPower.Suspend

  and resuming works the first time. However, calling it again after resume 
returns:
  Sleep has already been requested and is pending

  Sleeping directly via logind works every time:
  dbus-send --print-reply --system --dest=org.freedesktop.login1 
/org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true

  Returning FALSE for the LOGIND_AVAILABLE() case in gboolean
  up_backend_emits_resuming (UpBackend *backend) in src/linux/up-
  backend.c allows suspending multiple times via UPower (or the KDE
  suspend menu). UPower is somehow not getting the resume signal from
  logind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1196752/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()

[Ryan Lortie]

Line 1520 in that file looks like so:

g_error (The mapping function given to g_settings_get_mapped() for key 
 '%s' in schema '%s' returned FALSE when given a NULL value.,
 key, g_settings_schema_get_id (settings-priv-schema));


which is a pretty good indicator of what's probably happening here.

Quoth the docs:

If the mapping function fails for all possible values, one additional
attempt is made: the mapping function is called with a NULL value. If
the mapping function still indicates failure at this point then the
application will be aborted.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webapps-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1206314

Title:
  install-default-webapps-in-launcher.py crashed with signal 5 in
  g_settings_get_mapped()

Status in “webapps-applications” package in Ubuntu:
  Confirmed

Bug description:
  o sitema não emula corretamente travando.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-common 2.4.16+13.10.20130719-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 29 21:29:14 2013
  ExecutablePath: 
/usr/share/session-migration/scripts/install-default-webapps-in-launcher.py
  InstallationDate: Installed on 2013-07-14 (15 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130529)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python 
/usr/share/session-migration/scripts/install-default-webapps-in-launcher.py
  Signal: 5
  SourcePackage: webapps-applications
  StacktraceTop:
   g_settings_get_mapped () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1
   g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1
  Title: install-default-webapps-in-launcher.py crashed with signal 5 in 
g_settings_get_mapped()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1206314] Re: install-default-webapps-in-launcher.py crashed with signal 5 in g_settings_get_mapped()

[Ryan Lortie]

So indeed, the script contains this code:

first_mapping = [True]
def mapping_callback(value, first_mapping):
if not value:
return (True, [])
if first_mapping[0]:
first_mapping[0] = False
return (False, value)
return (True, value)

def get_default_value_for(settings, key):
return settings.get_mapped(UNITY_LAUNCHER_FAVORITE_KEY, mapping_callback, 
first_mapping)


Which looks like it's fine because of:

if not value:
return (True, [])

but for some reason, the python bindings are unable to deal with this.
Running the script gives warnings like so:

** (process:21913): WARNING **: (pygi-
argument.c:903):_pygi_argument_from_object: runtime check failed:
(transfer == GI_TRANSFER_NOTHING)

before crashing with the error from the previous comment.


An easier way of getting the default value of a key (and the one most commonly 
used by other developers) is this pattern:

1) create a GSettings object
2) .delay()
3) .reset('key')
4) .get('key')
5) free the object without calling .apply()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webapps-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1206314

Title:
  install-default-webapps-in-launcher.py crashed with signal 5 in
  g_settings_get_mapped()

Status in “webapps-applications” package in Ubuntu:
  Confirmed

Bug description:
  o sitema não emula corretamente travando.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity-webapps-common 2.4.16+13.10.20130719-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 29 21:29:14 2013
  ExecutablePath: 
/usr/share/session-migration/scripts/install-default-webapps-in-launcher.py
  InstallationDate: Installed on 2013-07-14 (15 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130529)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python 
/usr/share/session-migration/scripts/install-default-webapps-in-launcher.py
  Signal: 5
  SourcePackage: webapps-applications
  StacktraceTop:
   g_settings_get_mapped () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1
   g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1
  Title: install-default-webapps-in-launcher.py crashed with signal 5 in 
g_settings_get_mapped()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1206314/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending

[Ryan Lortie]

hi James,

Unfortunately we handle suspend in a much more ad-hoc way on precise.
There is no logind or systemd-shim through which all suspend requests
are handled.  These changes are therefore not really possible to
backport.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/922968

Title:
  shouldn't queue a second suspend if the machine is already suspending

Status in Gnome Powermanager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project precise series:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” source package in Precise:
  Confirmed
Status in “linux” source package in Precise:
  Invalid

Bug description:
  Reproduce:
  This only triggers when you suspend with (Fn-F4) then quickly close the 
laptop lid. The power settings are setup such that the laptop lid close will 
suspend the laptop as well. So we're getting two suspend events in a row.

  Workaround:
  Either close the lid to suspend and not use Fn-F4. Or suspend using Fn-F4 
then wait a few seconds before closing the lid.

  Version:
  Ubuntu 3.2.0-11.19-generic 3.2.1

  After suspending the computer using Fn-F4, and for an extended period
  of time, I then wake the computer up by opening the lid and pressing
  the 'Fn' key. The computer starts to resume, and I am prompted for my
  password. Then the computer suspends again, and I have to wake it up
  again to resume the computer. This is with the computer charged
  sufficiently, but not plugged into an AC source.

  In addition I've also confirmed that using pm-suspend and resuming by
  pressing 'Fn' will still cause the machine to suspend again after
  resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-11-generic 3.2.0-11.19
  ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
  Uname: Linux 3.2.0-11-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arges  2127 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 46'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:14f1506e,17aa21ce,0012 
HDA:80862805,80860101,0010'
     Controls  : 26
     Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Fri Jan 27 23:00:48 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  MachineType: LENOVO 4177CTO
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic 
root=UUID=0f84abde-0eb0-405f-a8c6-b09dd4c4dae9 ro quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-11-generic N/A
   linux-backports-modules-3.2.0-11-generic  N/A
   linux-firmware1.68
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to precise on 2011-12-21 (37 days ago)
  dmi.bios.date: 07/29/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET63WW (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4177CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4177CTO
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/922968/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 922968] Re: shouldn't queue a second suspend if the machine is already suspending

[Ryan Lortie]

We fixed this issue in saucy by moving responsibility for handling
suspend into systemd-shim and adding a check there to ignore suspend
requests that come in during a very small window after waking up.  From
personal reports, this has solved the issue for everyone who has tried
it.

I'm not totally happy with the solution -- I would prefer if we had one
based on the timestamps of the source of the suspend (ie: clicking a
menu item with the mouse, lid-close events, etc) and were able to
compare that with the time of the suspend itself.  This requires some
changes to logind, though.  This has been discussed with upstream and
we're waiting.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/922968

Title:
  shouldn't queue a second suspend if the machine is already suspending

Status in Gnome Powermanager:
  New
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project precise series:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” source package in Precise:
  Confirmed
Status in “linux” source package in Precise:
  Invalid

Bug description:
  Reproduce:
  This only triggers when you suspend with (Fn-F4) then quickly close the 
laptop lid. The power settings are setup such that the laptop lid close will 
suspend the laptop as well. So we're getting two suspend events in a row.

  Workaround:
  Either close the lid to suspend and not use Fn-F4. Or suspend using Fn-F4 
then wait a few seconds before closing the lid.

  Version:
  Ubuntu 3.2.0-11.19-generic 3.2.1

  After suspending the computer using Fn-F4, and for an extended period
  of time, I then wake the computer up by opening the lid and pressing
  the 'Fn' key. The computer starts to resume, and I am prompted for my
  password. Then the computer suspends again, and I have to wake it up
  again to resume the computer. This is with the computer charged
  sufficiently, but not plugged into an AC source.

  In addition I've also confirmed that using pm-suspend and resuming by
  pressing 'Fn' will still cause the machine to suspend again after
  resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-11-generic 3.2.0-11.19
  ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
  Uname: Linux 3.2.0-11-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arges  2127 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 46'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:14f1506e,17aa21ce,0012 
HDA:80862805,80860101,0010'
     Controls  : 26
     Simple ctrls  : 8
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
     Mixer name : 'ThinkPad EC (unknown)'
     Components : ''
     Controls  : 1
     Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Fri Jan 27 23:00:48 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  MachineType: LENOVO 4177CTO
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-11-generic 
root=UUID=0f84abde-0eb0-405f-a8c6-b09dd4c4dae9 ro quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-11-generic N/A
   linux-backports-modules-3.2.0-11-generic  N/A
   linux-firmware1.68
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: Upgraded to precise on 2011-12-21 (37 days ago)
  dmi.bios.date: 07/29/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET63WW (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4177CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4177CTO
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1159036] Re: gedit 3.7 doesn't display application menu

[Ryan Lortie]

*** This bug is a duplicate of bug 999827 ***
https://bugs.launchpad.net/bugs/999827

This is an old bug in the appmenu indicator.  gedit gives an appmenu via
GMenu but also has oldschool GtkMenu menus for the menubar.  Unity can't
deal with both of these at the same time.

** This bug has been marked a duplicate of bug 999827
   App menus aren't shown in the panel if the app is also exporting menus via 
dbusmenu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1159036

Title:
  gedit 3.7 doesn't display application menu

Status in “gedit” package in Ubuntu:
  New

Bug description:
  Starting with version 3.7.3, gedit has an application menu with menu
  items such as New Window, Preferences, About and Quit.  Unfortunately
  this menu does not display under Unity, which makes gedit nearly
  unusable.  You can see this if you install gedit 3.7 on Raring from
  the GNOME 3 PPA (https://launchpad.net/~gnome3-team/+archive/gnome3),
  or build it yourself on Raring (you'll need components from the GNOME
  3 PPA in order to do so).

  Unity *does* display the application menu in other applications
  including Nautilus and Epiphany.  Perhaps it's failing to display the
  menu in gedit because gedit has other top-level menus as well (unlike
  those other applications).  Or perhaps there's a deeper explanation.

  Also see some discussion (but no fix) at
  https://bugzilla.gnome.org/show_bug.cgi?id=696425 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1159036/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1154370] [NEW] [precise SRU] crash due to improper handling of / in GSettings

[Ryan Lortie]

Public bug reported:

GSettings in GLib 2.32.3 has a bug where the changed signal is emitted
for child settings objects as if they were keys ending with /.

That was fixed upstream and merged into the glib-2-32 stable branch
here:
https://git.gnome.org/browse/glib/commit/?h=glib-2-32id=e6f659a898595ba944bd02f0509b14694d1c26e7

GLib 2.32.4 was since released and contains the fix.


This fix is needed because there exists software (muffin) that contains
code along these lines:


void
change_event_handler (GSettings *settings, const gchar *key, gpointer user_data)
{
  ...
  g_settings_get_value (settings, key);
  ...
}

and it's invalid to pass a key containing / to g_settings_get_value()
(causing crashes).

This only happens when entire paths are reset (such as when running
'dconf update').  That makes the issue relatively rare but it's
affecting corporate deployments (Google, specifically).

We should either do an SRU with just the patch linked to above to
(ideally) QA and SRU the entire GLib 2.32.4 release to precise.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubuntu = glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
Milestone: None = precise-updates

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1154370

Title:
  [precise SRU] crash due to improper handling of / in GSettings

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  GSettings in GLib 2.32.3 has a bug where the changed signal is
  emitted for child settings objects as if they were keys ending with
  /.

  That was fixed upstream and merged into the glib-2-32 stable branch
  here:
  
https://git.gnome.org/browse/glib/commit/?h=glib-2-32id=e6f659a898595ba944bd02f0509b14694d1c26e7

  GLib 2.32.4 was since released and contains the fix.


  This fix is needed because there exists software (muffin) that
  contains code along these lines:

  
  void
  change_event_handler (GSettings *settings, const gchar *key, gpointer 
user_data)
  {
...
g_settings_get_value (settings, key);
...
  }

  and it's invalid to pass a key containing / to
  g_settings_get_value() (causing crashes).

  This only happens when entire paths are reset (such as when running
  'dconf update').  That makes the issue relatively rare but it's
  affecting corporate deployments (Google, specifically).

  We should either do an SRU with just the patch linked to above to
  (ideally) QA and SRU the entire GLib 2.32.4 release to precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code

[Ryan Lortie]

Note also that this depends on the systemd-shim MIR being approved: bug
1153633

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1153567

Title:
  [FFE] Use systemd-services rather than ubuntu-system-service
  systemdcompatibility code

Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Triaged
Status in “policykit-desktop-privileges” package in Ubuntu:
  Triaged
Status in “ubuntu-system-service” package in Ubuntu:
  Triaged

Bug description:
  The topic was discussed at UDS and work recorded in that spec:
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-ubuntu-system-services

  The transition is ready and tested in the desktop team ppa at the
  moment, it impacts on those sources:

   * systemd 
  - needs systemd-services MIRed, that's bug #1152187

   * gnome-settings-daemon and gnome-control-center:
  -  basically drop the revert-git-commits patches we carry at the moment 
(those patches make g-s-d ships a custom helper code and g-c-c uses that 
interface)

  *  indicator-datetime
  - use the systemd interface
  https://code.launchpad.net/~desrt/indicator-datetime/timedated/+merge/151560

  * ubuntu-system-service
  - drops the code that was added to emulate some of the systemd interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1153567] Re: [FFE] Use systemd-services rather than ubuntu-system-service systemdcompatibility code

[Ryan Lortie]

You need to ensure that you manually install the PPA versions of all 5
components listed above (since at least one of them is out of date in
the PPA at the time of writing).  Also need to install systemd-shim
(which will eventually make it into at least a recommends of ubuntu-
desktop at some point, I assume).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1153567

Title:
  [FFE] Use systemd-services rather than ubuntu-system-service
  systemdcompatibility code

Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-datetime” package in Ubuntu:
  Triaged
Status in “policykit-desktop-privileges” package in Ubuntu:
  Triaged
Status in “ubuntu-system-service” package in Ubuntu:
  Triaged

Bug description:
  The topic was discussed at UDS and work recorded in that spec:
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-ubuntu-system-services

  The transition is ready and tested in the desktop team ppa at the
  moment, it impacts on those sources:

   * systemd 
  - needs systemd-services MIRed, that's bug #1152187

   * gnome-settings-daemon and gnome-control-center:
  -  basically drop the revert-git-commits patches we carry at the moment 
(those patches make g-s-d ships a custom helper code and g-c-c uses that 
interface)

  *  indicator-datetime
  - use the systemd interface
  https://code.launchpad.net/~desrt/indicator-datetime/timedated/+merge/151560

  * ubuntu-system-service
  - drops the code that was added to emulate some of the systemd interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1153567/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1086868] Re: No global menu in Plasma (KDE) session in Raring

[Ryan Lortie]

The D-Bus protocol used to communicate the menus to the shell has
changed.  Some gtk3 applications (not GIMP) were the first to be
affected by this change, followed by Libreoffice.  The rest of the Gtk
applications will follow either this cycle or next.  The plan is to
completely eliminate the old protocol.

The proper fix for this is to update the menu widget in the plasma
desktop to speak the new protocol (GMenuModel).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1086868

Title:
  No global menu in Plasma (KDE) session in Raring

Status in “libreoffice” package in Ubuntu:
  Won't Fix

Bug description:
  Under a Plasma (KDE) session in raring there is no global menu
  (plasma-widget-menubar).  This does work in 12.10, so it's a
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost

[Ryan Lortie]

Ready to go, imho.

Marga: one tiny point that I missed the first time around.  GObject
signals are nominally written like signal-name rather than
signal_name.  Your patch is fine as-is -- it's mostly a matter of
style in this case.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950

Title:
  gnome-settings-daemon dconf to gconf plugin causes settings to be lost

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  This was tested in a fresh installed precise machine, with the
  addition of dconf and a particular dconf configuration.

  Settings set in gconf backend get overwritten when running 'dconf
  update'.  This can be tested by changing any value in gconf to
  something different than the default:

  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  Then editing some file under /etc/dconf and running dconf update:

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  click

  After talking about this with Ryan Lortie, he suggested disabling the
  gnome-settings-daemon plugin:

  $ gsettings set org.gnome.settings-daemon.plugins.gconf active false
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  It looks like the gconf plugin is overwriting all the settings with
  the defaults, thus losing anything the user had customized.  It's
  quite likely that a number of other bugs Compiz loses my settings
  are actually caused by this plugin.

  Also, as instructed by Ryan, I tried removing
  /usr/share/GConf/gsettings/wm-schemas.convert and re-enabling the
  plugin, and then it doesn't override any values that are related to
  the window manager but it does override the one in the example:

  $ gsettings reset org.gnome.settings-daemon.plugins.gconf active
  $ gsettings get org.gnome.settings-daemon.plugins.gconf active
  true
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  So, focus_mode didn't get overwritten while event_sounds did.

  One possible solution is to remove the wm-schemas so that compiz
  settings don't get lost.  A better (but probably harder) solution
  would be to fix the plugin so that it doesn't overwrite what the user
  sets.  Maybe just remove the schemas that are being modified and
  stored in gconf for Precise.

  I found out that to reproduce in a fresh installed precise machine, I
  had to set up some dconf files, then reboot, and then I could
  reproduce consistently as explained here.  I'm attaching a bunch of
  dconf files.  After unpacking, you need to run dconf update once to
  generate the db and then reboot.  After that it should be
  reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost

[Ryan Lortie]

Functionally, the patch looks pretty good to me.  Thanks for the
attention to detail with respect to the signal disconnection.

One small detail is that the function you introduce should be marked
'static' (since it is not used outside of the current file).  Otherwise,
everything else looks fine.  A comment about why this function exists is
probably also reasonable since it's non-obvious from just looking at it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950

Title:
  gnome-settings-daemon dconf to gconf plugin causes settings to be lost

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  This was tested in a fresh installed precise machine, with the
  addition of dconf and a particular dconf configuration.

  Settings set in gconf backend get overwritten when running 'dconf
  update'.  This can be tested by changing any value in gconf to
  something different than the default:

  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  Then editing some file under /etc/dconf and running dconf update:

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  click

  After talking about this with Ryan Lortie, he suggested disabling the
  gnome-settings-daemon plugin:

  $ gsettings set org.gnome.settings-daemon.plugins.gconf active false
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  It looks like the gconf plugin is overwriting all the settings with
  the defaults, thus losing anything the user had customized.  It's
  quite likely that a number of other bugs Compiz loses my settings
  are actually caused by this plugin.

  Also, as instructed by Ryan, I tried removing
  /usr/share/GConf/gsettings/wm-schemas.convert and re-enabling the
  plugin, and then it doesn't override any values that are related to
  the window manager but it does override the one in the example:

  $ gsettings reset org.gnome.settings-daemon.plugins.gconf active
  $ gsettings get org.gnome.settings-daemon.plugins.gconf active
  true
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  So, focus_mode didn't get overwritten while event_sounds did.

  One possible solution is to remove the wm-schemas so that compiz
  settings don't get lost.  A better (but probably harder) solution
  would be to fix the plugin so that it doesn't overwrite what the user
  sets.  Maybe just remove the schemas that are being modified and
  stored in gconf for Precise.

  I found out that to reproduce in a fresh installed precise machine, I
  had to set up some dconf files, then reboot, and then I could
  reproduce consistently as explained here.  I'm attaching a bunch of
  dconf files.  After unpacking, you need to run dconf update once to
  generate the db and then reboot.  After that it should be
  reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1042070] Re: soffice.bin crashed with SIGSEGV in g_menu_exporter_menu_prepare()

[Ryan Lortie]

This is at least partially caused by an upstream bug in GLib.

** Bug watch added: GNOME Bug Tracker #685995
   https://bugzilla.gnome.org/show_bug.cgi?id=685995

** Also affects: df-libreoffice via
   https://bugzilla.gnome.org/show_bug.cgi?id=685995
   Importance: Unknown
   Status: Unknown

** Project changed: df-libreoffice = glib

** Bug watch added: GNOME Bug Tracker #687089
   https://bugzilla.gnome.org/show_bug.cgi?id=687089

** Changed in: glib
 Remote watch: GNOME Bug Tracker #685995 = GNOME Bug Tracker #687089

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1042070

Title:
  soffice.bin crashed with SIGSEGV in g_menu_exporter_menu_prepare()

Status in The G Library - GLib:
  Unknown
Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  ???

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.0~rc4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Date: Mon Aug 27 11:37:22 2012
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=6
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fa4e4855501:cmpq   $0x0,0x20(%rdi)
   PC (0x7fa4e4855501) ok
   source $0x0 ok
   destination 0x20(%rdi) (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: soffice.bin crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1042070/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost

[Ryan Lortie]

The issue specifically:

'dconf update' emits a signal that says everything has changed

Meanwhile, we have the configuration migration stuff watching for
changes and assuming that if there was a change in dconf it means that
we should sync it up to gconf.

The trouble comes that everything has changed actually only means
everything has *potentially* changed.

One way we can work around this is the change-event signal on
GSettings.  It allows two things:

1) We can find out the difference between everything changed and one
thing changed.

2) We can return TRUE here to stop the signal from going further.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950

Title:
  gnome-settings-daemon dconf to gconf plugin causes settings to be lost

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  This was tested in a fresh installed precise machine, with the
  addition of dconf and a particular dconf configuration.

  Settings set in gconf backend get overwritten when running 'dconf
  update'.  This can be tested by changing any value in gconf to
  something different than the default:

  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  Then editing some file under /etc/dconf and running dconf update:

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  click

  After talking about this with Ryan Lortie, he suggested disabling the
  gnome-settings-daemon plugin:

  $ gsettings set org.gnome.settings-daemon.plugins.gconf active false
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  false
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  It looks like the gconf plugin is overwriting all the settings with
  the defaults, thus losing anything the user had customized.  It's
  quite likely that a number of other bugs Compiz loses my settings
  are actually caused by this plugin.

  Also, as instructed by Ryan, I tried removing
  /usr/share/GConf/gsettings/wm-schemas.convert and re-enabling the
  plugin, and then it doesn't override any values that are related to
  the window manager but it does override the one in the example:

  $ gsettings reset org.gnome.settings-daemon.plugins.gconf active
  $ gsettings get org.gnome.settings-daemon.plugins.gconf active
  true
  $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
  $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy

  $ sudo vi /etc/dconf/db/site.d/screensaver 
  $ sudo dconf update
  $ gconftool --get /desktop/gnome/sound/event_sounds
  true
  $ gconftool --get /apps/metacity/general/focus_mode
  sloppy

  So, focus_mode didn't get overwritten while event_sounds did.

  One possible solution is to remove the wm-schemas so that compiz
  settings don't get lost.  A better (but probably harder) solution
  would be to fix the plugin so that it doesn't overwrite what the user
  sets.  Maybe just remove the schemas that are being modified and
  stored in gconf for Precise.

  I found out that to reproduce in a fresh installed precise machine, I
  had to set up some dconf files, then reboot, and then I could
  reproduce consistently as explained here.  I'm attaching a bunch of
  dconf files.  After unpacking, you need to run dconf update once to
  generate the db and then reboot.  After that it should be
  reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1070905] [NEW] a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema

[Ryan Lortie]

Public bug reported:

We have a patch in the control-centre that depends on a schema that may
not be installed (if overlay scrollbars have been removed).

This causes the entire control centre to crash when trying to open the
a11y panel if overlay scrollbars have been uninstalled (which is
something particularly likely to be done by a user requiring a11y
features, since overlay scrollbars are known to cause issues for these
users).

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1070905

Title:
  a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar
  schema

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  We have a patch in the control-centre that depends on a schema that
  may not be installed (if overlay scrollbars have been removed).

  This causes the entire control centre to crash when trying to open the
  a11y panel if overlay scrollbars have been uninstalled (which is
  something particularly likely to be done by a user requiring a11y
  features, since overlay scrollbars are known to cause issues for these
  users).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1070905] Re: a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar schema

[Ryan Lortie]

hi Will,

Two notes:

1) you don't need to set this variable to NULL -- it will already be
NULL by virtue of being in a GObject priv structure.

2) the code further down calls g_settings_set() on the object without
first checking if it will be NULL, so in the case that you don't do
g_settings_new() there will be a crash (or probably at least critical)
there.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1070905

Title:
  a11y panel calls g_settings_new() on (uninstalled) overlay scrollbar
  schema

Status in “gnome-control-center” package in Ubuntu:
  Triaged

Bug description:
  We have a patch in the control-centre that depends on a schema that
  may not be installed (if overlay scrollbars have been removed).

  This causes the entire control centre to crash when trying to open the
  a11y panel if overlay scrollbars have been uninstalled (which is
  something particularly likely to be done by a user requiring a11y
  features, since overlay scrollbars are known to cause issues for these
  users).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1070905/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running

[Ryan Lortie]

I can confirm this bug locally.

Looking at the D-Bus log, I see:

method call sender=:1.41 - dest=org.ayatana.bamf serial=480 
path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; 
member=Xprop
   string _GTK_UNIQUE_BUS_NAME
method return sender=:1.30 - dest=:1.41 reply_serial=480
   string 

...

method call sender=:1.41 - dest=org.ayatana.bamf serial=461 
path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; 
member=Xprop
   string _GTK_UNIQUE_BUS_NAME
method return sender=:1.30 - dest=:1.41 reply_serial=461
   string 

...

method call sender=:1.38 - dest=org.ayatana.bamf serial=524 
path=/org/ayatana/bamf/window60817505; interface=org.ayatana.bamf.window; 
member=Xprop
   string _GTK_UNIQUE_BUS_NAME
method return sender=:1.30 - dest=:1.38 reply_serial=524
   string 


in essence: bamf is reporting that the _GTK_UNIQUE_BUS_NAME property is
not set on the window when it is first presented.

This means that either

  a) libreoffice is not setting the property before mapping the window 
(libreoffice bug)
  b) bamf is telling lies (bamf bug)

Pretty sure we can rule out the chances of this being in any other
component...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1064962

Title:
  Global menubar items do not work when opening a document directly from
  nautilus with no LibreOffice instance running

Status in BAMF Application Matching Framework:
  Confirmed
Status in The Application Menu:
  Confirmed
Status in “bamf” package in Ubuntu:
  Confirmed
Status in “indicator-appmenu” package in Ubuntu:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “bamf” source package in Quantal:
  Confirmed
Status in “indicator-appmenu” source package in Quantal:
  Confirmed
Status in “libreoffice” source package in Quantal:
  Invalid

Bug description:
  1) Have no instance of LibreOffice running
  2) open a document by double-clicking it in nautilus
  3) new window has no menu
  4) unfocusing/refocusing (e.g. by pressing F7 to bring up the spelling 
dialog) makes the menu appear

  WORKAROUND: minimize and restore the LibreOffice window

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-gtk 1:3.6.2~rc2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 10 11:48:20 2012
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago)

  original description:
  In writer, none of the menubar items appear to work.  Example:

  * Open new document in Writer
  * Type some text and highlight it
  * Try Edit-Cut
   Nothing happens
  * Try Format-Change chase-UPPERCASE
   Nothing happens!
  workaround: restart your session after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1064962/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running

[Ryan Lortie]

The bamf code is a bit hairy, but basically it is synchronously calling
XGetWindowProperty here, so I doubt that it's getting it wrong.  Looks
like a libreoffice issue...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1064962

Title:
  Global menubar items do not work when opening a document directly from
  nautilus with no LibreOffice instance running

Status in BAMF Application Matching Framework:
  Confirmed
Status in The Application Menu:
  Confirmed
Status in “bamf” package in Ubuntu:
  Confirmed
Status in “indicator-appmenu” package in Ubuntu:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “bamf” source package in Quantal:
  Confirmed
Status in “indicator-appmenu” source package in Quantal:
  Confirmed
Status in “libreoffice” source package in Quantal:
  Invalid

Bug description:
  1) Have no instance of LibreOffice running
  2) open a document by double-clicking it in nautilus
  3) new window has no menu
  4) unfocusing/refocusing (e.g. by pressing F7 to bring up the spelling 
dialog) makes the menu appear

  WORKAROUND: minimize and restore the LibreOffice window

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-gtk 1:3.6.2~rc2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 10 11:48:20 2012
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago)

  original description:
  In writer, none of the menubar items appear to work.  Example:

  * Open new document in Writer
  * Type some text and highlight it
  * Try Edit-Cut
   Nothing happens
  * Try Format-Change chase-UPPERCASE
   Nothing happens!
  workaround: restart your session after update

To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1064962/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1044322] Re: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished()

[Ryan Lortie]

Fixed upstream here:
http://git.gnome.org/browse/glib/commit/?id=3766b7b5cd0f22d2773c7efc8b52fc2f214d0372

Distro backport coming soon...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1044322

Title:
  indicator-messages-service crashed with assert in
  g_menu_exporter_name_vanished()

Status in The G Library - GLib:
  New
Status in “glib2.0” package in Ubuntu:
  Confirmed

Bug description:
  no details available

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: indicator-messages 12.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Fri Aug 31 12:56:04 2012
  ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120213)
  ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
  Signal: 6
  SourcePackage: indicator-messages
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: indicator-messages-service crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1044322/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058250] Re: conditionalise empathy u-o-a dependency

[Ryan Lortie]

This is empathy 3.5.92-0ubuntu2 in Q.

** Changed in: empathy (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1058250

Title:
  conditionalise empathy u-o-a dependency

Status in “empathy” package in Ubuntu:
  New

Bug description:
  Empathy currently has a hard dependency on ubuntu-online-accounts.

  ubuntu-online-accounts is currently not working.

  A workaround is to directly run empathy-accounts from the commandline,
  but this is hardly discoverable.

  Ideally, we should only have this patch butchery enabled when running
  under Unity and disabled otherwise (ie: you get the normal Empathy
  accounts dialog).

  Also: Empathy (via ubuntu-online-accounts) currently hard-depends on
  libqt, which is just a little bit odd...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058250] [NEW] conditionalise empathy u-o-a dependency

[Ryan Lortie]

Public bug reported:

Empathy currently has a hard dependency on ubuntu-online-accounts.

ubuntu-online-accounts is currently not working.

A workaround is to directly run empathy-accounts from the commandline,
but this is hardly discoverable.

Ideally, we should only have this patch butchery enabled when running
under Unity and disabled otherwise (ie: you get the normal Empathy
accounts dialog).

Also: Empathy (via ubuntu-online-accounts) currently hard-depends on
libqt, which is just a little bit odd...

** Affects: empathy (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1058250

Title:
  conditionalise empathy u-o-a dependency

Status in “empathy” package in Ubuntu:
  New

Bug description:
  Empathy currently has a hard dependency on ubuntu-online-accounts.

  ubuntu-online-accounts is currently not working.

  A workaround is to directly run empathy-accounts from the commandline,
  but this is hardly discoverable.

  Ideally, we should only have this patch butchery enabled when running
  under Unity and disabled otherwise (ie: you get the normal Empathy
  accounts dialog).

  Also: Empathy (via ubuntu-online-accounts) currently hard-depends on
  libqt, which is just a little bit odd...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1058250/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1045372] Re: libreoffice unity menu bars greyed out after opening any dialog or switching window

[Ryan Lortie]

A bit more info on this: the bug is caused by the gtk_menu_detach() call
in the cloaking code in libindicator.  The menu gets detached from its
GtkMenuItem, which breaks the GtkModelMenu logic (specifically: it
separates it from the action group so all actions disappear, disabling
the items).  The decloak code doesn't reverse this.

We could workaround it in indicator-appmenu by associating the actions
directly with each submenu but I think we should probably fix this in
libindicator instead.  The cloak logic is pretty suspicious

** Package changed: libreoffice (Ubuntu) = libindicator (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1045372

Title:
  libreoffice unity menu bars greyed out after opening any dialog or
  switching window

Status in “libindicator” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release:  Ubuntu 12.10 Quantal Quetzal beta1
  Package version: libreoffice-gtk
  Package version: 1:3.6.1~rc2-1ubuntu3

  Behavior: Triggering an action from the menu, i.e. opening a file ,
  turns the menu into disabled state. This happens randomly and
  sometimes also without any action triggers.

  This is a new issue we have discovered in the latest versions of
  Unity/Gtk+. This wrong behavior is not present in precise pangolin and
  Quantal Alpha 3. Can someone please confirm if this is an issue in
  Unity/Gtk+?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1045372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1045361] Re: Accelerators are not displayed

[Ryan Lortie]

Confirmed known issue.  Working on it...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1045361

Title:
  Accelerators are not displayed

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Ubuntu Release:  Ubuntu 12.10 Quantal Quetzal beta1
  Package version: libreoffice-gtk
  Package version: 1:3.6.1~rc2-1ubuntu3
  Expected behavior: LO accelerators should be available in Unity menu.
  Actual behavior: Accelerators are not displayed in Unity but actions are 
launched properly when triggered.

  This seems to due to an issue in Unity/GTK. AFAIK it has been confirmed by 
@desrt.
  I'm not aware of an issue in launchpad/unity to link to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045361/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1045372] Re: Menu bar in Unity is disabled

[Ryan Lortie]

I think this is more likely to be a bug in libreoffice since we have
quite a lot of apps that are working properly with Unity/Gtk in Q and
the libreoffice code is new.

I welcome a small testcase that demonstrates the issue.  Otherwise we're
going to have to go digging through some rather large D-Bus logs to find
the truth

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1045372

Title:
  Menu bar in Unity is disabled

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Ubuntu Release:  Ubuntu 12.10 Quantal Quetzal beta1
  Package version: libreoffice-gtk
  Package version: 1:3.6.1~rc2-1ubuntu3

  Behavior: Triggering an action from the menu, i.e. opening a file ,
  turns the menu into disabled state. This happens randomly and
  sometimes also without any action triggers.

  This is a new issue we have discovered in the latest versions of
  Unity/Gtk+. This wrong behavior is not present in precise pangolin and
  Quantal Alpha 3. Can someone please confirm if this is an issue in
  Unity/Gtk+?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1045372] Re: Menu bar in Unity is disabled

[Ryan Lortie]

I've tried to reproduce this bug and for me it's not happening as
described.

What does happen, however, with 100% reliability, is that the actions
are disabled when switching away from the window and back to it again.
In the case of triggering actions like Open or About this would
indeed cause the foreground window to be changed (to the open or about
dialog).  This is probably a unity-panel-service bug (probably in the
appmenu indicator).

For me, the bug does not happen with other actions like copy/paste that
do not display new windows

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1045372

Title:
  Menu bar in Unity is disabled

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Release:  Ubuntu 12.10 Quantal Quetzal beta1
  Package version: libreoffice-gtk
  Package version: 1:3.6.1~rc2-1ubuntu3

  Behavior: Triggering an action from the menu, i.e. opening a file ,
  turns the menu into disabled state. This happens randomly and
  sometimes also without any action triggers.

  This is a new issue we have discovered in the latest versions of
  Unity/Gtk+. This wrong behavior is not present in precise pangolin and
  Quantal Alpha 3. Can someone please confirm if this is an issue in
  Unity/Gtk+?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045372/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 968268] Re: Cannot permanently add wallpaper to 'Pictures Folder'

[Ryan Lortie]

Seb: we discussed this on IRC a few weeks ago and I mentioned that this
is a known and intended side effect.

Also note that the wallpaper is never really added to the pictures
folder -- just to a cache directory that appears under Pictures Folder
in the UI (which is a bit of a lie, imho).

It is my understanding that the existing behaviour (after the patch) is
the correct behaviour and that if you set an image as your wallpaper
then you should not delete it after.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/968268

Title:
  Cannot permanently add wallpaper to 'Pictures Folder'

Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-control-center” source package in Precise:
  Confirmed

Bug description:
  I successfully added a wallpaper from a subfolder of ~/Pictures to
  the Pictures Folder using the little + button. The wallpaper
  changed, 'org.gnome.desktop.background picture-uri' got set to the
  right file location, but the picture won't show up when opening g-c-c
  again.

  * Expected behavior
  The '-' button is enabled for the currently selected picture to allow user to 
remove this picture

  * Current behavior
  The '-' button is never anabled

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 29 16:11:59 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/968268/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 974938] Re: Process gsettings prevents logging in

[Ryan Lortie]

Looking at these traces I have a hard time beleiving this is a
glib/gsettings problem.  It rather looks like some deadlock between
fork() and the ldap nss module...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/974938

Title:
  Process gsettings prevents logging in

Status in “glib2.0” package in Ubuntu:
  Incomplete

Bug description:
  When I try to login with my newly upgraded Ubuntu 12.04 (development
  branch), nothing happens. It just shows the same empty background that
  LightDm has.

  I have found one solution to get myself logged: If I go to virtual
  console and display what processes I have, there are about six
  processes, and one of them is gsettings. It does not consume any CPU
  resources, and when I kill it (with -3), the login process immediately
  continues and finally gets me logged in. To my knowledge, gsettings
  comes from package libglib2.0-bin and I have version 2.32.0-1ubuntu1
  of it.

  How to reproduce:
  1 Try to log in.
  2 Wait for several minutes to be sure it is stuck
  3 Go to virtual console and killall -3 gsettings
  4 Logging in immediately continues and finally completes in few seconds

  Possible causes:
  1 I'm using LDAP. My user information comes from LDAP-server, and this has 
caused lots of other logging problems, thanks to software developers not 
realizing the fact, that people use stuff like LDAP.
  2 I had some problems when upgrading to 12.04, so that might have screwed 
things up. The funny thing is, that logging in works on my other PC, which has 
almost identical system and package configuration. So if you give me some 
hints, I can try to compare differences between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 974938] Re: Process gsettings prevents logging in

[Ryan Lortie]

Can you get a backtrace of the stuck gsettings process?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/974938

Title:
  Process gsettings prevents logging in

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  When I try to login with my newly upgraded Ubuntu 12.04 (development
  branch), nothing happens. It just shows the same empty background that
  LightDm has.

  I have found one solution to get myself logged: If I go to virtual
  console and display what processes I have, there are about six
  processes, and one of them is gsettings. It does not consume any CPU
  resources, and when I kill it (with -3), the login process immediately
  continues and finally gets me logged in. To my knowledge, gsettings
  comes from package libglib2.0-bin and I have version 2.32.0-1ubuntu1
  of it.

  How to reproduce:
  1 Try to log in.
  2 Wait for several minutes to be sure it is stuck
  3 Go to virtual console and killall -3 gsettings
  4 Logging in immediately continues and finally completes in few seconds

  Possible causes:
  1 I'm using LDAP. My user information comes from LDAP-server, and this has 
caused lots of other logging problems, thanks to software developers not 
realizing the fact, that people use stuff like LDAP.
  2 I had some problems when upgrading to 12.04, so that might have screwed 
things up. The funny thing is, that logging in works on my other PC, which has 
almost identical system and package configuration. So if you give me some 
hints, I can try to compare differences between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 965493] Re: cpu race between nautilus, hud- and unity-service

[Ryan Lortie]

Fix is committed upstream now too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/965493

Title:
  cpu race between nautilus, hud- and unity-service

Status in The Application Menu:
  Invalid
Status in Nautilus:
  New
Status in Unity:
  Invalid
Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “nautilus” package in Ubuntu:
  Fix Released

Bug description:
  Reproducable on guest and -user account. (on pc and laptop)
  Seen on user account first.
  Initial report from guest account (attached .xession-errors and screenshot of 
terminal output).
  Open a terminal and run 'top' to view processes.
  Open Nautilus, right click only on bookmarked folders and open properties.
  Result: nautilus, unity-panel and -hud service race cpu.
  Fan speed increases from ~1100 to ~2000 rpm (viewed on user account with 
conky).

  Viewing properties of folders which aren't bookmarked doesn't result in cpu 
race.
  The behaviour has been introduced since recent unity updates.

  compiz-core:
    Installed: 1:0.9.7.2-0ubuntu1
    Candidate: 1:0.9.7.2-0ubuntu1
    Version table:
   *** 1:0.9.7.2-0ubuntu1 0

  ~$ lspci -nnk | grep -i VGA -A2
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee 
ATI RV710 [Radeon HD 4350] [1002:954f]
   Subsystem: PC Partner Limited Device [174b:174b]
   Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Mar 26 18:33:32 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120204)
  ProcEnviron:
   TERM=xterm
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/965493/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 965493] Re: cpu race between nautilus, hud- and unity-service

[Ryan Lortie]

So the involvement of menus is secondary to the main problem -- nautilus
gets itself stuck in a silly loop reading and re-reading the free space
on the drive.  If a bookmarked directory is also involved then this
results in the bookmarks menu also being updated, thus causing the issue
we see here.

** Changed in: indicator-appmenu
   Status: Triaged = Invalid

** Changed in: unity
   Status: Triaged = Invalid

** Changed in: indicator-appmenu (Ubuntu)
   Status: Triaged = Invalid

** Changed in: unity (Ubuntu)
   Status: Triaged = Invalid

** Bug watch added: GNOME Bug Tracker #673550
   https://bugzilla.gnome.org/show_bug.cgi?id=673550

** Also affects: nautilus via
   https://bugzilla.gnome.org/show_bug.cgi?id=673550
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/965493

Title:
  cpu race between nautilus, hud- and unity-service

Status in The Application Menu:
  Invalid
Status in Nautilus:
  Unknown
Status in Unity:
  Invalid
Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Reproducable on guest and -user account. (on pc and laptop)
  Seen on user account first.
  Initial report from guest account (attached .xession-errors and screenshot of 
terminal output).
  Open a terminal and run 'top' to view processes.
  Open Nautilus, right click only on bookmarked folders and open properties.
  Result: nautilus, unity-panel and -hud service race cpu.
  Fan speed increases from ~1100 to ~2000 rpm (viewed on user account with 
conky).

  Viewing properties of folders which aren't bookmarked doesn't result in cpu 
race.
  The behaviour has been introduced since recent unity updates.

  compiz-core:
    Installed: 1:0.9.7.2-0ubuntu1
    Candidate: 1:0.9.7.2-0ubuntu1
    Version table:
   *** 1:0.9.7.2-0ubuntu1 0

  ~$ lspci -nnk | grep -i VGA -A2
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee 
ATI RV710 [Radeon HD 4350] [1002:954f]
   Subsystem: PC Partner Limited Device [174b:174b]
   Kernel driver in use: radeon

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Mar 26 18:33:32 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120204)
  ProcEnviron:
   TERM=xterm
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/965493/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 797188] Re: Call GTK functions without gdk lock

[Ryan Lortie]

This is definitely not a Gtk bug.

** Package changed: gtk+3.0 (Ubuntu) = ubuntu

** Changed in: ubuntu
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/797188

Title:
  Call GTK functions without gdk lock

Status in Application menu module for GTK+:
  New
Status in Ubuntu:
  Invalid

Bug description:
  There ar ecalls to GTK functions without a gdk lock, which cause
  random crashes on mullti-threaded applications.

  The one that we hit is the call to 
dsubmenu_gtk_parse_menu_structure 
find_menu_bar
...
rebuild_window_items
do_rebuild
glib stuff

  It is because is called vi g_timeout_add inside rebuild, which doesn't deal 
with gdk lock.
  It should call gdk_threads_add_timeout instead. 

  We found the bug running on Linux Mint.

  As a work around we setenv UBUNTU_MENUPROXY to nothing. 
  Other iseas?

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-gtk/+bug/797188/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 922114] Re: unity hud doesn't search the currently selected applications menus but those of the indicators

[Ryan Lortie]

*** This bug is a duplicate of bug 921231 ***
https://bugs.launchpad.net/bugs/921231

** This bug is no longer a duplicate of bug 932435
   HUD - HUD offers search results from app indicators more often than from 
currently focused application
** This bug has been marked a duplicate of bug 921231
   XUL Applications don't show up in HUD

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/922114

Title:
  unity hud doesn't search the currently selected applications menus but
  those of the indicators

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  What I have noticed is when I hit Alt to bring up the HUD and start
  searching for something it seems to be showing me options from the
  bluetooth indicator instead of whatever application I am currently
  interacting with. I'm not sure if this is a symptom or a different bug
  but if I close the HUD and try and just interact with the applications
  menus they no longer appear. To get the menus back you need to restart
  the application. I've seen this with empathy, gnome-terminal and
  firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+10ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,mousepoll,place,resize,regex,grid,vpswitch,imgpng,gnomecompat,snap,move,wall,session,animation,fade,expo,workarounds,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Thu Jan 26 09:43:40 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   ATI Technologies Inc Juniper XT [AMD Radeon HD 6000 Series] [1002:68ba] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03fe]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120125)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-10-generic 
root=UUID=11c0a87a-d237-4636-9c9c-f4aa22cdc8b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1902
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Crosshair IV Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1902:bd02/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901-1ubuntu3
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/922114/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 949277] Re: unity should not use dconf to store the average background colour

[Ryan Lortie]

** Changed in: unity (Ubuntu)
   Status: Opinion = New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/949277

Title:
  unity should not use dconf to store the average background colour

Status in “unity” package in Ubuntu:
  New

Bug description:
  Unity writes the 'average-bg-color' key in dconf whenever the
  background changes and also on login.  dconf is not an IPC mechanism
  nor is it a good place for transient state information and
  particularly the write on login leads to increased boot time (because
  the dconf-service must be started).

  Please find another way of dealing with this.  A property on the root
  window might make sense.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/949277/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 923171] Re: software-center crashed with AttributeError in popup(): 'Menu' object has no attribute 'popup_for_device'

[Ryan Lortie]

Likely caused by: https://bugzilla.gnome.org/show_bug.cgi?id=657385

** Bug watch added: GNOME Bug Tracker #657385
   https://bugzilla.gnome.org/show_bug.cgi?id=657385

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/923171

Title:
  software-center crashed with AttributeError in popup(): 'Menu' object
  has no attribute 'popup_for_device'

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Ubuntu 12.04 Precise Development Branch x64
  Software-center 5.1.7
  Wouldn't let me load software by source.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.7
  ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
  Uname: Linux 3.2.0-11-generic x86_64
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jan 28 14:26:19 2012
  ExecutablePath: /usr/share/software-center/software-center
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-center']
  SourcePackage: software-center
  Title: software-center crashed with AttributeError in popup(): 'Menu' object 
has no attribute 'popup_for_device'
  UpgradeStatus: Upgraded to precise on 2012-01-27 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/923171/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 923570] [NEW] unattractive UI when there are no proprietary drivers applicable

[Ryan Lortie]

Public bug reported:

The Additional Drivers pane in the control-centre looks really bad
when it's completely empty.

You have these two empty white areas with unknown purpose.  You can drag
a GtkPaned adjustor between the empty white spaces.  This looks really
janky.

There is an Enable button at the bottom that is greyed out and will
always be greyed out.

The text says No proprietary drivers are in use on this system which
seems like a bit of a no-brainer if I came here for the first time.  It
doesn't tell me that none are needed, so I might be left wondering how
to interact with this UI to try to enable some.  It should rather say
something along the lines of No proprietary drivers are required for
your system.

So, in short, get rid of everything except the icon, a new label No
proprietary drivers are required for your system and the help/close
buttons.  Probably the window should also not be resizable in this
state.

** Affects: jockey (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/923570

Title:
  unattractive UI when there are no proprietary drivers applicable

Status in “jockey” package in Ubuntu:
  New

Bug description:
  The Additional Drivers pane in the control-centre looks really bad
  when it's completely empty.

  You have these two empty white areas with unknown purpose.  You can
  drag a GtkPaned adjustor between the empty white spaces.  This looks
  really janky.

  There is an Enable button at the bottom that is greyed out and will
  always be greyed out.

  The text says No proprietary drivers are in use on this system which
  seems like a bit of a no-brainer if I came here for the first time.
  It doesn't tell me that none are needed, so I might be left wondering
  how to interact with this UI to try to enable some.  It should rather
  say something along the lines of No proprietary drivers are required
  for your system.

  So, in short, get rid of everything except the icon, a new label No
  proprietary drivers are required for your system and the help/close
  buttons.  Probably the window should also not be resizable in this
  state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/923570/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 915241] Re: Update menubar patches

[Ryan Lortie]

updated patch

** Patch added: 043_ubuntu_menu_proxy.patch
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/915241/+attachment/2669362/+files/043_ubuntu_menu_proxy.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/915241

Title:
  Update menubar patches

Status in “gtk+2.0” package in Ubuntu:
  In Progress
Status in “gtk+3.0” package in Ubuntu:
  In Progress

Bug description:
  We need to update the menubar patches for gtk2 and 3, in order to fix
  menubar appearing outside unity and the weird 1px menubar shown below
  the titlebar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/915241/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 730183] Re: evince crashed with SIGSEGV in getenv()

[Ryan Lortie]

Is it possible that setenv() is being called from another thread?

This could end up being a huge can of worms -- all of our libraries do
things like calling into gettext() from random arbitrary worker threads
and gettext() calls (thread-unsafe) getenv().

In effect, it's not safe to call setenv() from any program that uses
GLib, which is a bit scary.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/730183

Title:
  evince crashed with SIGSEGV in getenv()

Status in “evince” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: evince

  Description:  Ubuntu Natty (development branch)
  Release:  11.04

  evince:
Installed: 2.32.0-0ubuntu10
Candidate: 2.32.0-0ubuntu10
Version table:
   *** 2.32.0-0ubuntu10 0
  500 http://nl.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
  100 /var/lib/dpkg/status

  I tried opening a DVI file (I didn't even know that evince supports
  DVIs) and it crashed. It was started up from Fileroller, as the DVI is
  inside a ZIP.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: evince 2.32.0-0ubuntu10
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Uname: Linux 2.6.38-5-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar  6 16:02:08 2011
  ExecutablePath: /usr/bin/evince
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcCmdline: evince /home/username/.cache/.fr-ZUBicI/2010\ practice\ 
class/PAexams/exam2010/exam2010Jun.dvi
  ProcCmdline_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic 
root=UUID=a4475d80-6ca3-42f0-81bb-7cb272b51fbf ro i8042.nomux=1 
acpi_apic_instance=0 crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_ZA.utf8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature_: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  SegvAnalysis:
   Segfault happened at: 0xde50e4 getenv+100: cmp(%edi),%ax
   PC (0x00de50e4) ok
   source (%edi) (0x0100) not located in a known VMA region (needed 
readable region)!
   destination %ax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   getenv (name=0x6d6199 URSOR_PATH) at getenv.c:90
   XcursorLibraryPath () from /usr/lib/libXcursor.so.1
   ?? () from /usr/lib/libXcursor.so.1
   XcursorLibraryLoadImages () from /usr/lib/libXcursor.so.1
   XcursorShapeLoadImages () from /usr/lib/libXcursor.so.1
  Title: evince crashed with SIGSEGV in getenv()
  UpgradeStatus: Upgraded to natty on 2011-02-26 (8 days ago)
  UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/730183/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp