date:20160423

** Changed in: sysvinit (Ubuntu)
Milestone: xenial-updates => None

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

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

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

Title:
improve UTC setting migration on upgrades

Status in sysvinit package in Ubuntu:
Fix Released
Status in sysvinit source package in Xenial:
Fix Committed

Bug description:
[SRU Justification]
On upgrade, some users who have selected a non-default setting for their
clock handling in the installer will see prompts for a conffile they never
edited by hand.

[Regression potential]
Because we are adding a pre-dependency to a package, there is risk of this
causing upgrade failures. The upgrade path should be tested aggressively with
different profiles from both 14.04 and 15.10 before publishing to -updates.

[Test case]
1. On a newly-installed 14.04 system, edit /etc/default/rcS to contain
'UTC=no' instead of 'UTC=yes'. Make no other changes to this file.
2. Enable -proposed in your apt sources.
3. Run do-release-upgrade or update-manager to upgrade to 16.04.
4. Confirm that the upgrade succeeds.
5. Confirm that you are not shown a conffile prompt for /etc/default/rcS on
upgrade.
6. Confirm that /etc/adjtime has been created, with 'LOCAL' as the third line
of the file.
7. Repeat steps 1-6 for a newly-installed 15.10 system.

slangasek | pitti: I see sysvinit Breaks: systemd (<< 228-5ubuntu3), but that
doesn't enforce systemd 228-5ubuntu3 being configured before sysvinit, which
means the conffile may already be migrated away before systemd postinst runs...
I think the right way to do this is with initscripts Pre-Depends: systemd, and
for initscripts' preinst script to handle any conffile cleaning so that users
are spared conffile prompts on upgrade
pitti | slangasek: ah, good point; this needs to be tested thoroughly,
pre-depends have some habit of causing trouble

See bug 1541532 and

http://launchpadlibrarian.net/236311219/systemd_228-5ubuntu2_228-5ubuntu3.diff.gz
and

http://launchpadlibrarian.net/236367969/sysvinit_2.88dsf-59.3ubuntu1_2.88dsf-59.3ubuntu2.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1572752/+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 1473006] Re: [SRU] New upstream release 3.14.15

** Changed in: gtk+3.0 (Ubuntu Vivid)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] New upstream release 3.14.15

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Vivid:
  Won't Fix

Bug description:
  [ Description ]

  New stable bugfix release

  gtk+3.0 (3.14.14-0ubuntu1) UNRELEASED; urgency=medium

* New upstream release 3.14.14, fixing bugs:
  + gtk print dialog shows "Getting printer information failed" for cups
remote printer
  + GtkMenuButton is not disabled even if corresponding GAction is
  + GTK+/Quartz >= 3.14.8: Symbol not found: _gtk_drag_cancel
  + Adwaita : missing background for menu
  + icontheme: don't modify symbolic SVG dimensions when recoloring
  + Recent Chooser Widget doesn't expand
  + gtk3 does apparently ignore replayed events?
  + X11: First mouse wheel event ignored after right click or Alt+Tab or Win
key press
  + Moving the mouse while a stepper is activated causes the scrollbar to
jump to the beginning
  + file picker list box height stretches to match extra widgets area height
  + resource_path value cleared in gtk_image_set_from_resource
  + Deadlock in X11 when setting XSetErrorHandler while another thread is
opening display with XOpenDisplay
  + Memleak when both opening shm and opening file in tmp fail

   -- Iain Lane   Thu, 09 Jul 2015 11:28:26
  +0100

  [ QA & regression potential ]

  This is being uploaded under the GNOME MRE. You're allowed to believe
  upstream that the bugs are really fixed - just give the system a
  general once (or twice) over to see if things still work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1473006/+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 1553211] Re: gnome-software does not treat recommends and suggests as plugins to applications | impossible to install "technical" packages (plugins, kernels...)

2016-04-23 Thread 林博仁

Additional case: User wanted to run Windows application using Wine, but
they can't find it because the software component 'wine-*' isn't shown
in the search results of Ubuntu/GNOME Software.

This is actually happened at
https://www.facebook.com/groups/ubuntu.zh.hant/permalink/1138059266249394/
(Traditional Chinese facebook group)

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

Title:
  gnome-software does not treat recommends and suggests as plugins to
  applications | impossible to install "technical" packages (plugins,
  kernels...)

Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 will be useless for "normal" people if they can't find every 
software package as they did before.
  To force users to use gnome-software will be a regression!

  Examples:

  In old Software Center, you could add gimp plug-ins (plug-ins are recommends 
and suggests packages of gimp) by going in gimp description and check the 
plug-ins you want!
  In old Software Center, you could install another version of linux kernel by 
typing "linux" then click at bottom left to show the packages.

  Now, they have to use apt-get or install synaptic!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  4 15:06:20 2016
  InstallationDate: Installed on 2016-01-07 (57 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160105)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1553211/+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 1512327] Re: [dialer-app] Can't hang up phone calls

2016-04-23 Thread Inoe

** This bug is no longer a duplicate of bug 1528668
   [regression] Qt.application.active not working correctly

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

Title:
  [dialer-app] Can't hang up phone calls

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Recently I had a problem with hanging up. I don't think it was just
  with incoming calls but in that case I was able to reproduce it. I
  have all the recent updates installed and I think the problem only
  occurred after the update to OTA-7.

  - Somebody calls me
  - Name appears in the dialog and I take off
  - The dialer app opens but doesn't show the name nor number nor the calling 
time but the call works
  - It is not possible to hang up the call by pressing the red button
  - I close the dialer app, the green bar at the top appears
  - I reopen it, at this point I might be able to hang up the call otherwise I 
have to redo the closing

  I couldn't find the combination which led to this issue.

  Could be related to bug #1377996.


  - UX comment ---

  The dialer should always show the contact who is calling. Also, it
  should always be possible to hang up the call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512327/+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 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops

** Changed in: upstart (Ubuntu Vivid)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] segfault in log.c code causes phone reboot loops

Status in Canonical System Image:
  Fix Released
Status in upstart :
  Fix Committed
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Won't Fix
Status in upstart source package in Vivid:
  Won't Fix
Status in upstart source package in Wily:
  Fix Released
Status in upstart package in Ubuntu RTM:
  Fix Released

Bug description:
  = Summary =

  The version of Upstart in vivid is affected by a coule of bugs relating
  to the flushing data from early-boot jobs to disk which can both result
  in a crash:

  == Problem 1 ==

  An internal list is mishandled meaning a crash could occur randomly.

  == Problem 2 ==

  Jobs which spawn processes in the background then themselves exit can
  cause a crash due.

  = Explanation of how Upstart flushes early job output =

  If an Upstart job starts *and ends* early in the boot sequence (before
  the log partition is mounted and writable) and produces output to its
  stdout/stderr, Upstart will cache the output for later flushing by
  adding the 'Log' object associated with the 'Job' to a list.

  When the log partition is mounted writable, the
  /etc/init/flush-early-job-log.conf job is run which calls "initctl
  notify-disk-writeable". This is a signal to Upstart to flush its cache
  of early-boot job output which takes the form of iterating the
  'log_unflushed_files' list and flushing all the 'Log' entries to disk.

  = Code Specifics =

  There are 2 issues (note that the numbers used below match those used in
  the Summary).

  == Problem 1 detail ==

  Due to a bug in the way the 'log_unflushed_files' list is handled (the
  'Log' cannot be added to the list directly, so is added via an
  intermediary ('NihListElem') node), a crash can result when iterating
  the list since the 'Log' is freed, but NOT the intermediary node. The
  implication is that it is possible for the intermediary node to be
  attempt to dereference already-freed data, resulting in a crash.

  == Problem 2 detail ==

  If a job spawns a process in the background, then itself exits, that
  jobs 'Log' entry will be added to the 'log_unflushed_files' list. But,
  if the background process produces output and then exits before Upstart
  attempts to flush the original jobs data to disk, the 'NihIo'
  corresponding to the log will be serviced automatically and the data
  flushed to disk. The problem comes when Upstart receives the
  notification to flush the 'log_unflushed_files' list, since that list
  now contains an entry which has already been freed (since all its data
  has already been flushed). The result is an assertion failure.

  = Fix =

  == Problem 1 fix ==

  Correct the 'log_unflushed_files' list handling by freeing the
  'NihListElem' (which will automatically free the 'Log' object), not by
  simply freeing the 'Log' object itself.

  * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/
  * New Upstart test added to avoid regression?: Yes.

  == Problem 2 fix ==

  Correct the assumption that the only entries in the
  'log_unflushed_files' list will always have data to flush by checking if
  there is in fact any data to flush; if not, remove the entry from the
  'log_unflushed_files' list since it has already been handled
  automatically by the 'NihIo'.

  * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix
  * New Upstart test added to avoid regression?: Yes.

  = Workarounds =

  If a system is affected by this bug, it will be manifested by a crash
  early in the boot sequence.

  To overcome the issue, either:

  a) Boot by adding "--no-log" to the kernel command-line.

  b) Disable the flush-early-job-log job (assuming the machine is
  bootable) by running the following:

 $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override

  = Impact =

  The issue has been present in Upstart since logging was introduced but
  no known instances of crashes relating to these problems have been
  reported prior to this bug being reported (which relates the the issue
  being seen on a very small subset of specific Ubuntu Touch phone
  hardware where Upstart is used as the system init daemon).

  Note that vivid still uses Upstart for managing the graphical session,
  but now uses systemd by default for the system init daemon. Since the session 
(Upstart) init does not even require 
  a flush-early-job-log, the exposure to both the bug and the updated fix 
codepath is extremely limited.

  = Test Case =

  This bug is extremely hard to surface so the approach is simply to
  check that the internal list can be iterated correctly by:

  1) Booting the system with upstart
 (select the Upstart o

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

2016-04-23 Thread CaptainPlanet

I experience a similar isses as Tommy. I mounted the NFS manually and
the computer will just not shutdown. Additionally I also failed mounting
the device via fstab but I used different options.

-- 
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, D-BUS stops too early

Status in D-Bus:
  Won't Fix
Status in dbus package in Ubuntu:
  Fix Released

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/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 1535394] Re: Xorg crashes at certain wiki pages via firefox

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Xorg crashes at certain wiki pages via firefox

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi,

  I am having a weird problem in Ubuntu and I will try to explain when
  it happens. When I open Wikipedia main page or View history on any
  wiki page, sometimes (not always) Xorg (I suppose) freezes (UI becomes
  unresponsive for a while about 10-60 seconds) until it jumps to login
  screen. If I login, I need to start all the application all over
  again. Firefox starts but if I repeat the same process (visiting the
  same web page) Xorg crashes again. The two pages so far this behaviour
  occurs are:

  http://en.wikipedia.org (main page, I can however directly open any article 
and navigate from there)
  http://imagej.net/index.php?title=ImgLib2_Examples&action=history (history 
page of a wiki page)

  There are no dialogs after the crash reporting about a crash. I really don't 
