[Touch-packages] [Bug 1545784] Re: Unity8 crashes with Intel Sandybridge on 16.04

2016-05-03 Thread postadelmaga
*** This bug is a duplicate of bug 1556461 ***
https://bugs.launchpad.net/bugs/1556461

I have the same problem (blackscreen) on 16.04 and sandybridge

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

Title:
  Unity8 crashes with Intel Sandybridge on 16.04

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I can not log in to Unity8 session on Ubuntu 16.04. When I try to log
  in to Unity8 session, only a black screen is shown. And when I return
  to Unity7 session, I get a crash report from apport.

  To get to the default (unity7) session:
  1- CTRL+ALT+F1
  2- Log in
  3- sudo systemctrl restart lightdm
  ---
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (29 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160208-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Tags:  xenial
  Uname: Linux 4.4.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-01-16 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  Package: unity8 8.11+16.04.20160310.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Tags:  xenial
  Uname: Linux 4.4.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1446437] [NEW] nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not possible to reconnect

2015-04-20 Thread postadelmaga
Public bug reported:

- Ubunt: Vivid 15.04
- NetworkManager: 0.9.10.0

I'm experiencing this issue in a Starbucks cafee here in China.

I connect to the wifi network and start to surf ( see syslog-start.txt
), everything looks to to work fine but at some point I got the
following issues:

1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )

Now I don't connect to this precise network very often so I'm not 100%
sure the disconnection issue is caused by the network or by
networkmanager, anyway on my phone I'm not experiencing it but the
second issue not possible to reconnect looks something related to
Networkmanager.

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

** Attachment added: syslog-start.txt
   
https://bugs.launchpad.net/bugs/1446437/+attachment/4380283/+files/syslog-start.txt

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

Title:
   nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not
  possible to reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  - Ubunt: Vivid 15.04
  - NetworkManager: 0.9.10.0

  I'm experiencing this issue in a Starbucks cafee here in China.

  I connect to the wifi network and start to surf ( see syslog-start.txt
  ), everything looks to to work fine but at some point I got the
  following issues:

  1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
  2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )

  Now I don't connect to this precise network very often so I'm not 100%
  sure the disconnection issue is caused by the network or by
  networkmanager, anyway on my phone I'm not experiencing it but the
  second issue not possible to reconnect looks something related to
  Networkmanager.

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

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


[Touch-packages] [Bug 1446437] Re: nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not possible to reconnect

2015-04-20 Thread postadelmaga
** Attachment added: syslog-stall.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446437/+attachment/4380285/+files/syslog-stall.txt

** Description changed:

  I'm experiencing this issue in a Starbucks cafee here in China.
  
  I connect to the wifi network and start to surf ( see syslog-start.txt
  ), everything looks to to work fine but at some point I got the
  following issues:
  
  1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
  2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )
  
  Now I don't connect to this precise network very often so I'm not 100%
  sure the disconnection issue is caused by the network or by
- networkmanager, anyway on my phone I'm not experiencing it.
- 
- Anyway the second issue, not possible to reconnect looks something
- related to Networkmanager.
+ networkmanager, anyway on my phone I'm not experiencing it but the
+ second issue not possible to reconnect looks something related to
+ Networkmanager.

** Description changed:

+ - Ubunt: Vivid 15.04
+ - NetworkManager: 0.9.10.0
+ 
  I'm experiencing this issue in a Starbucks cafee here in China.
  
  I connect to the wifi network and start to surf ( see syslog-start.txt
  ), everything looks to to work fine but at some point I got the
  following issues:
  
  1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
  2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )
  
  Now I don't connect to this precise network very often so I'm not 100%
  sure the disconnection issue is caused by the network or by
  networkmanager, anyway on my phone I'm not experiencing it but the
  second issue not possible to reconnect looks something related to
  Networkmanager.

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

Title:
   nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not
  possible to reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  - Ubunt: Vivid 15.04
  - NetworkManager: 0.9.10.0

  I'm experiencing this issue in a Starbucks cafee here in China.

  I connect to the wifi network and start to surf ( see syslog-start.txt
  ), everything looks to to work fine but at some point I got the
  following issues:

  1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
  2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )

  Now I don't connect to this precise network very often so I'm not 100%
  sure the disconnection issue is caused by the network or by
  networkmanager, anyway on my phone I'm not experiencing it but the
  second issue not possible to reconnect looks something related to
  Networkmanager.

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

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


[Touch-packages] [Bug 1446437] Re: nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not possible to reconnect

