[Touch-packages] [Bug 1431141] Re: systemd-logind crashed with SIGABRT in udev_device_get_sysattr_value()

[Martin Pitt]

 $ journalctl -b -u systemd-logind.service
 No journal files were found.

Ah, apparently you are not in the adm group. Can you please re-try
with

  sudo journalctl -b -u systemd-logind.service

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431141

Title:
  systemd-logind crashed with SIGABRT in udev_device_get_sysattr_value()

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I just installed vivid on a Toshiba Satelite C50-B, this error shows
  up on every restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 11 18:39:11 2015
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2015-03-11 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
   Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite C50-B
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic 
root=UUID=dde4b40f-5d21-4e42-a8f9-c45a4c1256ba ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __read_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGABRT in __read_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.70
  dmi.board.asset.tag: *
  dmi.board.name: ZBWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.70:bd12/11/2014:svnTOSHIBA:pnSatelliteC50-B:pvrPSCMLC-02Y00T:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Satellite C50-B
  dmi.product.version: PSCMLC-02Y00T
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1438249] Re: /sbin/dhclient is unconfined after switch to systemd (aka, equivalent of upstart's network-interface-security.conf not implemented)

[Martin Pitt]

Fixed both dependencies in http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=dd2f43c5bcb

** No longer affects: ifupdown (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1438249

Title:
  /sbin/dhclient is unconfined after switch to systemd (aka, equivalent
  of upstart's network-interface-security.conf not implemented)

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  dhclient is starting before the apparmor profile for it is loaded
  which results in the following output from aa-status:

  $ sudo aa-status
  ...
  4 profiles are in enforce mode.
 /sbin/dhclient
  ...
  1 processes are unconfined but have a profile defined.
 /sbin/dhclient (634)

  Upstart had the network-interface-security.conf job to make sure this
  didn't happen. We wanted the cache loading library to be implemented
  in time (bug #1385414), but it still hasn't landed. Having the cache
  loading library in place would mean that this bug would also be fixed,
  but now we need to fix this bug differently for 15.04 and it must be
  fixed by release.

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

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

[Touch-packages] [Bug 1438306] Re: External monitors receive no signal

[Martin Pitt]

Your dmesg contains that:

[ 8849.688210] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to 
train DP, aborting
[ 9438.466017] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to 
train DP, aborting
[ 9464.436928] [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to 
train DP, aborting

Did you file the bug report right after this failure, i. e. is this
current information?

Can you reproduce this with sudo apt-get install --reinstall systemd?
If so, that's most probably fallout from bug 1431200; this is just about
the only (indirect) way how systemd touches graphics, so if that doesn't
reproduce it, this is a kernel bug. Thanks!

** Changed in: systemd (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438306

Title:
  External monitors receive no signal

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Upon running updates ( which included many related to systemd - so
  that's my best guess as to the right package - feel free to reclassify
  ) I can't get an external monitor to actually receive a signal from my
  laptop anymore.  I've tried both displayport and HDMI with no luck.
  You can flip the switch to turn the monitor on, but it doesn't
  actually send any data to the monitor ( it reports No signal ).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 30 10:55:00 2015
  InstallationDate: Installed on 2015-03-11 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150306)
  MachineType: System76, Inc. Galago UltraPro
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=44e9ad95-1beb-46e2-abaf-8960ae76bcff ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Martin Pitt]

The log shows that something requests the suspend over D-Bus. The most
probable candidate for this is logind. After this happens, can you
please copypaste the output of journalctl -f -b -u systemd-logind
here? That should show key presses and which buttons it listens to.

To confirm that it's logind, could you check if that stops happening if
you set HandleLidSwitch=ignore in /etc/systemd/logind.conf and then
reboot? There's a chance that it isn't actually logind as we use the
exact same logind and lid switch handling under upstart, just that we
replace the actual suspend D-Bus interface with systemd-shim.

Thanks!

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1403468] Re: dnsmasq profile incomplete for lxc usage

[Steve Beattie]

** Changed in: apparmor
Milestone: None = 2.9.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1403468

Title:
  dnsmasq profile incomplete for lxc usage

Status in AppArmor Linux application security framework:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  I am using the dnsmasq profile with lxc, and I am getting DENIED
  messages like:

  Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400
  audit(1418768818.310:865): apparmor=DENIED operation=truncate
  profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases
  pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118
  ouid=0

  Adding rw for that path obviously makes it go away, and seems like a
  reasonable change.

  Thanks,

  James

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-profiles 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 17 11:27:18 2014
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified]
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 
2014-12-16T20:38:31.370339
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2014-12-17T11:21:47.159017

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

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

[Touch-packages] [Bug 1435242] Re: Problematic type casting between int/long?

[Launchpad Bug Tracker]

This bug was fixed in the package cinder - 1:2015.1~b3-0ubuntu1

---
cinder (1:2015.1~b3-0ubuntu1) vivid; urgency=medium

  [ James Page ]
  * d/pydist-overrides: Add overrides for oslo packages.

  [ Corey Bryant ]
  * New upstream milestone release for OpenStack Kilo:
- d/control: Align with upstream dependencies.
- d/p/skip-huaweistorac-delete-snapshot-success-test.patch: Dropped.
  Patched test has been removed.

  [ James Page ]
  * d/control: Add missing BD on python-testresources.
  * d/p/fix-long-casting.patch: Workaround some problematic type casting between
int/long (LP: #1435242).
  * d/p/fix-assert-raises-regex-tests.patch: Patchup incorrect usage of
assertUsesRegex{p} in unit tests.
 -- James Page james.p...@ubuntu.com   Mon, 30 Mar 2015 11:07:20 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1435242

Title:
  Problematic type casting between int/long?

Status in cinder package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  New

Bug description:
  We're seeing this error with the new kilo-3 milestone:

  ==
  FAIL: 
cinder.tests.test_utils.GetBlkdevMajorMinorTestCase.test_get_blkdev_major_minor_file
  
cinder.tests.test_utils.GetBlkdevMajorMinorTestCase.test_get_blkdev_major_minor_file
  --
  _StringException: Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721, 
in test_get_blkdev_major_minor_file
  dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
  return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712, 
in _test_get_blkdev_major_minor_file
  dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in 
get_blkdev_major_minor
  return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in 
get_blkdev_major_minor
  return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
  SystemError: ../Objects/longobject.c:998: bad argument to internal function
  Traceback (most recent call last):
  _StringException: Empty attachments:
stderr
stdout

  Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721, 
in test_get_blkdev_major_minor_file
  dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
  return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712, 
in _test_get_blkdev_major_minor_file
  dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in 
get_blkdev_major_minor
  return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in 
get_blkdev_major_minor
  return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
  SystemError: ../Objects/longobject.c:998: bad argument to internal function

  Traceback (most recent call last):
  _StringException: Empty attachments:
stderr
stdout

  Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721, 
in test_get_blkdev_major_minor_file
  dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
  return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712, 
in _test_get_blkdev_major_minor_file
  dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in 
get_blkdev_major_minor
  return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in 
get_blkdev_major_minor
  return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
  SystemError: ../Objects/longobject.c:998: bad argument to internal function

  This is evidently not impacting cinder on 14.04, just 15.04 so I would
  suspect some sort of python 2.7.9 issue.

  Casting to long appears to workaround this problem.

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

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

[Touch-packages] [Bug 1436074] Re: tab previews black [arale only]

[Timo Jyrinki]

The current guess is that this is a driver specific problem related to
offscreen image rendering, since the bug only happens on arale and
started when the webbrowser started using the new Qt 5.4 function that
uses that OpenGL feature.

I'm not sure where to file this under Ubuntu-the-distro.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1436074

Title:
  tab previews black [arale only]

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Web Browser App:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  running vivid-proposed build 146 on arale

  When I swipe from bottom edge to reveal tabs, only the most recent tab
  has a preview. The other tabs are black where the preview should be.

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

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

[Touch-packages] [Bug 1435287] Re: cups-browsed crashed with SIGSEGV in g_slist_foreach()

[Jerry Preissler]

Till,

the crash happened when I booted from USB to see if Vivid works on my
machine. The USB stick has since been repurposed, but if it helps I can
try to recreate it and see if the problem can be reproduced. Which image
should I use - the one I originally had the problem with or the current
daily?

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

Title:
  cups-browsed crashed with SIGSEGV in g_slist_foreach()

Status in cups-filters package in Ubuntu:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  Daily build from Mar 23rd 2015, booted from USB on Lenovo T440s.
  Selected 'Try Ubuntu', crash occured during startup

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.355
  CupsErrorLog:
   
  Date: Mon Mar 23 11:14:22 2015
  ExecutablePath: /usr/sbin/cups-browsed
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20AQ007TGE
  Papersize: a4
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- maybe-ubiquity
  SegvAnalysis:
   Segfault happened at: 0x7f926f1a2cd0 g_slist_foreach+16:   mov
0x8(%rdi),%rbx
   PC (0x7f926f1a2cd0) ok
   source 0x8(%rdi) (0x0009) not located in a known VMA region (needed 
readable region)!
   destination %rbx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_slist_foreach()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET79WW (2.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1436684] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

[Barry Drake]

Cannot reproduce crash - and crash has never occurred since that one
instance.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1436684

Title:
  cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

Status in avahi package in Ubuntu:
  New
Status in cups-filters package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  but appeared after system-bootup and while checking for updates via
  sudo apt-get update  sudo apt-get install -f  sudo apt-get dist-
  upgrade  sudo apt-get upgrade on 15.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CupsErrorLog:
   
  Date: Wed Mar 25 22:32:50 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2014-08-23 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lpstat:
   device for PDF: cups-pdf:/
   device for Photosmart-B110-series: 
dnssd://Photosmart%20B110%20series%20%5B4EC8C9%5D._pdl-datastream._tcp.local/
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   Photosmart-B110-series: HP Photosmart b110 Series, hpcups 3.15.2
   PDF: Generic CUPS-PDF Printer
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=79703205-63f2-49b3-bd01-249e7af129dd ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f2060d2d15a:movl   $0x1,0xa8(%rax)
   PC (0x7f2060d2d15a) ok
   source $0x1 ok
   destination 0xa8(%rax) (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to vivid on 2015-03-21 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 05/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: G31M-GS.
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/16/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1437803] Re: kubuntu 15.04 ubuntu-bug broken - File /usr/share/apport/apport-kde, line 43 from PyQt5 uic ^ SyntaxError: invalid syntax

[Philip Muškovac]

** Changed in: apport (Ubuntu)
   Importance: Undecided = Medium

** Changed in: apport (Ubuntu)
Milestone: None = ubuntu-15.04

** Tags added: kubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1437803

Title:
  kubuntu 15.04 ubuntu-bug broken -  File /usr/share/apport/apport-
  kde, line 43 from PyQt5 uic   ^ SyntaxError: invalid syntax

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Using 15.04 (kubuntu amd64) I am unable to use ubuntu-bug.

  i.e

  
--
  morgan@morgan-MS-7758:~$ ubuntu-bug apport-kde 
File /usr/share/apport/apport-kde, line 43
  from PyQt5 uic
   ^
  SyntaxError: invalid syntax
  
--

  seeing as its the devel versio the bug-reporting tool is of fairly
  high importance.

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

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

[Touch-packages] [Bug 1374079] Re: Support periodic detection of app updates

[Sebastien Bacher]

Reassigning to ubuntu-download-manager, settings don't run all the time
so can't do periodic work, that needs to be a service. Not sure that
u-d-m is the right service but it's more likely valid than settings

** Package changed: ubuntu-system-settings (Ubuntu) = ubuntu-download-
manager (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1374079

Title:
  Support periodic detection of app updates

Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  Filing here for tracking until the approach is known

  Currently app updates are only reported to the user when they enter the 
settings app. 
  The user should be notified that app updates are available in a manner 
similar to system updates

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Colin Ian King]

journalctl -f -b -u systemd-logind

-- Logs begin at Tue 2015-03-31 09:36:25 BST. --
Mar 31 09:36:26 skylake systemd[1]: Starting Login Service...
Mar 31 09:36:26 skylake systemd-logind[671]: New seat seat0.
Mar 31 09:36:26 skylake systemd-logind[671]: Watching system buttons on 
/dev/input/event3 (Power Button)
Mar 31 09:36:26 skylake systemd-logind[671]: Watching system buttons on 
/dev/input/event0 (Lid Switch)
Mar 31 09:36:26 skylake systemd-logind[671]: Watching system buttons on 
/dev/input/event1 (Power Button)
Mar 31 09:36:26 skylake systemd-logind[671]: Watching system buttons on 
/dev/input/event2 (Sleep Button)
Mar 31 09:36:26 skylake systemd[1]: Started Login Service.
Mar 31 09:36:32 skylake systemd-logind[671]: New session 1 of user king.
Mar 31 09:39:22 skylake systemd-logind[671]: Suspending...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1438554] Re: Sound icon doesnt change when on Silent mode

[Albert Astals Cid]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1438554

Title:
  Sound icon doesnt change when on Silent mode

Status in indicator-sound package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  If you look at the printscreen I have taken, after I ckeck Silent
  mode the icon from the top doesnt change acordingly.

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

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

[Touch-packages] [Bug 1438554] Re: Sound icon doesnt change when on Silent mode

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1436351
   icon does not change in silent mode

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1438554

Title:
  Sound icon doesnt change when on Silent mode

Status in indicator-sound package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  If you look at the printscreen I have taken, after I ckeck Silent
  mode the icon from the top doesnt change acordingly.

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

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

[Touch-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off

[Olivier Febwin]

Yeah!!!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1308265

Title:
  First password letter not registered in lockscreen if screen off

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1431200] Re: daemon-reload runs alsa-restore.service and others

[Martin Pitt]

For the record, I don't see the behaviour from comment 1 with current
systemd any more.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431200

Title:
  daemon-reload runs alsa-restore.service and others

Status in systemd package in Ubuntu:
  In Progress
Status in systemd package in Debian:
  New

Bug description:
  When systemd is reloaded (manually, upgrades), the volume is reset,
  likely using alsa-restore.

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Colin Ian King]

The HandleLidSwitch=ignore stops the box from suspending:

$ uptime
 09:50:25 up 5 min,  2 users,  load average: 0.00, 0.00, 0.00

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1435287] Re: cups-browsed crashed with SIGSEGV in g_slist_foreach()

