[Bug 1972735] Re: "go test archive/zip" fails, gophercolor16x16.png wrong size

[Dan Kegel]

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 to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.18/+bug/1972735/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972735] [NEW] "go test archive/zip" fails, gophercolor16x16.png wrong size

[Dan Kegel]

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)
reader_test.go:675: gophercolor16x16.png: len=785, want 664
FAIL
FAILarchive/zip 26.182s
FAIL

The source for the test shows that it is comparing the size of the file 
/usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png
to the size of the same file inside the archive test.zip in the same directory:

$ ls -l /usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png
-rw-r--r-- 1 root root 664 Apr 13 14:52 
/usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png


$ unzip -v /usr/share/go-1.18/src/archive/zip/testdata/test.zip
...
 785  Stored  785   0% 2010-09-04 22:52 54d531fe  gophercolor16x16.png

The same file in the upstream tarball,
http://archive.ubuntu.com/ubuntu/pool/main/g/golang-1.18/golang-1.18_1.18.1.orig.tar.gz
has the expected size:

$ tar -tvf golang-1.18_1.18.1.orig.tar.gz | grep gophercolor
-rw-r--r-- root/root   785 2022-04-12 08:42 
go/src/archive/zip/testdata/gophercolor16x16.png

The file appears to be installed correctly per dpkg:

$ grep gophercolor /var/lib/dpkg/info/golang-1.18-src.md5sums
75631d6d103ce71fe8d58aff2386c4a4  
usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png

$ md5sum /usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png
75631d6d103ce71fe8d58aff2386c4a4  
/usr/share/go-1.18/src/archive/zip/testdata/gophercolor16x16.png

Where in the packaging pipeline did the file become smaller?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: golang-1.18-src 1.18.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May  9 14:29:13 2022
Dependencies:
 
InstallationDate: Installed on 2020-10-17 (569 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: golang-1.18
UpgradeStatus: Upgraded to jammy on 2022-05-01 (8 days ago)

** Affects: golang-1.18 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
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 to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.18/+bug/1972735/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921651] Re: colon in name causes gvfs hang when copying to phone

[Dan Kegel]

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 names
works fine, too.  It's just the colon that causes trouble.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921651

Title:
  colon in name causes gvfs hang when copying to phone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921651] [NEW] colon in name causes gvfs hang when copying to phone

[Dan Kegel]

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 mystery status card at very bottom of notifications 
saying "Android system - charging over USB, click for options", and click on 
it.) 
3) Select PTP.

Then on Ubuntu 20.04 (and probably other recent vintages as well):

0) observe your phone popping up in dock and in Files
1) cp good.mp3 bad:.mp3
2) xdg-open .
3) In dock or Files, also open your phone
4) drag good.mp3 to your phone, note that it succeeds
5) drag bad:.mpd to your phone, note that it hangs

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gvfs 1.44.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 28 15:28:32 2021
InstallationDate: Installed on 2020-10-17 (162 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gvfs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921651

Title:
  colon in name causes gvfs hang when copying to phone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 103537]

[Dan Kegel]

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:
https://bugs.launchpad.net/wine/+bug/103537/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

[Dan Kegel]

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 crashed in standard_pict_format_for_depth()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] Re: nbd locks system?

[Dan Kegel]

(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 Ubuntu.
https://bugs.launchpad.net/bugs/1896350

Title:
  nbd locks system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] Re: nbd locks system?

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1896350

Title:
  nbd locks system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] Re: nbd locks system?

[Dan Kegel]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] Re: nbd locks system?

[Dan Kegel]

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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] Re: nbd locks system?

[Dan Kegel]

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"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+attachment/5412512/+files/apport.linux-image-5.4.0-47-generic.0beq9kz0.apport

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896350] [NEW] nbd locks system?

[Dan Kegel]

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 /dev/nbd15
sudo qemu-nbd --disconnect /dev/nbd15

It seems to work on some systems, but even on those systems, strange things 
show up
in syslog, e.g.

Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck 
request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds
Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 
blocked for more than 241 seconds.

and in kern.log, e.g.

...
Sep 19 16:17:27 thinky kernel: [   71.676026] Buffer I/O error on dev nbd15, 
logical block 7, async page read
Sep 19 16:17:27 thinky kernel: [   71.676049] blk_update_request: I/O error, 
dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sep 19 16:17:27 thinky kernel: [   71.676051] Buffer I/O error on dev nbd15, 
logical block 0, async page read
Sep 19 16:17:27 thinky kernel: [   71.676061] blk_update_request: I/O error, 
dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sep 19 16:17:27 thinky kernel: [   71.676063] Buffer I/O error on dev nbd15, 
logical block 1, async page read
Sep 19 16:17:27 thinky kernel: [   71.676147] ldm_validate_partition_table(): 
Disk read failed.
Sep 19 16:17:27 thinky kernel: [   71.676324] Dev nbd15: unable to read RDB 
block 0
Sep 19 16:17:27 thinky kernel: [   71.676473]  nbd15: unable to read partition 
table
Sep 19 16:17:27 thinky kernel: [   71.678340] nbd15: detected capacity change 
from 0 to 524288000
Sep 19 16:17:27 thinky kernel: [   71.678536] ldm_validate_partition_table(): 
Disk read failed.
Sep 19 16:17:27 thinky kernel: [   71.678719] Dev nbd15: unable to read RDB 
block 0
Sep 19 16:17:27 thinky kernel: [   71.678947]  nbd15: unable to read partition 
table
Sep 19 16:17:27 thinky kernel: [   71.679985] ldm_validate_partition_table(): 
Disk read failed.
Sep 19 16:17:27 thinky kernel: [   71.680172] Dev nbd15: unable to read RDB 
block 0
Sep 19 16:17:27 thinky kernel: [   71.680366]  nbd15: unable to read partition 
table
Sep 19 16:17:27 thinky kernel: [   71.680647] block nbd15: Attempted send on 
invalid socket

and the system seems to hang on reboot.

Also, on another system (an up to date mac, running ubuntu 20.04 in 
virtualbox), 
the mkfs.ext4 fails, complaining the device is zero size.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-47-generic 5.4.0-47.51
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dank   2948 F pulseaudio
 /dev/snd/controlC2:  dank   2948 F pulseaudio
 /dev/snd/controlC0:  dank   2948 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 19 16:28:43 2020
HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f
InstallationDate: Installed on 2017-04-29 (1239 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO ThinkServer TS140
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-47-generic N/A
 linux-backports-modules-5.4.0-47-generic  N/A
 linux-firmware1.187.2
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKT99AUS
dmi.board.name: ThinkServer TS140
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 7
dmi.chassis.vendor: LENOVO
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000HUX:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: ThinkServer TS140
dmi.product.sku: LENOVO_PN_ThinkServer TS140
dmi.product.version: 70A4000HUX
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896350/+subscriptions

-- 
ubuntu-bugs mailing 

[Bug 1874879] Re: startx fails on first run with "Cannot run in framebuffer mode"

[Dan Kegel]

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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874879/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874879] Re: startx fails on first run with "Cannot run in framebuffer mode"

