Public bug reported:
Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
color profile switching. The commit at fault is
104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
when processing update” (which was intended to fix LP bug 1847044).
Upstream issue:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/185
Title:
gnome-session-binary crashed with SIGSEGV in
This is fixed by
https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested
850ef518795dcc20d3b9a4f661f70ff8d0ddacb2).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
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/1843107
Title:
Themes and font settings
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771
https://gitlab.gnome.org/GNOME/mutter/issues/771
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/771
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
By adding some debugging output to mutter and gnome-shell I verified
that mutter emits the x11-display-opened signal before gnome-shell is
able to connect a handler for it, and the handler never runs.
(Possibly things would be different in the experimental autostart-
xwayland mode, but the whole
Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem. Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t
Public bug reported:
After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
tweaks are no longer applied to X11 applications when running in a
Wayland session (I tried Firefox and Emacs). This seems to be because
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
I hope 3.32.1 will get into Disco, but in case this can’t happen and a
more minimal set of patches is required, these are the nine upstream
patches I added to my mutter package to get it to stop crashing on
wakeup:
fe86694dd renderer/native: Make EGLStream page flip errors non-fatal
1eabaf12d
** Information type changed from Private to Public
--
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/1820331
Title:
gnome-shell crashed with SIGABRT
Status in gnome-shell package
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with
1.12.4 is in cosmic-proposed now with the upstream fix.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: network-manager (Ubuntu)
Assignee: Anders Kaseorg (andersk) => (unassigned)
--
You received this bug notification becau
As long as you're working on this package would you mind including the
one-line upstream patch for bug 1788483, if you haven't already?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
That was a local build. I also saw it on Launchpad with an unrelated
patch (bug 1788483):
https://launchpadlibrarian.net/391298478/buildlog_ubuntu-
cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz
However, the failure seems to have disappeared with today’s updates of
other packages, or maybe
Public bug reported:
mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
A full build log is attached. The relevant part is these test failures.
==
clutter 1.26.1: tests/conform/test-suite.log
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Anders Kaseorg (andersk)
** Tags added: patch
(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)
** Patch added: "debdiff adding upstream patch, rebased"
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Patch added: "rebased on 1.12.2-0ubuntu5"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
Status in NetworkManager:
Unknown
Status in
** Bug watch added: GNOME Bug Tracker #797136
https://bugzilla.gnome.org/show_bug.cgi?id=797136
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=797136
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
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
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 Desktop
Packages, 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
• 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)
• 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
• 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:
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
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 Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
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
It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.
https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213
/* Contrary to what cURL manual claim
Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.
** Attachment added: "nm.19802.log"
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
Status
GNOME on Wayland works around the crash.
Based on the apport-retrace results, this is possibly a duplicate of bug
1788483.
--
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/1790992
Older versions in bionic than in xenial, as of now:
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29
** Summary changed:
- Older version in artful than in xenial
+ Older version in bionic
** Description changed:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 <
Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch
This happens all the time on my main Ubuntu installation and is not
specific to the live environment. I only demonstrated it in the live
environment for easy reproducibility, and to show it isn’t some crazy
misconfiguration of my specific installation.
** Changed in: firefox (Ubuntu)
Public bug reported:
Steps to reproduce:
1. kvm -cdrom ubuntu-17.10-desktop-amd64.iso -m 4096
2. Select “Try Ubuntu”.
3. Start Firefox.
4. Start Software Updater; uncheck everything except Firefox Web Browser;
select “Install Now”.
5. When update finishes, switch back to Firefox and go to
dino99: This is about the ubufox _source_ package, which is the source
for the xul-ext-ubufox binary package and is not transitional. The xul-
ext-ubufox binary package has the same problem.
$ rmadison xul-ext-ubufox
xul-ext-ubufox | 2.0.2-0ubuntu1 | precise | all
xul-ext-ubufox
Public bug reported:
$ rmadison -asource ubufox
ubufox | 2.0.2-0ubuntu1 | precise | source
ubufox | 2.8-0ubuntu1 | trusty | source
ubufox | 3.2-0ubuntu0.12.04.1 | precise-security | source
ubufox | 3.2-0ubuntu0.12.04.1 | precise-updates | source
ubufox |
This may have been fixed by mutter 3.26.1-2 (bug 1722510). At least I
can no longer reproduce it using the recipe in my duplicate bug 1722709.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in
this crash.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1721681
Title:
gnome-terminal-server crashed with SIGSEGV in
I’m not sure. Since it’s been a week without any sign of an upload to
artful-proposed, I’m changing this back to Confirmed.
I have a patched build of gnome-shell in my PPA if you need it now:
https://launchpad.net/~andersk/+archive/ubuntu/ppa/+packages
It seems to be the TopIcons Plus extension that triggers this so often.
I think that’s roughly consistent with the upstream bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
This might be triggered by a shell extension. I haven’t seen any
crashes after turning them all off. I’ll see if I can bisect which one
it is.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
This is happening to me very frequently (several times a day) on both
Wayland and Xorg. On Wayland, it brings down the entire session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Information type changed from Private to Public
--
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/1714745
Title:
gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
Public bug reported:
When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected. But if I then disconnect and connect to a different network,
it is not removed from resolv.conf. If the second network also sets a
Firefox 47 worked around this by disabling the dark theme entirely.
Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The
former gets you a
Firefox 47 worked around this by disabling the dark theme entirely.
Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The
former gets you a
Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076). The
former gets you a dark-themed UI without messing up web page content.
Official PPA for
I have the same problem on a ThinkPad Yoga 14 20FY. I can reproduce it
with the touchpad disabled as described in this report. However, I find
it much easier to reproduce (nearly 100% of the time) with the touchpad
enabled, as follows:
1. With my left finger, hold down the trackpoint’s left
Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647031
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=665073
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
The current location of 24.5+1-7ubuntu1 is zesty-proposed. I think it
has not migrated to zesty because it failed to build on ppc64el.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
Public bug reported:
Selecting previously unselected package liblirc-client0:amd64.
Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb
pauljohn: You installed the packages in the wrong order. Since a
24.5+1-7ubuntu1 package, identical to mine modulo debian/changelog, is
in yakkety-proposed for architectures other than arm64 and ppc64el, the
easiest solution is to enable yakkety-proposed and let apt install them
for you.
--
You
Adding -no-pie on arm64 doesn’t help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1623585
Title:
Toolbar is blank
Status in emacs24 package in Ubuntu:
Fix Committed
Status in
Rebuilding an unchanged 24.5+1-6ubuntu3 also fails on arm64 and ppc64el:
https://launchpadlibrarian.net/287872786/buildlog_ubuntu-yakkety-arm64.emacs24_24.5+1-6ubuntu3_BUILDING.txt.gz
https://launchpadlibrarian.net/287872619/buildlog_ubuntu-yakkety-ppc64el.emacs24_24.5+1-6ubuntu3_BUILDING.txt.gz
The arm64 problem, at least, looks like it could be
https://bugs.debian.org/837421. Ubuntu has already added -no-pie on
amd64 ppc64el s390x but not yet on arm64.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
** Tags added: patch-accepted-debian
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1623585
Title:
Toolbar is blank
Status in emacs24 package in Ubuntu:
Confirmed
Status in
** Tags added: regression-release
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1623585
Title:
Toolbar is blank
Status in emacs24 package in Ubuntu:
Confirmed
Status in emacs24
Confirmed that this fixes the toolbar with a test build in ppa:anders-
kaseorg/ppa. Subscribing sponsors.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1623585
Title:
Toolbar is
This is most straightforwardly solved by merging 24.5+1-7 from Debian,
which pulls in three fixes: one for for this bug, one for malloc
handling with GCC ≥ 5.2, and one for glibc 2.24 support. We certainly
want all three. Here is a debdiff from 24.5+1-6ubuntu3.
** Patch added:
** Bug watch added: Debian Bug tracker #828000
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828000
** Also affects: emacs24 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828000
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Also submitted upstream: https://github.com/hughsie/appstream-
glib/pull/129
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1591868
Title:
fwupd consuming 100% CPU
Status in
The infinite loop is not in libyaml (yaml_parser_parse), but rather in
its caller in appstream-glib (as_node_yaml_process_layer), which is
ignoring the error code returned by yaml_parser_parse and blindly going
around the loop again. This patch fixes it.
** Patch added:
Public bug reported:
When apport takes a core dump of a large application, it uses 100% CPU
for a _long_ time (often 30 seconds or more) to compress the core dump.
The system is virtually unusable during this time, especially if the
application was the window manager and won’t be restarted until
*** This bug is a duplicate of bug 1533458 ***
https://bugs.launchpad.net/bugs/1533458
Public bug reported:
package fonts-tlwg-kinnari-ttf (not installed) failed to
install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg
/Kinnari-Bold.ttf', which is also in package
Public bug reported:
Starting gnome-terminal results in a 79×23 window instead of the
standard 80×24, at least in Ubuntu Gnome with the default Adwaita theme
on a high-DPI laptop. This makes it irritating to use some applications
designed for an 80-column terminal.
According to an upstream bug
** Patch added: "vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1528728/+attachment/4539301/+files/vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff
** Tags added: patch
** Bug watch added: Debian Bug tracker #787104
Public bug reported:
The unicode-math LaTeX package no longer works at all in either of its
supported TeX engines (xelatex and lualatex). Downgrading texlive-math-
extra from 2015.20151116-1 to 2015.20150810-1 makes it work again.
$ cat test.tex
\documentclass{article}
\usepackage{unicode-math}
This can be fixed by merging texlive-base 2015.20151116-1 from Debian
unstable. Here’s a debdiff from 2015.20151116-1 porting the trivial
Ubuntu delta forward.
** Also affects: texlive-base (Ubuntu)
Importance: Undecided
Status: New
** Patch added:
** Bug watch added: Python Roundup #25493
http://bugs.python.org/issue25493
** Also affects: python via
http://bugs.python.org/issue25493
Importance: Unknown
Status: Unknown
** Bug watch added: GNOME Bug Tracker #757184
https://bugzilla.gnome.org/show_bug.cgi?id=757184
**
This is a combination of two problems. One is that starting update-
manager results in these warnings:
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1237904
Title:
Xorg crashed with SIGABRT in OsAbort()
This bug was marked Confirmed because it affected multiple users. It is
not a local issue, and in fact it’s still present in trusty, as you can
verify it for yourself by examining the contents of
http://archive.ubuntu.com/ubuntu/pool/main/libm/libmtp/libmtp-
Public bug reported:
$ cat foo.cc
#include string
std::string hello = Hello, world!\n;
$ cat bar.cc
#include string
#include iostream
extern std::string hello;
int main() {
std::cout hello;
return 0;
}
$ g++ -c foo.cc g++ foo.o bar.cc ./a.out
Hello, world!
$ clang++ -c foo.cc clang++
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1482439
Title:
wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()
Status
Public bug reported:
Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-aurora,
GNOME Shell fails to match running Firefox windows to the Firefox
launcher icon. This is because the Firefox windows report a WM_CLASS of
‘Firefox-dev’, which GNOME Shell by default tries to match against
Or, I guess, it could alternatively be fixed by renaming the Aurora
packages to firefox-dev with a firefox-dev.desktop. That might be closer
to upstream’s expectations: Aurora tries very hard to coexist with
stable Firefox rather than replace it. (It creates its own separate
Firefox profile
.xsession is sourced within /bin/sh, not /bin/bash. It wouldn’t make
sense to source .bashrc from it (unless you happened to write a .bashrc
that doesn’t use any bash features).
Also, .bashrc is sourced by _every_ interactive shell, so if you were to add
things to environment variables from
No, you misunderstand my comment. It doesn’t matter whether or not your
shell is bash. ~/.xsession file is sourced using /bin/sh, not using your
shell. You cannot expect to be able to source ~/.bashrc from
~/.xsession, no matter what your preferred shell is.
--
You received this bug notification
Aha, I was confusing ~/.xsessionrc with ~/.xsession. ~/.xsessionrc is
sourced using /bin/sh. A default Ubuntu session does not invoke
~/.xsession at all. Creating one that works correctly with Unity or
GNOME or whatever, as well as configuring LightDM to invoke it it,
requires a very pointy hat.
Every time I press one of these keys, I get the message
(gnome-settings-daemon:7822): GLib-GIO-WARNING **: Dropping signal
AcceleratorActivated of type (ua{sv}) since the type from the expected
interface is (uuu)
This is probably the same thing that happened in LP: #1217196 and LP:
#1376471.
--
Here’s a tested patch that reverts the relevant gnome-shell changes to
make it work with gnome-settings-daemon 3.14.x.
** Patch added: gnome-shell_3.16.2-1ubuntu1_lp1427877.debdiff
Specifically, this is caused because gnome-shell 3.16 has
https://git.gnome.org/browse/gnome-shell/commit/?id=2aa4fb02dd9c568038d12fe609252b6934367e76
but gnome-settings-daemon 3.14 does not have
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406189
Title:
evolution-addressbook-factory crashed with SIGABRT in
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406164
Title:
evolution-calendar-factory crashed with SIGABRT in
Chrome 40 now sets LIBGL_DRI3_DISABLE=1 automatically on desktop Linux
(https://code.google.com/p/chromium/issues/detail?id=415681).
** Bug watch added: code.google.com/p/chromium/issues #415681
http://code.google.com/p/chromium/issues/detail?id=415681
** Also affects: chromium-browser via
Public bug reported:
We should merge emacs24 24.4+1-4 from Debian unstable. Note that emacs24
-non-dfsg 24.4+1-2 has already been synced.
(I’m currently preparing this merge in my PPA; I’ll post a debdiff
shortly.)
** Affects: emacs24 (Ubuntu)
Importance: Undecided
Status: New
--
** Patch added: emacs24_24.4+1-4_4ubuntu1.debdiff
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1387323/+attachment/4248445/+files/emacs24_24.4%2B1-4_4ubuntu1.debdiff
** Description changed:
We should merge emacs24 24.4+1-4 from Debian unstable. Note that emacs24
-non-dfsg
Merge prepared at bug 1387323.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs23 in Ubuntu.
https://bugs.launchpad.net/bugs/493766
Title:
Multi_key / compose does not work when XMODIFIERS=@im=SCIM
Status in “emacs23” package in
The different appearance of 0017-Further-improve-create_frame_xic-
patch.patch is due to the slightly different diff algorithms used by Git
and Bazaar (http://bramcohen.livejournal.com/37690.html); the actual
code change is identical.
If you want to sponsor a merge instead, the one already
1 - 100 of 164 matches
Mail list logo
