[Touch-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended

2015-06-02 Thread Jan Rathmann
Yes, the output of 'lsmod|grep alx' is indeed empty.

Since my system doesn't have wifi, I don't think anything WPA related
could be the cause. I ran the commands anyway:

  sudo  wpa_cli suspend ; sudo systemctl suspend; sudo  wpa_cli resume

and it has no positive impact. The output of wpa_cli is:

"Failed to connect to non-global ctrl_ifname: (null)  error: No such
file or directory"


** Attachment added: "pm-suspend.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450396/+attachment/4408960/+files/pm-suspend.log

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

Title:
  Gigabyte P35-DS3: does not stay suspended

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended

2015-06-02 Thread Martin Pitt
OK, then it might be one of the other hooks in /usr/lib/pm-utils/sleep.d
that pm-suspend runs. According to your dmesg it's unlikely that you
have the "alx" module loaded ("lsmod | grep alx" should be empty).

Can you please attach your /var/log/pm-suspend.log?

60_wpa_supplicant could be a likely cause -- can you see if this works:

  sudo  wpa_cli suspend ; sudo systemctl suspend; sudo  wpa_cli resume

75modules is a less likely cause, I'll see if that does anything on your
system in pm-suspend.log. The other hooks seem rather unlikely to me, so
let's check these two first.

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

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

Title:
  Gigabyte P35-DS3: does not stay suspended

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


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

2015-06-02 Thread Jan Rathmann
Benjamin, I don't think the problem is related to a somehow messed up
configuration (user or system wide), because as mentioned in #8, I can
reproduce the bug by booting from a pristine live iso image. Or we a
suffering from different bugs.

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1450396] Re: Gigabyte P35-DS3: does not stay suspended

2015-06-02 Thread Jan Rathmann
I did check it again yesterday and today using 'systemctl suspend'. The
bug does not always happen, e.g. yesterday I was able to suspend my
system 4 or 5 times in a row properly, but tomorrow after the first
attempt the PC woke up again by itself ~2 seconds after I suspended it.
So yes, the bug is still there unfortunately. I have used 'pm-suspend'
almost exclusively during the last two months and this bug never ever
has happened with 'pm-suspend' during that time (or in earlier Ubuntu
releases).

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

Title:
  Gigabyte P35-DS3: does not stay suspended

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  using Suspend-to-RAM on my system has stopped working reliably on
  Vivid when booting with Systemd. When I try to suspend my PC the
  following happens:

  - PC turns off
  - PC unwantedly wakes up (turns on) by itself again. This time span until it 
turns on again can reach from a second (almost immediately) until two or three 
minutes.
  - In a few cases (<25%), the PC stays suspended properly.

  A way to workaround this problem is to boot my PC with Upstart instead
  of Systemd, then this problem never happens (and has never happened in
  any of the previous Ubuntu versions since 2008). Thus it seems to be a
  bug somehow related to Systemd.

  Other steps I have tried to solve the problem (without any success):

  - Checking BIOS settings, all options are set that way that the PC should 
never wake up by any event other than pressing the power button.
  - Checking by running "cat /proc/acpi/wakeup | grep enabled" if any device 
could cause wake up events. This lists my USB controller, but deactivating it 
(with commands like "echo USB0 > /proc/acpi/wakeup") had no success on the 
problem. Also suspend while running Upstart works fine despite the USB 
controller listed as "enabled".

  In the system logs I could see no hint what causes the undesired wake-
  ups.

  Allthough there is one factor which seems to have a certain influence:
  If I close programs like Pidgin, Skype or Firefox that cause
  continuous network traffic, the chance is higher that my PC will stay
  suspened (while runinng Systemd).

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 30 11:24:46 2015
  InstallationDate: Installed on 2015-04-16 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/internal--ssd-root ro rootflags=subvol=@ quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1461386] [NEW] pm-powersave is not triggered when unplugging charger

2015-06-02 Thread Oscar Tiderman
Public bug reported:

Not sure at all which package to file this bug against, hopefully
someone can help me tag the right package. There is no pm-powersave
event triggered when plugging or unplugging my charger, none of the
powersave scripts are therefore triggered. I'm on a Lenovo Yoga 2 Pro.
This must be a regression in Vivid, has worked fine in both Trusty and
Utopic. I can manually run sudo pm-powersave true to trigger the scripts

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pm-utils 1.4.1-15
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Wed Jun  3 07:05:30 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-03-30 (429 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: pm-utils
SystemImageInfo:
 current build number: 0
 device name: ?
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to vivid on 2015-04-30 (33 days ago)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Description changed:

  Not sure at all which package to file this bug against, hopefully
  someone can help me tag the right package. There is no pm-powersave
  event triggered when plugging or unplugging my charger, none of the
  powersave scripts are therefore triggered. I'm on a Lenovo Yoga 2 Pro.
  This must be a regression in Vivid, has worked fine in both Trusty and
- Utopic.
+ Utopic. I can manually run sudo pm-powersave true to trigger the scripts
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Wed Jun  3 07:05:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-30 (429 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  SystemImageInfo:
-  current build number: 0
-  device name: ?
-  channel: daily
-  last update: Unknown
+  current build number: 0
+  device name: ?
+  channel: daily
+  last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (33 days ago)

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

Title:
  pm-powersave is not triggered when unplugging charger

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Not sure at all which package to file this bug against, hopefully
  someone can help me tag the right package. There is no pm-powersave
  event triggered when plugging or unplugging my charger, none of the
  powersave scripts are therefore triggered. I'm on a Lenovo Yoga 2 Pro.
  This must be a regression in Vivid, has worked fine in both Trusty and
  Utopic. I can manually run sudo pm-powersave true to trigger the
  scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Wed Jun  3 07:05:30 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-30 (429 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  SystemImageInfo:
   current build number: 0
   device name: ?
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (33 days ago)

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

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


[Touch-packages] [Bug 1454253] Re: external usb breaks suspend

2015-06-02 Thread Martin Pitt
Thanks for confirming! Reassigning to the kernel then.

** Package changed: systemd (Ubuntu) => linux (Ubuntu)

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

Title:
  external usb breaks suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After booting xubuntu 15.04 it's possible to suspend it the normal way
  BUT - only until you've plugged external usb hard drive. After that
  (even if it was unmounted and removed) it becomes impossible: the
  system goes to suspend briefly (for bout 1 second) but immediately
  wakes up for no apparent reason.

  I suspect there's some weird bug in xfce power management - is there a
  way to disable it alltogether and  rely on systemd directly instead?

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

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


[Touch-packages] [Bug 1461274] Re: dependency cycles

2015-06-02 Thread Martin Pitt
Unfortunately that log only mentions that cycles exist, but not what
they are. Please attach /var/log/syslog, or better yet, run "sudo
journalctl -b > /tmp/journal.txt" and attach /tmp/journal.txt. Thanks!

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

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

Title:
  dependency cycles

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  There are several dependency cycles reported during the boot of
  xubuntu 15.04 x86_64: see attached log.

  Those cycles should be resoled.

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

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


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

2015-06-02 Thread Benjamin Geese
This was getting really annoying, so i simple reinstalled my system
yesterday. I directly installed Ubuntu 15.04. The problem is gone now.
So it must be a configuration. Either something i did which cannot
remember (i can not see a reason is should have fiddled with that), or
something introducing during the 15.05 development process. I still
suspect the timeframe around the systemd switch. It might be helpful to
know that 1) the problem did not exist with 14.04 or 14.10 (upgraded
from 14.04) but 15.04 since systemd switch (upgraded from 14.04, then
14.10).

@kaiserclaudius: sadly did not try to used upstart on this machine, but
we have a second machine with a similar issue, i will try this there as
soon as i find the time.

@carlix: Does Lubuntu use systemd?

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1461259] Re: PCI/internal sound card not detected

2015-06-02 Thread Raymond
*** This bug is a duplicate of bug 1458136 ***
https://bugs.launchpad.net/bugs/1458136

 02 17:14:10 username-Inspiron-5537 kernel: Could not create debugfs 
'i915_pipe_update_vblank_evaded' directory
Jun 02 17:14:10 username-Inspiron-5537 kernel: Could not create debugfs 
'i915_pipe_update_start' directory
Jun 02 17:14:10 username-Inspiron-5537 kernel: snd_hda_intel :00:03.0: 
Cannot turn on display power on i915


** Summary changed:

- PCI/internal sound card not detected
+ PCI/internal sound card not detected - snd_hda_intel :00:03.0: Cannot 
turn on display power on i915

** This bug has been marked a duplicate of bug 1458136
   [MS-7823, Realtek ALC892, Green SPDIF Out, Rear] No sound at all 
snd_hda_intel Cannot turn on display power on i915

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

Title:
  PCI/internal sound card not detected - snd_hda_intel :00:03.0:
  Cannot turn on display power on i915

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  UBUNTU 15.04

  HDMI audio option don`t appears on the sound config, just the video
  works

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabio  1475 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jun  2 17:25:53 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to vivid on 2015-06-02 (0 days ago)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 02T8TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn02T8TW:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron 5537
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1458981] Re: Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH, playback] Playback problem Cannot turn on display power on i915

2015-06-02 Thread Raymond
*** This bug is a duplicate of bug 1458136 ***
https://bugs.launchpad.net/bugs/1458136

** This bug has been marked a duplicate of bug 1458136
   [MS-7823, Realtek ALC892, Green SPDIF Out, Rear] No sound at all 
snd_hda_intel Cannot turn on display power on i915

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

Title:
  Digital Output HDMI not recognized at all: [HDA-Intel - HDA Intel PCH,
  playback] Playback problem Cannot turn on display power on i915

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Digital playback was working just fine. HDMI connected to 32" Vizio
  television from msi Z97 PC Mate Motherboard. Now no digital output,
  not even as an option. Analog audio works just fine. When I plug
  headphones in there is no problem. that is all identified in Settings
  panel and terminal commands used for troubleshooting. but the HDMI
  output does not appear to be recognized as everything says Analog.
  Ubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canibal2344 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 26 14:59:34 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-05 (293 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-04-26 (30 days ago)
  dmi.bios.date: 04/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd04/18/2014:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7850
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Touch-packages] [Bug 829581] Re: package initramfs-tools 0.99ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-06-02 Thread Perez Karuhaga
** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => Fix Released

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

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

Title:
  package initramfs-tools 0.99ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in tools for generating an initramfs:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  shut on on boot.

  ProblemType: Package
  DistroRelease: Ubuntu 11.10
  Package: initramfs-tools 0.99ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic i686
  Architecture: i386
  Date: Wed Aug 17 07:11:19 2011
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.99ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to oneiric on 2011-08-18 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/829581/+subscriptions

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


[Touch-packages] [Bug 1437512] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem

2015-06-02 Thread Raymond
12826.925350] WARNING: CPU: 1 PID: 1971 at 
/build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:4203 
intel_modeset_check_state+0x6b8/0x750 [i915]()
[12826.925354] Modules linked in: cuse ccm deflate ctr twofish_generic 
twofish_i586 twofish_common camellia_generic serpent_sse2_i586 xts 
serpent_generic lrw gf128mul glue_helper ablk_helper cryptd blowfish_generic 
blowfish_common cast5_generic cast_common des_generic cmac xcbc rmd160 
crypto_null af_key xfrm_algo rfcomm bnep binfmt_misc snd_hda_codec_idt 
snd_hda_codec_hdmi gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas 
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi 
snd_seq_midi_event snd_rawmidi coretemp joydev snd_seq r852 serio_raw arc4 
sm_common snd_seq_device nand iwl3945 nand_ecc snd_timer iwlegacy nand_bch bch 
mac80211 nand_ids mtd snd lpc_ich r592 cfg80211 btusb bluetooth i915 memstick 
wmi drm_kms_helper mac_hid drm soundcore video i2c_algo_bit parport_pc shpchp 
ppdev lp parport hid_generic usbhid hid psmouse ahci sdhci_pci firewire_ohci 
libahci firewire_core pata_acpi sdhci crc_itu_t sky2
[12826.925500] CPU: 1 PID: 1971 Comm: Xorg Tainted: GW 
3.13.0-48-generic #80-Ubuntu
[12826.925504] Hardware name: Dell Inc. Inspiron 1525   
/0U990C, BIOS A13 06/27/2008
[12826.925508]    e700bd40 c1655f92  e700bd70 c1056a7e 
c1833268
[12826.925522]  0001 07b3 f8c4bb64 106b f8c03af8 f8c03af8 e8025c00 

[12826.925536]  e80241c0 e700bd80 c1056b42 0009  e700bdd4 f8c03af8 
f8c4bb64
[12826.925550] Call Trace:
[12826.925558]  [] dump_stack+0x41/0x52
[12826.925567]  [] warn_slowpath_common+0x7e/0xa0
[12826.925614]  [] ? intel_modeset_check_state+0x6b8/0x750 [i915]
[12826.925658]  [] ? intel_modeset_check_state+0x6b8/0x750 [i915]
[12826.925666]  [] warn_slowpath_null+0x22/0x30
[12826.925711]  [] intel_modeset_check_state+0x6b8/0x750 [i915]
[12826.925726]  [] ? __wake_up_locked+0x1f/0x30
[12826.925770]  [] ? intel_crtc_update_dpms+0x67/0x90 [i915]
[12826.925815]  [] intel_connector_dpms+0x58/0x60 [i915]
[12826.925847]  [] drm_mode_obj_set_property_ioctl+0x39a/0x3c0 [drm]
[12826.925855]  [] ? __wake_up_sync_key+0x47/0x50
[12826.925886]  [] ? drm_mode_obj_set_property_ioctl+0x3c0/0x3c0 [drm]
[12826.925918]  [] drm_mode_connector_property_set_ioctl+0x33/0x40 
[drm]
[12826.925943]  [] drm_ioctl+0x472/0x500 [drm]
[12826.925981]  [] ? drm_mode_obj_set_property_ioctl+0x3c0/0x3c0 [drm]
[12826.925992]  [] ? sysfs_notify_dirent+0x51/0x70
[12826.925998]  [] ? sysfs_notify+0x3f/0x80
[12826.926006]  [] ? backlight_generate_event+0x4a/0x60
[12826.926014]  [] ? brightness_store+0x9f/0xe0
[12826.926021]  [] ? __kmalloc+0x49/0x1e0
[12826.926045]  [] ? drm_free_buffer+0x30/0x30 [drm]
[12826.926053]  [] do_vfs_ioctl+0x2e2/0x4d0
[12826.926061]  [] ? lockref_put_or_lock+0xb/0x30
[12826.926068]  [] ? dput+0x48/0x150
[12826.926075]  [] ? mntput+0x1d/0x30
[12826.926082]  [] ? __fput+0x155/0x210
[12826.926089]  [] SyS_ioctl+0x60/0x80
[12826.926097]  [] sysenter_do_call+0x12/0x12
[12826.926102] ---[ end trace df38ab00e22f1850 ]--

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

Title:
  [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  system goes into power save mode on AC,
  resuming from login screen
  keboard unmute does not unmute alsa control SPEAKER
  master, PCM will unmute.

  power save mode adds undesired MUTE of alsa's speaker

  expected power manager to not mute speaker only MASTER PCM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic i686
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kiera  2273 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 27 19:30:10 2015
  InstallationDate: Installed on 2014-04-21 (340 days ago)
  InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140205)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to trusty on 2015-03-24 (3 days ago)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA

[Touch-packages] [Bug 1437512] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem

2015-06-02 Thread Raymond
why do the output of alsa-info (speaker not working) missing many
important info (e.g.alsactl,..amixer, sysfs pin cfg) ?

it is normal the speaker is muted when either one of the headphone jack
is plugged


control.36 {
iface CARD
name 'Front Headphone Front Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
control.37 {
iface CARD
name 'Front Headphone Surround Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}

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

Title:
  [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] unmute problem

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  system goes into power save mode on AC,
  resuming from login screen
  keboard unmute does not unmute alsa control SPEAKER
  master, PCM will unmute.

  power save mode adds undesired MUTE of alsa's speaker

  expected power manager to not mute speaker only MASTER PCM

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic i686
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kiera  2273 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 27 19:30:10 2015
  InstallationDate: Installed on 2014-04-21 (340 days ago)
  InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140205)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to trusty on 2015-03-24 (3 days ago)
  dmi.bios.date: 06/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd06/27/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1450009] Re: suspends on closed lid, does not recognized external monitors/dock

2015-06-02 Thread Alberto Salvia Novella
** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  suspends on closed lid, does not recognized external monitors/dock

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using systemd as init system on a HP zbook15 notebook having 2 external 
monitors connected using a docking station and starting with lid closed the 
system goes to sleep after successfully booting and starting lightdm greeter. 
Sometimes there's enough time to enter username and password but system goes to 
sleep every time after a few seconds.
  The system can be woken up and used after this happens but it will not let me 
shutdown later.

  The problem is just present in docked situation starting with closed
  lid using systemd a init system.

  If notebook is used in non-docked situation with open lid and systemd
  the problem does not occur.

  Workaround: A switch back to upstart as init system resolves the
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd-sysv 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 29 14:46:09 2015
  InstallationDate: Installed on 2015-04-27 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

2015-06-02 Thread Erick Brunzell
Hi Tim, I assume that Nautilus (or Caja in the case of Ubuntu Mate) is
actually responsible for the "media already mounted" warning because if
you open dconf-editor and go to "org/gnome/desktop/media-handling" (or
"org/mate/desktop/media-handling") and change both "automount" and
"automount-open" to false then the "media already mounted" warning goes
away. The downside is that doing so interferes with mounting usb drives,
cameras, etc so it's not a truly viable workaround.

The descriptions in dconf certainly mention Nautilus and Caja
specifically:

If set to true, then Nautilus will automatically mount media such as
user-visible hard disks and removable media on start-up and media
insertion.

If set to true, then Nautilus will automatically open a folder when
media is automounted. This only applies to media where no known
x-content/* type was detected; for media where a known x-content type is
detected, the user configurable action will be taken instead.

If set to true, then Caja will automatically mount media such as user-
visible hard disks and removable media on start-up and media insertion.

If set to true, then Caja will automatically open a folder when media is
automounted. This only applies to media where no known x-content/* type
was detected; for media where a known x-content type is detected, the
user configurable action will be taken instead.

So I really assume that some file managers (Nautilus, Caja, and possibly
Nemo) attempt to mount the blank media after gvfs has already mounted it
and therefore produce that warning. I'll grant you that it's only a
cosmetic issue but it's certainly one of those bugs that just shouts
"not ready for prime time" and sends users looking elsewhere for a
reliable distro.

I'd think there'd be a way to have Nautilus and Caja just see if media
is already mounted by gvfs and if so say nothing rather than displaying
a useless and meaningless warning.

Since this does also effect the Mate DE I took the liberty of
subscribing Martin Wimpress, so apologies in advance to Martin. My
intention is not to be pushy but only to inform.

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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

[Touch-packages] [Bug 1320292] Re: ABI incompatibility between POWER and Z HTM builtins and intrinsics

2015-06-02 Thread Peter Bergner
Sorry, verified with "gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)".

** 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 gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1320292

Title:
  ABI incompatibility between POWER and Z HTM builtins and intrinsics

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gcc-4.8 source package in Trusty:
  Fix Committed
Status in gcc-4.9 source package in Trusty:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  Fix Released
Status in gcc-4.8 source package in Utopic:
  Fix Released
Status in gcc-4.9 source package in Utopic:
  Fix Released
Status in gccgo-4.9 source package in Utopic:
  Invalid

Bug description:
  The IBM XL team defined a set of HTM intrinsic functions that were supposed
  to be API compatible across the XL and GCC compilers on both Power and S390.
  PR61193 describes an issue where the functions that begin a transaction
  are incompatible.  The Power intrinsics return non-zero on success, while
  the S390 intrinsics return zero on success.

  After discussing this with the XL compiler team, the S390 GCC team and
  the Power GCC team, we have decided to leave the incompatibility between
  Power and S390.  However, the XL and GCC compilers will be compatible
  with each other when targeting the same processor target.  To mitigate
  the incompatibility somewhat, we have decided to add a macro to the
  powerpc*-linux's htmintrin.h file that defines what the "successful"
  return status value of the __TM_simple_begin() and __TM_begin() intrinsic
  function is.  This macro is already defined in the S390's htmintrin.h
  header file and is used by the S390 to determine whether the transaction
  was successfully started or not.  By adding the same macro on Power, we
  allow users to write common code between Power and S390, even though our
  successful return status values are different.

  For example, the following code can be used on Power and S390, even
  though the actual value returned by __TM_simple_begin() is different.

if ((tx_state = __TM_simple_begin ()) == _HTM_TBEGIN_STARTED)
  {
/* Transaction State Initiated.  */
...
  }
else
  {
/* Transaction State Failed.  */
...
  }

  David approved this offline, so I'm committing this to GCC mainline as
  revision 210486, as well as the 4.9 (210487) and 4.8 (210488)
  branches.

  Peter

PR target/61193
* config/rs6000/htmxlintrin.h (_HTM_TBEGIN_STARTED): New define.
(__TM_simple_begin): Use it.
(__TM_begin): Likewise.

  Index: gcc/config/rs6000/htmxlintrin.h
  ===
  --- gcc/config/rs6000/htmxlintrin.h   (revision 210485)
  +++ gcc/config/rs6000/htmxlintrin.h   (working copy)
  @@ -46,12 +46,17 @@ extern "C" {

   typedef char TM_buff_type[16];

  +/* Compatibility macro with s390.  This macro can be used to determine
  +   whether a transaction was successfully started from the __TM_begin()
  +   and __TM_simple_begin() intrinsic functions below.  */
  +#define _HTM_TBEGIN_STARTED 1
  +
   extern __inline long
   __attribute__ ((__gnu_inline__, __always_inline__, __artificial__))
   __TM_simple_begin (void)
   {
 if (__builtin_expect (__builtin_tbegin (0), 1))
  -return 1;
  +return _HTM_TBEGIN_STARTED;
 return 0;
   }

  @@ -61,7 +66,7 @@ __TM_begin (void* const TM_buff)
   {
 *_TEXASRL_PTR (TM_buff) = 0;
 if (__builtin_expect (__builtin_tbegin (0), 1))
  -return 1;
  +return _HTM_TBEGIN_STARTED;
   #ifdef __powerpc64__
 *_TEXASR_PTR (TM_buff) = __builtin_get_texasr ();
   #else

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

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


[Touch-packages] [Bug 1322287] Re: HTM __builtin_ttest rtl expansion uses wrong shift amount

2015-06-02 Thread Peter Bergner
Sorry, verified with "gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6)".

** 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 gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1322287

Title:
  HTM __builtin_ttest rtl expansion uses wrong shift amount

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Committed

Bug description:
  There is a semi-latent bug for the HTM ttest pattern used with the
  __builtin_ttest() builtin.  This is supposed to expand to a tabortwci.
  instruction which sets cr0 and then some code that copies the cr0 value
  into a gpr and then shifts and masks it into the lowest 2 bits in the gpr.
  The mfcr and mfocrf instructions which can be used to copy the CR0 value
  into a gpr, both copy the value into bits 32-35 of the gpr.  The bug is
  that we only shift the gpr 24 bits to get the CR value into the low
  order bits of the gpr, when we should be shifting 28 bits.  This "works"
  most of the time due to a peculiarity in how the mfocrf instruction
  works, since it copies the CR value into bits 32-35 and duplicates
  that value in bits 36-39.  Since newish -mcpu targets (eg, power8)
  normally generate a mfocrf, we don't see the problem.  However, in some
  cases, we will instead generate a mfcr instruction, which does expose
  the bug.

  This bug was reported upstream with a patch here:

  https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01667.html

  ...and has been fixed upstream in trunk and the FSF 4.9 and FSF 4.8
  branches, as revisions 210815, 210817 and 210818 respectively.

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

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


[Touch-packages] [Bug 1320292] Re: ABI incompatibility between POWER and Z HTM builtins and intrinsics

2015-06-02 Thread Peter Bergner
I can verify that this is fixed.

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

Title:
  ABI incompatibility between POWER and Z HTM builtins and intrinsics

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.9 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gcc-4.8 source package in Trusty:
  Fix Committed
Status in gcc-4.9 source package in Trusty:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  Fix Released
Status in gcc-4.8 source package in Utopic:
  Fix Released
Status in gcc-4.9 source package in Utopic:
  Fix Released
Status in gccgo-4.9 source package in Utopic:
  Invalid

Bug description:
  The IBM XL team defined a set of HTM intrinsic functions that were supposed
  to be API compatible across the XL and GCC compilers on both Power and S390.
  PR61193 describes an issue where the functions that begin a transaction
  are incompatible.  The Power intrinsics return non-zero on success, while
  the S390 intrinsics return zero on success.

  After discussing this with the XL compiler team, the S390 GCC team and
  the Power GCC team, we have decided to leave the incompatibility between
  Power and S390.  However, the XL and GCC compilers will be compatible
  with each other when targeting the same processor target.  To mitigate
  the incompatibility somewhat, we have decided to add a macro to the
  powerpc*-linux's htmintrin.h file that defines what the "successful"
  return status value of the __TM_simple_begin() and __TM_begin() intrinsic
  function is.  This macro is already defined in the S390's htmintrin.h
  header file and is used by the S390 to determine whether the transaction
  was successfully started or not.  By adding the same macro on Power, we
  allow users to write common code between Power and S390, even though our
  successful return status values are different.

  For example, the following code can be used on Power and S390, even
  though the actual value returned by __TM_simple_begin() is different.

if ((tx_state = __TM_simple_begin ()) == _HTM_TBEGIN_STARTED)
  {
/* Transaction State Initiated.  */
...
  }
else
  {
/* Transaction State Failed.  */
...
  }

  David approved this offline, so I'm committing this to GCC mainline as
  revision 210486, as well as the 4.9 (210487) and 4.8 (210488)
  branches.

  Peter

PR target/61193
* config/rs6000/htmxlintrin.h (_HTM_TBEGIN_STARTED): New define.
(__TM_simple_begin): Use it.
(__TM_begin): Likewise.

  Index: gcc/config/rs6000/htmxlintrin.h
  ===
  --- gcc/config/rs6000/htmxlintrin.h   (revision 210485)
  +++ gcc/config/rs6000/htmxlintrin.h   (working copy)
  @@ -46,12 +46,17 @@ extern "C" {

   typedef char TM_buff_type[16];

  +/* Compatibility macro with s390.  This macro can be used to determine
  +   whether a transaction was successfully started from the __TM_begin()
  +   and __TM_simple_begin() intrinsic functions below.  */
  +#define _HTM_TBEGIN_STARTED 1
  +
   extern __inline long
   __attribute__ ((__gnu_inline__, __always_inline__, __artificial__))
   __TM_simple_begin (void)
   {
 if (__builtin_expect (__builtin_tbegin (0), 1))
  -return 1;
  +return _HTM_TBEGIN_STARTED;
 return 0;
   }

  @@ -61,7 +66,7 @@ __TM_begin (void* const TM_buff)
   {
 *_TEXASRL_PTR (TM_buff) = 0;
 if (__builtin_expect (__builtin_tbegin (0), 1))
  -return 1;
  +return _HTM_TBEGIN_STARTED;
   #ifdef __powerpc64__
 *_TEXASR_PTR (TM_buff) = __builtin_get_texasr ();
   #else

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

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


[Touch-packages] [Bug 1322287] Re: HTM __builtin_ttest rtl expansion uses wrong shift amount

2015-06-02 Thread Peter Bergner
I can verify this is fixed.

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

Title:
  HTM __builtin_ttest rtl expansion uses wrong shift amount

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Committed

Bug description:
  There is a semi-latent bug for the HTM ttest pattern used with the
  __builtin_ttest() builtin.  This is supposed to expand to a tabortwci.
  instruction which sets cr0 and then some code that copies the cr0 value
  into a gpr and then shifts and masks it into the lowest 2 bits in the gpr.
  The mfcr and mfocrf instructions which can be used to copy the CR0 value
  into a gpr, both copy the value into bits 32-35 of the gpr.  The bug is
  that we only shift the gpr 24 bits to get the CR value into the low
  order bits of the gpr, when we should be shifting 28 bits.  This "works"
  most of the time due to a peculiarity in how the mfocrf instruction
  works, since it copies the CR value into bits 32-35 and duplicates
  that value in bits 36-39.  Since newish -mcpu targets (eg, power8)
  normally generate a mfocrf, we don't see the problem.  However, in some
  cases, we will instead generate a mfcr instruction, which does expose
  the bug.

  This bug was reported upstream with a patch here:

  https://gcc.gnu.org/ml/gcc-patches/2014-05/msg01667.html

  ...and has been fixed upstream in trunk and the FSF 4.9 and FSF 4.8
  branches, as revisions 210815, 210817 and 210818 respectively.

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

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


[Touch-packages] [Bug 1461335] [NEW] not sure what to do

2015-06-02 Thread Marco Avallone
*** This bug is a security vulnerability ***

Public security bug reported:

I am not sure I thought I just run a debugger.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jun  2 20:19:09 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Device [104d:8207]
   Subsystem: Sony Corporation Device [104d:8207]
InstallationDate: Installed on 2015-06-01 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
MachineType: Sony Corporation VGN-TXN17P
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=dbf9a87f-089c-4261-8c66-6dbc79471935 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0032N3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0032N3:bd04/11/2007:svnSonyCorporation:pnVGN-TXN17P:pvrJ002KQBA:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-TXN17P
dmi.product.version: J002KQBA
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Jun  2 18:20:22 2015
xserver.configfile: default
xserver.devices:
 inputSony Vaio Keys   KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputAlpsPS/2 ALPS GlidePoint TOUCHPAD, id 9
 inputALPS PS/2 Device MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

** Information type changed from Public to Public Security

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

Title:
  not sure what to do

Status in xorg package in Ubuntu:
  New

Bug description:
  I am not sure I thought I just run a debugger.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun  2 20:19:09 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:8207]
 Subsystem: Sony Corporation Device [104d:8207]
  InstallationDate: Installed on 2015-06-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Sony Corporation VGN-TXN17P
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=dbf9a87f-089c-4261-8c66-6dbc79471935 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log

[Touch-packages] [Bug 1458231] Re: Using displayport with external monitor flickers laptop screen

2015-06-02 Thread Christopher M. Penalver
maKA, to see if this is already resolved in a later version of Ubuntu,
could you please test http://cdimage.ubuntu.com/daily-live/current/ and
advise to the results?

** Tags removed: bios-outdated-1.45
** Tags added: latest-bios-1.45

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

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

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

Title:
  Using displayport with external monitor flickers laptop screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using a displayport link to connect with my external monitor causes
  heavy flickering on my laptop screen. Especially when the external
  monitor is being used. There is also a delay of refresh on the
  external monitor... I can see my mouse appear multiple times when I
  move the cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 23 15:44:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21d1]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21d1]
  InstallationDate: Installed on 2015-05-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo 
Integrated Camera (0.3MP)
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4242DT6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=6ccdd4eb-99eb-4e91-9475-83b0b6ec953b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242DT6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242DT6:pvrThinkPadT520:rvnLENOVO:rn4242DT6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242DT6
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May 23 10:47:36 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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1454989] Re: Freeze after boot

2015-06-02 Thread Christopher M. Penalver
anders, this is not Fix Released as defined in
https://wiki.ubuntu.com/Bugs/Status .

** Changed in: xorg (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  Freeze after boot

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Sometimes I will get the screen seen on the attached picture if i leave the PC
  idle for some time after boot. The image changes when pressing a key on the 
keyboard.

  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 i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,snap,regex,place,grid,resize,compiztoolbox,gnomecompat,mousepoll,move,animation,workarounds,vpswitch,imgpng,expo,session,wall,unitymtgrabhandles,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 14 10:09:48 2015
  DistUpgraded: 2015-04-23 19:53:08,580 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:01f2]
  InstallationDate: Installed on 2011-08-31 (1351 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: Dell Inc. Inspiron 1720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=bc46b217-a77a-490e-8b25-9fe396966dca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (20 days ago)
  dmi.bios.date: 08/16/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0UK437
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/16/2007:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK437:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1720
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1

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

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


[Touch-packages] [Bug 1437042] Re: xorg many call traces on dell1525

2015-06-02 Thread Christopher M. Penalver
Galen Thurber, as per http://www.dell.com/support/home/us/en/19/product-
support/product/inspiron-1525/drivers an update to your computer's buggy
and outdated BIOS is available (A17). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status Confirmed.

Thank you for your understanding.

** Tags added: bios-outdaed-a17

** Description changed:

  after updating from 12.0.5 to 14.04 xorg is causing many
  call traces on startup and shutdown
  
  computer not causing call traces under linux lite 2.2, sparky [debian8]
- 
  
  [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 
3.13.0-48-generic #80-Ubuntu
  [73852.453547] Hardware name: Dell Inc. Inspiron 1525   
/0U990C, BIOS A13 06/27/2008
  [73852.453550]    e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 
c1056a7e f8c2ccfc
  [73852.453559]  e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d 
e4937000 e48305c0
  [73852.453569]   e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc 
e3f8fbb4 e3f8fbf4
  [73852.453578] Call Trace:
  [73852.453587]  [] dump_stack+0x41/0x52
  [73852.453594]  [] warn_slowpath_common+0x7e/0xa0
  [73852.453629]  [] ? intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453659]  [] ? intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453664]  [] warn_slowpath_fmt+0x33/0x40
  [73852.453696]  [] intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453731]  [] intel_set_mode+0x30/0x40 [i915]
  [73852.453761]  [] intel_release_load_detect_pipe+0xc4/0xf0 [i915]
  [73852.453806]  [] intel_tv_detect+0x34d/0x510 [i915]
  [73852.453818]  [] ? i2c_transfer+0x11/0xc0
  [73852.453829]  [] 
drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper]
  [73852.453841]  [] ? mutex_lock+0x10/0x28
  [73852.453875]  [] drm_mode_getconnector+0x32d/0x390 [drm]
  [73852.453902]  [] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
  [73852.453920]  [] drm_ioctl+0x472/0x500 [drm]
  [73852.453947]  [] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
  [73852.453956]  [] ? __switch_to_xtra+0xfe/0x130
  [73852.453963]  [] ? set_next_entity+0xb1/0xe0
  [73852.453970]  [] ? __switch_to+0x2c0/0x340
  [73852.453987]  [] ? drm_free_buffer+0x30/0x30 [drm]
  [73852.453995]  [] do_vfs_ioctl+0x2e2/0x4d0
  [73852.454000]  [] ? __schedule+0x358/0x770
  [73852.454007]  [] ? lockref_put_or_lock+0xb/0x30
  [73852.454013]  [] ? __fput+0x155/0x210
  [73852.454018]  [] SyS_ioctl+0x60/0x80
  [73852.454023]  [] sysenter_do_call+0x12/0x12
  [73852.454027] ---[ end trace 1e49de400e8e1259 ]---
  
- 
-  example
+  example
  [73852.453544] CPU: 0 PID: 1970 Comm: Xorg Tainted: GW 
3.13.0-48-generic #80-Ubuntu
  [73852.453547] Hardware name: Dell Inc. Inspiron 1525   
/0U990C, BIOS A13 06/27/2008
  [73852.453550]    e3f8fb58 c1655f92 e3f8fb98 e3f8fb88 
c1056a7e f8c2ccfc
  [73852.453559]  e3f8fbb4 07b2 f8c2ab64 2413 f8be2a1d f8be2a1d 
e4937000 e48305c0
  [73852.453569]   e3f8fba0 c1056ad3 0009 e3f8fb98 f8c2ccfc 
e3f8fbb4 e3f8fbf4
  [73852.453578] Call Trace:
  [73852.453587]  [] dump_stack+0x41/0x52
  [73852.453594]  [] warn_slowpath_common+0x7e/0xa0
  [73852.453629]  [] ? intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453659]  [] ? intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453664]  [] warn_slowpath_fmt+0x33/0x40
  [73852.453696]  [] intel_modeset_check_state+0x5dd/0x750 [i915]
  [73852.453731]  [] intel_set_mode+0x30/0x40 [i915]
  [73852.453761]  [] intel_release_load_detect_pipe+0xc4/0xf0 [i915]
  [73852.453806]  [] intel_tv_detect+0x34d/0x510 [i915]
  [73852.453818]  [] ? i2c_transfer+0x11/0xc0
  [73852.453829]  [] 
drm_helper_probe_single_connector_modes+0x1d8/0x360 [drm_kms_helper]
  [73852.453841]  [] ? mutex_lock+0x10/0x28
  [73852.453875]  [] drm_mode_getconnector+0x32d/0x390 [drm]
  [73852.453902]  [] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
  [73852.453920]  [] drm_ioctl+0x472/0x500 [drm]
  [73852.453947]  [] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
  [73852.453956]  [] ? __switch_to_xtra+0xfe/0x130
  [73852.453963]  [] ? set_next_entity+0xb1/0xe0
  [73852.453970]  [] ? __switch_to+0x2c0/0x340
  [73852.453987]  [] ? drm_free_buffer+0x30/0x30 [drm]
  [73852.453995]  [] do_vfs_ioctl+0x2e2/0x4d0
  [73852.454000]  [] ? __schedule+0x358/0x770
  [73852.454007]  [] ? lockref_put_or_lock+0xb/0x30
  [73852.454013]  [] ? __fput+0x155/0x210
  [73852.454018]  [] SyS_ioctl+0x

[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

2015-06-02 Thread Tim
Lance,
  I think I mentioned this before, Nautilus does not handle the mounting, I 
don't think its some other process causing the additional mount.

Nautilus just displays the mounted gVolume's, those themeselves come from GIO 
Volume Monitor.
GIO Volume Monitor is basically a wrapper around the gvfs udisks2 volume 
monitor.

When you insert a disc, udisks2 will signal gvfs that disc was inserted,
gvfs will look at the disc, add it to the volume monitor. and decide if
it should be automounted (possibly with help from gio), mount it and add
it to the volume monitor.

so I would guess the bug is most likely in gvfs or GIO

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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


[Touch-packages] [Bug 1376996] Re: test_customised_proxy_classes_have_extension_classes started failing all of a sudden

2015-06-02 Thread Christopher Lee
** 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 autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1376996

Title:
  test_customised_proxy_classes_have_extension_classes started failing
  all of a sudden

Status in Autopilot:
  In Progress
Status in autopilot package in Ubuntu:
  New
Status in autopilot source package in Vivid:
  Fix Committed

Bug description:
  The test
  
"autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_customised_proxy_classes_have_extension_classes"
  is now failing (but was passing when CI ran it when it was merged.)

  [Impact]

   * The autopilot self test started failing outlining an issue.

   * justification: Ensures that autopilot remains correct and this test
  failing will outline any regression from anything else.

   * This fix improves confidence that this functionality is correct and
  working as expected.

  [Test Case]

   * To reproduce this bug:
  - Install the current python3-autopilot (apt-get install 
python3-autopilot python-windowmocker)
  - run this test (using the following command):
$ python3 -m autopilot.run run 
autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_customised_proxy_classes_have_extension_classes

   - With the fixed version this test will pass.

  [Regression Potential]

   * This test starts failing again indicating that there is an issue
  either with the selftest itself or the functionality is incorrect.
  Potentially causing application autopilot tests to exhibit the
  behaviour they see today (before fix).

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

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


[Touch-packages] [Bug 1454173] Re: Assertion crash with "ExecStart=- /path"

2015-06-02 Thread Brian Murray
Hello Erkan, or anyone else affected,

Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  Assertion crash with "ExecStart=- /path"

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

Bug description:
  We simple crash systemd by

  
  # cat /etc/systemd/system/crash.service 
  [Unit]
  Description = Crash Me

  [Service]

  ExecStartPre =- /usr/bin/printf pre
  ExecStart= /usr/bin/printf  MAIN

  
  # systemctl daemon-reload
  # systemctl start crash

  Broadcast message from systemd-journald@infra2 (Tue 2015-05-12
  09:28:18 UTC):

  systemd[1]: Caught , dumped core as pid 4471.

  
  Broadcast message from systemd-journald@infra2 (Tue 2015-05-12 09:28:18 UTC):

  systemd[1]: Freezing execution.

  Failed to start crash.service: Connection reset by peer

  
  Jeah.
  It is all because of the Typo in ExecStartPre.

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

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


[Touch-packages] [Bug 1444402] Re: LXC with r/w sys and udev keeps trying to unmount bind mounts

2015-06-02 Thread Brian Murray
Hello Iain, or anyone else affected,

Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  LXC with r/w sys and udev keeps trying to unmount bind mounts

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

Bug description:
  I recently hit ENOSPC which turned out to be the result of various
  syslogs from the current and previous boots totalling up to 30G.

  They were filled with messages like

  Apr 15 11:22:35 vivid systemd[1]: Unit 
var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount
 is bound to inactive unit 
dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. 
Stopping, too.
  Apr 15 11:22:35 vivid systemd[1]: Unmounting 
/var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734...
  Apr 15 11:22:35 vivid umount[31795]: umount: 
/var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734:
 target is busy
  Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about 
processes that
  Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or 
fuser(1).)
  Apr 15 11:22:35 vivid systemd[1]: 
var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount
 mount process exited, code=exited status=32
  Apr 15 11:22:35 vivid systemd[1]: Failed unmounting 
/var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734.
  Apr 15 11:22:35 vivid systemd[1]: Unit 
var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount
 is bound to inactive unit 
dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. 
Stopping, too.
  Apr 15 11:22:35 vivid systemd[1]: Unmounting 
/var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734...
  Apr 15 11:22:35 vivid systemd[1]: Unmounted 
/var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734.
  Apr 15 11:22:35 vivid systemd[1]: Unit 
var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount
 entered failed state.

  looping constantly for the duration of any builds in sbuild.

  Why is systemd trying to do this?

  SRU TEST CASE:
  --
   - Create a vivid container, and set "lxc.aa_profile = unconfined" and 
"lxc.mount.auto = sys:rw cgroup" in its config. (Note that the latter is not 
supported!)
   - Start the container
   - Run "mount -v -o bind /bin /mnt"
   - Observe that it doesn't stay mounted, but "sudo journalctl" says

  Mai 06 09:17:08 test systemd[1]: Unit mnt.mount is bound to inactive unit 
dev-sda3.device. Stopping, too.
  Mai 06 09:17:08 test systemd[1]: Unmounting /mnt...
  Mai 06 09:17:08 test systemd[1]: Unmounted /mnt.

   - With the fixed package bind mounts stay mounted.

  REGRESSION POTENTIAL: This could potentially break cleanup of stale
  mount points of either hotplug devices which disappear, or media which
  get forcefully ejected (like CDs). Testing should include that these
  still work.

  laney@vivid> apt-cache policy systemd
  systemd:
    Installed: 219-7ubuntu1
    Candidate: 219-7ubuntu1
    Version table:
   *** 219-7ubuntu1 0
  500 http://sherwood/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers

2015-06-02 Thread Brian Murray
Hello Martin, or anyone else affected,

Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  journal is broken in unprivileged LXC and nspawn containers

Status in lxc package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Vivid:
  Fix Committed
Status in systemd source package in Wily:
  Fix Released

Bug description:
  Test case
  -
  - Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in 
https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-containers/
  - Boot it. You'll get a lot of errors like

    [FAILED] Failed to start Journal Service.
    systemd-journald-audit.socket failed to listen on sockets: Operation not 
permitted
    [FAILED] Failed to listen on Journal Audit Socket.

  - The same happens with systemd-nspawn -b.

  As a result, the journal isn't working at all, and you have a bunch of
  failed journal related units.

  With a fixed systemd package, systemd in the container should realize
  that it cannot listen to the audit socket (as the kernel doesn't allow
  that -- the audit subsystem isn't fit for namespaces right now), and
  "sudo journalctl" should show the journal and systemd-journald.service
  should be running. These systemd fixes are sufficient for nspawn, but
  not completely for unprivileged LXC containers -- there the journal
  will start working, but systemd-journald-audit.socket will still keep
  failing (this is less important)

  REGRESSION POTENTIAL: Very low. This only affects the fallback error
  code path if binding to the audit socket failed. In that case the
  journal is currently not working at all. This usually doesn't happen
  on real iron/VMs (they also always CAP_AUDIT_READ), so there is no
  practical change there.

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

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


[Touch-packages] [Bug 1457321] Re: lxc-stop does not shut down container

2015-06-02 Thread Brian Murray
Hello Martin, or anyone else affected,

Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu6
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  lxc-stop does not shut down container

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

Bug description:
  lxc-stop sends SIGPWR to a container's pid 1 to notify it that it
  should shut down. This merely starts sigpwr.target right now, but
  nothing is hooked into it. That's deliberate for "real iron" systems
  as there it's usually UPSes sending that, which should be handled by
  e. g. nut, not directly systemd. However, for containers I believe
  that's a safe default.

  For the record, in upstart we had /etc/init/shutdown.conf . This is
  wrong, as it breaks UPS responders like nut (and it also halts instead
  of poweroff). But we should provide this for containers under systemd.

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2015-May/009279.html

  SRU TEST CASE:
  --
  - Create a vivid LXC container (system or unprivileged)
  - Try to lxc-stop it. With current vivid it will do nothing/hang, with the 
proposed version it will shut down as expected.

  REGRESSION POTENTIAL:
  -
  - This new unit is only active in containers (LXC, docker, nspawn, etc.). 
There a possible regression is that someone is running/testing nut or a similar 
UPS responder in a container, but that seems like a theoretical scenario only.
  - There is no change for VMs or "real" hardware.

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

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


[Touch-packages] [Bug 525154] Re: mountall for /var or other nfs mount races with rpc.statd

2015-06-02 Thread Maciej Puzio
For a similar bug affecting Ubuntu 14.04, please see bug #1371564

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

Title:
  mountall for /var or other nfs mount races with rpc.statd

Status in mountall package in Ubuntu:
  Invalid
Status in nfs-utils package in Ubuntu:
  Fix Released
Status in portmap package in Ubuntu:
  Fix Released
Status in mountall source package in Lucid:
  Invalid
Status in nfs-utils source package in Lucid:
  Fix Released
Status in portmap source package in Lucid:
  Fix Released
Status in mountall source package in Maverick:
  Invalid
Status in nfs-utils source package in Maverick:
  Fix Released
Status in portmap source package in Maverick:
  Fix Released
Status in mountall source package in Natty:
  Invalid
Status in nfs-utils source package in Natty:
  Fix Released
Status in portmap source package in Natty:
  Fix Released

Bug description:
  If one has /var (or /var/lib or /var/lib/nfs for that matter) on its
  own filesystem the statd.conf start races with the mounting of /var as
  rpc.statd needs /var/lib/nfs to be available in order to work.

  I am sure this is not the only occurrence of this type of problem.

  A knee-jerk solution is to simply spin in statd.conf waiting for
  /var/lib/nfs to be available, but polling sucks, especially for
  something like upstart whose whole purpose is to be an event driven
  action manager.

  SRU justification: NFS mounts do not start reliably on boot in lucid
  and maverick (depending on the filesystem layout of the client system)
  due to race conditions in the startup of statd.  This should be fixed
  so users of the latest LTS can make reliable use of NFS.

  Regression potential:  Some systems may fail to mount NFS filesystems
  at boot time that didn't fail before.  Some systems may hang at boot.
  Some systems may hang while upgrading the packages (this version or in
  a future SRU).  I believe the natty update adequately guards against
  all of these possibilities, but the risk is there.

  TEST CASE:
  1. Configure a system with /var as a separate partition.
  2. Add one or more mounts of type 'nfs' to /etc/fstab.
  3. Boot the system.
  4. Verify whether statd has started (status statd) and whether all NFS 
filesystems have been mounted.
  5. Repeat 3-4 until the race condition is triggered.
  6. Upgrade to the new version of portmap and nfs-common from -proposed.
  7. Repeat steps 3-4 until satisfied that statd now starts reliably and all 
non-gss-authenticated NFSv3 filesystems mount correctly at boot time.

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

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


[Touch-packages] [Bug 1457961] Re: Session (X11?) is killed when screen is turned off

2015-06-02 Thread Kai Mast
Problem seems to be resolved when unity-system-compositor is removed.

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

** Also affects: xmir
   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/1457961

Title:
  Session (X11?) is killed when screen is turned off

Status in Light Display Manager:
  New
Status in XMir:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  When my computer is idle it sometimes ends up at the login screen with
  my session killed. This also happens when I disable the session
  locking.

  Not sure if this is related to systemd or this bug: LP1441687

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  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: Fri May 22 11:56:27 2015
  InstallationDate: Installed on 2014-07-25 (301 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: lightdm
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2015-01-24 (117 days ago)

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

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


[Touch-packages] [Bug 1454253] Re: external usb breaks suspend

2015-06-02 Thread god
echo mem | sudo tee /sys/power/state - that fails the same way as
suspending through xfce, dmesg is attached.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1454253/+attachment/4408837/+files/dmesg

** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/1454253

Title:
  external usb breaks suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  After booting xubuntu 15.04 it's possible to suspend it the normal way
  BUT - only until you've plugged external usb hard drive. After that
  (even if it was unmounted and removed) it becomes impossible: the
  system goes to suspend briefly (for bout 1 second) but immediately
  wakes up for no apparent reason.

  I suspect there's some weird bug in xfce power management - is there a
  way to disable it alltogether and  rely on systemd directly instead?

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

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


[Touch-packages] [Bug 1461276] [NEW] Requesting ITS#8003 inclusion in 2.4.40 package

2015-06-02 Thread Kartik Subbarao
Public bug reported:

Would it be possible to include the patch for ITS#8003 in the next build
of the 2.4.40 package?

http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=c8353f7acdec4a42f537b0d475aaae005ba72363

It fixes a bug that causes slapd to crash when the audit log is enabled
and a large base64-encoded attribute is printed.

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


** Tags: crash slapd

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

Title:
  Requesting ITS#8003 inclusion in 2.4.40 package

Status in openldap package in Ubuntu:
  New

Bug description:
  Would it be possible to include the patch for ITS#8003 in the next
  build of the 2.4.40 package?

  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=c8353f7acdec4a42f537b0d475aaae005ba72363

  It fixes a bug that causes slapd to crash when the audit log is
  enabled and a large base64-encoded attribute is printed.

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

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


[Touch-packages] [Bug 1389605] Re: Bookmarks section header in new tab view not updated when a bookmark is added/removed

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

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

Title:
  Bookmarks section header in new tab view not updated when a bookmark
  is added/removed

Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  There are two issues in one:

  1. if a user has only one bookmark, she creates a new tab, the new tab
  view is displayed, if she then switches to another open tab that has
  this bookmark page open and unstars it from the address bar, and
  switches back to the new tab view, the bookmark has disappeared, but
  the bookmarks section header is still there, empty

  2. if a user has no bookmarks, she creates a new tab, the new tab view
  is displayed (with no bookmarks section), if she then switches to
  another open tab and stars it, then switches back to the new tab view,
  there is no bookmarks section displayed.

  Those two issues boil down to the static nature of the sectionsModel in 
NewTabView.qml.
  Instead of conditionally populating the model when the view is instantiated, 
the model should always contain the two sections, but the delegate in charge of 
displaying the sections should be visible only if the corresponding sub-model 
is not empty.

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

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


[Touch-packages] [Bug 1442190] Re: Deleting a bookmark from the new tab view doesn’t display the next one in the list

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

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

Title:
  Deleting a bookmark from the new tab view doesn’t display the next one
  in the list

Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  If a user has more than 5 bookmarks and opens a new tab, the first 5 
bookmarks are displayed, followed by a "See More" button.
  Swiping one of the visible bookmarks to the right to remove it correctly 
deletes it, but the view isn’t refilled with the next bookmark that was 
previously hidden, it remains with 4 bookmarks, even though there are more to 
show.

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

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


[Touch-packages] [Bug 1461274] [NEW] dependency cycles

2015-06-02 Thread god
Public bug reported:

There are several dependency cycles reported during the boot of xubuntu
15.04 x86_64: see attached log.

Those cycles should be resoled.

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

** Attachment added: "boot.log"
   https://bugs.launchpad.net/bugs/1461274/+attachment/4408820/+files/boot.log

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

Title:
  dependency cycles

Status in systemd package in Ubuntu:
  New

Bug description:
  There are several dependency cycles reported during the boot of
  xubuntu 15.04 x86_64: see attached log.

  Those cycles should be resoled.

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

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


[Touch-packages] [Bug 1457424] Re: Please update icon (May 2015)

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Please update icon (May 2015)

Status in Address Book App:
  In Progress
Status in Camera App:
  New
Status in the base for Ubuntu mobile products:
  New
Status in Dekko:
  Fix Committed
Status in Gallery App:
  New
Status in Media Player App:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Ubuntu Notes app:
  Fix Committed
Status in Default calculator application for Ubuntu devices:
  Fix Committed
Status in Calendar application for Ubuntu devices:
  Fix Committed
Status in Clock application for Ubuntu devices:
  Fix Committed
Status in RSS Feed Reader application for Ubuntu devices:
  Fix Committed
Status in Themes for Ubuntu:
  Triaged
Status in Weather application for Ubuntu devices:
  Fix Committed
Status in Web Browser App:
  Fix Released
Status in address-book-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  New icons are available. Please update app to new icon. Note the icon
  inside the app will need updating as well as the icon in the store
  (when uploaded).

  256x256 and 512x512 Icons attached in zip file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1457424/+subscriptions

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


[Touch-packages] [Bug 1445673] Re: Shouldn't be able to pass QObjects to WebContextDelegateWorker

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Shouldn't be able to pass QObjects to WebContextDelegateWorker

Status in Oxide Webview:
  Triaged
Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Calling WebContextDelegateWorker::sendMessage allows the caller to
  pass a QObject in to the script running on another thread. This isn't
  safe, and we shouldn't allow this in the API at all

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

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


[Touch-packages] [Bug 1371248] Re: [Browser] No home button to take you back to the default home page

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

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

Title:
  [Browser] No home button to take you back to the default home page

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Open the browser on a fresh flash
  2. Note the home page
  3. Browse to planet.ubuntu.com
  4. Close the browser
  5. Open the browser
  6. Try and get back to the original home page.

  EXPECTATION:
  Every browser has a home button, it may or may not be used on mobiles but at 
some point you might want to go back to that page.

  ACTUAL:
  Once you close the browser the history registers the home page but after a 
while that would disappear then you would be left with no reference of it.

  -- SOLUTION --
  Add a default bookmark in the New Tab screen
  http://start.ubuntu.com/current/?sourceid=hp
  Title="Ubuntu Start page"

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

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


[Touch-packages] [Bug 1351157] Re: [browser] Update visual design of the new tab page

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

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

Title:
  [browser] Update visual design of the new tab page

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  The visual design of the new tab page doesn’t fully match the visual spec:
   - the "see more" / "see less" actions for bookmarks should be in the section 
header
   - the layout should be different when in landscape mode

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

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


[Touch-packages] [Bug 1444023] Re: new tab view empty when restoring an empty tab

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

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

Title:
  new tab view empty when restoring an empty tab

Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

   1) Pull the bottom edge hint up to open the tabs view, then tap the "New 
Tab" button
   2) Verify that you get the new tab view that displays bookmarks and top sites
   3) Close the browser
   4) Open the browser again

  Expected result: the new tab view is opened

  Current result: a blank tab is restored, but the new tab view isn’t
  there

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

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


[Touch-packages] [Bug 1458963] Re: Favicons are saved to disk in private browsing mode

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  Favicons are saved to disk in private browsing mode

Status in Oxide Webview:
  Triaged
Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Currently, Oxide provides a http URL for the favicon via WebView.icon
  and the browser uses this URL to download the image via Qt's network
  stack. As well as displaying this in the addressbar, it also writes it
  to disk.

  There's a couple of problems here:

  1) The favicon is written to disk even in private browsing mode.
  2) I'm not too sure about this, but downloading using Qt's network stack 
potentially leaves a cache footprint. In any case, we don't audit its 
suitability for use with private browsing.

  The first part will need to be fixed in the browser.

  For the second part, I think that Oxide should do the actual network
  transaction to fetch the favicon. We can provide an implementation of
  QQmlImageProvider and make WebView.icon a image: URL. The browser
  should still be able to use this URL to access and write the icons to
  disk (I assume this is for displaying history), but it would do this
  by requesting the QImage from Oxide's image provider, using
  QQmlEngine::imageProvider() rather than doing the network transaction
  itself.

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

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


[Touch-packages] [Bug 1459956] Re: "Settings > Clear Cache" doesn’t actually clear the cache

2015-06-02 Thread Olivier Tilloy
** Changed in: webbrowser-app
   Status: In Progress => Fix Released

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  "Settings > Clear Cache" doesn’t actually clear the cache

Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Oxide 1.7 switched to the simple cache backend for its network cache
  (see bug #1430349). Since then the "Clear Cache" functionality in the
  privacy settings screen doesn’t work any longer, as it’s trying to
  delete the wrong set of files in the wrong directory.

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

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


[Touch-packages] [Bug 1461259] [NEW] PCI/internal sound card not detected

2015-06-02 Thread fabio nps
Public bug reported:

UBUNTU 15.04

HDMI audio option don`t appears on the sound config, just the video
works

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  fabio  1475 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jun  2 17:25:53 2015
InstallationDate: Installed on 2015-06-02 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to vivid on 2015-06-02 (0 days ago)
dmi.bios.date: 11/12/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 02T8TW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A07
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn02T8TW:rvrA00:cvnDellInc.:ct8:cvrA07:
dmi.product.name: Inspiron 5537
dmi.product.version: A07
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug vivid

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  UBUNTU 15.04

  HDMI audio option don`t appears on the sound config, just the video
  works

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fabio  1475 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jun  2 17:25:53 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to vivid on 2015-06-02 (0 days ago)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 02T8TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron5537:pvrA07:rvnDellInc.:rn02T8TW:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron 5537
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1389605] Re: Bookmarks section header in new tab view not updated when a bookmark is added/removed

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  Bookmarks section header in new tab view not updated when a bookmark
  is added/removed

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  There are two issues in one:

  1. if a user has only one bookmark, she creates a new tab, the new tab
  view is displayed, if she then switches to another open tab that has
  this bookmark page open and unstars it from the address bar, and
  switches back to the new tab view, the bookmark has disappeared, but
  the bookmarks section header is still there, empty

  2. if a user has no bookmarks, she creates a new tab, the new tab view
  is displayed (with no bookmarks section), if she then switches to
  another open tab and stars it, then switches back to the new tab view,
  there is no bookmarks section displayed.

  Those two issues boil down to the static nature of the sectionsModel in 
NewTabView.qml.
  Instead of conditionally populating the model when the view is instantiated, 
the model should always contain the two sections, but the delegate in charge of 
displaying the sections should be visible only if the corresponding sub-model 
is not empty.

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

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


[Touch-packages] [Bug 1442190] Re: Deleting a bookmark from the new tab view doesn’t display the next one in the list

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  Deleting a bookmark from the new tab view doesn’t display the next one
  in the list

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  If a user has more than 5 bookmarks and opens a new tab, the first 5 
bookmarks are displayed, followed by a "See More" button.
  Swiping one of the visible bookmarks to the right to remove it correctly 
deletes it, but the view isn’t refilled with the next bookmark that was 
previously hidden, it remains with 4 bookmarks, even though there are more to 
show.

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

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


[Touch-packages] [Bug 1459956] Re: "Settings > Clear Cache" doesn’t actually clear the cache

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  "Settings > Clear Cache" doesn’t actually clear the cache

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Oxide 1.7 switched to the simple cache backend for its network cache
  (see bug #1430349). Since then the "Clear Cache" functionality in the
  privacy settings screen doesn’t work any longer, as it’s trying to
  delete the wrong set of files in the wrong directory.

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

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


[Touch-packages] [Bug 1351157] Re: [browser] Update visual design of the new tab page

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  [browser] Update visual design of the new tab page

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  The visual design of the new tab page doesn’t fully match the visual spec:
   - the "see more" / "see less" actions for bookmarks should be in the section 
header
   - the layout should be different when in landscape mode

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

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


[Touch-packages] [Bug 1445673] Re: Shouldn't be able to pass QObjects to WebContextDelegateWorker

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  Shouldn't be able to pass QObjects to WebContextDelegateWorker

Status in Oxide Webview:
  Triaged
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Calling WebContextDelegateWorker::sendMessage allows the caller to
  pass a QObject in to the script running on another thread. This isn't
  safe, and we shouldn't allow this in the API at all

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

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


[Touch-packages] [Bug 1371248] Re: [Browser] No home button to take you back to the default home page

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

Title:
  [Browser] No home button to take you back to the default home page

Status in Ubuntu UX bugs:
  Fix Committed
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Open the browser on a fresh flash
  2. Note the home page
  3. Browse to planet.ubuntu.com
  4. Close the browser
  5. Open the browser
  6. Try and get back to the original home page.

  EXPECTATION:
  Every browser has a home button, it may or may not be used on mobiles but at 
some point you might want to go back to that page.

  ACTUAL:
  Once you close the browser the history registers the home page but after a 
while that would disappear then you would be left with no reference of it.

  -- SOLUTION --
  Add a default bookmark in the New Tab screen
  http://start.ubuntu.com/current/?sourceid=hp
  Title="Ubuntu Start page"

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

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


[Touch-packages] [Bug 1458963] Re: Favicons are saved to disk in private browsing mode

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  Favicons are saved to disk in private browsing mode

Status in Oxide Webview:
  Triaged
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Currently, Oxide provides a http URL for the favicon via WebView.icon
  and the browser uses this URL to download the image via Qt's network
  stack. As well as displaying this in the addressbar, it also writes it
  to disk.

  There's a couple of problems here:

  1) The favicon is written to disk even in private browsing mode.
  2) I'm not too sure about this, but downloading using Qt's network stack 
potentially leaves a cache footprint. In any case, we don't audit its 
suitability for use with private browsing.

  The first part will need to be fixed in the browser.

  For the second part, I think that Oxide should do the actual network
  transaction to fetch the favicon. We can provide an implementation of
  QQmlImageProvider and make WebView.icon a image: URL. The browser
  should still be able to use this URL to access and write the icons to
  disk (I assume this is for displaying history), but it would do this
  by requesting the QImage from Oxide's image provider, using
  QQmlEngine::imageProvider() rather than doing the network transaction
  itself.

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

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


[Touch-packages] [Bug 1444023] Re: new tab view empty when restoring an empty tab

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  new tab view empty when restoring an empty tab

Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

   1) Pull the bottom edge hint up to open the tabs view, then tap the "New 
Tab" button
   2) Verify that you get the new tab view that displays bookmarks and top sites
   3) Close the browser
   4) Open the browser again

  Expected result: the new tab view is opened

  Current result: a blank tab is restored, but the new tab view isn’t
  there

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

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


[Touch-packages] [Bug 1461247] [NEW] Xorg freeze

2015-06-02 Thread kyawmyatthu.ows
Public bug reported:

Distributor ID: Ubuntu
Description:Ubuntu 15.04
Release:15.04
Codename:   vivid

system freeze frequently

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic i686
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jun  3 03:55:17 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard: NVIDIA Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2015-06-01 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7387
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.1
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7387
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd12/17/2007:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7387:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7387:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7387
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Jun  3 03:15:06 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

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


** Tags: apport-bug freeze i386 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/1461247

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  system freeze frequently

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic i686
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun  3 03:55:17 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard: NVIDIA Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-06-01 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7387
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7387
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0

[Touch-packages] [Bug 1457424] Re: Please update icon (May 2015)

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package webbrowser-app -
0.23+15.10.20150602-0ubuntu1

---
webbrowser-app (0.23+15.10.20150602-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Olivier Tilloy ]
  * Actually clear the network cache by deleting the correct set of
files in the correct directory. (LP: #1459956)
  * Bump build dependency on liboxideqt-qmlplugin to 1.6 to fix unit
tests.
  * Do not cache favicons on disk when browsing in private mode. (LP:
#1458963)
  * Do not try to remove a file that doesn’t exist.
  * Pass plain strings to the worker script instead of RegExps. (LP:
#1445673)
  * Remove the upstreamcomponents folder, and use components from the
UITK instead. Add autopilot tests for the new tab view.
  * Update translation template.
  * Updated icon. (LP: #1457424)

  [ Riccardo Padovani ]
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)
  * New tab view refactoring. (LP: #1371248, #1444023, #1351157,
#1389605, #1442190)

 -- CI Train Bot   Tue, 02 Jun 2015 14:26:50
+

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

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

Title:
  Please update icon (May 2015)

Status in Address Book App:
  In Progress
Status in Camera App:
  New
Status in the base for Ubuntu mobile products:
  New
Status in Dekko:
  Fix Committed
Status in Gallery App:
  New
Status in Media Player App:
  New
Status in Music application for Ubuntu devices:
  Fix Committed
Status in Ubuntu Notes app:
  Fix Committed
Status in Default calculator application for Ubuntu devices:
  Fix Committed
Status in Calendar application for Ubuntu devices:
  Fix Committed
Status in Clock application for Ubuntu devices:
  Fix Committed
Status in RSS Feed Reader application for Ubuntu devices:
  Fix Committed
Status in Themes for Ubuntu:
  Triaged
Status in Weather application for Ubuntu devices:
  Fix Committed
Status in Web Browser App:
  In Progress
Status in address-book-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  New icons are available. Please update app to new icon. Note the icon
  inside the app will need updating as well as the icon in the store
  (when uploaded).

  256x256 and 512x512 Icons attached in zip file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1457424/+subscriptions

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


[Touch-packages] [Bug 1460794] Re: systemd will not work with a separate /usr partition

2015-06-02 Thread Robert Hardy
Please note attempting to mitigate this by switching back to upstart
failed as well.

Doing so did make it so the system would boot past mounting /usr however
for no obvious reason the system stopped automatically mounting the /var
partition.

With no network services running, the system would stop the boot process
on a screen and complain /var hadn't mounted and prompt me to press m to
enter emergency mode. Once I did that and logged in, /var was in fact
not mounted and a mount -av would immediately mount it and then exiting
emergency mode would cause a normal boot to complete. This should be a
blocking issue for 16.04 as it will cause a lot of grief to end users
when servers fail during upgrades. If I didn't have an IPMI remote
console device I would have been really stuck.

To be clear the only fix that worked was connecting using an IPMI remote 
console device, booting my server from a rescue iso, taring up each of my 
partitions with tar cpf and dumping them on a disk outside my raid array. I 
then wiped all the partitions off my main raid array and switched to a 
configurations where I had 1 primary boot, 1 primary swap and a root and home 
partition in a LVM physical volume. I then formated boot ext2, root btrfs and 
home xfs and extracted all the tars. I then follow a process similar to the one 
below to reinstall grub: 
https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot
At the end of the process, inside the chroot, I also did an: update-initramfs -u

The result was a working system but was way way more effort than should
have been required.

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

Title:
  systemd will not work with a separate /usr partition

Status in systemd package in Ubuntu:
  New

Bug description:
  I recently upgraded a server from 14.10 to 15.04. The upgrade claim to
  have worked but the system could not boot afterwards.

  Basically when you attempt to reboot you end up at an emergency maintenance 
prompt early in the boot process.
  After a lot of digging one of the messages in the logs gives:
  systemd[1]: /usr appears to be on its own filesystem and is not already 
mounted. This is not a supported setup. Some things will probably break 
(sometimes even silently) in mysterious ways. Consult 
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

  Basically systemd cannot deal with /usr being on a separate partition.
  That needs to be fixed or systemd should not be used for upgrades with
  a separate /usr partition.

  This is related to bug 1460790 but asking for systemd to actually be fixed.
  Please see bug 1460790 if you are looking for a work around on this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Mon Jun  1 15:29:32 2015
  InstallationDate: Installed on 2010-05-23 (1835 days ago)
  InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 
(20100427)
  MachineType: Supermicro X8STi
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/tcsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=676235cd-93b1-426e-8336-fa0078d96145 ro quiet acpi=off pci=noacpi
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago)
  dmi.bios.date: 09/17/10
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X8STi
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8STi:pvr1234567890:rvnSupermicro:rnX8STi:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X8STi
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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

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


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

2015-06-02 Thread carlix
Lubuntu 15.10 and 15.04 and other distros like debian 8 and fedora 22 works 
fine but others like kubuntu, ubuntu gnome, doesn´t.
This is so strange!!!

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1388612]

2015-06-02 Thread Mattst88
*** Bug 89341 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1388612

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  In Progress

Bug description:
  Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on
  a Dell Vostro 1510 laptop with Intel graphics. The problem used to
  arise also with Ubuntu 14.04 and is always reproducible with glmark2
  on the LiveCD. Just to run the "ideas" benchmark of glmark2 to trigger
  the lockup in few seconds (glmark2 -b ideas). Other OpenGL
  applications also causes the lockup (e.g. FooBillard++, my self-made
  SDL applications). Memory test passed, BIOS at the latest version.
  Don't know if the following is a good point but I think that the
  problem is not caused by a failing hardware because it works fine on
  Windows. I tried with the latest Intel upstream kernel
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
  next/current/) and upstream X.org (https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa), no change.

  [Personal Notes]
  I'm new to Ubuntu's world, I hope I've done things right, if not please tell 
me and I will resend the report or supply more information. I've created the 
bug report with "ubuntu-bug xorg --save" from another machine via SSH while the 
sick machine was frozen. It seemed to me more logical than using ubuntu-bug 
directly when the system is working fine. I've collected other information via 
SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was 
added as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 19:24:31 2014
  DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0273]
 Subsystem: Dell Device [1028:0273]
  InstallationDate: Installed on 2014-10-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro1510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago)
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0M277C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1510
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  2 18:41:51 2014
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and 
the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15873 
   vendor LPL
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1461137] Re: Sound indicator missing on upgrade

2015-06-02 Thread Charles Kerr
om26er, was there a crash log for indicator-sound?

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

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

Title:
  Sound indicator missing on upgrade

Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  The sound icon is missing when I upgraded from last promoted rtm image
  to RC.

  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  CrashDB: indicator_sound
  Date: Tue Jun  2 20:14:40 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
  SourcePackage: indicator-sound
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: indicator-sound stop/pre-start, process 3362

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

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


[Touch-packages] [Bug 1461137] Re: Sound indicator missing on upgrade

2015-06-02 Thread Charles Kerr
discussing with om26er on irc, the issue went away after reboot.

Also, pulseaudio had crashed during reboot.

indicator-sound hides itself iff the user opts in gsettings to hide it,
so it's not hiding. Probably whatever caused pulse to crash also caused
indicator-sound to crash.

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

Title:
  Sound indicator missing on upgrade

Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  The sound icon is missing when I upgraded from last promoted rtm image
  to RC.

  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  CrashDB: indicator_sound
  Date: Tue Jun  2 20:14:40 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
  SourcePackage: indicator-sound
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: indicator-sound stop/pre-start, process 3362

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

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


[Touch-packages] [Bug 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home

2015-06-02 Thread Slava
*** This bug is a duplicate of bug 1445595 ***
https://bugs.launchpad.net/bugs/1445595

When you fix this nasty bug? First report about this bug was TWO MONTH
ago!!!

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

Title:
  Launcher Trash icon: Empty Trash option opens nautilus @ home

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Add a file to trash if none already
  Right click on Unity launcher trash icon > click on Empty Trash option
  nautilus open a window @ home folder

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Apr 24 13:11:02 2015
  InstallationDate: Installed on 2015-04-24 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1245878] Re: Cannot connect to open network with captive portal

2015-06-02 Thread taiebot65
A workaround is to open a webapp like bbc news and you should be re-
directed to the captive portal. (anyway that's what i am doing)

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

Title:
  Cannot connect to open network with captive portal

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Visit a location with an open wireless network which requires you to click 
"agree" or similar before connecting to the internet proper - a so-called 
captive portal.
  Using system image 5 on mako I am unable to make such a connection. 
  I can see the network, click on it in the network-indicator, but I don't get 
an IP address, and no way to visit the "agree" page.
  I can connect to other open (and secure) networks just fine, and other 
devices can connect to the problem network (but prompt to "agree" in a browser).

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

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


[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

2015-06-02 Thread Erick Brunzell
This does still effect Ubuntu & Ubuntu Mate Wily as well as Debian Mate
Jessie. I'll try to file a Debian bug report ASAP (it'll be my first).

Anyone that has suggestions might find my forum post useful:

http://ubuntuforums.org/showthread.php?t=2280658

The challenge is trying to figure out what process in addition to the
file manager is mounting the blank media.

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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


[Touch-packages] [Bug 1418210] Re: Spotify App has changing volume levels per song

2015-06-02 Thread Charles Kerr
Ted, I'm not really sure this is an indicator-sound bug?

After talking to Elleo briefly about this, he says it happens anytime a
new QAudioOutput is created, so we could probably write a quick simple
test app to exercise this behavior w/o a premium Spotify account +
CuteSpotify.

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

Title:
  Spotify App has changing volume levels per song

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Reported by a user that the per-song levels when using CuteSpotify
  were resetting to really loud, making the application unusable.
  Considering the app has no control over the volume level, this is a
  bug to track down what is happening there.

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

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


[Touch-packages] [Bug 1461180] [NEW] segfault when opening menu in landscape oritentation

2015-06-02 Thread Sebastien Bacher
Public bug reported:

Using the vivid based ota candidate for bq
- open a photo in the gallery
- rotate the device to be in landscape
- click on the top-right menu

-> the menu is displayed with the wrong orientation, then rotate then
gallery closes

** Affects: gallery-app (Ubuntu)
 Importance: High
 Status: New

** Changed in: gallery-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  segfault when opening menu in landscape oritentation

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Using the vivid based ota candidate for bq
  - open a photo in the gallery
  - rotate the device to be in landscape
  - click on the top-right menu

  -> the menu is displayed with the wrong orientation, then rotate then
  gallery closes

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

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


[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-06-02 Thread Pat McGowan
Since we now know the led was blue to match the original indicator
color, which then changed to green then white then back to green, I
suggest we now make the indicator green as well.

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Messaging Menu:
  New
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators

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

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


[Touch-packages] [Bug 1458897] Re: [mako] When starting/seeking music the volume notification appears

2015-06-02 Thread Charles Kerr
I'm not able to reproduce this in r213:

$ system-image-cli -i
current build number: 213
device name: mako
channel: ubuntu-touch/devel-proposed/ubuntu
last update: 1969-12-31 20:21:01
version version: 213
version ubuntu: 20150602
version device: 20150529.1
version custom: 20150602

I tested with music-app, stopping & starting, seeking in the track, both
with and without headphones.

Andrew, could you update and retest? Please reopen this ticket with more
info if the problem's still there.

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

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

Title:
  [mako] When starting/seeking music the volume notification appears

Status in indicator-sound package in Ubuntu:
  Incomplete

Bug description:
  What happened:
  1) Open the music-app
  2) Start playing a track or seek the playing track
  3) Observe that the volume notification appears

  What was expected to happen:
  1) At step 3 the volume notification should not be shown

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/devel-proposed-customized-here
  alias: ubuntu-touch/vivid-proposed-customized-here
  last update: 2015-05-14 21:20:36
  version version: 194
  version ubuntu: 20150514
  version device: 20150210
  version custom: mako-1.1

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

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


[Touch-packages] [Bug 1458231] Re: Using displayport with external monitor flickers laptop screen

2015-06-02 Thread maKA
Sorry! Here it is:

maka@maka-ThinkPad-T520:~$ sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
8AET65WW (1.45 )
05/14/2015


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

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

Title:
  Using displayport with external monitor flickers laptop screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Using a displayport link to connect with my external monitor causes
  heavy flickering on my laptop screen. Especially when the external
  monitor is being used. There is also a delay of refresh on the
  external monitor... I can see my mouse appear multiple times when I
  move the cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 23 15:44:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21d1]
   NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21d1]
  InstallationDate: Installed on 2015-05-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo 
Integrated Camera (0.3MP)
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4242DT6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=6ccdd4eb-99eb-4e91-9475-83b0b6ec953b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242DT6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242DT6:pvrThinkPadT520:rvnLENOVO:rn4242DT6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242DT6
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May 23 10:47:36 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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

2015-06-02 Thread Erick Brunzell
** Tags added: caja ubuntu-mate wily

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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


[Touch-packages] [Bug 1450885] Re: Connection problems after boot and random crash

2015-06-02 Thread anders
Solved by BIOS update

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

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

Title:
  Connection problems after boot and random crash

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  syslog:
  May  1 20:48:49 inspiron NetworkManager[694]:  [1430506129.771441] 
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): (wlan0): 
error adding interface: wpa_supplicant couldn't grab this interface.
  May  1 20:48:49 inspiron NetworkManager[694]:  (wlan0): supplicant 
interface state: starting -> down
  May  1 20:48:49 inspiron kernel: [  402.109585] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:49 inspiron kernel: [  402.109591] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:49 inspiron kernel: [  402.156292] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:49 inspiron kernel: [  402.156295] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:49 inspiron kernel: [  402.202990] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:49 inspiron kernel: [  402.202993] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:49 inspiron kernel: [  402.249687] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:49 inspiron kernel: [  402.249690] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.296387] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron wpa_supplicant[852]: Could not set interface wlan0 
flags (UP): Input/output error
  May  1 20:48:50 inspiron wpa_supplicant[852]: nl80211: Could not set 
interface 'wlan0' UP
  May  1 20:48:50 inspiron kernel: [  402.296389] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.332577] iwl3945 :0c:00.0: Unable 
to initialize device after 5 attempts.
  May  1 20:48:50 inspiron kernel: [  402.380665] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.380669] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.427362] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.427365] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.474062] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.474065] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.520767] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.520770] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.567462] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.567465] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron wpa_supplicant[852]: Could not set interface wlan0 
flags (UP): Input/output error
  May  1 20:48:50 inspiron wpa_supplicant[852]: WEXT: Could not set interface 
'wlan0' UP
  May  1 20:48:50 inspiron wpa_supplicant[852]: wlan0: Failed to initialize 
driver interface
  May  1 20:48:50 inspiron NetworkManager[694]:  [1430506130.315106] 
[supplicant-manager/nm-supplicant-interface.c:856] interface_add_cb(): (wlan0): 
error adding interface: wpa_supplicant couldn't grab this interface.
  May  1 20:48:50 inspiron NetworkManager[694]:  (wlan0): supplicant 
interface state: starting -> down
  May  1 20:48:50 inspiron kernel: [  402.603939] iwl3945 :0c:00.0: Unable 
to initialize device after 5 attempts.
  May  1 20:48:50 inspiron kernel: [  402.653519] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May  1 20:48:50 inspiron kernel: [  402.653524] iwl3945 :0c:00.0: Unable 
to set up bootstrap uCode: -5
  May  1 20:48:50 inspiron kernel: [  402.700222] iwl3945 :0c:00.0: BSM 
uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 
0xf802020
  May

[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-06-02 Thread Charles Kerr
** Branch linked: lp:~tiheum/ubuntu-themes/suru-app-icons-v2

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Messaging Menu:
  New
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators

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

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


[Touch-packages] [Bug 1454989] Re: Freeze after boot

2015-06-02 Thread anders
Solved by BIOS update

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

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

Title:
  Freeze after boot

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Sometimes I will get the screen seen on the attached picture if i leave the PC
  idle for some time after boot. The image changes when pressing a key on the 
keyboard.

  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 i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,snap,regex,place,grid,resize,compiztoolbox,gnomecompat,mousepoll,move,animation,workarounds,vpswitch,imgpng,expo,session,wall,unitymtgrabhandles,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 14 10:09:48 2015
  DistUpgraded: 2015-04-23 19:53:08,580 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:01f2]
  InstallationDate: Installed on 2011-08-31 (1351 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: Dell Inc. Inspiron 1720
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=bc46b217-a77a-490e-8b25-9fe396966dca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (20 days ago)
  dmi.bios.date: 08/16/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0UK437
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/16/2007:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK437:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1720
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1

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

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


[Touch-packages] [Bug 1455745] Re: Wireless network bug

2015-06-02 Thread anders
Solved by BIOS update

** Changed in: wpa (Ubuntu)
   Status: New => Fix Released

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

Title:
  Wireless network bug

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  Occasional the wireless network connection stops working. If I then disable 
and enable networks using the network applet or the following command the whole 
PC slows down:
  > sudo systemctl restart NetworkManager.service

  I know of only two ways to resolve the problem: reboot and suspend.
  The fastest way is doing suspend followed by resume.

  The attached picture show the system load using top.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: wpasupplicant 2.1-0ubuntu7.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: Unity
  Date: Sat May 16 11:04:35 2015
  InstallationDate: Installed on 2011-08-31 (1353 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (22 days ago)

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

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


[Touch-packages] [Bug 1261387] Re: Change the build system from qmake to cmake

2015-06-02 Thread Benjamin Zeller
We decided to stay with qmake since we have proper qmake support inside
the chroots now.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Won't Fix

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

Title:
  Change the build system from qmake to cmake

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  The new cross-compiler solution supports cmake better than qmake. For
  the sake of easy and smooth cross compilation it would be beneficial
  to use the same build system as other projects.

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

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


[Touch-packages] [Bug 1461138] Re: Few click icons are appearing twice after upgrade to RC

2015-06-02 Thread Alejandro J. Cura
According to this paste that Omer sent, there are .desktop files left on
the filesystem after an upgrade: http://paste.ubuntu.com/11523151/

eg:
-rw-rw-r-- 1 phablet phablet   167 Jun  2 19:36 
com.canonical.cincodias_CINCODIAS.desktop
-rw-rw-r-- 1 phablet phablet   527 Jun  2 18:40 
com.canonical.cincodias_webapp-CINCODIAS_0.2.desktop
-rw-rw-r-- 1 phablet phablet   624 Jun  2 19:36 
com.canonical.cincodias_webapp-CINCODIAS_0.6.desktop

Omer also sent me the output of "click list" and "sudo click list", and
everything seems fine there, with only the very latest version
installed.

I suspect this might be an issue in the click desktop hook, so I'm
moving the bug there.

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-scope-click (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Summary changed:

- Few click icons are appearing twice after upgrade to RC
+ Some click icons are appearing twice after upgrade to RC

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

Title:
  Some click icons are appearing twice after upgrade to RC

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  Invalid

Bug description:
  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  After the upgrade, some of the Apps are appearing twice, see the
  attached screenshot.

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

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


[Touch-packages] [Bug 1311866] Re: update binutils and GCC for trusty

2015-06-02 Thread Matthias Klose
verification succeeded for all binutils issues.

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

Title:
  update binutils and GCC for trusty

Status in binutils package in Ubuntu:
  Invalid
Status in gcc-4.8 package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Fix Committed
Status in gcc-4.8 source package in Trusty:
  Fix Committed
Status in binutils source package in Utopic:
  Invalid
Status in gcc-4.8 source package in Utopic:
  Invalid

Bug description:
  an SRU issue to document the update of gcc-4.8 in trusty

  14.04 LTS saw two new architectures, arm64 and ppc64el. These require
  some updates for the toolchain. binutils takes some selected patches
  to fix specific issues, and gcc-4.8 takes the state of the current
  gcc-4.8 fsf branch to update the compiler.  Changes and addresses
  issues are mentioned in the debian changelog.  Packages are prepared
  in the ubuntu-toolchain-r/ppa PPA, and a test rebuild of the archive
  was done on all architectures using this PPA. The results of this test
  rebuild look ok (for all of the -release, -updates and -security
  pockets). As a further test, the linux (see bug #1383474), firefox and
  libreoffice packages were rebuilt, tested and found working.

  The test rebuild archives are:
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140911-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140912-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140913-trusty.html

  gcc-4.8 should be built with the new binutils.

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

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


[Touch-packages] [Bug 1191909] Re: gold and -flto always fails with an internal error on arm-linux-gnueabi*

2015-06-02 Thread Matthias Klose
fixed in trusty-proposed

** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1191909

Title:
  gold and -flto always fails with an internal error on arm-linux-
  gnueabi*

Status in binutils:
  Confirmed
Status in Linaro Binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Trusty:
  Fix Committed
Status in binutils package in Debian:
  Fix Released

Bug description:
  seen with gcc-4.7 and binutils 2.22, and 4.8 and binutils trunk,

  $ echo "int main() {return 0;}" >a.c
  $ gcc -fuse-ld=gold -flto a.c
  /usr/bin/ld.gold: internal error in do_read_symbols, at ../../gold/arm.cc:6735
  collect2: error: ld returned 1 exit status

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

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


[Touch-packages] [Bug 1461034] Re: Brings offline qthelp and sdk documentation

2015-06-02 Thread Timo Jyrinki
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Brings offline qthelp and sdk documentation

Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  After installing ubuntu-sdk, only ubuntu components have offline doc
  support on F1, there is none for QML upstream components.

  We should cleanup the dependency to drop the now (soon) unused -doc-
  html flavor in favor of the qthelp ones. That way, F1 will bring the
  full offline documentation as part of the current user's context.

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

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


[Touch-packages] [Bug 1414817] Re: [Ubuntu 15.04] Ubuntu should audit account modification events

2015-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package shadow - 1:4.1.5.1-1.1ubuntu5

---
shadow (1:4.1.5.1-1.1ubuntu5) wily; urgency=medium

  * debian/rules: Re-enable audit support. (LP: #1414817)
  * debian/control: add libaudit-dev to Build-Depends.

 -- Mathieu Trudel-Lapierre   Tue, 02 Jun 2015
10:46:18 -0400

** Changed in: shadow (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 shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1414817

Title:
  [Ubuntu 15.04] Ubuntu should audit account modification events

Status in shadow package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu should log user modification events to the system audit trail
  (/var/log/audit/audit.log) but does not.

  Steps to Verify:

  - Install Ubuntu 14.04 on an x86_64 VM
  - apt install auditd
  - useradd testuser
  - ausearch -i

  Expected Results:

  An audit record should be appended to the audit trail that indicates
  testuser was added.

  Actual Results:

  An appropriate audit event was not appended to the audit trail.  A
  record is logged in /var/log/auth.log.

  Discussion:

  Auditable system events should be logged in the standard audit trail
  via the Linux audit subsystem. Doing so provides a central location
  where sysadmins can monitor security events. The Linux audit subsystem
  can be used to meet Common Criteria and compliance hardening standards
  requirements. OSPP v2.0
  [https://www.commoncriteriaportal.org/files/ppfiles/pp0067b_pdf.pdf]
  should provide a good reference for commonly logged audit events and
  other audit requirements.

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

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


[Touch-packages] [Bug 1461152] [NEW] Pulseaudio crashed on boot after upgrading to RC (OTA4)

2015-06-02 Thread Omer Akram
Public bug reported:

When the device was first booted after upgrade, indicator sound was
missing, and later I found that there is no working sound.

This was reported by whoopise:
https://errors.ubuntu.com/oops/e76eae5a-0938-11e5-be34-fa163e5bb1a2

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu6
Uname: Linux 3.4.67 armv7l
AlsaInfo: This script requires lspci. Please install it, and re-run this script.
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: armhf
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Tue Jun  2 20:44:28 2015
InstallationDate: Installed on 2015-06-02 (0 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf third-party-packages vivid

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

Title:
  Pulseaudio crashed on boot after upgrading to RC (OTA4)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When the device was first booted after upgrade, indicator sound was
  missing, and later I found that there is no working sound.

  This was reported by whoopise:
  https://errors.ubuntu.com/oops/e76eae5a-0938-11e5-be34-fa163e5bb1a2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu6
  Uname: Linux 3.4.67 armv7l
  AlsaInfo: This script requires lspci. Please install it, and re-run this 
script.
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Jun  2 20:44:28 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1412553] Re: RELRO not working on Ubuntu 14.04

2015-06-02 Thread Breno Leitão
** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1412553

Title:
  RELRO not working on Ubuntu 14.04

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Trusty:
  Fix Committed

Bug description:
  RELRO (RELocation Read-Only) is security feature provided by the
  linker and implemented in conjunction with glibc to relocations
  sections that are used to resolve dynamically loaded functions read-
  only.

  The GLIBC side looks at the segments placement set by the linker and
  if they met some criteria regarding alignment, the are mprotect to be
  read-only.  More specifically, on GLIBC code:

  elf/dl-reloc.c:

  324 void internal_function
  325 _dl_protect_relro (struct link_map *l)
  326 {
  327   ElfW(Addr) start = ((l->l_addr + l->l_relro_addr)
  328   & ~(GLRO(dl_pagesize) - 1));
  329   ElfW(Addr) end = ((l->l_addr + l->l_relro_addr + l->l_relro_size)
  330 & ~(GLRO(dl_pagesize) - 1));
  331 
  332   if (start != end
  333   && __mprotect ((void *) start, end - start, PROT_READ) < 0)
  334 {
  335   static const char errstring[] = N_("\
  336 cannot apply additional memory protection after relocation");
  337   _dl_signal_error (errno, l->l_name, NULL, errstring);
  338 }
  339 }

  The problem is, if linker does not set the alignment correctly,
  'start' and 'end' will be equal and thus not protected. And this is
  happening on Ubuntu 14.04 due the fact its uses default binutils
  elf{32,64}-ppc.c ELF_COMMONPAGESIZE to align it to 4k instead of 64k.

  There is a recent patch on binutils-dev maillist [1] to change the
  default for 64k and Fedora rawhide already sets it [2] in its
  binutils.spec spec:

  # On ppc64 and aarch64, we might use 64KiB pages
  sed -i -e '/#define.*ELF_COMMONPAGESIZE/s/0x1000$/0x1/' bfd/elf*ppc.c
  sed -i -e '/#define.*ELF_COMMONPAGESIZE/s/0x1000$/0x1/' bfd/elf*aarch64.c

  Ubuntu for powerpc64le should do the same.

  [1] https://sourceware.org/ml/binutils/2014-12/msg00165.html
  [2] 
http://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/source/SRPMS/b/binutils-2.24-29.fc22.src.rpm

  I tested and building a binutils with the ELF_COMMONPAGESIZE set to
  64k instead of default 4k and rebuilding GLIBC I see its relocation
  sections being correctly mprotected.

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

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


[Touch-packages] [Bug 1413801] Re: TextField's placeHolderText invisible inside a dialog

2015-06-02 Thread Olivia Caro de Diego
Hi Christian,

Would you mind to change the opacity to 50%  on #5d5d5d, please?

I was checking with Jouni and this should be ok like this.

Thanks for all,
Olivia

** Changed in: ubuntu-ux
   Status: Triaged => Fix Committed

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

Title:
  TextField's placeHolderText invisible inside a dialog

Status in Ubuntu UX bugs:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Using a dark background in an application, a Dialog and a TextField
  inside that Dialog renders the placeholderText nearly invisible.

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

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


[Touch-packages] [Bug 1362962] Re: Calendar icon usually shows the wrong date

2015-06-02 Thread Charles Kerr
** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Calendar icon usually shows the wrong date

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Problem occurs with: Ubuntu 14.10 r203
  Does not occur with: iOS, Windows Phone

  1. In the clock menu, find the calendar app and launch it.
  2. In the Launcher or Dash, find the Calendar app.

  What you see:
  1. The icon always says "25", regardless of the actual date.
  2. The icon always says "28", regardless of the actual date.

  What you should see:
  1. The icon shows the current date.
  2. The icon shows the current date.

  The equivalent for PC is bug 1362033, and for the Clock app is bug
  1362964.

  This depends on bug 1453795 for Unity letting an app change its own
  icon.

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

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


[Touch-packages] [Bug 1433238] Re: add powerpc target for ppc64el

2015-06-02 Thread Breno Leitão
** 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 binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1433238

Title:
  add powerpc target for ppc64el

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Trusty:
  Fix Committed

Bug description:
  I would like to have a backport of patch available in Debian BTS
  #760395 in Ubuntu 14.04.

  Reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760395
  Patch: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=binutils-2.24.51.20140818.patch;att=1;bug=760395
  Motivation: With this patch integrated, some package build would work 
properly, as the linker shows that ppc64el has shared objects. 

  After a binutil with this patch made available, I would like to ask to
  build the following packages:

  * Slurm
  * Munge
  * environment-modules (Source: modules)

  Thanks

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

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


[Touch-packages] [Bug 1362033] Re: Icon for calendar item usually shows the wrong date

2015-06-02 Thread Charles Kerr
*** This bug is a duplicate of bug 1362962 ***
https://bugs.launchpad.net/bugs/1362962

IMO this can be treated as a dupe of bug #1362962, this isn't going to
get fixed before unity8 convergence because unity7 is in maintenance-
only mode now.

** This bug has been marked a duplicate of bug 1362962
   Calendar icon usually shows the wrong date

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

Title:
  Icon for calendar item usually shows the wrong date

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1, Ubuntu 14.04

  1. Open the clock menu.
  2. Look at the icon for the date item.

  What you see: "28", regardless of the current date.

  What you should see: The current date.

  The Ubuntu Touch equivalent is bug 1362962.

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

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


Re: [Touch-packages] [Bug 1461138] [NEW] Few click icons are appearing twice after upgrade to RC

2015-06-02 Thread Alejandro J. Cura
Hi Omer, thanks for reporting this.

Can you check what packages are installed on the phone?
This command should tell you that: $ click list | sort

thanks,

On Tue, Jun 2, 2015 at 12:21 PM, Omer Akram  wrote:
> Public bug reported:
>
> I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
> proposed/bq-aquaris.en
>
> After the upgrade, some of the Apps are appearing twice, see the
> attached screenshot.
>
> ** Affects: unity-scope-click (Ubuntu)
>  Importance: Undecided
>  Status: New
>
> ** Attachment added: "twice.png"
>
> https://bugs.launchpad.net/bugs/1461138/+attachment/4408709/+files/twice.png
>
> --
> You received this bug notification because you are a member of Ubuntu
> One Client Engineering team, which is subscribed to unity-scope-click in
> Ubuntu.
> https://bugs.launchpad.net/bugs/1461138
>
> Title:
>   Few click icons are appearing twice after upgrade to RC
>
> Status in unity-scope-click package in Ubuntu:
>   New
>
> Bug description:
>   I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
>   proposed/bq-aquaris.en
>
>   After the upgrade, some of the Apps are appearing twice, see the
>   attached screenshot.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1461138/+subscriptions


** Changed in: unity-scope-click (Ubuntu)
   Status: New => Incomplete

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

Title:
  Few click icons are appearing twice after upgrade to RC

Status in unity-scope-click package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  After the upgrade, some of the Apps are appearing twice, see the
  attached screenshot.

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

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


[Touch-packages] [Bug 1461143] [NEW] Mouse and pointing stick share pointer speed setting

2015-06-02 Thread wastrel
Public bug reported:

The pointing stick on my laptop keyboard shares the pointer speed
setting with the external USB mouse, so it's impossible to use both
concurrently.

When I undock the laptop I have to change the pointer speed to fast or the 
pointing stick is unusable.
When I dock the laptop this change must be reversed or the mouse is unusable.

When the laptop is docked, switching between pointing devices is
cumbersome as the speed must be changed each time.

There is a separate setting for touchpad, there should be one for the
other integrated pointing device.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.5+14.04.20150521.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Jun  2 11:29:06 2015
InstallationDate: Installed on 2014-02-04 (483 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-06-09 (358 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Mouse and pointing stick share pointer speed setting

Status in unity package in Ubuntu:
  New

Bug description:
  The pointing stick on my laptop keyboard shares the pointer speed
  setting with the external USB mouse, so it's impossible to use both
  concurrently.

  When I undock the laptop I have to change the pointer speed to fast or the 
pointing stick is unusable.
  When I dock the laptop this change must be reversed or the mouse is unusable.

  When the laptop is docked, switching between pointing devices is
  cumbersome as the speed must be changed each time.

  There is a separate setting for touchpad, there should be one for the
  other integrated pointing device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.5+14.04.20150521.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Jun  2 11:29:06 2015
  InstallationDate: Installed on 2014-02-04 (483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-06-09 (358 days ago)

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

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


[Touch-packages] [Bug 1461138] [NEW] Few click icons are appearing twice after upgrade to RC

2015-06-02 Thread Omer Akram
Public bug reported:

I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
proposed/bq-aquaris.en

After the upgrade, some of the Apps are appearing twice, see the
attached screenshot.

** Affects: unity-scope-click (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "twice.png"
   https://bugs.launchpad.net/bugs/1461138/+attachment/4408709/+files/twice.png

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

Title:
  Few click icons are appearing twice after upgrade to RC

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  After the upgrade, some of the Apps are appearing twice, see the
  attached screenshot.

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

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


[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-06-02 Thread Pat McGowan
setting for the krillin ota

** Changed in: canonical-devices-system-image
Milestone: ww24-2015 => ww22-2015

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Messaging Menu:
  New
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators

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

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


[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-06-02 Thread Magdalena Mirowicz
Renato, regarding LED light, it's fine to leave it blue

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Messaging Menu:
  New
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators

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

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


[Touch-packages] [Bug 1450894] Re: [Indicators] Messaging indicator does not indicate that there is a new message

2015-06-02 Thread Charles Kerr
For the green icon, ubuntu-themes' file "messages-new.svg" needs to be
changed to use the #3FB24F color referred to by design.

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

** Changed in: indicator-messages (Ubuntu)
 Assignee: (unassigned) => Matthieu James (tiheum)

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

Title:
  [Indicators] Messaging indicator does not indicate that there is a new
  message

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Messaging Menu:
  New
Status in Themes for Ubuntu:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in indicator-messages package in Ubuntu:
  Confirmed

Bug description:
  When you receive a message the indicator menu turns from opaque to
  full white to indicate that there is a new message. But this is not
  clear since all the other icons are white and you do not see any
  difference.

  This is very confuse to understand that the indicator is in a
  different state from the other indicators or if it needs attention.

  --DESIGN RESOLUTION---

  Please use the current ubuntu theme green to indicate that there is a
  new message - #3FB24F, the same green as we use for the battery icon
  in indicators

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
Hi Martin.

I have attached the output. Case a is with a combined wireless usb
dongle for a microsoft keyboard. Case b is for a wired usb keyboard
(logitech) and wired mouse (hp). Case c is with just the mouse. The js0
is not created for the last case.

I am of course interested in getting the bug fixed, but even more in
learning how to debug and fix it. So any details about what you think is
wrong would be much appreciated :)

** Attachment added: "a1"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408698/+files/a1

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
** Attachment added: "a2"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408699/+files/a2

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
** Attachment added: "b1"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408701/+files/b1

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
** Attachment added: "c2"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408704/+files/c2

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1456347] Re: [indicators] Possibility to set the last active alarm from the quick menu

2015-06-02 Thread Charles Kerr
Design, please reopen the indicator-datetime (Ubuntu) component of this
bug after deciding the Design-side portion of this bug.

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

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

Title:
  [indicators] Possibility to set the last active alarm from the quick
  menu

Status in Ubuntu UX bugs:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When I set the alarm I want to do this quickly and not wait for the
  clock app to open. Bug 1362548 already reports this problem. A even
  quicker option would be to have the alarm item always in the clock
  quick settings menu and to be able to set the last active alarm with a
  simple on off switch.

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

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


[Touch-packages] [Bug 1044111] Re: blkid is hanging on probing nonexistant floppy drive

2015-06-02 Thread Phillip Susi
Yes, if you do not have a floppy drive, then you need to tell your bios
that you do not have one.  As an alternative, you can blacklist the fd
module to force the kernel not to use it.


** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  blkid is hanging on probing nonexistant floppy drive

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  1. Lubuntu 12.10 i386 3.5.0-11-generic
  2. util-linux 2.20.1-5.1ubuntu1
  3. I expected sudo blkid to display partition stats. This bug is reference to 
bug #1029149 gparted never completing scanning all devices.
  4. I do not get the desired output from gparted or sudo blkid.

  The attached screenshot show the lack of results when using the sudo
  blkid command.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-5.1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  Date: Thu Aug 30 18:33:46 2012
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120826)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
** Attachment added: "b2"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408702/+files/b2

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1458631] Re: udev: /dev/input/js0 is created but no joystick attached

2015-06-02 Thread Thomas Andersen
** Attachment added: "c1"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1458631/+attachment/4408703/+files/c1

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

Title:
  udev: /dev/input/js0 is created but no joystick attached

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  With ubuntu vivid i see a /dev/input/js0. I do not have a joystick or
  gamepad attached. This invalid input device cause a game in steam
  "Crypt of the necrodancer" to crash during start. The game works fine
  when I delete it.

  This appears to be a ubuntu specific bug as it does not show up on
  fedora 22.

  It goes away if I unplug the mouse/keyboard usb dongle I use. If I
  attach a wired keyboard only it does not show up. I tried adding a
  wired mouse too, but that causes js0 to appear too. The output of
  udevadm changes depending on what mouse I have attached. The following
  output is from using the dongle for my wireless mouse/keyboard (both
  microsoft products)

  $sudo udevadm info /dev/input/js0
  P: 
/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  N: input/js0
  S: input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
  S: input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: 
DEVLINKS=/dev/input/by-id/usb-Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0-if02-joystick
 /dev/input/by-path/pci-:00:1a.2-usb-0:1:1.2-joystick
  E: DEVNAME=/dev/input/js0
  E: 
DEVPATH=/devices/pci:00/:00:1a.2/usb5/5-1/5-1:1.2/0003:045E:0745.0003/input/input7/js0
  E: ID_BUS=usb
  E: ID_FOR_SEAT=input-pci-_00_1a_2-usb-0_1_1_2
  E: ID_INPUT=1
  E: ID_INPUT_JOYSTICK=1
  E: ID_INPUT_KEY=1
  E: ID_INPUT_KEYBOARD=1
  E: ID_MODEL=Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_MODEL_ENC=Microsoft®\x202.4GHz\x20Transceiver\x20v6.0
  E: ID_MODEL_ID=0745
  E: ID_PATH=pci-:00:1a.2-usb-0:1:1.2
  E: ID_PATH_TAG=pci-_00_1a_2-usb-0_1_1_2
  E: ID_REVISION=0251
  E: ID_SERIAL=Microsoft_Microsoft®_2.4GHz_Transceiver_v6.0
  E: ID_TYPE=hid
  E: ID_USB_DRIVER=usbhid
  E: ID_USB_INTERFACES=:030101:030102:03:
  E: ID_USB_INTERFACE_NUM=02
  E: ID_VENDOR=Microsoft
  E: ID_VENDOR_ENC=Microsoft
  E: ID_VENDOR_ID=045e
  E: MAJOR=13
  E: MINOR=0
  E: SUBSYSTEM=input
  E: TAGS=:seat:uaccess:
  E: USEC_INITIALIZED=117298

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

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


[Touch-packages] [Bug 1461137] [NEW] Sound indicator missing on upgrade

2015-06-02 Thread Omer Akram
Public bug reported:

The sound icon is missing when I upgraded from last promoted rtm image
to RC.

I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
proposed/bq-aquaris.en

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: armhf
CrashDB: indicator_sound
Date: Tue Jun  2 20:14:40 2015
InstallationDate: Installed on 2015-06-02 (0 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
SourcePackage: indicator-sound
ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.indicator-sound.log: indicator-sound stop/pre-start, process 3362

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


** Tags: apport-bug armhf third-party-packages vivid

** Attachment added: "missing_sound_indicator.png"
   
https://bugs.launchpad.net/bugs/1461137/+attachment/4408705/+files/missing_sound_indicator.png

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

Title:
  Sound indicator missing on upgrade

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  The sound icon is missing when I upgraded from last promoted rtm image
  to RC.

  I upgraded from ubuntu-touch/stable/bq-aquaris.en to ubuntu-touch/rc-
  proposed/bq-aquaris.en

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150508-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: armhf
  CrashDB: indicator_sound
  Date: Tue Jun  2 20:14:40 2015
  InstallationDate: Installed on 2015-06-02 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20150602-080906)
  SourcePackage: indicator-sound
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-sound.log: indicator-sound stop/pre-start, process 3362

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

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


[Touch-packages] [Bug 1401141] Re: DHCP server does not work for IPoIB (Infiniband)

2015-06-02 Thread James Page
Updates for trusty, utopic and vivid uploaded to proposed for SRU team
review.

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

Title:
  DHCP server does not work for IPoIB (Infiniband)

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Confirmed
Status in isc-dhcp source package in Utopic:
  Confirmed
Status in isc-dhcp source package in Vivid:
  Confirmed

Bug description:
  [Impact]

   * DHCP for InfiniBand IPoIB does not work currently.
   * After providing missing GPXE patch it had problems (by Mellanox tests).
   * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated.

  [Test Case]

   * To have IPoIB devices (2 if possible)
   * Try to acquire IP using either DHCPv4 or DHCPv6

  [Regression Potential]

   * DHCP for InfiniBand was not working
   * Based on already implemented code (Fedora)
   * Mellanox has tested it

  [Other Info]

  Original BUG description:

  Release:  Ubuntu 14.04.1 LTS
  Version:  4.2.4-7ubuntu12

  The current DHCP package in Ubuntu can't handle IPoIB clients.  For
  IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path.
  DHCP is not working in this mode without a patch for DHCP server.

  ISC-DHCP-SERVER Missing GPXE patch.

  After applying GPXE patch only we faced the following problems:

  After apply

  1.

  dhcp ipoib, does not write in the log on which interface the dhcp work
  upon when starting the dhcp server using “/etc/init.d/isc-dhcp-server
  start” we don’t see the line that tells on which interfaces the dhcpd
  is listening on the /var/log/syslog when running it with “dhcpd –d”
  command – we do see it.

  2.

  dhcp ipoib ipv6, it did not provide ip6 when we start 2 ib interfaces
  in a parallel using the following setup:

  HOST_A: 
  acting as a dhcp server, listening on one of its 
  ipoib (ib0) interfaces.

  HOST_B: 
  running dhcp clients on two ipoib interfaces (ib1, ib2) ib1 
  and ib2 are two ports onf the same HCA both interfaces are
  configured in /etc/interfaces such as:

  auto ib1
  iface ib1 inet6 dhcp
 both 
interfaces are configured in /etc/dhcp/dhclient.conf with their 
dhcp-client-identifier Ib0@HOST_A, Ib1@HOST_B and Ib2@HOST_B are connected to 
an infiniband switch.

  We are running on the client (HOST_B) the following:

  $ ifup ib1
  -> ib1 get configured as expected

  but then when we run on the other interface:
  $ ifup ib2
  -> ib2 get configured, but ib1 is losing its configuration

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

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


  1   2   3   >