[Dan Kegel]

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 this, but adding 'sleep 10' before startx didn't seem to help.)

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874879/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874879] [NEW] startx fails on first run with "Cannot run in framebuffer mode"

[Dan Kegel]

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 log in automatically by creating 
/etc/systemd/system/getty@tty1.service.d/autologin.conf
containing

[Service]
ExecStart=
ExecStart=-/sbin/agetty --autologin buildbot --noclear %I 38400 linux
[Unit]
Wants=network-online.target
After=network-online.target

Installed lwm and xterm, created a simple .xinitrc that just runs xterm
and lwm:

/usr/bin/xterm  -geometry 80x25+0-0   &
exec lwm

In .profile, added lines at the end to run startx if at console:

case `tty` in
/dev/tty1) startx;;
esac

Rebooted.

Startx failed with

(EE) Cannot run in framebuffer mode. Please specify busIDsfor
all framebuffer devices

Running startx again manually worked fine.

Adding a second startx after the first one in .profile also worked fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-driver-440 440.82+really.440.64-0ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr 24 11:06:43 2020
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers-440
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-440 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874879/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865870] Re: [nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1865870

Title:
  [nvidia] xorg via gdm-x-session fails to start with "Cannot run in
  framebuffer mode. Please specify busIDs for all framebuffer devices"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1865870/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873920] [NEW] default vi on focal emits escape sequences unrecognized by bionic's terminal?

[Dan Kegel]

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 provided by vim.tiny via alternatives.  Oddly,
when running vim.tiny by itself, or if you install vim and let it
provide vi, the garbage does not appear.

Evidently focal's vim.tiny is confused about what escape sequences
ubu1804's Terminal accepts.

TERM is xterm-256color.  The problem also occurs if TERM is xterm.

There is no .vimrc.

If I use xterm on ubuntu 18.04, all is well.  Evidently xterm accepts
ESC[>4;m and gnome-terminal doesn't?

I captured a session using 'script' and dumped typescript via hexdump -C. 
In this session, I typed i, Q, and escape. Here's an excerpt
showing the end of vi's welcome message, followed by five escape sequences
and then the Q I typed.  The unrecognized ESC > 4;m is visible in the dump,
followed by ESC[?25l (CURSOR OFF)

1070  66 61 75 6c 74 1b 5b 33  34 6d 3c 45 6e 74 65 72  |fault.[34m.[m for info on|
1090  20 74 68 69 73 1b 5b 31  3b 31 48 1b 5b 3f 32 35  | this.[1;1H.[?25|
10a0  68 1b 5b 3f 32 30 30 34  6c 1b 5b 3e 34 3b 6d 1b  |h.[?2004l.[>4;m.|
10b0  5b 3f 32 35 6c 51 1b 5b  38 3b 34 37 48 1b 5b 31  |[?25lQ.[8;47H.[1|

The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier options, 
xterm",
per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html.  So it's trying
to modify function keys, or something.

ssh'ing in from a mac worked fine (TERM there was also xterm-256color),
as did ssh'ing from an ubuntu 19.04 system with gnome-terminal.
ssh'ing from another ubuntu 18.04 system exhibited the same problem.

So it's a little family squabble between focal's vim.tiny and ubuntu
18.04/bionic's gnome-terminal...?

Given how long 18.04's going to be supported, this seems worth resolving
somehow.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vim-tiny 2:8.1.2269-1ubuntu5 [modified: 
usr/share/vim/vim81/doc/help.txt usr/share/vim/vim81/doc/tags]
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
Uname: Linux 5.4.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 20 09:27:50 2020
InstallationDate: Installed on 2020-01-27 (83 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: vim (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873920

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1873920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849873] Re: Cannot compile programs that use gtk.h and -Werror

[Dan Kegel]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849873

Title:
  Cannot compile programs that use gtk.h and -Werror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1849873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849873] [NEW] Cannot compile programs that use gtk.h and -Werror

[Dan Kegel]

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   
Reading state information... Done
libgtk2.0-dev is already the newest version (2.24.32-4ubuntu1).
libgtk2.0-dev set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is 
deprecated [-Werror=deprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from foo.c:1:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from foo.c:1:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: error: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Werror=deprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from foo.c:1:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
cc1: all warnings being treated as errors
FAIL

This is a regression since ubuntu 19.04.

Noticed while building cef.

Workaround: -DGTK_DISABLE_DEPRECATED

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libgtk2.0-dev 2.24.32-4ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Fri Oct 25 09:48:14 2019
InstallationDate: Installed on 2019-10-18 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849873

Title:
  Cannot compile programs that use gtk.h and -Werror

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1849873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?

[Dan Kegel]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1732766/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

[Dan Kegel]

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 killall
timidity' resolved the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822426

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1828748] [NEW] gmtp can't connect to phone while gvfs-gphoto2-volume-monitor running

[Dan Kegel]

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 raw device(s)
Device 0 (VID=2e04 and PID=c025) is a Nokia 6.
   Found 1 device(s):
   Nokia: 6 (2e04:c025) @ bus 3, dev 35
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to 
initialize device
Unable to open raw device 0
OK.

As described in 
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/comments/40
killing gvfs-gphoto2-volume-monitor let mtd-detect and gmtd work properly.

Is the clash expected?

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gvfs-backends 1.40.1-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 12 15:21:27 2019
InstallationDate: Installed on 2017-04-29 (743 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: Upgraded to disco on 2019-05-12 (0 days ago)

** Affects: gvfs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828748

Title:
  gmtp can't connect to phone while gvfs-gphoto2-volume-monitor running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1828748/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822858] Re: In Ubuntu desktop, alt-tab twice does not return you to same window

[Dan Kegel]

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
   https://gitlab.gnome.org/689972

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822858

Title:
  In Ubuntu desktop, alt-tab twice does not return you to same window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1822858/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822858] [NEW] In Ubuntu desktop, alt-tab twice does not return you to same window

[Dan Kegel]

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 alt-tab, and fail miserably.  It's humiliating.
It's been like this for quite a while, and I'm sure it's by design,
and is the clever idea of somebody who doesn't actually use the desktop
like normal people do.

Today I got fed up and RTFM'd.

It's a GNOME 3 setting:
Settings > Devices > Keyboard > Navigation 
'Switch windows'
alt-tab

Fine.  Working again.  But why isn't this the default?

Please bring back the classic behavior of alt-tab, i.e. "pressing alt-tab
takes you to the window that was previously in front".

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822858

Title:
  In Ubuntu desktop, alt-tab twice does not return you to same window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1822858/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821483] Re: pip crashes when reinstalling native wheels

[Dan Kegel]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821483

Title:
  pip crashes when reinstalling native wheels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1821483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821247] Re: python-configparser 3.5.0-1 breaks the python backports namespace

[Dan Kegel]

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:
  python-configparser 3.5.0-1 breaks the python backports namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/configparser/+bug/1821247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812589] Re: pip's configparser dependency breaks backports namespace conventions

[Dan Kegel]

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 to Ubuntu.
https://bugs.launchpad.net/bugs/1812589

Title:
  pip's configparser dependency breaks backports namespace conventions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1812589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821483] Re: pip crashes when reinstalling native wheels

[Dan Kegel]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1821483

Title:
  pip crashes when reinstalling native wheels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1821483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821483] [NEW] pip crashes when reinstalling native wheels

[Dan Kegel]

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 fault (core dumped)

Running (on some machines, at least) under gdb is illuminating:
$ sudo apt install python-dbg
$ gdb python
(gdb) set args -m pip install simplejson
(gdb) run
Starting program: /usr/bin/python -m pip install simplejson
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Collecting simplejson
Installing collected packages: simplejson
Successfully installed simplejson-3.16.0

Program received signal SIGSEGV, Segmentation fault.
0x5562ae84 in visit_decref () at ../Modules/gcmodule.c:360
360 ../Modules/gcmodule.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0  0x5562ae84 in visit_decref ()
at ../Modules/gcmodule.c:360
#1  0x5562b004 in dict_traverse.lto_priv ()
at ../Objects/dictobject.c:2198
#2  0x55629da5 in subtract_refs ()
at ../Modules/gcmodule.c:385
#3  collect.lto_priv () at ../Modules/gcmodule.c:925
#4  0x55686721 in PyGC_Collect ()
at ../Modules/gcmodule.c:1440
#5  0x55685923 in Py_Finalize () at ../Python/pythonrun.c:455
#6  0x556a9bc8 in Py_Exit (sts=sts@entry=0)
at ../Python/pythonrun.c:1792

That backtrace that looks similar to 
https://github.com/pypa/pip/issues/5366

Happily, the fix that was committed for the bug seems simple and
plausible, and cherrypicking it seems to prevent the crash.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python-pip 9.0.1-2.3~ubuntu1
ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Mar 23 21:46:31 2019
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: python-pip
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-pip (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821483

Title:
  pip crashes when reinstalling native wheels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1821483/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821247] Re: python-configparser 3.5.0-1 breaks the python backports namespace

[Dan Kegel]

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(
 py_modules=modules,
 package_dir={'': 'src'},
 packages=find_packages('src'),
-namespace_packages=['backports'],
 include_package_data=True,
 zip_safe=False,
 install_requires=requirements,
--- configparser-3.5.0.orig/src/backports/__init__.py
+++ configparser-3.5.0/src/backports/__init__.py
@@ -3,9 +3,3 @@
 
 from pkgutil import extend_path
 __path__ = extend_path(__path__, __name__)
-
-try:
-import pkg_resources
-pkg_resources.declare_namespace(__name__)
-except ImportError:
-pass


** Bug watch added: github.com/jaraco/configparser/issues #17
   https://github.com/jaraco/configparser/issues/17

-- 
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:
  python-configparser 3.5.0-1 breaks the python backports namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/configparser/+bug/1821247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821247] [NEW] python-configparser 3.5.0-1 breaks the python backports namespace

[Dan Kegel]

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 fixed upstream in June 2018
https://github.com/jaraco/configparser/pull/22
and the current verison (3.7.3) is ok.

To see the bug in action:

# apt update
# apt install python-pip
# su ubuntu
$ pip install --user backports.os
$ python -c "from backports import os" && echo ok
ok
$ sudo apt install python-configparser
$ Setting up python-configparser (3.5.0-1) ...
$ python -c "from backports import os" && echo ok
Traceback (most recent call last):
  File "", line 1, in 
ImportError: cannot import name os
$ sudo apt remove python-configparser
$ pip install configparser
https://github.com/jaraco/configparser/pull/22
$ pip list | grep configparser
configparser (3.7.3)
$ python -c "from backports import os" && echo ok
ok

Please pull a fix for this configparser problem into Ubuntu 18.04.
Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python-configparser 3.5.0-1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 21 13:57:17 2019
PackageArchitecture: all
SourcePackage: configparser
UpgradeStatus: Upgraded to bionic on 2018-04-30 (325 days ago)

** Affects: configparser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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:
  python-configparser 3.5.0-1 breaks the python backports namespace

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/configparser/+bug/1821247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551351] Re: dhclient does not renew leases

[Dan Kegel]

(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 Ubuntu.
https://bugs.launchpad.net/bugs/1551351

Title:
  dhclient does not renew leases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1551351] Re: dhclient does not renew leases

[Dan Kegel]

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

Title:
  dhclient does not renew leases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819057] [NEW] uefi install of ubuntu 16.04 crashed installer

[Dan Kegel]

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
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CasperVersion: 1.376
Date: Thu Mar  7 20:05:23 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819057

Title:
  uefi install of ubuntu 16.04 crashed installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1819057/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819057] Re: uefi install of ubuntu 16.04 crashed installer

[Dan Kegel]

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 /dev/nvme0n1 
   g
   w
 run installer, choose erase disk and install ubuntu, select nvme... for 
bootloader destination
 reboot
 profit!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819057

Title:
  uefi install of ubuntu 16.04 crashed installer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1819057/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 (>= 8.9.3~dfsg-11ubuntu1~) but it is not 
going to be installed
  Depends: libjs-websocket but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

So it's more like "you can't count on being able to use xenial's nodejs on any 
system that 
has to build stuff against libssl-dev", which is pretty traumatic.

The situation's better on cosmic.  Backporting cosmic's nodejs to xenial isn't 
a great fix,
though, because it has a different soname, so any packages that need node's 
shared library
have to be rebuilt.  And that breaks our user apps.  As a workaround I'm using 
upstream's nodejs 8 on xenial, that seems to sidestep the openssl problem 
without causing the major version number problem.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 ).

debian/10.4.0_dfsg-2 has a few test failures (
https://github.com/nodejs/help/issues/1767 ), but seems promising.
Unfortunately, I'm not familiar with nodejs debian packaging, and I'm a
bit mystified by the test-assert failure.  Where's the best place to
discuss a backport like that?

** Bug watch added: github.com/nodejs/help/issues #1760
   https://github.com/nodejs/help/issues/1760

** Bug watch added: github.com/nodejs/help/issues #1767
   https://github.com/nodejs/help/issues/1767

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814607] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?

[Dan Kegel]

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 screen freezes

This was fine (i.e. zero hangs) on 18.04.1 + 
https://ubuntuforums.org/showthread.php?t=2400400
but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds)

The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds. Each hang 
usually lasted
for less than a second. Some lasted for a second and a half (maybe that was two 
hangs
back to back). Running xclock -update 1 seems to show that the hang extends to 
other apps,
i.e. when the fish hang, xclock also seems to hang. Running firefox in 
parallel, or a second
chromium window, seems to avoid the hang.

tail -f /var/log/syslog didn't show any new output during hangs.
(There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.)

I'll try to test on a non-Hades system.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb  4 16:50:27 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 
[VGA controller])
   Subsystem: Intel Corporation Device [8086:2073]
InstallationDate: Installed on 2019-02-04 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204)
MachineType: Intel Corporation NUC8i7HNK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601
dmi.board.name: NUC8i7HNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J68197-502
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i7HNK
dmi.product.version: J71486-502
dmi.sys.vendor: Intel Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic performance ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814607

Title:
  ubuntu 18.04.2 daily is janky with chromium on fishgl.com?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814607/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814606] [NEW] ubuntu 18.04.2 daily is janky with chromium on fishgl.com?

[Dan Kegel]

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 fps)
- after fish are happily swimming, watch them swim for 60 seconds, and count 
number of times the screen freezes

This was fine (i.e. zero hangs) on 18.04.1 + 
https://mzwiki.oblong.com/wiki/Hades_Canyon
but not fine on 18.04.2 (i.e. always hangs briefly within 60 seconds)

The last four times I ran this, I got 4, 2, 8, 3 hangs in 60 seconds.  Each 
hang usually lasted
for less than a second.  Some lasted for a second and a half (maybe that was 
two hangs
back to back).  Running xclock -update 1 seems to show that the hang extends to 
other apps,
i.e. when the fish hang, xclock also seems to hang.  Running firefox in 
parallel, or a second
chromium window, seems to avoid the hang.

tail -f /var/log/syslog didn't show any new output during hangs.
(There are a lot of gnome-shell stack dumps in /var/log/syslog, fwiw.)

I'll try to test on a non-Hades system.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb  4 16:15:59 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:694e] (rev c0) (prog-if 00 
[VGA controller])
   Subsystem: Intel Corporation Device [8086:2073]
InstallationDate: Installed on 2019-02-04 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190204)
MachineType: Intel Corporation NUC8i7HNK
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic 
root=UUID=861436ab-4967-41b5-99bc-64b8726682a5 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: HNKBLi70.86A.0049.2018.0801.1601
dmi.board.name: NUC8i7HNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J68197-502
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0049.2018.0801.1601:bd08/01/2018:svnIntelCorporation:pnNUC8i7HNK:pvrJ71486-502:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-502:cvnIntelCorporation:ct3:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i7HNK
dmi.product.version: J71486-502
dmi.sys.vendor: Intel Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic performance ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814606

