date:20130902

** Changed in: gucharmap (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  Gucharmap: Languages List Is Too Narrow

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

Thanks, I'm not part of the release team but I've some questions:

- what's the rational for updating (why do we need to update this cycle)

- how much testing did you do on compiz/unity?


The fact that some keys got dropped from the schemas and that 
gnome-control-center needs to be updated as well suggest that the update is non 
trivial and has potential to create issues, I would vote for those changes to 
happen next cycle if there is not a really strong reason we need it this cycle 
(and I didn't see one so far)

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  FFe: Update gnome-settings-daemon to 3.8.4

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219711] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1199371, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798893/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798895/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798897/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798898/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798899/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798900/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219711/+attachment/3798901/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1199371

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  nautilus crashed with SIGSEGV in g_slice_alloc()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219741] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1202426, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798991/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798993/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798995/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798996/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798997/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798998/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219741/+attachment/3798999/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1202426

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  nautilus crashed with SIGSEGV in g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1075923] Re: nautilus hangs copying large directories from a samba share

2013-09-02 Thread Claudio

it has to do something with speed. I get this problem very often on my older PC 
(Dual Core 2.6 Ghz).
On my newer PC (Intel i7) I have to start a lot more videos or file transfers 
to get this.

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

Title:
  nautilus hangs copying large directories from a samba share

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1180554] Re: gnome-panel buttons maximice minimizer and close sometimes stop working... ubuntu 13.04

2013-09-02 Thread Mikolaj Mackowiak

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

** This bug has been marked a duplicate of bug 1158267
   Regression: Broken (click-through) window decoration on some maximized 
windows

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

Title:
  gnome-panel buttons maximice minimizer and close sometimes stop
  working... ubuntu 13.04

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1188346] Re: fills $HOME/.cache/gdm/session.log

2013-09-02 Thread xouns

Found the same error in ~/.xsession-errors:
(rhythmbox-metadata:(pid)): GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: 
assertion `timeout == 0 || bus-priv-poll != NULL' failed.
32bit, 13.04

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

Title:
  fills $HOME/.cache/gdm/session.log

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219777] [NEW] [FFe] update to 0.15

Public bug reported:

Shotwell is following the Ubuntu cycles, they got a pre version of their
new 0.15 out just before FF, but we couldn't get it in because our
Ubuntu Online Account patch needs to be updated (Alberto is working on
that)

It would be nice to update to the new version about beta1.

I don't have a list of what changed (they didn't update their NEWS it seems) 
but the git log are on
http://git.yorba.org/cgit.cgi/shotwell/log/

The list of commits seem reasonable to me, and yorba has a good track
record of delivering working software aligned on our schedule

** Affects: shotwell (Ubuntu)
 Importance: Wishlist
 Assignee: Alberto Mardegan (mardy)
 Status: New

** Changed in: shotwell (Ubuntu)
   Importance: Undecided = Wishlist

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

Title:
  [FFe] update to 0.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219777] Re: [FFe] update to 0.15

Hey Alberto, I'm assigning that bug to you since the update is blocked
on the Ubuntu Online Account patch to get updated

** Changed in: shotwell (Ubuntu)
 Assignee: (unassigned) = Alberto Mardegan (mardy)

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

Title:
  [FFe] update to 0.15

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1059449] Re: Set Airplane Mode On, Bluetooth still work properly .

2013-09-02 Thread Ara Pulido

** Changed in: oem-priority
   Status: In Progress = Fix Released

** Changed in: oem-priority/precise
   Status: New = Fix Released

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

Title:
  Set Airplane Mode On, Bluetooth still work properly .

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 22119] Re: [network-admin] Dial out does not work

2013-09-02 Thread Thomas Hotz

** Changed in: gnome-system-tools (Ubuntu)
 Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/22119

Title:
  [network-admin] Dial out does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 22119] Re: [network-admin] Dial out does not work

2013-09-02 Thread Thomas Hotz

I'm sorry that nobody has looked at this bug earlier and could have made
a fixed.

My question is: Who is still effected by this bug? Please use only an
Ubuntu version starting with 12.04 LTS.

Thank you very much for you feedback!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/22119

Title:
  [network-admin] Dial out does not work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 217551] Re: Password prompt freezes system during presence of a drop-down menu [hardy]

2013-09-02 Thread Thomas Hotz

I'm closing this bug due to no response from the reporters. Some have
said it's fix. If anyone is still affected, please comment and we will
reopen the bug again.

** Changed in: gnome-keyring (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: gnome-keyring (Ubuntu)
   Status: Invalid = Fix Released

** Changed in: network-manager-applet (Ubuntu)
   Status: Incomplete = Fix Released

** Changed in: vinagre (Ubuntu)
   Status: Incomplete = Fix Released

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

Title:
  Password prompt freezes system during presence of a drop-down menu
  [hardy]

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219801] Re: [region]: gnome-control-center crashed with signal 5 in g_object_new_valist()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1195481, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799156/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799158/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799159/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799160/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799161/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799162/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219801/+attachment/3799163/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1195481
   [power]: gnome-control-center crashes if indicator-power is not installed in 
Unity

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  [region]: gnome-control-center crashed with signal 5 in
  g_object_new_valist()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219805] [NEW] 13.10 evolution-calendar-factory cevolution-calendar-factory constantly running and using 25% cpu

2013-09-02 Thread philinux

Public bug reported:

evolution-calendar-factory never stops running. Hogs the cpu and is
constantly running at about 25%.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: evolution 3.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Mon Sep  2 13:20:43 2013
InstallationDate: Installed on 2012-09-18 (349 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120918.1)
MarkForUpload: True
SourcePackage: evolution
UpgradeStatus: Upgraded to saucy on 2013-07-02 (61 days ago)
mtime.conffile..etc.xdg.autostart.evolution.alarm.notify.desktop: 
2013-08-17T17:10:39.992681

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


** Tags: amd64 apport-bug saucy

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

Title:
  13.10 evolution-calendar-factory cevolution-calendar-factory
  constantly running and using 25%  cpu

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1214204] Re: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

2013-09-02 Thread Martin Pitt

** Information type changed from Private to Public

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

Title:
  gvfs-afc-volume-monitor crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1214204] Re: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

2013-09-02 Thread Martin Pitt

** Changed in: gvfs (Ubuntu)
   Status: Confirmed = In Progress

** Changed in: gvfs (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  gvfs-afc-volume-monitor crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219818] Re: yelp crashed with SIGSEGV in yelp_uri_get_query()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #960065, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799233/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799235/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799237/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799238/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799239/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799240/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219818/+attachment/3799241/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 960065

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  yelp crashed with SIGSEGV in yelp_uri_get_query()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219805] Re: 13.10 evolution-calendar-factory cevolution-calendar-factory constantly running and using 25% cpu

2013-09-02 Thread philinux

I've identified the cause.

Would you believe it. I was caused by having seconds displayed in the
clock. Unchecking seconds stopped the high cpu activity as evolution-
calendar-factory went to sleep

I'm now interested in the bug fix!

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

Title:
  13.10 evolution-calendar-factory cevolution-calendar-factory
  constantly running and using 25%  cpu

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

2013-09-02 Thread Jeremy Bicha

1. GNOME 3.8 has only been tested with gnome-settings-daemon 3.8 and there's no
guarantee that things work correctly when we mix and match pieces.
2. Since we did the gsettings-desktop-schemas update, there are gsettings keys
that won't actually do anything without the updated gnome-settings-daemon
backend. Even without doing the gnome-control-center 3.8 update, it would be
nice for GNOME users to be able to tweak some of the new settings in
dconf-editor at least.
3. We need to update this cycle because we need to fix bug 1201679 which is a
High priority regression in Unity (GNOME was unaffected).
4. There are numerous other fixes and improvements if you read through the NEWS
file. The update isn't just GNOME dropping Fallback support and we've patched
back in the fallback pieces that Unity currently needs.
5. Tim did a lot of work on this update with the assumption that it could make
it into Saucy. We were delayed several weeks by indicator-keyboard taking
longer to land than expected. I tried to help indicator-keyboard along as well
as I could and complained that the longer the delay, the more difficult it
would be to land gnome-settings-daemon 3.8 by Feature Freeze.

There was one final regression that Tim fixed over the weekend. Ubuntu
GNOME shouldn't be penalized for taking care not to cause regressions
and waiting for Unity work.

I've been running Unity all weekend to make sure that the update didn't
cause any new problems. Many people have installed the GNOME3 Staging
PPA; some of those people use Unity.

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

Title:
FFe: Update gnome-settings-daemon to 3.8.4

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1214204] Re: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

2013-09-02 Thread Martin Pitt

I uploaded gvfs 1.17.90 to saucy which will fix this, but it won't go in
until after the beta freeze.

** Changed in: gvfs (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  gvfs-afc-volume-monitor crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219848] Re: eog crashed with SIGSEGV in g_type_check_instance_cast()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1205896, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799343/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799345/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799347/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799348/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799349/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799350/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219848/+attachment/3799351/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1205896

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  eog crashed with SIGSEGV in g_type_check_instance_cast()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1214204] Re: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

** Branch linked: lp:ubuntu/saucy-proposed/gvfs

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

Title:
  gvfs-afc-volume-monitor crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219870] [NEW] Saving PDF annotations in evince breaks PDF in acroread

2013-09-02 Thread Florian Echtler

Public bug reported:

[ Ubuntu 12.04, Evince 3.4.0, Poppler 0.18.4 ]

When I add annotations to a PDF in evince and save a copy of this PDF
(with annotations), I can no longer open the saved PDF in acroread
(gives an error message root object invalid or not found).

As far as I can tell, this only happens if the XREF table in the PDF is
a compressed stream - a workaround is to run

pdftk in.pdf output out.pdf uncompress

before annotating output.pdf in evince. The result can be opened in
acroread.

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

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

Title:
  Saving PDF annotations in evince breaks PDF in acroread

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219888] [NEW] nautilus crash on opening Dropbox folder

2013-09-02 Thread Morten E. Lund

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

Public bug reported:

When Dropbox deamon is running, nautilus crashes when opening dropbox folder. 
From terminal the following message is displayed :
(nautilus:4045): Gtk-WARNING **: Refusing to add non-unique action 
'NautilusDropbox::browse' to action group 'DirExtensionsMenuGroup'
Segmentation fault (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Sep  2 17:38:47 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b'960x618+2531+222'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'237'
InstallationDate: Installed on 2013-08-12 (20 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130812)
MarkForUpload: True
ProcCmdline: nautilus --no-desktop /home/username/Dropbox
SegvAnalysis:
 Segfault happened at: 0x7fdc858b8dd6 gtk_action_get_name+22: cmp
%rax,(%rdx)
 PC (0x7fdc858b8dd6) ok
 source %rax ok
 destination (%rdx) (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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


** Tags: amd64 apport-crash saucy

** Information type changed from Private to Public

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

Title:
  nautilus crash on opening Dropbox folder

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219888] Re: nautilus crash on opening Dropbox folder

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1193522, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799487/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799489/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799491/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799492/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799493/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799494/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219888/+attachment/3799495/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1193522
   nautilus crashed with SIGSEGV in gtk_action_get_name()

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crash on opening Dropbox folder

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0

2013-09-02 Thread PS Jenkins bot

Fix committed into lp:unity at revision None, scheduled for release in
unity, milestone 7.1.1

** Changed in: unity
   Status: In Progress = Fix Committed

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

Title:
  Move from zeitgeist-1.0 to zeitgeist-2.0

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

1. GNOME 3.8 has only been tested with gnome-settings-daemon 3.8 and
there's no guarantee that things work correctly when we mix and match
pieces.

the pieces that are the most matched are gnome-settings-daemon and
gnome-control-center, which are both in sync on 3.6 at the moment. Does
that mean you plan to FFe gnome-control-center as well (saying the
number of changes in g-c-c 3.8 I doubt it's a good idea to do that at
the end of the cycle)

2. Since we did the gsettings-desktop-schemas update, there are
gsettings keys that won't actually do anything without the updated
gnome-settings-daemon backend.

Do we have those exposed to users anywhere or is that a dconf editor
issue? We might also want to just drop those keys from the schemas if
you think that really confuses users

3. We need to update this cycle because we need to fix bug 1201679
which is a High priority regression in Unity (GNOME was unaffected).

Seems like that should be a one commit to backport if we need that fixes

4. There are numerous other fixes and improvements if you read through
the NEWS file. The update isn't just GNOME dropping Fallback support and
we've patched back in the fallback pieces that Unity currently needs.

Right, there are lot of changes in there, which makes me cautious,
gnome-settings-daemon has little automated testing and it's a somewhat
fragile component.

5. Tim did a lot of work on this update with the assumption that it could
make it into Saucy. We were delayed several weeks by
indicator-keyboard taking longer to land than expected. I tried to help
indicator-keyboard along as well as I could and
complained that the longer the delay, the more difficult it would be to land
gnome-settings-daemon 3.8 by Feature Freeze.

Right, thanks Tim for the work! The work is not wasted in any case, even
if that only lands next cycle. Things being less trivial than expected
is not a real reason to grant a FFe though, as you pointed we still have
fallout from 3.6 ibus migration we didn't sort out, it seems like what
we need is extra work on stabilization rather than changing that much
late in the cycle

There was one final regression that Tim fixed over the weekend. Ubuntu GNOME
shouldn't be penalized for taking care not to
cause regressions and waiting for Unity work.

It's not a matter to be penalized, what is the direct impact at the
moment on Ubuntu GNOME (out of not having the latests upstream version)?
The argument can go the other way around, Ubuntu GNOME wanted to be on
the current version is not a reason to create instability from
Unity/Ubuntu...

I've been running Unity all weekend to make sure that the update didn't cause
any new problems. Many people have installed
the GNOME3 Staging PPA; some of those people use Unity.

That's good to know!

To summarize my opinion: from the past record I would be careful to update
gnome-settings-daemon that late in the cycle, that's a component that drives
many settings in the desktop and which is not easy to test.

Having gnome-settings-daemon/gnome-control-center out of sync is
something we avoided so far, because it has extra potential to create
issue, and I'm still unsure that's something we should try...

Anyway, I'm going to let the release team review the request. I've a
small request, if the ffe is approved it should be under the condition
that those doing the update are going to deal with the bugs and
regressions it's going to create (not like previous cycle with nautilus)

Thanks

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

Title:
FFe: Update gnome-settings-daemon to 3.8.4

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219805] Re: 13.10 evolution-calendar-factory cevolution-calendar-factory constantly running and using 25% cpu

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: evolution (Ubuntu)
   Status: New = Confirmed

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

Title:
  13.10 evolution-calendar-factory cevolution-calendar-factory
  constantly running and using 25%  cpu

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

2013-09-02 Thread Jeremy Bicha

 Does that mean you plan to FFe gnome-control-center as well (saying
the number of changes in g-c-c 3.8 I doubt it's a good idea to do that
at the end of the cycle)

gnome-control-center 3.8 is about 90-95% ready and has quite a few
improvements Ubuntu GNOME really wants. But there's too much work to be
done to land now with zero regressions. We could really use Canonical
help for the remaining work but obviously you guys have other pressing
requirements this week. So no, I don't plan to file a FFe for gnome-
control-center 3.8 for 13.10.

On the other hand, we've talked for a long time about possibly forking
gnome-control-center so that there's both a mostly vanilla gnome-
control-center and a Ubuntu tweaked version in the repositories (but it
won't be possible for both to be simultaneously installed). gnome-
control-center is in good enough shape for GNOME — it's just the Unity
integration that needs more work — so we might still do a FFe for that
proposal if we agree that the benefits outweigh the negatives.

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

Title:
  FFe: Update gnome-settings-daemon to 3.8.4

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1214204] Re: gvfs-afc-volume-monitor crashed with SIGSEGV in g_type_check_instance_is_a()

This bug was fixed in the package gvfs - 1.17.90-0ubuntu1

---
gvfs (1.17.90-0ubuntu1) saucy; urgency=low

  * New upstream release:
- Works with current libimobiledevice API. (LP: #1214204)
  * debian/control.in: Bump libimobiledevice build dep.
  * Drop 00git_tests.patch, upstream now.
 -- Martin Pitt martin.p...@ubuntu.com   Mon, 02 Sep 2013 14:45:58 +0200

** Changed in: gvfs (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  gvfs-afc-volume-monitor crashed with SIGSEGV in
  g_type_check_instance_is_a()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219920] Re: nautilus crashed with SIGABRT in g_assertion_message()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1202159, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799609/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799611/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799612/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799613/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799614/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799615/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219920/+attachment/3799616/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1202159

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219922] Re: gnome-session-properties crashed with signal 5 in g_cclosure_marshal_VOID__BOXEDv()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1194546, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799641/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799643/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799645/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799646/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799647/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799648/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1219922/+attachment/3799649/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1194546
   gnome-session-properties crashed with signal 5 in 
g_cclosure_marshal_VOID__BOXEDv()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  gnome-session-properties crashed with signal 5 in
  g_cclosure_marshal_VOID__BOXEDv()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219943] [NEW] Nautilus Does Not Pass Logged in User Credentials to SAMBA Public Share

2013-09-02 Thread Jonathan

Public bug reported:

I've got a server running Ubuntu 13.04/SAMBA 3.6.9 that exposes a number
of private and public shared folders. The server and client both have a
user account with the username jfritz.

When I try to mount a public share from my Ubuntu 13.04 laptop by
clicking on it in the file explorer (nautilus), the share is mounted
with guest permissions and I cannot write to the folder, but I can read
all of the files.

However, if I manually mount the share from the terminal with the command mount 
-t cifs -o username=jfritz,password=mypassword //server.ip/sharename 
/localfolder
I get the read/write permissions of jfritz, as expected.

Further, if I mount the share with smbclient //server.ip/sharename
-Ujfritz, I get the read/write permissions of jfritz, as expected.

Finally, Windows machines that are logged in to an account with the same
username and password as jfritz also pass the correct credentials, and
are able to mount the share with read/write privileges.

tl;dr: Ubuntu 13.04 does not correctly pass the currently logged in
user's credentials to a SAMBA server when mounting shares via the file
explorer.

A copy of my smb.conf can be found at http://paste.ubuntu.com/6055511/,
although I don't suspect that this is a SAMBA issue, as it works as
expected with all non-nautilus clients.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu16
ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
Uname: Linux 3.8.0-29-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Mon Sep  2 14:10:39 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b'800x550+565+65'
InstallationDate: Installed on 2013-08-31 (1 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug raring

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

Title:
  Nautilus Does Not Pass Logged in User Credentials to SAMBA Public
  Share

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 272557] Re: Leaving an SD card in the slot when suspending creates a nautilus window on awake

2013-09-02 Thread S.O.E. Ansems

Until recent i never had this bug before even though i always have a SD-
card in the slot of my laptop.

The only things that changed since i have got bug are the laptop and SD-card.
-  The laptop is a Lenovo W530 
-  The SD-card is a cheap imitation (model 0, serial 0xb1538a26, vendor 
unknown)

I run Ubuntu 13.04 64bit.

If i were a developer i would be looking in the section of code that
deals with reactivating the hardware. Apparently Ubuntu incorreclty
treats the powering up of the SD-card as an insert of the card.

Hope this information helps, good luck with the bughunt!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/272557

Title:
  Leaving an SD card in the slot when suspending creates a nautilus
  window on awake

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1176985] [NEW] Ubuntu 13.04: Java not available in Open With properties, cannot set it as default application for jar files

You have been subscribed to a public bug:

After installing Java 6 and 7, I can right-click on jar files and do
open with and select Java 6 or 7 there, but I cannot set jar files to
always open with Java by going to the properties of a jar file, to the
Open With tab, and selecting them in the list because they do not
appear in the list of available applications nor does Ubuntu 13.04 give
you the ability to add applications to that list.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bot-comment
-- 
Ubuntu 13.04: Java not available in Open With properties, cannot set it as 
default application for jar files
https://bugs.launchpad.net/bugs/1176985
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to nautilus in Ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1176985] Re: Ubuntu 13.04: Java not available in Open With properties, cannot set it as default application for jar files

2013-09-02 Thread pcworld

Adding nautilus as the affected package, might be wrong, but better than
no package association.

** Package changed: ubuntu = nautilus (Ubuntu)

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

Title:
  Ubuntu 13.04: Java not available in Open With properties, cannot set
  it as default application for jar files

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219995] [NEW] package python-gi 3.8.0-2ubuntu1 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration.

2013-09-02 Thread mahmoud20070

Public bug reported:

I had installed xubuntu 12.04.3 and want to upgrade it to xubuntu 13.04
by edit sources.list file to raring repo and by this command apt-get
update  apt-get dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: python-gi 3.8.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
Date: Mon Sep  2 23:45:07 2013
DpkgTerminalLog:
 Preparing to replace python-oauthlib 0.3.7-0ubuntu1 (using 
.../python-oauthlib_0.3.7-0ubuntu1_all.deb) ...
 Unpacking replacement python-oauthlib ...
 dpkg: error processing python-gi (--configure):
  Package is in a very bad inconsistent state - you should
  reinstall it before attempting configuration.
DuplicateSignature: package:python-gi:3.8.0-2ubuntu1:Package is in a very bad 
inconsistent state - you should  reinstall it before attempting configuration.
ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
InstallationDate: Installed on 2013-09-02 (0 days ago)
InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820)
MarkForUpload: True
SourcePackage: pygobject
Title: package python-gi 3.8.0-2ubuntu1 failed to install/upgrade: Package is 
in a very bad inconsistent state - you should  reinstall it before attempting 
configuration.
UpgradeStatus: Upgraded to raring on 2013-09-02 (0 days ago)

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


** Tags: amd64 apport-package package-from-proposed raring

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

Title:
  package python-gi 3.8.0-2ubuntu1 failed to install/upgrade: Package is
  in a very bad inconsistent state - you should  reinstall it before
  attempting configuration.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219995] Re: package python-gi 3.8.0-2ubuntu1 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting configuration.

** Tags removed: need-duplicate-check

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

Title:
  package python-gi 3.8.0-2ubuntu1 failed to install/upgrade: Package is
  in a very bad inconsistent state - you should  reinstall it before
  attempting configuration.

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219999] [NEW] empathy facebook chat doesnt work

2013-09-02 Thread Ruben Rocha

Public bug reported:

As of last sunday i noticed facebook chat account in empathy doesnt work
anymore. When it tries to login it gives network error. Removing and
adding the account didnt solve the problem. I think Facebook has changed
(again) the authentication scheme.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: empathy 3.4.2.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
Uname: Linux 3.5.0-39-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
Date: Mon Sep  2 23:33:42 2013
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
MarkForUpload: True
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: empathy
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise running-unity

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

Title:
  empathy facebook chat doesnt work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 771272] Re: ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched

2013-09-02 Thread Tv

Tested on 13.04, still buggy. Manually running SSH_AUTH_SOCK=/tmp/ssh-
phxl1McWvuSj/agent.20832 skips gnome-keyring for ssh-agent actions, and
makes ecdsa work again -- but naturally that workaround is hard to do,
as the random parts keep changing.

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

Title:
  ssh-add does not handle ECDSA keys until ssh-agent exports are
  manually launched

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219999] Re: empathy facebook chat doesnt work

2013-09-02 Thread Quinn Balazs

Try adding @chat.facebook.com after your account in Empathy. The
facebook plugin is a bit flakey, but XMPP is fully supported.

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

Title:
  empathy facebook chat doesnt work

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

Running gnome-shell 3.8 on gnome-settings-daemon 3.6 is likely to be
very buggy and unstable. Although admittedly it hasn’t had a huge amount
of testing since the assumption was that we would get g-s-d 3.8 into
saucy.

For the 3.8 cycle many features were moved out of gnome-settings-daemon
and into other components such as mutter and gnome-shell. Most of these
however require code changes in g-s-d to use the new components. Other
than this there were not really many new features added to g-s-d and it
is largely just a big bug fix release.

- OSD Popups are now drawn by gnome-shell so that they match the shell UI.
- Keygrabber was moved into gnome-shell, since there were lots of issues with
media_keys keybindings not working in certain parts of gnome-shell
- Background plugin was moved into mutter
- Screenshots are handled by gnome-shell.
- Power support is pretty much broken when using g-s-d 3.6

All of these were moved to overcome technical limitations making it hard
or impossible to fix key bugs. In most cases by sticking with 3.6 we do
not get to take advantage of these new components and we are left using
the old unmaintained and buggy implementations.

In addition there are lots of bug fixes for things like power plugin,
notifications etc.

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

Title:
FFe: Update gnome-settings-daemon to 3.8.4

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

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 884145] Re: Gimp destroyes image file when trying to save as .tif with jpeg compression

2013-09-02 Thread Bug Watch Updater

** Changed in: gimp
   Status: New = Incomplete

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

Title:
  Gimp destroyes image file when trying to save as .tif with jpeg
  compression

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219486] Re: FFe: Update gnome-settings-daemon to 3.8.4

As for mixing g-s-d 3.8 with g-c-c 3.6, apart from a few moved gsettings
keys there are no major issues.

A lot of work went into improving a number of the upstream panels
(particularly network, power and region panels), and there a number of
new panels (notifications, privacy etc). However these changes are more
or less contained to g-c-c and don't introduce incompatibilities for
g-s-d.

Clearly Ubuntu GNOME really wants g-c-c 3.8  for these improvements. The
remaining Unity issues are all mostly trivial, however have basically
been blocked waiting on input from the desktop team. As far as I know no
one even bothered to look at this, even when I was working on these
issues very early in the Saucy cycle.

Nearly all the work I did on g-s-d was to fix Unity Integration. g-c-c
was split more evenly between general ubuntu integration and unity
integration. Obviously if regressions pop up, I will get them sorted.

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

Title:
  FFe: Update gnome-settings-daemon to 3.8.4

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

** Branch linked: lp:ubuntu/saucy-proposed/gdm

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

Title:
  lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

** Branch linked: lp:~darkxst/ubuntu/saucy/gnome-shell-
extensions/lp1212408

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

Title:
  lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

** Branch unlinked: lp:~darkxst/ubuntu/saucy/gnome-shell-
extensions/lp1212408

** Branch linked: lp:~darkxst/ubuntu/saucy/gnome-shell-
extensions/lp1212408-fix

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

Title:
  lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

** Branch linked: lp:ubuntu/saucy-proposed/gnome-shell-extensions

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

Title:
  lightdm/gdm needs to set $XDG_CURRENT_DESKTOP

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1194896] Re: eog crashed with SIGSEGV in g_type_check_instance_cast()

2013-09-02 Thread Mayank Suman

one instance of eog was running but when I mounted other partition and
loaded a photo in other instance of eog the first one crashed saying
there is no file in previous location.

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

Title:
  eog crashed with SIGSEGV in g_type_check_instance_cast()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1220039] Re: gnome-panel crashed with SIGSEGV in gtk_container_forall()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #851532, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800329/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800331/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800332/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800333/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800334/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800335/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1220039/+attachment/3800336/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 851532
   gnome-panel crashed with SIGSEGV in gtk_container_forall()

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  gnome-panel crashed with SIGSEGV in gtk_container_forall()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1219711] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2013-09-02 Thread jo

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

I am getting this message on trying to reach the original bug

Bug 1199371 cannot be found

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

Title:
  nautilus crashed with SIGSEGV in g_slice_alloc()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1220041] Re: nautilus crashed with SIGABRT in g_assertion_message()

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1202159, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800355/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800357/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800358/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800359/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800360/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800361/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1220041/+attachment/3800362/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1202159

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP