[Bug 1426307] Re: location is inaccurate

[Lucio Carreras]

Hi Costales,

Yes, it's working perfectly in Portugal/Spain but not in Germany. Even if I get 
some fix sometimes it's lost 5min later. The accuracy in Portugal drifts 
between 2m and 20m. In Germany there's no data at all visible in this app. 
I don't accept it to use a service like Nokia's HERE, because in the mountains 
e.g. there is no wifi. My wifi is usually turned off if I'm not at home, in 
order to save battery. And as I see here, I don't even need it.

I think it's neccessary to create the possibility to see some debug
output. Another way to improve this function might be the possibility to
enter the rough position in order to find satellites faster.

Greetings, Lucio

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

Title:
  location is inaccurate

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+subscriptions

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

[Bug 1426307] Re: location is inaccurate

[wdoekes]

I've never had GPS location work without the HERE functions enabled. As
soon as I disable it (I have to restart for a change to take effect) I
get *no* location info whatsoever. (I have waited for weeks to get a GPS
lock, to no avail.)

The SensorsStatus tool tells me (when HERE is enabled) that I only have
Horizontal accuracy, and that drifts between 8m and 250m.

Location: Netherlands
SIMs/network: dual sim and lots of wifi around
Version: latest Ubuntu 15.04 r24 (20150713) on the Aquaris BQ 4.5

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

Title:
  location is inaccurate

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+subscriptions

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

[Bug 194732] Re: Screen power saving mode will not resume after using VNC prorgram

[wallymann]

fyi...i had this exact same problem running ubuntu 14.04.

the monitor powersave function would work fine when sitting at the
machine and interacting directly with it.  when i'd step away, the
monitor would power-off as expected.

but when i would interact remotely via VNC (desktop sharing) and stop
using the machine, the workstation's monitor would stay on indefinitely
regardless of the powersave settings.

this undesired behaviour was consistent whether i was using xfce-power-
manager or light-locker to manage the monitor powersave settings.

but when i tried xscreensaver instead (after removing both xfce-power-
manager and light-locker), it worked fine -- the monitor powersave would
activate whether i was working directly with the machine or accessing
remotely via VNC.

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

Title:
  Screen power saving mode will not resume after using VNC prorgram

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

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

[Bug 1491557] [NEW] Nested containers aren't working in wily

[Serge Hallyn]

Public bug reported:

Several things are conspiring to stop nested containers in wily from
working.

** Affects: cgmanager (Ubuntu)
 Importance: High
 Assignee: Serge Hallyn (serge-hallyn)
 Status: In Progress

** Affects: lxcfs (Ubuntu)
 Importance: High
 Assignee: Serge Hallyn (serge-hallyn)
 Status: In Progress

** Affects: systemd (Ubuntu)
 Importance: High
 Assignee: Serge Hallyn (serge-hallyn)
 Status: In Progress

** Also affects: lxcfs (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cgmanager (Ubuntu)
   Importance: Undecided => High

** Changed in: lxcfs (Ubuntu)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Changed in: cgmanager (Ubuntu)
 Assignee: (unassigned) => Serge Hallyn (serge-hallyn)

** Changed in: lxcfs (Ubuntu)
 Assignee: (unassigned) => Serge Hallyn (serge-hallyn)

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Serge Hallyn (serge-hallyn)

** Changed in: cgmanager (Ubuntu)
   Status: New => In Progress

** Changed in: lxcfs (Ubuntu)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

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

Title:
  Nested containers aren't working in wily

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

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

[Bug 1491601] Re: Testcase for Gnome-terminal needs editing

[Nicholas Skaggs]

Patches most welcome! This was filed in the wrong spot. As software
changes, we have to maintain the tests. See
https://wiki.ubuntu.com/QATeam/ContributingTestcases/Manual for help,
it's as easy as writing out what you've said above. Thanks for the
report!

** Package changed: gnome-terminal (Ubuntu) => ubuntu-manual-tests

** Tags added: bitesize todo

** Changed in: ubuntu-manual-tests
   Importance: Undecided => Medium

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

Title:
  Testcase for Gnome-terminal needs editing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1491601/+subscriptions

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

[Bug 1069964] Re: Two processes attempt to mount blank optical discs

[Doug McMahon]

2 things here - 
This never occurs on the 1st. insertion of blank optical media in an internal 
cd/dvd drive but happens on all subsequent insertions in that session

This never occurs when automount is disabled  (org.gnome.desktop.media-
handling

There is likely no tie in to the above 2 but does beg the question of
why does gnome/gvfs connect blank media to org.gnome.desktop.media-
handling automount at all?? It should have nothing to do with it & as
far as usability of inserted blank media,  automount 'false' has no
effect. (other than prevent spurious warning

The same could/should  be said for audio cd's, org.gnome.desktop.media-
handling automount should not be involved.  In the case of audio cd's
there  is an effect of automount 'false' - auto run on audio cd
insertion is not possible. Again this is wrong behavior, a prompt on
audio cd's or a user set action on audio cd insertion should always
occur independent of org.gnome.desktop.media-handling automount
true/false

** Tags added: gnome-media-handling

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

Title:
  Two processes attempt to mount blank optical discs

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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

[Bug 1491699] [NEW] No Global menu for eog (Wily, Unity7)

[Khurshid Alam]

Public bug reported:

It looks like there is no global for eog (3.16.3-1) in Wily (Screenshot:
http://i.imgur.com/1uNr4CW.png) From the previous change-log it seems it
has something to with "Update debian/patches/disable-appmenu-when-not-
needed.patch to apply" which was introduced in eog 3.16.2-1.
(http://bazaar.launchpad.net/~ubuntu-desktop/eog/ubuntu/revision/158).

My purpose of app-menu is to access preference (and then plugins) or
toolbar menu so that I can add shotwell's "Edit Image" plugin into the
toolbar (screenshot in Vivid: http://i.imgur.com/4tfsVuv.png). Without
any sort preference in the menu that is not possible.


Edit: It seems "Show traditional titlebar under unity" patch does not
exist under debian/patches anymore. Does this mean that it went
upstream?

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


** Tags: wily

** Attachment added: "screenshot taken on Wily"
   
https://bugs.launchpad.net/bugs/1491699/+attachment/4456687/+files/Screenshot%20from%202015-09-03%2010-08-39.png

** Tags added: wily

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

Title:
  No Global menu for eog (Wily, Unity7)

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

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

[Bug 1491564] [NEW] package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[co...@elton.schivei.com.br]

Public bug reported:

It's occurs while system auto update.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: totem 3.14.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Wed Sep  2 16:06:07 2015
DuplicateSignature: package:totem:3.14.2-0ubuntu1:subprocess new pre-removal 
script returned error exit status 1
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-08-22 (10 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: totem
Title: package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check vivid

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

Title:
  package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

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

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

[Bug 1491564] Re: package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

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

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

[Bug 1491601] Re: Testcase for Gnome-terminal needs editing

[Ubuntu QA Website]

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:
http://packages.qa.ubuntu.com/qatracker/reports/bugs/1491601

** Tags added: package-qa-testing

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

Title:
  Testcase for Gnome-terminal needs editing

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

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

[Bug 1491601] [NEW] Testcase for Gnome-terminal needs editing

[Istimsak]

Public bug reported:

I have noticed some inconsistencies with the gnome-terminal testcase and
the gnome-terminal I have installed with ubuntu 15.10.

Test-case name: gnometerminal/ter-002
This test will check that terminal colors and zoom level can be changed

Open the Terminal application
Click on Edit, select Profiles, select Edit and select "Colors"
Using the options contained in the "Colors" tab modify the color palette, 
choosing some non-default colors or a different color scheme
The colors in your terminal match your modifications
Click on Edit, select Profiles, select Edit and select "Background"
Set the terminal choosing the option "Background Image"
Terminal background changes to the current wallpaper

For this tier, the only thing I was able to change were the palette
custom color themes. Clicking the colors below the custom palette
dropdown menu did not change anything.

Open the Terminal application
Press "Ctrl+Alt+T"
Is an instance of gnome-terminal with the title 'user@hostname: ~' opened, with 
the current directory set to the users home directory?

ctl-alt-t did not open the gnome-terminal. shift-ctr-t opens a new tab
within an open terminal and shift-ctrl-n opens a new terminal. This
needs to be modified.

Open the Terminal application
>From the main menu select 'Terminal > Set Title...'
The Set Title dialog appears
Enter 'Test Title' and click OK
Is the title of the window now 'Test Title'?

There was no "set title" under the terminal menu. There was no option of
changing the menu title.

This testcase needs to be edit to align with the terminal pre-installed
on ubuntu 15.10.

Description:Ubuntu Wily Werewolf (development branch)
Release:15.10
gnome-terminal:
  Installed: 3.16.2-1ubuntu2
  Candidate: 3.16.2-1ubuntu2
  Version table:
 *** 3.16.2-1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gnome-terminal 3.16.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic i686
ApportVersion: 2.18-0ubuntu9
Architecture: i386
Date: Wed Sep  2 17:02:23 2015
InstallationDate: Installed on 2015-05-18 (107 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150517)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: Opinion


** Tags: apport-bug i386 wily

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Opinion

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

Title:
  Testcase for Gnome-terminal needs editing

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

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

[Bug 1491135] Re: Sync gnome-system-monitor 3.16.0-2 (main) from Debian unstable (main)

[Iain Lane]

This bug was fixed in the package gnome-system-monitor - 3.16.0-2
Sponsored for Logan Rosen (logan)

---
gnome-system-monitor (3.16.0-2) unstable; urgency=medium

  [ Andreas Henriksson ]
  * Switch build-dependency from appdata-tools to appstream-util

  [ Michael Biebl ]
  * Bump debhelper compatibility level to 9.
  * Add Homepage: field.

 -- Michael Biebl   Tue, 01 Sep 2015 11:19:34 +0200

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync gnome-system-monitor 3.16.0-2 (main) from Debian unstable (main)

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

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

[Bug 1489702] Re: FFE: two small new features in networkd and machinectl

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 225-1ubuntu1

---
systemd (225-1ubuntu1) wily; urgency=medium

  * Merge with Debian unstable (FFE: LP: #1489702). Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
  /etc/writable/ instead.
- Keep our much simpler udev maintainer scripts (all platforms must
  support udev, no debconf).
- initramfs init-bottom: If LVM is installed, settle udev,
  otherwise we get missing LV symlinks. Workaround for LP #1185394.
- Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
  dependencies to "lvm2" which is handled with udev rules in Ubuntu.
- Add debian/udev.lvm2.service to avoid running the dummy lvm2 init
  script.
- Provide shutdown fallback for upstart. (LP: #1370329)
- debian/extra/ifup@.service: Additionally run for "auto" class. We don't
  really support "allow-hotplug" in Ubuntu at the moment, so we need to
  deal with "auto" devices appearing after "/etc/init.d/networking start"
  already ran. (LP: #1374521)
- ifup@.service: Drop dependency on networking.service (i. e.
  /etc/init.d/networking), and merely ensure that /run/network exists.
  This avoids unnecessary dependencies/waiting during boot and dependency
  cycles if hooks wait for other interfaces to come up (like ifenslave
  with bonding interfaces). (LP: #1414544)
- Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
  Ubuntu we currently keep the setting whether the RTC is in local or UTC
  time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
  (LP: #1377258)
- Put session scopes into all cgroup controllers. This makes unprivileged
  user LXC containers work under systemd. (LP: #1346734)
- systemctl: Don't forward telinit u to upstart. This works around
  upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
  that changes to point to systemd during the upgrade. This avoids running
  systemd during a dist-upgrade. (LP: #1430479)
- Drop hwdb-update dependency from udev-trigger.service, which got
  introduced in v219-stable. This causes udev and plymouth to start too
  late and isn't really needed in Ubuntu yet as we don't support stateless
  systems yet and handle hwdb.bin updates through dpkg triggers. This can
  be dropped again with initramfs-tools 0.117.
- Lower Breaks: to plymouth version which has the udev inotify fix in
  Ubuntu.
- Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
- Don't build new systemd-journal-remote package and drop
  libmicrohttpd-dev. This is blocked by the MIR (LP #1488341) and feature
  freeze.

Upgrade fixes, keep until 16.04 LTS release:
- systemd Conflicts/Replaces/Provides systemd-services.
- Remove obsolete systemd-logind upstart job.
- Clean up obsolete /etc/udev/rules.d/README.
- systemd.postinst: Migrate mountall specific fstab options to standard
  util-linux "nofail" option.

systemd (225-1) unstable; urgency=medium

  [ Martin Pitt ]
  * New upstream release.
- Fixes FTBFS on alpha. (Closes: #792551)
- Fixes machined state tracking logic. (Closes: #788269)
  * Add better fix for "systemctl link/enable" breakage with full paths.
(LP: #1480310)
  * debian/rules: Add missing $(dh_options) in overridden debhelper targets.

  [ Felipe Sateler ]
  * Move conffile from systemd to systemd-container package (Closes: #797048)

  [ Michael Biebl ]
  * Drop unnecessary Conflicts/Replaces from systemd-journal-remote.
None of the files in this package were previously shipped by systemd.
  * Create system users for systemd-journal-{gateway,remote,upload} when
installing the systemd-journal-remote package.
  * Explicitly turn off the features we don't want in a stage1 build.
Otherwise ./configure might enable them automatically if the build
dependencies are installed and "dh_install --fail-missing" will then fail
due to uninstalled files.
  * Enable GnuTLS support as systemd-journal-remote makes sense mostly with
encryption enabled.
  * Rely on build profiles to determine which packages should be skipped
during build and no longer specify that manually.
  * Drop our patch which removes rc-local-generator.
rc-local.service acts as an ordering barrier even if its condition is
false, because conditions are evaluated when the service is about to be
started, not when it is enqueued. We don't want this ordering barrier on
systems that don't need/use /etc/rc.local.

 -- Martin Pitt   Tue, 01 Sep 2015 14:19:33
+0200

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

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

Title:
  FFE: two small new 

[Bug 957558] Re: The bluetooth module in the Asus UX31/UX21 is based on Atheros AR3012 and requires a firmware to be uploaded before it's usable.

[madbiologist]

What version of Ubuntu is this occurring on?

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

Title:
  The bluetooth module in the Asus UX31/UX21 is based on Atheros AR3012
  and requires a firmware to be uploaded before it's usable.

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

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

[Bug 1491393] [NEW] 15.10: Long boot-time delays trying to find disconnected hot-plugged storage devices

[TJ]

Public bug reported:

Is there a way to prevent systemd from creating generator targets for
hot-plug disks?

Currently it is causing very long delays at boot-time - which are not
interruptible by the sys-admin - but I'm not sure at what point systemd
decided those hot-plug devices should be added to the boot-time tasks,
or how to safely delete them.

There are generator rules added at some stage but I cannot find
information on how to safely remove them, or how to prevent them being
created.

In this output the device-mapper names prefixed LUKS_HDD_ are the
problem:

$ ls -l /var/run/systemd/generator/*
-rw-r--r-- 1 root root 486 Sep  2 11:45 /var/run/systemd/generator/boot.mount
-rw-r--r-- 1 root root 486 Sep  2 11:45 /var/run/systemd/generator/home.mount
-rw-r--r-- 1 root root 294 Sep  2 11:45 /var/run/systemd/generator/-.mount
-rw-r--r-- 1 root root 933 Sep  2 11:45 
/var/run/systemd/generator/systemd-cryptsetup@LUKS_BOOT.service
-rw-r--r-- 1 root root 933 Sep  2 11:45 
/var/run/systemd/generator/systemd-cryptsetup@LUKS_DATA.service
-rw-r--r-- 1 root root 887 Sep  2 11:45 
/var/run/systemd/generator/systemd-cryptsetup@LUKS_HDD_OS.service
-rw-r--r-- 1 root root 887 Sep  2 11:45 
/var/run/systemd/generator/systemd-cryptsetup@LUKS_HDD_VM.service
-rw-r--r-- 1 root root 929 Sep  2 11:45 
/var/run/systemd/generator/systemd-cryptsetup@LUKS_OS.service
-rw-r--r-- 1 root root 491 Sep  2 11:45 
/var/run/systemd/generator/usr-local.mount
-rw-r--r-- 1 root root 485 Sep  2 11:45 /var/run/systemd/generator/var.mount

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

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

Title:
  15.10: Long boot-time delays trying to find disconnected hot-plugged
  storage devices

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

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

[Bug 1175122] Re: Doesn't work with Google 2-Factor Authentication

[BeowulfOF]

Heres the detailed version of the package where it is still failing
with:

apt-cache policy gnome-online-accounts
gnome-online-accounts:
  Installiert:   3.14.2-1ubuntu1
  Installationskandidat: 3.14.2-1ubuntu1
  Versionstabelle:
 *** 3.14.2-1ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  Doesn't work with Google 2-Factor Authentication

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1175122/+subscriptions

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

[Bug 1175122] Re: Doesn't work with Google 2-Factor Authentication

[BeowulfOF]

Maybe there was a fix, but I still get the popup to enter my password
for my google account every now and then, sometimes every 5 minutes,
sometimes only once a day.

It is not fixed on 15.04!

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

Title:
  Doesn't work with Google 2-Factor Authentication

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1175122/+subscriptions

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

[Bug 1491421] [NEW] Dbus-plugin does not work right.

[moma]

Public bug reported:

Totem's DBus-plugin may have a bug.  I try to control the Totem-player
from Audio-Recorder.  Audio-recorder does see the player on the DBus but
Totem does not reply requests.

This same bug was reported last year too. And year before.  Now this annoying 
bug is back!  
What the H* are they doing?

I run totem 3.16.2 on Ubuntu 15.10 (alfa).
$ totem --version
totem 3.16.2


Totem fails to return "PlaybackStatus". (this is a long one-line
command):

$  dbus-send --print-reply --session --dest=org.mpris.MediaPlayer2.totem
/org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.Get
string:'org.mpris.MediaPlayer2.Player' string:'PlaybackStatus'

Error org.freedesktop.DBus.Python.AttributeError: Traceback (most recent call 
last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/totem/plugins/dbus/dbusservice.py", line 164, in Get
return self.GetAll (interface_name)[property_name]
  File "/usr/lib/totem/plugins/dbus/dbusservice.py", line 182, in GetAll
if self.totem.action_remote_get_setting (
AttributeError: 'Object' object has no attribute 'action_remote_get_setting'


Totem fails to return "Metadata". (this is a long one-line command):

$ dbus-send --print-reply --session
--dest=org.mpris.MediaPlayer2.rhythmbox /org/mpris/MediaPlayer2
org.freedesktop.DBus.Properties.Get
string:'org.mpris.MediaPlayer2.Player' string:'Metadata'


dbus-send --print-reply --session --dest=org.mpris.MediaPlayer2.totem 
/org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.Get 
string:'org.mpris.MediaPlayer2.Player' string:'Metadata'
Error org.freedesktop.DBus.Python.AttributeError: Traceback (most recent call 
last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/totem/plugins/dbus/dbusservice.py", line 164, in Get
return self.GetAll (interface_name)[property_name]
  File "/usr/lib/totem/plugins/dbus/dbusservice.py", line 182, in GetAll
if self.totem.action_remote_get_setting (
AttributeError: 'Object' object has no attribute 'action_remote_get_setting'


Good samples:
Here are correct replies from the RhythmBox player:

Get Playerstatus from RhythmBox:

$ dbus-send --print-reply --session
--dest=org.mpris.MediaPlayer2.rhythmbox /org/mpris/MediaPlayer2
org.freedesktop.DBus.Properties.Get
string:'org.mpris.MediaPlayer2.Player' string:'PlaybackStatus'


method return time=1441188372.041001 sender=:1.146 -> destination=:1.149 
serial=194 reply_serial=2
   variant   string "Playing"
-

And get Metadata from RhytmBox:

$ dbus-send --print-reply --session
--dest=org.mpris.MediaPlayer2.rhythmbox /org/mpris/MediaPlayer2
org.freedesktop.DBus.Properties.Get
string:'org.mpris.MediaPlayer2.Player' string:'Metadata'

method return time=1441188535.630312 sender=:1.146 -> destination=:1.161 
serial=226 reply_serial=2
   variant   array [
 dict entry(
string "mpris:trackid"
variantstring "/org/mpris/MediaPlayer2/Track/2"
 )
 dict entry(
string "xesam:url"
variantstring 
"http://ubuntu.hbr1.com:19800/tronic.ogg;
 )
 dict entry(
string "xesam:title"
variantstring "After Midnight Dejavu (2006)"
 )
 dict entry(
string "xesam:genre"
variantarray [
  string "House"
   ]
 )
 dict entry(
string "rhythmbox:streamTitle"
variantstring "HBR1.com - Tronic Lounge"
 )




BTW: I can see in the Audio-recorder (when debugging) that Totems sends
some DBus-messages repeatedly. Audio-recorder gets mad by receiving 20
STOP, START, PAUSE, START, STOP, PAUSE, STOP... messages.  I programmed
a special workaround for Totem in Audio-Recorder.

Ref: 
http://bazaar.launchpad.net/~audio-recorder/audio-recorder/trunk/view/head:/src/dbus-mpris2.c

https://launchpad.net/~audio-recorder

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: totem 3.16.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Sep  2 15:10:10 2015
InstallationDate: Installed on 2015-08-29 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150827)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.