Title:
  ubuntu 18.04.2 daily is janky with chromium on fishgl.com?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814606/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812589] Re: pip's configparser dependency breaks backports namespace conventions

[Dan Kegel]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1812589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812589] Re: pip's configparser dependency breaks backports namespace conventions

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1812589

Title:
  pip's configparser dependency breaks backports namespace conventions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1812589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 ubuntu.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708674] Re: Haveged with AppArmor issue on Upstart

[Dan Kegel]

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 usr.sbin.haveged workaround originally
because it looked scary, but on a second read it's very clear and easy.
Applied it to all my ubu1604 boxes and rebooted, all are running haveged
now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708674

Title:
  Haveged with AppArmor issue on Upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haveged/+bug/1708674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708674] Re: Haveged with AppArmor issue on Upstart

[Dan Kegel]

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 comm="haveged" requested_mask="c" 
denied_mask="c" fsuid=0 ouid=0

so it looks like this hit me.  I'm running ubuntu 16.04 with haveged
1.9.1-3.

Looking at ubuntu 18.04's haveged 1.9.1-6, I see it has a fix for a similar 
problem, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824179
Applying that as a workaround by editing /lib/systemd/system/haveged.service 
like so:
-After=systemd-random-seed.service
+After=apparmor.service systemd-random-seed.service
seems to work.

** Bug watch added: Debian Bug tracker #824179
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824179

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708674

Title:
  Haveged with AppArmor issue on Upstart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haveged/+bug/1708674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 900901]

[Dan Kegel]

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 notifications about this bug go to:
https://bugs.launchpad.net/wine/+bug/900901/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 overwrite the standard ones).

I'll keep slogging.  At some point I'll try libssh-gcrypt-dev et al,
haven't gotten to that yet.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 would like that, though; we much prefer
LTS.

I suppose libxmltooling7 / libxml-security-c-dev / etc. could be
backported from 18.10, with a different -dev package name, so that
desperate people could get things building by changing -dev packages.  I
wonder how much of the sweater that would unravel

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804343] Re: apt: Misleadingly reports Hash Sum mismatch if package is missing stronger hashes

[Dan Kegel]

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 package is missing
  stronger hashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804343] [NEW] apt: Misleadingly reports Hash Sum mismatch if package is missing stronger hashes

[Dan Kegel]

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 http://buildbot.example.com/dev-bionic/apt bionic/main amd64 
python-swagger-spec-validator all 2.1.0-1 [14.8 kB]
Err:1 http://buildbot.example.com/dev-bionic/apt bionic/main amd64 
python-swagger-spec-validator all 2.1.0-1 
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:e5a36ff20cca22441dc0fe1a10566db98af9aee9e09c503179e29ccb33aac4ad
   - SHA1:3cd17f1b617277ad213f09e0f274d2ec740d44f0 [weak]
   - MD5Sum:3f310d6189ba23fb277145088d8e976e [weak]
   - Filesize:14812 [weak]
   - 
SHA512:7ad6456fe96bffe28bdb976c04a82b5ebb9b5b7c14f749c9b339147c124128692cbf4aa3d1d41cffb3079406c6e057bf90fdf2bade3f9ec22d1695f63b270f68
  Hashes of received file:
   - 
SHA512:edb96fd9989eb39d7d0984928a49fa8f8dbc23667585d30532751c730c8877298a7e55e99ed9f3ccb6923fe23eddffa5a8b205e3067624b7ef7317390026d08e
   - SHA256:e5a36ff20cca22441dc0fe1a10566db98af9aee9e09c503179e29ccb33aac4ad
   - SHA1:3cd17f1b617277ad213f09e0f274d2ec740d44f0 [weak]
   - MD5Sum:3f310d6189ba23fb277145088d8e976e [weak]
   - Filesize:14812 [weak]
  Last modification reported: Tue, 18 Sep 2018 19:28:25 +
Fetched 14.8 kB in 0s (1,002 kB/s)   
W: Sources disagree on hashes for supposely identical version '2.1.0-1' of 
'python-swagger-spec-validator:amd64'.
E: Failed to fetch 
http://buildbot.example.com/dev-bionic/apt/pool/main/s/swagger-spec-validator/python-swagger-spec-validator_2.1.0-1_all.deb
  Hash Sum mismatch

