Public bug reported:
The following message, or something like it, is output when an update to
appstream is done on 19.10:
dpkg: error: version '/usr/share/app-info/yaml /usr/share/app-info/icons' has ba
d syntax: version string has embedded spaces
This appears to be caused by this line in the
I tested on a System76 NVIDIA laptop that was affected by this issue, on
bionic and disco with proposed enabled. The eDP displays are detected as
builtin displays, as expected.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco
** Tags added:
Please see https://gitlab.gnome.org/GNOME/gnome-
desktop/merge_requests/39
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1731318
Title:
NVIDIA systems will not suspend with
For what it's worth, what was said about the patch was that the code it
was editing would be going away soon. That never happened. I have
commented again to see if there is still interest in the patch upstream.
I highly recommend considering the patch for Ubuntu even if upstream has
not taken it.
The solution to this is to run X11 as root, so it can use VGA arbiter
and detect displays on both the NVIDIA and modesetting drivers.
Add this to /etc/X11/Xwrapper.config :
needs_root_rights = yes
--
You received this bug notification because you are a member of Desktop
Packages, which is
You can download the Pop!_OS gnome-shell packages here:
https://launchpad.net/~system76/+archive/ubuntu/pop/+packages
We added the commit that fixed this on top of the current Ubuntu
version. You will probably only need to install these two deb files:
I was able to work around this with the attached patch. Apply by adding
the file to debian/patches and its name to the end of
debian/patches/series
** Patch added: "nvidia-background-workaround.patch"
There is an upstream bug related to GNOME 3.32 here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1084
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
** Also affects: gnome-shell via
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
** This bug has been marked a duplicate of bug 1809407
[nvidia] Corrupted wallpaper after resuming from suspend
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
See https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
** Affects: gnome-shell
Importance: Unknown
Status: Unknown
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added:
When can we expect a release of the proposed xkb-data?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in
I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for
me on bionic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed
I will try it out on bionic in a few hours
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in libxkbcommon
I can confirm that xkb-data 2.23.1-1ubuntu1.18.10.1 fixes this issue for
me on cosmic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed
That sounds great!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in gnome-settings-daemon package in
This particular issue as described no longer occurs. Instead, it should
be tracked here:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1740894
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon
Yes, this is still an issue. Please see the above scripts. I am not
aware of why gnome-settings-daemon does not receive the keypress and
trigger airplane mode, if those X11 packages are up to date.
--
You received this bug notification because you are a member of Desktop
Packages, which is
** No longer affects: system76
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/602809
Title:
add Mouse Click Debounce Feature?
Status in xserver-xorg-input-evdev:
Public bug reported:
Currently administrators are only added to the sudo group. This was
fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/810907, but there has likely been a
regression.
** Affects: accountsservice (Ubuntu)
Importance: Undecided
I can also confirm that this fixed the issue in Pop!_OS and elementary
OS.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1749546
Title:
Booting a live session is slow -
Yes, the latest packages work fine
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: gnome-initial-setup (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is
There is no issue with that. We will be able to keep our patches in
initial setup without any effort from Ubuntu and minimal effort from
Pop. We are going to be encouraging full disk encryption, the same as
Ubuntu.
--
You received this bug notification because you are a member of Desktop
This may also be the cause of https://bugs.launchpad.net/ubuntu/+source
/gnome-settings-daemon/+bug/1722034
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
In artful and later, a number of kernel drivers send KEY_RFKILL - which
is being ignored by the userspace handling code.
https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL
** Also affects: libxkbcommon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg
Attached is an alternative script which sends KEY_WLAN, which does
trigger Airplane Mode, as expected.
** Attachment added: "wlan.py"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+attachment/5030182/+files/wlan.py
--
You received this bug notification because
Attached is a test script that should trigger Airplane Mode in GNOME,
but does not. The code in gnome-settings-daemon looks for XF86RFKill,
but the key is not identified as such.
This is what xev reports from the script:
KeyPress event, serial 55, synthetic NO, window 0x2c1,
root 0x1ee,
Public bug reported:
There are a couple things going on, that could be fixed by a Debian or
Ubuntu maintainer:
- libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces
the RFKill key: https://lists.freedesktop.org/archives/wayland-
devel/2017-August/034721.html
- x11-proto needs
In artful and later, a number of kernel drivers send KEY_RFKILL - which
is being ignored by the userspace handling code.
https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Attached is an alternative script which sends KEY_WLAN, which does
trigger Airplane Mode, as expected.
** Attachment added: "wlan.py"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722034/+attachment/5030178/+files/wlan.py
--
You received this bug notification because
Attached is a test script that should trigger Airplane Mode in GNOME,
but does not. The code in gnome-settings-daemon looks for XF86RFKill,
but the key is not identified as such.
This is what xev reports from the script:
KeyPress event, serial 55, synthetic NO, window 0x2c1,
root 0x1ee,
There are a couple things going on, that could be fixed by a Debian or
Ubuntu maintainer:
- libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces
the RFKill key: https://lists.freedesktop.org/archives/wayland-
devel/2017-August/034721.html
- x11-proto needs a new release. This
Thanks for the feedback Robert. I will work on updating my patch.
That does sound like a much cleaner approach.
--
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/1699216
I tried looking for ubuntu.css in gnome-shell 3.26.1-0ubuntu5, but I did
not find it. Where do you see this issue mifjpn?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715722
Yes mif, that will probably be an issue. I will write a patch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715722
Title:
Allow safe override of GDM3 theme
Status in GNOME
Public bug reported:
With the NVIDIA driver, nvidia-384, the system will not sleep when the
lid is closed due to gnome_rr_output_is_builtin_display incorrectly
returning false. I have linked to an upstream bug, which also has
patches fixing the issue.
** Affects: gnome-desktop
Importance:
Here is a patch without symbol changes or whitespace changes
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4997109/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification
Finally, the kernel model from a SATA drive:
$ cat /sys/block/sda/device/model
Samsung SSD 850
And from an NVME drive:
$ cat /sys/block/nvme0n1/device/model
Samsung SSD 950 PRO 256GB
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Here is the information from an NVME drive. Note that ID_MODEL is
missing:
$ udevadm info /dev/nvme0n1
P: /devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
S: disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V
S: disk/by-id/nvme-eui.0025385761b084ef
S:
Attached is the current behavior, no Model is set
** Attachment added: "Screenshot from 2017-10-17 15-06-58.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+attachment/4974174/+files/Screenshot%20from%202017-10-17%2015-06-58.png
--
You received this bug
Attached is a screenshot of the expected behavior, with a model set
** Attachment added: "Screenshot from 2017-10-17 15-07-04.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+attachment/4974173/+files/Screenshot%20from%202017-10-17%2015-07-04.png
--
You
Public bug reported:
The Model field for NVME drives is blank. I believe this issue comes
from udisks2, and then from udev.
udisks2 has a function for getting the model which returns blank,
udisks_drive_get_model
udev has a parameter that should be returned for a disk if it has a
model,
Here is the information from a SATA drive:
$ udevadm info /dev/sda
P: /devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda
N: sda
S: disk/by-id/ata-Samsung_SSD_850_EVO_M.2_250GB_S33CNX0HC13989R
S: disk/by-id/wwn-0x5002538d418ea893
S: disk/by-path/pci-:00:17.0-ata-2
E:
12:36 seb128 dmj_s76, right, we are likely to get it reviewed next cycle
12:37 seb128 it hasn't been high priority for us since we don't use
gnome-inital-setup and don't plan to for next cycle either
12:37 seb128 but we should be able to review those changes anyways
12:51 jackpot51
IRC Log:
10:39 jackpot51 Can we talk about this patch again?
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216
ยทยทยท
10:39 ubot5 Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted
home support" [Wishlist,Confirmed]
10:40 jackpot51 I just saw a
This one updates the symbol names - they did not get updated with a
debuild -S
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966858/+files/accountsservice_encrypt_home.debdiff
--
You received this
Here is an updated version of the patch for accountsservice
--
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/1699216
Title:
Encrypted home support
Status in
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966857/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
The gnome-info-overview-panel.desktop points to about instead of info-
overview, meaning it launches the WiFi page instead of the
Details->About page.
I have attached a debdiff fixing this.
** Affects: gnome-control-center
Importance: Unknown
Status: Unknown
This affects pop-session as well, which uses session overrides similar
to how ubuntu-session does. The desktop icon settings are also
incorrect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
** Patch removed: "fix_x11_font_dpi.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956941/+files/fix_x11_font_dpi.patch
** Patch added: "fix_x11_font_dpi.debdiff"
Here is a debdiff with the change, if Ubuntu would like to use it
sooner.
** Patch added: "fix_x11_font_dpi.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956941/+files/fix_x11_font_dpi.patch
--
You received this bug notification because you are a
I have recommended this patch to upstream, which is the simplest method
to fix the scaling issues described in detail above.
** Patch added: "fix_x11_font_dpi.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713323/+attachment/4956940/+files/fix_x11_font_dpi.patch
--
You
Thanks very much!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1715722
Title:
Allow safe override of GDM3 theme
Status in GNOME Shell:
Won't Fix
Status in gnome-shell
The build finished, and I installed Ubuntu, Pop, and GNOME sessions
side-by-side. All three worked, and the GDM theme changed based on the
alternative selected. I believe the second patch version works as
expected.
--
You received this bug notification because you are a member of Desktop
Linking to an upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=787454
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=787454
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages,
11:01 Laney goodnight!
11:01 jackpot51 Ok, good night Laney
11:12 didrocksjackpot51: mind toning a little bit done please?
11:12 didrocksjackpot51: you are quite offensive in that bug report
11:13 didrocksand proposing a patch that you even didn't test it
10:57 Laney hmm, I guess actually we could use this in Ubuntu to let people
use the default gdm theme
11:00 Laney maybe not, that's the built in one isn't it?
11:00 Laney jackpot51: please attach it, I think it's worth considering
--
You received this bug notification because you
What is even worse, is that most of these changes that hard-code
Ubuntu's theme happened on the edge of the Feature Freeze period,
meaning any attempts to revert them or improve them are impaired by
bureaucracy.
Please try to see why this is a problem, and learn from this in the
future.
--
You
didrocks, I will also work on an upstreamable solution, but I am not
very satisfied with your unwillingness to see things from my
perspective. You have essentially broken GDM3 for all Ubuntu
derivatives, forcing your theme upon them, and then having no desire to
work on any solution to remove this
Here is a new patch fixing the alternatives path. I am waiting on a
launchpad build to test this fully:
https://launchpad.net/~system76/+archive/ubuntu/pop-
staging/+build/13352379
** Patch added: "ubuntu_gdm_alternatives.debdiff"
** Patch removed: "ubuntu_gdm_alternatives.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715722/+attachment/4946604/+files/ubuntu_gdm_alternatives.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
didrocks, here is a debdiff for implementing the alternatives method. It
did not require much code.
Please let me know what you think!
** Patch added: "ubuntu_gdm_alternatives.debdiff"
It is critical to our Beta release that we have a reliable method of
overriding the GDM theme, so the alternatives method seems to be the
best way to go. We can talk about further improvement and upstreaming
after 17.10
--
You received this bug notification because you are a member of Desktop
didrocks, I am going to do what I described above as it is a clean and
quick method to having both of our systems ready for a 17.10 Beta
release.
Is that ok?
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Jeremy Soller (jackpot51)
--
You received this bug notificat
Public bug reported:
Currently, in artful, GDM3's theme is hardcoded to be /usr/share/gnome-
shell/theme/ubuntu.css
In the Ubuntu default session, this is the same CSS file as the gnome-
shell mode in /usr/share/gnome-shell/modes/ubuntu.json
However, in other flavors, it makes sense to install
I have extra whitespace changes in there, I will resubmit with `-w`
--
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/1699216
Title:
Encrypted home support
Status in
Here is a better patch, ignoring whitespace changes.
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because
tsimonq2, here id a debdiff file
** Patch added: "Accountservice Encrypt Home Debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945505/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because you are a member of
tsimonq2, I have subscribed ubuntu-release. We have modifications in our
PPA that utilize this patch to accountsservice. If the patch to
accountsservice is not merged in Ubuntu's version, our version will be
overridden when there is another accountsservice release.
Since this is a feature that is
ximion, as I already said here:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/comments/11
Encrypted home cannot go upstream, as adduser --encrypt-home is only
implemented on Ubuntu.
--
You received this bug notification because you are a member of Desktop
Packages,
Simon, it is critical for our efforts that the accountsservice patches
make it upstream before 17.10. Can we focus only on those, leaving
inotial setup and control center patches for 18.04?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I believe this applies again to Ubuntu 17.10.
--
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/1437502
Title:
nautilus lacking 'new document' in context menu on GNOME
Status in
Yes, I believe this still affects 16.04. I applied the patch on machines
that System76 ships, but it is not upstream. It is the same patch as was
applied to 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
seb128: I subscribed ubuntu-sponsors. Is there anything else I can do?
--
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/1699216
Title:
Encrypted home support
Status in
Would anyone like to comment on my patches?
--
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/1699216
Title:
Encrypted home support
Status in accountsservice package in
I made a mistake in the accountsservice patch. Here is an updated
version.
** Patch added: "encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1699216/+attachment/4899663/+files/encrypt_home.patch
--
You received this bug notification because you are a
** Patch added: "gnome-initial-setup_encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899524/+files/gnome-initial-setup_encrypt_home.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Patch added: "gnome-control-center_encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899523/+files/gnome-control-center_encrypt_home.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is
Ok, here are new patches that do not break the current API.
It is a little bit messier in accountsservice due to this.
** Patch added: "accountsservice_encrypt_home.patch"
ximion, I am working on a more compatible patch, one that does not break
libaccountsservice API. As for going upstream, I would like to go into
Ubuntu first, as --encrypt-home is not implemented in other distros
right now.
--
You received this bug notification because you are a member of Desktop
Attached you will find a patch for encrypted home support in gnome-
initial-setup. This patch will add a switch for "Encrypted Home Folder",
and send the correct value to CreateUser in accountsservice.
** Patch added: "encrypt_home.patch"
If you would like to test these patches in action, you can add this PPA
and update:
https://launchpad.net/~system76/+archive/ubuntu/pop/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Attached you will find a patch for encrypted home support in gnome-
control-center. This patch will add a switch for "Encrypted Home
Folder", and send the correct value to CreateUser in accountsservice.
** Patch added: "encrypt_home.patch"
Attached find a proposed patch for this, allowing for two more patches
to gnome-initial-setup and gnome-control-center that add encrypted home
support when creating users. I have tested it on Ubuntu GNOME 17.04, and
it works.
** Patch added: "encrypted_home.patch"
Public bug reported:
In the CreateUser D-bus call, allow the home directory of the new user
to be encrypted.
** Affects: accountsservice (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: Confirmed
Here is how I have been working around this bug for System76's machines:
https://launchpadlibrarian.net/303137969/wpa_2.4-0ubuntu6_2.4-0ubuntu7~system76~1.diff.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
Would it be acceptable to have a patch to `wpa` to add `IgnoreOnIsolate`
for the time being? If we hold it in the Ubuntu debian/patches then we
can wait for a better solution to be done upstream.
--
You received this bug notification because you are a member of Desktop
Packages, which is
If we update `network-manager-applet` to include this commit:
https://git.gnome.org/browse/network-manager-
applet/commit/?id=7a59d41e5fd0da51f1f7aae7518befdb1182, then
`libnma` can be used, and this bug can be fixed without further code
changes.
--
You received this bug notification because
I created an upstream bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=779153
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1667129
Title:
Python cannot create
Sure thing.
** Bug watch added: GNOME Bug Tracker #779153
https://bugzilla.gnome.org/show_bug.cgi?id=779153
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1667129
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1667129
Title:
Python cannot create
Public bug reported:
Python, using pygobject, is unable to spawn an NMGtkWifiDialog using the
new function, due to the SSID setting not being settable (GArray
is not supported by pygobject). If the SSID is not set, the dialog will
not display correctly, and will not function.
A potential fix is
Sorry, I attached an incorrect patch, showing usage in ubiquity.
Here is the correct patch.
** Patch added: "python_wifi_dialog.patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1667129/+attachment/4824804/+files/python_wifi_dialog.patch
--
You received this bug
This is required for a patch to ubiquity:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1107935
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1667129
Title:
Here is a patch, python_wifi_dialog.patch
** Patch added: "wpa_enterprise.patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1667129/+attachment/4824791/+files/wpa_enterprise.patch
--
You received this bug notification because you are a member of Desktop
Packages,
Here is a test script. Edit IFACE and AP_NAME to be what you can connect
to.
** Attachment added: "wifi_dialog.py"
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1667129/+attachment/4824792/+files/wifi_dialog.py
--
You received this bug notification because you are a
Yes, I am. I just need to know what is permissible - we can add
IgnoreOnIsolate in a ubuntu patch but it seems like the source of the
issue is in network manager - it should detect that wpa supplicant is
not running and restart it dynamically.
--
You received this bug notification because you
By the way, it is possible to trigger the bug running on your own
system. All you have to do is run `sudo systemctl isolate
default.target` while connected to WiFi
Bluetooth may also go down.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
This is caused by wpa_supplicant being killed by systemctl isolate in
oem-config-firstboot
A potential fix is to add IgnoreOnIsolate=true to [Unit] in
wpa_supplicant.service
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
99 matches
Mail list logo