Attached is a syslog for the boot of 4.4.0-145 from start up to shut
down in the way described above.
** Attachment added: "Syslog from boot of 4.4.0-145"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145
--
You received this bug notifica
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Deskt
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Yo
Please not that Launchpad has automatically assigned this bug to mutter,
but mutter is not installed on the notebook in question, so I have added
linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of De
Public bug reported:
Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core
CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this
kernel everything is blank. Just a black screen. If I change to a
terminal using Ctrl Alt F4 it is still a black screen but I can
ca
Confirmed fixed with live ubuntu, working with gnome-shell
3.28.3-0ubuntu0.18.04.4 from bionic-proposed. Thanks guys, was a pesky
bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1765304
This problem affected me after upgrading to Ubuntu 18.10. However,
setting the Java version to use to OpenJDK 11 fixed this issue for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bu
Here's an update on this...
If, when in GRUB, I select the Advanced option and then choose the
(upstart) option, it works OK.
If I do the default boot, it nearly always results in the error message
and no wifi.
I hope this will give you some idea of what is going wrong.
--
You received this bu
** Changed in: network-manager (Ubuntu)
Status: New => 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/1781597
Title:
[SRU] WoWLAN settings are not supported
Hi Daniel
I'm grateful that you mentioned bug 1727356. I would have taken the
opportunity to upgrade to 18.04 but I see that I will have to wait until
it is fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
h
It seems I spoke too soon.
When I started the machine back up again today using 4.4.0-130, the bug
was back again.
It seems that when I restart, sometimes it will start without the error
message, then it will be back again if I restart again. Its quite
random.
Another thing I have noticed is th
Bug has been fixed in upgrade just released including kernel 4.4.0-131.
Even though the bug was reported against 4.4.0-124, it was also present
in releases between that and 4.4.0-130
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because yo
See errors in the xorg log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1783850
Title:
Cannot find display configuration
Status in xorg package in Ubuntu:
New
Bug description:
Wh
Public bug reported:
When booting an error window is displayed. The only option that works
is to use the default configuration.
This problem has been introduced by an upgrade in recent months, i.e.
since April 2018
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcV
If the X-axis is %time for the benchmark read/write then why does it typically
decrease over time?
Surely the X-axis is the read/write speed at different positions 0-100% across
the disk, like access time?
--
You received this bug notification because you are a member of Desktop
Packages, which
I mean to list shares NT1 is needed with smbtree.
the server will be listed but shares will not.
we will see what happens down the road but this is actually a good thing
because of security issues with lower protocols.
--
You received this bug notification because you are a member of Desktop
Pa
Andreas, it looks like to me that smbtree still needs NT1 to list
shares, as people harden there servers and disable less secure protocols
it will break browsing for shares.
the only way to get the computer listing with non-NT1 that I know of at
this point is with MDNS or Zeroconf/Bonjour
--
You
Andreas Hasenack, my server is nas4free (https://www.nas4free.org/)
running Samba version 4.7.6
smbstatus shows the connection with ubuntu 18.04 as SMB3_11.
ubuntu 17.10 would use NT1 by default.
so with 18.04 I would need to got to other "locations/connect to server"
and enter smb://server to b
Sebastien Bacher, I am not sure if it is documented anywhere?
I did notice that by default nautilus connects with smb3_11 to my
server.
thats good because it uses a more secure protocol but it breaks network
browsing.
if you downgrade to NT1 like I mentioned above it will work again but
with a l
Nautilus is now using protocol SMB3_11 in Ubuntu 18.04 and that breaks
browsing shares.
you could always choose "other locations/connect to server" and bookmark
the location and use a more secure protocol.
you could also install "smbclient" and edit "/etc/samba/samba.conf" in
the [global] section
This issue also applies to version 17.10. In my case, I am using gnome
desktop and the path /etx/xdg/xdg-gnome-xorg gets prepended to
$XDG_CONFIG_DIRS on every login.
Once the $XDG_CONFIG_DIRS gets beyond a certain length, applications
such as slack-desktop fails with a segmentation violation on s
Well I just wanted to confirm that I switched back to Xorg and
unfortunately the hack to 50-synaptics.conf no longer works -- the mouse
is still jumpy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Hi,
Oh my goodness...
I am using Wayland!!!
merc@merc-ThinkPad-X220:/disk/home/merc$ ps ax | grep wayl
922 tty1 Ssl+ 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session
--autostart /usr/share/gdm/greeter/autostart
968 tty1 Sl+0:00 /usr/bin/Xwayland :1024 -rootless -terminate -
I am even more confused as I installed -- and configured -- the Compiz
setting manager. So... is it really all compatible? How the heck...?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bu
Unfortunately, this:
[1] https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X230#Touchpad
No longer works as a fix in Ubuntu 17.10
Why would that be? Is the file no longer considered by Xorg?
Does anybody here know how to make it work?
I have a fantastic X220, which is still pretty damn fast
Public bug reported:
Got confused trying to start Synaptic with GKSUDO, SUDO, etc several times.
Eventually gave up and I have now booted into XORG instead Wayland. I hope it
works better.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVe
Public bug reported:
erreur d'installation lors de la mise à jour.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: am
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
I am affected by this bug as well.
* Ubuntu Xenial 16.04 AMD64 w most recent patches
* network-manager 1.2.6-0ubuntu0.16.04.2
* dnsmasq 2.75-1ubuntu0.16.04.4
Goth Queen's comment in post # 15 resolve
Public bug reported:
On logging in after reboot, my username and password are not recognized
for several attempts (two or three) and after I log in I get the
following report
lightdm crashed with SIGSEGV in pam_sm_authenticate
Segfault happened at: 0x7f5184e88d30 : mov
0x8(%rbx),%r15
PC(0x7f
Public bug reported:
installing ubuntustudio-audio
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_m
Re-opened, as there's some interest from OEMs in seeing NM teaming
support land in 18.04.
** Description changed:
Availability:
The package is available in universe, built on all architectures.
Rationale:
- The package is a new (Build-)Depends for network-manager, for network device
bon
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/956070
Title:
[info]: gn
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/976165
Title:
[backgro
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1064862
Title:
[blueto
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
** Changed in: gnome-software (Ubuntu)
Assignee: Tony (toekneemi) => (unassigned)
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received
This annoying bug still present in Ubuntu 16.04 LTS, 16.10 and 17.04.
It spreads everywhere through OS, only fresh Chrome is working fine and
Windows, sure
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
My point is that we shouldn't release these patches as an SRU without
being able to reproduce the bugs that the patches claim to fix first.
Otherwise we risk introducing additional regressions.
So if we want to consider an SRU for NM with one or more of Aaron's
patches, then yes we need to go thro
There's no evidence (ie. syslogs, package versions, output of wpa_cli)
provided which is a basis for re-opening the bug.
Also, please point us to the *exact* patch that is supposed to fix the
problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
This bug was marked FixReleased based on the upload of network-manager
1.2.6-0ubuntu0.16.04.1 to xenial updates and the comments from a many
people that the issue was resolved.
Recently there were two comments (#96 and #97) that claim that the bug
still exists. Comment #96 doesn't even list which
I'm not positive when an update was pushed out that caused this - my
machine gets updates automatically every night but I rarely reboot. I
rebooted yesterday and was immediately affected by it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: tony 161
@Kevin
NetworkManager already has code to monitor system signals related to
suspend/resume, so no adding additional scripts to /usr/lib/systemd
/system-sleep isn't the answer.
@Dan
Different bug... this bug is caused by NetworkManager's WiFi scanning
logic stalling due to a race condition. You
Updated the Status to "FixReleased" as it's not possible to do this
anymore on the latest 16.04 LTS release with NetworkManager 1.2.x, as
guest users no longer have sufficient permission to add new connections.
Retrofitting this to the version of NM in 14.04 might be a challenging as the
version
** Changed in: network-manager (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: network-manager (Ubuntu)
Status: Won't Fix => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a
Ugh, and then I wake my Thinkpad 410s just now, and I hit the bug on the
201st cycle. ;(-
Guess I'll go back to dropping the patch again from 1.2.6 and see how
many cycles I can run on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@taiebot65
Thanks. I'll take a look.
Regarding this bug, it turns out that when I was testing my version of
NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-
device...), I'd been doing so on top of the newly re-based 1.2.6, and it
turns out there was an actual fix in 1.2.6 which see
** Changed in: oem-priority/xenial
Status: New => 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/1585863
Title:
WiFi malfunction after suspend & resume stress
I've reproduced this on a Thinkpad 410s running 16.04 LTS. The version
of network-manager I used is the latest from xenial-updates:
1.2.2-0ubuntu0.16.04.3.
A few comments:
1) The fwts s3 test uses a low-level API to exercise suspend/resume.
I've been working with the fwts maintainer on an extens
Just moved this to Incomplete, as it's been posited that the fix for bug
#1104476 resolves the issue.
If anyone can confirm that this is still broken, we can investigate
further.
** Changed in: network-manager (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification b
Running 16.04 and this happens when i run remmina. i have to to a
Control-C to get back to prompt.
any suggestions?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1467588
Title:
Gtk-
: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tony 1706 F pulseaudio
CurrentDesktop: Unity
Date: Wed Nov 2 20:50:39 2016
InstallationDate: Installed on 2016-10-14 (19 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "X
@Alfonso
Let's put this on the agenda for this weeks' net/telephony meeting.
I'm not sure I'm comfortable with releasing your workaround just yet as
it introduces latency when the APs are properly configured for roaming.
--
You received this bug notification because you are a member of Desktop
An old thread, I know but I've experienced similar problems.
After upgrade from Ubuntu 14.04.3 to 16.04.1 with Xmonad window manager
certain undesirable symptoms began to arise. Of course, fglrx was be
removed and the xserver-xorg-driver-ati(?) graphics driver was installed
instead. In 14.04 I wa
I'm seeing this as well with a brand new Oryx Pro from System76. Ubuntu
16.04. Just arrived last week.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu.
https://bugs.launchpad.net/bugs/1631191
Title:
Public bug reported:
Doing a straight upgrade ..
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.57-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-lowlatency 4.8.0
Uname: Linux 4.8.0-22-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Man, this bug is a big show stopper for me. I use Chromium on my
RaspPi-3 to turn my local printer into a cloud ready printer, and I have
not been able to use this feature since this bug came about.
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Ubuntu 16.04 - fully upto date with all updates.
Menus not visible on Terminal, but running
initctl restart unity-panel-service
definitely restores the missing menus.
I rarely use many other application - but I can confirm that Firefox
doesn't seem ever to loose it's menus.
If you need deb
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: tony 16160 F...m pulseaudio
/dev/snd/controlC1: tony 16160 F pulseaudio
/dev/snd/controlC0: tony 16160
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/1551823
Title:
PPTP connection d
** Tags added: regression-release
** Tags added: xenial
** Tags added: packaging
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1614806
Title:
This package breaks "ark" rar
Public bug reported:
So i was told here:
https://bugs.kde.org/show_bug.cgi?id=367535
this mav be a package bug in ubuntu xenial, which i confirmed. There are
links to the upstream issue, which is already fixed, and a bugfix that i
would gladly wish you backport.
Description:KDE neon User Edi
Similar problems here with the update on 2 laptops. What I did then was
to download an iso, burn a dvd, backed up my files to external HDD and
did a fresh install of version 16.04.1 on both laptops. So far
everything is running well with no problems. Installed on a third laptop
without any problems
Public bug reported:
Running Ubuntu 14.04.4. Updating Libreoffice via
http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ trusty/main.
My Libreoffice installation upgraded to 5.2.0.4 yesterday, and now
libreoffice-gtk no longer works with it. When I try to reinstall
libreoffice-gtk, the following
New => Fix Committed
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: n
Public bug reported:
Ubuntu 16.04.1 LTS
tex-common:
Installed: 6.04
Candidate: 6.04
Version table:
*** 6.04 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status
lubuntu-artwork-16-04:
Installed: (none)
Candidate: 0.61.1
Version
The fix is currently in silo 005, and was just marked 'Lander Approved'.
The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and
should hopefully land in the next few days.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug n
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: indicator-network (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
http
-config (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Status: In Progress => Invalid
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desk
So... a long time ago, when Ubuntu Touch was first being developed, we
hit a bug with certain rild implementations that would configure the
routing table when a data call was established, and this caused problems
with NM's routing logic.
The workaround was the creation of a NM dispatcher script c
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: phablet-tools (Ubuntu)
Status: Confirmed => Invalid
** Changed in: network-manager (
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
--
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/1597681
Title:
[CTA] Enable WAPI support
Status
I just updated bug #1593686 ( WPA-PSK limit introduced in OTA11 ) with
the root cause which confirms Pete's theory about timeouts.
That said, *if* a user had successfully connected to an AP prior to the
update to OTA11. This *shouldn't* have caused issues, as the psk would
already have been prese
I just confirmed that this is a regression is caused by the final
deprecation of dbus-glib in NM 1.2x, and it's replacement by gdbus. As
part of this work, the code which requests secrets from a secret-agent,
now uses code generated from the introspection XML to make the actual
DBus method call.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed => Invalid
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ub
@Andrea
Can you provide the info requested on comment #25 too?
--
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/1580146
Title:
[touch] Internet connection stops working while W
Public bug reported:
Please see:
http://askubuntu.com/questions/794769/16-04-networking-ux-
inconsistent-with-wifi-state
Reposted here:
HW: Bus 003 Device 002: ID 13b1:003f Linksys WUSB6300 802.11a/b/g/n/ac Wireless
Adapter [Realtek RTL8812AU]
Net: *-network
description: Wireless
@Andrea
There are two tests I'd like you to run for me.
First, let's verify the baseline by flashing OTA10 ( pre-NM 1.1.93
landing ) on a spare krillin, and then set the WiFi connection to the
opposite as earlier suggested, this time setting ipv4.method to ignore.
This will validate that IPv6 con
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
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/1565717
Title:
No connection after returning
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
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/1579098
Title:
[touch] Mobile data connectio
** Attachment added: "Screenshot of Hotspot setup dialog"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688157/+files/hotspot-spinning.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
** Attachment added: "indicator-network log file from arale after start failed"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688158/+files/indicator-network.log
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
-
Public bug reported:
Although the hotspot logic was vastly improved in OTA11, there are still
intermittent issues with enabling hotspot on arale.
On a freshly flashed phone running rc-proposed / 356, when I first
attempt to setup a hotspot, when I click the "Start" button, the spinner
shows up an
** Changed in: xorg (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => tony (antonio-al5000)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
I think sometimes, it's not an issue that come from Chrome at all. I
faced this issue last week and found this guide on Google, which helped
me to resolve it.
Check it out!
https://usefulpcguide.com/16820/fix-err_ssl_protocol_error-google-
chrome/
--
You received this bug notification because y
AND
/dev/snd/controlC0: tony 1594 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jun 6 00:25:27 2016
InstallationDate: Installed on 2016-06-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
Source
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubun
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tony 1594 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jun 6 00:25:27 2016
InstallationDate: Installed on 2016-06-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Re
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification becaus
OK, so there are two low-level problems:
1. InProgress error returned by SetProperty('Active',true) call to ofono
for a gprs-context.
Alfonso's first syslog shows that this can happen, but I'm not sure
exactly how to reproduce. NM would've had to start activation, then
Attached bounced down and
@Pat
The reason I asked was that two of the three scenarios listed by Alfonso
in the bug involved a crash or restart of NetworkManager, and the
resulting state was that the mobile data connection gets stuck trying to
activate an already active ( or activating ) connection.
I wasn't sure if he was
I'm able to reproduce this on arale ( rc-proposed, 334 ) by either
toggling cellular technology ( 2/3g -> 2g only, and back ), or by
putting the device into a faraday cage.
This is partially a regression in 1.1.93 ( we dropped a related patch ),
and partially a day-one problem.
I have what looks
@Andrea
Can you try adding the following setting to the NetworkManager
connection file for "Canonical-2.4GHz-g" in /etc/NetworkManager/system-
connections:
[ipv6]
method=ignore
"[ipv6]" should already be there, so just add "method=ignore", and
remove any other settings under "ipv6".
Restart the
So from @Andrea's latest pastebin:
- NM shows both modem and wlan0 as connected
- syslog shows one DHCP renewal period
- a do-add-ip4-address error is logged, however the IP address is still
configured ( ip addr show confirms this ); need to investigate whether
the error log message is correc
@Alfsonso
One more note, although comment #2 isn't a valid scenario, it does
trigger the same behavior.
The root cause of the bug is that the current NM wwan plugin doesn't
properly handle already activated contexts.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
@Alfonso
The scenario in comment #2 isn't valid. That said, I am able to
reproduce by killing NetworkManager, so I agree this is a valid bug that
needs to be fixed.
@Pat
As Alfonso pointed out, your problem is different, as there's no active
context, nor does NetworkManager appear stuck. Could
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-mana
= uid=1000
euid=1000 tty=:0.0 ruser= rhost= user=tony
May 17 10:31:47 river gnome-screensaver-dialog:
pam_sss(gnome-screensaver:auth): authentication success; logname= uid=1000
euid=1000 tty=:0.0 ruser= rhost= user=tony
May 17 10:31:47 river gnome-screensaver-dialog: gkr-pam: unlocked login ke
Thanks for that tip Michael. Sad, but after updating to 16.04 the
problem persists. I can't seem to find a permanent fix.
I've also changed video cards (nvidia 960 now) so the vid card itself
apparently wasn't involved. This is an upgrade install all the way from
12.04 if I remember correctly,
@Andrea
Let's try and work together to get the description of the bug (
including steps to reproduce ) accurate.
The initial description was network "stops working" when WiFi is "still
connected". This implies the network was actually connected and working
before the bug occurred, true? It'd al
@Andrea
One last thing... did you check for crash files?
--
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/1580146
Title:
Internet connection stops working while WiFi is still c
101 - 200 of 886 matches
Mail list logo
