[Touch-packages] [Bug 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend

[Kevin Brubeck Unhammer]

I'm not sure if this is the same bug, but after upgrading to 15.04, I
have to "sudo systemctl restart NetworkManager" to get back my network
interfaces after a long suspend. If I test a short suspend/resume cycle,
like a couple seconds, it works fine, but when I open my laptop in the
morning I have to restart NetworkManager.

I attached a journalctl excerpt; I closed the lid last night at 20:29,
then opened it this morning at 08:09 and first tried the hardware
switch, then eventually restarted NetworkManager.

** Attachment added: "journalctl-networkmanager.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448555/+attachment/4392723/+files/journalctl-networkmanager.log

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

Title:
  network-manager does not autoconnect to wifi network after resume from
  suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 network manager does not reconnect to the
  wifi network after resuming from a suspend to memory.

  Workaround:
  disable and re-enable wireless network -> connects immediately

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 25 23:53:54 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-17 (708 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  IpRoute:
   default via 10.1.0.254 dev wlan0  proto static  metric 1024 
   10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/1  rsb_hs  
d8793959-2da1-4dc6-85ad-2dcf9e36e64b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:61:E9:5F  btdisconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend

[Kevin Brubeck Unhammer]

(And I'm on a Thinkpad X200, 3.13.0-39-generic, networkmanager
0.9.10.0-4ubuntu15.1)

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

Title:
  network-manager does not autoconnect to wifi network after resume from
  suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 network manager does not reconnect to the
  wifi network after resuming from a suspend to memory.

  Workaround:
  disable and re-enable wireless network -> connects immediately

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 25 23:53:54 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-17 (708 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  IpRoute:
   default via 10.1.0.254 dev wlan0  proto static  metric 1024 
   10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/1  rsb_hs  
d8793959-2da1-4dc6-85ad-2dcf9e36e64b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:61:E9:5F  btdisconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 1452584] [NEW] package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Carlos]

Public bug reported:

No se actualiza

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu4.1
Uname: Linux 4.0.1-040001-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Sun May  3 21:17:58 2015
DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el 
script post-installation devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2015-04-24 (12 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK COMPUTER INC. K55VD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic 
root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: systemd
Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VD.411
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VD
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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package package-from-proposed vivid

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

Title:
  package systemd 219-7ubuntu4.1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in systemd package in Ubuntu:
  New

Bug description:
  No se actualiza

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4.1
  Uname: Linux 4.0.1-040001-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sun May  3 21:17:58 2015
  DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el 
script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-04-24 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. K55VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic 
root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: systemd
  Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55VD.411
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55VD
  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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1447807] Re: systemctl enable shows error on enabling a SysV service

[Eric Heydrick]

After installing systemd 219-7ubuntu5 I can enable a SysV service
without any errors. Thanks!

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

Title:
  systemctl enable shows error on enabling a SysV service

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  SRU TEST CASE:
  --
  Trying to enable a SysV init service which does not have a corresponding 
systemd unit results in an error:

  # systemctl enable pulseaudio
  Synchronizing state for pulseaudio.service with sysvinit using update-rc.d...
  Executing /usr/sbin/update-rc.d pulseaudio defaults
  Executing /usr/sbin/update-rc.d pulseaudio enable
  Failed to execute operation: No such file or directory

  /etc/init.d/pulseaudio actually does get enabled (check
  /etc/rc*/*pulse*), but the command fails with code 1 and you get that
  error message. With the fix the command succeeds.

  SRU Regression potential
  
  Low, the modes for "sysv script + systemd unit" as well as "systemd unit 
only" already have automatic tests, and now this scenario ("sysv script only") 
has a test too. In the worst case this has the potential of completely breaking 
systemctl enable/disable, which can be worked around with changing symlinks 
manually, and isn't breaking the boot.

  
  Version details:

  Description:  Ubuntu 15.04
  Release:  15.04

  systemd:
    Installed: 219-7ubuntu3
    Candidate: 219-7ubuntu3
    Version table:
   *** 219-7ubuntu3 0
  500 http://us-west-2.ec2.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/systemd/+bug/1447807/+subscriptions

-- 
Mailing list: https://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 1452584] Re: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1452584

Title:
  package systemd 219-7ubuntu4.1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in systemd package in Ubuntu:
  New

Bug description:
  No se actualiza

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4.1
  Uname: Linux 4.0.1-040001-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sun May  3 21:17:58 2015
  DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el 
script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-04-24 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. K55VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic 
root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: systemd
  Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55VD.411
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55VD
  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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash

[Jakub Nietrzeba]

Thank you for your time, I really appreciate it. Reported as #1452581.

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

Title:
  Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash

Status in Compiz:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After upgrade from working machine with 14.10 to 15.10 I'm unable to
  login. Right after password screen I see loading of desktop and I'm
  returned to password prompt again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell]
  Date: Sun Apr 26 23:07:55 2015
  DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.26: added
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71]
  InstallationDate: Installed on 2014-11-07 (170 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: TOSHIBA SATELLITE C670-10V
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic 
root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: TKBSC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.40
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: SATELLITE C670-10V
  dmi.product.version: PSC3QE-00700JPL
  dmi.sys.vendor: TOSHIBA
  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~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sun Apr 26 23:07:32 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo

[Adrian Chapman]

Exactly the same being seen here, frequently.

Vivid 15.04, upgraded on release from 14.10 (previously upgraded several times)
Intel 3945ABG using iwl3945
Dell Latitude D830

deauthenticating by local choice message in dmesg, followed by a dozen
or so lines of "Failed check-sdata-in-driver check, flags: 0x4" all
timestamped within 0.01 seconds.

Check network-manager - networks all shown. Turn wireless hardware switch off, 
all go. Back on, all stay gone.
Restart network-manager - "Wi-Fi Networks: device not ready"

Under 14.10, on first booting the machine, it would always associate
with a weaker wireless network, and need manually changing to the
stronger. This never happened prior to 14.10, and doesn't happen under
15.04

Time before failure can be several days, or (as this morning) can be
~20min after boot. It can fail to resume, or it can happen whilst the
machine's in use. I think I've had it a dozen or so times since upgrade.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1393729] Re: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Updating a Vivid Vervet system (on Virtual Box v. 4.3.18) by running
  sudo apt-get update && sudo apt-get dist-upgrade at TTY1.

  Several packages where successfully upgraded.

  The only error I got was with avahi-daemon getting the following:

  Preparing to unpack .../avahi-daemon_0.6.31-4ubuntu4_i386.deb ...
  Job for avahi-daemon.service canceled.
  invoke-rc.d: initscript avahi-daemon, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Job for avahi-daemon.service canceled.
  invoke-rc.d: initscript avahi-daemon, action "stop" failed.
  dpkg: error processing archive 
/var/cache/apt/archives/avahi-daemon_0.6.31-4ubuntu4_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: avahi-daemon 0.6.31-4ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  Date: Tue Nov 18 09:27:13 2014
  DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu3:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-07-15 (125 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140506)
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1447807] Re: systemctl enable shows error on enabling a SysV service

[Martin Pitt]

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

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

Title:
  systemctl enable shows error on enabling a SysV service

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  SRU TEST CASE:
  --
  Trying to enable a SysV init service which does not have a corresponding 
systemd unit results in an error:

  # systemctl enable pulseaudio
  Synchronizing state for pulseaudio.service with sysvinit using update-rc.d...
  Executing /usr/sbin/update-rc.d pulseaudio defaults
  Executing /usr/sbin/update-rc.d pulseaudio enable
  Failed to execute operation: No such file or directory

  /etc/init.d/pulseaudio actually does get enabled (check
  /etc/rc*/*pulse*), but the command fails with code 1 and you get that
  error message. With the fix the command succeeds.

  SRU Regression potential
  
  Low, the modes for "sysv script + systemd unit" as well as "systemd unit 
only" already have automatic tests, and now this scenario ("sysv script only") 
has a test too. In the worst case this has the potential of completely breaking 
systemctl enable/disable, which can be worked around with changing symlinks 
manually, and isn't breaking the boot.

  
  Version details:

  Description:  Ubuntu 15.04
  Release:  15.04

  systemd:
    Installed: 219-7ubuntu3
    Candidate: 219-7ubuntu3
    Version table:
   *** 219-7ubuntu3 0
  500 http://us-west-2.ec2.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/systemd/+bug/1447807/+subscriptions

-- 
Mailing list: https://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 1167614] Re: DHCP server incorrectly handling VLAN tagged packets

[Lorin Weilenmann]

according to the changelog, this should be fixed in upstream since isc-dhcp 
4.3.2b1. see
ftp://ftp.isc.org/isc/dhcp/4.3.2/dhcp-4.3.2-RELNOTES

So all we'd need is a new package with the new upstream released

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

Title:
  DHCP server incorrectly handling VLAN tagged packets

Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  Upon receipt of a VLAN tagged packet, the DHCP server is processing it
  as though it was received without a VLAN tag.

  Steps to reproduce:
  - Send a DHCPDISCOVER packet to the broadcast address with a VLAN tag

  Expected results:
  - None. The DHCP server should ignore this packet.

  Actual results:
  - The DHCP server interprets the packet as though it were received untagged 
and transmits a response accordingly.

  Comments:
  - I believe this to be an instance of Debian bug #643564

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: isc-dhcp-server 4.1.ESV-R4-0ubuntu5.6
  ProcVersionSignature: Ubuntu 3.2.0-40.64-generic 3.2.40
  Uname: Linux 3.2.0-40-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Apr 10 18:42:30 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to precise on 2012-09-01 (221 days ago)
  modified.conffile..etc.dhcp.dhcpd.conf: [modified]
  mtime.conffile..etc.dhcp.dhcpd.conf: 2012-12-14T11:32:45

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

-- 
Mailing list: https://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 1441068] Re: lxc-destroy fails on btrfs subvolumes

[Chris West]

This also occurs for limited user containers, without asking for a btrfs
backing store.  This is more of a problem as the limited user can't
delete (or even detect) the subvolume themselves.

On a standard whole-partition-as-btrfs system, as setup by the installer, this 
looks like:
ID 257 gen 46021 top level 5 path @
ID 258 gen 46021 top level 5 path @home
...
ID 373 gen 35464 top level 257 path @/var/lib/machines
ID 374 gen 45983 top level 258 path 
faux/.local/share/lxc/vivid/rootfs/var/lib/machines
ID 395 gen 45995 top level 258 path 
faux/.local/share/lxc/vivid2/rootfs/var/lib/machines
ID 396 gen 46011 top level 258 path 
faux/.local/share/lxc/vivid3/rootfs/var/lib/machines
ID 397 gen 46014 top level 258 path 
faux/.local/share/lxc/vivid4/rootfs/var/lib/machines

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

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

-- 
Mailing list: https://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 1452601] [NEW] vivid container's networking.service fails on boot with signal=PIPE

[Chris West]

Public bug reported:

When starting a Vivid container, it fails to get an IP address.  It
believes networking.service was successful, but actually it dies with
SIGPIPE.  Restarting networking.service gets an IP, as expected.

Starting networking used to work with pre-vivid containers.  I'm
reasonably sure this fails 100% of the time.  Limited user container,
very standard setup (no unnecessary config; cgmanager and lxcfs
installed), btrfs filesystem but not btrfs-backed (as it's limited
user), ...

root@vivid:/# systemctl status networking.service
● networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
   └─50-insserv.conf-$network.conf
/lib/systemd/system/networking.service.d
   └─systemd.conf
   Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE)


root@vivid:/# systemctl restart networking.service
root@vivid:/# systemctl status networking.service
● networking.service - LSB: Raise network interfaces.
   Loaded: loaded (/etc/init.d/networking)
  Drop-In: /run/systemd/generator/networking.service.d
   └─50-insserv.conf-$network.conf
/lib/systemd/system/networking.service.d
   └─systemd.conf
   Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)
  Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, 
status=0/SUCCESS)
   CGroup: 
/user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service
   ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
   ├─1106 /bin/sh /etc/network/if-up.d/ntpdate
   ├─1109 lockfile-touch /var/lock/ntpdate-ifup
   ├─1125 /bin/sh /etc/network/if-up.d/ntpdate
   ├─1128 lockfile-create /var/lock/ntpdate-ifup
   └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com

root@vivid:/# ip a
...
22: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
...
inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lxc 1.1.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Thu May  7 08:53:02 2015
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.network.type = veth
 lxc.network.link = lxcbr0
 lxc.network.flags = up
 lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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


** Tags: amd64 apparmor apport-bug vivid

** Attachment added: "full boot log from lxc-start -F"
   
https://bugs.launchpad.net/bugs/1452601/+attachment/4392774/+files/vivid-boot.log

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

Title:
  vivid container's networking.service fails on boot with signal=PIPE

Status in lxc package in Ubuntu:
  New

Bug description:
  When starting a Vivid container, it fails to get an IP address.  It
  believes networking.service was successful, but actually it dies with
  SIGPIPE.  Restarting networking.service gets an IP, as expected.

  Starting networking used to work with pre-vivid containers.  I'm
  reasonably sure this fails 100% of the time.  Limited user container,
  very standard setup (no unnecessary config; cgmanager and lxcfs
  installed), btrfs filesystem but not btrfs-backed (as it's limited
  user), ...

  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 459 ExecStart=/etc/init.d/networking start (code=killed, 
signal=PIPE)

  
  root@vivid:/# systemctl restart networking.service
  root@vivid:/# systemctl status networking.service
  ● networking.service - LSB: Raise network interfaces.
 Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
 └─50-insserv.conf-$network.conf
  /lib/systemd/system/networking.service.d
 └─systemd.conf
 Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago
   Docs: man:systemd-sysv-generator(8)
Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, 
status=0/SUCCESS)

[Touch-packages] [Bug 1452161] Re: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed

[cm-t arudy]

** Description changed:

  I am on krillin #21 on rtm/stable channel.
  
-  * I go on flight mode (the checkbox from the indicator becomes green)
-  * I go out flight mode (the checkbox from the indicator is not anymore green)
-  * I have 2 button to unlock the SIM 1 and SIM 2
-  * I click on unlock SIM 1, I have a screen with the title "unlock SIM 2"
-  * I click on unlock SIM 2, I have s screen with the title "unlock SIM 1"
+  * I go on flight mode (the checkbox from the indicator becomes green)
+  * I go out flight mode (the checkbox from the indicator is not anymore green)
+  * I have 2 button to unlock the SIM 1 and SIM 2
+  * I click on unlock SIM 1, I have a screen with the title "unlock SIM 2"
+  * I click on unlock SIM 2, I have s screen with the title "unlock SIM 1"
  
  Since I have the same PIN, I am not sure if the button call to unlock
  the wrong SIM, on if it's only the wrong title.
+ 
+ Some details:
+  * Both SIM are from the same operator: Free (mobile.free.fr)

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

Title:
  from flight mode to normal mode with 2 SIM: PIN's title prompt is
  reversed

Status in indicator-network package in Ubuntu:
  New

Bug description:
  I am on krillin #21 on rtm/stable channel.

   * I go on flight mode (the checkbox from the indicator becomes green)
   * I go out flight mode (the checkbox from the indicator is not anymore green)
   * I have 2 button to unlock the SIM 1 and SIM 2
   * I click on unlock SIM 1, I have a screen with the title "unlock SIM 2"
   * I click on unlock SIM 2, I have s screen with the title "unlock SIM 1"

  Since I have the same PIN, I am not sure if the button call to unlock
  the wrong SIM, on if it's only the wrong title.

  Some details:
   * Both SIM are from the same operator: Free (mobile.free.fr)

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

-- 
Mailing list: https://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 1338527] Re: Bottle Gourd Is Nutritious And Healthy

[William Grant]

** Package changed: powerd (Ubuntu) => null-and-void

** Information type changed from Public to Private

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

Title:
  Bottle Gourd Is Nutritious And Healthy

Status in NULL Project:
  Invalid

Bug description:
  Lauki should be tasted before preparation or preparing its succus. Taste 
lauki can be detrimental for wellbeing. Do not eat raw lauki it can hurt your 
stomach, determine wee size lauki as big situation lauki may jazz calumnious 
chemical to raise it big.
  The succus of bottle gourd is rich and book as a penalization for umpteen 
diseases similar diabetes, diarrhea, and low execution pressure etc. bottleful 
bottle humour with a lowercase seasoning in it should be taken every day. 
Bottleful vine humour should not be mixed with any different juice, it may be 
offensive. It should be seized in summers to keep you from experience of 
sodium, tiredness, quenches desire. 
  Bottleful bottle humor mixed with sesame oil is an powerful penalty for 
insomnia. The salmagundi should be applied on scalp every night. Gourd humor 
also provides hair tutelage. It prevents graying of pilus at an embryotic age. 
Cure filament season or depilation as intimately.
  Having vine humour regularly helps tegument to brightness and emit. Remove 
pimples spatiality your skin. Women those who receive from oppressive injury 
during menstrual wheel should know bottle juice on standard assumption so as to 
keep full hurt. 
  http://forskolinfuelfacts.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1338527/+subscriptions

-- 
Mailing list: https://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 1452606] [NEW] package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from o

[Jetstorm]

Public bug reported:

encountered while installing skype from the repo.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6
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
Date: Thu May  7 02:12:14 2015
DuplicateSignature: 
package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite 
shared '/etc/xdg/Trolltech.conf', which is different from other instances of 
package libqtcore4:i386
ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
InstallationDate: Installed on 2015-05-03 (3 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: qt4-x11
Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict vivid

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

Title:
  package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to
  install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf',
  which is different from other instances of package libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  encountered while installing skype from the repo.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6
  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
  Date: Thu May  7 02:12:14 2015
  DuplicateSignature: 
package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite 
shared '/etc/xdg/Trolltech.conf', which is different from other instances of 
package libqtcore4:i386
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  InstallationDate: Installed on 2015-05-03 (3 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1452584] Re: package systemd 219-7ubuntu4.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package systemd 219-7ubuntu4.1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  No se actualiza

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu4.1
  Uname: Linux 4.0.1-040001-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Sun May  3 21:17:58 2015
  DuplicateSignature: package:systemd:219-7ubuntu4.1:el subproceso instalado el 
script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-04-24 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. K55VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.1-040001-generic 
root=UUID=97975335-8df6-4e88-bcc5-a088230afdca ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: systemd
  Title: package systemd 219-7ubuntu4.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55VD.411
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55VD
  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.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://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 1452606] Re: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from oth

[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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1452606

Title:
  package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to
  install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf',
  which is different from other instances of package libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  encountered while installing skype from the repo.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6
  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
  Date: Thu May  7 02:12:14 2015
  DuplicateSignature: 
package:libqtcore4:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6:trying to overwrite 
shared '/etc/xdg/Trolltech.conf', which is different from other instances of 
package libqtcore4:i386
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  InstallationDate: Installed on 2015-05-03 (3 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView

[Gary.Wang]

The reason why the modelChange was not triggered in such case is that
for occurrence cases, Pim(Organizer model) trigger modelChange signal
only if event id is null  ,  however eds plugin sets event id for
occurrence event which cause this bug occurs.  Same case for removing
occurrence event.

Enclose pls find the patch.

** Patch added: "fix-occurrence.patch"
   
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1364653/+attachment/4392801/+files/fix-occurrence.patch

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

Title:
  Daily Recurring Events need refresh to appear when created from
  DayView

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  New

Bug description:
  When I create a daily recurring event from the DayView that starts on
  that day, the EventBubble does not immediately appear on the current
  Day.  I can swipe to go to future days, and the EventBubble appears
  there.  If I swipe back to return to the original Day, or I go to a
  different view (MonthView, WeekView, etc.) the event appears.

  Since the EventBubble appears after re-navigating to the page in any
  way, this appears to be a "refreshing" problem, where the DayView
  isn't updated after creating a recurring event.

  Steps to Reproduce
  
  1) Open the Calendar App, and go to any day on the DayView.
  2) Create a recurring event starting on that day, which re-occurs daily.
  3) Save the new event and return to the DayView.  The EventBubble should not 
appear on the DayView for the current Day.

  Expected: The EventBubble should appear on the DayView page
  immediately after returning from creating the event.

  A reproduction of this behavior can be seen at:
  https://www.youtube.com/watch?v=9NK9m8ZznrA&feature=youtu.be

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

-- 
Mailing list: https://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 1193822] Re: dh-migrations: Typo in package description: "packaged"

[Launchpad Bug Tracker]

** Branch linked: lp:session-migration

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

Title:
  dh-migrations: Typo in package description: "packaged"

Status in Package Descriptions for Ubuntu (to make translation easy):
  Triaged
Status in session-migration package in Ubuntu:
  Fix Committed

Bug description:
  Package: dh-migrations
  Version: 0.2

  Hello,

  There's a typo in string #911 in the following sentence:

  "...operations on the installed packaged." (packaged should be
  replaced with packages)

  Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots
  /ddtp-ubuntu-main/fr/911

  Regards.

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

-- 
Mailing list: https://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 1452610] [NEW] /etc/modprobe.d is not a file

[Dimitri John Ledkov]

Public bug reported:

/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

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

-- 
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:
  New

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 1193822] Re: dh-migrations: Typo in package description: "packaged"

[Sebastien Bacher]

** Changed in: session-migration (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  dh-migrations: Typo in package description: "packaged"

Status in Package Descriptions for Ubuntu (to make translation easy):
  Triaged
Status in session-migration package in Ubuntu:
  Fix Committed

Bug description:
  Package: dh-migrations
  Version: 0.2

  Hello,

  There's a typo in string #911 in the following sentence:

  "...operations on the installed packaged." (packaged should be
  replaced with packages)

  Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots
  /ddtp-ubuntu-main/fr/911

  Regards.

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

-- 
Mailing list: https://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 1452616] [NEW] Ubuntu Web Browser identified as old Safari in gmail

[Pekorius Nedas]

Public bug reported:

Ubuntu Web Browser identified as old Safari in gmail.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1
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
CurrentDesktop: Unity
Date: Thu May  7 11:29:34 2015
SourcePackage: webbrowser-app
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

** Attachment added: "Screenshot.jpg"
   
https://bugs.launchpad.net/bugs/1452616/+attachment/4392839/+files/Screenshot.jpg

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

Title:
  Ubuntu Web Browser identified as old Safari in gmail

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu Web Browser identified as old Safari in gmail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Thu May  7 11:29:34 2015
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1452616] Re: Ubuntu Web Browser identified as old Safari in gmail

[Pekorius Nedas]

That also applies to unity Gmail webapp which also opens webbrowser-app 
Would be nice if gmai webapp and webbrowser nicely open gmail mobile version as 
the google chrome with the folowing link: 
https://mail.google.com/mail/mu/mp/912/?mui=ca#tl/priority/%5Eu

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

Title:
  Ubuntu Web Browser identified as old Safari in gmail

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Ubuntu Web Browser identified as old Safari in gmail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Thu May  7 11:29:34 2015
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1448446] Re: Cannot login into Ubuntu 15.04 after upgrade

