date:20150901

Mintdrivers (based on software-properties-gk) has a few interesting
commits:

There is one about firmware -
https://github.com/linuxmint/mintdrivers/commit/c443ecd54310d7e521d57b214bcbfb7979fe4c66

One requesting an internet connection -
https://github.com/linuxmint/mintdrivers/commit/6ff0dd4d102c078c319b3910ccdbf21ea8fc55d6

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+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 1491102] [NEW] [FFE] add mdadm and lvm2 to cloud image

2015-09-01 Thread Scott Moser

Public bug reported:

In order to make use of raid and lvm functionality that is being added
to curtin, we need to have mdadm and lvm2 packages available.  curtin is
able to install the packages, but that is less desireable than having
them already available inside the image.

This bug is a feature freeze exception to add mdadm and lvm2 to the wily
cloud-image seed [1].

== general risks ==
Adding these packages will add ~ 5M total to the cloud image installed system.

== mdadm risks ==
mdadm recommends on default-mta. So addition of this package to the cloud image 
means also adding an unconfigured mta (postifx). There is some discussion on 
this topic from ubuntu-devel at [2].

Additionally, its possible presence of this package could cause issues.
It installs udev rules that could misfire.  Any such issues encountered
really should be fixed anyway, rather than just hoped to not be hit.

== lvm2 risks ==
Similarly to mdadm, lvm adds udev rules and could raise cause problems.
As with mdadm, any such issues really ought to be fixed any way.


== general information ==
The reason this is proposed for inclusion into the cloud-image is 2 fold
a.) the maas ephemeral images are created from the cloud-image.  so packages in 
the cloud-image are then available in the install environment for maas.  We 
dont want to add differences between these installation sets.
b.) it is not unreasonable to add these packages to the cloud image.  It is not 
at all farfetched that someone would use lvm or raid in a "cloud" environment, 
so they're not entirely wasted space there.

--
[1] 
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/view/head:/cloud-image
[2] http://irclogs.ubuntu.com/2015/08/06/%23ubuntu-devel.html#t22:53

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

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


** Tags: cloud-images

** Package changed: ubuntu => mdadm (Ubuntu)

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

** Tags added: cloud-images

** Description changed:

  In order to make use of raid and lvm functionality that is being added
  to curtin, we need to have mdadm and lvm2 packages available.  curtin is
  able to install the packages, but that is less desireable than having
  them already available inside the image.
  
  This bug is a feature freeze exception to add mdadm and lvm2 to the wily
  cloud-image seed [1].
- 
  
  == general risks ==
  Adding these packages will add ~ 5M total to the cloud image installed system.
  
  == mdadm risks ==
  mdadm recommends on default-mta. So addition of this package to the cloud 
image means also adding an unconfigured mta (postifx). There is some discussion 
on this topic from ubuntu-devel at [2].
  
  Additionally, its possible presence of this package could cause issues.
  It installs udev rules that could misfire.  Any such issues encountered
  really should be fixed anyway, rather than just hoped to not be hit.
  
  == lvm2 risks ==
  Similarly to mdadm, lvm adds udev rules and could raise cause problems.
  As with mdadm, any such issues really ought to be fixed any way.
  
+ 
+ == general information ==
+ The reason this is proposed for inclusion into the cloud-image is 2 fold
+ a.) the maas ephemeral images are created from the cloud-image.  so packages 
in the cloud-image are then available in the install environment for maas.  We 
dont want to add differences between these installation sets.
+ b.) it is not unreasonable to add these packages to the cloud image.  It is 
not at all farfetched that someone would use lvm or raid in a "cloud" 
environment, so they're not entirely wasted space there.
+ 
  --
  [1] 
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/view/head:/cloud-image
  [2] http://irclogs.ubuntu.com/2015/08/06/%23ubuntu-devel.html#t22:53

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

Title:
  [FFE] add mdadm and lvm2 to cloud image

Status in lvm2 package in Ubuntu:
  New
Status in mdadm package in Ubuntu:
  New

Bug description:
  In order to make use of raid and lvm functionality that is being added
  to curtin, we need to have mdadm and lvm2 packages available.  curtin
  is able to install the packages, but that is less desireable than
  having them already available inside the image.

  This bug is a feature freeze exception to add mdadm and lvm2 to the
  wily cloud-image seed [1].

  == general risks ==
  Adding these packages will add ~ 5M total to the cloud image installed system.

  == mdadm risks ==
  mdadm recommends on default-mta. So addition of this package to the cloud 
image means also adding an unconfigured mta (postifx). There is some discussion 
on this topic from ubuntu-devel at [2].

  Additionally, its possible presence of this package could cause
  issues.  It

[Touch-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

2015-09-01 Thread Raymond

http://git.alsa-project.org/?p=alsa-
kmirror.git;a=commitdiff_plain;h=bb9a16dc52281d98dfb525552d29d8939845d8e2


it was this patch change master mono from mono to stereo 



/* build master mono controls */
if (snd_ac97_try_volume_mix(ac97, AC97_MASTER_MONO)) {
-   if ((err = snd_ctl_add(card, 
snd_ac97_cnew(_ac97_controls_master_mono[0], ac97))) < 0)
+   if ((err = snd_ac97_cmix_new(card, "Master Mono Playback", 
AC97_MASTER_MONO, ac97)) < 0)
return err;
-   if ((err = snd_ctl_add(card, kctl = 
snd_ac97_cnew(_ac97_controls_master_mono[1], ac97))) < 0)
-   return err;
-   snd_ac97_change_volume_params1(ac97, AC97_MASTER_MONO, );
-   kctl->private_value &= ~(0xff << 16);
-   kctl->private_value |= (int)max << 16;
-   snd_ac97_write_cache(ac97, AC97_MASTER_MONO, 0x8000 | max);
}

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in Virtualbox:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/virtualbox/+bug/1487168/+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 1311995] Re: Web app browser doesn't support HiDPI screens

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

Title:
  Web app browser doesn't support HiDPI screens

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Web app brower does not scale on HIDPI screens. It does not follow
  QT's scale setting that scale all the ubuntu touch app on a HiDPI
  screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1311995/+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 1490750] Re: ad blocks web-browser

2015-09-01 Thread Josué

Yes, I'm not sure, but if i click on "Aceptar" maybe it can take me to a 
download. When ads like it appears you just have the option tu press "Aceptar". 
You also can't close the window (lash) using the gesture from the bottom to the 
upper. 
Sorry for my grammar... Did you understand?

greetings

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

Title:
  ad blocks web-browser

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Bq aquaris 4.5 15.04 r24

  Some types of ads can block the web-browser because you just have the option 
to click in the add pop-up
  Its very annoying since if you restart the web-browser it charges again the 
add. The only why to avoid it is after restart web-browser be faster than the 
app to close the window before it'll be charged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490750/+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 1491043] Re: libxcb 1.10 has important bug fixed in 1.11

2015-09-01 Thread Krzysztof Pyrkosz

So it is fixed for 15.10, which is still in pre-release state.
When will be update rolled for 15.04, which is still supported distribution and 
latest stable release?

** Changed in: libxcb (Ubuntu)
   Status: Invalid => New

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

Title:
  libxcb 1.10 has important bug fixed in 1.11

Status in libxcb package in Ubuntu:
  New

Bug description:
  libxcb 1.10 has serious bug which prevents multi-threaded OpenGL applications 
from working.
  It crashes app with message like:
  ../../src/xcb_conn.c:186: write_vec: Assertion `!c->out.queue_len' failed.
  It is described on:
  http://lists.freedesktop.org/archives/xcb/2013-December/009027.html
  Please release upgrade to 1.11 version which as far as I know fixed this 
issues for Ubuntu 15.04.

  Kubuntu 15.04

  libxcb1:
Zainstalowana: 1.10-2ubuntu1
Kandydująca:   1.10-2ubuntu1
Tabela wersji:
   *** 1.10-2ubuntu1 0
  500 http://pl.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1491043/+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 1490212] Re: "Modaliases" field missing from debian control file

FYI for anyone requiring background information on all this, the support
of cards and a list of PCI ID's is here
https://wireless.wiki.kernel.org/en/users/Drivers/b43

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+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 1490750] Re: ad blocks web-browser

2015-09-01 Thread Olivier Tilloy

Yes, I understand what you mean. Unfortunately, it’s the nature of
javascript alerts to be modal dialogs, so if a website chooses to put an
ad (or a fake virus warning or whatever scam mechanism) in an alert,
there’s nothing the user can do about it, except for not browsing to
this website.

There doesn’t seem to be any setting in oxide to disallow javascript
dialogs specifically (other than entirely turning off javascript, which
nowadays would result in a very broken UX on the web).

** Changed in: webbrowser-app (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  ad blocks web-browser

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Bq aquaris 4.5 15.04 r24

  Some types of ads can block the web-browser because you just have the option 
to click in the add pop-up
  Its very annoying since if you restart the web-browser it charges again the 
add. The only why to avoid it is after restart web-browser be faster than the 
app to close the window before it'll be charged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490750/+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 1090413] Re: Cursor moved by Wacom tablet does not evoke hidden Unity bar

2015-09-01 Thread Gordon Fitch

I tried the Wacom 'Intuos Pen Small' CTL-480 hooked up to a
Dell Vostro 220 running Ubuntu 14.04, and moving the cursor
to the left edge of the screen did not bring out the Unity
panel, where as the USB mouse I'm using did.  I can test this
with the Asus Eee running 12.04 if desired, etc.

-- Gordon Fitch


Will Cooke:
> I don't have a WACOM tablet to test.  Could you say if this is still
> causing an issue?
> 
> ** Changed in: unity
>Status: New => Incomplete
> 
> ** Changed in: unity (Ubuntu)
>Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1090413
> 
> Title:
>   Cursor moved by Wacom tablet does not evoke hidden Unity bar
> 
> Status in Unity:
>   Incomplete
> Status in unity package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   I am writing on an Eee PC, therefore, small screen.  Unity pane/bar is
>   normally hidden and is supposed to pop out when cursor is moved to
>   left end of screen.  This works with the pad as expected.  However,
>   when I have a Wacom tablet (ET-0405-U) hooked up via USB, and move the
>   cursor with the tablet stylus, the bar does not appear; I have to use
>   the pad. I am not sure where the problem is, but I am guessing it's
>   the Wacom driver.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: unity 5.18.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
>   Uname: Linux 3.2.0-34-generic i686
>   ApportVersion: 2.0.1-0ubuntu15
>   Architecture: i386
>   CheckboxSubmission: 0e19c774ba5c106a21a2dbfb27a8bc22
>   CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
>   CompizPlugins: 
> [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
>   Date: Fri Dec 14 10:08:02 2012
>   InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
> (20100429.4)
>   MarkForUpload: True
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: unity
>   UpgradeStatus: Upgraded to precise on 2012-08-29 (106 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1090413/+subscriptions

-- 
}"{  g...@panix.com
}"{  http://www.etaoin.com 
}"{  http://www.starrygordon.com
}"{  http://www.artezine.com
}"{  718-666-5853

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

Title:
  Cursor moved by Wacom tablet does not evoke hidden Unity bar

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  I am writing on an Eee PC, therefore, small screen.  Unity pane/bar is
  normally hidden and is supposed to pop out when cursor is moved to
  left end of screen.  This works with the pad as expected.  However,
  when I have a Wacom tablet (ET-0405-U) hooked up via USB, and move the
  cursor with the tablet stylus, the bar does not appear; I have to use
  the pad. I am not sure where the problem is, but I am guessing it's
  the Wacom driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.18.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic i686
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  CheckboxSubmission: 0e19c774ba5c106a21a2dbfb27a8bc22
  CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Fri Dec 14 10:08:02 2012
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
(20100429.4)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-08-29 (106 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1090413/+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 1490212] Re: "Modaliases" field missing from debian control file

Back onto software-properties-gtk, the "this device is not working" is
very unreliable.  I'm not sure how it works this out, but it doesn't
seem to account for the firmware being manually installed or through
e.g. the linux-firmware-nonfree package which also contains b43
firmware.

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+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 1426307] Re: location is inaccurate

2015-09-01 Thread Lucio Carreras

I just figured out that GPS is working perfectly in Portugal and Spain
but not in Germany. Mobile data connection and wifi are completely
turned off and location is available after 10-30 seconds. In Germany
there is no location available at all. Maybe it depends on the mobile
provider, maybe on the different time zone. Is there a way to check how
many satellites can be contacted? And what the phone is actually doing
while searching for satellites? And especially where. I am using stable
release r8.

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

Title:
  location is inaccurate

Status in Canonical System Image:
  Fix Released
Status in location-service package in Ubuntu:
  Fix Released
Status in location-service source package in Vivid:
  Confirmed
Status in location-service package in Ubuntu RTM:
  Fix Released

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Location is inaccurate, it thinks that I'm several kilometres away
  from my actual location, in the middle of the sea.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Fri Feb 27 11:10:42 2015
  InstallationDate: Installed on 2015-02-25 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1489076] Re: clicking on active call banner and indicators with mouse

2015-09-01 Thread Michael Terry

** Also affects: canonical-pocket-desktop
   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/1489076

Title:
  clicking on active call banner and indicators with mouse

Status in canonical-pocket-desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens

  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1489076/+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 1490750] Re: ad blocks web-browser

2015-09-01 Thread Olivier Tilloy

I’m not sure I understand what the issue is. This add uses the
javascript alert() API to display a modal dialog box. This is bad™, but
the browser cannot be clever about which alerts are legitimate, and
which are ads. Closing the dialog should allow you to continue browsing.
Or does it enter a loop and open another dialog again?

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

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

Title:
  ad blocks web-browser

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Bq aquaris 4.5 15.04 r24

  Some types of ads can block the web-browser because you just have the option 
to click in the add pop-up
  Its very annoying since if you restart the web-browser it charges again the 
add. The only why to avoid it is after restart web-browser be faster than the 
app to close the window before it'll be charged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490750/+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 1490212] [NEW] "Modaliases" field missing from debian control file

You have been subscribed to a public bug:

The b43 module is not listed as an option by the "additional drivers"
section of the software-properties-gtk utility.  This takes its
information from the ubuntu-drivers-common package and a bug has been
reported against that package (https://bugs.launchpad.net/ubuntu/+source
/ubuntu-drivers-common/+bug/1186779 ).

However, if I'm reading things correctly, the firmware-b43-installer
package could solve this by providing a modaliases field in the debian
control file.  For example, the bcmwl-kernel-source package has the
line:

Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

This would be scanned by the ubuntu-drivers-common package and
consequently appear in software-properties-gtk.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: b43-fwcutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch
-- 
"Modaliases" field missing from debian control file
https://bugs.launchpad.net/bugs/1490212
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

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

[Touch-packages] [Bug 1490212] Re: "Modaliases" field missing from debian control file

Adding software-properties to the party since much of this involves
them.

** Also affects: software-properties
   Importance: Undecided
   Status: New

** Project changed: software-properties => software-properties (Ubuntu)

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

Title:
  "Modaliases" field missing from debian control file

Status in b43-fwcutter package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New

Bug description:
  The b43 module is not listed as an option by the "additional drivers"
  section of the software-properties-gtk utility.  This takes its
  information from the ubuntu-drivers-common package and a bug has been
  reported against that package
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1186779 ).

  However, if I'm reading things correctly, the firmware-b43-installer
  package could solve this by providing a modaliases field in the debian
  control file.  For example, the bcmwl-kernel-source package has the
  line:

  Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*)

  This would be scanned by the ubuntu-drivers-common package and
  consequently appear in software-properties-gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+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 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

2015-09-01 Thread Serge Hallyn

Do you get further failures upon reboots, or, if you have
not rebooted, upon doing

sudo apt-get install --reinstall lxc

?

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+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 1491005] Re: /etc/mtab is a normal file (should be a symlink to /proc/mounts)

We indeed did have cases where badly written postinst scripts broke the
/etc/mtab symlink, e. g. bug 1419623. debian-fixup.service is supposed
to convert it to a symlink at boot -- is it still a symlink after a
fresh boot? Can you please show

  sudo systemctl status -l debian-fixup

?

** Summary changed:

- /etc/mtab is missing entries
+ /etc/mtab is a normal file (should be a symlink to /proc/mounts)

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  /etc/mtab is a normal file (should be a symlink to /proc/mounts)

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 15.10 dev with mount 2.26.2-6ubuntu3 and I'm noticing
  that after booting my system /etc/mtab is only containing an ecryptfs
  entry for my home folder but nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1491005/+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 1489076] Re: clicking on active call banner and indicators with mouse

2015-09-01 Thread Michael Terry

This is because DirectionalDragArea doesn't emit pressed() events for a
mouse (and thus, IndicatorsMenu doesn't emit showTapped() events, and
thus Panel doesn't activate the call hint).

Looks like this bug only happens over the actual indicator area.
Pressing on the left side of the panel ought to still 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/1489076

Title:
  clicking on active call banner and indicators with mouse

Status in canonical-pocket-desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens

  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1489076/+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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-09-01 Thread Tony Espy

** Changed in: network-manager (Ubuntu)
 Assignee: Andrea Bernabei (faenil) => Tony Espy (awe)

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+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 1487174] Re: apport-retrace's build sandbox routine carries on if it can't find the package for an ExecutablePath

Somehow the error tracker is receiving plenty of crash reports from
applications that aren't part of Ubuntu, so we do end up in a situation
where an unknown ExecutablePath is some what common.

While the first install_packages() call doesn't do much because pkgs is
empty, it stills creates a sandbox and updates the packages in it, and
that seems unnecessary if pkgs is empty.

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

Title:
  apport-retrace's build sandbox routine carries on if it can't find the
  package for an ExecutablePath

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  In the event that a package which provides an ExecutablePath or
  InterpreterPath can not be found apport will carry on building the
  sandbox but then exits a short while later (the last line in the
  pasted code). I think it'd be better if apport just quit earlier.

  Here's the code in question from sandboxutils.py:

  # package hooks might reassign Package:, check that we have the originally
  # crashing binary
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report:
  pkg = apport.packaging.get_file_package(report[path], True, 
pkgmap_cache_dir,
  
release=report['DistroRelease'],
  
arch=report.get('Architecture'))
  if pkg:
  apport.log('Installing extra package %s to get %s' % (pkg, 
path), log_timestamps)
  pkgs.append((pkg, pkg_versions.get(pkg)))
  else:   
  apport.warning('Cannot find package which ships %s', path)

  # unpack packages for executable using cache and sandbox
  if pkgs:
  try:
  outdated_msg += apport.packaging.install_packages(
  sandbox_dir, config_dir, report['DistroRelease'], pkgs,
  verbose, cache_dir, permanent_rootdir,
  architecture=report.get('Architecture'), origins=origins)
  except SystemError as e:
  apport.fatal(str(e))

  # sanity check: for a packaged binary we require having the executable in
  # the sandbox; TODO: for an unpackage binary we don't currently copy its
  # potential local library dependencies (like those in build trees) into 
the
  # sandbox, and we call gdb/valgrind on the binary outside the sandbox.
  if 'Package' in report:
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report and not os.path.exists(sandbox_dir + 
report[path]):
  apport.fatal('%s %s does not exist (report specified package 
%s)',
   path, sandbox_dir + report[path], 
report['Package'])

  Instead of warning with ('Cannot find package which ships %s', path) I
  think that should be a fatal error. It'd probably be optimal to even
  move the check for the crashing binary to the earliest place possible
  in make_sandbox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1487174/+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 1491005] Re: /etc/mtab is missing entries

2015-09-01 Thread Sworddragon

/etc/mtab is a normal file that doesn't point to /proc/mounts and got
changed the last time today. But this installation is an older one so
maybe this is an upgrading issue? Or maybe something ecryptfs-related
has overwritten the symlink to add its own entry?

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => New

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

Title:
  /etc/mtab is missing entries

Status in util-linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 15.10 dev with mount 2.26.2-6ubuntu3 and I'm noticing
  that after booting my system /etc/mtab is only containing an ecryptfs
  entry for my home folder but nothing else.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1491005/+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 1478799] Re: bluetooth not working in 15.10

2015-09-01 Thread Norbert

My problem was a kernel problem and was fixed with this patch upstream:

https://bugzilla.kernel.org/show_bug.cgi?id=103451


** Bug watch added: Linux Kernel Bug Tracker #103451
   http://bugzilla.kernel.org/show_bug.cgi?id=103451

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

Title:
  bluetooth not working in 15.10

Status in bluez package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10 Wily

  No bluetooth indicator visible.

  I can't activate bluetooth in the bluetooth system-settings.

  Bluetooth mouse not working (I can't pair it).

  syslog:
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: DIS cannot start: GATT 
is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init time 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init alert 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  VPN: loaded 
org.freedesktop.NetworkManager.pptp
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  DNS: loaded 
plugin dnsmasq
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: 
Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: DIS 
cannot start: GATT is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init time plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init alert plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully called 
chroot().
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully dropped 
remaining capabilities.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: No service file found 
in /etc/avahi/services.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Network interface 
enumeration completed.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Avahi mDNS/DNS-SD 
Stack.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Registering HINFO 
record with values 'X86_64'/'LINUX'.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Bluetooth service.

  hciconfig 
  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:15:83:15:A3:0B  ACL MTU: 672:4  SCO MTU: 48:1
DOWN 
RX bytes:445 acl:0 sco:0 events:15 errors:0
TX bytes:63 acl:0 sco:0 commands:15 errors:0

  rfkill list 
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1478799/+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 1457508] Re: [USB-Audio - Logitech USB Headset, recording] No sound at all

2015-09-01 Thread Alex

I also have a spare C270 and that one works fine. Not sure what the
difference is, but good to know!

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

Title:
  [USB-Audio - Logitech USB Headset, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Since upgrade to Vivid, my Logitech Clearchat Pro USB Headset mic is
  not working any more.

  No recording activity in pavucontrol from ClearChat Pro USB, although
  i can see recording activity from my Logitech C270 USB Webcam.

  By the past i noticed similar issues, always corrected by kernel
  upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 21 16:11:55 2015
  InstallationDate: Installed on 2014-03-27 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   N o   s u c h   d e v i c e
  Symptom_Card: Webcam C270 - USB Device 0x46d:0x825
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  Symptom_Type: No sound at all
  Title: [USB-Audio - Logitech USB Headset, recording] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0XCR8D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1457508/+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 1457508] Re: [USB-Audio - Logitech USB Headset, recording] No sound at all

2015-09-01 Thread Alex

PS -- I'm on 3.19.0-27-generic.

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

Title:
  [USB-Audio - Logitech USB Headset, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Since upgrade to Vivid, my Logitech Clearchat Pro USB Headset mic is
  not working any more.

  No recording activity in pavucontrol from ClearChat Pro USB, although
  i can see recording activity from my Logitech C270 USB Webcam.

  By the past i noticed similar issues, always corrected by kernel
  upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 21 16:11:55 2015
  InstallationDate: Installed on 2014-03-27 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   N o   s u c h   d e v i c e
  Symptom_Card: Webcam C270 - USB Device 0x46d:0x825
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  Symptom_Type: No sound at all
  Title: [USB-Audio - Logitech USB Headset, recording] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0XCR8D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1457508/+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 1457508] Re: [USB-Audio - Logitech USB Headset, recording] No sound at all

2015-09-01 Thread Alex

I'm also having trouble with a Logitech C310 -- no audio since going to
a 3.19 kernel (I'm on 14.04.3).

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

Title:
  [USB-Audio - Logitech USB Headset, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Since upgrade to Vivid, my Logitech Clearchat Pro USB Headset mic is
  not working any more.

  No recording activity in pavucontrol from ClearChat Pro USB, although
  i can see recording activity from my Logitech C270 USB Webcam.

  By the past i noticed similar issues, always corrected by kernel
  upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 21 16:11:55 2015
  InstallationDate: Installed on 2014-03-27 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) :   N o   s u c h   f i l e  
 o r   d i r e c t o r y
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   N o   s u c h   d e v i c e
  Symptom_Card: Webcam C270 - USB Device 0x46d:0x825
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  manu  31450 F pulseaudio
   /dev/snd/controlC1:  manu  31450 F pulseaudio
   /dev/snd/controlC0:  manu  31450 F pulseaudio
  Symptom_Type: No sound at all
  Title: [USB-Audio - Logitech USB Headset, recording] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (23 days ago)
  dmi.bios.date: 09/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0XCR8D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/17/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0XCR8D:rvrA01:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1457508/+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 1484367] Re: package tzdata 2015f-0ubuntu0.15.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package tzdata 2015f-0ubuntu0.15.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  I don't know what is this

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: tzdata 2015f-0ubuntu0.15.04
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  Date: Thu Aug 13 09:04:18 2015
  DuplicateSignature: package:tzdata:2015f-0ubuntu0.15.04:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-06-21 (52 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: tzdata
  Title: package tzdata 2015f-0ubuntu0.15.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1484367/+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 1490506] Re: Does not send report from a crash file

2015-09-01 Thread dino99

** Description changed:

  i got a crash to report ( lp:1490501 ) but Apport has silently close
- without warning/error; so the report has been filed manually.
+ without warning/error; so the report has been filed manually. But the
+ Apport process still continue to run and use a core to 100%, until i
+ need to kill that process.
  
  I then use 'ubuntu-bug apport' and that time the report is opened, but
  got some errors into the terminal. I can't says which is/are related to
  Apport and which affect chromium-browser (which Apport open to send that
  report)
  
  ubuntu-bug apport
  
   [12729:12729:0831/123712:ERROR:nss_util.cc(856)] After loading Root
  Certs, loaded==false: NSS error code: -8018
  
  [12729:12729:0831/123712:ERROR:background_mode_manager_aura.cc(14)] Not
  implemented reached in virtual void
  BackgroundModeManager::EnableLaunchOnStartup(bool)
  
  [12729:12729:0831/123712:ERROR:desktop_window_tree_host_x11.cc(833)] Not
  implemented reached in virtual void
  views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
  
  [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
  [12729:12729:0831/123736:ERROR:browser_main_loop.cc(231)] Gdk: 
gdk_window_set_user_time called on non-toplevel
  
  Note: these errors above are related to chromium-browser lp:1490570
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport 2.18-0ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-6.6-generic 4.2.0-rc8
  Uname: Linux 4.2.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportLog:
  
  ApportVersion: 2.18-0ubuntu9
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Aug 31 12:36:59 2015
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Does not send report from a crash file

Status in apport package in Ubuntu:
  New

Bug description:
  i got a crash to report ( lp:1490501 ) but Apport has silently close
  without warning/error; so the report has been filed manually. But the
  Apport process still continue to run and use a core to 100%, until i
  need to kill that process.

  I then use 'ubuntu-bug apport' and that time the report is opened, but
  got some errors into the terminal. I can't says which is/are related
  to Apport and which affect chromium-browser (which Apport open to send
  that report)

  ubuntu-bug apport

   [12729:12729:0831/123712:ERROR:nss_util.cc(856)] After loading Root
  Certs, loaded==false: NSS error code: -8018

  [12729:12729:0831/123712:ERROR:background_mode_manager_aura.cc(14)]
  Not implemented reached in virtual void
  BackgroundModeManager::EnableLaunchOnStartup(bool)

  [12729:12729:0831/123712:ERROR:desktop_window_tree_host_x11.cc(833)]
  Not implemented reached in virtual void
  views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)

  [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
  [12729:12729:0831/123736:ERROR:browser_main_loop.cc(231)] Gdk: 
gdk_window_set_user_time called on non-toplevel

  Note: these errors above are related to chromium-browser lp:1490570

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport 2.18-0ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-6.6-generic 4.2.0-rc8
  Uname: Linux 4.2.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportLog:

  ApportVersion: 2.18-0ubuntu9
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Aug 31 12:36:59 2015
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1490506/+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 1485787] Re: package_hook does not include package version

Fixed in trunk: http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/2996

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

** Changed in: apport (Ubuntu)
Milestone: ubuntu-15.10 => ubuntu-15.09

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

Title:
  package_hook does not include package version

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  All of these problem reports are missing a package version:

  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738

  This is because package_hook in apport only writes the following:

  pr['Package'] = options.package

  We should include the package version in the problem report.

  Test Case
  -
  1) echo "You have failed this city." | /usr/share/apport/package_hook -p 
apport
  2) grep "^Package" /var/crash/apport.1000.crash

  With the current version of apport you'll only see the package name,
  with the version from -proposed you'll see the package version in
  addition to the name.

  Regression Potential
  
  Worst case scenario I screwed the patch up and we loose the package name too, 
but given that it works in wily and there is a test for it in test_hooks.py 
that seems unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1485787/+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 1485787] Re: package_hook does not include package version

** Branch linked: lp:apport

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

Title:
  package_hook does not include package version

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  All of these problem reports are missing a package version:

  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738

  This is because package_hook in apport only writes the following:

  pr['Package'] = options.package

  We should include the package version in the problem report.

  Test Case
  -
  1) echo "You have failed this city." | /usr/share/apport/package_hook -p 
apport
  2) grep "^Package" /var/crash/apport.1000.crash

  With the current version of apport you'll only see the package name,
  with the version from -proposed you'll see the package version in
  addition to the name.

  Regression Potential
  
  Worst case scenario I screwed the patch up and we loose the package name too, 
but given that it works in wily and there is a test for it in test_hooks.py 
that seems unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1485787/+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 772214] Re: default state file location is wrong in manpage

** Branch linked: lp:~abone/ubuntu/wily/logrotate/fix-for-772214

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

Title:
  default state file location is wrong in manpage

Status in logrotate package in Ubuntu:
  Confirmed
Status in logrotate package in Debian:
  New

Bug description:
  Binary package hint: logrotate

  manpage says that /var/lib/logrotate.status is the default state file,
  but it's actually /var/lib/logrotate/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/772214/+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 1490856] [NEW] pulseaudio crash when exiting supertux 2

2015-09-01 Thread dinamic

Public bug reported:

pulseaudio crash when exiting supertux 2

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: pulseaudio 1:6.0-0ubuntu10~gcc5.3
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pixel   575 F pulseaudio
CurrentDesktop: Unity
Date: Tue Sep  1 10:36:25 2015
InstallationDate: Installed on 2014-07-10 (417 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.6
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7369
dmi.board.vendor: MSI
dmi.board.version: 1.0
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.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7369
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug third-party-packages wily

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

Title:
  pulseaudio crash when exiting supertux 2

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  pulseaudio crash when exiting supertux 2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu10~gcc5.3
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pixel   575 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep  1 10:36:25 2015
  InstallationDate: Installed on 2014-07-10 (417 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  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.:bvrV2.6:bd03/11/2008:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1490856/+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 1464201] Re: Please merge rsyslog 8.12.0-1 (main) from Debian unstable (main)

Hey Louis,

thanks! I cleaned up some further unnecessary delta:

 * Calling init_is_upstart in debian/rsyslog.init is unnecessary, already done 
by /lib/lsb/init-functions.d/01-upstart-lsb.
 * Dropping debian/rsyslog-mongodb.install is unnecessary as the binary doesn't 
get built in the first place.

and added the bug ref to the changelog. I tested this myself, and it
works fine. Uploaded now, many thanks for your work!

It's really a shame that we still have to carry this silly
"DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions" workaround (four
years old) which apparently has never been fully understood or analyzed.
Is that really still necessary? It doesn't seem to affect Debian?

** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Please merge rsyslog 8.12.0-1 (main) from Debian unstable (main)

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  debian unstable has rsyslog-8.12.0-1 Ubuntu available version is quite
  behind

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464201/+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 1449778] Re: [dialer-app] + [messaging-app] remove pop up asking to select a SIM

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

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

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

Title:
  [dialer-app] + [messaging-app] remove pop up asking to select a SIM

Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  krillin vivid and RTM

  Current behaviour: If the device has both SIM slots occupied, users
  are asked on action to select a SIM card for either placing a phone
  call or sending a text message. This can be very annoying for users
  because on first time launch there is a different pop up asking a
  similar question and explaining to users where to amend their default
  SIM for outgoing communication.

  --UX comment--

  The desired solution is to change the text of the popup on first time launch 
and remove the popup on action.
  A 3rd popup appears on the dialer app after user made a phone call and didn't 
select a default SIM. This should be removed as well.
  The SIM card in the first SIM slot should be selected by default and the 
first popup will inform users where to alter the selection and change the 
default SIM for outgoing communication.

  Please follow guidance in this spec:
  
https://docs.google.com/document/d/1BRy9-DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1449778/+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 1449778] Re: [dialer-app] + [messaging-app] remove pop up asking to select a SIM

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

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

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

Title:
  [dialer-app] + [messaging-app] remove pop up asking to select a SIM

Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  krillin vivid and RTM

  Current behaviour: If the device has both SIM slots occupied, users
  are asked on action to select a SIM card for either placing a phone
  call or sending a text message. This can be very annoying for users
  because on first time launch there is a different pop up asking a
  similar question and explaining to users where to amend their default
  SIM for outgoing communication.

  --UX comment--

  The desired solution is to change the text of the popup on first time launch 
and remove the popup on action.
  A 3rd popup appears on the dialer app after user made a phone call and didn't 
select a default SIM. This should be removed as well.
  The SIM card in the first SIM slot should be selected by default and the 
first popup will inform users where to alter the selection and change the 
default SIM for outgoing communication.

  Please follow guidance in this spec:
  
https://docs.google.com/document/d/1BRy9-DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1449778/+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 1419877] Re: [bluetooth] krillin advertized as type "computer"

2015-09-01 Thread Simon Fels

This can get rather serios if remote device doesn't allow connection
with specific types of device like my carkit. It doesn't want to connect
with my krillin device as it has a wrong device type (being a laptop)
set.

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

Title:
  [bluetooth] krillin advertized as type "computer"

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 228, the device is advertized as being a "computer", it
  should probably be a "phone" rather?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+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 1487174] Re: apport-retrace's build sandbox routine carries on if it can't find the package for an ExecutablePath

** Branch linked: lp:apport

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

Title:
  apport-retrace's build sandbox routine carries on if it can't find the
  package for an ExecutablePath

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  In the event that a package which provides an ExecutablePath or
  InterpreterPath can not be found apport will carry on building the
  sandbox but then exits a short while later (the last line in the
  pasted code). I think it'd be better if apport just quit earlier.

  Here's the code in question from sandboxutils.py:

  # package hooks might reassign Package:, check that we have the originally
  # crashing binary
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report:
  pkg = apport.packaging.get_file_package(report[path], True, 
pkgmap_cache_dir,
  
release=report['DistroRelease'],
  
arch=report.get('Architecture'))
  if pkg:
  apport.log('Installing extra package %s to get %s' % (pkg, 
path), log_timestamps)
  pkgs.append((pkg, pkg_versions.get(pkg)))
  else:   
  apport.warning('Cannot find package which ships %s', path)

  # unpack packages for executable using cache and sandbox
  if pkgs:
  try:
  outdated_msg += apport.packaging.install_packages(
  sandbox_dir, config_dir, report['DistroRelease'], pkgs,
  verbose, cache_dir, permanent_rootdir,
  architecture=report.get('Architecture'), origins=origins)
  except SystemError as e:
  apport.fatal(str(e))

  # sanity check: for a packaged binary we require having the executable in
  # the sandbox; TODO: for an unpackage binary we don't currently copy its
  # potential local library dependencies (like those in build trees) into 
the
  # sandbox, and we call gdb/valgrind on the binary outside the sandbox.
  if 'Package' in report:
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report and not os.path.exists(sandbox_dir + 
report[path]):
  apport.fatal('%s %s does not exist (report specified package 
%s)',
   path, sandbox_dir + report[path], 
report['Package'])

  Instead of warning with ('Cannot find package which ships %s', path) I
  think that should be a fatal error. It'd probably be optimal to even
  move the check for the crashing binary to the earliest place possible
  in make_sandbox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1487174/+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 1487174] Re: apport-retrace's build sandbox routine carries on if it can't find the package for an ExecutablePath

> Well trying to run get_file_package() before install_packages() didn't work 
> out to well.
> NotImplementedError: Cannot map DistroRelease to a code name without 
> install_packages()

Indeed, as without a config directory we can't map something like
"Ubuntu 15.04" to "wily", which we need to download the matching
Contents.gz.

I turned the warning into a fatal, which should already help:
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2997 .
This should be okay, as realistically the first
apport.packaging.install_packages() call does not really do anything
(unless you specified extra_packages), as we usually have ProcMaps
available in reports and thus use the needed_runtime_packages() pass to
install only the packages we need instead of all Packages: plus
Dependencies:. So I think any additional potential speedup by reordering
things should be miniscule, especially since (hopefully) an unknown
ExecutablePath isn't the common case?

** Changed in: apport
   Status: New => Fix Released

** Changed in: apport (Ubuntu)
   Status: New => Fix Committed

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

Title:
  apport-retrace's build sandbox routine carries on if it can't find the
  package for an ExecutablePath

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  In the event that a package which provides an ExecutablePath or
  InterpreterPath can not be found apport will carry on building the
  sandbox but then exits a short while later (the last line in the
  pasted code). I think it'd be better if apport just quit earlier.

  Here's the code in question from sandboxutils.py:

  # package hooks might reassign Package:, check that we have the originally
  # crashing binary
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report:
  pkg = apport.packaging.get_file_package(report[path], True, 
pkgmap_cache_dir,
  
release=report['DistroRelease'],
  
arch=report.get('Architecture'))
  if pkg:
  apport.log('Installing extra package %s to get %s' % (pkg, 
path), log_timestamps)
  pkgs.append((pkg, pkg_versions.get(pkg)))
  else:   
  apport.warning('Cannot find package which ships %s', path)

  # unpack packages for executable using cache and sandbox
  if pkgs:
  try:
  outdated_msg += apport.packaging.install_packages(
  sandbox_dir, config_dir, report['DistroRelease'], pkgs,
  verbose, cache_dir, permanent_rootdir,
  architecture=report.get('Architecture'), origins=origins)
  except SystemError as e:
  apport.fatal(str(e))

  # sanity check: for a packaged binary we require having the executable in
  # the sandbox; TODO: for an unpackage binary we don't currently copy its
  # potential local library dependencies (like those in build trees) into 
the
  # sandbox, and we call gdb/valgrind on the binary outside the sandbox.
  if 'Package' in report:
  for path in ('InterpreterPath', 'ExecutablePath'):
  if path in report and not os.path.exists(sandbox_dir + 
report[path]):
  apport.fatal('%s %s does not exist (report specified package 
%s)',
   path, sandbox_dir + report[path], 
report['Package'])

  Instead of warning with ('Cannot find package which ships %s', path) I
  think that should be a fatal error. It'd probably be optimal to even
  move the check for the crashing binary to the earliest place possible
  in make_sandbox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1487174/+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 1301623] Re: unity freezes when moving windows among workspaces

2015-09-01 Thread Michael Tienzo

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

New Ubuntu user here. Experienced this on 14.04. Didn't want to disable
window snapping, so my workaround was to place the menu bar back to the
panel. Hope this gets fixed.

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

Title:
  unity freezes when moving windows among workspaces

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Sometimes In Ubuntu 14.04, when I move windows from one workspace to
  another, Unity freezes, letting me with this 4 workspaces overview. I
  have to use terminal and restart Unity to resolve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 23:26:06 2014
  DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-02-10 (51 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic 
root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-03-18 (15 days ago)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Mar 31 16:48:50 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8192
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1301623/+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 772214] Re: default state file location is wrong in manpage

2015-09-01 Thread Bug Watch Updater

** Changed in: logrotate (Debian)
   Status: Unknown => New

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

Title:
  default state file location is wrong in manpage

Status in logrotate package in Ubuntu:
  Confirmed
Status in logrotate package in Debian:
  New

Bug description:
  Binary package hint: logrotate

  manpage says that /var/lib/logrotate.status is the default state file,
  but it's actually /var/lib/logrotate/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/772214/+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 772214] Re: default state file location is wrong in manpage

2015-09-01 Thread Andrey Bondarenko

** Changed in: logrotate (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  default state file location is wrong in manpage

Status in logrotate package in Ubuntu:
  Fix Committed
Status in logrotate package in Debian:
  New

Bug description:
  Binary package hint: logrotate

  manpage says that /var/lib/logrotate.status is the default state file,
  but it's actually /var/lib/logrotate/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/772214/+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 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth

2015-09-01 Thread Simon Fels

@Pat: I tried to reproduce this today but didn't had success.

A few more questions:

1. With "Leave the car and disconnect" you mean the phone automatically 
disconnects as it goes out of range or do you actively disconnect the car?
2. How long did you wait to place the call after you left the car? You saw you 
were disconnect from the car (through the indicator)?

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

Title:
  After disconnnecting from car bluetooth, audio is still routed to
  bluetooth

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  New

Bug description:
  MX4 r96

  This has been happening fro a few weeks
  Phone automatically connects to the car, you don't have to make or receive a 
call
  Leave the car and disconnect
  Place a call
  The audio starts out using the phone as expected, after a few seconds the 
audio switches to bluetooth
  You can manually change the audio in the UI
  This happens until you reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+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 1419877] Re: [bluetooth] krillin advertized as type "computer"

2015-09-01 Thread Simon Fels

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Simon Fels (morphis)

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

Title:
  [bluetooth] krillin advertized as type "computer"

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 228, the device is advertized as being a "computer", it
  should probably be a "phone" rather?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+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 1468624] Re: job queue not populated and nothing listed

2015-09-01 Thread dino99

hi Till,

here is the answer made by Matthias Clasen (id=754346):
**
The job queue is in the control-center printer panel. I don't think we need to 
duplicate it in the print dialog.
***

So i does not think that upstream will made change, as it appear the request is 
not understood, or wrongly affected to GTK print dialog.  I'm not sure about 
that 'control-center printer panel', is it refering to hp-tool box or else ?
Can you explain to Matthias that usability issue, and request a better design 
to replace the now dispatched features ?

** Changed in: gtk+3.0 (Ubuntu)
   Status: Invalid => New

** Changed in: hplip (Ubuntu)
   Status: Invalid => New

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

Title:
  job queue not populated and nothing listed

Status in gtk+3.0 package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  when a printing task is started, it happens that some old jobs are
  still in job queue and so are printed first instead of the wanted one.

  Opening the hplip toolbox, the old jobs are not listed, so its
  impossible to know about it/them and their numbers. And there is no
  option to blindly emptying that queue. Such working feature is really
  needed.

  But if the user ask for opening a task into that hplip toolbox, that
  time the job is displayed with its path. That is expected, but the
  real pain is about these old jobs not listed, not shown and fully
  unknown.

  On the other side cups is also fully ignoring to list & display these
  old jobs: this is also fully awaited.

  https://github.com/gtkd-developers/GtkD/issues/126
  https://bugzilla.gnome.org/show_bug.cgi?id=754346
  https://bugs.launchpad.net/hplip/+bug/1490273  Tray icon missing

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: hplip 3.15.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.0.0-3.5-generic 4.0.5
  Uname: Linux 4.0.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CupsErrorLog:

  CurrentDesktop: GNOME
  Date: Thu Jun 25 08:29:24 2015
  Lpstat:
   device for Photosmart-C4500-series: 
usb://HP/Photosmart%20C4500%20series?serial=CN87JD4109057K=1
   device for Photosmart_C4500: 
hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Photosmart_C4500.ppd', 
'/etc/cups/ppd/Photosmart-C4500-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Photosmart_C4500.ppd: Permission denied
   grep: /etc/cups/ppd/Photosmart-C4500-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-3-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: hplip
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1468624/+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 1419877] Re: [bluetooth] krillin advertized as type "computer"

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

Title:
  [bluetooth] krillin advertized as type "computer"

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Using rtm 228, the device is advertized as being a "computer", it
  should probably be a "phone" rather?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419877/+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 1468624] Re: job queue not populated and nothing listed

2015-09-01 Thread dino99

ok i've found what "control-center printer panel" refer to: System
Settings --> Printers

but there, if we can get the jobs list, it is a separate dialog and does
not offer the interactivity when a print job is made

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

Title:
  job queue not populated and nothing listed

Status in gtk+3.0 package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  when a printing task is started, it happens that some old jobs are
  still in job queue and so are printed first instead of the wanted one.

  Opening the hplip toolbox, the old jobs are not listed, so its
  impossible to know about it/them and their numbers. And there is no
  option to blindly emptying that queue. Such working feature is really
  needed.

  But if the user ask for opening a task into that hplip toolbox, that
  time the job is displayed with its path. That is expected, but the
  real pain is about these old jobs not listed, not shown and fully
  unknown.

  On the other side cups is also fully ignoring to list & display these
  old jobs: this is also fully awaited.

  https://github.com/gtkd-developers/GtkD/issues/126
  https://bugzilla.gnome.org/show_bug.cgi?id=754346
  https://bugs.launchpad.net/hplip/+bug/1490273  Tray icon missing

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: hplip 3.15.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.0.0-3.5-generic 4.0.5
  Uname: Linux 4.0.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CupsErrorLog:

  CurrentDesktop: GNOME
  Date: Thu Jun 25 08:29:24 2015
  Lpstat:
   device for Photosmart-C4500-series: 
usb://HP/Photosmart%20C4500%20series?serial=CN87JD4109057K=1
   device for Photosmart_C4500: 
hp:/usb/Photosmart_C4500_series?serial=CN87JD4109057K
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Photosmart_C4500.ppd', 
'/etc/cups/ppd/Photosmart-C4500-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Photosmart_C4500.ppd: Permission denied
   grep: /etc/cups/ppd/Photosmart-C4500-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-3-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: hplip
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1468624/+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 1319403] Re: uid match not working in sudoers file

2015-09-01 Thread Mark Huijgen

New version sudo 1.8.9p5-1ubuntu1.2 fixes the UID problem for me as well
on Trusty.

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

Title:
  uid match not working in sudoers file

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Trusty:
  Fix Committed
Status in sudo source package in Utopic:
  Won't Fix

Bug description:
  [Impact]

  sudo 1.8.9p5 had a bug which caused any rule added to sudoers to be
  ignored if the user was stated by user id (with the username works
  just fine).

  [Test Case]

  * Rules using user id should work after the fix.

  #33ALL = NOPASSWD: /usr/bin/whatever

  * Also make sure that rules using username still work.

  myusernameALL = NOPASSWD: /usr/bin/whatever

  [Regression Potential]

  This bug has been fixed in the current stable release of sudo
  (1.8.10p3).

  You can check the original bug report (and patch) here:
  http://www.sudo.ws/bugs/show_bug.cgi?id=640

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1319403/+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 1464201] Re: Please merge rsyslog 8.12.0-1 (main) from Debian unstable (main)

** Branch linked: lp:ubuntu/wily-proposed/rsyslog

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

Title:
  Please merge rsyslog 8.12.0-1 (main) from Debian unstable (main)

Status in rsyslog package in Ubuntu:
  Fix Committed

Bug description:
  debian unstable has rsyslog-8.12.0-1 Ubuntu available version is quite
  behind

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464201/+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 1381050] Re: "Import Key File" fails when the path of the file has special characters

Using the change provided (path = path.encode('utf-8') # ensure path is
encoded in UTF-8) still doesn't seem to fix the issue for me on Wily.

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1491055] Re: package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2015-09-01 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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1491055

Title:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in util-linux package in Ubuntu:
  New

Bug description:
  das sistem leuft nürnoch total rukelich

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: uuid-runtime 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Tue Sep  1 19:04:11 2015
  DuplicateSignature: package:uuid-runtime:2.25.2-4ubuntu3:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-09-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1491055/+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 1489076] Re: clicking on active call banner and indicators with mouse

2015-09-01 Thread kevin gunn

so is this effectively the same as bug 1473566 ?
altho, note that it seems to work for some things but not others.

** Changed in: canonical-pocket-desktop
   Importance: Undecided => Critical

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Critical

** Description changed:

  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens
  
  there is also a design question of what is to happen in this case with
- the indicators? should a click reveal ?
+ the indicators? should a click reveal ? or should indicators be kept to
+ a non-green area when a monitor is connected? could get tricky quick

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

Title:
  clicking on active call banner and indicators with mouse

Status in canonical-pocket-desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens

  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ? or should indicators be kept
  to a non-green area when a monitor is connected? could get tricky
  quick

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1489076/+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 1438465] Re: It's possible to put a window under the top panel

2015-09-01 Thread kevin gunn

changing to critical b/c it is super annoying, especially b/c windows
now remember their locations

** Changed in: unity8 (Ubuntu)
   Importance: High => Critical

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: qtmir
   Importance: Undecided => Critical

** Changed in: canonical-pocket-desktop
   Importance: High => Critical

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

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

Status in canonical-pocket-desktop:
  New
Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1438465/+subscriptions

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

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2015-09-01 Thread AE Grey

^Submitted a apport report as well.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts

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

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

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts

Status in Canonical System Image:
  Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To

[Touch-packages] [Bug 1478087] Re: ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

2015-09-01 Thread Tyler Hicks

I've created an upstream lightdm merge request to add login and logout
auditing support:

  https://code.launchpad.net/~tyhicks/lightdm/auditing/+merge/269828

I've also submitted the (simple) changes needed in the openssh package
to Debian since Colin keeps the Debian and Ubuntu openssh package in
sync:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797727

** Bug watch added: Debian Bug tracker #797727
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797727

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

Title:
  ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

Status in audit package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out 
the login 
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  
  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1478087/+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 1319278] Re: aulastlog doesn't report logins

2015-09-01 Thread Tyler Hicks

FYI, I've been updating bug #1478087 with my findings to fix audit
login/logout event logging.

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

Title:
  aulastlog doesn't report logins

Status in audit package in Ubuntu:
  New

Bug description:
  aulastlog and aulast don't appear to be functioning correctly:

  root@hunt:~# aulast
  root@hunt:~# aulastlog
  Username Port From   Latest
  root **Never logged in**
  daemon   **Never logged in**
  bin  **Never logged in**
  sys  **Never logged in**
  sync **Never logged in**
  games**Never logged in**
  man  **Never logged in**
  lp   **Never logged in**
  mail **Never logged in**
  news **Never logged in**
  uucp **Never logged in**
  proxy**Never logged in**
  www-data **Never logged in**
  backup   **Never logged in**
  list **Never logged in**
  irc  **Never logged in**
  gnats**Never logged in**
  nobody   **Never logged in**
  libuuid  **Never logged in**
  syslog   **Never logged in**
  messagebus   **Never logged in**
  colord   **Never logged in**
  lightdm  **Never logged in**
  whoopsie **Never logged in**
  avahi-autoipd**Never logged in**
  avahi**Never logged in**
  usbmux   **Never logged in**
  kernoops **Never logged in**
  pulse**Never logged in**
  rtkit**Never logged in**
  speech-dispatcher **Never logged in**
  hplip**Never logged in**
  saned**Never logged in**
  sarnold  **Never logged in**
  sshd **Never logged in**
  libvirt-qemu **Never logged in**
  libvirt-dnsmasq  **Never logged in**
  sbuild   **Never logged in**
  lxc-dnsmasq  **Never logged in**
  dictd**Never logged in**
  statd**Never logged in**
  dnsmasq  **Never logged in**
  ntp  **Never logged in**
  pdns **Never logged in**
  clickpkg **Never logged in**
  usermetrics  **Never logged in**
  root@hunt:~# 

  I would expect at least my user account sarnold should have logged in
  -- it was how I got to sudo, after all.

  There's no shortage of logging information, it just appears the logs
  for USER_LOGIN are missing:

  root@hunt:~# ausearch -l | wc -l
  262312
  root@hunt:~# ausearch -l | grep USER_LOGIN | wc -l
  0
  root@hunt:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: auditd 1:2.3.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue May 13 23:48:21 2014
  InstallationDate: Installed on 2012-10-18 (573 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=en_US

[Touch-packages] [Bug 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

2015-09-01 Thread Derek Poon

I got this message on trusty 14.04:

Processing triggers for hicolor-icon-theme (0.13-1) ...

(gtk-update-icon-cache-3.0:31711): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.


As instructed, I tried and got:

# gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
The program 'gdk-pixbuf-query-loaders' is currently not installed. You can 
install it by typing:
apt-get install libgdk-pixbuf2.0-dev


Taking that hint, if I install libgdk-pixbuf2.0-dev first, then 
hicolor-icon-theme.postinst no longer complains.  So, maybe 
/usr/bin/gdk-pixbuf-query-loaders belongs in the libgdk-pixbuf2.0 rather than 
the libgdk-pixbuf2.0-dev package.  Furthermore, libgtk-3-bin (which owns the 
/usr/bin/gtk-update-icon-cache-3.0 command that hicolor-icon-theme.postinst 
calls) should declare a dependency on it.

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

Title:
  GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
  /gdk-pixbuf-2.0/2.10.0/loaders.cache'

Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Debian:
  New

Bug description:
  During installation of updated version of libgdk-pixbuf2.0-0 on August
  10th 2010, the apt term.log contained multiple (>300) copies of the
  following warning:

  (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf
  loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No
  such file or directory

  Nevertheless, the file complained about exists, and is readable in
  gedit.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Aug 16 18:13:29 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 1384431] Re: libapparmor's aa_query_label() needs man page documentation

2015-09-01 Thread Steve Beattie

A man page for aa_query_label(3) was included in the AppArmor 2.10
release.

** Changed in: apparmor
   Status: Triaged => Fix Released

** Changed in: apparmor
Milestone: 2.9.3 => None

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

Title:
  libapparmor's aa_query_label() needs man page documentation

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  The aa_query_label() interface should be documented with a new man
  page.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1384431/+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 1485787] Re: package_hook does not include package version

Setting up apport (2.14.1-0ubuntu3.13) ...
apport start/running
bdmurray@clean-trusty-amd64:~$ echo "You have failed this city." | 
/usr/share/apport/package_hook -p apport
bdmurray@clean-trusty-amd64:~$ grep "^Package" /var/crash/apport.1000.crash
Package: apport 2.14.1-0ubuntu3.13


** Tags removed: verification-needed
** Tags added: verification-done-trusty

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

Title:
  package_hook does not include package version

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  All of these problem reports are missing a package version:

  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738

  This is because package_hook in apport only writes the following:

  pr['Package'] = options.package

  We should include the package version in the problem report.

  Test Case
  -
  1) echo "You have failed this city." | /usr/share/apport/package_hook -p 
apport
  2) grep "^Package" /var/crash/apport.1000.crash

  With the current version of apport you'll only see the package name,
  with the version from -proposed you'll see the package version in
  addition to the name.

  Regression Potential
  
  Worst case scenario I screwed the patch up and we loose the package name too, 
but given that it works in wily and there is a test for it in test_hooks.py 
that seems unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1485787/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-09-01 Thread Don McCants

Sorry, I just saw this. It should read:

"mouse power management should NOT take priority over OS power
management"

And I'm leaving the word NOT in all caps. I find this to be one of the
most frustrating laptop bugs ever, other than broken keys and poor
touchpads. I could care less about mouse power--unless your mouse lights
up like a xmas tree, that battery will last 2 years.

My laptop battery, on the other hand, runs out several times a day with
heavy use.

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1470700] Re: QNetworkAccessManager hangs when in flight mode

2015-09-01 Thread Michi Henning

I was going to test whether networkAccessible() returns the right thing
now. But it looks like silo 32 won't build at the moment. I couldn't
find another silo for this. Am I looking in the wrong place?

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

Title:
  QNetworkAccessManager hangs when in flight mode

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  When my phone is in flight mode, HTTP requests made using
  QNetworkAccessManager seem to hang rather than erroring out
  immediately.

  From my tests, it looks like the HTTP request is blocked until the
  flight mode is disabled and a network connection is reestablished.
  This is contrary to the documentation, which states:

  """If the network is not accessible the network access manager will
  not process any new network requests, all such requests will fail with
  an error. Requests with URLs with the file:// scheme will still be
  processed."""

  http://doc.qt.io/qt-5/qnetworkaccessmanager.html#networkAccessible-
  prop

  By running strace on my test program, it doesn't even look like it
  attempts to open a TCP connection when blocked in flight mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1470700/+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 1491102] Re: [FFE] add mdadm and lvm2 to cloud image

2015-09-01 Thread Scott Moser

** Description changed:

  In order to make use of raid and lvm functionality that is being added
  to curtin, we need to have mdadm and lvm2 packages available.  curtin is
  able to install the packages, but that is less desireable than having
  them already available inside the image.
  
  This bug is a feature freeze exception to add mdadm and lvm2 to the wily
  cloud-image seed [1].
  
  == general risks ==
  Adding these packages will add ~ 5M total to the cloud image installed system.
  
  == mdadm risks ==
- mdadm recommends on default-mta. So addition of this package to the cloud 
image means also adding an unconfigured mta (postifx). There is some discussion 
on this topic from ubuntu-devel at [2].
+ mdadm recommends 'default-mta', and cloud-images have always been built with 
'recommends by default'. So addition of this package to the cloud image means 
also adding an unconfigured mta (postifx). There is some discussion on this 
topic from ubuntu-devel at [2].
+ 
+ As a point of reference here, I did a server ISO install with raid, and
+ found that 'default-mta' does *not* get installed.  The installer must
+ select to install mdadm but not pull in its Recommends.
  
  Additionally, its possible presence of this package could cause issues.
  It installs udev rules that could misfire.  Any such issues encountered
  really should be fixed anyway, rather than just hoped to not be hit.
  
  == lvm2 risks ==
  Similarly to mdadm, lvm adds udev rules and could raise cause problems.
  As with mdadm, any such issues really ought to be fixed any way.
  
- 
  == general information ==
  The reason this is proposed for inclusion into the cloud-image is 2 fold
  a.) the maas ephemeral images are created from the cloud-image.  so packages 
in the cloud-image are then available in the install environment for maas.  We 
dont want to add differences between these installation sets.
  b.) it is not unreasonable to add these packages to the cloud image.  It is 
not at all farfetched that someone would use lvm or raid in a "cloud" 
environment, so they're not entirely wasted space there.
  
  --
  [1] 
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/view/head:/cloud-image
  [2] http://irclogs.ubuntu.com/2015/08/06/%23ubuntu-devel.html#t22:53

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

Title:
  [FFE] add mdadm and lvm2 to cloud image

Status in lvm2 package in Ubuntu:
  New
Status in mdadm package in Ubuntu:
  New

Bug description:
  In order to make use of raid and lvm functionality that is being added
  to curtin, we need to have mdadm and lvm2 packages available.  curtin
  is able to install the packages, but that is less desireable than
  having them already available inside the image.

  This bug is a feature freeze exception to add mdadm and lvm2 to the
  wily cloud-image seed [1].

  == general risks ==
  Adding these packages will add ~ 5M total to the cloud image installed system.

  == mdadm risks ==
  mdadm recommends 'default-mta', and cloud-images have always been built with 
'recommends by default'. So addition of this package to the cloud image means 
also adding an unconfigured mta (postifx). There is some discussion on this 
topic from ubuntu-devel at [2].

  As a point of reference here, I did a server ISO install with raid,
  and found that 'default-mta' does *not* get installed.  The installer
  must select to install mdadm but not pull in its Recommends.

  Additionally, its possible presence of this package could cause
  issues.  It installs udev rules that could misfire.  Any such issues
  encountered really should be fixed anyway, rather than just hoped to
  not be hit.

  == lvm2 risks ==
  Similarly to mdadm, lvm adds udev rules and could raise cause problems.
  As with mdadm, any such issues really ought to be fixed any way.

  == general information ==
  The reason this is proposed for inclusion into the cloud-image is 2 fold
  a.) the maas ephemeral images are created from the cloud-image.  so packages 
in the cloud-image are then available in the install environment for maas.  We 
dont want to add differences between these installation sets.
  b.) it is not unreasonable to add these packages to the cloud image.  It is 
not at all farfetched that someone would use lvm or raid in a "cloud" 
environment, so they're not entirely wasted space there.

  --
  [1] 
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/view/head:/cloud-image
  [2] http://irclogs.ubuntu.com/2015/08/06/%23ubuntu-devel.html#t22:53

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

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

[Touch-packages] [Bug 1490750] Re: ad blocks web-browser

2015-09-01 Thread Luciano Barea

Any option in Javascript alert() API for add a close button, "Close" in
contextual menu, or be identify like other normal window in "Open Tabs"?

Sorry for my grammar...

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

Title:
  ad blocks web-browser

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Bq aquaris 4.5 15.04 r24

  Some types of ads can block the web-browser because you just have the option 
to click in the add pop-up
  Its very annoying since if you restart the web-browser it charges again the 
add. The only why to avoid it is after restart web-browser be faster than the 
app to close the window before it'll be charged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490750/+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 33288]

2015-09-01 Thread Albert Astals Cid

I just realized we never really followed up on the last two patches.

My concern is that they change the pdftotext output.

I though they where for a) speed b) text selection so i'd prefer if they
did not change pdftotext output.

I've checked a few files of the changed ones and the changes can be
argued not to be for better or worse, but then again the problem is that
1 out of 3 files i have has a changed output in pdftotext and having
1600 files in the test suite it makes it impossible for me to go over
them all and verify the changes are "not better nor worse".

Is there any chance we get patches that don't influence pdftotext output
or at least not such drastically?

And yes, i know it's ages ago since you wrote the patches, sorry.

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

Title:
  Evince doesn't handle columns properly

Status in Poppler:
  Confirmed
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Lucid:
  Fix Released

Bug description:
  So, now that RC is here, let's propose it as an SRU.
  I've pushed it in lucid-proposed. The debdiff is 
poppler_0.12.4-0ubuntu4_2_0.12.4-0ubuntu5.debdiff attached there for 
information. I'm removing old debdiff to avoid confusion.

  poppler (0.12.4-0ubuntu5) lucid-proposed; urgency=low

* debian/patches/11_column_selection.patch:
  - backport from upstream git commit to fix wrong selection in pdf when
containing tables, long text, broken flow and so on.
(fixing most of known issues with selection in pdf) (LP: #33288)

  
  
  

  When making a multi column selection from a PDF like this:

  http://www.specialist-games.com/mordheim/assets/lrb/1Rules.pdf

  And pasting the result into OpenOffice.org the columns are not
  maintained. The results unusable because the text from both columns
  becomes mixed.

  Please note, this is not a PDF problem, using Adobe Acrobat Reader 7.x
  under Windows does properly copy-paste columned text over to
  OpenOffice.org.

  Regards,
  Pascal de Bruijn

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/33288/+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 1491182] [NEW] /usr/bin/dialer-app:11:size:size:QCoreApplicationPrivate::sendThroughObjectEventFilters:QCoreApplicationPrivate::notify_helper:QCoreApplication::notify

2015-09-01 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding dialer-app.  This problem was most recently seen with version
0.1+15.10.20150810-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/49939ac04e076972cae62ec846e3d0e8c14f7d4f
contains more details.

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


** Tags: vivid wily

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

Title:
  /usr/bin/dialer-
  
app:11:size:size:QCoreApplicationPrivate::sendThroughObjectEventFilters:QCoreApplicationPrivate::notify_helper:QCoreApplication::notify

Status in dialer-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding dialer-app.  This problem was most recently seen with
  version 0.1+15.10.20150810-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/49939ac04e076972cae62ec846e3d0e8c14f7d4f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1491182/+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 1491102] Re: [FFE] add mdadm and lvm2 to cloud image

TBH I'm less concerned about this from the POV of a FFE rather than in
general. You won't ever need this in almost all cloud environments, and
it adds unnecessarily complexity, boot delays, and potential boot
blockers. I can't think of a reason why you would set up LVM and mdadm
in the cloud guest, rather than on the host?

This is different for using cloud images on real hardware, of course.
But for that we are also missing a lot of kernel drivers for that (as
the cloud images only have linux-image-virtual, not -generic).

Perhaps it would be time to split this to build two images? One for real
clouds, which could then also drop other bits which are rarely needed in
the cloud and would better be installed on demand in user_data:
accountsservice, ntfs-3g, sosreport, aptitude, vim, etc. And one which
are much more like the server images that we have today, with a nice and
complete shell CLI environment, a full kernel, mdadm and friends?

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

Title:
  [FFE] add mdadm and lvm2 to cloud image

Status in lvm2 package in Ubuntu:
  New
Status in mdadm package in Ubuntu:
  New

Bug description:
  In order to make use of raid and lvm functionality that is being added
  to curtin, we need to have mdadm and lvm2 packages available.  curtin
  is able to install the packages, but that is less desireable than
  having them already available inside the image.

  This bug is a feature freeze exception to add mdadm and lvm2 to the
  wily cloud-image seed [1].

  == general risks ==
  Adding these packages will add ~ 5M total to the cloud image installed system.

  == mdadm risks ==
  mdadm recommends 'default-mta', and cloud-images have always been built with 
'recommends by default'. So addition of this package to the cloud image means 
also adding an unconfigured mta (postifx). There is some discussion on this 
topic from ubuntu-devel at [2].

  As a point of reference here, I did a server ISO install with raid,
  and found that 'default-mta' does *not* get installed.  The installer
  must select to install mdadm but not pull in its Recommends.

  Additionally, its possible presence of this package could cause
  issues.  It installs udev rules that could misfire.  Any such issues
  encountered really should be fixed anyway, rather than just hoped to
  not be hit.

  == lvm2 risks ==
  Similarly to mdadm, lvm adds udev rules and could raise cause problems.
  As with mdadm, any such issues really ought to be fixed any way.

  == general information ==
  The reason this is proposed for inclusion into the cloud-image is 2 fold
  a.) the maas ephemeral images are created from the cloud-image.  so packages 
in the cloud-image are then available in the install environment for maas.  We 
dont want to add differences between these installation sets.
  b.) it is not unreasonable to add these packages to the cloud image.  It is 
not at all farfetched that someone would use lvm or raid in a "cloud" 
environment, so they're not entirely wasted space there.

  --
  [1] 
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.wily/view/head:/cloud-image
  [2] http://irclogs.ubuntu.com/2015/08/06/%23ubuntu-devel.html#t22:53

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1491102/+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 1491055] Re: package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2015-09-01 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in util-linux package in Ubuntu:
  New

Bug description:
  das sistem leuft nürnoch total rukelich

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: uuid-runtime 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Tue Sep  1 19:04:11 2015
  DuplicateSignature: package:uuid-runtime:2.25.2-4ubuntu3:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-09-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1491055/+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 1489076] Re: clicking on active call banner and indicators with mouse

2015-09-01 Thread kevin gunn

** Description changed:

+ possibly related to bug 1473571 &  bug 1473566
+ 
  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens
  
  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ? or should indicators be kept to
  a non-green area when a monitor is connected? could get tricky quick

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

Title:
  clicking on active call banner and indicators with mouse

Status in canonical-pocket-desktop:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  possibly related to bug 1473571 &  bug 1473566

  on windowed mode vivid+o + silo0
  when in an active call, set dialer app to the background to activate the 
green banner (active call banner)
  using BT connected mouse click on the banner or the indicators and nothing 
happens

  there is also a design question of what is to happen in this case with
  the indicators? should a click reveal ? or should indicators be kept
  to a non-green area when a monitor is connected? could get tricky
  quick

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1489076/+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 1319278] Re: aulastlog doesn't report logins

** Branch linked: lp:~tyhicks/lightdm/auditing

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

Title:
  aulastlog doesn't report logins

Status in audit package in Ubuntu:
  New

Bug description:
  aulastlog and aulast don't appear to be functioning correctly:

  root@hunt:~# aulast
  root@hunt:~# aulastlog
  Username Port From   Latest
  root **Never logged in**
  daemon   **Never logged in**
  bin  **Never logged in**
  sys  **Never logged in**
  sync **Never logged in**
  games**Never logged in**
  man  **Never logged in**
  lp   **Never logged in**
  mail **Never logged in**
  news **Never logged in**
  uucp **Never logged in**
  proxy**Never logged in**
  www-data **Never logged in**
  backup   **Never logged in**
  list **Never logged in**
  irc  **Never logged in**
  gnats**Never logged in**
  nobody   **Never logged in**
  libuuid  **Never logged in**
  syslog   **Never logged in**
  messagebus   **Never logged in**
  colord   **Never logged in**
  lightdm  **Never logged in**
  whoopsie **Never logged in**
  avahi-autoipd**Never logged in**
  avahi**Never logged in**
  usbmux   **Never logged in**
  kernoops **Never logged in**
  pulse**Never logged in**
  rtkit**Never logged in**
  speech-dispatcher **Never logged in**
  hplip**Never logged in**
  saned**Never logged in**
  sarnold  **Never logged in**
  sshd **Never logged in**
  libvirt-qemu **Never logged in**
  libvirt-dnsmasq  **Never logged in**
  sbuild   **Never logged in**
  lxc-dnsmasq  **Never logged in**
  dictd**Never logged in**
  statd**Never logged in**
  dnsmasq  **Never logged in**
  ntp  **Never logged in**
  pdns **Never logged in**
  clickpkg **Never logged in**
  usermetrics  **Never logged in**
  root@hunt:~# 

  I would expect at least my user account sarnold should have logged in
  -- it was how I got to sudo, after all.

  There's no shortage of logging information, it just appears the logs
  for USER_LOGIN are missing:

  root@hunt:~# ausearch -l | wc -l
  262312
  root@hunt:~# ausearch -l | grep USER_LOGIN | wc -l
  0
  root@hunt:~#

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: auditd 1:2.3.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue May 13 23:48:21 2014
  InstallationDate: Installed on 2012-10-18 (573 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=rxvt-unicode
   PATH=(custom, no user)

[Touch-packages] [Bug 1478087] Re: ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

** Branch linked: lp:~tyhicks/lightdm/auditing

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

Title:
  ISST-LTE: aureport -l couldn't print out login info on ubuntu 14.04.3

Status in audit package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New

Bug description:
  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried 
to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out 
the login 
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 
lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 
auid=0 old-ses=4294967295 ses=8 res=1

  
  root@lakelp1:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1478087/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

Steve Langasek [2015-09-01 21:38 -]:
> The *only* thing that's made a no-op is the invocation of the init
> script *by the rc?.d symlink*.  This is something that should never
> happen anyway; our dependency-based boot is already supposed to bypass
> invoking this script in favor of the upstart job.  Any system that has
> been configured to not use the dependency-based boot in trusty is going
> to have race conditions at boot because of the combination of upstart
> job and init script

I suppose you are talking about insserv here. Note that trusty did
*not* use that yet, it was enabled in utopic
(https://launchpad.net/ubuntu/+source/sysvinit/2.88dsf-41ubuntu13) and
it took a lot of fine-tuning and fixing to mop up the fallout.

Thus in trusty you don't have the option to use dependency-based
sysvinit scripts, you *have* to have rc?.d symlinks; and they are
being used through upstart too via /etc/init/rc.conf.

So this change does influence the boot significantly, and I'm
not yet convinced that it necessarily regression proof? Or am I still
missing something?

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

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

Status in lsb package in Ubuntu:
  Fix Released
Status in mysql-5.5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  In Progress
Status in mysql-5.5 source package in Trusty:
  Invalid
Status in upstart source package in Trusty:
  Won't Fix
Status in lsb source package in Utopic:
  Fix Released
Status in mysql-5.5 source package in Utopic:
  Invalid
Status in upstart source package in Utopic:
  Fix Released
Status in upstart package in Debian:
  New

Bug description:
  [ impact ]

  Previously, init.d scripts that were replaced by upstart jobs had
  "upstart-job" symlink as a redirect in-place, which directed users at
  using upstart commands. Despite the good intentions, that never
  actually taught people about the correct interfaces. Now with the
  advent of co-installability of multiple init systems, users may have
  systemd, upstart, and sysv-init all installed on users system and have
  init.d scripts / upstart jobs / systemd units all available. To avoid
  any doubt, we should support executing /etc/init.d/ scripts which may
  call into upstart, or into systemd, or actually execute the script in
  question depending on whether there is native configuration for that
  particular job and which init system we are running under.

  [ test case ]

  Invoking init.d script should invoke upstart commands, for example:

  $ /etc/init.d/ssh status
  ssh start/running, process 4620
  $ /etc/init.d/ssh stop
  stop: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")
  $ sudo /etc/init.d/ssh stop
  ssh stop/waiting
  $ sudo /etc/init.d/ssh start
  ssh start/running, process 5373
  $ sudo /etc/init.d/ssh restart
  ssh stop/waiting
  ssh start/running, process 5405

  Description:Ubuntu 13.10
  Release:13.10

  mysql-server-5.5:
    Installed: 5.5.35-0ubuntu0.13.10.1
    Candidate: 5.5.35-0ubuntu0.13.10.1
    Version table:
   *** 5.5.35-0ubuntu0.13.10.1 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ 
saucy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.32-0ubuntu7 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 
Packages

  In Ubuntu 13.10, the Upstart job and the init.d script do not work
  properly.  In previous versions, the init.d script was a symlink to
  the wrapper script around upstart (/lib/init/upstart-job).  This
  conflict means that if the server was started using the init.d script,
  upstart does not recognize that the server is running and will attempt
  to start a second instance of mysqld.

  Also problematic is that if the upstart job is started using the
  service or start commands, the init.d script's "stop" function runs a
  mysql shutdown, but upstart simply restarts mysqld (because it's
  marked respawn in the upstart config).

  Description: Ubuntu 14.04
  Release: 14.04
  mysql:   mysql-server-5.5.43-0ubuntu0.14.04.1
  The problem in some setup was that the upgrade von 12.04 to 14.04 requres the 
adjustment of the InnoDB log size. Therefore the start of MySQL via upstart 
failed directly while the one via init started successfully and then failed as 
below.
  r...@webserver01.kurt..ref:~# status mysql
  mysql start/running, process 5866
  r...@webserver01.kurt..ref:~#

Re: [Touch-packages] [Bug 1491162] Re: FTBFS in Wily

2015-09-01 Thread Barry Warsaw

On Sep 01, 2015, at 10:57 PM, Colin Watson wrote:

>I thought (from https://github.com/pytest-dev/pytest/issues/744) that
>you were planning to fix this by backporting the pytest fix instead?

I think I forgot to do that.  I'll look at that tomorrow and back out the six
change if it works out.  I was hoping upstream would have landed and released
the fix by now.

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

Title:
  FTBFS in Wily

Status in six package in Ubuntu:
  New

Bug description:
  Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast
  module API change (ast API is not guaranteed to be stable across
  Python releases).  This causes six to FTBFS in Wily, where we've
  enabled Python 3.5 as a supported version.

  https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1491162/+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 1485787] Re: package_hook does not include package version

Setting up apport (2.17.2-0ubuntu1.4) ...
bdmurray@blacklightning:~$ echo "You have failed this city." | 
/usr/share/apport/package_hook -p apport
bdmurray@blacklightning:~$ grep "^Package" /var/crash/apport.1000.crash
Package: apport 2.17.2-0ubuntu1.4


** Tags added: verification-done-vivid

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

Title:
  package_hook does not include package version

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Vivid:
  Fix Committed

Bug description:
  All of these problem reports are missing a package version:

  https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738

  This is because package_hook in apport only writes the following:

  pr['Package'] = options.package

  We should include the package version in the problem report.

  Test Case
  -
  1) echo "You have failed this city." | /usr/share/apport/package_hook -p 
apport
  2) grep "^Package" /var/crash/apport.1000.crash

  With the current version of apport you'll only see the package name,
  with the version from -proposed you'll see the package version in
  addition to the name.

  Regression Potential
  
  Worst case scenario I screwed the patch up and we loose the package name too, 
but given that it works in wily and there is a test for it in test_hooks.py 
that seems unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1485787/+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 1381050] Re: "Import Key File" fails when the path of the file has special characters

Here is the Traceback I see

ipdb> n
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.UnicodeEncodeError: 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 707, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py",
 line 288, in AddKey
return self.add_key(path)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
804, in add_key
path = path.encode("utf-8")
  File "/usr/lib/python3.4/genericpath.py", line 19, in exists
os.stat(path)
UnicodeEncodeError: 'ascii' codec can't encode character '\xed' in position 58: 
ordinal not in range(128)

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1491192] [NEW] Mouse Flickering When 3rd USB Monitor is Enabled - 15.04 Unity

2015-09-01 Thread AE Grey

Public bug reported:

Action Causing Bug:
Installed a 3rd monitor via a DisplayLink USB Adapter
Enabled the 3rd monitor via system settings

Bug Description:
Mouse Pointer flickers and disappears - on Monitor on HDMI AND built in display 
on laptop.
Mouse Pointer does not flicker on 3rd DisplayLink monitor.

Unplugging the 3rd monitor eliminated the flickering.

System:
Ubuntu 15.04 Unity
ASUS Laptop
Intel® Ivybridge Mobile Graphics
Intel® Core™ i7-3632QM CPU @ 2.20GHz × 8
16GB RAM

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.3
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 Sep  1 20:31:30 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1467]
InstallationDate: Installed on 2015-05-05 (119 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK COMPUTER INC. Q400A
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed 
root=UUID=8b626700-3635-4660-b5ee-1aa96e15f49f ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q400A.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q400A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ400A.208:bd09/06/2012:svnASUSTeKCOMPUTERINC.:pnQ400A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ400A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: Q400A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Sep  1 12:18:35 2015
xserver.configfile: default
xserver.errors:
 modeset(G0): glamor initialization failed
 modeset(G1): glamor initialization failed
 modeset(G2): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3

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


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

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

Title:
  Mouse Flickering When 3rd USB Monitor is Enabled - 15.04 Unity

Status in xorg package in Ubuntu:
  New

Bug description:
  Action Causing Bug:
  Installed a 3rd monitor via a DisplayLink USB Adapter
  Enabled the 3rd monitor via system settings

  Bug Description:
  Mouse Pointer flickers and disappears - on Monitor on HDMI AND built in 
display on laptop.
  Mouse Pointer does not flicker on 3rd DisplayLink monitor.

  Unplugging the 3rd monitor eliminated the flickering.

  System:
  Ubuntu 15.04 Unity
  ASUS Laptop
  Intel® Ivybridge Mobile Graphics
  Intel® Core™ i7-3632QM CPU @ 2.20GHz × 8
  16GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  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 Sep  1 20:31:30 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen

[Touch-packages] [Bug 1483637] Re: ufw init doesn't start in vivid kernel

2015-09-01 Thread Cindy Quach

Ah, it looks like it's because my /etc/ufw/after.rules reference the
ULOG kernel module so it kept erroring out. If ULOG is deprecated I have
no idea it's in my rules. Sorry for the noise~

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

Title:
  ufw init doesn't start in vivid kernel

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  I just switched to the vivid kernel and it seems that because this
  kernel config: CONFIG_IP_NF_TARGET_ULOG is missing ufw service doesn't
  get started. Is there a workaround for this? We don't compile our own
  kernels so removing that re-enabling that config sadly won't be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1483637/+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 1426307] location is inaccurate

2015-09-01 Thread costales

Hi Lucio :)
Did you try it in Portugal and it worked fine and it is not working in 
Germany?
Could you try the app Sensor Status and give me the feedback? It will tell 
you about the accuracy.
I think there is not more information available abaout satellites :(
Best regards

-- 
Sent using Dekko from my Ubuntu device

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

Title:
  location is inaccurate

Status in Canonical System Image:
  Fix Released
Status in location-service package in Ubuntu:
  Fix Released
Status in location-service source package in Vivid:
  Confirmed
Status in location-service package in Ubuntu RTM:
  Fix Released

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Location is inaccurate, it thinks that I'm several kilometres away
  from my actual location, in the middle of the sea.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Fri Feb 27 11:10:42 2015
  InstallationDate: Installed on 2015-02-25 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1490750] Re: ad blocks web-browser

2015-09-01 Thread Drwd

The browser must have a option to disable java scripts.

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

Title:
  ad blocks web-browser

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Bq aquaris 4.5 15.04 r24

  Some types of ads can block the web-browser because you just have the option 
to click in the add pop-up
  Its very annoying since if you restart the web-browser it charges again the 
add. The only why to avoid it is after restart web-browser be faster than the 
app to close the window before it'll be charged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490750/+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 1491125] [NEW] [Arale r4] Can't login with facebook in "flipboard"

2015-09-01 Thread Marco Graziotti

Public bug reported:

* I'm using *

> Arale r4, on Meizu MX4 Ubuntu Edition
> webbrowser-app 0.23+15.04.20150817-0ubuntu1 (checked via terminal, because in
> Software Center the version is not showed)

* Problem *

When you try to sign in with facebook in "Flipboard" it's impossible to fill
the textbox with your facebook email and password, the textbox it isn't
cliccable.
I don't know if the same things happen with another website that permits to
login with facebook.

I attach the screenshot in this message.
Tell me if you need more information.

Thank you.

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

** Attachment added: "screenshot login with facebook"

https://bugs.launchpad.net/bugs/1491125/+attachment/4455830/+files/screenshot20150901_220051092.png

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

Title:
[Arale r4] Can't login with facebook in "flipboard"

Status in webbrowser-app package in Ubuntu:
New

Bug description:
* I'm using *

> Arale r4, on Meizu MX4 Ubuntu Edition
> webbrowser-app 0.23+15.04.20150817-0ubuntu1 (checked via terminal, because
in Software Center the version is not showed)

* Problem *

I attach the screenshot in this message.
Tell me if you need more information.

Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1491125/+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 1491128] [NEW] Doesn't allow to file a bug for mtr

2015-09-01 Thread Uqbar

Public bug reported:

When I install mtr I get this error:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mtr : Depends: libncurses5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed
   Depends: libtinfo5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

So I tried to file a bug against mtr. But I got an error from apport:

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third party
package and try again.

Which is trivially wrong:

Package: mtr
Version: 0.86-1
Architecture: amd64
Maintainer: Robert Woodcock 
Installed-Size: 149
Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.15), libcairo2 (>= 1.2.4), 
libfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.8.0), libncurses5 (>= 6), 
libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 
(>= 1.14.0), libtinfo5 (>= 6)
Conflicts: mtr-tiny, suidmanager (<< 0.50)
Replaces: mtr-tiny
Homepage: http://www.bitwizard.nl/mtr/
Priority: extra
Section: net
Filename: pool/main/m/mtr/mtr_0.86-1_amd64.deb
Size: 62426
SHA256: 07ad41c5d5d7ad9ba730deb0ccf874b5d22f0e28c44924e97766b92f5453d014
SHA1: 5fa44030a9b6e8b34d1686bafbd99e8d329ecf94
MD5sum: dbd68cb9e9a0de7b5dd36fe0f6c69143
Description-en: Full screen ncurses and X11 traceroute tool
 mtr combines the functionality of the 'traceroute' and 'ping' programs
 in a single network diagnostic tool.
 .
 As mtr starts, it investigates the network connection between the host
 mtr runs on and a user-specified destination host.  After it
 determines the address of each network hop between the machines,
 it sends a sequence ICMP ECHO requests to each one to determine the
 quality of the link to each machine.  As it does this, it prints
 running statistics about each machine.
Description-md5: b8c484682736394f444f476dd46943f5

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.12
Uname: Linux 4.1.0-pf3+ x86_64
ApportLog:
 
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
CrashReports: 644:0:116:5216:2015-08-28 07:53:12.331027955 +0200:2015-08-28 
07:53:12.331027955 +0200:/var/crash/fglrx-core.0.crash
CurrentDesktop: KDE
Date: Tue Sep  1 22:19:31 2015
InstallationDate: Installed on 2015-05-16 (108 days ago)
InstallationMedia: Kubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150219.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages trusty

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

Title:
  Doesn't allow to file a bug for mtr

Status in apport package in Ubuntu:
  New

Bug description:
  When I install mtr I get this error:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   mtr : Depends: libncurses5 (>= 6) but 5.9+20140118-1ubuntu1 is to be 
installed
 Depends: libtinfo5 (>= 6) but 5.9+20140118-1ubuntu1 is to be installed
  E: Unable to correct problems, you have held broken packages.
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  So I tried to file a bug against mtr. But I got an error from apport:

  The problem cannot be reported:

  This is not an official Ubuntu package. Please remove any third party
  package and try again.

  Which is trivially wrong:

  Package: mtr
  Version: 0.86-1
  Architecture: amd64
  Maintainer: Robert Woodcock 
  Installed-Size: 149
  Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.15), libcairo2 (>= 1.2.4), 
libfontconfig1 (>= 2.11), libfreetype6 (>= 2.2.1), libgdk-pixbuf2.0-0 (>= 
2.22.0), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.8.0),

[Touch-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

2015-09-01 Thread TJ

Also happening in 15.10 Wily, with lightdm 1.15.3-0ubuntu3

Repeated 3 times per second constantly for about 15 minutes and then
system froze - not sure if this was the cause of the freeze but it was
the only logged info immediately before the freeze.

Sep  1 19:23:43 hephaestion lightdm[951]: /etc/modprobe.d is not a file
Sep  1 19:23:43 hephaestion lightdm[951]: message repeated 3 times: [ 
/etc/modprobe.d is not a file]
Sep  1 19:23:43 hephaestion lightdm[951]: update-alternatives: error: no 
alternatives for x86_64-linux-gnu_gfxcore_conf
...
Sep  1 19:35:39 hephaestion lightdm[951]: /etc/modprobe.d is not a file
Sep  1 19:35:39 hephaestion lightdm[951]: message repeated 3 times: [ 
/etc/modprobe.d is not a file]
Sep  1 19:35:39 hephaestion lightdm[951]: update-alternatives: error: no 
alternatives for x86_64-linux-gnu_gfxcore_conf

It also occurs for gpu-manager so this may be caused by systemd-init

Sep 01 19:48:49 hephaestion.lan.iam.tj gpu-manager[784]: /etc/modprobe.d is not 
a file
Sep 01 19:48:49 hephaestion.lan.iam.tj gpu-manager[784]: /etc/modprobe.d is not 
a file
Sep 01 19:48:49 hephaestion.lan.iam.tj gpu-manager[784]: /etc/modprobe.d is not 
a file
Sep 01 19:48:49 hephaestion.lan.iam.tj gpu-manager[784]: /etc/modprobe.d is not 
a file
...
Sep 01 19:48:51 hephaestion.lan.iam.tj gpu-manager[989]: /etc/modprobe.d is not 
a file
Sep 01 19:48:51 hephaestion.lan.iam.tj gpu-manager[989]: /etc/modprobe.d is not 
a file
Sep 01 19:48:51 hephaestion.lan.iam.tj gpu-manager[989]: /etc/modprobe.d is not 
a file
Sep 01 19:48:51 hephaestion.lan.iam.tj gpu-manager[989]: /etc/modprobe.d is not 
a file
Sep 01 19:48:51 hephaestion.lan.iam.tj gpu-manager[989]: update-alternatives: 
error: no alternatives for x86_64-linux-gnu_gfxcore_conf

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Triaged

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

Title:
  /etc/modprobe.d is not a file

Status in lightdm package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  /var/log/upstart# cat lightdm.log
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  Above looks weird... modprobe.d is a directory & why update-
  alternatives are called?!

  This is lightdm 1.10.5-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452610/+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 1455139] Re: package libgpg-error0:i386 1.12-0.2ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

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

** Changed in: libgpg-error (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libgpg-error0:i386 1.12-0.2ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in libgpg-error package in Ubuntu:
  Confirmed

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgpg-error0:i386 1.12-0.2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Thu May 14 21:28:34 2015
  Dependencies:
   gcc-4.9-base 4.9.1-0ubuntu1
   libc6 2.19-0ubuntu6.6
   libgcc1 1:4.9.1-0ubuntu1
   multiarch-support 2.19-0ubuntu6.6
  DuplicateSignature: package:libgpg-error0:i386:1.12-0.2ubuntu1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-03-29 (45 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: i386
  SourcePackage: libgpg-error
  Title: package libgpg-error0:i386 1.12-0.2ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgpg-error/+bug/1455139/+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 1491162] Re: FTBFS in Wily

2015-09-01 Thread Barry Warsaw

See also https://launchpadlibrarian.net/211356903/buildlog_ubuntu-wily-
amd64.six_1.9.0-3_BUILDING.txt.gz

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

Title:
  FTBFS in Wily

Status in six package in Ubuntu:
  New

Bug description:
  Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast
  module API change (ast API is not guaranteed to be stable across
  Python releases).  This causes six to FTBFS in Wily, where we've
  enabled Python 3.5 as a supported version.

  https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1491162/+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 1491162] [NEW] FTBFS in Wily

2015-09-01 Thread Barry Warsaw

Public bug reported:

Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast module
API change (ast API is not guaranteed to be stable across Python
releases).  This causes six to FTBFS in Wily, where we've enabled Python
3.5 as a supported version.

https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

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

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

Title:
  FTBFS in Wily

Status in six package in Ubuntu:
  New

Bug description:
  Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast
  module API change (ast API is not guaranteed to be stable across
  Python releases).  This causes six to FTBFS in Wily, where we've
  enabled Python 3.5 as a supported version.

  https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1491162/+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 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

2015-09-01 Thread tikend

No error after

sudo apt-get install --reinstall lxc

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

Title:
  package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  Error during do-releas-update -d from 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 29 10:13:04 2015
  DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  InstallationDate: Installed on 2015-08-13 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: lxc
  Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+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 1491162] Re: FTBFS in Wily

2015-09-01 Thread Colin Watson

I thought (from https://github.com/pytest-dev/pytest/issues/744) that
you were planning to fix this by backporting the pytest fix instead?

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

Title:
  FTBFS in Wily

Status in six package in Ubuntu:
  New

Bug description:
  Upstream six 1.9.0 is incompatible with Python 3.5 due to an ast
  module API change (ast API is not guaranteed to be stable across
  Python releases).  This causes six to FTBFS in Wily, where we've
  enabled Python 3.5 as a supported version.

  https://bitbucket.org/gutworth/six/issues/131/python-35-test-failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/six/+bug/1491162/+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 1381050] Re: "Import Key File" fails when the path of the file has special characters

I've followed the test case provided for Wily and the bug does not seem
fixed there either, so I am going to set the task back to In Progress
and look at Bruno Nova's change that was missed.

** Changed in: software-properties (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: software-properties (Ubuntu)
 Assignee: Michael Vogt (mvo) => Brian Murray (brian-murray)

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

Title:
  "Import Key File" fails when the path of the file has special
  characters

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Importing a key that is in a path that contains special characters
  (like "/home/$USER/Transferências") fails silently.

  [Test Case]

  1. Download a PGP key for a Debian repository (for example, the VideoLAN
 team's key: download.videolan.org/pub/debian/videolan-apt.asc)
  2. Move the key file to a folder that contains special characters, or rename
 the file to contain them (example: VídeoLAN.asc).
  3. Open "Software & Updates" from the Dash, then select the Authentication
 tab.
  4. Press the "Import Key File..." button and then choose the key file.
 Admin authentication should then be requested, so authenticate yourself.

 If the bug is fixed: the key should now appear in the list of keys.
 If not: the key was not added.

  [Regression Potential]

  If the fix is not correct, I suppose it could potentially break the
  "import key" feature even more, so it wouldn't work even in "normal"
  paths.

  [Original Report]

  The "Import Key File..." button in the "Authentication" tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the "/home/$USER/Downloads" folder is 
named "/home/$USER/Transferências" here.
  Adding a key from that folder fails, but adding a key from "/home/$USER" (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
    _("Error importing selected file"),
    _("The selected file may not be a GPG key file "
  "or it might be corrupt."))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error("Authentication canceled, changes have not 
been saved")

  "self.backend.AddKey(chooser.get_filename())" throws a 
"org.freedesktop.DBus.Python.UnicodeEncodeError" exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

2015-09-01 Thread Steve Langasek

> I think this should be the responsibility of existing packages to make
they are doing the correct thing.

That is not sufficient for an SRU.  Your SRU needs to be compatible with
the existing packages in the archive /as they are/, not as you declare
they should be.

However, per my previous comment, I don't think this is actually a
problem.

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

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

Status in lsb package in Ubuntu:
  Fix Released
Status in mysql-5.5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  In Progress
Status in mysql-5.5 source package in Trusty:
  Invalid
Status in upstart source package in Trusty:
  Won't Fix
Status in lsb source package in Utopic:
  Fix Released
Status in mysql-5.5 source package in Utopic:
  Invalid
Status in upstart source package in Utopic:
  Fix Released
Status in upstart package in Debian:
  New

Bug description:
  [ impact ]

  Previously, init.d scripts that were replaced by upstart jobs had
  "upstart-job" symlink as a redirect in-place, which directed users at
  using upstart commands. Despite the good intentions, that never
  actually taught people about the correct interfaces. Now with the
  advent of co-installability of multiple init systems, users may have
  systemd, upstart, and sysv-init all installed on users system and have
  init.d scripts / upstart jobs / systemd units all available. To avoid
  any doubt, we should support executing /etc/init.d/ scripts which may
  call into upstart, or into systemd, or actually execute the script in
  question depending on whether there is native configuration for that
  particular job and which init system we are running under.

  [ test case ]

  Invoking init.d script should invoke upstart commands, for example:

  $ /etc/init.d/ssh status
  ssh start/running, process 4620
  $ /etc/init.d/ssh stop
  stop: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")
  $ sudo /etc/init.d/ssh stop
  ssh stop/waiting
  $ sudo /etc/init.d/ssh start
  ssh start/running, process 5373
  $ sudo /etc/init.d/ssh restart
  ssh stop/waiting
  ssh start/running, process 5405

  Description:Ubuntu 13.10
  Release:13.10

  mysql-server-5.5:
    Installed: 5.5.35-0ubuntu0.13.10.1
    Candidate: 5.5.35-0ubuntu0.13.10.1
    Version table:
   *** 5.5.35-0ubuntu0.13.10.1 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ 
saucy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.32-0ubuntu7 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 
Packages

  In Ubuntu 13.10, the Upstart job and the init.d script do not work
  properly.  In previous versions, the init.d script was a symlink to
  the wrapper script around upstart (/lib/init/upstart-job).  This
  conflict means that if the server was started using the init.d script,
  upstart does not recognize that the server is running and will attempt
  to start a second instance of mysqld.

  Also problematic is that if the upstart job is started using the
  service or start commands, the init.d script's "stop" function runs a
  mysql shutdown, but upstart simply restarts mysqld (because it's
  marked respawn in the upstart config).

  Description: Ubuntu 14.04
  Release: 14.04
  mysql:   mysql-server-5.5.43-0ubuntu0.14.04.1
  The problem in some setup was that the upgrade von 12.04 to 14.04 requres the 
adjustment of the InnoDB log size. Therefore the start of MySQL via upstart 
failed directly while the one via init started successfully and then failed as 
below.
  r...@webserver01.kurt..ref:~# status mysql
  mysql start/running, process 5866
  r...@webserver01.kurt..ref:~# /etc/init.d/mysql stop
  * Stopping MySQL database server mysqld [ OK ]
  r...@webserver01.kurt..ref:~# status mysql
  mysql start/running, process 6101
  r...@webserver01.kurt..ref:~# /etc/init.d/mysql status
  * /usr/bin/mysqladmin Ver 8.42 Distrib 5.5.43, for debian-linux-gnu on x86_64
  Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
  Oracle is a registered trademark of Oracle Corporation and/or its
  affiliates. Other names may be trademarks of their respective
  owners.
  Server version5.5.43-0ubuntu0.14.04.1-log
  Protocol version  10
  ConnectionLocalhost via UNIX socket
  UNIX socket   /var/run/mysqld/mysqld.sock
  Uptime:   7 sec
  Threads: 1 Questions: 108 Slow queries: 0

[Touch-packages] [Bug 911622] Re: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefund

2015-09-01 Thread Derek Poon

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

** This bug has been marked a duplicate of bug 619003
   GdkPixbuf-WARNING **: Cannot open pixbuf loader module file 
'/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

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

Title:
  [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file
  '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei
  oder Verzeichnis nicht gefunden (file not found)

Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  after the latest dist-upgrade on 12.04 there are a lot of these
  messages (Datei oder Verzeichnis not found == file not found)

  GdkPixbuf-WARNING **: Cannot open pixbuf loader module file
  '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei
  oder Verzeichnis nicht gefunden

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgdk-pixbuf2.0-0 2.25.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
  Uname: Linux 3.2.0-7-generic i686
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  Date: Wed Jan  4 07:30:55 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf
  UpgradeStatus: Upgraded to precise on 2011-12-04 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/911622/+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 1491147] [NEW] libapparmor-dev missing manpages for query and policy cache APIs

2015-09-01 Thread Steve Beattie

Public bug reported:

libapparmor is missing the following manpages from upstream:

  aa_query_label.2
  aa_features.3
  aa_kernel_interface.3
  aa_policy_cache.3
  aa_splitcon.3

** Affects: apparmor (Ubuntu)
 Importance: Medium
 Assignee: Steve Beattie (sbeattie)
 Status: In Progress

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

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  libapparmor-dev missing manpages for query and policy cache APIs

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  libapparmor is missing the following manpages from upstream:

aa_query_label.2
aa_features.3
aa_kernel_interface.3
aa_policy_cache.3
aa_splitcon.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1491147/+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 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

2015-09-01 Thread Steve Langasek

I think the change description within the patch is wrong (or at least, 
misleading/incomplete).  What this patch actually does is:
 - for anything that calls /etc/init.d/foo, if /etc/init/foo.conf exists, make 
the call a passthrough to upstart instead of calling the init script.
 - for anything that calls /etc/rc?.d/[KS]??foo, make it a no-op.

The *only* thing that's made a no-op is the invocation of the init
script *by the rc?.d symlink*.  This is something that should never
happen anyway; our dependency-based boot is already supposed to bypass
invoking this script in favor of the upstart job.  Any system that has
been configured to not use the dependency-based boot in trusty is going
to have race conditions at boot because of the combination of upstart
job and init script, and while making this change may change the
characteristics of the behavior at boot it would not be a regression
because things are already broken.

If anything interfaces with the /etc/init.d/foo script, that will still
function, except that now it will *work* by passing through to the
upstart job instead of trying to manipulate processes via (possibly non-
existent) pid files etc

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

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

Status in lsb package in Ubuntu:
  Fix Released
Status in mysql-5.5 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in lsb source package in Trusty:
  In Progress
Status in mysql-5.5 source package in Trusty:
  Invalid
Status in upstart source package in Trusty:
  Won't Fix
Status in lsb source package in Utopic:
  Fix Released
Status in mysql-5.5 source package in Utopic:
  Invalid
Status in upstart source package in Utopic:
  Fix Released
Status in upstart package in Debian:
  New

Bug description:
  [ impact ]

  Previously, init.d scripts that were replaced by upstart jobs had
  "upstart-job" symlink as a redirect in-place, which directed users at
  using upstart commands. Despite the good intentions, that never
  actually taught people about the correct interfaces. Now with the
  advent of co-installability of multiple init systems, users may have
  systemd, upstart, and sysv-init all installed on users system and have
  init.d scripts / upstart jobs / systemd units all available. To avoid
  any doubt, we should support executing /etc/init.d/ scripts which may
  call into upstart, or into systemd, or actually execute the script in
  question depending on whether there is native configuration for that
  particular job and which init system we are running under.

  [ test case ]

  Invoking init.d script should invoke upstart commands, for example:

  $ /etc/init.d/ssh status
  ssh start/running, process 4620
  $ /etc/init.d/ssh stop
  stop: Rejected send message, 1 matched rules; type="method_call", 
sender=":1.2469694" (uid=1000 pid=3908 comm="stop ssh ") 
interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" 
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 
comm="/sbin/init")
  $ sudo /etc/init.d/ssh stop
  ssh stop/waiting
  $ sudo /etc/init.d/ssh start
  ssh start/running, process 5373
  $ sudo /etc/init.d/ssh restart
  ssh stop/waiting
  ssh start/running, process 5405

  Description:Ubuntu 13.10
  Release:13.10

  mysql-server-5.5:
    Installed: 5.5.35-0ubuntu0.13.10.1
    Candidate: 5.5.35-0ubuntu0.13.10.1
    Version table:
   *** 5.5.35-0ubuntu0.13.10.1 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ 
saucy-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.32-0ubuntu7 0
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 
Packages

  In Ubuntu 13.10, the Upstart job and the init.d script do not work
  properly.  In previous versions, the init.d script was a symlink to
  the wrapper script around upstart (/lib/init/upstart-job).  This
  conflict means that if the server was started using the init.d script,
  upstart does not recognize that the server is running and will attempt
  to start a second instance of mysqld.

  Also problematic is that if the upstart job is started using the
  service or start commands, the init.d script's "stop" function runs a
  mysql shutdown, but upstart simply restarts mysqld (because it's
  marked respawn in the upstart config).

  Description: Ubuntu 14.04
  Release: 14.04
  mysql:   mysql-server-5.5.43-0ubuntu0.14.04.1
  The problem in some setup was that the upgrade von 12.04 to 14.04 requres the 
adjustment of the InnoDB log size. Therefore the start of MySQL via upstart 
failed directly while the one via init started successfully and then failed as 
below.

[Touch-packages] [Bug 1466510] Re: Stretched screen (briefly) after rotating

2015-09-01 Thread Daniel d'Andrada

** Changed in: qtmir (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: qtmir
   Status: Confirmed => Fix Released

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

** Changed in: mir
   Status: New => Invalid

** Changed in: qtubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Stretched screen (briefly) after rotating

Status in Mir:
  Invalid
Status in QtMir:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Fix Released
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Test on image with shell rotation enabled.

  Steps to repro:
  1. open app, e.g. system settings.
  2. rotate device to landscape, see app adjust to suit.
  3. lock phone.
  4. rotate device to portrait. 
  5. unlock phone. 

  Bug: You see flash of stretched app, before it redraws to look
  correct.

  Think we need to resize/reorient the app sooner.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1466510/+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 1486456] Re: Please set back libvpx1 into Wily archive

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

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

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

Title:
  Please set back libvpx1 into Wily archive

Status in libvpx package in Ubuntu:
  Confirmed

Bug description:
  Wanting to install virtualbox 5.0 from  virtualbox.org, as the wily
  archive one (5.02-dfsg-2) has a vboxpci iommu issue.

  but i require libvpx1 to install (and no more available into Wily archive)
  https://launchpad.net/ubuntu/+source/libvpx

  virtualbox-5.0:
   Depends: libvpx1 (>=1.0.0) but it is not installable

  Error with the Wily package:
  dmesg | grep -i iommu
  [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-4-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro intel_iommu=on
  [0.00] DMAR: IOMMU enabled
  [   32.662814] vboxpci: IOMMU not found (not registered)

  (this is a test with intel_iommu=on kernel parameter, but without i
  get the same result. So i need the version from virtualbox.org)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+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 1337262] Re: kmod should permit use of compressed modules

** Changed in: kmod (Ubuntu)
Milestone: ubuntu-15.08 => ubuntu-15.09

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

Title:
  kmod should permit use of compressed modules

Status in kmod package in Ubuntu:
  Triaged

Bug description:
  kmod should permit use of compressed modules. This enables images that
  boot from RAM to be much smaller. In essence this requires only
  changing a build option. Uncompressed modules are still supported.

  A patch is here:
  https://github.com/abligh/kmod/commit/31795c8078ba9ccb6f064d11d0c9e640f8e0fab1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1337262/+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 1450009] Re: suspends on closed lid, does not recognized external monitors/dock

Thanks Andreas, well spotted! This is the same issue as for the original
reporter, inode77, and Kevin:

Mai 04 08:47:33 damm-xyz1 kernel: input: HP WMI hotkeys as 
/devices/virtual/input/input17
[...]
Mai 04 08:47:37 damm-xyz1 systemd-logind[853]: Watching system buttons on 
/dev/input/event2 (Power Button)
Mai 04 08:47:37 damm-xyz1 systemd-logind[853]: Watching system buttons on 
/dev/input/event4 (Video Bus)
Mai 04 08:47:37 damm-xyz1 systemd-logind[853]: Watching system buttons on 
/dev/input/event1 (Lid Switch)
Mai 04 08:47:37 damm-xyz1 systemd-logind[853]: Watching system buttons on 
/dev/input/event0 (Sleep Button)

Robin has:
Jul 14 10:06:33 rgarner-Latitude-E6420 kernel: input: Dell WMI hotkeys as 
/devices/virtual/input/input19

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

Title:
  [HP, Dell notebooks] suspends on closed lid, does not recognized
  external monitors/dock

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Using systemd as init system on a HP zbook15 notebook having 2 external 
monitors connected using a docking station and starting with lid closed the 
system goes to sleep after successfully booting and starting lightdm greeter. 
Sometimes there's enough time to enter username and password but system goes to 
sleep every time after a few seconds.
  The system can be woken up and used after this happens but it will not let me 
shutdown later.

  The problem is just present in docked situation starting with closed
  lid using systemd a init system.

  If notebook is used in non-docked situation with open lid and systemd
  the problem does not occur.

  Workaround: A switch back to upstart as init system resolves the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 29 14:46:09 2015
  InstallationDate: Installed on 2015-04-27 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1466965] Re: update-initramfs runs more often than necessary

** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-15.08 => ubuntu-15.09

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

Title:
  update-initramfs runs more often than necessary

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  A discussion that has come up before,  but I figured I'd file a bug.

  When you 'apt-get install ' often times:
   a.) update-initramfs is called more than once for the same kernel
   b.) update-initramfs might not even be called (such as in bug 1466960).

  some conversation with infinity in #ubuntu-devel [1] indicates that he
  and apw have discussed how to do solve this.

  [1] http://irclogs.ubuntu.com/2015/06/19/%23ubuntu-devel.html#t18:04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.103ubuntu15
  ProcVersionSignature: User Name 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 19 18:19:15 2015
  Ec2AMI: ami-0425
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1466965/+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 1423796] Re: Unable to mount lvmcache root device at boot time

** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.08 => ubuntu-15.09

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

Title:
  Unable to mount lvmcache root device at boot time

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm experimenting with Vivid Vervet on a virtual machine and tried a
  new LVM feature, lvmcache. I made a cache for the root file system,
  rebuilt the initrd and rebooted the VM.

  At boot time, the system failed to activate the root LV. After some
  investigation, I found out, it's because the initrd is missing some
  essential stuff needed for activating a cached LV.

  The initrd was missing the dm-cache module. I regenerated the initrd
  with explicitly listing dm-cache in /etc/initramfs-tools/modules, but
  the system still can't boot up, because now it is missing the
  /usr/sbin/cache_check utility.

  As SSDs are becoming more and more common, I think it will be common
  to use them as cache for root file systems, thus it is mandatory to
  make sure that an initrd can mount an lvmcached root device when
  necessary, preferably without /etc/initramfs-tools/modules and other
  manual initrd hacking.

  System details:

  Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  LVM version: 2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+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 1250109] Re: Please use dpkg-triggers