know how to track the problem to find the cause.
  Even though Firefox is chrashing, Xorg should not be affected.

  I am using Ubuntu 14.04 LTS

  3.13.0-74-generic

  X.Org X Server 1.15.1
  Release Date: 2014-04-13
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-76-generic x86_64 Ubuntu
  Current Operating System: Linux lngrad031 3.13.0-74-generic #118-Ubuntu SMP 
Thu Dec 17 22:52:10 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=aa4cedea-18e5-4b0f-86ac-3423c2221c78 ro acpi_osi=Linux quiet splash 
acpi_backlight=vendor vt.handoff=7
  Build Date: 12 February 2015  02:49:29PM
  xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.30.2
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.

  unity 7.2.6

  I could only capture a line in x-0.log.old file with only "(EE)". (no
  explanation or whatsoever)

  Please don't hesitate to ask for more information.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5036]
  MachineType: LENOVO 20BX000XMH
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=aa4cedea-18e5-4b0f-86ac-3423c2221c78 ro acpi_osi=Linux quiet splash 
acpi_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-74-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET49WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XMH
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BX000XMH:pvrThinkPadT450s:rvnLENOVO:rn20BX000XMH:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XMH
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Jan 18 18:35:47 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4925 
   vendor AUO
  xserver.ver

[Touch-packages] [Bug 1485334] Re: No content to display on send a SMS to yourself.

[Expired for messaging-app (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: messaging-app (Ubuntu)
   Status: Incomplete => Expired

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

Title:
No content to display  on send a SMS to yourself.

Status in messaging-app package in Ubuntu:
  Expired

Bug description:
  Test Environment:
  $ system-image-cli -i
  current build number: 98
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-08-16 09:38:54
  version version: 98
  version ubuntu: 20150814
  version device: 20150804-7bba081
  version custom: 20150814-887-30-30-vivid

  Reproduce steps:
  1.Open the messaging application
  2.Send a SMS to yourself

  Actual result:
  After step 2: Got this SMS but no content to display  and this message that 
display on information bar  can't delete

  Expected result:
   Content to display  on send a SMS to yourself.

  Other info:This is not issue for arale

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1485334/+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 1562733] Re: apt signature requierements prevent updates from some repositories

2016-04-23 Thread Lonnie Lee Best

Here's how I'm dealing with it for now:
http://askubuntu.com/a/760348/256054

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

Title:
  apt signature requierements prevent updates from some repositories

Status in apt package in Ubuntu:
  In Progress

Bug description:
  Since xenial updated the requirements for the strength of PGP
  signatures of packages, packages from some repositories are no longer
  updated. Apt-get update reports these errors:

  E: Failed to fetch http://[...]/Release  No Hash entry in Release file 
/var/lib/apt/lists/partial/[...] which is considered strong enough for security 
purposes
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While the motivation for the change is valid, the result is a
  potential security problem, as the new versions of the packages that
  may fix recently discovered vulnerabilities are not automatically
  installed.

  One less important but unfortunate effect is a scary message that is
  displayed to the user, without clear explanation that the problem
  needs to be addressed by the repository owner.

  Related: Bug #1558331

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+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 1574154] [NEW] xorg.conf changed on start of lightdm service

2016-04-23 Thread Jos Nouwen

Public bug reported:

After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It
appears that my xorg.conf is modified such that I get a non-working way
(I get a coredump in the video driver I think). I have a Thinkpad T530
with dual video cards, so I change the from the nvidia that is
somewere(?) auto selected back to intel. Alas, restarting of lightdm
service does not work: xorg.conf is re-modified. Manually starting a X
session with 'startx' (after correcting xorg.conf) works as expected.
Alas, nobody logs about this; that would have helped me find the
culprit..

Who modifies my xorg.conf? Why? This never happened before, and should
IMHO not be done.

Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto-
changing impossible. But this is a hack. I should be allowed to change
my system such that it works the way I want.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 24 05:45:17 2016
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)

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


** Tags: amd64 apport-bug crash xenial

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

Title:
  xorg.conf changed on start of lightdm service

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading from 15.10 (Wily) to 16.04 (Xenial), X wont start. It
  appears that my xorg.conf is modified such that I get a non-working
  way (I get a coredump in the video driver I think). I have a Thinkpad
  T530 with dual video cards, so I change the from the nvidia that is
  somewere(?) auto selected back to intel. Alas, restarting of lightdm
  service does not work: xorg.conf is re-modified. Manually starting a X
  session with 'startx' (after correcting xorg.conf) works as expected.
  Alas, nobody logs about this; that would have helped me find the
  culprit..

  Who modifies my xorg.conf? Why? This never happened before, and should
  IMHO not be done.

  Temporary solution: 'chattr +i /etc/X11/xorg.conf'. This makes auto-
  changing impossible. But this is a hack. I should be allowed to change
  my system such that it works the way I want.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr 24 05:45:17 2016
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574154/+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 1557227] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-04-23 Thread DJ_Spies

I received this error during an upgrade from 15.10 and now the install
has hung.

** Attachment added: "Screenshot of hung install"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1557227/+attachment/4644882/+files/Screenshot%20from%202016-04-23%2022-51-15.png

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  after running the upgrade script errors were reported.
  Logon doesn't complete. Used to log me right out.
  I did apt-get upgrade/update and now log on leads to an empty screen.

  Release 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Mar 14 10:35:43 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-05 (69 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1557227/+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 1574153] [NEW] 'Contacts' forces portrait position

2016-04-23 Thread Bob Harvey

Public bug reported:

On the M10 tablet, running OTA9.5,  opening 'contacts' forces you to
turn the device from Landscape to Portrait.

I would expect the app to honour the device orientation.

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  'Contacts' forces portrait position

Status in address-book-app package in Ubuntu:
  New

Bug description:
  On the M10 tablet, running OTA9.5,  opening 'contacts' forces you to
  turn the device from Landscape to Portrait.

  I would expect the app to honour the device orientation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574153/+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 1564156] Re: xenial: invalid opcode when using llvmpipe

** Changed in: llvm-toolchain-3.8 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: llvm-toolchain-3.8 (Ubuntu Xenial)
   Importance: Undecided => Critical

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Committed
Status in System76:
  Fix Committed
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Confirmed

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note the above work-around wont work till 
  llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently 
only in xenial-proposed). FIXME: update description once this happens.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1,
  which has a bug that results in invalid JIT code generation when using
  the mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1574067] Re: Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Never had the issue on 14.04, comes on every reboot on 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 22 13:27:18 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-17 (462 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1574067/+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 1005677] Fw: new message

2016-04-23 Thread davidryman

Hello!


You have a new message, please read



li...@davidryman.com

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

Title:
  Re-emergence of "Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion
  `GTK_IS_WIDGET   (widget)'" Makes vlc and other Qt apps crash

Status in overlay-scrollbar:
  Fix Released
Status in Ubuntu One Control Panel:
  Invalid
Status in Unity Distro Priority:
  Fix Released
Status in overlay-scrollbar package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Invalid
Status in overlay-scrollbar source package in Quantal:
  Fix Released
Status in qt4-x11 source package in Quantal:
  Invalid

Bug description:
  The symptoms of this bug have re-emerged in 12.10 (Bug  805303) and in
  13.04 (Bug 1084255).

  Current test cases:
  May not happen the 1st try

  Open vlc  > Media > Open Disc
  Open vlc > Tools > Preferences > click on " Show Settings > all" radio button
  Open calibre after initial setting up
  Use cola git gui
  Open a file from context menu > open with Vlc Media Player, then switch to 
'Show Playlist'

  In both all using LIBOVERLAY_SCROLLBAR=0  prevents bad behavior (same
  as previous bug

  In the case of vlc once bug occurs you must remove ~.config/vlc/vlc-
  qt-inferface.conf first before running with the
  LIBOVERLAY_SCROLLBAR=0

  Ex of sizing  "Open Media" window in vlc

  xwininfo: Window id: 0x1e0004b "Open Media"

    Absolute upper-left X:  -7566
    Absolute upper-left Y:  367
    Relative upper-left X:  3
    Relative upper-left Y:  3
    Width: 16383
    Height: 421
    Depth: 24
    Visual: 0x21
    Visual Class: TrueColor
    Border width: 0
    Class: InputOutput
    Colormap: 0x20 (installed)
    Bit Gravity State: NorthWestGravity
    Window Gravity State: NorthWestGravity
    Backing Store State: NotUseful
    Save Under State: no
    Map State: IsViewable
    Override Redirect State: no
    Corners:  +-7566+367  --7537+367  --7537-12  +-7566-12
    -geometry 16383x421+-7569-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1005677/+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 1553417] Re: obex-check-device crashed with SIGSEGV in GI___strtoul_l_internal()

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

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

** Changed in: libopenobex (Ubuntu)
   Status: New => Confirmed

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

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  Confirmed

Bug description:
nothing observed   system seems ok

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex2 1.7.1-4
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Mar  4 20:25:12 2016
  Dependencies:
   gcc-6-base 6-20160227-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160227-0ubuntu1
   libudev1 229-2ubuntu1
   libusb-1.0-0 2:1.0.20-1
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2016-01-22 (42 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  ProcCmdline: /usr/sbin/obex-check-device 046d
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f7b8ef71674 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7f7b8ef71674) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f7b8f2fb500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1553417/+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 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

2016-04-23 Thread Sworddragon

Has using -vv any additional effect (because only -v is documented in
the strace manpage)? Anyways, in the attachments is the requested
output.

** Attachment added: "strace.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+attachment/4644822/+files/strace.log

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

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root@ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Operation failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1545707/+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 1571500] Re: serial-getty@.service does not configure baud rate

2016-04-23 Thread Phillip Susi

Because it renders the baud rate setting inoperable?  Or are you
supposed to set the baud rate using some other mechanism, and thus, it
is intended that this script should not modify it?

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

Title:
  serial-getty@.service does not configure baud rate

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I want to add a console port on a Ubuntu machine to be able to access
  it from a terminal server.

  This machine has no serial port but lots of USB ports (like most nowadays).
  I use a USB-to-serial adapter to have the ttyUSB0 up and listening.

  I copied /lib/systemd/system/serial-getty@.service to
  /lib/systemd/system/serial-getty@ttyUSB0.service and set the speed to
  57600

  +++
  [Service]
  ExecStart=-/sbin/agetty --keep-baud 57600 %I $TERM
  +++

  the service status shows the right speed

  +++
  $ sudo systemctl status serial-getty@ttyUSB0.service
  ● serial-getty@ttyUSB0.service - Serial Getty on ttyUSB0
 Loaded: loaded (/lib/systemd/system/serial-getty@ttyUSB0.service; enabled; 
vendor preset: enabled)
 Active: active (running) since 月 2016-04-18 14:07:30 JST; 58min ago
   Docs: man:agetty(8)
 man:systemd-getty-generator(8)
 http://0pointer.de/blog/projects/serial-console.html
   Main PID: 3017 (agetty)
 CGroup: 
/system.slice/system-serial\x2dgetty.slice/serial-getty@ttyUSB0.service
 └─3017 /sbin/agetty --keep-baud 57600 ttyUSB0 vt220
  +++

  Even so, I can't log in from the serial port at a speed other than
  9600...

  With such settings I shouldn't even be able to get a right answer at
  9600bps, only garbage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1571500/+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 1571886] Re: NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

2016-04-23 Thread Steve Langasek

On Sat, Apr 23, 2016 at 08:10:21PM -, Steve wrote:
> It may not be the same output, however the upgrade from 14.04 to 16.04
> is causing me the exact same problem you're experiencing.

No, it is not.  Please file a separate bug for your unrelated issue.

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

Title:
  NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Twice today, NM 1.1.93 has dropped my wifi connection.  I don't know
  why and haven't looked; the connection is usually stable since the AP
  is in the room with my laptop, but perhaps there's something up with
  the kernel I'm currently running.

  However, the serious bug that I'm reporting is that when the wifi
  connection dropped, nothing told me that this had happened.  nm-
  applet's display did not update; there was no automatic reconnect
  attempt; even the VPN process, which was no longer operational because
  it had lost its route to the VPN endpoint, was still running (and the
  lock icon still shown on nm-applet).

  Only when I looked at my routing table to see what was going on did
  the problem become apparent.

  Since this has already happened twice today, I can probably get more
  debugging information "soon" if needed - just ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 15:39:18 2016
  InstallationDate: Installed on 2010-09-24 (2033 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WWanEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (3 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571886/+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 1564156] Re: xenial: invalid opcode when using llvmpipe

2016-04-23 Thread Joel Heinzel

Thank you Joakim!

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Committed
Status in System76:
  Fix Committed
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Confirmed

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note the above work-around wont work till 
  llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently 
only in xenial-proposed). FIXME: update description once this happens.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1,
  which has a bug that results in invalid JIT code generation when using
  the mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+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 1574132] [NEW] package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread ka8ztlb

Public bug reported:

Simply showed this as an error and that the upgrade may have left the
system unusable.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: colord 1.2.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 23 19:04:26 2016
DuplicateSignature:
 Setting up colord (1.2.12-1ubuntu1) ...
 chown: invalid group: ‘colord:colord’
 dpkg: error processing package colord (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-04-25 (728 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: colord
Title: package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in colord package in Ubuntu:
  New

Bug description:
  Simply showed this as an error and that the upgrade may have left the
  system unusable.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: colord 1.2.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 19:04:26 2016
  DuplicateSignature:
   Setting up colord (1.2.12-1ubuntu1) ...
   chown: invalid group: ‘colord:colord’
   dpkg: error processing package colord (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-25 (728 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: colord
  Title: package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1574132/+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 1574132] Re: package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread 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 colord in Ubuntu.
https://bugs.launchpad.net/bugs/1574132

Title:
  package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in colord package in Ubuntu:
  New

Bug description:
  Simply showed this as an error and that the upgrade may have left the
  system unusable.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: colord 1.2.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 19:04:26 2016
  DuplicateSignature:
   Setting up colord (1.2.12-1ubuntu1) ...
   chown: invalid group: ‘colord:colord’
   dpkg: error processing package colord (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-25 (728 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: colord
  Title: package colord 1.2.12-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1574132/+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 1550490] Re: network-manager unresponsive after suspend

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

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

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

Title:
  network-manager unresponsive after suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using an Ubuntu OEM image on the Dell Precision 5510. After
  unboxing and applying all updates (running apt-get update/upgrade
  multiple times), if I suspend the system, when it comes back,
  networking shows as "disabled". The network interfaces however are
  still up. Once I kill the NetworkManager process, networking comes
  back.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 11:43:28 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-25 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  IpRoute:
   default via 172.24.64.1 dev wlan0  proto static 
   172.24.64.0/19 dev wlan0  proto kernel  scope link  src 172.24.67.197  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   sfo3  aa8c189d-e8dd-429b-948f-025579dfbe33   
802-11-wireless   1456515772   Fri 26 Feb 2016 11:42:52 AM PSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   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/ubuntu/+source/network-manager/+bug/1550490/+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 1573428] Re: network-manager not finding any wifi network

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

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

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

Title:
  network-manager not finding any wifi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Sometimes network-manager stops finding any wifi network. I'm still
  investigating in what circumstances does it happen. The last time it
  happened after logging out and back in (switching optimus GPU).

  Workaround:
  sudo service network-manager restart

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 08:49:03 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-21 (397 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.106  
metric 600
  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  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/0  
lxcbr0  7fd1e377-d0ea-4999-b2a6-5011fe4cfa3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
GONNESA e19c4e31-7de8-4c0d-a7db-47d4b59a55c8  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573428/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

Had to find my beaglebone and LTS card, but I went ahead and back-ported
the patch to upower_0.9.23 (and did my best to follow the gist of the
deb/ubuntu packaging stuff).  Attached are the packages.

** Attachment added: "gir1.2-upowerglib-1.0_0.9.23-3ubuntu1_armhf"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4644793/+files/gir1.2-upowerglib-1.0_0.9.23-3ubuntu1_armhf.deb

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

Package 2.

** Attachment added: "libupower-glib1_0.9.23-3ubuntu1_armhf"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4644794/+files/libupower-glib1_0.9.23-3ubuntu1_armhf.deb

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

Package 3.

** Attachment added: "libupower-glib-dev_0.9.23-3ubuntu1_armhf"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4644795/+files/libupower-glib-dev_0.9.23-3ubuntu1_armhf.deb

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

Package 4.

** Attachment added: "upower_0.9.23-3ubuntu1_armhf"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4644796/+files/upower_0.9.23-3ubuntu1_armhf.deb

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

Docs package.

** Attachment added: "upower-doc_0.9.23-3ubuntu1_all"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4644797/+files/upower-doc_0.9.23-3ubuntu1_all.deb

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1511817] Re: bluetoothd consumes 100% CPU when scanning for devices, system hangs

2016-04-23 Thread Julius Schwartzenberg

I'm seeing bluetoothd using 100% CPU permanently on 16.04, Xenial.

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

Title:
  bluetoothd consumes 100% CPU when scanning for devices, system hangs

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to use the bluedevil wizard on Kubuntu 15.04  to add a new device 
(BT headset). The scan window opens but no device is found.
  Meanwhile, both cpu and memory usage start to increase until memory is 100% 
full and the system hangs!
  If I just kill bluedevil, then dbus-daemon keeps using 100% cpu, the only way 
to stop it is by manually stopping the bluetooth service.

  $ uname -a
  Linux Home1 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:23:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ hciconfig -a
  hci0:   Type: BR/EDR  Bus: USB
  BD Address: 44:39:C4:19:43:C9  ACL MTU: 1022:8  SCO MTU: 183:5
  DOWN 
  RX bytes:564 acl:0 sco:0 events:29 errors:0
  TX bytes:358 acl:0 sco:0 commands:29 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 

  $ rfkill list
  1: dell-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  2: dell-bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: no
  3: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  4: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  $ lsmod | grep blue
  bluetooth 491520  23 bnep,ath3k,btusb,rfcomm

  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
  Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. 
  Bus 004 Device 002: ID 8087:8000 Intel Corp. 
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 0c45:649d Microdia 
  Bus 003 Device 002: ID 8087:8008 Intel Corp. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ lsusb -s 004:005 -v

  Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. 
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass  224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize064
idVendor   0x0cf3 Atheros Communications, Inc.
idProduct  0x817a 
bcdDevice0.02
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  177
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  4 
  bmAttributes 0xe0
Self Powered
Remote Wakeup
  MaxPower  100mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass   224 Wireless
bInterfaceSubClass  1 Radio Frequency
bInterfaceProtocol  1 Bluetooth
iInterface  0 
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0010  1x 16 bytes
  bInterval   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   1
  Interface Descriptor:
bLength

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

2016-04-23 Thread Pawel

Hi again,

this repair problem:

sudo systemctl enable NetworkManager.service

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1511817] Re: bluetoothd consumes 100% CPU when scanning for devices, system hangs

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

** Changed in: bluez (Ubuntu)
   Status: New => Confirmed

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

Title:
  bluetoothd consumes 100% CPU when scanning for devices, system hangs

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to use the bluedevil wizard on Kubuntu 15.04  to add a new device 
(BT headset). The scan window opens but no device is found.
  Meanwhile, both cpu and memory usage start to increase until memory is 100% 
full and the system hangs!
  If I just kill bluedevil, then dbus-daemon keeps using 100% cpu, the only way 
to stop it is by manually stopping the bluetooth service.

  $ uname -a
  Linux Home1 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:23:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ hciconfig -a
  hci0:   Type: BR/EDR  Bus: USB
  BD Address: 44:39:C4:19:43:C9  ACL MTU: 1022:8  SCO MTU: 183:5
  DOWN 
  RX bytes:564 acl:0 sco:0 events:29 errors:0
  TX bytes:358 acl:0 sco:0 commands:29 errors:0
  Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x8f
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH HOLD SNIFF 
  Link mode: SLAVE ACCEPT 

  $ rfkill list
  1: dell-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  2: dell-bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: no
  3: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  4: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  $ lsmod | grep blue
  bluetooth 491520  23 bnep,ath3k,btusb,rfcomm

  $ lsusb
  Bus 004 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
  Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. 
  Bus 004 Device 002: ID 8087:8000 Intel Corp. 
  Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 0c45:649d Microdia 
  Bus 003 Device 002: ID 8087:8008 Intel Corp. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ lsusb -s 004:005 -v

  Bus 004 Device 005: ID 0cf3:817a Atheros Communications, Inc. 
  Couldn't open device, some information will be missing
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   1.10
bDeviceClass  224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize064
idVendor   0x0cf3 Atheros Communications, Inc.
idProduct  0x817a 
bcdDevice0.02
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  177
  bNumInterfaces  2
  bConfigurationValue 1
  iConfiguration  4 
  bmAttributes 0xe0
Self Powered
Remote Wakeup
  MaxPower  100mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass   224 Wireless
bInterfaceSubClass  1 Radio Frequency
bInterfaceProtocol  1 Bluetooth
iInterface  0 
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0010  1x 16 bytes
  bInterval   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   1
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

2016-04-23 Thread Pawel

In the 16.04 LTS problem still persists.

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

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1574053] Re: [Gmail] Notification opens mobile version in frieza

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

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Gmail] Notification opens mobile version in frieza

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Open Gmail.
  - Introduce credentials.
  - Close Gmail.
  - From another device, send an email to the Gmail account.
  - When the notification arrives, don't dismiss it. Open the indicator, and 
tap on the right icon to open Gmail.

  Expected result.
  - Gmail is opened in desktop mode.

  Actual result.
  - Webbrowser opens Gmail's mobile version.

  current build number: 89
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574053/+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 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

2016-04-23 Thread Yavor Nikolov

** Description changed:

  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.
  
  ===
  The current behaviour is:
  
  When I boot short after the Grub login screen I'm getting log messages
  like:
  
  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---
  
  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:
  
  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---
  
  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).
  
  ===
- One workaround so far is creating 
/etc/initramfs-tools/scripts/init-premount/lvm2 script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.
+ One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.
  
  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).
  
  ===
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  ===
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+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 1574079] Re: USB audio device is not recognized after startup in 16.04

2016-04-23 Thread TheBigW

I read the description of what fwupd does and if it really is just UEFI BIOS 
related it won't matter on my older machine I thought and just got rid of it 
(apt-get purge). What shall I see: after restart my USB audio device worked out 
of the box - seems this issue is not alsa - related at all.
I updated my 2nd lubuntu machine to 16.10 with another class compliant USB 
device (RME Fireface UCX) and it worked out of the box.

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574079/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-04-23 Thread Till Kamppeter

** Changed in: cups-filters (Ubuntu)
   Status: Fix Released => Confirmed

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

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Confirmed
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1574020] Re: Can't use networkmanager from lightdm

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

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

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

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1574020] Re: Can't use networkmanager from lightdm

2016-04-23 Thread Steven Partridge

Also affects me, fresh install Dell vostro 3750.

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

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-04-23 Thread Richard Elkins

Two different Epson printers are working with the printer-driver-escpr
package.

** Project changed: lsb => epson-inkjet-printer-escpr (Ubuntu)

** Changed in: epson-inkjet-printer-escpr (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1568094] Re: Many error message such as "Start request repeated too quickly."

2016-04-23 Thread jondee

I am having the exact same issue as the original poster. I see they
haven't replied so I'll give you my output: :)

` systemctl show systemd-binfmt.service |grep By`:
WantedBy=sysinit.target


** Attachment added: "dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1568094/+attachment/4644719/+files/dump.txt

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when I look at journalctl's output, I see many error messages of the
  same type:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to Console Directory Watch.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

2016-04-23 Thread jondee

BTW I am running Ubuntu 16.04 (Release) upgraded from Ubuntu 15.10.

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when I look at journalctl's output, I see many error messages of the
  same type:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to Console Directory Watch.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start reque

[Touch-packages] [Bug 1574118] [NEW] M10 tablet has phone app

2016-04-23 Thread Bob Harvey

Public bug reported:

M10 tablet, delivered with 15.04 OTA9.5 Fireza, has a phone app.you can
even dial a number, but it complains of having 'no network'.  Hardly
surprising.  It has no sim, and no cellphone radio.

The phone appp needs to be uninstalled when you can't use it.

Sloppy.

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  M10 tablet has phone app

Status in address-book-app package in Ubuntu:
  New

Bug description:
  M10 tablet, delivered with 15.04 OTA9.5 Fireza, has a phone app.you
  can even dial a number, but it complains of having 'no network'.
  Hardly surprising.  It has no sim, and no cellphone radio.

  The phone appp needs to be uninstalled when you can't use it.

  Sloppy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574118/+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 1574115] [NEW] Google accounts sign in as safari

2016-04-23 Thread Bob Harvey

Public bug reported:

During the setup process I was given the chance to create new accounts.
I had hoped there would be some way to share what is already running on
my ubuntu phone, but couldn't.

So I created, among others, 4 gmail accounts, and set up all acesses for
all of them.

As I was doing this I got a stream of security warnings by email, grom
google, warning me of activity on a new device.  See screenshot.

But in every case the access was reported as coming from Safari.  Should
that not be Ubunto, in some form?

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screen grab of warning emails"
   https://bugs.launchpad.net/bugs/1574115/+attachment/4644705/+files/image.png

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

Title:
  Google accounts sign in as safari

Status in address-book-app package in Ubuntu:
  New

Bug description:
  During the setup process I was given the chance to create new
  accounts.  I had hoped there would be some way to share what is
  already running on my ubuntu phone, but couldn't.

  So I created, among others, 4 gmail accounts, and set up all acesses
  for all of them.

  As I was doing this I got a stream of security warnings by email, grom
  google, warning me of activity on a new device.  See screenshot.

  But in every case the access was reported as coming from Safari.
  Should that not be Ubunto, in some form?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1574115/+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 1505507] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

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

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

** Changed in: libunity (Ubuntu)
   Status: New => Confirmed

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

Title:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 13 08:27:37 2015
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2015-10-10 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151010)
  ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6834f9d3d0 : 
movzbl 0xc0(%rdi),%eax
   PC (0x7f6834f9d3d0) ok
   source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   g_desktop_app_info_get_is_hidden () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/libgnome-menu-3.so.0
   ?? () from /usr/lib/libgnome-menu-3.so.0
   gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
  Title: unity-scope-loader crashed with SIGSEGV in 
g_desktop_app_info_get_is_hidden()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1505507/+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 1574107] [NEW] busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such file or directory"

2016-04-23 Thread TJ

Public bug reported:

Working on 16.04 and trying to solve some unrelated issues due to a
complex initrd set-up I discovered that the included "modinfo" tool
doesn't work, whether given just a module name or an absolute path to
the .ko file.

In this case it always reports, e.g:

(initramfs) pwd
/lib/modules/4.4.0-21-generic/kernel/drivers/md

(initramfs) modinfo dm-crypt
modinfo: can't open '/4.4.0-21-generic/': No such file or directory

(initramfs) modinfo /lib/modules/4.4.0-21-generic/kernel/drivers/md/dm-crypt.ko
modinfo: can't open '/4.4.0-21-generic/': No such file or directory

There seems there may be a related issue with modprobe too, as I've
found it doesn't always insert a module when instructed to - also using
either just name, or absolute path. In the specific case here I was
working with a LUKS/dm-crypt rootfs, where the initrd.img had been
generated using "MODULES=dep" and hadn't included dm-crypt.ko.

I connected a USB storage device with an identical root file-system
(same kernel version, etc.) at /mnt/USB/ and was trying to use:

(initramfs) modprobe -v -d /mnt/USB dm-crypt 
modprobe: FATAL: Module dm-crypt not found in directory 
/mnt/USB/lib/modules/4.4.0-21-generic

I'm *assuming* this is because despite setting the alternate root
directory with "-d" it is still looking at the "modules.dep" in
/lib/modules/4.4.0-21-generic rather than prefixing the "-d" alternate
root.

Using a chroot the module(s) can be loaded and the block device
unlocked:

(initramfs) chroot /mnt/USB
(initramfs) modprobe dm-crypt
(initramfs) modprobe aesni-intel
(initramfs) modprobe xts
(initramfs) exit
(initramfs) grep dm_crypt /proc/modules
dm_crypt 28672 0 - Live 0xc02fa000

(initramfs) LD_LIBRARY_PATH=/mnt/USB/lib/x86_64-gnu-linux
/mnt/USB/sbin/cryptsetup open /dev/sda4 LUKS_VG02 --type luks

(initramfs) blkid /dev/mapper/LUKS_VG02
/dev/mapper/LUKS_VG02: UUID="..." TYPE="LVM2_member"

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

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

Title:
  busybox-initramfs: modinfo reports "can't open '/${VERSION}/': No such
  file or directory"

Status in busybox package in Ubuntu:
  New

Bug description:
  Working on 16.04 and trying to solve some unrelated issues due to a
  complex initrd set-up I discovered that the included "modinfo" tool
  doesn't work, whether given just a module name or an absolute path to
  the .ko file.

  In this case it always reports, e.g:

  (initramfs) pwd
  /lib/modules/4.4.0-21-generic/kernel/drivers/md

  (initramfs) modinfo dm-crypt
  modinfo: can't open '/4.4.0-21-generic/': No such file or directory

  (initramfs) modinfo 
/lib/modules/4.4.0-21-generic/kernel/drivers/md/dm-crypt.ko
  modinfo: can't open '/4.4.0-21-generic/': No such file or directory

  There seems there may be a related issue with modprobe too, as I've
  found it doesn't always insert a module when instructed to - also
  using either just name, or absolute path. In the specific case here I
  was working with a LUKS/dm-crypt rootfs, where the initrd.img had been
  generated using "MODULES=dep" and hadn't included dm-crypt.ko.

  I connected a USB storage device with an identical root file-system
  (same kernel version, etc.) at /mnt/USB/ and was trying to use:

  (initramfs) modprobe -v -d /mnt/USB dm-crypt 
  modprobe: FATAL: Module dm-crypt not found in directory 
/mnt/USB/lib/modules/4.4.0-21-generic

  I'm *assuming* this is because despite setting the alternate root
  directory with "-d" it is still looking at the "modules.dep" in
  /lib/modules/4.4.0-21-generic rather than prefixing the "-d" alternate
  root.

  Using a chroot the module(s) can be loaded and the block device
  unlocked:

  (initramfs) chroot /mnt/USB
  (initramfs) modprobe dm-crypt
  (initramfs) modprobe aesni-intel
  (initramfs) modprobe xts
  (initramfs) exit
  (initramfs) grep dm_crypt /proc/modules
  dm_crypt 28672 0 - Live 0xc02fa000

  (initramfs) LD_LIBRARY_PATH=/mnt/USB/lib/x86_64-gnu-linux
  /mnt/USB/sbin/cryptsetup open /dev/sda4 LUKS_VG02 --type luks

  (initramfs) blkid /dev/mapper/LUKS_VG02
  /dev/mapper/LUKS_VG02: UUID="..." TYPE="LVM2_member"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1574107/+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 1571886] Re: NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

2016-04-23 Thread Steve

@Steve Langsek

It may not be the same output, however the upgrade from 14.04 to 16.04
is causing me the exact same problem you're experiencing. That is the
only error output that I am able to locate when it occurs. The
possibility that they are related due to similarity may be pertinent to
its resolution.

Thank you.

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

Title:
  NM 1.1.93 in xenial silently loses wifi connection (no GUI feedback)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Twice today, NM 1.1.93 has dropped my wifi connection.  I don't know
  why and haven't looked; the connection is usually stable since the AP
  is in the room with my laptop, but perhaps there's something up with
  the kernel I'm currently running.

  However, the serious bug that I'm reporting is that when the wifi
  connection dropped, nothing told me that this had happened.  nm-
  applet's display did not update; there was no automatic reconnect
  attempt; even the VPN process, which was no longer operational because
  it had lost its route to the VPN endpoint, was still running (and the
  lock icon still shown on nm-applet).

  Only when I looked at my routing table to see what was going on did
  the problem become apparent.

  Since this has already happened twice today, I can probably get more
  debugging information "soon" if needed - just ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 15:39:18 2016
  InstallationDate: Installed on 2010-09-24 (2033 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WWanEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-15 (3 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571886/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-04-23 Thread Michael

I tried the printer-driver-escpr package from Ubuntu 16.04 with my Epson 
ET-4550 and it works well.
Thanks Richard!

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  Confirmed
Status in cups-filters package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsb/+bug/1536353/+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 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update

2016-04-23 Thread Grief

https://bugs.kde.org/show_bug.cgi?id=362141 <- fixed in upstream, can it
be merged urgently?

** Bug watch added: KDE Bug Tracking System #362141
   https://bugs.kde.org/show_bug.cgi?id=362141

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

Title:
  [Kubuntu] Fail to connect to wifi after a recent update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I installed the recent updates in the Update Manager and after rebooting I 
wasn't able to connect to my wifi network anymore.
  It attempts to connect to the network and fails with the following error 
message:

  Failed to update connection [network name]
  connection.gateway-ping-timeout: can not set property:
  value "46730064" of type 'guint' is invalid or out of range for property 
'gateway-ping-timeout' of type 'guint'

  I am able to use wired connection.

  1. release:
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. network-manager version:
  network-manager:
Installed: 1.1.93-0ubuntu3
Candidate: 1.1.93-0ubuntu3
Version table:
   *** 1.1.93-0ubuntu3 500
  500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expected the machine to connect to wifi as always

  4. it failed to connect with the above error message

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 13 06:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-01 (11 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  IpRoute:
   default via 10.100.102.1 dev enp0s31f6  proto static  metric 100 
   10.100.102.0/24 dev enp0s31f6  proto kernel  scope link  src 10.100.102.5  
metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-12T22:28:14.870844
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s31f6  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  d956dc0d-4de6-4f45-8869-a3703d8d0d28  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0 wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569674/+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 1559308] Re: Plugging HDMI screen in causes system hang

2016-04-23 Thread dlh

>If I plug in an external HDMI monitor (FHD) either into either HDMI
port (there's one on the machine and there's one available via a usb 3.1
extra adaptor) then the whole system hangs, completely unresponsive and
needing a hard reboot. Before hanging the 2nd display gets an image as
expected, but the laptop's screen flashes randomly, sometimes you see
weird artifacts. Then the hang comes.

Exactly the same happens on my laptop HP ProBook 640 G2 with Intel
driver.

In addition trying to switch tty with ctrl+alt+f{1,7} does not work
either. Hard reboot only helps.

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

Title:
  Plugging HDMI screen in causes system hang

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a 4K UHD laptop screen and am running Ubuntu Gnome 16.04 Beta1
  using 4.4.0-13-generic and the Nouveau drivers.

  If I plug in an external HDMI monitor (FHD) either into either HDMI
  port (there's one on the machine and there's one available via a usb
  3.1 extra adaptor) then the whole system hangs, completely
  unresponsive and needing a hard reboot. Before hanging the 2nd display
  gets an image as expected, but the laptop's screen flashes randomly,
  sometimes you see weird artifacts. Then the hang comes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar 18 20:43:42 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06e4]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:06e4]
  InstallationDate: Installed on 2016-03-15 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=b026feed-8801-44f4-9f3f-c245f4a1f25e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar 18 17:28:07 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV117
   SynPS/2 Synaptics TouchPad: Read error 19
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5182 
   vendor SHP
  xserver.version: 2:1.18.1-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559308/+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 1574100] [NEW] System won't power off

2016-04-23 Thread Tom

Public bug reported:

Since I clean installed Ubuntu 16.04 LTS my system won't power off
anymore on itself, I have to hold the powerbutton.

Ubuntu 15.04 and 15.10 had no problems turning off my system.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 23 21:46:35 2016
ExecutablePath: /lib/systemd/systemd
InstallationDate: Installed on 2016-04-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Z420 Workstation
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 
 3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J61 v03.88
dmi.board.name: 1589
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 0.00
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z420 Workstation
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  System won't power off

Status in systemd package in Ubuntu:
  New

Bug description:
  Since I clean installed Ubuntu 16.04 LTS my system won't power off
  anymore on itself, I have to hold the powerbutton.

  Ubuntu 15.04 and 15.10 had no problems turning off my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 21:46:35 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.88
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.88:bd05/27/2015:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z420 Workstation
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574100/+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 1574099] [NEW] Problem with kwallet after migration to 16.04

2016-04-23 Thread Christophe H

Public bug reported:

Hello

I have migrated to 16.04 and now when I am trying to connect to wifi
networks through network manager tit is showing waiting for
authorization and then it saus connection deactivated and then no
secrets provided

In the log I have the following kwalletd5:
../../../../src/runtime/kwalletd/kwalletd.cpp:590: int
KWalletD::internalOpen(const QString&, const QString&, bool, WId, bool,
const QString&): Assertion `b->cipherType() !=
KWallet::BACKEND_CIPHER_UNKNOWN' failed.

More over as a complimentary information when launching wallet manager
from the user management it says the wallet is closed and I can not open
it...

Thanks in advance

** 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/1574099

Title:
  Problem with kwallet after migration to 16.04

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello

  I have migrated to 16.04 and now when I am trying to connect to wifi
  networks through network manager tit is showing waiting for
  authorization and then it saus connection deactivated and then no
  secrets provided

  In the log I have the following kwalletd5:
  ../../../../src/runtime/kwalletd/kwalletd.cpp:590: int
  KWalletD::internalOpen(const QString&, const QString&, bool, WId,
  bool, const QString&): Assertion `b->cipherType() !=
  KWallet::BACKEND_CIPHER_UNKNOWN' failed.

  More over as a complimentary information when launching wallet manager
  from the user management it says the wallet is closed and I can not
  open it...

  Thanks in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574099/+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 1574097] [NEW] package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread Jaka Abdillah

Public bug reported:

Like bug installation when upgrade from 14.04 (dell factory state) to
ubuntu 16.04. I think, its kernel version problem. Thanks

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initscripts 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
Uname: Linux 3.13.0-85-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 23 22:29:07 2016
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-23 (0 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: sysvinit
Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Like bug installation when upgrade from 14.04 (dell factory state) to
  ubuntu 16.04. I think, its kernel version problem. Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 22:29:07 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1574097/+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 1574096] [NEW] Asus's touchpad does't work

2016-04-23 Thread EDO

Public bug reported:

in these pc touchpad doesn't work

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19
Uname: Linux 3.19.0-59-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
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
Date: Sat Apr 23 21:33:21 2016
DistUpgraded: 2016-04-23 18:07:02,116 DEBUG failed to SystemUnLock() (E:Non 
bloccato)
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
   Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
InstallationDate: Installed on 2016-02-17 (65 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 005: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 
Reciever
 Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL552VW
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic 
root=UUID=559bd433-509b-42a7-8e2e-179b5e7b0feb ro i8042.reset i8042.nomux 
i8042.nopnp i8042.noloop quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2016-04-23 (0 days ago)
dmi.bios.date: 10/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL552VW.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.213:bd10/22/2015:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL552VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Apr 23 20:59:28 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1135 
 vendor LGD
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

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

Title:
  Asus's touchpad  does't work

Status in xorg package in Ubuntu:
  New

Bug description:
  in these pc touchpad doesn't work

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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
  Date: Sat Apr 23 21:33:21 2016
  DistUpgraded: 2016-04-23 18:07:02,116 DEBUG failed to SystemUnLock() (E:Non 
bloccato)
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
  InstallationDate: Installed on 2016-02-17 (65 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 005: ID 045e:00e1 Microsoft Corp. Wireless

[Touch-packages] [Bug 1570449] Re: GTK3 Libreoffice default theme is too dark

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  GTK3 Libreoffice default theme is too dark

Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Libreoffice default theme became too dark. I think it is a problem
  with switching to GTK3. See the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 14 17:48:21 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-03-29 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1570449/+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 1570449] Re: GTK3 Libreoffice default theme is too dark

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

** Changed in: libreoffice (Ubuntu)
   Status: New => Confirmed

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

Title:
  GTK3 Libreoffice default theme is too dark

Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Libreoffice default theme became too dark. I think it is a problem
  with switching to GTK3. See the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-core 1:5.1.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 14 17:48:21 2016
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-03-29 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1570449/+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 1557227] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-04-23 Thread Sina Mashek

I have had this happen too, and now my machine is in an "unstable
state," per what the updater said.

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  after running the upgrade script errors were reported.
  Logon doesn't complete. Used to log me right out.
  I did apt-get upgrade/update and now log on leads to an empty screen.

  Release 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Mar 14 10:35:43 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-05 (69 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1557227/+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 1557227] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

** Changed in: gconf (Ubuntu)
   Status: New => Confirmed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  after running the upgrade script errors were reported.
  Logon doesn't complete. Used to log me right out.
  I did apt-get upgrade/update and now log on leads to an empty screen.

  Release 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Mar 14 10:35:43 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-05 (69 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1557227/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

2016-04-23 Thread Richard Elkins

After re-installing Xubuntu 16.04 this morning, I was able to find a
suitable driver for my Epson XP-410 printer by adding the package,
printer-driver-escpr.  There was no requirement for lsb as a
prerequisite.

dpkg -L printer-driver-escpr
/.
/usr
/usr/lib
/usr/lib/printer-driver-escpr
/usr/lib/printer-driver-escpr/libescpr.so.1.0.0
/usr/lib/cups
/usr/lib/cups/driver
/usr/lib/cups/driver/escpr
/usr/lib/cups/filter
/usr/lib/cups/filter/epson-escpr
/usr/lib/cups/filter/epson-escpr-wrapper
/usr/share
/usr/share/cups
/usr/share/cups/ppd-updaters
/usr/share/cups/ppd-updaters/printer-driver-escpr.ppd-updater
/usr/share/doc
/usr/share/doc/printer-driver-escpr
/usr/share/doc/printer-driver-escpr/copyright
/usr/share/doc/printer-driver-escpr/changelog.Debian.gz
/usr/lib/printer-driver-escpr/libescpr.so.1

I would recommend that the other affected parties should try this
approach with 16.04.  Stay away from the Epson site downloads.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in lsb:
  Confirmed
Status in cups-filters package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsb/+bug/1536353/+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 1543351] Re: Add on-screen-keyboard support for Xmir/Puritine apps

2016-04-23 Thread Will Atwood

New Aquarius M10 owner.. Love it but was also confused when no keyboard
was available for Firefox, LibreOffice and gEdit..  An on screen
keyboard we could slide up and down would be great.. Similar to terminal
app or even this text box I'm typing into on this page.. When I touch
the comment box the keyboard pops up.. Very cool...keep up the great
work!

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

Title:
  Add on-screen-keyboard support for Xmir/Puritine apps

Status in Canonical Pocket Desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  From perspective of product management - this is currently not a
  requirement, just want to capture it for future

  we currently can't interact with puritine apps relying on the OSK

  to add this feature in where text-box selection on an xapp results in
  triggering the osk, in unity8 would be a very large/complicated
  effort. However, with a manual capability to trigger the OSK this
  could be achieved.

  For design team
  one idea was to add a show/hide button for the OSK.
  realizing this may be undesirable to add another indicator item - a follow-on 
idea might be to add an alpha button in the corner of the xmir-root window (the 
window that holds any xapp at the moment)
  this way the button presence would only be limited to the Xapp interaction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1543351/+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 1574079] [NEW] USB audio device is not recognized after startup in 16.04

2016-04-23 Thread TheBigW

Public bug reported:

Hi @all,

I used the same USB audio device in all previous Ubuntu versions
(Focusrite Scarlet 2i2). It is supposed to be class compliant and works
an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10
to 16.04 it stopped to work: after start-up it does not show up as an
audio device at all (also not recognized by aplay -l). I can workaround
this by unplugging it and plugging it in again after Ubuntu booted up
(strangely 2 times unplug/re-plug). After 2nd time plugging it in again
it shows up and works great without any further issues until next
restart.

Maybe worth to note that I recognized today that fwupd uses continuously
100% CPU load, so I just killed it today. My Hardware (Main-board/CPU)
is a bit older (Intel E8400), so could probably be some compatibility
issue...

regards,
Tobias

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
 /dev/snd/controlC1:  tobias 1553 F pulseaudio
 /dev/snd/controlC0:  tobias 1553 F pulseaudio
 /dev/snd/controlC2:  tobias 1553 F pulseaudio
CurrentDesktop: Unity
Date: Sat Apr 23 20:09:04 2016
InstallationDate: Installed on 2015-09-19 (217 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
dmi.bios.date: 09/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1238
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnS

[Touch-packages] [Bug 1574045] Re: Can't install account-plugin-google; kaccounts-providers already provides /usr/share/accounts/providers/google.provider

2016-04-23 Thread Bug Watch Updater

Launchpad has imported 27 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=347219.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-05-05T11:08:16+00:00 Jonathan Riddell wrote:

This file overlaps with a file in gnome's account-plugin-facebook
/usr/share/accounts/services/facebook-im.service

and kaccounts-providers has a file which overlaps with gnome's 
account-plugin-google
/usr/share/accounts/providers/google.provider

gnome and kde need to be co-installable so these files should be renamed
to not overlap.

As a separate but related issue if ktp explodes because gnome accounts-
plugins are installed that should also be gracefully delt with.


Reproducible: Always

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/0


On 2015-05-05T11:21:46+00:00 Mklapetek wrote:

It cannot be gracefully dealt with because Gnome uses different system
for creating their (telepathy) accounts and KAccounts has no way of
knowing which provider is for gnome and which is for kde. To KAccounts,
all is the same.

The way gnome creates telepathy accounts is also incompatible with ktp,
this _will_ result in user having invalid ktp accounts. I am working on
making these compatible, but for now they aren't and will not be till
15.08. There's nothing that can make it compatible.

facebook-im.service will not be installed from 15.04.1 as facebook chat
support is deprecated.

Simply renaming all the files is also not a good option, because if
you'll have both packages installed, you will have duplicated entries,
each doing different things.

I'm afraid these two simply aren't co-installable.

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/1


On 2015-05-05T15:53:31+00:00 Jonathan Riddell wrote:

> I'm afraid these two simply aren't co-installable.
that's quite a big fail compared to the normal setup for  linux desktops.  if 
we can't install two applications from gnomey stuff and kdey stuff at the same 
time that breaks package install for an awful lot of people

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/2


On 2015-05-06T09:21:25+00:00 Mklapetek wrote:

Yes, well, apparently nobody has thought about that.

Quoting Accounts SSO developer:
"hi! I'd say that the problem is on the .provider files only, because the 
service files refer to a provider, so as long as that's a different one, they 
won't mess up

I admit I don't have a solution for the .provider files anyway...

one possibility is to play with environment variables, to instruct
libaccounts-glib to look for its files in a different directory"

So for now the only solution is to rename and use different install dir
and use an env variable (I'm not sure which one yet).

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/3


On 2015-11-12T16:45:02+00:00 Scarlett Clark wrote:

We still have a growing number of bug reports piling up on launchpad in regards 
to this bug.
I expect it is because many ubuntu users will have gnome stuff..
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728

Any progress?
Scarlett

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/4


On 2015-11-12T17:02:46+00:00 Mklapetek wrote:

One possible solution is adding an env variable and patching the install
prefix.

That's the only solution we have right now.

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/5


On 2016-01-15T09:13:00+00:00 Flames_in_Paradise wrote:

This is a real blocker - so...  Multi-Desktop environment (still
recommended?) puts interested peoples desktop in a unsecure state as it
blocks APT then.

If there is no other solution we will have to ask to remove Telepathy
from Kubuntu-meta or _not_ to recommend a mixed Desktop-Environment any
longer  & put up a warning. May sound harsh, but...

This error covers two release + a third that's in current development.

A possible solution to get at least APT back into it's shoes again was
posted in askubuntu:

https://askubuntu.com/questions/618389/error-upgrading-kde-telepathy-
kubuntu-15-04

Reply at: https://bugs.launchpad.net/ubuntu/+source/account-
plugins/+bug/1574045/comments/6

[Touch-packages] [Bug 1574067] [NEW] Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandon

2016-04-23 Thread Heine Pedersen

Public bug reported:

Never had the issue on 14.04, comes on every reboot on 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 22 13:27:18 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-01-17 (462 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  Upgraded 14.04 to 16.04 (forcing upgrade from terminal) - after reboot
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Never had the issue on 14.04, comes on every reboot on 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 22 13:27:18 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-17 (462 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1574067/+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 1574045] Re: Can't install unity - unity-scope-gdrive depends on account-plugin-google, but kaccounts-providers already provides /usr/share/accounts/providers/google.provider

** Also affects: account-plugins
   Importance: Undecided
   Status: New

** Summary changed:

- Can't install unity - unity-scope-gdrive depends on account-plugin-google, 
but kaccounts-providers already provides 
/usr/share/accounts/providers/google.provider
+ Can't install  account-plugin-google;  kaccounts-providers already provides 
/usr/share/accounts/providers/google.provider

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

Title:
  Can't install  account-plugin-google;  kaccounts-providers already
  provides /usr/share/accounts/providers/google.provider

Status in Online Accounts: Account plugins:
  New
Status in kaccounts-providers:
  Unknown
Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 16.04, later tried to install unity with `sudo
  apt-get install unity` which has a dependency (unity-scope-gdrive)
  requiring account-plugin-google and that wouldn't install since
  '/usr/share/accounts/providers/google.provider' is already provided by
  kaccounts-providers:

  $ sudo apt-get install unity
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    account-plugin-google
  The following NEW packages will be installed:
    account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1574045/+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 1574045] Re: Can't install unity - unity-scope-gdrive depends on account-plugin-google, but kaccounts-providers already provides /usr/share/accounts/providers/google.provider

** Also affects: kaccounts-providers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't install  account-plugin-google;  kaccounts-providers already
  provides /usr/share/accounts/providers/google.provider

Status in Online Accounts: Account plugins:
  New
Status in kaccounts-providers:
  Unknown
Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 16.04, later tried to install unity with `sudo
  apt-get install unity` which has a dependency (unity-scope-gdrive)
  requiring account-plugin-google and that wouldn't install since
  '/usr/share/accounts/providers/google.provider' is already provided by
  kaccounts-providers:

  $ sudo apt-get install unity
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    account-plugin-google
  The following NEW packages will be installed:
    account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1574045/+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 1574045] Re: Can't install unity - unity-scope-gdrive depends on account-plugin-google, but kaccounts-providers already provides /usr/share/accounts/providers/google.provider

** No longer affects: unity-scope-gdrive

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

Title:
  Can't install unity - unity-scope-gdrive depends on account-plugin-
  google, but kaccounts-providers already provides
  /usr/share/accounts/providers/google.provider

Status in kaccounts-providers:
  Unknown
Status in account-plugins package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 16.04, later tried to install unity with `sudo
  apt-get install unity` which has a dependency (unity-scope-gdrive)
  requiring account-plugin-google and that wouldn't install since
  '/usr/share/accounts/providers/google.provider' is already provided by
  kaccounts-providers:

  $ sudo apt-get install unity
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
    account-plugin-google
  The following NEW packages will be installed:
    account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kaccounts-providers/+bug/1574045/+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 1574045] Re: Can't install account-plugin-google

** Description changed:

  I installed Kubuntu 16.04, later tried to install unity with `sudo apt-
