That would be helpful, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972735
Title:
"go test archive/zip" fails, gophercolor16x16.png wrong size
To manage notifications about this bug go
Public bug reported:
Go's test suite shows a problem:
$ go test archive/zip
--- FAIL: TestReader (0.06s)
--- FAIL: TestReader/test.zip (0.00s)
reader_test.go:675: gophercolor16x16.png: len=785, want 664
--- FAIL: TestReader/test-trailing-junk.zip (0.00s)
Also: if the colon is in the name of a directory you are copying, the
directory gets created with the colon in the name, but any attempt to
put files in it hangs.
Deleting the colon-named things via Files does seem to work, though.
And transferring files with spaces, dashes, and umlauts in the
Public bug reported:
A colon in a file or directory name causes the operation to hang when
copying to a phone via ptp.
To reproduce:
On android phone:
1) plug usb cable between phone and computer
2) Go to settings. Search for USB. Click on "Standard USB configuration".
(Alternately, notice
I tip my hat to you, sir!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/103537
Title:
rosetta stone won't install via WINE
To manage notifications about this bug go to:
I no longer have access to the system in question, and haven't seen it
anywhere else, may as well close as abandoned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766938
Title:
gnome-shell
(The zero size problem mentioned above also occurs occasionally on
ubuntu 18.04, and the workaround is to add a sleep in the user script
after modprobe nbd, so that's really a separate problem.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On today's groovy snapshot (with the default kernel, 5.8.0-generic), the
original problem is still present; didn't seem to show up until 2nd run
of the bug script.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also seems to work fine on ubuntu 18.04 (fresh, fully updated).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896350
Title:
nbd locks system?
To manage notifications about this bug go to:
FWIW, running same script on ubuntu 16.04 seems to work better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896350
Title:
nbd locks system?
To manage notifications about this bug go to:
Here's the apport file from the VM (which is a very recent clean install);
for some reason I couldn't upload it with ubuntu-bug.
** Attachment added: "apport.linux-image-5.4.0-47-generic.0beq9kz0.apport"
Public bug reported:
I'm trying to use nbd on ubuntu 20.04 like so:
qemu-img create -f qcow2 foo.img 500M
sudo modprobe nbd
sudo qemu-nbd --disconnect /dev/nbd15 || true
sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img
sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard
Here's the rough recipe for building ubuntu 18.04's systemd (well, or
anything, really):
Start a clean ubuntu 18.04 system (perhaps with lxd), then:
sudo apt update
sudo apt dist-upgrade
sudo apt install devscripts
sudo apt build-dep systemd
apt source systemd
cd systemd-237
debuild -b -uc -us
cd
The 2nd startx workaround turns out not to work, alas; I spoke too soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874879
Title:
startx fails on first run with "Cannot run in framebuffer mode"
440 ought to work with that card, if I'm reading this right:
https://www.nvidia.com/Download/driverResults.aspx/159360/en-us
- Dan
On Fri, Apr 24, 2020 at 4:30 PM Dimitri John Ledkov wrote:
> On Mon, 20 Apr 2020 at 20:53, Jack Howarth
> wrote:
> >
> > I am finding on a 2008 MacPro with
BTW this worked fine on earlier versions of ubuntu, including 18.04 and
19.10.
(I'm perfectly happy to hear it's user error, and the login needs to
wait for something other than network-online.target, or that I did the
wait wrong. The wait didn't seem to be needed before. Also, I didn't
mention
Public bug reported:
Fresh ubuntu 20.04 machine with a gtx 1080.
Configured to boot to commandline with sudo systemctl set-default multi-
user.target
Proprietary driver nvidia 440 installed with 'ubuntu-driver install'.
Rebooted.
Logged in, ran startx.
Startx ran fine.
Configured system to
I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install'
to
get drivers for my gtx 1080. Reinstalling ubuntu 20.04 final made the problem
vanish
(whew).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On ubuntu 18.04, opening the default terminal (gnome-terminal
3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04 system,
running 'vi', and pressing 'i' shows the unwelcome garbage ESC [>4;m.
Pressing ESC emits more garbage: ESC [>4;2m
Focal's default vi is
No, it's hard to imagine that working, I fear.
Theoretically Canonical could upgrade bionic's nodejs to use the system's
primary openssl.
That is also not likely to happen, though, as it is a lot of work, and still
might not please nodejs users fully. (Plus it could break some users.)
--
You
Well, yes. And as a result, the nodejs package on bionic is completely broken
when you actually try to use it for any project.
So, I guess one should avoid bionic if one uses nodejs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> DKMS make.log for amdgpu-17.40-492261 for kernel 5.3.0-40-generic (x86_64)
> /var/lib/dkms/amdgpu/17.40-492261/build/include/kcl/kcl_pci.h:7:5: error:
> conflicting types for ‘pci_enable_atomic_ops_to_root’
Sounds like you downloaded amdgpu-pro some time ago, and are trying to
install an old
It is a bit hard to find.
https://help.ubuntu.com/stable/ubuntu-help/report-ubuntu-bug.html.en
mentions running ubuntu-bug, and that should work; just give the name
of the package as an argument.
- Dan
On Mon, Feb 24, 2020 at 2:42 PM Petr Schuchmann
wrote:
>
> Hello,
>
> I asked question on
As far as I know, libssl-dev is stable.
The -dev suffix just means it provides development files, e.g. .h and .pc
files.
On any particular Ubuntu version, it only gets micro updates, and no
experimental ones.
- Dan
On Wed, Dec 11, 2019 at 11:02 AM Brylie Christopher Oxley
wrote:
> Hello,
>
> I
Filed https://gitlab.gnome.org/GNOME/gtk/issues/2221 in case it's an upstream
bug.
I'll probably regret that.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2221
https://gitlab.gnome.org/GNOME/gtk/issues/2221
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c &&
gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
On Wed, Sep 25, 2019 at 6:19 AM kavitha R wrote:
> When we run "apt-get update", does it download all the packages information
> that will be stored in /var/lib/apt/lists/* _Packages file?
I think so. You could use tcpdump or wireshark to confirm.
> Why do we store the package full
On Wed, Sep 25, 2019 at 6:19 AM kavitha R wrote:
> How does apt-cache create and updates the local package cache? Is it periodic
> or manual? As far as my investigation, it is manual (apt-get update).
It can be manual; if a package like unattended-upgrades is installed,
it can run apt-get
Upstream bug now https://bugzilla.mozilla.org/show_bug.cgi?id=1399501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732766
Title:
firefox 57 does not display fish in fishgl.com on intel 530?
To
Yeah... I suspect the OpenSSL folks are painfully aware of that, and
future versions will likely be much better at preserving compatibility.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
FWIW, I ran into this after updating to 19.04 from 18.04.
Audio working fine with HDMI (yay) but not with back panel audio (boo)
unless I ran aplay as root, e.g.
sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav
ps showed timidity running. 'sudo apt remove timidity; sudo
Quicker approach:
realizing that the package you want is gone but not forgotten :-),
download the debs from
https://launchpad.net/ubuntu/disco/amd64/clang-format-4.0/1:4.0.1-10build1
and
https://launchpad.net/ubuntu/cosmic/amd64/libllvm4.0/1:4.0.1-10build1
and install them with
sudo dpkg -i
For what it's worth, I just forward-ported 3.9 from xenial to disco
because the alternative was reformatting a bazillion lines of
source code. It wasn't too hard, just had to do 'apt source clang-format'
on an ubuntu 18.04 box, transfer the source to a 19.04 box,
install gcc 7 and make three
Public bug reported:
My Nokia 6.1 phone is properly autodetected, and I can fetch files from it fine
via
the default ubuntu gui (using gvfs etc).
However, running gmtp fails. To diagnose this I tried running mtp-detect.
This fails with
dank@thinky:~$ mtp-detect
libmtp version: 1.1.16
Listing
It's worse than that. Developers who use nodejs in their apps, and have
to use libssl-dev, are simply screwed. Even moving to a container won't
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In a similar vein, my ppa
https://launchpad.net/~dank/+archive/ubuntu/python-fixes has a couple
cherrypicked fixes for the python ecosystem in ubuntu 16.04 and 18.04.
I put that together as I was fixing
https://github.com/nexB/scancode-toolkit to install via system pip;
turns out there were a
Here's where the regression occurred:
https://bugzilla.gnome.org/show_bug.cgi?id=689972
The design page, https://wiki.gnome.org/Design/OS/KeyboardShortcuts,
noted "Maybe the familiarity is too strong on this one". It most certainly is.
** Bug watch added: GNOME Bug Tracker #689972
Public bug reported:
In olden days, you could alt-tab to return to the last window you had active.
and pressing alt-tab twice was a round trip, bringing you back to the same
window.
Now alt-tab does something else less useful. Every time I want to switch
between
two windows, I try to use
The first line of the bug report should have said "and ubuntu 16.04".
https://launchpad.net/~dank/+archive/ubuntu/python-fixes/+packages now includes
updated pip with the cherrypicked fix for both ubuntu 16.04 and ubuntu 18.04.
--
You received this bug notification because you are a member of
PPA https://launchpad.net/~dank/+archive/ubuntu/python-fixes/ now
contains a python-configparser with that fix applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821247
Title:
I suspect this was the cause of https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=865359
** Bug watch added: Debian Bug tracker #865359
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865359
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
https://launchpad.net/~dank/+archive/ubuntu/python-fixes contains an updated
pip with the cherrypicked fix.
(Also, http://kegel.com/linux/howto-ppa/ happens to document how it was
prepared.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
On Ubuntu 18.04 (and ,
Running 'pip install simplejson' or 'pip install PyOpenSSL' twice
crashes on exit because their shared libraries are overwritten while in use.
To reproduce:
$ sudo apt install python-pip
$ pip install simplejson
$ pip install simplejson
Segmentation
See also https://github.com/jaraco/configparser/issues/17
I also verified that rebuilding the package python-configparser with the
following patch, and installing that, fixes the problem here:
--- configparser-3.5.0.orig/setup.py
+++ configparser-3.5.0/setup.py
@@ -42,7 +42,6 @@ setup(
Public bug reported:
Installing python-configparser 3.5.0-1 breaks other python modules in
the backports namespace.
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1812589 was
filed against the wrong package; see also
https://github.com/PiDelport/backports.os/issues/11
The problem was
(although on ubuntu 18.04 desktop, the underlying network system might
be systemd rather than dhclient; it's hard to tell, there are so many
layers to keep track of, and they keep changing)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This affects me on Ubuntu 18.04 desktop. After changing hostname, I
have to use nmcli c down... nmcli c up... to update the dynamic DNS
entry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551351
Public bug reported:
Trying to install 16.04 on a Dell 3620 in secure boot mode with uefi.
Two disks: nvme... and sda.
Seems confused by old contents on disks, even though I chose "erase disk and
install ubuntu".
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63
Workaround was easy: in the live session the installer started for my
convenience after the fault, I ran fdisk on each of the two disks to
create a new gpt partition table, then reran the live installer. Worked
great this time.
So:
start terminal
lsblk
fdisk /dev/sda
g
w
fdisk
Even with lxd or schroot, you won't be able build anything against libssl-dev
if your build script happens to need any of the nodejs modules that use openssl.
So that's not really much of a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think the advice is harder to follow than it looks. Many node packages
require libssl-1.0-dev,
and you can't install them on a system used to develop c/c++ apps that require
libssl-dev.
To wit:
$ sudo apt install -s node-websocket libssl-dev
...
node-websocket : Depends: nodejs-dev (>=
In hopes of being able to create a ppa that reduces the pain level a
bit, I tried rebuilding a newer nodejs for ubuntu 18.04 using the
debian/ubuntu nodejs git repo.
Using the source from 19.04's runs into quite a few test failures (
https://github.com/nodejs/help/issues/1760 ).
Public bug reported:
I've been testing as follows:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60 fps)
- after fish are happily swimming, watch them swim for 60 seconds, and count
number of times the
Public bug reported:
I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe
https://mzwiki.oblong.com/wiki/Hades_Canyon
My smoke test is:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60
This just cost me four hours on Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812589
Title:
pip's configparser dependency breaks backports namespace conventions
To manage
More specifically, if I do
pip install backports.os
python -c "from backports import os"
it fails as described. But if I then do
sudo apt remove python-configparser
it succeeds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just re-read kapouer's comments. They seem spot on.
I also re-read vorlon's comments. They have a vaguely disturbing
attitude along the lines of 'Why are you using Ubuntu to develop
software on? It's only for running software somebody else built
already.'
--
You received this bug
You could try
https://github.com/nodesource/distributions/blob/master/README.md
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage
That was the correct solution, and I sympathise with your rant.
Node is an ecosystem, and shipping a version of node that can't handle
native libraries is like sticking a fork in the eyes of the users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I uploaded the backports of xmltooling, xml-security-c, and opensaml2 to
https://launchpad.net/~dank/+archive/ubuntu/openssl-uplift
and wrote it up at http://kegel.com/linux/openssl-ubuntu18.04-snafu/
That might be enough to let us limp by now that we've given up on the
nodejs packaged with
Correction:
1) futzing with /lib/systemd/system/haveged.service doesn't help
2) strace -f shows that haveged is indeed failing because it can't write to
/var/run
3) adding the line suggested in the original post to
/etc/apparmor.d/usr.sbin.haveged works
I failed to try the single-line
I verified that my 16.04 system has upstart-sysv installed and that
/var/log/syslog contains
haveged: haveged starting up
kernel: [43612.894002] audit: type=1400 audit(1544731842.319:38):
apparmor="DENIED" operation="mknod" profile="/usr/sbin/haveged"
name="/run/haveged.pid" pid=15508
Does https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46468 need tidying?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900901
Title:
Steam overlay does not work due to GCC-4.6 issues
To manage
Those two weren't hard; I also had to backport opensaml2-tools. I can
imagine a little ppa with those three packages and maybe a few more;
using the ppa would let you rebuild your app using the backported
packages (and prevent you from building against the old packages, as the
new -dev's would
The next place this reared its ugly head was libxmltooling7 / libxml-
security-c-dev, and I don't see an alternate available.
Looks like ubuntu 18.10 has solved that bit. Maybe the answer for me is
to give up on 18.04 and use 18.10 / 19.04 / 19.10 / 20.04. I really
don't think our product folks
correct, apt-cache policy did show two sources. I wasn't paying
attention.
Invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804343
Title:
apt: Misleadingly reports Hash Sum mismatch if
Public bug reported:
I'm using reprepro to maintain a local repository. It doesn't compute SHA512
hashes.
This worked fine until today, when I got this error:
buildbot@workstation:~/src/python-modules-deps/old$ apt download
python-swagger-spec-validator
Get:1
{Thank,curse} you for offering that solution. I will have a look!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications about
Our project also links against libssh-dev (sorry, I meant to mention that),
which has the same problem, but lacks a libssh-openssl1.0-dev.
Also, it's somewhat jarring to have to change dependency names
when we build against ubuntu 18.04 vs. 16.04; we can do that,
and have done it, but it adds a
I've been really happy with Ubuntu for ten years, but this particular situation
is making me scratch my head. Might want to get Mark's input here -- is Ubuntu
intended to be a
curated ecosystem that works well as a platform for both proprietary and open
source software?
--
You received this
Yup, I have a package that uses node and requires libssl-dev and
libcurl-openssl.
It was rather jarring when it stopped building because of the update to
node.
If you're saying that Ubuntu is not suitable for developing proprietary
software that uses node, libssl, and libcurl, well, I guess
Here's a short way to see the failure:
1) make sure /etc/apt/sources.list has bionic-updates enabled for universe (and
multiverse?)
2) sudo apt update
3) sudo apt install nodejs-dev libssl-dev
...
The following packages have unmet dependencies:
nodejs-dev : Depends: libssl1.0-dev (>= 1.0.2)
Then my original bug report was correct. nodejs needs to be updated to a
version that uses ubuntu 18.04's openssl instead of using the
incompatible one. Shall I refile?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
To reproduce:
$ sudo apt install vagrant virtualbox
$ vagrant box add ubuntu/xenial64
$ vagrant plugin install vagrant-scp
Installing the 'vagrant-scp' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error.
I see Debian's up to 2.1.2 in Buster for what it's worth:
https://packages.debian.org/search?keywords=vagrant
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796168
Title:
"vagrant plugin install
Can you pin the version of nodejs (either in the command that installs
it, or in apt configuration)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
nodejs-dev conflicts with
Can you comment out universe from bionic-updates in /etc/apt/sources.list ?
That works for me, at least for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
nodejs-dev conflicts
Doing version transitions of popular libraries is not rocket science. It's a
hard slog.
I respect and thank the node and openssl maintainers.
I was not assigning blame, simply giving the symptom that caused my
world to explode.
--
You received this bug notification because you are a member of
When will ubuntu provide nodejs 10.x (said to depend on openssl 1.1)?
cosmic would be none too soon.
(I kind of wish Debian and Ubuntu allowed simultaneous installs of node8
and node10 ecosystems... e.g. by installing nodejs 10 to
/usr/lib/node/10 and using node10 prefixes on package names, and
Public bug reported:
The fix for https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863
is, not surprisingly, somewhat traumatic for some users.
In my case, installing libssl1.0-dev causes libcurl4-openssl-dev,
libssh-dev, and libssl-dev to be uninstalled, which makes some of our
internal
I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing
list posts).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714178
This just changed for me... but the hardware may matter, as I'm on Hades
Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on
Oh? Then you think
https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163 was
decided incorrectly, and makedev should indeed create devices inside lxc
containers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Correction: the repro script was
#!/bin/sh
set -ex
sudo apt install dh-make-golang
DIST=bionic git-pbuilder create dh-make-golang github.com/gomatic/renderizer
dh-make-golang github.com/gomatic/renderizer
cd renderizer/
gbp buildpackage --git-dist=bionic --git-pbuilder
--
You received this bug
Public bug reported:
On Ubuntu 18.04, I was trying to reproduce a problem, so I spun up an
lxc container and ran my reproduce script in it, i.e.
#!/bin/sh
set -ex
sudo apt install dh-make-golang
DIST=bionic git-pbuilder create
dh-make-golang github.com/gomatic/renderizer
cd renderizer/
gbp
This just hit me as well, on a kosher 18.04 system.
I recently upgraded to a newer nvidia card, so that must have mangled it
somehow.
Looks like three of its symlinks got nuked:
ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or
directory
ls: cannot access
Also occurs on Ubuntu 18.04 updated to latest mesa and using Vega M
graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732766
Title:
firefox 57 does not display fish in fishgl.com on intel
Tested as follows on ubuntu 18.04:
$ apt-get install lxd lxd-client
$ lxd init
$ lxc launch ubuntu:18.04 ubu1804-demo
$ lxc exec ubu1804-demo bash
# apt update
# apt install composer
# composer --version
Composer 1.6.3 2018-01-31 16:28:17
# composer create-project drupal/drupal hellodrupal 8.5.6
Public bug reported:
This is on a fresh Dell 8930 with an i7-8700 (and a gtx1050) running ubuntu
18.04.
Linux rbb-ubu1804-1 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Oddly this only happens on one of the two such boxes I have.
Here's the main
https://lkml.org/lkml/2017/12/7/201 tries to raise the limit, but according to
https://bugs.freedesktop.org/show_bug.cgi?id=102508#c11 it does not work.
Also, Skull Canyon is 6th generation, is it not? See
https://www.intel.com/content/www/us/en/nuc/nuc-kit-nuc6i7kyk-features-
See also similar bugs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178
Those were treated as if the 8kx8k limit was ok, and the bug was in the
compositor
which failed to work around that limit. Perhaps this bug
Thanks... sounds like it's a hardware limitation, and the fix involves noticing
when the limit's being violated, and doing extra work in that case.
I wonder what the framerate impact of that extra work will be.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks, I'll try weston-launch when I get a chance, and I'll try it on
ubuntu 18.04 with intel graphics.
In the meantime, I checked the maximum size a few systems report, and it
does seem to be a property of the graphics hardware and/or driver.
See also
Sorry, that Intel URL should have been
https://www.intel.com/content/www/us/en/support/articles/05571/mini-
pcs.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776260
Title:
Can't use three
Public bug reported:
https://www.intel.com/content/www/us.../mini-pcs.html
claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so
I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04.
It works great when plugged into one 4k monitor (via any of the three
https://askubuntu.com/questions/836105/ubuntu-16-04-takes-long-time-to-
boot-using-btrfs-and-persistent-logs suggests disabling COW on the
systemd journal directory may help.
Avoiding / as btrfs, and using it just for e.g. /var/lib/lxd, may be an
option for some people.
--
You received this bug
May be fixed now? See https://forum.snapcraft.io/t/swap-on-core/5430/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560942
Title:
Support swap
To manage notifications about this bug go to:
optimized out, alas. But:
(gdb) frame 9
#9 surface_from_pixmap (xdisplay=xdisplay@entry=0x56149472f000,
xpixmap=xpixmap@entry=31457330, height=,
width=) at x11/iconcache.c:325
325 return cairo_xlib_surface_create_with_xrender_format (xdisplay,
xpixmap, DefaultScreenOfDisplay
Too late! The world has moved on, and I can no longer upload this bug:
You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:
libdb5.3, libplist3, libssl1.1, openssl
I guess if it happens on another machine, I'll upload
Sure, sorry for uploading it wrong in the first place.
The new bug is ... uh... it didn't create one, it just went into the ether, in
a cloud of dots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 652 matches
Mail list logo