[Enrico]

The same bug happened in my installed version. It's quite hard to
reproduce for me because it happens randomly when I boot the PC. Which
log should I save when it happens?

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

Title:
  cups-browsed crashed with SIGSEGV in g_slist_foreach()

Status in cups-filters package in Ubuntu:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  Daily build from Mar 23rd 2015, booted from USB on Lenovo T440s.
  Selected 'Try Ubuntu', crash occured during startup

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.355
  CupsErrorLog:
   
  Date: Mon Mar 23 11:14:22 2015
  ExecutablePath: /usr/sbin/cups-browsed
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20AQ007TGE
  Papersize: a4
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- maybe-ubiquity
  SegvAnalysis:
   Segfault happened at: 0x7f926f1a2cd0 g_slist_foreach+16:   mov
0x8(%rdi),%rbx
   PC (0x7f926f1a2cd0) ok
   source 0x8(%rdi) (0x0009) not located in a known VMA region (needed 
readable region)!
   destination %rbx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_slist_foreach()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET79WW (2.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1421293] Re: Icon width is inconsistent when height is specified

[Albert Astals Cid]

No, I haven't

just run the file with different pixel per grid unit and see how the
error is still there.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1421293

Title:
  Icon width is inconsistent when height is specified

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  The width of an Icon {} depends if the Icon is an SVG coming from
  image://theme/ or a JPG.

  For the SVG the width grows as the units.gu grow, but for the JPEG it
  does not and one has to manually add code to maitain the aspect ratio.

  See the attached code and files.

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

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

[Touch-packages] [Bug 1283763] Re: Cannot connect to WPA Enterprise networks

[Maarten Bonnema]

Hi There too,

Yes, I managed as well by manually editing. In fact I took a working eduroam 
settings-file from my laptop, removed the mac-address, and moved it to the 
ubuntu phone. Indeed chmod +600 was necessary.
Also, strangely, I had to change eap to ttls and phase2-auth to pap.
Now it works.

MaBo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1283763

Title:
  Cannot connect to WPA Enterprise networks

Status in indicator-network package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I cannot connect to a wireless network that uses enterprise WPA (which
  asks not only for a password but also for a username) on a Touch
  device.

  It seems like there is just no GUI implemented to handle that, as
  nothing happens when I ty to connect.

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

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

[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

[Kiril]

Nice. Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1313904

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Вбудоване аудіо - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[ghortor]

Hi Mark,

I’m not able to confirm this works right now, I’m having hard time
recompiling kernel modules. I just tried yesterday, as I haven’t got
much time so far. I will send an update as soon as I succeeded in
compiling kernel module.

Be aware that I will test solution in message #12 for my ubuntu kernel,
which is 3.13 ( 3.16 as written in the solution). I’d rather let ubuntu
decide which kernel needs to be used, even if I can’t use bluetooth
(this is not a mandatory option for me).

Regards,

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1366418

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo 04ca 2006  /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 

[Touch-packages] [Bug 1438567] Re: package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1438567

Title:
  package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in python-apt package in Ubuntu:
  New

Bug description:
  Failure to load python-apt package after updateto 14.04 Ubuntu server
  version

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3-apt 0.9.3.5ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Mon Mar 30 22:30:54 2015
  DuplicateSignature: package:python3-apt:0.9.3.5ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-01-30 (789 days ago)
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
  SourcePackage: python-apt
  Title: package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (334 days ago)

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

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

[Touch-packages] [Bug 1438558] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361644/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361646/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361647/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361648/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361649/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361650/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1438558/+attachment/4361651/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1380982
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1438558

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  New

Bug description:
  testing beta version 15.04 64 from upgrade 14.00 rebooted after
  upgrades found error on fist login

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: ibus 1.5.9-1ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Mar 31 08:28:38 2015
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2014-08-14 (228 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to vivid on 2015-03-28 (2 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1374079] [NEW] Support periodic detection of app updates

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Filing here for tracking until the approach is known

Currently app updates are only reported to the user when they enter the 
settings app. 
The user should be notified that app updates are available in a manner similar 
to system updates

** Affects: ubuntu-download-manager (Ubuntu)
 Importance: High
 Status: Confirmed

-- 
Support periodic detection of app updates 
https://bugs.launchpad.net/bugs/1374079
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu.

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

[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel

[Michał Sawicz]

** Summary changed:

- we donot see the max-min-close button when you drag it to the top
+ It's possible to put a window under the top panel

** Changed in: unity8 (Ubuntu)
   Status: New = Triaged

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1438465

Title:
  It's possible to put a window under the top panel

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

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

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

[Touch-packages] [Bug 1438567] [NEW] package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Dudule Crapouille]

Public bug reported:

Failure to load python-apt package after updateto 14.04 Ubuntu server
version

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-apt 0.9.3.5ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
Date: Mon Mar 30 22:30:54 2015
DuplicateSignature: package:python3-apt:0.9.3.5ubuntu1:subprocess installed 
post-installation script returned error exit status 139
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
InstallationDate: Installed on 2013-01-30 (789 days ago)
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
SourcePackage: python-apt
Title: package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to trusty on 2014-05-01 (334 days ago)

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1438567

Title:
  package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in python-apt package in Ubuntu:
  New

Bug description:
  Failure to load python-apt package after updateto 14.04 Ubuntu server
  version

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3-apt 0.9.3.5ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Mon Mar 30 22:30:54 2015
  DuplicateSignature: package:python3-apt:0.9.3.5ubuntu1:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2013-01-30 (789 days ago)
  InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 
(20121017.2)
  SourcePackage: python-apt
  Title: package python3-apt 0.9.3.5ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (334 days ago)

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

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

[Touch-packages] [Bug 1410113] Re: [krillin] Data connection doesn't switch from Wifi to Cellular

[Jean-Baptiste Lallement]

When it happens it shows the 'no connection' icon (attached)

** Attachment added: wifi-no-connection.png
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1410113/+attachment/4361695/+files/wifi-no-connection.png

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

Title:
  [krillin] Data connection doesn't switch from Wifi to Cellular

Status in the base for Ubuntu mobile products:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  New

Bug description:
  Conditions to reproduce are not clear.
  *Sometimes* when going out of Wifi range, data doesn't switch to 3G. I waited 
45min and the connection never established. When I'm back within Wifi range, 
the device reconnects to the AP and data is working.

  I didn't play with airplane mode.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: network-manager 0.9.8.8-0ubuntu33
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jan 13 09:34:02 2015
  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 2015-01-12 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150112-030205)
  IpRoute:
   default via 192.168.1.254 dev wlan0  proto static
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.16  metric 
9
  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-12-18T18:05:17
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   /ril_0 gsm   connected 
/org/freedesktop/NetworkManager/Devices/2
   /ril_1 gsm   disconnected  
/org/freedesktop/NetworkManager/Devices/1
   wlan0  802-11-wireless   connected 
/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 disabled

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

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

[Touch-packages] [Bug 1438249] Re: /sbin/dhclient is unconfined after switch to systemd (aka, equivalent of upstart's network-interface-security.conf not implemented)

[John Johansen]

So just a little more context around this whole split in policy loading.
AppArmor does a check that the cached policy is current and matches to
the kernel before loading and then if not falls back to recompiling
policy. The policy load was split into an early stage
(/etc/apparmor/init) and full policy (/etc/apparmor.d/), so that early
boot would only load the minimum amount of policy needed during early
boot to minimize potential delays (specifically fallback to compile)
during early boot. The recompile is not such an issue in later boot as
it can be run in parallel with more services.

TLDR: The split is all about boot speed. It would be easier and safer if
all policy was loaded as early as possible.

More context:
* apparmor init scripts all sys V and not upstart based (for various reasons)
* apparmor_parser at the time would only process one file and had to be called 
multiple times (which slowed down loading) - (FIXED)
* apparmor_parser is single threaded, so shell scripts were used to get 
parallel loading/compiles - (NOT fixed)
* apparmor_parser was a LOT (at least a couple orders of magnitude) slower at 
compiles when this was done
* apparmor_parser couldn't properly build policy for anything but the current 
kernel, so policy compile was always left to first boot of a given kernel
  - specifying the feature set was broken (FIXED)
  - the abi matching had issues (FIXED)
  - new kernels didn't ship the needed feature information to compile policy 
for the kernel during kernel installed so policy compiles needed to wait until 
booting into the new kernel (NOT fixed)
* apparmor only supported a single cache ( NOT fixed - soon)
  - needed to support policy for multiple kernels, having policy compiled 
before boot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438249

Title:
  /sbin/dhclient is unconfined after switch to systemd (aka, equivalent
  of upstart's network-interface-security.conf not implemented)

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  dhclient is starting before the apparmor profile for it is loaded
  which results in the following output from aa-status:

  $ sudo aa-status
  ...
  4 profiles are in enforce mode.
 /sbin/dhclient
  ...
  1 processes are unconfined but have a profile defined.
 /sbin/dhclient (634)

  Upstart had the network-interface-security.conf job to make sure this
  didn't happen. We wanted the cache loading library to be implemented
  in time (bug #1385414), but it still hasn't landed. Having the cache
  loading library in place would mean that this bug would also be fixed,
  but now we need to fix this bug differently for 15.04 and it must be
  fixed by release.

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

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

[Touch-packages] [Bug 1438172] Re: Non-pinned apps disappear when push counter cleared

[Nekhelesh Ramananthan]

This also affects RTM. Would we see a backport to RTM or just wait for
the transition to vivid?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1438172

Title:
  Non-pinned apps disappear when push counter cleared

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Steps:
  * kill Telegram and keep it off your launcher
  * wait for a push notification to come in
  * use the launcher item to launch Telegram

  Expected:
  * Telegram launches
  * item on launcher remains, with the count emblem reset and invisible
  * nothing happens on incoming push notification when Telegram on screen

  Current:
  * Telegram launches
  * launcher item disappears
  * launcher pops out on every incoming message

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150320-0ubuntu1
  Uname: Linux 3.10.35+ armv7l
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: armhf
  Date: Mon Mar 30 14:31:40 2015
  InstallationDate: Installed on 2015-03-30 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150330-020203)
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 155
   device name: m75
   channel: ubuntu-touch/vivid-proposed
   last update: 2015-03-30 10:26:47
   version version: 155
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links

[Martin Pitt]

I can't fix that in general, as I don't know what causes these invalid
rc2.d/ to rc5.d/ links with rcS init scripts. But for /etc/init.d/lvm2
in particular we can avoid running this pointless dummy script at all, I
committed a change for this.

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

** Summary changed:

- ordering cycles with early boot rcS scripts with inappropriate rc2.d links
+ ordering cycles with lvm2 init script with inappropriate rc2.d links

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431107

Title:
  ordering cycles with lvm2 init script with inappropriate rc2.d links

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  After switching to systemd, the AppArmor service often fails to start
  on boot.  This seems to happen at least 50% of the times I turn on the
  system.  If I attempt to start the process again after the system is
  otherwise finished booting, it works fine.  I also have another system
  with the same software configuration but a much slower storage system
  (HDD instead of SSD) which never suffers from this problem, so I think
  it is probably a race condition.  If I do systemctl status apparmor,
  I get the following output:

  michael@mamarley-laptop:~$ sudo systemctl status apparmor
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor)
 Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 
5s ago
   Docs: man:systemd-sysv-generator(8)
Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process 
exited, code=exited status=123
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail!
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered 
failed state.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1
  Uname: Linux 3.19.0-9-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 11 21:30:08 2015
  InstallationDate: Installed on 2014-06-01 (283 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  MachineType: LENOVO 2359CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency 
root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline 
intel_pstate=enable acpi_osi=Windows 2012
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA2WW (2.62 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10

[Jeroen T. Vermeulen]

So to be clear: my desktop is still utterly broken, but the one on an
installer disc for the same version is not.  Hopefully there is a simple
configuration problem.  I haven't done anything very special, I thought.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1437765

Title:
  No desktop after upgrade to 14.10

Status in unity package in Ubuntu:
  New

Bug description:
  After upgrading my desktop machine from 14.04 to 14.10, I no longer
  have a desktop.  The login screen works, but after logging in, I get
  just the backdrop image and a mouse pointer.  Nothing else.

  The pointer responds to mouse movements, and I can switch to a text
  console using ctrl-alt-Fn, which is how I installed KDE in order to
  file this bug.  But I can no longer open a terminal with ctrl-alt-T,
  or switch workspaces with ctrl-alt-arrow.

  My .xsession-errors after logging in showed:

  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  19 (X_GLXQueryServerString)
Serial number of failed request:  22
Current serial number in output stream:  22
  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  upstart: hud main process (2389) terminated with status 1
  upstart: unity-settings-daemon main process (2393) terminated with status 1
  upstart: unity7 main process (2405) terminated with status 1
  upstart: gnome-session (Unity) main process (2411) terminated with status 1
  upstart: unity-panel-service main process (2422) terminated with status 1
  upstart: indicator-keyboard main process (2496) terminated with status 1
  upstart: indicator-printers main process (2502) terminated with status 1
  upstart: upstart-dbus-session-bridge main process (2366) terminated with 
status 1
  upstart: indicator-bluetooth main process (2485) killed by TERM signal
  upstart: indicator-power main process (2486) killed by TERM signal
  upstart: indicator-datetime main process (2494) killed by TERM signal
  upstart: indicator-sound main process (2501) killed by TERM signal
  upstart: indicator-session main process (2503) killed by TERM signal
  upstart: indicator-application main process (2536) killed by TERM signal
  upstart: Disconnected from notified D-Bus bus

  This is quite a slow machine, so normally it'd take a while to
  complete a graphical login.  But now, when I log in and immediately
  switch to a graphical console to run top, it doesn't show much going
  on.  External filesystem volumes are not auto-mounted under /media the
  way they usually are.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: KDE
  Date: Sun Mar 29 09:23:52 2015
  InstallationDate: Installed on 2012-11-25 (853 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago)

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

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

[Touch-packages] [Bug 1411560] Re: Graphics performance degrades with time in 14.04

[Roberto Sosa Cano]

Hi Christopher,

It seems a lot more stable now. It is already 3 weeks without restarting
the machine and I haven't had any issue. I would say the enablement
stack has fixed the issue. Please let me know if you want me to perform
any additional check or attach more information.

Thanks,
Roberto

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1411560

Title:
  Graphics performance degrades with time in 14.04

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After several days using the system the graphics performance degrades.
  I cannot find any information in syslog or dmesg. It takes an awful
  amount of time to open a new window, and during that time the mouse is
  trapped into one of the monitors (cannot move to the other one). Also
  I've noticed that the Unity notification bar freezes and I cannot
  access any of the icons there, and the clock is just frozen.

  HDD, memory and CPU load seem normal. The only solution I've found is
  to reboot.

  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan 16 10:08:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed
   nvidia-331, 331.113, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:084a]
  InstallationDate: Installed on 2014-10-15 (93 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision WorkStation T5500
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0CRH6C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/20/2011:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0CRH6C:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T5500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Jan  9 11:10:54 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.6

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

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

[Touch-packages] [Bug 1438172] Re: Non-pinned apps disappear when push counter cleared

[Michał Sawicz]

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1438172

Title:
  Non-pinned apps disappear when push counter cleared

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Steps:
  * kill Telegram and keep it off your launcher
  * wait for a push notification to come in
  * use the launcher item to launch Telegram

  Expected:
  * Telegram launches
  * item on launcher remains, with the count emblem reset and invisible
  * nothing happens on incoming push notification when Telegram on screen

  Current:
  * Telegram launches
  * launcher item disappears
  * launcher pops out on every incoming message

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.02+15.04.20150320-0ubuntu1
  Uname: Linux 3.10.35+ armv7l
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: armhf
  Date: Mon Mar 30 14:31:40 2015
  InstallationDate: Installed on 2015-03-30 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150330-020203)
  SourcePackage: unity8
  SystemImageInfo:
   current build number: 155
   device name: m75
   channel: ubuntu-touch/vivid-proposed
   last update: 2015-03-30 10:26:47
   version version: 155
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1403468] Re: dnsmasq profile incomplete for lxc usage

[Christian Boltz]

Fixed in bzr trunk r2974 and 2.9 branch r2881.

** Changed in: apparmor
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1403468

Title:
  dnsmasq profile incomplete for lxc usage

Status in AppArmor Linux application security framework:
  Fix Committed
Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  I am using the dnsmasq profile with lxc, and I am getting DENIED
  messages like:

  Dec 16 22:26:58 superstar kernel: [226445.568383] type=1400
  audit(1418768818.310:865): apparmor=DENIED operation=truncate
  profile=/usr/sbin/dnsmasq name=/var/lib/misc/dnsmasq.lxcbr0.leases
  pid=1472 comm=dnsmasq requested_mask=w denied_mask=w fsuid=118
  ouid=0

  Adding rw for that path obviously makes it go away, and seems like a
  reasonable change.

  Thanks,

  James

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-profiles 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 17 11:27:18 2014
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic 
root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: [modified]
  mtime.conffile..etc.apparmor.d.usr.sbin.avahi.daemon: 
2014-12-16T20:38:31.370339
  mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2014-12-17T11:21:47.159017

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

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

[Touch-packages] [Bug 1390120] Re: Manually set time and date reverts to Automatically on restart (Ubuntu Phone)

[Trevor Cobbett]

It also reverts to 'automatic' after connecting to a wi-fi network (not
sure if part of this bug, or should raise as separate bug, but it's the
same behaviour issue)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1390120

Title:
  Manually set time and date reverts to Automatically on restart (Ubuntu
  Phone)

Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  1a - On OS build #6 (Channel: ubuntu-touch/ubuntu-rtm/14.09), I open Time  
Date settings and select Manually under Set the time and date:
  2a - I set the time manually from Old_Time to New_Time and wait for New_Time 
to display in the Date Time Indicator at top-right
  3a - Then restart Ubuntu Phone and Date Time Indicator shows New_Time for 
10 seconds and then reverts to Old_Time
  4a - Time  Date settings agree with Old_Time and Automatically has been 
selected under Set the time and date:

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

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

[Touch-packages] [Bug 1368864] Re: old motd is displayed on login

[Michael]

Same here on 14.04 , MOTD doen't get updated.

/etc/pam.d/login:

[...]
sessionoptional   pam_motd.so  motd=/run/motd.dynamic noupdate
sessionoptional   pam_motd.so
[...]

/etc/pam.d/sshd:

[...]
session optional pam_motd.so motd=/run/motd.dynamic
session optional pam_motd.so noupdate
[...]

Please fix this as we use the MOTD for update-infos and other stuff.

Regards!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1368864

Title:
  old motd is displayed on login

Status in shadow package in Ubuntu:
  Triaged

Bug description:
  On Trusty, during login, the motd displayed is from the cache file
  /run/motd.dynamic. After being displayed, the scripts from /etc
  /update-motd.d are run to refresh /run/motd.dynamic. This behavior of
  displaying the cache first is not very convenient and didn't happen on
  Precise. This is also does not match the documentation (man 5 update-
  motd) nor the users' expectations.

  Steps to reproduce:

  $ cat  EOF | sudo tee /etc/update-motd.d/60-test
  #!/bin/sh
  printf motd from: $(date +%T)\n
  EOF
  $ sudo chmod +x /etc/update-motd.d/60-test

  
  $ echo 'echo real time: $(date +%T);exit' | ssh -T localhost
  Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64)

   * Documentation:  https://help.ubuntu.com/
  motd from: 6:05:43
  real time: 12:36:14

  The above is just an example of how old/stale the output can be.

  More details:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy libpam-modules
  libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libpam-modules 1.1.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 12 12:22:09 2014
  InstallationDate: Installed on 2014-01-26 (228 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124)
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[Sebastien Bacher]

That's indeed quite annoying, I activated silent mode while I was at a
spectacle the other day and then forgot it was on for a full day and
missed some calls, it's not the first time...

** Tags added: bq

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1437633] Re: Choosing not to report crashes and errors setting reverts

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1437633

Title:
  Choosing not to report crashes and errors setting reverts

Status in the base for Ubuntu mobile products:
  New
Status in lxc-android-config package in Ubuntu:
  Confirmed
Status in whoopsie package in Ubuntu:
  Invalid
Status in lxc-android-config package in Ubuntu RTM:
  New

Bug description:
  Possibly related to bug 1389407
  Reported on Askubuntu [1] and confirmed here on a retail bq handset with no 
modifications (no app installs, only OTA updates).

  Steps to reproduce:-

  System Settings - Security  Privacy - Diagnostics -
  Untick box next to App crashes and errors
  Leave system settings.
  Wait some time - the AU report suggests an hour, I waited less than that

  Go back into System Settings  - Security  Privacy - Diagnostics
  Not the tick box is ticked again.

  I would expect the tickbox to remain at whatever I set it to.

  [1] http://askubuntu.com/questions/602365/permanently-disable-error-
  reports-on-aquaris-e4-5-ubuntu-edition

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

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

[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts

[Dimitri John Ledkov]

Please do not comment and continue to reproduce this bug. It has status
open, therefore it is known that it is not fixed yet. A developer should
upload a patch to fix  close this bug report in the remaining
components that it is open against.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1242572

Title:
  xkeyboard-config, console-setup, and ubiquity should use Super+Space
  for switching keyboard layouts

Status in central project for keyboard configuration:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in console-setup source package in Trusty:
  Confirmed
Status in ubiquity source package in Trusty:
  Confirmed
Status in xkeyboard-config source package in Trusty:
  In Progress

Bug description:
  Super+Space is default combination for switching keyboard layouts in
  gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg;
  console-setup; and ubiquity should also use Super+Space combination
  for switching keyboard layouts.

  reading xkeyboard-config sources and documentations i don't see that
  xkeyboard-config can support grp:lwin_space and i guess that needs to
  be the first step to properly support super+space.

  
  Original bug report below:

  
  Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10.
  I use two keyboard layouts - English and Russian.
  So I select them on the corresponding screen of ubiquity setup wizard.

  It quietly set the keyboard switching shortcut to Alt+Shift and wrote this 
setting to /etc/default/keyboard:
  # ...
  XKBMODEL=pc105
  XKBLAYOUT=us,ru
  XKBVARIANT=,
  XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll
  # ...

  On first boot of installed system the small notification pop-up showed
  that Ibus will use Super+Space for layout switching.

  Please fix this configuration inconsistency.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 21 12:16:58 2013
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash --
  InstallationDate: Installed on 2013-10-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 
(20131017)
  MarkForUpload: True
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Martin Pitt]

@Colin: I need a journal after all, see bug 1438612. Thanks!

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1438612] Re: D-Bus stops too early under systemd

[Martin Pitt]

Actually, this isn't the full story, as NetworkManager doesn't tear down
interfaces when it shuts down. So Colin, I'm afraid I need a shutdown
journal output from current vivid after all..

** Changed in: dbus (Ubuntu)
   Status: Triaged = Incomplete

** Summary changed:

- D-Bus stops too early under systemd
+ remote file systems hang on shutdown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1438645] [NEW] The circle on the lock screen shows yesterday's info

[Michal Predotka]

Public bug reported:

When I wake up in the morning and look at my phone, I see for example:
14 text messages sent today which is not true. It was true yesterday.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1438645

Title:
  The circle on the lock screen shows yesterday's info

Status in unity8 package in Ubuntu:
  New

Bug description:
  When I wake up in the morning and look at my phone, I see for example:
  14 text messages sent today which is not true. It was true
  yesterday.

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Martin Pitt]

Debugging notes:

 - I see tons of Refusing operation, as it is turned off in the logs
now, which is due to the disabled HandleLidSwitch (before it was
Suspending...)

 - I see no event at all in evtest

 - I believe stopping acpid does not help, I still see the Refusing
operation... messages from logind.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Colin Law]

No problem.  Attaching journal

** Attachment added: Journal showing wait on unmount when connected via wifi
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1438612/+attachment/4361872/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1436724] Re: No prompt to unlock sim after airplane mode

[Olga Kemmet]

I think the UX is not ideal if I have to input my SIM PIN every single time I 
switch off the flight mode. The what i understood it that it only is required 
if the device was rebooted. 
What is the need for a SIM PIN input after flight mode was disabled? 

** Changed in: ubuntu-ux
   Status: New = Incomplete

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

** Summary changed:

- No prompt to unlock sim after airplane mode
+ [indicators] [SIM PIN] No prompt to unlock sim after airplane mode

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1436724

Title:
  [indicators] [SIM PIN] No prompt to unlock sim after airplane mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Incomplete
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  BQ phone:

  Steps to reproduce:
  1. Turn airplane mode on
  2. Turn airplane mode off

  Desired effect:
  You get a prompt to unlock your sim cards

  What I got:
  You get no connection and no prompt. Only if you open the network panel, 
you see that your sim is still locked.

  You should get a prompt to unlock your sim after turning off airplane
  mode. Otherwise the user does not know the sim card is still locked.
  The fact that the sim card becomes locked after airplane mode is not
  something you should have to think about as a user.

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

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

[Touch-packages] [Bug 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator

[Michal Predotka]

I have this problem on bq phone as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1382861

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

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

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

[Touch-packages] [Bug 1438645] Re: The circle on the lock screen shows yesterday's info

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1438645

Title:
  The circle on the lock screen shows yesterday's info

Status in libusermetrics package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When I wake up in the morning and look at my phone, I see for example:
  14 text messages sent today which is not true. It was true
  yesterday.

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

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

[Touch-packages] [Bug 1268097] Re: [System settings] Can't set user-supplied ring tone

[Rex Tsai]

It only need the ubuntu-system-settings to look into user's folder.

I wonder would it be suitable to just  looks into ${XDG_MUSIC_DIR} or we
like to have ${XDG_MUSIC_DIR}/ringtone or ${XDG_MUSIC_DIR}/notification

XDG_MUSIC_DIR=/home/phablet/Music

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
https://bugs.launchpad.net/bugs/1268097

Title:
  [System settings] Can't set user-supplied ring tone

Status in Ubuntu UX bugs:
  Triaged
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

I am still seeing a second nautilus icon opening in the launcher.
$ apt-cache policy unity
unity:
  Installed: 7.3.2+15.04.20150330-0ubuntu1
  Candidate: 7.3.2+15.04.20150330-0ubuntu1
  Version table:
 *** 7.3.2+15.04.20150330-0ubuntu1 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1436297

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1430000] Re: [regression] mir_acceptance_tests.NestedServer failure in clang CI

[PS Jenkins bot]

Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.13.0

** Changed in: mir
   Status: Triaged = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/143

Title:
  [regression] mir_acceptance_tests.NestedServer failure in clang CI

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1565/parameters/?
  and
  
https://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1567/parameters/?

  have both failed in: 
  Start  26: mir_acceptance_tests.NestedServer.*
   26/287 Test  #26: mir_acceptance_tests.NestedServer.* 
...***Exception: SegFault  0.25 sec

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

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

[Touch-packages] [Bug 1430828] Re: scopes dont load pictures

[Alfonso Sanchez-Beato]

The bug might be related to a problem with DNS configuration.  The
default route is wlan0:

default via 10.0.1.1 dev wlan0  proto static

However, the last line of grep dnsmasq syslog is

Mar 30 15:26:35 ubuntu-phablet dnsmasq[3855]: using nameserver
172.26.38.2#53

which is the DNS provided by the cellular data connection

 [ /ril_0/context1 ]
Active = 1
Protocol = ip
AccessPointName = nxtgenphone
Type = internet
Settings = { Interface=ccmni0 Address=10.25.102.183 
DomainNameServers=172.26.38.1,172.26.38.2, Gateway=10.25.102.183 
Netmask=255.255.255.0 Method=static }

and it is probably not reachable via WiFi. I have seen similar problems
some times when doing apt-get update, for instance.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1430828

Title:
  scopes dont load pictures

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The phone (krillin) is clearly connected and you can retrive text data
  but pictures do not updated see, attached pictures.

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

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

[Touch-packages] [Bug 1430828] Re: scopes dont load pictures

[Albert Astals Cid]

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

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

Title:
  scopes dont load pictures

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The phone (krillin) is clearly connected and you can retrive text data
  but pictures do not updated see, attached pictures.

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

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

[Touch-packages] [Bug 1438393] Re: Cannot authenticate to swingbyswing.com

[Michael Zanetti]

The reply is in json format. However, the content type header is set to
text/html for some reason. I assume it would work for the else if
branch too, as that one seems to fall back to the jsonParser if the
plaintextParser fails. Haven't tried it though and I wiped my device
with this branch already.

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-plugin-oauth2 in
Ubuntu.
https://bugs.launchpad.net/bugs/1438393

Title:
  Cannot authenticate to swingbyswing.com

Status in signon-plugin-oauth2 package in Ubuntu:
  New

Bug description:
  I'm trying to create an OAuth plugin for swingbyswing.com. However it
  keeps failing.

  I got it to working with this diff: http://paste.ubuntu.com/10708914/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-plugin-oauth2/+bug/1438393/+subscriptions

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

[Touch-packages] [Bug 1438628] [NEW] vpn service fails

[Wolf Rogner]

Public bug reported:

Trying to connect via VPN (pptp) fails:

Mar 31 12:25:39 mbr NetworkManager[1002]: info Starting VPN service 'pptp'...
Mar 31 12:25:39 mbr NetworkManager[1002]: info VPN service 'pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 4143
Mar 31 12:25:39 mbr NetworkManager[1002]: info VPN service 'pptp' appeared; 
activating connections
Mar 31 12:25:39 mbr NetworkManager[1002]: error [1427797539.109043] 
[nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: 
(6) No agents were available for this request.
Mar 31 12:25:39 mbr NetworkManager[1002]: info Policy set 'rsb_hs' (wlan0) as 
default for IPv4 routing and DNS.
Mar 31 12:25:43 mbr NetworkManager[1002]: info VPN service 'pptp' disappeared


Workaround (as previously suggested):

remove ~/.gconf/apps/nm-applet/%gconf.xml
logout / login
connection works

...
until the next reboot

System: Ubuntu 14.10 (64bit)
Linux mbr 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

Not quite similar to #1297849 but same effect.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Date: Tue Mar 31 12:27:16 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-05-17 (682 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424)
IpRoute:
 default via 10.1.0.254 dev wlan0  proto static 
 10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103  metric 9 
 192.168.97.0/24 dev vmnet8  proto kernel  scope link  src 192.168.97.1 
 192.168.204.0/24 dev vmnet1  proto kernel  scope link  src 192.168.204.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 EC:88:92:61:E9:5F bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/1  
 wlan0  802-11-wireless   connected 
/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 disabled

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


** Tags: amd64 apport-bug utopic

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

Title:
  vpn service fails

Status in network-manager package in Ubuntu:
  New

Bug description:
  Trying to connect via VPN (pptp) fails:

  Mar 31 12:25:39 mbr NetworkManager[1002]: info Starting VPN service 
'pptp'...
  Mar 31 12:25:39 mbr NetworkManager[1002]: info VPN service 'pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 4143
  Mar 31 12:25:39 mbr NetworkManager[1002]: info VPN service 'pptp' appeared; 
activating connections
  Mar 31 12:25:39 mbr NetworkManager[1002]: error [1427797539.109043] 
[nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: 
(6) No agents were available for this request.
  Mar 31 12:25:39 mbr NetworkManager[1002]: info Policy set 'rsb_hs' (wlan0) 
as default for IPv4 routing and DNS.
  Mar 31 12:25:43 mbr NetworkManager[1002]: info VPN service 'pptp' 
disappeared

  
  Workaround (as previously suggested):

  remove ~/.gconf/apps/nm-applet/%gconf.xml
  logout / login
  connection works

  ...
  until the next reboot

  System: Ubuntu 14.10 (64bit)
  Linux mbr 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  Not quite similar to #1297849 but same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  Date: Tue Mar 31 12:27:16 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-17 (682 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac 
(20130424)
  IpRoute:
   default via 10.1.0.254 dev wlan0  proto static 
   10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103  metric 9 
   192.168.97.0/24 dev vmnet8  proto kernel  scope link  src 192.168.97.1 
   192.168.204.0/24 dev vmnet1  proto kernel  scope link  src 192.168.204.1
  

[Touch-packages] [Bug 1437633] Re: Choosing not to report crashes and errors setting reverts

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1437633

Title:
  Choosing not to report crashes and errors setting reverts

Status in the base for Ubuntu mobile products:
  New
Status in lxc-android-config package in Ubuntu:
  Confirmed
Status in whoopsie package in Ubuntu:
  Invalid
Status in lxc-android-config package in Ubuntu RTM:
  New

Bug description:
  Possibly related to bug 1389407
  Reported on Askubuntu [1] and confirmed here on a retail bq handset with no 
modifications (no app installs, only OTA updates).

  Steps to reproduce:-

  System Settings - Security  Privacy - Diagnostics -
  Untick box next to App crashes and errors
  Leave system settings.
  Wait some time - the AU report suggests an hour, I waited less than that

  Go back into System Settings  - Security  Privacy - Diagnostics
  Not the tick box is ticked again.

  I would expect the tickbox to remain at whatever I set it to.

  [1] http://askubuntu.com/questions/602365/permanently-disable-error-
  reports-on-aquaris-e4-5-ubuntu-edition

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

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

[Touch-packages] [Bug 1437633] Re: Choosing not to report crashes and errors setting reverts

[Iain Lane]

Here's the one for RTM

How do we get a candidate image to test this fix?

** Patch added: lxc-android-config_0.208rtm10.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1437633/+attachment/4361857/+files/lxc-android-config_0.208rtm10.debdiff

** Changed in: whoopsie (Ubuntu)
   Status: Confirmed = Invalid

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1437633

Title:
  Choosing not to report crashes and errors setting reverts

Status in the base for Ubuntu mobile products:
  New
Status in lxc-android-config package in Ubuntu:
  Confirmed
Status in whoopsie package in Ubuntu:
  Invalid
Status in lxc-android-config package in Ubuntu RTM:
  New

Bug description:
  Possibly related to bug 1389407
  Reported on Askubuntu [1] and confirmed here on a retail bq handset with no 
modifications (no app installs, only OTA updates).

  Steps to reproduce:-

  System Settings - Security  Privacy - Diagnostics -
  Untick box next to App crashes and errors
  Leave system settings.
  Wait some time - the AU report suggests an hour, I waited less than that

  Go back into System Settings  - Security  Privacy - Diagnostics
  Not the tick box is ticked again.

  I would expect the tickbox to remain at whatever I set it to.

  [1] http://askubuntu.com/questions/602365/permanently-disable-error-
  reports-on-aquaris-e4-5-ubuntu-edition

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

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

[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

** Attachment added: freeze_i386.JPG
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361870/+files/freeze_i386.JPG

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1432843

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions

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

[Touch-packages] [Bug 1422309] Re: Today's scope doesn't refresh automatically and indicates wrong day

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1422309

Title:
  Today's scope doesn't refresh automatically and indicates wrong day

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Not sure if that's rather something for unity8 or the today, but
  that page should auto-refresh on day changes. Otherwise when you pick
  your phone in the morning and unlocks it you get welcomed with the
  wrong date info until you pull down to manually refresh the view

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

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

[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

No idea why the explanatory text disappeared with comment #24 but that's
a pic of what the screen displays when the i386 image freezes.

This pic is what the screen displays when the amd64 image freezes.

** Attachment added: freeze_amd64.JPG
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361871/+files/freeze_amd64.JPG

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1432843

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions

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

[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

I've tested both the Lubuntu 20150330 i386 and amd64 images on two
totally different sets of hardware.

Both fail to boot to the live DE on this hardware:

Intel Atom CPU  230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller (rev 01)
Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
2GB DDR2 RAM

The i386 image fails to boot to the live DE, but the amd64 image does
boot to the live DE while producing bug #1438605 on this hardware:

AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
nVidia MCP61 High Definition Audio (rev a2)
nVidia MCP61 Ethernet (rev a2)
2GB DDR2 RAM

But the installation freezes at the second screen on that second set of
hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1432843

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions

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

[Touch-packages] [Bug 1373461] Re: Multiple delete confirmation uses Yes/No rather than verbs

[Olga Kemmet]

Is there a specific instance where the Yes/No occurs?

** Changed in: ubuntu-ux
   Status: New = Incomplete

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1373461

Title:
  Multiple delete confirmation uses Yes/No rather than verbs

Status in Ubuntu UX bugs:
  Incomplete
Status in address-book-app package in Ubuntu:
  New

Bug description:
  Use of Yes/No for confirmation (particularly on destructive actions, such 
as deleting) is generally considered inadvisable:
  
http://ux.stackexchange.com/questions/9946/should-i-use-yes-no-or-ok-cancel-on-my-message-box

  Recommend switching language to use the verbs Confirm/Cancel (as
  seen when uninstalling applications).

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

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

[Touch-packages] [Bug 1428762] Re: [SDK] Add Menu to the SDK to support convergence

[Olga Kemmet]

Try this one here Zsombor: https://sites.google.com/a/canonical.com
/apps-and-platform-team/?pli=1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1428762

Title:
  [SDK] Add Menu to the SDK to support convergence

Status in Ubuntu UI Toolkit:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  We need a menu component to enable medium  large form factors  point
   click interactions

  E.g.
  Selection Menu
  Contextual Menu

  UX Spec here
  
https://www.dropbox.com/s/ox09jqzrbgnl1lp/050315_Convergence%20-%20Menu_gv.pdf?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1428762/+subscriptions

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

[Touch-packages] [Bug 1438645] Re: The circle on the lock screen shows yesterday's info

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1438645

Title:
  The circle on the lock screen shows yesterday's info

Status in libusermetrics package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When I wake up in the morning and look at my phone, I see for example:
  14 text messages sent today which is not true. It was true
  yesterday.

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

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

[Touch-packages] [Bug 1438645] Re: The circle on the lock screen shows yesterday's info

[Albert Astals Cid]

Adding usermetrics, not sure it's usermetrics or unity8 that should
realize a new day has passed and update the infographics content

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusermetrics in Ubuntu.
https://bugs.launchpad.net/bugs/1438645

Title:
  The circle on the lock screen shows yesterday's info

Status in libusermetrics package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When I wake up in the morning and look at my phone, I see for example:
  14 text messages sent today which is not true. It was true
  yesterday.

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

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

[Touch-packages] [Bug 1438595] [NEW] systemd: fsck of ext4 filesystem does not show progress

[Andy Whitcroft]

Public bug reported:

When booting following a crash fsck is triggered for the root volume
(LVM containing ext4 filesystem).  This is correctly announced by
systemd/plymouth and remains announced for the duration of the fsck,
however the percentage complete is always 0.0% for the entire duration
of the check.  For those of us with no disk lights this is very off
putting.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-5ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 10:10:41 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-06-20 (648 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
MachineType: Intel Corporation 2012 Client Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro debug splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2013-11-10 (505 days ago)
dmi.bios.date: 07/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Latexo FFRD
dmi.board.vendor: Intel Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
dmi.product.name: 2012 Client Platform
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Intel Corporation

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


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438595

Title:
  systemd: fsck of ext4 filesystem does not show progress

Status in systemd package in Ubuntu:
  New

Bug description:
  When booting following a crash fsck is triggered for the root volume
  (LVM containing ext4 filesystem).  This is correctly announced by
  systemd/plymouth and remains announced for the duration of the fsck,
  however the percentage complete is always 0.0% for the entire duration
  of the check.  For those of us with no disk lights this is very off
  putting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 31 10:10:41 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (648 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro debug splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (505 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation

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

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

[Touch-packages] [Bug 1438595] Re: systemd: fsck of ext4 filesystem does not show progress

[Andy Whitcroft]

Adding a boot with fsck booted with debug on the kernel command line,
attaching journalctl -b as requested on IRC.

** Attachment added: BOOT
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1438595/+attachment/4361751/+files/BOOT

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438595

Title:
  systemd: fsck of ext4 filesystem does not show progress

Status in systemd package in Ubuntu:
  New

Bug description:
  When booting following a crash fsck is triggered for the root volume
  (LVM containing ext4 filesystem).  This is correctly announced by
  systemd/plymouth and remains announced for the duration of the fsck,
  however the percentage complete is always 0.0% for the entire duration
  of the check.  For those of us with no disk lights this is very off
  putting.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 31 10:10:41 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (648 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro debug splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (505 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation

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

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

[Touch-packages] [Bug 1434847] Re: Can't boot with Systemd

[Martin Pitt]

jobs.txt shows that there are no outstanding jobs, and journal.txt shows
that the boot went all the way through. However, it seems you don't have
any display manager installed/configured? Do you known which one should
be running? lightdm/gdm/sddm etc.?

Please give me the output of

  systemctl status display-manager
  cat /etc/X11/default-display-manager


** Summary changed:

- Can't boot with Systemd
+ does not start a display manager

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1434847

Title:
  does not start a display manager

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After updating all packages, I can't boot by choosing Ubuntu in the 
bootloader anymore. Kubuntu logo remains until the terminal shows, Starting 
version 219.
  I can boot successfully by choosing Ubuntu...(Updstart).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu7 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 21 12:02:06 2015
  InstallationDate: Installed on 2015-03-21 (0 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed 
root=UUID=ed2ae459-760e-4bd7-b5a0-f7f221d2d7fe ro quiet splash 
init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Martin Pitt]

The original issue here was fixed in network-manager 0.9.10.0-4ubuntu11
(see comment 20), and that's what the bug title says too, so closing the
NetworkManager task again. The remaining issue, D-Bus stopping too
early, is tracked in bug 1438612.

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

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1438602] Re: apt-get crashed with SIGSEGV in _IO_vfprintf_internal()

[Apport retracing service]

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

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361761/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361763/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361765/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361766/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361767/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361768/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1438602/+attachment/4361769/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1438602

Title:
  apt-get crashed with SIGSEGV in _IO_vfprintf_internal()

Status in apt package in Ubuntu:
  New

Bug description:
  apt-fast upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  Uname: Linux 4.0.0-04rc5-lowlatency x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  Date: Tue Mar 31 16:22:56 2015
  ExecutablePath: /usr/bin/apt-get
  InstallationDate: Installed on 2015-03-26 (5 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150322)
  ProcCmdline: apt-get upgrade
  SegvAnalysis:
   Segfault happened at: 0x7f20aa4d64b2 _IO_vfprintf_internal+18578:  repnz 
scas %es:(%rdi),%al
   PC (0x7f20aa4d64b2) ok
   source %es:(%rdi) (0x0076) not located in a known VMA region (needed 
readable region)!
   destination %al ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apt
  StacktraceTop:
   _IO_vfprintf_internal (s=s@entry=0x7f20ad0fe8d0, format=optimized out, 
ap=ap@entry=0x7ffca622f448) at vfprintf.c:1642
   ___fprintf_chk (fp=0x7f20ad0fe8d0, flag=1, format=optimized out) at 
fprintf_chk.c:35
   pkgDPkgPM::WriteApportReport(char const*, char const*) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   pkgDPkgPM::ProcessDpkgStatusLine(char*) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
   pkgDPkgPM::DoDpkgStatusFd(int) () from 
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
  Title: apt-get crashed with SIGSEGV in _IO_vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Martin Pitt]

Ah, ok; Some more ideas:

  - sudo systemctl stop acpid, to rule out acpid and acpi-support

 - install evtest and run sudo evtest, select the lid switch, and
check if you actually get an event after ~ 3 minutes? I don't actually
expect one, as logind should then log a Lid closed. event which it
apparently doesn't; but let's verify.

Is it possible for me to get ssh access to this machine?
(https://launchpad.net/~pitti/+sshkeys, possibly via you doing an ssh
port forward to chinstrap?)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[Buzea Bogdan]

After i ckecked Silence mode

** Attachment added: After Silence mode activated
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436351/+attachment/4361776/+files/screenshot20152830_192812770.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[Buzea Bogdan]

After i ckecked Silence mode

** Attachment added: After Silence mode activated
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436351/+attachment/4361775/+files/screenshot20152830_192812770.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[Buzea Bogdan]

Mee to, I have the same problem. Is on Silent mode, but the symbol is
like normal sound. I am on BQ device.


** Attachment added: screenshot20152830_192803795.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436351/+attachment/4361774/+files/screenshot20152830_192803795.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1437316] Re: [Clock] Too easy to accidentally turn off the alarm instead of snoozing

[Robie Basak]

Since reporting this I've read the design guidelines. I note that the
turn off button is on the right and green, and the snooze button is
on the left and white.

I suggest that maybe this is backwards. Turning off the alarm is
essentially deleting this instances of it and is potentially dangerous,
and so perhaps should be red and on the left? The safe action is to
snooze, so that should be default, green and on the right.

However, even with that change (if you or design team agree - I admit it
is subjective), the off button would still be too easy to hit, so I
still think something further needs to be done to avoid user accidents.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1437316

Title:
  [Clock] Too easy to accidentally turn off the alarm instead of
  snoozing

Status in Clock application for Ubuntu devices:
  Confirmed
Status in Ubuntu UX bugs:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  While half asleep and when I want to snooze, it's too easy to hit the
  wrong button and accidentally turn off the alarm instead of activating
  the snooze option.

  I expect the snooze button to be more easily available, and for the
  turn off button to be made harder to activate - for example with a
  slide or something.

  Other phones I've had have had the snooze button much bigger, or the
  snooze activate when the phone is turned over, or something like that,
  to assist with preventing accidental alarm switch off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1437316/+subscriptions

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

[Touch-packages] [Bug 1438612] [NEW] D-Bus stops too early under systemd

[Martin Pitt]

Public bug reported:

(part of bug 1431774). During shutdown, D-Bus stops too early. In
particular, it stops before NetworkManager and remote-fs.target,  so
that any network unmount  will cause errors and hang the boot. This can
be seen with

$ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

A quick workaround is to add After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section, but this
should be fixed in a more general fashion.

** Affects: dbus (Ubuntu)
 Importance: High
 Assignee: Martin Pitt (pitti)
 Status: Triaged


** Tags: systemd-boot

** Tags added: systemd-boot

** Changed in: dbus (Ubuntu)
   Status: New = Triaged

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

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

** Summary changed:

- stops too early under systemd
+ D-Bus stops too early under systemd

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  D-Bus stops too early under systemd

Status in dbus package in Ubuntu:
  Triaged

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1438393] Re: Cannot authenticate to swingbyswing.com

[Alberto Mardegan]

What is the reply that you get from the server?
Does it work if you move the  || contentType.startsWith(CONTENT_TEXT_HTML) 
condition to the else if branch?

** Changed in: signon-plugin-oauth2 (Ubuntu)
   Status: New = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-plugin-oauth2 in
Ubuntu.
https://bugs.launchpad.net/bugs/1438393

Title:
  Cannot authenticate to swingbyswing.com

Status in signon-plugin-oauth2 package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to create an OAuth plugin for swingbyswing.com. However it
  keeps failing.

  I got it to working with this diff: http://paste.ubuntu.com/10708914/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-plugin-oauth2/+bug/1438393/+subscriptions

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Martin Pitt]

@Colin: nevermind, I can reproduce the wrong shutdown ordering here now.

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1411560] Re: Graphics performance degrades with time in 14.04

[Christopher M. Penalver]

Roberto Sosa Cano, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1411560/comments/12
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1411560

Title:
  Graphics performance degrades with time in 14.04

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After several days using the system the graphics performance degrades.
  I cannot find any information in syslog or dmesg. It takes an awful
  amount of time to open a new window, and during that time the mouse is
  trapped into one of the monitors (cannot move to the other one). Also
  I've noticed that the Unity notification bar freezes and I cannot
  access any of the icons there, and the clock is just frozen.

  HDD, memory and CPU load seem normal. The only solution I've found is
  to reboot.

  Thanks in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan 16 10:08:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed
   nvidia-331, 331.113, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:084a]
  InstallationDate: Installed on 2014-10-15 (93 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Precision WorkStation T5500
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0CRH6C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/20/2011:svnDellInc.:pnPrecisionWorkStationT5500:pvr:rvnDellInc.:rn0CRH6C:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T5500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Jan  9 11:10:54 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.6

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Martin Pitt]

Interesting.. so logind does *not* log a button event; here I get
something like

  Mär 31 11:04:09 donald systemd-logind[805]: Power key pressed.

on a button event.  Can you check if the bug happens:

  1) if you just log into VT1 after boot, not into X, and run sudo
systemctl stop lightdm

  2) if you run initctl stop unity-settings-daemon and initctl stop
indicator-session in the Unity session?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1438587] [NEW] connect button is grey when connecting to Ad-hoc SSID

[Yang Bai]

Public bug reported:

First, I created an adhoc network through nm-applet-create new wifi
network.

Network Name: 111
wi-fi security: WEP 128-bit Passphrase
key: 222

Then click create button and wait for its ready.

using another machine to connect to this 111, enter password 222 and
you can find that the connect button is grey, you can not click it.

** Affects: network-manager
 Importance: Undecided
 Status: New

** Affects: oem-priority
 Importance: High
 Status: New

** Affects: oem-priority/trusty
 Importance: Undecided
 Status: New

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

** Also affects: network-manager
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided = High

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

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

Title:
  connect button is grey when connecting to Ad-hoc SSID

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  First, I created an adhoc network through nm-applet-create new wifi
  network.

  Network Name: 111
  wi-fi security: WEP 128-bit Passphrase
  key: 222

  Then click create button and wait for its ready.

  using another machine to connect to this 111, enter password 222 and
  you can find that the connect button is grey, you can not click it.

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

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

[Touch-packages] [Bug 1438301] Re: desktop machine suspends with systemd after ~3 minutes, does NOT suspend with upstart

[Colin Ian King]

I'm actually running vivid server on this box, so I don't have a unity
session running.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1438301

Title:
  desktop machine suspends with systemd after ~3 minutes, does NOT
  suspend with upstart

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  For reasons I cannot fathom, my development server goes into deep
  suspend after ~3 minutes after startup with systemd, however, if I
  boot with upstart it does not.   This happens everytime I boot with
  systemd, the machine just goes into a deep suspend without me
  requesting it.

  I enabled debug; attached is a gzip'd syslog showing the activity -
  look at the end of the log, it goes into deep suspend. No idea why.

  acpi_listen is showing some curious audio plug/unplug events that seem
  to occur on this development box, so maybe these are being
  misinterpreted as suspend events.

  $ acpi_listen
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug
  jack/headphone HEADPHONE plug
  jack/headphone HEADPHONE unplug

  ..but I am not seeing any other ACPI related events that could be
  triggering a suspend request from acpi_listen.

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

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

[Touch-packages] [Bug 1431200] Re: daemon-reload runs alsa-restore.service and others

[Martin Pitt]

I tried with apt-get install --reinstall systemd udev, several
systemctl daemon-reexec and daemon-reload, but I just don't get this
bug any more. Unit193, do you?

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

** Changed in: systemd (Ubuntu)
   Importance: High = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431200

Title:
  daemon-reload runs alsa-restore.service and others

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd package in Debian:
  New

Bug description:
  When systemd is reloaded (manually, upgrades), the volume is reset,
  likely using alsa-restore.

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

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Martin Pitt]

Colin: I meant with latest wpasupplicant (we already have previous
journals here)

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1431774] Re: network mount hangs on shutdown - NetworkManager needs to stop after network.target

[Martin Pitt]

Colin, can you please get me a journalctl output without the workaround
when this happens? (see comment 3). Thanks!

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

Title:
  network mount hangs on shutdown - NetworkManager needs to stop after
  network.target

Status in network-manager package in Ubuntu:
  Confirmed
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa package in Debian:
  New

Bug description:
  To replicate, perform a manual cifs mount, for example:

  sudo mount -t cifs -o credentials=,user,rw,uid=1000
  //192.168.1.nnn/docs   /media/test_mount

  Then shutdown.  When booted with systemd there is a 1 to 2 minute
  delay before shutdown.  In syslog the last shutdown (09:47:11 13th
  March) showed the effect, though I fear that syslog shuts down too
  early to see anything.

  If booted with upstart there is no noticeable delay on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 09:50:08 2015
  InstallationDate: Installed on 2014-10-21 (142 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017)
  MachineType: FUJITSU LIFEBOOK A544
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago)
  dmi.bios.date: 12/01/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.18
  dmi.board.name: FJNBB35
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A544
  dmi.sys.vendor: FUJITSU

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

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

[Touch-packages] [Bug 1437486] Re: sms notification baloon dont work to send sms directly

[Tiago Salem Herrmann]

Once you are able to reproduce this bug again, can you please check if the 
actual message you replied to is gone from the messaging-menu?
Also, did you reboot your phone to get that working again? Or it simply started 
working again after some time without a reboot?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1437486

Title:
  sms notification baloon dont work to send sms directly

Status in telephony-service package in Ubuntu:
  New

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 1436684] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

[wgroiss]

For me today it seems also the first the bug occured: immediately after
system boot (15.04) and login. No action was possible after typing the
password. After long time of working the hard disc (no mouse pointer was
seen), automatic bug report started. Reproducing was not possible. If it
is later, i give a new comment.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1436684

Title:
  cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

Status in avahi package in Ubuntu:
  Confirmed
Status in cups-filters package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  but appeared after system-bootup and while checking for updates via
  sudo apt-get update  sudo apt-get install -f  sudo apt-get dist-
  upgrade  sudo apt-get upgrade on 15.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CupsErrorLog:
   
  Date: Wed Mar 25 22:32:50 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2014-08-23 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lpstat:
   device for PDF: cups-pdf:/
   device for Photosmart-B110-series: 
dnssd://Photosmart%20B110%20series%20%5B4EC8C9%5D._pdl-datastream._tcp.local/
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   Photosmart-B110-series: HP Photosmart b110 Series, hpcups 3.15.2
   PDF: Generic CUPS-PDF Printer
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic 
root=UUID=79703205-63f2-49b3-bd01-249e7af129dd ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f2060d2d15a:movl   $0x1,0xa8(%rax)
   PC (0x7f2060d2d15a) ok
   source $0x1 ok
   destination 0xa8(%rax) (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to vivid on 2015-03-21 (4 days ago)
  UserGroups:
   
  dmi.bios.date: 05/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: G31M-GS.
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/16/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[John Lea]

** Changed in: ubuntu-ux
 Assignee: (unassigned) = Jouni Helminen (jounihelminen)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Stephen M. Webb]

@Seb is there a way to manually reset the configuration (ie what is the
dconf setting)?

I saw the problem fixed after an upgrade without any manual intervention
and can no longer reproduce on my test systems, but I am willing to
believe my tests systems house gremlins that like to fool me on a
regular basis.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1436297

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Colin Law]

On a vivid which was originally updated from Trusty and is up to date I created 
a new user (via System Settings  User Accts) and logged in as that user.  
Clicking on Files opens a new icon in the launcher.
The desktop file the system has put in the launcher is 
org.gnome.Nautilus.desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1436297

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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

[Touch-packages] [Bug 1438669] [NEW] confirm button in nautilus warning dialog for missing disk space for move target should be Trotzdem verschieben instead of Trotzdem kopieren

[Karl-Philipp Richter]

Public bug reported:

confirm button in nautilus warning dialog for missing disk space for
move target should be Trotzdem verschieben instead of Trotzdem
kopieren

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: language-pack-gnome-de 1:14.10+20141205
Uname: Linux 3.19.3-031903-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 14:37:21 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-26 (63 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: language-pack-gnome-de
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: language-pack-gnome-de (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-de in
Ubuntu.
https://bugs.launchpad.net/bugs/1438669

Title:
  confirm button in nautilus warning dialog for missing disk space for
  move target should be Trotzdem verschieben instead of Trotzdem
  kopieren

Status in language-pack-gnome-de package in Ubuntu:
  New

Bug description:
  confirm button in nautilus warning dialog for missing disk space for
  move target should be Trotzdem verschieben instead of Trotzdem
  kopieren

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: language-pack-gnome-de 1:14.10+20141205
  Uname: Linux 3.19.3-031903-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 31 14:37:21 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-26 (63 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: language-pack-gnome-de
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-de/+bug/1438669/+subscriptions

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Martin Pitt]

Can you confirm that you have wpasupplicant 2.1-0ubuntu7 ? I. e. you
should see

$ systemctl cat wpa_supplicant.service |grep Before
Before=network.target

Your journal looks like it would stop wpa_supplicant before
network.target.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  New

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

Re: [Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module

[jose]

Now that it looks like the package is fixed for Vivid, are there plans 
to backport to Trusty? and do we know when that may be?

Thanks
Jose

On 03/02/2015 09:25 AM, Barry Warsaw wrote:
 We still need to work on backporting to Trusty and doing the SRU.  I
 don't know when I will have time to do that though. :(


-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1290847

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Martin Pitt]

Andy gets this issue as well (http://paste.ubuntu.com/10711795/)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

[Touch-packages] [Bug 1437425] Re: Flight mode broken

[Víctor R . Ruiz]

Ricardo: Just tested and it is fixed.

current build number: 169
device name: krillin
channel: ubuntu-touch/devel-proposed


** Changed in: indicator-network (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1437425

Title:
  Flight mode broken

Status in indicator-network package in Ubuntu:
  Fix Released

Bug description:
  Test case.
  - Open indicator network.
  - Enable flight mode.

  Expected result.
  - Wifi and phone goes offline.

  Actual result.
  - Both wifi and phone remain online.

  current build number: 163
  device name: krillin
  channel: ubuntu-touch/devel-proposed

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

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

[Touch-packages] [Bug 1426559] Re: [Shell] Bring the HUD back to Unity 8

[John Lea]

** Changed in: ubuntu-ux
   Status: Triaged = New

** Changed in: ubuntu-ux
 Assignee: Benjamin Keyser (bjkeyser) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1426559

Title:
  [Shell] Bring the HUD back to Unity 8

Status in Ubuntu UX bugs:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  One of the most innovative, useful, and wildly popular features
  introduced into Unity 7 was the HUD. Unity 8 currently does not have
  it.

  When Unity 8 was started, we had a way of accessing the HUD with a
  long-swipe from the bottom edge. However, the API to use it was late
  in being added to the SDK, and changed in incompatible ways after it
  was available, and as a result only a few apps (including one of my
  own) had taken advantage of it. Moreover user testing showed that the
  swipe-up activation was not easily discover-able by users.

  When the toolbar/header was redesigned and the bottom-edge gesture
  given to app developers, the way of accessing the HUD was removed, and
  the API was removed before the first supported API freeze.

  Before switching to Unity 8 on the desktop we will need to re-
  introduce the HUD into Unity, to avoid a feature regression that many
  have come to expect and appreciate. Moreover, we should re-introduce
  it on the phone so that apps can once again start taking advantage of
  it, so we can learn how to provide new use cases and user interactions
  for phone/tablet apps.

  In order to match, as much as possible, the Unity 7 way of accessing
  the HUD, my recommendation would be to implement it like an Indicator,
  but always on the far left of the panel. Then it would be touch-
  accessible with a swipe down from the top, or switchable from within
  the drop-down of another indicator, placing it at the same screen
  position as it is on the Unity 7 desktop. Placing the window title or
  simple Menu in that location of the panel (or switching between
  them, depending on available space) would aid in discovery of the
  feature.

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

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

[Touch-packages] [Bug 1436351] Re: icon does not change in silent mode

[Jouni Helminen]

Can't replicate this on Meizu - the sound indicator icon changes as
expected. Seems to be a bq specific bug?

So the desired functionality would be to change the volume indicator to
the one with the cross next to it, when phone is in silent mode.

** Changed in: ubuntu-ux
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1436351

Title:
  icon does not change in silent mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  If I pull down on the indicator-network and check 'Silent Mode', the
  icon does not change.

  $ system-image-cli -i
  current build number: 214
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-11 22:07:13
  version version: 214
  version ubuntu: 20150312
  version device: 20150116
  version custom: mako-1.1

  Bug 1367818 seems related, but is marked Fix Released.

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

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

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown

[Martin Pitt]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612

Title:
  remote file systems hang on shutdown

Status in dbus package in Ubuntu:
  New

Bug description:
  (part of bug 1431774). During shutdown, D-Bus stops too early. In
  particular, it stops before NetworkManager and remote-fs.target,  so
  that any network unmount  will cause errors and hang the boot. This
  can be seen with

  $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
  Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
  Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
  Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
  Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
  Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
  Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.

  A quick workaround is to add After=dbus.service to
  /lib/systemd/system/NetworkManager.service's [Unit] section, but this
  should be fixed in a more general fashion.

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

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

Re: [Touch-packages] [Bug 1436724] Re: No prompt to unlock sim after airplane mode

[Merlijn Sebrechts]

@Olga Kemmet: as Michael Zandi said:

The bq hardware seems to be a bit special in that it turns off
the modem completely in flight mode and loses the unlocked state. Ubuntu
touch itself doesn't require to re-enter the sim pin after flight mode.
On the nexus 4 for instance, the SIM card stays unlocked.

2015-03-31 13:20 GMT+02:00 Olga Kemmet 1436...@bugs.launchpad.net:

 I think the UX is not ideal if I have to input my SIM PIN every single
 time I switch off the flight mode. The what i understood it that it only is
 required if the device was rebooted.
 What is the need for a SIM PIN input after flight mode was disabled?

 ** Changed in: ubuntu-ux
Status: New = Incomplete

 ** Changed in: ubuntu-ux
Importance: Undecided = Medium

 ** Changed in: ubuntu-ux
  Assignee: (unassigned) = Olga Kemmet (olga-kemmet)

 ** Summary changed:

 - No prompt to unlock sim after airplane mode
 + [indicators] [SIM PIN] No prompt to unlock sim after airplane mode

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1436724

 Title:
   [indicators] [SIM PIN] No prompt to unlock sim after airplane mode

 Status in the base for Ubuntu mobile products:
   New
 Status in Ubuntu UX bugs:
   Incomplete
 Status in indicator-network package in Ubuntu:
   New
 Status in unity8 package in Ubuntu:
   Invalid

 Bug description:
   BQ phone:

   Steps to reproduce:
   1. Turn airplane mode on
   2. Turn airplane mode off

   Desired effect:
   You get a prompt to unlock your sim cards

   What I got:
   You get no connection and no prompt. Only if you open the network
 panel, you see that your sim is still locked.

   You should get a prompt to unlock your sim after turning off airplane
   mode. Otherwise the user does not know the sim card is still locked.
   The fact that the sim card becomes locked after airplane mode is not
   something you should have to think about as a user.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436724/+subscriptions


-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1436724

Title:
  [indicators] [SIM PIN] No prompt to unlock sim after airplane mode

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Incomplete
Status in indicator-network package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  BQ phone:

  Steps to reproduce:
  1. Turn airplane mode on
  2. Turn airplane mode off

  Desired effect:
  You get a prompt to unlock your sim cards

  What I got:
  You get no connection and no prompt. Only if you open the network panel, 
you see that your sim is still locked.

  You should get a prompt to unlock your sim after turning off airplane
  mode. Otherwise the user does not know the sim card is still locked.
  The fact that the sim card becomes locked after airplane mode is not
  something you should have to think about as a user.

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

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

[Touch-packages] [Bug 1436297] Re: Nautilus launcher icon matching issue (seems due to desktop rename)

[Sebastien Bacher]

works fine here on a daily livecd with updated unity, how did you test
exactly?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1436297

Title:
  Nautilus launcher icon matching issue (seems due to desktop rename)

Status in nautilus package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Boot Latest vivid cd
  2. Select Live session or install
  3. On the live session or installed system open Nautilus
  4. The Nautilus window opens but in the launcher there is now a second window

  EXPECTED:
  I expect all nautilus windows to be linked to the original Nautilus launcher

  ACTUAL:
  A second nautilus launcher appears and all windows are linked to it instead.

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

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