- get istall unity` which has a dependency requiring account-plugin-google
- and that wouldn't install:
+ get install unity` which has a dependency (unity-scope-gdrive) requiring
+ account-plugin-google and that wouldn't install:
  
+ $ sudo apt-get install unity
+ Reading package lists... Done
+ Building dependency tree   
+ Reading state information... Done
+ unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
+ You might want to run 'apt-get -f install' to correct these:
+ The following packages have unmet dependencies:
+  unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed
+ 
+ $ sudo apt-get -f install
+ Reading package lists... Done
+ Building dependency tree   
+ Reading state information... Done
+ Correcting dependencies... Done
+ The following additional packages will be installed:
+   account-plugin-google
+ The following NEW packages will be installed:
+   account-plugin-google
+ 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
+ 250 not fully installed or removed.
+ Need to get 0 B/3,368 B of archives.
+ After this operation, 29.7 kB of additional disk space will be used.
+ Do you want to continue? [Y/n] y
+ (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Can't install account-plugin-google
+ Can't install unity - unity-scope-gdrive depends on account-plugin-google, 
but kaccounts-providers already provides 
/usr/share/accounts/providers/google.provider

** Description changed:

  I installed Kubuntu 16.04, later tried to install unity with `sudo apt-
  get install unity` which has a dependency (unity-scope-gdrive) requiring
- account-plugin-google and that wouldn't install:
+ account-plugin-google and that wouldn't install since
+ '/usr/share/accounts/providers/google.provider' is already provided by
+ kaccounts-providers:
  
  $ sudo apt-get install unity
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
-  unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed
+  unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed
  
  $ sudo apt-get -f install
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
-   account-plugin-google
+   account-plugin-google
  The following NEW packages will be installed:
-   account-plugin-google
+   account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories curr

[Touch-packages] [Bug 1451728]

2016-04-23 Thread Mklapetek

Please don't report Kubuntu bugs here.

This bug is fixed and is fixed properly from our side.

There is _NOTHING_ more we can do about that, this is purely
Kubuntu's bug now.

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in meta-telepathy:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  Fix Released
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1451728]

This still happens and I'm Kubuntu 16.04.
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1574045

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in meta-telepathy:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  Fix Released
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1574045] Re: Can't install account-plugin-google

2016-04-23 Thread Martin Klapetek

Dear Kubuntu packagers,

please backport these patches into your packaging.

https://quickgit.kde.org/?p=kaccounts-integration.git&a=commit&h=a60c1636b6bf0bf5b0718d8de06facfa959ad719
https://quickgit.kde.org/?p=kaccounts-integration.git&a=commit&h=deff781ae751f2f1c95b24997d01aa38c0dd7502

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

Title:
  Can't install account-plugin-google

Status in kaccounts-providers:
  Unknown
Status in Google Documents Lens:
  New
Status in account-plugins package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 16.04, later tried to install unity with `sudo
  apt-get install unity` which has a dependency (unity-scope-gdrive)
  requiring account-plugin-google and that wouldn't install:

  $ sudo apt-get install unity
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
account-plugin-google
  The following NEW packages will be installed:
account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kaccounts-providers/+bug/1574045/+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 1574045] Re: Can't install account-plugin-google

This might be a duplicate of bug #1488909

** Bug watch added: KDE Bug Tracking System #347219
   https://bugs.kde.org/show_bug.cgi?id=347219

** Also affects: kaccounts-providers via
   https://bugs.kde.org/show_bug.cgi?id=347219
   Importance: Unknown
   Status: Unknown

** Description changed:

- I was trying to install a package that requires account-plugin-google
+ I installed Kubuntu 16.04, later tried to install unity with `sudo apt-
+ get istall unity` which has a dependency requiring account-plugin-google
  and that wouldn't install:
  
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
-  trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
+  trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
-  
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
+  
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
-  trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
+  trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
-  
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
+  
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: unity-scope-gdrive
   Importance: Undecided
   Status: New

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

Title:
  Can't install account-plugin-google

Status in kaccounts-providers:
  Unknown
Status in Google Documents Lens:
  New
Status in account-plugins package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 16.04, later tried to install unity with `sudo
  apt-get install unity` which has a dependency (unity-scope-gdrive)
  requiring account-plugin-google and that wouldn't install:

  $ sudo apt-get install unity
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   unity-scope-gdrive : Depends: account-plugin-google but it is not going to 
be installed

  $ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
account-plugin-google
  The following NEW packages will be installed:
account-plugin-google
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  250 not fully installed or removed.
  Need to get 0 B/3,368 B of archives.
  After this operation, 29.7 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  (Reading database ... 214947 files and directories currently installed.)
  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-

[Touch-packages] [Bug 1574042] Re: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread Jose Maria Micoli

** Changed in: python-defaults (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/python-defaults/+question/292047

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in python-defaults package in Ubuntu:
  Invalid

Bug description:
  During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few
  errors talking about python-minimal 2.7.11-1 saying failed to
  install/upgrade. For now the problem is: my unity not appear.

  Sorry for my bad English and thank you for help me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 11:45:08 2016
  DuplicateSignature:
   Setting up python-minimal (2.7.11-1) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-07 (260 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+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 1574053] [NEW] [Gmail] Notification opens mobile version in frieza

2016-04-23 Thread Víctor R . Ruiz

Public bug reported:

Test case.
- Open Gmail.
- Introduce credentials.
- Close Gmail.
- From another device, send an email to the Gmail account.
- When the notification arrives, don't dismiss it. Open the indicator, and tap 
on the right icon to open Gmail.

Expected result.
- Gmail is opened in desktop mode.

Actual result.
- Webbrowser opens Gmail's mobile version.

current build number: 89
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: webbrowser-app (Ubuntu)
 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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1574053

Title:
  [Gmail] Notification opens mobile version in frieza

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Test case.
  - Open Gmail.
  - Introduce credentials.
  - Close Gmail.
  - From another device, send an email to the Gmail account.
  - When the notification arrives, don't dismiss it. Open the indicator, and 
tap on the right icon to open Gmail.

  Expected result.
  - Gmail is opened in desktop mode.

  Actual result.
  - Webbrowser opens Gmail's mobile version.

  current build number: 89
  device name: frieza
  channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574053/+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 1574048] [NEW] Panel appears white for a second when unity8 starts

2016-04-23 Thread Michael Terry

Public bug reported:

On boot, when unity8 starts drawing itself on the screen, the panel
first appears lightly colored (grey). I'm assuming it is drawing itself
in the light theme first, before switching to suru dark.

** 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/1574048

Title:
  Panel appears white for a second when unity8 starts

Status in unity8 package in Ubuntu:
  New

Bug description:
  On boot, when unity8 starts drawing itself on the screen, the panel
  first appears lightly colored (grey). I'm assuming it is drawing
  itself in the light theme first, before switching to suru dark.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1574048/+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 1574042] Re: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread 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-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1574042

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few
  errors talking about python-minimal 2.7.11-1 saying failed to
  install/upgrade. For now the problem is: my unity not appear.

  Sorry for my bad English and thank you for help me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 11:45:08 2016
  DuplicateSignature:
   Setting up python-minimal (2.7.11-1) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-07 (260 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+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 1574045] [NEW] Can't install account-plugin-google

Public bug reported:

I was trying to install a package that requires account-plugin-google
and that wouldn't install:

Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
 trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
Errors were encountered while processing:
 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
 trying to overwrite '/usr/share/accounts/providers/google.provider', which is 
also in package kaccounts-providers 4:15.12.3-0ubuntu1
Errors were encountered while processing:
 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Apr 23 11:09:16 2016
InstallationDate: Installed on 2016-04-23 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
SourcePackage: account-plugins
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Can't install account-plugin-google

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I was trying to install a package that requires account-plugin-google
  and that wouldn't install:

  Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack 
.../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ...
  Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/providers/google.provider', which 
is also in package kaccounts-providers 4:15.12.3-0ubuntu1
  Errors were encountered while processing:
   
/var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 23 11:09:16 2016
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  SourcePackage: account-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1574045/+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 1574042] [NEW] package python-minimal 2.7.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-04-23 Thread Jose Maria Micoli

Public bug reported:

During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few errors
talking about python-minimal 2.7.11-1 saying failed to install/upgrade.
For now the problem is: my unity not appear.

Sorry for my bad English and thank you for help me.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-minimal 2.7.11-1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 23 11:45:08 2016
DuplicateSignature:
 Setting up python-minimal (2.7.11-1) ...
 dpkg: error processing package python-minimal (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-08-07 (260 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: python-defaults
Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python-minimal 2.7.11-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  During upgrade my Ubuntu 15.10 to the new 16.04 LTS i take a few
  errors talking about python-minimal 2.7.11-1 saying failed to
  install/upgrade. For now the problem is: my unity not appear.

  Sorry for my bad English and thank you for help me.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.11-1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 11:45:08 2016
  DuplicateSignature:
   Setting up python-minimal (2.7.11-1) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-08-07 (260 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.11-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1574042/+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 1406810] Re: screen is garbled with 14.10 (was fine with 14.04)

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: xorg (Ubuntu)
   Importance: Medium => High

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

Title:
  screen is garbled with 14.10 (was fine with 14.04)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  On a iMac Alu 2010, when upgrading from 14.04 desktop to 14.10 desktop
  or installing 10.10 server (SSH package only) the screen shows thin 
horizontal lines moving on a black background.

  /etc/X11/xorg.conf is absent (using default config),
  /var/log/Xorg.0.log doesn't show any error beside the lack of the
  fglrx module. But I doubt it's relevant with the symptoms appearing on
  the server install.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.19
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV770/M98L [Mobility Radeon HD 4850] 
[1002:944a] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00b5]
  InstallationDate: Installed on 2015-01-01 (440 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: Apple Inc. iMac11,1
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=f19c8f84-1553-4a36-889a-acfb8a13da9a ro
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-79-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 03/17/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM111.88Z.0034.B02.1003171314
  dmi.board.name: Mac-F2268DAE
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DAE
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM111.88Z.0034.B02.1003171314:bd03/17/10:svnAppleInc.:pniMac11,1:pvr1.0:rvnAppleInc.:rnMac-F2268DAE:rvr:cvnAppleInc.:ct13:cvrMac-F2268DAE:
  dmi.product.name: iMac11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Mar 16 19:43:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+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 1554590] Re: System freezes if I connect my extern monitor via hdmi

albflo, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554590/comments/4
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/1554590

Title:
  System freezes if I connect my extern monitor via hdmi

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  yesterday my notebook freezes when I connected my extern monitor, I tried it 
various times after new reboots, but the problem always occurred.
  Today I started my notebook with the extern monitor connected and to my joy 
everything went normally. Therefore I tried again to unplug it and plug it in 
again and the problem still occurs.

  Call trace:
  https://launchpadlibrarian.net/247148393/CurrentDmesg.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  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: Tue Mar  8 16:47:21 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Skylake Integrated Graphics [17aa:2237]
  InstallationDate: Installed on 2016-01-28 (40 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127)
  MachineType: LENOVO 20FES0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-11-generic.efi.signed 
root=UUID=dd1054f1-c980-4766-bc47-6399a1954244 ro quiet splash 
intel_pstate=no_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET34W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET34W(1.11):bd11/05/2015:svnLENOVO:pn20FES0:pvrThinkPadYoga260:rvnLENOVO:rn20FES0:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FES0
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build1
  xserver.bootTime: Tue Mar  8 16:40:28 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4665
   vendor CMN
  xserver.version: 2:1.17.3-2ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554590/+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 1573428] Re: network-manager not finding any wifi network

2016-04-23 Thread Dragon Ball

when that bug happens to you does it think it's on Ethernet connection?
I have to keep to restarting  network-manager to see the wifi network
list.

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

Title:
  network-manager not finding any wifi network

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sometimes network-manager stops finding any wifi network. I'm still
  investigating in what circumstances does it happen. The last time it
  happened after logging out and back in (switching optimus GPU).

  Workaround:
  sudo service network-manager restart

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 08:49:03 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-21 (397 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev lxcbr0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.106  
metric 600
  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  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   lxcbr0  bridgeconnected/org/freedesktop/NetworkManager/Devices/0  
lxcbr0  7fd1e377-d0ea-4999-b2a6-5011fe4cfa3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
GONNESA e19c4e31-7de8-4c0d-a7db-47d4b59a55c8  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/3  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1573428/+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 1574029] Re: Failed to boot after upgrade to 16.04 LTS

2016-04-23 Thread 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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1574029

Title:
  Failed to boot after upgrade to 16.04 LTS

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  At the end of the upgrade, a dialog box appeared "The upgrade has
  aborted. Your system could be in an unstable state. A recovery will
  run now (dpkg -configure - a). Nothing happened after closing the
  dialog box.

  
  After shutdown, boot up failed after grub tries to load something with this 
message "Starting up", then after 10 seconds this message "Gave up waiting 
for root device., common problems:.ALERT! UUID = 2476e..does not exist.

  The the boot process stopped at the initramfs prompt.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 17:34:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-11-12 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+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 1574029] [NEW] Failed to boot after upgrade to 16.04 LTS

2016-04-23 Thread chankartat

Public bug reported:

At the end of the upgrade, a dialog box appeared "The upgrade has
aborted. Your system could be in an unstable state. A recovery will run
now (dpkg -configure - a). Nothing happened after closing the dialog
box.


After shutdown, boot up failed after grub tries to load something with this 
message "Starting up", then after 10 seconds this message "Gave up waiting 
for root device., common problems:.ALERT! UUID = 2476e..does not exist.

The the boot process stopped at the initramfs prompt.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat Apr 23 17:34:29 2016
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-11-12 (162 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  Failed to boot after upgrade to 16.04 LTS

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  At the end of the upgrade, a dialog box appeared "The upgrade has
  aborted. Your system could be in an unstable state. A recovery will
  run now (dpkg -configure - a). Nothing happened after closing the
  dialog box.

  
  After shutdown, boot up failed after grub tries to load something with this 
message "Starting up", then after 10 seconds this message "Gave up waiting 
for root device., common problems:.ALERT! UUID = 2476e..does not exist.

  The the boot process stopped at the initramfs prompt.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 17:34:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-11-12 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+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 1573935] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 22 21:00:12 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-04-20 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1573935/+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 1574012] Re: Music stops playing when files synchronising

2016-04-23 Thread Victor Thompson

Hi, Peter, thanks for taking the time to file this bug and for helping
to make Ubuntu better! I'm not quite sure if this is the fault of the
app itself or of the daemon that indexes the user's music library. I've
added them as affected.

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

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

Title:
  Music stops playing when files synchronising

Status in Ubuntu Music App:
  New
Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  I am using the music app on the Aquaris M10 with OTA-10.1.

  When playing music if I then copy new music onto the device from an
  external source the music stops playing (not just paused but stopped)
  as the library synchronises to find the new music.

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1574012/+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 1574020] Re: Can't use networkmanager from lightdm

2016-04-23 Thread Joakim Koed

** Description changed:

  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that lightdm
  with unity-greeter (all stock, nothing changed) can't connect to WiFi
  with network-manager.
  
  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)
  
  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.
  
  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.
  
  Feel free to ask for more info.
+ 
+ Edit:
+ 
+ From syslog:
+ 
+ Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
+ Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
+ Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

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

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1525554] Re: [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

RonaldP3, could you please confirm if 4.6-rc1 addresses your issues
following https://wiki.ubuntu.com/Kernel/MainlineBuilds?

** No longer affects: alsa-driver (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at
  all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound on brand new HP ProBook 470 G3 after installing Ubuntu 14.04
  on headphones or internal speakers.

  Connecting a USB headphone and microphone both work, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ronald 2199 F pulseaudio
ronald 2513 F alsamixer
  CurrentDesktop: Unity
  Date: Sat Dec 12 19:36:01 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
127: Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2015
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.02
  dmi.board.name: 8102
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.1F
  dmi.chassis.asset.tag: 5CD54286XY
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.02:bd09/30/2015:svnHP:pnHPProBook470G3:pvr:rvnHP:rn8102:rvrKBCVersion16.1F:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 470 G3
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525554/+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 1523086] Re: Ubuntu 15.10: GNOME Terminal window loses mouse cursor

Vlad K., this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1523086/comments/17
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/1523086

Title:
Ubuntu 15.10: GNOME Terminal window loses mouse cursor

Status in xorg package in Ubuntu:
Invalid

Bug description:
Ubuntu: Ubuntu 15.10
Package: gnome-terminal-3.16.2-1ubuntu4
Problem:

Sometimes, but always when out of focus, a GNOME terminal window will
lose mouse icon when it is hovered over the window. Clicking the
window (and thus bringing it back in focus) restores the mouse icon.

Once all that starts to happen, any URLs in the terminal stop showing pointer
cursor when hovered over, but they do respond to clicks and right-clicks.
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: vlad 1856 F pulseaudio
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=a666043d-11d1-472f-8ccd-3ef13cae559a
InstallationDate: Installed on 2015-11-19 (15 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic
root=UUID=7671ab7d-b593-4193-9a95-3f7b4389bf8f ro quiet splash
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.2.0-19-generic N/A
linux-backports-modules-4.2.0-19-generic N/A
linux-firmware1.149.3
RfKill:

Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 11/26/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: A770DE+
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.40:bd11/26/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA770DE+: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/xorg/+bug/1523086/+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 1556228] Re: HP Notebook Probook 440 G3 HDA Intel PCH horrible sounds while booting

** No longer affects: alsa-driver (Ubuntu Xenial)

** No longer affects: alsa-driver (Ubuntu)

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

Title:
  HP Notebook Probook 440 G3  HDA Intel PCH horrible sounds while
  booting

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  At first there was no native recognition of my sound driver (see this [ 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525554 ] a lot of 
others a experiencing this problem)
  so there was a workaround to fix that, the notebook has sound output now, but 
ever since i got these horrible scratching noises while booting, which i dont 
have booting windows, which is kinda surprising while one could take it for a 
bios or hardware problem.

  basic workaround for fixing missing sound driver was adding two lines to the 
/etc/modprobe.d/alsa-base.conf
  options snd-hda-intel single_cmd=1
  options snd-hda-intel probe_mask=1

  with these lines a was able to get sound, but i then have these crazy
  noises while booting.

  the following are some lines from the terminal which might help:

  'lsb_release -rd'
  Ubuntu 15.10

  cat /proc/asound/version
  Advanced Linux Sound Architecture Driver Version k4.2.0-30-generic.

  uname -a
  Linux 15 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  lspci -v | grep -A7 -i "audio"
  00:1f.3 Multimedia audio controller: Intel Corporation Device 9d70 (rev 21)
   Subsystem: Hewlett-Packard Company Device 8100
   Flags: bus master, fast devsel, latency 64, IRQ 16
   Memory at c132 (64-bit, non-prefetchable) [size=16K]
   Memory at c131 (64-bit, non-prefetchable) [size=64K]
   Capabilities: 
   Kernel driver in use: snd_hda_intel

  lsmod | grep snd
  snd_hda_codec_hdmi 49152 1
  snd_hda_intel 36864 2
  snd_hda_codec 135168 2 snd_hda_codec_hdmi,snd_hda_intel
  snd_hda_core 65536 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
  snd_hwdep 16384 1 snd_hda_codec
  snd_pcm 106496 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
  snd_seq_midi 16384 0
  snd_seq_midi_event 16384 1 snd_seq_midi
  snd_rawmidi 32768 1 snd_seq_midi
  snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
  snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
  snd_timer 32768 2 snd_pcm,snd_seq
  snd 81920 13 
snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device
  soundcore 16384 1 snd

  cat /proc/asound/cards
   0 [PCH ]: HDA-Intel - HDA Intel PCH
    HDA Intel PCH at 0xc132 irq 129

  even adding the right driver and module into /etc/modules (like snd-
  hda-intel model=PCH index=0) did not work, like i found in this thread
  ( https://wiki.ubuntuusers.de/Soundkarten_konfigurieren/ ) sorry for
  the german thread.

  i dont know what to add anymore. feel free to ask.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1613 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=80c72696-84ee-47f5-8764-86ed7ccd8bf2
  InstallationDate: Installed on 2016-02-18 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP ProBook 440 G3
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=9c79ccaf-65c6-40d6-a2a8-16d77841af74 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.07
  dmi.board.name: 8100
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.03
  dmi.chassis.asset.tag: 5CD5514XK5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.07:bd01/25/2016:svnHP:pnHPProBook440G3:pvr:rvnHP:rn8100:rvrKBCVersion40.03:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 440 G3
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1574020] [NEW] Can't use networkmanager from lightdm

2016-04-23 Thread Joakim Koed

Public bug reported:

After upgrading to 16.04 desktop (unity) (clean install) from 14.04,
(so not really upgrading, but you get the point) I noticed that lightdm
with unity-greeter (all stock, nothing changed) can't connect to WiFi
with network-manager.

WiFi works after loggin it, but it should be working before also, if
not, what's the point in having an icon there :)

I get the following message: Failed to add/activate connection. - (1)
Insufficient privileges. - see image.
This worked fine in 14.04.

I have noticed this problem in both my desktop (Broadcom WiFi) and
Laptop (Intel WiFi) - So it has nothing to be with the chip.

Feel free to ask for more info.

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

** Tags: lightdm

** Attachment added: "error"

https://bugs.launchpad.net/bugs/1574020/+attachment/4644286/+files/IMG_20160421_224655.jpg

** Summary changed:

- networkmanager
+ Can't use networkmanager from lightdm

** Tags added: lightdm

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

Title:
Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
New

Bug description:
After upgrading to 16.04 desktop (unity) (clean install) from 14.04,
(so not really upgrading, but you get the point) I noticed that
lightdm with unity-greeter (all stock, nothing changed) can't connect
to WiFi with network-manager.

WiFi works after loggin it, but it should be working before also, if
not, what's the point in having an icon there :)

I get the following message: Failed to add/activate connection. - (1)
Insufficient privileges. - see image.
This worked fine in 14.04.

I have noticed this problem in both my desktop (Broadcom WiFi) and
Laptop (Intel WiFi) - So it has nothing to be with the chip.

Feel free to ask for more info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1573168] Re: [Frieza] Location service fails to start cleanly, entering restart loop

2016-04-23 Thread Sergi Quiles Pérez

Now it has again the same behavior as described on the title. :(

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

Title:
  [Frieza] Location service fails to start cleanly, entering restart
  loop

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  See http://makeagif.com/i/QlHXU7 for further details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1573168/+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 721786] Re: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track

2016-04-23 Thread Adam Niedling

** Tags added: xenial

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

Title:
  (Non-overlay) scroll-bar lacks sufficient contrast to easily identify
  its position in the scroll-track

Status in Ayatana Design:
  Fix Committed
Status in One Hundred Papercuts:
  Fix Released
Status in ubuntu-mate:
  Won't Fix
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: gnome-session

  The scroll-bars that appear on the right-side and bottom of gnome
  windows lack sufficient contrast to the scroll-track. I have
  difficulty identifying where in the scroll-track the bar is
  positioned. I often mistake the background of the scroll-track as the
  scroll-bar itself. I'm using Inverted Control theme. More contrast and
  better color separation is needed here.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-session-bin 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  Architecture: i386
  Date: Sat Feb 19 09:19:22 2011
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  ProcEnviron:
   LC_TIME=en_GB.UTF-8
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  XsessionErrors: (polkit-gnome-authentication-agent-1:1387): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/721786/+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 1457098] Re: [Indicators] Expanded indicators are not visible in direct sunlight

2016-04-23 Thread GTriderXC

Fix Committed → Fix Released ???

OK, so You released a fix. And did You test it? I did (photo-
22.04.2016)

** Attachment added: "IMG_20160418_130001.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1457098/+attachment/4644269/+files/IMG_20160418_130001.jpg

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

Title:
  [Indicators] Expanded indicators are not visible in direct sunlight

Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  The selected/expanded indicator is currently highlighted in fully
  opaque white, the other indicators are semi-opaque white. This works
  fine when in dark ambient lighting conditions, but found myself
  struggling to see the semi opaque indicators for example outdoors.

  I would suggest finding a different way of highlighting the current
  indicator, maybe a different color, and increase the opacity of the
  other indicators, or just make them white.

  -

  Desired resolution:

  Highlighted text in #FF
  Adjust the colour value to #88

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1457098/+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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)

2016-04-23 Thread Adam Niedling

** Tags added: xenial

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

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will "show in the PulseAudio mixer"
  * After connecting the external speaker to the audio sink, I can also see the 
device in the "Play sound through" listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose "Audio Profile" from the context 
menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I 
get an error message stating "failed to change profile to a2dp"

  I've already added "Enable=Socket" in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1181106/+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 1571154] Re: No wifi in 16.04 because of permission issue not having systemd-network permission