date:20150403

** Information type changed from Private to Public

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in ibus package in Ubuntu:
  New

Bug description:
  happens on every start!

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Oct 10 17:09:08 2014
  Disassembly: => 0x7f461004dd27:   Cannot access memory at address 
0x7f461004dd27
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2013-01-14 (633 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT
  UpgradeStatus: Upgraded to utopic on 2014-09-14 (26 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1440289] [NEW] Touch, background is black and not changeable

2015-04-03 Thread ypsman

Public bug reported:

On my BQ Aquaris the Background changed to Black.
I was closing the Camera App atm. Since these the BG stays Black.
When i change it in the Options it has no Effect, also a complete Phone Reset 
didnt Work.
The BG stays black.

What Logfiles you need?

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

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

Title:
  Touch, background is black and  not changeable

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

Bug description:
  On my BQ Aquaris the Background changed to Black.
  I was closing the Camera App atm. Since these the BG stays Black.
  When i change it in the Options it has no Effect, also a complete Phone Reset 
didnt Work.
  The BG stays black.

  What Logfiles you need?

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

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

[Touch-packages] [Bug 1378117] Re: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()

** Information type changed from Private to Public

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

Title:
  ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()

Status in ibus package in Ubuntu:
  New

Bug description:
  Unclear what went wrong.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ibus 1.5.8-2ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Mon Oct  6 15:05:41 2014
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2011-05-04 (1251 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to utopic on 2014-09-15 (21 days ago)
  UserGroups: adm admin autopilot cdrom dialout libvirtd lpadmin pkcs11 plugdev 
sambashare sbuild sudo vboxusers

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

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

[Touch-packages] [Bug 1300462]

2015-04-03 Thread Cpblpublic+bugzilla

Thank you very much. I think it's been listed against LightDM on the Ubuntu bug 
site since (near) the beginning.  So it's just that it hasn't caught their 
attention yet, I suppose. Or maybe it needs another upstream link out of Ubuntu.
Thanks!

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

Title:
  Login timed out after waking from suspend

Status in fprintd:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm using fprint package for finger-print authentication.

  Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
  But half the time when it recovers from suspend, the lightdm  (?) login 
screen  instead says that authentication has timed out. For some reason I then 
have to wait a good 25 seconds  before I get another chance. At that point, I 
am able to enter a password or fingerprint as normal.

  This "time out" should not be triggered during/after a suspend.
  Also, if there is a time out for some reason, it should just wait the normal 
2 seconds required after entering an incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:29:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1300462]

2015-04-03 Thread Bugzilla-x

File a bug against LightDM and let the LightDM developers fix it, if
they can.

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

Title:
  Login timed out after waking from suspend

Status in fprintd:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm using fprint package for finger-print authentication.

  Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
  But half the time when it recovers from suspend, the lightdm  (?) login 
screen  instead says that authentication has timed out. For some reason I then 
have to wait a good 25 seconds  before I get another chance. At that point, I 
am able to enter a password or fingerprint as normal.

  This "time out" should not be triggered during/after a suspend.
  Also, if there is a time out for some reason, it should just wait the normal 
2 seconds required after entering an incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:29:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1300462]

2015-04-03 Thread Cpblpublic+bugzilla

This problem continues to plague me on the upcoming Ubuntu release
15.04.

I do not understand your instructions, or maybe am not qualified. How do
I "debug the LightDM side of things"?

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

Title:
  Login timed out after waking from suspend

Status in fprintd:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm using fprint package for finger-print authentication.

  Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
  But half the time when it recovers from suspend, the lightdm  (?) login 
screen  instead says that authentication has timed out. For some reason I then 
have to wait a good 25 seconds  before I get another chance. At that point, I 
am able to enter a password or fingerprint as normal.

  This "time out" should not be triggered during/after a suspend.
  Also, if there is a time out for some reason, it should just wait the normal 
2 seconds required after entering an incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:29:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1214540] Re: apparmor is shutting down syslog - and why ?

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

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

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

Title:
  apparmor is shutting down syslog - and why ?

Status in rsyslog package in Ubuntu:
  Expired

Bug description:
  here is Ubuntu 12.10 resp. pear OS 7.0.1 with rsyslogd 5.8.6 and
  kernel 3.10-RC4 :

  ( since update to kernel 3.10-RC4 - date and time are not shown in
  syslog any more while scrolling - only now stopped by apparmor - then
  date and time are shown ? )

  obviously apparmor is shutting down rsyslogd - and then syslog stops
  to protocol and stops to scroll on.

  here is output of syslog yesterday, when rsyslogd resp. syslog crashed
  ( as so often ) :

  pluto cracklib: no dictionary update necessary.
  Aug 19 11:17:23 pluto kernel: [ 8090.193574] audit_printk_skb: 57 callbacks 
suppressed
  Aug 19 11:17:23 pluto kernel: [ 8090.193576] type=1400 
audit(1376903843.989:36): apparmor="STATUS" operation="profile_replace" 
name="/usr/lib/cups/backend/cups-pdf" pid=26536 comm="apparmor_parser"
  Aug 19 11:17:24 pluto kernel: [ 8090.193899] type=1400 
audit(1376903843.993:37): apparmor="STATUS" operation="profile_replace" 
name="/usr/sbin/cupsd" pid=26536 comm="apparmor_parser"
  Aug 19 11:17:24 pluto kernel: [ 8090.882368] FW REJECT (input): IN=eth0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:00:23:5e:6f:ab:d9:08:00 SRC=10.158.0.1 
DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=43484 PROTO=UDP 
SPT=67 DPT=68 LEN=308
  Aug 19 11:17:26 pluto kernel: [ 8093.100463] FW REJECT (input): IN=eth0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:00:23:5e:6f:ab:d9:08:00 SRC=10.158.0.1 
DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=43579 PROTO=UDP 
SPT=67 DPT=68 LEN=308
  Aug 19 11:17:28 pluto dhclient: DHCPREQUEST of 78.94.198.169 on eth0 to 
10.158.0.1 port 67

  ( often syslog is simply stopped too by signal 15 - but not here
  yesterday ... )

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

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

[Touch-packages] [Bug 1406565] Re: Device lock after a certain period.

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

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

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

Title:
  Device lock after a certain period.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When I start to use the computer, the device (mouse) functions
  normally. After a certain period of use, it starts to get out of
  control on the screen when I move it ie it loses focus, gets out of
  control but this happens over a period of two (2) seconds. After, use
  it normally and when I'm using the computer, surfing the Internet when
  I open several tabs, each eight (8) or so, it simply for the screen
  and disobeys my device via command (mouse). The keyboard works
  normally up because I can use the keys "alt + tab" to switch between
  windows normally, and the "tab" to jump between the hyperlink fields
  and input fields, and can not type normally. Tested on Microsoft
  Windows XP the device, and it presented no problem. I used it for a
  period of ten (10) continuous hours and it presented no problem. I
  believe the problem is in this package as I was to the Ubuntu forums,
  and realized that there are many people complaining about the same
  problem but with a different mouse models. So I can rule out that this
  problem is related to hardware because not only happens in my but on
  other hardware of different brands and models.

  weiller@weiller-desktop:~/Downloads/xorg-docs-1.7$ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  weiller@weiller-desktop:~/Downloads/xorg-docs-1.7$ apt-cache policy 
xserver-xorg-input-mouse 
  xserver-xorg-input-mouse:
Instalado: 1:1.9.1-1
Candidato: 1:1.9.1-1
Tabela de versão:
   *** 1:1.9.1-1 0
  500 http://ubuntu.c3sl.ufpr.br/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status
   1:1.9.0-1build2 0
  500 http://archive.ubuntu.com/ubuntu/ utopic/main i386 Packages

  I hope it will be analyzed and redone this file "xserver-xorg-input-
  mouse", and is located the error as to solve this problem is probably
  in this file.

  It happened that the mouse catching and only resolved when I restart
  the computer terminal, using the keyboard because it works normally
  and launching the command "sudo reboot" by entering the password and
  pressing the "enter" key. After the restart, the mouse works normally
  but it after a while, around the same cycle consisting of lose focus,
  ie become "windsock" on the screen or in other words, I lose control
  of it on the screen but this only happens in a period of one (1) or
  two (2) seconds and it returns to normal, but then this happens again
  and is thus during the same period, which is one (1) or two (2 )
  seconds and returns to normal. This happens suddenly and there comes a
  time that the arrow is stagnant on the screen that is, it hangs on the
  screen, and that can only solve reinciando the computer using the
  keyboard to enter the terminal and running the command "sudo reboot"
  by entering the password and pressing the "enter" key.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-input-mouse 1:1.9.1-1
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic i686
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Dec 30 12:17:31 2014
  InstallationDate: Installed on 2014-11-11 (48 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  SourcePackage: xserver-xorg-input-mouse
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroRelease: Ubuntu 15.04
  DistroVariant: ubuntu
  DkmsStatus:
   tp-smapi, 0.41, 3.18.0-12-generic, i686: installed
   virtualbox, 4.3.20, 3.16.0-29-generic, i686: installed
   virtualbox, 4.3.20, 3.18.0-12-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:2e32]
  InstallationDate: Installed on 2014-11-11 (82 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic 
root=UUID=b6ac5ea6-b001-4154-8b0a-ae19f0e070d0 ro quiet spl

[Touch-packages] [Bug 1415292] Re: [945GCT-M, SigmaTel STAC9221 A2, Pink Speaker, Rear] No sound at all

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

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

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

Title:
  [945GCT-M, SigmaTel STAC9221 A2, Pink Speaker, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  no se oye

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nestor 2062 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 17:44:48 2015
  InstallationDate: Installed on 2012-09-11 (868 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=es_VE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_VE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio Interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1371 F pulseaudio
nestor 2062 F pulseaudio
  Symptom_Jack: Pink Speaker, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [945GCT-M, SigmaTel STAC9221 A2, Pink Speaker, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-23 (157 days ago)
  dmi.bios.date: 07/18/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 945GCT-M
  dmi.board.vendor: Intel
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd07/18/2008:svnECS:pn945GCT-M:pvr2.0:rvnIntel:rn945GCT-M:rvr2.0:cvnECS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 945GCT-M
  dmi.product.version: 2.0
  dmi.sys.vendor: ECS

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

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

[Touch-packages] [Bug 1417302] Re: NetworkManager fails to activate connection on modem

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  NetworkManager fails to activate connection on modem

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  Trying to activate /ril_0/context1 on ril_0 and get the following.
  It's almost the same code that produced this classic bug #1378102

  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): link 
connected
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ril_0): IPv4 
static configuration:
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:address 
2.149.176.49/24
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:gateway 
2.149.176.49
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:DNS 
193.213.112.4
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:DNS 
130.67.15.198
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:mms proxy: 
10.10.10.11:8080
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 
41]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) starting connection 'ccmni0'
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 1 of 5 (Device Prepare) scheduled...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 1 of 5 (Device Prepare) started...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 2 of 5 (Device Configure) scheduled...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 1 of 5 (Device Prepare) complete.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 2 of 5 (Device Configure) starting...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: prepare -> config (reason 'none') [40 50 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 2 of 5 (Device Configure) successful.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 3 of 5 (IP Configure Start) scheduled.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 2 of 5 (Device Configure) complete.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 3 of 5 (IP Configure Start) started...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: config -> ip-config (reason 'none') [50 70 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 3 of 5 (IP Configure Start) complete.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 5 of 5 (IPv4 Commit) started...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Could not send 
ARP for local address 2.149.176.49: Failed to execute child process 
"/usr/bin/arping" (No such file or directory)
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: ip-config -> ip-check (reason 'none') [70 80 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 5 of 5 (IPv4 Commit) complete.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: ip-check -> secondaries (reason 'none') [80 90 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: secondaries -> activated (reason 'none') [90 100 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  NetworkManager 
state is now CONNECTED_LOCAL
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) successful, device activated.
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ril_0) starting connection '/242013054944676/context1'
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ril_0) Stage 1 of 5 (Device Prepare) scheduled...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ril_0) Stage 1 of 5 (Device Prepare) started...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ril_0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  NetworkManager 
state is now CONNECTING
  Feb  2

[Touch-packages] [Bug 1435492] Re: Xsession.d script assumes that /sbin is in $PATH

This bug was fixed in the package upstart - 1.13.2-0ubuntu12

---
upstart (1.13.2-0ubuntu12) vivid; urgency=medium

  * debian/xsession.d/99upstart:
Don't assume that /sbin is in $PATH when calling upstart
(LP: #1435492).
 -- Gunnar HjalmarssonFri, 03 Apr 2015 14:48:00 +0100

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

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

Title:
  Xsession.d script assumes that /sbin is in $PATH

Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  According to changelog.Debian from version 1.12.3 on lightdm is using
  "bash for the session to improve error handling" to fix #678421.

  Unfortunately this can break the session start up when the user sets
  the $PATH environment variable in ~/.bashrc. Then /sbin might no
  longer be in $PATH and /etc/X11/Xsession.d/99cadence-session-start
  won't find /sbin/upstart when calling "upstart --user"

  The mechanism is the following:

  1. /usr/sbin/lightdm-session lines 37-42 source among others
  ~/.profile

  2. The usual .profile of /etc/skel will source ~/.bashrc if the shell
  is Bash (and not /bin/sh)

  3. ~/.bashrc (maybe) is setting $PATH without /sbin

  4. upstart --user call fails as /sbin is not in $PATH

  Suggested solutions:

  * switch back to /bin/sh

  * make sure that /sbin is in $PATH

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

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

[Touch-packages] [Bug 1295822] Re: kmod crashed with SIGSEGV in kmod_module_dependency_symbol_get_crc()

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

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

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

Title:
  kmod crashed with SIGSEGV in kmod_module_dependency_symbol_get_crc()

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: kmod 15-0ubuntu5
  Uname: Linux 3.14.0-031400rc6-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 17 10:54:46 2014
  ExecutablePath: /bin/kmod
  InstallationDate: Installed on 2014-03-05 (15 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: depmod -a -b /tmp/mkinitramfs_NiGLg8 3.14.0-031400rc7-generic
  SegvAnalysis:
   Segfault happened at: 0x7ffe2c3ebcc9:mov(%rax),%rax
   PC (0x7ffe2c3ebcc9) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: kmod
  StacktraceTop:
   ?? ()
   ?? ()
   __libc_start_main (main=0x7ffe2c3d9240, argc=5, argv=0x7fff8722ab88, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff8722ab78) at libc-start.c:285
   ?? ()
  Title: kmod crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1440275] [NEW] Ubuntu GNOME only allows regional format setting for US, UK, Canada, Australia, and NZ

2015-04-03 Thread Ki Bum Lee

Public bug reported:

I installed Ubuntu GNOME 15.04 Beta 2. I set the system locale to Korean
language, which worked okay. When I tried to set regional format (date,
time, currency, number, metric, etc.), however, the options are only
limited to 5 regions: US, UK, Canada, Australia, New Zealand. I do live
in the US, but I want to set the regional format in Korean because that
goes with the system language. I currently set the regional format to
that of Canada because I am not familiar with US system of yards, feet
and pounds. As you can see in the attached screenshot, the date format
shown on the middle of the task bar is a mixture of English and Korean
(Frankenstein-ish).

As I browsed through the bug report launchpad site, I found this bug has
a long history which dates back to Ubuntu version 9.04. I have installed
Ubuntu GNOME 14.04 LTS on my other computer and it does not have the
same bug. I guess it has something to do with the newly introduced
"systemd"?

I would very much like to see this bug is fixed ASAP (at least before
the release of 15.04 proper version). I love GNOME interface, but this
bug annoys me. Regards.

** Affects: indicator-datetime (Ubuntu)
Importance: Undecided
Status: New

** Attachment added: "Ubuntu GNOME Regional Format Bug.png"

https://bugs.launchpad.net/bugs/1440275/+attachment/4365563/+files/Ubuntu%20GNOME%20Regional%20Format%20Bug.png

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

Title:
Ubuntu GNOME only allows regional format setting for US, UK, Canada,
Australia, and NZ

Status in indicator-datetime package in Ubuntu:
New

Bug description:
I installed Ubuntu GNOME 15.04 Beta 2. I set the system locale to
Korean language, which worked okay. When I tried to set regional
format (date, time, currency, number, metric, etc.), however, the
options are only limited to 5 regions: US, UK, Canada, Australia, New
Zealand. I do live in the US, but I want to set the regional format in
Korean because that goes with the system language. I currently set the
regional format to that of Canada because I am not familiar with US
system of yards, feet and pounds. As you can see in the attached
screenshot, the date format shown on the middle of the task bar is a
mixture of English and Korean (Frankenstein-ish).

As I browsed through the bug report launchpad site, I found this bug
has a long history which dates back to Ubuntu version 9.04. I have
installed Ubuntu GNOME 14.04 LTS on my other computer and it does not
have the same bug. I guess it has something to do with the newly
introduced "systemd"?

I would very much like to see this bug is fixed ASAP (at least before
the release of 15.04 proper version). I love GNOME interface, but this
bug annoys me. Regards.

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

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

[Touch-packages] [Bug 1440268] [NEW] [regression] python2.7 again on the desktop images

2015-04-03 Thread Matthias Klose

Public bug reported:

the python and python2.7 packages are again on the desktop images. we
had a 14.04 LTS release which only relied on python3 for the desktop.
Please don't release 15.04 with python2 on the desktop images.

trying to remove python2 from the desktop results in:

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

The following packages have unmet dependencies:
 indicator-bluetooth : Depends: unity-control-center but it is not going to be 
installed or
gnome-control-center but it is not going to be 
installed or
ubuntu-system-settings but it is not going to 
be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

something is messy, please lets fix it.

** Affects: ubuntu
 Importance: Critical
 Status: Confirmed

** Affects: Ubuntu Vivid
 Importance: Critical
 Status: Confirmed

** Package changed: python2.7 (Ubuntu) => ubuntu

** Also affects: Ubuntu Vivid
   Importance: Critical
   Status: Confirmed

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

Title:
  [regression] python2.7 again on the desktop images

Status in Ubuntu:
  Confirmed
Status in The Vivid Vervet:
  Confirmed

Bug description:
  the python and python2.7 packages are again on the desktop images. we
  had a 14.04 LTS release which only relied on python3 for the desktop.
  Please don't release 15.04 with python2 on the desktop images.

  trying to remove python2 from the desktop results in:

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

  The following packages have unmet dependencies:
   indicator-bluetooth : Depends: unity-control-center but it is not going to 
be installed or
  gnome-control-center but it is not going to 
be installed or
  ubuntu-system-settings but it is not going to 
be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  something is messy, please lets fix it.

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

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

[Touch-packages] [Bug 1440251] Re: X crashed after a reboot.. no X now

2015-04-03 Thread mike

figured out how to get my display working.. not sure if you can find out what 
caused the problem.
i had to installed the standard fglrx from the package manager..
then ran driver-manager and selected fglrx

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

Title:
  X crashed after a reboot.. no X now

Status in xorg package in Ubuntu:
  New

Bug description:
  this was fine for a while.. out of the box mint 16 was buggy with my video 
card on this brand new laptop.
  its a lenovo E545 with a Radeon HD 8450G video card.
  so i installed Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip and it 
was fine.. up until now.
  i rebooted my laptop and X never came up.. ive uninstalled the amd stuff and 
i can get X back but its tearing the screen and very unusable, like it was the 
day i got it.. if I reinstall AMD stuff, I get the spash screen back but when I 
go to log in it just sits at a blank screen with the loading icon spinning.

  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Richland [Radeon HD 8450G]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Apr  3 19:05:15 2015
  InstallationDate: Installed on 2014-03-23 (376 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1440180] Re: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Branch linked: lp:~vorlon/ubuntu/vivid/cloud-init/lp.1440180

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

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

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/1?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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

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

[Touch-packages] [Bug 1440180] Re: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

The error in the log is:

Setting up initscripts (2.88dsf-41ubuntu18) ...
insserv: warning: script 'S99teamviewer' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and overrides
insserv: Default-Start undefined, assuming empty start runlevel(s) for script 
`cron'
insserv: Default-Stop  undefined, assuming empty stop  runlevel(s) for script 
`cron'
insserv: warning: script 'teamviewer_start' missing LSB tags and overrides
insserv: There is a loop between service rc.local and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop at service rc.local if started
insserv: Starting teamviewer_start depends on rc.local and therefore on system 
facility `$all' which can not be true!
insserv: Starting teamviewer_start depends on rc.local and therefore on system 
facility `$all' which can not be true!

insserv: Max recursions depth 99 reached
insserv:  loop involving service hddtemp at depth 1

insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

This is caused by a non-Ubuntu init script on your system,
/etc/init.d/teamviewer_start, which is not an LSB init script, which
prevents the system from calculating boot ordering on upgrade.

So your non-Ubuntu init script is archaic and doesn't work right on a
recent system - however, Ubuntu should handle this more gracefully on
upgrade, rather than breaking the upgrade in the middle.

Dimitri, do you have any insight into how this should be handled?  I'm
sure it wasn't the intention to have systems with non-Ubuntu init
scripts fail to upgrade, but I don't remember what the plan was for
handling this case.

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/1?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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

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

[Touch-packages] [Bug 1435492] Re: Xsession.d script assumes that /sbin is in $PATH

2015-04-03 Thread Gunnar Hjalmarsson

Brw, would this symlink help?

$ ll /usr/share/upstart/sessions/initctl
lrwxrwxrwx 1 root root 13 apr  4 02:30 /usr/share/upstart/sessions/initctl -> 
/sbin/initctl*

OTOH I suppose that '.' must be included in $PATH for that to work, and
that's not recommended.

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

Title:
  Xsession.d script assumes that /sbin is in $PATH

Status in upstart package in Ubuntu:
  Fix Committed

Bug description:
  According to changelog.Debian from version 1.12.3 on lightdm is using
  "bash for the session to improve error handling" to fix #678421.

  Unfortunately this can break the session start up when the user sets
  the $PATH environment variable in ~/.bashrc. Then /sbin might no
  longer be in $PATH and /etc/X11/Xsession.d/99cadence-session-start
  won't find /sbin/upstart when calling "upstart --user"

  The mechanism is the following:

  1. /usr/sbin/lightdm-session lines 37-42 source among others
  ~/.profile

  2. The usual .profile of /etc/skel will source ~/.bashrc if the shell
  is Bash (and not /bin/sh)

  3. ~/.bashrc (maybe) is setting $PATH without /sbin

  4. upstart --user call fails as /sbin is not in $PATH

  Suggested solutions:

  * switch back to /bin/sh

  * make sure that /sbin is in $PATH

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

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

[Touch-packages] [Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

2015-04-03 Thread Bug Watch Updater

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

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

The remaining issue is that /etc/init.d/networking is sequenced before
network.target, with no timeout.

# cat 
/run/systemd/generator/networking.service.d/50-insserv.conf-\$network.conf 
# Automatically generated by systemd-insserv-generator

[Unit]
Wants=network.target
Before=network.target
#

ifupdown has a systemd hook that's intended to reproduce the "network-
failsafe" behavior that we had under upstart; but this only hooks into
the network-online target, not the earlier network target which is the
one that actually blocks boot (nothing on a snappy system actually
references network-online.target).

We should definitely not be blocking network.target indefinitely on boot
waiting for the results of /etc/init.d/networking.  There needs to be
some kind of timeout to allow the system to continue booting when a
network device configured in /etc/network can't be brought online -
while also allowing the system to continue trying to bring that network
device up in the background.

Since
/run/systemd/generator/networking.service.d/50-insserv.conf-\$network.conf
is created by systemd-insserv-generator, opening a systemd task as well.

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

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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

[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

Martin, I'm assigning the ifupdown and systemd tasks to you, as I'm not
sure how to fix this.  Can you please have a look?

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

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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

[Touch-packages] [Bug 1435492] Re: Xsession.d script assumes that /sbin is in $PATH

2015-04-03 Thread Gunnar Hjalmarsson

Hi Johannes,

My own feeling is that Ubuntu doesn't distinguish as strictly between
bin and sbin as you would like to see. This is the standard $PATH in the
default /etc/environment:

PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

Possibly it can be justified by the fact that the root user is not
enabled by default in a fresh Ubuntu install, but you are encouraged to
use sudo when needed. After all, running stuff in sbin as a normal user
don't typically do much harm, right?

Anyway, I think that some experienced developer should better comment on
your objection.

The easiest ways to fix it for yourself are to either not dropping /sbin
from $PATH in ~/.bashrc or prevent ~/.profile from sourcing ~/.bashrc.

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

Title:
  Xsession.d script assumes that /sbin is in $PATH

Status in upstart package in Ubuntu:
  Fix Committed

Bug description:
  According to changelog.Debian from version 1.12.3 on lightdm is using
  "bash for the session to improve error handling" to fix #678421.

  Unfortunately this can break the session start up when the user sets
  the $PATH environment variable in ~/.bashrc. Then /sbin might no
  longer be in $PATH and /etc/X11/Xsession.d/99cadence-session-start
  won't find /sbin/upstart when calling "upstart --user"

  The mechanism is the following:

  1. /usr/sbin/lightdm-session lines 37-42 source among others
  ~/.profile

  2. The usual .profile of /etc/skel will source ~/.bashrc if the shell
  is Bash (and not /bin/sh)

  3. ~/.bashrc (maybe) is setting $PATH without /sbin

  4. upstart --user call fails as /sbin is not in $PATH

  Suggested solutions:

  * switch back to /bin/sh

  * make sure that /sbin is in $PATH

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

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

[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

Sorry, that part of the systemd.special(7) manpage doesn't actually
explain the problem with network.target.  The problem is described here:

SPECIAL PASSIVE SYSTEM UNITS
   A number of special system targets are defined that can be used to
   properly order boot-up of optional services. These targets are
   generally not part of the initial boot transaction, unless they are
   explicitly pulled in by one of the implementing services. Note
   specifically that these passive target units are generally not pulled
   in by the consumer of a service, but by the provider of the service.
   This means: a consuming service should order itself after these targets
   (as appropriate), but not pull it in. A providing service should order
   itself before these targets (as appropriate) and pull it in (via a
   Wants= type dependency).

network.target is one of these "special passive system units".

Locally fixing these bugs in cloud-init and ifupdown does not unblock
the networkless boot.

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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

[Touch-packages] [Bug 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte

2015-04-03 Thread Chris Bainbridge

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

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

** Also affects: apt (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781858
   Importance: Unknown
   Status: Unknown

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

Title:
  aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8'
  codec can't decode byte 0x93 in position 1: invalid start byte

Status in apt package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  Unknown

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: aptdaemon 0.45+bzr861-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 06:17:45 2012
  ExecutablePath: /usr/sbin/aptd
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd
  ProcEnviron:
   
  PythonArgs: ['/usr/sbin/aptd']
  SourcePackage: aptdaemon
  Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' 
codec can't decode byte 0x93 in position 1: invalid start byte
  UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

I'm looking through the systemd ordering now; I've found a couple of
issues so far:

 - ifupdown: /lib/systemd/system/network-online.target.wants/ifup-wait-
all-auto.service is a broken symlink to ../ifup-all-auto.service, looks
like this should be ../ifup-wait-all-auto.service instead.

 - cloud-init: cloud-init.service declares a 'Requires=network.target',
but the definition of network.target is:

   network.target
   This unit is supposed to indicate when network functionality is
   available, but it is only very weakly defined what that is supposed
   to mean, with one exception: at shutdown, a unit that is ordered
   after network.target will be stopped before the network -- to
   whatever level it might be set up then -- is shut down. It is hence
   useful when writing service files that require network access on
   shutdown, which should order themselves after this target, but not
   pull it in. Also see Running Services After the Network is up[1]
   for more information. Also see network-online.target described
   above.

   systemd automatically adds dependencies of type After= for this
   target unit to all SysV init script service units with an LSB
   header referring to the "$network" facility.

Since cloud-init is not a provider of network connectivity, it must not
use 'Requires=network.target'.  It's possible that this should be a
dependency on 'network-online.target' instead.

Still looking.

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

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

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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

[Touch-packages] [Bug 1440251] Re: X crashed after a reboot.. no X now

2015-04-03 Thread mike

lshw -c display
  *-display   
   description: VGA compatible controller
   product: Richland [Radeon HD 8450G]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 1
   bus info: pci@:00:01.0
   version: 00
   width: 32 bits
   clock: 33MHz
   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
   configuration: driver=fglrx_pci latency=0
   resources: irq:17 memory:e000-efff ioport:3000(size=256) 
memory:f030-f033

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

Title:
  X crashed after a reboot.. no X now

Status in xorg package in Ubuntu:
  New

Bug description:
  this was fine for a while.. out of the box mint 16 was buggy with my video 
card on this brand new laptop.
  its a lenovo E545 with a Radeon HD 8450G video card.
  so i installed Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip and it 
was fine.. up until now.
  i rebooted my laptop and X never came up.. ive uninstalled the amd stuff and 
i can get X back but its tearing the screen and very unusable, like it was the 
day i got it.. if I reinstall AMD stuff, I get the spash screen back but when I 
go to log in it just sits at a blank screen with the loading icon spinning.

  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Richland [Radeon HD 8450G]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Apr  3 19:05:15 2015
  InstallationDate: Installed on 2014-03-23 (376 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1440251] [NEW] X crashed after a reboot.. no X now

2015-04-03 Thread mike

Public bug reported:

this was fine for a while.. out of the box mint 16 was buggy with my video card 
on this brand new laptop.
its a lenovo E545 with a Radeon HD 8450G video card.
so i installed Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip and it 
was fine.. up until now.
i rebooted my laptop and X never came up.. ive uninstalled the amd stuff and i 
can get X back but its tearing the screen and very unusable, like it was the 
day i got it.. if I reinstall AMD stuff, I get the spash screen back but when I 
go to log in it just sits at a blank screen with the loading icon spinning.

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Richland [Radeon HD 8450G]

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Apr  3 19:05:15 2015
InstallationDate: Installed on 2014-03-23 (376 days ago)
InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Attachment added: "apport.xorg.m47wi1.apport"
   
https://bugs.launchpad.net/bugs/1440251/+attachment/4365489/+files/apport.xorg.m47wi1.apport

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

Title:
  X crashed after a reboot.. no X now

Status in xorg package in Ubuntu:
  New

Bug description:
  this was fine for a while.. out of the box mint 16 was buggy with my video 
card on this brand new laptop.
  its a lenovo E545 with a Radeon HD 8450G video card.
  so i installed Linux_AMD_Catalyst_14.3_Beta_V1.0_B22_March12_2014.zip and it 
was fine.. up until now.
  i rebooted my laptop and X never came up.. ive uninstalled the amd stuff and 
i can get X back but its tearing the screen and very unusable, like it was the 
day i got it.. if I reinstall AMD stuff, I get the spash screen back but when I 
go to log in it just sits at a blank screen with the loading icon spinning.

  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Richland [Radeon HD 8450G]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Fri Apr  3 19:05:15 2015
  InstallationDate: Installed on 2014-03-23 (376 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1428711] Re: indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()

This bug was fixed in the package indicator-sound -
12.10.2+15.04.20150403-0ubuntu1

---
indicator-sound (12.10.2+15.04.20150403-0ubuntu1) vivid; urgency=medium

  [ Ted Gould ]
  * Handle Vala incorrectly returning null for a non-null type (LP:
#1428711)
 -- CI Train BotFri, 03 Apr 2015 14:52:02 +

** Changed in: indicator-sound (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 indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1428711

Title:
  indicator-sound-service crashed with SIGSEGV in g_variant_is_trusted()

Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  Crash seemed to happen when I opened both rhythmbox and banshee at the
  same time.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  5 10:50:51 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2011-07-08 (1336 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f072b0e3b80:mov0x20(%rdi),%eax
   PC (0x7f072b0e3b80) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-sound
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   accounts_service_user_set_player ()
   _start ()
  Title: indicator-sound-service crashed with SIGSEGV in 
g_variant_builder_add_value()
  UpgradeStatus: Upgraded to vivid on 2015-01-19 (45 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
sbuild vboxusers

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

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

[Touch-packages] [Bug 1170299] Re: Pulseaudio: high CPU usage

2015-04-03 Thread Danil Lopatin

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

On my machine it depends on google chrome. On running chrome it consumes
about 10% CPU.

Environment:
pulseaudio 4.0
Google Chrome 41.0.2272.118

Linux 3.16.0-33-generic #44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04.2 LTS
Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz

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

Title:
  Pulseaudio: high CPU usage

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Running a KDE session, the Pulseaudio CPU usage is constantly over 25%, even 
without audio activity.
  If you need more informations, please ask.
  Thanks,

  Albert

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raffaele   2020 F pulseaudio
  Date: Thu Apr 18 12:21:19 2013
  InstallationDate: Installed on 2013-03-15 (34 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130314)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 144A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058811242D10010020100:rvnHewlett-Packard:rn144A:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058811242D10010020100
  dmi.sys.vendor: Hewlett-Packard

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

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

2015-04-03 Thread Adam Olsen

When I tried kernel 3.19, I also lost wifi.  Using the iwlwifi firmware
from the 3.18 kernel fixed it, though.

On Fri, Apr 3, 2015 at 2:55 PM klinge <1414...@bugs.launchpad.net>
wrote:

> @GH (chili-g) and Timo
> I have a T450s and ubuntu 14.04 and tried kernel 3.19.0-11.11 and
> 3.19.0-12.12. I experienced the same strange issues wit wifi in the sense
> that it just didn't exist any more.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1414930
>
> Title:
>   [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
>   work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions
>

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

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

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

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

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

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

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

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

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

[Touch-packages] [Bug 1438870] Re: Lock screen doesn't emit ActiveChanged signal

2015-04-03 Thread Marc Deslauriers

This is CVE-2015-1319

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1319

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

Title:
  Lock screen doesn't emit ActiveChanged signal

Status in Unity:
  New
Status in unity package in Ubuntu:
  New
Status in unity source package in Trusty:
  New
Status in unity source package in Utopic:
  New
Status in unity source package in Vivid:
  New

Bug description:
  tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is
  locked/unlocked

  Long version:

  unity-settings-daemon's automount plugin has code to detect whether
  the screen is locked or not before automatically mounting a volume.
  This prevents someone from inserting a USB thumb drive when the screen
  is locked and exploiting a possible nautilus thumbnailer
  vulnerability. (See bug #714958 for original implementation details.)

  In Ubuntu 14.04, this code no longer works. Inserting a USB thumb
  drive while the screen is locked results in a Nautilus window opening
  underneath the lock screen, and the contents of the USB thumb drive
  being read.

  Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no
  longer emits the org.gnome.ScreenSaver ActiveChanged signal when the
  screen gets locked or unlocked.

  To test:

  1- in terminal, type:
  dbus-monitor 
"type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'"
  2- Lock the screen
  3- Unlock the screen
  4- Notice that no signal was received

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150330-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Mar 31 15:15:48 2015
  InstallationDate: Installed on 2013-11-26 (489 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago)

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

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

[Touch-packages] [Bug 1440198] Re: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 9

2015-04-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 9

Status in sudo package in Ubuntu:
  New

Bug description:
  crashes while updating

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: sudo 1.8.9p5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Sat Apr  4 02:17:50 2015
  DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 9
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 9
  InstallationDate: Installed on 2015-02-10 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  SourcePackage: sudo
  Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 9
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1440198] [NEW] package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 9

2015-04-03 Thread gurpartap

Public bug reported:

crashes while updating

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: sudo 1.8.9p5-1ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
Date: Sat Apr  4 02:17:50 2015
DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 9
ErrorMessage: subprocess installed post-installation script returned error exit 
status 9
InstallationDate: Installed on 2015-02-10 (52 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
SourcePackage: sudo
Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 9
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK

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


** Tags: amd64 apport-package trusty

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

Title:
  package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 9

Status in sudo package in Ubuntu:
  New

Bug description:
  crashes while updating

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: sudo 1.8.9p5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Sat Apr  4 02:17:50 2015
  DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1.1:subprocess installed 
post-installation script returned error exit status 9
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 9
  InstallationDate: Installed on 2015-02-10 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac 
(20140417)
  SourcePackage: sudo
  Title: package sudo 1.8.9p5-1ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 9
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

2015-04-03 Thread klinge

@GH (chili-g) and Timo
I have a T450s and ubuntu 14.04 and tried kernel 3.19.0-11.11 and 3.19.0-12.12. 
I experienced the same strange issues wit wifi in the sense that it just didn't 
exist any more.

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

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

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

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

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

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

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

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

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

[Touch-packages] [Bug 1439923] Re: GTK does not build because gtk_menu_tracker_item_get_menu_item does not always return a value

2015-04-03 Thread Steve Dodier-Lazaro

I've just checked upstream GTK, and these two methods only exist in
Ubuntu. They come from the patch named
debian/patches/ubuntu_gtk_custom_menu_items.patch

Cheers,

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

Title:
  GTK does not build because gtk_menu_tracker_item_get_menu_item does
  not always return a value

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Tested version: 3.14.11-0ubuntu1
  Bug most likely introduced in: 3.10.6-0ubuntu1

  gtk_menu_tracker_item_get_menu_item and
  gtk_menu_tracker_item_get_action_namespace both have return types, but
  use g_return_if_fail instead of g_return_val_if_fail.

  Attached is a diff of the change I made to make my Clang build the
  package, although you might want to verify whether returning NULL is
  correct (I have no idea what GtkMenuTrackerItem is).

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

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

[Touch-packages] [Bug 1440180] Re: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-04-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/1?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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

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

[Touch-packages] [Bug 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04

2015-04-03 Thread Mario Limonciello

** Changed in: dell-sputnik
   Status: New => Invalid

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys
  stopped working in Ubuntu 15.04

Status in Dell Sputnik:
  Invalid
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Volume hotkeys were working and now they're not. A coworker has
  another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated
  in a week, and the hotkeys function, so it seems like the bug came up
  sometime in the past week.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   jared  4299 F...m arecord
   /dev/snd/controlC1:  jared  2929 F pulseaudio
   /dev/snd/controlC0:  jared  2929 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Feb 18 19:49:30 2015
  InstallationDate: Installed on 2014-11-03 (107 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago)
  dmi.bios.date: 02/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0144PA
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X04
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions

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

[Touch-packages] [Bug 1440180] Re: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-04-03 Thread Ubuntu Foundations Team Bug Bot

** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1440180/+attachment/4365370/+files/VarLogDistupgradeTermlog.gz

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

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

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/1?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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

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

[Touch-packages] [Bug 1439988] Re: package init-system-helpers 1.22ubuntu4 failed to install/upgrade: trying to overwrite '/lib/init/apparmor-profile-load', which is also in package upstart-bin 1.13.2

2015-04-03 Thread Manoj Iyer

updating from http://us.archive.ubuntu.com/ubuntu/ vivid main I get the
same error.

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

Title:
  package init-system-helpers 1.22ubuntu4 failed to install/upgrade:
  trying to overwrite '/lib/init/apparmor-profile-load', which is also
  in package upstart-bin 1.13.2-0ubuntu9

Status in init-system-helpers package in Ubuntu:
  Invalid

Bug description:
  x

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: init-system-helpers 1.22ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  Date: Fri Apr  3 10:20:08 2015
  DpkgTerminalLog:
   Preparing to unpack .../init-system-helpers_1.22ubuntu6_all.deb ...
   Unpacking init-system-helpers (1.22ubuntu6) over (1.22ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/init-system-helpers_1.22ubuntu6_all.deb (--unpack):
trying to overwrite '/lib/init/apparmor-profile-load', which is also in 
package upstart-bin 1.13.2-0ubuntu9
  DuplicateSignature: package:init-system-helpers:1.22ubuntu4:trying to 
overwrite '/lib/init/apparmor-profile-load', which is also in package 
upstart-bin 1.13.2-0ubuntu9
  ErrorMessage: trying to overwrite '/lib/init/apparmor-profile-load', which is 
also in package upstart-bin 1.13.2-0ubuntu9
  InstallationDate: Installed on 2015-03-21 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.24ubuntu1
   apt  1.0.9.7ubuntu3
  SourcePackage: init-system-helpers
  Title: package init-system-helpers 1.22ubuntu4 failed to install/upgrade: 
trying to overwrite '/lib/init/apparmor-profile-load', which is also in package 
upstart-bin 1.13.2-0ubuntu9
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1439988/+subscriptions

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

[Touch-packages] [Bug 1440070] Re: openssh-server attempts to connect to upstart and the connection is refused

2015-04-03 Thread Seth Arnold

** Tags added: systemd-boot

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

Title:
  openssh-server attempts to connect to upstart and the connection is
  refused

Status in openssh package in Ubuntu:
  New

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  pkg-name:
  christian@Moustachio:~/Code$ apt-cache policy openssh-server
  openssh-server:
Installed: 1:6.7p1-5
Candidate: 1:6.7p1-5
Version table:
   *** 1:6.7p1-5 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  On Ubuntu 15.04 (Vivid Ververt) the installation of the package 
openssh-server displays the following error message:

  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

  Running 'systemctl status ssh' shows that systemd knows about the
  service:

  christian@Moustachio:~/Code$ ubuntu-bug openssh-server
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:12244): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  christian@Moustachio:~/Code$ systemctl status ssh
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Fri 2015-04-03 07:43:01 MDT; 4min 41s ago
   Main PID: 11689 (sshd)
 CGroup: /system.slice/ssh.service
 └─11689 /usr/sbin/sshd -D

  Apr 03 07:43:01 Moustachio systemd[1]: Started OpenBSD Secure Shell server.
  Apr 03 07:43:01 Moustachio systemd[1]: Starting OpenBSD Secure Shell server...
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on 0.0.0.0 port 22.
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on :: port 22.

  It appears that sshd is attempting to register with upstart and with
  systemd. SInce Ubuntu 15.04 upstart has been replaced with systemd. I
  expected openssh-server on Ubuntu 15.04 to not want to use upstart. It
  does properly use systemd, it just prints an error about trying to
  tallk to upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-server 1:6.7p1-5
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  3 07:45:13 2015
  InstallationDate: Installed on 2015-03-23 (11 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150322)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1440184] [NEW] Message view blank when invoked over url

2015-04-03 Thread Michał Sawicz

Public bug reported:

Steps:
* go to dialer, bottom swipe for history, drag a contact left and tap on 
message icon
or
* tap on an incoming message notification
or
* invoke url-dispatcher, replacing "" with a number you have messaging 
history for:
$ gdbus call --session -d com.canonical.URLDispatcher -o 
/com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 
"message:///" ""
* send a message from that page

Expected:
* you can see the message history
* new message shows after sending

Current:
* there's a blank page
* still blank after sending

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: messaging-app 0.1+15.04.20150318-0ubuntu1
Uname: Linux 3.10.35+ armv7l
ApportVersion: 2.17-0ubuntu1
Architecture: armhf
Date: Fri Apr  3 21:40:02 2015
InstallationDate: Installed on 2015-04-03 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150403-020204)
SourcePackage: messaging-app
SystemImageInfo:
 current build number: 160
 device name: m75
 channel: ubuntu-touch/vivid-proposed
 last update: 2015-04-03 10:36:07
 version version: 160
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf vivid

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

Title:
  Message view blank when invoked over url

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Steps:
  * go to dialer, bottom swipe for history, drag a contact left and tap on 
message icon
  or
  * tap on an incoming message notification
  or
  * invoke url-dispatcher, replacing "" with a number you have 
messaging history for:
  $ gdbus call --session -d com.canonical.URLDispatcher -o 
/com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 
"message:///" ""
  * send a message from that page

  Expected:
  * you can see the message history
  * new message shows after sending

  Current:
  * there's a blank page
  * still blank after sending

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: messaging-app 0.1+15.04.20150318-0ubuntu1
  Uname: Linux 3.10.35+ armv7l
  ApportVersion: 2.17-0ubuntu1
  Architecture: armhf
  Date: Fri Apr  3 21:40:02 2015
  InstallationDate: Installed on 2015-04-03 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150403-020204)
  SourcePackage: messaging-app
  SystemImageInfo:
   current build number: 160
   device name: m75
   channel: ubuntu-touch/vivid-proposed
   last update: 2015-04-03 10:36:07
   version version: 160
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1438824] Re: ALL FSCKs triggered for no apparent reason

2015-04-03 Thread gregrwm

"several times in a row" is ambiguous, sorry, to be more clear, all
filesystems are checked once through per bootup.  Or, sometimes, the
bootup is normal (ie does not check all filesystems).  whatever triggers
it, checking all filesystems seems to happen several bootups in a row,
then i'll enjoy several bootups in a row without all the checking.

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

Title:
  ALL FSCKs triggered for no apparent reason

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  this bug has been around since early in vivid devel cycle, both before
  and after making systemd the default.

  i AM GRATEFUL that systemd DOES know how to properly parallelize all
  the fsck processes, activating only one per spindle at all times.

  still, i see no apparent reason that very frequently (tho not always)
  fsck is scheduled for ALL filesystems, when the preceeding event was a
  proper shutdown/reboot.  i may reboot several times in a day
  (switching between different vivid installs) and often ALL filesystems
  are checked several times in a row.

  the current bootup is one such.  several fsck processes still continue
  as i write this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-lowlatency 3.19.2
  Uname: Linux 3.19.0-10-lowlatency i686
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Mar 31 12:35:50 2015
  InstallationDate: Installed on 2015-03-30 (0 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Beta i386 (20150326)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=960c92bd-69d3-415f-93b6-2242187e3557 panic=30
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1438824] Re: ALL FSCKs triggered for no apparent reason

2015-04-03 Thread gregrwm

all spindles here are MBR.  before systemd this was handled by mountall.
if not systemd, what package handles this now?  you've labeled this
incomplete, what is 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/1438824

Title:
  ALL FSCKs triggered for no apparent reason

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  this bug has been around since early in vivid devel cycle, both before
  and after making systemd the default.

  i AM GRATEFUL that systemd DOES know how to properly parallelize all
  the fsck processes, activating only one per spindle at all times.

  still, i see no apparent reason that very frequently (tho not always)
  fsck is scheduled for ALL filesystems, when the preceeding event was a
  proper shutdown/reboot.  i may reboot several times in a day
  (switching between different vivid installs) and often ALL filesystems
  are checked several times in a row.

  the current bootup is one such.  several fsck processes still continue
  as i write this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-lowlatency 3.19.2
  Uname: Linux 3.19.0-10-lowlatency i686
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Mar 31 12:35:50 2015
  InstallationDate: Installed on 2015-03-30 (0 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Beta i386 (20150326)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz ro 
root=UUID=960c92bd-69d3-415f-93b6-2242187e3557 panic=30
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1440180] [NEW] package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-04-03 Thread James M Knock

Public bug reported:

I have no idea. The seems to have failed. If 1/99 fails, this is my
second of two that has failed. Why am I 1/1?

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: initscripts 2.88dsf-41ubuntu18
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
Date: Fri Apr  3 15:16:04 2015
DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-08-09 (237 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: sysvinit
Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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


** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic

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

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

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have no idea. The seems to have failed. If 1/99 fails, this is my
  second of two that has failed. Why am I 1/1?

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr  3 15:16:04 2015
  DuplicateSignature: package:initscripts:2.88dsf-41ubuntu18:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-09 (237 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2015-04-03 (0 days ago)
  mtime.conffile..etc.default.rcS: 2014-08-08T23:23:35.190844

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

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

[Touch-packages] [Bug 1435452] Re: dh_apparmor has no dh sequencer support

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  dh_apparmor has no dh sequencer support

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  As dh_apparmor timing is critical (it must run before services are
  started with dh_installinit), it makes sense to provide direct dh
  sequencer support so that maintainers don't have to remember to run it
  directly, and cannot mistakenly call it at the wrong point, as
  happened with MySQL in bug 1421303).

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

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

[Touch-packages] [Bug 1440177] [NEW] page tearing

2015-04-03 Thread AngryMan

Public bug reported:

not even sure how i posted this, but the drivers could use some work
when being run on an nvidia card, e.g. slow firefox performance with
video (html5 & flash) and general page tearing/lack of smooth motion.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
Uname: Linux 3.19.0-11-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Apr  4 05:16:05 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation Device [10de:0479]
InstallationDate: Installed on 2015-04-03 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150402)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic 
root=UUID=47da01d8-0b6a-4af4-b5fb-ece8c1c75897 ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1003
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Sat Apr  4 02:27:23 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt Microsoft USB Optical Mouse MOUSE, id 8
 inputMicrosoft Wired Keyboard 600 KEYBOARD, id 9
 inputMicrosoft Wired Keyboard 600 KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(0): [COPY] failed to allocate class.
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: amd64 apport-bug ubuntu vivid

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

Title:
  page tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  not even sure how i posted this, but the drivers could use some work
  when being run on an nvidia card, e.g. slow firefox performance with
  video (html5 & flash) and general page tearing/lack of smooth motion.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
  Uname: Linux 3.19.0-11-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr  4 05:16:05 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0479]
  InstallationDate: Installed on 2015-04-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150402)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boo

[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5

2015-04-03 Thread Morgan

** Also affects: messaging-app
   Importance: Undecided
   Status: New

** No longer affects: messaging-app

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

Title:
  impossible receive MMS any operator on bq aquaris E4.5

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  
  In France no MMS is received regardless of the operator used on bq aquaris 
E4.5 ubuntu Edition

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

-- 
Mailing list: https://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 1440061] Re: Grey out entry in Ubuntu Unity 14.04+

2015-04-03 Thread costales

It's not really in the background, the window is hidden.

Please, uncomment this line:
costales@netbook:~$ grep "debug" /usr/share/anoise/anoise.py
#win.show_all() # For debug
costales@netbook:~$

Logout & login again. Click on the entry "Ambient Noise" of the sound
indicator (it's normal before the click) and you'll see the window, but the
entry will change to grey.

Thanks in advance!! I really apreciate the help.

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

Title:
  Grey out entry in Ubuntu Unity 14.04+

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Hi!
  I developed a player for play noise sounds from the sound indicator.

  I'm using this library:
  
http://theravingrick.blogspot.com.es/2011/02/easily-support-sound-menu-in-python.html
  in my code:
  https://code.launchpad.net/anoise

  When the player is running, the entry in the sound indicator is grey out, as 
you can see in the attachment.
  But all works fine anyway. It's just the grey color.

  I reviewed all the code and library and I'm stuck in this issue.
  FYI, these tests:
  1. With the precise indicator-sound is not grey.
  2. In Ubuntu MATE is not grey.
  3. The library is returning a critical error: 
http://paste.ubuntu.com/10730511/ But others players aren't grey.

  Thanks in advance!!

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

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

[Touch-packages] [Bug 1440171] Re: package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

2015-04-03 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  i am trying to do conference call in skype but the video doesnt work. 
  when i try calling individuals it works but for a group call it remains 
disabled.
  when i tried to install skype-bin i got this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  AptOrdering:
   libebook-contacts-1.2-0: Configure
   libedata-book-1.2-20: Configure
   libebook-1.2-14: Configure
   evolution-data-server: Configure
  Architecture: amd64
  Date: Sat Apr  4 00:27:46 2015
  DpkgHistoryLog:
   Start-Date: 2015-04-04  00:27:46
   Commandline: apt-get install skype-bin
  DpkgTerminalLog:
   dpkg: error processing package libebook-contacts-1.2-0 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: 
package:libebook-contacts-1.2-0:3.12.10-0ubuntu1~14.10.1:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-01-24 (69 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evolution-data-server
  Title: package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1440171/+subscriptions

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

[Touch-packages] [Bug 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected

2015-04-03 Thread zebul666

I am wrong. It only worked once in archlinux. I have no idea why it does
not work anymore.

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

Title:
  Laptop does not go to sleep when closing lid with external monitor
  connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on 
HDMI output, in 15.04 beta 2:
  when closing the lid of the laptop, the laptop does not go to sleep (suspend 
to ram) as expected, but instead stays on, with the external monitor still on.

  I excepted that the laptop goes to sleep and the external monitor was
  blanked and turned off. This was the behavior on 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu4
  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: Thu Apr  2 01:17:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0597]
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Apr  2 00:14:49 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 939 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost (mako)

2015-04-03 Thread Sam Bull

This has also been happening to me a little too frequently. It's
particularly bad, given that you can't use the system without these edge
gestures, being unable to return to the home screen, switch app, launch
new apps etc.

Like others, this seems to happen when in a pocket, and most times when
playing music. If music-app still has some kind of exception for
suspending the phone, then that might explain why it happens more
frequently there, if it is somehow linked to suspending.

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

Title:
  Edge gestures still get lost (mako)

Status in android package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  There are still cases where edge gestures are lost. Over the christmas
  holidays It happened about 5 times to me (in 2 weeks). Only way to
  recover is to reboot the phone. It always happened while the phone was
  in my pocket. When pulling it out of the pocket the edge gestures
  (launcher and right edge) were gone. This is most likely related to
  random taps on the screen, maybe in combination with the display
  toggling on/off.

  Haven't found a way yet to manually trigger it. Will keep on trying.

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

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

[Touch-packages] [Bug 1440171] [NEW] package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2015-04-03 Thread Subhra

Public bug reported:

i am trying to do conference call in skype but the video doesnt work. 
when i try calling individuals it works but for a group call it remains 
disabled.
when i tried to install skype-bin i got this bug.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
AptOrdering:
 libebook-contacts-1.2-0: Configure
 libedata-book-1.2-20: Configure
 libebook-1.2-14: Configure
 evolution-data-server: Configure
Architecture: amd64
Date: Sat Apr  4 00:27:46 2015
DpkgHistoryLog:
 Start-Date: 2015-04-04  00:27:46
 Commandline: apt-get install skype-bin
DpkgTerminalLog:
 dpkg: error processing package libebook-contacts-1.2-0 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature: 
package:libebook-contacts-1.2-0:3.12.10-0ubuntu1~14.10.1:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-01-24 (69 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: evolution-data-server
Title: package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

Title:
  package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  i am trying to do conference call in skype but the video doesnt work. 
  when i try calling individuals it works but for a group call it remains 
disabled.
  when i tried to install skype-bin i got this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  AptOrdering:
   libebook-contacts-1.2-0: Configure
   libedata-book-1.2-20: Configure
   libebook-1.2-14: Configure
   evolution-data-server: Configure
  Architecture: amd64
  Date: Sat Apr  4 00:27:46 2015
  DpkgHistoryLog:
   Start-Date: 2015-04-04  00:27:46
   Commandline: apt-get install skype-bin
  DpkgTerminalLog:
   dpkg: error processing package libebook-contacts-1.2-0 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: 
package:libebook-contacts-1.2-0:3.12.10-0ubuntu1~14.10.1:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-01-24 (69 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: evolution-data-server
  Title: package libebook-contacts-1.2-0 3.12.10-0ubuntu1~14.10.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1440171/+subscriptions

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

[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

2015-04-03 Thread professordes

Same deal with a Thinkpad X201 - this also now boots to the lightdm
login screen after the latest updates but it "freezes" at this point.
The cursor disappears when it is moved and the only thing that
resurrects the laptop after this is the power button.

Again:

upstart+lightdm
systemd+gdm

are both working OK on this laptop too.

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

Title:
  Xserver does not start on boot (low-graphics mode)

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  After upgrading to (32bit) vivid I hadn't got any problem, but since a
  day (daily upgraded) booting results in a dialog saying low graphics
  mode and a dialog window about this. Choosing running in default mode
  causes to boot splash to be shown forever. if I choose exit to
  console, log in then service stop then start for lightdm, it works
  then though. Maybe is not Xserver bug, but the new init system
  (systemd) race condition of starting things, or such?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  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
  CurrentDesktop: Unity
  Date: Fri Mar 20 07:35:37 2015
  DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21dd]
  InstallationDate: Installed on 2012-03-03 ( days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: LENOVO 5016NW6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago)
  dmi.bios.date: 11/04/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET38WW (1.15 )
  dmi.board.name: 5016NW6
  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:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5016NW6
  dmi.product.version: ThinkPad L520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Mar 20 07:25:51 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9196 
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1439815] Re: edge swipes stop working

2015-04-03 Thread Sam Bull

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

** This bug has been marked a duplicate of bug 1408263
   Edge gestures still get lost (mako)

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

Title:
  edge swipes stop working

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Occasionally the system gets in a state where the left/right edge
  swipes stop functioning. I've found no way to fix this other than
  restarting the phone.

  This is a critical issue given that the phone is mostly unusable
  without these gestures, there is no way to switch between apps, or to
  get out of an app, launch new apps etc.

  The issue happens often enough to be a serious issue, but not
  frequently enough for it to be reliably reproduced.

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

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

[Touch-packages] [Bug 1440162] Re: Hourglass always shows in sound settings applet

2015-04-03 Thread Christopher Townsend

** Project changed: unity => indicator-sound (Ubuntu)

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

Title:
  Hourglass always shows in sound settings applet

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  See attachment

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

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

[Touch-packages] [Bug 1440162] [NEW] Hourglass always shows in sound settings applet

You have been subscribed to a public bug:

See attachment

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


** Tags: trusty
-- 
Hourglass always shows in sound settings applet
https://bugs.launchpad.net/bugs/1440162
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to indicator-sound in Ubuntu.

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

[Touch-packages] [Bug 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected

2015-04-03 Thread zebul666

So this seems to be a new feature of systemd (introduced in systemd
211): when docked, it does not suspend when closing the lid

Changing HandleLidSwitchDocked to suspend in /etc/systemd/logind.conf
"fixed" the problem; that is I get the expected behavior that when
closing the lid the laptop goes to sleep even with a connected external
monitor

BUT ONLY ON ARCHLINUX

This work-around does not work in ubuntu !!!

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

Title:
  Laptop does not go to sleep when closing lid with external monitor
  connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on 
HDMI output, in 15.04 beta 2:
  when closing the lid of the laptop, the laptop does not go to sleep (suspend 
to ram) as expected, but instead stays on, with the external monitor still on.

  I excepted that the laptop goes to sleep and the external monitor was
  blanked and turned off. This was the behavior on 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu4
  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: Thu Apr  2 01:17:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0597]
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Apr  2 00:14:49 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 939 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1440061] Re: Grey out entry in Ubuntu Unity 14.04+

2015-04-03 Thread Kai Mast

I think the problem is that your application runs in the background.
There is no way to bring it focus using the sound menu.

How do I close it?

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

Title:
  Grey out entry in Ubuntu Unity 14.04+

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Hi!
  I developed a player for play noise sounds from the sound indicator.

  I'm using this library:
  
http://theravingrick.blogspot.com.es/2011/02/easily-support-sound-menu-in-python.html
  in my code:
  https://code.launchpad.net/anoise

  When the player is running, the entry in the sound indicator is grey out, as 
you can see in the attachment.
  But all works fine anyway. It's just the grey color.

  I reviewed all the code and library and I'm stuck in this issue.
  FYI, these tests:
  1. With the precise indicator-sound is not grey.
  2. In Ubuntu MATE is not grey.
  3. The library is returning a critical error: 
http://paste.ubuntu.com/10730511/ But others players aren't grey.

  Thanks in advance!!

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

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

[Touch-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS

2015-04-03 Thread Christopher Townsend

@Ryan,

This bug is about random log off's, not preventing a machine from going
to sleep and issues derived from that.  I believe you commented in the
wrong bug.  Please either find an appropriate bug or enter a new bug
report altogether.  Thanks!

All others,
This is a bug closed as Fixed Released and is specific to 12.04.  If you are 
seeing similar behavior, please submit a new bug report.

Thanks!

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

Title:
  Random log off in Ubuntu 12.04 LTS

Status in Unity:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in Fedora:
  New

Bug description:
  I get logged off from Ubuntu sometimes. There is no error message or
  any indication that it is going to log off. The screen goes black, and
  after 2-4 seconds, i get presented with the Ubuntu Log On Screen.

  There is no clear pattern (or at least if have not noticed any). One
  time i am working with Netbeans, another time i am using firefox. This
  also means that at present i can not clearly say what package might be
  causing this behaviour.

  I am fairly sure the problem lies in 12.04 (or more precise - the
  combination of 12.04 and the hardware i am using). I do not have the
  same problem running 11.04 or 11.10.

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

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

[Touch-packages] [Bug 1437686] Re: NTP connects any 3 min and never stops

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

** Information type changed from Private Security to Public

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

Title:
  NTP connects any 3 min and never stops

Status in ntp package in Ubuntu:
  New

Bug description:
  Hi there, i got a problem with ntp after the last update of my ubuntu
  14.04 x64 after updating tzdata and reboot the system ntp still
  connecting any 3 min again and again i only could stop it by stoping
  the ntp service completly.

  
  here are the ip 's that where connected by ntp

   129.70.132.36

  5.9.156.53

  144.76.172.53

  131.234.137.23

  91.189.94.4

  I check them by doing a whois they all seems legid to me but ntp still 
connecting all the time,
  i try sudo ntpd -q -g -x -n and it says time is still sync but ntp not stops 
connecting.

  I reinstall a fresh Ubuntu and after updating the dist the problem
  still comes back!

  Please check this and fix it.

  Greetz Onimusha

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Chris Coulson

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

** Changed in: oxide
 Assignee: (unassigned) => Michael Terry (mterry)

** Changed in: oxide
Milestone: None => branch-1.7

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.6 series:
  Triaged
Status in oxide-qt package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

** Branch linked: lp:oxide

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.6 series:
  Triaged
Status in oxide-qt package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Chris Coulson

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

** Changed in: oxide
   Importance: Undecided => High

** Also affects: oxide/1.6
   Importance: Undecided
   Status: New

** Changed in: oxide/1.6
   Importance: Undecided => High

** Changed in: oxide/1.6
   Status: New => Triaged

** Changed in: oxide/1.6
Milestone: None => 1.6.1

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.6 series:
  Triaged
Status in oxide-qt package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Michael Terry

** Changed in: oxide-qt (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: oxide-qt (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.6 series:
  Triaged
Status in oxide-qt package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1400402] Re: Task bar empty gap not refilled when program undocked

2015-04-03 Thread Henry Fleminger Thomson

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

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

Title:
  Task bar empty gap not refilled when program undocked

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I am running on Ubuntu 14.04.

  I undocked an application today from my task bar, and instead of the
  task bar getting shorter and closing up the gap, the gap where the now
  undocked application had been stayed and acted as if it was its own
  application link there, because if I dragged some applications around
  on the task bar, it would act as if it was one of them. I have
  attached a screenshot of it to this report.

  But when I moved enough stuff around, it finally decided to move
  places and ended up at the top. I have attached a screenshot of it at
  this stage with the description of "At the top of my task bar stage ".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec  8 16:44:16 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5002]
  InstallationDate: Installed on 2014-12-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 62742SG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H5ET69WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 62742SG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK IPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 62742SG
  dmi.product.version: Lenovo B590
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 12:25:49 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 827
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1440157] [NEW] WARNING **: Could not connect to geoname lookup server: Operation was cancelled

2015-04-03 Thread Doug McMahon

Public bug reported:

Test Case:
open Date & Time panel > Clock 
Enable Time in other locations
Click Choose Locations...

No other locations can be added

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CasperVersion: 1.358
CurrentDesktop: Unity
Date: Fri Apr  3 23:54:13 2015
LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-datetime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-datetime (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 indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1440157

Title:
  WARNING **: Could not connect to geoname lookup server: Operation was
  cancelled

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Test Case:
  open Date & Time panel > Clock 
  Enable Time in other locations
  Click Choose Locations...

  No other locations can be added

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.358
  CurrentDesktop: Unity
  Date: Fri Apr  3 23:54:13 2015
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1012081] Re: util-linux needs updating to 2.24.2

2015-04-03 Thread Jan

Issue present in Linux Mint 17.1 (Ubuntu 14.04).

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

Title:
  util-linux needs updating to 2.24.2

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Raring:
  Won't Fix
Status in util-linux package in Debian:
  Fix Released

Bug description:
  Applications in the default desktop - specifically gnome-disk-utility
  - depend on behaviour only introduced in util-linux 2.21+.
  Specifically if you select "Show in user interface" in mount options,
  it adds the mount option "x-gvfs-show" to the mount options in
  /etc/fstab. Mounting of this mount point then fails because the option
  is unrecognised.

  Also reported bug from the other point of view in bug #1011257

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: util-linux 2.20.1-1ubuntu3
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.1.1-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 12 12:38:02 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to quantal on 2012-06-09 (3 days ago)

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

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

[Touch-packages] [Bug 1436427] Re: Turning off WiFi doesn't set a route after the modem connects data

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

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

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

Title:
  Turning off WiFi doesn't set a route after the modem connects data

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

Bug description:
  I just switched off WiFi in order to test if the device switches
  successfully to a mobile data connection. After disabling WiFi the
  indicator showed "H" in no time. So it would seem all is fine. I
  opened the browser and no data went through.

  Here's the output of "ip route" and "list-contexts":

  phablet@ubuntu-phablet:~$ sudo ip route
  [sudo] password for phablet: 
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts 
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Name = E-Plus Web GPRS
  Settings = { Netmask=255.255.255.0 Address=10.121.30.213 
Interface=ccmni0 Method=static DomainNameServers=212.23.103.8,212.23.103.9, 
Gateway=10.121.30.213 }
  Username = eplus
  IPv6.Settings = { }
  Protocol = ip
  Active = 1
  Password = internet
  Type = internet
  AccessPointName = internet.eplus.de

  [ /ril_0/context2 ]
  IPv6.Settings = { }
  Name = E-Plus MMS
  MessageProxy = 212.23.97.153:5080
  MessageCenter = http://mms/eplus/
  Username = mms
  Settings = { }
  Protocol = ip
  Active = 0
  Password = eplus
  Type = mms
  AccessPointName = mms.eplus.de

  [ /ril_0/context3 ]
  Name = ___ubuntu_custom_apn_internet
  Settings = { }
  Username = 
  IPv6.Settings = { }
  Protocol = ip
  Active = 0
  Password = 
  Type = internet
  AccessPointName = 

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 21
  device name: krillin
  channel: ubuntu-touch/rc/bq-aquaris.en
  last update: 2015-03-13 17:11:07
  version version: 21
  version ubuntu: 20150312
  version device: 20150310-3201c0a
  version custom: 20150216-561-29-186

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

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

[Touch-packages] [Bug 1423942] Re: Replying from the indicator discards messages if invalid SIM is set as default

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  Replying from the indicator discards messages if invalid SIM is set as
  default

Status in the base for Ubuntu mobile products:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  Using rtm 240 on a bq device
  - use 2 SIMs
  - select SIM 2 as default
  - remove SIM 2
  - receive a call on SIM 1 and miss it
  - reply to the missed call from the messaging menu

  -> the reply is discarded without any error or user feedback

  The code should check that the configuration is valid and restore a
  sane default if it's not

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

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

[Touch-packages] [Bug 1437486] Re: sms notification baloon dont work to send sms directly

** Changed in: canonical-devices-system-image
   Status: New => Fix Released

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

Title:
  sms notification baloon dont work to send sms directly

Status in the base for Ubuntu mobile products:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 1423942] Re: Replying from the indicator discards messages if invalid SIM is set as default

This bug was fixed in the package telephony-service - 0.1+15.04.20150402
~rtm-0ubuntu1

---
telephony-service (0.1+15.04.20150402~rtm-0ubuntu1) 14.09; urgency=medium

  [ Tiago Salem Herrmann ]
  * Check if default sim is active before sending messages. (LP:
#1437486, #1423942)
 -- CI Train BotThu, 02 Apr 2015 20:51:32 +

** Changed in: telephony-service (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  Replying from the indicator discards messages if invalid SIM is set as
  default

Status in the base for Ubuntu mobile products:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  Using rtm 240 on a bq device
  - use 2 SIMs
  - select SIM 2 as default
  - remove SIM 2
  - receive a call on SIM 1 and miss it
  - reply to the missed call from the messaging menu

  -> the reply is discarded without any error or user feedback

  The code should check that the configuration is valid and restore a
  sane default if it's not

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

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

[Touch-packages] [Bug 1437486] Re: sms notification baloon dont work to send sms directly

This bug was fixed in the package telephony-service - 0.1+15.04.20150402
~rtm-0ubuntu1

---
telephony-service (0.1+15.04.20150402~rtm-0ubuntu1) 14.09; urgency=medium

  [ Tiago Salem Herrmann ]
  * Check if default sim is active before sending messages. (LP:
#1437486, #1423942)
 -- CI Train BotThu, 02 Apr 2015 20:51:32 +

** Changed in: telephony-service (Ubuntu RTM)
   Status: Confirmed => Fix Released

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

Title:
  sms notification baloon dont work to send sms directly

Status in the base for Ubuntu mobile products:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu RTM:
  Fix Released

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 1431582] Re: there is no wi-fi after suspend/hybernate mode

2015-04-03 Thread Twente

No, still doesn't work- NO WIFI AFTER SUSPEND/HYBERNATE
MODE!!

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

Title:
  there is no wi-fi after suspend/hybernate mode

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During last three days: after suspend/hybernate mode there is no wi-
  fi. I have to turn off Network-manager and turn it on again- only
  after that wi-fi works again

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu10
  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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 00:56:10 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-18 (510 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static  metric 1024
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.18
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  READONLY  DBUS-PATH
   ACTIVE  DEVICE  STATE  ACTIVE-PATH
   k3b   66a32a2c-3eac-46e3-a111-0c63e94bd135  802-11-wireless  1426197268  Пт. 
13 марта 2015 00:54:28  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  k3b  
   66a32a2c-3eac-46e3-a111-0c63e94bd135  
/org/freedesktop/NetworkManager/ActiveConnection/0
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1300462] Re: Login timed out after waking from suspend

2015-04-03 Thread Christopher Barrington-Leigh

This problem exists still in 15.04.  If this is a lightdm problem, what
should be done next?

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

Title:
  Login timed out after waking from suspend

Status in fprintd:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I'm using fprint package for finger-print authentication.

  Half the time when my laptop recovers from suspend, I am able to enter a 
password (or, after pressing Enter, a finger print instead).
  But half the time when it recovers from suspend, the lightdm  (?) login 
screen  instead says that authentication has timed out. For some reason I then 
have to wait a good 25 seconds  before I get another chance. At that point, I 
am able to enter a password or fingerprint as normal.

  This "time out" should not be triggered during/after a suspend.
  Also, if there is a time out for some reason, it should just wait the normal 
2 seconds required after entering an incorrect password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.9.13-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 31 17:29:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1431582] Re: there is no wi-fi after suspend/hybernate mode

2015-04-03 Thread Twente

Maybe fixed? Now after suspend/hybernate mode my notebook after some
time can find wi-fi and join them.

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

Title:
  there is no wi-fi after suspend/hybernate mode

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During last three days: after suspend/hybernate mode there is no wi-
  fi. I have to turn off Network-manager and turn it on again- only
  after that wi-fi works again

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu10
  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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 00:56:10 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-18 (510 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static  metric 1024
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.18
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  READONLY  DBUS-PATH
   ACTIVE  DEVICE  STATE  ACTIVE-PATH
   k3b   66a32a2c-3eac-46e3-a111-0c63e94bd135  802-11-wireless  1426197268  Пт. 
13 марта 2015 00:54:28  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  k3b  
   66a32a2c-3eac-46e3-a111-0c63e94bd135  
/org/freedesktop/NetworkManager/ActiveConnection/0
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1435492] Re: Xsession.d script assumes that /sbin is in $PATH

2015-04-03 Thread Johannes Mueller

The patch in #9 doesn't fix it completely for me, as also some of the
scripts in /usr/share/upstart/sessions/* assume that /sbin is in $PATH.
Some of them call initctl which resides in /sbin

Unfortunately this means that a lot of packages would need to be fixed.

A grep->loop->dpkg -S->awk->sort->uniq command gave on my machine the
following list of affected packages.

avahi-daemon
cgmanager
dbus
gnome-keyring
gnupg-agent
indicator-application
kde-workspace-bin
logrotate
openssh-client
rsync
upstart-bin

Sorry for being that late about this. I only had time now to test and
debug it.

In my opinion it's upstart's fault to put executables that are needed by
non-root users into (/usr)?/sbin. That is against what I learned back in
the 1990 when I started using UNIX / Linux.

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

Title:
  Xsession.d script assumes that /sbin is in $PATH

Status in upstart package in Ubuntu:
  Fix Committed

Bug description:
  According to changelog.Debian from version 1.12.3 on lightdm is using
  "bash for the session to improve error handling" to fix #678421.

  Unfortunately this can break the session start up when the user sets
  the $PATH environment variable in ~/.bashrc. Then /sbin might no
  longer be in $PATH and /etc/X11/Xsession.d/99cadence-session-start
  won't find /sbin/upstart when calling "upstart --user"

  The mechanism is the following:

  1. /usr/sbin/lightdm-session lines 37-42 source among others
  ~/.profile

  2. The usual .profile of /etc/skel will source ~/.bashrc if the shell
  is Bash (and not /bin/sh)

  3. ~/.bashrc (maybe) is setting $PATH without /sbin

  4. upstart --user call fails as /sbin is not in $PATH

  Suggested solutions:

  * switch back to /bin/sh

  * make sure that /sbin is in $PATH

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

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

[Touch-packages] [Bug 1421117] Re: fails to boot with "Attempted to kill init" in VMWare, absolute /sbin/init symlink does not work

2015-04-03 Thread Will Rouesnel

So can this be backported to utopic? It's kind of a serious bug since it
renders the system unbootable.

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

Title:
  fails to boot with "Attempted to kill init" in VMWare, absolute
  /sbin/init symlink does not work

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after 
permanently switching to systemd.
  I've switched to systemd with "apt install systemd-sysv --purge" (it only 
purged the upstart package) and with the default "Ubuntu" entry the boot fails 
after about 2.5 sec with a kernel panic ("Attempted to kill init"). But it 
works when edit the grub entry (in the grub shell) and add 
"init=/lib/systemd/systemd".

  Attached is the serial output (with "debug" but no "init=" parameter).

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

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

[Touch-packages] [Bug 1440128] [NEW] Cannot add extenstion to number when dialing.

2015-04-03 Thread Paweł Eichler

Public bug reported:

Adding '+' in front of entered number in dialer ends up in adding '0' in
front, moving cursor to the end of entered number and replacing last
digit with '+'.

Found on BQ Aquaris E4.5, Ubuntu 14.10, r20.

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

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

Title:
  Cannot add extenstion to number when dialing.

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Adding '+' in front of entered number in dialer ends up in adding '0'
  in front, moving cursor to the end of entered number and replacing
  last digit with '+'.

  Found on BQ Aquaris E4.5, Ubuntu 14.10, r20.

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Chris Coulson

The desktop using GL rather than GLES shouldn't affect Oxide - I don't
think it cares too much what API the application is using (and Chromium
only supports GLES with EGL in any case. "GL" in Chromium refers to one
of the windowing-system specific desktop GL API's - GLX on Linux and WGL
on Windows). Given that all GL access in Chromium happens on a dedicated
thread, it can use a different API without affecting the rest of the
application.

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in oxide-qt package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS

2015-04-03 Thread Ryan

This bug has starting affecting one of my production servers. I would
classify it as "critical". I turned off and uninstalled the screensaver
on this computer, but apparently that is not enough to prevent Ubuntu
from going to sleep.  It will go to sleep by itself even if there is NO
SCREENSAVER application installed on the operating system! That is a
CRITICAL BUG!!!

So, in an effert to stop the computer from going to sleep, I installed
XScreenSaver, and turned it to "never go to sleep, ever" settings. Now I
have to start XScreenSaver at startup, to try to PREVENT this machine
from going to sleep. But it doesn't work.

Every few days, I'll wake up and be logged out of the machine, server is
down, not live to the world. Downtime caused by this bug. If I then try
to log back in, it IMMEDIATELY logs me back out! I have to cold restart
the whole machine to get back in.

This bug is so critical that I may have to migrate away from Ubuntu if
there is no forthcoming solution.

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

Title:
  Random log off in Ubuntu 12.04 LTS

Status in Unity:
  Fix Released
Status in nvidia-graphics-drivers package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in Fedora:
  New

Bug description:
  I get logged off from Ubuntu sometimes. There is no error message or
  any indication that it is going to log off. The screen goes black, and
  after 2-4 seconds, i get presented with the Ubuntu Log On Screen.

  There is no clear pattern (or at least if have not noticed any). One
  time i am working with Netbeans, another time i am using firefox. This
  also means that at present i can not clearly say what package might be
  causing this behaviour.

  I am fairly sure the problem lies in 12.04 (or more precise - the
  combination of 12.04 and the hardware i am using). I do not have the
  same problem running 11.04 or 11.10.

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

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

[Touch-packages] [Bug 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 14.10)

2015-04-03 Thread Bug Watch Updater

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=89893.

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


On 2015-04-03T16:05:11+00:00 d❤vid seaward wrote:

Steps to reproduce:

 * Launch Unity desktop session
 * Minimize current window or alt-tab between windows
 * Reveal launcher to click on application
 * Click `Super` to bring up Dash
 * Hold `Super` to bring up Keyboard Shortcuts

What should happen:

Action completes smoothly and quickly.

What happens instead:

 * Action may be slow / animation jerky.
 * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
 * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

Notes:

This occurs on Ubuntu 14.04 and 14.10. See
https://bugs.launchpad.net/bugs/1314587 for a downstream bug report. It
was suggested there that an upstream report would be helpful.

I'm not sure which X.org component this applies to, if there is any
additional info I can provide please let me know (also see downstream
bug, linked above).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314587/comments/12


** Changed in: xorg-server
   Status: Unknown => Confirmed

** Changed in: xorg-server
   Importance: Unknown => Medium

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

Title:
  Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
  (14.04 and 14.10)

Status in Unity:
  Incomplete
Status in X.Org X server:
  Confirmed
Status in unity package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

   * Minimize current window or alt-tab between windows
   * Reveal launcher to click on application
   * Click `Super` to bring up Dash
   * Hold `Super` to bring up Keyboard Shortcuts

  What should happen:

  Action completes smoothly and quickly.

  What happens instead:

   * Action may be slow / animation jerky.
   * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
   * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

  Notes:

   * Not application specific. Minimizing is reliably slow/stalls with 
minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, 
but I use those programs more often.
   * I am using an Nvidia Optimus machine with the default Nouveau driver - no 
`nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia 
driver (including `nvidia-prime`) and it made no difference.
   * I did not experience this issue on the same machine running 13.10 (with 
Bumblebee).
   * I am running Maximus.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 12:53:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b6]
  InstallationDate: Installed on 2014-04-24 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7
  SourcePackage: xorg

[Touch-packages] [Bug 1440121] Re: Can not connect to WPA2-EAP wireless LAN with bq aquaris

2015-04-03 Thread Akos Mate

I don't know, what package is responsible for this error.

** Package changed: network-manager (Ubuntu) => ubuntu

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

Title:
  Can not connect to WPA2-EAP wireless LAN with bq aquaris

Status in Ubuntu:
  New

Bug description:
  When I touch the name of the network on the list, at the indicators
  menu, nothing happens. When I try it again 3, 4 times, the whole
  "Network" tab becomes empty, even the SIM card informations disappear,
  and the icon of the tab switches to a gear instead of the signal
  strength indicator. Then the Network tab stays empty until the next
  reboot.

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

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

[Touch-packages] [Bug 1440121] [NEW] Can not connect to WPA2-EAP wireless LAN with bq aquaris

2015-04-03 Thread Akos Mate

Public bug reported:

When I touch the name of the network on the list, at the indicators
menu, nothing happens. When I try it again 3, 4 times, the whole
"Network" tab becomes empty, even the SIM card informations disappear,
and the icon of the tab switches to a gear instead of the signal
strength indicator. Then the Network tab stays empty until the next
reboot.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: aquaris-e4.5 wifi wpa-eap

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

Title:
  Can not connect to WPA2-EAP wireless LAN with bq aquaris

Status in Ubuntu:
  New

Bug description:
  When I touch the name of the network on the list, at the indicators
  menu, nothing happens. When I try it again 3, 4 times, the whole
  "Network" tab becomes empty, even the SIM card informations disappear,
  and the icon of the tab switches to a gear instead of the signal
  strength indicator. Then the Network tab stays empty until the next
  reboot.

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

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

[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5

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

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

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

Title:
  impossible receive MMS any operator on bq aquaris E4.5

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  
  In France no MMS is received regardless of the operator used on bq aquaris 
E4.5 ubuntu Edition

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

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

[Touch-packages] [Bug 1432696] Re: [SDK] Bottom edge header improvement

2015-04-03 Thread Giorgio Venturi

** Changed in: ubuntu-ux
 Assignee: Giorgio Venturi (giorgio-venturi) => (unassigned)

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

Title:
  [SDK] Bottom edge header improvement

Status in Dekko:
  Fix Released
Status in Calendar application for Ubuntu devices:
  New
Status in Clock application for Ubuntu devices:
  Triaged
Status in Document Viewer application for Ubuntu devices:
  Triaged
Status in Ubuntu UX bugs:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  When user does a bottom edge gesture to show a new view (Address Book,
  Dialer, Clock, etc) the new header should never have a chevron
  pointing left, as it seems to suggest the wrong direction for the
  movement.

  The header of the new View should always have a chevron pointing down.
  Also, it should allow people using a gesture and dismiss the new
  screen by dragging or swiping the [chevron & title area of the header]
  downward

  UX here:
  
https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0

  VD:
  https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0

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

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

[Touch-packages] [Bug 1420395] Re: [mako] upower consuming over 17% cpu when in idle

** Changed in: canonical-devices-system-image
   Importance: High => Low

** Changed in: upower (Ubuntu)
   Importance: High => Low

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

Title:
  [mako] upower consuming over 17% cpu when in idle

Status in the base for Ubuntu mobile products:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  From the meta battery bug # 1372413
  mako running 191

  As device was not suspending and battery level running down, upower is 
reported at 17%+ cpu by the cpustat tool
   mpdecision and systemd-udevd also change their behavior.

  The upower cpu consumption is just a side effect of the amount of
  battery related events the kernel send, and specific to mako.

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

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

[Touch-packages] [Bug 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04

2015-04-03 Thread d❤vid seaward

Created and linked to https://bugs.freedesktop.org/show_bug.cgi?id=89893
as suggested.

** Summary changed:

- Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
+ Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 (14.04 and 
14.10)

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

Title:
  Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
  (14.04 and 14.10)

Status in Unity:
  Incomplete
Status in X.Org X server:
  Unknown
Status in unity package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

   * Minimize current window or alt-tab between windows
   * Reveal launcher to click on application
   * Click `Super` to bring up Dash
   * Hold `Super` to bring up Keyboard Shortcuts

  What should happen:

  Action completes smoothly and quickly.

  What happens instead:

   * Action may be slow / animation jerky.
   * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
   * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

  Notes:

   * Not application specific. Minimizing is reliably slow/stalls with 
minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, 
but I use those programs more often.
   * I am using an Nvidia Optimus machine with the default Nouveau driver - no 
`nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia 
driver (including `nvidia-prime`) and it made no difference.
   * I did not experience this issue on the same machine running 13.10 (with 
Bumblebee).
   * I am running Maximus.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 12:53:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b6]
  InstallationDate: Installed on 2014-04-24 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 12:03:43 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia"

[Touch-packages] [Bug 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04

2015-04-03 Thread d❤vid seaward

Link to downstream bug report.

** Bug watch added: freedesktop.org Bugzilla #89893
   https://bugs.freedesktop.org/show_bug.cgi?id=89893

** Changed in: xorg-server
   Importance: Undecided => Unknown

** Changed in: xorg-server
   Status: New => Unknown

** Changed in: xorg-server
 Remote watch: None => freedesktop.org Bugzilla #89893

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

Title:
  Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7
  (14.04 and 14.10)

Status in Unity:
  Incomplete
Status in X.Org X server:
  Unknown
Status in unity package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

   * Minimize current window or alt-tab between windows
   * Reveal launcher to click on application
   * Click `Super` to bring up Dash
   * Hold `Super` to bring up Keyboard Shortcuts

  What should happen:

  Action completes smoothly and quickly.

  What happens instead:

   * Action may be slow / animation jerky.
   * Action may stall (animation frozen on given frame, e.g. window partially 
minimized) - initiating another action cancels first action and second action 
may succeed (most often calling Guake with F12 seems to solve the issue)
   * Action may freeze - cursor no longer moves - a soft reboot 
(Alt+PrtScr+REISUB) usually works, otherwise a hard reboot

  Notes:

   * Not application specific. Minimizing is reliably slow/stalls with 
minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, 
but I use those programs more often.
   * I am using an Nvidia Optimus machine with the default Nouveau driver - no 
`nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia 
driver (including `nvidia-prime`) and it made no difference.
   * I did not experience this issue on the same machine running 13.10 (with 
Bumblebee).
   * I am running Maximus.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 12:53:15 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:04b6]
  InstallationDate: Installed on 2014-04-24 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 12:03:43 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module

[Touch-packages] [Bug 998285] Re: Tapping alt-tab switches between windows of the same application sometimes

2015-04-03 Thread Christopher Townsend

** Branch linked: lp:~3v1n0/unity/switcher-first-selection-mode

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

Title:
  Tapping alt-tab switches between windows of the same application
  sometimes

Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Normally, tapping alt-tab switches between applications, and tapping
  alt-` switches between windows of the front-most application. However,
  if the two front-most windows are from the same application, then alt-
  tab will switch between these windows instead, instead of moving to
  the second-front-most application. Hence, in this case, alt-tab
  duplicates the action of alt-`.

  Here is an example:
  1) create the stack with two nautilus windows at the top, e.g. Nautilus 
window 1 (N1), Nautilus window 2 (N2), and Firefox window (F1) (but you can use 
any applications). Create the stack either by [clicking F1, N2, N1] or 
[switching to Nautilus with alt-tab, then alt-` to the other Nautilus window].
  2) Tap alt-tab.

  What happens: I switch to the other nautilus window.

  What I expected: to switch to the other application (i.e. Firefox).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sat May 12 10:17:21 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-04-29 (12 days ago)

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

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

[Touch-packages] [Bug 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption

2015-04-03 Thread Sebastien Bacher

(seems like the changes got sponsored, unsubscribing sponsors)

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

Title:
  Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap
  corruption

Status in Embedded GLIBC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Precise:
  Fix Committed

Bug description:
  [Impact]

   * This bug is likely to cause a crash with a SEGV in multithreading
  applications doing many memory deallocations with ATOMIC_FASTBINS
  feature enabled.

  [Test Case]

   * Since this is a race condition issue there is no simple path of 
reproducing it, however one could try to follow the instructions in the 
upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073):
  https://www.sourceware.org/bugzilla/attachment.cgi?id=7331

  [Regression Potential]

   * This issue has been merged upstream with no further issues
  reported.

  [Other Info]

  * Original bug description:

  We have an application which makes heavy allocation and de-allocation
  demands from multiple threads.  We run this application continuously
  on many servers, and once every several CPU months or years, we were
  getting a crash in _int_free that did not look like vanilla heap
  corruption.  I believe I have narrowed it down to a race condition in
  _int_free due to the ATOMIC_FASTBINS feature.  Basically, in the
  lockless FASTBIN _int_free path, a chunk is pulled into a local
  variable with the intent to add it to the fastbins list.  However, the
  heap consolidation/trim code can race with this, and can coalesce the
  entire block and/or give it back to the OS before _int_free has a
  chance to try and store it into the fastbins list.

  The problem is very challenging to reproduce in situ, but using gdb I
  have a recipe which demonstrates the crash 100% of the time on my
  12.04 x64 system running eglibc 2.15.  It relies on malloc_trim,
  although in our in situ data, the consolidation is triggered as a
  result of a normal free.  malloc_trim is just easier to control.

  While I am not a glibc developer, I could not see any easy ways to fix
  the situation shy of disabling ATOMIC_FASTBINS.

  I am attaching the reproduction source.  Other pertinent information
  follows:

  > jpieper@calculon:~/downloads$ lsb_release -rd
  > Description:Ubuntu 12.04 LTS
  > Release:12.04

  > jpieper@calculon:~/downloads$ apt-cache policy libc6
  > libc6:
  >   Installed: 2.15-0ubuntu10
  >   Candidate: 2.15-0ubuntu10
  >   Version table:
  >  *** 2.15-0ubuntu10 0
  >500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  >100 /var/lib/dpkg/status

  What I expect: I expect the attached application, when run using the gdb 
script in the comments, to complete with no failures.
  What happened: A SIGSEGV after the final continue.

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

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

[Touch-packages] [Bug 1440098] [NEW] "start job is running" hangs boot until timeout

2015-04-03 Thread Barry Warsaw

Public bug reported:

Booting a freshly dist-upgraded vivid, I see the following console
messages with a red spinner hang the boot process until the first one
reaches its timeout:

(1 of 2) A start job is running for dev-mapper-cryptswap1.device (34s / no 
limit)
(2 of 2) A start job is running for dev-sdb1.device (36s / 1min 30s)

Eventually:

Timed out waiting for device dev-sdb1.device.
[ESC[1;33mDEPENDESC[0m] Dependency failed for Cryptography Setup for cryptswap1.
[ESC[1;33mDEPENDESC[0m] Dependency failed for /dev/mapper/cryptswap1.
[ESC[1;33mDEPENDESC[0m] Dependency failed for Swap.
[ESC[1;33mDEPENDESC[0m] Dependency failed for Encrypted Volumes.

then the boot continues.  AFAICT, there are no ill effects on the post-
boot system.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-6ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
Uname: Linux 3.19.0-11-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr  3 11:22:16 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-07-12 (1360 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
MachineType: Dell Inc. Studio XPS 435MT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic 
root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro nomdmonddf nomdmonisw
SourcePackage: systemd
SystemImageInfo:
 current build number: 0
 device name: 
 channel: daily
 last update: Unknown
UpgradeStatus: Upgraded to vivid on 2011-12-23 (1196 days ago)
dmi.bios.date: 05/05/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 0R849J
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr:
dmi.product.name: Studio XPS 435MT
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug vivid

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

Title:
  "start job is running" hangs boot until timeout

Status in systemd package in Ubuntu:
  New

Bug description:
  Booting a freshly dist-upgraded vivid, I see the following console
  messages with a red spinner hang the boot process until the first one
  reaches its timeout:

  (1 of 2) A start job is running for dev-mapper-cryptswap1.device (34s / no 
limit)
  (2 of 2) A start job is running for dev-sdb1.device (36s / 1min 30s)

  Eventually:

  Timed out waiting for device dev-sdb1.device.
  [ESC[1;33mDEPENDESC[0m] Dependency failed for Cryptography Setup for 
cryptswap1.
  [ESC[1;33mDEPENDESC[0m] Dependency failed for /dev/mapper/cryptswap1.
  [ESC[1;33mDEPENDESC[0m] Dependency failed for Swap.
  [ESC[1;33mDEPENDESC[0m] Dependency failed for Encrypted Volumes.

  then the boot continues.  AFAICT, there are no ill effects on the
  post-boot system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
  Uname: Linux 3.19.0-11-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  3 11:22:16 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-07-12 (1360 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  MachineType: Dell Inc. Studio XPS 435MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic 
root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro nomdmonddf nomdmonisw
  SourcePackage: systemd
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2011-12-23 (1196 days ago)
  dmi.bios.date: 05/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0R849J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 435MT
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Michael Terry

(To clarify, we don't have a more future-proof solution yet.  So when
the situation changes, we'll just have to come back and edit oxide
again.)

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: oxide-qt (Ubuntu)
   Status: New => In Progress

** Changed in: oxide-qt (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) => (unassigned)

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in oxide-qt package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

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

Title:
  [indicator] + [dialog] Silent Mode causes no indication of a change in
  [icon] state.

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Ubuntu UX bugs:
  Triaged
Status in indicator-sound package in Ubuntu:
  Fix Released
Status in indicator-sound package in Ubuntu RTM:
  Fix Released

Bug description:
  - "When the sound is muted, the volume icon to the left of the volume slider 
should have a red "/" running through it."
  - "Add an explicit "Mute" button to the sound indicator menu."
  - "Pressing and holding the icon to the left of the volume slider should mute 
volume straight away."

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

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

[Touch-packages] [Bug 1439829] Re: Wizard crashes when trying to view HERE terms and conditions

2015-04-03 Thread Gerry Boland

Ok code is doing platform specific things (reading GRID_UNIT_PX, getting
a shared gl context is very QPA plugin), so yeah the qpa name is a good
way to distinguish them. Figuring out if it should GL or GLES really
should be something Qt can communicate. We're exclusively using GLES for
now, but desktop will gain GL support in time, so this fix isn't future-
proof

** Changed in: unity8 (Ubuntu)
 Assignee: Gerry Boland (gerboland) => Michael Terry (mterry)

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Wizard crashes when trying to view HERE terms and conditions

Status in oxide-qt package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Flash like so:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed-
  customized-here --wipe

  And you'll have the HERE bits on your phone.  Now go through the
  wizard, click on the "terms and conditions" link on the location
  screen to see the Nokia terms.  Your screen will seem frozen and
  unity8 will crash.

  This is what we see in the logs:

  [0402/192155:WARNING:oxide_qt_browser_startup.cc(161)] Unrecognized Qt 
platform: mirserver
  [0402/192155:ERROR:gl_implementation_osmesa.cc(22)] Failed to load 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: 
/usr/lib/arm-linux-gnueabihf/oxide-qt/libosmesa.so: cannot open shared object 
file: No such file or directory

  And it's because oxide expects the platform to start with "ubuntu" but
  unity8 translates "ubuntumirclient" to "mirserver" which oxide does
  not expect.  So it falls back to non-GLES2 mode and can't find
  libosmesa.so, crashing.

  It's not clear to me *why* unity8 is doing that.  But until we sort
  that out, oxide can simply support "mirserver" too.

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

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

[Touch-packages] [Bug 1439847] Re: Surface Pro 3 touchpad not working on ubuntu 15.04

2015-04-03 Thread Brian Murray

** Tags added: vivid

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

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

Title:
  Surface Pro 3 touchpad not working on ubuntu 15.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I booted ubuntu 15.04 final beta to try before the full version
  release and everything on the surface pro 3 works except for the
  touchpad mouse movement. Will this be fixed in the final release of
  ubuntu 15.04

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

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

[Touch-packages] [Bug 1429285] Re: feature request: apt-get update --if-necessary

2015-04-03 Thread Scott Moser

$ echo "now: $(TZ=GMT date)"; wget -S -q 
http://azure.archive.ubuntu.com/ubuntu/dists/vivid/Release -O /dev/null
now: Fri Apr  3 14:37:31 GMT 2015
  HTTP/1.1 200 OK
  Date: Fri, 03 Apr 2015 14:37:31 GMT
  Server: Apache/2.2.22 (Ubuntu)
  Last-Modified: Fri, 03 Apr 2015 14:28:00 GMT
  ETag: "34f32-512d2c15bbc00"
  Accept-Ranges: bytes
  Content-Length: 216882
  Cache-Control: max-age=1228, proxy-revalidate
  Expires: Fri, 03 Apr 2015 14:58:00 GMT
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive

So the 'Expires' is most definitely in the future.  This one is
currently 21 minutes in the future.

I didn't say that the solutions I pointed to were complete, but the fact
that people are attempting to solve the problem (and doing so
incorrectly) should indicate a need for a good solution.

It would seem possible for apt to go through the sources.list
(+sources.list.d/*) and figure out what it was going to download.  It
could decide  based on previously stored headers or a global default "5
minutes" or a per-mirror default if it should bother.  Of course it
would make sense to have the ability to force.

running 'apt-get update' on a system does take real time. On a cloud instance 
with a on-network mirror:
% TIMEFORMAT='real=%3lR user=%3lU sys=%3lS' bash -c 'for i in $(seq 1 10); do 
printf "%-3s " $i ; time apt-get update -q >/dev/null; done'
1   real=0m3.987s user=0m3.628s sys=0m0.244s
2   real=0m4.052s user=0m3.688s sys=0m0.220s
3   real=0m3.980s user=0m3.656s sys=0m0.204s
4   real=0m4.077s user=0m3.676s sys=0m0.272s
5   real=0m4.068s user=0m3.732s sys=0m0.228s
6   real=0m4.052s user=0m3.688s sys=0m0.236s
7   real=0m4.201s user=0m3.812s sys=0m0.248s
8   real=0m4.247s user=0m3.852s sys=0m0.252s
9   real=0m4.059s user=0m3.688s sys=0m0.256s
10  real=0m4.064s user=0m3.680s sys=0m0.252s

It just seems reasonable to me, that operations 2->10 could take .002
seconds.

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

Title:
  feature request: apt-get update --if-necessary

Status in apt package in Ubuntu:
  New

Bug description:
  In many cases (juju, lxc containers .. ) we find ourselves in the
  position of not knowing if the apt-cache has been udpated recently.
  So, you either risk not doing it, or do it and it takes some time and
  generates load.

  so long story short, you always run 'apt-get update' which is quite often
  unnecessary.

  Would it be possible to add (or is there now) something like
  '--if-necessary' or '--if-necessary=5m'.  I could imagine that that would
  look at /var/lib/apt/lists and check timestamps on files for each url that
  /etc/apt/sources.list[.d/*] would hit.  If nothing was needed and
  reasonably recent, then it would not do the update.

  There exist other solutions to this like:

https://coderwall.com/p/0xtstw/doing-an-apt-get-update-in-ansible-only-if-a-condition-is-met

https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/

  
  It'd be nice if we had a sane way to say:
update if you need to, otherwise don't waste time and resources

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  6 17:06:22 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-02 (63 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150101)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1439847] [NEW] Surface Pro 3 touchpad not working on ubuntu 15.04