Public bug reported:
When pressing ESC after going into a trace, I got this:
```
(gdb) bt
#0 0x77bf470b in del_panel () from /lib/x86_64-linux-gnu/libpanelw.so.6
#1 0x5556ab18 in ui_destroy (ui=0x555856a0 ) at
curses/ui_panel.c:64
#2 ui_default_handle_key (ui=ui@entry=0x55
Ahyes, that fixes things on Ubuntu/Jammy as well:
mkdir -p /etc/apparmor.d/disable
# (did not exist, over here)
ln -s /etc/apparmor.d/usr.bin.tcpdump /etc/apparmor.d/disable
# (note, no sbin, but bin)
apparmor_parser -R /etc/apparmor.d
# (this is indeed needed, instead of an apparmor restart)
-
Today it was experimental.refresh-app-awareness expiry time. It claimed
it had waited long enough and did the refresh anyway without consulting
me.
Immediately my fonts broke. And, as usual, the red dot in the Ubuntu
Dock (the "running applications indicator") next to the Chromium icon
disappeared
https://jira.mariadb.org/browse/MDEV-27937
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964622
Title:
MariaDB limits to 1000 parameters
To manage notifications about this bug go to:
https://bugs.
That is a likely culprit, as there are changes there after 10.3.32:
$ git tag --contains a65d01a4cf04c744f9355bec186430540ce6ba08 | grep 10.3 -F
mariadb-10.3.34
mariadb-10.3.33
commit a65d01a4cf04c744f9355bec186430540ce6ba08
Author: Dmitry Shulga
Date: Wed Oct 20 19:24:31 2021 +0700
Okay. That experimental.refresh-app-awareness did not fix it.
This morning (16 March), while switching tabs, the font "change"
occurred visibly again. Apparently I'm not looking at a fresh Chromium.
Yet still there is _something_ that messed up the fonts.
Here's some system info:
$ snap list --
I suspect OP suffers from this:
www.osso.nl/blog/chromium-snap-wrong-fonts
Clearing out the font cache `rm /var/snap/chromium/common/fontconfig/*`
and restarting chromium is the only thing that reliably works for me.
I think "Refresh App Awareness" might be a workable workaround, as
Chromium ten
This is nice and old :)
Here's a starting point, if others are still interested:
https://github.com/wdoekes/gtkradiant-deb/tree/v1.6.6-0wjd0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/3
Confirmed with 98.0.4758.54:
- the pasting of content in an unrelated X window is _fixed_;
- the sorting is _fixed_;
- the moving of Tabs is _fixed_.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Personally, I think it's a waste of space to setup timeshift just
because Ubuntu snapcraft cannot keep more than two versions alive... I
think there is something wrong in the snap ecosystem if we cannot choose
between more than two versions which are both broken.
My two cents.
--
You received th
See also https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956888/comments/10 for downgrading instructions and
possible upstream bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19568
I think the relevant bug report is:
https://bugs.chromium.org/p/chromium/issues/detail?id=1279532
It causes havoc with Tab moving, and broken sortable lists (like the
bookmarks), and with pasting stuff to the wrong (X11) window. (See my
previous comment.)
Downgrading to a previous version (1854)
Is this related to https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1956838/comments/4 perhaps?
That bug reared its head for me when I was using a drag-drop widget in a
website.
If it is, it is even uglier than you think.
> As a workaround, it's too bad we can't restore a bugfre
I'm really unhappy with this, because it appears to paste text into the
window below it:
https://junk.devs.nu/2022/bugs/chromium_98.0.4758.9_snap_pastes_in_gedit.mp4
"""This is a video with two gedit windows side by side, and this bug report on
top. When dragging and dropping text INSIDE the brow
Fix 0.103-0ubuntu5~20.04.3 appears to work on Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949104
Title:
netplan try is broken
To manage notifications about this bug go to:
https://bugs.la
Also affects Ubuntu/Focal:
# readlink /usr/share/doc/zfs-zed/changelog.Debian.gz
../libnvpair1linux/changelog.Debian.gz
# readlink /usr/share/doc/zfsutils-linux/changelog.Debian.gz
../libnvpair1linux/changelog.Debian.gz
# readlink /usr/share/doc/zfsutils-linux/../libnvpair1linux/changelog.Debia
Ok. I stand corrected.
I reinstall of libnvpair1linux _did_ fix it. (After removing zfs-doc.)
# apt-get install --reinstall libnvpair1linux
# ls -l /usr/share/doc/libnvpair1linux/
total 76
-rw-r--r-- 1 root root 1615 jul 12 16:36 changelog.Debian.gz
Move along.. nothing to see here.
--
You r
> ...so if a user has built against libxxhash for such
> a use case that is supported by upstream, your proposal
> for changing Focal would break them.
*shrug*
I'd rather have my build break now than succeed and get harder to debug
issues with failing cross device communication.
Well, I've done
** Description changed:
+ **NOTE: This ticket has been moved/altered. Original problem referred to
+ rsync behaviour with libxxhash0. New subject is the changed ABI of
+ libxxhash0.**
+
+ Original-Subject: rsync 3.2.x in Groovy depends on broken libxxhash
+ 0.7.x
+
+ Actual problem: libxxhash0 i
Thanks, Robie, for the excellent response.
> Actually I'm not sure it's a symbol versioning issue now.
Maybe this example can persuade you that there is a problem between
(lib)xxhash in Focal and in Groovy:
focal$ xxh128sum <(echo -n)
07fd4e968e916ae11f17545bce1061f1 /dev/fd/63
groovy$ x
How about this case:
- I make a hypothetical package that depends on libxxhash < 0.8 because
I want the "broken/old" xxh128 support;
- I have libxxhash 0.7.3 (that came with Focal);
- I have rsync 3.1.x (that came with Focal);
- Now I release-upgrade my system from Focal to Groovy;
- I get all
Hi Wayne! Thanks for commenting.
> It's only the 128-bit hash that depends on 0.8.0.
> The 0.7 version works fine with rsync, giving it
> the 64-bit and 32-bit hashes.
Yes. Except it seems that if you switch the libxxhash0 from 0.8 to 0.7,
you get different behaviour.
rsync doesn't check what ki
Public bug reported:
**Problem**
$ rsync root@focal-system:/etc/.pwd.lock .
ERROR: .pwd.lock failed verification -- update discarded.
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1816) [generator=3.2.3]
$ rsync root@focal-system:/etc/
Public bug reported:
On our upgrade Focal system (which had ZFS-on-root _before_ this was an
installer option in Ubuntu) we're seeing these non-fatal warnings when
running update-grub:
```
# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generati
Public bug reported:
The Focal-shipped MariaDB 10.3.22 is affected by:
https://jira.mariadb.org/browse/MDEV-21614
It is fixed in 10.3.23, and it was apparently not broken in 10.3.21.
It's a nasty optimizer bug that makes certain expressions like this
wrongly return no results:
SELECT y FROM y
[~ozdror] / [~andraz313]:
> but cant apply the fix mentioned same write error
You cannot sudo echo to a file. The opener of the file is still regular-
user.
Try either:
sudo sh -c 'echo deep > /sys/power/mem_sleep'
Or:
echo deep | sudo tee /sys/power/mem_sleep >/dev/null
(P.S. Looks
Here, a combined patch against the debian/ dir.
** Patch added: "xmlindent-combined-fix-for-1803309.patch"
https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323384/+files/xmlindent-combined-fix-for-1803309.patch
--
You received this bug notification because you ar
** Patch added: "yywrap-to-mark-eof.patch (better fix to 857796)"
https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323381/+files/yywrap-to-mark-eof.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, there are two bugs here:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823315
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857796
They've both been fixed in Debian version 0.2.17-5.
I suggest Ubuntu to adopt the load of them. And ideally a better version
of the 857796 fix.
** Patch added: "clean-exit-on-error.patch (823315)"
https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323380/+files/clean-exit-on-error.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Patch added: "makefile2.patch"
https://bugs.launchpad.net/ubuntu/+source/xmlindent/+bug/1803309/+attachment/5323382/+files/makefile2.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803309
And for cross-reference, the ticket by ~chrisren on Kronuz/pyScss:
https://github.com/Kronuz/pyScss/issues/375
** Bug watch added: github.com/Kronuz/pyScss/issues #375
https://github.com/Kronuz/pyScss/issues/375
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
$ pip freeze | grep pyScss
pyScss==1.3.4
$ python -m scss --style compact
xstatic/pkg/mdi/data/scss/materialdesignicons.scss 2>&1 | uniq -c | head -n 10
1650 ERROR: Function not found: function-exists:1
1 @font-face { font-family: 'Material Design Icons'; src:
url('../fonts/materialdesi
Related to https://lkml.org/lkml/2019/10/3/862 ? (That rervert is _not_
in ubuntu linux 4.15.0-66.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849178
Title:
upgrading linux-image package to 4.15
Hi Oliver, thanks for checking.
That's not what I meant though:
> chromium-codecs-ffmpeg are actual files
Yes, they are. So I *do* have *a* changelog.
But the chromium-browser files are not real files, and they point to the
wrong files, making it harder to find the chromium-browser changelog.
(Not sure whose responsibility this is. I did not find the problematic
packaging code directly. Also filed as #1818987 under chromium-browser.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194574
Tit
Public bug reported:
Related to https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/194574,
which has to do with saving space, for some reason, the chromium-browser
has its changelog symlinked to an optional package.
Version: 72.0.3626.119-0ubuntu0.18
Right now, I have chromium-codecs-ffmpeg ins
Right now I have the former installed, also boom.
```
$ dpkg -L chromium-browser | grep changelog.Debian
/usr/share/doc/chromium-browser/changelog.Debian.gz
$ dpkg -l | grep chromium-
ii chromium-browser 72.0.3626.119-0ubuntu0.18.04.1
amd64Chromiu
For the record, now that I've moved from Artful 17.10 to Bionic 18.04,
this bug is not affecting me anymore, but now bug #1724439 is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724557
Title:
gno
I just upgraded to Ubuntu 18.04 with libmutter 3.28.0-2 and ran into
this; monitor poweroff/poweron yields a crash of gnome-shell. The good
news is that the applications are not killed like they were in 17.10
(with wayland?). But waiting for the ubuntu-bug crash file to get
generated isn't a good u
Hi Olivier,
I'm sorry, I must've missed your reply. Apparently I did not auto-
subscribe to the bug-updates.
It crashed again today with 64.0.3282.167-0ubuntu0.17.10.1, so I went
here, saw your response and tried to reproduce: before upgrading it
crashed as expected, but with the latest version f
I've seen a crash with that exact backtrace on Artful just now.
Both on 64.0.3282.140-0ubuntu0.17.10.1 and on
64.0.3282.167-0ubuntu0.17.10.1.
For 140 I did not get a full backtrace because I could not locate the
dbgsym at the time. For 167 the backtrace ends in AsLocatedEvent() <-
DispatchMouseEv
@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the
same:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
By the way, upstream appears to have a fix for this too:
https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726352
Tit
Perhaps this helps?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29
->
https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/
Cheers,
Walter Doekes
OSSO B.V.
--
You received this bug notification because you are a member of Ubunt
In my case, applying just [3] wasn't enough.
[1] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557
[2] https://bugzilla.gnome.org/show_bug.cgi?id=788764
[3] https://bug788764.bugzilla-attachments.gnome.org/attachment.cgi?id=361654
I also had to apply [6] to fix [5]:
[4] https://bu
Yes. Also experiencing these crashes since I switched from Zesty to
Artful yesterday. A lock-screen reproduces the crash, as does turning
the monitor off.
I have a UWQHD (3440×1440) resolution, if that matters, on my Dell
monitor. I'll try to gather some more debug info.
This is highly annoying,
BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
Configuration:
[x] Enable Thunderbolt(tm) Technology Support
[ ] Enable Thunderbolt(tm) Adapter Boot Support
[ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
(x) Security level - User Authorization
I have/had no dev
Ok, rebooted and verified that Thunderbolt was enabled. Both pm-suspend
and lid-closing now works as intended.
Dec 25 23:35:41 walter-tretton kernel: [ 53.790125] Suspended for
135.895 seconds
LGTM :okay_hand:
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Ah..
$ gcc -I /usr/include/efivar 1.c -lsmbios_c
In file included from /usr/include/smbios_c/config/get_config.h:36:0,
from /usr/include/smbios_c/compat.h:27,
from /usr/include/smbios_c/smi.h:22,
from 1.c:22:
/usr/include/smbios_c/config/compiler/
No, because it won't install.
I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-
NN1TN_NVM21.00.cab", but I got:
could not find thunderbolt device at
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:00.0/:03:00.0/domain0/0-0
So I rebooted with Thunderbolt enabled.
(And indeed, no suspend, it was waking/sleeping during the entire 1.5h it was
"suspended" just now.
$ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
115)
Hi Mario, do you mean this?
$ fwupdmgr get-devices
Intel AMT (unprovisioned)
DeviceID: /dev/mei
Guid:
Additional info:
- if I use pm-suspend, it just refuses to suspend (after 20secs wait)
[ma dec 25 18:33:49 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:33:49 2017] thunderbolt :03:00.0: Ignoring mailbox command
error (-110) in icm_suspend
[ma dec 25 18:33:49 2017] PM: Some d
Hi there,
I upgraded to Ubuntu Artful the other day, and today I updated the Dell
BIOS (using the GUI tools).
Out of curiosity, I went back to check this: re-*enabling* Thunderbolt
in the BIOS *still* *breaks* *suspend*.
Again "Some devices failed to suspend, or early wake event detected".
dmid
I have the same problem, but with gpg-agent, which also reverse-depends
on graphical-session-pre.target.
Also upgraded from 17.04 (clean install) to 17.10.
I'm not sure where when the --user graphical-session-pre.target is
supposed to get started (and by whom), but it appears it never does. If
I
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for
me.
Suspend works.
Don't know when/if I'll need the Thunderbolt. This works for now.
Thanks!
Can I provide any additional info to help you debug/fix this properly?
Cheers,
Walter
Before disabling Thunderbolt:
[ 4694.66762
Yeap, that fixes things. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710789
Title:
chromium does not open downloaded files
To manage notifications about this bug go to:
https://bugs.laun
I see it has been fixed in later versions (e.g. on Zesty):
uwsgi-2.0.14+20170111/debian$ grep BINARY_IS_UWSGI_ALTERNATIVE= -A3
uwsgi-plugin-__PLUGIN__.postinst.in*
uwsgi-plugin-__PLUGIN__.postinst.in.pri: BINARY_IS_UWSGI_ALTERNATIVE="$(\
uwsgi-plugin-__PLUGIN__.postinst.in.pri-update
That should be `; true` or ` || true`, but not ` | true`.
Reproduced on Xenial machine where I first installed uwsgi and then
uwsgi-plugin-python3 2.0.12-5ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Uptime is now 13 days. I think we can close this one as "fixed by
4.4.0-79-generic".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kerne
Update: running 4.4.0-79-generic on the original machine with issues for
24hrs (normal workload) without kernel panics thusfar. *Crosses fingers*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691741
The docker1-tcn machine with vanilla kernel 4.4.70 is still up.
And on another (abmfn-staging) machine with 4.4.0-78 I've seen the
crash. According to dmesg output in the console, btrfs and other fs
modules were loaded. Probably due to an update-grub call.
After restart, I ensured that those modu
Okay. So we've been running 4.4.70 now for 22 hours and counting on
docker1-tcn.
/var/crash# uptime
09:45:30 up 22:25, 1 user, load average: 0,01, 0,02, 0,00
/var/crash# uname -a
Linux ossoio-docker1-tcn 4.4.70-040470-generic #201705251131 SMP Thu May 25
15:34:16 UTC 2017 x86_64 x86_64 x86_64
Okay. On a different machine with different load, we've now got the same
problem:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705300948 [PARTIAL DUMP]
CPUS: 4
DATE: Tue May 30 09:48:05 2017
UPTIME: 01:47:38
LOAD AVERAGE: 0.05, 0.06, 0.04
So, I tried to revert the backing_dev_info changes and dpkg-built an
updated kernel. But that didn't work out. Either because it isn't the
cause, or because I reverted too much or too little.
After several hours of normal-load uptime, a removal of the mysql data
dir quickly caused a panic. I did n
I could be on a wild goose chase here.
But one of the prominent changes between 77 and 78 is the
backing_dev_info element of the queue turning into a pointer.
Part of the "bdi" changes in this bit:
++ * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
++4.4.0-47-gene
Crash info appears the same:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-78-generic
DUMPFILE: dump.201705191443 [PARTIAL DUMP]
CPUS: 4
DATE: Fri May 19 14:43:31 2017
UPTIME: 00:43:02
LOAD AVERAGE: 2.53, 1.81, 2.56
TASKS: 544
NODENAME:
RELEASE: 4.4.0-
** 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/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
To mana
Well. That did not go so well: there were no ZFS modules in the builds.
We've tried all of:
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.8-vivid/linux-
image-3.19.8-031908-generic_3.19.8-031908.201505110938_amd64.deb
* http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.68/linux-
image-4
> Does the panic stop happening if you boot back into -77?
Yes. It's now running fine for more thant 3 hours now on -77.
Observe that we have upgraded more than one machine to -78, and only one
machine has trouble.
> Would it be possible for you to test the latest upstream stable kernel?
Ah, y
** 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/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
To mana
A google search turned up this as the most likely candidate for my
logrotate+gzip issues.
I'm going to try this for a workaround:
/var/log/upstart/*.log {
daily
missingok
rotate 7
compress
notifempty
nocreate
# Added by wjd 2017-03 for launchpad b
It works.
$ apt-cache policy pdns-recursor
pdns-recursor:
Installed: 4.0.0~alpha2-2
Candidate: 4.0.0~alpha2-2ubuntu0.1
Version table:
4.0.0~alpha2-2ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64
Packages
4.0.0~alpha2-2osso1 500
s/the broken Xenial version is lower/the fixed Xenial version is lower/
(sorry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641380
Title:
chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
Okay, that didn't take long. My slack windows started to "Aw snap!"
within another 10 minutes.
Both the Xenial [*1] version and the version from Haw Loeung (hloeung)
[*2] work fine though. Where the second is better because the broken
Xenial version is lower and would be auto-replaced with the bro
54.0.2840.100-0ubuntu0.16.10.1326 from 'ppa:canonical-chromium-
builds/stage' (on Yakkety) hasn't crashed yet. (Running for 10 minutes
now.) Beats having to switch to FF for some pages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
The patch is present in rec-4.0.0-beta1, so if Yakkety runs >=4.0.0 (not
alpha), we should be good.
But sure:
$ grep VERSION /etc/os-release
VERSION="16.10 (Yakkety Yak)"
VERSION_ID="16.10"
VERSION_CODENAME=yakkety
$ dpkg -l pdns-recursor | grep ^ii
ii pdns-recursor 4.0.1-1build2 amd64
Public bug reported:
The pdns-recursor in Xenial returns this:
$ dig A umcg-nl.mail.protection.outlook.com. @127.0.0.1 +edns +dnssec
...
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 57895
While it should return this:
...
umcg-nl.mail.protection.outlook.com. 10 IN
I happens every now and then as far as I can tell (xenial here, but seen
with earlier OSes):
Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report
/etc/cron.weekly )
```
/etc/cron.weekly/apt-xapian-index:
Exception ignored in: >
Traceback (most recent call last):
File "/usr/lib/python
Thanks for you reply. Looks like it indeed.
The only confusing bit left was the apparent "crashing" of the release-
upgrade dialog, causing the startup of apport and this bug report in the
first place.
A dialog with "we cannot properly convert your sources.list, please fix
it manually" and no cra
Public bug reported:
Versions:
python-pil:amd64 3.1.2-0ubuntu1
python-pisa3.0.32-3
Exception:
File "...", line 172, in to_pdf
context = CreatePDF(src=source, dest=destination, default_css=DEFAULT_CSS)
File "/usr/lib/python2.7/dist-packages/s
** Attachment added: "VarLogDistupgradeMainlog.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1613183/+attachment/4721073/+files/VarLogDistupgradeMainlog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
The GUI warned that ubuntu-minimal could not be located.
The console version showed this:
"""
After updating your package information, the essential package
'ubuntu-minimal' could not be located. This may be because you have
no official mirrors listed in your software sour
I think so. I did a single attempt at reproducing it recently, I didn't
succeed.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465959
Title:
In phones with two SIMs, if you don't unlock SI
void
StaticSwitchScreen::getWindowPosition (unsigned int index,
int *x,
int *y)
{
int row, column;
if (index >= windows.size ())
return;
column = (int)index % xCount;
row= (
Also on Ubuntu 14.04. This has never happened to me before, as fas as
I'm aware, and now twice in a row:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename: trusty
Versions:
compiz 1:0.9.11.3+14.04.20150313
I've never had GPS location work without the HERE functions enabled. As
soon as I disable it (I have to restart for a change to take effect) I
get *no* location info whatsoever. (I have waited for weeks to get a GPS
lock, to no avail.)
The SensorsStatus tool tells me (when HERE is enabled) that I
Same here. I had the "Using GPS only" since I bought the phone and GPS
never worked. Days/weeks of uptime should be enough to get a GPS lock,
right?
Now I enabled the GPS/Wifi/mobile-network ("HERE"), rebooted, and like
you said, within 30 seconds, the SensorsStatus tool started reporting
GPS info
The released new icon solves this problem indeed.
I'm not fond of the new gsm-signal and wifi indicators though, but
that's another matter ;)
Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
> My proposal is to have two icons:
> orientation-lock.svg [standing + flat phone + X]
> and
> orientation-unlock.svg [standing + flat phone + move-arrow]
>
> What do you think about that?
Awesome!
Right now the latter image [standing + flat phone + move-arrow] is used
for the lock case; so that
No idea; I only noticed this when initially using the phone.
If you think it's fixed in the next version, I'll believe you. I'll
reopen if it happens again.
Thanks!
** Changed in: indicator-location (Ubuntu)
Status: New => Fix Released
** Changed in: indicator-location (Ubuntu RTM)
100% reproducible:
- boot with dual sim,
- when it says sim 1: press X (to cancel)
- then it says sim 1, but it wants sim 2 code
- enter sim 2 code
- at this point, only sim 2 is activated,
- authenticate, go to network, unlock sim 1, now it says "sim 2" but wants sim
1 code
--
You received thi
*** This bug is a duplicate of bug 1447479 ***
https://bugs.launchpad.net/bugs/1447479
** This bug has been marked a duplicate of bug 1447479
SIM Pin1 and Pin2 headings get mixed up sometimes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
- even though I've disabled GPS and "Location detection", the crosshair icon is
always on.
- after playing around with *enabling* the GPS and waiting a bit, the ico
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
- the "Rotation locked" icon appears as "phone which can be rotated",
which is illogical to me. If the rotation is locked, then I'd expect the
icon to cross out the
*** This bug is a duplicate of bug 1358340 ***
https://bugs.launchpad.net/bugs/1358340
Oops. Hadn't found those. Sorry.
Disabling both the "Launcher" and "Notifications and quick settings"
suits my needs.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs
Agreed. I tried Europe first, before I searched for Amsterdam. And when
selecting that, I saw that it had properly converted that to the
appropriate "Europe/Amsterdam".
If we're configuring time, it should IMO not ask for location, but for a
timezone, which is Europe/Amsterdam. I don't want to tel
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've noticed the following:
even though the phone is supposed to be locked, one can:
- read incoming messages from the notification (top swipe) area,
- change on/off state of bluetooth, gps, wi
Public bug reported:
On the Aquaris E4.5 (ubuntu 14.10 r21, Utopic Unicorn dev, armhf
20150410-232623), I've had the following issue:
- both SIMs are inserted, I'm asked to unlock one SIM, and the text
above says SIM2 while in fact it wanted the pin code for SIM1 (and vice
versa): notably, the co
** Summary changed:
- [greeter] strange persistant "Enter SIM1 PIN" dialog on Greeter
+ [greeter] strange persistent "Enter SIM1 PIN" dialog on Greeter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
1 - 100 of 138 matches
Mail list logo