[swestlake]

ignore my previous post, discovered the problem is addressed to
something else

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

Title:
  Cannot login into Ubuntu 15.04 after upgrade

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded my Ubuntu 14.10 to 15.04, I wanted to login into the
  GUI system. I have 4 users on my system. 3 of them is unable to login,
  1 is able. The message is "unsuccessful login". Terminal logins work
  for all users. I use lightdm.

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

-- 
Mailing list: https://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 1452390] Re: invalid pam rule in vivid is preventing logins

[swestlake]

please close this report as the issue is more prevalent to something else
thanks

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

Title:
  invalid pam rule in vivid is preventing logins

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  there are problematic pam rules preventing users from logging in (pam
  errors show up with auth.log)

  Other users are reporting this problem online with upgrades but I  can
  confirm this occurs with just new installs in Virtualbox (15.04 amd64)

  please have a look 
  thanks

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

-- 
Mailing list: https://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 1432265] Re: does not ask for multiple LUKS passphrases without plymouth

[Kimmo Satta]

I can confirm this also.

Steps to reproduce:
- install *buntu 15.04
- sudo systemctl set-default multi-user.target
- add some partition _other than root_ to /etc/crypttab

-> systemd doesn't ask for passphrase, stops at "starting cryptography
for foo.."

booting with upstart and "text" kernel option (same as systemd and
multi-user.target), it asks for passphrase and works correctly.

In my tests I had root without encryption and another partition in
crypttab, then it doesn't ask for passphrase. In another test I had root
encrypted and that in crypttab, then it asks for the passphrase.

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

Title:
  does not ask for multiple LUKS passphrases without plymouth

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Vivid:
  Triaged
Status in systemd package in Debian:
  New

Bug description:
  after the recent upstart -> systemd "migration" my system is left unable to 
complete it's boot process.
  It asks for the first passphrase, but not for the second.

  When booting with upstart (via the advanced boot options), the system
  behaves correctly and asks for both passphrases.

  /etc/crypttab
  sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard
  sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard  

  /etc/fstab
  #
  /dev/mapper/sda2_crypt  /ext4
discard,noatime,nodiratime,commit=300,errors=remount-ro 0   1
  /dev/sda1  /boot  ext3
discard,relatime,nodiratime,commit=300,defaults  0   2
  /dev/mapper/sdb1_crypt  /opt btrfs   
nofail,autodefrag,discard,enospc_debug   0   1
  #  
  tmpfs/tmp tmpfs   
relatime,nosuid 0   0
  #/dev/mapper/swap   none swapsw,discard   
  0   0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Mar 15 00:10:02 2015
  InstallationDate: Installed on 2014-05-30 (288 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. Precision M4800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic 
root=UUID=c72e0d8e-4822-45c8-b95f-6e13971940d3 ro nomodeset allow-discards 
root_trim=yes nomdmonddf nomdmonisw crashkernel=384M-:128M nogpumanager 
init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/graphical.target → 
/lib/systemd/system/graphical.target.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PMFT3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1450747] Re: Native overlay scrollbars aren't themed

[Iain Lane]

Looks like gtk in master has a position indicator thingy on mouse
activity (3.16 shows the whole scrollbar), so maybe we can tweak this to
do what o-s did & be shown all the time.

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

Title:
  Native overlay scrollbars aren't themed

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  In 3.16 (from ppa:ubuntu-desktop/ww + overlay-scrollbar from this
  PPA), applications have native overlay scrollbars provided by GTK. We
  want to use these in Ubuntu, but currently they are not themed so look
  a bit incongruous. I think we want to

- Theme them to fit in with Ambiance/Radiance
- If possible, show a thumb when the scrollbar is hidden so that you can 
see where you are in a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1450747/+subscriptions

-- 
Mailing list: https://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 1450562] Re: libdrm-intel1 2.4.60 breaks Valve/Steam games

[Timo Aaltonen]

upstream isn't convinced, someone needs to poke Valve

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

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

Title:
  libdrm-intel1 2.4.60 breaks Valve/Steam games

Status in X.Org X server:
  Confirmed
Status in libdrm package in Ubuntu:
  Incomplete

Bug description:
  Referring to this bug: https://github.com/ValveSoftware/steam-for-
  linux/issues/3506

  The only option to get games working again is to take the libdrm-intel
  2.4.56 lib files from the .deb and copy them to your local steam
  install as an override for 2.4.60 system lib.

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

-- 
Mailing list: https://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 1448834] Re: mouse battery not shown after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  mouse battery not shown after upgrade

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the
  battery level in my wireless logitech mouse.  However after upgrading
  to 15.04 the mouse battery status is not shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xfce4-power-manager 1.4.3-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 26 19:49:19 2015
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)

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

-- 
Mailing list: https://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 1452622] [NEW] /etc/os-release should not prompt on upgrade

[Dimitri John Ledkov]

Public bug reported:

--- /etc/os-release 2015-04-21 22:25:24.866354309 +0100
+++ /etc/os-release.dpkg-new2014-10-16 01:42:10.0 +0100
@@ -1,9 +1,9 @@
 NAME="Ubuntu"
-VERSION="14.04.2 LTS, Trusty Tahr"
-ID='ubuntu'
+VERSION="14.10 (Utopic Unicorn)"
+ID=ubuntu
 ID_LIKE=debian
-PRETTY_NAME="Ubuntu 14.04.2 LTS"
-VERSION_ID="14.04"
+PRETTY_NAME="Ubuntu 14.10"
+VERSION_ID="14.10"
 HOME_URL="http://www.ubuntu.com/";
 SUPPORT_URL="http://help.ubuntu.com/";
 BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

This should not happen...

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /etc/os-release should not prompt on upgrade

Status in base-files package in Ubuntu:
  New

Bug description:
  --- /etc/os-release 2015-04-21 22:25:24.866354309 +0100
  +++ /etc/os-release.dpkg-new2014-10-16 01:42:10.0 +0100
  @@ -1,9 +1,9 @@
   NAME="Ubuntu"
  -VERSION="14.04.2 LTS, Trusty Tahr"
  -ID='ubuntu'
  +VERSION="14.10 (Utopic Unicorn)"
  +ID=ubuntu
   ID_LIKE=debian
  -PRETTY_NAME="Ubuntu 14.04.2 LTS"
  -VERSION_ID="14.04"
  +PRETTY_NAME="Ubuntu 14.10"
  +VERSION_ID="14.10"
   HOME_URL="http://www.ubuntu.com/";
   SUPPORT_URL="http://help.ubuntu.com/";
   BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/";

  This should not happen...

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

-- 
Mailing list: https://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 1448834] Re: mouse battery not shown after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  mouse battery not shown after upgrade

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the
  battery level in my wireless logitech mouse.  However after upgrading
  to 15.04 the mouse battery status is not shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xfce4-power-manager 1.4.3-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 26 19:49:19 2015
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)

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

-- 
Mailing list: https://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 1452624] [NEW] /etc/os-release should be deprecated in favor of /usr/lib/os-release

[Dimitri John Ledkov]

Public bug reported:

/etc/os-release should be deprecated in favor of /usr/lib/os-release

as per latest freedesktop spec.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  /etc/os-release should be deprecated in favor of /usr/lib/os-release

Status in base-files package in Ubuntu:
  New

Bug description:
  /etc/os-release should be deprecated in favor of /usr/lib/os-release

  as per latest freedesktop spec.

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

-- 
Mailing list: https://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 1448446] Re: Cannot login into Ubuntu 15.04 after upgrade

[Sebastien Bacher]

Thank you for your bug report. Can you include your
/var/log/lightdm/lightdm.log and ~/.xsession-errors and .cache/upstart
/gnome-session-Unity.log logs?

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

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

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

Title:
  Cannot login into Ubuntu 15.04 after upgrade

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After I upgraded my Ubuntu 14.10 to 15.04, I wanted to login into the
  GUI system. I have 4 users on my system. 3 of them is unable to login,
  1 is able. The message is "unsuccessful login". Terminal logins work
  for all users. I use lightdm.

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

-- 
Mailing list: https://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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

[Luis Henriques]

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

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

Title:
  [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  Fix Released
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Confirmed
Status in systemd source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Committed
Status in systemd source package in Utopic:
  Confirmed

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions

-- 
Mailing list: https://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 1452633] [NEW] gtk-update-icons-cache-3.0 is weird during upgrade

[Dimitri John Ledkov]

Public bug reported:

it looks like it expects gtk2 pixbuf stuff?!

(gtk-update-icon-cache-3.0:29280): 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.

(gtk-update-icon-cache-3.0:29282): 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.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: 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/1452633

Title:
  gtk-update-icons-cache-3.0 is weird during upgrade

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  it looks like it expects gtk2 pixbuf stuff?!

  (gtk-update-icon-cache-3.0:29280): 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.

  (gtk-update-icon-cache-3.0:29282): 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1452633/+subscriptions

-- 
Mailing list: https://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 1319626] Re: Ubuntu One Captcha too hard to enter correctly

[Rick Ames]

How has this not been fixed yet? this problem has existed for years...

The captcha's almost always have some string of illegible r,n,u and m's.
It's so stupid.

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

Title:
  Ubuntu One Captcha too hard to enter correctly

Status in ubuntuone-client-data package in Ubuntu:
  Confirmed

Bug description:
  I tried to create a new Ubuntu One while setting up the Sofware Center
  "suggested apps"  (which required an Ubuntu One account) and ended
  frustated.

  The Captcha is really hard, I gave up on the account creation after 10
  tries, I'm a male on my twentys with normal vision and could not
  decipher the Captcha.

  Not even 4***.org captchas gives me troubles as those on the Ubuntu
  One register page.

  I suggest to improve the captchas so they're not so difficult to read,
  I can just imagie my dad would just close that window if he saw such a
  hard captcha.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntuone-client-data 13.05-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.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 14 21:29:17 2014
  Dependencies:
   
  InstallationDate: Installed on 2014-05-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntuone-client-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client-data/+bug/1319626/+subscriptions

-- 
Mailing list: https://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 1452308] Re: Mysql Workbench repeated menu options when using "locally integrated menus"

[Luis Alberto Pabón]

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

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

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

Title:
  Mysql Workbench repeated menu options when using "locally integrated
  menus"

Status in compiz package in Ubuntu:
  New
Status in mysql-workbench package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  When using locally integrated menus, Mysql workbench becomes a menu-
  nightmare of titanic proportions.

  There seems to be two sets of menues being repeated. The options are
  not the same on the first "file" menu as on the second.

  It's just better to look at the screenshot attached, actually.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mysql-workbench 6.2.3+dfsg-7build1
  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
  CurrentDesktop: Unity
  Date: Wed May  6 15:50:43 2015
  InstallationDate: Installed on 2015-05-01 (5 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: mysql-workbench
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1452640] [NEW] after upgarding to vivid version of ubuntu VPN connections are not working

[Szalay Dániel]

Public bug reported:

I've just upgraded to the new version of Ubuntu distrib, called Vivid
and now the network manager doesn't connect to the VPN server. In the
earlier version there was no problem with the connecting.   " A VPN
kapcosolat meghiúsult érvénytelen titkos VPN információk miatt"

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.1
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic i686
ApportVersion: 2.17.2-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME-Flashback:Unity
Date: Thu May  7 11:16:54 2015
EcryptfsInUse: Yes
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2011-04-17 (1480 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IpRoute:
 default via 192.168.42.129 dev usb0  proto static  metric 1024 
 169.254.0.0/16 dev usb0  scope link  metric 1000 
 192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.77
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WiMAXEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago)
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 usb0ethernet  connected /org/freedesktop/NetworkManager/Devices/3  
Automatikus Ethernet  926ed2d3-404f-4b1a-8e71-9c5ff6e44c33  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  --  
  ----  
   
 eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  --  
  ----  
   
 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  --  
  ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: apport-bug i386 vivid

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

Title:
  after upgarding to vivid version of ubuntu VPN connections are not
  working

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've just upgraded to the new version of Ubuntu distrib, called Vivid
  and now the network manager doesn't connect to the VPN server. In the
  earlier version there was no problem with the connecting.   " A VPN
  kapcosolat meghiúsult érvénytelen titkos VPN információk miatt"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Thu May  7 11:16:54 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2011-04-17 (1480 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 192.168.42.129 dev usb0  proto static  metric 1024 
   169.254.0.0/16 dev usb0  scope link  metric 1000 
   192.168.42.0/24 dev usb0  proto kernel  scope link  src 192.168.42.77
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WiMAXEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   usb0ethernet  connected /org/freedesktop/NetworkManager/Devices/3  
Automatikus Ethernet  926ed2d3-404f-4b1a-8e71-9c5ff6e44c33  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
------  
   
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
------  
   
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops

[John McAleely]

DIsabling as a workaround is bug #1452663

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

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

Status in the base for Ubuntu mobile products:
  Fix Committed
Status in Upstart:
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  We recently started getting reprots from phone users that their
  devices go into a reboot loop after changing the language or getting
  an OTA upgrade (either of both end with a reboot of the phone)

  after a bit of research we collected the log at
  http://pastebin.ubuntu.com/10872934/

  this shows a segfault of upstarts init binary in the log.c code:

  [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: 
log->unflushed->len
  [7.000279]init: Caught abort, core dumped
  [7.467176]Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0600

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

-- 
Mailing list: https://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 1393729] Re: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Alberto Salvia Novella]

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

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

Title:
  package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Updating a Vivid Vervet system (on Virtual Box v. 4.3.18) by running
  sudo apt-get update && sudo apt-get dist-upgrade at TTY1.

  Several packages where successfully upgraded.

  The only error I got was with avahi-daemon getting the following:

  Preparing to unpack .../avahi-daemon_0.6.31-4ubuntu4_i386.deb ...
  Job for avahi-daemon.service canceled.
  invoke-rc.d: initscript avahi-daemon, action "stop" failed.
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Job for avahi-daemon.service canceled.
  invoke-rc.d: initscript avahi-daemon, action "stop" failed.
  dpkg: error processing archive 
/var/cache/apt/archives/avahi-daemon_0.6.31-4ubuntu4_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: avahi-daemon 0.6.31-4ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: i386
  Date: Tue Nov 18 09:27:13 2014
  DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu3:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2014-07-15 (125 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140506)
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1436405] Re: Duplicate menu (both unity and in-app) for kde apps

[Alberto Salvia Novella]

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Confirmed

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

Title:
  Duplicate menu (both unity and in-app) for kde apps

Status in One Hundred Papercuts:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

-- 
Mailing list: https://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 1437538] Re: Battery Applet appears in English with Gnome in Ubuntu 12.04

[Matthew Paul Thomas]

The "three years" thing is irrelevant: it applied only to Ubuntu 10.04 LTS and 
earlier.



It's not clear whether this bug is actually a problem with incomplete
translations, or with something else. But if it is, the language-pack-es
package has been updated six times since Ubuntu 12.04 was released. Why
can't it be updated again? 

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

Title:
  Battery Applet appears in English with Gnome in Ubuntu 12.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 12.04 on a Toshiba NB500. I use the Gnome desktop environment, but 
I found a bug:
  The battery applet appears in English, but with Unity appears in Spanish, but 
I still use Gnome !. So I ask you traduzcais battery applet to Spanish. If you 
ask me I missing some information. a greeting

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

-- 
Mailing list: https://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 1436405] Re: Duplicate menu (both unity and in-app) for kde apps

[Alberto Salvia Novella]

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

** Changed in: libdbusmenu-qt (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Duplicate menu (both unity and in-app) for kde apps

Status in One Hundred Papercuts:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

-- 
Mailing list: https://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 1450652] Re: 15.04: no route when connected to both WiFi and Ethernet

[Alberto Salvia Novella]

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

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

Title:
  15.04: no route when connected to both WiFi and Ethernet

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  ===

  1) Enable both a WiFi connection and plug into Ethernet
  2) Test your network connectivity or run `route`

  Expected results
  =

  NetworkManager should prefer the wired connection over the WiFi
  connection, and `route` should return something like this:

  $ route
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  default 10.17.75.1  0.0.0.0 UG1024   00 wlan0
  10.17.75.0  *   255.255.255.0   U 0  00 wlan0
  link-local  *   255.255.0.0 U 1000   00 wlan0

  (To get the above results on Vivid, I had to unplug my Ethernet.)

  Actual results
  ===

  `route` will produce no results and your connectivity will be broken

  Work-arounds
  ===

  As soon as you disable either the WiFi or unplug from Ethernet, you
  will again have a route and your network connectivity will work. This
  is a regression from Trusty and Utopic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 16:00:09 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.17.75.1 dev wlan0  proto static  metric 1024 
   10.17.75.0/24 dev wlan0  proto kernel  scope link  src 10.17.75.247 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
  
   Wired connection 1  4ff8582e-2864-4729-877e-52b037de1ee8  802-3-ethernet   
1430431120  Thu 30 Apr 2015 03:58:40 PM MDT  yes  no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
  
   system76_5g 74de1f59-702b-4d15-9803-82b281989bed  802-11-wireless  
1430431008  Thu 30 Apr 2015 03:56:48 PM MDT  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
system76_5g  74de1f59-702b-4d15-9803-82b281989bed  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 1448834] Re: mouse battery not shown after upgrade

[Alberto Salvia Novella]

** Changed in: upower (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-power-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  mouse battery not shown after upgrade

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the
  battery level in my wireless logitech mouse.  However after upgrading
  to 15.04 the mouse battery status is not shown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xfce4-power-manager 1.4.3-0ubuntu1
  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
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 26 19:49:19 2015
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-power-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago)

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

-- 
Mailing list: https://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 1452238] Re: Failed to upgrade system from 14.04

[Tim Chen]

@4$

which command did you run at firsttime in

https://pastebin.canonical.com/130750/

?

 apt-get dist-upgrade or apt-get upgrade?

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

Title:
  Failed to upgrade system from 14.04

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Download and install the 14.04 image.
  
http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso

  $ sudo apt-get update
  $ sudo apt-get upgrade
  .
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ...
  Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ...
  Setting up libudev1:amd64 (204-5ubuntu20.11) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  (Reading database ... 163205 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ...
  Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on initscripts (>= 2.88dsf-25); however:
Package initscripts is not configured yet.

  dpkg: error processing package ifupdown (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

E: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

-- 
Mailing list: https://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 1452238] Re: Failed to upgrade system from 14.04

[Tim Chen]

@Bin

could we use

#apt-get dist-upgrade

instead?

since that's what update-manager would do~

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

Title:
  Failed to upgrade system from 14.04

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Download and install the 14.04 image.
  
http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso

  $ sudo apt-get update
  $ sudo apt-get upgrade
  .
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ...
  Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ...
  Setting up libudev1:amd64 (204-5ubuntu20.11) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  (Reading database ... 163205 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ...
  Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on initscripts (>= 2.88dsf-25); however:
Package initscripts is not configured yet.

  dpkg: error processing package ifupdown (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

E: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

-- 
Mailing list: https://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 1452238] Re: Failed to upgrade system from 14.04

[Tim Chen]

Package: udev
Source: systemd
Version: 204-5ubuntu20kittyhawk1
Architecture: amd64
Maintainer: Ubuntu Developers 
Installed-Size: 5143
Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.17), 
libcgmanager0, libdbus-1-3 (>= 1.0.2), libkmod2 (>= 5~), libnih-dbus1 (>= 
1.0.0), libnih1 (>= 1.0.0), libselinux1 (>= 2.0.65), libudev1 (= 
204-5ubuntu20kittyhawk1), sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), 
lsb-base (>= 3.0-6), util-linux (>= 2.16), procps
Replaces: systemd-services (<< 202-0ubuntu6)
Section: admin
Priority: important
Multi-Arch: foreign

not sure why but seems udev only depends on libc6, however libc6-dbg and
libc6-dev  depends on a old version of libc6, so it seems a loop
dependency to me but I'm not sure why libc6-dbg and libc6-dev didn't get
upgrade in the same time...

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

Title:
  Failed to upgrade system from 14.04

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Download and install the 14.04 image.
  
http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso

  $ sudo apt-get update
  $ sudo apt-get upgrade
  .
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ...
  Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ...
  Setting up libudev1:amd64 (204-5ubuntu20.11) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  (Reading database ... 163205 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ...
  Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on initscripts (>= 2.88dsf-25); however:
Package initscripts is not configured yet.

  dpkg: error processing package ifupdown (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

E: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

-- 
Mailing list: https://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 1452238] Re: Failed to upgrade system from 14.04

[Shih-Yuan Lee]

apt-get dist-upgrade

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

Title:
  Failed to upgrade system from 14.04

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Download and install the 14.04 image.
  
http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso

  $ sudo apt-get update
  $ sudo apt-get upgrade
  .
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ...
  Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ...
  Setting up libudev1:amd64 (204-5ubuntu20.11) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  (Reading database ... 163205 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ...
  Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on initscripts (>= 2.88dsf-25); however:
Package initscripts is not configured yet.

  dpkg: error processing package ifupdown (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

E: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

-- 
Mailing list: https://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 1452676] [NEW] Right-click menu instead of leading/ trailing actions

[Christian Dywan]

Public bug reported:

On desktops/ laptops the leading and trailing actions of list items
should be available as context menus. In practise we probably want to
enable the menu if a mouse is being used and only enable the actions if
s touchscreen is available.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  Right-click menu instead of leading/ trailing actions

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

Bug description:
  On desktops/ laptops the leading and trailing actions of list items
  should be available as context menus. In practise we probably want to
  enable the menu if a mouse is being used and only enable the actions
  if s touchscreen is available.

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

-- 
Mailing list: https://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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices

[redfox7691]

Fixed on Kernel 4.0 or with patch of btusb.c and firmware from Windows
driver

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

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

Title:
  Broadcom Corporation BCM4352 bluetooth adapter not finding any
  bluetooth devices

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Broadcom Corporation BCM4352 wi-fi/bluetooth adapter  is unable to
  find/detect Bluetooth devices, and Bluetooth devices can not see the
  Ubuntu PC, even when in pairing mode.

  (Here is a similar bug, but for a different Broadcom device:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311)

  MOTHERBOARD INFO

  $ sudo dmidecode -t baseboard
  # dmidecode 2.12
  SMBIOS 2.7 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASRock
   Product Name: Z87E-ITX
   Version:
   Serial Number: E80-34027900563
   Asset Tag:
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis:
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  UBUNTU INFO

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

   $ uname -a
  Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  WI-FI DEVICE INFO

  $ lspci | grep Broadcom
  03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless 
Network Adapter (rev 03)

  Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth
  adapter.

  BLUETOOTH DEVICE INFO

  $ lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 13d3:3404 IMC Networks
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1b1c:0c04 Corsair
  Bus 003 Device 003: ID 046d:0826 Logitech, Inc.
  Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D 
Wireless Optical Mouse
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The system log does not show any errors when the btusb module is
  loaded...

  kernel: [36245.996355] usbcore: registered new interface driver btusb
  bluetoothd[833]: Unknown command complete for opcode 19
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled

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

-- 
Mailing list: https://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 1450652] Re: 15.04: no route when connected to both WiFi and Ethernet

[BenTLor]

For me the situation is slightly different but the result is the same:
Connect to WiFi
 - internet connection works
Connect LAN cable (note that wifi is still active and nm sets up eth0 correctly)
 - internet connection breaks, although route -n shows both interfaces and 
routes.

Expected: when I connect eth0, it is preferred over wifi (either with
metric or disconnecting wifi entirely, I don't care) and thus routing
works as normal.

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

Title:
  15.04: no route when connected to both WiFi and Ethernet

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  ===

  1) Enable both a WiFi connection and plug into Ethernet
  2) Test your network connectivity or run `route`

  Expected results
  =

  NetworkManager should prefer the wired connection over the WiFi
  connection, and `route` should return something like this:

  $ route
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  default 10.17.75.1  0.0.0.0 UG1024   00 wlan0
  10.17.75.0  *   255.255.255.0   U 0  00 wlan0
  link-local  *   255.255.0.0 U 1000   00 wlan0

  (To get the above results on Vivid, I had to unplug my Ethernet.)

  Actual results
  ===

  `route` will produce no results and your connectivity will be broken

  Work-arounds
  ===

  As soon as you disable either the WiFi or unplug from Ethernet, you
  will again have a route and your network connectivity will work. This
  is a regression from Trusty and Utopic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  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
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 16:00:09 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.17.75.1 dev wlan0  proto static  metric 1024 
   10.17.75.0/24 dev wlan0  proto kernel  scope link  src 10.17.75.247 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
  
   Wired connection 1  4ff8582e-2864-4729-877e-52b037de1ee8  802-3-ethernet   
1430431120  Thu 30 Apr 2015 03:58:40 PM MDT  yes  no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
  
   system76_5g 74de1f59-702b-4d15-9803-82b281989bed  802-11-wireless  
1430431008  Thu 30 Apr 2015 03:56:48 PM MDT  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
system76_5g  74de1f59-702b-4d15-9803-82b281989bed  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices

[redfox7691]

SOLVED: if you have this USB device 13d3:3404 like me there is a lack of
firmware uploading, this is solved in kernel 4.0, so if you have a
kernel 3.x you must patch btusb.c and recompile this module.

For example I have a 3.18.12 kernel (installed into Ubuntu 14.04 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D), here is what
I've done:

- get the kernel source with wget 
https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.12.tar.xz
- tar xpvf linux-3.18.12.tar.xz
- cd linux-3.18.12/drivers/bluetooth
- gedit btusb
- add this line under /* Broadcom BCM20702A0 */ 
  { USB_DEVICE(0x13d3, 0x3404), .driver_info = BTUSB_BCM_PATCHRAM },
- cp /boot/config-$(uname -r) .config
- cp /usr/src/linux-headers-$(uname -r)/Module.symvers Module.symvers
- sudo apt-get install build-essential linux-headers-generic
- sudo cp btusb.ko /lib/modules/$(uname -r)/kernel/drivers/bluetooth/
- get file https://dl.dropboxusercontent.com/u/2259248/BCM20702A0-13d3-3404.hcd 
and put it into /lib/firmware/brcm directory
- reboot

That's all, folk!

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

Title:
  Broadcom Corporation BCM4352 bluetooth adapter not finding any
  bluetooth devices

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Broadcom Corporation BCM4352 wi-fi/bluetooth adapter  is unable to
  find/detect Bluetooth devices, and Bluetooth devices can not see the
  Ubuntu PC, even when in pairing mode.

  (Here is a similar bug, but for a different Broadcom device:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311)

  MOTHERBOARD INFO

  $ sudo dmidecode -t baseboard
  # dmidecode 2.12
  SMBIOS 2.7 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASRock
   Product Name: Z87E-ITX
   Version:
   Serial Number: E80-34027900563
   Asset Tag:
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis:
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  UBUNTU INFO

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

   $ uname -a
  Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  WI-FI DEVICE INFO

  $ lspci | grep Broadcom
  03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless 
Network Adapter (rev 03)

  Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth
  adapter.

  BLUETOOTH DEVICE INFO

  $ lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 13d3:3404 IMC Networks
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1b1c:0c04 Corsair
  Bus 003 Device 003: ID 046d:0826 Logitech, Inc.
  Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D 
Wireless Optical Mouse
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The system log does not show any errors when the btusb module is
  loaded...

  kernel: [36245.996355] usbcore: registered new interface driver btusb
  bluetoothd[833]: Unknown command complete for opcode 19
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled

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

-- 
Mailing list: https://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 1452300] Re: Reboot takes too long

[John McAleely]

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

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

Title:
  Reboot takes too long

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

Bug description:
  Test case.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="816" x-info="http://w
  ww.rsyslog.com"] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="817" x-info="http://w
  ww.rsyslog.com"] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

-- 
Mailing list: https://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 1452099] Re: unshare -r is broken

[Martin Pitt]

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

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  unshare -r is broken

Status in util-linux package in Ubuntu:
  Fix Committed
Status in util-linux package in Debian:
  Fix Released

Bug description:
  After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no
  longer works.

  $ unshare -Ur
  unshare: write failed /proc/self/gid_map: Operation not permitted
  $ sudo -i
  # unshare -r
  unshare: write failed /proc/self/gid_map: Operation not permitted

  This was fixed in Debian’s util-linux 2.25.2-6.

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

-- 
Mailing list: https://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 1452346] Re: please drop build-dependency on g++-4.9

[Michi Henning]

Thanks for the heads-up. Will change this as soon as Wily is open to
landings.

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  please drop build-dependency on g++-4.9

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  The unity-scopes-api package currently has a build-dependency on
  g++-4.9. This build-dependency is present because of the
  recommendations on https://wiki.ubuntu.com/cpp-11 about handling of
  C++11.

  The C++11 ABI has now stabilized in gcc as of gcc 5; however, before
  we can switch to gcc 5, we first need to be able to do rebuild tests
  of the archive against this compiler.

  To facilitate this, please drop the build-dependency on g++-4.9 from
  the package in wily. 4.9 will remain the default until all transition
  issues have been identified, so there is no risk of accidental ABI
  breakage here anymore.

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

-- 
Mailing list: https://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 1452681] [NEW] Incomplete doc for scope.ini files

[Michi Henning]

Public bug reported:

We need to add a section to the doc to detail all the possible settings
in a scope's .ini file. For example, right now, the ResultsTtlType
config item is effectively undocumented. The doc should show all the
scope.ini settings that are recognised, with an explanation of their
meaning and the possible range of values.

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Assignee: Michi Henning (michihenning)
 Status: New

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

Title:
  Incomplete doc for scope.ini files

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  We need to add a section to the doc to detail all the possible
  settings in a scope's .ini file. For example, right now, the
  ResultsTtlType config item is effectively undocumented. The doc should
  show all the scope.ini settings that are recognised, with an
  explanation of their meaning and the possible range of values.

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

-- 
Mailing list: https://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 1452682] [NEW] Individual input source per window not working on 15.04

[solarw]

Public bug reported:

ubuntu 15.04. unity

I use unity config center to set two input languages and check use individual 
input source per window.
But it does not work for me. I tried guest session. Same issue.
Language input source is global for all windows.

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


** Tags: ibus input unity

** Tags added: input

** Tags added: ibus unity

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

Title:
  Individual input source per window not working on 15.04

Status in ibus package in Ubuntu:
  New

Bug description:
  ubuntu 15.04. unity

  I use unity config center to set two input languages and check use individual 
input source per window.
  But it does not work for me. I tried guest session. Same issue.
  Language input source is global for all windows.

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

-- 
Mailing list: https://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 1452238] Re: Failed to upgrade system from 14.04

[Shih-Yuan Lee]

If I upgrade ifupdown by `sudo apt-get install ifupdown` first and then
upgrade the whole system by `sudo apt-get dist-upgrade`, there is no
problem at all.

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

Title:
  Failed to upgrade system from 14.04

Status in ifupdown:
  New
Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Download and install the 14.04 image.
  
http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso

  $ sudo apt-get update
  $ sudo apt-get upgrade
  .
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ...
  Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ...
  Setting up libudev1:amd64 (204-5ubuntu20.11) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  (Reading database ... 163205 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ...
  Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  dpkg: dependency problems prevent configuration of ifupdown:
   ifupdown depends on initscripts (>= 2.88dsf-25); however:
Package initscripts is not configured yet.

  dpkg: error processing package ifupdown (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

E: Sub-process /usr/bin/dpkg returned an error code 
(1)

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

-- 
Mailing list: https://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 1452682] Re: Individual input source per window not working on 15.04

[Aron Xu]

Such behavior is expected as ibus lost the ability during its
integration time with GNOME 3.

** Changed in: ibus (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Individual input source per window not working on 15.04

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  ubuntu 15.04. unity

  I use unity config center to set two input languages and check use individual 
input source per window.
  But it does not work for me. I tried guest session. Same issue.
  Language input source is global for all windows.

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

-- 
Mailing list: https://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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles

[Martin Pitt]

This really doesn't belong into init-system-helpers. It was just right
in upstart, as it's only being used in upstart jobs. I don't want to
have a permanent delta just for this.

** Changed in: upstart (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  apt-get install lxc doesn't load required apparmor profiles

Status in apparmor package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in squid3 package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  I'm trying to use LXC on my openstack instance which runs vivid daily:

  $ sudo apt-get install lxc -y

  $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
  --stream=daily --release=vivid

  $ sudo lxc-start --name vivid --logfile=lxc.log
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  In the log file (lxc.log) I observe the following error:
  lxc-start 1426516387.814 ERRORlxc_apparmor - 
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - 
failed to change apparmor profile to lxc-container-default

  This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was
  not loaded appropriately.

  This issue disappears if I:
  (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
  or
  (b) reboot the instance

  I'd expect that 'apt-get install lxc' has to load all appropriate
  apparmor profiles to allow starting containers w/o profile reloading /
  rebooting.

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

-- 
Mailing list: https://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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

[Simon Déziel]

Works here too, thanks!

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

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in rsyslog package in Ubuntu:
  Fix Released
Status in apparmor source package in Trusty:
  In Progress
Status in linux source package in Trusty:
  Confirmed
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in rsyslog source package in Trusty:
  Fix Committed

Bug description:
  [rsyslog impact]
  This bug prevents rsyslog from receiving all events from other services on 
trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds 
an additional permission (read access to /dev/log) to the rsyslog apparmor 
policy to allow this to work.

  [rsyslog test case]
  (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up 
listed in the "XX  profiles are in enforce mode." section reported by "sudo 
aa-status" (if it's disabled, do "sudo aa-enforce rsyslogd").

  (2) Install the utopic or newer hwe enablement stack reboot into the
  kernel. Using the logger(1) utility should generate log messages (e.g.
  "logger foo") that are recorded in syslog; with this bug, they will be
  blocked (grep DENIED /var/log/syslog).

  [rsyslog regression potential]
  The only change to rsyslog in the SRU is a slight loosening of the rsyslog 
apparmor policy. The risk of an introduced regression is small.

  [rsyslog addition info]
  The qa-regression-testing script is useful for verifying that rsyslog is 
still functioning properly 
(http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py)
   

  [Original description]
  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely 
unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" 
requested_mask="r" denied_mask="r" fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" 
profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  I'm not sure how apparmor decides which profile to use for which task,
  but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

-- 
Mailing list: https://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 1452682] Re: Individual input source per window not working on 15.04

[solarw]

is there any workaround? like changing input method app?
i want to use unity, but I need individual input source per window

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

Title:
  Individual input source per window not working on 15.04

Status in ibus package in Ubuntu:
  Won't Fix

Bug description:
  ubuntu 15.04. unity

  I use unity config center to set two input languages and check use individual 
input source per window.
  But it does not work for me. I tried guest session. Same issue.
  Language input source is global for all windows.

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

-- 
Mailing list: https://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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles

[Martin Pitt]

lxc wasn't fixed for this yet -- /usr/lib/x86_64-linux-gnu/lxc/lxc-
apparmor-load still calls the wrapper, and not /lib/apparmor/profile-
load.

** Changed in: lxc (Ubuntu)
   Importance: Critical => Medium

** Changed in: lxc (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  apt-get install lxc doesn't load required apparmor profiles

Status in apparmor package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Triaged
Status in squid3 package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  I'm trying to use LXC on my openstack instance which runs vivid daily:

  $ sudo apt-get install lxc -y

  $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
  --stream=daily --release=vivid

  $ sudo lxc-start --name vivid --logfile=lxc.log
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  In the log file (lxc.log) I observe the following error:
  lxc-start 1426516387.814 ERRORlxc_apparmor - 
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - 
failed to change apparmor profile to lxc-container-default

  This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was
  not loaded appropriately.

  This issue disappears if I:
  (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
  or
  (b) reboot the instance

  I'd expect that 'apt-get install lxc' has to load all appropriate
  apparmor profiles to allow starting containers w/o profile reloading /
  rebooting.

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

-- 
Mailing list: https://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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles

[Martin Pitt]

Upstream pull request for LXC: https://github.com/lxc/lxc/pull/512

** Changed in: init-system-helpers (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: init-system-helpers (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Changed in: init-system-helpers (Ubuntu)
   Importance: Critical => Medium

** Changed in: lxc (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  apt-get install lxc doesn't load required apparmor profiles

Status in apparmor package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  In Progress
Status in squid3 package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  I'm trying to use LXC on my openstack instance which runs vivid daily:

  $ sudo apt-get install lxc -y

  $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
  --stream=daily --release=vivid

  $ sudo lxc-start --name vivid --logfile=lxc.log
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  In the log file (lxc.log) I observe the following error:
  lxc-start 1426516387.814 ERRORlxc_apparmor - 
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - 
failed to change apparmor profile to lxc-container-default

  This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was
  not loaded appropriately.

  This issue disappears if I:
  (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
  or
  (b) reboot the instance

  I'd expect that 'apt-get install lxc' has to load all appropriate
  apparmor profiles to allow starting containers w/o profile reloading /
  rebooting.

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

-- 
Mailing list: https://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 1317449]

[Caulier-gilles-9]

*** Bug 347107 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in digikam package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Fix Released
Status in digikam source package in Trusty:
  Confirmed
Status in sqlite3 source package in Trusty:
  Confirmed
Status in digikam source package in Utopic:
  Fix Released
Status in sqlite3 source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version > 3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3 > 3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

-- 
Mailing list: https://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 1317449]

[Caulier-gilles-9]

*** Bug 347054 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in digikam package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Fix Released
Status in digikam source package in Trusty:
  Confirmed
Status in sqlite3 source package in Trusty:
  Confirmed
Status in digikam source package in Utopic:
  Fix Released
Status in sqlite3 source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version > 3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3 > 3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

-- 
Mailing list: https://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 1317449]

[Caulier-gilles-9]

*** Bug 347340 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in digikam package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Fix Released
Status in digikam source package in Trusty:
  Confirmed
Status in sqlite3 source package in Trusty:
  Confirmed
Status in digikam source package in Utopic:
  Fix Released
Status in sqlite3 source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version > 3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions > 3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3 > 3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

-- 
Mailing list: https://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 1441847] Re: Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

[Timo Aaltonen]

xtrans & lllvm-toolchain-3.6 verified

libdrm issue (bug 1450562) is, according to upstream, not a bug in the
package

** Description changed:

  The vivid X11 stack backport needs libdrm and xtrans backported to
  trusty.
  
  libdrm 2.4.56-1 -> 2.4.60-2 important changes:
  - new SI & CIK pci-ids (radeon)
  - SKL pci-ids (intel)
  - tegra support
  
- 
  xtrans 1.3.4-1 -> 1.3.5-1 changes
  - a bunch of const fixes
  - a new Listen function which the X server wants to allow -nolisten tcp by 
default
  http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz
+ 
+ llvm-toolchain-3.6 is new for trusty, needed by mesa

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

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

Title:
  Please backport libdrm, xtrans, llvm-toolchain-3.6 for 14.04.3

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.6 package in Ubuntu:
  Invalid
Status in xtrans package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.6 source package in Trusty:
  Fix Committed
Status in xtrans source package in Trusty:
  Fix Committed

Bug description:
  The vivid X11 stack backport needs libdrm and xtrans backported to
  trusty.

  libdrm 2.4.56-1 -> 2.4.60-2 important changes:
  - new SI & CIK pci-ids (radeon)
  - SKL pci-ids (intel)
  - tegra support

  xtrans 1.3.4-1 -> 1.3.5-1 changes
  - a bunch of const fixes
  - a new Listen function which the X server wants to allow -nolisten tcp by 
default
  http://launchpadlibrarian.net/189120642/xtrans_1.3.4-1_1.3.5-1.diff.gz

  llvm-toolchain-3.6 is new for trusty, needed by mesa

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

-- 
Mailing list: https://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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices

[Robin]

The description in #5 is not a fix, but rather a hack, which will have to be 
repeated for every kernel update. A true fix would involve:
a) amending the btusb file
b) including the fully BT capable firmware in a package

If only a) is done, that would be a big improvement!

Please note that 14.04 LTS will be using the 3.13.0 kernel until 2019,
so this bug needs a robust fix!

Thanks to redfox for getting to the bottom of it!

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

Title:
  Broadcom Corporation BCM4352 bluetooth adapter not finding any
  bluetooth devices

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Broadcom Corporation BCM4352 wi-fi/bluetooth adapter  is unable to
  find/detect Bluetooth devices, and Bluetooth devices can not see the
  Ubuntu PC, even when in pairing mode.

  (Here is a similar bug, but for a different Broadcom device:
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311)

  MOTHERBOARD INFO

  $ sudo dmidecode -t baseboard
  # dmidecode 2.12
  SMBIOS 2.7 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
   Manufacturer: ASRock
   Product Name: Z87E-ITX
   Version:
   Serial Number: E80-34027900563
   Asset Tag:
   Features:
    Board is a hosting board
    Board is replaceable
   Location In Chassis:
   Chassis Handle: 0x0003
   Type: Motherboard
   Contained Object Handles: 0

  UBUNTU INFO

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

   $ uname -a
  Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  WI-FI DEVICE INFO

  $ lspci | grep Broadcom
  03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless 
Network Adapter (rev 03)

  Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth
  adapter.

  BLUETOOTH DEVICE INFO

  $ lsusb
  Bus 002 Device 002: ID 8087:8000 Intel Corp.
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 13d3:3404 IMC Networks
  Bus 001 Device 002: ID 8087:8008 Intel Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1b1c:0c04 Corsair
  Bus 003 Device 003: ID 046d:0826 Logitech, Inc.
  Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D 
Wireless Optical Mouse
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The system log does not show any errors when the btusb module is
  loaded...

  kernel: [36245.996355] usbcore: registered new interface driver btusb
  bluetoothd[833]: Unknown command complete for opcode 19
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.1820 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG
  bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSource
  bluetoothd[833]: Endpoint registered: sender=:1.77 
path=/MediaEndpoint/A2DPSink
  bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled

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

-- 
Mailing list: https://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 1452300] Re: Reboot takes too long

[John McAleely]

Also reproduced from 'today' screen for me. Very disconcerting, because
the screen was black for most of the 'reboot' period before there was a
flash of the greeter and then the BQ splash logo.

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

Title:
  Reboot takes too long

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

Bug description:
  Test case.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="816" x-info="http://w
  ww.rsyslog.com"] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="817" x-info="http://w
  ww.rsyslog.com"] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

-- 
Mailing list: https://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 1452300] Re: Reboot takes too long

[John McAleely]

FWIW, this does not seem to impact the reboot performed by 'factory
reset'

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

Title:
  Reboot takes too long

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

Bug description:
  Test case.
  - In the greeter screen, long press power button to display power dialog.
  - Tap to reboot.

  Expected result.
  - Must take similar time than stable.

  Actual result.
  - Stable takes 30 seconds to show the bq white screen.
  - 274 takes bewteen than 2 and 3 minutes to show the bq screen.

  syslog:

  May  6 14:16:35 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="816" x-info="http://w
  ww.rsyslog.com"] exiting on signal 15.
  May  6 14:20:05 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="817" x-info="http://w
  ww.rsyslog.com"] start

  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed

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

-- 
Mailing list: https://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 1170647] Re: After minimizing a Nautilus window of another partition or external media or Trash folder, clicking on the "Files" icon on the Launcher again doesn't restore the min

[Ishan Chaki]

OMG! this bug still exists. I faced this bug an year ago, then switched
to elementary os. Can't believe this bug is still not 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/1170647

Title:
  After minimizing a Nautilus window of another partition or external
  media or Trash folder, clicking on the "Files" icon on the Launcher
  again doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in Vivid OPM Workspace:
  New
Status in unity package in Ubuntu:
  Triaged
Status in unity source package in Trusty:
  Confirmed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the "Files" icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the "Files" icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - One way to navigate between windows at this moment is to use the
  "control + tabulation" key combination, or to click again on the
  "Files" icon so windows are exposed.

  Otherwise the minimized window Can be restored by clicking on the
  Volume's launcher icon or scrolling on the Files icon

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the "Files" icon and select the
  "unlock from Launcher" option.

  FIX

  - The launcher icon for "Files" to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the "Files" icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

-- 
Mailing list: https://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 1193822] Re: dh-migrations: Typo in package description: "packaged"

[Launchpad Bug Tracker]

This bug was fixed in the package session-migration - 0.2.3

---
session-migration (0.2.3) wily; urgency=low

  * debian/patches/fix-typo-in-package-desc.dff: fix typo in package
description. The word 'packaged' was replaced with 'packages'.
(LP: #1193822)

 -- Gayan Weerakutti   Wed, 06 May 2015 11:39:12
+0530

** Changed in: session-migration (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  dh-migrations: Typo in package description: "packaged"

Status in Package Descriptions for Ubuntu (to make translation easy):
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  Package: dh-migrations
  Version: 0.2

  Hello,

  There's a typo in string #911 in the following sentence:

  "...operations on the installed packaged." (packaged should be
  replaced with packages)

  Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots
  /ddtp-ubuntu-main/fr/911

  Regards.

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

-- 
Mailing list: https://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 1442733] Re: on autopilot helpers, swipe child into view fails if the on-screen keyboard is visible

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntuone-credentials -
14.04+15.10.20150506

---
ubuntuone-credentials (14.04+15.10.20150506) wily; urgency=medium

  [ Leo Arias ]
  * On autopilot helpers, dismiss the on-screen keyboard when filling
the new account form. Workaround for bug #1442733. (LP: #1442733)

 -- CI Train Bot   Wed, 06 May 2015 20:53:15
+

** Changed in: ubuntuone-credentials (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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1442733

Title:
  on autopilot helpers, swipe child into view fails if the on-screen
  keyboard is visible

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released

Bug description:
  On the autopilot helpers we have a method to swipe a child into view.
  When the child is in the bottom of the container and the on-screen
  keyboard is visible, the helper will fail because it will start
  swiping over the keyboard.

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

-- 
Mailing list: https://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 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView

[Ubuntu Foundations Team Bug Bot]

The attachment "fix-occurrence.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Daily Recurring Events need refresh to appear when created from
  DayView

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  New

Bug description:
  When I create a daily recurring event from the DayView that starts on
  that day, the EventBubble does not immediately appear on the current
  Day.  I can swipe to go to future days, and the EventBubble appears
  there.  If I swipe back to return to the original Day, or I go to a
  different view (MonthView, WeekView, etc.) the event appears.

  Since the EventBubble appears after re-navigating to the page in any
  way, this appears to be a "refreshing" problem, where the DayView
  isn't updated after creating a recurring event.

  Steps to Reproduce
  
  1) Open the Calendar App, and go to any day on the DayView.
  2) Create a recurring event starting on that day, which re-occurs daily.
  3) Save the new event and return to the DayView.  The EventBubble should not 
appear on the DayView for the current Day.

  Expected: The EventBubble should appear on the DayView page
  immediately after returning from creating the event.

  A reproduction of this behavior can be seen at:
  https://www.youtube.com/watch?v=9NK9m8ZznrA&feature=youtu.be

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

-- 
Mailing list: https://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 1452437] Re: 15.04 container does not get an IP address when started

[Christopher Townsend]

This may be an lxc only issue as well, so I'm adding that package to
this bug.

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

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

Title:
  15.04 container does not get an IP address when started

Status in lxc package in Ubuntu:
  New
Status in lxd package in Ubuntu:
  New

Bug description:
  I created a 15.04 container using the following command:

  lxd-images import lxc ubuntu vivid amd64 --alias ubuntu/vivid

  I then start it up by issuing the following command:

  lxc launch ubuntu/vivid tester

  The started container does not obtain an IP address.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxd 0.7-0ubuntu1
  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
  CurrentDesktop: Unity
  Date: Wed May  6 16:22:00 2015
  InstallationDate: Installed on 2013-03-18 (779 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: lxd
  UpgradeStatus: Upgraded to vivid on 2014-10-20 (198 days ago)

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

-- 
Mailing list: https://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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

[Andy Whitcroft]

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

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

Title:
  [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  Fix Released
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Committed
Status in systemd source package in Utopic:
  Confirmed

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions

-- 
Mailing list: https://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 1436405] Re: Duplicate menu (both unity and in-app) for kde apps

[Albert Astals Cid]

do you have appmenu-qt5 installed? it creates some issues when used
outside of unity, but if you're using only unity i think it fixes this
issue.

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

Title:
  Duplicate menu (both unity and in-app) for kde apps

Status in One Hundred Papercuts:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

-- 
Mailing list: https://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 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

[Matthew Paul Thomas]

Specification updated.


** Changed in: network-manager (Ubuntu)
   Status: In Progress => Triaged

** Changed in: network-manager (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

** Description changed:

  On Ubuntu for Phones final image on mako I can see a network but cannot
  connect because I never get prompted for the username/password.
+ 
+ :
+ "In both the ‘Connect to “{network name}”’ and “Connect to Hidden
+ Network” dialogs, the contents of the dialog, and the behavior of the
+ “Connect” button, should vary depending on the security and
+ authentication methods..."

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

Title:
  Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network

Status in the base for Ubuntu mobile products:
  In Progress
Status in network-manager package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  On Ubuntu for Phones final image on mako I can see a network but
  cannot connect because I never get prompted for the username/password.

  :
  "In both the ‘Connect to “{network name}”’ and “Connect to Hidden
  Network” dialogs, the contents of the dialog, and the behavior of the
  “Connect” button, should vary depending on the security and
  authentication methods..."

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

-- 
Mailing list: https://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 1451046] Re: shorten long strings...

[Charles Kerr]

** Changed in: indicator-sound (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  shorten long strings...

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  here's the problem http://i.imgur.com/wKfWUvW.png
  when listening music with audacious the panel's size is too wide

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

-- 
Mailing list: https://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 1436045] Re: (Krillin) Keyboard layout suggests wrong national domain as shortcut

[Launchpad Bug Tracker]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/layout-
improvements

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

Title:
  (Krillin) Keyboard layout suggests wrong national domain as shortcut

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  On BQ Aquaris HD4.5 Ubuntu Edition I found the following bug concerning 
Croatian (hrvatski) keyboard layout,
  when using the keyboard with browser it has a key that suggests domain name 
shortcuts, it suggests .com which is ok, but that key also suggests .ba domain 
as shortcut which is a Bosnian, and not Croatian national domain, the key 
should suggest .com and .hr which is Croatian domain. Not a major issue but 
still it would be nice if it can be fixed.

  Device is fully updated and running 14.10 (r20).

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

-- 
Mailing list: https://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 1436405] Re: Duplicate menu (both unity and in-app) for kde apps

[Egmont Koblinger]

I do have appmenu-qt5 installed. If I remove the package, the menu
inside konsole's window remains, and the one in Unity's top bar
vanishes. Clearly not the direction in which I'd expect the duplicate
menu issue to be resolved.

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

Title:
  Duplicate menu (both unity and in-app) for kde apps

Status in One Hundred Papercuts:
  Confirmed
Status in libdbusmenu-qt package in Ubuntu:
  Confirmed

Bug description:
  At least konsole and khelpcenter suffers from this bug:

  Start the app inside the default Unity environment (not under KDE).
  Notice that the app's menubar appears twice.  Once in the upper row of
  the whole desktop, as expected and as it is for every Gnome app.  And
  also inside the application's window, wasting precious screen real
  estate.

  In Utopic, at least for konsole, I'm quite sure that the menu wasn't
  duplicated inside the app, it only appeared on the desktop's top Unity
  bar.

  (I'm not sure I guessed the component right; please reassign as
  appropriate.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 16:33:14 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: libdbusmenu-qt
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

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

-- 
Mailing list: https://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 1452717] [NEW] Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd

[Lior Goikhburg]

Public bug reported:

Problem happens when choosing a normal boot.
Works ok when choosing upstart.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
 GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Thu May  7 16:05:34 2015
DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed
 bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed
 bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed
 nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed
 nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1742]
InstallationDate: Installed on 2011-11-22 (1261 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: ASUSTeK Computer Inc. K43SJ
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K43SJ.313
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K43SJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0:
dmi.product.name: K43SJ
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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
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 N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May  7 15:41:03 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nouveau" (module does not exist, 0)
 Failed to load module "nouveau" (module does not exist, 0)
 open /dev/fb0: No such file or directory
 open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-bug 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/1452717

Title:
  Xorg doesn't start after upgrade from utopic to vivid, starts ok when
  chosen to boot upstart instead of systemd

Status in xorg package in Ubuntu:
  New

Bug description:
  Problem happens when choosing a normal boot.
  Works ok when choosing upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Thu May  7 16:05:34 2015
  DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed
   nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed
   nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1742]
  InstallationDate: Installed on 2011-11-22 (1261 days ago)
 

Re: [Touch-packages] [Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

[Serge Hallyn]

This is fixed in upstream git HEAD, so you can get the fix from
ppa:ubuntu-lxc/daily.  It should hopefully make its way into the
vivid package soon.

 status: fixcommitted


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

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

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

-- 
Mailing list: https://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 1422143] Re: No wifi connection after suspend with systemd

[Mentis]

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

Happening to me starting from migration to systemd. Haven't seen this on
upstart.

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

Title:
  No wifi connection after suspend with systemd

Status in One Hundred Papercuts:
  Confirmed
Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----   
  
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----   
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 782516] Re: [HDA-Intel - HDA Intel, playback] No sound at all

[dalewilliams]

** Changed in: alsa-driver (Ubuntu)
   Status: New => Fix Committed

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

Title:
  [HDA-Intel - HDA Intel, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed

Bug description:
  when I first did a clean install of Ubuntu 11.04 amd64 my usb microphone 
(Microsoft) was recognised right away and worked flawlessly. (front panel) I 
then removed usb mike and plugged in patch cord to my stereo receiver. No sound 
at all. I know this isn't a hardware problem since windows works perfectly. (I 
triple boot: Windows 7 pro_64 and Windows XP Pro. with Ubuntu).
  I tried several fixes suggested in Ubuntu forums with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: VT1828S Analog [VT1828S Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dangmc 1847 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7ff8000 irq 51'
 Mixer name : 'VIA VT1828S'
 Components : 'HDA:11064441,104383d0,00100100'
 Controls  : 36
 Simple ctrls  : 21
  Date: Fri May 13 21:29:31 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_DevicesInUse: 1847
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D-E
  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.:bvr0806:bd03/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://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 1452729] [NEW] installed applications categories are showing untranslated

[Sebastien Bacher]

Public bug reported:

Using a bq/rtm phone in French, a recent server update included
categories translations and those work in the click store view but not
in the installed application view (the combo at the top of the view)

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  installed applications categories are showing untranslated

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Using a bq/rtm phone in French, a recent server update included
  categories translations and those work in the click store view but not
  in the installed application view (the combo at the top of the view)

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

-- 
Mailing list: https://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 1452727] Re: Very slow start

[Martin Pitt]

Please report bugs with apport ("ubuntu-bug systemd"), you didn't
include any useful information I'm afraid. After booting, please do

  sudo journalctl -b > /tmp/journal.txt

and attach /tmp/journal.txt and your /etc/rc.local. Also include the
status of

  sudo systemctl status -l rc-local.service

Thanks!

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

** Summary changed:

- Very slow start
+ rc-local.service hangs

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

Title:
  rc-local.service hangs

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The boot is very slow more than 130 seconds because of:   1min 8.191s
  rc-local.service... 

  Using upstart works perfectly and fast.

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

-- 
Mailing list: https://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 1452727] [NEW] Very slow start

[Carles]

Public bug reported:

The boot is very slow more than 130 seconds because of:   1min 8.191s
rc-local.service... 

Using upstart works perfectly and fast.

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

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

Title:
  Very slow start

Status in systemd package in Ubuntu:
  New

Bug description:
  The boot is very slow more than 130 seconds because of:   1min 8.191s
  rc-local.service... 

  Using upstart works perfectly and fast.

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

-- 
Mailing list: https://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 1452729] Re: installed applications categories are showing untranslated

[Alejandro J. Cura]

The translated names for departments are downloaded from the server the
first time the "store" scope is opened, and as expected they are stored
in .cache/click-departments.db.

The bug seems to be that the "installed apps" scope is not showing these
translated names. They are only shown after a reboot.

** Changed in: unity-scope-click (Ubuntu)
   Status: New => Confirmed

** Changed in: unity-scope-click (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  installed applications categories are showing untranslated

Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Using a bq/rtm phone in French, a recent server update included
  categories translations and those work in the click store view but not
  in the installed application view (the combo at the top of the view)

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

-- 
Mailing list: https://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 1392437] Re: [design] [snap decisions] incoming call notification swipe looks like buttons

[Launchpad Bug Tracker]

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

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

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

Title:
  [design] [snap decisions] incoming call notification swipe looks like
  buttons

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I think the incoming call notification should be made more obvious that we 
are not dealing with buttons but a swipe.
  The arrows are not enough. Maybe a line in the background could make the 
swipe obvious  like this:

[dismiss]<->[answer].

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

-- 
Mailing list: https://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 1452390] Re: invalid pam rule in vivid is preventing logins

[Steve Langasek]

** Changed in: pam (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: pam (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  invalid pam rule in vivid is preventing logins

Status in pam package in Ubuntu:
  Invalid

Bug description:
  there are problematic pam rules preventing users from logging in (pam
  errors show up with auth.log)

  Other users are reporting this problem online with upgrades but I  can
  confirm this occurs with just new installs in Virtualbox (15.04 amd64)

  please have a look 
  thanks

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

-- 
Mailing list: https://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 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled

[Lars Uebernickel]

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

** Changed in: libtimezonemap (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

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

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

Title:
  WARNING **: Could not connect to geoname lookup server: Operation was
  cancelled

Status in One Hundred Papercuts:
  Confirmed
Status in Unity Control Center:
  New
Status in libtimezonemap package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  Test Case:
  open Date & Time panel > Clock 
  Enable Time in other locations
  Click Choose Locations...

  No other locations can be added

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  CurrentDesktop: Unity
  Date: Fri Apr  3 23:54:13 2015
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1197969] Re: Date and Time config missing cities

[Lars Uebernickel]

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

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Date and Time config missing cities

Status in Ubuntu Geonames:
  New
Status in libtimezonemap package in Ubuntu:
  Invalid
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  Date and Time configuration tool is missing Jerusalem and Tel Aviv,
  making it hard to properly set the current time zone.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: compizconfig-settings-manager 0.9.5.92-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: i386
  Date: Fri Jul  5 00:05:14 2013
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: compizconfig-settings-manager
  UpgradeStatus: Upgraded to precise on 2013-04-14 (80 days ago)

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

-- 
Mailing list: https://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 1437375] Re: [udev] Adding "Austin" adapter to Ubuntu partition take over system network interface

[Mathieu Trudel-Lapierre]

pitti, I had uploaded a day before you committed things to git, seems
like there was a bit of miscommunication before, I had mentioned it on
IRC I believe. In any case, it's good that things are covered in
-proposed now.

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

Title:
  [udev] Adding "Austin" adapter to Ubuntu partition take over system
  network interface

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  This impacts any user of LPARs; upon adding physical network interfaces (or, 
realistically, any network interface at all, even virtual), the network 
interface which is used for system access and used to install the system may 
not appear in the same order after reboot.

  [Test Case]
  Requires access to logical partitions.
  1) Install system
  2) Add an physical network adapter to the partition
  3) Reboot.

  Observed behavior:
  After reboot, the virtual adapter expected to be used is unavailable, the 
address is assigned to any other network adapter which may have been detected 
and used persistent addresses.

  Expected behavior
  The system should come up with network interfaces in the same order as before 
rebooting.

  [Regression Potential]
  Added virtual interfaces that should be not persist (because they are locally 
administered and thus may have their MAC address change) may come up as 
persistent devices due to the use of the ibmveth driver, and thus fail to work 
as expected.

  ---

  Problem Description:
  

  Adding Austin adapter to Ubuntu partition took over system network
  interface.  This caused system to be off network connection.

   ver 1.5.4.3 - OS, HTX, Firmware and Machine details

     OS: GNU/Linux
     OS Version: Ubuntu Vivid Vervet (development branch) \n \l
     Kernel Version: 3.18.0-13-generic
    HTX Version: htxubuntu-322
  Host Name: br14p08
  Machine Serial No: IBM,0210800E7
     Machine Type/Model: IBM,9119-MHE
    System FW Level: FW830.00 (SC830_021)

  BEFORE adding Austin adapter to br14p08:
  

  Before adding austin adapter to br14p05 (vio client), the system
  network is good.

  ubuntu@br14p08:~$ lsslot -cpci
  ubuntu@br14p08:~$

  + eth0 U9119.MHE.10800E7-V8-C2-T1
   Interpartition Logical LAN

  root@br14p08:~# lscfg |grep eth
  + eth0 U9119.MHE.10800E7-V8-C2-T1

  root@br14p08:~# ifconfig
  eth0  Link encap:Ethernet  HWaddr 16:59:c0:50:0a:02
    inet addr:9.3.21.12  Bcast:9.3.21.255  Mask:255.255.254.0
    inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link
    inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:37366 errors:0 dropped:16 overruns:0 frame:0
    TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2472739 (2.4 MB)  TX bytes:22596 (22.5 KB)
    Interrupt:19

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:65536  Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  root@br14p08:~# ping br14p08
  PING br14p08.aus.stglabs.ibm.com (9.3.21.12) 56(84) bytes of data.
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=1 ttl=64 
time=0.008 ms
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=2 ttl=64 
time=0.004 ms
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=3 ttl=64 
time=0.005 ms
  ^C
  --- br14p08.aus.stglabs.ibm.com ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 1998ms
  rtt min/avg/max/mdev = 0.004/0.005/0.008/0.003 ms

  root@br14p08:~# ping nimitz
  PING nimitz.aus.stglabs.ibm.com (9.3.165.31) 56(84) bytes of data.
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=1 ttl=254 
time=0.344 ms
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=2 ttl=254 
time=0.326 ms
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=3 ttl=254 
time=0.363 ms
  ^C

  AFTER ADDED Austin Adapter:
  ===

  Once the Austin adapter added to the partition, the Austin's 1st port became 
eth0.
  and it pushed the virtual ethernet (which is system's ethernet) to be eth4.
  However, the system still loo

Re: [Touch-packages] [Bug 1437375] Re: [udev] Adding "Austin" adapter to Ubuntu partition take over system network interface

[Martin Pitt]

Mathieu Trudel-Lapierre [2015-05-07 14:20 -]:
> pitti, I had uploaded a day before you committed things to git, seems
> like there was a bit of miscommunication before, I had mentioned it on
> IRC I believe. In any case, it's good that things are covered in
> -proposed now.

Ah okay, sorry for the misunderstanding then!

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

Title:
  [udev] Adding "Austin" adapter to Ubuntu partition take over system
  network interface

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  This impacts any user of LPARs; upon adding physical network interfaces (or, 
realistically, any network interface at all, even virtual), the network 
interface which is used for system access and used to install the system may 
not appear in the same order after reboot.

  [Test Case]
  Requires access to logical partitions.
  1) Install system
  2) Add an physical network adapter to the partition
  3) Reboot.

  Observed behavior:
  After reboot, the virtual adapter expected to be used is unavailable, the 
address is assigned to any other network adapter which may have been detected 
and used persistent addresses.

  Expected behavior
  The system should come up with network interfaces in the same order as before 
rebooting.

  [Regression Potential]
  Added virtual interfaces that should be not persist (because they are locally 
administered and thus may have their MAC address change) may come up as 
persistent devices due to the use of the ibmveth driver, and thus fail to work 
as expected.

  ---

  Problem Description:
  

  Adding Austin adapter to Ubuntu partition took over system network
  interface.  This caused system to be off network connection.

   ver 1.5.4.3 - OS, HTX, Firmware and Machine details

     OS: GNU/Linux
     OS Version: Ubuntu Vivid Vervet (development branch) \n \l
     Kernel Version: 3.18.0-13-generic
    HTX Version: htxubuntu-322
  Host Name: br14p08
  Machine Serial No: IBM,0210800E7
     Machine Type/Model: IBM,9119-MHE
    System FW Level: FW830.00 (SC830_021)

  BEFORE adding Austin adapter to br14p08:
  

  Before adding austin adapter to br14p05 (vio client), the system
  network is good.

  ubuntu@br14p08:~$ lsslot -cpci
  ubuntu@br14p08:~$

  + eth0 U9119.MHE.10800E7-V8-C2-T1
   Interpartition Logical LAN

  root@br14p08:~# lscfg |grep eth
  + eth0 U9119.MHE.10800E7-V8-C2-T1

  root@br14p08:~# ifconfig
  eth0  Link encap:Ethernet  HWaddr 16:59:c0:50:0a:02
    inet addr:9.3.21.12  Bcast:9.3.21.255  Mask:255.255.254.0
    inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link
    inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:37366 errors:0 dropped:16 overruns:0 frame:0
    TX packets:153 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2472739 (2.4 MB)  TX bytes:22596 (22.5 KB)
    Interrupt:19

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:65536  Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  root@br14p08:~# ping br14p08
  PING br14p08.aus.stglabs.ibm.com (9.3.21.12) 56(84) bytes of data.
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=1 ttl=64 
time=0.008 ms
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=2 ttl=64 
time=0.004 ms
  64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=3 ttl=64 
time=0.005 ms
  ^C
  --- br14p08.aus.stglabs.ibm.com ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 1998ms
  rtt min/avg/max/mdev = 0.004/0.005/0.008/0.003 ms

  root@br14p08:~# ping nimitz
  PING nimitz.aus.stglabs.ibm.com (9.3.165.31) 56(84) bytes of data.
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=1 ttl=254 
time=0.344 ms
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=2 ttl=254 
time=0.326 ms
  64 bytes from nimitz.aus.stglabs.ibm.com (9.3.165.31): icmp_seq=3 ttl=254 
time=0.363 ms
  ^C

  AFTER ADDED Austin Adapter:
  ===

  Once the Austin adapter added to the partition, the Austin's 1st port became 
eth0.
  an

[Touch-packages] [Bug 1452759] [NEW] departement translations should include all supported locales by default

[Sebastien Bacher]

Public bug reported:

The default db seems to currently include only spanish variants, it
should include translations for all supported languages so the
application categories are translated out of the box in other locales as
well

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  departement translations should include all supported locales by
  default

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  The default db seems to currently include only spanish variants, it
  should include translations for all supported languages so the
  application categories are translated out of the box in other locales
  as well

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

-- 
Mailing list: https://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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles

[Martin Pitt]

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

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

Title:
  apt-get install lxc doesn't load required apparmor profiles

Status in apparmor package in Ubuntu:
  Fix Released
Status in init-system-helpers package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Fix Committed
Status in squid3 package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  I'm trying to use LXC on my openstack instance which runs vivid daily:

  $ sudo apt-get install lxc -y

  $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
  --stream=daily --release=vivid

  $ sudo lxc-start --name vivid --logfile=lxc.log
  lxc-start: lxc_start.c: main: 344 The container failed to start.
  lxc-start: lxc_start.c: main: 346 To get more details, run the container in 
foreground mode.
  lxc-start: lxc_start.c: main: 348 Additional information can be obtained by 
setting the --logfile and --logpriority options.

  In the log file (lxc.log) I observe the following error:
  lxc-start 1426516387.814 ERRORlxc_apparmor - 
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - 
failed to change apparmor profile to lxc-container-default

  This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was
  not loaded appropriately.

  This issue disappears if I:
  (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
  or
  (b) reboot the instance

  I'd expect that 'apt-get install lxc' has to load all appropriate
  apparmor profiles to allow starting containers w/o profile reloading /
  rebooting.

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

-- 
Mailing list: https://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 1452760] [NEW] Unlocking takes up to 30 seconds

[Merlijn Sebrechts]

Public bug reported:

I have this problem a lot on the BQ phone. Please let me know what
information you need from me next time this happens.

When I press the power button to come back from sleep, it can take up to
20 seconds before the screen appears. After that, unlocking the phone
also takes a lot of time, about 5 seconds. Opening the drawer happens
immediately... Most of the time there is only one or two apps open. The
browser has always been open when I had this.

Please let me know what information I need to get next time this
happens!

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

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

Title:
  Unlocking takes up to 30 seconds

Status in unity8 package in Ubuntu:
  New

Bug description:
  I have this problem a lot on the BQ phone. Please let me know what
  information you need from me next time this happens.

  When I press the power button to come back from sleep, it can take up
  to 20 seconds before the screen appears. After that, unlocking the
  phone also takes a lot of time, about 5 seconds. Opening the drawer
  happens immediately... Most of the time there is only one or two apps
  open. The browser has always been open when I had this.

  Please let me know what information I need to get next time this
  happens!

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

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