The downloaded file was correct.  The 'expected' SHA512 sum appears to
have been randomly generated.

Vaguely resembles upstream bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=827758

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.6
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 20 17:06:06 2018
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2018-04-30 (204 days ago)

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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 package is missing
  stronger hashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1804343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

{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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 layer of confusion.

Giving up on Ubuntu's node seems like the best option at the moment,
which makes me sad.  But since the next version of node uses the 'right'
version of openssl for ubuntu 18.04, it's very very tempting to
grab that from debian and slam it in to our 18.04 under a different name
(as we did with nodejs6 for a while).

I'm fighting a rising tide of "just use docker and upstream everything",
so if you don't hear from me anymore, I may have drowned :-)

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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 that's
interesting and surprising news.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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) but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

In other words, the current nodejs-dev does not fit into the Ubuntu
18.04 ecosystem.

-- 
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796168] [NEW] "vagrant plugin install vagrant-scp" fails

[Dan Kegel]

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. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 1.45.0)
  Activated fog-core-1.45.0
  which does not match conflicting dependency (~> 1.43.0)

  Conflicting dependency chains:
fog-core (= 1.45.0), 1.45.0 activated

  versus:
vagrant-libvirt (> 0), 0.0.41 activated, depends on
fog-core (~> 1.43.0)

(don't know if the 'box add' is required)

This was reported earlier at
https://github.com/dotless-de/vagrant-vbguest/issues/292
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896904
https://tutorials.technology/solved_errors/Vagrant-plugin-install--conflicting-dependencies-fog-core--~%3E-1_43_0--and-fog-core1_45_0-.html

In all three cases, the workaround was 'install vagrant 2.0.3 from
vendor'.

And indeed, installing 2.0.4 from vendor solved the problem.

So... please update!
They're up to 2.1.5 now, dunno whether latest 2.0.x or 2.1.x is appropriate.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vagrant 2.0.2+dfsg-2ubuntu8
ProcVersionSignature: User Name 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Oct  4 19:13:52 2018
PackageArchitecture: all
SourcePackage: vagrant
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: vagrant (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
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 vagrant-scp" fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1796168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796168] Re: "vagrant plugin install vagrant-scp" fails

[Dan Kegel]

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 vagrant-scp" fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1796168/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing build failures

[Dan Kegel]

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 libcurl4-openssl-dev libssh-dev libssl-dev,
  causing build failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing build failures

[Dan Kegel]

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 with libcurl4-openssl-dev libssh-dev libssl-dev,
  causing build failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing build failures

[Dan Kegel]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev,
  causing build failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] Re: nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing build failures

[Dan Kegel]

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 using
alternatives for the commands.)

-- 
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 libcurl4-openssl-dev libssh-dev libssl-dev,
  causing build failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794589] [NEW] nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing build failures

[Dan Kegel]

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 packages fail to build.

Commenting out universe from bionic-updates in /etc/apt/sources.list
would work around this, but that's not going to fly for everybody.

nodejs appears to be the tail wagging the dog now, and that's rather
uncomfortable.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nodejs-dev (not installed)
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 26 11:03:51 2018
SourcePackage: nodejs
UpgradeStatus: Upgraded to bionic on 2018-04-30 (148 days ago)

** Affects: nodejs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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 libcurl4-openssl-dev libssh-dev libssl-dev,
  causing build failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Dan Kegel]

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

[Dan Kegel]

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 my Hades Canyon, I now see a 16384 x 16384 
limit:
$ xrandr
Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384
Three screens horizontally work.
https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg24954.html looks 
related.

I have not yet tested on HD graphics with the new kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714178

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1714178/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791437] Re: Can't use pbuilder inside simple lxc container?

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1791437

Title:
  Can't use pbuilder inside simple lxc container?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1791437/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791437] Re: Can't use pbuilder inside simple lxc container?

[Dan Kegel]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791437

Title:
  Can't use pbuilder inside simple lxc container?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1791437/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791437] [NEW] Can't use pbuilder inside simple lxc container?

[Dan Kegel]

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 buildpackage --git-dist=bionic --git-pbuilder

This failed with

+ DIST=bionic git-pbuilder create
I: Invoking pbuilder
I: forking: pbuilder create --buildplace /var/cache/pbuilder/base-bionic.cow 
--mirror http://archive.ubuntu.com/ubuntu --distribution bionic --no-targz 
--extrapackages cowdancer
W: /home/ubuntu/.pbuilderrc does not exist
I: Running in no-targz mode
I: Distribution is bionic.
I: Current time: Sat Sep  8 14:40:20 UTC 2018
I: pbuilder-time-stamp: 1536417620
I: Building the build environment
I: running debootstrap
/usr/sbin/debootstrap
mknod: /var/cache/pbuilder/base-bionic.cow/test-dev-null: Operation not 
permitted
E: Cannot install into target '/var/cache/pbuilder/base-bionic.cow' mounted 
with noexec or nodev

Sad face.  Not sure who's at fault here, is it me, debootstrap,
pbuilder, or gbp?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pbuilder 0.229.1
ProcVersionSignature: User Name 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Sep  8 14:47:59 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: pbuilder
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pbuilder (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791437

Title:
  Can't use pbuilder inside simple lxc container?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1791437/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770742] Re: Cannot find -lGL

[Dan Kegel]

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 '/usr/lib/x86_64-linux-gnu/libGL.so': No such file or 
directory
ls: cannot access '/usr/lib/x86_64-linux-gnu/libGLESv2.so': No such file or 
directory
lrwxrwxrwx 1 root root   22 Jun  5 07:16 
/usr/lib/x86_64-linux-gnu/libGLdispatch.so -> libGLdispatch.so.0.0.0
...
-rw-r--r-- 1 root root 4697 Jan 25  2018 /usr/share/doc/libglvnd-dev/copyright

Doing

sudo apt install --reinstall libglvnd-dev

resolved the problem here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770742

Title:
  Cannot find -lGL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1770742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?

[Dan Kegel]

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 530?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732766/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1530204] Re: "composer create-project drupal/drupal hellodrupal 8.0.0" throws error

[Dan Kegel]

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

That completed with some warnings and no crash.

This bug can be closed as 'fixed in 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/1530204

Title:
  "composer create-project drupal/drupal hellodrupal 8.0.0" throws error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/composer/+bug/1530204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787299] [NEW] Frequent PCIe bus error on device 8086:a292

[Dan Kegel]

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 warning I'm seeing:

Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113915] pcieport :00:1c.2: 
AER: Corrected error received: id=00e2
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113931] pcieport :00:1c.2: 
PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter 
ID)
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113942] pcieport :00:1c.2:   
device [8086:a292] error status/mask=1000/2000
Aug 15 00:08:18 rbb-ubu1804-1 kernel: [24014.113950] pcieport :00:1c.2:
[12] Replay Timer Timeout


