[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

2015-04-18 Thread Dave Gilbert
I'm tempted to think this is a bug either in the kernel, X or the input
handling - because it seems more to do with what the interpretation of
key input (that happens to be how the accelerator signals?) than actual
actions.  What happens if you try booting with 14.10 kernel but leave
everything else the same?

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.I

[Touch-packages] [Bug 1369250] Re: Blackscreen; lightdm not starting up after update

2014-09-14 Thread Dave Gilbert
Some notes:
  1) The contents of /var/log/lightdm.log aren't being touched - so perhaps 
it's not getting that far?
  2) Hmm /var/log/upstart/lightdm.log

root@davros:/var/log/upstart# more lightdm.log
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found
/proc/self/fd/9: 24: exec: lightdm: not found

hmm; it looks like the lightdm packages got uninstalled (I did do an
autoremove after the update  so I suspect a dependency has gone); but
given that log it looks like something was still trying to start lightdm
and it hadn't updated to select a new dm.   So that's still a bug - but
not sure where; removing lightdm shouldn't try and start it.

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

Title:
  Blackscreen; lightdm not starting up after update

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,
As of today lightdm isn't managing to start at all (blackscreen after the 
boot); if I log
  in on the console and then startx it's fine.

This machine was upgraded to Utopic a month or ago and has been working 
fine; I did
  an apt-get update && apt-get dist-upgrade yeterday and it's the first reboot 
since then.

  Note: This machine is running KDE Framework 5 desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 14 12:14:34 2014
  InstallationDate: Installed on 2013-11-15 (302 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20131115)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to utopic on 2014-06-28 (77 days ago)

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

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


[Touch-packages] [Bug 1369250] [NEW] Blackscreen; lightdm not starting up after update

2014-09-14 Thread Dave Gilbert
Public bug reported:

Hi,
  As of today lightdm isn't managing to start at all (blackscreen after the 
boot); if I log
in on the console and then startx it's fine.

  This machine was upgraded to Utopic a month or ago and has been working fine; 
I did
an apt-get update && apt-get dist-upgrade yeterday and it's the first reboot 
since then.

Note: This machine is running KDE Framework 5 desktop

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
Date: Sun Sep 14 12:14:34 2014
InstallationDate: Installed on 2013-11-15 (302 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20131115)
SourcePackage: lightdm
UpgradeStatus: Upgraded to utopic on 2014-06-28 (77 days ago)

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


** Tags: amd64 apport-bug utopic

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

Title:
  Blackscreen; lightdm not starting up after update

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Hi,
As of today lightdm isn't managing to start at all (blackscreen after the 
boot); if I log
  in on the console and then startx it's fine.

This machine was upgraded to Utopic a month or ago and has been working 
fine; I did
  an apt-get update && apt-get dist-upgrade yeterday and it's the first reboot 
since then.

  Note: This machine is running KDE Framework 5 desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Sun Sep 14 12:14:34 2014
  InstallationDate: Installed on 2013-11-15 (302 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20131115)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to utopic on 2014-06-28 (77 days ago)

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

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


[Touch-packages] [Bug 1343962] Re: Sound slider moves itself randomly when scrolling or moving sound pointer

2014-09-02 Thread Dave Gilbert
Set back to Confirmed because Pool provided the requested information

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

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

Title:
  Sound slider moves itself randomly when scrolling or moving sound
  pointer

Status in “indicator-sound” package in Ubuntu:
  Confirmed

Bug description:
  I've described this bug in details at askubuntu.com ::
  http://askubuntu.com/questions/499268/strange-bug-with-sound-slider

  In brief:
  1) Problem caused by installation of Ubuntu-SDK
  2) Removing Ubuntu-SDK didn't fix the problem
  3) This problem occurs only with desktop sound slider (notification slider). 
In Ubuntu sound settings, everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': 
(true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true, 
'', [<0.1183929443359375>]), 'scroll': (true, 'i', []), 
'play-playlist.spotify.desktop': (true, 's', []), 'vlc.desktop': (true, '', 
[<{'running': , 'state': <'Paused'>}>]), 'desktop-settings': (true, '', 
[]), 'previous.vlc.desktop': (true, '', []), 'play-playlist.vlc.desktop': 
(true, 's', []), 'spotify.desktop': (true, '', [<{'running': , 'state': 
<'Paused'>}>]), 'volume': (true, 'i', [<0.51992553710937495>]), 
'play.spotify.desktop': (true, '', [<'Paused'>]), 'previous.spotify.desktop': 
(true, '', []), 'root': (true, '', [<{'title': <'Dźwięk'>, 'accessible-desc': 
<'Głośność (51%)'>, 'icon': <('themed', <['audio-volume-medium-panel', 
'audio-volume-medium', 'audio-volume', 'audio']>)>, 'visible': }>]), 
'next.spotify.desktop': (true, '', []), 'play.vlc.desktop': (true, '', 
[<'Paused'>])},)
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 18 12:28:16 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2014-04-17 (91 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=pl
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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