I can confirm the commit is working :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834845
Title:
DetachedInstanceError: Parent instance is not
bound to a Session
To manage notifications about
Is the issue still valid an reproducible?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981592
Title:
package latexmk 1:4.24-1 failed to install/upgrade: ErrorMessage:
dependency problems - leavin
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834950 (xenial/li
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834898 (bionic/li
Public bug reported:
Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally.
It's detected, but nothing seems to work, however working very normal with
Windows 10.
Laptop model - iBall CompBook M500
It's somewhat similar to this bug, probably using the same touchpad hardware
Public bug reported:
name: python3-asyncpushbullet
url: https://pypi.org/project/asyncpushbullet/ and
https://github.com/rharder/asyncpushbullet
short description: An asyncio-based python client for Pushbullet
long description: This is a python library for synchronous and asyncio-
based communi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835041
Title:
Package asyn
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1835040
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Details in the video: https://photos.app.goo.gl/4aWGw7dbR95iqZ796
P.S.: Sorry, I don't know the method how to load video to Launchpad.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Unam
Did launchpad auto-fill in the bug title? I don't remember typing in
"spinning" or any of the rest of the text, but maybe I'm just going mad!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835033
Titl
Sorry, when will we see Gnome 3.33.3 with Ubuntu 19.10 (testing)?
пн, 17 июн. 2019 г., 9:50 Daniel van Vugt
:
> Note that not all performance improvements will ever make it into Ubuntu
> 18.04.
>
> If you want higher performance right now then please use Ubuntu 19.04
> instead. And Ubuntu 19.10 w
Public bug reported:
3.5 is out since May and no major issues got reported.
Merge it from Debian/experimental (waits for bulls-eye there), but we want it
in Eoan for being up to date and also to catch any issues with the new code
before 20.04.
See https://chrony.tuxfamily.org/news.html
** Affe
** Tags removed: block-proposed block-proposed-bionic kernel-block-
proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833932
Title:
linux-oem-osp1: 5.0.0-1012.13 -proposed tracker
To manage n
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835040
Title:
Touchpd not working properly on Linux
To manage notifications about
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
ht
Actually, the version of libvirt I'd upgraded from was 5.0.0-1ubuntu2.2
-> 5.0.0-1ubuntu2.3.
Downgrading all of libvirt-clients libvirt-daemon libvirt-daemon-driver-
storage-rbd libvirt-daemon-system libvirt0 to 5.0.0-1ubuntu2.2 seems to
have fixed this after several sleep-resume cycles, although
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835046
Title:
merge version 3.5 for E
** Summary changed:
- linux: -proposed tracker
+ linux: 4.4.0-155.182 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => K
I might have asked at a bad time of day, document it here
@jjohansen/jdstrand (now subscribed to the bug):
[13:50] does the 2.13.2-9ubuntu7 have the "include if exists" code that we once
discussed for https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1745114 ?
[13:50] if so, is there a way t
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834916 (trusty/li
Oh! Trevhino said both that he could reproduce this *and* that he had a
fix (although he didn't seem very happy with the fix).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834583
Title:
GNOME Shel
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: New =
This configuration that is referred to in the duplicate now linked here
is a Debian and Ubuntu specific configuration option in the **example**
default config. While it may not match with the CURRENT PHP paths it is
designed as an example rather than a "quickly enable this feature"
mechanism. Thi
** Changed in: gnome-calendar
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725005
Title:
gnome-calendar crashed with SIGSEGV in GCAL_IS_MANAGER()
To manage notificat
I will prepare a change in Eoan for this in the future however this also
needs upstreamed to Debian as well for them to do a similar comment in
theirs. Debian is currently frozen however so it is unlikely to see a
fix there until after freeze.
--
You received this bug notification because you ar
Related changes are
3 * SECURITY UPDATE: DoS via incorrect permissions check
4 - debian/patches/CVE-2019-3886-1.patch: disallow virDomainGetHostname
5 for read-only connections in src/libvirt-domain.c.
6 - debian/patches/CVE-2019-38
Packages uploaded to their respective -proposed queues, it's up to the
SRU team now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiat
Excellent and nice post. This is such a great resource that you are
providing and you give it away for free. I love seeing that understands
the value. I'm glad to have found this post as its such an interesting
one! I have also something very interesting for you. Visit our blog
post-http://www.appl
** Changed in: upower (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744366
Title:
xfce power manager shows wrong battery life information (Lbuntu
16.0
** Tags added: id-5d1adb08f3b51440c727e268
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820604
Title:
curtin fails to find itself in subiquity snap, when running on serial-
subiquity@.service
T
I'll try a few full boot-sleep-resume cycles on both versions and see
how often it replicates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834113
Title:
QEMU touchpad input erratic after wakeup fr
As a temporary fix, so you don't have to launch it from the terminal you
can do something like this, (need root):
sudo su
mv /usr/bin/vlc /usr/bin/vlcbin
echo 'QT_AUTO_SCREEN_SCALE_FACTOR=0 /usr/bin/vlcbin "$@"' > /usr/bin/vlc
chmod +x /usr/bin/vlc
It fixes the problem for me and i can launch it
Hi Werner,
The fix for this bug hasn't been released yet, so kernel 4.15.0-54 is
expected to still have the issue. A new kernel version containing the
fix is planned to be published to -proposed this week and an automated
comment will be added when the new version is available for testing.
Meanwhi
I forgot to post the version of upower I am running:
peter@peter-Studio-1558:~$ apt show upower
Package: upower
Version: 0.99.4-2ubuntu0.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1744366
Title
I have similar problem on xubuntu 16.04. The only problem is that it
occurs with only one of my two batteries. This leads me to consider that
the problem may be stemming from an interaction with the battery
metadata. The odd thing about the battery (the one that instigates the
faulty behavior) is
This bug was fixed in the package whoopsie - 0.2.65
---
whoopsie (0.2.65) eoan; urgency=medium
[ Sebastien Bacher ]
* Don't use deprecated n-m components. LP: #1833236.
-- Steve Langasek Mon, 01 Jul 2019
11:43:00 -0700
** Changed in: whoopsie (Ubuntu Eoan)
Status: Fix
Hi,
any updates on this one?
All I could reproduce would be fixed with the suggested change, but
since according to you that isn't sufficient I now need you to debug
your case and/suggest add whatever change on top that you need.
After fixing the bug that I could identify I'd hate if this goes in
Public bug reported:
the error had happened when i tyr to install pcl library
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libavahi-glib1:amd64 0.6.32~rc+dfsg-1ubuntu2 [modified:
usr/lib/x86_64-linux-gnu/libavahi-glib.so.1.0.2]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Public bug reported:
I had that error when upgrading from 16.04 to 18.04.
Upgrade has been discontinued.
What should I do to upgrade to 18.04?
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835052
Title:
package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess
installed post-installation
The right state for ack is "in progress" per [1], setting that.
[1]: https://wiki.ubuntu.com/MIRTeam#Process_states
** Changed in: zope.component (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Thank you for your bug report. The change is commit from Debian
https://salsa.debian.org/gnome-team/librsvg/commit/1c53c0b1d
Could you report it to them on https://packages.qa.debian.org/libr/librsvg.html
?
** Changed in: librsvg (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: librs
Hi Hui Wang, sorry it has taken me so long to test this. I installed
your patch and noticed the following things:
1. I **think** the noise is less than before although still present.
2. The commands in your test instructions now make no difference
(https://bugs.launchpad.net/ubuntu/+source/alsa-d
Public bug reported:
-
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioD
Public bug reported:
At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) - a driver for
network controllers(s) in Marvell SOCs, particularly Armada 8040 -
neither as a model or a built-in:
$ uname -m
aarch64
$ grep MVPP2 /boo
** Summary changed:
- linux: -proposed tracker
+ linux: 4.18.0-26.27 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => St
I was just waiting for some feedback, as this is hard to reproduce. I
tried the script for a few minutes but nothing out of the ordinary
happened.
I see two +1s now, so I'll proceed with the SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1835054
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/ruby2.3/+git/ruby2.3/+merge/369590
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet agent using
Thanks, closing then
** Package changed: indicator-keyboard (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
Currently the relevant error message is:
Setting up texlive-base (2009-13) ...
texconfig: unknown option `paperconf' given as argument for `texconfig dvips'
texconfig: try `texconfig dvips' for help
texconfig: unknown option `paperconf' given as argument for `texconfig dvipdfmx'
texconfig: try `te
Follow-up,
The current ACPI status still remain unresolved to this date. The dmesg is
located on https://linux-hardware.org/index.php?probe=ce83006200
Is there someone from HP willing to take a look?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: ruby2.3 (Ubuntu)
Status: Triaged => In Progress
** Changed in: ruby2.3 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834903 (bionic/li
You didn't address my comments.
I really don't want it being called lockPref. That will confuse it with
the autoconfig "lockPref" function.
There is already enough confusion with pref()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
:(
Ideally, I'd like to favor this patch over the one I proposed at
https://bugzilla.mozilla.org/show_bug.cgi?id=976334 - since it has been
tried and tested for so long...and that just adds another use case for
this: ease of locking preferences for android distributions (which
aren't as straightfo
(In reply to mirh from comment #113)
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-May/149706.html
>
> CX2072X is landing in 5.3.
That's good news! I'll look forward to it, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ Ruby proces
It's not the same syntax, that's my point.
pref() in a prefs.js file is NOT the same as pref() in an AutoConfig.js
file.
pref() in prefs.js sets the default pref, defaultPref() in an Autoconfig
sets a default pref.
user_pref() in prefs.js sets a user pref, pref() in an AutoConfig file
sets a use
> I hope these efforts can be merged into mainline Linux and ALSA.
Me too: I lack the know-how to fix the kernel myself, unfortunately...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563110
Title:
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu Disco)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
https://mailman.alsa-project.org/pipermail/alsa-
devel/2019-May/149706.html
CX2072X is landing in 5.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563110
Title:
No sound on Asus e200ha, intel ss
** Tags added: rls-ee-incoming
** Changed in: python3.7 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834236
Title:
codecs.open(errors='strict') doesn't f
The syntax is a triviality of the patch. The core problem here is that
there's no one to review the patch so that it possibly lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541951
Title:
Firef
(In reply to Mike Kaply [:mkaply] from comment #39)
> Oddly, this document:
>
> https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/
> A_brief_guide_to_Mozilla_preferences
>
> Says we already support lockPref in JS files?
It says: "All preferences files may call pref(), user_pref() and
(In reply to Mike Hommey [:glandium] (VAC: 31 Dec - 11 Jan) from comment #32)
> The syntax is a triviality of the patch. The core problem here is that
> there's no one to review the patch so that it possibly lands.
Can I help review?
--
You received this bug notification because you are a member
>From a quick glance at the history of the patch in Debian, in the past 5
years, I had to do actual but trivial code changes twice, and adapt to
context changes twice (one of them having been the change from PRBool to
bool)
--
You received this bug notification because you are a member of Ubuntu
(In reply to Benjamin Smedberg [:bsmedberg] from comment #36)
> Because this came up on the mailing list
Which mailing list is that? (just so I can make sure I'm following the
right one)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Comment on attachment 8613433
Allow .js preference files to set locked prefs with lockPref()
Because this came up on the mailing list, I'll try to be explicit about
the decision here. I don't think we should allow extensions to lock
preferences, and we don't even have a clear description (other th
Comment on attachment 8613433
Allow .js preference files to set locked prefs with lockPref()
>From b8015e0754742650a4877de9ebe7d6db2671970d Mon Sep 17 00:00:00 2001
>From: Mike Hommey
>Date: Sat, 21 Jun 2008 02:48:46 +0200
>Subject: [PATCH] Allow .js preference files to set locked prefs with
> lo
Looking forward to see the patch landed as we use it at Fedora.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541951
Title:
Firefox 3.6 does not honour lockPref
To manage notifications about this b
This bug seems to be stalled
Is there anything I may do to help get it advanced?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541951
Title:
Firefox 3.6 does not honour lockPref
To manage notifica
Created attachment 8956310
Bug 440908 - Add support for `sticky` and `locked` attributes to default prefs.
Sticky prefs are already specifiable with `sticky_pref`, but this is a more
general attribute mechanism. The ability to specify a locked pref in the data
file is new.
The patch also adds nsI
(In reply to Mike Kaply [:mkaply] from comment #30)
> It's not the same syntax, that's my point.
I tend to agree here. I think this could be a useful patch (I'd use it
instead of doing autoconfig stuff) but it's kind of silly to be hung up
on naming...
I do think that "lockPref" sticks out relat
https://hg.mozilla.org/mozilla-central/rev/edb57fbc6bea
https://hg.mozilla.org/mozilla-central/rev/b82802657783
https://hg.mozilla.org/mozilla-central/rev/d1d9ef8f7c0e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
The preferences code is being heavily refactored, and this needs to wait
a bit for things to settle first. That being said, I do think the ideal
timing for this would be to get it into 60. Nick, what do you think?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@glandium
I see Comment #46 speaks of a FF 60 ESR release; but effort expended to
a continuation '.js' amendments to configurations appears to conflict
with the the '.json' configuration management direction outlined for 60
as well, at:
> https://wiki.mozilla.org/Firefox/EnterprisePolicies
Polic
https://hg.mozilla.org/integration/mozilla-inbound/rev/edb57fbc6beac233b12486fa7d7381220339de0f
Bug 440908 - Remove gIsAnyPrefLocked. r=glandium
https://hg.mozilla.org/integration/mozilla-inbound/rev/b82802657783b6188e320ba966183ae1eedabf62
Bug 440908 - Add support for `sticky` and `locked` attrib
> Looking forward to see the patch landed as we use it at Fedora.
For what purpose? user.js shouldn't be used for anything mission
critical at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541951
> clang-format changed its mind, I guess?
No, chutten changed that code in bug 1435753. I generally run `./mach
clang-format -p modules/libpref`. Perhaps I should just run `./mach
clang-format` instead...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Comment on attachment 8931547
Bug 440908 - Allow preference files to set locked prefs.
https://reviewboard.mozilla.org/r/202672/#review208008
As per our IRC discussion, I think this is a good feature, and the patch
does a good job of implementing it. But before doing this I'd like to
officially s
Created attachment 8956311
Bug 440908 - Convert sticky prefs in default pref files to the new syntax.
Review commit: https://reviewboard.mozilla.org/r/225186/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/225186/
--
You received this bug notification because you are a me
Hp is a complete Linux enemy
Hp Computer:
[serdar@archlinux Desktop]$ uname -a
Linux archlinux 5.1.12-arch1-1-ARCH #1 SMP PREEMPT Wed Jun 19 09:16:00 UTC 2019
x86_64 GNU/Linux
[serdar@archlinux Desktop]$ dmesg | grep Error
[1.813390] RAS: Correctable Errors collector initialized.
[4.818
(In reply to Mike Kaply [:mkaply] from comment #28)
> I really don't want it being called lockPref. That will confuse it with the
> autoconfig "lockPref" function.
What is confusing? It's the same syntax. The only difference aiui, is
the execution environment, which means autoconf can do more java
Created attachment 8613433
Allow .js preference files to set locked prefs with lockPref()
Refreshed after bug 1098343. Benjamin, would you like to review this,
this time, considering comment 26?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
To expound on what :glandium said:
Extensions can lock preferences with:
Components.classes["@mozilla.org/preferences-service;1"]
.getService(Components.interfaces.nsIPrefService)
.getBranch(null)
.lockPref("name_of_pref");
Locking a preference doesn't affec
(In reply to Mike Hommey (VAC: 31 Dec - 11 Jan) [:glandium] from comment #40)
> (In reply to Mike Kaply [:mkaply] from comment #39)
> > Oddly, this document:
> >
> > https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/
> > A_brief_guide_to_Mozilla_preferences
> >
> > Says we already supp
Created attachment 8931547
Bug 440908 - Allow preference files to set locked prefs.
Review commit: https://reviewboard.mozilla.org/r/202672/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/202672/
--
You received this bug notification because you are a member of Ubuntu
Bug
user.js was never intended to be an enterprise level feature for
configuration of Firefox. I don't recommend using it for that.
For enterprise configuration, we have provided Autoconfig since day one,
and we are working on a better solution involving JSON, GPO and possibly
authors.
Our goal is to
(In reply to Mike Hommey [:glandium] from comment #46)
> The preferences code is being heavily refactored, and this needs to wait a
> bit for things to settle first. That being said, I do think the ideal timing
> for this would be to get it into 60. Nick, what do you think?
If things go well with
I was only referring to the use of user.js for enterprise. I do
understand that it's worthwhile to have locking of prefs in JS file for
Firefox purposes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/5
The ability to lock prefs at the .js level is not *only* for enterprise
customization. Specifically, we have many "prefs" that are meant to
allow e.g. per channel (release, beta, nightly) tweaks but are not meant
for users to change. There are multiple such footguns that would be
avoided by having
Created attachment 8956309
Bug 440908 - Remove gIsAnyPrefLocked.
It optimizes Preferences::IsLocked(), but that function is called fewer than
200 times while starting the browser and opening a range of tabs.
Review commit: https://reviewboard.mozilla.org/r/225182/diff/#index_header
See other revi
(In reply to Benjamin Smedberg [:bsmedberg] from comment #36)
> Comment on attachment 8613433
> Allow .js preference files to set locked prefs with lockPref()
>
> Because this came up on the mailing list, I'll try to be explicit about the
> decision here. I don't think we should allow extensions
Comment on attachment 8956310
Bug 440908 - Add support for `sticky` and `locked` attributes to default prefs.
https://reviewboard.mozilla.org/r/225184/#review231212
::: modules/libpref/Preferences.cpp:3982
(Diff revision 1)
> -Preferences::GetCString(kChannelPref, updateChannelPrefValue,
> -
Comment on attachment 8956309
Bug 440908 - Remove gIsAnyPrefLocked.
https://reviewboard.mozilla.org/r/225182/#review231210
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541951
Title:
Firefox 3.6 do
Comment on attachment 8956311
Bug 440908 - Convert sticky prefs in default pref files to the new syntax.
https://reviewboard.mozilla.org/r/225186/#review231216
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
it crashes while installing, ubuntu 19.04 near the end of completion
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubunt
Public bug reported:
it crashes while installing, ubuntu 19.04 near the end of completion
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubunt
Hi,
Want to share an update. The following kernels are available. It is
becoming impractical to manually load the earliest version while booting
everytime.
Please guide as to how to proceed.
On Fri, Jun 28, 2019, 9:26 PM Sumneet Kaur Bamrah
wrote:
> Hi,
> Tried loading/booting. Keep getting the
101 - 200 of 821 matches
Mail list logo
