[Bug 1207812] Re: [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt Looping

2014-11-22 Thread bosale30
** Changed in: libimobiledevice (Ubuntu)
 Assignee: (unassigned) = bosale30 (salebo11)

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

Title:
  [FFe] Update libimobiledevice to support iOS 7, fix Trust Prompt
  Looping

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

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


[Bug 1395301] [NEW] Inconsistent terminology for Bluetooth pairing

2014-11-22 Thread Ben Harris
Public bug reported:

The Personal File Sharing Preferences window has two sections relating
to Bluetooth, and those use different terminology (and user interface
features) to describe Bluetooth pairing, both from one another and from
the main Bluetooth settings.

Under Share Files over Bluetooth, the requirement for pairing is
controlled by a tickbox labelled Require remote devices to bond with
this computer, while under Receive Files over Bluetooth, it's
controlled by a pop-up menu labelled Accept files: with options
Always and Only for set up devices.  As far as I can tell from the
docuementation (which disagrees slightly about how the user interface
should look), these controls have equivalent effects and control whether
files can be respectively browsed or sent by unpaired devices.
Meanwhile, the Bluetooth indicator menu uses the phrase Set-up [sic]
New Device, the Bluetooth pane of System Settings describes certain
devices as Paired, and the Ubuntu Desktop Guide explains how to
Connect your computer to a Bluetooth device but helpfully explains
that This is also called pairing the Bluetooth devices.

Personally, I think that both of these settings should be tickboxes, and
their labels should both be phrased in terms of paired deviced, since
that's standard Bluetooth terminology.  For consistency with the Ubuntu
Desktop Guide, perhaps connected would be better (but I think it's
less obvious what it means).

PS: I've just found the Control sharing over Bluetooth page of the
Ubuntu Desktop Guide, which adds to the fun by introducing trusted
devices, which are apparently yet another way of talking about paired
devices.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-user-share 3.0.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CurrentDesktop: Unity
Date: Sat Nov 22 10:53:26 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-file-share-properties
InstallationDate: Installed on 2010-06-09 (1626 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 Karmic - Build i386 LIVE Binary 
20100121-21:52
SourcePackage: gnome-user-share
UpgradeStatus: Upgraded to trusty on 2014-08-15 (98 days ago)

** Affects: gnome-user-share (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

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

Title:
  Inconsistent terminology for Bluetooth pairing

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

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


[Bug 481056] FW: bpentz

2014-11-22 Thread stephen.pivo...@gmail.com
http://sgk-ssk.com/qryjeyh/cgxyytixkekha.bpwplduzapsdqwhartpirpsvcccopf












 stephen.pivonka

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

Title:
  Dell Vostro 1000 laptop goes into hibernation whenever I plug in the
  power cord as if battery is dead

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/devicekit-power/+bug/481056/+subscriptions

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


[Bug 1385292] Re: can't rename files in nautilus

2014-11-22 Thread aexl
I can confirm the above.
I can also confirm that killing and restarting nautilus helps.

Strange: Ctrl-L does work though.

-- 
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/1385292

Title:
  can't rename files in nautilus

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

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


[Bug 1390954] [NEW] Screensaver disregard settings

2014-11-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hallo
Screensaver starts every 10 minutes even it is set to never (it works with 1 
min). This is really anoying when watching movies.
Best regards

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity-control-center 15.04.0+15.04.20141105-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov  9 19:06:19 2014
EcryptfsInUse: Yes
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center: deja-dup 32.0-0ubuntu1

** Affects: unity-control-center
 Importance: Undecided
 Status: New

** Affects: gnome-screensaver (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug vivid
-- 
Screensaver disregard settings
https://bugs.launchpad.net/bugs/1390954
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-screensaver in Ubuntu.

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


[Bug 1390954] Re: Screensaver disregard settings

2014-11-22 Thread Fabio Marconi
** Package changed: unity-control-center (Ubuntu) = gnome-screensaver
(Ubuntu)

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

Title:
  Screensaver disregard settings

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

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


[Bug 1339016] Re: Initial sync of the calendar takes a prohibitive amount of time

2014-11-22 Thread Bill Filler
We were able to improve the situation by limiting how far in the past to
sync for calendar events. This was a combination of a new version of
syncevolution, and a patch to it and sync-monitor to introduce a
syncInterval configuration setting (defaults to 90 days) specifiying
how many days in the past to go back when syncing. For my caledar, it
used to take 20 minutes for initial sync. Now it takes 33 seconds! Will
need testing by others but this seems to help greatly.

** No longer affects: evolution-data-server (Ubuntu)

** Also affects: sync-monitor (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: sync-monitor (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: syncevolution (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: sync-monitor (Ubuntu)
   Status: New = Fix Committed

** Changed in: sync-monitor (Ubuntu)
   Importance: Undecided = Critical

** Changed in: syncevolution (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: syncevolution (Ubuntu)
   Importance: Undecided = Critical

** Changed in: syncevolution (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: sync-monitor (Ubuntu RTM)
   Importance: Undecided = Critical

** Changed in: sync-monitor
   Status: Confirmed = Fix Committed

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

Title:
  Initial sync of the calendar takes a prohibitive amount of time

To manage notifications about this bug go to:
https://bugs.launchpad.net/sync-monitor/+bug/1339016/+subscriptions

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


[Bug 1395390] [NEW] does not connect after suspend/resume

2014-11-22 Thread Robinson Tryon
Public bug reported:

After resume from suspend, empathy no longer connects to any server,
even after restarting the application.

This bug has similar behavior to an existing report, however in my case neither 
interaction with the application GUI nor (solely) killing empathy seemed to 
have any effect:
https://bugs.launchpad.net/ubuntu/natty/+source/empathy/+bug/662766

Ubuntu 14.04.1 (Trusty)
Empathy 3.8.6-0 (Adding the Gnome3 PPA to get an updated version of Empathy 
(3.10.3-0) had no change)

Workarounds:
- Rebooting
- Killing all empathy *and* telepathy processes identified by:
  ps aux|grep 'empathy\|telepathy'

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

-- 
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/1395390

Title:
  does not connect after suspend/resume

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

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


[Bug 1166125] Re: Broken fonts for Gtk based applications

2014-11-22 Thread Ogilvierothchild
This package was somehow auto-installed in a release upgrade today from 14.04 
to 14.10, and cost me most of the day trying to figure out why everything in X 
was glitchy and crashing.  The terminal looked like
http://askubuntu.com/questions/285836/letter-spacing-in-gnome-terminal

Even xterm would crash on ctrl-right-click, and these badly-spaced
strange characters appeared in almost every terminal emulator (xterm
worked, except for its menus).  Font selection dialogs ground the
computer to a halt, and even the window manager titlebars were in a
wonky font.  Yet, something was showing, so it was a lot of work to
investigate the entire stack of X11, Xft, fontconfig, freetype, pango,
gtk, etc to find what component was bad.

sudo apt-get purge pango-graphite

solved the problem.  No idea how that package got installed, but it's
removal fixed everything immediately.  There is a serious problem with
this package in the 14.10 release of ubuntu as well.

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

Title:
  Broken fonts for Gtk based applications

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

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


[Bug 1166125] Re: Broken fonts for Gtk based applications

2014-11-22 Thread Ogilvierothchild
Given that this package breaks the entire desktop in a non-obvious way,
the priority should be high.  I'm a  software developer and have used
linux as my daily OS since 1993 and it took me several hours to figure
out what was going wrong.

What are novice users going to do, other than install another OS, if
this bug strikes them?  This bug makes all of X totally unusable.

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

Title:
  Broken fonts for Gtk based applications

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

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


[Bug 946742] Re: Shotwell crashes on start with gstreamer0.10-vaapi

2014-11-22 Thread Launchpad Bug Tracker
[Expired for intel-vaapi-driver (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: Incomplete = Expired

-- 
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/946742

Title:
  Shotwell crashes on start with gstreamer0.10-vaapi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/946742/+subscriptions

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