I've tried that as well but that does not work either unfortunately. The
system freezes pretty much directly after the purple screen appears.
Hitting Ctrl+Alt+F4 does not do anything at that moment.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug not
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”). The API is completely different and this is expected. See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug d
Can you please try booting without the graphical splash? That way we
might be able to see what's failing...
Try editing /etc/default/grub and change "splash" to "nosplash", then
'sudo update-initramfs' and reboot. You might then see errors on the
next reboot and can take a photo of them.
--
You
apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped. A corresponding Depends was already dropped in
https://bugs.debian.org/757140.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https:/
Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7
apr-util: filed a Debian bug.
** Changed in: wget (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in
• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug:
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing:
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support
** Bug watch added: bugs
• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support,
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
** Changed in: nmap (Ubuntu)
reported upstream: https://savannah.gnu.org/bugs/index.php?54677
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in favor of pcre2
To manage notifi
Hi Alberto,
is there a way to test if this works? Should I use the ppa 8they do not
seems to be up to date(?)
thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
S
• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
** Changed in: rasqal (Ubuntu)
Status: New => Incomplete
** Changed in: slang2 (Ubuntu)
Status: New => Incomplete
--
You received this
Actually, sssd build would still pull libpcre3-dev because of some
dependency, and then use that... and upstream config phase doesn't
support pcre2. I've filed a bug upstream.
** Changed in: sssd (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a
Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.
** Changed i
sssd: https://pagure.io/SSSD/sssd/issue/3833
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in favor of pcre2
To manage notifications about this b
Hi,
Andreas Hasenack wrote:
> I've seen the wget debian change, but just switching builddeps from pcre3-dev
> to pcre2-dev and rebuilding isn't enough. The package ends up not finding
> pcre and doesn't enable it:
> checking for PCRE... no
> checking pcre.h usability... no
> checking pcre.h pres
Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720
** Bug watch added: trac.nginx.org/nginx/ #720
http://trac.nginx.org/nginx/ticket/720
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a mem
https://www.applemacsupportnumbers.com/apple-customer-support/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1153488
Title:
Treats bluetooth input device batteries as
** Changed in: libselinux (Ubuntu)
Status: New => Triaged
** Changed in: haproxy (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Nice find, I looked in trac but must have missed that...
Sent from my Sprint Samsung Galaxy S9+.
Original message From: Anders Kaseorg Date:
9/18/18 06:22 (GMT-05:00) To: tew...@thomas-ward.net Subject: [Bug 1792544]
Re: demotion of pcre3 in favor of pcre2
Likewise, nginx d
@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login passwo
glib is filed upstream as
https://gitlab.gnome.org/GNOME/glib/issues/1085
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion of pcre3 in favor of pcre2
To mana
Lol, 'this is not a bug'. The installer clearly guesses wrong, only 1%
in Brussels speaks German. I want my installation in English but with
the Belgian locale.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ub
This bug was fixed in the package apr-util - 1.6.1-2ubuntu1
---
apr-util (1.6.1-2ubuntu1) cosmic; urgency=medium
* Drop build dependency on libpcre3-dev. Closes: #909077. LP:
#1792544.
-- Matthias Klose Tue, 18 Sep 2018 13:05:27 +0200
** Changed in: apr-util (Ubuntu)
Sta
Alan would be using 18.04 (bug 1792924).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is shown in plain text on the VT1 console
To manage not
Robert, could you have a look to this one?
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.laun
@gunnarhj, "guessing" a locale should not use a locale used only by a very
small percentage of people in Belgium.
>From the format I'm going to assume it's picking the first locale it can find?
In that case I would actually suggest to remote de_BE from the default locale
listing as it's a very ni
Public bug reported:
Ubuntu 18.04.1 - Communitheme installed
If I have to format a Volume (in my case an external usb 750GB hard
drive with secure erasing flag on) I have no feedback about the process,
the window simply disappear.
Good to have some progressing feedback since could be a long proc
That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.
For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':
要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
| 状態=(N)無/
(For anyone following this bug, the second merge request for the
ubuntu-3-30 branch landed, so this just needs the ubuntu-3-30 code to be
pushed into the cosmic).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu
Problem with context menu
** Attachment added: "20180918_172409.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1793167/+attachment/5190212/+files/20180918_172409.jpg
** Description changed:
I'm using two displays vertically. One large (3840x2160) and one small (1920
x1080
Here the correct context menu behavior when screens have their left
edges aligned
** Attachment added: "Screenshot from 2018-09-18 17-30-30.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1793167/+attachment/5190214/+files/Screenshot%20from%202018-09-18%2017-30-30.png
--
You
Public bug reported:
I'm using two displays vertically. One large (3840x2160) and one small (1920
x1080
If I put the 2 displays horizontally or vertically with left edge aligned
everything is correct.
If I put the large display above the small one without left edges aligned, I
have got the foll
Here the correct behavior with eclipse JDialog when screens have their
left edges aligned
** Attachment added: "Screenshot from 2018-09-18 17-30-30.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1793167/+attachment/5190213/+files/Screenshot%20from%202018-09-18%2017-30-30.png
NGINX has technically said this is won't fix:
>From a response to my inquiry: http://mailman.nginx.org/pipermail/nginx-
devel/2018-September/011448.html
--
Hello!
On Tue, Sep 18, 2018 at 08:12:20AM -0400, Thomas Ward wrote:
> Downstream in Ubuntu, it has been proposed to demote pcre3 and
Agreeing. Always using type-ahead in any OS, any application really.
Having it become 10x as slow (even when never allow recursive search) is
a show stopper.
It's literally the difference between having the UI responsive, and the
content /already there/ being navigatable and waiting 5 seconds fo
@OliWare: You get a Belgian locale, just not the one you want.
@Jonas: I assume the same. We can't remove a locale for this reason; we
have the locales provided by glibc.
But I suppose that the installer (ubiquity/localechooser) could be
tweaked to 'guess better'. That would require some hard cod
** Package changed: gnome-panel (Ubuntu) => gnome-shell (Ubuntu)
--
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/1793167
Title:
Dual screen: context menu and dialog truncated
T
installed 18.10 development branch which contained mutter v3.30 and yes
it fixed the issue
the login screen now appears even when choosing gdm3 as the default
desktop manager
sudo dpkg-reconfigure gdm3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
1) why not let the user choose ? When a country has multiple languages,
just show the list.
2) what if a Belgian user like me wants Belgium-English ? That's just
impossible to obtain... For once, Windows does it better with this regard.
Le mar. 18 sept. 2018 à 18:55, Gunnar Hjalmarsson <
1295...
I've done that now:
1. $ sudo vim /etc/default/grub
2. changed "splash" to "nosplash"
3. $ sudo update-initramfs -u
4. $ sudo update-grub
5. $ sudo reboot
Note:
* I've added the "-u" option to the update-initramfs as well (it tells me "You
must specify at least one of -c, -u, or -d", so I did "-
** Attachment added: "nosplash_2.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190305/+files/nosplash_2.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.
** Attachment added: "nosplash_3.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190314/+files/nosplash_3.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.
I noticed that I have installed (and could only find) the amd64 image. I
have a 64-bit Intel (https://ark.intel.com/products/52209/Intel-
Core-i5-2500-Processor-6M-Cache-up-to-3_70-GHz) processor. Would that
matter at all? (Maybe a dumb question, but throwing it out there anyway
;-))
--
You recei
1) I suppose that those responsible for the design of the installer want
to keep it simple.
But, as I explained in comment #27, you can choose afterwards.
2) That would be quite a different approach to locale handling. A huge
project.
--
You received this bug notification because you are a memb
Btw, Belgium-English is possible to obtain, sort of:
* Choose English as language
* Choose fr_BE.UTF-8 as region in the GUI
* Add this line to the ~/.profile file:
export LC_TIME=en_DK.UTF-8
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
https://askubuntu.com/questions/896971/problem-with-display-after-
suspending
It looks like a NVIDIA bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1792798
Title:
gdm3 will sta
It is fixed for me after I cleaned old package sources in Synaptic and
updated:
Commit Log for Tue Sep 18 22:36:57 2018
Following packages was removed:
gstreamer1.0-plugins-ugly-amr
xserver-xorg-input-vmmouse
Following packages was updated:
gstreamer1.0-plugins-good (1.8.3-1ubuntu0.4) to 1.14.1-
I am seeing this exact same problem. Performed a fresh install of 18.04
LTS and have remained updated the whole time. Still seeing problems with
gnome-shell filling the logs. This seems to happen when the user session
in gnome goes to the lock screen and you can see it go black
momentarily, then re
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs
*** This bug is a duplicate of bug 1161468 ***
https://bugs.launchpad.net/bugs/1161468
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1161468, so is being marked as such.
Can anybody please nominate this bug for bionic because it produces an
error when trying to upgrade from 18.04 to 18.10? See:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1790693
and
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1793164
--
Y
Renaming folders does not appear to resolve the issues. See bug 1793256
for potentially-related information.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1792668
Title:
gn
55 matches
Mail list logo
