[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2017-09-02 Thread Douglas H. Silva
Unable to reproduce this in Ubuntu MATE 17.04. I use full-disk
encryption too and enabled auto-login as well.

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

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in ubuntu-mate:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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

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


[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

2017-08-12 Thread Douglas H. Silva
** Description changed:

  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
  
  This affects any desktop environment made with gtk+3, such as MATE,
- Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
- affected. Any DE still using gtk2 works fine. I tested 3 different
+ Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity are
+ not affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

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

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME and Unity
  are not affected. Any DE still using gtk2 works fine. I tested 3
  different computers with Intel Graphics and they were all displaying
  the same glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-06-27 Thread Douglas H. Silva
Using ath9k driver: no issues

My netbook running iwlwifi driver still has this bug. It's in Ubuntu,
because I'm running Debian Stretch just fine there.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1690671] Re: Pointer clicks and hovering fail to have effect at the very left and top borders of screen

2017-05-22 Thread Douglas H. Silva
** Description changed:

+ THE ISSUE:
+ The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
+ 
  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
- THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.
- 
  It can always be reproduced. I can record a video of the issue if
  needed.

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

Title:
  Pointer clicks and hovering fail to have effect at the very left and
  top borders of screen

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.

  It can always be reproduced. I can record a video of the issue if
  needed.

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

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


[Touch-packages] [Bug 1690671] [NEW] Pointer clicks and hovering fail to have effect at the very left and top borders of screen

2017-05-14 Thread Douglas H. Silva
Public bug reported:

This affects any desktop environment made with gtk+3, such as MATE,
Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
affected. Any DE still using gtk2 works fine. I tested 3 different
computers with Intel Graphics and they were all displaying the same
glitch.

THE ISSUE:
The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear on top of it starts to flicker on and off. If the icon 
highlights, I can click. If it doesn't, clicking such menu icon doesn't have 
any effect. It happens at the last pixel of the screen. Moving the pointer just 
one pixel away from the border restores the desired effect.

It can always be reproduced. I can record a video of the issue if
needed.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested with 3 different
- computers and they were all displaying the same glitch.
+ computers with Intel Graphics and they were all displaying the same
+ glitch.
  
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
- affected. Any DE still using gtk2 works fine. I tested with 3 different
+ affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
  The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Summary changed:

- Pointer clicks and hovering fail to have effect at the very left and top 
edges of screen
+ Pointer clicks and hovering fail to have effect at the very left and top 
borders of screen

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top edges of the 
screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below restores the desired effect.
+ The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or highlight any object at the very last pixel of the left and top borders of 
the screen. If there is a menu at the top, for instance, the highlighting that 
should appear starts to flicker on and off. If the icon highlights, I can 
click. If it doesn't, clicking such menu icon doesn't have any effect. It 
happens at the last pixel of the screen. Moving the pointer just one pixel 
below (away from border) restores the desired effect.
  
  It can always be reproduced. I can record a video of the issue if
  needed.

** Description changed:

  This affects any desktop environment made with gtk+3, such as MATE,
  Pantheon, parts of Xfce, Budgie and probably others. GNOME is not
  affected. Any DE still using gtk2 works fine. I tested 3 different
  computers with Intel Graphics and they were all displaying the same
  glitch.
  
  THE ISSUE:
- The pointer (happens with mouse, but it's worse with touchpad) fails to click 
or 

[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)

2017-05-12 Thread Douglas H. Silva
I fixed it with `sudo systemctl enable bluetooth` followed by a reboot.
It will print something to the terminal when you enable. Something else
must have disabled bluetooth.

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

Title:
  serious bug on bluetooth (Ubuntu 16.04 LTS)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed ubuntu 16.04 LTS twice -and i discovered that
  the problem was from the tool katoolin so i didn't install it- after i
  installed ubuntu the bluetooth didn't work for me.

  P.S:the bluetooth was working when my laptop was ubuntu 15.04

  when i turn bluetooth on to connect my mouse the switch was on but it
  said that

  Bluetooth is disabled

  i entered the command

  sudo rfkill unblock bluetooth

  it worked but didn't connect to the mouse even after the next restart
  i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock 
bluetooth before last line and restarting)

  and i've tried **sudo hciconfig hci0 reset** with output

  > Can't init device hci0: Connection timed out (110)

  my lsusb; rfkill list output:

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  0: asus-wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
   1: asus-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
   11: hci0: Bluetooth
    Soft blocked: no
   Hard blocked: no

  and output of **dmesg | grep -Ei 'ath3k|blue'**

  [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   34.157120] Bluetooth: Core ver 2.21
  [   34.157135] Bluetooth: HCI device and connection manager initialized
  [   34.157138] Bluetooth: HCI socket layer initialized
  [   34.157140] Bluetooth: L2CAP socket layer initialized
  [   34.157145] Bluetooth: SCO socket layer initialized
  [   35.604410] usbcore: registered new interface driver ath3k
  [   51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller
  [   53.810045] Bluetooth: hci0 command 0x0c25 tx timeout
  [   55.814079] Bluetooth: hci0 command 0x0c38 tx timeout
  [   57.818111] Bluetooth: hci0 command 0x0c39 tx timeout
  [   59.822149] Bluetooth: hci0 command 0x0c05 tx timeout
  [   66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   66.997552] Bluetooth: BNEP filters: protocol multicast
  [   66.997556] Bluetooth: BNEP socket layer initialized
  [  195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  195.328480] Bluetooth: RFCOMM TTY layer initialized
  [  195.328488] Bluetooth: RFCOMM socket layer initialized
  [  195.328495] Bluetooth: RFCOMM ver 1.11
  [  199.131870] Bluetooth: hci0 command 0x1009 tx timeout
  [  276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  294.258992] Bluetooth: hci0 command 0x1005 tx timeout
  [  296.263065] Bluetooth: hci0 command 0x0c23 tx timeout
  [  298.267076] Bluetooth: hci0 command 0x0c14 tx timeout
  [  306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  346.417970] Bluetooth: hci0 command 0x0c56 tx timeout
  [  348.421916] Bluetooth: hci0 command 0x0c45 tx timeout
  [  350.425782] Bluetooth: hci0 command 0x0c58 tx timeout
  [  352.429744] Bluetooth: hci0 command 0x1004 tx timeout
  [  366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  368.145218] Bluetooth: hci0 command 0x1001 tx timeout
  [  370.149130] Bluetooth: hci0 command 0x1009 tx timeout
  [  410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  421.612041] Bluetooth: hci0 command 0x0c23 tx timeout
  [  423.616060] Bluetooth: hci0 command 0x0c14 tx timeout
  [  425.620018] Bluetooth: hci0 command 0x0c25 tx timeout
  [  427.623984] Bluetooth: hci0 command 0x0c38 tx timeout
  [  442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller
  [  444.727752] Bluetooth: hci0 command 0x0c52 tx timeout
  [  446.731800] Bluetooth: hci0 command 0x0c45 tx timeout
  [  448.735743] Bluetooth: hci0 command 0x0c58 tx timeout
  [  450.739762] Bluetooth: hci0 command 0x1004 tx timeout
  [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller
  [ 4011.801141] 

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-02-28 Thread Douglas H. Silva
The applet started functioning properly after 16.04.2. If the problem
was Intel drivers, it solved it. Intel Wireless 3160 + Ubuntu MATE with
kernel 4.8.0-39-generic. Confirm this.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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


[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-02-25 Thread Douglas H. Silva
Any change after 16.04.2? New kernel 4.8...

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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