** Also affects: wpasupplicant (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Changed in: empathy (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/971880
Title:
go on line to edit your personal information
Status i
I re-opened this because I am experiencing the same problem.
:~$ uname -a
Linux x200 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
This may be difficult to reproduce, because I am not sure how the "ghost
account" got there. When it is deleted, it r
** Attachment added: "Account I want to keep (actually works)."
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/971880/+attachment/3223405/+files/real.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https
After further investigation, I discovered a work-around.
The problem appears to be the result of an upgrade from a time where
gnome-online-accounts was used in ubuntu. My google account was added
there, and the ghosts of that addition seem to have echoed into 12.04 --
where that package is no lon
Joseph,
Tested against 3.5.0-030500rc7 my wifi fails to connect to 802.1x at all
--so if anything its a regression.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
** Summary changed:
- wlan
Mathieu --
My first attachment contains a wpasupplicant debug log created with
"debug-helper.py --wpa msgdump" turned on. (-nm debug too)
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1024740/+attachment/3223273/+files/syslog.txt)
If running it with debug will provide more useful inform
I'm setting statuses back to confirmed in lieu of someone telling me I
need to run the logs again (see previous comment).
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: wpasupplicant (Ubuntu)
Status: Incomplete => Confirmed
--
You received
Or - let me be more precise, this type of network.
On Jul 23, 2012 9:12 AM, "Patrick Kilgore"
wrote:
> I do not know, I did not need to use this network earlier.
> On Jul 23, 2012 9:06 AM, "Christopher M. Penalver" <
> christopher.penal...@gmx.com> wrote:
I do not know, I did not need to use this network earlier.
On Jul 23, 2012 9:06 AM, "Christopher M. Penalver" <
christopher.penal...@gmx.com> wrote:
> Patrick Kilgore, thank you for reporting this and helping make Ubuntu
> better. Did this problem occur in prior versions of
mx.com> wrote:
> Patrick Kilgore:
> + What is the manufacturer and model of the router you are connecting to?
> + Does this problem occur with other authentication types on the same
> router?
> + Does this problem occur on a different mfg/model router?
> + Could you please test f
Public bug reported:
- Freshly installed 18.04 (from 16.04, in which everything was working
great). This behavior is consistent across several tested applications
(firefox, ubuntu desktop, terminal).
What I expected to happen:
1. I right click the touchpad, see appropriate response from relevan
** Description changed:
- Freshly installed 18.04 (from 16.04, in which everything was working
great). This behavior is consistent across several tested applications
(firefox, ubuntu desktop, terminal).
What I expected to happen:
- 1. I right click the mouse, see appropriate response
Additional logs enclosed in coming posts (multi-attachments still not
supported!?).
The `evtest` events are me alternating between right (first) then left
clicks on the touchpad.
In the `xev` events log, I hit the "r" key to identify when I am about
to rt+click and "l" as an identifier of when I
** Attachment added: "evtest"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1767383/+attachment/5128515/+files/evtest
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu
** Attachment added: "xinput"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1767383/+attachment/5128514/+files/xinput
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu
** Attachment added: "xev.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1767383/+attachment/5128516/+files/xev.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubun
After some additional troubleshooting, I've decided this is reported to
the wrong package. Switching that.
The fix for me here was to set:
$ gsettings set org.gnome.desktop.peripherals.touchpad click-method
areas
It appears that libinput defaulted my computer on reinstall of Ubuntu to
the Ap
@vanvugt I think this is still a big problem lots of 16.04 -> 18.04
upgraders will run into.
This one blew my mind after installing 18.04 today. If this is going to
be the new default, we need to warn users, because those of us not using
Apple/ChromeOS hardware *expect* clickpads to work like the
This is viewed as a confusing regression by a portion of the
userbase[0]. God knows it destroyed my workflow (and morning) when I
updated to 18.04 from 16.04.
For some of us 'old farts' who never use macs and always relied on the
"areas" behavior in both Linux and Windows it would be helpful to h
20 matches
Mail list logo