Public bug reported:
The 'fwupd' package in Ubuntu is responsible for retrieving firmware
updates from the Linux Vendor Firmware Service [1] and applying them to
Ubuntu client hosts. The fwupd package version that is shipped with
Ubuntu 20.04 and 22.04 [2] is currently End of Life, though, and is
Public bug reported:
It seems an intel video driver update is needed to get Ubuntu 20.04.6
working on the Lenovo X1 Carbon Gen 11. On boot, only a blank screen
appears with a blinking cursor. Here are some details:
# lsb_release -rd
Description:Ubuntu 20.04.6 LTS
Release:20.04
# apt
Public bug reported:
It seems an intel video driver update is needed to get Ubuntu 20.04.6
working on the Lenovo X1 Carbon Gen 11. On boot, only a blank screen
appears with a blinking cursor. Here are some details:
# lsb_release -rd
Description:Ubuntu 20.04.6 LTS
Release:20.04
# apt
Public bug reported:
It seems an intel video driver update is needed to get Ubuntu 20.04.6
working on the Lenovo X1 Carbon Gen 11. On boot, only a blank screen
appears with a blinking cursor. Here are some details:
# lsb_release -rd
Description:Ubuntu 20.04.6 LTS
Release:20.04
# apt
tor will have to be inserted between the
> mic input and the soundcard AF input. A capacitor of 1 to 5 uF should
> do fine.
>
> If this does not answer your question, the respond with more text
> instead of us trying to guess from just a subject li
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net
This list hosted by: http://www.qsl.net
Please help support this email list: ht
'm interested, I should be available.
>
> Mike
>
>
> On Wed, Feb 16, 2022 at 1:58 PM Jim Campbell via gnome-doc-list <
> gnome-doc-list@gnome.org> wrote:
>
>> Hi All,
>>
>> I discussed working on docs with Shaun during the Docs Office Hours
>>
Hi All,
I discussed working on docs with Shaun during the Docs Office Hours
yesterday. We penciled-in a remote docs hackfest for the weekend of 2/25 -
2/27. Would folks be interested and available during that time?
Regards,
Jim
___
gnome-doc-list maili
Is this bug closed? When installing via 20.04.1 live server ISO, I see a
message that says:
initramfs unpacking failed: Decoding failed
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Communicating to TPM chip
ima: Error Com
The time of which I speak was in the mid-1950s. As I vaguely remember
there was study material that prepared you to be a knowledgeable ham.
There was also a big book that prepared you technically to be a radio
station engineer. At a later time there was a one-day cram course to
prepare you for
While in college, I co-oped with the FCC in Atlanta, GA. I had to take
and pass my Radiotelephone First and General class licenses before I was
allowed to administer those exams. If you did not pass a test you had to
wait 30 days before you could take it again. Some applicants tried to
game the
Noticed a 404 in one of the linked URLS ... should point to:
https://gnome.org/challenge/faq - not 'faqs' : /
Best of luck with the initiative!! <3
Jim
On Thu, Apr 9, 2020 at 1:19 PM Community Education Challenge <
cechalle...@gnome.org> wrote:
> Hi Everyone,
>
> We are incredibly excited to
I can't speak for our bretheren in the Rockies, but most of the people
in my part of the Appalachians live in the valleys with mountains around
us. I don't live there now but I did grow up there. Utilities,
especially water, are very expensive on mountaintops and icy roads in
the Winter are det
In trying to recreate the issue this afternoon, it looks as though
installs based on all of the updated / most recent packages are
succeeding again (i.e., this may no longer be an issue).
In our dpkg logs, we noticed that an update came through today for libc-
bin (2.27-3ubuntu1), and wonder if th
In trying to recreate the issue this afternoon, it looks as though
installs based on all of the updated / most recent packages are
succeeding again (i.e., this may no longer be an issue).
In our dpkg logs, we noticed that an update came through today for libc-
bin (2.27-3ubuntu1), and wonder if th
We are doing additional testing here. Please sit tight / do not research
further until we check into things further on our end.
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
We are doing additional testing here. Please sit tight / do not research
further until we check into things further on our end.
Thanks again for your help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu
Before I continue - I want to say thanks for your response to this
report. I appreciate your effort and help.
As for the issue, when I say, "If I only install the latest packages" I
mean a fully up-to-date system at the time of install, including sssd
version 1.16.1-1ubuntu1.4. As part of my testi
Before I continue - I want to say thanks for your response to this
report. I appreciate your effort and help.
As for the issue, when I say, "If I only install the latest packages" I
mean a fully up-to-date system at the time of install, including sssd
version 1.16.1-1ubuntu1.4. As part of my testi
... I tried this following Leonidas' (leosilvab) request to "Could you
downgrade to the previous version and check if it happens there too? And
so re upgrade and re-test?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
... I tried this following Leonidas' (leosilvab) request to "Could you
downgrade to the previous version and check if it happens there too? And
so re upgrade and re-test?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-
If I only install the latest packages (without the earlier versions of
these packages being installed previously) (i.e., if I do a clean
install of the most current packages when deploying a new host), it does
not work.
If I downgrade the packages to the prior versions, and then upgrade the
packag
If I only install the latest packages (without the earlier versions of
these packages being installed previously) (i.e., if I do a clean
install of the most current packages when deploying a new host), it does
not work.
If I downgrade the packages to the prior versions, and then upgrade the
packag
After allowing the packages to be upgraded to their newer versions, the
problem does _not_ persist. We see expected / desired results.
We only get a good outcome after the packages have been upgraded,
though. When the packages are installed as the initial versions ... that
is when we consistently
After allowing the packages to be upgraded to their newer versions, the
problem does _not_ persist. We see expected / desired results.
We only get a good outcome after the packages have been upgraded,
though. When the packages are installed as the initial versions ... that
is when we consistently
I will try updating the packages to their current-released versions and
see if the problem persists. We ran into this issue across several 18.04
deployments yesterday, though. It prevented commands like `id -u
username` from working (at least that is how we initially noticed a
problem).
I'll rever
I will try updating the packages to their current-released versions and
see if the problem persists. We ran into this issue across several 18.04
deployments yesterday, though. It prevented commands like `id -u
username` from working (at least that is how we initially noticed a
problem).
I'll rever
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The
package itself is from the standard Ubuntu repos.
$ dpkg -s sssd
Package: sssd
Status: install ok installed
Priority: extra
Section: metapackages
Installed-Size: 32
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch: fo
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The
package itself is from the standard Ubuntu repos.
$ dpkg -s sssd
Package: sssd
Status: install ok installed
Priority: extra
Section: metapackages
Installed-Size: 32
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch: fo
When downgrading to the prior package, we do not see this problem.
We've taken the following steps as a work-around:
- apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1
- apt-get -y --allow-downgrades install
libsasl2-modules-db=2.1.26.dfsg1-14build1
- apt-get -y --allow-down
When downgrading to the prior package, we do not see this problem.
We've taken the following steps as a work-around:
- apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1
- apt-get -y --allow-downgrades install
libsasl2-modules-db=2.1.26.dfsg1-14build1
- apt-get -y --allow-down
Public bug reported:
We are seeing the following in the journal after upgrading to these sets
of packages:
libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1
amd64
libsasl2-modules/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
libsasl2-modul
Public bug reported:
We are seeing the following in the journal after upgrading to these sets
of packages:
libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1
amd64
libsasl2-modules/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
libsasl2-modul
tions that their positions weren't getting.
We were providing real-time communications because communications was
our only job. Many others had their primary job and communications was
something that they did when they had a spare minute.
Jim Campbell - W4BQP
K2/100 #2268
Former Spartanb
I have a K2/100 and an 88 ft low antenna fed with ladder-line. I run
FT-8 at 12 watts. I use 40, 30 and occasionally 20M. While I haven't
been on in a few months, earlier this year I was regularly working into
NA, SA, Europe and occasionally Africa.
72, 73,
Jim - W4BQP
On 9/27/2019 11:38 AM,
ne of work, for the Navy, using an R-390,
but I don't think we had Rhombics. This was in the mid-60's
Lots of us in ham radio.
73 de Dick, K6KR
-Original Message-
From: elecraft-boun...@mailman.qth.net On
Behalf Of Jim Campbell
Sent: Friday, September 13, 2019 17:21
To: elec
In the late '50s I was stationed at a field station in Northern Germany
that was monitoring transmissions from the 'other side'. We were at a
former WWII German airfield and had an antenna farm comprised of
rhombics. I never bothered to count how many there were but I estimate
that there were m
For reference, I also see this same issue with Firefox set as my default
browser, and I am using the snap version of Slack.
--
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/1766230
Ti
For reference, I also see this same issue with Firefox set as my default
browser, and I am using the snap version of Slack.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230
Seeing this behavior, as well. Others reference vscode (in the comment
above), so I am curious to know if this is related to electron, or if
this is a snap-specific issue.
I do see reference to it as a snap-specific issue here:
https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and-
c
Seeing this behavior, as well. Others reference vscode (in the comment
above), so I am curious to know if this is related to electron, or if
this is a snap-specific issue.
I do see reference to it as a snap-specific issue here:
https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and-
c
For reference, I also see this same issue with Firefox set as my default
browser, and I am using the snap version of Slack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766230
Title:
Strange windo
Seeing this behavior, as well. Others reference vscode (in the comment
above), so I am curious to know if this is related to electron, or if
this is a snap-specific issue.
I do see reference to it as a snap-specific issue here:
https://forum.snapcraft.io/t/slack-opening-file-browser-firefox-and-
c
I know that Mozilla has moved (at least many of) their mailing lists to
Discourse, and that you can reply to Discourse threads via email (i.e., you
don't need to use a web browser to participate in discussions). There's
even the ability to import GNU Mailman messages and threads into Discourse.
Be
FWIW, we have the patch for Trusty, and I can test it, but I know that
Trusty will reach EOL in less than four months. I will leave it at your
discretion as to whether to go forward with the update for Trusty.
Also, I thanked Brian for getting the Xenial update into Proposed, but
forgot to thank S
FWIW, we have the patch for Trusty, and I can test it, but I know that
Trusty will reach EOL in less than four months. I will leave it at your
discretion as to whether to go forward with the update for Trusty.
Also, I thanked Brian for getting the Xenial update into Proposed, but
forgot to thank S
$ apt-cache policy geoclue-ubuntu-geoip
geoclue-ubuntu-geoip:
Installed: 1.0.2+14.04.20131125-0ubuntu2.16.04.1
Candidate: 1.0.2+14.04.20131125-0ubuntu2.16.04.1
Test #1 - Passed - URL includes https on first check
$ gsettings get com.ubuntu.geoip geoip-url
'https://geoip.ubuntu.com/lookup'
Tes
$ apt-cache policy geoclue-ubuntu-geoip
geoclue-ubuntu-geoip:
Installed: 1.0.2+14.04.20131125-0ubuntu2.16.04.1
Candidate: 1.0.2+14.04.20131125-0ubuntu2.16.04.1
Test #1 - Passed - URL includes https on first check
$ gsettings get com.ubuntu.geoip geoip-url
'https://geoip.ubuntu.com/lookup'
Tes
Hi All - I can test this on Xenial tomorrow (Jan 23). I'll report back
after testing.
Thanks to Brian for getting the package into xenial-proposed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-geoip in Ubuntu.
https://bugs.laun
Hi All - I can test this on Xenial tomorrow (Jan 23). I'll report back
after testing.
Thanks to Brian for getting the package into xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/161753
ubuntu-geoip (1.0.2+14.04.20131125-0ubuntu2.16.04.1) xenial; urgency=medium
[ Jim Campbell ]
* Use https for geoip.ubuntu.com/lookup URL (LP: #1617535)
Date: Fri, 16 Mar 2018 19:26:42 +
Changed-By: Jim Campbell
Maintainer: Ubuntu Desktop Team
Signed-By: Brian Murray
https
I'm still on 18.04, but this problem remains for me, as well.
Grub with noresume doesn't work
RESUME=none doesn't work
RESUME=/dev/mapper/ubuntu-root doesn't work
RESUME=/dev/mapper/ubuntu-swap doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'm still on 18.04, but this problem remains for me, as well.
Grub with noresume doesn't work
RESUME=none doesn't work
RESUME=/dev/mapper/ubuntu-root doesn't work
RESUME=/dev/mapper/ubuntu-swap doesn't work
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bi
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
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/17653
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.ne
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765304
Title:
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bio
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bi
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bi
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bio
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Bio
I've shared an item with you:
Best Practice Guidelines for Tooling and i2b2 Metadata Development
https://docs.google.com/document/d/1RHgvlkPDUQx0UZbtL8HdE6JHFVnRBWDNAWNCrt_ENSM/edit?usp=sharing&invite=CK-sqNsM&ts=5babb7f7
It's not an attachment -- it's stored online. To open this item, just clic
as Haller wrote:
> On Fri, 2018-06-29 at 15:48 -0500, Jim Campbell wrote:
> > Hi All,
> >
> > I was looking through the options regarding MAC Address
> > randomization, and have a question about them. A member of my team
> > wanted to know if it would be possible to
Hi All,
I was looking through the options regarding MAC Address randomization, and have
a question about them. A member of my team wanted to know if it would be
possible to do a sort of combo between the "stable" and the "random" options.
As a refresher, here is my understanding of these two p
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778554
Title:
Please update SSSD to version 1.16.2
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
SSSD 1.16.2 was released on June 6th:
https://lists.fedorahosted.org/archives/list/sssd-
us...@lists.fedorahosted.org/thread/HFL7756NZEMOLTPE3KY3IPNFDGVDN3LE/
Requesting an update to the SSSD package for Ubuntu 18.04.
It does appear as though there are some feature improveme
n and evolution-ews. Everything now works as expected /
Evolution remains awesome and the developer(s) should get donuts.
Thank you for your work on this,
Jim
On Tue, May 22, 2018, at 11:26 AM, Jim Campbell wrote:
> Hi All,
>
> I'm using Evolution 3.28.1-2 with Evolution-EWS
Hi All,
I'm using Evolution 3.28.1-2 with Evolution-EWS 3.28.1-1 on Ubuntu 18.04, and
I'm unable to set an 'Organizer' when attempting to create a new meeting
invitation.
I can add attendees (it integrates neatly with GOA Exchange plugin to pick up
entries from my address book, thanks!), but b
Might anyone be able to clarify what kinds of additional test cases (if
any) are needed? If so, I would appreciate it. I'm making an attempt to
be helpful in fixing this bug, but am a bit new to Canonical's internal
processes in terms of what they expect to test / resolve these kinds of
bugs. Any a
Might anyone be able to clarify what kinds of additional test cases (if
any) are needed? If so, I would appreciate it. I'm making an attempt to
be helpful in fixing this bug, but am a bit new to Canonical's internal
processes in terms of what they expect to test / resolve these kinds of
bugs. Any a
Hi All,
I think it is the case that all cockpit extensions need to be written in
Javascript. Is that the case, or can they be written in other languages, as
well (as long as they only use the Cockpit APIs)?
Thanks,
Jim
___
cockpit-devel mailing list
i don't think disabling the "guest session" session is part of the
issue, as we have that disabled and are still experiencing the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1733557
Title:
Adding test case here:
1) Install patches / patched package
2) Confirm that the 'geoip url' is set to a correct 'https' value, and that
this value is set as the default:
`$ gsettings get com.ubuntu.geoip geoip-url` should display
`https://geoip.ubuntu.com/lookup`
`$ gsettings reset com.ubu
Adding test case here:
1) Install patches / patched package
2) Confirm that the 'geoip url' is set to a correct 'https' value, and that
this value is set as the default:
`$ gsettings get com.ubuntu.geoip geoip-url` should display
`https://geoip.ubuntu.com/lookup`
`$ gsettings reset com.ubu
Thank you Timo, Andreas and Simon. This is a big help to us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754746
Title:
Please update to 1.16.1 for bionic
To manage notifications about this bug g
Users at my workplace who experienced this issue are reporting that
updating all packages and restarting / rebooting has resolved the issue
for them, even after repeated screen locks and login-logouts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I'm not certain that this is due to multiple user accounts.
This bug has appeared on a coworker's system which has only one user
account. His session locked due to meeting the regular idle timeout
threshold, and he saw this greeter message when going to log back in.
--
You received this bug noti
Include associated patch to fix this for Trusty. Please update package
after associated packages for Artful and Xenial.
** Patch added: "One-line fix and associated changelog - Trusty"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081722/+files/ubuntu_geoip_
Include patch to set https geoip url for Xenial. Package should be
updated after the related Artful package, but before the associated
Trusty package.
** Patch added: "One-line fix and associated changelog - Xenial"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachmen
Include associated patch to fix this for Trusty. Please update package
after associated packages for Artful and Xenial.
** Patch added: "One-line fix and associated changelog - Trusty"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081722/+files/ubuntu_geoip_
Include associated patch for Artful. This package should be updated
before packages for Trusty and Xenial, although I'm attaching all three
patches at more or less the same time.
** Patch added: "One-line fix and associated changelog"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug
Include patch to set https geoip url for Xenial. Package should be
updated after the related Artful package, but before the associated
Trusty package.
** Patch added: "One-line fix and associated changelog - Xenial"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachmen
Include associated patch for Artful. This package should be updated
before packages for Trusty and Xenial, although I'm attaching all three
patches at more or less the same time.
** Patch added: "One-line fix and associated changelog"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug
Gentle bump. Might someone be able to assist / identify what I'm missing here?
Thanks very much,
Jim
On Tue, Mar 6, 2018, at 1:47 PM, Jim Campbell wrote:
> Hi All,
>
> I seem to be having trouble with correctly partitioning a hard drive
> using a PXE boot + preseed file , an
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754746
Title:
Please update to 1.16.1 for bionic
To manage notifications about this bug go to:
https://bugs.la
Public bug reported:
SSSD 1.16.1 was tagged for release:
https://pagure.io/SSSD/sssd/releases
https://github.com/SSSD/sssd/releases/tag/sssd-1_16_1
. . . I'm hopeful that, although we're past the Debian sync freeze, that
it will be possible to get this point release into Ubuntu before the
final
Hi All,
I seem to be having trouble with correctly partitioning a hard drive using a
PXE boot + preseed file , and am seeking help.
What works:
I can use an expert_recipe string as part of a preseed.cfg file contained in a
custom ISO (booted via grub-imageboot), and it correctly partitions a dr
It appears as though the servers may have been updated to also serve
this over https (previously, https didn't work at the Ubuntu geoip url),
but the default value for desktops is to use the http value, and the
defaults should be updated
Current values:
$ gsettings reset com.ubuntu.geoip geoip-url
It appears as though the servers may have been updated to also serve
this over https (previously, https didn't work at the Ubuntu geoip url),
but the default value for desktops is to use the http value, and the
defaults should be updated
Current values:
$ gsettings reset com.ubuntu.geoip geoip-url
I'm looking forward to some fixes that will arrive in SSSD 1.16.1, and
am hopeful that it will be released in time to be included in Bionic.
1) I know that the Debian sync deadline for 18.04 is March 1st. If
1.16.1 is released prior to that, is it likely that 1.16.1 could be
included in the initia
Hi Petr,
Thanks I would be in favor of this transition.
Jim
On Jan 11, 2018 12:51 PM, "Petr Kovar" wrote:
> Hi all,
>
> More and more GNOME projects seem to be migrating from old git
> infrastructure and Bugzilla to https://gitlab.gnome.org/.
>
> Would there be any objections to moving our doc
Hi Petr,
Thanks I would be in favor of this transition.
Jim
On Jan 11, 2018 12:51 PM, "Petr Kovar" wrote:
> Hi all,
>
> More and more GNOME projects seem to be migrating from old git
> infrastructure and Bugzilla to https://gitlab.gnome.org/.
>
> Would there be any objections to moving our doc
Hi Hannie,
Thanks for giving this a look, and for being so detail-oriented.
While Ubuntu 16.04 is an LTS release for Ubuntu, it's a rather old version
to be troubleshooting against for docs. Could you see if you have the same
question on Ubuntu 17.10?
Not seeing the curtain also makes me wonder
Hello,
It sounds as though the policy engine will also work with the Rapid Release
version of Firefox (starting with version 60), and not only the Extended
Support Release. Can you confirm?
Kind regards,
Jim
From: Enterprise on behalf of Sylvestre Ledru
Hi Hannie,
If you're working on a file that will be part of (for example) gedit, and
you've cloned the gedit repository, the documentation would be in
gedit/help/C. You'd place your new "page" file in the gedit/help/C
directory, and then do "yelp gedit/help/C" and it will launch all of the
gedit
Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1542782
Titl
Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542782
Title:
unity-scope-loader crash
Same issue here on Ubuntu 16.04 as descried.
Nvidia Driver 384.90-0ubuntu0.16
4.4.0-98-generic
system up to date
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net
I'm still seeing this on 16.04.3. The 'expert_recipe' partitioning string is
being skipped / ignored. i.e., anything that looks like this:
---
preseed partman-auto/expert_recipe string \
boot-root :: \
500 500 500 ext4\
$primary{ }
1 - 100 of 3175 matches
Mail list logo