Happens kind of randomly; dmesg shows it happened 13 times in first 9 minutes;
syslog shows it happened 841 times in about 12 hours.

Also see a bit of this:

Aug 15 15:59:40 rbb-ubu1804-1 kernel: [  385.278631] pcieport :00:1c.2: 
AER: Multiple Corrected error received: id=00e2
Aug 15 15:59:40 rbb-ubu1804-1 kernel: [  385.278635] pcieport :00:1c.2: 
can't find device of ID00e2

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  buildbot   1881 F pulseaudio
 /dev/snd/controlC0:  buildbot   1881 F pulseaudio
Date: Wed Aug 15 15:55:59 2018
HibernationDevice: RESUME=UUID=d0b594a3-6d1f-41af-bde1-89c3ec729d02
InstallationDate: Installed on 2018-08-14 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 8930
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/17/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.10
dmi.board.name: 0DF42J
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.10:bd05/17/2018:svnDellInc.:pnXPS8930:pvr1.0.10:rvnDellInc.:rn0DF42J:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.version: 1.0.10
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787299

Title:
  Frequent PCIe bus error on device 8086:a292

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774425] Re: i915 driver limits virtual resolution to 8192x8192

[Dan Kegel]

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-
configurations.html

** Bug watch added: freedesktop.org Bugzilla #102508
   https://bugs.freedesktop.org/show_bug.cgi?id=102508

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774425

Title:
  i915 driver limits virtual resolution to 8192x8192

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1774425] Re: i915 driver limits virtual resolution to 8192x8192

[Dan Kegel]

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 could be for the
lack of the raised limit when using 7th generation chips, if the limit is really
higher there?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774425

Title:
  i915 driver limits virtual resolution to 8192x8192

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"

[Dan Kegel]

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 is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776260

Title:
  Can't use three monitors properly; "xrandr: screen cannot be larger
  than 8192x8192"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"

[Dan Kegel]

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 http://webglstats.com/webgl2/parameter/MAX_TEXTURE_SIZE

===
+ uname -a
Linux rbb-ubu1604-6 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:15:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ grep maximum
+ xrandr
Screen 0: minimum 8 x 8, current 3840 x 6480, maximum 32767 x 32767
+ lspci
+ grep VGA
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
+ glxinfo
+ grep string
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1060 6GB/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 390.67
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 390.67
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 390.67
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

===

+ uname -a
Linux rbb-ubu1804-5 4.17.0-999-generic #201806080237 SMP Fri Jun 8 06:41:11 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ xrandr
+ grep maximum
Screen 0: minimum 320 x 200, current 7680 x 2160, maximum 16384 x 16384
+ lspci
+ grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 
[Radeon RX Vega M] (rev c0)
+ glxinfo
+ grep string
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: AMD VEGAM (DRM 3.26.0, 4.17.0-999-generic, LLVM 6.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel
OpenGL core profile shading language version string: 4.50
OpenGL version string: 3.1 Mesa 18.2.0-devel
OpenGL shading language version string: 1.40
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.2.0-devel
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

===

+ uname -a
Linux rbb-ubu1804-6 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ xrandr
+ grep maximum
Screen 0: minimum 320 x 200, current 3840 x 6480, maximum 8192 x 8192
+ lspci
+ grep VGA
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 
09)
+ glxinfo
+ grep string
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Iris Pro Graphics 580 (Skylake GT4e) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.0.0-rc5
OpenGL core profile shading language version string: 4.50
OpenGL version string: 3.0 Mesa 18.0.0-rc5
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.0.0-rc5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

-- 
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 monitors properly; "xrandr: screen cannot be larger
  than 8192x8192"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1776260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776260] Re: Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"

[Dan Kegel]

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 monitors properly; "xrandr: screen cannot be larger
  than 8192x8192"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776260] [NEW] Can't use three monitors properly; "xrandr: screen cannot be larger than 8192x8192"

[Dan Kegel]

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
ports: hdmi, mini-dp, or type c; all three show up in xrandr as DisplayPort).
It even seems to work ok when I plug in two. Doesn't matter which two.

When I plug in all three, and boot to normal graphical.target mode with the 
usual gdm
greeter, one of the three screens does show gdm, and allows me to log in.
But I can't seem to get all three screens active at the same time.

Falling back to old school tools, I did 'sudo systemctl set-default 
multi-user.target'
and rebooted.  Logging in, creating a trivial .xinitrc, and doing 'startx'
started the X server, and all three screens show the same output.
So far so good.

But trying to arrange them like this:

$ xrandr --auto --output DP-2 --right-of DP-1 --output DP-3 --right-of
DP-2

fails with

xrandr: screen cannot be larger than 8192x8192 (desired size 11520x2160)

Using --above instead of --right-of works, but that's not how the
monitors are arranged.

I tried creating /usr/share/X11/xorg.conf.d/85-screen.conf
containing

Section "Screen"
Identifier  "Default Screen"   
DefaultDepth24 
SubSection "Display"
  Virtual 11520 6480
EndSubSection
EndSection

and applied it by killing X and doing startx again,
but that gave very strange results: the mouse showed up on two
screens, but .xinit didn't seem to have taken effect, and the
content on the screen was the same as before startx.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jun 11 09:49:40 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Iris Pro Graphics 580 [8086:2064]
InstallationDate: Installed on 2018-06-08 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-22-generic 
root=UUID=80ac733c-b098-4643-84a4-fe81874f2101 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-404
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

-- 
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 monitors properly; "xrandr: screen cannot be larger
  than 8192x8192"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1776260/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1460447] Re: Boot slow, "scanning for btrfs filesystems" takes 100 seconds

[Dan Kegel]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447

Title:
  Boot slow, "scanning for btrfs filesystems" takes 100 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460447/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1560942] Re: Support swap

[Dan Kegel]

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:
https://bugs.launchpad.net/snapd/+bug/1560942/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

[Dan Kegel]

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 (xdisplay),
(gdb) list
320 
321   if (!XGetGeometry (xdisplay, xpixmap, _return,
322  _ret, _ret, _ret, _ret, _ret, 
_ret))
323 return NULL;
324 
325   return cairo_xlib_surface_create_with_xrender_format (xdisplay, 
xpixmap, DefaultScreenOfDisplay (xdisplay),
326 
pict_format_for_depth (xdisplay, depth_ret), w_ret, h_ret);
327 }
328 
329 static gboolean
(gdb) print depth_ret
$2 = 16

So, not corrupt, just not handled?

FWIW, see also https://bugzilla.redhat.com/show_bug.cgi?id=1239129

I'm having a little trouble believing my screen was using 16 bit mode,
could one of the cached icons have been 16 bits?

** Bug watch added: Red Hat Bugzilla #1239129
   https://bugzilla.redhat.com/show_bug.cgi?id=1239129

-- 
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 crashed in standard_pict_format_for_depth()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

[Dan Kegel]

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 it properly and
add a link here.

I still have the .crash file if you want it.

-- 
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 crashed in standard_pict_format_for_depth()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()

[Dan Kegel]

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.
https://bugs.launchpad.net/bugs/1766938

Title:
  gnome-shell crashed in standard_pict_format_for_depth()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashes after a few seconds

[Dan Kegel]

Ah, that assert is in mutter.

$ mkdir ~/xsrc
$ cd ~/xsrc
$ apt-get source libmutter-2-0
$ cd ~
$ apport-retrace -g _usr_bin_gnome-shell.1000.crash
(gdb) bt
...
(gdb) frame 7
#7  0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303
303 x11/iconcache.c: No such file or directory.
(gdb) directory xsrc/mutter-3.28.1/src
(gdb) list 291
291 static int
292 standard_pict_format_for_depth (int depth)
293 {
294   switch (depth)
295 {
296 case 1:
297   return PictStandardA1;
298 case 24:
299   return PictStandardRGB24;
300 case 32:
301   return PictStandardARGB32;
302 default:
303   g_assert_not_reached ();
304 }

FWIW, that code was added in
https://gitlab.gnome.org/GNOME/mutter/commit/9b903e93e3cd0601b436c55b7cea1fbecf29895f

So... uh... maybe some icon on my system is making it unhappy?

I gather gtk-update-icon-cache is involved?

buildbot@rbb-ubu1804-3:~$ ls -l /usr/share/icons/*/*.cache
-rw-r--r-- 1 root root  35776 Apr 24 14:57 
/usr/share/icons/Adwaita/icon-theme.cache
-rw-r--r-- 1 root root  20312 Apr 25 09:40 
/usr/share/icons/hicolor/icon-theme.cache
-rw-r--r-- 1 root root  49808 Apr 24 14:39 
/usr/share/icons/HighContrast/icon-theme.cache
-rw-r--r-- 1 root root  26816 Apr 24 14:57 
/usr/share/icons/Humanity-Dark/icon-theme.cache
-rw-r--r-- 1 root root 327184 Apr 24 14:57 
/usr/share/icons/Humanity/icon-theme.cache
-rw-r--r-- 1 root root628 Apr 24 14:57 
/usr/share/icons/LoginIcons/icon-theme.cache
-rw-r--r-- 1 root root  54104 Apr 24 14:57 
/usr/share/icons/ubuntu-mono-dark/icon-theme.cache
-rw-r--r-- 1 root root  55040 Apr 24 14:57 
/usr/share/icons/ubuntu-mono-light/icon-theme.cache

But now I can't get it to crash anymore.
so maybe I accidentally fixed it by installing some package that updated the 
icon caches...?

$ grep hicolor /var/log/dpkg.log
...
2018-04-24 14:42:29 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-24 15:33:00 status installed hicolor-icon-theme:all 0.17-2
...
2018-04-25 09:40:43 status installed hicolor-icon-theme:all 0.17-2

Hrmf.  My uneducated theory is that an icon cache was corrupt, but is fine now.
Who knows?

-- 
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 crashes after a few seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashes after a few seconds

[Dan Kegel]

Doesn't sound like a release blocker offhand, but sheesh.  Boot loops
are no fun.

-- 
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 crashes after a few seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] Re: gnome-shell crashes after a few seconds

[Dan Kegel]

apport-retrace -g _usr_bin_gnome-shell.1000.crash

bt

indicates it's an assert in standard_pict_format_for_depth:

(gdb) bt
#0  0x7f75c68f0727 in raise (sig=) at 
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x56149221ba6b in dump_gjs_stack_on_signal_handler (signo=6) at 
../src/main.c:367
#2  0x7f75c68f0890 in  () at 
/lib/x86_64-linux-gnu/libpthread.so.0
#3  0x7f75c652be97 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:51
#4  0x7f75c652d801 in __GI_abort () at abort.c:79
#5  0x7f75c868dfa5 in g_assertion_message () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f75c868e00a in g_assertion_message_expr () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f75c6bb5fbe in standard_pict_format_for_depth (depth=) at x11/iconcache.c:303
#8  0x7f75c6bb5fbe in pict_format_for_depth (depth=, 
xdisplay=0x56149472f000) at x11/iconcache.c:310
#9  0x7f75c6bb5fbe in surface_from_pixmap 
(xdisplay=xdisplay@entry=0x56149472f000, xpixmap=xpixmap@entry=31457330, 
height=, width=)
at x11/iconcache.c:325
#10 0x7f75c6bb6117 in try_pixmap_and_mask (display=0x5614949c0200, 
src_pixmap=src_pixmap@entry=31457330, src_mask=src_mask@entry=31457332, 
iconp=iconp@entry=0x7fff9d183198) at x11/iconcache.c:345
#11 0x7f75c6bb65a4 in meta_read_icons (screen=0x56149454bcd0, 
xwindow=31457316, icon_cache=0x561495d18df8, wm_hints_pixmap=31457330, 
wm_hints_mask=31457332, iconp=iconp@entry=0x7fff9d183198, ideal_width=96, 
ideal_height=96, mini_iconp=0x7fff9d1831a0, ideal_mini_width=16, 
ideal_mini_height=16) at x11/iconcache.c:546
#12 0x7f75c6bbd3c1 in meta_window_x11_update_icon (window=0x561495d18e30, 
icon=0x7fff9d183198, mini_icon=0x7fff9d1831a0) at x11/window-x11.c:1472
#13 0x7f75c6ba2608 in meta_window_update_icon_now 
(window=window@entry=0x561495d18e30, force=force@entry=1) at core/window.c:5326
#14 0x7f75c6ba9abd in _meta_window_shared_new 
(display=display@entry=0x5614949c0200, screen=screen@entry=0x56149454bcd0, 
client_type=client_type@entry=META_WINDOW_CLIENT_TYPE_X11, 
surface=surface@entry=0x0, xwindow=xwindow@entry=31457316, 
existing_wm_state=existing_wm_state@entry=0, effect=, 
attrs=)
at core/window.c:1148
#15 0x7f75c6bbf6a0 in meta_window_x11_new 
(display=display@entry=0x5614949c0200, xwindow=31457316, 
must_be_viewable=must_be_viewable@entry=0, 
effect=effect@entry=META_COMP_EFFECT_CREATE) at x11/window-x11.c:3148
#16 0x7f75c6bb4554 in handle_other_xevent 
(display=display@entry=0x5614949c0200, event=event@entry=0x7fff9d183640) at 
x11/events.c:1372
#17 0x7f75c6bb4deb in meta_display_handle_xevent (event=0x7fff9d183640, 
display=0x5614949c0200) at x11/events.c:1791
#18 0x7f75c6bb4deb in xevent_filter (xevent=0x7fff9d183640, 
event=, data=0x5614949c0200) at x11/events.c:1830
#19 0x7f75c5e07edf in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#20 0x7f75c5e081c9 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#21 0x7f75c5dd2d70 in gdk_display_get_event () at 
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#22 0x7f75c5e07f72 in  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#23 0x7f75c8667287 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f75c86674c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f75c86677d2 in g_main_loop_run () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f75c6b94a7c in meta_run () at core/main.c:664

-- 
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 crashes after a few seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766938] [NEW] gnome-shell crashes after a few seconds

[Dan Kegel]

Public bug reported:

I have a fleet of Dell T7500's, a few Dell 3620's, a Skull Canyon, and a
Hades Canyon, and a few other odds and ends, running a mix of ubuntu
16.04 and 17.10.

On one of the T7500 ubuntu 17.10 boxes (nvidia 340 package, Quadro K5000 card),
I did sudo "do-release-upgrade -d".  Went fine, but on reboot, the desktop would
come up for about ten seconds, then the system would shut down.

Did 
  systemctl set-default multi-user.target
then removed all traces of the proprietary driver with
  sudo apt remove --purge nvidia-340 nvidia-opencl-icd-340 nvidia-settings 
nvidia-384 nvidia-opencl-icd-384 nvidia-prime  libcuda1-340
and rebooted.  Logging in to the console and running 'startx' reproduces the 
problem reliably, and does not shut down the system.

Installing lwm, and a .xinitrc that started an xterm, let startx succeed, and
the system was stable running firefox, so it's not an obvious graphics problem.

/var/log/syslog says

Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: **
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: 
mutter:ERROR:x11/iconcache.c:303:standard_pict_format_for_depth: code should 
not be reached
Apr 25 09:59:41 rbb-ubu1710-3 org.gnome.Shell.desktop[3936]: == Stack trace for 
context 0x556d30f3c4c0 ==
Apr 25 09:59:41 rbb-ubu1710-3 dbus-daemon[690]: [system] Successfully activated 
service 'org.freedesktop.fwupd'
Apr 25 09:59:41 rbb-ubu1710-3 systemd[1]: Started Firmware update daemon.
Apr 25 09:59:42 rbb-ubu1710-3 PackageKit: get-updates transaction 
/2379_acbceaca from uid 1000 finished with success after 1175ms
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session[3605]: gnome-session-binary[3605]: 
CRITICAL: We failed, but the fail whale is dead. Sorry
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: Unrecoverable failure 
in required component org.gnome.Shell.desktop
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: WARNING: App 
'org.gnome.Shell.desktop' respawning too quickly
Apr 25 09:59:42 rbb-ubu1710-3 gnome-session-binary[3605]: CRITICAL: We failed, 
but the fail whale is dead. Sorry

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 10:06:55 2018
DisplayManager:
 
GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-01-04 (111 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170918)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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 crashes after a few seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766102] Re: dh_installchangelogs fails if version is 0

[Dan Kegel]

(Right... that's why I linked to that bug.  
It would have been nice if I had noticed this problem a month ago, apologies...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766102

Title:
  dh_installchangelogs fails if version is 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1766102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766102] [NEW] dh_installchangelogs fails if version is 0

[Dan Kegel]

Public bug reported:

If the package's debian/changelog has a first line with version 0,
dh_installchangelogs fails with

dh_installchangelogs: changelog parse failure

This is fixed upstream, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=894895

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: debhelper 11.1.6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
Date: Sun Apr 22 16:31:02 2018
PackageArchitecture: all
SourcePackage: debhelper
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: debhelper (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766102

Title:
  dh_installchangelogs fails if version is 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1766102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761932] [NEW] make -j2 aborts with "make[3]: *** read jobs pipe: Success. Stop."

[Dan Kegel]

Public bug reported:

Porting a particular build of v8 from ubuntu 17.10 to ubuntu 18.04 circa beta 2,
its make failed at -j2, but succeeded at -j1.
The error message was odd:

...
make[3]: Entering directory '/home/buildbot/src/oblong-v8/out/v8/out'
testing/gtest.target.x64.release.mk:229: warning: overriding recipe for target 
'/home/buildbot/src/oblong-v8/out/v8/out/x64.release/libgtest.a'
testing/gtest.host.x64.release.mk:221: warning: ignoring old recipe for target 
'/home/buildbot/src/oblong-v8/out/v8/out/x64.release/libgtest.a'
make[3]: Leaving directory '/home/buildbot/src/oblong-v8/out/v8/out'
make[3]: *** read jobs pipe: Success.  Stop.
make[3]: *** Waiting for unfinished jobs
make[3]: Entering directory '/home/buildbot/src/oblong-v8/out/v8/out'
  
/home/buildbot/src/oblong-v8/out/v8/third_party/llvm-build/Release+Asserts/bin/clang++
 '-DCR_CLANG_REVISION=278861-1'... -c -o 
/home/buildbot/src/oblong-v8/out/v8/out/x64.release/obj.target/v8_base/src/address-map.o
 ../src/address-map.cc
make[3]: Leaving directory '/home/buildbot/src/oblong-v8/out/v8/out'
make[3]: *** write jobserver: Bad file descriptor.  Stop.
Makefile:318: recipe for target 'x64.release' failed
make[2]: *** [x64.release] Error 2
make[2]: INTERNAL: Exiting with 1 jobserver tokens available; should be 2!
Makefile:48: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/buildbot/src/oblong-v8'
dh_auto_build: make -j8 -O returned exit code 2
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui -b -j8 failed
...

This is on a machine with 32GB of RAM.

The problem reproduces quickly and reliably.  Happy to try other
versions of make and/or provide more data.

** Affects: make (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "apport report"
   
https://bugs.launchpad.net/bugs/1761932/+attachment/5105088/+files/apport.make.tkkb4vy9.apport

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761932

Title:
  make -j2 aborts with "make[3]: *** read jobs pipe: Success.  Stop."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make/+bug/1761932/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655709] Re: Spurious crash report dialog on every login

[Dan Kegel]

Still in ubuntu 17.10 with nvidia card.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655709

Title:
  Spurious crash report dialog on every login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655709/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734575] Re: guile-2.2 FTBFS on bionic on x86_64?

[Dan Kegel]

Out of 51 tries, a little more than half fail:
 29 FAIL: test-out-of-memory
 22 PASS: test-out-of-memory

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734575

Title:
  guile-2.2 FTBFS on bionic on x86_64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1734575/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734575] Re: guile-2.2 FTBFS on bionic on x86_64?

[Dan Kegel]

Nevermind, it failed on the next try.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734575

Title:
  guile-2.2 FTBFS on bionic on x86_64?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1734575/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs