Fresh install of Ubuntu 12.04.2 LTS, fully updated last night.
And I still have this crackling sound, and it's very loud.
lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV710/7
Seeing this on a 17.04 fresh install on LibreOffice Calc as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1589215
Title:
'Unknown Application Name' menu item in Indicator A
I have the same problem in Ubuntu 16.04 with an Huawei E122.
My workaround is to execute manually the switch using "Huawei newmode"
parameter:
/usr/sbin/usb_modeswitch --default-vendor 0x12d1 --default-product 0x1446 -J
--
You received this bug notification because you are a member of Desk
Public bug reported:
Right-clicking an icon on the Unity tray (not sure of the real name) and
attempting to click any menu item causes the menu to disappear, before
it can even be reached. The menu disappears the moment the mouse exits
the panel.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Packa
Public bug reported:
sistem not working
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libgl1-mesa-glx 8.0.4-0ubuntu0.7
ProcVersionSignature: Ubuntu 3.2.0-80.116-generic 3.2.68
Uname: Linux 3.2.0-80-generic i686
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Mon Apr 27 14:53
Public bug reported:
Trying to open Empathy results in nothing. Opening in a terminal
provides this output:
empathy: error while loading shared libraries: libwayland-egl.so.1:
cannot open shared object file: No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: empathy
Public bug reported:
The tooltip which pops up when a launcher icon is hovered cuts off
abruptly. Not much else to be said, other than it's pretty ugly.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140313-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13
Once implemented, the Startup Applications item should be removed from
the list of applications.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1280381
Title:
include sta
Public bug reported:
I've got this error when I tried to update the system:
Errors were encountered while processing:
duplicity
Current status: 1 update [-29].
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4
ProcVersio
Full update log:
The following packages will be upgraded:
duplicity
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/199 kB of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y
(Reading database ... 651380 files and directories
Public bug reported:
No, se exactamente cual es el reporte, me sale la pantalla de error
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 19.0.2+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
AddonCompatC
Hello Adela,
"I didn't know, what is a problem".
Two days ago, I was re-installed ubuntu 12.04 LTS, wiht kernel 3.5.0-23, all is
Ok. I can't update kernel 3.5.0-26 because when updated it ubuntu is corrupted
and I can't report it.
Thanks for all.
If, I have some more information, I'll report it.
** Changed in: unity
Status: Confirmed => Fix Released
** Changed in: unity (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https:
I've been experiencing this issue since I changed my user password.
Solved:
Followed post #24 indications and now I can properly restart and shutdown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.
By the way, as I side effect I was not able to mount other disk
partitions or removable media. Disabling auto login for my user solved
both problems at once.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https:/
It looks like this bug is back in 12.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgnomeui in Ubuntu.
https://bugs.launchpad.net/bugs/187183
Title:
nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Status in Nautil
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1035946
Title:
nautilus crashed with SIGSEGV
Status in “nautilus” package in Ubuntu:
New
Bug descr
Public bug reported:
no se que esta pasando, soy nuevo en linux
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: screen-resolution-extra 0.17.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-
I understand that this is marked as invalid, but it affects many people
and is triggered by seemingly nothing by other than restart.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1
Can this patch get integrated? I'm running Ubuntu 12.04 on my Power Mac
G4 and the lying icon bugs me, because I know I have a strong signal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpasupplicant in Ubuntu.
https://bugs.launchpad.
Public bug reported:
Description:Ubuntu 16.04.2 LTS
Release:16.04
unity-control-center:
Installed: 15.04.0+16.04.20160705-0ubuntu1
Expected Behaviour: When I start a recording with a specific audio
source, changing the default audio source has no effect on the recording
source.
Act
The same happens if I use the gnome-control-center
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1694294
Title:
Changing default audio source changes the recording audio
Although at the beginning they talk about other bug. In #860485 they
manage this problem. There is a workaround here:
https://bugs.launchpad.net/ubuntu/oneiric/+source/gnome-settings-
daemon/+bug/860485/comments/15
--
You received this bug notification because you are a member of Desktop
Package
Public bug reported:
Doesn't Update
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262
Uname: Linux 4.4.0-210-generic i686
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: i386
Date: Fri Dec 31 14:37:50 2021
E
Please report this for the network-manager debian package, the snappy-
hwe-snaps is only for the network-manager snap package.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snappy-hwe-snaps
Status: New => Invalid
--
You received this
The problem is not confined to Ubuntu.
I am seeing the same problem in Fedora SilverBlue 38 and Fedora SilverBlue 39.
The problem is restricted to `btrfs` only; other partitions such as
ext3, ext4, NTFS look fine.
--
You received this bug notification because you are a member of Desktop
Packages
@slyon thanks, I have manually tested and seems to work. I've created
https://github.com/snapcore/network-manager-snap/pull/15, let's see how
tests go.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bug
Public bug reported:
There is a mismatch between what netplan expresses when using globbing
in a netplan file and what NM understands when using a match setting.
For instance:
network:
version: 2
ethernets:
all-en:
match:
name: "en*"
dhcp4:
Right, it is more about the plugin, was not fully sure where to put
this, but now probably we can put under network-manager deb.
--
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/19
It turns out that this actually regressed some qualcomm modems because
modem-manager started to use some special netlink sockets that were not
enabled in the 5.4 kernel.
To have that we need (see LP: #1998194):
CONFIG_QRTR=m
CONFIG_QRTR_SMD=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m
in the 5.4 kernel
Unfortunately this is still happening with the patch from comment #3. In
fact I do not even need to create a VPN connection for this. If I
install easy-openvpn-server:
$ snap install easy-openvpn-server
it creates two tun devices (tun0 and tun1) that can be seen with "ip
address" command. That ma
Changing the check as suggested to:
if (!is_volatile && !is_nm_generated && !is_external) {
...
does help and netplan files for tun0 and tun1 are not written anymore.
But, when I create a VPN connection I still have problems.
$ network-manager.nmcli c import type openvpn file
$ network-manager.
> So IIUC the connection works as expected, but only after reloading the
connection profiles; it doesn't show up at the time it is expected,
right?
Hm, not sure if we mean the same. That two connections (tun2 and
) appear after connecting to the VPN is expected. NM
recognizes tun2 as "external" as
To reproduce the problem, this should be enough:
1. Create a connection to an OpenVPN server
2. Start the connection. The OpenVPN plugin will create a tunnel interface.
3. "nmcli c" should show a tunX connection and the VPN connection. "nmcli d"
should show tunX as a external connection.
4. Dis
Changes for nuntium in
https://github.com/ubuntu-phonedations/nuntium/pull/18
** Changed in: nuntium (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
** Changed in: nuntium (Ubuntu)
Status: Confirmed => In Progress
--
You received th
** 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/1454625
Title:
Cannot send MMS messages with com
The regression is due to NM setting DEVICE_IFACE to "ril_0" in version
0.9.10.0 instead of "/ril_0" as in 0.9.8.8.
There has been a change in nm-modem-ofono.c:nm_modem_ofono_new that
explains this (MODEM_UID is skipping the slash in the latest version).
The patch that creates nm_modem_ofono_new is
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
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/1454625
Title:
Cannot send MMS messages with
** Changed in: nuntium (Ubuntu)
Status: In Progress => Fix Released
--
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/1361864
Title:
add "Preferred" property to Connection
@Will, @Tony:
The behaviour you see is probably related to indicator-network, so if
you open a bug please include that package too. I think the behaviour
has improved after latest landings for that package which fixed some
problems for PUK-blocked SIMs, although issues still remain.
I do not real
Probably the same as bug #1459995
--
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/1370376
Title:
Can't receive MMS despite ability to send on Tele2
Status in network-manager p
Maybe this trace is the key here:
Mar 24 10:27:01 ubuntu-phablet NetworkManager[1377]: (ril_0):
device state change: prepare -> failed (reason 'no-secrets') [40 120
I have seen this error in some cases where I was unable to start a
cellular data connection. Rebooting solved the issue, and when t
This brach
https://github.com/rilmodem/ofono/pull/173
implements a per-context "Preferred" property that can be used freely by
the ofono clients to express preference on context activation.
** Changed in: ofono (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notificat
Marked as won't fix, as we are not using MBPI any more.
** Changed in: mobile-broadband-provider-info (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mobile-broadband-provider-info in
Ubuntu.
https:
@Jonas, yes, it can be used for MMS too. There is in fact no restriction
on how this flag is used on the ofono side. Whatever needs to be
enforced is something between system-settings and NetworkManager. For
ofono, it is just a property that can be read and written from outside,
and it is not used
Adding
to /etc/dbus-1/system.d/wpa_supplicant.conf makes hotspot.py work. This
would make sure that only the needed methods are accessible from
unconfined applications.
--
You received this bug notification because you are a m
Public bug reported:
Cannot send MMS messages with combined contexts in case the WiFi is
enabled, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
- enabled, for some operators. Combined contexts are able to handle
+ connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen
** Summary changed:
- Cannot send MMS messages with combined contexts with WiFi enabled
+ Cannot send MMS messages with combined contexts with WiFi connected
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
http
** Description changed:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contex
This is a regression: in the same situation MMS are being sent in RTM.
$ system-image-cli -i
current build number: 276
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-05-13 16:13:32
version version: 276
version ubuntu: 20150508
version device: 20150505-db7b5b
Public bug reported:
03mmsproxy sets up routes for MMS. It is undocumented and possibly racy.
It would be better if NetworkManager's ofono plugin did the job.
** Affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
** Affects: network-manager (Ubuntu)
Importa
** Changed in: nuntium (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nuntium (Ubuntu RTM)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://
My comment #23 is probably a red herring, as it looks like in the end
all DNS servers are registered in dnsmasq, and it sends queries to all
available servers. So I am hiding it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-man
Reproduced. syslog attached. Steps:
1. Start the phone
2. Check that you have network connectivity
3. Disable WiFi
4. Check that you cannot connect to network although cellular data is ON.
The mobile context was up, cnmi0 was up, phone was attached, but "ip
route" showed nothing.
Adding a defaul
Public bug reported:
Cellular data is not activated in ~50% of the cases in arale after
setting then unsetting flight mode.
I obtained the attached log this way:
1. Disabled wifi (to have less noise) and removed syslog (to make smaller the
attached one)
2. Reboot
3. See cellular data is on: rou
** Description changed:
Cellular data is not activated in ~50% of the cases in arale after
setting then unsetting flight mode.
I obtained the attached log this way:
1. Disabled wifi (to have less noise) and removed syslog (to make smaller the
attached one)
2. Reboot
3. See cellu
i-network crash
$ system-image-cli -i
current build number: 202
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/devel-proposed
alias: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-01-19 12:54:53
version version: 202
version ubuntu: 20150119
version device: 20150113-2a2e4c5
version
:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alfonso1591 F pulseaudio
Date: Mon Nov 19 19:43:00 2012
InstallationDate: Installed on 2012-11-18 (0 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
ProcEnviron:
File with ofono contexts that seems to trigger the bug
** Attachment added: "gprs"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316496/+attachment/4106226/+files/gprs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
syslog attached
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316496/+attachment/4106216/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:/
Public bug reported:
After installing packages from
https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/
when I reboot once, everything seems fine: NM opens an ofono context and
a connection is established. However, the second time I reboot, NM
crashes and upstart re-starts it conti
Full trace:
http://paste.ubuntu.com/7405345/
--
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/1316496
Title:
NM crash when testing MMS silo
Status in “network-manager” package
the time that msm_hsic_host is
locked is reduced substantially when low power mode is enabled. This
happens as no events from the modem are produced in this case (for
instance, no signal strength change is notified).
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) => Alfonso Sanc
Public bug reported:
The data for the following provider was missing:
...
Telenor
Telenor
Public bug reported:
Hola, me ha desaparecido la barra con los botones maximizar, minimizar y
cerrar. Muchas gracias
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9
Uname: Linux 3.5.0-28-generic x86_64
ApportVersi
Public bug reported:
Asda Mobile APN settings take precedence over Vodafone UK in MBPI. This
happens because both operators have the same (MCC, MNC) tuple and Asda
appears first in serviceproviders.xml.
This is a problem for ofono, as it always takes the first found operator
by default. This will
Also, if we stop network-manager upstart job after setting flight mode,
and then switch off flight mode, org.ofono.ConnectionManager.Powered
value will be 0.
** Changed in: ofono (Ubuntu)
Status: New => Invalid
** Also affects: ubuntu-system-settings
Importance: Undecided
Status:
# /usr/share/urfkill/scripts/enumerate
/org/freedesktop/URfkill/devices/100
Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100
Printing props for Ofono device: /org/freedesktop/URfkill/devices/100
soft: 0
name: Fake Manufacturer Fake Modem Model
urftype: org.freedesktop.
~# dbus-send --system --print-reply --dest=org.freedesktop.URfkill
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.GetAll
string:org.freedesktop.URfkill.Killswitch
method return sender=:1.2 -> dest=:1.67 reply_serial=2
array [
dict entry(
string "state"
va
** Summary changed:
- WiFi shown as enabled in indicator while enabled in status bar
+ WiFi shown as enabled in indicator while disabled in status bar
** Description changed:
After disabling WiFi and rebooting, WiFi appears as enabled in
indicator-network and system settings.
This contr
LP bug #1377148 has been reported to follow the -different from this
one- bug of the flickering roaming status.
--
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/1371032
Title:
C
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1376957
Title:
Cellular Data Prefs not pre
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
** Changed in: network-manager (Ubuntu)
Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
First of all, my assumption here was that no WiFi icon would be shown on
the display if WiFi was disabled, and that an icon with empty "beam"
would be shown if WiFi was enabled but we where not connected to any.
If that is not the case, and the same icon is used in both cases, we
would need to ret
Ok, I have re-read this and the only problem in the original screenshot
was the lack of networks, which *is* a bug. Also, the issue with just
reported in comment #7 is a bug. @Antti, could you comment on this?
Should be use this bug for that issue or open a new one?
--
You received this bug notif
The image for comment #7 was:
# system-image-cli -i
current build number: 29
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-09-11 05:41:43
version version: 29
version ubuntu: 20140910
version device: 20140908-d8c11f3
version custom: 1410379789
** Changed i
My guess here is that what I saw was an instance of the generic problem
that NM seems to have some times creating connections, which is probably
related to not detecting the creation of the ofono's ConnectionManager
interface.
As I usually have two SIMs around, this is maybe easier for me to
repro
This show that this is a duplicate of bug #1336715
phablet@ubuntu-phablet:~$ dbus-send --print-reply
--dest=com.canonical.indicator.network /com/canonical/indicator/network
org.gtk.Actions.Describe string:wifi.enable
method return sender=:1.48 -> dest=:1.130 reply_serial=2
struct {
bool
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
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/1368675
Title:
No
@Matthew I have an idea of what might be happening, but I need traces to
confirm. Please do as follows (I assume we are talking about Nexus 4
here):
$ phablet-shell
$ sudo su
# stop ofono
# export OFONO_RIL_HEX_TRACE=""
# export OFONO_RIL_TRACE=""
# ofonod -n -d -P stktest,provision,sap,udev,dun,s
** Changed in: ofono (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/1368675
Title:
No Wi-Fi on Nexus 4
(org::ofono::Interfac
This PR contains a fix for ofono:
https://github.com/rilmodem/ofono/pull/87
With the fix "Status" is now "denied", as can be seen in list-modems
output from Matthew:
https://pastebin.canonical.com/117079/
However, Matthew still sees issues with the WiFi indicator, but
indicator-network does not
@Tony, the crash was because "Status" property was an empty string (it
was not "unknown" or anything else), which is wrong as specified by
ofono/doc/network-api.txt. And it was an actual ofono bug, as we were
getting a value for state from rild that was not valid for ofono core.
--
You received t
@Víctor, @Tony:
Regarding roaming, there are already mechanisms that check the content
of SIM files and the registered network that should prevent the
registration state to be roaming, even in these cases when we bounce
between different networks.
Víctor, could you please check if you see a roami
I have just noticed that the output of monitor-ofono is part of the
logs, and I see that network status actually gets into roaming state.
But, it is in very short time windows:
2014-09-26 20:11:18,643 {NetworkRegistration} [/ril_0] Status = roaming
2014-09-26 20:11:19,323 {NetworkRegistration} [/r
I have monitored calls to ofono DBus connection manager interfaces
following comment #7 in
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1226739
The command was:
# dbus-monitor --system "interface=org.ofono.ConnectionManager"
"interface=org.ofono.ConnectionContext"
I have attac
Public bug reported:
Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r140 krillin
When testing a large number of phone calls it could be seen that on
certain calls there would be a significant delay between the snap
decision dialog being displayed and the ringtone beginning to play.
In extreme c
See LP bug #1388899 for more information.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1394105
Title:
Sometimes significant lag between snap dialog and ringtone start
Status in
Same error for OEM phones:
<<
phablet@ubuntu-phablet:~$ nmcli c up uuid aab22b5d-7342-48dc-8920-1b7da31d6829
Error: Timeout 90 sec expired.
>>
I attach the syslog. NM fails with the same reason:
Jul 11 09:29:59 ubuntu-phablet NetworkManager[1456]: Activation
(wlan0/wireless): Ad-Hoc network cr
Public bug reported:
In case NM has failed to open any mobile data context, it will not re-
try when rebooting the phone.
This happened with a pre-paid SIM with no credit: opening a data context
for it obviously failed. After adding credit to the SIM, I followed the
instructions from the operator
This happened for touch image #149, with network-manager version
0.9.8.8-0ubuntu23 .
syslog for a simulated case where the APN name is wrong (APN
err.airtelwap.es), then ofono is stopped, the APN corrected
(airtelwap.es) and the phone rebooted is attached. The result is that no
context is activate
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: snappy-hwe-snaps
--
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/18819
This is, I think, a glib bug. See LP:#1846837.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
broke
This is, I think, a glibc bug. See
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1914044
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and totem-video-thumb
This is, I think, a glibc bug. See LP:#1914044
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1846837
Title:
Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently
broke
There is here a change in behavior in lxc/lxd. Running
https://paste.ubuntu.com/p/vz7SXcX3K9/:
On hirsute lxd container:
root@hirsute:~# ./test
access errno 13
path is read only: 0
root@hirsute:~# mount | grep 'sysfs on /sys '
sysfs on /sys type sysfs (rw,relatime)
On focal lxd container:
root
Just FTR, note that the change in NM upstream was needed so the network-
manager snap was able to correctly detect if udevd is running. We
currently build the snap from the source package + some patches
including this one. But, the long term target is to be able to create
the snap by simply staging
It looks like the VPN related SRU that was previous to this one was
reverted. Could we land this into bionic?
--
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:
[SR
Public bug reported:
It has been detected that pppd crashes when running confined inside the
NM 1.10 snap. This happens because it cannot open/create a file in
called /var/run/pppd2.tdb, which triggers a bug later.
This is the backtrace:
#0 0x5581bd1031e9 in tdb_close (tdb=0x0) at tdb.c:187
1 - 100 of 178 matches
Mail list logo