2015-04-20 Thread postadelmaga
** Attachment added: syslog-stop.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1446437/+attachment/4380284/+files/syslog-stop.txt

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

Title:
   nm-apple: after disconnected (DISASSOC_DUE_TO_INACTIVITY) not
  possible to reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  - Ubunt: Vivid 15.04
  - NetworkManager: 0.9.10.0

  I'm experiencing this issue in a Starbucks cafee here in China.

  I connect to the wifi network and start to surf ( see syslog-start.txt
  ), everything looks to to work fine but at some point I got the
  following issues:

  1. after some time 2/4 min I got disconnected: reason 
`DISASSOC_DUE_TO_INACTIVITY` ( see syslog-stop.txt )
  2. at this point I cannot connect again to the wifi network unless I kill 
networkmanager ( see syslog-stall.txt )

  Now I don't connect to this precise network very often so I'm not 100%
  sure the disconnection issue is caused by the network or by
  networkmanager, anyway on my phone I'm not experiencing it but the
  second issue not possible to reconnect looks something related to
  Networkmanager.

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

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


[Touch-packages] [Bug 1434758] Re: mysqld: errno: 24 - Too many open files

2015-03-27 Thread postadelmaga
I re-added systemd because It affect the systemd boot option so I think
it is good to have it listed with other problems with systemd and vivid.
( maybe it is  bad idea in that case remove it )

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

Title:
  mysqld: errno: 24 - Too many open files

Status in mysql-5.6 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to 15.04 mysql cannot set the file limit and so it
  doesn't work well.

  /var/log/mysql/error.log shows the following:

  [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
  [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
  [ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open 
files)

  The issue looks to be related to the recent switch to systemd indeed
  if I start using upstart everything work fine.

  I found out similar issues reported on Debian and the general
  suggestion is to add following line to the `mysqld.service` anyway
  this file is not present on my installation :

  LimitNOFILE=infinity
  LimitMEMLOCK=infinity

  Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
  I'm not sure how Ubuntu is managing this, maybe with file in dir 
/etc/default/ ?

  I have also tried adding following lines in /etc/security/limits.conf,
  but the problem persist:

  mysql soft nofile 65535
  mysql hard nofile 65535

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mysql-server (not installed)
  Uname: Linux 3.19.2-031902-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 21 10:17:00 2015
  InstallationDate: Installed on 2014-03-10 (375 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140309)
  SourcePackage: mysql-5.5
  UpgradeStatus: Upgraded to vivid on 2015-03-20 (0 days ago)

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

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


[Touch-packages] [Bug 1434758] Re: mysqld: errno: 24 - Too many open files

2015-03-23 Thread postadelmaga
** Package changed: mysql-5.5 (Ubuntu) = mysql-5.6 (Ubuntu)

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

Title:
  mysqld: errno: 24 - Too many open files

Status in mysql-5.6 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to 15.04 mysql cannot set the file limit and so it
  doesn't work well.

  /var/log/mysql/error.log shows the following:

  [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
  [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
  [ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open 
files)

  The issue looks to be related to the recent switch to systemd indeed
  if I start using upstart everything work fine.

  I found out similar issues reported on Debian and the general
  suggestion is to add following line to the `mysqld.service` anyway
  this file is not present on my installation :

  LimitNOFILE=infinity
  LimitMEMLOCK=infinity

  Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
  I'm not sure how Ubuntu is managing this, maybe with file in dir 
/etc/default/ ?

  I have also tried adding following lines in /etc/security/limits.conf,
  but the problem persist:

  mysql soft nofile 65535
  mysql hard nofile 65535

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mysql-server (not installed)
  Uname: Linux 3.19.2-031902-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 21 10:17:00 2015
  InstallationDate: Installed on 2014-03-10 (375 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140309)
  SourcePackage: mysql-5.5
  UpgradeStatus: Upgraded to vivid on 2015-03-20 (0 days ago)

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

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


[Touch-packages] [Bug 1434758] Re: mysqld: errno: 24 - Too many open files

2015-03-23 Thread postadelmaga
I think this should be a milestone for ubuntu 15.04

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

Title:
  mysqld: errno: 24 - Too many open files

Status in mysql-5.5 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to 15.04 mysql cannot set the file limit and so it
  doesn't work well.

  /var/log/mysql/error.log shows the following:

  [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
  [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
  [ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open 
files)

  The issue looks to be related to the recent switch to systemd indeed
  if I start using upstart everything work fine.

  I found out similar issues reported on Debian and the general
  suggestion is to add following line to the `mysqld.service` anyway
  this file is not present on my installation :

  LimitNOFILE=infinity
  LimitMEMLOCK=infinity

  Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
  I'm not sure how Ubuntu is managing this, maybe with file in dir 
/etc/default/ ?

  I have also tried adding following lines in /etc/security/limits.conf,
  but the problem persist:

  mysql soft nofile 65535
  mysql hard nofile 65535

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mysql-server (not installed)
  Uname: Linux 3.19.2-031902-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 21 10:17:00 2015
  InstallationDate: Installed on 2014-03-10 (375 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140309)
  SourcePackage: mysql-5.5
  UpgradeStatus: Upgraded to vivid on 2015-03-20 (0 days ago)

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

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


[Touch-packages] [Bug 1434758] [NEW] mysqld: errno: 24 - Too many open files

2015-03-20 Thread postadelmaga
Public bug reported:

After upgrading to 15.04 mysql cannot set the file limit and so it
doesn't work well.

/var/log/mysql/error.log shows the following:

[Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
[Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
[ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open files)

The issue looks to be related to the recent switch to systemd indeed if
I start using upstart everything work fine.

I found out similar issues reported on Debian and the general suggestion
is to add following line to the `mysqld.service` anyway this file is not
present on my installation :

LimitNOFILE=infinity
LimitMEMLOCK=infinity

Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
I'm not sure how Ubuntu is managing this, maybe with file in dir /etc/default/ ?

I have also tried adding following lines in /etc/security/limits.conf,
but the problem persist:

mysql soft nofile 65535
mysql hard nofile 65535

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: mysql-server (not installed)
Uname: Linux 3.19.2-031902-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 21 10:17:00 2015
InstallationDate: Installed on 2014-03-10 (375 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140309)
SourcePackage: mysql-5.5
UpgradeStatus: Upgraded to vivid on 2015-03-20 (0 days ago)

** Affects: mysql-5.5 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug mysqld systemd-boot vivid

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

** Summary changed:

- mysqld  systemd - errno: 24 - Too many open files
+ mysql: errno: 24 - Too many open files

** Summary changed:

- mysql: errno: 24 - Too many open files
+ mysqld: errno: 24 - Too many open files

** Tags added: systemd-boot

** Description changed:

  After upgrading to 15.04 mysql cannot set the file limit and so it
  doesn't work well.
  
  /var/log/mysql/error.log shows the following:
  
  [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
  [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
  [ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open 
files)
  
  The issue looks to be related to the recent switch to systemd indeed if
  I start using upstart everything work fine.
  
  I found out similar issues reported on Debian and the general suggestion
  is to add following line to the `mysqld.service` anyway this file is not
  present on my installation :
  
  LimitNOFILE=infinity
  LimitMEMLOCK=infinity
  
+ Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
+ I'm not sure how Ubuntu is managing this, maybe with file in dir 
/etc/default/ ?
+ 
+ I have also tried adding following lines in /etc/security/limits.conf,
+ but the problem persist:
+ 
+ mysql soft nofile 65535
+ mysql hard nofile 65535
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mysql-server (not installed)
  Uname: Linux 3.19.2-031902-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 21 10:17:00 2015
  InstallationDate: Installed on 2014-03-10 (375 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140309)
  SourcePackage: mysql-5.5
  UpgradeStatus: Upgraded to vivid on 2015-03-20 (0 days ago)

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

Title:
  mysqld: errno: 24 - Too many open files

Status in mysql-5.5 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to 15.04 mysql cannot set the file limit and so it
  doesn't work well.

  /var/log/mysql/error.log shows the following:

  [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 
5000)
  [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000)
  [ERROR] /usr/sbin/mysqld: Can't open file: ... (errno: 24 - Too many open 
files)

  The issue looks to be related to the recent switch to systemd indeed
  if I start using upstart everything work fine.

  I found out similar issues reported on Debian and the general
  suggestion is to add following line to the `mysqld.service` anyway
  this file is not present on my installation :

  LimitNOFILE=infinity
  LimitMEMLOCK=infinity

  Other distro stores this file in `/usr/lib/systemd/system/mysqld.service`
  I'm not sure how Ubuntu is managing this, maybe with file in dir 
/etc/default/ ?

  I have also tried adding following lines in /etc/security/limits.conf,
  but the problem persist:

  mysql soft nofile 65535
  mysql hard nofile 65535

  ProblemType: