[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04

[Oliver Grawert]

we funnily have removed these udev rules before (but i guess the patch
was dropped when syncing a new version)

https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Committed
Status in brltty source package in Jammy:
  Confirmed
Status in brltty package in Debian:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  * Regression potential

  There are some braille devices on the market using generic IDs which
  are going to stop working out of the box. Those devices are uncommon
  and it's arguably an hardware bugs they are using those IDs.

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

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


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

[Desktop-packages] [Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Oliver Grawert]

for people not using the official announcement channels, here is a link
to the related public announcement (with details on the reasoning and a
place for discussion and feedback):

https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the-
official-firefox-snap-in-ubuntu-desktop/24210

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

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


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

[Desktop-packages] [Bug 1900679] Re: [snap] chromium spams dmesg

[Oliver Grawert]

snap run --strace chromium

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

Title:
  [snap] chromium spams dmesg

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions

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

[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Oliver Grawert]

there are various forum and askubuntu threads about this issue already
as well:

https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133

https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window-
control-and-fonts/17859

https://askubuntu.com/q/1206868/66509

https://discourse.ubuntu.com/t/odd-close-button-with-snaps/19392

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gnome-themes-extra package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package

[Oliver Grawert]

please note that the stable UbuntuCore18 images regressed due to this:

https://github.com/snapcore/core18/issues/170

** Bug watch added: github.com/snapcore/core18/issues #170
   https://github.com/snapcore/core18/issues/170

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  k) Test that supporting changes for xenial are in place:

i) verify grub-legacy-ec2 is not in the xenial server seed
ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the 

[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

[Oliver Grawert]

is there any particular reason to not simply adjust the patch to point
to $SNAP_DATA/etc/chromium-browser/policies ? after all this is where
system-wide configs should go ...

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433 comm
  ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions

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

[Desktop-packages] [Bug 1850977] Re: Snap installs software without user having sudo access

[Oliver Grawert]

the requirement for policykit (and dropping of gksu/gksudo) came with
the switch to gnome upstream, its a hard requirement for the desktop
nowadays.

while the default here might be wrong (and should be reviewed by someone
from the desktop team), this is definitely not a snapd related bug. i
added a gnome-software task and will close the snapd one ...

** Changed in: snapd (Ubuntu)
   Status: Incomplete => Invalid

** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Snap installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850977] Re: Snap installs software without user having sudo access

[Oliver Grawert]

policyKit does not involve sudo in any way, it uses systemd-logind from
the session to elevate privileges. if you are marked as admin in the
policyKit setup you will indeed be able to do admin things no matter
what is written in sudoers ;)

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

Title:
  Snap installs software without user having sudo access

Status in policykit-1 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1850977/+subscriptions

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

[Desktop-packages] [Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

[Oliver Grawert]

after a comment from jamesh in the forum discussion i found that
installing nscd from universe works around the issue, but this does not
change the fact that it is a regression of an ubuntu default feature, so
there still needs to be some solution (snapd dependency on nscd and
moving nscd back into main, fixing nssswitch.conf inside the core/core18
snap or some other new solution)

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions

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

[Desktop-packages] [Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

[Oliver Grawert]

trying your test on any of my machines does not work here btw (so i
assume it has nothing to do with running the server locally)

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions

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

[Desktop-packages] [Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

[Oliver Grawert]

well, try something thats not on localhost, i know that i cant resolve
anything in my LAN that uses mdns (note that this will also affect
printing i guess)

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+subscriptions

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

[Oliver Grawert]

snapd's userd just calls "xdg-open " in the users session when a
link is clicked, i have opened a task against xdg-utils, it should make
sure to call the right command to open urls in existing browser
sessions.

the opening of "help://" urls via userd is an explicit limitation in
snapd's userd that should get a separate bug so things are not being
mixed here.

** Also affects: xdg-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in Snappy:
  New
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Oliver Grawert]

> Now that Ubuntu has given up on Wayland by default

Ubuntu has not given up on Wayland by default but delayed it by one more
LTS (particulary because of bugs like this one).

Wayland by default is still the plan for the next LTS (and the interim
releases between 18.04 and 20.04). The incentive for transitioning the
apps has not dropped but it was clear that it could not be finished by
18.04.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  

[Desktop-packages] [Bug 1677924] Re: Local privilege escalation via guest user login

[Oliver Grawert]

This security fix seems to have caused some fallout ... see bug 1733557

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

Title:
  Local privilege escalation via guest user login

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.20 series:
  Fix Released
Status in Light Display Manager 1.22 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  It was discovered that a local attacker could watch for lightdm's
  guest-account script to create a /tmp/guest-XX file and then quickly 
create
  the lowercase representation of the guest user's home directory before lightdm
  could. This allowed the attacker to have control of the guest user's home
  directory and, subsequently, gain control of an arbitrary directory in the
  filesystem which could lead to privilege escalation.

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

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Oliver Grawert]

please note that this rule will also likely be used inside the initrd to
set up the console for encyption key input and there will be no systemd
around ... you probably want to rather handle it conditionally so it is
still available when creating an initrd ...

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Oliver Grawert]

might be that we need it on Ubuntu Core (and server) though ... so
installing the rule at all should probably be conditional ...

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  New
Status in console-setup package in Ubuntu:
  Triaged
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1711625] Re: Installation won't create music, documents ... folders in home partition

[Oliver Grawert]

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

** This bug has been marked a duplicate of bug 1708569
   1st. login fails to create a complete $HOME directory in a ubuntu-wayland 
(defacto default) session

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

Title:
  Installation won't create music, documents ... folders in home
  partition

Status in xdg-user-dirs package in Ubuntu:
  Triaged

Bug description:
  On ubuntu ARTFUL,
  Making a new installation with a new home partition will create only one 
folder "exemples"

  There is no folder "Documents", "Music", "Downloads" 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1711625/+subscriptions

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

[Desktop-packages] [Bug 1710468] Re: XDG user directories are missing in Ubuntu 17.10

[Oliver Grawert]

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

** This bug has been marked a duplicate of bug 1708569
   Installer on latest image fails to create a complete $HOME directory

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

Title:
  XDG user directories are missing in Ubuntu 17.10

Status in xdg-user-dirs-gtk package in Ubuntu:
  Triaged

Bug description:
  XDG user directories are not being created in Ubuntu 17.10. There are
  just "Desktop" and "Downloads" directories in my home and they are not
  even translated on my non-english installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1710468/+subscriptions

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

[Desktop-packages] [Bug 1708569] Re: Installer on latest image fails to create a complete $HOME directory

[Oliver Grawert]

xdg-user-dirs normally runs on first login to create these dirs, not an
installer issue ...

** Also affects: xdg-user-dirs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Installer on latest image fails to create a complete $HOME directory

Status in gnome-session package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid
Status in xdg-user-dirs package in Ubuntu:
  New

Bug description:
  Test case:
  Use latest image (august 2 here
  Install, reboot
  Check contents of home folder

  Seen here:
  $ ls
  Desktop  examples.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 22:07:38 2017
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
  InstallationDate: Installed on 2017-08-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170802)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[Oliver Grawert]

note that i see the non-starting wayland session on a 16.04 system that
does not have the unity8-desktop-session package installed, x11 gnome as
well as unity (7) start just fine and there is no trace of any unity8
packages on this laptop.

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Invalid
Status in unity8-desktop-session:
  Won't Fix
Status in gnome-session package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Won't Fix

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1644237] Re: unity8 fails to start as guest user

[Oliver Grawert]

related to bug 1593407 ?

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

Title:
  unity8 fails to start as guest user

Status in Canonical System Image:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  This is shown in unity8.log:

  [2016-11-23 15:59:25.820868] mirserver: Starting
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
 Throw in function 
mir::DefaultServerConfiguration::the_graphics_platform()::
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Exception while creating graphics platform
  ERROR: 
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
 Throw in function 
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const 
string&, const string&, const 
std::shared_ptr&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Nested Mir Platform Connection Error: Failed to connect 
to server socket: Permission denied


  [2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
  initctl: No such variable: UNITY_MIR_SOCKET

  running current zesty, but I had the same problem on yakkety too.

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

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

[Desktop-packages] [Bug 1593604] Re: gvfs should ignore snap package mounts

[Oliver Grawert]

not sure if the fix for this needs to be in gvfs or in snapd, so i added
a snapd bugtask as well.

** Description changed:

  when removing a snap package gvfs shows a device in the unity panel for
  a split second while the squashfs is unmounted during package removal.
  
  ideally gvfs should ignore all snap package operations since the package
  mounts should never be used directly by users.
  
- running in one terminal: 
+ running in one terminal:
  sudo snap remove 
  
  while in another terminal gvfs-mount --monitor is running i get the
  following output:
  
  ogra@styx:~$ gvfs-mount --monitor
  Monitoring events. Press Ctrl+C to quit.
  
  Volume added:   'Datenträger 66 MB'
  Volume changed: 'Datenträger'
  Volume removed: 'Datenträger'
  
- 
- this only happens on snap removal, not when installing a snap (nothing is 
printed in the --monitor terminal during instal)
+ this only happens on snap removal, not when installing a snap (nothing
+ is printed in the --monitor terminal during install)

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

Title:
  gvfs should ignore snap package mounts

Status in gvfs package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  when removing a snap package gvfs shows a device in the unity panel
  for a split second while the squashfs is unmounted during package
  removal.

  ideally gvfs should ignore all snap package operations since the
  package mounts should never be used directly by users.

  running in one terminal:
  sudo snap remove 

  while in another terminal gvfs-mount --monitor is running i get the
  following output:

  ogra@styx:~$ gvfs-mount --monitor
  Monitoring events. Press Ctrl+C to quit.

  Volume added:   'Datenträger 66 MB'
  Volume changed: 'Datenträger'
  Volume removed: 'Datenträger'

  this only happens on snap removal, not when installing a snap (nothing
  is printed in the --monitor terminal during install)

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

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

[Desktop-packages] [Bug 1593604] [NEW] gvfs should ignore snap package mounts

[Oliver Grawert]

Public bug reported:

when removing a snap package gvfs shows a device in the unity panel for
a split second while the squashfs is unmounted during package removal.

ideally gvfs should ignore all snap package operations since the package
mounts should never be used directly by users.

running in one terminal:
sudo snap remove 

while in another terminal gvfs-mount --monitor is running i get the
following output:

ogra@styx:~$ gvfs-mount --monitor
Monitoring events. Press Ctrl+C to quit.

Volume added:   'Datenträger 66 MB'
Volume changed: 'Datenträger'
Volume removed: 'Datenträger'

this only happens on snap removal, not when installing a snap (nothing
is printed in the --monitor terminal during install)

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

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

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

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

Title:
  gvfs should ignore snap package mounts

Status in gvfs package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  when removing a snap package gvfs shows a device in the unity panel
  for a split second while the squashfs is unmounted during package
  removal.

  ideally gvfs should ignore all snap package operations since the
  package mounts should never be used directly by users.

  running in one terminal:
  sudo snap remove 

  while in another terminal gvfs-mount --monitor is running i get the
  following output:

  ogra@styx:~$ gvfs-mount --monitor
  Monitoring events. Press Ctrl+C to quit.

  Volume added:   'Datenträger 66 MB'
  Volume changed: 'Datenträger'
  Volume removed: 'Datenträger'

  this only happens on snap removal, not when installing a snap (nothing
  is printed in the --monitor terminal during install)

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

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

[Desktop-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage

[Oliver Grawert]

hmm, this bug seems ot have been dragged away from the actual topic by
the audience, please note that this bug talks about phone and tablet
installs (as the "Canonical System Image" task implies) where we use a
reduced and slightly different installation compared to desktops (and
definitely no support for things like ~/.config/autostart and such).

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

Title:
  evolution-calendar-factory always running with high memory usage

Status in Canonical System Image:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  At boot the process is using over 100MB on my mako (build 129)
  I sync'd a fairly large set of calendar events from google previously

  Does this process need to be running all the time?
  Can we streamline it to not read so much of the data set, which it appears to 
be doing?

  With no calendar entries (i.e. removing 
.local/share/evolution/xxx/calendar.ics) the process still uses over 30MB
  (looking at RSS with  ps aux --sort -rss )

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

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

[Desktop-packages] [Bug 1342123] Re: evolution-calendar-factory always running with high memory usage

[Oliver Grawert]

if you have issues with evolution-data-server on a desktop install your
chances are way higher to have some desktop people look at it if you
file a new bug.

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

Title:
  evolution-calendar-factory always running with high memory usage

Status in Canonical System Image:
  Confirmed
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  At boot the process is using over 100MB on my mako (build 129)
  I sync'd a fairly large set of calendar events from google previously

  Does this process need to be running all the time?
  Can we streamline it to not read so much of the data set, which it appears to 
be doing?

  With no calendar entries (i.e. removing 
.local/share/evolution/xxx/calendar.ics) the process still uses over 30MB
  (looking at RSS with  ps aux --sort -rss )

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

[Oliver Grawert]

Looks like there is breakage caused by thus change, see bug #1589006

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

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Fix Committed

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

[Oliver Grawert]

freecad doesnt use any GL to draw the UI, you will simply not have full
functionality (rendering etc) but the app will run

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

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  In Progress
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-361 source package in Xenial:
  In Progress

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1542602] Re: can not boost volume past 100% using vol control applet

[Oliver Grawert]

** Also affects: indicator-sound (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Invalid

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

Title:
  can not boost volume past 100% using vol control applet

Status in indicator-sound package in Ubuntu:
  New
Status in ubuntu-wallpapers package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 and with the latest update the volume control
  behavior changed.  Before I could use the volume applet to increase
  the vol past 100%.  I can no longer do that.  The applet control stops
  at 100.  If I choose 'Sound Settings' I can up the vol past 100%.

   4.2.0-27-generic
  Lenovo Flex 2  

  From  lshw, two references to sound

  Haswell-ULT HD Audio Controller
  8 Series HD Audio Controller

  
  pulseaudio:
Installed: 1:6.0-0ubuntu13
Candidate: 1:6.0-0ubuntu13
Version table:
   *** 1:6.0-0ubuntu13 0
  500 http://es.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1542602/+subscriptions

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

[Desktop-packages] [Bug 1478506] Re: Apps change audio output role all the time

[Oliver Grawert]

If we would have a volume-slider Qt/QML element that allows you to pick the 
role it manages you could have a volume control in the app (like i described in 
bug #1389761) ...
that would indeed not fix indicator sound (or volume button) behaviour unless 
you limit its focus to certain roles.

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

Title:
  Apps change audio output role all the time

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, install the app Maroon in trouble from the app store
  and play it a little with having sound enabled. Press the volume down
  hardware button on the phone. It will temporarily decrease the volume.
  However, whenever a new item comes into the scene, it will be on 100%
  volume again.

  Setting the system volume to 0 should keep everything at 0.

  
  Please note that this app does *not* have any code to set the volume! Also 
this app is one of the upstream Qt QML example demo apps, so this is really how 
QML apps are supposed to work (in other words, it is not a badly implemented 
app, but really an issue in the system)

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

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

[Desktop-packages] [Bug 1468811] Re: headphone volume auto-set to loudest

[Oliver Grawert]

bug #1478506 seems to be related here...

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

Title:
  headphone volume auto-set to loudest

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Music App:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  since OTA-4 i get the headphone volume randomly set to the highest
  setting. it can only be set when headphones are plugged in and
  playback has started, so I have no way of checking beforehand. (of
  course I can choose to keep headphones away from the ears.)

  
  this occurs both in the music app and in the podcast app podbird. also occurs 
sometimes during playback, when notification sound is played. 

  not a security issue, but rather a quite serious hearing health issue. 
  I'm on BQ Aquaris E4.5

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

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

[Desktop-packages] [Bug 1376212] Re: BQ Aquaris E4.5 Android Phone not recognised by libmtp

[Oliver Grawert]

** Also affects: libmtp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  BQ Aquaris E4.5 Android Phone not recognised by libmtp

Status in libmtp package in Ubuntu:
  Confirmed
Status in libmtp source package in Trusty:
  New

Bug description:
  The bq Aquaris E4.5 phone is not recognised when in MTP file mode by
  Ubuntu.

   idVendor=2a47, idProduct=2012

  Tested on a trusty/14.04 laptop with all recommended apt-get update's
  as of 5th Sep (sorry for long reporting delay).

  Reproduction Proceedure:

   - Plug a BQ Aquaris E4.5 Android phone into the Ubuntu desktop via a USB 
cable
   - Expect to see a natuilus window pop up, with the option to browse and copy 
files to the phone's file system

   - Actual result: no response from the Ubuntu host.

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

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

[Desktop-packages] [Bug 1395682] Re: Ciborium is disconnecting over night and looping causing multiple messages

[Oliver Grawert]

i see a lot of power related MMC messages there ...

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

Title:
  Ciborium is disconnecting over night and looping causing multiple
  messages

Status in “ciborium” package in Ubuntu:
  Incomplete
Status in “upower” package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Add an sd card
  2. Leave the phone over night

  EXPECTED:
  No messages in the morning

  ACTUAL:
  see screenshot

  http://paste.ubuntu.com/9211733/  this shows some issues with upower
  maybe turning the sd card off.

  I will try taking the card out cleaning it and seeing if there is an
  issue with it tonight

  This has happened ever night since Wednesday 19 so Thursday the 20
  morning was the first time I saw it.

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

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

[Desktop-packages] [Bug 1394919] [NEW] constant crash in trying to collect info for recoverable error

[Oliver Grawert]

Public bug reported:

since a few days my phone started producing a 
/var/crash/_usr_share_apport_recoverable_problem.32011.crash

i see the timestamp updated multiple times and the matching PID from the
traceback seems to be cgmanager

https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4
https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81
https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2

are the respective whoopsie uploads.

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

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

** Affects: apport (Ubuntu RTM)
 Importance: Undecided
 Status: New

** Affects: cgmanager (Ubuntu RTM)
 Importance: Undecided
 Status: New

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

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

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

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

Title:
  constant crash in trying to collect info for recoverable error

Status in “apport” package in Ubuntu:
  New
Status in “cgmanager” package in Ubuntu:
  New
Status in “apport” package in Ubuntu RTM:
  New
Status in “cgmanager” package in Ubuntu RTM:
  New

Bug description:
  since a few days my phone started producing a 
  /var/crash/_usr_share_apport_recoverable_problem.32011.crash

  i see the timestamp updated multiple times and the matching PID from
  the traceback seems to be cgmanager

  https://errors.ubuntu.com/oops/c25e8678-70f2-11e4-976f-fa163e4aaad4
  https://errors.ubuntu.com/oops/94398858-70a0-11e4-906f-fa163e339c81
  https://errors.ubuntu.com/oops/235b2dd0-7118-11e4-837c-fa163e5bb1a2

  are the respective whoopsie uploads.

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

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

[Desktop-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

[Oliver Grawert]

it is tagged ota-1, so it will land, just not in one of the next two
promoted images, which just delays it by two weeks

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Desktop-packages] [Bug 258110] Re: Camera application cannot record video

[Oliver Grawert]

** Changed in: cmpc
   Status: In Progress = Won't Fix

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

Title:
  Camera application cannot record video

Status in Cheese Camera Application:
  Expired
Status in Application and image devlopment around the Classmate PC:
  Won't Fix
Status in “cheese” package in Ubuntu:
  Fix Released
Status in “gstreamer0.10” package in Ubuntu:
  Fix Released
Status in “cheese” source package in Hardy:
  Fix Released
Status in “gstreamer0.10” source package in Hardy:
  Fix Released
Status in “cheese” source package in Intrepid:
  Fix Released
Status in “gstreamer0.10” source package in Intrepid:
  Fix Released

Bug description:
  Run cheese, select video and start recording.Try clicking stop
  recording but there's no response.

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

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

[Desktop-packages] [Bug 1321650] Re: wifi not connecting network on Nexus 4 image #28

[Oliver Grawert]

this snippet looks most interesting in teh syslog ...


May 21 08:20:23 ubuntu-phablet wpa_supplicant[2458]: wlan0: Trying to associate 
with SSID 'darline'
May 21 08:20:23 ubuntu-phablet kernel: [ 1247.147016] wlan: [1284:E :PE ] 
limProcessAuthFrame: 1302: received Auth frame from peer with failure code 13 
90:84:0d:f3:74:15
May 21 08:20:23 ubuntu-phablet kernel: [ 1247.147230] wlan: [1284:E :PE ] 
limProcessMlmAuthCnf: 622: Auth Failure occurred.
May 21 08:20:23 ubuntu-phablet kernel: [ 1247.147352] wlan: [1284:E :PE ] 
limDeactivateAndChangeTimer: 1438: Deactivated probe after hb timer
May 21 08:20:23 ubuntu-phablet NetworkManager[1262]: info (wlan0): supplicant 
interface state: disconnected - associating
May 21 08:20:23 ubuntu-phablet wpa_supplicant[2458]: wlan0: 
CTRL-EVENT-ASSOC-REJECT bssid=90:84:0d:f3:74:15 status_code=1
May 21 08:20:23 ubuntu-phablet kernel: [ 1247.157637] wlan: connection failed 
with 90:84:0d:f3:74:15 reason:1 and Status:9
May 21 08:20:23 ubuntu-phablet NetworkManager[1262]: info (wlan0): supplicant 
interface state: associating - disconnected

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  wifi not connecting network on Nexus 4 image #28

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Since some images, none of both of my Nexus 4 can't connect to Internet over 
the wifi.
  As it seems I'm the only one to have this issue, it may be linked to the 
network I'm using.
  It's a shared network from an iMac, using a WEP key at 128bits.
  It used to work for a long (and I'm using it right now from my Ubuntu 14.04 
laptop).
  Attached is the dmesg of one of the devices.

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

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

[Desktop-packages] [Bug 1319906] Re: indicator-network show wifi disabled on a bootstrap install or ota update on 31

[Oliver Grawert]

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Critical

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

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

Title:
  indicator-network show wifi disabled on a bootstrap install or ota
  update on 31

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Indicator network shows wifi disabled on a fresh bootstrapped install
  or on an ota update.

  Enabling the wifi will aloow it to search and connect to a new
  network.

  On reboot wifi is disabled again on manta and flo but not on mako by
  the look of it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu10
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.2-0ubuntu3
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu May 15 15:38:10 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2014-05-15 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140515.1)
  IpRoute:
   default via 10.86.112.74 dev rmnet_usb0  proto static 
   10.86.112.0/24 dev rmnet_usb0  proto kernel  scope link  src 10.86.112.73  
metric 13
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2014-05-15T09:58:23
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   /234308403223936/context3 00f83d8b-6636-7d5d-3266-70a1176b7bff   gsm 
  0never  yes   yes
/org/freedesktop/NetworkManager/Settings/1
   /234308403223936/context1 a12a5a56-2d89-315e-38b0-9d3e8d4fe0e5   gsm 
  1400168303   Thu 15 May 2014 03:38:23 PM UTCyes   yes
/org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1307981] Re: [touch] randomly messed up routing with recent trusty images

[Oliver Grawert]

lxc-android-config (0.163) utopic; urgency=medium

  * add /etc/NetworkManager/dispatcher.d/02default_route_workaround to make
sure the default route is always reset when an interface change is
detected (LP: #1307981)

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lxc-android-config (Ubuntu)
   Status: New = Fix Released

** Changed in: lxc-android-config (Ubuntu)
   Importance: Undecided = High

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed = Won't Fix

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

Title:
  [touch] randomly messed up routing with recent trusty images

Status in “lxc-android-config” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Won't Fix

Bug description:
  I have no clue when exactly it started (probably before image 290),
  but since a while i experience random issues where the browser
  suddenly doesnt find websites anymore ... digging deeper i can see
  that the routing table is completely messed up having two default
  routes:

  root@ubuntu-phablet:~# route -n 
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

  i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
  afer a reboot the routing is normal:

  root@ubuntu-phablet:~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1307981/+subscriptions

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

[Desktop-packages] [Bug 1307981] Re: [touch] randomly messed up routing with recent trusty images

[Oliver Grawert]

on boot my routing is usually fine ... what i see today is:

- boot with proper default route over WLAN, mobile is enabled but not owning 
the default route.
- leave the phone next to me in the office or living room (both covered by the 
same WLAN) and randomly pick up the device to check G+ or read some news in a 
webapp
- two or three times throughout the day notice that suddenly the app pops up 
the internal error page, checking the routing then via adb shows the two 
default routes, disabling and re-enabling WLAN then sets the route properly 
again.
- while i *have* seen the routing being broken from boot on once or twice this 
is a very rare case, usually routing is fine on boot and breaks later (though 
pats comments above indicate that this is different for him)

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

Title:
  [touch] randomly messed up routing with recent trusty images

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  I have no clue when exactly it started (probably before image 290),
  but since a while i experience random issues where the browser
  suddenly doesnt find websites anymore ... digging deeper i can see
  that the routing table is completely messed up having two default
  routes:

  root@ubuntu-phablet:~# route -n 
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

  i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
  afer a reboot the routing is normal:

  root@ubuntu-phablet:~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

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

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

[Desktop-packages] [Bug 1307981] Re: [touch] randomly messed up routing with recent trusty images

[Oliver Grawert]

i just noticed bug 1314410

do not rely on a webapp for testing if your connectivity is back
(restarting the app works fine indeed, but the button on the error page
nor the refresh option from the hud does not)

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

Title:
  [touch] randomly messed up routing with recent trusty images

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I have no clue when exactly it started (probably before image 290),
  but since a while i experience random issues where the browser
  suddenly doesnt find websites anymore ... digging deeper i can see
  that the routing table is completely messed up having two default
  routes:

  root@ubuntu-phablet:~# route -n 
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

  i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
  afer a reboot the routing is normal:

  root@ubuntu-phablet:~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

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

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

[Desktop-packages] [Bug 1307981] Re: [touch] randomly messed up routing with recent trusty images

[Oliver Grawert]

ogra@styx:~/apps$ adb shell ip route 
default via 37.83.18.26 dev rmnet_usb1 
default via 192.168.2.1 dev wlan0  proto static 
37.83.18.24/30 dev rmnet_usb1  proto kernel  scope link  src 37.83.18.25 
192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.78  metric 9 
ogra@styx:~/apps$

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

Title:
  [touch] randomly messed up routing with recent trusty images

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I have no clue when exactly it started (probably before image 290),
  but since a while i experience random issues where the browser
  suddenly doesnt find websites anymore ... digging deeper i can see
  that the routing table is completely messed up having two default
  routes:

  root@ubuntu-phablet:~# route -n 
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

  i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
  afer a reboot the routing is normal:

  root@ubuntu-phablet:~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

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

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

[Desktop-packages] [Bug 1308459] [NEW] on touch rfkill needs to ship the /var/lib/rfkill directory or create it from a postinst script

[Oliver Grawert]

Public bug reported:

rfkill expects to be able to put state files into /var/lib/rfkill, for
this the upstart job has a mkdir -p /var/lib/rfkill line ...

on touch writable dirs need to exist on boot to be made writable. the
above mkdir will just fail. the package either needs to ship this path
via debian/rfkill.dirs or it needs to create it from the postinst script
so that the directory is there on first boot of a phone.

** Affects: rfkill (Ubuntu)
 Importance: High
 Status: New

** Changed in: rfkill (Ubuntu)
   Importance: Undecided = High

** Summary changed:

- on touch rfkill needs to ship the /var/lib/rfkill direcotry or create it from 
a postinst script
+ on touch rfkill needs to ship the /var/lib/rfkill directory or create it from 
a postinst script

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

Title:
  on touch rfkill needs to ship the /var/lib/rfkill directory or create
  it from a postinst script

Status in “rfkill” package in Ubuntu:
  New

Bug description:
  rfkill expects to be able to put state files into /var/lib/rfkill, for
  this the upstart job has a mkdir -p /var/lib/rfkill line ...

  on touch writable dirs need to exist on boot to be made writable. the
  above mkdir will just fail. the package either needs to ship this path
  via debian/rfkill.dirs or it needs to create it from the postinst
  script so that the directory is there on first boot of a phone.

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

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

[Desktop-packages] [Bug 1235436] Re: /etc/init/apport-noui.conf is non-functional on the phone

[Oliver Grawert]

this was never fixed, apport needs to create the dir from postinst or
ship it in debian/apport.dirs, writable-paths only works with existing
directories by design, so the change to lxc-android-config was a no-op.

additionally there are also the lines:

env MATCH=NULL
 [ $MATCH = NULL ]  exit 0

in the apport-noui.conf job, so it would always exit anyway.

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

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

Title:
  /etc/init/apport-noui.conf is non-functional on the phone

Status in “apport” package in Ubuntu:
  Confirmed

Bug description:
  I've uploaded a fix to upstart for bug #1235387, but /etc/init/apport-
  noui.conf in the apport-noui package still doesn't work here.  There's
  no /etc/apport/autoreport in the image, so it fails on the first line
  of the script:

  [ -e /etc/apport/autoreport ] || exit 0

  Apparently further integration work is needed.

  The job is also structured quite confusingly, with an 'instance' that
  means the job will be launched once for each file found in /var/crash
  - even though the command it runs is called /usr/share/apport
  /whoopsie-upload-*all*.  So we'll get multiple copies of this running
  in parallel the first time it successfully triggers.  I suspect this
  may result in multiple submissions, as whoopsie sees the .upload stamp
  updated?

  In any case, I don't see the point of having this as a separate
  upstart job from whoopsie at all.  whoopsie is already monitoring the
  /var/crash directory with inotify; it should just check
  /etc/apport/autoreport itself (or maybe this should be
  /etc/whoopsie/autoreport?), and if present, monitor the .crash files
  directly.

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

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

[Desktop-packages] [Bug 1307981] [NEW] [touch] randomly messed up routing with recent trusty images

[Oliver Grawert]

Public bug reported:

I have no clue when exactly it started (probably before image 290), but
since a while i experience random issues where the browser suddenly
doesnt find websites anymore ... digging deeper i can see that the
routing table is completely messed up having two default routes:

root@ubuntu-phablet:~# route -n 
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
afer a reboot the routing is normal:

root@ubuntu-phablet:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: New

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = High

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

Title:
  [touch] randomly messed up routing with recent trusty images

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  I have no clue when exactly it started (probably before image 290),
  but since a while i experience random issues where the browser
  suddenly doesnt find websites anymore ... digging deeper i can see
  that the routing table is completely messed up having two default
  routes:

  root@ubuntu-phablet:~# route -n 
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 37.85.159.174   0.0.0.0 UG0  00 
rmnet_usb1
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.85.159.172   0.0.0.0 255.255.255.252 U 0  00 
rmnet_usb1
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

  i did not roam or switch networks, this phone was constantly on wlan in the 
same room.
  afer a reboot the routing is normal:

  root@ubuntu-phablet:~# route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.2.1 0.0.0.0 UG0  00 wlan0
  37.84.75.1400.0.0.0 255.255.255.252 U 13 00 
rmnet_usb0
  192.168.2.0 0.0.0.0 255.255.255.0   U 9  00 wlan0

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

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

[Desktop-packages] [Bug 1185565] Re: Indicators should have Upstart jobs

[Oliver Grawert]

seems indicator-messages was forgotten (it significantly sticks out on the 
Ubuntu Touch bootcharts).
i added a task for it so it can be fixed before 14.40

** Also affects: indicator-messages (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Indicators should have Upstart jobs

Status in Application Indicators:
  Fix Committed
Status in The Date and Time Indicator:
  Fix Released
Status in Indicator Location:
  Fix Committed
Status in Network Menu:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in The Session Menu:
  Fix Released
Status in Sound Menu:
  Fix Released
Status in The Sync Menu:
  Fix Committed
Status in Libindicator:
  Confirmed
Status in Unity:
  Fix Released
Status in “indicator-application” package in Ubuntu:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-location” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  New
Status in “indicator-power” package in Ubuntu:
  Fix Released
Status in “indicator-session” package in Ubuntu:
  Fix Released
Status in “indicator-sound” package in Ubuntu:
  Fix Released
Status in “indicator-sync” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “unity-greeter” package in Ubuntu:
  Fix Released

Bug description:
  Indicators should move over to using the upstart jobs to get better
  logging and management of their processes.

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

** Attachment added: lightdm.log
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1285234/+attachment/3999245/+files/lightdm.log

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

** Attachment added: /etc/lightdm/lightdm.conf.d/52-ubuntu-touch.conf
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1285234/+attachment/3999260/+files/52-ubuntu-touch.conf

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

** Attachment added: unity-system-compositor.log
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1285234/+attachment/3999246/+files/unity-system-compositor.log

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

Note that this setup uses a wrapper script to start unity-system-
compositor ... attaching this as well (i guess lightdm doesnt have the
right PID for u-s-c due it being spawned from a subshell)

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

** Attachment added: usc-wrapper
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1285234/+attachment/3999256/+files/usc-wrapper

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] [NEW] lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

Public bug reported:

using stop lightdm on an ubuntu touch device leaves the unity-system-
compositor process running, starting lightdm later again fires up a new
unity-system-compositor process.

(adding something like pkill unity-system-compositor into the post-
stop script block in the upstart job actually causes a hard reboot of
the device (as any occasion when stopping the u-s-c, doesnt only happen
when stopped from lightdm)

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

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1285234] Re: lightdm on touch leaves a unity-system-compositor process around

[Oliver Grawert]

see also bug 1285236

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

Title:
  lightdm on touch leaves a unity-system-compositor process around

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  using stop lightdm on an ubuntu touch device leaves the unity-
  system-compositor process running, starting lightdm later again fires
  up a new unity-system-compositor process.

  (adding something like pkill unity-system-compositor into the post-
  stop script block in the upstart job actually causes a hard reboot of
  the device (as any occasion when stopping the u-s-c, doesnt only
  happen when stopped from lightdm)

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

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

[Desktop-packages] [Bug 1283326] Re: u-s-c crashes on first boot on flo, stuck on Google boot screen

[Oliver Grawert]

opening a task against lightdm, we need to identify why we need to delay
the startup by nearly two seconds (which depending on runlevel does ...
we do not use runlevels and should have a proper dependency chain
instread) and add a proper dependency to the upstart override job for
the actually needed prerequisite.

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

** Changed in: lightdm (Ubuntu)
   Importance: Undecided = High

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

Title:
  u-s-c crashes on first boot on flo, stuck on Google boot screen

Status in “lightdm” package in Ubuntu:
  New
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released

Bug description:
  This seems to always happen to me on first boot specifically,
  typically rebooting once will allow it to boot properly

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-system-compositor 0.0.2+14.04.20140212.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 21:13:41 2014
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-07-26 (210 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity-system-compositor
  UpgradeStatus: Upgraded to trusty on 2013-11-21 (92 days ago)
  version.libdrm: libdrm2 2.4.52-1
  version.lightdm: lightdm 1.9.8-0ubuntu1
  version.mesa: libegl1-mesa-dev 10.1.0~rc1-1ubuntu4

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

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

[Desktop-packages] [Bug 1283326] Re: u-s-c crashes on first boot on flo, stuck on Google boot screen

[Oliver Grawert]

It would also be intresting to know why the demo image behaves different
here, I tested this change against an Image from the normal archive
builds where it did not expose any issues on flo.

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

Title:
  u-s-c crashes on first boot on flo, stuck on Google boot screen

Status in “lightdm” package in Ubuntu:
  New
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released

Bug description:
  This seems to always happen to me on first boot specifically,
  typically rebooting once will allow it to boot properly

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-system-compositor 0.0.2+14.04.20140212.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 21 21:13:41 2014
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-07-26 (210 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity-system-compositor
  UpgradeStatus: Upgraded to trusty on 2013-11-21 (92 days ago)
  version.libdrm: libdrm2 2.4.52-1
  version.lightdm: lightdm 1.9.8-0ubuntu1
  version.mesa: libegl1-mesa-dev 10.1.0~rc1-1ubuntu4

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

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

[Desktop-packages] [Bug 1282051] [NEW] Camera app on maguro flickering degraded massively with latest Unity

[Oliver Grawert]

Public bug reported:

After an update of libunity-core-6.0-8 to libunity-core-6.0-9 the
already existing flickering in the camera-app on maguro degraded so much
that the app got unusable (looks like a strobe now). Seemingly the
rendering frequency was raised with this update.

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


** Tags: r189 touch

** Package changed: unity8 (Ubuntu) = unity (Ubuntu)

** Summary changed:

- Camera app on maguro flickering degraded massively with latest Unity8 
+ Camera app on maguro flickering degraded massively with latest Unity

** Tags added: r189 touch

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

Title:
  Camera app on maguro flickering degraded massively with latest Unity

Status in “unity” package in Ubuntu:
  New

Bug description:
  After an update of libunity-core-6.0-8 to libunity-core-6.0-9 the
  already existing flickering in the camera-app on maguro degraded so
  much that the app got unusable (looks like a strobe now). Seemingly
  the rendering frequency was raised with this update.

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

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

[Desktop-packages] [Bug 1255530] Re: system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts

[Oliver Grawert]

obviously going to the settings app, switching my language setting back
and forth and rebooting fixes it. my clock is now properly staying at
24h time.

seemingly we now set more variables in /home/phablet/.pam_environment than we 
did at the time i was firstly setting up the image.
during OTA upgrade the new settings were not updated inside this config file so 
that parts of my settings flipped back to english.

to handle this case in the future (we might have other cases where pam
settings of a user need upgrading even on released images) the session-
migration tool should get a backend to handle this.

i am turning this into a wishlist bug against session-migration, the
indicator task is solved.

** Also affects: session-migration (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: session-migration (Ubuntu)
   Importance: Undecided = Wishlist

** Changed in: indicator-datetime (Ubuntu)
   Status: New = Invalid

** Summary changed:

- system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock 
starts
+ /home/phablet/.pam_environment does not get updated on OTA upgrades

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

Title:
  /home/phablet/.pam_environment does not get updated on OTA upgrades

Status in “indicator-datetime” package in Ubuntu:
  Invalid
Status in “session-migration” package in Ubuntu:
  New

Bug description:
  starting my phone set to german language the lock screen properly
  shows a 24h clock ...

  as aoon as the panel clock shows up, the lockscreen format (and all
  other places where the time is shown in the UI) is swithcing to AM/PM
  12h time format.

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

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

[Desktop-packages] [Bug 1256062] [NEW] session-migration needs to be handled by upstart session

[Oliver Grawert]

Public bug reported:

while we ship session-migration on the ubuntu touch phone, the original
code was developed to hook into gnome-session. since we do not ship
gnome-session on the phone images session-migration never runs.
therefore we need to have it integrated with the upstart-user-session
now.

** Affects: session-migration (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  session-migration needs to be handled by upstart session

Status in “session-migration” package in Ubuntu:
  New

Bug description:
  while we ship session-migration on the ubuntu touch phone, the
  original code was developed to hook into gnome-session. since we do
  not ship gnome-session on the phone images session-migration never
  runs. therefore we need to have it integrated with the upstart-user-
  session now.

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

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

[Desktop-packages] [Bug 1248143] [NEW] the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases

[Oliver Grawert]

Public bug reported:

with image 11 the fix for the above bug landed.
it causes the systemsettle test to fail on mako for any test where 
friends-service is involved.

http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/

this currently causes a regression in the overall pass rate of the image
builds which blocks us from releasing new touch images. please revert
the change or fix it in a non-regressive way.

** Affects: friends (Ubuntu)
 Importance: High
 Assignee: Robert Bruce Park (robru)
 Status: Confirmed

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

Title:
  the fix for Bug #1238083 seems to cause the systemsettle tests on mako
  to fail, blocking image releases

Status in “friends” package in Ubuntu:
  Confirmed

Bug description:
  with image 11 the fix for the above bug landed.
  it causes the systemsettle test to fail on mako for any test where 
friends-service is involved.

  
http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/
  
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/

  this currently causes a regression in the overall pass rate of the
  image builds which blocks us from releasing new touch images. please
  revert the change or fix it in a non-regressive way.

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

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

[Desktop-packages] [Bug 1248143] Re: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases

[Oliver Grawert]

** Changed in: friends (Ubuntu)
   Importance: Undecided = High

** Changed in: friends (Ubuntu)
 Assignee: (unassigned) = Robert Bruce Park (robru)

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

Title:
  the fix for Bug #1238083 seems to cause the systemsettle tests on mako
  to fail, blocking image releases

Status in “friends” package in Ubuntu:
  Confirmed

Bug description:
  with image 11 the fix for the above bug landed.
  it causes the systemsettle test to fail on mako for any test where 
friends-service is involved.

  
http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/
  
https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/

  this currently causes a regression in the overall pass rate of the
  image builds which blocks us from releasing new touch images. please
  revert the change or fix it in a non-regressive way.

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Oliver Grawert]

[   59.264921] type=1400 audit(1380291018.856:28): apparmor=STATUS
info=failed to unpack profile error=-71 pid=781 comm=apparmor_parser
name=/usr/lib/NetworkManager/nm-dhcp-client.action offset=155

this line from dmesg looks very suspicious ... adding
apparmor.enable=0 to the kernel cmdline (to diable apparmor
completely) might help

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40  stuw iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

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

[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander

[Oliver Grawert]

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  wifi not working on Saucy Salamander

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu 13.10 installed from daily image have wifi not working, even
  with BT disabled.

  confirmed by stuw on IRC at Sun Sep 22
  15:40  stuw iz1glg, I saw similar problem, but I don't know the reason and 
solution.

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

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

[Desktop-packages] [Bug 1226997] [NEW] lighdm does not get along with switchable Mir and surfaceflinger sessions

[Oliver Grawert]

Public bug reported:

we tried to use lp:~mterry/session-manager-touch/lightdm-switch on the ubuntu 
touch images. 
this code was written prior to adding Mir as a switchable (test) option to the 
otherwise surfaceflinger based images.

now that Mir is shipped alongside, lightdm always prefers Mir for the
user session and we lose the ability to use surfaceflinger (which is
supposed to still be the default) completely.

i am not sure how hard it is to update the patch to support that
usecase. in case it is not, we need to wait for Mir to become the
default on the touch images before merging.

** Affects: lightdm (Ubuntu)
 Importance: High
 Assignee: Michael Terry (mterry)
 Status: New

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) = Michael Terry (mterry)

** Changed in: lightdm (Ubuntu)
   Importance: Undecided = High

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

Title:
  lighdm does not get along with switchable Mir and surfaceflinger
  sessions

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  we tried to use lp:~mterry/session-manager-touch/lightdm-switch on the ubuntu 
touch images. 
  this code was written prior to adding Mir as a switchable (test) option to 
the otherwise surfaceflinger based images.

  now that Mir is shipped alongside, lightdm always prefers Mir for the
  user session and we lose the ability to use surfaceflinger (which is
  supposed to still be the default) completely.

  i am not sure how hard it is to update the patch to support that
  usecase. in case it is not, we need to wait for Mir to become the
  default on the touch images before merging.

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

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

[Desktop-packages] [Bug 1210083] Re: volume control does not work on Galaxy S2

[Oliver Grawert]

I agree, pulse had a really hard hit on the system that made it close to
unusable with udev-detect in place.

For the further stuff i agree we should wait, since the changes are
supposed to land this month anyway ...

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

Title:
  volume control does not work on Galaxy S2

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
  load-module module-udev-detect use_ucm=0
  is commented out in /etc/pulse/default.pa

  while pulse starts after this modification, volume control is neither
  possible through the indicator (no UI elements at all) nor via
  alsamixer or the hardware butoons. Videos play with sound, the camera
  snap sound works too, but volume can not be controlled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu1
  Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
  NonfreeKernelModules: dhd Si4709_driver
  ApportVersion: 2.11-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Aug  8 12:02:06 2013
  InstallationDate: Installed on 2013-08-01 (6 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

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

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

[Desktop-packages] [Bug 1210083] Re: volume control does not work on Galaxy S2

[Oliver Grawert]

** Also affects: android-audiosystem (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- volume control does not work on Galaxy S2
+ volume control does not work on Galaxy S2 and pulseaudio misbehaves

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

Title:
  volume control does not work on Galaxy S2 and pulseaudio misbehaves

Status in “android-audiosystem” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
  load-module module-udev-detect use_ucm=0
  is commented out in /etc/pulse/default.pa

  while pulse starts after this modification, volume control is neither
  possible through the indicator (no UI elements at all) nor via
  alsamixer or the hardware butoons. Videos play with sound, the camera
  snap sound works too, but volume can not be controlled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu1
  Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
  NonfreeKernelModules: dhd Si4709_driver
  ApportVersion: 2.11-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Aug  8 12:02:06 2013
  InstallationDate: Installed on 2013-08-01 (6 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1210083/+subscriptions

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

[Desktop-packages] [Bug 1210083] [NEW] volume control does not work on Galaxy S2

[Oliver Grawert]

Public bug reported:

In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
load-module module-udev-detect use_ucm=0
is commented out in /etc/pulse/default.pa

while pulse starts after this modification, volume control is neither
possible through the indicator (no UI elements at all) nor via alsamixer
or the hardware butoons. Videos play with sound, the camera snap sound
works too, but volume can not be controlled.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: pulseaudio 1:4.0-0ubuntu1
Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
NonfreeKernelModules: dhd Si4709_driver
ApportVersion: 2.11-0ubuntu1
Architecture: armhf
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
Date: Thu Aug  8 12:02:06 2013
InstallationDate: Installed on 2013-08-01 (6 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
MarkForUpload: True
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Assignee: David Henningsson (diwic)
 Status: New


** Tags: apport-bug armhf saucy

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

Title:
  volume control does not work on Galaxy S2

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
  load-module module-udev-detect use_ucm=0
  is commented out in /etc/pulse/default.pa

  while pulse starts after this modification, volume control is neither
  possible through the indicator (no UI elements at all) nor via
  alsamixer or the hardware butoons. Videos play with sound, the camera
  snap sound works too, but volume can not be controlled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu1
  Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
  NonfreeKernelModules: dhd Si4709_driver
  ApportVersion: 2.11-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Aug  8 12:02:06 2013
  InstallationDate: Installed on 2013-08-01 (6 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

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

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

[Desktop-packages] [Bug 1210083] Re: volume control does not work on Galaxy S2

[Oliver Grawert]

http://paste.ubuntu.com/5962040/ has the output of the alsa-info.sh
schellscript as described on https://wiki.ubuntu.com/Audio/AlsaInfo

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) = David Henningsson (diwic)

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

Title:
  volume control does not work on Galaxy S2

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
  load-module module-udev-detect use_ucm=0
  is commented out in /etc/pulse/default.pa

  while pulse starts after this modification, volume control is neither
  possible through the indicator (no UI elements at all) nor via
  alsamixer or the hardware butoons. Videos play with sound, the camera
  snap sound works too, but volume can not be controlled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu1
  Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
  NonfreeKernelModules: dhd Si4709_driver
  ApportVersion: 2.11-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Aug  8 12:02:06 2013
  InstallationDate: Installed on 2013-08-01 (6 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

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

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

[Desktop-packages] [Bug 1210083] Re: volume control does not work on Galaxy S2

[Oliver Grawert]

i dont, thats how it is on teh toumch images by default ... the android
type is provided by libandroid-audiosystem-asound2 which talks to the
container

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

Title:
  volume control does not work on Galaxy S2

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  In the Ubuntu Touch port to the Samsung Galaxy S2 phone pulseaudio misbehaves 
until 
  load-module module-udev-detect use_ucm=0
  is commented out in /etc/pulse/default.pa

  while pulse starts after this modification, volume control is neither
  possible through the indicator (no UI elements at all) nor via
  alsamixer or the hardware butoons. Videos play with sound, the camera
  snap sound works too, but volume can not be controlled.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu1
  Uname: Linux 3.0.64-CM-g27bbb67-dirty armv7l
  NonfreeKernelModules: dhd Si4709_driver
  ApportVersion: 2.11-0ubuntu1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Thu Aug  8 12:02:06 2013
  InstallationDate: Installed on 2013-08-01 (6 days ago)
  InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf 
(20130801)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2013-08-07T19:50:18.924314

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

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

[Desktop-packages] [Bug 989846] Re: libmad causes mpd to seg fault on update

[Oliver Grawert]

follow https://wiki.ubuntu.com/StableReleaseUpdates to get a 12.04
update

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

Title:
  libmad causes mpd to seg fault on update

Status in “libmad” package in Ubuntu:
  Fix Released
Status in “libmad” source package in Precise:
  New
Status in “libmad” source package in Quantal:
  New
Status in “libmad” package in Debian:
  New

Bug description:
  This is an 12.04 armhf install on a B7 BeagleBoard.

  mpd version is 0.16.5-1ubuntu4
  libmad version is 0.15.1b-7ubuntu1

  What happens: mpd will start and allow local and remote clients to
  connect as expected.  Requesting a database update with an attached
  client (ie 'mpc update') causes mpd to crash.  Attaching gdb reveals
  seg fault occurs in call to libmad.

  What should happen:  Database should update and mpd should continue to
  run.

  Installing armhf build of libmad0 (0.15.1b-7) from Debian Wheeze
  solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libmad0 0.15.1b-7ubuntu1
  Uname: Linux 3.2.16-x10 armv7l
  ApportVersion: 2.0.1-0ubuntu6
  Architecture: armhf
  Date: Fri Apr 27 11:27:03 2012
  SourcePackage: libmad
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1196729] Re: chromium-browser crashed with SIGILL on ARM (Toshiba AC100)

[Oliver Grawert]

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

** This bug has been marked a duplicate of bug 1196019
   Chromium crashes with the error Illegal instruction (core dumped) with the 
newest apt-get version on Toshiba AC100, lubuntu 13.04

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

Title:
  chromium-browser crashed with SIGILL on ARM (Toshiba AC100)

Status in Enablement project for the Toshiba AC100 NetBook:
  New
Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  I start it, it crashes.

  I hope after I installed chromium-browser-dbg, this bug report
  contains enough info for debugging.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 28.0.1500.52-0ubuntu1.12.04.2
  Uname: Linux 3.0.27-1-ac100 armv7l
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: armhf
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  Date: Tue Jul  2 01:55:24 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu-2d
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 4
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=

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

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

[Desktop-packages] [Bug 1196719] Re: chromium-browser ctashes with ILL

[Oliver Grawert]

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

** This bug is no longer a duplicate of bug 1196729
   chromium-browser crashed with SIGILL on ARM (Toshiba AC100)
** This bug has been marked a duplicate of bug 1196019
   Chromium crashes with the error Illegal instruction (core dumped) with the 
newest apt-get version on Toshiba AC100, lubuntu 13.04

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

Title:
  chromium-browser ctashes with ILL

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  I start it, it crashes.

  I've installed chromium-browser-dbg, because I wanted to provide more
  useful information (with a backtrace), but don't know how to do this
  (because it's not an executable, but rather a script).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 28.0.1500.52-0ubuntu1.12.04.2
  Uname: Linux 3.0.27-1-ac100 armv7l
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: armhf
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  Date: Tue Jul  2 01:31:20 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu-2d
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1196719/+subscriptions

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

[Desktop-packages] [Bug 1196726] Re: chromium-browser crashes with ILL

[Oliver Grawert]

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

** This bug is no longer a duplicate of bug 1196729
   chromium-browser crashed with SIGILL on ARM (Toshiba AC100)
** This bug has been marked a duplicate of bug 1196019
   Chromium crashes with the error Illegal instruction (core dumped) with the 
newest apt-get version on Toshiba AC100, lubuntu 13.04

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

Title:
  chromium-browser crashes with ILL

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  I hope that this report is with a backtrace from gdb because I've
  installed chromium-browser-dbg

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 28.0.1500.52-0ubuntu1.12.04.2
  Uname: Linux 3.0.27-1-ac100 armv7l
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: armhf
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  Date: Tue Jul  2 01:38:42 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu-2d
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 4
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1196726/+subscriptions

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

[Desktop-packages] [Bug 1196705] Re: chromium-browser crashed with SIGILL on ARM (Toshiba AC100)

[Oliver Grawert]

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

** This bug is no longer a duplicate of bug 1196729
   chromium-browser crashed with SIGILL on ARM (Toshiba AC100)
** This bug has been marked a duplicate of bug 1196019
   Chromium crashes with the error Illegal instruction (core dumped) with the 
newest apt-get version on Toshiba AC100, lubuntu 13.04

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

Title:
  chromium-browser crashed with SIGILL on ARM (Toshiba AC100)

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  I wanted to start it, it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 28.0.1500.52-0ubuntu1.12.04.2
  Uname: Linux 3.0.27-1-ac100 armv7l
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: armhf
  ChromiumPrefs:
   browser/check_default_browser = **unset** (no such key yet)
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  CrashCounter: 1
  Date: Tue Jul  2 01:06:30 2013
  Desktop-Session:
   DESKTOP_SESSION = ubuntu-2d
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  MarkForUpload: True
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 4
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/chromium-browser/libs/libv8.so
   ?? ()
   ?? ()
  Title: chromium-browser crashed with SIGILL
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  chromium-default: CHROMIUM_FLAGS=

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1196705/+subscriptions

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

[Desktop-packages] [Bug 1116791] Re: xterm and gnome-terminal should not be dependencies

[Oliver Grawert]

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  xterm and gnome-terminal should not be dependencies

Status in “ubuntu-meta” package in Ubuntu:
  Fix Released
Status in “xinit” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
   Hi,

  ubuntu-desktop depends on xterm and gnome-terminal. xorg is a
  dependency as well, and in turn depends on xterm | x-terminal-
  emulator. Something is wrong here. I'd say either removing the depends
  on the terminal emulators from ubuntu-desktop or, in case of xorg
  getting replaced at some point, depend on xterm | x-terminal-emulator
  here too...

  
  Best wishes, Nafallo

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-desktop 1.293
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Tue Feb  5 23:58:17 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-09 (485 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20111007.1)
  MarkForUpload: True
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago)

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

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

[Desktop-packages] [Bug 1116791] Re: xterm and gnome-terminal should not be dependencies

[Oliver Grawert]

i guess at least using x-terminal-emulator as the dep would help so it
is enough to have only one terminal installed

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

Title:
  xterm and gnome-terminal should not be dependencies

Status in “ubuntu-meta” package in Ubuntu:
  Confirmed
Status in “xinit” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
   Hi,

  ubuntu-desktop depends on xterm and gnome-terminal. xorg is a
  dependency as well, and in turn depends on xterm | x-terminal-
  emulator. Something is wrong here. I'd say either removing the depends
  on the terminal emulators from ubuntu-desktop or, in case of xorg
  getting replaced at some point, depend on xterm | x-terminal-emulator
  here too...

  
  Best wishes, Nafallo

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-desktop 1.293
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Tue Feb  5 23:58:17 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-09 (485 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20111007.1)
  MarkForUpload: True
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago)

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

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

[Desktop-packages] [Bug 1116791] Re: xterm and gnome-terminal should not be dependencies

[Oliver Grawert]

oh, and i wonder if instead of breaking xinit for the users that use it
by dropping the dep or demoting xterm to x-terminal-emulator if we could
probably just get away with not shipping it at all on the desktop
(indeed that gets us in debugging hell where users are asked to run
startx to produce a log etc, but we could just document that you have to
install xinit in such cases)

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

Title:
  xterm and gnome-terminal should not be dependencies

Status in “ubuntu-meta” package in Ubuntu:
  Confirmed
Status in “xinit” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
   Hi,

  ubuntu-desktop depends on xterm and gnome-terminal. xorg is a
  dependency as well, and in turn depends on xterm | x-terminal-
  emulator. Something is wrong here. I'd say either removing the depends
  on the terminal emulators from ubuntu-desktop or, in case of xorg
  getting replaced at some point, depend on xterm | x-terminal-emulator
  here too...

  
  Best wishes, Nafallo

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-desktop 1.293
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Tue Feb  5 23:58:17 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-09 (485 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20111007.1)
  MarkForUpload: True
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago)

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

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

[Desktop-packages] [Bug 1116791] Re: xterm and gnome-terminal should not be dependencies

[Oliver Grawert]

added tasks for xorg and xinit, they both have hard deps on xterm, the
xorg team needs to inspect if it is safe to demote it there as well

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

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

** Changed in: xinit (Ubuntu)
   Importance: Undecided = Medium

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  xterm and gnome-terminal should not be dependencies

Status in “ubuntu-meta” package in Ubuntu:
  Confirmed
Status in “xinit” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
   Hi,

  ubuntu-desktop depends on xterm and gnome-terminal. xorg is a
  dependency as well, and in turn depends on xterm | x-terminal-
  emulator. Something is wrong here. I'd say either removing the depends
  on the terminal emulators from ubuntu-desktop or, in case of xorg
  getting replaced at some point, depend on xterm | x-terminal-emulator
  here too...

  
  Best wishes, Nafallo

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubuntu-desktop 1.293
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Tue Feb  5 23:58:17 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-09 (485 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20111007.1)
  MarkForUpload: True
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago)

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

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

[Desktop-packages] [Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts

[Oliver Grawert]

The problem here is that the USB Vendor and DeviceID are the same in
Ubuntu Touch and in android (we use the same kernel so the device
identifies itself the same way). Unlike android Ubuntu Touch doesn't
ship and MTP userspace bits which makes the mount fail. I would expect
gvfs to notice that and not try again as long as there was no reconnect
but instead it fires a new mount attempt every minute (resulting in a
new error popup).

gvfs should definitely not try mounting over and over once it knows
there is no way to mount as long as there was no physical reconnect. We
can't just rip out the device IDs from the rules file as this would
break all devices of the same model using android here. Thenaks for the
info that MTP does not interfere with adb, so in case we decide we will
use it (this is not clear yet, we might decide to just connect as USB
mass storage for more convenient device access) it would go away.

I still think teh behavior is a bug though. Can gvfs be told to not
attempt constant mounting in a loop please ? An USB ID is not enough to
identify if the MTP protocol is supported or not. A single mount attempt
should be enough to notice if there is userspace support.

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

Title:
  please add an option to inhibit gvfs mtp mounts

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  trying to use phablet-flash in raring to flash a phone or tablet (or
  when just running adb shell or adb root from commandline) causes a
  constant reconnect loop of an attached mtp device. it seems adb and
  gvfs try concurrently to establish a connection which results in
  permanent reconnects and a huge amount of mtp popup windows on the
  desktop PC.

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

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

[Desktop-packages] [Bug 1160847] Re: gvfs should not attempt to mount MTP devices in an endless loop (cluttering your desktop with messages)

[Oliver Grawert]

** Summary changed:

- please add an option to inhibit gvfs mtp mounts 
+ gvfs should not attempt to mount MTP devices in an endless loop (cluttering 
your desktop with messages)

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

Title:
  gvfs should not attempt to mount MTP devices in an endless loop
  (cluttering your desktop with messages)

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  trying to use phablet-flash in raring to flash a phone or tablet (or
  when just running adb shell or adb root from commandline) causes a
  constant reconnect loop of an attached mtp device. it seems adb and
  gvfs try concurrently to establish a connection which results in
  permanent reconnects and a huge amount of mtp popup windows on the
  desktop PC.

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

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

[Desktop-packages] [Bug 1160847] [NEW] please add an option to inhibit gvfs mtp mounts

[Oliver Grawert]

Public bug reported:

trying to use phablet-flash in raring to flash a phone or tablet (or
when just running adb shell or adb root from commandline) causes a
constant reconnect loop of an attached mtp device. it seems adb and gvfs
try concurrently to establish a connection which results in permanent
reconnects and a huge amount of mtp popup windows on the desktop PC.

** Affects: gvfs (Ubuntu)
 Importance: High
 Status: Confirmed

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

Title:
  please add an option to inhibit gvfs mtp mounts

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  trying to use phablet-flash in raring to flash a phone or tablet (or
  when just running adb shell or adb root from commandline) causes a
  constant reconnect loop of an attached mtp device. it seems adb and
  gvfs try concurrently to establish a connection which results in
  permanent reconnects and a huge amount of mtp popup windows on the
  desktop PC.

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

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

[Desktop-packages] [Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts

[Oliver Grawert]

so analyzing this a bit deeper, it actually does not have anything to do
with adb but with the fact that gvfs assumes that if an USB device
registers with:

Product: Android
Manufacturer: Android 
(seen in dmesg)

gvfs blindly assumes there is mtp support on the other side ... Ubuntu
Touch currently does not ship any mtp support which causes the gvfs
mount to fail and to retry over and over (once every 60 seconds).

we should:

a) not make gvfs try to mount at all if we detect an adb connection since then 
it is clear that we are in developer or flashing mode.
b) probably make gvfs not try to remount at all if it already knows there is no 
mtp on the responding side
c) at some point ship mtp support on the ubuntu touch images though it has to 
be researched if this interferes with adb which we require for flashing, 
debugging and development currently.

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

Title:
  please add an option to inhibit gvfs mtp mounts

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  trying to use phablet-flash in raring to flash a phone or tablet (or
  when just running adb shell or adb root from commandline) causes a
  constant reconnect loop of an attached mtp device. it seems adb and
  gvfs try concurrently to establish a connection which results in
  permanent reconnects and a huge amount of mtp popup windows on the
  desktop PC.

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

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

[Desktop-packages] [Bug 1160847] Re: please add an option to inhibit gvfs mtp mounts

[Oliver Grawert]

the mtp functionallity seems to be defined in
/lib/udev/rules.d/69-libmtp.rules, a quick and hackish workaround for
affected people using Ubuntu Touch would be to move this rules file out
of /lib/udev/rules.d/ (note that this indeed suppresses all mtp support)

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

Title:
  please add an option to inhibit gvfs mtp mounts

Status in “gvfs” package in Ubuntu:
  Confirmed

Bug description:
  trying to use phablet-flash in raring to flash a phone or tablet (or
  when just running adb shell or adb root from commandline) causes a
  constant reconnect loop of an attached mtp device. it seems adb and
  gvfs try concurrently to establish a connection which results in
  permanent reconnects and a huge amount of mtp popup windows on the
  desktop PC.

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

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

[Desktop-packages] [Bug 974260] Re: Screen brightness does not persist over reboots

[Oliver Grawert]

a new ubuntu-defaults-nexus7 with luxd removed was uploaded ... please
check if the issue still persists on the recent nexus7 images

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: unity-greeter
   Status: New = Invalid

** Also affects: ubuntu-defaults-nexus7 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
   Status: New = Incomplete

** Changed in: ubuntu-nexus7
   Status: Confirmed = Incomplete

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

Title:
  Screen brightness does not persist over reboots

Status in Ubuntu on the Nexus 7:
  Incomplete
Status in Unity Greeter:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Invalid
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  Incomplete

Bug description:
  The brightness of laptop panel is set to minimum instead to maximum when 
system starts. In Natty and older Ubuntu versions it was set to minimum during 
boot, and wold go to maximum just before login screen. In Onerick and Precise 
it just stays at minimum until changed manually to higher values. Laptop is 
connected to power.
   I have Nvidia G105M GPU. On laptop with Intel graphics and Onerick I can't 
reproduce this.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mile   1998 F pulseaudio
  CheckboxSubmission: 9448ae01985a062cb9f7d6705930e25a
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  Date: Thu Apr  5 15:31:51 2012
  HibernationDevice: RESUME=UUID=4dfa8c64-5b19-422d-be25-6053b9b44eab
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111004)
  MachineType: Acer Extensa 5635G
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=67f9c537-e53e-444a-98d0-12afd884e79e ro quiet splash pcie_aspm=force 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-01-07 (88 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  NonfreeKernelModules: nvidia
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-17-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-08-28 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/974260/+subscriptions

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

[Desktop-packages] [Bug 1077260] Re: When using software center search, onboard goes away until text box is reslected after entering 2 chars

[Oliver Grawert]

** Tags removed: quantal

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

Title:
  When using software center search, onboard goes away until text box is
  reslected after entering 2 chars

Status in Onboard on-screen keyboard:
  Invalid
Status in Ubuntu on the Nexus 7:
  Confirmed
Status in “software-center” package in Ubuntu:
  New

Bug description:
  As soon as you start to type in a keyword in the search box, after two
  letters the search routine starts and the keyboard disappears.

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

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

[Oliver Grawert]

The nexus7 issue is fixed (update-notifier does not pop up gksu anymore
but uses pkexec which is usable with onboard).

While gksu is still broken in this regard (so leaving that bug task
open) and xdiagnose still uses it (leaving that open as well) you will
not get into a situation on the nexus7 where xdiagnose runs (and even if
... you wouldnt have any input method at all)

For the nexus7 i consider this issue solved (we will solve it harder by
dropping gksu from the default install though)

** Changed in: ubuntu-defaults-nexus7 (Ubuntu Raring)
   Status: New = Invalid

** Changed in: ubuntu-nexus7
   Status: Confirmed = Fix Released

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in Ubuntu on the Nexus 7:
  Fix Released
Status in “gksu” package in Ubuntu:
  Confirmed
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  Invalid
Status in “xdiagnose” package in Ubuntu:
  New
Status in “gksu” source package in Raring:
  Confirmed
Status in “ubuntu-defaults-nexus7” source package in Raring:
  Invalid
Status in “xdiagnose” source package in Raring:
  New

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/421660/+subscriptions

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

[Desktop-packages] [Bug 974260] Re: Screen brightness does not persist over reboots

[Oliver Grawert]

this bug pre-dates the inclusion of luxd, luxd is just an interim
solution while the function is added to gnome-settings-daemon properly
(with a checkbox to allow manual vs auto-setting of the backlight)

fixes to luxd are indeed welcome in the interim ...

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

Title:
  Screen brightness does not persist over reboots

Status in Ubuntu on the Nexus 7:
  Confirmed
Status in Unity Greeter:
  New
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  The brightness of laptop panel is set to minimum instead to maximum when 
system starts. In Natty and older Ubuntu versions it was set to minimum during 
boot, and wold go to maximum just before login screen. In Onerick and Precise 
it just stays at minimum until changed manually to higher values. Laptop is 
connected to power.
   I have Nvidia G105M GPU. On laptop with Intel graphics and Onerick I can't 
reproduce this.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-22-generic 3.2.0-22.35
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mile   1998 F pulseaudio
  CheckboxSubmission: 9448ae01985a062cb9f7d6705930e25a
  CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
  Date: Thu Apr  5 15:31:51 2012
  HibernationDevice: RESUME=UUID=4dfa8c64-5b19-422d-be25-6053b9b44eab
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111004)
  MachineType: Acer Extensa 5635G
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic 
root=UUID=67f9c537-e53e-444a-98d0-12afd884e79e ro quiet splash pcie_aspm=force 
vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to precise on 2012-01-07 (88 days ago)
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.3311
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnExtensa5635G:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  NonfreeKernelModules: nvidia
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-17-generic x86_64
  UpgradeStatus: Upgraded to quantal on 2012-08-28 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/974260/+subscriptions

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

[Desktop-packages] [Bug 1093543] Re: Battery status behaves erratically

[Oliver Grawert]

testing with all patches applied this seems to fix it ...

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

Title:
  Battery status behaves erratically

Status in Ubuntu on the Nexus 7:
  New
Status in “linux-nexus7” package in Ubuntu:
  Triaged
Status in “upower” package in Ubuntu:
  Fix Released

Bug description:
  I've recently updated my nexus and I've noticed that the battery
  system behaves very erratically. It will say that the battery is at
  43%, 1 hour left, then say it is low with 43% and 1 minute left. At
  some points it says the battery is critical and shuts down the screen,
  only to re-awake soon after saying that the battery is simply low. The
  percentage seems to remain constant, however the time left changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions

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

[Desktop-packages] [Bug 1093543] Re: Battery status behaves erratically

[Oliver Grawert]

a test kernel is here http://people.canonical.com/~ogra/tegra/nexus7
/linux-image-3.1.10-9-nexus7_3.1.10-9.24_armhf.deb

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

Title:
  Battery status behaves erratically

Status in Ubuntu on the Nexus 7:
  New
Status in “linux-nexus7” package in Ubuntu:
  Triaged
Status in “upower” package in Ubuntu:
  Fix Released

Bug description:
  I've recently updated my nexus and I've noticed that the battery
  system behaves very erratically. It will say that the battery is at
  43%, 1 hour left, then say it is low with 43% and 1 minute left. At
  some points it says the battery is critical and shuts down the screen,
  only to re-awake soon after saying that the battery is simply low. The
  percentage seems to remain constant, however the time left changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions

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

[Desktop-packages] [Bug 1093543] Re: Battery status behaves erratically

[Oliver Grawert]

there is no change with this patch, turning back to confirmed

** Changed in: linux-nexus7 (Ubuntu)
   Status: Fix Released = Confirmed

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

Title:
  Battery status behaves erratically

Status in Ubuntu on the Nexus 7:
  New
Status in “linux-nexus7” package in Ubuntu:
  Confirmed
Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  I've recently updated my nexus and I've noticed that the battery
  system behaves very erratically. It will say that the battery is at
  43%, 1 hour left, then say it is low with 43% and 1 minute left. At
  some points it says the battery is critical and shuts down the screen,
  only to re-awake soon after saying that the battery is simply low. The
  percentage seems to remain constant, however the time left changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions

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

[Desktop-packages] [Bug 1093543] Re: Battery status behaves erratically

[Oliver Grawert]

awesome, i will test it during the day ...

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

Title:
  Battery status behaves erratically

Status in Ubuntu on the Nexus 7:
  New
Status in “linux-nexus7” package in Ubuntu:
  Confirmed
Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  I've recently updated my nexus and I've noticed that the battery
  system behaves very erratically. It will say that the battery is at
  43%, 1 hour left, then say it is low with 43% and 1 minute left. At
  some points it says the battery is critical and shuts down the screen,
  only to re-awake soon after saying that the battery is simply low. The
  percentage seems to remain constant, however the time left changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions

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

[Desktop-packages] [Bug 1093543] Re: Battery status behaves erratically

[Oliver Grawert]

testing a kernel with teh above patch doesnt seem to fix it either ...
but i made an intresting observation:

right after first boot
ogra@nexus7:~$ upower -d |grep energy-full:
energy-full: 73.66 Wh

the energy-full value actually should be a fixed value coming from the
battery describing the upper charge level...

after a reboot:

ogra@nexus7:~$ upower -d |grep energy-full:
energy-full: 69.42 Wh

and indeed the battery applet (with show time set in the options)
immediately show 100% charge at boot (even though thats nonsense indeed)

so i think our base value used to compute the time in upower is reported
wrongly (or read wrongly by upower)

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

Title:
  Battery status behaves erratically

Status in Ubuntu on the Nexus 7:
  New
Status in “linux-nexus7” package in Ubuntu:
  Confirmed
Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  I've recently updated my nexus and I've noticed that the battery
  system behaves very erratically. It will say that the battery is at
  43%, 1 hour left, then say it is low with 43% and 1 minute left. At
  some points it says the battery is critical and shuts down the screen,
  only to re-awake soon after saying that the battery is simply low. The
  percentage seems to remain constant, however the time left changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+subscriptions

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

[Oliver Grawert]

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

** Changed in: xdiagnose (Ubuntu Raring)
   Importance: Undecided = High

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in Ubuntu on the Nexus 7:
  New
Status in “gksu” package in Ubuntu:
  Confirmed
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  New
Status in “update-notifier” package in Ubuntu:
  Triaged
Status in “xdiagnose” package in Ubuntu:
  New
Status in “gksu” source package in Raring:
  Confirmed
Status in “ubuntu-defaults-nexus7” source package in Raring:
  New
Status in “update-notifier” source package in Raring:
  Triaged
Status in “xdiagnose” source package in Raring:
  New

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/421660/+subscriptions

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

[Desktop-packages] [Bug 1068442] Re: physical rotation doesn't rotate screen and input automatically

[Oliver Grawert]

it has been worked around by some scripts ...
nontheless it should be properly fixed in gnome-settings-daemon instead, 
closing the nexus7 task but leaving g-s-d open


ubuntu-defaults-nexus7 (0.41) raring; urgency=low

  * add acceld.conf upstart job, acceld binary to /usr/bin
and 95-acceld_start XSession.d file this enables auto-rotation of
the screen. it can be disabled by editing /etc/default/acceld

-- Oliver Grawert o...@ubuntu.com   Mon, 21 Jan 2013 16:48:47 +0100

** Changed in: ubuntu-nexus7
   Status: Triaged = Fix Released

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

Title:
  physical rotation doesn't rotate screen and input automatically

Status in Ubuntu on the Nexus 7:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged

Bug description:
  Once Bug# 1092952 is solved and we are able to listen for rotate
  events from the kernel, then we need to hook this signal in with the
  gnome-settings-daemon code that tracks rotation status and performs
  the xinput and xrandr rotation events.

  Bryce has written an xrotate script that maybe we could attach to the
  rotation events, but in theory we shouldn't need it.

  Bryce adds, Theoretically there should be code in gnome-settings-
  daemon (or gnome-desktop) which listens for xrandr events and rotates
  the input.  So when we have proper handling of the sensor we can hook
  that to the gtk events and let g-s-d rotate the input, and then
  xrotate simply becomes a debugging tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068442/+subscriptions

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

[Desktop-packages] [Bug 1098835] Re: Can't input password when login

[Oliver Grawert]

do you not have the onboard applet in the panel of the login screen
where you can start the onscreen keyboard ?

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

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

Title:
  Can't input password when login

Status in Ubuntu on the Nexus 7:
  New
Status in “onboard” package in Ubuntu:
  Incomplete

Bug description:
  I set my account doesn't login automatically,when I start the Nexus
  7,I need to input account password,but the keyboard doesn't show up,so
  I can't input password when login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1098835/+subscriptions

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

[Oliver Grawert]

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

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in Ubuntu on the Nexus 7:
  New
Status in “gksu” package in Ubuntu:
  Confirmed
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  New

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/421660/+subscriptions

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

[Desktop-packages] [Bug 1072406] Re: /usr/lib/evolution/evolution-calendar-factory consume 99% cpu

[Oliver Grawert]

could someone from the desktop team explain the reason why lightdm uses
the evo calendar factory at all ? does not really seem necessary for
spawning a greeter ...

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

Title:
  /usr/lib/evolution/evolution-calendar-factory consume 99% cpu

Status in Ubuntu on the Nexus 7:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in “evolution-data-server” package in Ubuntu:
  Triaged

Bug description:
  /usr/lib/evolution/evolution-calendar-factory consumes 100% CPU.
  Confirmed on multiple desktops, laptops and Nexus 7.

  Workaround:
  sudo apt-get remove evolution-data-server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1072406/+subscriptions

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

[Oliver Grawert]

** Also affects: ubuntu-defaults-nexus7 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
   Status: New = Confirmed

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
   Importance: Undecided = High

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in One Hundred Paper Cuts:
  Invalid
Status in Ubuntu on the Nexus 7:
  Confirmed
Status in “gksu” package in Ubuntu:
  Confirmed
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  Confirmed

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

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

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

[Desktop-packages] [Bug 421660] Re: gksu's and gksudo's modal password prompt prevents OnBoard's virtual keyboard input, causing accessibility issues

[Oliver Grawert]

for fixing the remianing issues in raring (where the plan is to get rid of gksu 
in favour of using pkexec everywhere), it would be good to know when exactly 
users get gksu prompts.
we need to fix the apps using it to instead use pkexec. 
people seeing this issue on the nexus7, please tell us where/when exactly gksu 
pops up

** Changed in: ubuntu-nexus7
   Status: Confirmed = Incomplete

** Changed in: ubuntu-defaults-nexus7 (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  gksu's and gksudo's modal password prompt prevents OnBoard's virtual
  keyboard input, causing accessibility issues

Status in One Hundred Paper Cuts:
  Invalid
Status in Ubuntu on the Nexus 7:
  Incomplete
Status in “gksu” package in Ubuntu:
  Confirmed
Status in “ubuntu-defaults-nexus7” package in Ubuntu:
  Incomplete

Bug description:
  I'm loath to report this as a bug, since it is functioning as
  designed, but I can't really find a better place to submit my
  complaint. I'm running 9.04 Netbook Remix, and if I run a GUI
  application and do something requiring sudo privileges, I receive a
  password prompt that blocks access to any other windows on the screen.
  Fine and good, but because of a disability, my only means of keyboard
  input is the OnBoard on-screen keyboard. My only recourse for such
  basic tasks as installing updates and adding packages is to pull out
  the terminal, hope I can find the pertinent command, and sudo it so I
  can give my password via terminal. This rather negates the convenience
  of doing these things from the GUI.

  Naturally, the expected behavior is that I be able to use OnBoard to
  enter my password into the prompt.

  Any other user who uses an on-screen keyboard or other GUI-based
  application for keyboard input will be susceptible to this issue. I
  imagine there are a fair number.

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

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

[Desktop-packages] [Bug 1066046] Re: pvr driver crashes when ubiquity-slideshow starts

[Oliver Grawert]

this seems to affect all flavours on all arm hardware, the ubuntu
slideshow also needs to be removed in preinstalled images, adding a
livecd-rootfs task for this.

having it crash on a tegra ac100 netbook crashes the installer but not X
like on omap4 with the pvr driver, i get an error message there and am
properly put into a rootshell afterwards.

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided = Critical

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) = Oliver Grawert (ogra)

** Also affects: ubiquity (Ubuntu Quantal)
   Importance: Critical
   Status: Invalid

** Also affects: livecd-rootfs (Ubuntu Quantal)
   Importance: Critical
 Assignee: Oliver Grawert (ogra)
   Status: New

** Also affects: webkit (Ubuntu Quantal)
   Importance: High
   Status: Confirmed

** Also affects: pvr-omap4 (Ubuntu Quantal)
   Importance: High
   Status: Confirmed

** Changed in: livecd-rootfs (Ubuntu Quantal)
Milestone: None = ubuntu-12.10

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

Title:
  pvr driver crashes when ubiquity-slideshow starts

Status in “livecd-rootfs” package in Ubuntu:
  New
Status in “pvr-omap4” package in Ubuntu:
  Confirmed
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “webkit” package in Ubuntu:
  Confirmed
Status in “livecd-rootfs” source package in Quantal:
  New
Status in “pvr-omap4” source package in Quantal:
  Confirmed
Status in “ubiquity” source package in Quantal:
  Invalid
Status in “webkit” source package in Quantal:
  Confirmed

Bug description:
  On panda, I'm hitting this crash on the 20121012.2 image for quantal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.10
  ProcVersionSignature: Ubuntu 3.5.0-213.20-omap4 3.5.5
  Uname: Linux 3.5.0-213-omap4 armv7l
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: armhf
  CasperVersion: 1.328
  Date: Fri Oct 12 11:26:13 2012
  InstallCmdLine: fixrtc quiet splash -- boot=casper only-ubiquity
  LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Release armhf+omap4 
(20121012.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1066046/+subscriptions

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

[Desktop-packages] [Bug 1066046] Re: ubiquity crashes after user info screen on panda

[Oliver Grawert]

switching to console before running the install and purging ubiquity-
slideshow-ubuntu fixes the issue, apparently the new webkit tears down
the pvr driver

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

** Also affects: pvr-omap4 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubiquity (Ubuntu)
   Status: Confirmed = Invalid

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

** Changed in: pvr-omap4 (Ubuntu)
   Status: New = Confirmed

** Summary changed:

- ubiquity crashes after user info screen on panda
+ pvr driver crashes when ubiquity-slideshow starts

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

Title:
  pvr driver crashes when ubiquity-slideshow starts

Status in “pvr-omap4” package in Ubuntu:
  Confirmed
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “webkit” package in Ubuntu:
  Confirmed

Bug description:
  On panda, I'm hitting this crash on the 20121012.2 image for quantal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.10
  ProcVersionSignature: Ubuntu 3.5.0-213.20-omap4 3.5.5
  Uname: Linux 3.5.0-213-omap4 armv7l
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: armhf
  CasperVersion: 1.328
  Date: Fri Oct 12 11:26:13 2012
  InstallCmdLine: fixrtc quiet splash -- boot=casper only-ubiquity
  LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Release armhf+omap4 
(20121012.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pvr-omap4/+bug/1066046/+subscriptions

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

[Desktop-packages] [Bug 1066046] Re: pvr driver crashes when ubiquity-slideshow starts

[Oliver Grawert]

i applied a seed change that removes teh slideshow from all arm images,
that should work around it for now

** Changed in: pvr-omap4 (Ubuntu)
   Importance: Undecided = High

** Changed in: webkit (Ubuntu)
   Importance: Undecided = High

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

Title:
  pvr driver crashes when ubiquity-slideshow starts

Status in “pvr-omap4” package in Ubuntu:
  Confirmed
Status in “ubiquity” package in Ubuntu:
  Invalid
Status in “webkit” package in Ubuntu:
  Confirmed

Bug description:
  On panda, I'm hitting this crash on the 20121012.2 image for quantal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: ubiquity 2.12.10
  ProcVersionSignature: Ubuntu 3.5.0-213.20-omap4 3.5.5
  Uname: Linux 3.5.0-213-omap4 armv7l
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: armhf
  CasperVersion: 1.328
  Date: Fri Oct 12 11:26:13 2012
  InstallCmdLine: fixrtc quiet splash -- boot=casper only-ubiquity
  LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Release armhf+omap4 
(20121012.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pvr-omap4/+bug/1066046/+subscriptions

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