[Desktop-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging

2018-06-13 Thread Nando
I just tried to use the same exact device on a PC that runs the same
version of Ubuntu (kernel: 4.15.0-22-generic) but has USB 2.0 ports and
it worked as expected. The machine which reports the error has only USB
1.0/1.1 ports.

Does this fact make the problem clearer or should I still try and
install the latest upstream kernel ?

Thank you again.

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

Title:
  TP-LINK TL-WN722N causes 100% CPU usage due to  trace logging

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello.

  Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK
  TL-WN722N into the USB port, the CPU usage goes to 100%, and there are
  multiple reports of "stack traces" in dmesg.

  The attached snippet repeats multiple consecutive times in the dmesg
  output (albeit with a different trace id).

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

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


[Desktop-packages] [Bug 1775230] Re: TP-LINK TL-WN722N causes 100% CPU usage due to trace logging

2018-06-06 Thread Nando
This is a text-only installation, and I cannot seem to login to
launchpad via a text browser (error: "bad robot go away").

Is there another way I can provide the information needed?

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

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

Title:
  TP-LINK TL-WN722N causes 100% CPU usage due to  trace logging

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello.

  Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK
  TL-WN722N into the USB port, the CPU usage goes to 100%, and there are
  multiple reports of "stack traces" in dmesg.

  The attached snippet repeats multiple consecutive times in the dmesg
  output (albeit with a different trace id).

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

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


[Desktop-packages] [Bug 1775230] [NEW] TP-LINK TL-WN722N causes 100% CPU usage due to trace logging

2018-06-05 Thread Nando
Public bug reported:

Hello.

Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-
WN722N into the USB port, the CPU usage goes to 100%, and there are
multiple reports of "stack traces" in dmesg.

The attached snippet repeats multiple consecutive times in the dmesg
output (albeit with a different trace id).

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


** Tags: tp-link usb wireless

** Attachment added: "tplink-trace-dmesg.txt"
   
https://bugs.launchpad.net/bugs/1775230/+attachment/5149056/+files/tplink-trace-dmesg.txt

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

Title:
  TP-LINK TL-WN722N causes 100% CPU usage due to  trace logging

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello.

  Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK
  TL-WN722N into the USB port, the CPU usage goes to 100%, and there are
  multiple reports of "stack traces" in dmesg.

  The attached snippet repeats multiple consecutive times in the dmesg
  output (albeit with a different trace id).

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

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


[Desktop-packages] [Bug 926630] [NEW] Auto raise feature does not honor auto_raise_delay

2012-02-04 Thread Nando Florestan
Public bug reported:

I like windows to get the keyboard focus as I hove the mouse on them.
And I like them to raise after a little while. I have been using this
feature in Linux forever. I enabled this functionality in Oneiric
(Ubuntu 11.10) through the following gconf settings:

gconftool-2 --type string --set /apps/metacity/general/focus_mode sloppy
gconftool-2 --type boolean --set /apps/metacity/general/auto_raise true
gconftool-2 --type string --set /apps/metacity/general/auto_raise_delay 600

(One can also see and edit these settings in the GUI application gconf-
editor.)

I have Metacity 1:2.34.1-1ubuntu4.1.

The problem is that the last setting, auto_raise_delay, is not honored
in this new Ubuntu version. This means a window is brought to the
forefront as soon as the mouse hovers on it. This spoils the whole
feature because you can't really switch to a window on the far end of
the screen if another window is on the way and is larger than the window
you want. The delay is absolutely essential to the usability of this
feature.

I am switching to Kubuntu as a result.

Here is more detail on my configuration, though I don't think it is
really relevant.

$ gconftool -R /apps/metacity/general
 auto_maximize_windows = false
 action_middle_click_titlebar = lower
 button_layout = close,minimize,maximize:
 auto_raise_delay = 600
 compositing_manager = false
 workspace_switcher_keyboard_cycle = false
 raise_on_click = true
 visual_bell = false
 theme = Ambiance
 num_workspaces = 4
 focus_mode = sloppy
 resize_with_right_button = false
 action_double_click_titlebar = toggle_maximize
 visual_bell_type = frame_flash
 action_right_click_titlebar = menu
 titlebar_uses_system_font = false
 focus_new_windows = smart
 compositor_effects = true
 capture_before_unmap = false
 application_based = false
 audible_bell = true
 disable_workarounds = true
 titlebar_font = Ubuntu Bold 11
 reduced_resources = false
 auto_raise = true
 mouse_button_modifier = Alt
 show_maximized_titlebars = true

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


** Tags: focus mouse oneiric

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/926630

Title:
  Auto raise feature does not honor auto_raise_delay

Status in “metacity” package in Ubuntu:
  New

Bug description:
  I like windows to get the keyboard focus as I hove the mouse on them.
  And I like them to raise after a little while. I have been using this
  feature in Linux forever. I enabled this functionality in Oneiric
  (Ubuntu 11.10) through the following gconf settings:

  gconftool-2 --type string --set /apps/metacity/general/focus_mode sloppy
  gconftool-2 --type boolean --set /apps/metacity/general/auto_raise true
  gconftool-2 --type string --set /apps/metacity/general/auto_raise_delay 600

  (One can also see and edit these settings in the GUI application
  gconf-editor.)

  I have Metacity 1:2.34.1-1ubuntu4.1.

  The problem is that the last setting, auto_raise_delay, is not honored
  in this new Ubuntu version. This means a window is brought to the
  forefront as soon as the mouse hovers on it. This spoils the whole
  feature because you can't really switch to a window on the far end of
  the screen if another window is on the way and is larger than the
  window you want. The delay is absolutely essential to the usability of
  this feature.

  I am switching to Kubuntu as a result.

  Here is more detail on my configuration, though I don't think it is
  really relevant.

  $ gconftool -R /apps/metacity/general
   auto_maximize_windows = false
   action_middle_click_titlebar = lower
   button_layout = close,minimize,maximize:
   auto_raise_delay = 600
   compositing_manager = false
   workspace_switcher_keyboard_cycle = false
   raise_on_click = true
   visual_bell = false
   theme = Ambiance
   num_workspaces = 4
   focus_mode = sloppy
   resize_with_right_button = false
   action_double_click_titlebar = toggle_maximize
   visual_bell_type = frame_flash
   action_right_click_titlebar = menu
   titlebar_uses_system_font = false
   focus_new_windows = smart
   compositor_effects = true
   capture_before_unmap = false
   application_based = false
   audible_bell = true
   disable_workarounds = true
   titlebar_font = Ubuntu Bold 11
   reduced_resources = false
   auto_raise = true
   mouse_button_modifier = Alt
   show_maximized_titlebars = true

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

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